Patton electronics 3120, Справочное руководство администратора

Страница: 319 / 331

Using SNMP with the Access Server 319
Model 3120 RAS Administrators’ Reference Guide C • Technical Reference
Finding the section of the MIB tree in which the SNMP parameter resides
Refer to figure 129 on page 320 and look at the Model 2960 MIB tree. There two sections in the tree:
• The Internet standards section, identified by the shaded box surrounding it. In this section are MIBs (Man-
agement Information Base) that deal with Internet standards such as SNMP, IP, ICMP, Frame-Relay, and
Ethernet. It contains parameters that could potentially be on any machine that implements these features.
• The private Patton MIB—In this section are MIB variables that are specific to Patton products. This section
is further divided into:
– Those variables valid for a group of products
– Those variables valid for a Model 31XX Series: m3120 node
Active Calls is a product specific parameter.
Now, the OID can start to be built up. Choose the nodes that will take you to the private Patton MIB (these
nodes are shaded red in figure 129 on page 320). All private Patton MIB variables will begin with this series
(1.3.6.1.4.1.1768).
Finding the branch where the SNMP parameter resides
On the SNMP web page are links to the Patton MIB definitions. Most of the MIBs are common to all Patton
access server products, therefore the parameter is likely to be found in the Enterprise MIB. Click on Enterprise
MIB and open the file. Search for the SNMP name diActive that maps to Active Calls. The following entry is
listed:
diActive OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION "The total number of active calls."
::= { calldialin 25 }
The entry includes the name, the type, the access available, and the description of the parameter. The last line
gives another part of the OID. There the diActive parameter is identified as parameter 25 under the calldialin
branch. Looking at the MIB tree, the calldialin node is labeled as branch 5 (shaded green in figure 129 on
page 320).
Note
For the purpose of this example, figure 129 on page 320 shows
parameter identifier 25 (diActive). Normally, a MIB tree shows only
branches and nodes, it will not show the myriad of parameters that
come under each node. Therefore, while you can use the MIB dia-
grams in Appendix B, “MIB trees” to map out the OID through the
Enterprise node level, you will need to refer to section “Using SNMP
with the Access Server” on page 318 for help in determining where
the parameter you are interested in resides.
The calldialin node is immediately under the Patton branch, therefore the OID is 1.3.6.1.4.1.1768.5.25, as
shown in figure 129 on page 320. This new OID is used by the network management software to query the
RAS for the total number of active calls.