MY-SMI: View SNMP OID List / Download MIB

VENDOR: D-LINK


 Home MIB: MY-SMI
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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.