SMI Expanded

SMI Expanded
Name	SMI Expanded

SMI Expanded

SMI Expanded is a schema and operational profile intended to extend Simple Network Management Protocol data modeling practices for broader interoperability and richer metadata exchange. It provides a set of syntactic and semantic conventions that complement established specifications to enable more expressive object identification, annotation, and instrumentation across heterogeneous platforms.

Definition and Purpose

SMI Expanded defines an augmented object identification and metadata framework that builds on existing naming and type conventions used by standards bodies such as Internet Engineering Task Force, International Telecommunication Union, Institute of Electrical and Electronics Engineers, International Organization for Standardization, and European Telecommunications Standards Institute. The purpose is to permit equipment vendors like Cisco Systems, Juniper Networks, Huawei, Arista Networks, and Hewlett-Packard to represent complex operational states compatible with management systems from vendors such as IBM, Microsoft, Oracle Corporation, Dell Technologies, and NetApp. It aims to align with management architectures exemplified by Network Management System, Simple Network Management Protocol, Common Information Model, Management Information Base, and Lightweight Directory Access Protocol to support richer telemetry and policy orchestration across platforms including Amazon Web Services, Microsoft Azure, Google Cloud Platform, and on-premises data centers managed by VMware.

History and Development

SMI Expanded emerged as an editorial and technical response to limitations noted in legacy documents produced by bodies like Internet Engineering Task Force working groups and implementers from Sun Microsystems, Bell Labs, Nokia, Ericsson, and Alcatel-Lucent. Early discussion threads referenced operational cases involving vendors such as Intel, Broadcom, Marvell Technology Group, and Qualcomm and management consoles like HP OpenView and SolarWinds. Influential events and forums that shaped its evolution include meetings at IETF gatherings, workshops at Interop, panels at RSA Conference, and contributions from research labs at MIT, Stanford University, University of California, Berkeley, and Carnegie Mellon University. The profile incorporated lessons learned from deployments in environments overseen by institutions such as NASA, European Space Agency, US Department of Defense, and enterprises participating in interoperability trials orchestrated by Open Network Foundation and similar consortia.

Technical Specifications

The technical specification of SMI Expanded details object identifier allocation, type inheritance, indexing rules, and metadata annotations intended to be compatible with existing MIB module composition and encoding formats standardized by IETF documents and by serialization approaches from World Wide Web Consortium. It defines mappings for scalar and tabular constructs to interoperate with management agents on devices by Cisco Systems, Juniper Networks, Arista Networks, and Hewlett-Packard Enterprise. The specification addresses issues of extensibility, name space governance, registration authorities like Internet Assigned Numbers Authority, and conformance statements aligned with validation practices used by OASIS and IEEE Standards Association. Encoding considerations reference established formats used by SNMP, as well as integration guidance for telemetry pipelines common to Prometheus, Grafana, and Elasticsearch.

Applications and Deployment

SMI Expanded is applied in multi-vendor operational environments such as service provider networks run by AT&T, Verizon, Deutsche Telekom, NTT Communications, and Vodafone, in cloud deployments by Amazon Web Services and Microsoft Azure, and in enterprise campuses managed by Google, Facebook, Apple Inc., and Twitter. Use cases include fault management workflows in systems integrated with ServiceNow, performance monitoring feeding platforms like Splunk and Dynatrace, and inventory reconciliation in asset systems from SAP and Oracle Corporation. Deployment patterns often involve cooperation between network equipment from Cisco Systems and Juniper Networks, server instrumentation from Dell Technologies and Hewlett-Packard Enterprise, and orchestration tools from Red Hat and Ansible.

Comparison with Related Standards

Compared with the original schema published in documents by IETF working groups, SMI Expanded introduces richer metadata and more flexible indexing similar to efforts seen in Common Information Model work from Distributed Management Task Force and extends ideas found in YANG models standardized by IETF. It contrasts with directory-oriented schemas like those used in Lightweight Directory Access Protocol deployments by emphasizing object identification for instrumentation rather than human-centric directory entries used by Microsoft Active Directory or OpenLDAP. In telemetry ecosystems it complements time-series approaches from Prometheus and schema registries associated with Apache Kafka rather than replacing them.

Criticisms and Limitations

Critics from vendor communities including representatives of Cisco Systems, Juniper Networks, Huawei, and open-source projects such as those hosted by The Linux Foundation have cited complexity of adoption, overlap with YANG and Common Information Model initiatives, and challenges in retrofitting legacy agents like those used in HP OpenView and SolarWinds installations. Operational constraints observed in large-scale carriers like AT&T and Verizon include the effort required for namespace governance enforced by authorities such as IANA and the coordination needed with certification and compliance programs run by organizations like PCI Security Standards Council and National Institute of Standards and Technology. Limitations also arise in contexts requiring strict lightweight encodings favored by embedded vendors such as Broadcom and Qualcomm.

Category:Network management standards