- About this Manual
- Chapter 1, Shelf and Backplane Hardware
- Chapter 2, Card Reference
- Chapter 3, Card Protection
- Chapter 4, Cisco Transport Controller Operation
- Chapter 5, Security
- Chapter 6, Timing
- Chapter 7, Circuits and Tunnels
- Chapter 8, SDH Topologies and Upgrades
- Chapter 9, Management Network Connectivity
- Chapter 10, Ethernet Operation
- Chapter 11, Alarm Monitoring and Management
- Chapter 12, Performance Monitoring
- Chapter 13, SNMP
- Appendix A, Hardware Specifications
- Appendix B, Administrative and Service States
- Appendix C, Network Element Defaults
SNMP
This chapter explains Simple Network Management Protocol (SNMP) as implemented by the Cisco ONS 15600 SDH.
For SNMP setup information, refer to the Cisco ONS 15600 SDH Procedure Guide.
Chapter topics include:
•
SNMP External Interface Requirement
•SNMP Management Information Bases
13.1 SNMP Overview
SNMP is an application-layer communication protocol that allows ONS 15600 SDH 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. Up to 10 SNMP trap destinations and five concurrent Cisco Transport Controller (CTC) user sessions are allowed per node.
The ONS 15600 SDH 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 SDH read-only management. 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 15600 SDH supports SNMP Version 1 (SNMPv1) and SNMP Version 2c (SNMPv2c). 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 15600 SDH.
Note It is recommended that the SNMP Manager timeout value be set to 60 seconds. Under certain conditions, if this value is lower than the recommended time, the TCC card can reset. However, the response time depends on various parameters such as object being queried, complexity, and number of hops in the node, etc.
Note The CERENT-MSDWDM-MIB.mib, CERENT-FC-MIB.mib, and CERENT-GENERIC-PM-MIB.mib in the CiscoV2 directory support 64-bit performance monitoring counters. The 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.
Note When you switch multiplex-section shared protection ring (MS-SPRing) traffic from working to protect, the intermediate path performance monitoring (IPPM) TCAs and SDH near-end path PM values are available on the protect path. The protect TCA and PM values will not be available after the switch is cleared. Note that the protection channel access (PCA) TCAs and PM values are collected when the protect is not active.
Figure 13-1 illustrates the basic layout idea of an SNMP-managed network.
Figure 13-1 Basic Network Managed by SNMP
13.2 Basic SNMP Components
In general terms, an SNMP-managed network consists of a management system, agents, and managed devices.
A network might be managed by one or several management systems. 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. Figure 13-2 illustrates the relationship between the network manager, SNMP agent, and the managed devices.
Figure 13-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 13-3 illustrates SNMP agent get-requests that transport data to the network management software.
Figure 13-3 Agent Gathering Data from a MIB and Sending Traps to the Manager
The SNMP agent captures data from 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 15600 SDH)—is accessed through the SNMP agent. Managed devices collect and store management information, making it available through SNMP to other management systems having the same protocol compatibility.
13.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.
13.4 SNMP Version Support
The ONS 15600 SDH supports SNMPv1 and SNMPv2c traps and get requests. The ONS 15600 SDH 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 SDH multiplexers using a supported MIB.
Note ONS 15600 SDH 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 three MIBs with 64-bit performance monitoring counters: CERENT-MSDWDM-MIB.mib, CERENT-FC-MIB.mib, and CERENT-GENERIC-PM-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.
13.5 SNMP Message Types
The ONS 15600 SDH SNMP agent communicates with an SNMP management application using SNMP messages. Table 13-1 describes these messages.
13.6 SNMP Management Information Bases
A managed object, sometimes called a MIB object, is one of many specific characteristics of a managed device. The MIB consists of hierarchically organized object instances (variables) that are accessed by network-management protocols such as SNMP. Section 13.6.1 lists the IETF standard MIBs implemented in the ONS 15600 SDH SNMP agent. Section 13.6.2 lists the proprietary MIBs implemented in the ONS 15600 SDH.
13.6.1 IETF-Standard MIBs for ONS 15600 SDH
Table 13-2 lists the IETF-standard MIBs implemented in the ONS 15600 SDH SNMP agents.
First compile the MIBs in Table 13-2. Next, compile the MIBs in the order given in Table 13-3.
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 Internet: 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 SNMPv2 |
2358 |
EtherLike-MIB-rfc2358.mib |
Definitions of Managed Objects for the Ethernet-like Interface Types |
2493 |
PerfHist-TC-MIB-rfc2493.mib |
(Not applicable to the ONS 15600 SDH) Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals |
2495 |
DS1-MIB-rfc2495.mib |
Not applicable to the ONS 15600 SDH |
2496 |
DS3-MIB-rfc2496.mib |
Not applicable to the ONS 15600 SDH |
2558 |
SDH-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 RMON 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 |
13.6.2 Proprietary ONS 15600 SDH MIBs
Each ONS 15600 SDH is shipped with a software CD containing applicable proprietary MIBs. The MIBs in Table 13-3 lists the proprietary MIBs for the ONS 15600 SDH.
|
|
|
|---|---|
1 |
CERENT-GLOBAL-REGISTRY.mib |
2 |
CERENT-TC.mib |
3 |
CERENT-600.mib |
4 |
CERENT-GENERIC.mib |
Note If you cannot compile the proprietary MIBs correctly, log into the Cisco Technical Assistance Center (TAC) at http://www.cisco.com/techsupport or call Cisco TAC (800) 553-2447.
13.7 SNMP Trap Content
The ONS 15600 SDH uses SNMP traps to generate all alarms and events, such as raises and clears. The traps contain the following information:
•Object IDs that uniquely identify each event with information about the generating entity (the slot or port; virtual container [VC], or MS-SPRing).
•Severity and service effect of the alarm (Critical [CR], Major [MJ], Minor [MN], or event; Service-Affecting [SA] or Non Service Affecting [NSA]).
•Date and time stamp showing when the alarm occurred.
13.7.1 Generic and IETF Traps
Table 13-4 contains information about the generic threshold and performance monitoring MIBs that can be used to monitor any network element (NE) contained in the network. The ONS 15600 SDH supports the generic IETF traps listed in Table 13-4.
13.7.2 Variable Trap Bindings
Each SNMP trap contains variable bindings that are used to create the MIB tables. Variable bindings for the ONS 15600 SDH are listed in Table 13-5. For each group (such as Group A), all traps within the group are associated with all of the group's variable bindings.
13.8 Proxy Over Firewalls
SNMP and NMS applications have traditionally been unable to cross firewalls used for isolating security risks inside or outside networks. CTC enables network operations centers (NOCs) to access performance monitoring data such as remote monitoring (RMON) statistics or autonomous messages across firewalls by using an SNMP 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 15600 SDH Procedure Guide.
13.9 Remote Monitoring
The ONS 15600 SDH incorporates RMON to allow network operators to monitor Ethernet facility performance and events. Software Releases 7.0 and later provide remote data communications channel (DCC) monitoring using 64-bit RMON over the DCC to gather historical and statistical Ethernet data. In general, the ONS 15600 SDH system RMON 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.
Note Typical RMON operations, other than threshold provisioning, are invisible to the CTC user.
13.9.1 64-Bit RMON Monitoring over DCC
The ONS 15600 SDH DCC is implemented over the IP protocol, which is not compatible with Ethernet. The system monitors Ethernet equipment history and statistics using RMON. RMON DCC monitoring for IP and Ethernet is used to check the health of remote DCC connections.
RMON DCC contains two MIBs for DCC interfaces. They are:
•cMediaIndependentTable—Standard, RFC 3273; the proprietary extension of the HC-RMON MIB used for reporting statistics
•cMediaIndependentHistoryTable—Proprietary MIB used to support history
13.9.1.1 Row Creation in MediaIndependentTable
The mediaIndependentTable is created automatically when the Ethernet facility is created on the ONS 15600 SDH ASAP card.
13.9.1.2 Row Creation in cMediaIndependentHistoryControlTable
SNMP row creation and deletion for the cMediaIndependentHistoryControlTable follows the same processes as for the MediaIndependentTable; only the variables differ.
In order to create a row, the SetRequest PDU should contain the following:
•cMediaIndependentHistoryControlDataSource and its desired value
•cMediaIndependentHistoryControlOwner and its desired value
•cMediaIndependentHistoryControlStatus with a value of createRequest (2)
13.9.2 HC-RMON-MIB Support
For the ONS 15600 SDH, 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 should have the ability to upload RFC 3273 SNMP MIB variables in the etherStatsHighCapacityTable, etherHistoryHighCapacityTable, or mediaIndependentTable.
13.9.3 Ethernet Statistics RMON Group
The Ethernet Statistics group contains the basic statistics monitored for each subnetwork in a single table called the etherStatsTable.
13.9.3.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.
13.9.3.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 15600 SDH Ethernet facilities.
13.9.3.3 Row Deletion in etherStatsTable
To delete a row in the etherStatsTable, the SetRequest PDU should contain an etherStatsStatus value of 4 (invalid). The OID marks the row for deletion. If required, a deleted row can be recreated.
13.9.4 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.
13.9.4.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 13-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.
13.9.4.2 Row Creation in historyControlTable
The etherStats table and historyControl table are automatically created when the Ethernet facility is created. History size is based upon the default history bucket located in Table 13-6.
13.9.4.3 Get Requests and GetNext Requests
These PDUs are not restricted.
13.9.4.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.
13.9.4.5 Ethernet History RMON Group
The ONS 15600 SDH 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.
13.9.4.6 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.
13.9.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.
13.9.5.1 Alarm Table
The NMS uses the alarmTable to determine and provision network performance alarmable thresholds.
13.9.5.2 Get Requests and GetNext Requests
These PDUs are not restricted.
13.9.5.3 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.
13.9.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 15600 SDH implements the logTable as specified in RFC 2819.
13.9.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 sent to all provisioned destinations.
•The eventOwner column value is always "monitor."
•The eventStatus column value is always "valid(1)".
13.9.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