The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
An SNMP trap is basically an asynchronous notification set from SNMP agent to a network mangement system. Like other messages in SNMP, traps are sent using UDP.
A trap is a bundle of data that's defined by a managed information base (MIB). Traps falls into catagories: Generic and enterprise-specific.
- Either “proxy-only”
- Or GNE.
Socks Proxy (GNE, ENE, Proxy only, LNE)
If Enable Socks Proxy button is selected. And, GNE is selected.
--- Creates a SOCKS tunnel to be built between the PC running CTC and the Lan connected node.
--- It means it is the Gateway node (GNE) that uses SOCKS PROXY.
--- This optionTurns on Firewall. (GNE = SOCKS PROXY + FIREWALL)
--- This node is LAN connected and has ENE's behind it.
--- ENE's behind GNE cannot advertise across the LAN.
--- You can ping, telnet and CTC to GNE and be able to see all the ENE's behind the GNE.
--- You cannot ping, telnet or CTC to ENE.
If Enable Socks Proxy button is selected. And ENE is selected.
--- Creates a SOCKS tunnel to be built between the PC running CTC and the Lan connected node.
--- This is for nodes that are DCC connected only.
--- This setting prevents the ENE node from adding any routes to the routing table with a next hop of the LAN interface (motfcc0 for 15xxx).
--- You can ping ENE's unless the LAN connected node is a SOCKS GNE.
--- A tech can ping, telnet or CTC to the ENE if connected to the node with a pc in the same subnet as the NE.
If Enable Socks Proxy button is selected. And Socks Proxy Only is selected.
--- Creates a SOCKS tunnel to be built between the PC running CTC and the Lan connected node.
--- Same as GNE except it does not turn on Firewall.
--- Firewall is turned off.
--- You can ping and telnet to the nodes.
If Enable Socks Proxybutton is selected. And Socks Proxy Only is selected.
--- Creates a SOCKS tunnel to be built between the PC running CTC and the Lan connected node.
--- Same as GNE except it does not turn on Firewall.
--- Firewall is turned off.
--- You can ping and telnet to the nodes.
MIB Number |
Module Name |
Technology Specific |
1 |
CERENT-GLOBAL-REGISTRY.mib |
15454 Specific |
2 |
CERENT-TC.mib |
15454 Specific |
3 |
CERENT-454.mib |
15454 Specific |
4 |
CERENT-GENERIC.mib (not applicable to ONS 15454) |
15454 Specific |
5 |
CISCO-SMI.mib |
15454 Specific |
6 |
CISCO-VOA-MIB.mib |
15454 MSTP Specific |
7 |
CERENT-MSDWDM-MIB.mib |
|
8 |
CISCO-OPTICAL-MONITOR-MIB.mib |
|
9 |
CERENT-HC-RMON-MIB.mib |
15454 Specific |
10 |
CERENT-ENVMON-MIB.mib |
15454 Specific |
11 |
CERENT-GENERIC-PM-MIB.mib |
15454 Specific |
Cisco ONS 15454 implements enterprise-specific MIBs as well as standard MIBs from IETF, while the IETF MIBs are common for both Cisco 15327 as well as Cisco 15454, the same is not true for Proprietary MIBs. Each product has a set of three proprietary MIB files.
The enterprise-specific MIB files are available in SMIv2 (Commonly referred to as 'SNMP Version 2 MIB') as well as SMIv1 (Commonly referred to as 'SNMP Version 1 MIB'). Depending on what is required by the NMS, appropriate set of MIB files should be loaded in the NMS.
Note that there are no differences between SMIv2 and SMIv1 MIB files except the syntax, hence it would not impact the NMS if SMIv1 MIB files are loaded instead of SMIv2 MIB files, or vice versa.
An unique feature of SNMP is that a particular version of a mib file is always compatible with all the earlier versions of the same file. For instance, CERENT-454-MIB.mib file is compatible with software version R2.2.3, R2.2.1, R2.0, etc. This is a mandatory property of every SNMP mib and Cisco ONG proprietary MIB files are no exception. Hence, when there is a choice, load the latest MIB files into the NMS for worry-free operations.
Following these guidelines while loading the SNMP MIB files into a Network Management System would make things easier and quicker.
Pick up SMIv2 mib files from above and load the HPOV NNM (HP OpenView Network Node Manager) in the correct order.
The following table shows the dependencies of a mib file that are to be resolved while being loaded in a NMS.
MIB file |
Requires |
BRIDGE-MIB-rfc1493.mib |
RFC1155-SMI |
RFC1212 |
|
RFC1215 |
|
RFC1213-MIB-rfc1213.mib |
|
CERENT-454-MIB.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
CERENT-GLOBAL-REGISTRY.mib |
|
CERENT-TC.mib |
|
CERENT-GENERIC-MIB.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
CERENT-GLOBAL-REGISTRY.mib |
|
CERENT-TC.mib |
|
DS1-MIB-rfc2495.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
IF-MIB-rfc2233.mib |
|
PerfHist-TC-MIB-rfc2493.mib |
|
IANAifType-MIB.mib |
|
SNMPv2-MIB-rfc1907.mib |
|
DS3-MIB-rfc2496.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
IF-MIB-rfc2233.mib |
|
PerfHist-TC-MIB-rfc2493.mib |
|
IANAifType-MIB.mib |
|
SNMPv2-MIB-rfc1907.mib |
|
ENTITY-MIB-rfc2737.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
SNMP-FRAMEWORK-MIB-rfc2571.mib |
|
EtherLike-MIB-rfc2358.mib |
SNMPv2-SMI |
SNMPv2-CONF |
|
SNMPv2-MIB-rfc1907.mib |
|
IANAifType-MIB.mib |
|
IF-MIB-rfc2233.mib |
|
IF-MIB-rfc2233.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
SNMPv2-MIB-rfc1907.mib |
|
IANAifType-MIB.mib |
|
P-BRIDGE-MIB-rfc2674.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
RFC1213-MIB-rfc1213.mib |
|
BRIDGE-MIB-rfc1493.mib |
|
Q-BRIDGE-MIB-rfc2674.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
RFC1213-MIB-rfc1213.mib |
|
BRIDGE-MIB-rfc1493.mib |
|
SNMP-FRAMEWORK-MIB-rfc2571.mib |
|
P-BRIDGE-MIB-rfc2674.mib |
|
RMON-MIB-rfc1757.mib |
|
RMONTOK-rfc1513.mib |
|
RMON2-MIB-rfc2021.mib |
|
RFC1213-MIB-rfc1213.mib |
RFC1155-SMI |
RFC-1212 |
|
RMON-MIB-rfc1757.mib |
RFC1155-SMI |
RFC-1212 |
|
RFC1213-MIB-rfc1213.mib |
|
RFC1215 |
|
SONET-MIB-rfc2558.mib |
SNMPv2-SMI |
SNMPv2-TC |
|
SNMPv2-CONF |
|
SNMPv2-MIB-rfc1907.mib |
|
IANAifType-MIB.mib |
|
IF-MIB-rfc2233.mib |
|
PerfHist-TC-MIB-rfc2493.mib |
1.Read the trap
2.Identify the following:
Trap: TrapId
cerent454AlarmObjectType attrValue: ObjectType
cerent454AlarmState attrValue: ServiceAffecting/ No service Affecting
cerent454AlarmObjectName: Level/Slot/Port
Type = IpAddress, Value = 10.105.142.205 (V2 only)
3.Browse through the Troubleshooting guidelines / alarm troubleshooting, select the proper TrapId, and browse to the related section.
4.Use the information on Level / Slot / Port to identify the card and port affected
5.Implement the procedure and clear the alarm.
SNMPv1 Trap: lossOfSignalForOpticalChannel
(Wed May 05 11:20:49 2014) SNMPv1 Trap: Agent IP = 10.105.142.205, with time = 18 hrs : 31 min : 16.37 sec (6667637)
Enterprise = 1.3.6.1.4.1.3607.6.10.30, Generic = enterpriseSpecific, Specific = lossOfSignalForOpticalChannel
AttrOid1 = cerent454NodeTime.0 , AttrType = OctetString, AttrValue = 20051128022020S
AttrOid2 = cerent454AlarmState.8195.5600 , AttrType = Integer, AttrValue = criticalServiceAffecting(100)
AttrOid3 = cerent454AlarmObjectType.8195.5600 , AttrType = Integer, AttrValue = dwdmTrunk(170)
AttrOid4 = cerent454AlarmObjectIndex.8195.5600 , AttrType = Integer, AttrValue = 8195
AttrOid5 = cerent454AlarmSlotNumber.8195.5600 , AttrType = Integer, AttrValue = 2
AttrOid6 = cerent454AlarmPortNumber.8195.5600 , AttrType = Integer, AttrValue = port2(20)
AttrOid7 = cerent454AlarmLineNumber.8195.5600 , AttrType = Integer, AttrValue = 0
AttrOid8 = cerent454AlarmObjectName.8195.5600 , AttrType = OctetString, AttrValue = CHAN-2-2
Varbind 1 in trap 1.3.6.1.4.1.3607.6.10.100.10.20.0: Matches MIB definition.
Varbind 2 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.80.8195.5600: Matches MIB definition.
Varbind 3 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.20.8195.5600: Matches MIB definition.
Varbind 4 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.60.8195.5600: Matches MIB definition.
Varbind 5 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.30.8195.5600: Matches MIB definition.
Varbind 6 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.40.8195.5600: Matches MIB definition.
Varbind 7 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.50.8195.5600: Matches MIB definition.
Varbind 8 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.100.8195.5600: Matches MIB definition.
SNMPv1 Trap: lossOfSignalForOpticalChannel
(Wed May 05 11:20:49 2014) SNMPv1 Trap: Agent IP = 10.105.142.205, with time = 18 hrs : 31 min : 16.37 sec (6667637)
Enterprise = 1.3.6.1.4.1.3607.6.10.30, Generic = enterpriseSpecific, Specific = lossOfSignalForOpticalChannel
AttrOid1 = cerent454NodeTime.0 , AttrType = OctetString, AttrValue = 20051128022020S
AttrOid2 = cerent454AlarmState.8195.5600 , AttrType = Integer, AttrValue =criticalServiceAffecting(100)
AttrOid3 = cerent454AlarmObjectType.8195.5600 , AttrType = Integer, AttrValue = dwdmTrunk(170)
AttrOid4 = cerent454AlarmObjectIndex.8195.5600 , AttrType = Integer, AttrValue = 8195
AttrOid5 = cerent454AlarmSlotNumber.8195.5600 , AttrType = Integer, AttrValue = 2
AttrOid6 = cerent454AlarmPortNumber.8195.5600 , AttrType = Integer, AttrValue = port2(20)
AttrOid7 = cerent454AlarmLineNumber.8195.5600 , AttrType = Integer, AttrValue = 0
AttrOid8 = cerent454AlarmObjectName.8195.5600 , AttrType = OctetString, AttrValue = CHAN-2-2
The highlighted output above, has to be considered as URGENT alarm.
What to do --> Go to Cisco troubleshooting guideline \ Alarm Troubleshooting:
http://www.cisco.com/c/en/us/td/docs/optical/15000r9_6/dwdm/troubleshooting/guide/b_454d96_ts.html
Identify the Probable Cause and browse to it:
SNMPv2 Trap: lossOfSignalForOpticalChannel
(Wed May 05 11:20:49 2014): SNMPv2 Trap : Request Id = 254, Error Status = No Error , Error Index = 0
Oid1 = sysUpTime.0 , Type = TimeTicks, Value = 116 hrs : 48 min : 23.38 sec (42050338)
Oid2 = snmpTrapOID.0 , Type = ObjectID, Value = 1.3.6.1.4.1.3607.6.10.30.0.5600
Oid3 = cerent454NodeTime.0 , Type = OctetString, Value = 20051128031653S
Oid4 = cerent454AlarmState.65544.5600 , Type = Integer, Value = criticalServiceAffecting(100)
Oid5 = cerent454AlarmObjectType.65544.5600 , Type = Integer, Value = ots(3210)
Oid6 = cerent454AlarmObjectIndex.65544.5600 , Type = Integer, Value = 65544
Oid7 = cerent454AlarmSlotNumber.65544.5600 , Type = Integer, Value = 16
Oid8 = cerent454AlarmPortNumber.65544.5600 , Type = Integer, Value = port1(10)
Oid9 = cerent454AlarmLineNumber.65544.5600 , Type = Integer, Value = 0
Oid10 = cerent454AlarmObjectName.65544.5600 , Type = OctetString, Value = LINE-16-1-RX
Oid11 = 1.3.6.1.6.3.18.1.3.0 , Type = IpAddress, Value = 10.105.142.205
Varbind 3 in trap 1.3.6.1.4.1.3607.6.10.100.10.20.0: Matches MIB definition.
Varbind 4 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.80.65544.5600: Matches MIB definition.
Varbind 5 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.20.65544.5600: Matches MIB definition.
Varbind 6 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.60.65544.5600: Matches MIB definition.
Varbind 7 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.30.65544.5600: Matches MIB definition.
Varbind 8 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.40.65544.5600: Matches MIB definition.
Varbind 9 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.50.65544.5600: Matches MIB definition.
Varbind 10 in trap 1.3.6.1.4.1.3607.6.10.20.30.20.1.100.65544.5600: Matches MIB definition.
Oid11 = 1.3.6.1.6.3.18.1.3.0 , Type = IpAddress, Value = 10.105.142.205
http://www.cisco.com/c/en/us/td/docs/optical/15000r9_6/dwdm/troubleshooting/guide/b_454d96_ts.html
http://issues.opennms.org/secure/attachment/10480/CERENT-454-MIB.txt