Skip to end of metadata
Go to start of metadata

In this section:


This section details SNMP functionality, and how to configure the Sonus SBC Portfolio for SNMP.

The SNMP system consists of three parts: SNMP manager, SNMP agent, and MIB. The SNMP manager running on the Network Management System (NMS) collects information about network connectivity, activity, and event by polling managed devices. The SNMP agent exchanges network management information with the SNMP manager. The agent also controls access to the agent’s MIB, the collection of objects that can be viewed by the SNMP manager.

SNMP uses five basic messages for communication between the manager and agent, one of which is the GET request that is used to query for information on or about a network entity.

As shown in the figure below, the SNMP agent (SBC 51x0 shown) gathers data from the MIB, which is the repository for information about device parameters and network data. The agent also can send traps or notifications of events that happen in the agent to the manager.

Figure : SNMP Manager and Agent

The SNMP manager sends SNMP GET and SNMP GET-NEXT requests to SNMP agent. The SNMP agent sends SNMP GET responses back to the SNMP manager. The SNMP manager receives SNMP trap messages from agent. SNMP traps are messages that notify a manager that an event has occurred on the SBC node. Any event that results in an SNMP trap message is also logged in an event log.

snmpwalk is an SNMP application that uses SNMP GETNEXT requests to query a network entity for a tree of information. An object identifier (OID) may be given on the command line. This OID specifies which portion of the object identifier space will be searched using GETNEXT requests. snmpwalk man pages are available on the Internet.

Deploying SNMPv3

The SBC can be configured to support either SNMPv1 and v2, or SNMPv3 only using the OAM command from EMA or CLI.

To correct security deficiencies of SNMPv1/v2, use SNMPv3 to take advantage of three important services: Authentication, Privacy, and Access Control. Secret-Key authentication mechanism in SNMPv3 ensures that a received message is transmitted to the principal whose identifier appears as the source in the message header. In addition, this mechanism ensures that the message was not altered in transit and that it was not artificially delayed or replayed.

When a Sonus SBC Portfolio system is deployed in the network along with the EMS, SNMP protocol is used for the following functions:

  1. SBC sends traps to the SNMP manager (EMS)

  2. EMS sends SNMP requests to collect real time and periodic statistics


See also: