HP Insight Management WBEM Providers 2.80 SNMP Data Migration Guide

| | | | | | | |-cpqSsStorageSys(8) | | | | | | | |-cpqSm2(9) | | | | |
| | |-cpqThresholdMgmt(10) | | | | | | | |-cpqHostOS(11) | | | | | | |
|-cpqUps(12) | | | | | | | |-cpqRecovery(13) | | | | | | | |-cpqIde(14)
| | | | | | | |-cpqCluster(15) | | | | | | | |-cpqFibreArray(16) | | |
| | | | |-cpqExternalMgmt(17) | | | | | | | |-cpqNic(18) | | | | | | |
|-cpqWinOsMgmt(19) | | | | | | | |-cpqApplianceMgmt(21) | | | | | | |
|-cpqRackInfo(22)
Every piece of information is referred to by its full name so each piece of information can be
unambiguously specified. Full names are commonly given in dotted decimal notation. Dotted
decimal notation specifies all the branch numbers, separated by periods, needed to reach the
particular item. For example the number 1.3.6.1.4.1.232.1 stands for the Standard Equipment
MIB. All information in the Standard Equipment MIB will start with this prefix and then continue on
to distinguish different pieces of information within the MIB.
The name of each branch is specified in MIB documents. The number series, in parentheses after
the name, is what is sent over the network in an SNMP packet when referring to a specific item in
the tree. Sending a series of numbers specifying a tree location in a packet rather than a text
description of the item as a name lessens network traffic. However, this protocol requires that both
ends involved in the protocol understand the meanings of these code numbers and the structure of
the information. This scheme requires a precise grammar to document the MIB structure to avoid
confusion between the agent and the management station. The grammar typically used is called
the Concise MIB format and is defined in RFC 1212.
9