TB640 User's guide CONFIDENTIAL 9000-00002-1Y

14 SNMP
14.1 Overview
The SNMP (Simple Network Management Protocol) was created to manage devices attached to the
network. SNMP is based on the manager /agent model consisting of a manager, an agent, a
database of management information, managed objects and the network protocol.

The manager and agent use Management Information Base (MIB) and a relatively small set of
commands to exchange information. The MIB is organized in a tree structure. Each node in tree is
assigned a unique dot separated sequence of integers called OID(Object Identifier).

SNMP uses five basic messages (GET, GET-NEXT,GET-RESPONSE,SET and TRAP) to

communicate between the Management Station and the agent. The GET and GET-NEXT messages
are used by the Management station to request information for a specific variable. The GET-
RESPONSE message is sent by the agent in response to GET/GET-NEXT request. The GET-
RESPONSE may contain the values of the all variables in the GET/GET-NEXT requests or an
error if the agent fails to process at least one variable in the request message.
The SET message, in the other hand, is used by Management station to request a change be made to
the value of a specific variable. The TRAP message allows the agent to spontaneously inform the
manager of an important event.

14.2 SNMP Limitation

In this section we present the limitation of our current implementation of the SNMP protocol. The
only version supported by our implementation is the SNMP version 1. The communities public,
telcobridges can be used to query (GET, GET-NEXT) variables and the community private is used
to request change (SET) of a specific variable

14.3 SNMP Messages

The messages GET and GET-NEXT are fully supported. The message SET is only used to change
the trunks’ loopback status. In other words, even if some variables are declared with read-write
access, all requests to change the values of these variables cause an error to be returned to the
Management station. The only exception is the trunk’s loopback variable.
Finally, the message TRAP is not supported and it will not be generated by the agent.

Page 176 Copyright © 2002-2006 by TelcoBridges inc.

9000-00002-1Y CONFIDENTIAL TB640 User's guide

14.4 Supported MIBs

14.4.1 RFC 1213 MIB II

Here is a list of the limitation or the unsupported feature in this MIB:

x The ipRouteTable is not implemented
x The EGP group is not implemented
x The atTable is not implemented.
x TCP,UDP and ICMP statistics are the sum of statistics from the two CPUs
x Only the udpTable and TcpConnTable of CPU 0 will be shown

14.4.2 RFC 2959 Real-Time Transport Protocol Management Information

Base

The following tables are supported:

x rtpSessionTable
x rtpSenderTable
x rtpRcvrTable
The agents returns the value 9999 for the unsupported values

14.4.3 RFC 2495 DS1, E1, DS2 and E2 Interfaces

The trunks will be shown in the interface table independently of their configurations/allocations. In
addition, the agent returns the 9999 for unsupported fields

The following tables are supported:

x Dsx1ConfigTable
x Dsx1CurrentTable
x Dsx1IntervalTable
x Dsx1TotalTable

It should be noted here that the trunk’s loopback setting is supported in dsx1ConfigTable

14.4.4 RFC 2496 - Definitions of Managed Object for the DS3/E3 Interface
Type
The DS3 line interfaces will be shown in the interface table independently of their
configurations/allocations. In addition, the agent returns the 9999 for unsupported fields

The following tables are supported:

x Dsx3ConfigTable
x Dsx3CurrentTable
x Dsx3IntervalTable
x Dsx3TotalTable

Copyright © 2002-2006 by TelcoBridges inc. Page 177

TB640 User's guide CONFIDENTIAL 9000-00002-1Y

14.4.5 Telcobridges Private MIB (TB-MIB)

The private MIB provides information on the software and hardware components installed on the
adapter.
The TB-MIB file is provided with the package under the directory tb/tb640/doc/mibs.
Please refer to TB-MIB file for more information about a specific object.

The following paragraph provides roadmap of TB-MIB files.

1. Direcotry group: contains the module table which have an entry for each supported
module
2. Common Group : contains the following objects
a. tbHwCommon:
i. Serial Number, Slot ID, Shelf ID and adapter’s part number
ii. tbHwVersinTable :
iii. tbHwTempTable(Device Temperature)
b. tbSwCommon
i. tbSwFeatureTable
ii. tbVersionTable
3. Specific Group : contains product’s specific objects
4. Experimental Group : used for experimental purpose

At the moment of writing this document, the Specific and Experimental groups are empty

14.5 Browsing MIBs

The tools used during testing are the command lines tools provided by net-snmp. These tools can
downloaded freely from http://net-snmp.sourceforge.net. In order to see the objects’ names when
using these tools, the environnement variable MIBDIRS should be set to the location where the
MIB files were installed.

All the tools accept the following options:

-v : version. In our case only version one is supported
-m : modules list. Use ALL to load all modules
-c : community’s name. Use public for read and private for write

Please refer to the tools for more information about theirs usage.

14.5.1 Get a single object

The command snmpget can be used to get one or more objects in the same request. In this example
we send a request command to read system’s description and system up time:

>snmpget –v 1 –c public –m ALL 192.168.100.100 sysDescr.0 sysUpTime.0

Your can replace the object’s name by theirs OIDs

Page 178 Copyright © 2002-2006 by TelcoBridges inc.

9000-00002-1Y CONFIDENTIAL TB640 User's guide

14.5.2 Get the next object

The command snmpgetnext can be used to get the next lexicographically object in the tree
following the specified object. In this example we send a request command to read the next object
after the system’s description.

>snmpgetnext –v 1 –c public –m ALL 192.168.100.100 sysObjectID.0

SNMPv2-MIB::sysObjectID.0 = OID: TB-MIB::Specific.1.252

14.5.3 Get a specific table

The command snmptable can be used to get a table and display it in a tabular form. The following
example reads the features tables from the Telcobridges private MIB.

>snmptable –v 1 –c public –m ALL 192.168.100.100 tbFeaturesTable

14.5.4 Get a tree branch

In the following example, the command snmpwalk is used to display a branch. When using this
command, the tables are displayed by columns rather than by lines.

>snmptable –v 1 –c public –m ALL 192.168.100.100 tbFeaturesTable

Copyright © 2002-2006 by TelcoBridges inc. Page 179