Session Mib Support On Subscriber Sessions; Snmp Notifications - Cisco NCS 5000 Series Manual
System management configuration guide for cisco ncs 5000 series
routers
Hide thumbs
Also See for NCS 5000 Series:
- Hardware installation manual (72 pages) ,
- Manual (186 pages)
Table of Contents
Advertisement
Session MIB support on subscriber sessions
The IP Precedence value is the first three bits in the type of service (ToS) byte of an IP header. The IP DSCP
code point value is the first six bits of the differentiate services (DiffServ Field) byte. You can configure up
to eight different IP Precedence markings or 64 different IP DSCP markings.
Session MIB support on subscriber sessions
SNMP monitoring requires information about subscribers of all types. The
CISCO-SUBSCRIBER-SESSION-MIB is defined to model per-subscriber data as well as aggregate subscriber
(PPPoE) data. It is required to support notifications (traps) for aggregate session counts crossing configured
thresholds. Generic MIB Data Collector Manager (DCM) support for CISCO-SUBSCRIBER-SESSION-MIB,
helps faster data collection and also better handling of parallel data.
SNMP Notifications
A key feature of SNMP is the ability to generate notifications from an SNMP agent. These notifications do
not require that requests be sent from the SNMP manager. On Cisco IOS XR software, unsolicited
(asynchronous) notifications can be generated only as traps. Traps are messages alerting the SNMP manager
to a condition on the network. Notifications can indicate improper user authentication, restarts, the closing of
a connection, loss of connection to a neighbor router, or other significant events.
Note
Inform requests (inform operations) are supported in Cisco IOS XR software.
Traps are less reliable than informs because the receiver does not send any acknowledgment when it receives
a trap. The sender cannot determine if the trap was received. An SNMP manager that receives an inform
request acknowledges the message with an SNMP response protocol data unit (PDU). If the manager does
not receive an inform request, it does not send a response. If the sender never receives a response, the inform
request can be sent again. Thus, informs are more likely to reach their intended destination.
However, traps are often preferred because informs consume more resources in the router and in the network.
Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in memory until a
response is received or the request times out. Also, traps are sent only once, and an inform may be retried
several times. The retries increase traffic and contribute to a higher overhead on the network. Thus, traps and
inform requests provide a trade-off between reliability and resources.
In this illustration, the agent router sends a trap to the SNMP manager. Although the manager receives the
trap, it does not send any acknowledgment to the agent. The agent has no way of knowing that the trap reached
its destination.
Figure 2: Trap Received by the SNMP Manager
System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x
26
Implementing SNMP
Hide quick links:
Advertisement
Table of Contents
