Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 10165-5-95 (2003): Generic Management Information for OSI Network Management
Technical Guide to ISO/IEC 10165-5 – Structure of Management Information Part 5
Introduction to IEC 10165-5-95 (2003)
IEC 10165-5-95 (also published as ISO/IEC 10165-5:1995, confirmed and updated through 2003) is a pivotal standard within the Open Systems Interconnection (OSI) management framework. It defines the Generic Management Information (GMI) model, providing a set of common managed object classes, attributes, notifications, and behaviour that form the foundation for building interoperable network management systems. The standard is part of the larger Structure of Management Information (SMI) family (ISO/IEC 10165), which establishes the methodology for specifying management information in an OSI environment.
Originally released in 1995 and reaffirmed with technical enhancements in 2003, IEC 10165-5-95 addresses the need for a reusable, standardised set of management constructs that can be applied across diverse network elements and services. It enables consistency in how management information is defined, named, and accessed, thereby reducing integration complexity and promoting multivendor interoperability.
PRACTICAL TIP: When deploying OSI-based management systems, rely on the object classes defined in IEC 10165-5-95 as a starting point for your Management Information Base (MIB). This accelerates development and ensures alignment with international practices.
Scope and Applicability
The scope of IEC 10165-5-95 encompasses the specification of generic management information that is independent of any particular network technology or application domain. Key aspects include:
- Definition of managed object classes (e.g.,
top,system,alarmRecord) that can be specialised for specific resources. - Standardised naming structure and naming attributes (e.g.,
objectClass,nameBinding). - Behavioural definitions for management operations (action, create, delete, get, set).
- Standard notifications (e.g.,
attributeValueChange,objectCreation,objectDeletion). - Guidelines for extending the generic model to build domain-specific management information.
The standard is applicable to any OSI management environment, including TMN (Telecommunications Management Network), enterprise network management, and industrial automation systems where X.700-series management standards are used.
Technical Requirements
IEC 10165-5-95 mandates a set of core managed object classes and associated properties. Conformant implementations must support at least the following generic classes and their behaviour as defined in the standard:
| Managed Object Class | Key Attribute(s) | Notifications | Behavioral Package |
|---|---|---|---|
top | objectClass, nameBinding, packages | objectCreation, objectDeletion | TopPackage |
system | systemDescription, systemAdminState, systemOpState | stateChange, attributeValueChange | SystemPackage |
alarmRecord | alarmType, probableCause, perceivedSeverity | alarmNotification | AlarmRecordPackage |
logRecord | logRecordId, loggingTime, recordData | logRecordNotification | LogRecordPackage |
eventForwardingDiscriminator | discriminatorId, destinationAddress, eventTypes | notification | DiscriminatorPackage |
Each managed object class is defined using the GDMO (Guidelines for Definition of Managed Objects) notation, as referenced by ISO/IEC 10165-4. The standard also specifies how inheritance and specialisation should be applied to create subclasses for specific domains (e.g., networkElement for transmission equipment).
WARNING: Although IEC 10165-5-95 allows implementers to extend the generic object classes, you must not modify the mandatory attributes or behaviour of core classes such as
top or system. Extensions must be additive only, using the packages mechanism defined in the standard.Implementation Highlights
Successful deployment of systems based on IEC 10165-5-95 requires careful attention to the conformance guidelines and realisation choices. The following points are essential:
- Use of GDMO templates: All managed object classes, attributes, and notifications must be specified in conformance with the GDMO templates (ISO/IEC 10165-4). This ensures machine-readable and unambiguous definitions that can be used across different management platforms.
- Naming structure: The standard defines a hierarchical naming architecture using name bindings. Each managed object instance must be uniquely identified by a distinguished name (DN) built from the system’s containment tree. Implementations should support both relative and absolute names as per X.501.
- Systems management function support: Object state management, attribute control, and event reporting must align with the systems management functions (SMFs) from ISO/IEC 10164. For example, the
systemobject class interacts directly with the State Management SMF. - Backward compatibility: When upgrading from older versions (pre-2003) of the standard, ensure that deprecated attributes (e.g.,
additionalText) are still supported in read-only mode to avoid breaking existing management applications.
SUCCESS PATTERN: Organisations that adopt IEC 10165-5-95 as their baseline for custom MIBs report up to 40% reduction in integration effort when deploying multivendor equipment. Early standardisation of generic information models is key.
Compliance Notes
Conformance to IEC 10165-5-95 is typically claimed through implementation conformance statements (ICS) that list supported mandatory and optional features. Testing bodies and certification programmes follow the procedures defined in ISO/IEC 9646 (OSI conformance testing). Specific compliance criteria include:
- Mandatory object classes: An implementation must at least instantiate the
topandsystemclasses.alarmRecordis mandatory if the system reports alarms. - Behavioural conformance: The system must exhibit the state diagrams, creation/deletion rules, and notification generation behaviour exactly as specified in the standard’s formal definitions.
- Attribute support: All mandatory attributes (marked as mandatory in the GDMO template) must be readable and, where applicable, writable through CMIP (Common Management Information Protocol) operations.
- Registration: Object classes and attributes must be registered with correct ASN.1 object identifiers (OIDs) as allocated in the standard. Using unallocated or private OIDs for standard constructs is non‑conformant.
COMMON NON‑COMPLIANCE ISSUE: A frequent finding in conformance audits is the omission of the
packages attribute in the top class or the incorrect mapping of alarmType enumeration values. Always cross-check your MIB with the oid.cs registry from the standard.Frequently Asked Questions
Q: Is IEC 10165-5-95 still relevant if our systems use SNMP instead of CMIP?
A: Yes. While the standard was originally designed for OSI/CMIP environments, the generic managed object classes and attribute definitions have influenced various other management protocols, including SMIv2 MIBs for SNMP. Many of the concepts (e.g., system description, alarm record) are directly mapped in standards like ITU-T X.733 and IETF RFC 3877. The generic information model serves as a translation reference between management paradigms.
A: Yes. While the standard was originally designed for OSI/CMIP environments, the generic managed object classes and attribute definitions have influenced various other management protocols, including SMIv2 MIBs for SNMP. Many of the concepts (e.g., system description, alarm record) are directly mapped in standards like ITU-T X.733 and IETF RFC 3877. The generic information model serves as a translation reference between management paradigms.
Q: What is the relationship between IEC 10165-5-95 and the ITU-T X.700 series?
A: IEC 10165-5-95 is identical in technical content to ITU-T X.721 | ISO/IEC 10165-5. The ITU-T Recommendation X.700 series provides the overall OSI management framework, while this standard fills the detail for the generic information model. Both texts can be used interchangeably.
A: IEC 10165-5-95 is identical in technical content to ITU-T X.721 | ISO/IEC 10165-5. The ITU-T Recommendation X.700 series provides the overall OSI management framework, while this standard fills the detail for the generic information model. Both texts can be used interchangeably.
Q: How do I stay up to date with amendments? The standard shows “2003” but what about later changes?
A: The 2003 version incorporated several corrigenda and minor enhancements. As of 2026, the standard has not been revised, but it has been reaffirmed by ISO/IEC JTC 1/SC 6. Always consult the latest published version and any associated corrigenda from the ISO or IEC webstore for the most current requirements.
A: The 2003 version incorporated several corrigenda and minor enhancements. As of 2026, the standard has not been revised, but it has been reaffirmed by ISO/IEC JTC 1/SC 6. Always consult the latest published version and any associated corrigenda from the ISO or IEC webstore for the most current requirements.