All MIBs › MY-SMI
Organization: D-Link Crop.
Last Updated: 2002-03-19
Category: Products/Registration
Description:
Defines D-Link Corp. enterprise SMI structure and OID registration hierarchy.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| enterprises |
What Is MY-SMI?
MY-SMI is the Structure of Management Information (SMI) module for D-Link Corporation, establishing the enterprise's private OID branch under the IANA-assigned enterprise numbers arc. Rather than exposing any runtime data itself, it defines the top-level object identifier registration points under which all other D-Link enterprise MIB modules attach their tables and scalars. As a pure SMI/root module it has no hardware or software status objects of its own to poll, so it plays no direct role in monitoring uptime, temperature, CPU load, or similar metrics. It has no dependency beyond the standard SNMPv2-SMI conventions used to define the OID tree. It is typically loaded as a prerequisite MIB alongside the actual D-Link product MIBs (switches, routers, wireless APs), and when an SNMP tool fails to resolve a D-Link object, the first thing to check is whether the MY-SMI MIB file itself was compiled first so that the full OID namespace resolves correctly.
IPNetwork Monitor allows you to monitor SNMP objects defined in MY-SMI. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- D-Link Corporation networking equipment (any generation, enterprise OID root)
Monitoring Examples
Because MY-SMI contains no tables, counters, or notifications, there is no realistic monitoring scenario to describe for it directly. Its sole practical use is as a compile-time dependency: an SNMP manager or MIB compiler loads MY-SMI first so that OIDs defined in other D-Link MIBs (e.g. under the dlink enterprise subtree) resolve correctly. No sample objects were present in this module, consistent with its role as a pure registration/root MIB.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| my | 1.3.6.1.4.1.171 | |||
| products | 1.3.6.1.4.1.171.10 | |||
| switchMib | 1.3.6.1.4.1.171.10.97 | The Structure of Management Information for the My enterprise. | ||
| mySwitchProducts | 1.3.6.1.4.1.171.10.97.1 | mySwitchProducts is the root OBJECT IDENTIFIER from which sysObjectID values are assigned for switch. Actual values are defined in MY-PRODUCTS-MIB. | ||
| myMgmt | 1.3.6.1.4.1.171.10.97.2 | myMgmt is the main subtree for those functional mib. | ||
| myAgentCapability | 1.3.6.1.4.1.171.10.97.3 | myAgentCapability provides a root object identifier from which AGENT-CAPABILITIES values may be assigned. | ||
| myModules | 1.3.6.1.4.1.171.10.97.4 | myModules provides a root object identifier from which MODULE-IDENTITY values may be assigned. | ||
| myExperiment | 1.3.6.1.4.1.171.10.97.5 | myExperiment provides a root object identifier from which experimental mibs may be temporarily based. mibs are typicially based here if they fall in one of two categories 1) are IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) are my work-in-process which has not been assigned a permanent object identifier by the my assigned number authority, typicially because the mib is not ready for deployment. NOTE WELL: support for mibs in the myExperiment subtree will be deleted when a permanent object identifier assignment is made. |
RFC description
Enterprise structure of management information (SMI) for D-Link switch products providing root organization for functional MIBs.
Start monitoring D-Link Corporation networking equipment (any generation, enterprise OID root) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.