SNMP
This chapter explains Simple Network Management Protocol (SNMP) as implemented by the Cisco ONS 15454.
For SNMP setup information, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.
Chapter topics include:
•
SNMP External Interface Requirement
•SNMP Management Information Bases
5.1 SNMP Overview
SNMP is an application-layer communication protocol that allows ONS 15454 network devices to exchange management information among these systems and with other devices outside the network. Through SNMP, network administrators can manage network performance, find and solve network problems, and plan network growth.
The ONS 15454 uses SNMP for asynchronous event notification to a network management system (NMS). ONS SNMP implementation uses standard Internet Engineering Task Force (IETF) management information bases (MIBs) to convey node-level inventory, fault, and performance management information for generic read-only management of DS-1, DS-3, SONET, and Ethernet technologies. SNMP allows a generic SNMP manager such as HP OpenView Network Node Manager (NNM) or Open Systems Interconnection (OSI) NetExpert to be utilized for limited management functions.
The Cisco ONS 15454 supports SNMP Version 1 (SNMPv1) and SNMP Version 2c (SNMPv2c). Both of these versions share many features, but SNMPv2c includes additional protocol operations and 64-bit performance monitoring support. This chapter describes both versions and gives SNMP configuration parameters for the ONS 15454.
Note The CERENT-MSDWDM-MIB.mib and CERENT-FC-MIB.mib in the CiscoV2 directory support 64-bit performance monitoring counters. However, the respective SNMPv1 MIB in the CiscoV1 directory does not contain 64-bit performance monitoring counters, but supports the lower and higher word values of the corresponding 64-bit counter. The other MIB files in the CiscoV1 and CiscoV2 directories are identical in content and differ only in format.
Figure 5-1 illustrates the basic layout idea of an SNMP-managed network.
Figure 5-1 Basic Network Managed by SNMP
5.2 Basic SNMP Components
In general terms, an SNMP-managed network consists of a management system, agents, and managed devices.
A management system such as HP OpenView executes monitoring applications and controls managed devices. Management systems execute most of the management processes and provide the bulk of memory resources used for network management. A network might be managed by one or more management systems. Figure 5-2 illustrates the relationship between the network manager, SNMP agent, and the managed devices.
Figure 5-2 Example of the Primary SNMP Components
An agent (such as SNMP) residing on each managed device translates local management information data, such as performance information or event and error information caught in software traps, into a readable form for the management system. Figure 5-3 illustrates SNMP agent get-requests that transport data to the network management software.
Figure 5-3 Agent Gathering Data from a MIB and Sending Traps to the Manager
The SNMP agent captures data from management information bases, or MIBs, which are device parameter and network data repositories, or from error or change traps.
A managed element—such as a router, access server, switch, bridge, hub, computer host, or network element (such as an ONS 15454)—is accessed through the SNMP agent. Managed devices collect and store management information, making it available via SNMP to other management systems having the same protocol compatibility.
5.3 SNMP External Interface Requirement
Since all SNMP requests come from a third-party application, the only external interface requirement is that a third-part SNMP client application can upload RFC 3273 SNMP MIB variables in the etherStatsHighCapacityTable, etherHistoryHighCapacityTable, or mediaIndependentTable.
5.4 SNMP Version Support
The ONS 15454 supports SNMPv1 and SNMPv2c traps and get requests. The ONS 15454 SNMP MIBs define alarms, traps, and status. Through SNMP, NMS applications can query a management agent for data from functional entities such as Ethernet switches and SONET multiplexers using a supported MIB.
Note ONS 15454 MIB files in the CiscoV1 and CiscoV2 directories are almost identical in content except for the difference in 64-bit performance monitoring features. The CiscoV2 directory contains two 64-bit performance monitoring counters, CERENT-MSDWDM-MIB.mib and CERENT-FC-MIB.mib. The CiscoV1 directory does not contain any 64-bit counters, but it does support the lower and higher word values used in 64-bit counters. The two directories also have somewhat different formats.
5.5 SNMP Version Support
The ONS 15454 supports SNMP v1 and SNMPv2c traps and get requests. The SNMP MIBs in the ONS 15454 define alarms, traps, and status. Through SNMP, NMS applications can query a management agent using a supported MIB. The functional entities include Ethernet switches and SONET multiplexers. Refer to the Cisco ONS 15454 Procedure Guide for procedures to set up or change SNMP settings.
5.6 SNMP Message Types
The ONS 15454 SNMP agent communicates with an SNMP management application using SNMP messages. Table 5-1 describes these messages.
5.7 SNMP Management Information Bases
Table 5-2 lists the IETF-standard MIBs implemented in the ONS 15454SNMP agents.
First compile the MIBs in the in Table 5-2. Compile the Table 5-3 MIBs next.
If you do not compile MIBs in the correct order, one or more might not compile correctly.
|
|
|
|
|---|---|---|
— |
IANAifType-MIB.mib |
Internet Assigned Numbers Authority (IANA) ifType |
1213 |
RFC1213-MIB-rfc1213.mib |
Management Information Base for Network |
1907 |
SNMPV2-MIB-rfc1907.mib |
Management of TCP/IP-based Internets: MIB-II |
1253 |
RFC1253-MIB-rfc1253.mib |
OSPF Version 2 Management Information Base |
1493 |
BRIDGE-MIB-rfc1493.mib |
Definitions of Managed Objects for Bridges |
2819 |
RMON-MIB-rfc2819.mib |
Remote Network Monitoring Management Information Base |
2737 |
ENTITY-MIB-rfc2737.mib |
Entity MIB (Version 2) |
2233 |
IF-MIB-rfc2233.mib |
Interfaces Group MIB using SMIv2 |
2358 |
EtherLike-MIB-rfc2358.mib |
Definitions of Managed Objects for the Ethernet-like Interface Types |
2493 |
PerfHist-TC-MIB-rfc2493.mib |
Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals |
2495 |
DS1-MIB-rfc2495.mib |
Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types |
2496 |
DS3-MIB-rfc2496.mib |
Definitions of Managed Object for the DS3/E3 Interface Type |
2558 |
SONET-MIB-rfc2558.mib |
Definitions of Managed Objects for the SONET/SDH Interface Type |
2674 |
P-BRIDGE-MIB-rfc2674.mib Q-BRIDGE-MIB-rfc2674.mib |
Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions |
3273 |
HC-RMON-MIB |
The MIB module for managing remote monitoring device implementations, augmenting the original RMON MIB as specified in RFC 2819 and RFC 1513 and RMON-2 MIB as specified in RFC 2021 |
1 RFC = Request for Comment |
Each ONS system is shipped with a software CD containing applicable proprietary MIBs. Table 5-3 lists the proprietary MIBs for the ONS 15454.
Note If you cannot compile the proprietary MIBs correctly, log into the Technical Support Website at http://www.cisco.com/techsupport or call Cisco TAC (800) 553-2447.
Note When SNMP indicates that the wavelength is unknown, it means that the corresponding card (MXP_2.5G_10E, TXP_MR_10E, MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G) works with the first tunable wavelength.
5.8 SNMP Trap Content
The ONS 15454 generates all alarms and events, such as raises and clears, as SNMP traps. These contain the following information:
•Object IDs that uniquely identify each event with information about the generating entity (the slot or port; synchronous transport signal [STS] and Virtual Tributary [VT]; bidirectional line switched ring [BLSR], Spanning Tree Protocol [STP], etc.).
•Severity and service effect of the alarm (critical, major, minor, or event; service-affecting or non-service affecting).
•Date and time stamp showing when the alarm occurred.
5.8.1 Generic and IETF Traps
The ONS 15454 supports the generic IETF traps listed in Table 5-4.
5.8.2 Variable Trap Bindings
Each SNMP trap contains variable bindings that are used to create the MIB tables. ONS 15454 traps and variable bindings are listed in Table 5-5. For each group (such as Group A), all traps within the group are associated with all of its variable bindings.
5.9 SNMP Community Names
Community names are used to group SNMP trap destinations. All ONS 15454 trap destinations can be provisioned as part of SNMP communities in Cisco Transport Controller (CTC). When community names are assigned to traps, the ONS 15454 treats the request as valid if the community name matches one that is provisioned in CTC. In this case, all agent-managed MIB variables are accessible to that request. If the community name does not match the provisioned list, SNMP drops the request.
5.10 Proxy Over Firewalls
SNMP and NMS applications have traditionally been unable to cross firewalls used for isolating security risks inside or from outside networks. Release 5.0 (and 4.6.x) versions of CTC enable network operations centers (NOCs) to access performance monitoring data such as remote monitoring (RMON) statistics or autonomous messages across firewalls by using an SMP proxy element installed on a firewall.
The application-level proxy transports SNMP protocol data units (PDU) between the NMS and NEs, allowing requests and responses between the NMS and NEs and forwarding NE autonomous messages to the NMS. The proxy agent requires little provisioning at the NOC and no additional provisioning at the NEs.
The firewall proxy is intended for use in a gateway network element-end network element (GNE-ENE) topology with many NEs through a single NE gateway. Up to 64 SNMP requests (such as get, getnext, or getbulk) are supported at any time behind single or multiple firewalls. The proxy interoperates with common NMS such as HP-OpenView.
For security reasons, the SNMP proxy feature must be enabled at all receiving and transmitting NEs to function. For instructions to do this, refer to the Cisco ONS 15454 Procedure Guide.
5.11 Remote Monitoring
The ONS 15454 incorporates RMON to allow network operators to monitor Ethernet card performance and events. (The ONS 15600 does not support RMON.) The RMON thresholds are user-provisionable in CTC. Refer to the Cisco ONS 15454 Procedure Guide for instructions. Note that otherwise, RMON operation is invisible to the typical CTC user.
ONS 15454 system RMON implementation is based on the IETF-standard MIB RFC 2819 and includes the following five groups from the standard MIB: Ethernet Statistics, History Control, Ethernet History, Alarm, and Event.
5.11.1 HC-RMON-MIB Support
For the ONS 15454, the implementation of the high-capacity remote monitoring information base (HC-RMON-MIB, or RFC 3273) enables 64-bit support of existing RMON tables. This support is provided with the etherStatsHighCapacityTable and the etherHistoryHighCapacityTable. An additional table, the mediaIndependentTable, and an additional object, hcRMONCapabilities, are also added for this support. All of these elements are accessible by any third-party SNMP client having RFC 3273 support.
5.11.2 Ethernet Statistics RMON Group
The Ethernet Statistics group contains the basic statistics monitored for each subnetwork in a single table called the etherStatsTable.
5.11.2.1 Row Creation in etherStatsTable
The SetRequest PDU for creating a row in this table should contain all the values needed to activate a row in a single set operation, and an assigned status variable to createRequest. The SetRequest PDU object ID (OID) entries must all carry an instance value, or type OID, of 0.
In order to create a row, the SetRequest PDU should contain the following:
•The etherStatsDataSource and its desired value
•The etherStatsOwner and its desired value (size of this value is limited to 32 characters)
•The etherStatsStatus with a value of createRequest (2)
The etherStatsTable creates a row if the SetRequest PDU is valid according to the above rules. When the row is created, the SNMP agent decides the value of etherStatsIndex. This value is not sequentially allotted or contiguously numbered. It changes when an Ethernet interface is added or deleted. The newly created row will have etherStatsStatus value of valid (1).
If the etherStatsTable row already exists, or if the SetRequest PDU values are insufficient or do not make sense, the SNMP agent returns an error code.
Note EtherStatsTable entries are not preserved if the SNMP agent is restarted.
5.11.2.2 Get Requests and GetNext Requests
Get requests and getNext requests for the etherStatsMulticastPkts and etherStatsBroadcastPkts columns return a value of zero because the variables are not supported by ONS 15454 Ethernet cards.
5.11.2.3 Row Deletion in etherStatsTable
To delete a row in the etherStatsTable, the SetRequest PDU should contain an etherStatsStatus "invalid" value (4). The OID marks the row for deletion. If required, a deleted row can be recreated.
5.11.2.4 64-Bit etherStatsHighCapacity Table
The Ethernet statistics group contains 64-bit statistics in the etherStatsHighCapacityTable, which provides 64-bit RMON support for the HC-RMON-MIB. The etherStatsHighCapacityTable is an extension of the etherStatsTable that adds 16 new columns for performance monitoring data in 64-bit format. There is a one-to-one relationship between the etherStatsTable and etherStatsHighCapacityTable when rows are created or deleted in either table.
5.11.3 History Control RMON Group
The History Control group defines sampling functions for one or more monitor interfaces in the historyControlTable. The values in this table, as specified in RFC 2819, are derived from the historyControlTable and etherHistoryTable.
5.11.3.1 History Control Table
The RMON is sampled at one of four possible intervals. Each interval, or period, contains specific history values (also called buckets). Table 5-6 lists the four sampling periods and corresponding buckets.
The historyControlTable maximum row size is determined by multiplying the number of ports on a card by the number of sampling periods. For example, an ONS 15454 E100 card contains 24 ports, which multiplied by periods allows 96 rows in the table. An E1000 card contains 14 ports, which multiplied by four periods allows 56 table rows.
5.11.3.2 Row Creation in historyControlTable
The SetRequest PDU must be able to activate a historyControlTable row in one single-set operation. In order to do this, the PDU must contain all needed values and have a status variable value of 2 (createRequest). All OIDs in the SetRequest PDU should be type OID.0 type for entry creation.
To create a creation SetRequest PDU for the historyControlTable, the following values are required:
•The historyControlDataSource and its desired value
•The historyControlBucketsRequested and it desired value
•The historyControlInterval and its desired value
•The historyControlOwner and its desired value
•The historyControlStatus with a value of createRequest (2)
The historyControlBucketsRequested OID value is ignored because the number of buckets allowed for each sampling period, based upon the historyControlInterval value, is already fixed as listed in Table 5-6.
The historyControlInterval value cannot be changed from the four allowed choices. If you use another value, the SNMP agent selects the closest smaller time period from the set buckets. For example, if the set request specifies a 25-minute interval, this falls between the 15-minute (32 bucket) variable and the 60-minute (24 bucket) variable. The SNMP agent automatically selects the lower, closer value, which is 15 minutes, so it allows 32 buckets.
If the SetRequest PDU is valid, a historyControlTable row is created. If the row already exists, or if the SetRequest PDU values do not make sense or are insufficient, the SNMP agent does not create the row and returns an error code.
5.11.3.3 Get Requests and GetNext Requests
These PDUs are not restricted.
5.11.3.4 Row Deletion in historyControl Table
To delete a row from the table, the SetRequest PDU should contain a historyControlStatus value of 4 (invalid). A deleted row can be recreated.
5.11.4 Ethernet History RMON Group
The ONS 15454 implements the etherHistoryTable as defined in RFC 2819. The group is created within the bounds of the historyControlTable and does not deviate from the RFC in its design.
5.11.4.1 64-Bit etherHistoryHighCapacityTable
64-bit Ethernet history for the HC-RMON-MIB is implemented in the etherHistoryHighCapacityTable, which is an extension of the etherHistoryTable. The etherHistoryHighCapacityTable adds four columns for 64-bit performance monitoring data. These two tables have a one-to-one relationship. Adding or deleting a row in one table will effect the same change in the other.
5.11.5 Alarm RMON Group
The Alarm group consists of the alarmTable, which periodically compares sampled values with configured thresholds and raises an event if a threshold is crossed. This group requires the implementation of the event group, which follows this section.
5.11.5.1 Alarm Table
The NMS uses the alarmTable to determine and provision network performance alarmable thresholds.
5.11.5.2 Row Creation in alarmTable
To create a row in the alarmTable, the SetRequest PDU must be able to create the row in one single-set operation. All OIDs in the SetRequest PDU should be type OID.0 type for entry creation. The table has a maximum number of 256 rows.
To create a creation SetRequest PDU for the alarmTable, the following values are required:
•The alarmInterval and its desired value
•The alarmVariable and its desired value
•The alarmSampleType and its desired value
•The alarmStartupAlarm and its desired value
•The alarmOwner and its desired value
•The alarmStatus with a value of createRequest (2)
If the SetRequest PDU is valid, a historyControlTable row is created. If the row already exists, or if the SetRequest PDU values do not make sense or are insufficient, the SNMP agent does not create the row and returns an error code.
In addition to the required values, the following restrictions must be met in the SetRequest PDU:
•The alarmOwner is a string of length 32 characters.
•The alarmRisingEventIndex always takes value 1.
•The alarmFallingEventIndex always takes value 2.
•The alarmStatus has only two values supported in SETs: createRequest (2) and invalid (4).
•The AlarmVariable is of the type OID.ifIndex, where ifIndex gives the interface this alarm is created on and OID is one of the OIDs supported in Table 5-7.
5.11.5.3 Get Requests and GetNext Requests
These PDUs are not restricted.
5.11.5.4 Row Deletion in alarmTable
To delete a row from the table, the SetRequest PDU should contain an alarmStatus value of 4 (invalid). A deleted row can be recreated. Entries in this table are preserved if the SNMP agent is restarted.
5.11.6 Event RMON Group
The Event group controls event generation and notification. It consists of two tables: the eventTable, which is a read-only list of events to be generated, and the logTable, which is a writable set of data describing a logged event. The ONS 15454 implements the logTable as specified in RFC 2819.
5.11.6.1 Event Table
The eventTable is read-only and unprovisionable. The table contains one row for rising alarms and another for falling ones. This table has the following restrictions:
•The eventType is always log-and-trap (4).
•The eventCommunity value is always a zero-length string, indicating that this event causes the trap to be despatched to all provisioned destinations.
•The eventOwner column value is always "monitor."
•The eventStatus column value is always valid(1).
5.11.6.2 Log Table
The logTable is implemented exactly as specified in RFC 2819. The logTable is based upon data that is locally cached in a controller card. If there is a controller card protection switch, the existing logTable is cleared and a new one is started on the newly active controller card. The table contains as many rows as provided by the alarm controller.
Feedback