H3C S9500 Trap Message. Table of Contents

Transcription

1 Table of Contents Chapter 1 Alarms Introduction Alarm Message Content Alarm Message Format Alarm Message Alarm Level Alarm Modules Alarm Parameters Function Types Chapter 2 Alarm Messages x X/2/PRXYCHKED: BGP bgp/1/trap4: bgp/1/trap4: LDP LDP/5/TRAP: LDP/5/TRAP: LSPM LSPM/5/TRAP: LSPM/5/TRAP: OSPF OSPF/1/ Trap1: OSPF/1/Trap2: OSPF/1/ Trap3: OSPF/1/ Trap4: OSPF/1/ Trap5: OSPF/1/ Trap6: OSPF/1/ Trap7: OSPF/1/ Trap8: OSPF/1/ Trap9: OSPF/1/ Trap10: OSPF/1/ Trap11: OSPF/1/ Trap12: OSPF/1/ Trap13: OSPF/1/ Trap14: OSPF/1/ Trap15: OSPF/1/ Trap16:

2 2.6 MSTP MSTP/2/ ROOT: MSTP/2/ RGSUP: MSTP/2/ IVBPDU: MSTP/2/ LGEXP: POS POS/3/TRAP: POS/2/TRAP: POS/3/TRAP: POS/3/TRAP: POS/2/TRAP: POS/2/TRAP: POS/2/TRAP: POS/2/ TRAP: POS/3/TRAP: POS/3/TRAP: POS/3/TRAP: POS/3/TRAP: POS/3/TRAP: VRRP vrrp/5/trapbecomenewmaster: vrrp/4/ TrapAuthFailed: DEV DEV/2/POWER STATE CHANGE TO FAILURE: DEV/2/POWER STATE CHANGE TO NORMAL: DEV/2/POWER REMOVED: DEV/2/FAN STATE CHANGE TO FAILURE: DEV/2/FAN STATE CHANGE TO NORMAL: DEV/2/BOARD REMOVED: DEV/2/BOARD INSERTED: DEV/2/BOARD STATE CHANGE TO FAILURE: DEV/2/BOARD STATE CHANGE TO NORMAL: DEV/2/BOARD TEMPERATURE LOWER: DEV/2/BOARD TEMPERATURE NORMAL: DEV/2/BOARD TEMPERATURE UPPER DEV/2/BOARD TEMPERATURE NORMAL: DEV/2/BOARD REQUEST LOADING: DEV/2/LOAD FAILURE: DEV/2/LOAD FINISHED: DEV/2/POWER INSERT: DEV/2/PORT POE POWER ON: DEV/2/PSE POWER USAGE OVER THRESHOLD: DEV/2/PSE POWER USAGE BELOW THRESHOLD:

3 DEV/2/PD PULL: DEV/2/PD PULL: ENTITY ENTITY/5/CONFIG CHANGE: HWCM HWCM/5/TRAP: HWCM/5/CFGCOPY: L2INF L2INF/2/ PORT LINK STATUS CHANGE: L2INF/2/PORT LINK STATUS CHANGE: MIX MIX/2/SLAVE SWITCH OVER: RMON rmon/2/ ALARMUP: rmon/2/ ALARMFALL: rmon/2/ RISING: rmon/2/falling: VFS VFS/5/TRAP: SNMP-V ColdStart: WarmStart: AuthenticationFailure:

4 Chapter 1 Alarms 1.1 Introduction When a device fails or the system does not function somehow, the system generates an alarm based on the fault type and the faulty module, and saves the alarm in the alarm buffer of the device. At the same time, the system generates a log. You can determine the size of the alarm buffer as actually needed. If the Network Management System (NMS) is present, the alarm is sent to the NMS through the Simple Network Management Protocol (SNMP). The system can also sense the environment. When the device works beyond its limits, the system generates an alarm. The equipment enables you to view alarm messages on the terminal. Alarm messages are displayed on the terminal interface, and saved in the buffer. You can also view all the alarms saved in the buffer using a command on the device. Alarm messages fall into the following three categories in terms of nature: Failure alarms: Alarms generated due to the failure of hardware or some key functions; Recovery alarms: Alarms generated when the faulty device or abnormal functions are recovered; s: Warnings or alarms generated when the fault and the recovery messages do not match. 1.2 Alarm Message Content This section includes the following contents: Alarm Message Format Alarm Message Alarm Level Alarm Modules Alarm Parameters Alarm Message Format An alarm starts with a # and takes the following format. 1-1

5 Brief AlarmLevel ModuleName HostName TimeStamp Figure 1-1 Alarm output format The fields in the format are described as follows. TimeStamp It specifies the time when the alarm is generated. It is in the format of Mmm dd hh:mm:ss yyyy. Mmm stands for the month in English, that is, Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nove, and Dec. dd is the date. If the value is smaller than 10, fill in as space + date, such as 7. hh:mm:ss is the local time. hh uses the 24-hour system, with a value ranging from 00 to 23. The values for both "mm" and ss range from 00 to 59. yyyy specifies the year. TimeStamp is separated from HostName by a space. HostName It is the system name of the host, H3C by default. HostName is separated from ModuleName by a space. ModuleName It specifies the module that generates the alarm. ModuleName is separated from by a slash (/). Alarm Level Alarms fall into four ranks, ranging from 1 to 4. is separated from Brief by a slash (/). Brief It contains a short term to brief the alarm. Brief is separated from by a colon (:). It contains the character string sent by the module to the information center to detail the specific content of this alarm. 1-2

6 1.2.2 Alarm Message See the following table. Table 1-1 List of basic parameters in an alarm message Alarm message Alarm OID Alarm meaning Character string of alarm message displayed on the device. Object ID defined in the MIB file. The meaning of the alarm message. The nature of the alarm message. Impacts of the failure upon the service. Paramters contained in the alarm message used for alarm location and translation. It specifies the function domain to which the fault belongs Alarm Level It describes probable causes of the alarm message, and locates the exact reasons. It provides the advice for further diagnosis and recovery based on the cause of the alarm message. It describes the related alarm message to locate the root cause of the alarm message and reasons related alarm message occurs. The alarm level identifies the severity of an alarm message. It has the following four ranks with severity in a descending sequence: Critical,, Minor, and Warning. For descriptions, see the following table. Table 1-2 description Definition 1 Critical Such failure affects the services provided by the system and requires action at once. For example, when certain device or resource is completely unavailable, it requires recovery at once. Even if the failure occurs outside the working time, immediate actions are required. 2 Such failure affects the quality of the service, and requires urgent recovery. For example, when the quality of certain device or resource declines, it must be restored so that the full capatility is recovered. In the case of occurrence in working hours, immediate actions are required. 3 Minor Such failure does not affect the quality of the service at the moment. But to avoid more severe failures, processing at proper time or further observation is required. 4 Warning Such failure indicates that there may be potential errors that affect the service. Related measures vary with the errors. 1-3

7 1.2.4 Alarm Modules The following table shows the abbreviations of alarm modules. Table 1-3 s of alarm module abbreviations Alarm Module 802.1X 802.1X protocol module BGP BGP module LDP Label Distribution Protocol module LSPM LSP Management module OSPF OSPF module MSTP MSTP module POS POS management module VRRP VRRP module DEV Device management module ENTITY Entity MIB module HWCM Configuration Management module L2INF Layer 2 Interface management module MIX Slave Swtichover management module RMON RMON module VFS File management module SNMP-V2 SNMP-V2 module Alarm Parameters The following table describes the variables in alarm parameters. Table 1-4 Explanations of alarm parameters Function Types The following table describes the function types. Table 1-5 Explanations of function types Communication alarm Service quality alarm Alarm for error handling Environmental alarm Such alarms are related to the handling process of message transmission, including alarms generated in communication failures between NEs, NE and OS, or OSs. Such alarms result from reduction of the service quality, including alarms generated in congestion, performance reduction, high resource occupation rate, and bandwidth reduction. Such alarms result from software or handling process errors, including alarms generated in service processing such as software error, memory overflow, unmatched versions, and abnormal interruption of programs. Such alarms result from problems related to the location of the device, including alarms generated when the temperature, humidity and ventilation in the environment are abnormal. Such alarms result from faults of physical resources, including alarms generated by devices such as the power, fan, processor, clock, and input or output interface. 1-4

8 Chapter 2 Alarm Messages x X/2/PRXYCHKED: Alarm message The smart proxy-checker report! Alarm OID supplicantproxycheck It is detected that the user connects to the Internet through an agent. Warning $2: VLAN ID $3: Port Name $4: MAC Address $5: IP Address $6: User Name Communication alarm This alarm message has the following trigger actions: The user connects to the Internet through an Agent; There are multiple network cards on the device; The user connects to the Internet through the IE agent. Based on the causes of the alarm message, the suggestions for recovery include: Notify the user to eliminate the agent 2-1

9 2.2 BGP bgp/1/trap4: connection established Alarm message [oid] BgpPeerRemoteAddr = [ipaddr] BgpPeerLastError = [octet] BgpPeerState = [integer] Alarm OID bgpestablished The BGP Established event is generated when the BGP FSM enters the ESTABLISHED state. Establishment of adjacency with BGP Warning $2: IP address of the peer neighbor $3: Record of last break of adjacency $4: Status of the current neighbor Service quality alarm Adjacency with BGP is set up successfully. This alarm informs the user of the successful setup of adjacency with BGP. The user does not need to clear the alarm. Related alarm bgpbackwardtransition: Relationship bgpestablished Relation degree Prossible Cause After the BGP adjacency is set up, when the BGP status changes toward lower status, Related alarm messagebgpbackwardtransition: appears bgp/1/trap4: BGP FSM moves from a higher numbered state to a lower numbered state [oid] BgpPeerRemoteAddr = Alarm message [ipaddr] BgpPeerLastError = [octet] BgpPeerState = [integer] Alarm OID bgpbackwardtransition The BGPBackwardTransition Event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. The BGP FSM moves from the higher numbered state to the lower numbered state. 2-2

10 Warning $2: IP address of the peer neighbor $3: Record of last break of adjacency $4: State of the current neighbor Service quality alarm This alarm message is sent when the BGP neighbor state changes from the higher numbered state to the lower numbered state. State relationship: IDLE(1)<CONNECT(2)<ACTIVE(3)<OPENSENT(4)<OPENCONFIRM(5)<ESTABLIS HED(6) This alarm message informs the user of the change to the BGP adjacency. If it is caused by the link state, check the links. Related alarm bgpestablished message Relationship bgpestablished Relation degree Prossible Cause After the BGP adjacency is set up, when BGP changes to the lower numbered state, Related alarm messagebgpbackwardtransition: appears. 2.3 LDP LDP/5/TRAP: Alarm message [oid] LDP Session [integer] [integer] [integer] [integer] [octet] Changes to Up Alarm OID hwmplsldpsessionupeventfailure Generation of this trap occurs when the value of hwmplsldpsessionstate enters the operational (5) state. The LDP session is set up. $2: LDP case ID, 0 at the moment $3: Interface index, 0 at the moment $4: Peer index, 0 at the moment $5: Session index, 0 at the moment $6: Session ID, LSR ID of the Peer 2-3

11 Communication alarm This alarm is triggered because: The LDP session is set up. LDP/5/TRAP: LDP/5/TRAP: Alarm message [oid] LDP Session [integer] [integer] [integer] [integer] [octet] Changes to Down Alarm OID hwmplsldpsessiondowneventfailure Generation of this trap occurs when the value of hwmplsldpsessionstate leaves the operational (5) state. The LDP session is disconnected. $2: LDP case ID, 0 at the moment $3: Interface index, 0 at the moment $4: Peer index, 0 at the moment $5: Session index, 0 at the moment $6: Session ID, LSR ID of the Peer Communication alarm This alarm has the following trigger actions: The session setup interface fails; Related configurations have been deleted. For example, the LDP or MPLS is disabled. Based on the cause, the recommended actions include: If the session setup interface fails, recover the session by finding and clearing the interface fault; If related configurations have been deleted, restore related configurations to re-set up the LSP. 2-4

12 2.4 LSPM LDP/5/TRAP: LSPM/5/TRAP: Alarm message [oid] LSP [integer] Changes to Up Alarm OID mplsxcup This notification is generated when a mplsxcoperstatus object for one of the configured cross-connect entries is about to leave the down state and transition into some other state (but not into the notpresent state). This other state is indicated by the included value of mplsxcoperstatus. The LSP is set up. $2: LSP index Communication alarm This alarm has the following trigger action: The LSP is set up. LSPM/5/TRAP: LSPM/5/TRAP: Alarm message [oid] LSP [integer] Changes to Down Alarm OID mplsxcdown This notification is generated when an mplsxcoperstatus object for one of the configured cross-connect entries is about to enter the down state from some other state (but not from the notpresent state). This other state is indicated by the included value of mplsxcoperstatus. The LSP is removed. $2: LSP index Communication alarm 2-5

13 2.5 OSPF This alarm has the following trigger actions: The LDP session is disconnected; The LSP setup policy is changed; The route is changed. The route related to this LSP is removed or changed in the next jump; Related configurations have been deleted. For example, the LDP or MPLS is disabled. Based on the cause, the recommended actions include: If the LDP session is disconnected, locate the cause by viewing the link state and related configurations, and recover the session; If the LSP setup policy is changed, restore the policy by using the lsp-trigger command in the MPLS view; If the route is changed, restore the route to re-set up the LSP; If related configurations have been deleted, restore related configurations to re-set up the LSP. LSPM/5/TRAP: OSPF/1/ Trap1: OSPF virtual link state changed [oid] VirIfAreaId = [ipaddr] Alarm message VirIfNbrId = [ipaddr] RouterId = [ipaddr] VirIfState = [integer] Alarm OID ospfvirtifstatechange An ospfifstatechange trap signifies that there has been a change in the state of an OSPF virtual interface. This trap should be generated when the link state regresses (e.g., goes from Point-to-Point to Down) or progresses to a terminal state (i.e., Point-to-Point). The state of the link on an OSPF virtual interface changes. Warning $1:Alarm OID $2: Area ID of the virtual interface $3: Neighbor router of the virtual interface $4: Local router $5: Virtual link state 2-6

14 Service quality alarm Possible causes of the state change of the link on an OSPF virtual interface include: Normal state change. For example, the OSPF virtual interface serves as the Designated Router (DR); The link state on an interface changes. For example, the link is set to Down. If the alarm is caused by an link state change on the interface, find the cause of the change: if the link state is changed to Down through the command line, recover the state through the command Undo Shutdown on this interface; if the hardware on the interface fails, change the faulty hardware; if the peer interface fails, clear the fault OSPF/1/Trap2: OSPF neighbour state changed [oid] NbrIpAddress = [ipaddr] NbrAddrLessIndex = [integer] Alarm message RouterId = [ipaddr] NbrRouterId = [ipaddr] NbrState = [integer] Alarm OID ospfnbrstatechange An ospfnbrstatechange trap signifies that there has been a change in the state of a non-virtual OSPF neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., 2-Way or Full). When a neighbor transitions from or to Full on non-broadcast multi-access and broadcast networks, the trap should be gen-erated by the designated router. A designated router transitioning to Down will be noted by ospfifstatechange. The state of an OSPF neighbor changes. Warning $2: IP address of the neighbor $3: No address interface index in the neighbor $4: Local router $5: Neighbor router $6: Neighbor state Service quality alarm Possible causes of the state change of an OSPF neighbor include: 2-7

15 The OSPF neighbor state changes from the lower numberd state to the higher numbered state, that is, normal setup of adjacency; The OSPF neighbor state changes from the higher numbered state to the lower numbered state, that is, abnormal adjacency. No alarm recovery is needed when the OSPF adjacency is set up normally; When the OSPF neighbor changes from the higher numbered state to the lower numbered state, the user should check for abnormal link state. If there is no abnormal link state, check whether the peer neighbor normally sends the Hello packet OSPF/1/ Trap3: OSPF virtual neighbour state changed [oid] VirNbrAreaId = [ipaddr] Alarm message VirNbrRtrId = [ipaddr] RouterId = [ipaddr] VirNbrState = [integer] Alarm OID ospfvirtnbrstatechange An ospfifstatechange trap signifies that there has been a change in the state of an OSPF vir-tual neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., Full). The state of an OSPF virtual neighbor changes. Warning $2: Area ID of the virtual link $3: Neighbor router of the virtual link $4: Local router $5: Neighbor state of the virtual link Service quality alarm Possible causes of the change to the state of an OSPF virtual neighbor include: The OSPF neighbor state changes from the lower numbered state to the higher numbered state, that is, normal setup of adjacency; The OSPF neighbor state changes from the higher numbered state to the lower numbered state, that is, abnormal setup of adjacency. 2-8

16 No alarm recovery is needed when the OSPF adjacency is set up normally; When the OSPF neighbor changes from the higher numbered state to the lower numbered state, the user should check for abnormal link state. If there is no abnormal link state, check further whether the peer neighbor normally sends the report OSPF/1/ Trap4: OSPF interface configuration error IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] Alarm message RouterId = [ipaddr] PacketSrc = [ipaddr] ErrorType = [integer] PacketType = [integer] Alarm OID ospfifconfigerror An ospfifconfigerror trap signifies that a packet has been received on a non-virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event op-tionmismatch should cause a trap only if it prevents an adjacency from forming. OSPF interface configurations conflict. Warning $2: IP address of the interface $3: No address interface index $4: Local router $5: Packet source address $6: Error type $7: Packet type Service quality alarm The local terminal is not a vlan interface. The parameter configurations on both interfaces are different. In this case, the adjacency cannot be normally set up. The inconsistency of parameter configuration includes: OSPF version numbers, region configurations, network mask configurations, time settings of Hello packet timer, and time settings of the Dead timer. Check whether the configurations mentioned earlier are the same. 2-9

17 2.5.5 OSPF/1/ Trap5: OSPF virtual interface configuration error [oid] VirIfAreaId = [ipaddr] VirIfNbrId = [ipaddr] Alarm message RouterId = [ipaddr] ErrorType = [integer] PacketType = [integer] \r\n Alarm OID ospfvirtifconfigerror An ospfconfigerror trap signifies that a packet has been received on a virtual interface from a router whose configuration parameters conflict with this router s configuration parameters. Note that the event optionmismatch should cause a trap only if it prevents an adjacency from forming. OSPF virtual link interface configurations conflict. Warning $2: Area ID of the virtual interface $3: Neighbor router of the virtual link $4: Local router $5: Error type $6: Packet type Service quality alarm The local terminal is not a vlan interface. The parameter configurations on both interfaces are not the same. The inconsistency of parameter configuration includes: OSPF version numbers, region configurations, network mask configurations, time settings of Hello packet timer, and time settings of the Dead timer. Check whether the configurations mentioned earlier are the same. 2-10

18 2.5.6 OSPF/1/ Trap6: OSPF interface authentication failure [oid] IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] Alarm message RouterId = [ipaddr] PacketSrc = [ipaddr] ErrorType = [integer] PacketType = [integer] Alarm OID ospfifauthfailure An ospfifauthfailure trap signifies that a packet has been received on a non-virtual in-terface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type. The OSPF interface authentication fails. Warning $2: IP address of the interface $3: Local address interface index $4: Local router $5: Packet source address $6: Error type $7: Packet type Service quality alarm Authentication configurations on both interfaces are not the same. Check configurations of the authentication type and key on both interfaces. Set the types and keys to the same OSPF/1/ Trap7: OSPF virtual interface authentication failure [oid] VirIfAreaId = [ipaddr] VirIfNbrId = [ipaddr] Alarm message RouterId = [ipaddr] ErrorType = [integer] PacketType = [integer] Alarm OID ospfvirtifauthfailure 2-11

19 An ospfvirtifauthfailure trap signifies that a packet has been received on a virtual interface from a router whose authentication key or au-thentication type conflicts with this router's authentication key or authentication type. The OSPF virtual link interface authentication fails. Warning $2: Area ID of the virtual interface $3: Neighbor router of the virtual interface $4: Local router $5: Error type $6: Packet type Service quality alarm Authentication keys on both interfaces are not the same. Check the authentication types and keys on both interfaces. Set the types and keys to the same OSPF/1/ Trap8: OSPF interface received wrong packet [oid] IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] Alarm message RouterId = [ipaddr] PacketSrc = [ipaddr] PacketType = [integer] Alarm OID ospfifrxbadpacket An ospfifrxbadpacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed. The OSPF interface receives a wrong packet. Warning $2: IP address of the interface $3: No address interface index $4: Local router $5: Packet source address $6: Packet type Service quality alarm 2-12

20 The local termination is not a vlan interface. It receives a bad packet. Bad packets include: packets with wrong types, IP addresses, or protocols, packets from an unknown neighbor, small bad packets, large bad packets, checksum error, Router ID conflict in Hello packets, Router ID conflict in DD packets, neighbor state errors in DD, LSA update, LSA request, or LSA confirmation packets, and empty LSA request packets. Check whether the configuration on the related neighbor at this interface is correct, or whether there is an aggressive packet OSPF/1/ Trap9: OSPF virtual interface received wrong packet [oid] VirIfAreaId = [ipaddr] Alarm message VirIfNbrId = [ipaddr] RouterId = [ipaddr] PacketType = [integer] Alarm OID OspfVirtIfRxBadPacket An ospfrxbadpacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed. The OSPF virtual link interface receives a wrong packet. Warning $2: Area ID of the virtual interface $3: Neighbor router of the virtual interface $4: Local router $5: Local router Service quality alarm The local termination is a vlan interface. It receives a bad packet. Bad packets include: packets with wrong types, IP addresses, or protocols, packets from an unknown neighbor, small bad packets, large bad packets, checksum error, Router ID conflict in Hello packets, Router ID conflict in DD packets, neighbor state errors in DD, LSA update, LSA request, or LSA confirmation packets, and empty LSA request packets. 2-13

21 Check whether the configuration on the related neighbor at this interface is correct, or whether there is an aggressive packet OSPF/1/ Trap10: OSPF interface retransmitted packet [oid] IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] NbrIpAddress = [ipaddr] NbrAddrLessIndex = [integer] LsdbAreaId = [ipaddr] Alarm message LsdbType = [integer] LsdbLsid = [ipaddr] LsdbRouterId = [ipaddr] RouterId = [ipaddr] NbrRouterId = [ipaddr] PacketType = [integer] Alarm OID ospftxretransmit An ospftxretransmit trap signifies that an OSPF packet has been retransmitted on a non-virtual interface. All packets that may be re-transmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry. The OSPF interface retransmits a packet. Warning $2: IP address of the interface $3: No address interface index $4: IP address of the neighbor $5: No address interface index in the neighbor $6: LSA area ID $7: LSA type $8: LSA ID $9: LSA release router $10: Local router $11: Neighbor router $12: Packet type Service quality alarm The local terminal is a non-virtual interface. When it does not receive the confirmation packet of a related LSA within the configured time, it retransmits the LSA. 2-14

22 OSPF/1/ Trap11: OSPF virtual interface retransmitted packet [oid] VirIfAreaId = [ipaddr] VirIfNbrId = [ipaddr] LsdbAreaId = [ipaddr] Alarm message LsdbType = [integer] LsdbLsid = [ipaddr] LsdbRouterId = [ipaddr] RouterId = [ipaddr] PacketType = [integer] Alarm OID ospfvirtiftxretransmit An ospftxretransmit trap signifies than an OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmit-ted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry. The link of the OSPF virtual interface retransmits a packet. Warning $2: Area ID of the virtual interface $3: Neighbor router of the virtual interface $4: LSA area ID $5: LSA type $6: LSA ID $7: LSA release router $8: Local router $9: Packet type Service quality alarm The local terminal is a virtual interface. When it does not receive the confirmation packet of a related LSA within the configured time, it retransmits the LSA. 2-15

23 OSPF/1/ Trap12: OSPF (re)originated LSA [oid] LsdbAreaId = [ipaddr] LsdbType = [integer] Alarm message LsdbLsid = [ipaddr] LsdbRouterId = [ipaddr] RouterId = [ipaddr] Alarm OID ospforiginatelsa An ospforiginatelsa trap signifies that a new LSA has been originated by this router. The OSPF (re-)generates an LSA. Warning $2: LSA area ID $3: LSA type $4: LSA ID $5: LSA release router $6: Local router Service quality alarm When a new router is added in a network, a router LSA is generated in the area of the router; When the DR in a network segment changes, or a new router is placed in the segment, the DR generates a network LSA; When there is a change to the link state in the area where the Area Border Router (ABR) locates, a new network summary LSA is generated; When there is a change to the Autonomous System Border Router (ASBR) in the area where the ABR locates, a new network summary LSA is generated; When there is a change to the external route imported by the ASBR, a new ASE LSA is generated; When there is a change to the external route brought to the NSSA area, the router that brings this external route generates a new NSSA LSA; All situations stated above lead to this alarm message. 1) Check whether a cable was wrongly connected or disconnected before the alarm message; 2) Check whether there is a new router in the network; 3) Check whether there is a router removed from the network; 2-16

24 4) Check whether the interface of a router fails; 5) Check whether there is a change to the external route brought to the network OSPF/1/ Trap13: OSPF LSA reached max-age [oid] LsdbAreaId = [ipaddr] LsdbType = [integer] Alarm message LsdbLsid = [ipaddr] LsdbRouterId = [ipaddr] RouterId = [ipaddr] Alarm OID ospfmaxagelsa An ospfmaxagelsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge. The OSPF LSA reaches the max age. Warning $2: LSA area ID $3: LSA type $4: LSA ID $5: LSA release router $6: Local router Service quality alarm The neighbor state changes. The neighbor cannot send new packets. The router that generated this LSA fails and cannot generate new LSAs. There is a change to the router that generated this LSA. For example, the DR changes. 1) Check whether a wrong configuration existed or a cable was wrongly connected or disconnected before the alarm message is generated; 2) Check whether there is a change to the link state of the router that generated this LSA; 3) Check the ID of the router that generated this LSA. For example, if the category-3 LSA generates an alarm message, check whether the related router is still an ABR; if the category-2 LSA generates an alarm message, check whether the related router is still a DR; 2-17

25 4) Check whether there is a change to the neighbor state; 5) Check whether the link of a router fails OSPF/1/ Trap14: OSPF number of LSAs exceeded ExtLsdbLimit [oid] Alarm message RouterId = [ipaddr] ExtLsdbLimit = [integer] Alarm OID ospflsdboverflow An ospflsdboverflow trap signifies that the number of LSAs in the router's link-state database has exceeded ospfextlsdblimit. The OSPF LSA number reaches ExtLsdbLimit. Warning $2: Local router $3: ExtLsdbLimit Service quality alarm There are excessive routers, resulting in excessive router LSAs in the area; Routes in category-3 LSAs that can be aggregated are not converged, resulting in excessive category-3 LSAs; There are excessive external routes brought to the network, resulting in excessive category-5 LSAs. This is the normal warning in the protocol, and requires no processing. Related alarm message Relationship Relation degree Cause OSPF/1/ Trap15: ospflsdbapproachingoverflow Prossible If the number of LSAs increases to ExtLsdbLimit after the ospflsdbapproachingoverflow alarm, this alarm message appears. 2-18

26 OSPF/1/ Trap15: OSPF number of LSAs exceeded 90%% ExtLsdbLimit [oid] Alarm message RouterId = [ipaddr] ExtLsdbLimit = [integer] Alarm OID ospflsdbapproachingoverflow An ospflsdbapproachingoverflow trap signifies that the number of LSAs in the router's linkstate database has exceeded ninety percent of ospfextlsdblimit. The OSPF LSA number reaches 90% of ExtLsdbLimit. Warning $2: Local router $3: ExtLsdbLimit Service quality alarm There are excessive routers, resulting in excessive router LSAs in the area; Routes in category-3 LSAs that can be aggregated are not converged, resulting inexcessive category-3 LSAs; There are excessive external routes brought to the network, resulting in excessive category-5 LSAs. This is the normal prompt message in the protocol, and requires no processing. Related alarm message Relationship Relation degree Cause OSPF/1/ Trap14: ospflsdbapproachingoverflow Prossible If the number of LSAs continues to increase to ExtLsdbLimit after this alarm, the ospflsdbapproachingoverflow alarm message appears OSPF/1/ Trap16: OSPF link state changed [oid] IfIpAddress = [ipaddr] Alarm message IfAddrLessIndex = [integer] RouterId = [ipaddr] IfState = [integer] Alarm OID

27 ospfifstatechange An ospfifstatechange trap signifies that there has been a change in the state of a non-virtual OSPF interface. This trap should be generated when the link state regresses (e.g., goes from Dr to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, Dr, or Backup). The OSPF link state changes. Warning $1:Alarm OID $2: IP address of the interface $3: Router ID of the OSPF $4: Interface state Service quality alarm 2.6 MSTP Possible causes of the state change of an OSPF interface include: Normal state change. For example, when the OSPF interface serves as the DR; The link state changes. For example, the link state is set to Down. Normal change to the OSPF link state does not require recovery. If the alarm message is caused by a change of link state on the interface, find the cause of the change: If the link state is changed to Down through the command line, recover the state through the command Undo Shutdown on this interface; If the hardware on the interface fails, change the hardware; If the peer interface fails, clear the fault MSTP/2/ ROOT: Alarm message [OID]: We are not the root switch of the instance [INTEGER]! Alarm OID hwbridgelostrootprimary The SNMP trap that is generated when the bridge is no longer the root bridge of the instance. Another switch with higher priority has already been the root bridge of the instance. The switch that has been configured as the root bridge of an instance receives a superior packet and becomes no longer the root bridge of the instance. 1: hwdot1sinstanceid instance ID Environmental alarm 2-20

28 The equipment that has been configured as the root bridge of an instance receives the superior packet of this instance. If the local switch is configured as the root bridge of an instance, and another switch with a smaller MAC address is also configured as the root bridge of the instance, the second switch will preempt the root bridge of the local switch in the instance. In this case, the alarm is generated. Check whether another switch is configured as the root bridge of the same instance. If so, change the configuration to ensure that only one switch is configured as the root bridge of one instance MSTP/2/ RGSUP: Alarm message [OID]: Instance [INTEGER]'s ROOT-Protection port [INTEGER].[INTEGER] received superior message! Alarm OID hwportmstirootguarded The SNMP trap that is generated when a root-guard port receives a superior message on the relevant instance. The root-guard port receives a superior message. 1: hwdot1sinstanceid instance ID 2: hwdot1smstiportindex port Index Environmental alarm For Root-protection ports, they can only be designated ports for instances. Once this port receives a configuration message with a higher priority from some instance, this alarm is generated. The port of this instance is set to interception state and does not transfer packets any more (that is, the links of this port are disconnected).when no configuration message with a higher priority is received in a considerable period of time, the port resumes the normal state. Check where the packet with higher priority comes from and whether the configuration is wrong. 2-21

29 2.6.3 MSTP/2/ IVBPDU: Alarm message [OID]: BPDU-Protection port [INTEGER] received BPDU packet! Alarm OID hwportmstibpduguarded The SNMP trap that is generated when an edged port of the BPDU-guard switch receives BPDU packets. A BPDU-protection edged port receives BPDU packets. 1: dot1dstpport port Index Environmental alarm For the equipment at the access layer, the access ports are often directly connected to the user terminal (such as a PC) or file server. At this time, the access ports are set as an edged port to realize fast migration. When these ports receive a configuration message (BDPU packet), the system automatically sets these ports to non-edged ports, and re-calculates the Spanning Tree, leading to network topology storm. Under normal condition, these ports do not receive configuration messages of the Spanning Tree protocol. If a person forges configuration messages to attack the switch with malice, a network storm occurs. MSTP uses BPDU-protection to prevent such attacks. The BPDU-protection is enabled in the switch. Once the edged ports receive configuration messages, the system generates this alarm message and closes these ports. The closed ports can only be resumed by network administrators. Edged ports are generally connected to a PC or file server. Hence they do not receive BPDU packets under normal condition.check the source of the BPDU this port receives. Check whether this port is wrongly connected to a switch. Recover the port connection first, and then undo shutdown the port. 2-22

30 2.6.4 MSTP/2/ LGEXP: Alarm message [OID]: Instance [INTEGER]'s LOOP-Protection port [INTEGER].[INTEGER] did not receive message! Alarm OID hwportmstiloopguarded The SNMP trap that is generated when an Alternate-Port or Root-Port is aged out. A root port or optional port times out when receiving a BPDU message. 1: hwdot1sinstanceid instance ID 2: hwdot1smstiportindex port Index Environmental alarm 2.7 POS The root port or optional port does not receive the BPDU packet from the upstream for a long time, leading to timeout of the port in receiving the BPDU message. Check whether the upstream port normally sends a packet and whether the local port normally receives the packet POS/3/TRAP: Alarm message [oid] LRDI Alarm on interface [INTEGER] Alarm OID h3cposlrdialarm LRDI is used to return an indication to the transmit end that the received end has detected an incoming section defect or is receiving LAIS.LRDI is generated by inserting a 110 code in positions 6,7 and 8 of the K2 byte befor scrambing. LRDI is used to inform the transmission end of a serious link failure at the local end or of the event that the local end receives an LAIS. LRDI is generated by inserting 110 into bits 6, 7, and 8 in K2. Failure alarm $2: Interface of the alarm 2-23

31 The peer end has a serious link failure or receives an LAIS alarm message. Check the links or peer configuration POS/2/TRAP: Alarm message [oid] LOF Alarm on interface [INTEGER] Alarm OID h3cposlofalarm This alarm message indicates loss of frame. Frame alignment loss Failure alarm $2: Interface of the alarm Bit errors occur in the links. Check the links POS/3/TRAP: Alarm message [oid] OOF Alarm on interface [INTEGER] Alarm OID h3cposoofalarm Alarm indicates out of frame. Out of framed alignment. Failure alarm $2: Interface of the alarm 2-24

32 Bit errors occur in the links. Check the link connection POS/3/TRAP: Alarm message [oid] PRDI Alarm on interface [INTEGER] Alarm OID h3cposprdialarm PRDI is used to return an indication to the transmit STS PTE that the receiving STS PTE has detected an incoming STS Path defect.. PRDI is used to return an indication to the transmission STS PTE that the local STS PTE has detected a serious STS Path defect. Failure alarm $2: Interface of the alarm An error occurs in the net load boren by the path layer or the path layers are not normally connected. Check whether the path layers are configured in the same way at both ends, and whether the path layer connection is abnormal POS/2/TRAP: Alarm message [oid] LOS Alarm on interface [INTEGER] 2-25

33 Alarm OID h3cposlosalarm Alarm indicates loss of signal. A signal is lost. Failure alarm $2: Interface of the alarm The reception end cannot detect 01 transient within 20us. 1. Check the connection; 2. Check whether the scrambles at both ends are configured in the same way POS/2/TRAP: Alarm message [oid] LOP Alarm on interface [INTEGER] Alarm OID h3cposlopalarm Alarm indicates loss of pointer. A pointer is lost. Failure alarm $2: Interface of the alarm An LOP alarm message appears when 8 consecutive frames receive an invalid pointer or NDF. 1. Check clock configuration; 2. Check frame format configurations at both ends. 2-26

34 2.7.7 POS/2/TRAP: Alarm message [oid] LAIS Alarm on interface [INTEGER] Alarm OID h3cposlaisalarm LAIS is used to indicate that a signal defect has been detected at a section terminating equipment. LAIS is detected by a 111 code in bits 6,7 and 8 of the K2 byte after unsrambing. The local end receives an LOS or LOF alarm message. Failure alarm $2: Interface of the alarm The local end receives an LOS or LOF alarm message. Check whether links are normally connected POS/2/ TRAP: Alarm message [oid] PAIS Alarm on interface [INTEGER] Alarm OID h3cpospaisalarm PAIS is generated by an LTE upon detection of an LOS, LOF, AIS-L, or LOP-P defect.. PAIS alarm message appears when the local end receives an LOS, LOF, AIS-L or LOP-P alarm message. Failure alarm $2: Interface of the alarm The local end receives a serious alarm message such as LOS, LOF, AIS-L and LOP. Check whether links are normally connected. 2-27

35 2.7.9 POS/3/TRAP: Alarm message [oid] STIM Alarm on interface [INTEGER] Alarm OID h3cposstimalarm Alarm indicates inconsistency between sent and received J0 bytes. The received J0 bytes are different from the expected. Failure alarm $2: Interface of the alarm The received J0 bytes are different from the expected. Check whether J0 bytes are configured in the same way at both ends POS/3/TRAP: Alarm message [oid] PTIM Alarm on interface [INTEGER] Alarm OID h3cposptimalarm Alarm indicates inconsistency between sent and received J1 bytes. The received J1 bytes are different from the expected. Failure alarm $2: Interface of the alarm The received J1 bytes are different from the expected. 2-28

36 Check whether J1 bytes are configured in the same way at both ends POS/3/TRAP: Alarm message [oid] PSLM Alarm on interface [INTEGER] Alarm OID h3cpospslmalarm Alarm indicates a mismatched C2 byte. The received C2 bytes are different from the expected. Failure alarm $1:Alarm OID $2: Interface of the alarm The received C2 bytes are different from the expected. Check whether C2 bytes are configured in the same way at both ends POS/3/TRAP: Alarm message [oid] LSD Alarm on interface [INTEGER] Alarm OID h3cposlsdalarm Alarm indicates that the B2 bit-error rate exceeds SD threshold. The bit-error rate exceeds the SD threshold. Failure alarm $2: Interface of the alarm 2-29

37 The bit-error rate exceeds the SD threshold. Check whether errors occur in the optical fiber and optical module POS/3/TRAP: Alarm message [oid] LSM Alarm on interface [INTEGER] Alarm OID h3cposlsfalarm Alarm indicates that the B2 bit-error rate exceeds SF threshold. The bit-error rate exceeds the SF threshold. Failure alarm $2: Interface of the alarm 2.8 VRRP The bit-error rate exceeds the SF threshold. Check whether errors occur in the optical fiber and optical module vrrp/5/trapbecomenewmaster: Alarm message [oid]become new master Alarm OID vrrptrapnewmaster A device become new master The device becomes the master virtual switch. 2-30

38 Warning Communication alarm 1) When a new group of VRRP backup switches are set up, one switch will be designated as the master; 2) When the priority of a switch that was not the master switch is elevated to a level higher than the former master, this switch becomes the new master; 3) When the master switch fails, the switch in the backup group that has the highest priority becomes the master vrrp/4/ TrapAuthFailed: Alarm message [oid]failed to authenticate Alarm OID vrrptrapauthfailure Virtual router anthtication failure,master and backup don not same The authentication passwords are different in the master and slave switches. Warning Communication alarm The VRRP packet authentication passwords are different in the master and slave switches. Set the authentication passwords in the master and slave switches to the same. 2-31

39 2.9 DEV DEV/2/POWER STATE CHANGE TO FAILURE: Alarm message Trap [OID]: power ID is [INTEGER] Alarm OID Powerfailure Equipment power failure. The alarm appears when the power is just inserted to the equipment or some power in the equipment fails. The power fails. Failure alarm $1: OID $2: Power ID The power fails. Replace the power. Related alarm message DEV/2/ POWER STATE CHANGE TO NORMAL: Relationship DEV/2/ POWER STATE CHANGE TO FAILURE: Relation degree Certain Cause The related alarm is the recovery alarm. If this fault is recovered, the related alarm appears. If the fault is not recovered, this related alarm does not appear DEV/2/POWER STATE CHANGE TO NORMAL: Alarm message Trap [OID]: power ID is [INTEGER] Alarm OID hwpowernormal This alarm message appears when the power state turns normal. The power is normal. Recovery alarm 2-32