GDMO—the Guidelines for the Definition of Managed Objects—is a template-based notation for specifying managed objects in the OSI systems-management paradigm. It is standardized as ITU-T X.722 and paired with ISO/IEC 10165-4. GDMO describes the managed resources or services and characteristics such as their attributes, behavior, notifications, actions, and naming; it is not a universal language for every network-management interface.
What does GDMO mean?
GDMO expands to Guidelines for the Definition of Managed Objects. Its standard identity is ITU-T Recommendation X.722, paired with ISO/IEC 10165-4. X.722 dates to 1992, and the standards history includes a 1997 amendment summary; GDMO is therefore an established standards notation, not a newly introduced method. ITU-T X.722 · ISO/IEC 10165-4 · ITU-T X.722 amendment summary
As an Amazon Associate I earn from qualifying purchases.
What does GDMO define?
In OSI systems management, a managed object is an abstract representation of a resource or service that is subject to management. GDMO provides a consistent way to specify such objects and their characteristics and behavior. A definition can describe the object’s class, attributes, actions, notifications, naming, and related behavior. ITU-T M.3020 (04/2023) describes GDMO templates as part of the OSI information-model specification.
How does its template approach work?
Rather than expressing every detail in one undifferentiated description, GDMO organizes definitions into related templates. The managed-object-class template is the central organizing point; other templates supply additional parts of the definition.
#1 Best Overall
- Packages group details associated with a managed-object class.
- Attributes describe information associated with an object.
- Behavior specifies relevant object behavior.
- Notifications describe events an object can report.
- Actions and parameters describe management operations and their associated inputs or details.
- Name bindings describe naming relationships and instances of a class.
This list is an orientation to the notation, not a replacement for the normative X.722 text. ITU-T M.3020 also refers to error and exception specifications in its description of the OSI design specification context.
Where does GDMO fit in network management?
GDMO belongs to the OSI systems-management paradigm. It should not be treated as the common definition language for all network-management systems: the appropriate specification method depends on the management paradigm and the language selected for that paradigm. ITU-T M.3020 (04/2023) makes this distinction when discussing management-interface specification methodology. Its characterization is specific to the OSI approach, where GDMO templates are used for managed-object classes and related design details.
What does the standards history indicate?
The ITU-T amendment summary for X.722 describes, among other changes, adding a NO-MODIFY syntax element to GDMO Package Templates and addressing migration from ASN.1:1990 to ASN.1:1994 in X.700-series specifications. This is an example of material in that amendment summary, not evidence about how every current implementation behaves.
Free tools Windows power users keep installed
One-click scans. No signup required.
How should GDMO be compared with another approach?
A meaningful comparison starts by identifying the management paradigm each approach serves. Then compare how each defines information, represents object identity and naming, and expresses attributes and behavior. Those are useful comparison dimensions; the cited standards material does not establish a detailed feature-by-feature comparison between GDMO and SMI, CIM/MOF, or other management-information approaches.
Quick Recap
Rank #4
Rank #3
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
