huawei series ethernet switches alarm handling s2750&5700&6700.pdf

S2750&S5700&S6700 Series Ethernet Switches

V200R003(C00&C02&C10)

Alarm Handling

Issue 06

Date 2014-07-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://enterprise.huawei.com

Issue 06 (2014-07-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://enterprise.huawei.com

About This Document

Intended AudienceThis document provides the trap description, attributes, parameters, impact on the system,possible causes, procedures, and references.

This document provides a complete set of traps, through which intended readers are kept of therunning status of the device so as to locate faults.

This document is intended for:

l Commissioning engineers

l Network monitoring engineers

l System maintenance engineers

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

Indicates an imminently hazardous situationwhich, if not avoided, will result in death orserious injury.

Indicates a potentially hazardous situationwhich, if not avoided, could result in death orserious injury.

Indicates a potentially hazardous situationwhich, if not avoided, may result in minor ormoderate injury.

Indicates a potentially hazardous situationwhich, if not avoided, could result inequipment damage, data loss, performancedeterioration, or unanticipated results.NOTICE is used to address practices notrelated to personal injury.

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling About This Document


ii

Symbol Description

NOTE Calls attention to important information, bestpractices and tips.NOTE is used to address information notrelated to personal injury, equipment damage,and environment deterioration.

Command ConventionsThe command conventions that may be found in this document are defined as follows.

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

&<1-n> The parameter before the & sign can be repeated 1 to n times.

# A line starting with the # sign is comments.

Mappings between Product Software Versions and NMSVersions

The mappings between product software versions and NMS versions are as follows.

Product Software Version eSight

V200R003C00 V200R003C01

V200R003C02 V200R003C10



iii

Product Software Version eSight

V200R003C10 V200R005C00

Change HistoryChanges between document issues are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 06 (2014-07-30) V200R003(C00&C02&C10)

This version has the following updates:

Some contents are modified according to updates in the product.

Updates in Issue 05 (2014-05-15) V200R003(C00&C02&C10)



Updates in Issue 04 (2013-11-06) V200R003(C00&C02)



Updates in Issue 03 (2013-09-30) V200R003(C00&C02)


The following information is added:

l 16.20 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135190l 16.21 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135191l 16.22 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135192l 16.26 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135193l 16.23 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135190l 16.24 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135191l 16.25 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135192l 16.27 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135193l 16.28 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid 135450-135458l 16.29 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid 135459l 16.30 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume

135450-135458l 16.31 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume 135459



iv

l 16.32 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.9.1 hwCommunicateError 135457l 16.33 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.9.2 hwCommunicateResume 135457

Updates in Issue 02 (2013-07-25) V200R003C00This version has the following updates:


Updates in Issue 01 (2013-05-30) V200R003C00Initial commercial release.



v

Contents

About This Document.....................................................................................................................ii

1 Locating Alarms.............................................................................................................................1

2 Introduction....................................................................................................................................22.1 Alarm Message Format Description...............................................................................................................................32.2 Alarm Functionality Description....................................................................................................................................42.3 Alarm Information Description......................................................................................................................................52.4 Alarm Severity Description............................................................................................................................................5

3 ACL...................................................................................................................................................83.1 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.1 hwAclResThresholdExceedClearTrap..............................................................93.2 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.2 hwAclResThresholdExceedTrap.....................................................................103.3 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.3 hwAclResTotalCountExceedClearTrap..........................................................113.4 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.4 hwAclResTotalCountExceedTrap...................................................................12

4 ARP.................................................................................................................................................134.1 ARP_1.3.6.1.4.1.2011.5.25.123.2.1 hwEthernetARPSpeedLimitAlarm.....................................................................144.2 ARP_1.3.6.1.4.1.2011.5.25.123.2.4 hwEthernetARPThresholdExceedAlarm............................................................164.3 ARP_1.3.6.1.4.1.2011.5.25.123.2.5 hwEthernetARPThresholdResumeAlarm...........................................................184.4 ARP_1.3.6.1.4.1.2011.5.25.123.2.6 hwEthernetARPIPConflictEvent........................................................................19

5 BASETRAP...................................................................................................................................215.1 BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.19_hwEntityDyingGasp.........................................................................22

6 BFD.................................................................................................................................................246.1 BFD_1.3.6.1.4.1.2011.5.25.38.3.1 hwBfdSessDown...................................................................................................256.2 BFD_1.3.6.1.4.1.2011.5.25.38.3.2 hwBfdSessUp........................................................................................................276.3 BFD_1.3.6.1.4.1.2011.5.25.38.3.3 hwBfdSessReachLimit..........................................................................................296.4 BFD_1.3.6.1.4.1.2011.5.25.38.3.4 hwBfdSessReachLimitBindIf...............................................................................31

7 BGP.................................................................................................................................................337.1 BGP_1.3.6.1.2.1.15.7.1 bgpEstablished.......................................................................................................................347.2 BGP_1.3.6.1.2.1.15.7.2 bgpBackwardTransition.........................................................................................................367.3 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.1 hwBgpPeerRouteNumThresholdExceed.........................................................437.4 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.2 hwBgpPeerRouteNumThresholdClear............................................................467.5 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.3 hwBgpPeerGRStatusChange...........................................................................47

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling Contents


vi

7.6 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished....................................................................................507.7 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.10 hwBgpPeerBackwardTransition....................................................................53

8 CMD...............................................................................................................................................608.1 CMD_1.3.6.1.4.1.2011.5.25.37.2.136 hwSuperChangeSuccesful...............................................................................618.2 CMD_1.3.6.1.4.1.2011.5.25.37.2.137 hwSuperChangeFailure...................................................................................618.3 CMD_1.3.6.1.4.1.2011.5.25.205.2.1 hwClockChanged..............................................................................................62

9 MAD...............................................................................................................................................649.1 MAD_1.3.6.1.4.1.2011.5.25.246.1.1 hwMadConflictDetect.......................................................................................659.2 MAD_1.3.6.1.4.1.2011.5.25.246.1.2 hwMadConflictResume.....................................................................................65

10 DHCP...........................................................................................................................................6710.1 DHCP_1.3.6.1.4.1.2011.5.25.112.2.1 hwDhcpSnpChaddrAlarm..............................................................................6810.2 DHCP_1.3.6.1.4.1.2011.5.25.112.2.4 hwUntrustedReplyPktAlarm..........................................................................6910.3 DHCP_1.3.6.1.4.1.2011.5.25.112.2.5 hwNomatchSnpBindTblDhcpPktAlarm........................................................7010.4 DHCP_1.3.6.1.4.1.2011.5.25.112.2.6 hwDhcpPktRateAlarm...................................................................................7110.5 DHCP_1.3.6.1.4.1.2011.5.25.112.2.8 hwSnpUserNumberAlarmIf...........................................................................7210.6 DHCP_1.3.6.1.4.1.2011.5.25.112.2.9 hwSnpUserNumberAlarmIfResume..............................................................7310.7 DHCP_1.3.6.1.4.1.2011.5.25.112.2.10 hwSnpUserNumberAlarmVlan....................................................................7510.8 DHCP_1.3.6.1.4.1.2011.5.25.112.2.11 hwSnpUserNumberAlarmVlanResume.......................................................7610.9 DHCP_1.3.6.1.4.1.2011.5.25.112.2.12 hwSnpUserNumberAlarmGlobal.................................................................7710.10 DHCP_1.3.6.1.4.1.2011.5.25.112.2.13 hwSnpUserNumberAlarmGlobalResume..................................................7810.11 DHCP_1.3.6.1.4.1.2011.5.25.112.2.14 hwNdSnpUserNumberAlarmIf..................................................................7910.12 DHCP_1.3.6.1.4.1.2011.5.25.112.2.15 hwNdSnpUserNumberAlarmIfResume.....................................................8010.13 DHCP_1.3.6.1.4.1.2011.5.25.112.2.16 hwNdSnpUserNumberAlarmGlobal..........................................................8110.14 DHCP_1.3.6.1.4.1.2011.5.25.112.2.17 hwNdSnpUserNumberAlarmGlobalResume.............................................82

11 DLDP............................................................................................................................................8411.1 DLDP_1.3.6.1.4.1.2011.5.25.173.3.1 hwDldpUnidirectionalLink............................................................................8511.2 DLDP_1.3.6.1.4.1.2011.5.25.173.3.2 hwDldpLinkResume......................................................................................8911.3 DLDP_1.3.6.1.4.1.2011.5.25.173.3.3 hwDldpLoopDetect........................................................................................9011.4 DLDP_1.3.6.1.4.1.2011.5.25.173.3.4 hwDldpLoopResume......................................................................................91

12 DOT1X.........................................................................................................................................9312.1 DOT1X_1.3.6.1.4.1.2011.5.25.40.4.2.1 hwSrvcfgEapMaxUserAlarm.....................................................................9412.2 DOT1X_1.3.6.1.4.1.2011.5.25.171.2.1 hwMacAuthenMaxUserAlarm....................................................................94

13 DS.................................................................................................................................................9613.1 DS_1.3.6.1.4.1.2011.5.25.191.3.1 hwCfgChgNotify.................................................................................................97

14 ECM..............................................................................................................................................9814.1 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.9 hwStackLogicStackPortLinkErr.................................................................9914.2 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.10 hwStackPhyStackPortLinkErr................................................................10014.3 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.11 hwPhyStackPortIsDown.........................................................................10114.4 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.14 hwStackPortConfigureFailed..................................................................101



vii

15 EFM............................................................................................................................................10315.1 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.4 hwDot3ahEfmThresholdEvent....................................................................10415.2 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5 hwDot3ahEfmNonThresholdEvent.............................................................10615.3 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.8 hwDot3ahEfmRemoteDyingGaspEvent.....................................................10815.4 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.17 hwDot3ahEfmNonThresholdRecovery.....................................................11015.5 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.29 hwDot3ahEfmLoopbackFailed.................................................................111

16 ENTITYTRAP...........................................................................................................................11316.1 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.5 hwBoardInvalid 132626..............................................................11616.2 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132121...................................................................11716.3 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132124...................................................................11816.4 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132127...................................................................11916.5 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132128...................................................................12016.6 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132131...................................................................12116.7 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132137...................................................................12216.8 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132145...................................................................12316.9 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132146...................................................................12416.10 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132147.................................................................12516.11 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132121....................................................12716.12 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132124....................................................12816.13 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132127....................................................12916.14 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132128....................................................13016.15 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132131....................................................13116.16 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132137....................................................13216.17 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132145....................................................13316.18 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132146....................................................13416.19 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132147....................................................13516.20 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135190....................................................................13616.21 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135191....................................................................13716.22 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135192....................................................................13816.23 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135190.......................................................13916.24 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135191.......................................................14016.25 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135192.......................................................14116.26 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135193....................................................................14316.27 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135193.......................................................14416.28 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid 135450-135458.................................................14516.29 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid 135459..............................................................14616.30 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume 135450-135458....................................14816.31 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume 135459.................................................14916.32 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.9.1 hwCommunicateError 135457...................................................15016.33 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.9.2 hwCommunicateResume 135457..............................................15216.34 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.13 hwBrdTempAlarm 140544...................................................153



viii

16.35 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.13 hwBrdTempAlarm 140545...................................................15516.36 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.14 hwBrdTempResume 140544................................................15616.37 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.14 hwBrdTempResume 140545................................................15716.38 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5 hwOpticalInvalid 136192..........................................................15816.39 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5 hwOpticalInvalid 136193..........................................................16016.40 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5 hwOpticalInvalid 136194..........................................................16116.41 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5 hwOpticalInvalid 136195..........................................................16216.42 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5 hwOpticalInvalid 136196..........................................................16316.43 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.6 hwOpticalInvalidResume 136193.............................................16416.44 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.6 hwOpticalInvalidResume 136194.............................................16516.45 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.6 hwOpticalInvalidResume 136195.............................................16616.46 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.6 hwOpticalInvalidResume 136196.............................................16716.47 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.1 hwPowerRemove 136448.........................................................16816.48 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.2 hwPowerInsert 136448.............................................................17016.49 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.5 hwPowerInvalid 136961...........................................................17116.50 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.5 hwPowerInvalid 136966...........................................................17216.51 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.5 hwPowerInvalid 136972...........................................................17316.52 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.5 hwPowerInvalid 136973...........................................................17416.53 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume 136961..............................................17516.54 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume 136966..............................................17616.55 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume 136972..............................................17716.56 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume 136973..............................................17816.57 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.1 hwFanRemove 137216.............................................................17916.58 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.2 hwFanInsert 137216..................................................................18016.59 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.5 hwFanInvalid 139264...............................................................18116.60 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.6 hwFanInvalidResume 139264..................................................18216.61 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.1 hwCardRemove.........................................................................18316.62 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.2 hwCardInsert.............................................................................18416.63 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid...........................................................................18516.64 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume..............................................................18616.65 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.1 hwCPUUtilizationRising........................................................18716.66 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.2 hwCPUUtilizationResume......................................................18816.67 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.15.1 hwMemUtilizationRising........................................................19016.68 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.15.2 hwMemUtilizationResume.....................................................191

17 ENTMIB.................................................................................................................................... 19317.1 ENTMIB_1.3.6.1.2.1.47.2.0.1 entConfigChange.....................................................................................................194

18 EOAM1AG................................................................................................................................19518.1 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.1 hwDot1agCfmFaultAlarm...............................................................19618.2 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.32 hwDot1agCfmUnexpectedMEGLevel...........................................20118.3 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.33 hwDot1agCfmUnexpectedMEGLevelCleared..............................20218.4 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.34 hwDot1agCfmMismerge................................................................203



ix

18.5 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.35 hwDot1agCfmMismergeCleared...................................................20418.6 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.36 hwDot1agCfmUnexpectedMEP.....................................................20518.7 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.37 hwDot1agCfmUnexpectedMEPCleared........................................20718.8 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.38 hwDot1agCfmUnexpectedPeriod..................................................20818.9 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.39 hwDot1agCfmUnexpectedPeriodCleared......................................20918.10 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.40 hwDot1agCfmUnexpectedMAC..................................................21018.11 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.41 hwDot1agCfmUnexpectedMACCleared.....................................21218.12 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.42 hwDot1agCfmLOC......................................................................21318.13 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.43 hwDot1agCfmLOCCleared.........................................................21418.14 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.44 hwDot1agCfmExceptionalMACStatus........................................21518.15 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.45 hwDot1agCfmExceptionalMACStatusCleared...........................21718.16 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.46 hwDot1agCfmRDI.......................................................................21818.17 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.47 hwDot1agCfmRDICleared...........................................................220

19 EOAM_Y1731............................................................................................................................22219.1 EOAMY_1731_1.3.6.1.4.1.2011.5.25.136.1.6.23 hwCfmVlanOnewayDelay........................................................22319.2 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.24 hwCfmVlanOnewayDelayRecovery.........................................22419.3 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.25 hwCfmVlanTwowayDelay.......................................................22519.4 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.26 hwCfmVlanTwowayDelayRecovery........................................22719.5 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.30 hwY1731AisDefectAlarm........................................................22819.6 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.31 hwY1731AisDefectAlarmRecovery.........................................229

20 EZOP..........................................................................................................................................23120.1 EZOP_1.3.6.1.4.1.2011.2.25.311.6.2.1_hwEasyOperationClientAdded.................................................................23220.2 EZOP_1.3.6.1.4.1.2011.2.25.311.6.2.2_hwEasyOperationClientLost.....................................................................233

21 ETRUNK....................................................................................................................................23421.1 ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.1 hwETrunkStatusChange.........................................................................23521.2 ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.2 hwETrunkMemberStatusChange...........................................................237

22 FM...............................................................................................................................................24022.1 FM_1.3.6.1.4.1.2011.5.25.180.2.1 hwAlarmTargetHostDel....................................................................................24122.2 FM_1.3.6.1.4.1.2011.5.25.180.2.2 hwAlarmStorm..................................................................................................241

23 ERRORDOWN.........................................................................................................................24323.1 ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.1 hwErrordown......................................................................................24423.2 ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.2 hwErrordownRecovery......................................................................245

24 FSP..............................................................................................................................................24724.1 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.1 hwStackLinkUp..........................................................................................24824.2 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.2 hwStackLinkDown.....................................................................................24924.3 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.3 hwStackStandbyChange.............................................................................25024.4 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.4 hwStackSwitchOver....................................................................................25124.5 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.5 hwStackSystemRestart................................................................................25224.6 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.6 hwStackStackMemberAdd.........................................................................254



x

24.7 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.7 hwStackStackMemberLeave.......................................................................25424.8 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.8 hwStackSystemMacChange........................................................................256

25 HWCM.......................................................................................................................................25825.1 HWCM_1.3.6.1.4.1.2011.6.10.2.1 hwCfgManEventLog........................................................................................25925.2 HWCM_1.3.6.1.4.1.2011.6.10.2.5 hwCfgB2STransferFail.....................................................................................25925.3 HWCM_1.3.6.1.4.1.2011.6.10.2.6 hwCfgB2SOperate............................................................................................261

26 IFNET.........................................................................................................................................26226.1 IFNET_1.3.6.1.4.1.2011.5.25.41.4.1 hwIfMonitorCrcErrorRising..........................................................................26326.2 IFNET_1.3.6.1.4.1.2011.5.25.41.4.2 hwIfMonitorCrcErrorResume.......................................................................26426.3 IFNET_1.3.6.1.4.1.2011.5.25.41.4.5 hwIfMonitorInputRateRising........................................................................26526.4 IFNET_1.3.6.1.4.1.2011.5.25.41.4.6 hwIfMonitorInputRateResume......................................................................26626.5 IFNET_1.3.6.1.4.1.2011.5.25.41.4.7 hwIfMonitorOutputRateRising.....................................................................26726.6 IFNET_1.3.6.1.4.1.2011.5.25.41.4.8 hwIfMonitorOutputRateResume...................................................................26926.7 IFNET_1.3.6.1.6.3.1.1.5.3 linkDown.......................................................................................................................27026.8 IFNET_1.3.6.1.6.3.1.1.5.4 linkUp............................................................................................................................27126.9 IFNET_1.3.6.1.4.1.2011.5.25.41.4.9 hwIfMonitorHalfduplexRising......................................................................27326.10 IFNET_1.3.6.1.4.1.2011.5.25.41.3.5 hwIfFlowDown...........................................................................................27326.11 IFNET_1.3.6.1.4.1.2011.5.25.41.3.6 hwIfFlowUp................................................................................................27526.12 IFNET_1.3.6.1.4.1.2011.5.25.41.3.7_hwIfNameChange.......................................................................................27626.13 IFNET_1.3.6.1.4.1.2011.5.25.41.3.8 hwIfNameChangeResume...........................................................................27726.14 IFNET_1.3.6.1.4.1.2011.5.25.41.3.26 hwEntityExtCfmOverSlot.........................................................................27826.15 IFNET_1.3.6.1.4.1.2011.5.25.41.3.27 hwEntityExtCfmOverCard........................................................................27926.16 IFNET_1.3.6.1.4.1.2011.5.25.41.3.33 hwExtInterfaceDelete................................................................................280

27 IPv6.............................................................................................................................................28227.1 IPv6_1.3.6.1.2.1.55.2.0.1 ipv6IfStateChange...........................................................................................................283

28 IFPDT.........................................................................................................................................28628.1 IFPDT_1.3.6.1.4.1.2011.5.25.219.2.12.3_hwPortNoSupportOETrap.....................................................................287

29 ISIS.............................................................................................................................................28929.1 ISIS_1.3.6.1.3.37.2.0.1 isisDatabaseOverload.........................................................................................................29129.2 ISIS_1.3.6.1.3.37.2.0.2 isisManualAddressDrops....................................................................................................29229.3 ISIS_1.3.6.1.3.37.2.0.3 isisCorruptedLSPDetected.................................................................................................29429.4 ISIS_1.3.6.1.3.37.2.0.4 isisAttemptToExceedMaxSequence...................................................................................29529.5 ISIS_1.3.6.1.3.37.2.0.5 isisIDLenMismatch............................................................................................................29729.6 ISIS_1.3.6.1.3.37.2.0.6 isisMaxAreaAddressesMismatch.......................................................................................29929.7 ISIS_1.3.6.1.3.37.2.0.7 isisOwnLSPPurge...............................................................................................................30229.8 ISIS_1.3.6.1.3.37.2.0.8 isisSequenceNumberSkip...................................................................................................30329.9 ISIS_1.3.6.1.3.37.2.0.9 isisAuthenticationTypeFailure...........................................................................................30529.10 ISIS_1.3.6.1.3.37.2.0.10 isisAuthenticationFailure................................................................................................30829.11 ISIS_1.3.6.1.3.37.2.0.11 isisVersionSkew.............................................................................................................311



xi

29.12 ISIS_1.3.6.1.3.37.2.0.12 isisAreaMismatch...........................................................................................................31329.13 ISIS_1.3.6.1.3.37.2.0.13 isisRejectedAdjacency....................................................................................................31529.14 ISIS_1.3.6.1.3.37.2.0.14 isisLSPTooLargeToPropagate........................................................................................31829.15 ISIS_1.3.6.1.3.37.2.0.15 isisOrigLSPBuffSizeMismatch......................................................................................32029.16 ISIS_1.3.6.1.3.37.2.0.16 isisProtocolsSupportedMismatch...................................................................................32229.17 ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange.....................................................................................................32429.18 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.1 hwIsisSystemIdConflict...............................................................................32829.19 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.2 hwIsisL1ImportRouteExceedLimit..............................................................33029.20 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.3 hwIsisL1ImportRouteRestoreToLimit.........................................................33129.21 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.4 hwIsisL2ImportRouteExceedLimit..............................................................33329.22 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.5 hwIsisL2ImportRouteRestoreToLimit.........................................................33429.23 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.6 hwIsisL1ImportRouteThresholdReach.........................................................33529.24 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.7 hwIsisL1ImportRouteThresholdReachClear................................................33729.25 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.8 hwIsisL2ImportRouteThresholdReach.........................................................33829.26 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.9 hwIsisL2ImportRouteThresholdReachClear................................................34029.27 ISIS-STD_1.3.6.1.2.1.138.0.1 isisDatabaseOverload............................................................................................34129.28 ISIS-STD_1.3.6.1.2.1.138.0.2 isisManualAddressDrops.......................................................................................34329.29 ISIS-STD_1.3.6.1.2.1.138.0.3 isisCorruptedLSPDetected.....................................................................................34429.30 ISIS-STD_1.3.6.1.2.1.138.0.4 isisAttemptToExceedMaxSequence......................................................................34629.31 ISIS-STD_1.3.6.1.2.1.138.0.5 isisIDLenMismatch...............................................................................................34729.32 ISIS-STD_1.3.6.1.2.1.138.0.6 isisMaxAreaAddressesMismatch..........................................................................34929.33 ISIS-STD_1.3.6.1.2.1.138.0.7 isisOwnLSPPurge..................................................................................................35129.34 ISIS-STD_1.3.6.1.2.1.138.0.8 isisSequenceNumberSkip......................................................................................35329.35 ISIS-STD_1.3.6.1.2.1.138.0.9 isisAuthenticationTypeFailure...............................................................................35429.36 ISIS-STD_1.3.6.1.2.1.138.0.10 isisAuthenticationFailure.....................................................................................35729.37 ISIS-STD_1.3.6.1.2.1.138.0.11 isisVersionSkew..................................................................................................35929.38 ISIS-STD_1.3.6.1.2.1.138.0.12 isisAreaMismatch................................................................................................36129.39 ISIS-STD_1.3.6.1.2.1.138.0.13 isisRejectedAdjacency.........................................................................................36229.40 ISIS-STD_1.3.6.1.2.1.138.0.14 isisLSPTooLargeToPropagate.............................................................................36529.41 ISIS-STD_1.3.6.1.2.1.138.0.15 isisOrigLSPBuffSizeMismatch...........................................................................36729.42 ISIS-STD_1.3.6.1.2.1.138.0.16 isisProtocolsSupportedMismatch........................................................................36829.43 ISIS-STD_1.3.6.1.2.1.138.0.17 isisAdjacencyChange...........................................................................................37029.44 ISIS-STD_1.3.6.1.2.1.138.0.18 isisLSPErrorDetected..........................................................................................372

30 LACP..........................................................................................................................................37430.1 LACP_1.3.6.1.4.1.2011.5.25.41.3.2 hwLacpNegotiateFailed..................................................................................37530.2 LACP_1.3.6.1.4.1.2011.5.25.41.3.3 hwLacpTotalLinkLoss....................................................................................37630.3 LACP_1.3.6.1.4.1.2011.5.25.41.3.4 hwLacpPartialLinkLoss..................................................................................37830.4 LACP_1.3.6.1.4.1.2011.5.25.41.3.13 hwLacpNegotiateResume.............................................................................38030.5 LACP_1.3.6.1.4.1.2011.5.25.41.3.14 hwLacpTotalLinkLossResume.....................................................................38130.6 LACP_1.3.6.1.4.1.2011.5.25.41.3.15 hwLacpPartialLinkLossResume...................................................................382

31 LINE...........................................................................................................................................384



xii

31.1 LINE_1.3.6.1.4.1.2011.5.25.207.2.1 hwVtyNumExceed........................................................................................38531.2 LINE_1.3.6.1.4.1.2011.5.25.207.2.2 hwUserLogin.................................................................................................38531.3 LINE_1.3.6.1.4.1.2011.5.25.207.2.3 hwUserLoginFail...........................................................................................38631.4 LINE_1.3.6.1.4.1.2011.5.25.207.2.4 hwUserLogout...............................................................................................388

32 LSPV...........................................................................................................................................39032.1 LSPV_1.3.6.1.4.1.2011.5.25.302.3.1 hwLspPingProbe...........................................................................................39132.2 LSPV_1.3.6.1.4.1.2011.5.25.302.3.2 hwLspTraceProbe.........................................................................................392

33 L2BPTNL...................................................................................................................................39333.1 L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.15 hwL2ProtocolTunnelDropThresholdRaising..................................39433.2 L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.16 hwL2ProtocolTunnelDropThresholdFalling...................................395

34 L2IFPPI......................................................................................................................................39734.1 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.6 hwPortSecRcvInsecurePktAlarm..........................................................39834.2 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.9 hwPortStickyReachMaxAlarm.............................................................39934.3 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.10 hwRecIllegalMacPktAlarm................................................................40034.4 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.11 hwMacLimitOverThresholdAlarm.....................................................40134.5 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.1 hwMflpIfBlock.........................................................................................40234.6 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.2 hwMflpIfResume......................................................................................40434.7 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.7 hwMflpVlanAlarm....................................................................................40534.8 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.9 hwMflpMacAddrAlarm............................................................................40634.9 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.10 hwMflpMacAddrResume.......................................................................40834.10 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.11 hwMflpQuitVlanAlarm........................................................................40934.11 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.12 hwMflpQuitVlanResume......................................................................41134.12 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.1 hwMacTrapAlarm...................................................................................41234.13 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.2 hwPortVlanSecureMacAlarm.................................................................41334.14 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.3 hwSlotMacUsageRaisingThreshold........................................................41434.15 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.4 hwSlotMacUsageFallingThreshold........................................................415

35 L2V..............................................................................................................................................41735.1 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.7 hwVplsVcDeleted........................................................................................41935.2 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown...........................................................................................42035.3 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp................................................................................................42235.4 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.8 hwVplsVcStatusChange...............................................................................42335.5 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.6 hwVplsVsiDeleted.......................................................................................42535.6 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown..........................................................................................42635.7 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp...............................................................................................42835.8 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.5 hwVplsVcBackup.........................................................................................42935.9 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.1 hwKompellaVcDown...................................................................................43135.10 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.2 hwKompellaVcUp......................................................................................43335.11 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.3 hwKompellaSwitchWtoP...........................................................................43435.12 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.4 hwKompellaSwitchPtoW...........................................................................43635.13 L2V_1.3.6.1.4.1.2011.5.25.119.3.2.1 hwCCCVcDown.........................................................................................437



xiii

35.14 L2V_1.3.6.1.4.1.2011.5.25.119.3.2.2 hwCCCVcUp.............................................................................................43935.15 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.1 hwPWVcSwitchWtoP.............................................................................44035.16 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.2 hwPWVcSwitchPtoW.............................................................................44235.17 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.5 hwPWVcDeleted.....................................................................................44435.18 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown........................................................................................44635.19 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp............................................................................................45035.20 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.6 hwPWVcBackup.....................................................................................45235.21 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.3 hwSvcDown............................................................................................45435.22 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.4 hwSvcUp.................................................................................................45635.23 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.5 hwSvcDeleted..........................................................................................458

36 L3MB..........................................................................................................................................46036.1 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.5 hwBoardL3FwdResLack..........................................................................46136.2 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.6 hwBoardL3FwdResLackResume.............................................................46336.3 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.7 hwBoardL3ACLResLack.........................................................................46436.4 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.8 hwBoardL2mcResLack.............................................................................46536.5 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.9 hwBoardL2mcResLackResume................................................................46636.6 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.10 hwBoardipmcResLack............................................................................46736.7 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.11 hwBoardipmcResLackResume...............................................................468

37 L3VPN........................................................................................................................................47037.1 L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp.............................................................................................47137.2 L3VPN_1.3.6.1.2.1.10.166.11.0.2 mplsL3VpnVrfDown........................................................................................47237.3 L3VPN_1.3.6.1.2.1.10.166.11.0.3 mplsL3VpnVrfRouteMidThreshExceeded.......................................................47437.4 L3VPN_1.3.6.1.2.1.10.166.11.0.4 mplsL3VpnVrfNumVrfRouteMaxThreshExceeded.........................................47637.5 L3VPN_1.3.6.1.2.1.10.166.11.0.6 mplsL3VpnNumVrfRouteMaxThreshCleared..................................................47837.6 L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent................................................................................479

38 LDP.............................................................................................................................................48138.1 LDP_1.3.6.1.2.1.10.166.4.0.1 mplsLdpInitSessionThresholdExceeded..................................................................48238.2 LDP_1.3.6.1.2.1.10.166.4.0.2 mplsLdpPathVectorLimitMismatch.........................................................................48338.3 LDP_1.3.6.1.2.1.10.166.4.0.3 mplsLdpSessionUp..................................................................................................48438.4 LDP_1.3.6.1.2.1.10.166.4.0.4 mplsLdpSessionDown.............................................................................................485

39 LSPM..........................................................................................................................................49039.1 LSPM_1.3.6.1.2.1.10.166.2.0.1 mplsXCUp.............................................................................................................49239.2 LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown........................................................................................................49339.3 LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp.......................................................................................................49439.4 LSPM_1.3.6.1.2.1.10.166.3.0.2 mplsTunnelDown..................................................................................................49639.5 LSPM_1.3.6.1.2.1.10.166.3.0.3 mplsTunnelRerouted.............................................................................................49939.6 LSPM_1.3.6.1.2.1.10.166.3.0.4 mplsTunnelReoptimized.......................................................................................50039.7 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.1 hwMplsStaticLSPUp.................................................................................50139.8 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLSPDown............................................................................50239.9 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.3 hwMplsStaticCRLSPUp...........................................................................504



xiv

39.10 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.4 hwMplsStaticCRLSPDown.....................................................................50639.11 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.5 hwMplsTeFrrProtAval............................................................................50839.12 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.6 hwMplsTeFrrProtNotAval......................................................................50939.13 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.7 hwMplsTeFrrSwitch...............................................................................51039.14 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.8 hwMplsTeFrrResume..............................................................................51239.15 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.9 hwMplsTunnelHSBSwitch.....................................................................51339.16 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.10 hwMplsTunnelHSBResume..................................................................51639.17 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.11 hwMplsTunnelOBSwitch......................................................................51739.18 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.12 hwMplsTunnelOBResume....................................................................51939.19 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.15 hwMplsTunnelChangeBw.....................................................................52039.20 LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.1 hwMplsLdpVirtualTunnelUp................................................................52139.21 LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.2 hwMplsLdpVirtualTunnelDown...........................................................52239.22 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.46 hwMplsTunnelPrimaryUp.....................................................................52339.23 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryDown................................................................52439.24 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp...............................................................52839.25 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.49 hwMplsTunnelHotstandbyDown..........................................................52939.26 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp...................................................................53239.27 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.51 hwMplsTunnelOrdinaryDown..............................................................53339.28 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52 hwMplsTunnelBesteffortUp.................................................................53739.29 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.53 hwMplsTunnelBesteffortDown.............................................................53839.30 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.54 hwMplsTeAutoTunnelDownClear........................................................54139.31 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.55 hwMplsTeAutoTunnelPrimaryDownClear...........................................54239.32 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.56 hwMplsTunnelBBSwitch......................................................................54339.33 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.57 hwMplsTunnelBBResume....................................................................54639.34 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.58 hwMplsExtTunnelDown.......................................................................54739.35 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59 hwMplsExtTunnelDownClear..............................................................55039.36 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.62 hwMplsTunnelDelete............................................................................55139.37 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.63 hwMplsLspThresholdExceed................................................................55339.38 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.64 hwMplsLspThresholdExceedClear.......................................................55439.39 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.65 hwMplsLspTotalCountExceed..............................................................55539.40 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.66 hwMplsLspTotalCountExceedClear.....................................................55639.41 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.67 hwMplsDynamicLabelThresholdExceed..............................................55739.42 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.68 hwMplsDynamicLabelThresholdExceedClear.....................................55839.43 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.69 hwMplsDynamicLabelTotalCountExceed............................................56039.44 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70 hwMplsDynamicLabelTotalCountExceedClear...................................561

40 LBDT..........................................................................................................................................56340.1 LBDT_1.3.6.1.4.1.2011.5.25.174.3.3 hwLdtPortLoopDetect..................................................................................56440.2 LBDT_1.3.6.1.4.1.2011.5.25.174.3.4 hwLdtPortLoopDetectRecovery..................................................................565

41 LLDP..........................................................................................................................................56741.1 LLDP_1.0.8802.1.1.2.0.0.1 lldpRemTablesChange.................................................................................................56841.2 LLDP_1.3.6.1.4.1.2011.5.25.134.2.1 hwLldpEnabled.............................................................................................569



xv

41.3 LLDP_1.3.6.1.4.1.2011.5.25.134.2.2 hwLldpDisabled............................................................................................57041.4 LLDP_1.3.6.1.4.1.2011.5.25.134.2.5 hwLldpLocManIPAddrChange....................................................................571

42 MCAST......................................................................................................................................57342.1 MCAST/3/TRAP......................................................................................................................................................574

43 MID_L2BPTNL........................................................................................................................57643.1 MID_L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.15 hwL2ProtocolTunnelDropThresholdRaising........................57743.2 MID_L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.16 hwL2ProtocolTunnelDropThresholdFalling.........................578

44 MONITOR................................................................................................................................58044.1 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.8 CARDABNORMAL...........................................................................58144.2 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.9 CARDNORMAL................................................................................58144.3 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.10 INPUTLINEABNORMAL...............................................................58244.4 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.11 INPUTLINENORMAL....................................................................583

45 MSTP..........................................................................................................................................58545.1 MSTP_1.3.6.1.2.1.17.0.1 NEWRT...........................................................................................................................58645.2 MSTP_1.3.6.1.2.1.17.0.2 TOPOC............................................................................................................................58745.3 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.1 hwMstpiPortStateForwarding.....................................................................58945.4 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.2 hwMstpiPortStateDiscarding......................................................................59145.5 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.3 hwMstpiBridgeLostRootPrimary................................................................59245.6 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.4 hwMstpiPortRootGuarded..........................................................................59445.7 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.5 hwMstpiPortBpduGuarded.........................................................................59645.8 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.6 hwMstpiPortLoopGuarded..........................................................................59745.9 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.7 hwMstpiEdgePortChanged.........................................................................59945.10 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.15 hwMstpiTcGuarded.................................................................................60045.11 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.16 hwMstpProTcGuarded............................................................................60245.12 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.17 hwMstpProRootChanged........................................................................60445.13 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.18 hwMstpProNewPortStateForwarding.....................................................60645.14 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.19 hwMstpProNewPortStateDiscarding......................................................60745.15 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.20 hwMstpProNewBridgeLostRootPrimary................................................60945.16 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.21 hwMstpProNewPortRootGuarded..........................................................61145.17 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.22 hwMstpProNewPortBpduGuarded.........................................................61345.18 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.23 hwMstpProNewPortLoopGuarded..........................................................61545.19 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.24 hwMstpProNewEdgePortChanged.........................................................61745.20 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.25 hwMstpProLoopbackDetected................................................................618

46 NAP............................................................................................................................................62146.1 NAP_1.3.6.1.4.1.2011.5.25.206.3.1 hwNapStatusNotify........................................................................................622

47 NQA...........................................................................................................................................62347.1 NQA_1.3.6.1.2.1.80.0.1 pingProbeFailed................................................................................................................62547.2 NQA_1.3.6.1.2.1.80.0.2 pingTestFailed...................................................................................................................62647.3 NQA_1.3.6.1.2.1.80.0.3 pingTestCompleted...........................................................................................................628



xvi

47.4 NQA_1.3.6.1.2.1.81.0.2 traceRouteTestFailed........................................................................................................62947.5 NQA_1.3.6.1.2.1.81.0.3 traceRouteTestCompleted.................................................................................................63047.6 NQA_1.3.6.1.4.1.2011.5.25.111.6.1 nqaResultsProbeFailed...................................................................................63147.7 NQA_1.3.6.1.4.1.2011.5.25.111.6.2 nqaResultsTestFailed.....................................................................................63347.8 NQA_1.3.6.1.4.1.2011.5.25.111.6.3 nqaResultsTestCompleted..............................................................................63447.9 NQA_1.3.6.1.4.1.2011.5.25.111.6.4 nqaResultsThresholdNotification..................................................................63547.10 NQA_1.3.6.1.4.1.2011.5.25.111.6.5 nqaHTTPStatsProbeFailed...........................................................................63747.11 NQA_1.3.6.1.4.1.2011.5.25.111.6.6 nqaHTTPStatsTestFailed.............................................................................63947.12 NQA_1.3.6.1.4.1.2011.5.25.111.6.7 nqaHTTPStatsTestCompleted......................................................................64147.13 NQA_1.3.6.1.4.1.2011.5.25.111.6.8 nqaHTTPStatsThresholdNotification..........................................................64247.14 NQA_1.3.6.1.4.1.2011.5.25.111.6.10 nqaJitterStatsTestFailed.............................................................................64347.15 NQA_1.3.6.1.4.1.2011.5.25.111.6.11 nqaJitterStatsTestCompleted......................................................................64547.16 NQA_1.3.6.1.4.1.2011.5.25.111.6.12 nqaFTPStatsProbeFailed............................................................................64647.17 NQA_1.3.6.1.4.1.2011.5.25.111.6.13 nqaFTPStatsTestFailed..............................................................................64847.18 NQA_1.3.6.1.4.1.2011.5.25.111.6.14 nqaFTPStatsTestCompleted.......................................................................65147.19 NQA_1.3.6.1.4.1.2011.5.25.111.6.15 nqaFTPStatsThresholdNotification............................................................65247.20 NQA_1.3.6.1.4.1.2011.5.25.111.6.25 nqaJitterStatsJitterThresholdNotificationSD.............................................65347.21 NQA_1.3.6.1.4.1.2011.5.25.111.6.26 nqaJitterStatsJitterThresholdNotificationDS.............................................65447.22 NQA_1.3.6.1.4.1.2011.5.25.111.6.16 nqaJitterStatsRTDThresholdNotification..................................................65547.23 NQA_1.3.6.1.4.1.2011.5.25.111.6.17 nqaJitterStatsOWDThresholdNotificationSD............................................65647.24 NQA_1.3.6.1.4.1.2011.5.25.111.6.18 nqaJitterStatsOWDThresholdNotificationDS............................................658

48 OSPF...........................................................................................................................................66048.1 OSPF_1.3.6.1.2.1.14.16.2.1 ospfVirtIfStateChange................................................................................................66248.2 OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange...................................................................................................66348.3 OSPF_1.3.6.1.2.1.14.16.2.3 ospfVirtNbrStateChange.............................................................................................66748.4 OSPF_1.3.6.1.2.1.14.16.2.4 ospfIfConfigError........................................................................................................67048.5 OSPF_1.3.6.1.2.1.14.16.2.5 ospfVirtIfConfigError.................................................................................................67248.6 OSPF_1.3.6.1.2.1.14.16.2.6 ospfIfAuthFailure........................................................................................................67448.7 OSPF_1.3.6.1.2.1.14.16.2.7 ospfVirtIfAuthFailure.................................................................................................67648.8 OSPF_1.3.6.1.2.1.14.16.2.8 ospfIfRxBadPacket.....................................................................................................67848.9 OSPF_1.3.6.1.2.1.14.16.2.9 ospfVirtIfRxBadPacket...............................................................................................68048.10 OSPF_1.3.6.1.2.1.14.16.2.10 ospfTxRetransmit....................................................................................................68148.11 OSPF_1.3.6.1.2.1.14.16.2.11 ospfVirtIfTxRetransmit...........................................................................................68448.12 OSPF_1.3.6.1.2.1.14.16.2.12 ospfOriginateLsa.....................................................................................................68648.13 OSPF_1.3.6.1.2.1.14.16.2.13 ospfMaxAgeLsa......................................................................................................68848.14 OSPF_1.3.6.1.2.1.14.16.2.14 ospfLsdbOverflow..................................................................................................69048.15 OSPF_1.3.6.1.2.1.14.16.2.15 ospfLsdbApproachingOverflow..............................................................................69148.16 OSPF_1.3.6.1.2.1.14.16.2.16 ospfIfStateChange...................................................................................................69348.17 OSPF_1.3.6.1.2.1.14.16.2.17 ospfNSSATranslatorStatusChange.........................................................................69548.18 OSPF_1.3.6.1.2.1.14.16.2.18 ospfRestartStatusChange........................................................................................69848.19 OSPF_1.3.6.1.2.1.14.16.2.19 ospfNbrRestartHelperStatusChange.......................................................................699



xvii

48.20 OSPF_1.3.6.1.2.1.14.16.2.20 ospfVirtNbrRestartHelperStatusChange.................................................................70148.21 OSPF_1.3.6.1.4.1.2011.5.25.155.31.3 hwOspfv2IntraAreaRouteridConflict........................................................70348.22 OSPF_1.3.6.1.4.1.2011.5.25.155.31.4 hwOspfv2IntraAreaDRIpAddressConflict................................................704

49 OSPFV3......................................................................................................................................70749.1 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.1 hwOspfv3VirtIfStateChange....................................................................70849.2 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.2 hwOspfv3NbrStateChange.......................................................................71049.3 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.3 hwOspfv3VirtNbrStateChange................................................................71249.4 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.4 hwOspfv3IfConfigError...........................................................................71549.5 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.5 hwOspfv3VirtIfConfigError....................................................................71849.6 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.6 hwOspfv3IfRxBadPacket.........................................................................72049.7 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.7 hwOspfv3VirtIfRxBadPacket..................................................................72249.8 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.8 hwOspfv3IfStateChange..........................................................................72349.9 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.9 hwOspfv3RestartStatusChange................................................................72649.10 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.10 hwOspfv3NbrRestartHelperStatusChange...........................................72749.11 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.11 hwOspfv3VirtNbrRestartHelperStatusChange....................................72949.12 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.12 hwOspfv3NssaTranslatorStatusChange...............................................73149.13 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.13 hwOspfv3LastAuthKeyExpiry.............................................................73449.14 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.14 hwOspfv3AuthSequenceNumWrap.....................................................735

50 PoE..............................................................................................................................................73750.1 POE_1.3.6.1.4.1.2011.5.25.195.40.2 hwPoePowerOff............................................................................................73850.2 POE_1.3.6.1.4.1.2011.5.25.195.40.3 hwPoePowerOn.............................................................................................74050.3 POE_1.3.6.1.4.1.2011.5.25.195.40.8 hwPoePdConnected......................................................................................74050.4 POE_1.3.6.1.4.1.2011.5.25.195.40.9 hwPoePdDisconnected..................................................................................74150.5 POE_1.3.6.1.4.1.2011.5.25.195.40.10 hwPoePdClassInvalid..................................................................................74250.6 POE_1.3.6.1.4.1.2011.5.25.195.40.11 hwPoePdClassOvercurrent..........................................................................74350.7 POE_1.3.6.1.4.1.2011.5.25.195.40.16 hwPoePdPriorityDifferent...........................................................................74550.8 POE_1.3.6.1.4.1.2011.5.25.195.40.17 hwPoePowerOverUtilizationThreshold......................................................74650.9 POE_1.3.6.1.4.1.2011.5.25.195.40.18 hwPoePowerOverUtilizationThresholdResume.........................................74750.10 POE_1.3.6.1.4.1.2011.5.25.195.40.20 hwPoePowerAbsent..................................................................................74850.11 POE_1.3.6.1.4.1.2011.5.25.195.40.21 hwPoePowerAbsentResume.....................................................................74950.12 POE_1.3.6.1.4.1.2011.5.25.195.40.22 hwPoeRpsPowerOutputAlarm..................................................................74950.13 POE_1.3.6.1.4.1.2011.5.25.195.40.23 hwPoeRpsPowerOutputAlarmResume.....................................................750

51 Portal..........................................................................................................................................75251.1 WEB_1.3.6.1.4.1.2011.5.4.2.2.1.1 hwPortalServerUp.............................................................................................75351.2 WEB_1.3.6.1.4.1.2011.5.4.2.2.1.2 hwPortalServerDown........................................................................................75451.3 WEB 1.3.6.1.4.1.2011.5.4.2.2.1.3 hwPortalMaxUserAlarm....................................................................................75551.4 WEB 1.3.6.1.4.1.2011.5.4.2.2.1.4 hwPortalUserClearAlarm..................................................................................756

52 RDS............................................................................................................................................75852.1 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.1 hwRadiusAuthServerUp.........................................................................75952.2 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.2 hwRadiusAuthServerDown....................................................................759



xviii

52.3 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.3 hwRadiusAcctServerUp..........................................................................76052.4 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.4 hwRadiusAcctServerDown.....................................................................761

53 RMON........................................................................................................................................76353.1 RMON_1.3.6.1.2.1.16.0.1 risingAlarm....................................................................................................................76453.2 RMON_1.3.6.1.2.1.16.0.2 fallingAlarm...................................................................................................................76553.3 RMON_1.3.6.1.4.1.2011.1.3.4.0.1 pririsingAlarm..................................................................................................76653.4 RMON_1.3.6.1.4.1.2011.1.3.4.0.2 prifallingAlarm.................................................................................................767

54 RRPP..........................................................................................................................................76954.1 RRPP_1.3.6.1.4.1.2011.5.25.113.4.1 hwRrppRingRecover....................................................................................77054.2 RRPP_1.3.6.1.4.1.2011.5.25.113.4.2 hwRrppRingFail............................................................................................77154.3 RRPP_1.3.6.1.4.1.2011.5.25.113.4.3 hwRrppMultiMaster......................................................................................77254.4 RRPP_1.3.6.1.4.1.2011.5.25.113.4.4 hwRrppTrackInterfaceDown........................................................................77354.5 RRPP_1.3.6.1.4.1.2011.5.25.113.4.5 hwRrppTrackInterfaceUp.............................................................................774

55 RSVP..........................................................................................................................................77655.1 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.1 hwRsvpTeHelloLost.............................................................................77755.2 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.2 hwRsvpTeHelloLostRecovery..............................................................77855.3 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.3 hwRsvpTeAuthFail...............................................................................77955.4 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.4 hwRsvpTeAuthSuccess........................................................................780

56 SECE...........................................................................................................................................78256.1 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.1 hwStrackUserInfo...................................................................................78456.2 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.2 hwStrackIfVlanInfo................................................................................78556.3 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.3 hwStrackDenyPacket..............................................................................78656.4 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.4 hwStrackErrorDown...............................................................................78856.5 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.1 hwARPSGatewayConflict......................................................................78956.6 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.2 hwARPSEntryCheck..............................................................................79056.7 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.3 hwARPSPacketCheck.............................................................................79156.8 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.4 hwARPSDaiDropALarm........................................................................79256.9 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.5 hwARPGlobleSpeedLimitALarm...........................................................79356.10 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.6 hwARPIfSpeedLimitALarm.................................................................79456.11 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.7 hwARPVlanSpeedLimitALarm............................................................79556.12 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.13 hwArpIfRateLimitBlockALarm.........................................................79656.13 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.8 hwARPMissGlobleSpeedLimitALarm.................................................79756.14 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.9 hwARPMissIfSpeedLimitALarm.........................................................79856.15 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.10 hwARPMissVlanSpeedLimitALarm..................................................79956.16 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.11 hwARPSIPSpeedLimitALarm............................................................80056.17 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.12 hwARPMissSIPSpeedLimitALarm....................................................80156.18 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.3.1 hwIPSGDropALarm.............................................................................80256.19 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.4.1 hwICMPGlobleDropALarm.................................................................80356.20 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.4.2 hwICMPIfDropALarm.........................................................................80456.21 SECE_1.3.6.1.4.1.2011.5.25.32.4.1.14.1 hwXQoSStormControlTrap..................................................................805



xix

57 SNMP.........................................................................................................................................80757.1 SNMP_1.3.6.1.6.3.1.1.5.1 coldStart.........................................................................................................................80857.2 SNMP_1.3.6.1.6.3.1.1.5.2 warmStart.......................................................................................................................80857.3 SNMP_1.3.6.1.6.3.1.1.5.5 authenticationFailure.....................................................................................................809

58 SOCKET....................................................................................................................................81158.1 SOCKET_1.3.6.1.4.1.2011.5.25.34.2.1 hwTCPMD5AuthenFail............................................................................812

59 SRM............................................................................................................................................81459.1 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.13 hwEntityOffline.........................................................................................81659.2 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.14 hwEntityOnline.........................................................................................81759.3 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.1 hwTempRisingAlarm..................................................................................81859.4 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.2 hwTempRisingResume...............................................................................82059.5 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.3 hwTempFallingAlarm.................................................................................82259.6 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.4 hwTempFallingResume..............................................................................82359.7 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.11 hwPortPhysicalEthHalfDuplexAlarm.......................................................82559.8 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.12 hwPortPhysicalEthFullDuplexClear.........................................................82659.9 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.13 hwPortPhysicalPortTypeChange...............................................................82859.10 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67590..............................................................................82959.11 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67591..............................................................................83059.12 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67861..............................................................................83159.13 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67958..............................................................................83359.14 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67960..............................................................................83459.15 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67961..............................................................................83659.16 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67962..............................................................................83759.17 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67963..............................................................................83859.18 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67964..............................................................................83959.19 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67966..............................................................................84159.20 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67967..............................................................................84259.21 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67968..............................................................................84359.22 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68072..............................................................................84559.23 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68073..............................................................................84659.24 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68074..............................................................................84759.25 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68080..............................................................................84859.26 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68081..............................................................................85059.27 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68082..............................................................................85159.28 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68083..............................................................................85259.29 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68084..............................................................................85359.30 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67590..........................................................................85559.31 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67591..........................................................................85659.32 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67958..........................................................................85759.33 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67960..........................................................................858



xx

59.34 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67961..........................................................................85959.35 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67962..........................................................................86159.36 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67963..........................................................................86259.37 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67964..........................................................................86359.38 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67966..........................................................................86459.39 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67967..........................................................................86659.40 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67968..........................................................................86759.41 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 68072..........................................................................86859.42 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 68073..........................................................................87059.43 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 68080..........................................................................87159.44 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 68082..........................................................................87259.45 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 68081..........................................................................87359.46 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 68074..........................................................................87459.47 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 68084..........................................................................87559.48 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.14 hwPortPhysicalAutoNegotiateFail..........................................................87759.49 SRM_1.3.6.1.4.1.2011.5.25.129.2.17.1 hwOpticalPowerAbnormal......................................................................87859.50 SRM_1.3.6.1.4.1.2011.5.25.129.2.17.2 hwOpticalPowerResume.........................................................................87959.51 SRM_1.3.6.1.4.1.2011.5.25.31.7.2.1 NETWORKHEARTBEATTRAP...............................................................881

60 SYSMIB.....................................................................................................................................88260.1 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.1 hwSysClockChangedNotification..............................................................88360.2 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.2 hwSysReloadNotification..........................................................................88360.3 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.1 hwPatchErrorTrap...................................................................................88460.4 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.2 hwPatchActiveOverTimeTrap................................................................88560.5 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.3 hwPatchMalfunctionComebackTrap......................................................88760.6 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.8 hwSysSlaveSwitchSuccessNotification.....................................................88760.7 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.9 hwSysSlaveSwitchFailNotification...........................................................88860.8 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.10 hwSysIssuNotification.............................................................................88960.9 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.14 hwSysCfgFileErrorNotification...............................................................89160.10 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.15 hwSysImageErrorNotification...............................................................892

61 TRUNK......................................................................................................................................89461.1 TRUNK_1.3.6.1.4.1.2011.5.25.41.3.9 hwExtLinkDown.........................................................................................89561.2 TRUNK_1.3.6.1.4.1.2011.5.25.41.3.10 hwExtLinkUp............................................................................................896

62 TUNNEL....................................................................................................................................89862.1 TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.1 hwMplsPsSwitchPtoW............................................................................89962.2 TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.2 hwMplsPsSwitchWtoP............................................................................901

63 UCM...........................................................................................................................................90463.1 UCM_1.3.6.1.4.1.2011.5.25.307.2.3 hwVpVmAuthenticateFail.............................................................................90563.2 UCM_1.3.6.1.4.1.2011.5.25.307.2.4 hwVpVmDeliverAuthorInformationFail.......................................................906

64 VFS.............................................................................................................................................908



xxi

64.1 VFS_1.3.6.1.4.1.2011.6.9.1.3.1 hwFlhOperNotification.........................................................................................90964.2 VFS_1.3.6.1.4.1.2011.6.9.1.3.2 hwFlhSyncSuccessNotification.............................................................................90964.3 VFS_1.3.6.1.4.1.2011.6.9.1.3.3 hwFlhSyncFailNotification...................................................................................910

65 VRRP..........................................................................................................................................91365.1 vrrp_1.3.6.1.2.1.68.0.1 vrrpTrapNewMaster............................................................................................................91465.2 vrrp_1.3.6.1.2.1.68.0.2 vrrpTrapAuthFailure...........................................................................................................91665.3 VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.1 hwVrrpExtTrapMasterDown..................................................................91765.4 VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.2 hwVrrpExtTrapNonMaster.....................................................................919

66 Appendix...................................................................................................................................92266.1 BGP Error Code........................................................................................................................................................923



xxii

1 Locating Alarms

An alarm is generated when a fault occurs or the environment in which it is kept, fails to meetthe requirements for its normal operation. The alarm messages vary with fault categories, faultfunctionality, or modules where the faults occur.

You can find the specific alarms by the following ways:l Use the Network Management System (NMS).l Run the display trapbuffer [ size value ] command. Alarms will be displayed in the alarm

buffer.The maximum number of alarms that can be displayed in the alarm buffer is determinedby value. If the number of alarms is less than the value specified by value, the actual numberof alarms will be displayed.

The following tips can help you to find the specific alarms quickly.

l "Alarm ID" , uniquely identifies a alarm, which is first recommended for you to search fora alarm.If different alarms have the same ID, you can use error values, such as Base Trap ProbableCause, to search for alarms.

l This manual does not support searching with variable information, such as generation time,interface number, process ID, and device name.

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 1 Locating Alarms


1

2 Introduction

About This Chapter

An alarm is generated when a fault occurs or when the system does not operate properly. Thesystem generates alarms when the environment in which it is kept, fails to meet the requirementsfor its normal operation. The alarm messages vary with fault categories, fault functionality, ormodules where the faults occur. Alarm messages are not only logged by the system but also aresaved in the alarm cache. The size of the alarm cache is configurable.

Alarm messages are sent to the network management system (NMS), if any, through the SimpleNetwork Management Protocol (SNMP). The terminal display function outputs the alarmmessages to the terminal screen and also saves them in the cache. Alarm messages in the cachecan also be displayed through the command line interface (CLI).

Alarms are classified into the following three categories:

l Fault alarm: indicates that a fault occurs to the device hardware or that the device cannotperform certain important functions normally.

l Recovery alarm: indicates that the fault has been removed or the device has becomeoperational.

l Event alarm: indicates that an event happens.

2.1 Alarm Message Format Description

2.2 Alarm Functionality Description

2.3 Alarm Information Description

2.4 Alarm Severity Description

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 2 Introduction


2

2.1 Alarm Message Format Description

Format of Alarm MessageThe alarm message begins with "#". Figure 2-1 shows the output format of an alarm message.

Figure 2-1 Output format of an alarm message

Fields

Field Description

# Information type: # indicates the alarminformation.

TimeStamp It is the time when a alarm message isgenerated. It is a variable of the date type andexpressed in the format Mmm dd hh:mm:ssyyyy.l Mmm indicates a month. It can be Jan,

Feb, Mar, Apr, May, Jun, Jul, Aug, Sep,Oct, Nov, or Dec.

l dd indicates a date of a month. If the valueis less than 10, it is expressed as "(blank)date". For example, " 7".

l hh:mm:ss indicates the local time. hhranges from 00 to 23. mm or ss rangesfrom 00 to 59.

l yyyy indicates a year.TimeStamp and HostName are separated bya space.

HostName It is the system name of a local host.HostName and ModuleName are separatedby a space.

ModuleName It specifies the module that generates alarmmessages. ModuleName and Severity areseparated by a slash (/).



3

Field Description

Severity Alarm messages are classified into sixseverity levels.Severity and Brief are separated by a slash(/).

Brief It is a phrase that summarizes information.There should be a colon (:) between the Brieffield and the Description field.

Description It is a string of characters that describe adetailed alarm message. It is output by amodule to the information center. It is filledin by a module at each output time.

2.2 Alarm Functionality DescriptionIn terms of functionality, alarm messages are classified into the five types described in followingtable.

Type Description

Communication alarm Indicates that a fault occurs to the processassociated with the data transfer. Forexample, an alarm is generated due to thecommunication failure between the NEs,between the NE and the OS, or between theOSs.

QoS alarm Indicates that the QoS decreases. Forexample, an alarm is generated due tocongestion, performance decrease, highresource occupancy, or bandwidth shortage.

Error alarm during data handling Indicates that an error occurs when thesoftware or process handles data. Forexample, an alarm is generated due to thesoftware error, memory overflow, versionmismatch, or abortion of the program.

Environment alarm Indicates that the environment cannot meetthe requirements for the equipment to operatenormally. For example, an alarm is generateddue to improper temperature, humidity, orventilation.

Equipment alarm Indicates that a fault occurs to physicalresources, including power supply, fan,processor, clock, and I/O interfaces



4

2.3 Alarm Information Description

Description

Two parts are included:

l Alarm message: indicates the character string that describes the alarm. It is displayed on adevice.

l Alarm meaning: indicates the meaning of the alarm.

Attribute

Three parts are included:

l OID: indicates the object ID defined in the MIB.

l Alarm severity: indicates to what extent the fault affects the performance of the device.

l Alarm functionality: indicates the function that the fault is related to.

Parameters

Indicates the parameters included in the alarm. Parameters in an alarm help in locating the faultand analyzing the alarm.

Impact on System

Analyzes the impact of this trap on system .

Possible Causes

This part describes the causes for an alarm generated by the system.

Handling Procedure

This part diagnoses the fault and provides suggestions for system recovery.

Related Information

This part describes associated alarms to help in finding out the root cause for the alarm and thecauses for the associated alarms.

2.4 Alarm Severity DescriptionThe severity level indicates the seriousness of a fault. The severity levels can be classified intoCritical, Major, Minor, Warning, Indeterminate, and Cleared.



5

Level Severity Description

1 Critical Indicates that the fault affectsnormal operation of thesystem. Effective measuresshould be taken immediately.For example, a fault causesthe unavailability of a deviceor resources. Recover thesystem immediately even ifthe fault occurs during non-working hours.

2 Major Indicates that the faultdecreases the systemperformance. Effectivemeasures should be takenimmediately. For example,the performance of a deviceor resources decreasessignificantly. Recover thesystem immediately duringworking hours.

3 Minor Indicates that a fault occursbut does not decrease thesystem performance. Toprevent the fault fromcausing a more serious one,observe the fault and removeit at a proper time.

4 Warning Indicates that an error mayoccur and affect the systemperformance. The measuresto be taken vary with thesituation or the error.

5 Indeterminate Indicates that the severitylevel cannot be determined.This means that the severitylevel is determined by thereal-world situation.



6

Level Severity Description

6 Cleared The Cleared severity levelindicates the clearing of oneor more previously reportedalarms. This alarm clears allalarms for this managedobject that have the sameAlarm type, Probable causeand Specific problems.Multiple associatednotifications may be clearedby using the Correlatednotifications parameter .



7

3 ACL

About This Chapter

3.1 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.1 hwAclResThresholdExceedClearTrap

3.2 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.2 hwAclResThresholdExceedTrap

3.3 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.3 hwAclResTotalCountExceedClearTrap

3.4 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.4 hwAclResTotalCountExceedTrap

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 3 ACL


8

3.1 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.1hwAclResThresholdExceedClearTrap

Description

ACL/4/ACL_RULERESLACKRESUME_TRAP:OID [OID] The rule resource usage isrestored to be lower than [INTEGER]%.(Slot=[OCTET], Stage=[OCTET])

The ACL resource usage falls below the lower threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.1.2.2.1.1.4.1 Warning qualityOfServiceAlarm(3)

Parameters

Name Meaning

OID Indicates the ID of the MIB object.

INTEGER Indicates the lower threshold of ACL resource usage.

Slot Specifies the stack ID of the card where the alarm is generated.

Stage Indicates the ACL processing stage when the alarm is generated.

Impact on the System

None

Possible Causes

The ACL resource usage falls below the lower threshold.

Procedure

Step 1 This alarm is informational only, and no action is required.

----End

Related Information

None



9

3.2 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.2hwAclResThresholdExceedTrap

Description

ACL/4/ACL_RULERESLACK_TRAP:OID [OID] The rule resource usage has exceeded[INTEGER]%.(Slot=[OCTET], Stage=[OCTET])

The ACL resource usage reaches the upper threshold.

Attribute



Parameters

Name Meaning


INTEGER Indicates the upper threshold of ACL resource usage.




None

Possible Causes

The ACL resource usage reaches the upper limit.

Procedure


----End

Related Information

None



10

3.3 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.3hwAclResTotalCountExceedClearTrap

Description

ACL/4/ACL_RULERESFULLRESUME_TRAP:OID [OID] The rule resource usage isrestored to be lower than [INTEGER]%.(Slot=[OCTET], Stage=[OCTET])

The ACL resource usage decreases from 100% and keeps below 100% for a period.

Attribute



Parameters

Name Meaning


INTEGER The value is fixed as 100%.




None

Possible Causes

The ACL resource usage decreases from 100% and keeps below 100% for a period.

Procedure


----End

Related Information

None



11

3.4 ACL_1.3.6.1.4.1.2011.5.1.2.2.1.1.4.4hwAclResTotalCountExceedTrap

Description

ACL/4/ACL_RULERESFULL_TRAP:OID [OID] The rule resource usage has reached[INTEGER]%.(Slot=[OCTET], Stage=[OCTET])

The ACL resource usage reaches 100%.

Attribute



Parameters

Name Meaning


INTEGER The value is fixed as 100%.




None

Possible Causes

The ACL resource usage reaches 100%.

Procedure


----End

Related Information

None



12

4 ARP

About This Chapter

4.1 ARP_1.3.6.1.4.1.2011.5.25.123.2.1 hwEthernetARPSpeedLimitAlarm

4.2 ARP_1.3.6.1.4.1.2011.5.25.123.2.4 hwEthernetARPThresholdExceedAlarm

4.3 ARP_1.3.6.1.4.1.2011.5.25.123.2.5 hwEthernetARPThresholdResumeAlarm

4.4 ARP_1.3.6.1.4.1.2011.5.25.123.2.6 hwEthernetARPIPConflictEvent

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 4 ARP


13

4.1 ARP_1.3.6.1.4.1.2011.5.25.123.2.1hwEthernetARPSpeedLimitAlarm

Description

ARP/4/ARP_SUPP_TRAP:OID [OID] Exceed the speed limit value configured. (Ifnet index=[INTEGER], Configured value=[COUNTER], Sampling value=[COUNTER], Speed-limittype=[OCTET],Source Ip address=[IPADDR], Destination Ip address=[IPADDR], VPN-Instance name=[OCTET]).

The trap was generated when the transmitting rate of ARP packets or ARP Miss Messages wasgreater than the rate limit.

You can run the arp speed-limit command to set the rate limit. The default rate limit is 500 bit/s.

Attribute


1.3.6.1.4.1.2011.5.25.123.2.1 Warning processingErrorAlarm(4)

Parameters

Name Meaning

OID Indicates the trap ID.

Ifnet index Indicates the interface index.

Configured value Indicates the configured rate limit.

Sampling value Indicates the sampling of the number of packets received within aperiod.

Speed-limit type Indicates the type of packets configured with timestamp suppression,for example, ARP and ARP Miss.

Source Ip address Indicates source IP addresses.

Destination Ip address Indicates the destination IP address.

VPN-Instance name Indicates the VPN instance name.



14


View the type of packets configured with timestamp suppression in trap messages.

If ARP packets are configured with timestamp suppression, it indicates that some normal ARPpackets are discarded. As a result, traffic cannot be forwarded normally.

If ARP Miss messages are configured with timestamp suppression, it indicates that some ARPMiss messages are discarded. As a result, ARP Request messages cannot be triggered and thustraffic cannot be forwarded normally.

If this trap is cleared shortly, services will not be affected and the system will resume the normaloperation.

If this trap is not cleared for a long time, the service processing capability of the system will beaffected.

Possible Causes

1:

The interval for enabling the log function and sending traps for potential attack behaviors wasset to Ns. Within the period of N+1s, the number of sent ARP packets was greater than thethreshold. Within the first Ns, the average number of sent ARP packets was greater than thethrehold.

2:

The interval for enabling the log function and sending traps for potential attack behaviors wasset to Ns. Within the period of N+1s, the number of sent ARP Miss messages was greater thanthe threshold. Within the first Ns, the average number of sent ARP Miss messages was greaterthan the threhold.

Procedure

l To locate and address the fault, do as follows:

1. View the type of packets configured with timestamp suppression in trap messages.

(1) If the type of packets is ARP, go to Step 2.

(2) If the type of packets is ARP Miss, go to Step 4.

2. Run the display arp_anti-attack configuration command to view the rate limit of ARPpackets on each board.

3. Run the arp speed-limit source-ip [ ip-address ]maximum maximum command to re-set the maximum value of timestamp suppression of ARP packets. This value must begreater than that displayed in Step 2; otherwise, the trap cannot be cleared, but this valuemust be less than 32768.Then, check whether the trap is cleared.

– Y=>7.

– N=>6.

4. Run the display arp_anti-attack configuration command to view the rate limit of ARPMiss messages on each board.



15

5. Run the arp-miss speed-limit [ ip-address ]source-ip maximum maximum commandto re-set the maximum value of timestamp suppression of ARP Miss messages. This valuemust be greater than that displayed in Step 4; otherwise, the trap cannot be cleared, but thisvalue must be less than 32768.Then, check whether the trap is cleared.

– Y=>7.

– N=>6.

6. Contact Huawei technical personnel.

7. End.

----End

Related Information

None

4.2 ARP_1.3.6.1.4.1.2011.5.25.123.2.4hwEthernetARPThresholdExceedAlarm

Description

ARP/4/ARP_THRESHOLDEXCEED_TRAP:OID [OID] The number of ARP entries exceededthe threshold. (entPhysicalIndex=[INTEGER], Slot name=[OCTET], Threshold=[COUNTER],Number of dynamic ARP entries=[COUNTER], Number of static ARP entries=[COUNTER]).

The number of ARP entries exceeds the upper threshold.

Attribute


1.3.6.1.4.1.2011.5.25.123.2.4 Warning qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid Indicates the index of the alarm.

entPhysicalIndex Indicates the index of the physical entity.

Slot name Indicates the board name.

Threshold Indicates the alarm threshold.



16

Name Meaning

Number of dynamic ARP entries Indicates the number of dynamic ARP entries.

Number of static ARP entries Indicates the number of static ARP entries.


If this alarm is displayed, the number of ARP entries on the device is great. If the numbercontinuously increases, system resources become insufficient and no new ARP entries can belearned. As a result, service interruption may occur.

Possible Causes

The number of ARP entries on the device exceeded the upper threshold.

Procedure

Step 1 Run the display arp statistics command to view ARP entry statistics on the device and checkwhether there are more static ARP entries or dynamic ARP entries.

l If there are more dynamic ARP entries, go to Step 2.

l If there are more static ARP entries, go to Step 3.

Step 2 Run the display arp all command to identify the interface that has more ARP entries. Then runthe display arp interface command to check ARP entries on the interface and determine whetherthese ARP entries are necessary for the interface.

l If these ARP entries are necessary, go to Step 6.

l If these ARP entries are not necessary, run the reset arp command to delete certain ARPentries (without system running being affected) and go to Step 4.

Step 3 Run the display current-configuration command to view static ARP entries and check whetherthese static ARP entries are necessary.

l If these static ARP entries are necessary, go to Step 6.

l If these static ARP entries are not necessary,run the undo arp static command to deletecertain static ARP entries (without system running being affected) or run the reset arpstatic command to clear all static ARP entries. Then go to Step 4.

Step 4 Run the display arp statistics command to check whether the number of ARP entries stillcontinuously increases unexpectedly.

l If the number of ARP entries does not continuously increase unexpectedly, go to Step 6.

l If the number of ARP entries still continuously increases unexpectedly, go to Step 5.

Step 5 Collect the alarm information, log information, and configuration information, and contactHuawei technical support engineers.

Step 6 End.

----End



17

Related Information

None

4.3 ARP_1.3.6.1.4.1.2011.5.25.123.2.5hwEthernetARPThresholdResumeAlarm

Description

ARP/4/ARP_THRESHOLDRESUME_TRAP:OID [OID] The number of ARP entries wasrestored to the threshold. (entPhysicalIndex=[INTEGER], Slot name=[OCTET], Threshold=[COUNTER], Number of dynamic ARP entries=[COUNTER], Number of static ARP entries=[COUNTER]).

The number of ARP entries falls below the upper threshold.

Attribute



Parameters

Name Meaning

oid Indicates the index of the alarm.

entPhysicalIndex Indicates the index of the physical entity.

Slot name Indicates the board name.

Threshold Indicates the alarm threshold.

Number of dynamic ARP entries Indicates the number of dynamic ARP entries.

Number of static ARP entries Indicates the number of static ARP entries.


None

Possible Causes

The number of ARP entries on the device fell below the upper threshold.



18

Procedure

Step 1 This alarm message is informational only, and no action is required.

----End

Related Information

None

4.4 ARP_1.3.6.1.4.1.2011.5.25.123.2.6hwEthernetARPIPConflictEvent

Description

ARP/4/ARP_IPCONFLICT_TRAP:OID [OID] ARP detects IP conflict. (IP address=[IPADDR], Local interface=[OCTET], Local MAC=[OCTET], Local vlan=[INTEGER], LocalCE vlan=[INTEGER], Receive interface=[OCTET], Receive MAC=[OCTET], Receive vlan=[INTEGER], Receive CE vlan=[INTEGER], IP conflict type=[OCTET]).

An IP address conflict is detected by ARP.

Attribute


1.3.6.1.4.1.2011.5.25.123.2.6 Warning environmentalAlarm(6)

Parameters

Name Meaning

OID Index of the alarm

IP address IP address

Local interface Interface recorded in the ARP entry of the IP address

Local MAC Source MAC address recorded in the ARP entry of the IP address

Local vlan VLAN recorded in the ARP entry of the IP address

Local CE vlan CEVLAN recorded in the ARP entry of the IP address

Receive interface Inbound interface of the second ARP packet with the IP address



19

Name Meaning

Receive MAC Source MAC address of the second ARP packet with the IP address

Receive vlan VLAN configured on the inbound interface of the second ARP packet withthe IP address

Receive CE vlan CEVLAN configured on the inbound interface of the second ARP packetwith the IP address

IP conflict type IP address conflict type

Impact on the SystemThis alarm indicates that an IP address conflict occurred. If the IP address conflict is noteliminated timely, route flapping may occur and services may be interrupted.

Possible Causesl Cause 1: The source IP address in an ARP packet is the same as the IP address of the inbound

interface that receives the ARP packet, but the source MAC address in the ARP packet isdifferent than the MAC address of the inbound interface.

l Cause 2: The source IP address in an ARP packet is the same as the IP address in an existingARP entry, but the source MAC address is different than the MAC address in the ARPentry.

Procedure

Step 1 Identify the devices or users that use the same IP address.l If the devices or users using the same IP address can be identified, modify the IP address of

one device or user. Then, go to step 2.l If the devices or users using the same IP address cannot be identified, collect the alarm

information, log information, and configuration information, and contact Huawei technicalsupport personnel.

Step 2 Run the display arp ip-conflict track command to check whether there is any IP address conflictinformation, or check whether there is any alarm generated for IP address conflict.l If there is any IP address conflict, go to step 1.l If there is no IP address conflict, go to step 3.

Step 3 End.

----End



20

5 BASETRAP

About This Chapter

5.1 BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.19_hwEntityDyingGasp

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 5 BASETRAP


21

5.1BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.19_hwEntityDyingGasp

DescriptionNOTE

Only the S5700LI, S5700S-LI, S5700HI and S5710HI support this alarm.

BASETRAP/1/ENTITYDYINGGASP:OID [OID] Dying Gasp event is occurred.(MacAddress=\"[OCTET]\", ReasonCode=\"[INTEGER]\", ReasonDescription=\"[OCTET]\")

The device is powered off.

Attribute


1.3.6.1.4.1.2011.5.25.129.2.1.19 Critical equipmentAlarm(5)

Parameters

Name Meaning

[oid] Indicates the ID of the MIB object.

MacAddress Indicates the MAC address of the device.

ReasonCode Indicates the code of the alarm cause.

ReasonDescription Indicates the description of the alarm cause.

Impact on the SystemServices on the device are interrupted.

Possible CausesThe power cable is loose.

The external power cable is faulty.

The power supply unit is faulty.



22

Procedure

Step 1 Check whether the power cable is loose or faulty. If so, properly connect the power cable andpower on the device. If not, check whether the power supply unit is faulty. If so, replace thepower supply unit.

----End



23

6 BFD

About This Chapter

6.1 BFD_1.3.6.1.4.1.2011.5.25.38.3.1 hwBfdSessDown

6.2 BFD_1.3.6.1.4.1.2011.5.25.38.3.2 hwBfdSessUp

6.3 BFD_1.3.6.1.4.1.2011.5.25.38.3.3 hwBfdSessReachLimit

6.4 BFD_1.3.6.1.4.1.2011.5.25.38.3.4 hwBfdSessReachLimitBindIf

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 6 BFD


24

6.1 BFD_1.3.6.1.4.1.2011.5.25.38.3.1 hwBfdSessDown

DescriptionBFD/2/BFD_DOWN_TRAP:OID [oid] Session changes to DOWN. (Index=[integer],ConfigurationName=[octet], PeerIp=[ipaddr], BindIfIndex=[integer], BindIfName=[octet],Diagnosis=[integer], BindVrfIndex=[integer], BindVpnName=[octet], SessionType=[integer],DefaultIp=[integer], BindType=[integer], StaticLspName=[octet], PwSecondary=[integer],NextHop=[ipaddr], VcId=[integer], VsiName=[octet], VsiPeerAddress=[ipaddr], DiscrAuto=[integer], PeerIpv6=[ipv6addr], Ipv6NextHop=[ipv6addr])

The trap was generated when the BFD session changed from another state to the Down state.

The statuses of the BFD session include: Up, Init, Down, and AdmDown.

Attribute


1.3.6.1.4.1.2011.5.25.38.3.1 Major qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid Indicates the ID of the MIB object.

Index Indicates the index of the BFD session.

ConfigurationName Indicates the configuration name of the BFD session.

PeerIP Indicates the bound destination IP address.

BindIfIndex Indicates the index of the bound interface.

BindIfName Indicates the name of the bound interface.

Diagnosis Indicates information about session diagnostic characters.

BindVrfIndex Indicates the index of the bound VPN.

BindVpnName Indicates the name of the bound VPN.



25

Name Meaning

SessionType Indicates the type of the BFD session.l 1: Static, indicates the statically configured BFD session.l 2: Dynamic, indicates the dynamically established BFD session.l 3: Entire_Dynamic, indicates that the establishment of a BFD session

is triggered entirely dynamically. This type of BFD session is createdonly after the function of passively creating BFD sessions is enabledon the egress switch of the LSP.

l 4: Static_Auto, indicates the static BFD session that is establishedwith automatically negotiated discriminators.

DefaultIP Indicates the default multicast IP address.

BindType Indicates the binding type.l 2 or 3: Peer Ip Address, detects the multi-hop IP link.l 1 or 4: Interface, detects the single-hop IP link.l 10: STATIC_LSP, detects the static LSP.l 9: LDP_LSP, detects the LDP LSP.l 11: TE_LSP, detects the LSP bound to the TE tunnel.l 12: TE_TUNNEL, detects the TE tunnel.l 13: PW, detects the PW.l 15: VSI_PW, detects the VSI PW.

StaticLspName Indicates the name of the static LSP.

PwSecondary Indicates the ID of the secondary PW.

NextHop Indicates the IP address of the next hop.

VcId Indicates the ID of the VC.

VsiName Indicates the name of the VSI.

VsiPeerAddress Indicates the destination address of the VSI.

DiscrAuto Indicates the static auto-negotiation identifier.

PeerIpv6 Indicates the bound destination IPv6 address.

Ipv6NextHop Indicates the next-hop IPv6 address.

Impact on the SystemIf a large number BFD session states flap that results in high CPU utilization rate. Except forthis, no service will be affected.

Possible CausesCause 1:

The session-bound interface goes down.

Cause 2:



26

The peer BFD session is deleted or shut down.

Cause 3:

The link went Down or was congested. Consequently, it failed to forward packets.

Procedure

Step 1 Run the display interface command to check whether the physical status of the interface wherethe session resides is Up.

l If so, go to Step 2.

l If not, go to Step 6.

Step 2 Check whether a message reporting alarm recovery is received.



Step 3 Run the display bfd session all command to check whether the BFD sessions on the local endand on the remote end are deleted.



Step 4 Run the ping ip-address command to check whether the link detected by the BFD session failsto forward packets.



Step 5 Collect configurations, trap messages, and log messages, and then contact Huawei technicalsupport personnel.

Step 6 End.

----End

Related Information

BFD_1.3.6.1.4.1.2011.5.25.38.3.2 hwBfdSessUp

6.2 BFD_1.3.6.1.4.1.2011.5.25.38.3.2 hwBfdSessUp

Description

BFD/2/BFD_UP_TRAP:OID [oid] Session changes to UP. (Index=[integer],ConfigurationName=[octet], PeerIp=[ipaddr], BindIfIndex=[integer], BindIfName=[octet],Diagnosis=[integer], BindVrfIndex=[integer], BindVpnName=[octet], SessionType=[integer],DefaultIp=[integer], BindType=[integer], StaticLspName=[octet], PwSecondary=[integer],NextHop=[ipaddr], VcId=[integer], VsiName=[octet], VsiPeerAddress=[ipaddr], DiscrAuto=[integer], PeerIpv6=[ipv6addr], Ipv6NextHop=[ipv6addr])

The trap was generated when the BFD session changed from another state to the Up state.



27

The statuses of the BFD session include: Up, Init, Down, and AdmDown.

Attribute


1.3.6.1.4.1.2011.5.25.38.3.2 Major qualityOfServiceAlarm(3)

Parameters

Name Meaning


Index Indicates the index of the BFD session.

ConfigurationName Indicates the configuration name of the BFD session.

PeerIP Indicates the bound destination IP address.

BindIfIndex Indicates the index of the bound interface.

BindIfName Indicates the name of the bound interface.

Diagnosis Indicates information about the session diagnostic characters.

BindVrfIndex Indicates the index of the bound VPN.

BindVpnName Indicates the name of the bound VPN.

SessionType Indicates the type of the BFD session.l 1: Static, indicates the statically configured BFD session.l 2: Dynamic, indicates the dynamically established BFD session.l 3: Entire_Dynamic, indicates that the establishment of a BFD session

is triggered entirely dynamically. This type of BFD session is createdonly after the function of passively creating BFD sessions is enabledon the egress switch of the LSP.

l 4: Static_Auto, indicates the static BFD session that is establishedwith automatically negotiated discriminators.

DefaultIP Indicates the default multicast IP address.

BindType Indicates the binding type.l 2 or 3: Peer Ip Address, detects the multi-hop IP link.l 1 or 4: Interface, detects the single-hop IP link.l 10: STATIC_LSP, detects the static LSP.l 9: LDP_LSP, detects the LDP LSP.l 11: TE_LSP, detects the LSP bound to the TE tunnel.l 12: TE_TUNNEL, detects the TE tunnel.l 13: PW, detects the PW.l 15: VSI_PW, detects the VSI PW.



28

Name Meaning

StaticLspName Indicates the name of the static LSP.

PwSecondary Indicates the ID of the secondary PW.

NextHop Indicates the IP address of the next hop.

VcId Indicates the ID of the VC.

VsiName Indicates the name of the VSI.

VsiPeerAddress Indicates the destination address of the VSI.

DiscrAuto Indicates the static auto-negotiation identifier.

PeerIpv6 Indicates the bound destination IPv6 address.

Ipv6NextHop Indicates the next-hop IPv6 address.

Impact on the SystemAfter the trap function is enabled, if a large number of BFD sessions flap, high CPU will beutilized. Except for this, no service will be affected.


A BFD session was created. That is, the BFD session changed from Init to Up.

Cause 2:

The undo shutdown command was run to restore the BFD session. That is, the BFD sessionchanged from AdmDown to Up.

Cause 3:

The BFD session changed from Down to Up.

Procedure


----End

Related InformationBFD_1.3.6.1.4.1.2011.5.25.38.3.1 hwBfdSessDown

6.3 BFD_1.3.6.1.4.1.2011.5.25.38.3.3 hwBfdSessReachLimit

DescriptionBFD/4/BFD_SESSLMT_TRAP:OID [oid] The session number in all the IO boards has reachedthe limit, the new session can not be created. (TotalSessionLimit=[integer])



29

The trap was generated when the number of all the BFD sessions set up on interface boardsreached the PAF upper limit and no more session can be set up.

You can run the display bfd statistics command to view information aboutBFD_SESSION_NUM and know the upper limit.

Attribute


1.3.6.1.4.1.2011.5.25.38.3.3 Warning qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid indicates the ID of the MIB object.

TotalSessionLimit indicates the upper limit of global BFD sessions.


Services will not be affected.

Possible Causes

New BFD configurations were still committed when the number of global BFD sessions reachedthe upper limit

Procedure

Step 1 Run the display bfd statistics command to check whether the BFD_SESSION_NUM hasreached the upper limmit.



Step 2 Delete the useless BFD session, and then the BFD session about committed configuration willbe set up automatically=>4.


Step 4 End.

----End

Related Information

None



30

6.4 BFD_1.3.6.1.4.1.2011.5.25.38.3.4hwBfdSessReachLimitBindIf

DescriptionBFD/4/BFD_IFSESSLMT_TRAP:OID [oid] Try to build session, but the session number in theIO board with interface has reached the limit, the new session binding with interface can not becreated. (ConfigurationName=[octet], InterfaceName=[octet], SessionLimitPerBoard=[integer])

The trap was generated when the number of BFD sessions bound to the interface on the interfaceboard reached the PAF upper limit and no more BFD session bound to the interface can be setup.

You can run the display bfd statistics command to view the value of BFD_IO_SESSION_NUMcorresponding to the upper limit.

Attribute


1.3.6.1.4.1.2011.5.25.38.3.4 Warning qualityOfServiceAlarm (3)

Parameters

Name Meaning


ConfigurationName indicates the configuration name.

InterfaceName indicates the interface name.

SessionLimitPerBoard indicates the allowable maximum number of BFD sessions on eachboard.

Impact on the SystemServices will not be affected.

Possible CausesNew BFD sessions bound to the interface were still set up when the number of BFD sessionsbound to the interface have reached the upper limit.

Procedure

Step 1 Run the display bfd statistics command to check whether the BFD_IO_SESSION_NUM onthe board has reached the upper limmit.



31

l If so, go to Step2.l If not, go to Step3.

Step 2 Delete the useless BFD session which bound to this interface, and then the BFD session aboutcommitted configuration will be set up automatically=>4.


Step 4 End.

----End

Related InformationNone



32

7 BGP

About This Chapter

7.1 BGP_1.3.6.1.2.1.15.7.1 bgpEstablished

7.2 BGP_1.3.6.1.2.1.15.7.2 bgpBackwardTransition

7.3 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.1 hwBgpPeerRouteNumThresholdExceed

7.4 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.2 hwBgpPeerRouteNumThresholdClear

7.5 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.3 hwBgpPeerGRStatusChange

7.6 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished

7.7 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.10 hwBgpPeerBackwardTransition

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 7 BGP


33

7.1 BGP_1.3.6.1.2.1.15.7.1 bgpEstablished

DescriptionBGP/2/ESTABLISHED:OID [oid] The BGP FSM enters the Established state.(BgpPeerRemoteAddr=[BgpPeerRemoteAddrValue], BgpPeerLastError=[BgpPeerLastErrorValue], BgpPeerState=[BgpPeerStateValue])

Indicates that this trap was generated when the BGP FSM was in the Established state.

Attribute


1.3.6.1.2.1.15.7.1 Major communicationsAlarm(2)

Parameters

Name Meaning


BgpPeerRemoteAddr Indicates the address of the peer.

BgpPeerLastError Indicates the error code of the BGP Notification when the neighborrelationship is disconnected for the last time.

The value is expressed in the format of [ErrorCode][ErrorSubCode].[ErrorCode] refers to the error code and [ErrorSubCode] refers to theerror subcode. Take the integer 35 as an example, figure 3 is the errorcode and figure 5 is the error subcode. For detailed information aboutthe error code, refer to 66.1 BGP Error Code.

If the value is 0, it indicates that no error occurs.



34

Name Meaning

BgpPeerState Indicates the status of the BGP peer.l Idle: indicates that BGP denies any request of entering. This is the

initiatory status of BGP.Upon receiving a Start event, BGP initiates a TCP connection to theremote BGP peer, starts the ConnectRetry Timer with the initialvalue, detects a TCP connection initiated by the remote BGP peer,and changes its state to Connect.

l Connect: indicates that BGP performs other actions after the TCPconnection is set up.

– If the TCP connection succeeds, BGP stops the ConnectRetryTimer, sends an Open message to the remote peer, and changesits state to OpenSent.

– If the TCP connection fails, BGP restarts the ConnectRetryTimer with the initial value, continues to detect a TCPconnection initiated by the remote peer, and changes its state toActive.

– If the ConnectRetry Timer has expired before a TCP connectionis established, BGP restarts the timer with the initial value,initiates a TCP connection to the remote BGP peer, and stays inthe Connect state.

l Active: indicates that BGP tries to set up TCP connection. This isthe intermediate status of BGP.


– If the ConnectRetry Timer has expired before a TCP connectionis established, BGP restarts the timer with the initial value andchanges its state to Connect.

– If BGP initiates a TCP connection with an unknown IP address,the TCP connection fails. When this occurs, BGP restarts theConnectRetry Timer with the initial value and stays in the Activestate.

l OpenSent: indicates that BGP has sent one Open message to its peerand waits for the other Open message from the peer.

– If there are no errors in the Open message received, BGPchanges its state to OpenConfirm.

– If there are errors in the Open message received, BGP sends aNotification message to the remote peer and changes its state toIdle.

– If the TCP connection fails, BGP restarts the ConnectRetryTimer with the initial value, continues to detect a TCPconnection initiated by the remote peer, and changes its state toActive.



35

Name Meaning

l OpenConfirm: indicates that BGP waits for a Notification messageor a Keepalive message.

– If BGP receives a Notification message, or the TCP connectionfails, BGP changes its state to Idle.

– If BGP receives a Keepalive message, BGP changes its state toEstablished.

l Established: indicates that BGP peers can exchange Update,Notification and Keepalive packets.

– If BGP receives an Update or a Keepalive message, its state staysin Established.

– If BGP receives a Notification message, BGP changes its stateto Idle.


The BGP neighbor relationship can be normally established.

Possible Causes

The BGP neighbor relationship was established.

Procedure


----End

Related Information

BGP_1.3.6.1.2.1.15.7.2 bgpBackwardTransition

7.2 BGP_1.3.6.1.2.1.15.7.2 bgpBackwardTransition

Description

BGP/2/BACKWARD:OID [oid] The BGP FSM moves from a higher numbered state to a lowernumbered state. (BgpPeerRemoteAddr=[ipaddr], InstanceId=[gauge], Afi=[integer], Safi=[integer], PeerType=[integer], PeerRemoteAddr=[binary], InterfaceIndex=[integer],BgpPeerLastError=[octet], BgpPeerState=[integer], BgpPeerUnavaiReason=[gauge],InterfaceName=[octet])

Indicates that this trap was generated when the BGP state machine moved from a highernumbered state, namely, Openconfirm or Established, to a lower numbered state.



36

Attribute



Parameters

Name Meaning


BgpPeerRemoteAddr Indicates the address of the peer.

InstanceId Indicates the index of the instance to which the peer belongs.

Afi Indicates the address family:l 1: ipv4l 2: ipv6l 25: vplsl 196: l2vpn

Safi Indicates the sub-address family:l 1: unicastl 2: multicastl 4: mplsl 65: vplsl 128: vpn

PeerType Indicates the address type of the peer:l 1: ipv4l 2: ipv6

PeerRemoteAddr Indicates the address of the peer.

InterfaceIndex Indicates the index of the interface.



37

Name Meaning

BgpPeerLastError Indicates the error code of the BGP Notification when the neighborrelationship is disconnected for the last time.

The value is expressed in the format of [ErrorCode][ErrorSubCode].[ErrorCode] refers to the error code and [ErrorSubCode] refers to theerror subcode. Take the integer 35 as an example, figure 3 is the errorcode and figure 5 is the error subcode. For detailed information aboutthe error code, refer to 66.1 BGP Error Code.




38

Name Meaning

BgpPeerState Indicates the status of the BGP peer.l Idle: indicates that BGP denies any request of entering. This is the

initiatory status of BGP.Upon receiving a Start event, BGP initiates a TCP connection tothe remote BGP peer, starts the ConnectRetry Timer with theinitial value, detects a TCP connection initiated by the remoteBGP peer, and changes its state to Connect.



– If the TCP connection fails, BGP restarts the ConnectRetryTimer with the initial value, continues to detect a TCPconnection initiated by the remote peer, and changes its stateto Active.

– If the ConnectRetry Timer has expired before a TCPconnection is established, BGP restarts the timer with theinitial value, initiates a TCP connection to the remote BGPpeer, and stays in the Connect state.

l Active: indicates that BGP tries to set up TCP connection. This isthe intermediate status of BGP.


– If the ConnectRetry Timer has expired before a TCPconnection is established, BGP restarts the timer with theinitial value and changes its state to Connect.

– If BGP initiates a TCP connection with an unknown IP address,the TCP connection fails. When this occurs, BGP restarts theConnectRetry Timer with the initial value and stays in theActive state.

l OpenSent: indicates that BGP has sent one Open message to itspeer and waits for the other Open message from the peer.

– If there are no errors in the Open message received, BGPchanges its state to OpenConfirm.

– If there are errors in the Open message received, BGP sends aNotification message to the remote peer and changes its stateto Idle.

– If the TCP connection fails, BGP restarts the ConnectRetryTimer with the initial value, continues to detect a TCPconnection initiated by the remote peer, and changes its stateto Active.



39

Name Meaning

l OpenConfirm: indicates that BGP waits for a Notificationmessage or a Keepalive message.


– If BGP receives a Keepalive message, BGP changes its stateto Established.


– If BGP receives an Update or a Keepalive message, its statestays in Established.

– If BGP receives a Notification message, BGP changes its stateto Idle.

BgpPeerUnavaiReason Indicates the reason that the BGP peer down.

InterfaceName Indicates the name of the interface.


The BGP neighbor will be disconnected, and the BGP route received from the neighbor will bedeleted. The packet forwarding based on the BGP route will fail.

Possible Causes

1. The BGP holdtimer timed out and did not receive the Keepalive packet.

2. BGP received incorrect BGP packets.

3. The BGP neighbor relationship was reset and the neighbor relationship was automaticallyinterrupted.

4. BGP received Notification packets from the neighbor.

Procedure

Step 1 Run the display bgp peer ipv4-addresses log-info command to check the check the Error fieldin the command output. You can view the Error Code and Sub Error Code in the receivedNotification in the form of [ErrorCode][ErrorSubCode].

l If the error code of the Notification is 1, it indicates that the BGP module receives the packetwith incorrect headers. Then, go to Step 23.

l If the error code of the Notification is 2, it indicates that the BGP module receives the incorrectOpen packet. Then, go to Step 23.

l If the error code of the Notification is 3, it indicates that the BGP module receives the incorrectUpdate packet. Then, go to Step 23.



40

l If the error code of the Notification is 4, it indicates that till the Holdtimer times out, the BGPmodule does not receive the Keepalive packet. Then, go to Step 4.

l If the error code of the Notification is 5, it indicates that the finite state machine of the BGPmodule is faulty. Then, go to Step 23.

l If the error code of the Notification is 6, go to Step 2.

Step 2 If the error code of the Notification is 6, it indicates that BGP automatically closes the connection.Then, you need to run the display bgp peer ipv4-address log-info command to view theNotification field and check whether the Notification is sent by the switch that generates thetrap.

l If "Send Notification" is displayed, it indicates that the local switch actively sends theNotification. Then, go to Step 3.

l If "Receive Notification" is displayed, it indicates that the local switch receives theNotification. Then, go to Step 22.

Step 3 Search for the reset bgp all and reset bgp ipv4-address commands in the logs to check whetherBGP is reset on the local end; or search for the peer ipv4-address enable command to checkwhether the peer is enabled in other address families on the local, or parameters for the BGPconnection are configured.

l If so, it indicates that incorrect configurations cause the trap, and thus no action is required.Then, go to Step 24.


Step 4 If the error code is 4, it indicates that the BGP disconnection is caused by the timeout of theHoldtimer. Then, you need to check whether the address of the BGP neighbor can be pingedsuccessfully.



Step 5 Run the display ip routing-table command to check whether the Destination/Mask field hasthe route to the peer address.



Step 6 Run the display acl all command to check whether the switch is configured with the ACL thatdisables TCP port 179.



Step 7 Run the display ip interface command to check whether the values of Physical and Protocolfields of the outbound interface are Up.



Step 8 Check the origin of the route with the BGP peer address.

l If the route is originated from OSPF, go to Step 12.

l If the route is originated from IS-IS, go to Step 13.

l Else, go to Step 23.



41

Step 9 Delete the ACL that disables the TCP port 179, and check whether the trapBGP_1.3.6.1.2.1.15.7.1 bgpEstablished appears later.l If so, go to Step 24.l If not, go to Step 10.

Step 10 Check the BGP configuration to see whether loopback interfaces are used to establish BGP peers.l If so, go to Step 14.l If not, go to Step 15.

Step 11 Enter the view of the outbound interface, and run the display this command to check whetherthe interface is shut down.l If so, run the undo shutdown command to enable the interface.l If not, go to Step 22.

Step 12 Run the display ospf peer command to check whether the OSPF peer relationship is established.l If so, go to Step 23.l If not, refer to the solution provided in the case of trap OSPF_1.3.6.1.2.1.14.16.2.2

ospfNbrStateChange.

Step 13 Run the display isis peer command to check whether the IS-IS peer relationship is established.l If so, go to Step 23.l If not, refer to the solution provided in the case of trap ISIS_1.3.6.1.3.37.2.0.13

isisRejectedAdjacency.

Step 14 Check whether the peer connect-interface is configured for specifying the source address.l If so, go to Step 15.l If not, go to Step 16.

Step 15 If BGP is the EBGP neighbor relationship and multiple hops exist between EBGP neighbors,check whether the peer ebgp-max-hop is configured.l If so, go to Step 17.l If not, go to Step 19.

Step 16 Configure the peer connect-interface command. The parameter in the command must be thelocal interface that establishes a connection with the peer. Then, check whether the trapBGP_1.3.6.1.2.1.15.7.1 bgpEstablished appears later.l If so, go to Step 24.l If not, go to Step 23.

Step 17 Check whether the peer valid-ttl-hops hops command is configured.l If so, go to Step 18.l If not, go to Step 23.

Step 18 If the peer valid-ttl-hops hops is configured, check whether the TTL of the packet to the peerranges from [255-hops+1] to 255.l If so, go to Step 23.l If not, go to Step 20.

Step 19 Configure the peer ebgp-max-hop. Then, check whether the trap BGP_1.3.6.1.2.1.15.7.1bgpEstablished appears later.



42

l If so, go to Step 24.l If not, go to Step 23.

Step 20 Changed the value of the peer valid-ttl-hops hops and make it within the range from [255-hops+1] to 255. Then, check whether the trap BGP_1.3.6.1.2.1.15.7.1 bgpEstablished appears later.l If so, go to Step 24.l If not, go to Step 23.

Step 21 Run the the display cpu-usage command to check whether the CPU usage whether the CPUusage remains 100% in a period.l If so, go to Step 23.l If not, go to Step 6.

Step 22 Contact the maintenance personnel of the peer device to check whether BGP is reset on the peerswitch, the peer is enabled in other address families on the local, and parameters for BGPconnection are configured. Then, check whether the trap BGP_1.3.6.1.2.1.15.7.1bgpEstablished appears later.l If so, go to Step 24.l If not, go to Step 23.

Step 23 Collect the trap information, log information, and configuration of the switch, and contactHuawei technical support personnel.

Step 24 End.

----End

Related InformationBGP_1.3.6.1.2.1.15.7.1 bgpEstablished

7.3 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.1hwBgpPeerRouteNumThresholdExceed

DescriptionBGP/2/ROUTETHRESHOLDEXCEED:OID [oid] The number of routes received from theBGP peer exceeded the alarm threshold. (InstanceId=[gauge], Afi=[integer], Safi=[integer],PeerType=[integer], PeerRemoteAddr=[binary], MaxRouteNum=[gauge], AlarmThreshold=[gauge])

The number of routes received from the peer configured with the route limit exceeded the alarmthreshold (MaxRouteNum x AlarmThreshold).



43

Attribute


1.3.6.1.4.1.2011.5.25.177.1.3.1 Major qualityOfServiceAlarm(3)

Parameters

Name Meaning







MaxRouteNum Indicates the maximum number of routes that can be received from the peer.

AlarmThreshold Indicates the alarm threshold (expressed in percentage) for the route limiton the peer.


l If the peer is configured with the peer route-limit command in which the alarm thresholdis set to 100% and the keyword alert-only is not specified, the peer session will beinterrupted, and all the received routes will be deleted.



44

l If the peer is configured with other parameters, no services will be affected.

Possible Causes

The number of routes received from the peer configured with the route limit exceeded the alarmthreshold.

Procedure

Step 1 Run the display bgp peer ipv4-address verbose command to view the Received total routesfield and check whether the number of routes currently received from the peer exceeds the upperlimit, which equals the maximum number of allowed routes multiplied by the alarm threshold(expressed in percentage).



Step 2 Check whether excessive routes are required to meet the requirements of actual applications.



Step 3 View the user log to check whether the local inbound policy is changed. For example, configuringthe peer route-policy, peer ip-prefix, or peer filter-policy command causes excessive andunnecessary routes to be received.



Step 4 Update the local inbound policy. For example, configure the peer route-policy, peer ip-prefix, or peer filter-policy command to deny unnecessary routes. Then, go to Step 9.

Step 5 Contact the maintenance personnel of the remote device to check whether the routes advertisedto the local device are necessary routes.



Step 6 Advise the maintenance personnel of the remote device to summarize routes so that the numberof routes to be advertised can be reduced. Then, go to Step 9.

Step 7 Advise the maintenance personnel of the remote device to change the policy for importing oradvertising routes so that the unnecessary routes can be withdrawn. Then, go to Step 9.

Step 8 Increase the maximum number of routes that can be received from the peer. Then, go to Step 9.

Step 9 Check whether the trap BGP_1.3.6.1.4.1.2011.5.25.177.1.3.2hwBgpPeerRouteNumThresholdClear appears.



Step 10 Contact Huawei technical support personnel.

Step 11 End.

----End



45

Related Information

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.2 hwBgpPeerRouteNumThresholdClear

7.4 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.2hwBgpPeerRouteNumThresholdClear

Description

BGP/2/ROUTETHRESHOLDCLEAR:OID [oid] The number of routes received from the BGPpeer decreased below the alarm threshold. (InstanceId=[gauge], Afi=[integer], Safi=[integer],PeerType=[integer], PeerRemoteAddr=[binary], MaxRouteNum=[gauge], AlarmThreshold=[gauge])

The number of routes received from the peer configured with the route limit decreased belowthe alarm threshold (MaxRouteNum x AlarmThreshold).

Attribute



Parameters

Name Meaning







46

Name Meaning



MaxRouteNum Indicates the maximum number of routes that can be received from the peer.

AlarmThreshold Indicates the alarm threshold (expressed in percentage) for the route limiton the peer.


None.

Possible Causes

The number of routes received from the peer configured with the route limit decreased belowthe alarm threshold.

Procedure


----End

Related Information

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.1 hwBgpPeerRouteNumThresholdExceed

7.5 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.3hwBgpPeerGRStatusChange

Description

BGP/3/GRSTATUSCHANGE:OID [oid] The graceful restart status of the BGP peer changed.(InstanceId=[gauge], Afi=[integer], Safi=[integer], PeerType=[integer], PeerRemoteAddr=[binary], GrStatus=[integer])

The GR status of either BGP speaker that succeeded in the GR capability negotiation changed.



47

Attribute


1.3.6.1.4.1.2011.5.25.177.1.3.3 Minor communicationsAlarm(2)

Parameters

Name Meaning







GrStatus Indicates the GR status of the peer:l 1: peerNotBeingHelpedl 2: peerRestartingl 3: peerFinishRestartl 4: peerHelping



48


l If an alarm of the type peerNotBeingHelped(1) is generated, it indicates that the local endfails to function as the GR Helper during the restart of the BGP peer. As a result, serviceswill be interrupted until the peer session is reestablished and all routes are converged.

l If an alarm of the type peerRestarting(2) is generated, it indicates that the local end detectsthat the BGP peer is performing graceful restarting. When the routing protocol on whichBGP route iteration depends has the GR capability, services will not be affected. Otherwise,services will be interrupted.

l If an alarm of the type peerFinishRestart(3) is generated, it indicates that the BGP peersession becomes normal. In this case, no services will be affected.

l If an alarm of the type peerHelping(4) is generated, it indicates that the BGP peer is helpingthe local end to perform GR. When the routing protocol on which BGP route iterationdepends has the GR capability, services will not be affected. Otherwise, services will beinterrupted.

Possible Causes

The GR status of either BGP peer that succeeded in the GR capability negotiation changed.

Procedure

Step 1 Do as follows according to the value of the parameter GrStatus:

l If an alarm of the type peerNotBeingHelped(1) is generated, it indicates that the BGP peerwill not be helped during restarting. Then, go to Step 4.

l If an alarm of the type peerRestarting(2) is generated, it indicates that the BGP peer is detectedrestarting. Then, go to Step 2.

l If an alarm of the type peerFinishRestart(3) is generated, it indicates that the BGP peerfinishes the latest GR. In this case, no action is required. Then, go to Step 5.

l If an alarm of the type peerHelping(4) is generated, it indicates that the BGP peer is helpingthe local end to perform GR. Then, go to Step 3.

Step 2 Run the display ip routing-table ipv4-address command to check whether the address of thepeer exists.

l If so, it indicates that the local end is performing GR. In this case, no services will be affected,and no action is required.


Step 3 During GR, active/standby switchover is complete. In this case, you need to check whether thelocal end performs active/standby switchover actively.




Step 5 End.

----End



49

Related InformationNone.

7.6 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9hwBgpPeerEstablished

DescriptionBGP/2/HWESTABLISHED:OID [oid] The BGP FSM enters the Established state. (InstanceId=[gauge], Afi=[integer], Safi=[integer], PeerType=[integer], PeerRemoteAddr=[binary],PeerLastError=[octet], PeerState=[integer])

Indicates that this trap was generated when the BGP FSM was in the Established state.

Attribute


1.3.6.1.4.1.2011.5.25.177.1.3.9 Major communicationsAlarm(2)

Parameters

Name Meaning







50

Name Meaning



PeerLastError Indicates the error code of the BGP Notification when the neighborrelationship is disconnected for the last time.

The value is expressed in the format of [ErrorCode][ErrorSubCode].[ErrorCode] refers to the error code and [ErrorSubCode] refers to the errorsubcode. Take the integer 35 as an example, figure 3 is the error code andfigure 5 is the error subcode. For detailed information about the error code,refer to 66.1 BGP Error Code.




51

Name Meaning

PeerState Indicates the status of the BGP peer.l Idle: indicates that BGP denies any request of entering. This is the

initiatory status of BGP.Upon receiving a Start event, BGP initiates a TCP connection to theremote BGP peer, starts the ConnectRetry Timer with the initial value,detects a TCP connection initiated by the remote BGP peer, and changesits state to Connect.


– If the TCP connection succeeds, BGP stops the ConnectRetry Timer,sends an Open message to the remote peer, and changes its state toOpenSent.

– If the TCP connection fails, BGP restarts the ConnectRetry Timerwith the initial value, continues to detect a TCP connection initiatedby the remote peer, and changes its state to Active.

– If the ConnectRetry Timer has expired before a TCP connection isestablished, BGP restarts the timer with the initial value, initiates aTCP connection to the remote BGP peer, and stays in the Connectstate.

l Active: indicates that BGP tries to set up TCP connection. This is theintermediate status of BGP.

– If the TCP connection succeeds, BGP stops the ConnectRetry Timer,sends an Open message to the remote peer, and changes its state toOpenSent.

– If the ConnectRetry Timer has expired before a TCP connection isestablished, BGP restarts the timer with the initial value and changesits state to Connect.

– If BGP initiates a TCP connection with an unknown IP address, theTCP connection fails. When this occurs, BGP restarts theConnectRetry Timer with the initial value and stays in the Activestate.

l OpenSent: indicates that BGP has sent one Open message to its peer andwaits for the other Open message from the peer.

– If there are no errors in the Open message received, BGP changesits state to OpenConfirm.

– If there are errors in the Open message received, BGP sends aNotification message to the remote peer and changes its state to Idle.


l OpenConfirm: indicates that BGP waits for a Notification message or aKeepalive message.



52

Name Meaning

– If BGP receives a Notification message, or the TCP connection fails,BGP changes its state to Idle.



– If BGP receives an Update or a Keepalive message, its state stays inEstablished.

– If BGP receives a Notification message, BGP changes its state toIdle.


The BGP neighbor relationship can be normally established.

Possible Causes

The BGP neighbor relationship was established.

Procedure


----End

Related Information

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.10 hwBgpPeerBackwardTransition

7.7 BGP_1.3.6.1.4.1.2011.5.25.177.1.3.10hwBgpPeerBackwardTransition

Description

BGP/2/HWBACKWARD:OID [oid] The BGP FSM moves from a higher numbered state to alower numbered state. (InstanceId=[gauge], Afi=[integer], Safi=[integer], PeerType=[integer],PeerRemoteAddr=[binary], InterfaceIndex=[integer], PeerLastError=[octet], PeerState=[integer], PeerUnavaiReason=[gauge], InterfaceName=[octet])

Indicates that this trap was generated when the BGP state machine moved from a highernumbered state, namely, Openconfirm or Established, to a lower numbered state.



53

Attribute



Parameters

Name Meaning







InterfaceIndex Indicates the index of the interface.

PeerLastError Indicates the error code of the BGP Notification when the neighborrelationship is disconnected for the last time.

The value is expressed in the format of [ErrorCode][ErrorSubCode].[ErrorCode] refers to the error code and [ErrorSubCode] refers to the errorsubcode. Take the integer 35 as an example, figure 3 is the error code andfigure 5 is the error subcode. For detailed information about the error code,refer to 66.1 BGP Error Code.




54

Name Meaning

PeerState Indicates the status of the BGP peer.l Idle: indicates that BGP denies any request of entering. This is the

initiatory status of BGP.Upon receiving a Start event, BGP initiates a TCP connection to theremote BGP peer, starts the ConnectRetry Timer with the initial value,detects a TCP connection initiated by the remote BGP peer, andchanges its state to Connect.


– If the TCP connection succeeds, BGP stops the ConnectRetryTimer, sends an Open message to the remote peer, and changes itsstate to OpenSent.


– If the ConnectRetry Timer has expired before a TCP connection isestablished, BGP restarts the timer with the initial value, initiatesa TCP connection to the remote BGP peer, and stays in the Connectstate.

l Active: indicates that BGP tries to set up TCP connection. This is theintermediate status of BGP.

– If the TCP connection succeeds, BGP stops the ConnectRetryTimer, sends an Open message to the remote peer, and changes itsstate to OpenSent.

– If the ConnectRetry Timer has expired before a TCP connection isestablished, BGP restarts the timer with the initial value andchanges its state to Connect.

– If BGP initiates a TCP connection with an unknown IP address,the TCP connection fails. When this occurs, BGP restarts theConnectRetry Timer with the initial value and stays in the Activestate.

l OpenSent: indicates that BGP has sent one Open message to its peerand waits for the other Open message from the peer.

– If there are no errors in the Open message received, BGP changesits state to OpenConfirm.

– If there are errors in the Open message received, BGP sends aNotification message to the remote peer and changes its state toIdle.


l OpenConfirm: indicates that BGP waits for a Notification message ora Keepalive message.



55

Name Meaning




– If BGP receives an Update or a Keepalive message, its state staysin Established.

– If BGP receives a Notification message, BGP changes its state toIdle.

PeerUnavaiReason Indicates the reason that the BGP peer down.

InterfaceName Indicates the name of the interface.


The BGP neighbor will be disconnected, and the BGP route received from the neighbor will bedeleted. The packet forwarding based on the BGP route will fail.

Possible Causes

1. The BGP holdtimer timed out and did not receive the Keepalive packet.

2. BGP received incorrect BGP packets.

3. The BGP neighbor relationship was reset and the neighbor relationship was automaticallyinterrupted.

4. BGP received Notification packets from the neighbor.

Procedure

Step 1 Run the display bgp peer ipv4-addresses log-info command to check the check the Error fieldin the command output. You can view the Error Code and Sub Error Code in the receivedNotification in the form of [ErrorCode][ErrorSubCode].

l If the error code of the Notification is 1, it indicates that the BGP module receives the packetwith incorrect headers. Then, go to Step 23.

l If the error code of the Notification is 2, it indicates that the BGP module receives the incorrectOpen packet. Then, go to Step 23.

l If the error code of the Notification is 3, it indicates that the BGP module receives the incorrectUpdate packet. Then, go to Step 23.

l If the error code of the Notification is 4, it indicates that till the Holdtimer times out, the BGPmodule does not receive the Keepalive packet. Then, go to Step 4.



56

l If the error code of the Notification is 5, it indicates that the finite state machine of the BGPmodule is faulty. Then, go to Step 23.

l If the error code of the Notification is 6, go to Step 2.

Step 2 If the error code of the Notification is 6, it indicates that BGP automatically closes the connection.Then, you need to run the display bgp peer ipv4-address log-info command to view theNotification field and check whether the Notification is sent by the switch that generates thetrap.

l If "Send Notification" is displayed, it indicates that the local switch actively sends theNotification. Then, go to Step 3.

l If "Receive Notification" is displayed, it indicates that the local switch receives theNotification. Then, go to Step 22.

Step 3 Search for the reset bgp all and reset bgp ipv4-address commands in the logs to check whetherBGP is reset on the local end; or search for the peer ipv4-address enable command to checkwhether the peer is enabled in other address families on the local, or parameters for the BGPconnection are configured.

l If so, it indicates that incorrect configurations cause the trap, and thus no action is required.Then, go to Step 24.


Step 4 If the error code is 4, it indicates that the BGP disconnection is caused by the timeout of theHoldtimer. Then, you need to check whether the address of the BGP neighbor can be pingedsuccessfully.



Step 5 Run the display ip routing-table command to check whether the Destination/Mask field hasthe route to the peer address.



Step 6 Run the display acl all command to check whether the switch is configured with the ACL thatdisables TCP port 179.



Step 7 Run the display ip interface brief command to check whether the values of Physical andProtocol fields of the outbound interface are Up.



Step 8 Check the origin of the route with the BGP peer address.

l If the route is originated from OSPF, go to Step 12.

l If the route is originated from IS-IS, go to Step 13.

l Else, go to Step 23.

Step 9 Delete the ACL that disables the TCP port 179, and check whether the trapBGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished appears later.



57


Step 10 Check the BGP configuration to see whether loopback interfaces are used to establish BGP peers.l If so, go to Step 14.l If not, go to Step 15.

Step 11 Enter the view of the outbound interface, and run the display this command to check whetherthe interface is shut down.l If so, run the undo shutdown command to enable the interface.l If not, go to Step 22.

Step 12 Run the display ospf peer command to check whether the OSPF peer relationship is established.l If so, go to Step 23.l If not, refer to the solution provided in the case of trap OSPF_1.3.6.1.2.1.14.16.2.2

ospfNbrStateChange.

Step 13 Run the display isis peer command to check whether the IS-IS peer relationship is established.l If so, go to Step 23.l If not, refer to the solution provided in the case of trap ISIS_1.3.6.1.3.37.2.0.13

isisRejectedAdjacency.

Step 14 Check whether the peer connect-interface is configured for specifying the source address.l If so, go to Step 15.l If not, go to Step 16.

Step 15 If BGP is the EBGP neighbor relationship and multiple hops exist between EBGP neighbors,check whether the peer ebgp-max-hop is configured.l If so, go to Step 17.l If not, go to Step 19.

Step 16 Configure the peer connect-interface command. The parameter in the command must be thelocal interface that establishes a connection with the peer. Then, check whether the trapBGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished appears later.l If so, go to Step 24.l If not, go to Step 23.

Step 17 Check whether the peer valid-ttl-hops hops command is configured.l If so, go to Step 18.l If not, go to Step 23.

Step 18 If the peer valid-ttl-hops hops is configured, check whether the TTL of the packet to the peerranges from [255-hops+1] to 255.l If so, go to Step 23.l If not, go to Step 20.

Step 19 Configure the peer ebgp-max-hop. Then, check whether the trapBGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished appears later.l If so, go to Step 24.



58


Step 20 Changed the value of the peer valid-ttl-hops hops and make it within the range from [255-hops+1] to 255. Then, check whether the trap BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9hwBgpPeerEstablished appears later.l If so, go to Step 24.l If not, go to Step 23.

Step 21 Run the the display cpu-usage command to check whether the CPU usage whether the CPUusage remains 100% in a period.l If so, go to Step 23.l If not, go to Step 6.

Step 22 Contact the maintenance personnel of the peer device to check whether BGP is reset on the peerswitch, the peer is enabled in other address families on the local, and parameters for BGPconnection are configured. Then, check whether the trap BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9hwBgpPeerEstablished appears later.l If so, go to Step 24.l If not, go to Step 23.


Step 24 End.

----End

Related InformationBGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished



59

8 CMD

About This Chapter

8.1 CMD_1.3.6.1.4.1.2011.5.25.37.2.136 hwSuperChangeSuccesful

8.2 CMD_1.3.6.1.4.1.2011.5.25.37.2.137 hwSuperChangeFailure

8.3 CMD_1.3.6.1.4.1.2011.5.25.205.2.1 hwClockChanged

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 8 CMD


60

8.1 CMD_1.3.6.1.4.1.2011.5.25.37.2.136hwSuperChangeSuccesful

DescriptionCMD/2/SUPER_CHANGE_SUCCESS:OID [oid] Super change successful.

The current user succeeded in changing the user level.

Attribute


1.3.6.1.4.1.2011.5.25.37.2.136 Major environmentalAlarm(6)

Parameters

Name Meaning


Impact on the SystemSystem will not be affected.

Possible CausesThe current user succeeded in changing the user level.

Procedure


----End


8.2 CMD_1.3.6.1.4.1.2011.5.25.37.2.137hwSuperChangeFailure

DescriptionCMD/2/SUPERCHANGE_FAIL:OID [oid] Super change failure.



61

The current user failed to change the user level.

Attribute


1.3.6.1.4.1.2011.5.25.37.2.137 Major environmentalAlarm(6)

Parameters

Name Meaning



System will not be affected.

Possible Causes

The current user failed to change the user level.

Procedure


----End

Related Information

None

8.3 CMD_1.3.6.1.4.1.2011.5.25.205.2.1 hwClockChanged

Description

CMD/4/UTCCLOCKCHANGE:OID [oid] The system UTC clock changed. (CurrentTime=[STRING])

The system UTC clock changed.

Attribute


1.3.6.1.4.1.2011.5.25.205.2.1 Warning equipmentAlarm(5)



62

Parameters

Name Meaning

oid Indicates the OID of a MIB object.

CurrentTime Indicates the current UTC time.


Possible CausesThe system UTC time changed.

Procedure


----End




63

9 MAD

About This Chapter

9.1 MAD_1.3.6.1.4.1.2011.5.25.246.1.1 hwMadConflictDetect

9.2 MAD_1.3.6.1.4.1.2011.5.25.246.1.2 hwMadConflictResume

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 9 MAD


64

9.1 MAD_1.3.6.1.4.1.2011.5.25.246.1.1 hwMadConflictDetect

DescriptionMAD/4/MULTIACTIVEDETECTED(t): OID [oid] Multi-active scenario is detected.

A multi-active scenario was detected.

Attribute



Parameters

Name Meaning

oid Indicates the OID of the MIB object.

Impact on the SystemSwitches with the same IP address, MAC address, and global configuration are workingproperly. As a result, an address conflict occurs.

Possible CausesThe stack link was faulty.

Procedurel Check the stack cable.

----End


9.2 MAD_1.3.6.1.4.1.2011.5.25.246.1.2hwMadConflictResume

DescriptionMAD/4/MULTIACTIVEMERGE(t): OID [oid] Multi-active scenario is merged.

The nulti-active fault was rectified.



65

Attribute



Parameters

Name Meaning

oid Indicates the OID of the MIB object.

Impact on the SystemNone

Possible CausesNone

Procedurel None

----End




66

10 DHCP

About This Chapter

10.1 DHCP_1.3.6.1.4.1.2011.5.25.112.2.1 hwDhcpSnpChaddrAlarm

10.2 DHCP_1.3.6.1.4.1.2011.5.25.112.2.4 hwUntrustedReplyPktAlarm

10.3 DHCP_1.3.6.1.4.1.2011.5.25.112.2.5 hwNomatchSnpBindTblDhcpPktAlarm

10.4 DHCP_1.3.6.1.4.1.2011.5.25.112.2.6 hwDhcpPktRateAlarm

10.5 DHCP_1.3.6.1.4.1.2011.5.25.112.2.8 hwSnpUserNumberAlarmIf

10.6 DHCP_1.3.6.1.4.1.2011.5.25.112.2.9 hwSnpUserNumberAlarmIfResume

10.7 DHCP_1.3.6.1.4.1.2011.5.25.112.2.10 hwSnpUserNumberAlarmVlan

10.8 DHCP_1.3.6.1.4.1.2011.5.25.112.2.11 hwSnpUserNumberAlarmVlanResume

10.9 DHCP_1.3.6.1.4.1.2011.5.25.112.2.12 hwSnpUserNumberAlarmGlobal

10.10 DHCP_1.3.6.1.4.1.2011.5.25.112.2.13 hwSnpUserNumberAlarmGlobalResume

10.11 DHCP_1.3.6.1.4.1.2011.5.25.112.2.14 hwNdSnpUserNumberAlarmIf

10.12 DHCP_1.3.6.1.4.1.2011.5.25.112.2.15 hwNdSnpUserNumberAlarmIfResume

10.13 DHCP_1.3.6.1.4.1.2011.5.25.112.2.16 hwNdSnpUserNumberAlarmGlobal

10.14 DHCP_1.3.6.1.4.1.2011.5.25.112.2.17 hwNdSnpUserNumberAlarmGlobalResume

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 10 DHCP


67

10.1 DHCP_1.3.6.1.4.1.2011.5.25.112.2.1hwDhcpSnpChaddrAlarm

Description

DHCP/1/REQMACTRAP:OID [OID] The number of the discarded DHCP packets in which theCHADDR field is inconsistent with the source MAC address exceeds the threshold on theinterface. (IfIndex=[INTEGER], VlanIndex=[INTEGER], Interface=[OCTET], VlanID=[INTEGER], DiscardedNumber=[INTEGER])

The number of discarded DHCP packets in which the CHADDR field and the source MACaddress mismatched exceeded the threshold on the interface.

Attribute


1.3.6.1.4.1.2011.5.25.112.2.1 Critical equipmentAlarm(5)

Parameters

Name Meaning

OID Indicates the OID of the alarm.

IfIndex Indicates the interface index.

VlanIndex Indicates the VLAN index.

Interface Indicates the interface name.

VlanID Indicates the VLAN ID.

DiscardedNumber Indicates the number of discarded packets.


Invalid DHCP packets are discarded.

Possible Causes

The CHADDR field in DHCP packets is different from the source MAC address in DHCPpackets.

Procedure

Step 1 Capture packets on the interface to check whether a DHCP attack occurs on this interface.

l If the interface receives a large number of invalid DHCP packets, a DHCP attack occurs onthis interface. Because these attack packets have been discarded, no action is required.



68

l If no DHCP attack occurs, determine whether to run the undo dhcp snooping check dhcp-chaddr enable command on the interface according to networking requirements.

----End

Related Information

None.

10.2 DHCP_1.3.6.1.4.1.2011.5.25.112.2.4hwUntrustedReplyPktAlarm

Description

DHCP/1/REPLYTRAP:OID [OID] The number of the discarded DHCP reply packets on theuntrusted interface exceeds the threshold. (IfIndex=[INTEGER], VlanIndex=[INTEGER],Interface=[OCTET], VlanID=[INTEGER], DiscardedNumber=[INTEGER])

The number of DHCP Reply packets discarded on the untrusted interface exceeded the threshold.

Attribute



Parameters

Name Meaning









Possible Causes

Bogus DHCP server attacks occurred.



69

Procedure

Step 1 Capture packets on the interface to check whether a bogus DHCP server attack occurs on thisinterface.

l Check whether the DHCP server address in the received DHCP Reply packet is the specifiedserver address. If not, the DHCP server is a bogus server. Because the invalid DHCP packetshave been discarded, no action is required.

l If the DHCP server is a valid server and needs to be used, run the dhcp snooping trustedcommand on the interface to configure it as a trusted interface.

----End

Related Information

None.

10.3 DHCP_1.3.6.1.4.1.2011.5.25.112.2.5hwNomatchSnpBindTblDhcpPktAlarm

Description

DHCP/1/REQUESTTRAP:OID [OID] The number of the discarded DHCP request packets thatdo not match the binding table exceeds the threshold on the interface. (IfIndex=[INTEGER],VlanIndex=[INTEGER], Interface=[OCTET], VlanID=[INTEGER], DiscardedNumber=[INTEGER])

The number of DHCP Request packets discarded on the interface because they do not match thebinding table exceeded the threshold.

Attribute



Parameters

Name Meaning









70



Possible Causes

DHCP attacks occurred.

Procedure

Step 1 Capture packets on the interface to check whether a DHCP attack occurs on this interface.

l If the interface receives a large number of invalid DHCP packets, a DHCP attack occurs onthis interface. Because these attack packets have been discarded, no action is required.

l If no DHCP attack occurs, determine whether to run the undo dhcp snooping check dhcp-request enable command on the interface according to networking requirements.

----End

Related Information

None.

10.4 DHCP_1.3.6.1.4.1.2011.5.25.112.2.6hwDhcpPktRateAlarm

Description

DHCP/1/RATETRAP:OID [OID] The rate of DHCP packets exceeds the speed limit. (IfIndex=[INTEGER], VlanIndex=[INTEGER], Interface=[OCTET], VlanID=[INTEGER],DiscardedNumber=[INTEGER]).

The number of discarded DHCP packets reached the threshold after the DHCP packet rateexceeded the upper limit.

Attribute



Parameters

Name Meaning






71

Name Meaning





The DHCP packets of which the rate exceeds the upper limit are discarded.

Possible Causes

A large number of DHCP packets were received.

Procedure

Step 1 Check whether there is a DHCP attack.

l If the interface receives a large number of invalid packets, a DHCP attack occurs. Becausethese attack packets have been discarded, no action is required.

l If no DHCP attack occurs, determine whether to change the upper limit of DHCP packet rateaccording to networking requirements.

----End

Related Information

None

10.5 DHCP_1.3.6.1.4.1.2011.5.25.112.2.8hwSnpUserNumberAlarmIf

Description

DHCP/4/DHCPUSERBINDTRAPIF:OID [OID] The number of DHCP users on the interfaceexceeds alarm threshold. (IfIndex=[INTEGER],VlanIndex=[INTEGER],Interface=[OCTET],CurrentUser=[INTEGER],MaxUser=[INTEGER])

The number of DHCP users connected to an interface reaches the upper alarm threshold.

Attribute





72

Parameters

Name Meaning



VlanIndex Indicates the VLAN index. The value is 0.

Interface Indicates the interface name of the device.

CurrentUser Indicates the number of current access users.

MaxUser Indicates the maximum number of access users.


None.

Possible Causes

The number of DHCP snooping binding entries on an interface reaches the upper alarm threshold.

Procedure

Step 1 This trap message is informational only, and no action is required.

----End

Related Information

None.

10.6 DHCP_1.3.6.1.4.1.2011.5.25.112.2.9hwSnpUserNumberAlarmIfResume

Description

DHCP/4/DHCPUSERBINDTRAPIFRESUME:OID [OID] The number of DHCP users on theinterface descends to alarm threshold (IfIndex=[INTEGER],VlanIndex=[INTEGER],Interface=[OCTET],CurrentUser=[INTEGER],MaxUser =[INTEGER])

The number of DHCP users connected to an interface reaches the lower alarm threshold.



73

Attribute



Parameters

Name Meaning







Impact on the SystemNone.

Possible CausesThe number of DHCP snooping binding entries on an interface reaches the lower alarm threshold.

Procedure


----End




74

10.7 DHCP_1.3.6.1.4.1.2011.5.25.112.2.10hwSnpUserNumberAlarmVlan

DescriptionDHCP/4/DHCPUSERBINDTRAPVLAN:OID [OID] The number of DHCP users on the vlanexceeds alarm threshold. (IfIndex=[INTEGER],VLANIndex=[INTEGER], VlanID=[INTEGER],CurrentUser=[INTEGER], MaxUser=[INTEGER])

The number of DHCP users in a VLAN reaches the upper alarm threshold.

Attribute



Parameters

Name Meaning


IfIndex Indicates the interface index. The value is 0.






Possible CausesThe number of DHCP snooping binding entries in a VLAN reaches the upper alarm threshold.

Procedure


----End



75

Related Information

None.

10.8 DHCP_1.3.6.1.4.1.2011.5.25.112.2.11hwSnpUserNumberAlarmVlanResume

Description

DHCP/4/DHCPUSERBINDTRAPVLANRESUME:OID [OID] The number of DHCP users onthe vlan descends to alarm threshold. ( IfIndex=[INTEGER],VLANIndex=[INTEGER],VlanID=[INTEGER],CurrentUser=[INTEGER],MaxUser=[INTEGER])

The number of DHCP users in a VLAN reaches the lower alarm threshold.

Attribute



Parameters

Name Meaning








None.

Possible Causes

The number of DHCP snooping binding entries in a VLAN reaches the lower alarm threshold.



76

Procedure


----End


10.9 DHCP_1.3.6.1.4.1.2011.5.25.112.2.12hwSnpUserNumberAlarmGlobal

DescriptionDHCP/4/DHCPUSERBINDTRAPGLOBAL:OID [OID] The number of DHCP global usesexceeds alarm threshold. (IfIndex=[INTEGER],VlanIndex=[INTEGER],CurrentUser=[INTEGER],MaxUser=[INTEGER])

The number of global DHCP users reaches the upper alarm threshold.

Attribute



Parameters

Name Meaning







Possible CausesThe number of global DHCP snooping binding entries reaches the upper alarm threshold.



77

Procedure


----End


10.10 DHCP_1.3.6.1.4.1.2011.5.25.112.2.13hwSnpUserNumberAlarmGlobalResume

DescriptionDHCP/4/DHCPUSERBINDTRAPGLOBALRESUME:OID [OID] The number of DHCPglobal users descends to alarm threshold. (IfIndex=[INTEGER],VlanIndex=[INTEGER],CurrentUser=[INTEGER], MaxUser=[INTEGER])

The number of global DHCP users reaches the lower alarm threshold.

Attribute



Parameters

Name Meaning







Possible CausesThe number of global DHCP snooping binding entries reaches the lower alarm threshold.



78

Procedure


----End

Related Information

None.

10.11 DHCP_1.3.6.1.4.1.2011.5.25.112.2.14hwNdSnpUserNumberAlarmIf

Description

DHCP/4/NDUSERBINDTRAPIF:OID [OID] The number of ND users on the interface exceedsalarm threshold. (IfIndex=[INTEGER],VlanIndex =[INTEGER],Interface=[OCTET],CurrentUser=[INTEGER],MaxUser=[INTEGER])

The number of ND users connected to an interface reaches the upper alarm threshold.

Attribute



Parameters

Name Meaning








None.



79

Possible Causes

The number of ND snooping binding entries on an interface reaches the upper alarm threshold.

Procedure


----End

Related Information

None.

10.12 DHCP_1.3.6.1.4.1.2011.5.25.112.2.15hwNdSnpUserNumberAlarmIfResume

Description

DHCP/4/NDUSERBINDTRAPIFRESUME:OID [OID] The number of ND users on theinterface descends to alarm threshold. (IfIndex=[INTEGER],VlanIndex=[INTEGER],Interface=[OCTET],CurrentUser=[INTEGER],MaxUser=[INTEGER])

The number of ND users connected to an interface reaches the lower alarm threshold.

Attribute



Parameters

Name Meaning









80


None.

Possible Causes

The number of ND snooping binding entries on an interface reaches the lower alarm threshold.

Procedure


----End

Related Information

None.

10.13 DHCP_1.3.6.1.4.1.2011.5.25.112.2.16hwNdSnpUserNumberAlarmGlobal

Description

DHCP/4/NDUSERBINDTRAPGLOBAL:OID [OID] The number of ND global users exceedsalarm threshold. (IfIndex=[INTEGER],VlanIndex=[INTEGER],CurrentUser=[INTEGER],MaxUser=[INTEGER])

The number of global ND users reaches the upper alarm threshold.

Attribute



Parameters

Name Meaning







81

Name Meaning



None.

Possible Causes

The number of global ND snooping binding entries reaches the upper alarm threshold.

Procedure


----End

Related Information

None.

10.14 DHCP_1.3.6.1.4.1.2011.5.25.112.2.17hwNdSnpUserNumberAlarmGlobalResume

Description

DHCP/4/NDUSERBINDTRAPGLOBALRESUME:OID [OID] The number of ND globalusers descends to alarm threshold. (IfIndex=[INTEGER],VlanIndex=[INTEGER],CurrentUser=[INTEGER],MaxUser=[INTEGER])

The number of global ND users reaches the lower alarm threshold.

Attribute



Parameters

Name Meaning





82

Name Meaning





Possible CausesThe number of global ND snooping binding entries reaches the lower alarm threshold.

Procedure


----End




83

11 DLDP

About This Chapter

11.1 DLDP_1.3.6.1.4.1.2011.5.25.173.3.1 hwDldpUnidirectionalLink

11.2 DLDP_1.3.6.1.4.1.2011.5.25.173.3.2 hwDldpLinkResume

11.3 DLDP_1.3.6.1.4.1.2011.5.25.173.3.3 hwDldpLoopDetect

11.4 DLDP_1.3.6.1.4.1.2011.5.25.173.3.4 hwDldpLoopResume

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 11 DLDP


84

11.1 DLDP_1.3.6.1.4.1.2011.5.25.173.3.1hwDldpUnidirectionalLink

Description

DLDP/4/DETECTUNIDIRECT(t): OID [oid] The port is detected in one way status. (IfIndex=[integer], IfName=[STRING])

A unidirectional link is detected in either of the following situations:

Single-neighbor mode: If one of the two connected devices can receive packets from the remotedevice but the remote device cannot receive packets from the local device, the two devices areconnected unidirectionally.

Multi-neighbor mode: A device detects that one of its neighbors is in unidirectional state or thedevice receives the disable packet.

Attribute


1.3.6.1.4.1.2011.5.25.173.3.1 Minor equipmentAlarm(5)

Parameters

Name Meaning

[oid] Indicates the OID of the alarm.

IfIndex Indicates the index of the interface where the unidirectional communication alarm isgenerated.

IfName Indicates the name of the interface where the unidirectional communication alarm isgenerated.


The interface cannot receive packets.

Possible Causes

To ensure bidirectional communication between interfaces, establish a bidirectional connectionbetween the interfaces. The interfaces can be connected through optical fibers or twisted-paircables.

Figure 11-1 shows the correct connection between interfaces using two pairs of interfaces ontwo devices as an example.



85

Figure 11-1 Direct bidirectional connection

This alarm is generated in one of the following situations.

1. Interfaces of the two devices are not connected one to one, as shown in Figure 11-2.

Figure 11-2 Cross connection error 1

2. One or more cables are disconnected, as shown in Figure 11-3.



86

Figure 11-3 Cable disconnection error

NOTE

Figure 11-3 uses the connection method shown in Figure 11-1 as an example.

3. Links are disconnected because of faults, as shown in Figure 11-4.

Figure 11-4 Cable fault

NOTE

Figure 11-4 uses the connection method shown in Figure 11-1 as an example.

Procedure

Step 1 Run the display this command in the system view to check the DLDP unidirectional-shutdown field. The DLDP unidirectional-shutdown field specifies the mode in which aninterface is disabled when a unidirectional link is detected. Perform the following operationsaccording to the DLDP unidirectional-shutdown field value:



87

l If the DLDP unidirectional-shutdown field displays manual, the interface is disabledmanually.

Run the shutdown command in the interface view to disable the interface from sending orreceiving packets. Then go to step 2.

l If the DLDP unidirectional-shutdown field displays auto, the interface is disabledautomatically.

The system sends logs and traps automatically and sets the interface status to Block. Go tostep 2.

Step 2 Check whether devices are cross-connected.

(1) If so, connect the devices correctly and go to step 4.

(2) If not, go to step 3.

Step 3 Check whether the physical connection between the two devices is correct.

If any of the following situations occur, the physical connection between the two devices isincorrect:

l An optical fiber is disconnected.

l The twisted-pair cable is disconnected.

(1) If so, go to step 5.

(2) If not, connect the optical fiber or twisted-pair cable to the two devices and go to step 4.

Step 4 Check whether the alarm is cleared.

(1) If so, go to step 7.


Step 5 Check whether any optical fiber or twisted-pair cable is damaged.

(1) If so, replace the optical fiber or twisted-pair cable and go to step 4.



Step 7 End.

The following situations indicate that the fault is rectified:

l The alarm is not displayed on the NMS.

l This alarm is not displayed in the display trapbuffer command output.

l This alarm is not displayed when you run the terminal monitor or terminal trappingcommand.

----End

Related Information

DLDP_1.3.6.1.4.1.2011.5.25.173.3.2 hwDldpLinkResume



88

11.2 DLDP_1.3.6.1.4.1.2011.5.25.173.3.2hwDldpLinkResume

Description

DLDP/4/DETECTUNIDIRECT(t): OID [oid] The port is detected in two way status. (IfIndex=[integer], IfName=[STRING])

A unidirectional link fault was removed, and two connected devices can send and receive packetscorrectly.

A bidirectional communication alarm is generated when the device that receives packets fromthe other device detects the bidirectional communication state.

Attribute


1.3.6.1.4.1.2011.5.25.173.3.2 Cleared equipmentAlarm(5)

Parameters

Name Meaning



IfName Indicates the interface name.


The interface sends and receives packets correctly.

Possible Causes

1. Optical fibers or twisted-pair cables were connected correctly.

2. The cable connection fault was rectified.

Procedure

Step 1 Run the display this command in the system view to check the DLDP unidirectional-shutdown field.

l If the DLDP unidirectional-shutdown field displays manual, the interface is disabledmanually.Run the undo shutdown command in the interface view to enable the interface to send andreceive packets.



89

l If the DLDP unidirectional-shutdown field is not displayed, the interface is disabledautomatically.To enable the interface that is disabled automatically, use either of the following methods:

– Run the dldp reset command in the system view to enable the interface.

– Wait until DLDP detects the bidirectional communication state of the neighbor. DLDPwill enable the interface using the automatic link recovery mechanism.

----End

Related Information

DLDP_1.3.6.1.4.1.2011.5.25.173.3.1 hwDldpUnidirectionalLink

11.3 DLDP_1.3.6.1.4.1.2011.5.25.173.3.3 hwDldpLoopDetect

Description

DLDP/4/DETECTUNIDIRECT(t): OID [oid] The port is detected in Loop status. (IfIndex=[integer], IfName=[STRING])

A loop is detected on an interface due to incorrect fiber connection or a hub fault.

Attribute



Parameters

Name Meaning

[oid] Indicates the MIB object ID.

IfIndex Indicates the index of the interface where the loop alarm is generated.

IfName Indicates the name of the interface where the loop alarm is generated.


Packet forwarding on the interface is affected.

Possible Causes

The signals transmitted from the Tx end of an optical interface are received by the Rx end ofthe interface due the either of the following reasons:

l The Tx end and Rx end of the interface is connected on a fiber.

l A fault occurs on the hub connected to the interface.



90

Procedure

Step 1 Run the display dldp command to check the DLDP status on the interface.

l If the DLDP port state field displays advertisement, the loop has been removed. Go to 4.

l If the DLDP port state field displays loop, a loop link exists. Go to 2.

Step 2 Check whether the fibers on the interface are connected correctly or whether the hub connectedto the interface is working properly.

(1) If the fibers are corrected incorrectly or the hub fails, connect the fibers correctly or fix thehub fault, and go to 1.

(2) If the fibers are connected correctly and the hub connected to the interface is workingproperly, go to 3.


Step 4 End.

----End

Related Information

DLDP_1.3.6.1.4.1.2011.5.25.173.3.4 hwDldpLoopResume

11.4 DLDP_1.3.6.1.4.1.2011.5.25.173.3.4hwDldpLoopResume

Description

DLDP/4/DETECTUNIDIRECT(t): OID [oid] The port is detected exit Loop status. (IfIndex=[integer], IfName=[STRING])

The loop on an interface has been removed or the interface is shut down.

Attribute



Parameters

Name Meaning

[oid] Indicates the MIB object ID.

IfIndex Indicates the index of the interface where the alarm is generated.

IfName Indicates the name of the interface where the alarm is generated.



91

Impact on the SystemThe loop on the interface has been removed.

l If the fibers on the interface are connected correctly and the loop is removed, services onthe interface are resumed.

l If the interface is shut down, the interface cannot work.

Possible Causes1:

The fibers on the interface are connected correctly and the loop is removed.

2:

The interface is shut down.

Procedure

Step 1 Run the display dldp command to check the DLDP status on the interface.l If the DLDP port state field displays advertisement, the loop has been removed. Go to 4.l If the DLDP port state field displays inactive, go to 2.

Step 2 Check whether the interface is in Down state.

(1) If so, connect the fibers correctly. When the interface goes Up, go to 1.

(2) If not, go to 3.


Step 4 End.

----End

Related InformationDLDP_1.3.6.1.4.1.2011.5.25.173.3.3 hwDldpLoopDetect



92

12 DOT1X

About This Chapter

12.1 DOT1X_1.3.6.1.4.1.2011.5.25.40.4.2.1 hwSrvcfgEapMaxUserAlarm

12.2 DOT1X_1.3.6.1.4.1.2011.5.25.171.2.1 hwMacAuthenMaxUserAlarm

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 12 DOT1X


93

12.1 DOT1X_1.3.6.1.4.1.2011.5.25.40.4.2.1hwSrvcfgEapMaxUserAlarm

DescriptionDOT1X/4/8021XREACHMAXNUM(t):OID [OID] The number of users has been reached maxnumber.(PortIndex=[INTEGER], PortName=[OCTET])

The number of 802.1x authentication users reaches the upper limit.

Attribute


1.3.6.1.4.1.2011.5.25.40.4.2.1 Warning processingErrorAlarm(4)

Parameters

Name Meaning


PortIndex Indicates the access interface index.

PortName Indicates the access interface name.

Impact on the SystemUsers cannot access through this interface.

Possible CausesThe number of 802.1x authentication users reaches the upper limit.

Procedure

Step 1 This alarm is informational and no action is required.

----End


12.2 DOT1X_1.3.6.1.4.1.2011.5.25.171.2.1hwMacAuthenMaxUserAlarm



94

DescriptionDOT1X/4/MACAREACHMAXNUM(t):OID [OID] The number of users has been reached maxnumber.(PortIndex=[INTEGER], PortName=[OCTET])

The number of MAC address authentication users reaches the upper limit.

Attribute



Parameters

Name Meaning


PortIndex Indicates the access interface index.

PortName Indicates the access interface name.

Impact on the SystemUsers cannot access through this interface.

Possible CausesThe number of MAC address authentication users reaches the upper limit.

Procedure


----End




95

13 DS

About This Chapter

13.1 DS_1.3.6.1.4.1.2011.5.25.191.3.1 hwCfgChgNotify

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 13 DS


96

13.1 DS_1.3.6.1.4.1.2011.5.25.191.3.1 hwCfgChgNotify

Description

DS/4/DATASYNC_CFGCHANGE:OID [OID] configurations have beed changed. The currentchange number is [change-number], the change loop count is [loop-count], and the maximumnumber of records is [max-number].

Configurations on the host have been changed.

Attribute


1.3.6.1.4.1.2011.5.25.191.3.1 Warning communicationsAlarm(2)

Parameters

Name Meaning

oid OID of the alarm for the configuration change

[change-number] Sequence number of the current change

[loop-count] Current loop count

[max-number] Maximum number of entries in the configuration change cache table


Configurations about services will change.

Possible Causes

Configurations on the host have been changed within a specified period.

Procedure

l This log message is informational only, and no action is required.

----End

Related Information

None.

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 13 DS


97

14 ECM

About This Chapter

NOTE

S5710-HI, S5700SI, S5700EI, and S5700S-LI series switches do not support these alarms.

14.1 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.9 hwStackLogicStackPortLinkErr

14.2 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.10 hwStackPhyStackPortLinkErr

14.3 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.11 hwPhyStackPortIsDown

14.4 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.14 hwStackPortConfigureFailed

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 14 ECM


98

14.1 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.9hwStackLogicStackPortLinkErr

Description

ECM/3/LOGICAL_STACK_PORT_ILLEGAL: OID [OID] stack port [octet1] connects with[octet2], there are port member of the same logic stack port ID.

The logical stack ports are connected in a wrong order. The switch requires that the memberports in logical stack port 1 be connected to the member ports in stack port 2.

Attribute



Parameters

Name Meaning


[octet1] Indicates the local interface name.

[octet2] Indicates the name of remote interface connected to the local interface.


The stack cannot be set up or the link generating the alarm is unavailable.

Possible Causes

The logical stack ports are connected in a wrong order.

Procedure

l Connect the member ports in logical stack port 1 to the member ports in logical stack port2, and perform the same operation on the remote device.

----End

Related Information

None.



99

14.2 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.10hwStackPhyStackPortLinkErr

Description

ECM/3/PHYSICAL_STACK_PORT_ILLEGAL: OID [OID] stack port [octet1] and [octet2] inthe same logical stack port, but connect to different switch.

The member ports in a logical stack port on the switch are connected to different switches. Theswitch requires that the member ports in the same logical stack port be connected to the sameswitch.

Attribute



Parameters

Name Meaning


[octet1] Indicates the local interface name.

[octet2] Indicates the name of remote interface connected to the local interface.


The stack cannot be set up or the link generating the alarm is unavailable.

Possible Causes

The member ports in a logical stack port on the switch are connected to different switches.

Procedure

l Connect the member ports in a logical stack port to the same switch according to the stackport connection rule.

----End

Related Information

None.



100

14.3 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.11hwPhyStackPortIsDown

Description

ECM/3/STACKPORTISDOWN: OID [OID] stack port [octet] is down.

A member port that has been added to a logical stack port becomes Down.

Attribute



Parameters

Name Meaning


[octet] Indicates the local interface name.


None.

Possible Causes

The member port is not connected.

Procedure

l Insert an optical port to the member port and connect the port to another port. The memberport will become Up.

----End

Related Information

None.

14.4 ECM_1.3.6.1.4.1.2011.5.25.183.1.22.14hwStackPortConfigureFailed



101

DescriptionECM/3/STACKPORTCONFIGUREFAILED: OID [OID] Stack port configuration failed.Please reset slot [OCTET] and re-configure the stack port.

The stacking configuration failed on the interface, and the device needs to be restated.

Attribute



Parameters

Name Meaning


OCTET Indicates the stack ID of the device.

Impact on the SystemThe stack cannot be set up.

Possible CausesThe stacking configuration failed on the interface.

Procedurel Reconfigure the stack interface after the device is restarted.

----End




102

15 EFM

About This Chapter

15.1 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.4 hwDot3ahEfmThresholdEvent

15.2 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5 hwDot3ahEfmNonThresholdEvent

15.3 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.8 hwDot3ahEfmRemoteDyingGaspEvent

15.4 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.17 hwDot3ahEfmNonThresholdRecovery

15.5 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.29 hwDot3ahEfmLoopbackFailed

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 15 EFM


103

15.1 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.4hwDot3ahEfmThresholdEvent

Description

EFM/3/THRESHOLDTRAP:OID [oid] Threshold event occured. ( IfIndex=[INTEGER],EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], EventLogOui=[OPAQUE],EventLogType=[GAUGE], EventLogLocation=[INTEGER], EventLogWindowHi=[GAUGE], EventLogWindowLo=[GAUGE], EventLogThresholdHi=[GAUGE],EventLogThresholdLo=[GAUGE], EventLogValue=[COUNTER64],EventLogRunningTotal=[COUNTER64], EventLogEventTotal=[GAUGE])

The number of error frames, error codes, or error frame seconds exceeded the set threshold withinthe specified period.

Attribute



Parameters

Name Meaning



EventLogIndex Indicates the index of the printed log.

EventLogTimestamp Indicates the time stamp that records when the event occurs.

EventLogOui Indicates the OUI of an event.

EventLogType Indicates the type of an event.

EventLogLocation Indicates where the event occurs (1 indicates local end, 2 indicatespeer end).

EventLogWindowHi Indicates the high-order value of the monitoring interval.

EventLogWindowLo Indicates the low-order value of the monitoring interval.

EventLogThresholdHi Indicates the high-order value of the threshold of the monitoringinterval.

EventLogThresholdLo Indicates the low-order value of the threshold of the monitoringinterval.

EventLogValue Indicates the number of times that the threshold-crossing eventoccurs.



104

Name Meaning

EventLogRunningTotal Indicates the number of event occurrences.

EventLogEventTotal Indicates the number of event notifications.


Services cannot be forwarded.

Possible Causes

1. The user configured the efm error-code threshold 0,efm error-frame threshold 0 or efmerror-frame-second threshold 0 command on the interface.

2. The physical link became faulty, causing the error frame or error code.

Procedure

Step 1 Check the value of the EventLogType field in the trap:

l 1: indicates a trap about error codes. Then, go to Step 2.

l 2: indicates a trap about error frames. Then, go to Step 3.

l 4: indicates a trap about error frame seconds. Then, go to Step 4.

Step 2 Run the display this command in the interface view to check whether the efm error-codethreshold 0 command is configured.



Step 3 Run the display this command in the interface view to check whether the efm error-framethreshold 0 command is configured.



Step 4 Run the display this command in the interface view to check whether the efm error-frame-second threshold 0 command is configured.



Step 5 Check whether the physical link is faulty.



Step 6 Run the efm error-frame threshold threshold command in the interface view to reconfigurethe threshold for detecting error frames on the current interface as required. Then, check whetherthe alarm is cleared.





105

Step 7 Run the efm error-frame-second threshold threshold command in the interface view toreconfigure the threshold for detecting error frame seconds on the current interface as required.Then, check whether the alarm is cleared.



Step 8 Change the physical link and then check whether the alarm is cleared.



Step 9 Collect trap messages, log messages, and configurations, and then contact the Huawei technicalsupport personnel.

Step 10 End.

----End

Related Information

None

15.2 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5hwDot3ahEfmNonThresholdEvent

Description

EFM/3/NONTHRESHOLDTRAP:OID [oid] Nonthreshold Event occured. (IfIndex=[INTEGER], EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK],EventLogOUI=[OPAQUE], EventLogType=[GAUGE], EventLogLocation=[INTEGER])

None-threshold-crossing events occur on the link, including LinkLost, LinkFault, DyingGasp,and CriticalLink events.

Attribute



Parameters

Name Meaning







106

Name Meaning

EventLogOUI Indicates the OUI of an event.

EventLogType Indicates the type of an event.

EventLogLocation Indicates where the event occurs (1 indicates local end, 2 indicates peerend).

Impact on the SystemServices will be interrupted.

Possible Causes1. The remote interface was not enabled with EFM.

2. The interface was shut down; or the physical link went Down.

3. The local or remote device was restarted.

4. Faults occurred at the public network side.

Procedure

Step 1 Check the value of the EventLogType field in the trap:l 254: indicates the timeout. Then, go to Step 2.l 256: indicates that the local interface is shut down. Then, go to Step 3.l 257: indicates the DyingGasp event. Then, go to Step 4.l 258: indicates the CriticalLink event. Then, go to Step 5.

Step 2 Run the display this command in the interface view to check whether EFM is enabled on theremote device.l If so, go to Step 6.l If not, go to Step 8.

Step 3 Run the display this command in the interface view to check whether the local interface is shutdown.l If so, go to Step 9.l If not, go to Step 6.

Step 4 Check whether the remote device is being restarted.l If so, go to Step 10.l If not, go to Step 12.

Step 5 Check whether a fault occurs on the module associated with EFM.l If so, go to Step 7.l If not, go to Step 12.

Step 6 Check whether the physical link is faulty.l If so, go to Step 11.



107


Step 7 Restore the module associated with EFM, and then check whether the alarm is cleared.



Step 8 Run the efm enable command in the interface view of the remote device to enable EFM. Then,check whether the alarm is cleared.



Step 9 Run the undo shutdown command in the interface view to check whether the alarm is cleared.



Step 10 After the remote device works normally, check whether the alarm is cleared.



Step 11 Replace the physical link and then check whether the alarm is cleared.




Step 13 End.

----End

Related Information

None

15.3 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.8hwDot3ahEfmRemoteDyingGaspEvent

Description

EFM/3/DYINGGASP: OID [oid] Remote DyingGasp Event occurred. (IfIndex=[INTEGER],RemoteMacAddress=[OCTET], IfName=[OCTET])

An unrecoverable event occurs, for example, the system or a board restarts, or the device ispowered off.



108

Attribute


1.3.6.1.4.1.2011.5.25.136.1.6.8 Minor processingErrorAlarm (4)

Parameters

Name Meaning

oid MIB OID

IfIndex Interface index of the peer device received by the local device

RemoteMacAddress MAC address of the remote device

IfName Interface name of the peer device received by the local device


Services on the remote device are unavailable.

Possible Causes

Cause 1:

The remote device restarts.

Cause 2:

The board on the remote device restarts.

Cause 3:

The remote device is powered off.

Procedure

Step 1 After the remote device or the board on the remote device restarts, run the display efmsession command to check the EFM status.

l If yes, go to Step 3.

l If no, go to Step 2.

Step 2 Collect configuration, trap messages, and log messages, and then contact Huawei technicalpersonnel.

Step 3 End.

----End

Related Information

None.



109

15.4 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.17hwDot3ahEfmNonThresholdRecovery

Description

EFM/3/NONTHRDRECV:OID [OID] Nonthreshold trap recovered.(IfIndex=[INTEGER],EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], TrapLogOUI=[OPAQUE],TrapLogType=[GAUGE], TrapLogLocation=[INTEGER])

The trap about handshake timeout, a link event, an urgent event, or a remote fault was cleared.

Attribute



Parameters

Name Meaning





TrapLogOUI Indicates the OUI of an event.

TrapLogType Indicates the type of an event.

TrapLogLocation Indicates where the event occurs, on the local end or the remote end.


The system performance is not affected.

Possible Causes

The trap about handshake timeout, a link event, an urgent event, or a remote fault was cleared.

Procedure

l This trap message is informational only, and no action is required.

----End



110

15.5 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.29hwDot3ahEfmLoopbackFailed

Description

EFM/5/LOOPBACKFAIL:OID [OID] Interface starts loopback failed. (IfIndex=[INTEGER],IfName=[STRING])

802.3ah loopback failed after no response to an 802.3ah loopback request was received withina specified period of time.

Attribute


1.3.6.1.4.1.2011.5.25.136.1.6.29 Indeterminate qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid ID of the MIB object

IfIndex Interface index

IfName Interface name


EFM OAM loopback cannot be initiated.

Possible Causes

802.3ah loopback failed after no response to an 802.3ah loopback request was received withina specified period of time.

Procedure

Step 1 Check whether the remote interface denies the remote loopback request from the local end.

Run the display current-configuration command. Check whether the efm loopback ignore-request command is used.

l If this command is used, the remote interface denies the request. Run the undo efm loopbackignore-request command to enable the remote interface to receive the remote loopbackrequest. Then go to Step 2.

l If this command is not used, the remote interface is able to receive the request. Then go toStep 3.



111

Step 2 Then check whether the alarm is cleared.

If the alarm persists, go to Step 3.

Step 3 Check the EFM status.

Run the display efm session all command. Check whether the value of the EFM State field isdetect.

l If the value of the EFM State field is detect, go to Step 5.l If the value of the EFM State field is not detect, go to Step 4.

Step 4 Check the physical link. If the physical link is faulty, see "Physical InterconnectionTroubleshooting" for details about how to troubleshoot the link fault.

Step 5 Collect the alarm information, log information, and configuration information, and then contactHuawei technical support personnel.

----End




112

16 ENTITYTRAP

About This Chapter

16.1 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.5 hwBoardInvalid 132626

16.2 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132121









16.11 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132121









16.20 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135190

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 16 ENTITYTRAP


113



16.23 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135190





16.28 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid 135450-135458

16.29 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid 135459

16.30 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume 135450-135458

16.31 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume 135459

16.32 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.9.1 hwCommunicateError 135457

16.33 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.9.2 hwCommunicateResume 135457

16.34 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.13 hwBrdTempAlarm 140544

16.35 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.13 hwBrdTempAlarm 140545

16.36 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.14 hwBrdTempResume 140544

16.37 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.14 hwBrdTempResume 140545

16.38 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5 hwOpticalInvalid 136192





16.43 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.6 hwOpticalInvalidResume 136193




16.47 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.1 hwPowerRemove 136448

16.48 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.2 hwPowerInsert 136448

16.49 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.5 hwPowerInvalid 136961






114

16.53 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume 136961




16.57 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.1 hwFanRemove 137216

16.58 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.2 hwFanInsert 137216

16.59 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.5 hwFanInvalid 139264

16.60 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.6 hwFanInvalidResume 139264

16.61 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.1 hwCardRemove

16.62 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.2 hwCardInsert

16.63 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid

16.64 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume

16.65 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.1 hwCPUUtilizationRising

16.66 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.2 hwCPUUtilizationResume

16.67 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.15.1 hwMemUtilizationRising

16.68 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.15.2 hwMemUtilizationResume



115

16.1 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.5hwBoardInvalid 132626

DescriptionNOTE

Only the S5700LI support this trap.

Entitytrap/1/BOARDINVALID(t):OID [oid] Board is invalid for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=\"[OCTET]\",EntityTrapEntType= [INTEGER], EntityTrapFaultID=132626)

The board fails.

Attribute



Parameters

Name Meaning


Index Indicates the index.

EntityPhysicalIndex Indicates the physical index.

PhysicalName Indicates the entity name.

EntityTrapEntType Indicates the entity type.

EntityTrapFaultID Indicates the error code.


Services on the device are interrupted.

Possible Causes

The power cable is loose.

The external power cable is faulty.

The power supply unit is faulty.



116

Procedure

Step 1 Check whether the power cable is loose or faulty. If so, properly connect the power cable andpower on the device. If not, check whether the power supply unit is faulty. If so, replace thepower supply unit.

----End

Related Information

None

16.2 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3hwBoardFail 132121

Description

ENTITYTRAP/2/BOARDFAIL: OID [oid] Board become failure for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])

Some functions on the board did not take effect.

Attribute


1.3.6.1.4.1.2011.5.25.219.2.2.3 Major equipmentAlarm(5)

Parameters

Name Meaning




PhysicalName Indicates the entity name, which varies with the board type, such as FSU,LPU, and MPU.




The board may be unavailable, some functions on it did not take effect, and services may beinterrupted.



117

Possible Causes

The USB controller was faulty.

Procedure

l If there is no storage device on the USB interface, services will not be affected. This alarmmessage is informational only, and no action is required.

l If you need to use the USB interface, choose the other USB interfaces on this board or theUSB interfaces on other boards.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132121


Description



Attribute



Parameters

Name Meaning









118



Possible Causes

The I2C bus was faulty.

Procedure

l Replace the faulty board in the slot.

----End

Related Information



Description



Attribute



Parameters

Name Meaning








119

Name Meaning




Possible Causes

The clock module on the board was faulty.

Procedure

l Replace the faulty board in the slot.

----End

Related Information



Description



Attribute



Parameters

Name Meaning






120

Name Meaning




Impact on the SystemThe board may be unavailable, some functions on it did not take effect, and services may beinterrupted.

Possible CausesThe Phase-Locked Loop (PLL) was faulty.

Procedurel Replace the faulty board in the slot.

----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume 132128


DescriptionENTITYTRAP/2/BOARDFAIL: OID [oid] Board become failure for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])


Attribute





121

Parameters

Name Meaning








Possible CausesThe Digital Signal Processor (DSP) was faulty.


----End







122

Attribute



Parameters

Name Meaning








Possible CausesChips (including CPLD, RTC, EEPROM, and temperature control chip) were faulty.


----End







123

Attribute



Parameters

Name Meaning








Possible CausesThe POS SPF flexible card was faulty.

Procedurel Replace the faulty POS SPF flexible card.

----End







124

Attribute



Parameters

Name Meaning








Possible CausesThe Power over Ethernet (PoE) was faulty.

Procedure

Step 1 Replace the faulty PoE power.If the fault persists, go to step 2.

Step 2 Replace the faulty PoE DIMM.If the fault persists, go to step 3.


----End





125

Description



Attribute



Parameters

Name Meaning









Possible Causes

The indicator was faulty.

Procedure

l Collect the alarm information, log information, and configuration information, and thencontact Huawei technical support personnel.

----End

Related Information




126

16.11 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.4hwBoardFailResume 132121

DescriptionENTITYTRAP/4/BOARDFAILRESUME: OID [oid] Board resume from failure.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])

Effective functions on the board recovered.

Attribute


1.3.6.1.4.1.2011.5.25.219.2.2.4 warning environmentalAlarm(6)

Parameters

Name Meaning








Possible CausesThe USB controller fault was rectified.

Procedurel This alarm message is informational only, and no action is required.

----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail 132121



127




Attribute



Parameters

Name Meaning








Possible CausesThe I2C bus fault was rectified.


----End




128




Attribute



Parameters

Name Meaning








Possible CausesThe clock fault in the board was rectified.


----End




129




Attribute



Parameters

Name Meaning








Possible CausesThe Phase-Locked Loop (PLL) fault was rectified.


----End




130




Attribute



Parameters

Name Meaning








Possible CausesThe DSP fault was rectified.


----End




131




Attribute



Parameters

Name Meaning








Possible CausesThe chip fault was rectified.


----End




132




Attribute



Parameters

Name Meaning








Possible CausesThe fault in the POS SPF flexible card was rectified.


----End




133




Attribute



Parameters

Name Meaning








Possible CausesThe PoE fault was rectified.


----End




134




Attribute



Parameters

Name Meaning








Possible CausesThe indicator fault was rectified.


----End




135

16.20 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3hwCardFail 135190

Description

ENTITYTRAP/2/CARDFAIL: OID [oid] Card become failure for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])

The available power of a lithium battery is too low.

NOTE

This alarm is available only on the S5700-28P-LI-BAT and S5700-28P-LI-24S-BAT.

Attribute



Parameters

Name Meaning


Index Indicates the alarm index.

EntityPhysicalIndex Indicates the physical entity index.

PhysicalName Indicates the name of the physical entity where the alarm is generated.

EntityTrapEntType Indicates the alarm type.

EntityTrapFaultID Indicates the error code of the alarm.NOTE

The error code of a low power alarm for the lithium battery is 135190.


The low power may affect operation of the lithium battery.

Possible Causes

The lithium battery is supplying power to the device, and the available power of the battery isless than 20%, 10%, or 5% of the full power.



136

Procedure

l The lithium battery can be charged automatically after the power supply of the device isturned on.

----End

Related Information16.23 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4 hwCardFailResume 135190


DescriptionENTITYTRAP/2/CARDFAIL: OID [oid] Card become failure for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])

The temperature of a lithium battery is too low.

NOTE


Attribute



Parameters

Name Meaning







The error code of a low temperature alarm for the lithium battery is 135191.

Impact on the SystemThe low temperature may affect operation of the lithium battery.



137

Possible Causes

The discharge temperature range for a lithium battery is -5°C to 50°C. When the dischargetemperature of the lithium battery is lower than the lower temperature threshold, the systemgenerates a lower temperature alarm.

Procedure

l Increase the ambient temperature.

----End



Description


The discharge temperature of a lithium battery is too high.

NOTE


Attribute



Parameters

Name Meaning








138

Name Meaning


The error code of a high discharge temperature alarm for the lithium battery is135192.


The high discharge temperature may affect operation of the lithium battery.

Possible Causes

The normal discharge temperature for a lithium battery is -5°C to 50°C. If the ambienttemperature exceeds the upper threshold during discharge of the lithium battery, the systemgenerates a high discharge temperature alarm.

Procedure

Step 1 Check whether the air vent for the lithium battery is blocked and whether the fans are runningnormally. Fix the problem (if any) to ensure that fans are running normally.


----End


16.23 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.4hwCardFailResume 135190

Description

ENTITYTRAP/4/CARDFAILRESUME: OID [oid] Card resume from failure.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])

The low power alarm of a lithium battery has been cleared.

NOTE


Attribute


1.3.6.1.4.1.2011.5.25.219.2.3.4 Warning equipmentAlarm(5)



139

Parameters

Name Meaning







The error code of a low power recovery alarm is 135190.


None

Possible Causes

The available power of the lithium battery has increased to more than 20% of its total power.

Procedure

l This alarm is informational only, and no action is required.

----End

Related Information16.20 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.3 hwCardFail 135190


Description


The low temperature alarm of a lithium battery has been cleared.

NOTE




140

Attribute



Parameters

Name Meaning







The error code of low temperature recovery alarm for the lithium battery is135191.


None

Possible Causes

The temperature of the lithium battery has raised above the lower threshold.

Procedure


----End



Description




141

The high discharge temperature alarm of a lithium battery has been cleared.

NOTE


Attribute



Parameters

Name Meaning







The error code of a high discharge temperature recovery alarm for the lithiumbattery is 135192.


Possible CausesThe discharge temperature of the lithium battery has fallen below the upper threshold.

Procedurel This alarm is informational only, and no action is required.

----End




142


Description


The charge temperature of a lithium battery is too high.

NOTE


Attribute



Parameters

Name Meaning







The error code of a high charge temperature alarm for the lithium battery is135193.


The high charge temperature may affect operation of the lithium battery.

Possible Causes

The normal charge temperature for a lithium battery is 0°C to 450°C. If the ambient temperatureexceeds the upper threshold during charge of the lithium battery, the system generates a highcharge temperature alarm.



143

Procedure

Step 1 Check whether the air vent for the lithium battery is blocked and whether the fans are runningnormally. Fix the problem (if any) to ensure that fans are running normally.


----End



Description


The high charge temperature alarm of a lithium battery has been cleared.

NOTE


Attribute



Parameters

Name Meaning







The error code of a high charge temperature recovery alarm for the lithium batteryis 135193.



144


None

Possible Causes

The charge temperature of the lithium battery has fallen below the upper threshold.

Procedure


----End


16.28 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.5hwCardInvalid 135450-135458

Description

ENTITYTRAP/1/CARDINVALID:OID [oid] Card is invalid for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])

A lithium battery has failed.

NOTE


Attribute



Parameters

Name Meaning








145

Name Meaning


The error codes of different lithium battery faults are:

l 135450: The charge switch of the lithium battery is in a short-circuit condition.

l 135451: The charge switch of the lithium battery is in an open-circuitcondition.

l 135452: The discharge switch of the lithium battery is in a short-circuitcondition.

l 135453: The discharge switch of the lithium battery is in an open-circuitcondition.

l 135454: Both the charge and discharge switches of the lithium battery are ina short-circuit condition.

l 135455: Both the charge and discharge switches of the lithium battery are inan open-circuit condition.

l 135456: Other internal faults of the lithium battery.

l 135457: The electrochemical cell of the lithium battery is faulty.

l 135458: An error occurs when the system is collecting temperature of thelithium battery.


The lithium battery may not work normally.

Possible Causes

The lithium battery has an internal fault.

Procedure

l Replace the lithium battery.

----End

Related Information16.30 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume135450-135458

16.29 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5hwCardInvalid 135459

Description

ENTITYTRAP/1/CARDINVALID:OID [oid] Card is invalid for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])



146

The lithium battery's supply time is below threshold value .

NOTE


Attribute



Parameters

Name Meaning






EntityTrapFaultID Indicates the error code of the alarm, which is 13459.

Impact on the SystemIf the lithium battery is not replaced, it may not work normally.

Possible Causesl The lithium battery discharges fast due to internal losses or faults. As a result, the power

supply time of the battery is shorter than the threshold.

Procedurel Replace the lithium battery.

----End

Related Information16.31 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume 135459



147

16.30 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.6hwCardInvalidResume 135450-135458

DescriptionENTITYTRAP/1/CARDINVALIDRESUME: OID [oid] Card resume from invalid situation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])

The faulty lithium battery has been removed.

NOTE


Attribute



Parameters

Name Meaning








148

Name Meaning


The error code depends on the fault that has occurred on the lithium battery:

l 135450: The removed lithium battery has a short-circuit fault on the chargeswitch.

l 135451: The removed lithium battery has an open-circuit fault on the chargeswitch.

l 135452: The removed lithium battery has a short-circuit fault on the dischargeswitch.

l 135453: The removed lithium battery has an open-circuit fault on thedischarge switch.

l 135454: The removed lithium battery has a short-circuit fault on the chargeand discharge switches.

l 135455: The removed lithium battery has an open-circuit fault on the chargeand discharge switches.

l 135456: The removed lithium battery has another type of internal fault.

l 135457: The electrochemical cell of the removed lithium battery is faulty.

l 135458: The removed lithium battery encounters a temperature collectionfailure.

Impact on the SystemIf you do not install a new lithium battery in the device, the device cannot work when the externalpower supply is shut down.

Possible CausesThe faulty lithium battery is removed.

Procedurel Install a new lithium battery in the device.

----End

Related Information16.28 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid 135450-135458

16.31 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6hwCardInvalidResume 135459

DescriptionENTITYTRAP/1/CARDINVALIDRESUME: OID [oid] Card resume from invalid situation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER])



149

The lithium battery whose supply time is below threshold value has been removed.

NOTE


Attribute



Parameters

Name Meaning







Impact on the SystemIf you do not install a new lithium battery in the device, the device cannot work when the externalpower supply is shut down.

Possible CausesThe lithium battery has been removed.

Procedurel Install a new lithium battery in the device.

----End

Related Information16.29 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid 135459

16.32 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.9.1hwCommunicateError 135457

DescriptionENTITYTRAP/4/ENTITYCOMMUNICATEERROR: OID [oid] Communication error hasbeen detected.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER],



150

PhysicalName="[OCTET]", EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER], EntityCommunicateType=[INTEGER])

A lithium battery fails to communicate with the device.

NOTE


Attribute


1.3.6.1.4.1.2011.5.25.219.2.9.1 warning communicationsAlarm(2)

Parameters

Name Meaning




PhysicalName Indicates the name of the physical entity where the alarm isgenerated.



The error code of a communication failure alarm for a lithium battery is135457.

EntityCommunicateType Indicates the type of the communication failure.


The device cannot obtain the working status of the lithium battery.

Possible Causes

The RS232 serial port that the lithium battery uses to communicate with the device has failed.

Procedure

l Unplug and plug the lithium battery several times. If the lithium battery still fails tocommunicate with the device, replace the lithium battery.

----End

Related Information

Entitytrap 1.3.6.1.4.1.2011.5.25.219.2.9.2 hwCommunicateResume 135457



151

16.33 ENTITYTRAP 1.3.6.1.4.1.2011.5.25.219.2.9.2hwCommunicateResume 135457

Description

ENTITYTRAP/4/ENTITYCOMMUNICATERESUME: OID [oid] Resume fromcommunication error situation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER],PhysicalName="[OCTET]", EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER], EntityCommunicateType=[INTEGER])

Communication between a lithium battery and the device resumes.

NOTE


Attribute


1.3.6.1.4.1.2011.5.25.219.2.9.2 warning communicationsAlarm(2)

Parameters

Name Meaning




PhysicalName Indicates the name of the physical entity where the alarm isgenerated.



The error code of a communication recovery alarm for a lithium battery is135457.

EntityCommunicateType Indicates the type of the communication failure.


None

Possible Causes

Communication between a lithium battery and the device resumes.



152

Procedure


----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.9.1 hwCommunicateError 135457

16.34 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.13hwBrdTempAlarm 140544

Description

ENTITYTRAP/1/ENTITYBRDTEMPALARM: OID [oid] Temperature rise over or fall belowthe warning alarm threshold.(Index=[INTEGER], ThresholdEntityPhysicalIndex=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityThresholdType=[INTEGER],EntityThresholdValue=[INTEGER],EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The temperature of the board is higher than the upper threshold.

Attribute


1.3.6.1.4.1.2011.5.25.219.2.10.13 Critical environmentalAlarm(6)

Parameters

Name Meaning



ThresholdEntityPhysicalIndex Indicates the index of the physical entity threshold.

EntityPhysicalIndex Indicates the index of the physical entity.

PhysicalName Indicates the name of the physical entity.

EntityThresholdType Indicates the threshold type of the physical entity.

EntityTrapEntType Indicates the alarm type of the physical entity.

EntityThresholdValue Indicates the threshold value of the physical entity.

EntityThresholdCurrent Indicates the current value of the physical entity.




153

Impact on the SystemThe board is not affected for the moment. Services on the board may be affected if thetemperature becomes too high.

Possible Causesl The hot air in the equipment cannot be exhausted.l The temperature of the environment where the device is located is high.l The number of fans on the device is insufficient.l A fan on the device is faulty.l The temperature of the chip is high.

Procedure

Step 1 Clean the air vent and check whether the alarm is cleared.

1) If yes, go to Step 10.

2) If not, go to Step 2.

Step 2 Check whether the temperature of the environment where the device is located is high.

1) If the temperature of the environment where the device is located is high, go to Step 3.


Step 3 Lower the temperature in the equipment room. Then go to Step 4.

Step 4 Check whether the fans on the device are available.

1) If the fans on the device are available, go to Step 6.


Step 5 Add fans. Then go to Step 6.

Step 6 Run the display fan command to check whether any fan is faulty according to the statusinformation of fans.

1) If a fan is faulty, go to Step 7.


Step 7 Replace the fan that is faulty. Then go to Step 8.

Step 8 Run the display environment command to view the temperature of each board on the device.Check whether the temperature of the chip on the board is high.

1) If the temperature of the chip on the board is high, go to Step 9.


Step 9 Contact Huawei technical personnel.

Step 10 End.

If the following conditions are met, it indicates that the fault is rectified:



154

1. The alarm is not displayed on the NMS.

2. After you run the display trapbuffer command, this alarm is not displayed.

3. After you run the terminal monitor and terminal trapping commands, this alarm is notdisplayed.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.14 hwBrdTempResume 140544

16.35 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.13hwBrdTempAlarm 140545

Description

ENTITYTRAP/1/ENTITYBRDTEMPALARM: OID [oid] Temperature rise over or fall belowthe warning alarm threshold.(Index=[INTEGER], ThresholdEntityPhysicalIndex=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityThresholdType=[INTEGER],EntityThresholdValue=[INTEGER],EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The temperature of the board falls below the lower threshold.

Attribute


1.3.6.1.4.1.2011.5.25.219.2.10.13 Critical environmentalAlarm(6)

Parameters

Name Meaning












155

Name Meaning



The board is not affected for the moment. Services on the board may be affected if thetemperature becomes too low.

Possible Causes

The ambient temperature falls below the upper threshold.

Procedure

Step 1 Test the actual ambient temperature. If the ambient temperature is too low, use the air conditioneror the indoor heating system to increase the temperature.

Step 2 If the ambient temperature is normal, the upper threshold may be set too low. Run the cmu-analog command to lower the lower threshold.

Step 3 End.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.14 hwBrdTempResume 140545

16.36 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.14hwBrdTempResume 140544

Description

ENTITYTRAP/4/ENTITYBRDTEMPRESUME: OID [oid] Temperature back to normal level.(Index=[INTEGER], ThresholdEntityPhysicalIndex=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER],EntityThresholdValue=[INTEGER],EntityThresholdCurrent=[INTEGER],EntityTrapFaultID=[INTEGER])

The temperature of the board is restored to the allowed range.

Attribute


1.3.6.1.4.1.2011.5.25.219.2.10.14 Warning environmentalAlarm(6)



156

Parameters

Name Meaning












Possible CausesThe temperature of the board has been restored to the allowed range.

Procedure


----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.13 hwBrdTempAlarm 140544

16.37 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.14hwBrdTempResume 140545

DescriptionENTITYTRAP/4/ENTITYBRDTEMPRESUME: OID [oid] Temperature back to normal level.(Index=[INTEGER], ThresholdEntityPhysicalIndex=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER],EntityThresholdValue=[INTEGER],EntityThresholdCurrent=[INTEGER],EntityTrapFaultID=[INTEGER])

The temperature of the board is restored to the allowed range.



157

Attribute



Parameters

Name Meaning












None.

Possible Causes

The temperature of the board has been restored to the allowed range.

Procedure


----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.10.13 hwBrdTempAlarm 140545

16.38 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5hwOpticalInvalid 136192



158

Description

ENTITYTRAP/3/OPTICALINVALID:OID [oid] Optical Module is invalid.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=\"[OCTET]\",EntityTrapFaultID=136192)

An optical module installed on the device is not a Huawei-customized optical module.

Attribute


1.3.6.1.4.1.2011.5.25.219.2.4.5 Minor equipmentAlarm(5)

Parameters

Name Meaning







If this optical module was delivered from Huawei early, this alarm does not affect the system.If not, the optical module may not work normally.

Possible Causes

The optical module is not a Huawei-customized optical module. Vendor information of the earlydelivered Huawei optical module is not recorded.

Procedure

Step 1 If this optical module was delivered from Huawei earlier, run the transceiver phony-alarm-disable command to disable the alarm function for non-Huawei customized optical modules.

Step 2 If this optical module is not delivered from Huawei or is not customized for Huawei, replace itwith a Huawei-customized optical module.

----End

Related Information

None



159


Description

ENTITYTRAP/3/OPTICALINVALID:OID [oid] Optical Module is invalid.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=\"[OCTET]\",EntityTrapFaultID=136193)

The transmit power of an optical module is too high.

Attribute



Parameters

Name Meaning







This alarm does not affect system operating if the interface on which the optical module isinstalled works properly.

Possible Causes

The transmit power of the optical module is too high.

Procedure

Step 1 Run the display transceiver slot slot-id verbose command in the system view to check whetherthe transmit power Tx Power of the optical module is within the allowed range.

l If the transmit power is in the allowed range, services are not affected. Collect alarms, logs,and configurations and contact Huawei technical support personnel.

l If the transmit power is out of the allowed range, replace the optical module. Connect anattenuator to the optical module. If the receive power is in the allowed range and services are



160

not affected, the optical module can be used. This alarm alerts you to check the transmitpower of optical modules.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.6 hwOpticalInvalidResume 136193


Description

ENTITYTRAP/3/OPTICALINVALID: OID [oid] Optical Module is invalid.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapFaultID=[INTEGER])

The transmit power of an optical module is too low.

Attribute



Parameters

Name Meaning








Possible Causes

The transmit power of the optical module is too low.



161

Procedure

Step 1 Run the display transceiver slot slot-id verbose command in the system view to check whetherthe transmit power Tx Power of the optical module is within the allowed range.

l If the transmit power is in the allowed range, services are not affected. Collect alarms, logs,and configurations and contact Huawei technical support personnel.

l If the transmit power is out of the allowed range, replace the optical module. This alarm onlyalerts you to check the transmit power of optical modules. Ignore it if services are not affected.

----End

Related Information



Description


The receive power of an optical module is too high.

Attribute



Parameters

Name Meaning






136195 Indicates that the receive power of the optical module is too high.



162



Possible Causes

The receive power is too high.

Procedure

Step 1 Run the display transceiver slot slot-id verbose command in the system view to check whetherthe receive power Rx Power of the optical module is within the allowed range. If so, collectalarms, logs, and configurations, and contact Huawei technical support personnel.

Step 2 Check whether an alarm is generated for high transmit power on the peer optical module. If so,rectify the peer optical module fault first.

Step 3 Check whether the peer optical module and the local optical module are of the same type. If not,replace the local optical module with a new one to ensure they are of the same type.

Step 4 Add -5 dBm (recommended) attenuators to the optical module.

Step 5 If the problem persists after the preceding steps, collect alarms, logs, and configurations, andcontact Huawei technical support personnel.

----End

Related Information



Description


The receive power of an optical module is too low.

Attribute





163

Parameters

Name Meaning








Possible Causes

The receive power of the optical module was too low.

Procedure

Step 1 Run the display transceiver slot slot-id verbose command in the system view to check whetherthe receive power Rx Power of the optical module is within the allowed range. If so, collectalarms, logs, and configurations, and contact Huawei technical support personnel.

Step 2 If no alarm on low receive power is generated and the peer interface is Up, go to step 5.

Step 3 If the peer interface is Down and an alarm on that is generated, rectify the peer interface.

Step 4 Check whether the optical fiber is faulty. If so, replace the optical fiber.

Step 5 Perform an external loopback test on the interface. If the interface is in Up state, performloopback tests on the nodes along the transmission path to locate the failure point or link.

Step 6 Replace the local optical module.

Step 7 If the fault persists after the optical module is replaced, collect alarms, logs, and configurations,and contact Huawei technical support personnel.

----End

Related Information


16.43 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.6hwOpticalInvalidResume 136193



164

Description

ENTITYTRAP/4/OPTICALINVALIDRESUME:OID [oid] Optical Module resume frominvalid situation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=\"[OCTET]\", EntityTrapFaultID=136193)

The optical module has recovered.

Attribute



Parameters

Name Meaning







None.

Possible Causes

The transmit optical power fell below the upper threshold.

Procedure


----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5 hwOpticalInvalid 136193




165

Description

ENTITYTRAP/4/OPTICALINVALIDRESUME: OID [oid] Optical Module resume frominvalid situation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER],PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])


Attribute



Parameters

Name Meaning







None.

Possible Causes

The transmit optical power increased above the lower threshold.

Procedure


----End

Related Information





166

Description



Attribute



Parameters

Name Meaning




PhysicalName Indicates the entity name.



None.

Possible Causes

The receiving optical power fell below the upper threshold.

Procedure


----End

Related Information





167

Description



Attribute



Parameters

Name Meaning







None.

Possible Causes

The receiving optical power increased above the lower threshold.

Procedure


----End

Related Information


16.47 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.1hwPowerRemove 136448



168

Description

ENTITYTRAP/4/POWERREMOVE: OID [oid] Power is absent.(Index=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

The power supply was removed.

Attribute


1.3.6.1.4.1.2011.5.25.219.2.5.1 warning equipmentAlarm(5)

Parameters

Name Meaning







Some boards cannot work properly due to lack of power.

Possible Causes

The power supply was removed.

Procedure

Step 1 Check whether the power supply is installed on the device.

l If yes, go to step 2.

l If no, install the power supply.

Step 2 Check whether the power supply is installed properly.

l If yes but the alarm still exists, replace the power supply.

l If no, insert the power supply properly.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.2 hwPowerInsert 136448



169

16.48 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.2hwPowerInsert 136448

Description

ENTITYTRAP/4/POWERINSERT: OID [oid] Power is present.(Index=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

The power supply was inserted.

Attribute


1.3.6.1, 4.1.2011.5.25.219.2.5.2 warning equipmentAlarm(5)

Parameters

Name Meaning







None.

Possible Causes

The power supply was inserted.

Procedure


----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.1 hwPowerRemove 136448



170

16.49 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.5hwPowerInvalid 136961

DescriptionNOTE

Only S5700LI supports Entitytrap_1.3.6.1.4.1.2011.5.25.219.2.5.5 hwPowerInvalid 136961.

Entitytrap/1/POWERINVALID(t):OID [oid] Power is invalid for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=\"[OCTET]\",EntityTrapFaultID=136961)

The power supply is invalid.

Attribute



Parameters

Name Meaning




PhysicalName Indicates the entity name, such as SFU, LPU, and MPU. The entity namevaries with the type of the board.




Boards may fail to be powered on due to insufficient power supply

Possible Causes

Power module fault.

Procedure

Step 1 Check whether the power supply is working properly.

----End



171

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume_136961


DescriptionENTITYTRAP/1/POWERINVALID: OID [oid] Power is invalid for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapFaultID=[INTEGER])"


Attribute



Parameters

Name Meaning







Impact on the SystemBoards may fail to be powered on due to insufficient power supply

Possible CausesThe power supply was installed but not powered on.

Procedure

Step 1 Power on the power module.

----End



172

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume_136966


Description

ENTITYTRAP/1/POWERINVALID: OID [oid] Power is invalid for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapFaultID=[INTEGER])"


Attribute



Parameters

Name Meaning








Boards may fail to be powered on due to insufficient power supply.

Possible Causes

The type of the PoE power supply is incorrect.

Procedure

Step 1 Check whether a DC power supply is installed in the PoE power supply slot. If so, replace itwith an AC power supply.



173

Step 2 If an AC power supply is installed in the PoE power supply slot, the AC power supply is faulty.Contact Huawei technical personnel.

Step 3 If no power supply is installed in the PoE power supply slot, contact Huawei technical personnel.

----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume_136972


DescriptionENTITYTRAP/1/POWERINVALID: OID [oid] Power is invalid for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapFaultID=[INTEGER])"


Attribute



Parameters

Name Meaning







Impact on the SystemThe device may fail to be powered on due to insufficient power supply.

Possible CausesThe power supply of the system is incorrectly installed.



174

NOTE

The S5710EI uses 1150 W and 580 W PoE power supplies. If other power supplies are installed on the device,this alarm is generated.

Procedure

Step 1 Ensure that the power supply is working properly.

Step 2 Ensure that the power supplies installed on the device are of the same type.

Step 3 If all power supplies are DC power supplies, ensure that they are installed and configuredcorrectly. For example, check whether they are working in 1+1 backup mode.

Step 4 If the configurations of the power supplies meet the requirements but the alarm still exists,contact Huawei technical personnel.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume 136973

16.53 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.6hwPowerInvalidResume 136961

DescriptionNOTE

Only S5700LI supports Entitytrap_1.3.6.1.4.1.2011.5.25.219.2.5.6 hwPowerInvalidResume 136961.

Entitytrap/4/POWERINVALIDRESUME(t):OID [oid] Power resume from invalid situation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=\"[OCTET]\",EntityTrapFaultID=136961)

The power supply has recovered.

Attribute



Parameters

Name Meaning






175

Name Meaning





Possible CausesThe working power supply of the switch failed and then the switch was powered by the standbyRPS power module.

Procedure


----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.5 hwPowerInvalid 136961


DescriptionENTITYTRAP/4/POWERINVALIDRESUME: OID [oid] Power resume from invalidsituation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapFaultID=[INTEGER])"


Attribute





176

Parameters

Name Meaning








None.

Possible Causes

The fault in which the power supply was installed but not powered on was rectified.

Procedure


----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.5.5 hwPowerInvalid 136966


Description

ENTITYTRAP/4/POWERINVALIDRESUME: OID [oid] Power resume from invalidsituation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapFaultID=[INTEGER])"


Attribute





177

Parameters

Name Meaning








None.

Possible Causes

The fault of the improper PoE power supply type was rectified.

Procedure


----End

Related Information



Description

ENTITYTRAP/4/POWERINVALIDRESUME: OID [oid] Power resume from invalidsituation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapFaultID=[INTEGER])"


Attribute





178

Parameters

Name Meaning








None.

Possible Causes

The fault in which the power supply of the system was incorrectly installed was rectified.

Procedure


----End

Related Information


16.57 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.1hwFanRemove 137216

Description

ENTITYTRAP/4/FANREMOVE: OID [oid] Fan has been removed.(Index=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])"

The fan is not installed properly.

Attribute





179

Parameters

Name Meaning






Impact on the SystemThe temperature of the device will increase due to deterioration of heat dissipation performance.Services are not affected in a short time, but the fault should be rectified quickly.

Possible CausesThe fan was removed or not installed properly.

Procedure

Step 1 Check whether the fan is installed well.l If yes, replace the fan.l If no, install the fan well.

----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.2 hwFanInsert 137216

16.58 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.2hwFanInsert 137216

DescriptionENTITYTRAP/4/FANINSERT: OID [oid] Fan has been inserted.(Index=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

The fan is installed correctly.



180

Attribute



Parameters

Name Meaning







None.

Possible Causes

The fan was installed.

Procedure


----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.1 hwFanRemove 137216

16.59 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.5hwFanInvalid 139264

Description

ENTITYTRAP/1/FANINVALID: OID [oid] Fan is invalid.(Index=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

The fan is invalid.



181

Attribute



Parameters

Name Meaning







Boards fail to work properly due to increased temperature. For example, packet loss may occuror even seriously, the device may be suspended or reset.

Possible Causes

The hardware of the fan is faulty.

Procedure

Step 1 Check whether the fan is installed well.

l If yes, replace the fan.

l If no, install the fan properly.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.6 hwFanInvalidResume 139264

16.60 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.6.6hwFanInvalidResume 139264

Description

ENTITYTRAP/4/FANINVALIDRESUME: OID [oid] Fan resume from invalid situation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]",EntityTrapFaultID=[INTEGER])



182

The fan has recovered.

Attribute



Parameters

Name Meaning







None.

Possible Causes

The hardware of the fan has recovered.

Procedure


----End

Related Information

ENTITYTRAP_1.3.6.1, 4.1.2011.5.25.219.2.6.5 hwFanInvalid 139264

16.61 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.1hwCardRemove

Description

Entitytrap/4/CARDREMOVE(t):OID [oid] Card has been removed.(Index=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName=[OCTET], EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER])

The subcard was removed.



183

Attribute



Parameters

Name Meaning

OID Indicates the MIB object ID.

Index Indicates the entity index.


PhysicalName Indicates the entity name, such as SFU, LPU, and MPU. The entity namevaries with the board type.




The subcard was unavailable and all services on the subcard were interrupted.

Possible Causes

The subcard was removed.

Procedure

l Install the subcard.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.2 hwCardInsert

16.62 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.2hwCardInsert

Description

Entitytrap/4/CARDINSERT(t):OID [oid] Card has been inserted.(Index=[INTEGER],EntityPhysicalIndex=[INTEGER], PhysicalName=[OCTET], EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER])

The subcard was inserted.



184

Attribute



Parameters

Name Meaning

OID Indicates the MIB object ID.

Index Indicates the entity index.


PhysicalName Indicates the entity name, such as SFU, LPU, and MPU. The entity namevaries with the board type.




None.

Possible Causes


Procedure

l This alarm is informational and no action is required.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.1 hwCardRemove

16.63 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5hwCardInvalid

Description

ENTITYTRAP/1/CARDINVALID:OID [oid] Card is invalid for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=[OCTET],EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER])

A subcard is installed in an incorrect subcard slot, and the system considers the subcard invalid.



185

Attribute



Parameters

Name Meaning

oid Indicates the ID of the alarm MIB object.

Index Indicates the alarm ID.

EntityPhysicalIndex Indicates the index of the physical entity where the alarm is reported.

PhysicalName Indicates the physical entity name.


EntityTrapFaultID Indicates the error code of the alarm.


None

Possible Causes

The subcard type does not match the slot type, and the subcard cannot be used in this slot.

Procedure

Step 1 Install the subcard to the matching slot.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6 hwCardInvalidResume

16.64 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.6hwCardInvalidResume

Description

ENTITYTRAP/1/CARDINVALIDRESUME:OID [oid] Card resume from invalid situation.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=[OCTET],EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER])

An originally invalid subcard recovers and can be used normally.



186

Attribute



Parameters

Name Meaning








Possible CausesThe subcard is installed in a correct slot and can be used normally.

Procedure

Step 1 This alarm is informational, and no action is required.

----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.3.5 hwCardInvalid.xml

16.65 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.1hwCPUUtilizationRising

DescriptionENTITYTRAP/4/ENTITYCPUALARM:OID [oid] CPU utilization exceeded the pre-alarmthreshold.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=[OCTET],EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER],EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER].)

The CPU usage exceeds the alarm threshold.



187

Attribute



Parameters

Name Meaning





EntityThresholdType Indicates the alarm type.

EntityThresholdValue Indicates the alarm threshold.

EntityThresholdCurrent Indicates the current CPU usage.



The high CPU usage will delay processing of some services.

Possible Causes

The CPU usage of the device exceeds the alarm threshold.

Procedure

Step 1 Some services can cause a high CPU usage in a period of time. Normally, the CPU usage willrestore to the normal range after a while.

----End

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.2 hwCPUUtilizationResume

16.66 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.2hwCPUUtilizationResume

Description

ENTITYTRAP/4/ENTITYCPURESUME:OID [oid] CPU utilization recovered to the normalrange.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=[OCTET],



188

EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER],EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER].)

The CPU usage falls below the alarm threshold.

Attribute



Parameters

Name Meaning







EntityThresholdCurrent Indicates the current CPU usage.



Possible CausesThe CPU usage falls below the alarm threshold.

Procedure


----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.1 hwCPUUtilizationRising



189

16.67 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.15.1hwMemUtilizationRising

DescriptionENTITYTRAP/4/ENTITYMEMORYALARM:OID [oid] Memory usage exceeded thethreshold. (Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=[OCTET],EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER],EntityThresholdCurrent=[INTEGER],EntityTrapFaultID=[INTEGER].)

The memory usage exceeds the alarm threshold.

Attribute



Parameters

Name Meaning







EntityThresholdCurrent Indicates the current memory usage.


Impact on the SystemThe high memory usage will delay processing of some services.

Possible CausesThe memory usage of the device exceeds the alarm threshold.

Procedure

Step 1 Some services can cause a high memory usage in a period of time. Normally, the memory usagewill restore to the normal range after a while.

----End



190

Related Information

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.15.2 hwMemUtilizationResume

16.68 ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.15.2hwMemUtilizationResume

Description

ENTITYTRAP/4/ENTITYMEMORYRESUME:OID [oid] Memory usage recovered to thenormal range.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName=[OCTET], EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER],EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER].)

The memory usage falls below the alarm threshold.

Attribute



Parameters

Name Meaning







EntityThresholdCurrent Indicates the current memory usage.



None

Possible Causes

The memory usage falls below the alarm threshold.



191

Procedure


----End

Related InformationENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.15.1 hwMemUtilizationRising



192

17 ENTMIB

About This Chapter

17.1 ENTMIB_1.3.6.1.2.1.47.2.0.1 entConfigChange

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 17 ENTMIB


193

17.1 ENTMIB_1.3.6.1.2.1.47.2.0.1 entConfigChange

DescriptionENTMIB/4/TRAP: OID [oid] Entity MIB change.

The MIB information changes because an entity in a device is installed, removed, reset, orregistered.

Attribute


1.3.6.1.2.1.47.2.0.1 Warning equipmentAlarm(5)

Parameters

Name Meaning



Possible CausesAn entity (a board or a subcard) on a device is installed, removed, reset, or registered.

Procedure

Step 1 This is a normal notification and no action is required.

----End


S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 17 ENTMIB


194

18 EOAM1AG

About This Chapter

18.1 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.1 hwDot1agCfmFaultAlarm

18.2 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.32 hwDot1agCfmUnexpectedMEGLevel

18.3 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.33hwDot1agCfmUnexpectedMEGLevelCleared

18.4 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.34 hwDot1agCfmMismerge

18.5 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.35 hwDot1agCfmMismergeCleared

18.6 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.36 hwDot1agCfmUnexpectedMEP

18.7 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.37 hwDot1agCfmUnexpectedMEPCleared

18.8 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.38 hwDot1agCfmUnexpectedPeriod

18.9 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.39 hwDot1agCfmUnexpectedPeriodCleared

18.10 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.40 hwDot1agCfmUnexpectedMAC

18.11 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.41 hwDot1agCfmUnexpectedMACCleared

18.12 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.42 hwDot1agCfmLOC

18.13 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.43 hwDot1agCfmLOCCleared

18.14 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.44 hwDot1agCfmExceptionalMACStatus

18.15 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.45hwDot1agCfmExceptionalMACStatusCleared

18.16 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.46 hwDot1agCfmRDI

18.17 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.47 hwDot1agCfmRDICleared

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 18 EOAM1AG


195

18.1 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.1hwDot1agCfmFaultAlarm

Description

EOAM1AG/4/CCFAULTALARM:OID [oid] MEP is disconnected or reconnected with one ormore MEPs. (CfmMdIndex=[GAUGE], CfmMaIndex=[GAUGE], RmepId=[GAUGE],CfmMdIndex=[GAUGE], CfmMdIndex=[GAUGE], CfmMaIndex=[GAUGE], Dmac=[OPAQUE], HighestDefect=[INTEGER], MdName=[STRING], MdLevel=[INTEGER],MaName=[STRING])

This trap is used to indicate ink connectivity. The trap was generated when the link connectivityis restored. The trap was also generated in the following situations:

l The CC packets from the RMEP could not match the local MAID.

l Incorrect CC packets were received from the RMEP.

l The local MEP did not receive the CC packets from the RMEP.

l The CC packets from the RMEP carried information about RDI.

Attribute


1.3.6.1.4.1.2011.5.25.136.1.6.1 Warning communicationsAlarm(2)

Parameters

Name Meaning


CfmMdIndex Indicates the index of an MD table.

CfmMaIndex Indicates the index of an MA table.

RmepId Indicates the ID of a remote MEP.



CfmMaIndex Indicates the index of an MA table.

Dmac Indicates the destination MAC address.

HighestDefect Indicates the tap of the highest level.

MdName Indicates the name of the MD.

MdLevel Indicates the level of the MD.

MaName Indicates the name of the MA.



196

Impact on the SystemThis trap is generated only when the connectivity of a link is faulty (for example, a physical orlogical link is faulty) and services may be seriously affected.

Possible Causes1. The fault was rectified.

2. An RMEP detected link faulty.

3. The CC packets were not received from the RMEP within three periods.

4. The transmission frequency set on both MEPs was inconsistent, or an incorrect MAC addresswas assigned to the RMEP.

5. The MD, MA, and MEP were incorrectly configured.

Procedure

Step 1 If IEEE 802.1ag Draft 7 runs on the entire network, do as follows:

1. Check the alarm severity in the HighestDefect field:l If it is Level 6, go to 1.2.l If it is Level 5, go to 1.3.l If it is Level 4, go to 1.4.l If it is Level 2, go to 1.5.l If it is Level 0, go to 1.13.

Level 0 indicates that the fault is rectified.2. If it is a Level 6 alarm, it indicates that the MD name and MA name in CC packets from

the RMEP are different from the local MD name and MA name. Run the display thiscommand in the MD view to check whether the MD name and MA name configured onthe local device are consistent with the MD name and MA name configured on the remotedevice.l If so, go to 1.12.l If not, go to 1.6.

3. If it is a Level 5 alarm, it indicates that the transmission frequencies set on both MEPs areinconsistent, or an incorrect MAC address is assigned to the RMEP. Run the display cfmma [ md md-name [ ma ma-name ] ] command to check whether the local and remotedevices are configured with the same interval for CC detection.l If so, go to 1.9.l If not, go to 1.8.

4. If it is a Level 4 alarm, it indicates that the local MEP does not receive the CC packet fromthe RMEP or the MD levels configured on the two ends are different. Run the pingmac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ interface { interface-name | interface-type interface-num } | -c count | -s packetsize | -t timeout ] * command tocheck whether the Ping Echo packet expires, which indicates whether the link worksproperly.l If so, go to 1.12.



197

l If not, go to 1.11.

5. If it is a Level 2 alarm, it indicates that the RMEP detects a fault. Run the pingmac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ interface { interface-name | interface-type interface-num } | -c count | -s packetsize | -t timeout ] * command tocheck whether the Ping Echo packet expires, which indicates whether the link worksproperly.

l If so, go to 1.12.


6. Run the cfm md md-name [ level level ] command in the system view to configure thename for the MD. Then, check whether the alarm is cleared.



7. Run the ma ma-name command in the MD view to configure the name for the MA. Then,check whether the alarm is cleared.



8. Run the ccm-interval interval command in the MA view to configure the interval for CCdetection as required. Then, check whether the alarm is cleared.



9. Run the display cfm remote-mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ]command to check whether the MAC address of the remote device is consistent with theMAC address of the RMEP configured on the local device.



10. Run the remote-mep mep-id mep-id [ mac mac-address ] command in the MA view toconfigure the bridge MAC address of the device on which the RMEP is located as required.Then, check whether the alarm is cleared.



11. Run the trace mac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ ttl ttl-value | interface { interface-name | interface-type interface-num } |-t timeout ] * commandto locate the specific device that does not respond to the Ping packet. After locating thefault, rectify it. Then, check whether the alarm is cleared.



12. Collect trap messages, log messages, and configurations, and then contact the Huaweitechnical support personnel.

13. End.

Step 2 If IEEE Standard 802.1ag-2007 runs on the entire network, do as follows:

1. Check the alarm severity in the HighestDefect field:

l If it is Level 5, go to 2.2.



198





Level 0 indicates that the fault is rectified.

2. If it is a Level 5 alarm, it indicates that the MD name and MA name in CC packets fromthe RMEP do not match the local MD name and MA name; or CCM packet leakage occurs.Run the display this command in the MD view to check whether the MD name and MAname configured on the local device are consistent with the MD name and MA nameconfigured on the remote device.



3. If it is a Level 4 alarm, it indicates that the transmission frequencies set on both MEPs areinconsistent, or an incorrect MAC address is assigned to the RMEP. Run the display cfmma [ md md-name [ ma ma-name ] ] command to check whether the local and remotedevices are configured with the same interval for CC detection.



4. If it is a Level 3 alarm, it indicates that the local MEP does not receive CC packets fromthe RMEP. Run the ping mac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ interface { interface-name | interface-type interface-num } | -c count | -s packetsize| -t timeout ] * command to check whether the Ping Echo packet expires, which indicateswhether the link works properly.



5. If it is a Level 1 alarm, it indicates that the RMEP detects a fault. Run the pingmac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ interface { interface-name | interface-type interface-num } | -c count | -s packetsize | -t timeout ] * command tocheck whether the Ping Echo packet expires, which indicates whether the link worksproperly.



6. Run the cfm md md-name [ level level ] command in the system view to configure thename for the MD. Then, check whether the alarm is cleared.



7. Run the ma ma-name command in the MD view to configure the name for the MA. Then,check whether the alarm is cleared.



8. Run the ccm-interval interval [ mac mac-address ] command in the MA view to configurethe interval for CC detection as required. Then, check whether the alarm is cleared.




199


9. Run the display cfm remote-mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ]command to check whether the MAC address of the remote device is consistent with theMAC address of the RMEP configured on the local device.



10. Run the remote-mep mep-id mep-id command in the MA view to configure the bridgeMAC address of the device on which the RMEP is located as required. Then, check whetherthe alarm is cleared.



11. Run the trace mac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ ttl ttl-value | interface { interface-name | interface-type interface-num } |-t timeout ] * commandto locate the specific device that does not respond to the Ping packet. After locating thefault, rectify it. Then, check whether the alarm is cleared.



12. Run the display cfm error-info [ interface interface-type interface-number ] [ vlanvlanid ] [ error-type { ccm-interval-error | maid-error | mac-error | cfm-leak } ]command to check whether CCM packet leakage occurs.



13. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] commandto check whether the MEP is configured.



14. Run one of the following commands in the MA view as required:

l Run the mep mep-id mep-id interface { interface-type interface-number | interface-type interface-number.subnumber } [ vlan vlan-id ] { inward | outward } command tocreate an interface-based MEP.

l Run the mep mep-id mep-id vlan command to create a VLAN-aware MEP.

Then, check whether the alarm is cleared.



15. Collect trap messages, log messages, and configurations, and then contact the Huaweitechnical support personnel.

16. End.

----End

Related Information

None



200

18.2 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.32hwDot1agCfmUnexpectedMEGLevel

Description

EOAM1AG/1/UNEXPECTEDMEGLEVEL: OID [oid] MEP received a CCM with unexpectedMEG level. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER])

The MD level carried in a CCM sent by the RMEP was different from that specified on the MEP.

Attribute


1.3.6.1.4.1.2011.5.25.136.1.6.32 Critical communicationsAlarm(2)

Parameters

Name Meaning

oid OID of a MIB object

MdIndex Index of an MD table

MaIndex Index of an MA table

MdName Name of an MD

MaName Name of an MA

MepId ID of a MEP


CFM will fail.

Possible Causes

The MD level carried in a CCM sent by the RMEP was different from that specified on the MEP.

Procedure

Step 1 Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command on boththe MEP and RMEP to view the value of the Level field. Check whether the MD levels are thesame.

l If the MD levels are different, go to Step 2.

l If the MD levels are the same, go to Step 3.



201

Step 2 Perform the following steps on the MEP:

1. Run the undo cfm md name md-name command to delete existing MD configurations.

2. Run the cfm md md-name level level command to reconfigure an MD the same as that onthe RMEP.

3. Run the display alarm active command to view the trap. Check whether the trap is cleared.If the trap persists, go to Step 3.

Step 3 Collect the trap information and contact Huawei technical support personnel.

----End

18.3 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.33hwDot1agCfmUnexpectedMEGLevelCleared

Description

EOAM1AG/1/UNEXPECTEDMEGLEVELCLEARED: OID [oid] MEP did not receive anyCCM with unexpected MEG level before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE],MdName=[STRING], MaName=[STRING], MepId=[INTEGER])

The trap about inconsistency between the MD level carried in a CCM sent by the RMEP andthat specified on the MEP was cleared.

Attribute



Parameters

Name Meaning






MepId ID of a MEP


System performance will not be affected.



202

Possible CausesThe MEP received a CCM carrying the MD level the same as that specified on the MEP.

Procedurel This trap message is informational only, and no action is required.

----End

18.4 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.34hwDot1agCfmMismerge

DescriptionEOAM1AG/1/MISMERGE: OID [oid] MEP received a CCM with unexpected MEG ID.(MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING],MepId=[INTEGER]).

An MD or MA name carried in a CCM sent by the RMEP was different from that specified onthe MEP.

Attribute



Parameters

Name Meaning






MepId ID of a MEP

Impact on the SystemCFM will fail.

Possible CausesAn MD or MA name carried in a CCM sent by the RMEP was different from that specified onthe MEP when the MEP and RMEP had the same MD level and service type in a MEG.



203

Procedure

Step 1 Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command to viewthe value of the MD Name field on the MEP and RMEP that have the same service type andMD level. Check whether the MD names are the same.

l If they are the same, go to Step 2.l If they are different, go to Step 3.

Step 2 Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command to viewthe value of the MA Name field on the MEP and RMEP that have the same service type, MDlevel, and MD name. Check whether the MA names are the same.l If they are the same, go to Step 5.l If they are different, go to Step 4.

Step 3 Perform the following steps on the MEP:1. Run the undo cfm md name md-name command to delete existing MD configurations.2. Run the cfm md md-name level level command to reconfigure an MD the same as that on

the RMEP.3. Run the display alarm active command to view the trap. Check whether the trap is cleared.

If the trap persists, go to Step 5.

Step 4 Perform the following steps on the MEP:1. Run the undo ma name ma-name command to delete existing MA configurations.2. Run the ma name ma-name command to reconfigure an MA the same as that on the RMEP.3. Run the display alarm active command to view the trap. Check whether the trap is cleared.

If the trap persists, go to Step 5.


----End

18.5 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.35hwDot1agCfmMismergeCleared

DescriptionEOAM1AG/1/MISMERGECLEARED: OID [oid] MEP did not receive any CCM withunexpected MEG ID before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER]).

The trap about inconsistency between the MD or MA name carried in a CCM sent by the RMEPand that specified on the MEP was cleared.



204

Attribute



Parameters

Name Meaning






MepId ID of a MEP

Impact on the SystemSystem performance will not be affected.

Possible CausesThe MEP received a CCM carrying an MD or MA name the same as that specified on the MEP.


----End

18.6 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.36hwDot1agCfmUnexpectedMEP

DescriptionEOAM1AG/3/UNEXPECTEDMEP: OID [oid] MEP received a CCM with unexpected MEP.(MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING],MepId=[INTEGER])

The MEP ID carried in a CCM sent by the RMEP was not listed in the RMEP list of the MEP.



205

Attribute



Parameters

Name Meaning






MepId ID of a MEP


CFM will fail.

Possible Causes

The MEP ID carried in a received CCM was not listed in the RMEP list of the MEP when theMEP and RMEP have the same MD level and MA ID.

Procedure

Step 1 Run the display cfm remote-mep [ md md-name ma ma-name mep-id mep-id ] command onthe MEP to view the value of the RMEP ID field. Check whether the RMEP ID is displayed inthe command output.

l If the RMEP ID is displayed and the fault persists, go to Step 3.

l If the RMEP ID is not displayed, go to Step 2.


1. Run the remote-mep mep-id mep-id [ mac mac-address ] command to specify a correctRMEP.



----End



206

18.7 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.37hwDot1agCfmUnexpectedMEPCleared

DescriptionEOAM1AG/3/UNEXPECTEDMEPCLEARED: OID [oid] MEP did not receive any CCM withunexpected MEP before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER])

The trap about the event that a MEP ID in a CCM sent by the RMEP was not listed in the RMEPlist of the MEP was cleared.

Attribute



Parameters

Name Meaning






MepId ID of a MEP


Possible CausesThe MEP received a CCM carrying a MEP ID that was listed in the local RMEP list under thefollowing conditions:

l The MEP and RMEP had the same MD level.l The MEP and RMEP had the same MA ID.


----End



207

18.8 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.38hwDot1agCfmUnexpectedPeriod

DescriptionEOAM1AG/3/UNEXPECTEDPERIOD: OID [oid] MEP received a CCM with unexpectedperiod. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The CCM interval carried in a CCM sent by the RMEP was different from that specified on theMEP.

Attribute



Parameters

Name Meaning






MepId ID of a MEP

RmepId ID of an RMEP

Impact on the SystemCFM will fail.

Possible CausesThe CCM interval carried in a CCM sent by the RMEP was different from that specified on theMEP in the scenario where the MEP and RMEP had the same MD level and MA ID, and theMEP was enabled to receive CCMs carrying the specified RMEP ID.

Procedure

Step 1 Run the display cfm ma [ md md-name [ ma ma-name ] ] command to view the value of theInterval field on the MEP and RMEP. Check whether the intervals configured on the MEP andRMEP are the same.



208

l If they are the same, go to Step 3.l If they are different, go to Step 2.

Step 2 Perform the following steps on the MEP:1. Run the cfm md md-name command to enter the MD view.2. Run the display this command. Check whether the mep ccm-send enable command has

been run to enable the MEP to send CCMs and the remote-mep ccm-receive enablecommand has been run to enable the MEP to receive CCMs.

3. If the mep ccm-send enable command has been run, run the undo mep ccm-sendenable command to disable the MEP from sending CCMs.

4. If the remote-mep ccm-receive enable command has been run, run the undo remote-mepccm-receive enable command to disable the MEP from receiving CCMs.

5. Run the ccm-interval interval command to configure the interval between CCMs the sameas the interval configured on the RMEP. Then run the remote-mep ccm-receive enablecommand to enable the MEP to receive CCMs and the mep ccm-send enable commandto enable the MEP to send CCMs.



----End

18.9 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.39hwDot1agCfmUnexpectedPeriodCleared

DescriptionEOAM1AG/3/UNEXPECTEDPERIODCLEARED: OID [oid] MEP did not receive any CCMwith unexpected period before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The trap about inconsistency between the CCM interval specified on the MEP and that carriedin a CCM sent by the RMEP was cleared.

Attribute



Parameters

Name Meaning





209

Name Meaning




MepId ID of a MEP




Possible Causes

The MEP received a CCM sent by the RMEP within a specified period of time and the intervalcarried in the CCM and that specified on the MEP were the same under the following conditions:

l The MEP and RMEP had the same MD level.

l The MEP and RMEP had the same MA ID.

l The MEP ID carried in the received CCMs was listed in the RMEP list on the MEP.

l The MEP was enabled to receive CCMs.

Procedure


----End

18.10 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.40hwDot1agCfmUnexpectedMAC

Description

EOAM1AG/3/UNEXPECTEDMAC: OID [oid] MEP received a CCM with unexpected MACaddress. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The source MAC address carried in a CCM sent by the RMEP was different from the RMEP'sMAC address specified on the MEP.

Attribute





210

Parameters

Name Meaning






MepId ID of a MEP



CFM will fail.

Possible Causes

The source MAC address carried in a CCM sent by the RMEP was different from the RMEP'sMAC address specified on the MEP under the following conditions:





l The MEP and RMEP had the same interval at which CCMs were sent.

Procedure

Step 1 Perform the following steps:

1. Run the cfm md md-name command on the MEP to enter the MD view.

2. Run the display this command on the MEP to view the RMEP's MAC address.

3. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] commandon the RMEP to view the value of the MAC field.

4. Check whether the value of the MAC field on the RMEP is the same as the RMEP's MACaddress on the MEP.

l If they are the same, go to Step 3.

l If they are different, go to Step 2.


1. Run the undo remote-mep mep-id mep-id command to delete the existing RMEPconfiguration.

2. Run the remote-mep mep-id mep-id mac mac-address command to specify the correctMAC address of the RMEP.



211



----End

18.11 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.41hwDot1agCfmUnexpectedMACCleared

Description

EOAM1AG/3/UNEXPECTEDMACCLEARED: OID [oid] MEP did not receive any CCM withunexpected MAC address before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE],MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The trap about inconsistency between the source MAC address carried in a CCM sent by theRMEP and the RMEP's MAC address specified on the MEP was cleared.

Attribute



Parameters

Name Meaning






MepId ID of a MEP




Possible Causes

The MEP received a CCM carrying the source MAC address the same as the RMEP's MACaddress specified on the MEP under the following conditions:



212





l The MEP and RMEP had the same interval at which CCMs were sent.

Procedure


----End

18.12 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.42hwDot1agCfmLOC

Description

EOAM1AG/1/LOC: OID [oid] MEP is disconnected with the remote MEP. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The MEP received no CCM in a period of time 3.5 times the interval at which CCMs were sent.

Attribute



Parameters

Name Meaning






MepId ID of a MEP






213

Possible Causes

The MEP received no CCM in a period of time 3.5 times the interval at which CCMs were sent.

Procedure

Step 1 Perform the following operations to check the network operating status on the MEP:

1. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] commandto view the value of the Interface Name field. Obtain the interface type and number.

2. Run the display interface interface-type interface-num command with the obtainedinterface type and number specified. View the value of the current state field.

l If the value of the current state field is Up, go to Step 2.

l If the value of the current state field is not Up, the interface connection fails. For thetroubleshooting procedure, see "Physical Interconnection Troubleshooting."

Step 2 Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command to viewthe value of the CCM Send field on the RMEP. Check whether the RMEP is enabled to sendCCMs.

l If the value of the CCM Send field is enabled, go to Step 4.

l If the value of the CCM Send field is disabled, go to Step 3.

Step 3 Perform the following steps on the RMEP:

1. Run the cfm md md-name command to enter the MD view.

2. Run the ma ma-name command to enter the MA view.

3. Run the mep ccm-send enable command to enable the RMEP to send CCMs. Checkwhether the trap is cleared. If the trap persists, go to Step 4.

Step 4 Run the display cfm remote-mep [ md md-name ma ma-name mep-id mep-id ] command toview the value of the CCM Receive field on the MEP.

l If the value of the CCM Receive field is enabled, go to Step 6.

l If the value of the CCM Receive field is disabled, go to Step 5.


1. Run the cfm md md-name command to enter the MD view.

2. Run the ma ma-name command to enter the MA view.

3. Run the remote-mep ccm-receive enable command to enable the MEP to receive CCMs.Check whether the trap is cleared. If the trap persists, go to Step 6.


----End

18.13 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.43hwDot1agCfmLOCCleared



214

Description

EOAM1AG/1/LOCCLEARED: OID [oid] MEP is reconnected with the remote MEP.(MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING],MepId=[INTEGER], RmepId=[INTEGER])

The MEP received a CCM within a period of time 3.5 times the interval at which CCMs weresent.

Attribute



Parameters

Name Meaning






MepId ID of a MEP




Possible Causes

The MEP received a CCM within a period of time 3.5 times the interval at which CCMs weresent, and CFM was successful.

Procedure


----End

18.14 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.44hwDot1agCfmExceptionalMACStatus



215

Description

EOAM1AG/2/EXCEPTIONALMACSTATUS: OID [oid] MEP received a CCM with the PortStatus TLV or Interface Status TLV reporting an error status. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

TLV information carried in a CCM sent by the RMEP within a specified interval showed thatthe interface connecting the RMEP to the MEP became abnormal.

Attribute



Parameters

Name Meaning






MepId ID of a MEP




Possible Causes

TLV information carried in a CCM sent by the RMEP within a specified interval showed thatthe interface connecting the RMEP to the MEP became abnormal.

Procedure

Step 1 Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command on theRMEP to view the values of the Interface Name and Direction fields. Obtain the interface typeand number and check the value of the Direction field.

l If the value of the Direction field is inward, go to Step 2.

l If the value of the Direction field is outward, go to Step 4.




216

l Run the interface interface-type interface-number command with the obtained interface typeand number specified to enter the interface view.

l Run the display this interface command to view the value of the current state field.

– If the value of the current state field is Up, go to Step 5.

– If the value of the current state field is not Up, go to Step 3.

Step 3 Run the display interface interface-type interface-number command to view the value of thecurrent state field on the RMEP.

l If the value of the current state field is Administratively DOWN, go to Step 4.

l If the value of the current state field is not Administratively DOWN, go to Step 6.


l Run the interface interface-type interface-number command to enter the interface view.

l Run the undo shutdown command to restart the interface. Check whether the trap is cleared.If the trap persists, go to Step 5.

Step 5 Run the display stp brief command to view the value of the STP State field. The STP Statefield is related to the Interface Name field that shows the same interface type and number asthose obtained in step 1.

l If the value of the STP State field is DISCARDING, an MSTP fault occurred. Fortroubleshooting procedure, see the chapter "MSTP Troubleshooting" in theS2750&S5700&S6700 Troubleshooting - L2 Network.

l If the value of the STP State field is FORWARDING, go to Step 6.


----End

18.15 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.45hwDot1agCfmExceptionalMACStatusCleared

Description

EOAM1AG/2/EXCEPTIONALMACSTATUSCLEARED: OID [oid] MEP received a CCMwith the Port Status TLV or Interface Status TLV reporting an error status cleared. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

TLV information carried in a CCM sent by the RMEP within a specified interval showed thatthe interface connecting the RMEP to the MEP was restored.

Attribute





217

Parameters

Name Meaning






MepId ID of a MEP




Possible Causes

TLV information carried in a CCM sent by the RMEP showed that the interface connecting theRMEP to the MEP was restored.

Procedure


----End

18.16 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.46hwDot1agCfmRDI

Description

EOAM1AG/3/RDI: OID [oid] MEP received a CCM with RDI flag set. (MdIndex=[GAUGE],MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER],RmepId=[INTEGER])

The RMEP sent a CCM carrying the RDI flag with the value of 1 to the MEP.

Attribute





218

Parameters

Name Meaning






MepId ID of a MEP




Possible Causes

Cause 1: If an RMEP received a non-RDI trap, the RMEP set the RDI flag to 1 in a CCM andsent the CCM to the MEP.

Cause 2: If CFM association was enabled and an associated interface or protocol notified theRMEP of a detected fault, the RMEP set the RDI flag to 1 in a CCM and sent the CCM to theMEP.

Procedure

Step 1 Run the display cfm remote-mep [ md md-name ma ma-name mep-id mep-id ] command onthe RMEP to view the value of the Alarm Status field.

l If the value of the Alarm Status field is none, go to Step 3.

l If the value of the Alarm Status field is not none, go to Step 2.


l If the value of the Alarm Status field is LOC, follow the troubleshooting proceduredescribed in 18.12 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.42 hwDot1agCfmLOC torectify the fault. Check whether the trap is cleared. If the trap persists, go to Step 3.

l If the value of the Alarm Status field is unexpectedMAC, follow the troubleshootingprocedure described in 18.10 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.40hwDot1agCfmUnexpectedMAC to rectify the fault. Check whether the trap is cleared. Ifthe trap persists, go to Step 3.

l If the value of the Alarm Status field is unexpectedPeriod, follow the troubleshootingprocedure described in 18.8 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.38hwDot1agCfmUnexpectedPeriod to rectify the fault. Check whether the trap is cleared. Ifthe trap persists, go to Step 3.

l If the value of the Alarm Status field is unexpectedMEP, follow the troubleshootingprocedure described in 18.6 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.36



219

hwDot1agCfmUnexpectedMEP to rectify the fault. Check whether the trap is cleared. Ifthe trap persists, go to Step 3.

l If the value of the Alarm Status field is mismerge, follow the troubleshooting proceduredescribed in 18.4 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.34hwDot1agCfmMismerge to rectify the fault. Check whether the trap is cleared. If the trappersists, go to Step 3.


1. Run the oam-mgr command to enter the MGR view.

2. Run the display this command. Check whether CFM is associated with an interface or aprotocol. If there is no association configuration, go to Step 4.

3. If CFM is associated with an interface or a protocol, check whether the associated interfaceor protocol fails. If the associated interface or protocol works properly, go to Step 4. If theassociated interface or protocol fails, rectify the fault. Check whether the trap is cleared. Ifthe trap persists, go to Step 4.


----End

18.17 EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.47hwDot1agCfmRDICleared

Description

EOAM1AG/3/RDICLEARED: OID [oid] MEP received a CCM with RDI flag cleared.(MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING],MepId=[INTEGER], RmepId=[INTEGER])

The RMEP sent a CCM carrying the RDI flag with the value of 0 to the MEP.

Attribute



Parameters

Name Meaning








220

Name Meaning

MepId ID of a MEP



Possible CausesThe MEP received a CCM carrying the RDI flag with the value of 0.


----End



221

19 EOAM_Y1731

About This Chapter

19.1 EOAMY_1731_1.3.6.1.4.1.2011.5.25.136.1.6.23 hwCfmVlanOnewayDelay

19.2 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.24 hwCfmVlanOnewayDelayRecovery

19.3 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.25 hwCfmVlanTwowayDelay

19.4 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.26 hwCfmVlanTwowayDelayRecovery

19.5 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.30 hwY1731AisDefectAlarm

19.6 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.31 hwY1731AisDefectAlarmRecovery

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 19 EOAM_Y1731


222

19.1 EOAMY_1731_1.3.6.1.4.1.2011.5.25.136.1.6.23hwCfmVlanOnewayDelay

Description

EOAM_Y1731/4/VLAN_1DM_EXCEED_THRESHOLD:OID [OID] The result of one-waydelay-measure exceeded the threshold. (MdIndex=[GAUGE], MaIndex=[GAUGE],RemoteMacAddress=[OPAQUE], Timestamp=[TIMETICK], DelayValue=[GAUGE],ThresholdValue=[GAUGE])

In the VLAN networking where one-way frame delay measurement was configured and anexpected alarm threshold was set, if the network delay exceeded the alarm threshold, an alarmwas generated.

Attribute


1.3.6.1.4.1.2011.5.25.136.1.6.23 Warning qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid ID of a MIB object

MdIndex Index of the MD where a one-way frame delay alarm is generated

MaIndex Index of the MA where a one-way frame delay alarm is generated

RemoteMacAddress Source MAC address contained in the 1DM frame received by the localend from the remote end

Timestamp Timestamp indicating the time when a one-way frame delay alarm isgenerated

DelayValue Delay when a one-way frame delay alarm is generated

ThresholdValue An alarm threshold for one-way frame delay measurement



Possible Causes

The device was enabled with one-way frame delay measurement and was configured with analarm threshold, and the delay in unidirectional frame transmission exceeded the alarm threshold.



223

Procedure

Step 1 Check whether the clocks of the transmitting device and the receiving device are synchronized.

l If the clocks of the two devices are synchronized, go to Step 3.

l If the clocks of the two devices are not synchronized, go to Step 2.

Step 2 Perform clock synchronization between the two devices. Then, check whether the alarm iscleared.

l If the alarm is cleared, go to Step 6.

l If the alarm is not cleared, go to Step 5.

Step 3 Use the trace function defined in 801.1ag to check whether there is a long delay in frametransmission on a link or a device.

l If there is a long delay, go to Step 4.

l If there is no long delay, go to Step 5.

Step 4 Troubleshoot the fault of a long delay. Then, check whether the alarm is cleared.



Step 5 Collect the trap information, log information, configuration of the router, and contact Huaweitechnical personnel.

Step 6 End.

----End

19.2 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.24hwCfmVlanOnewayDelayRecovery

Description

EOAM_Y1731/4/VLAN_1DM_UNDER_THRESHOLD:OID [OID] The result of one-waydelay-measure is under the threshold. (MdIndex=[GAUGE], MaIndex=[GAUGE],RemoteMacAddress=[OPAQUE], Timestamp=[TIMETICK], DelayValue=[GAUGE],ThresholdValue=[GAUGE])

In the VLAN networking where one-way frame delay measurement was enabled and an expectedalarm threshold was set, if the network delay fell below the alarm threshold and a one-way framealarm had been generated, a recovery alarm was generated.

Attribute





224

Parameters

Name Meaning


MdIndex Index of the MD where a one-way frame delay alarm is cleared

MaIndex Index of the MA where a one-way frame delay alarm is cleared

RemoteMacAddress Source MAC address contained in the 1DM frame received by the localend from the remote end

Timestamp Timestamp indicating the time when a one-way frame delay alarm iscleared

DelayValue Delay when a one-way frame delay alarm is cleared

ThresholdValue An alarm threshold for one-way frame delay measurement



Possible Causes

The device in VLAN networking was enabled with one-way frame delay measurement and wasconfigured with an expected alarm threshold, the network delay fell below the alarm thresholdand a one-way frame delay alarm had been generated.

Procedure

l This alarm message is informational only, and no action is required.

----End

19.3 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.25hwCfmVlanTwowayDelay

Description

EOAM_Y1731/4/VLAN_2DM_EXCEED_THRESHOLD:OID [OID] The result of two-waydelay-measure exceeded the threshold. (MdIndex=[GAUGE], MaIndex=[GAUGE],RemoteMacAddress=[OPAQUE], Timestamp=[TIMETICK], DelayValue=[GAUGE],ThresholdValue=[GAUGE])

In the VLAN networking where two-way frame delay measurement was configured and theexpected alarm threshold was set, if the network delay exceeded the set alarm threshold, an alarmwas generated.



225

Attribute



Parameters

Name Meaning


MdIndex Index of the MD where a two-way frame delay alarm is generated

MaIndex Index of the MA where a two-way frame delay alarm is generated

RemoteMacAddress Source MAC address contained in the DMR frame received by the localend from the remote end

Timestamp Timestamp indicating the time when a two-way frame delay alarm isgenerated

DelayValue Delay when a two-way frame delay alarm is generated

ThresholdValue An alarm threshold for two-way frame delay measurement



Possible Causes

The device was enabled with two-way frame delay measurement and was configured with analarm threshold, and the delay in bidirectional frame transmission exceeded the alarm threshold.

Procedure

Step 1 Use the trace function defined in 801.1ag to check whether a long delay in frame transmissionon a link or a device.

l If there is such a long delay, go to Step 2.

l If there is no such a long delay, go to Step 3.

Step 2 Troubleshoot the fault of a long delay. Then, check whether the alarm is cleared.



Step 3 Collect the trap information, log information, and configuration of the router, and contactHuawei technical personnel.

Step 4 End.

----End



226


19.4 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.26hwCfmVlanTwowayDelayRecovery

DescriptionEOAM_Y1731/4/VLAN_2DM_UNDER_THRESHOLD:OID [OID] The result of two-waydelay-measure is under the threshold. (MdIndex=[GAUGE], MaIndex=[GAUGE],RemoteMacAddress=[OPAQUE], Timestamp=[TIMETICK], DelayValue=[GAUGE],ThresholdValue=[GAUGE])

In the VLAN scenario where two-way frame delay measurement was configured and theexpected alarm threshold was set, if the network delay fell below the set alarm threshold and atwo-way frame delay alarm had been generated, a recovery alarm was generated.

Attribute



Parameters

Name Meaning


MdIndex Index of the MD where a two-way frame delay alarm is cleared

MaIndex Index of the MA where a two-way frame delay alarm is cleared

RemoteMacAddress Source MAC address contained in the DMR frame received by the localend from the remote end

Timestamp Timestamp indicating the time when a two-way frame delay alarm iscleared

DelayValue Delay when a two-way frame delay alarm is cleared.

ThresholdValue An alarm threshold for two-way frame delay measurement




227

Possible Causes

The device in VLAN networking was enabled with two-way frame delay measurement and wasconfigured with an expected alarm threshold, the network delay fell below the alarm thresholdand a two-way frame delay alarm had been generated.

Procedure


----End

19.5 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.30hwY1731AisDefectAlarm

Description

EOAM_Y1731/4/AISDEFECTALARM:OID [OID] MEP enters AIS defect condition.(MdIndex=[INTEGER], MaIndex =[INTEGER], MdName=[STRING], MaName=[STRING],MepId =[INTEGER])

An MEP received an AIS PDU and entered the faulty state.

Attribute


1.3.6.1.4.1.2011.5.25.136.1.6.30 warning qualityOfServiceAlarm (3)

Parameters

Name Meaning


MdIndex MD index

MaIndex MA index



MepId MEP ID


Service instances bound to the MA to which the MEP belongs is unavailable.



228

Possible Causes

The MEP received an AIS PDU carrying an MD level lower than the level of the MD to whichthe MEP belongs.

Procedure

Step 1 Check whether a fault occurs in an MA with the lower MD level.

Run the display cfm remote-mep command to view the value of the CFM Status field.

l If the value of the CFM Status field is Down, an MA fails. Rectify the fault.

l If the value of the CFM Status field is Up, go to step 3.


Step 3 End.

----End

Related Information

None.

19.6 EOAM_Y1731_1.3.6.1.4.1.2011.5.25.136.1.6.31hwY1731AisDefectAlarmRecovery

Description

EOAM_Y1731/4/AISDEFECTALARMRECOVERY:OID [OID] MEP exits AIS defectcondition. (MdIndex=[INTEGER], MaIndex =[INTEGER], MdName=[STRING], MaName=[STRING], MepId =[INTEGER])

The MEP received no AIS PDU within the AIS PDU timeout period and exited from the faultystate.

Attribute


1.3.6.1.4.1.2011.5.25.136.1.6.31 Warning qualityOfServiceAlarm (3)

Parameters

Name Meaning


MdIndex MD index



229

Name Meaning

MaIndex MA index



MepId MEP ID

Impact on the SystemThe system will not be affected.

Possible CausesThe MEP exited from the faulty state.

Procedurel This alarm is informational only, and no action is required.

----End




230

20 EZOP

About This Chapter

20.1 EZOP_1.3.6.1.4.1.2011.2.25.311.6.2.1_hwEasyOperationClientAdded

20.2 EZOP_1.3.6.1.4.1.2011.2.25.311.6.2.2_hwEasyOperationClientLost

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 20 EZOP


231

20.1EZOP_1.3.6.1.4.1.2011.2.25.311.6.2.1_hwEasyOperationClientAdded

Description

EZOP/4/CLIENTADD: OID [oid] Easy operation client device added.(ClientId=[INTEGER],HostName="[OCTET]", ClientIp="[OCTET]",ClientMac="[OCTET]",ClientEsn="[OCTET]")

A client has joined the management domain of the Commander.

Attribute



Parameters

Name Meaning

[oid] Indicates the ID of the alarm MIB object.

ClientId Indicates a client ID.

HostName Indicates the host name of the new client.

ClientIp This object indicates the IP address of the new client.

ClientMac Indicates the MAC address of the new client

ClientEsn Indicates the ESN of the new client.


None.

Possible Causes

A client has joined the management domain of the Commander.

Procedure


----End



232

20.2EZOP_1.3.6.1.4.1.2011.2.25.311.6.2.2_hwEasyOperationClientLost

Description

EZOP/4/CLIENTLOST: OID [oid] Easy operation client device lost.(ClientId=[INTEGER],HostName="[OCTET]", ClientIp="[OCTET]",ClientMac="[OCTET]",ClientEsn="[OCTET]")

A client has left the management domain of the Commander.

Attribute



Parameters

Name Meaning

[oid] Indicates the ID of the alarm MIB object.

ClientId Indicates a client ID.

HostName Indicates the host name of the client.

ClientIp This object indicates the IP address of the client.

ClientMac Indicates the MAC address of the client

ClientEsn Indicates the ESN of the client.


None.

Possible Causes

A client has left the management domain of the Commander. The Commander does not receivethe response from the client in 2 minutes. In a stack, change of the system MAC address causesa LOST alarm.

Procedure


----End



233

21 ETRUNK

About This Chapter

21.1 ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.1 hwETrunkStatusChange

21.2 ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.2 hwETrunkMemberStatusChange

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 21 ETRUNK


234

21.1 ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.1hwETrunkStatusChange

Description

ETRUNK/4/TRAP_STATUS:OID [oid] The status of an E-Trunk changed. (Index=[integer],State=[integer], Reason=[integer])

The status change of an E-Trunk was advertised to the NMS.

Attribute



Parameters

Name Meaning


Index Index of the E-Trunk

State Status of the E-Trunkl initialize(1)l backup(2)l master(3)

Reason Cause for the E-Trunk in such a status


The system is not affected.

Possible Causes

1.

The priority of the E-Trunk was changed.

2.

The packet-receiving timer at the local device expired.

3.

BFD detected the fault on the control link between PEs.



235

Procedure

Step 1 Run the display e-trunk etrunk-id command to check the cause for the master/backup statusswitchover of the E-Trunk.

l If the entry PRI(1) is displayed, indicating that the master/backup status is determined by theE-Trunk priority, go to Step 2.

l If the entry TIMEOUT(2) is displayed, indicating that the local device becomes the masterbecause it receives no protocol packets from the peer device within the timeout period, goto Step 3.

l If the entry PEER_TIMEOUT(4) is displayed, indicating that the peer device becomes themaster because it receives no protocol packets from the local device within the timeoutperiod, go to Step 3.

l If the entry ALL_MEMBER_DOWN(6) is displayed, indicating that the two devices of anE-Trunk are Down, go to Step 4.

l If the entry INIT(7) is displayed, indicating that the E-Trunk is being initialized, go to Step5.

Step 2 Check whether the master/backup status of the E-Trunk is switched over according to user'srequirement.



Step 3 Check whether the IP addresses of the E-Trunk local device and peer device are correctlyconfigured.



Step 4 Check whether the E-Trunk interface is shut down.



Step 5 Check whether the E-Trunk is correctly initialized.



Step 6 Check whether the E-Trunk priority is changed according to the entries displayed in Step 1.



Step 7 Check whether the route between E-Trunk devices is reachable.



Step 8 Run the undo shutdown command in the interface view to check whether the trap is cleared.



Step 9 Check whether the E-Trunk priority is changed according to a legal requirement.



236



Step 10 Check whether the physical links are repaired, and the trap is cleared.



Step 11 Run the priority priority command in the E-Trunk view to correctly configure the E-Trunkpriority according to the networking requirement, and then check whether the trap is cleared.



Step 12 Run the peer-address peer-ip-address source-address source-ip-address command in the E-Trunk view to correctly configure the IP addresses of the E-Trunk local device and peer device,and then check whether the trap is cleared.



Step 13 Collect trap information, log information, and configuration information, and then contactHuawei technical support personnel.

Step 14 End.

----End

Related Information

None

21.2 ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.2hwETrunkMemberStatusChange

Description

ETRUNK/4/TRAP_MEMBER_STATUS:OID [oid] The status of an E-Trunk memberchanged. (E-Trunk ID=[integer], Member type=[integer], Member ID=[integer], Memberstatus=[integer], Status reason=[integer])

The status change of an E-Trunk member was advertised to the NMS.

Attribute





237

Parameters

Name Meaning


E-Trunk ID ID of the E-Trunk to which the E-Trunk member belongs

Member type Type of E-Trunk member. There is only one member type: Eth-Trunk.

Member ID ID of the E-Trunk member

Member status Status of the E-Trunk member

Status reason Cause for the E-Trunk member in such a status


If the local E-Trunk member is the master, the E-Trunk member can forward data.

If the local E-Trunk member is the backup, the E-Trunk member cannot forward data.

Possible Causes

1.

The status of the E-Trunk to which the local E-Trunk member belongs was changed.

2.

The peer of the E-Trunk member was faulty or recovered from a fault.

3.

The operating mode of the local E-Trunk member is changed.

Procedure

Step 1 Run the display e-trunk etrunk-id command to check whether the master/backup status ischanged on the local end of the E-Trunk.

l If so, see 21.1 ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.1 hwETrunkStatusChange toperform the subsequent procedures.


Step 2 Check whether the operating mode of the local E-Trunk member is changed.



Step 3 Check whether the E-Trunk interface is shut down.



Step 4 Check whether the physical links are repaired, and the trap is cleared.




238


Step 5 Check whether the operating mode of the local E-Trunk member is changed according to a legalrequirement.l If so, go to Step 9.l If not, go to Step 8.

Step 6 Run the e-trunk mode { auto |force-master | force-backup } command in the Eth-Trunkinterface view to correctly configure the operating mode of the Eth-Trunk in the E-Trunkaccording to the networking requirement. Then, check whether the trap is cleared.l If so, go to Step 9.l If not, go to Step 8.

Step 7 Run the undo shutdown command in the interface view to check whether the trap is cleared.l If so, go to Step 9.l If not, go to Step 4.

Step 8 Collect trap information, log information, and configuration information, and then contactHuawei technical support personnel.

Step 9 End.

----End

Related Information21.1 ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.1 hwETrunkStatusChange



239

22 FM

About This Chapter

22.1 FM_1.3.6.1.4.1.2011.5.25.180.2.1 hwAlarmTargetHostDel

22.2 FM_1.3.6.1.4.1.2011.5.25.180.2.2 hwAlarmStorm

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 22 FM


240

22.1 FM_1.3.6.1.4.1.2011.5.25.180.2.1hwAlarmTargetHostDel

DescriptionFM/4/TARGETHOST_DEL:OID [oid] Target host [octet] was deleted.

The target host was deleted.

Attribute



Parameters

Name Meaning

oid Indicates the ID of an MIB object.

[octet] Indicates the IP address of a target host.


Possible CausesThe target host was deleted.

Procedure

Step 1 This alarm information is informational only, and no action is required.

----End


22.2 FM_1.3.6.1.4.1.2011.5.25.180.2.2 hwAlarmStorm

DescriptionFM/4/ALARM_STORM:OID [oid] There are excessive traps, which form a trap storm.



241

Excessive traps were generated, which caused a trap storm.

Attribute



Parameters

Name Meaning

oid Indicates the ID of an MIB object.

Impact on the SystemIf a trap storm is caused, traps will accumulate and the trap queue will reach full. If such asituation lasts for a long time, the last traps in the queue may fail to be sent.

Possible CausesThe number of traps received by the system at one time reached the upper limit, which causeda trap storm.

Procedure

Step 1 Record the information about the traps that are reported frequently.


Step 3 End.

----End




242

23 ERRORDOWN

About This Chapter

23.1 ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.1 hwErrordown

23.2 ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.2 hwErrordownRecovery

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 23 ERRORDOWN


243

23.1 ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.1 hwErrordown

Description

ERRDOWN/4/ErrordownOccur: OID [oid] Error-down occured. (Ifindex=[INTEGER],Ifname=[STRING], Cause=[STRING])

The alarm was generated when an errordown event occurred.

Attribute



Parameters

Name Meaning

oid MIB object ID

IfIndex Index of an interface

Ifname Interface name

Cause Cause of the errordown event


After the errordown event occurs, traffic cannot be forwarded on relevant interfaces and servicesare interrupted.

Possible Causes

The faults detected by service modules triggered errordown events. The possible causes are asfollows:

l EFM detected a link fault, which can be a fault that occurred on the remote end or athreshold-crossing event.

l The MSTP edge port received BPDU packets.

Procedure

Step 1 Locate the fault based on the value of the Cause field in the alarm.

l If the value of the Cause field is bpdu-protection, go to Step 2.

l If the value of the error-down cause field is port security, See Port Security to checkwhether the nunber of secure MAC addresses reaches the threshold.



244

l If the value of the Cause field is efm-threshold-event, rectify the fault according to the log15.1 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.4 hwDot3ahEfmThresholdEvent.

l If the value of the Cause field is efm-remote-failure, rectify the fault according to the log15.2 EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5 hwDot3ahEfmNonThresholdEvent.

Step 2 Check whether the interface is specified as an edge port.

l If the interface is not specified as an edge port, go to Step 3.

l If the interface is specified as an edge port, go to Step 4.

Step 3 Perform the following steps.

l Run:interface interface-type interface-num

The interface view is displayed.

l Run:undo stp edged-port and undo shutdown

The edge port configuration is removed. Check whether the log still exists. If the log stillexists, go to Step 4.

Step 4 Collect log messages and contact Huawei technical support personnel.

----End

23.2 ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.2hwErrordownRecovery

Description

ERRDOWN/4/ErrordownRecover: OID [oid] Error-down recovered. (Ifindex=[INTEGER],Ifname=[STRING], Cause=[STRING], RecoverType=[STRING])

The error-down fault recovered.

Attribute



Parameters

Name Meaning

oid MIB object ID

Ifindex Index of an interface

Ifname Interface name



245

Name Meaning

Cause Cause of an alarm

RecoverType Recovery type: automatic recovery or recovery using a command line.


Possible Causesl Services that generated the errordown events were unbound from the errordown module.l Services associated with the errordown events recovered.

Procedurel This log message is informational only, and no action is required.

----End




246

24 FSP

About This Chapter

24.1 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.1 hwStackLinkUp

24.2 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.2 hwStackLinkDown

24.3 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.3 hwStackStandbyChange

24.4 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.4 hwStackSwitchOver

24.5 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.5 hwStackSystemRestart

24.6 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.6 hwStackStackMemberAdd

24.7 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.7 hwStackStackMemberLeave

24.8 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.8 hwStackSystemMacChange

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 24 FSP


247

24.1 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.1 hwStackLinkUp

Description

FSP/4/STACK_TRAP: OID [oid] stackid:[integer] portid:[integer] stack-port change to up.

This alarm was sent to the NMS by the master switch when the logical stack port of a switch inthe stack system was Up.

Attribute



Parameters

Name Meaning

[OID] OID of the MIB

[integer] Stack ID of the device generating the alarm

[integer] ID of logical stack port whose status changes on the device


If the stack interface is Up, service interfaces in the stack system increase. Services, however,are not interrupted.

If the stack interface is Down, the stack system recalculates the ring-breaking point, and thenrefreshes the forwarding entries. In this case, services are transiently interrupted andautomatically recover after the forwarding entries are refreshed.

Possible Causes

1. The switch in the stack system was powered on.

2. The running switch was added to the stack system.

Procedure

l No action is required.

----End

Related Information

None



248

24.2 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.2 hwStackLinkDown

Description

FSP/4/STACK_TRAP: OID [oid] stackid:[integer] portid:[integer] stack-port change to down.

This alarm was sent to the NMS by the master switch when the logical stack port of a switch inthe stack system was Down.

Attribute



Parameters

Name Meaning



[integer] ID of the logical stack port whose status changes on the device


If the previous stack system is in a ring topology and the interface in the Down state just functionsas the ring-breaking point, the topology may become a link topology. Services, however, are notaffected. If the logical stack port in the Down state does not function as the ring-breaking point,the stack system refreshes the forwarding entries. In this case, services are transiently interruptedand automatically recover after the forwarding entries are refreshed.

If the previous stack system is in a link topology, services on the switch that is Down areinterrupted and cannot recover until the switch is added to the stack system again.

Possible Causes

1. The switch in the stack system was powered off.

2. The stack cable was connected loosely or even removed.

3. The stack card was loosened.

Procedure

Step 1 Check whether the switch is powered off.

l If so, power on the switch. Then, go to Step 5.




249

Step 2 Check whether the stack cable is loosened. If so, connect the stack cable tightly.l If the stack interface is Up, go to Step 5.l If the stack interface is Down, go to Step 3.

Step 3 Power off the switch and install the stack card tightly. Then, power on the switch that is connectedto the stack cable to check whether the stack interface is Up.l If the stack interface is Up, go to Step 5.l If the stack interface is Down, go to Step 4.


Step 5 End.

----End


24.3 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.3hwStackStandbyChange

DescriptionFSP/4/STACK_TRAP: OID [oid] stackid:[integer] is Designated as standby master.

This alarm was generated when a slave switch was elected as the standby switch.

Attribute



Parameters

Name Meaning



Impact on the SystemServices on the original standby switch are interrupted and cannot recover until the switch isadded to the stack system again.

Possible Causes1. Once a new stack system was created, a slave switch was elected as the standby switch.



250

2. The original standby switch left the stack system if the switch was powered off or the stackcable was loosened or manually removed. In this case, a new standby switch was elected.

Procedure

Step 1 Once a new stack system is created, the standby switch is elected. In this case, the alarm isinformational only, and no action is required. Otherwise, go to Step 2

Step 2 Check whether the original standby switch is powered off.

l If so, power on the original standby switch. Then, go to Step 6.


Step 3 Check whether the stack cable is loosened.

l If so, connect the stack cable tightly. Then, go to Step 6.


Step 4 Power off the switch and install the stack card tightly. Then, power on the switch that is connectedto the stack cable to check whether the stack interface is Up.

l If the stack interface is Up, go to Step 6.

l If the stack interface is Down, go to Step 5.


Step 6 End.

----End

Related Information

FSP_1.3.6.1.4.1.2011.5.25.183.1.22.7 hwStackStackMemberLeave

24.4 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.4 hwStackSwitchOver

Description

FSP/4/STACK_TRAP: OID [oid] Switch over stackid:[integer] is selected as master.

This alarm was generated when the original standby switch became the master switch.

Attribute





251

Parameters

Name Meaning




When the standby switch becomes the master switch to replace the faulty original master switch,the device needs to refresh entries, which interrupts services.

Possible Causes

1. The master switch was powered off and left the stack system.

2. The stack cable connecting the master switch was loosened or the stack card was loosened.

3. The master/standby switchover was manually performed.

Procedure

Step 1 Check whether the original master switch is powered off.

l If so, power on the original master switch. Then, go to Step 5.


Step 2 Check whether the stack cable is loosened.

l If so, install it tightly. Then, go to Step 5.


Step 3 Check whether the stack card is loosened.

l If the stack card is loosened, power off the device and install the stack card tightly. Then,power on the device that is connected to the stack cable and go to Step 5.

l If the stack card is not loosened, go to Step 4.


Step 5 End.

----End

Related Information

FSP_1.3.6.1.4.1.2011.5.25.183.1.22.7 hwStackStackMemberLeave

24.5 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.5hwStackSystemRestart



252

DescriptionFSP/4/STACK_TRAP: OID [oid] stack system restart :The new master stackid: [integer].

This alarm was sent to the NMS by the master switch after all the switches in the stack systemwere restarted.

Attribute



Parameters

Name Meaning



Impact on the SystemDuring the restart of the stack system, services are interrupted. After the restart of the stacksystem, services recover.

Possible Causes1. The reboot command was manually run on the master switch to restart the stack system.

2. The master and standby switches in the stack system were powered off at the same time.

3. All the switches in the stack system were powered off at the same time.

Procedure

Step 1 Check whether the stack system is restarted because related commands are run manually.l If so, go to Step 4.l If not, go to Step 2.

Step 2 Check whether the stack system is powered off.l If so, go to Step 4.l If not, go to Step 3.


Step 4 End.

----End




253

24.6 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.6hwStackStackMemberAdd

Description

FSP/4/STACK_TRAP: OID [oid] stackid:[integer] added into stack.

This alarm is generated when a new member switch is added to the stack system.

Attribute



Parameters

Name Meaning




None

Possible Causes

1. The switch in the stack system was powered on.

2. A running switch was added to the stack system.

Procedure


----End

Related Information

None

24.7 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.7hwStackStackMemberLeave



254

DescriptionFSP/4/STACK_TRAP: OID [oid] stackid:[integer] leaved from stack.

This alarm was generated when a member switch left the stack system.

Attribute



Parameters

Name Meaning



Impact on the SystemThe services that are forwarded through the device are interrupted.

Possible Causes1. A switch was manually removed from the stack system.

2. A switch in the stack system was powered off.

3. The stack cable connecting a switch in the stack system was removed or the stack card wasloosened.

Procedure

Step 1 Check whether a switch is manually removed from the stack system.l If so, go to Step 6.l If not, go to Step 2

Step 2 Check whether the leaving switch is powered off.l If so, power on and restart the switch. Then, go to Step 6.l If not, go to Step 3.

Step 3 Check whether the stack cable is loosened.l If so, install the stack cable tightly. Then, go to Step 6.l If not, go to Step 4.

Step 4 Check whether the stack card is loosened.l If so, power off the switch and install the stack card tightly. Then, power on the switch that

is connected to the stack cable and go to Step 6.l If not, go to Step 5.



255


Step 6 End.

----End

Related Information

None

24.8 FSP_1.3.6.1.4.1.2011.5.25.183.1.22.8hwStackSystemMacChange

Description

FSP/4/STACK_TRAP: OID [oid] Stack system's Mac address change to stackid [integer]'s Macaddress:[octet]

When the master switch in the stack system changed, the MAC address of the stack system wasswitched to the MAC address of the new master switch if the MAC address switching functionwas enabled in the stack system. In this case, this alarm was generated.

Attribute



Parameters

Name Meaning



[octet] New MAC address currently used by the stack system


The entries are refreshed in the stack system, which results in the temporary interruption ofservices. After the entries are refreshed, services recover.

Possible Causes

The master switch in the stack system changed.



256

Procedurel No action is required.

----End




257

25 HWCM

About This Chapter

25.1 HWCM_1.3.6.1.4.1.2011.6.10.2.1 hwCfgManEventLog

25.2 HWCM_1.3.6.1.4.1.2011.6.10.2.5 hwCfgB2STransferFail

25.3 HWCM_1.3.6.1.4.1.2011.6.10.2.6 hwCfgB2SOperate

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 25 HWCM


258

25.1 HWCM_1.3.6.1.4.1.2011.6.10.2.1 hwCfgManEventLog

Description

HWCM/4/CFGCHANGE:OID [oid] Configure changed. (EventIndex=[integer],CommandSource=[integer], ConfigSource=[integer], ConfigDestination=[integer])

The trap was generated when the configuration changed.

Attribute


1.3.6.1.4.1.2011.6.10.2.1 Warning processingErrorAlarm(4)

Parameters

Name Meaning


EventIndex Indicates the index of EventTable.

CommandSource indicates the command source.

ConfigSource indicates the configuration source.

ConfigDestination indicates the configuration destination.



Possible Causes

The configuration changed.

Procedure


----End

Related Information

None

25.2 HWCM_1.3.6.1.4.1.2011.6.10.2.5 hwCfgB2STransferFail



259

DescriptionHWCM/4/HWCM_B2S_TRANSFAIL: OID [oid] Failed to transfer the configuration file to(index=[integer]) server [server-ip] through [transport-type] when automatically backing up theconfiguration.

Failed to set up a connection with the server when backing up the configuration file to the serverprobably because the configuration parameter was incorrect or the server was unreachable.

Attribute



Parameters

Name Meaning


index Indicates the index of the backup server table.

[server-ip] Indicates the IP address of the server.

[transport-type] Indicates the protocol used to transmit backup configurations. Possiblecauses can be:l FTPl TFTPl SFTP

Impact on the SystemThis alarm indicates that the configuration file fails to be backed up to the server this time. Ifthis alarm is generated multiple times, the configuration is probably incorrect or the link isprobably faulty. You need to check the configuration and network condition.

Possible Causesl The server was unreachable.l The password was incorrect.l The user name was inexistent or the path to the server was inexistent.

Procedure

Step 1 Run the ping command on the device to ping the server to check whether the server is reachable.

Step 2 Set the device as a client to access the server.

Step 3 Re-configure the path to the server if it is incorrect.

----End



260


25.3 HWCM_1.3.6.1.4.1.2011.6.10.2.6 hwCfgB2SOperate

DescriptionHWCM/4/HWCM_B2S_BACKUP:OID [oid] Began to back up the current configuration to theserver.

The configuration file was backed up to the server.

Attribute


1.3.6.1.4.1.2011.6.10.2.6 Warning environmentalAlarm(6)

Parameters

Name Meaning


Impact on the SystemThis alarm indicates that time when the configuration file is backed up to the server is reached.

Possible CausesThe timer expired, and the configuration file was backed up to the server.


----End




261

26 IFNET

About This Chapter

26.1 IFNET_1.3.6.1.4.1.2011.5.25.41.4.1 hwIfMonitorCrcErrorRising

26.2 IFNET_1.3.6.1.4.1.2011.5.25.41.4.2 hwIfMonitorCrcErrorResume

26.3 IFNET_1.3.6.1.4.1.2011.5.25.41.4.5 hwIfMonitorInputRateRising

26.4 IFNET_1.3.6.1.4.1.2011.5.25.41.4.6 hwIfMonitorInputRateResume

26.5 IFNET_1.3.6.1.4.1.2011.5.25.41.4.7 hwIfMonitorOutputRateRising

26.6 IFNET_1.3.6.1.4.1.2011.5.25.41.4.8 hwIfMonitorOutputRateResume

26.7 IFNET_1.3.6.1.6.3.1.1.5.3 linkDown

26.8 IFNET_1.3.6.1.6.3.1.1.5.4 linkUp

26.9 IFNET_1.3.6.1.4.1.2011.5.25.41.4.9 hwIfMonitorHalfduplexRising

26.10 IFNET_1.3.6.1.4.1.2011.5.25.41.3.5 hwIfFlowDown

26.11 IFNET_1.3.6.1.4.1.2011.5.25.41.3.6 hwIfFlowUp

26.12 IFNET_1.3.6.1.4.1.2011.5.25.41.3.7_hwIfNameChange

26.13 IFNET_1.3.6.1.4.1.2011.5.25.41.3.8 hwIfNameChangeResume

26.14 IFNET_1.3.6.1.4.1.2011.5.25.41.3.26 hwEntityExtCfmOverSlot

26.15 IFNET_1.3.6.1.4.1.2011.5.25.41.3.27 hwEntityExtCfmOverCard

26.16 IFNET_1.3.6.1.4.1.2011.5.25.41.3.33 hwExtInterfaceDelete

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 26 IFNET


262

26.1 IFNET_1.3.6.1.4.1.2011.5.25.41.4.1hwIfMonitorCrcErrorRising

Description

IFNET/1/CRCERRORRISING: OID [oid] The CRC error is rising. (hwIfMonitorIndex=[INTEGER], hwIfMonitorCrcErrorStatistics=[COUNTER64],hwIfMonitorCrcErrorThreshold=[INTEGER], hwIfMonitorCrcErrorInterval=[INTEGER],InterfaceName=[STRING])

The trap is generated if the number of CRC errors exceeds the specified value in the specifiedtime.

Attribute


1.3.6.1.4.1.2011.5.25.41.4.1 Critical other(1)

Parameters

Name Meaning

OID indicates the MIB node number.

hwIfMonitorIndex indicates the interface index.

hwIfMonitorCrcErrorStatistics indicates statistics on CRC errors.

hwIfMonitorCrcErrorThreshold indicates the threshold for CRC trap (a trap is generated ifthe number of CRCs exceeds the threshold).

hwIfMonitorCrcErrorInterval indicates the time period for collecting CRC error statistics.



Data of some services on the interface will be dropped.

Possible Causes

The number of packets that are dropped because they failed the CRC exceeded the threshold.

The possible causes are as follows:

1.The optical module was faulty.

2.The optical fiber was faulty.



263

Procedure

Step 1 Replace the optical module and then check whether the fault is rectified.

1. If so, go to step 4.

2. If not, go to step 2.

Step 2 Replace the optical fiber, and then check whether the fault is rectified.

1. If so, go to step 4.

2. If not, go to step 3.

Step 3 Collect the trap information, log information, and configuration of the router, and contactHuawei technical support personnel.

Step 4 End.

----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.4.2 hwIfMonitorCrcErrorResume

26.2 IFNET_1.3.6.1.4.1.2011.5.25.41.4.2hwIfMonitorCrcErrorResume

Description

IFNET/1/CRCERRORRESUME: OID [oid] The CRC error resume. (hwIfMonitorIndex=[INTEGER], hwIfMonitorCrcErrorStatistics=[COUNTER64],hwIfMonitorCrcErrorThreshold=[INTEGER], hwIfMonitorCrcErrorInterval=[INTEGER],InterfaceName=[STRING])

The trap is cleared if the number of CRC errors is smaller than the specified value in the specifiedtime.

Attribute


1.3.6.1.4.1.2011.5.25.41.4.2 Critical other(1)

Parameters

Name Meaning

oid Indicates the MIB node number.

hwIfMonitorIndex Indicates the interface index.

hwIfMonitorCrcErrorStatistics Indicates statistics on CRC errors.



264

Name Meaning

hwIfMonitorCrcErrorThreshold Indicates the threshold for CRC trap (a trap is generated ifthe number of CRCs exceeds the threshold).

hwIfMonitorCrcErrorInterval indicates the time period for collecting CRC error statistics.



Services will be restored.

Possible Causes

The trap that the number of packets that are dropped because they failed the CRC exceeded thethreshold was cleared.

Procedure


----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.4.1 hwIfMonitorCrcErrorRising

26.3 IFNET_1.3.6.1.4.1.2011.5.25.41.4.5hwIfMonitorInputRateRising

Description

IFNET/4/INBWRATEEXCEED: OID [oid] Interface input flow bandwidth usage exceeded thetrap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER], TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of received traffic to the total bandwidthon an interface was greater than the threshold.

Attribute


1.3.6.1.4.1.2011.5.25.41.4.5 Warning other(1)



265

Parameters

Name Meaning


Interface Indicates the interface index.

BandWidthUsage Indicates bandwidth usage.

TrapThreshold Indicates the trap threshold of bandwidth usage.

InterfaceName Indicates the interface name.


When the rate of traffic is close to 90% out of the total bandwidth, delay or packet loss willoccur.

Possible Causes

The rate of traffic received by the interface was too large.

Procedure

Step 1 Run the display this interface command on the interface to check whether the traffic thresholdis too low. The threshold range is specified by users according to actual services.



Step 2 Run the trap-threshold input-rate threshold_value command to reset the threshold and thencheck whether the alarm is cleared.




Step 4 End.

----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.4.6 hwIfMonitorInputRateResume

26.4 IFNET_1.3.6.1.4.1.2011.5.25.41.4.6hwIfMonitorInputRateResume



266

Description

IFNET/4/INBWRATERESUME: OID [oid] Interface input flow bandwidth usage was restoredto the trap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER], TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of received traffic to the total bandwidthon an interface became lower than the threshold.

Attribute


1.3.6.1.4.1.2011.5.25.41.4.6 Warning other(1)

Parameters

Name Meaning







None.

Possible Causes

The rate of traffic received by the interface became lower than the threshold.

Procedure


----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.4.5 hwIfMonitorInputRateRising

26.5 IFNET_1.3.6.1.4.1.2011.5.25.41.4.7hwIfMonitorOutputRateRising



267

Description

IFNET/4/OUTBWRATEEXCEED: OID [oid] Interface output flow bandwidth usage exceededthe trap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER], TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of sent traffic to the total bandwidth onan interface was greater than the threshold.

Attribute


1.3.6.1.4.1.2011.5.25.41.4.7 Warning other(1)

Parameters

Name Meaning







When the rate of traffic is close to the threshold, delay or packet loss will occur.

Possible Causes

The rate of traffic sent by the interface was too large.

Procedure

Step 1 Run the display this interface command on the interface to check whether the traffic thresholdis too low. The threshold range is specified by users according to actual services.



Step 2 Run the trap-threshold output-rate threshold_valuecommand to re-set the threshold and thencheck whether the alarm is cleared.






268

Step 4 End.

----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.4.8 hwIfMonitorOutputRateResume

26.6 IFNET_1.3.6.1.4.1.2011.5.25.41.4.8hwIfMonitorOutputRateResume

Description

IFNET/4/OUTBWRATERESUME: OID [oid] Interface output flow bandwidth usage wasrestored to the trap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER],TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of sent traffic to the total bandwidth onan interface became lower than the threshold.

Attribute


1.3.6.1.4.1.2011.5.25.41.4.8 Warning other(1)

Parameters

Name Meaning







None.

Possible Causes

The rate of traffic sent by the interface became lower than the threshold.



269

Procedure


----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.4.7 hwIfMonitorOutputRateRising

26.7 IFNET_1.3.6.1.6.3.1.1.5.3 linkDown

Description

IFNET/1/IF_LINKDOWN: OID [oid] Interface [interface-index] turned into DOWN state.(AdminStatus=[INTEGER],OperStatus=[INTEGER],InterfaceName=[OCTET])

The status of the link protocol on the interface became Down.

Attribute


1.3.6.1.6.3.1.1.5.3 Critical other(1)

Parameters

Name Meaning


interface-index Indicates the interface index.

AdminStatus Indicates the admin status, which means whether the interface has beendisabled.l 1: undo shutdownl 2: shutdown

OperStatus Indicates the operation status, which means the link layer protocol status ofthe interface.l 1: Upl 2: Down



The interface cannot forward packets normally.



270


The interface became Down and the link was disconnected.

Cause 2:

The VLANIF interface is deleted.

Procedure

Step 1 If the VLANIF interface is deleted, this trap message is informational only. No action is required,go to Step 7.

Step 2 Run the display this command in the interface view to check whether interfaces on both endsare shut down.l If so, go to Step 3.l If not, go to Step 4.

Step 3 Run the undo shutdown command in the interface view to check whether the alarm is cleared.l If so, go to Step 7.l If not, go to Step 4.

Step 4 Check whether the cable and optical module are loosened or dropped.l If so, go to Step 6.l If not, go to Step 5.

Step 5 Connect the physical link correctly and then check whether the alarm is cleared.l If so, go to Step 7.l If not, go to Step 6.


Step 7 End.

----End

Related InformationIFNET_1.3.6.1.6.3.1.1.5.4 linkUp

26.8 IFNET_1.3.6.1.6.3.1.1.5.4 linkUp

DescriptionIFNET/1/IF_LINKUP: OID [oid] Interface [interface-index] turned into UP state.(AdminStatus=[INTEGER],OperStatus=[INTEGER],InterfaceName=[OCTET])

The alarm was generated when the link protocol status of a trunk member interface became Up.



271

Attribute


1.3.6.1.6.3.1.1.5.4 Critical other(1)

Parameters

Name Meaning


interface-index Indicates the interface index.

AdminStatus Indicates the admin status.l 1: undo shutdownl 2: shutdown

OperStatus Indicates the operation status.l 1: Upl 2: Down


Impact on the SystemTraffic will be recovered.

Possible Causes1.

The undo shutdown command was run in the interface view.

2.

The interface became Up and the link was recovered.

3.

The link layer protocol was Up.

4.

The physical status of an Ethernet interface became Up.

Procedure


----End

Related InformationIFNET_1.3.6.1.6.3.1.1.5.3 linkDown



272

26.9 IFNET_1.3.6.1.4.1.2011.5.25.41.4.9hwIfMonitorHalfduplexRising

Description

IFNET/1/HALFDUPLEXRISING: OID [oid] The work mode is half duplex.(hwIfMonitorIndex=[INTEGER])

The trap is generated when the interface works in half-duplex mode.

Attribute


1.3.6.1.4.1.2011.5.25.41.4.9 Critical other(1)

Parameters

Name Meaning

oid Indicates the MIB node number.

hwIfMonitorIndex Indicates the physical index.


Packets may be dropped when the interface works in half-duplex mode.

Possible Causes

The electrical interface worked in half-duplex mode.

Procedure

Step 1 You can set the interface to work in full duplex mode by the duplex full command.

----End

Related Information

None.

26.10 IFNET_1.3.6.1.4.1.2011.5.25.41.3.5 hwIfFlowDown



273

Description

IFNET/4/IF_FLOWDOWN:OID [OID] The state of interface turned to DOWN because ofFLOW DOWN. (Interface=[INTEGER], InterfaceIndex=[INTEGER], SysUpTime=[TIMETICK], FlowStatus=[INTEGER], InterfaceName=[STRING])

The trap was generated when the traffic on a particular interface was interrupted and then theinterface became Down. The time and cause for the status change was recorded.

Attribute



Parameters

Name Meaning


Interface Indicates the unfixed index of an interface.

InterfaceIndex Indicates the fixed index of an interface.

SysUpTime Indicates the time for system startup.

FlowStatus Indicates the traffic status on an interface.

InterfaceName Indicates the name of interface.


Traffic will be interrupted.

Possible Causesl The mVRRP backup group changed to the non-Master state.

l When the mVRRP backup group was in the Master state or the interface was bound to thePW, the shutdown command was run on the interface or the link was faulty.

l The PW configuration was deleted.

Procedure

Step 1 Run the display vrrp binding admin-vrrp command to check whether the interface is boundto the mVRRP backup group.



Step 2 Run the display vrrp admin-vrrp command to check whether the mVRRP backup group towhich the interface is bound is in the Master state.




274


Step 3 Run the display this command in the interface view to check whether the shutdown commandis configured on the interface.l If so, go to Step 4.l If not, go to Step 5.

Step 4 Run the undo shutdown command in the interface view. Then, run the display this interfacecommand to check whether the interface status is Up.l If so, go to Step 10.l If not, go to Step 1.

Step 5 Check and change the physical link to ensure that the physical link works normally. Then, runthe display this interface command to check whether the interface status is Up.l If so, go to Step 10.l If not, go to Step 9.

Step 6 Check whether the status of the mVRRP backup group needs to be switched.l If so, go to Step 7.l If not, go to Step 10.

Step 7 Switch the status of the mVRRP backup group. For details, refer to "VRRP Configuration" inthe S2750&S5700&S6700 Series Ethernet Switches Configuration Guide - Reliability.

Step 8 Run the display this interface command in the interface view to check whether the physicalstatus and link protocol status of the interface are Up.l If so, go to Step 10.l If not, go to Step 9.


Step 10 End.

----End

Related InformationIFNET_1.3.6.1.4.1.2011.5.25.41.3.6 hwIfFlowUp

26.11 IFNET_1.3.6.1.4.1.2011.5.25.41.3.6 hwIfFlowUp

DescriptionIFNET/4/IF_FLOWUP:OID [oid] The state of interface turned to UP because of FLOW UP.(Interface=[INTEGER], InterfaceIndex=[INTEGER], SysUpTime=[TIMETICK], FlowStatus=[INTEGER], InterfaceName=[STRING])

The trap was generated when the traffic on a particular interface was recovered. The time andcause for the recovery was recorded.



275

Attribute


1.3.6.1.4.1.2011.5.25.41.3.6 Warning other(1)

Parameters

Name Meaning


Interface Indicates the unfixed index of an interface.

InterfaceIndex Indicates the fixed index of an interface.


FlowStatus Indicates the traffic status on an interface.

InterfaceName Indicates the name of interface.


Traffic will be recovered.

Possible Causesl 1.

The mVRRP backup group was switched to the Master state.

2.

When the mVRRP backup group was in the Master state or the interface was bound to thePW, the interface went Up.

3.

A PW was configured on the interface.

Procedure


----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.3.5 hwIfFlowDown

26.12 IFNET_1.3.6.1.4.1.2011.5.25.41.3.7_hwIfNameChange



276

Description

IFNET/1/IF_CHANGE:OID [oid] When a single-chassis device is upgraded to a multi-chassisdevice, the interface information is changed.

The single-chassis device was expanded into the multi-chassis device, and consequently theinterface information was changed.

Attribute



Parameters

Name Meaning



An interface is no longer defined in three dimensions, but in four dimensions.

Possible Causes

The device was upgraded from a single-chassis system to a multi-chassis system.

Procedure


----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.3.8 hwIfNameChangeResume

26.13 IFNET_1.3.6.1.4.1.2011.5.25.41.3.8hwIfNameChangeResume

Description

IFNET/1/IF_CHANGE_RESUME:OID [oid] When a multi-chassis restore a single-chassisdevice, the interface information is changed.

The multi-chassis device was changed back into the single-chassis device, and consequently theinterface information was changed.



277

Attribute



Parameters

Name Meaning



An interface is no longer defined in four dimensions, but in three dimensions.

Possible Causes

The device was reverted from a multi-chassis device to a single-chassis device.

Procedure


----End

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.3.7 hwIfNameChange

26.14 IFNET_1.3.6.1.4.1.2011.5.25.41.3.26hwEntityExtCfmOverSlot

Description

IFNET/4/IF_SLOT_CFMOVER: OID [oid] The configuration of the interface board is restored.(BoardName=[STRING])

The configuration of the interface board was restored.

Attribute


1.3.6.1.4.1.2011.5.25.41.3.26 Warning other(1)



278

Parameters

Name Meaning


BoardName Indicates the name of the interface board.


After the configuration of the interface board is restored, the interface board is usable.

Possible Causes

The configuration restoration of the interface board completes after the entire device or theinterface board was restarted.

Procedure


----End

Related Information

None.

26.15 IFNET_1.3.6.1.4.1.2011.5.25.41.3.27hwEntityExtCfmOverCard

Description

IFNET/4/IF_CARD_CFMOVER: OID [oid] The configuration of the interface card is restored.(CardName=[STRING])

The configuration of the interface card was restored.

Attribute


1.3.6.1.4.1.2011.5.25.41.3.27 Warning other(1)

Parameters

Name Meaning




279

Name Meaning

CardName Indicates the name of the interface card.


After the configuration of the interface card is restored, the interface card is usable.

Possible Causes

The entire device or the interface card was restarted.

Procedure


----End

Related Information

None.

26.16 IFNET_1.3.6.1.4.1.2011.5.25.41.3.33hwExtInterfaceDelete

Description

IFNET/4/IF_DELETE :OID [OID] Interface [interface-index] was deleted. (InterfaceName=[STRING])

Interface was deleted.

Attribute



Parameters

Name Meaning


Interface-index Indicates the interface index.




280



This alarm is generated when a specified interface is deleted.

Procedure


----End



281

27 IPv6

About This Chapter

27.1 IPv6_1.3.6.1.2.1.55.2.0.1 ipv6IfStateChange

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 27 IPv6


282

27.1 IPv6_1.3.6.1.2.1.55.2.0.1 ipv6IfStateChange

DescriptionIPV6/4/IF_IPV6CHANGE:OID [oid] The status of the IPV6 Interface changed. (IfIndex=[INTEGER], IfDescr=[OCTET], IfOperStatus=[INTEGER], IfAdminStatus=[INTEGER])

The status of the IPv6 interface was changed.

Attribute


1.3.6.1.2.1.55.2.0.1 Warning communicationsAlarm(2)

Parameters

Name Meaning


IfIndex Indicates the index of the interface.

IfDescr Indicates the description of the interface.

IfOperStatus Indicates the status of the interface.

IfAdminStatus Indicates the management status of the interface.

Impact on the SystemThe influence depends on the ipv6IfOperStatus:

1) Down: indicates that the IPv6 services on the interface are interrupted.

2) Up: indicates that the IPv6 services on the interface are recovered.

Possible Causesl The protocol status on the interface became Down.

– Cause 1: The interface was damaged or the link is faulty.

– Cause 2: The interface was shut down.

– Cause 3: When the IPv6 protocol was Up, the undo ipv6 enable command was run.

– Cause 4: All the IPv6 addresses were deleted.

– Cause 5: When the IPv6 protocol was Up, the IPv6 function was disabled.l The interface protocol can become Up only when the following requirements are met

synchronously.

– Cause 1: The interface and the link are normal.



283

– Cause 2: The undo shutdown command is run on the interface.

– Cause 3: The IPv6 function is enabled in the system view.

– Cause 4: The IPv6 forwarding function is enabled in the interface view.

– Cause 5: The IPv6 address is assigned.

Procedure

Step 1 If the interface turned Up, this log message is informational only and no action is required.

Step 2 If the protocol status of the interface becomes Down, do as follows to locate the fault or changethe protocol status to Up.

1. Run the display ipv6 interface [ interface-type interface-number ] command to checkwhether the IPv6 address is assigned to the interface.

l If so, go to Step b.

l If not, go to Step c.

2. Check the "current state" field of the interface in the display ipv6 interface [ interface-type interface-number ] command output.

l If it displays Down, check whether the shutdown command is run on the remoteinterface.

– If so, run the undo shutdown command in the remote interface view and then repeatStep a and Step b.

– If not, it indicates that the local interface is damaged or the link is faulty. You needto replace the interface module or the cable, and then repeat Step a and Step b.

l If it displays Administratively Down, run the undo shutdown command in the interfaceview, and then repeat Step a and Step b.

l If it displays Up and the IPv6 protocol status is Down, go to Step e.

l If it displays Up and the IPv6 protocol status is Up, go to Step i.

3. Run the display this command in the interface view to check whether the ipv6 enablecommand is configured.

l If so, go to Step d.

l If not, configure the ipv6 enable command. Then, go to Step d.

4. Run the ipv6 address ipv6-address prefix-length in the interface view to assign the IPv6address. Then, go to Step f.

5. Run the display this command in the system view to check whether the ipv6 command isconfigured.

l If so, go to Step f.

l If not, configure the ipv6 command in the system view. Then, go to Step f.

6. Run the display ipv6 interface [ interface-type interface-number | brief ] command tocheck the protocol status of the interface.

l If the status is Down, go to Step g.

l If the status is Up, go to Step h.

7. Collect the trap information, log information, and configuration of the router, and contactHuawei technical personnel.



284

8. End.

----End




285

28 IFPDT

About This Chapter

28.1 IFPDT_1.3.6.1.4.1.2011.5.25.219.2.12.3_hwPortNoSupportOETrap

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 28 IFPDT


286

28.1IFPDT_1.3.6.1.4.1.2011.5.25.219.2.12.3_hwPortNoSupportOETrap

Description

IFPDT/4/CSS_NOSUPPORT_OEPORT:OID [oid] The 1000base-T optical/electrical moduleor optical module cannot be installed on the port when the port is used as a stack port.(EntityPhysicalIndex=[INTEGER], EntityIfIndex=[INTEGER], EntPhysicalName=[OCTET],hwEntityTrapFaultID=[INTEGER]).

A copper module or GE optical module cannot be used on a stack port.

Attribute



Parameters

Name Meaning

oid Indicates the ID of a MIB object.


EntityIfIndex Indicates the interface index.

EntPhysicalName Indicates the entity name. The entity name varies according to the cardtype.

hwEntityTrapFaultID Indicates an error code.


The copper module or GE optical module cannot be used on a stack port.

Possible Causes

The port has been configured as a stack port and cannot have any copper module or GE opticalmodule installed.



287

Procedurel Replace the copper module or GE optical module with a 10GE or 40GE optical module

that can be used on the stack port.l If the stack port is not required, delete the stack port configuration to restore the port to a

common service port. Then the copper module or GE optical module can be used on theport.

l If the problem persists, contact the Huawei technical support personnel.l End.

----End



288

29 ISIS

About This Chapter

NOTE

Only the S6700EI, S5700EI, S5700HI, and S5710EI support ISIS alarm.

29.1 ISIS_1.3.6.1.3.37.2.0.1 isisDatabaseOverload

29.2 ISIS_1.3.6.1.3.37.2.0.2 isisManualAddressDrops

29.3 ISIS_1.3.6.1.3.37.2.0.3 isisCorruptedLSPDetected

29.4 ISIS_1.3.6.1.3.37.2.0.4 isisAttemptToExceedMaxSequence

29.5 ISIS_1.3.6.1.3.37.2.0.5 isisIDLenMismatch

29.6 ISIS_1.3.6.1.3.37.2.0.6 isisMaxAreaAddressesMismatch

29.7 ISIS_1.3.6.1.3.37.2.0.7 isisOwnLSPPurge

29.8 ISIS_1.3.6.1.3.37.2.0.8 isisSequenceNumberSkip

29.9 ISIS_1.3.6.1.3.37.2.0.9 isisAuthenticationTypeFailure

29.10 ISIS_1.3.6.1.3.37.2.0.10 isisAuthenticationFailure

29.11 ISIS_1.3.6.1.3.37.2.0.11 isisVersionSkew

29.12 ISIS_1.3.6.1.3.37.2.0.12 isisAreaMismatch

29.13 ISIS_1.3.6.1.3.37.2.0.13 isisRejectedAdjacency

29.14 ISIS_1.3.6.1.3.37.2.0.14 isisLSPTooLargeToPropagate

29.15 ISIS_1.3.6.1.3.37.2.0.15 isisOrigLSPBuffSizeMismatch

29.16 ISIS_1.3.6.1.3.37.2.0.16 isisProtocolsSupportedMismatch

29.17 ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange

29.18 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.1 hwIsisSystemIdConflict

29.19 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.2 hwIsisL1ImportRouteExceedLimit

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 29 ISIS


289

29.20 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.3 hwIsisL1ImportRouteRestoreToLimit

29.21 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.4 hwIsisL2ImportRouteExceedLimit

29.22 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.5 hwIsisL2ImportRouteRestoreToLimit

29.23 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.6 hwIsisL1ImportRouteThresholdReach

29.24 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.7 hwIsisL1ImportRouteThresholdReachClear

29.25 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.8 hwIsisL2ImportRouteThresholdReach

29.26 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.9 hwIsisL2ImportRouteThresholdReachClear

29.27 ISIS-STD_1.3.6.1.2.1.138.0.1 isisDatabaseOverload

29.28 ISIS-STD_1.3.6.1.2.1.138.0.2 isisManualAddressDrops

29.29 ISIS-STD_1.3.6.1.2.1.138.0.3 isisCorruptedLSPDetected

29.30 ISIS-STD_1.3.6.1.2.1.138.0.4 isisAttemptToExceedMaxSequence

29.31 ISIS-STD_1.3.6.1.2.1.138.0.5 isisIDLenMismatch

29.32 ISIS-STD_1.3.6.1.2.1.138.0.6 isisMaxAreaAddressesMismatch

29.33 ISIS-STD_1.3.6.1.2.1.138.0.7 isisOwnLSPPurge

29.34 ISIS-STD_1.3.6.1.2.1.138.0.8 isisSequenceNumberSkip

29.35 ISIS-STD_1.3.6.1.2.1.138.0.9 isisAuthenticationTypeFailure

29.36 ISIS-STD_1.3.6.1.2.1.138.0.10 isisAuthenticationFailure

29.37 ISIS-STD_1.3.6.1.2.1.138.0.11 isisVersionSkew

29.38 ISIS-STD_1.3.6.1.2.1.138.0.12 isisAreaMismatch

29.39 ISIS-STD_1.3.6.1.2.1.138.0.13 isisRejectedAdjacency

29.40 ISIS-STD_1.3.6.1.2.1.138.0.14 isisLSPTooLargeToPropagate

29.41 ISIS-STD_1.3.6.1.2.1.138.0.15 isisOrigLSPBuffSizeMismatch

29.42 ISIS-STD_1.3.6.1.2.1.138.0.16 isisProtocolsSupportedMismatch

29.43 ISIS-STD_1.3.6.1.2.1.138.0.17 isisAdjacencyChange

29.44 ISIS-STD_1.3.6.1.2.1.138.0.18 isisLSPErrorDetected



290

29.1 ISIS_1.3.6.1.3.37.2.0.1 isisDatabaseOverload

DescriptionISIS/3/OLOAD:OID [oid] The overload state of IS-IS LSDB changed. (sysInstance=[integer],sysInstanceofLevel=[integer], sysLevel=[integer], overLoadState=[integer])

The database entered or exited from the Overload state.

Attribute


1.3.6.1.3.37.2.0.1 Minor other(1)

Parameters

Name Meaning


sysInstance Indicates the ID of the IS-IS process.

sysInstanceofLevel Indicates the ID of the IS-IS process.

sysLevel Indicates the IS-IS level:l 1: Level-1l 2: Level-2

overLoadState Indicates the LSDB Overload state:l 1: offl 2: onl 3: waitingl 4: overloaded

Impact on the System1. If the trap is triggered by the change of the LSDB Overload state, route selection of theneighbor will be affected.

2. If the trap is triggered by memory failure, it indicates that the IS-IS database is unauthentic.

Possible Causes1. The set-overload or undo set-overload command is run in the IS-IS view.



291

2. The IS-IS process exited from the Overload state after entering the Overload state.

3. Memory application failed because memory was insufficient. As a result, the system of theswitch may crash.

Procedure

Step 1 Run the display this command in the IS-IS view to check whether the set-overload or undoset-overload command is run in this process.l If so, it indicates that this trap message is informational only, and no action is required. Go

to Step 5.l If not, go to Step 2.

Step 2 Run the display memory-usage command to check the memory usage of the switch. Checkwhether the memory usage reaches the threshold.l If so, go to Step 3.l If not, go to Step 4.

Step 3 Obtain and analyze the log, and then go to Step 4.

Step 4 Collect the trap information, log information, and configuration of the router, and contactHuawei technical personnel.

Step 5 End.

----End


29.2 ISIS_1.3.6.1.3.37.2.0.2 isisManualAddressDrops

DescriptionISIS/2/MANAREA_DROP:OID [oid] Some area addresses were discarded because the numberof area addresses exceeded three. (sysInstance=[process-id], sysInstanceofLevel=[process-id],sysLevel=[level], sysInstanceofManAreaAddrExistState=[process-id], manAreaAddr=[area-address], manAreaAddrExistState=[area-address-state])

On the Level-1-2 switch, IS-IS leaked the Level-1 area addresses to the Level-2 area. As a result,the number of Level-2 area addresses was more than 3 and IS-IS selected the top three smallestarea addresses as the Level-2 area addresses. This may lead to the loss of Level-2 area addressesof the local IS-IS system.

Attribute


1.3.6.1.3.37.2.0.2 Major other(1)



292

Parameters

Name Meaning





sysInstanceofManAreaAddrExistState Indicates the ID of the IS-IS process.

manAreaAddr Indicates the area address. If the value is 0, it indicatesthe parameter is not used.

manAreaAddrExistState Indicates the area address state:l 1: activel 2: notInServicel 3: notReadyl 4: createAndGol 5: createAndWaitl 6: destroy


The Level-2 area addresses of the local IS-IS system may be lost.

Possible Causes

The Level-1-2 switch leaked the LSP with the area ID of Level-1 to Level-2. When the numberof Level-2 area ID exceeded 3, IS-IS selected top three smallest area IDs. Then, the local areaaddresses in the Level-2 area may be lost.

Procedure

Step 1 Run the display isis lsdb level-1 verbose command to check the detailed information about theLevel-1 IS-IS LSDB, and the AREA ADDR field carried in the LSP with the LSP fragment IDbeing 0. Then, count the number of different Level-1 area addresses to check whether the numberis larger than three.

l If so, go to step 2.

l If not, go to step 3.



293

Step 2 Run the undo network-entity command (this command needs to be run with caution) in the IS-IS view to delete the IS-IS area address, and then run the network-entity command in the IS-IS view to configure a new IS-IS area address to ensure that there are not more than three differentIS-IS area addresses in the Level-1 area that is connected to the Level-1-2 router. Run the displayisis lsdb command to check whether the value of the Level-1 Area Address field is the same asthe value of the Level-2 Area Address field in the LSP with the fragment number being 0 on thelocal switch.

l If so, go to step 4.


Step 3 Collect the trap information, log information, and configuration of the switch, and contactHuawei technical personnel.

Step 4 End.

----End

Related Information

None

29.3 ISIS_1.3.6.1.3.37.2.0.3 isisCorruptedLSPDetected

Description

ISIS/3/CORRUPT_LSP:OID [oid] The checksum of LSP is wrong. (sysInstance=[integer],sysInstanceofLevel=[integer], sysLevel=[integer], pduLspId=[opaque])

A trap was generated when the LSP checksum authentication of the local LSDB failed beforethe IS-IS switch sent LSPs.

Attribute


1.3.6.1.3.37.2.0.3 Minor other(1)

Parameters

Name Meaning






294

Name Meaning


pduLspId Indicates the LSP ID.


The LSP checksum failure will lead to the reset of the IS-IS process and relevant IS-IS serviceswill be interrupted.

Possible Causes

During the LSP refreshing period, a fault might occur in the memory, and consequently the LSPwas modified.

Procedure

Step 1 Run the display memory-usage command to check whether the memory usage exceeds thethreshold (approximately 80%).



Step 2 Run the reset isis all command to restart the IS-IS process. After the IS-IS process is restarted,check whether the trap is cleared.




Step 4 End.

----End

Related Information

None

29.4 ISIS_1.3.6.1.3.37.2.0.4isisAttemptToExceedMaxSequence



295

Description

ISIS/3/MAXSEQ_EXCEED:OID [oid] The LSP sequence number almost reaches the maximumvalue. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], pduLspId=[opaque])

The sequence number of the IS-IS LSP would reach the maximum value.

Attribute


1.3.6.1.3.37.2.0.4 Minor other(1)

Parameters

Name Meaning





pduLspId Indicates the LSP ID.


After the sequence number reaches the maximum value 0xFFFFFFFF, the IS-IS process will besuspended for a period of time, namely, the sum of the maximum lifetime and zero aging timeof an LSP. As a result, IS-IS services will be interrupted.

Possible Causes

The sequence number of the LSP generated locally reached the maximum value 0xFFFFFFFF.

Procedure

Step 1 After the LSP whose sequence number is 0xFFFFFFFF (the maximum lifetime of an LSP + 60,of which, the default maximum lifetime of an LSP is 1200s) ages out, the sequence number ofthe LSP starts from 1 again. The display isis lsdb local command can be used to check the SeqNum field of an LSP generated by the local switch.



296

l If the increasing speed of the LSP sequence number is matched with the configured refreshingperiod, it indicates that this trap message is informational only, and no action is required, goto Step 5.

l If the sequence number increases rapidly, go to Step 2.

Step 2 Check whether there is another switch whose system ID is the same as the system ID or thevirtual system ID of the local switch. According to ISO10589, the system ID in an IS-IS domainmust be unique.



Step 3 (Use the undo network-entity command or the undo virtual-system command with caution.)Enter the IS-IS view of the local switch or another switch whose system ID is the same as thesystem ID or the virtual System ID of the local switch. Then run the undo network-entitycommand or the undo virtual-system command to delete the repeated system ID or virtualsystem ID and the network-entity command or the virtual-system command to configure adifferent system ID or virtual system ID for the switch. Check whether the trap is cleared.




Step 5 End.

----End

Related Information

None

29.5 ISIS_1.3.6.1.3.37.2.0.5 isisIDLenMismatch

Description

ISIS/2/SYSID_MISMATCH:OID [oid] The ID length of received PDU is different from localconfiguration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer],sysInstanceofPduFieldLen=[integer], circIndex=[integer], ifIndex=[integer], pduFieldLen=[integer], circIfIndex=[integer], pduFrag=[opaque], ifName=[string])

The length of the system ID carried in the header of the received PDU, including all types of IS-IS packets, did not match the length of the system ID of the local switch.

Attribute


1.3.6.1.3.37.2.0.5 Major other(1)



297

Parameters

Name Meaning





sysInstanceofPduFieldLen Indicates the ID of the IS-IS process.

circIndex Indicates the index of the interface.

ifIndex Indicates the index of the interface.

pduFieldLen Indicates the length of the received PDU.

circIfIndex Indicates the IF index of the interface.

pduFrag Indicates the fragment of 64-byte PDU header.

ifName Indicates the name of the interface.


1. If the trap is triggered because of a hardware fault on the board, route flapping may occur.

2. If the trap is triggered because of intercommunication between switchs, neighbors cannot beestablished, or routes cannot be learnt from each other.

Possible Causes

1. The length of the system ID supported by other switchs mismatch with the length of the systemID supported by the local switch.

2. The system ID Length field was modified during packet transmission.

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (inhexadecimal) in the trap and fetch the system ID of the source switch. Check whether the lengthof the system ID is neither 0 nor 6.



298


Table 29-1 Methods of searching for system IDs and types of IS-IS packets

Searching for the Packet Type Searching for the System ID

Hello: the 5th byte in the pdu-fragment fieldbeing 0f, 10, or 11

The system ID is continuous 6 bytes after the10th byte in the pdu-fragment field

LSP: the 5th byte in the pdu-fragment fieldbeing 12 or 14


SNP: the 5th byte in the pdu-fragment fieldbeing 18, 19, 1A, or 1B


Step 2 Modify the system ID length configured on the source switch to 6. Then, check whether the trapis cleared.l If so, go to Step 6.l If not, go to Step 3.

Step 3 View the logs or ping the board to check whether the board has a fault and hence the packet istampered.l If so, go to Step 4.l If not, go to Step 5.

Step 4 Change the board. Then, check whether the trap is cleared.l If so, go to Step 6.l If not, go to Step 5.


Step 6 End.

----End


29.6 ISIS_1.3.6.1.3.37.2.0.6 isisMaxAreaAddressesMismatch

DescriptionISIS/2/MAXAREA_MISMATCH:OID [oid] The MaxAreaAddress field of received PDU isdifferent from local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer],sysLevel=[integer], pduMaxAreaAddress=[integer], sysInstanceofPduMaxAreaAddress=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFrag=[opaque],ifName=[string])



299

The maximum number of area addresses supported in the header of the received Level-1 PDUmismatched with that supported by the local switch.

Attribute


1.3.6.1.3.37.2.0.6 Major other(1)

Parameters

Name Meaning





pduMaxAreaAddress Indicates the maximum number of area addresses.

sysInstanceofPduMaxAreaAddress Indicates the ID of the IS-IS process.







1. If the trap is triggered by a hardware fault of the board, route flapping may occur and the CPUusage will increase.

2. If the trap is triggered because of the intercommunication failure between switchs, neighborscannot be established, and routes cannot be learnt from each other.



300

Possible Causes

1. The maximum number of area addresses supported by the local switch mismatch the numberof area addresses supported by other switchs.

2. The maximum area address field was modified.

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (inhexadecimal) in the trap and fetch the system ID of the source switch. Then, find the value ofthe pdu-max-area field in the trap and check whether the number of maximum area addressesis neither 0 nor 3.











Step 2 Modify the maximum number of area addresses of the source switch to 3. Then, check whetherthe trap is cleared.



Step 3 View the logs or ping the board to check whether the board has a fault and hence the packet istampered.



Step 4 Change the board. Then, check whether the trap is cleared.




Step 6 End.

----End



301

Related Information

None

29.7 ISIS_1.3.6.1.3.37.2.0.7 isisOwnLSPPurge

Description

ISIS/2/OWNLSP_PURGE:OID [oid] ISIS received a self-originated LSP with the age being 0.(sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer],sysInstanceofInterface=[integer], circuit=[integer], ifIndex=[integer], circuitIfIndex=[integer],pduLspId=[opaque], pduRemoteRouterID=[integer], ifName=[string])

An LSP with the system ID as local IS-IS and the lifetime as 0 was received.

Attribute



Parameters

Name Meaning





sysInstanceofInterface Indicates the ID of the IS-IS process.

circuit Indicates the index of the interface.


circuitIfIndex Indicates the IF index of the interface.

pduLspId Indicates the ID of the LSP.



302

Name Meaning

pduRemoteRouterID Indicates the router ID of the remote system.



1. If the trap triggered by the restart of the local switch, services will not be affected.

2. If the trap is generated frequently, IS-IS routes are affected and packets may not be forwarded.

Possible Causes

1. The local switch did not refresh its LSPs in time. As a result, Purge packets were generatedafter LSPs were aged and flooded to the local switch.

2. The packet was modified and Purge packets were generated because of transmission failure.

3. The local switch was restarted and then received the LSP with the system ID as local IS-ISand the lifetime as 0 from the neighbor.

Procedure

Step 1 Check whether the local switch is restarted.

l If so, it indicates that this trap message is informational only, and no action is required. Goto Step 4.


Step 2 Check whether the IS-IS authentication configuration is modified and hence the Purge packetsare generated and the trap is triggered.

l If so, it indicates that this trap message is informational only, and no action is required. Goto Step 4.



Step 4 End.

----End

Related Information

None

29.8 ISIS_1.3.6.1.3.37.2.0.8 isisSequenceNumberSkip



303

DescriptionISIS/2/SEQNUM_SKIP:OID [oid] ISIS received a self-originated LSP with a greater sequencenumber. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer],sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduLspId=[opaque], ifName=[string])

The sequence number of the local IS-IS LSP irregularly increases.

Attribute


1.3.6.1.3.37.2.0.8 Major other(1)

Parameters

Name Meaning





sysInstanceofCircIfIndex Indicates the ID of the IS-IS process.






Impact on the System1. You can ignore the trap caused by the restart of the local switch, and services will not beaffected.

2. If the trap is triggered by the incorrect configuration, routes will flap frequently.



304

Possible Causes

1. After the IS-IS process was restarted, IS-IS received the LSP with the greater sequence numberand the same LSP ID from the neighbor.

2. The system ID of the local switch was the same as that of another switch. This caused theLSP to be updated continuously.

Procedure

Step 1 Run the display history-command command to check whether the reset isis all command isrun on the local switch to restart the IS-IS process.

l If so, it indicates that this trap message is informational only, and no action is required, goto Step 5.


Step 2 Run the display isis lsdb command to continuously check whether the LSP sequence numberof the local switch increases rapidly, that is, to check whether the actual LSP refresh period isshorter than the value configured through the timer lsp-refresh command.



Step 3 Run the display current-configuration command to check whether there is another switchwhose system ID or virtual system ID is the same as that of the local switch on the network.



Step 4 (Use the undo network-entity command or the undo virtual-system command with caution.)Enter the IS-IS view of the local switch or another switch whose system ID is the same as thesystem ID or the virtual System ID of the local switch. Then run the undo network-entitycommand or the undo virtual-system command to delete the repeated system ID or virtualsystem ID and the network-entity command or the virtual-system command to configure adifferent system ID or virtual system ID for the switch. Check whether the trap is cleared.




Step 6 End.

----End

Related Information

None

29.9 ISIS_1.3.6.1.3.37.2.0.9 isisAuthenticationTypeFailure



305

DescriptionISIS/3/AUTHTYPE_FAIL:OID [oid] The authentication type of received PDU is different fromlocal configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer],sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFrag=[opaque], ifName=[string])

The received packet, including the LSP, CSNP, PSNP, and Hello packet, did not contain theauthentication information, or the authentication type carried in the received packet was differentfrom that of the local switch. For example, one end is configured with MD5 authentication,whereas the other end is configured with simple authentication.

Attribute


1.3.6.1.3.37.2.0.9 Minor other(1)

Parameters

Name Meaning











Impact on the System1. If the authentication of the Hello packet fails, IS-IS neighbors cannot be established.



306

2. If the authentication of the LSP or SNP fails, LSDBs cannot be synchronized; however, IS-IS neighbors can be established.

Possible Causes1. Authentication was configured on the interface or process of the local end. The authenticationtype configured on the peer end was different from that configured on the local end.

2. Authentication was configured on the interface or process of the local end. The peer end,however, was not configured with authentication.

Procedure

Step 1 Check the sysInstance field in the trap to identify the ID of the IS-IS process that receives thepacket, and then check the sysLevel field to identify the level of the packet. The value 1 indicatesLevel-1 packets; the value 2 indicates Level-2 packets; the value 3 indicates P2P Hello packets.According to the IS-IS packet format defined in ISO 10589, check the IfName field in the trapto identify the interface that receives packets. Then, check the PduFrag field in the trap andobtain the system ID of the source router that sends the packet and packet type.l If the type of the packet is Hello, go to Step 2.l If the type of the packet is LSP or SNP, go to Step 4.









Step 2 Run the display isis peer command on the source switch to check the interface that sends thepacket. Run the display this command in the interface view to check whether the interfaceauthentication mode is configured. If the interface authentication mode is configured, checkwhether it is consistent with the interface authentication mode of the local switch.l If so, go to Step 6.l If not, go to Step 3.

Step 3 Run the isis authentication-mode command in the interface view of the source switch toconfigure the same authentication mode as the local switch. Ensure that the authenticationpasswords on the interfaces at both ends are the same. Then, check whether the trap is cleared.l If so, go to Step 7.l If not, go to Step 6.

Step 4 Run the display current-configuration configuration isis command on the source switch tocheck whether the area or domain authentication mode is configured in the IS-IS process. If thearea or domain authentication mode is configured, check whether it is the same as the



307

authentication mode of the local switch, and ensure that the authentication passwords configuredon the two ends are the same.l If so, go to Step 6.l If not, go to Step 5.

Step 5 Run the area-authentication-mode (for Level-1 packets) command or the domain-authentication-mode (for Level-2 packets) command in the IS-IS view of the source switch toconfigure the same authentication mode as the local switch. Then check whether the trap iscleared.l If so, go to Step 7.l If not, go to Step 6.


Step 7 End.

----End


29.10 ISIS_1.3.6.1.3.37.2.0.10 isisAuthenticationFailure

DescriptionISIS/3/AUTH_FAIL:OID [oid] The authentication password of received PDU is different fromlocal configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer],sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFrag=[opaque], ifName=[string])

The received packet, including the LSP, CSNP, PSNP, and Hello packet, contained theauthentication information and the same authentication type carried in the packet was the sameas that configured on the local switch, however, the authentication password in the packet wasdifferent from that configured on the local switch. For example, both ends were configured witheither MD5 authentication or simple authentication, whereas the configured authenticationpasswords were different.

Attribute


1.3.6.1.3.37.2.0.10 Minor environmentalAlarm(6)



308

Parameters

Name Meaning











Impact on the System1. If Hello packet authentication fails, IS-IS neighbors cannot be established.

2. If LSP or SNP packet authentication fails, LSDBs cannot be synchronized; however, IS-ISneighbors can be established.

Possible CausesAuthentication was configured for the interface or process on the local end. The authenticationtypes configured on both ends were the same, whereas the authentication passwords weredifferent.

Procedure

Step 1 Through the parameter in the trap, check the ID of the IS-IS process that receives the packet andcheck the level that the packet belongs to. The value 1 indicates Level-1 packets; the value 2indicates Level-2 packets; the value 3 indicates P2P Hello packets. Based on the IS-IS packetformat defined in ISO10589, search for the if-index field (in decimal) in the trap and convertthe decimal value into a hexadecimal value. Run the display rm interface command on theinterface and search the command output for the information about the interface that receivesthe packet. The value of IfnetIndex in the interface information is the same as the hexadecimal



309

if-index. Then, find the pdu-fragment field in the trap and fetch the system ID of the sourceswitch that sends the packet and packet type.

l If the type of the packet is Hello, go to Step 2.

l If the type of the packet is LSP or SNP, go to Step 4.









Step 2 Run the display isis peer command in the source switch to check the interface that sends thepacket. Enter the interface view and run the display this command to check the password usedfor authentication is the same as that configured on the local switch.



Step 3 Run the isis authentication-mode command in the interface view of the source switch toconfigure the same authentication password as the local switch. Then check whether the trap iscleared.



Step 4 Run the display current-configuration configuration isis command on the source switch tocheck whether the IS-IS process is configured with the same area authentication password ordomain authentication password as the local switch.



Step 5 Run the area-authentication-mode (for Level-1 packets) command or the domain-authentication-mode (for Level-2 packets) command in the IS-IS view of the source switch toconfigure the same authentication password as the local switch. Then check whether the trap iscleared.




Step 7 End.

----End



310

Related Information

None

29.11 ISIS_1.3.6.1.3.37.2.0.11 isisVersionSkew

Description

ISIS/2/VERSION_SKEW:OID [oid] IS-IS received a PDU with incorrect ProtocolVersion.(sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer],sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduProtocolVersion=[integer], pduFragment=[opaque], ifName=[string])

The IS-IS version number of the received Hello packet was inconsistent with that of the Hellopacket supported by the local switch.

Attribute


1.3.6.1.3.37.2.0.11 Major environmentalAlarm(6)

Parameters

Name Meaning









pduProtocolVersion Indicates the protocol version contained in a PDU.



311

Name Meaning

pduFragment Indicates the fragment of 64-byte PDU header.



1. If the board modifies the packet, route flapping may occur, and the CPU usage will increase.

2. If the trap is generated because of intercommunication between switchs, neighbors cannot beestablished, and routes cannot be learnt from each other.

Possible Causes

1. The IS-IS version numbers supported by the local switch and other switchs were inconsistent.

2. The version number field was modified during packet transmission.

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (inhexadecimal) in the trap and fetch the system ID of the source switch. Check whether the valueof version field on the source switch is as 1.











Step 2 View the logs or ping the board to check whether the board has a fault.



Step 3 Change the board. Then check whether the trap is cleared.



Step 4 Check whether the IS-IS version number of the source switch can be modified.



312



Step 5 Modify the IS-IS version number of the source switch. The Huawei switch does not support themodification of the IS-IS version number through a command. Then check whether the trap iscleared.




Step 7 End.

----End

Related Information

None

29.12 ISIS_1.3.6.1.3.37.2.0.12 isisAreaMismatch

Description

ISIS/3/AREA_MISMATCH:OID [oid] IS-IS received a level-1 Hello PDU whose area addressis different from the local area address. (sysInstance=[integer], sysInstanceofLevel=[integer],sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFragment=[opaque], ifName=[string])

The area address of the received Level-1 Hello packet was different from that of the local Level-1IS-IS.

Attribute



Parameters

Name Meaning






313

Name Meaning









1. If the trap is triggered because of a hardware fault of the board, route flapping may occur andthe CPU usage will increase.

2. If the trap is triggered because of incorrect configuration, neighbors cannot be established,and routes cannot be learnt from each other.

Possible Causes

1. The configuration was incorrect.

2. The area address field was modified.

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (inhexadecimal) in the trap and fetch the system ID of the source switch. Then, run the displaythis command in the IS-IS view to check whether the area address configured on the sourceswitch is the same as that of the local switch.









314






Step 2 (Run the undo network-entity command with caution.) Run the network-entity command inthe IS-IS view of the source switch to configure a new IS-IS area address so that the area addressof the switch is consistent with that of the local switch. Then, check whether the trap is cleared.l If so, go to Step 4.l If not, go to Step 3.


Step 4 End.

----End


29.13 ISIS_1.3.6.1.3.37.2.0.13 isisRejectedAdjacency

DescriptionISIS/3/REJECT_ADJ:OID [oid] IS-IS failed to establish the adjacency with its peer.(sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer],sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFragment=[opaque], ifName=[string], hwIsisAdjChangeReason=[integer],hwIsisAdjChangeSubReason=[integer])

The local switch received a Hello packet sent by the adjacent switch, but cannot establish theIS-IS neighbor relationship with the adjacent switch.

Attribute





315

Parameters

Name Meaning











hwIsisAdjChangeReason Indicates the main cause of the change in the neighborrelationship.

hwIsisAdjChangeSubReason Indicates details about the cause of the change in the neighborrelationship.


The neighbor relationship cannot be established.

Possible Causes

1. The system ID or virtual system ID of the local switch is the same as the system ID of theneighbor.

2. The authentication mode or the authentication password configured for the interface on thelocal switch was inconsistent with that configured on the neighbor. As a result, the authenticationof the Hello packet failed.

3. The Level-1 area address of the IS-IS neighbor was inconsistent with the Level-1 area addressof the local switch.



316

4. The local interface received a Hello packet whose level is inconsistent with the local switchlevel.

5. In a broadcast network, the local interface received a Hello packet sent by the adjacent interfacewhose IP address is on a different network segment.

6. In a P2P network, because the isis peer-ip-ignore is not configured, the local interface receiveda Hello packet sent by the adjacent interface whose IP address is on a different network segment.

Procedure

Step 1 Check the IfName field in the trap to identify the interface that receives packets.

l If the interface is a broadcast interface, go to Step 2.

l If the interface is a P2P interface, go to Step 7.

Step 2 Check the PduFragment field in the trap, and then identify the source switch according to theconsecutive six bytes beginning with the tenth byte, which indicates the system ID of the sourceswitch. Run the display this command in the views of interfaces on the two ends of the link andin the IS-IS process view to check whether the IS-IS levels and interface levels on both ends ofthe link are consistent.



Step 3 Run the isis circuit-level command in the interface view to change the IS-IS levels and interfacelevels on both ends of the link to be consistent. Then, check whether the trap is cleared.



Step 4 Run the display ip interface command to check whether the IP address of the interface on thesource switch is on the same network segment as the IP address of the local interface.



Step 5 Run the ip address command in the interface views of the source switch and local switch toconfigure IP addresses of interfaces on both ends to belong to the same network segment. Then,check whether the trap is cleared.



Step 6 Run the display this command in the interface views of the source switch and local switch tocheck whether the isis peer-ip-ignore command is run.



Step 7 Run the isis peer-ip-ignore or ip address command in the interface views of the sourceswitch and local switch to configure IP addresses of interfaces on both ends to belong to thesame network segment. Then, check whether the trap is cleared.





317

Step 8 Check whether the Level-1 area addresses on both ends of the link are the same.



Step 9 Run the network-entity command in the IS-IS view to configure a new area address to ensurethat the Level-1 area addresses on both ends are the same. Then, check whether the trap is cleared.



Step 10 Run the display current-configuration command to check whether the system ID of the sourceswitch is the same as the system ID or virtual system ID of the local switch.



Step 11 (Run the undo network-entity command with caution.) Change the system ID or virtual systemID on one switch to ensure that the system IDs or virtual system IDs on both ends are different.Then, check whether the trap is cleared.



Step 12 Check IS-IS authentication modes and authentication passwords of interfaces on both ends arethe same.



Step 13 Run the isis authentication-mode command in the views of interface on both ends to changethe authentication mode and authentication password to ensure that IS-IS authentication modesand authentication passwords of interfaces on both ends are consistent. Alternatively, run theundo isis authentication-mode command in the views of interface on both ends to disable IS-IS authentication (disabling IS-IS authentication degrades the system security). Then, checkwhether the trap is cleared.



Step 14 Collect the trap information, log information, and configuration, and then contact Huaweitechnical personnel.

Step 15 End.

----End

Related Information

None

29.14 ISIS_1.3.6.1.3.37.2.0.14 isisLSPTooLargeToPropagate



318

Description

ISIS/4/LARGE_LSP:OID [oid] The length of the PDU to be sent is greater than the MTU.(sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer],sysInstanceofCircIfIndex=[integer], circIndex=[integer], circIfIndex=[integer],lspSizeSupport=[integer], pduLspId=[opaque])

The length of the PDU to be sent is greater than the MTU of the interface.

Attribute


1.3.6.1.3.37.2.0.14 Warning environmentalAlarm(6)

Parameters

Name Meaning


sysInstance IS-IS process ID

sysInstanceofLevel IS-IS process ID

sysLevel IS-IS level:l 1: Level-1l 2: Level-2

sysInstanceofCircIfIndex IS-IS process ID

circIndex Interface index

circIfIndex IS-IS interface index

lspSizeSupport Maximum LSP length

pduLspId LSP ID


None.

Possible Causes

The LSP to be forwarded exceeds the interface MTU.



319

Procedure

Step 1 Run the display ip interface interface-type interface-number command to view the interfaceMTU. The Maximum Transmit Unit in the command output shows the MTU value.

Step 2 Run the display current-configuration configuration isis command to view the maximum LSPlength. lsp-length originate in the command output shows the maximum LSP length. If thecommand output does not show a setting, the default value is used. The default maximum LSPis 1497 bytes.

Step 3 Run the lsp-length originate command in the IS-IS view to change the maximum LSP lengthto a value smaller than the interface MTU.

Step 4 Check whether the alarm is cleared.l If the alarm is cleared, go to Step 6.l If the alarm persists, go to Step 5.


Step 6 End.

----End


29.15 ISIS_1.3.6.1.3.37.2.0.15 isisOrigLSPBuffSizeMismatch

DescriptionISIS/3/LSPMTU_MISMATCH: OID [oid] The size of the local buffer for originating IS-ISLSPs is smaller than the size of the received LSP. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer],ifIndex=[integer], circIfIndex=[integer], pduLspId=[opaque], pduOriginatingBufferSize=[integer], ifName=[string])

The size of the local buffer for originating LSPs is smaller than the size of the received LSP.

Attribute





320

Parameters

Name Meaning










pduOriginatingBufferSize Indicates the buffer size for originating LSPs.



Routes cannot be learnt, and traffic forwarding is affected.

Possible Causes

The size of the LSPs originated from IS-IS on the source switch is larger than the size of thelocal buffer for originating LSPs.

Procedure

Step 1 Run the display current-configuration configuration isis command on the local device tocheck the size of LSPs. If the command output does not contain the LSP size, the default LSPsize is used. Run the display default-parameter isis command to check the LSP-Receive-Length field.

Step 2 Find the source switch from which the LSPs are originated based on the lsp-id field value in thetrap output. Run the display current-configuration configuration isis command to check thesize of the LSPs on the source switch. If the command output does not contain the LSP size, the



321

default LSP size is used. Run the display default-parameter isis command to check the LSP-Originate-Length field.

Step 3 Check whether the value obtained in Step 1 is smaller than that obtained in Step 2.



Step 4 Perform the following steps as required:

l If the size of the local receiving buffer for LSPs is a default value, go to Step 5.

l If the size of LSPs originated from the source switch is a default value, go to Step 6.

Step 5 Run the lsp-length orignate command in the IS-IS process of the source switch to modify thesize of LSPs, and ensure that the size is smaller than or equal to the size of the local receivingbuffer. Then, check whether the trap is cleared.



Step 6 Run the lsp-length recieve command in the IS-IS process to modify the size of the LSPs thatcan be received by the local switch, and ensure that the size is greater than or equal to the sizeof LSPs sent from the source switch. Then, check whether the trap is cleared.



Step 7 Collect the trap information, log information, and configuration of the switch, and contact theHuawei technical support personnel.

Step 8 End.

----End

Related Information

None.

29.16 ISIS_1.3.6.1.3.37.2.0.16isisProtocolsSupportedMismatch

Description

ISIS/2/PROTO_MISMATCH:OID [oid] The protocol of received Protocol TLV is mismatchedwith local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer],circIfIndex=[integer], pduProtocolsSupported=[opaque], pduLspId=[opaque], pduFragment=[opaque], ifName=[string])

The type of the protocol supported TLV (the type field being 0x81) carried in the received LSPmismatched with the type of the protocol supported by the local switch.



322

Attribute



Parameters

Name Meaning









pduProtocolsSupported Indicates the supported protocol.





LSPs cannot be learnt, and routes cannot be generated.

Possible Causes

The protocol type supported by the source switch that generated the LSP was different from thatsupported by the local switch.



323

Procedure

Step 1 The type of the protocol supported TLV carried in the received LSP mismatched with the typeof the protocol supported by the local switch. Check whether the trap is cleared in 10 minutes.




Step 3 End.

----End

Related Information

None

29.17 ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange

Description

ISIS/2/ADJ_CHANGE:OID [oid] The state of IS-IS adjacency changed. (sysInstance=[integer],sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofInterface=[integer], circuit=[integer], ifIndex=[integer], circuitIfIndex=[integer], lspID=[opaque], adjState=[integer],ifName=[string], hwIsisAdjChangeReason=[integer], hwIsisAdjChangeSubReason=[integer])

The status of the neighbor changed.

Attribute



Parameters

Name Meaning






324

Name Meaning


sysInstanceofInterface Indicates the ID of the IS-IS process.

circuit Indicates the ID of the circuit.


circuitIfIndex Indicates the IF index of the interface.

lspID Indicates the ID of the LSP.

adjState Indicates the status of the neighbor.l 1: downl 2: initializingl 3: upl 4: failed


hwIsisAdjChangeReason Indicates the main cause of the change in the neighborrelationship:l 1: peer hold timer expirel 2: physical interface changel 3: protocol reasonl 4: BFD session get downl 5: configuration changel 6: reason of peer routerl 7: other reasonl 8: alarm is cleared



325

Name Meaning

hwIsisAdjChangeSubReason Indicates details about the cause of the change in the neighborrelationship:l 1: status of peer relation get upl 2: peer is deletedl 3: delete interfacel 4: interface is silentl 5: receive invalid hello packetsl 6: authentication faill 7: system ID is conflictl 8: maximum area address number is mismatchl 9: L1 area addresses are not samel 10: the router can not receive hello packetsl 11: interface is downl 12: protocols are mismatchl 13: delete adjacency for spacel 14: BFD session get downl 15: level changel 16: P2P negotiations changel 17: reset peerl 18: interface type changel 19: reset IS-ISl 20: undo networkl 21: undo isisl 22: level mismatchl 23: no SNP for broadcastl 24: Three-way adjacency not upl 25: topology mismatchl 26: circuit ID mismatchl 27: Three-way adjacency state is downl 28: other errorsl 29: optional checksum TLV check failed


IS-IS may re-calculate routes, which causes route flapping and interrupts the IS-IS service.

Possible Causes

1. The IS-IS neighbor relationship went Up or Down.



326

2. The IS-IS configuration was incorrect.

3. The system was busy, and consequently the IS-IS neighbor relationship was intermittentlyinterrupted.

4. The link failed, and consequently the status of the IS-IS neighbor relationship was changed.

Procedure

Step 1 According to the IS-IS packet format defined in ISO 10589, find the LspID field (in hexadecimalformat) in the trap to identify the system ID of the source switch. Then, check whether theneighbor status on both ends is the same.



Step 2 Download the user logs from the source switch, and then find out the cause for the neighborstatus change according to the logs. Check whether the neighbor status is changed because theinterface goes Down.



Step 3 Find information about the local interface from the logs, and then check the interface status andMTU status on the interface. Ensure that both the interface status and MTU status on two endsare Up. Then, check whether the neighbor status on both ends is the same.



Step 4 Check the system IDs and ensure that the system IDs on both ends are correct. Then, checkwhether the neighbor status on both ends is the same.



Step 5 Check the levels of the IS-IS process and ensure that levels on both ends match. Then, checkwhether the neighbor status on both ends is the same.



Step 6 Check the area ID of the switch and ensure that area IDs on both ends are the same. Then, checkwhether the neighbor status on both ends is the same.



Step 7 Check that IP addresses of interfaces on both ends belong to the same network segment. Then,check whether the neighbor status on both ends is the same.



Step 8 Check whether the authentication mode is configured on both ends and ensure that the encryptionauthentication modes on both ends are the same. If authentication is required, ensure that theauthentication modes and passwords on both ends are the same. Otherwise, authentication is



327

disabled on both ends (disabling authentication degrades the system security). Then, checkwhether the neighbor status on both ends is the same.



Step 9 Check whether interfaces on both ends can transmit Hello packets normally and ensure that theycan transmit Hello packets normally. Then, check whether the neighbor status on both ends isthe same.



Step 10 Run the display cpu-usage command to check whether the CPU usage remains 100% in a periodof time.



Step 11 Run the isis timer hello command in the interface view to set the interval for sending Hellopackets to a larger value, which increases by 10s each time. Prolonging the interval for sendingHello packets slows down the detection of network faults and thus slows down routeconvergence. Then, check whether the neighbor statuses on both ends are the same.



Step 12 Collect the trap information, log information, and configuration, and then contact Huaweitechnical personnel.

Step 13 End.

----End

Related Information

None

29.18 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.1hwIsisSystemIdConflict

Description

ISIS/2/SYSTEM_ID_CONFLICT:OID [oid] System ID may conflict.(sysProcIndexofDyname=[integer], hwisisSysInstance=[integer], hwisisSysLevelIndex =[integer], OwnSystemId=[opaque], OwnDynamicName=[string], AdjSystemId=[opaque],AdjDynamicName=[string])

Intermediate System to Intermediate System (IS-IS) detected that system IDs conflicted.



328

Attribute



Parameters

Name Meaning

oid ID of the management information base (MIB) object

sysProcIndexofDyname Index of the dynamic hostname of the local router

hwisisSysInstance Conflicting system ID

hwisisSysLevelIndex Level of the process in which system IDs conflicted

OwnSystemId System ID of the local router

OwnDynamicName Dynamic hostname of the local router

AdjSystemId System ID of the neighbor

AdjDynamicName Dynamic hostname of the neighbor


Link state protocol data units (LSPs) are frequently updated, and route flapping occurs.

Possible Causes

Two or more routers in the IS-IS area had the same system ID.

Procedure

Step 1 View the OwnSystemId and hwisisSysInstance parameters in the alarm information to checkwhether the system ID of the local router is the same as the conflicting system ID.

l If the system ID of the local router is the same as the conflicting system ID, change the systemID of the local router. Then check whether the alarm is cleared. If the alarm is cleared, go tostep 4. If the alarm persists, go to step 3.

l If the system ID of the local router is different from the conflicting system ID, go to step 2.

Step 2 Check the system IDs of other routers on the network, and change the system IDs that are thesame as the conflicting system ID in the alarm information. Then check whether the alarm iscleared.



329

l If the alarm is cleared, go to step 4.

l If the alarm persists, go to step 3.

Step 3 Collect alarm, log, and configuration information, and contact Huawei technical supportpersonnel.

Step 4 End.

----End

Related Information

None.

29.19 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.2hwIsisL1ImportRouteExceedLimit

Description

ISIS/2/L1_REDIST_EXCEED_LIMIT:OID [oid] The number of level-1 imported routes hasexceeded the maximum limit. (sysInstance=[integer], sysProtocol=[integer], sysMTIndex=[integer], sysMaxLimit=[integer], sysTotalRedist=[integer])

The number of imported routes that the routers in the Intermediate System to IntermediateSystem (IS-IS) Level-1 area advertised exceeded the configured maximum number.

Attribute



Parameters

Name Meaning


sysInstance Number of the IS-IS process

sysProtocol Protocol typel 1: IPv4l 2: IPv6

sysMTIndex Multi-topology ID



330

Name Meaning

sysMaxLimit Maximum number of imported routes that the routers in the IS-IS Level-1 areacan advertise

sysTotalRedist Number of routes imported by IS-IS

Impact on the SystemSome imported routes are not advertised.

Possible CausesThe number of imported routes that the routers in the IS-IS Level-1 area advertised exceededthe maximum number of imported routes that the routers in the IS-IS Level-1 area can advertise.

Procedure

Step 1 Run the display current-configuration command to check the configuration.l If the configured maximum number of imported routes is improper, run the import-route

limit command to modify it.l If the configured maximum number is proper, go to Step 2.

Step 2 If incorrect external routes have been imported into the IS-IS process, run the undo import-route command in the IS-IS view to disable external routes from being imported. Then checkwhether the alarm is cleared.l If the alarm is cleared, go to Step 3.l If the alarm persists, go to Step 2.


Step 4 End.

----End


29.20 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.3hwIsisL1ImportRouteRestoreToLimit

DescriptionISIS/2/L1_REDIST_RESTORE_TO_LIMIT:OID [oid] The number of level-1 imported routesis restored to less than or equal to the maximum limit. (sysInstance=[integer], sysProtocol=[integer], sysMTIndex=[integer], sysMaxLimit=[integer], sysTotalRedist=[integer])



331

The number of imported routes that the routers in the Intermediate System to IntermediateSystem (IS-IS) Level-1 area advertised was less than or equal to the configured maximumnumber. All imported routes were advertised properly.

Attribute



Parameters

Name Meaning








Possible CausesThe number of imported routes that the IS-IS Level-1 router advertised was less than or equalto the configured maximum number.

Procedure

Step 1 The alarm is informational only, and no action is required.

----End




332

29.21 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.4hwIsisL2ImportRouteExceedLimit

Description

ISIS/2/L2_REDIST_EXCEED_LIMIT:OID [oid] The number of level-2 imported routes hasexceeded the maximum limit. (sysInstance=[integer], sysProtocol=[integer], sysMTIndex=[integer], sysMaxLimit=[integer], sysTotalRedist=[integer])

The number of imported routes that the routers in the Intermediate System to IntermediateSystem (IS-IS) Level-2 area advertised exceeded the configured maximum number.

Attribute



Parameters

Name Meaning








Some imported routes are not advertised.



333

Possible Causes

The number of imported routes that the routers in the IS-IS Level-2 area advertised exceededthe maximum number of imported routes that the routers in the IS-IS Level-2 area can advertise.

Procedure

Step 1 Run the display current-configuration command to check the configuration.

l If the configured maximum number of imported routes is improper, run the import-routelimit command to modify it.

l If the configured maximum number is proper, go to Step 2.

Step 2 If incorrect external routes have been imported into the IS-IS process, run the undo import-route command in the IS-IS view to disable external routes from being imported. Then checkwhether the alarm is cleared.


l If the alarm persists, go to Step 2.


Step 4 End.

----End

Related Information

None.

29.22 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.5hwIsisL2ImportRouteRestoreToLimit

Description

ISIS/2/L2_REDIST_RESTORE_TO_LIMIT:OID [oid] The number of level-2 imported routesis restored to less than or equal to the maximum limit. (sysInstance=[integer], sysProtocol=[integer], sysMTIndex=[integer], sysMaxLimit=[integer], sysTotalRedist=[integer])

The number of imported routes that the routers in the Intermediate System to IntermediateSystem (IS-IS) Level-2 area advertised was less than or equal to the configured maximumnumber. All imported routes were advertised properly.

Attribute





334

Parameters

Name Meaning








Possible CausesThe number of imported routes that the routers in the IS-IS Level-2 area advertised was less thanor equal to the maximum number of imported routes that the routers in the IS-IS Level-2 areacan advertise.

Procedure


----End


29.23 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.6hwIsisL1ImportRouteThresholdReach

DescriptionISIS/4/L1_REDIST_THRESHOLD_REACH:OID [oid] The number of level-1 imported routeshas reached the upper threshold value. (sysInstance=[integer], sysProtocol=[integer],



335

sysMTIndex=[integer], sysMaxLimit=[integer], sysUpperThresholdValue=[integer],sysLowerThresholdValue=[integer], sysTotalRedist=[integer])

The number of external routes imported to an IS-IS Level-1 area reached the configured upperthreshold for advertising routes.

Attribute



Parameters

Name Meaning


sysInstance ID of an IS-IS process

sysProtocol Protocol typesl 1: IPv4l 2: IPv4


sysMaxLimit Maximum number of imported routes that are allowed to beadvertised

sysUpperThresholdValue Alarm upper threshold

sysLowerThresholdValue Alarm lower threshold

sysTotalRedist Number of imported routes

Impact on the SystemSome of the imported routes cannot be advertised.

Possible CausesThe number of imported routes reached the configured threshold.

Procedure

Step 1 Run the display current-configuration command to view limitations on the number of routesthat can be imported.



336

l If the configured threshold is small, run the import-route limit command to change thethreshold to a proper value.

l If the configured threshold is proper, go to Step 2.

Step 2 Check whether the routes are correctly imported in the IS-IS process. If external routes areimported incorrectly, run the undo import-route command in the IS-IS view to delete the routesthat are imported incorrectly. Then check whether the alarm is cleared.




Step 4 End.

----End

29.24 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.7hwIsisL1ImportRouteThresholdReachClear

Description

ISIS/4/L1_REDIST_THRESHOLD_REACH_CLEAR:OID [oid] The number of level-1imported routes has been less than the lower threshold value. (sysInstance=[integer],sysProtocol=[integer], sysMTIndex=[integer], sysMaxLimit=[integer],sysUpperThresholdValue=[integer], sysLowerThresholdValue=[integer], sysTotalRedist=[integer])

IS-IS was restored from threshold state, all routes imported by an IS-IS Level-1 area could beadvertised.

Attribute



Parameters

Name Meaning





337

Name Meaning








Possible CausesThe number of imported routes fell below the configured threshold.

Procedure


----End

29.25 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.8hwIsisL2ImportRouteThresholdReach

DescriptionISIS/4/L2_REDIST_THRESHOLD_REACH:OID [oid] The number of level-2 imported routeshas reached the upper threshold value. (sysInstance=[integer], sysProtocol=[integer],sysMTIndex=[integer], sysMaxLimit=[integer], sysUpperThresholdValue=[integer],sysLowerThresholdValue=[integer], sysTotalRedist=[integer])

The number of Level-2 imported routes reached the configured upper threshold.



338

Attribute



Parameters

Name Meaning










Some of the imported routes cannot be advertised.

Possible Causes

The number of imported routes reached the configured threshold.

Procedure

Step 1 Run the display current-configuration command to view the threshold of routes that can beimported.

l If the configured threshold is small, run the import-route limit command to change thethreshold to a proper value.

l If the configured threshold is proper, go to Step 2.



339

Step 2 Check whether the routes are correctly imported in the IS-IS process. If external routes areimported incorrectly, run the undo import-route command in the IS-IS view to delete the routesthat are imported incorrectly. Then check whether the alarm is cleared.




Step 4 End.

----End

Related Information

None.

29.26 ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.9hwIsisL2ImportRouteThresholdReachClear

Description

ISIS/4/L2_REDIST_THRESHOLD_REACH_CLEAR:OID [oid] The number of level-2imported routes has been less than the lower threshold value. (sysInstance=[integer],sysProtocol=[integer], sysMTIndex=[integer], sysMaxLimit=[integer],sysUpperThresholdValue=[integer], sysLowerThresholdValue=[integer], sysTotalRedist=[integer])

IS-IS was restored from threshold state, all routes imported by an IS-IS Level-2 area could beadvertised.

Attribute



Parameters

Name Meaning





340

Name Meaning








None.

Possible Causes

The number of imported routes fell below the configured threshold.

Procedure


----End

Related Information

None.

29.27 ISIS-STD_1.3.6.1.2.1.138.0.1 isisDatabaseOverload

Description

ISIS-STD/3/OLOAD:OID [oid] The overload state of IS-IS LSDB changed. (sysLevel=[integer], NotificationSysLevelIndex=[integer], OverLoadState=[integer])

The IS-IS LSDB entered or exited from the overload state.



341

Attribute


1.3.6.1.2.1.138.0.1 Minor other(1)

Parameters

Name Meaning

oid MIB object ID

SysLevel IS-IS level:l 1: Level-1l 2: Level-2

NotificationSysLevelIndex IS-IS level of a device that sends the trap

OverLoadState Overload state

Impact on the System1. If the trap is generated because the IS-IS LSDB entered or exited from the overload state,route selection on the IS-IS neighbor will be affected.

2. If the trap is generated because the memory usage exceeds the upper threshold, the IS-ISLSDB is unreliable.

Possible CausesCause 1: The set-overload or undo set-overload command was run in the IS-IS view.

Cause 2: After the set-overload on-startup command was run in the IS-IS view, the switchrestarted.

Cause 3: The IS-IS process entered the Overload state and then exited from it.

Cause 4: Applying for memory resources failed in the case of memory shortage, causing a systemcrash.

Procedure

Step 1 Run the display this command in the IS-IS view to check whether the set-overload or undoset-overload command has been run in the process.l If set-overload or undo set-overload command has been run in the process, go to Step 5.l If set-overload or undo set-overload command has not been run in the process, go to Step

2.

Step 2 Run the display memory-usage command to check whether the memory usage of the switchhas reached the upper threshold.



342

l If the memory usage has reached the upper threshold, go to Step 3.

l If the memory usage has not reached the upper threshold, go to Step 4.

Step 3 Obtain the logs.


Step 5 End.

----End

Related Information

None

29.28 ISIS-STD_1.3.6.1.2.1.138.0.2 isisManualAddressDrops

Description

ISIS-STD/2/MANAREA_DROP:OID [oid] Some area addresses were discarded because thenumber of area addresses exceeded three. (ManAreaAddr=[opaque])

On a Level-1-2 switch, IS-IS leaked Level-1 area addresses to the Level-2 area, increasing thearea addresses of the Level-2 area to more than 3. In this case, IS-IS used the top three smallestarea addresses as the Level-2 area addresses, causing address loss in the local Level-2 area.

Attribute


1.3.6.1.2.1.138.0.2 Major other(1)

Parameters

Name Meaning


ManAreaAddr Area address


Area addresses are lost in the local IS-IS Level-2 area.



343

Possible Causes

On a Level-1-2 switch, IS-IS leaked Level-1 area addresses to the Level-2 area, increasing thearea addresses of the Level-2 area to more than 3. In this case, IS-IS used the top three smallestarea addresses as the Level-2 area addresses.

Procedure

Step 1 Run the display isis lsdb level-1 verbose command to view details about the Level-1 LSDB.Based on the information about the AREA ADDR field in the LSP with the fragment numberbeing 0, you can determine whether the number of Level-1 area addresses is greater than 3.

l If the number of Level-1 area addresses is greater than 3, go to Step 2.

l If the number of Level-1 area addresses is not greater than 3, go to Step 3.

Step 2 Run the undo network-entity command (exercise caution when running this command) in theIS-IS view to delete IS-IS area addresses, and then run the network-entity command in the IS-IS view to configure new IS-IS area addresses to ensure that there are not more than threedifferent IS-IS area addresses in the Level-1 area that is connected to the Level-1-2 router. Then,run the display isis lsdb command to check whether the Level-1 area addresses are the same asthe Level-2 area addresses in the LSPs with the fragment number being 0 on the local switch.

l If the Level-1 area addresses are the same as the Level-2 area addresses in the LSPs with thefragment number being 0, go to Step 4.

l If the Level-1 area addresses are different from the Level-2 area addresses in the LSPs withthe fragment number being 0, go to Step 3.


Step 4 End.

----End

Related Information

None

29.29 ISIS-STD_1.3.6.1.2.1.138.0.3isisCorruptedLSPDetected

Description

ISIS-STD/3/CORRUPT_LSP:OID [oid] The checksum of LSP is wrong.(NotificationSysLevelIndex=[integer], PduLspId=[opaque])

When an IS-IS switch sent LSP packets, LSP checksum authentication failed.



344

Attribute


1.3.6.1.2.1.138.0.3 Minor other(1)

Parameters

Name Meaning



PduLspId LSP ID

Impact on the SystemThe LSP checksum authentication failure causes the IS-IS process to restart and IS-IS servicesto be interrupted.

Possible CausesCause 1: During the LSP refreshment period, a memory fault caused the LSPs to be changed.

Cause 2: LSPs with non-zero checksum did not pass checksum authentication in the local LSDB.

Procedure

Step 1 Run the display memory-usage command to check whether the memory usage exceeds theupper threshold (around 80%).l If the memory usage has reached the upper threshold, go to Step 3.l If the memory usage has not reached the upper threshold, go to Step 2.

Step 2 Run the reset isis all command to restart the IS-IS process, and then check whether the trap iscleared.l If the trap is cleared, go to Step 4.l If the trap is not cleared, go to Step 3.


Step 4 End.

----End




345

29.30 ISIS-STD_1.3.6.1.2.1.138.0.4isisAttemptToExceedMaxSequence

Description

ISIS-STD/3/MAXSEQ_EXCEED:OID [oid] The LSP sequence number almost reaches themaximum value. (NotificationSysLevelIndex=[integer], PduLspId=[opaque])

The IS-IS LSP sequence number almost reached the maximum value.

Attribute


1.3.6.1.2.1.138.0.4 Minor other(1)

Parameters

Name Meaning



PduLspId LSP ID


After the LSP sequence number of an LSP reaches 0xFFFFFFFF, the IS-IS process will stoprunning for a period of time (the period equal the sum of the maximum lifetime of an LSP andthe aging time of an LSP), causing IS-IS services to be interrupted.

Possible Causes

The sequence number of a locally generated LSP reached 0xFFFFFFFF.

Procedure

Step 1 After the sequence number of an LSP reaches 0xFFFFFFFF (it equals the maximum lifetimeplus 60s, and the default maximum lifetime is 1200s), the sequence number of the LSP beginsfrom 0 again. Run the display isis lsdb local command to view the sequence number of an LSPgenerated by the local switch,

l If the sequence number matches the configured update time, go to Step 5.

l If the sequence number increases quickly, go to Step 2.



346

Step 2 Check whether the system IDs of other switchs in the domain are the same as the system ID orvirtual system ID of the local switch.l If the system IDs of other switchs in the domain are the same as the system ID or virtual

system ID of the local switch, go to Step 3.l If the system IDs of other switchs in the domain are different from the system ID or virtual

system ID of the local switch, go to Step 4.

Step 3 Exercise caution when running the undo network-entity or undo virtual-system command.Run the undo network-entity or undo virtual-system command in the IS-IS view of the localswitch or other switchs that have the same system ID or virtual system ID with the localswitch to delete the system ID or virtual system ID. Run the network-entity or virtual-system command to configure a new system ID or virtual system ID for the switch. Checkwhether the trap is cleared.l If the trap is cleared, go to Step 5.l If the trap is not cleared, go to Step 4.


Step 5 End.

----End


29.31 ISIS-STD_1.3.6.1.2.1.138.0.5 isisIDLenMismatch

DescriptionISIS-STD/2/SYSID_MISMATCH:OID [oid] The ID length of received PDU is different fromlocal configuration. (NotificationSysLevelIndex=[integer], PduFieldLen=[integer],CircIfIndex=[integer], PduFrag=[opaque])

The length of the System ID contained in the received PDU (including all types of IS-IS packets)header mismatched that of the System ID on the local switch.

Attribute


1.3.6.1.2.1.138.0.5 Major other(1)



347

Parameters

Name Meaning



PduFieldLen Length of the received PDU

CircIfIndex Interface index

PduFrag 64-byte PDU header


1. If the trap is triggered by a hardware fault on the board, route flapping may occur.

2. If the trap is triggered by communication between devices, neighbor relationships cannot beestablished, and routes cannot be learned from each other.

Possible Causes

Cause 1: The length of the System ID supported by the local switch mismatched that of theSystem ID supported by another switch.

Cause 2: The value of the System ID Length field was changed.

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, check the pdu-fragment field value (inhexadecimal) and obtain the system ID of the source switch. Check whether the length of thesystem ID is neither 0 nor 6.

l If the length of the system ID is neither 0 nor 6, go to Step 2.

l If the length of the system ID is 0 or 6, go to Step 3.

Table 29-7 Methods of identifying system IDs and types of IS-IS packets

Identifying the Packet Type Identifying the System ID

Hello: A Hello packet is identified when the5th byte in the pdu-fragment field is 0f, 10,or 11.

The six consecutive bytes beginning with the10th byte in the pdu-fragment fieldconstitute a System ID.

LSP: An LSP is identified when the 5th bytein the pdu-fragment field is 12 or 14.




348


SNP: An SNP is identified when the 5th bytein the pdu-fragment field is 18, 19, 1A, or1B.


Step 2 Change the System ID length of the source switch to 6 and check whether the trap is cleared.l If the trap is cleared, go to Step 6.l If the trap is not cleared, go to Step 3.

Step 3 Check the logs and ping packets to determine whether a hardware fault of the board causes thepackets to be changed.l If a hardware fault of the board causes the packets to be changed, go to Step 4.l If the packets are changed due to other reasons, go to Step 5.

Step 4 Replace the board. Then check whether the trap is cleared.l If the trap is cleared, go to Step 6.l If the trap is not cleared, go to Step 5.


Step 6 End.

----End


29.32 ISIS-STD_1.3.6.1.2.1.138.0.6isisMaxAreaAddressesMismatch

DescriptionISIS-STD/2/MAXAREA_MISMATCH:OID [oid] The MaxAreaAddress field of received PDUis different from local configuration. (NotificationSysLevelIndex=[integer],PduMaxAreaAddress=[integer], CircIfIndex=[integer], PduFrag=[opaque])

The maximum number of area addresses in the received Level-1 PDU header mismatched themaximum number of area addresses supported by the local device.

Attribute


1.3.6.1.2.1.138.0.6 Major other(1)



349

Parameters

Name Meaning



PduMaxAreaAddress Maximum number of area addresses contained in a received PDUheader




1. If the trap is triggered by a hardware fault on the board, route flapping may occur and theCPU usage increases.

2. If the trap is triggered by communication between devices, neighbor relationships cannot beestablished, and routes cannot be learned from each other.

Possible Causes

Cause 1: The maximum number of area addresses supported by the local switch mismatchedthat supported by another switch.

Cause 2: The maximum area address field was modified.

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, check the pdu-fragment field value (inhexadecimal) and obtain the system ID of the source switch. Check the pdu-max-area fieldvalue and determine whether the maximum number of area addresses is neither 0 nor 3.

l If the maximum number of area addresses is neither 0 nor 3, go to Step 2.

l If the maximum number of area addresses is 0 or 3, go to Step 3.









350




Step 2 Change the maximum number of area addresses on the source switch to 3 and check whetherthe trap is cleared.

l If the trap is cleared, go to Step 6.

l If the trap is not cleared, go to Step 3.

Step 3 Check the logs and ping packets to determine whether a hardware fault of the board causes thepackets to be changed.

l If a hardware fault of the board causes the packets to be changed, go to Step 4.

l If the packets are changed due to other reasons, go to Step 5.

Step 4 Replace the board. Then check whether the trap is cleared.




Step 6 End.

----End

Related Information

None

29.33 ISIS-STD_1.3.6.1.2.1.138.0.7 isisOwnLSPPurge

Description

ISIS-STD/2/OWNLSP_PURGE:OID [oid] ISIS received a self-originated LSP with the agebeing 0. (NotificationSysLevelIndex=[integer], CircuitIfIndex=[integer], PduLspId=[opaque])

IS-IS received an LSP with the same system ID as that of the device and the lifetime of 0.

Attribute





351

Parameters

Name Meaning



CircuitIfIndex Interface index

PduLspId LSP ID

Impact on the System1. If the trap is triggered by the restart of the switch, services will not be affected.

2. If the trap is generated frequently, IS-IS routes will be affected and traffic forwarding mayfail.

Possible CausesCause 1: The local switch did not refresh LSPs in time. As a result, purge packets were generatedafter these LSPs aged out and flooded to the local switch.

Cause 2: Packets were changed due to a transmission failure and purge packets were generated.

Cause 3: After the local switch restarted, it received an LSP with the same system ID as that ofthe local switch the lifetime of 0.

Procedure

Step 1 Check whether the local switch restarts.l If the local switch restarts, this trap message is informational only, and no action is required,

go to Step 4.l If the local switch does not restart, go to Step 2.

Step 2 Check whether the IS-IS authentication configuration is changed on the switch.l If the IS-IS authentication configuration is changed, this trap message is informational only,

and no action is required, go to Step 4.l If the IS-IS authentication configuration is not changed, go to Step 3.


Step 4 End.

----End




352

29.34 ISIS-STD_1.3.6.1.2.1.138.0.8isisSequenceNumberSkip

Description

ISIS-STD/2/SEQNUM_SKIP:OID [oid] ISIS received a self-originated LSP with a greatersequence number. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduLspId=[opaque])

When local LSPs were refreshed, the sequence numbers of the LSPs increased irregularly.

Attribute


1.3.6.1.2.1.138.0.8 Major other(1)

Parameters

Name Meaning




PduLspId LSP ID


1. If the trap is triggered by the restart of the switch, services will not be affected.

2. If the trap is triggered by incorrect configurations, route flapping will occur frequently.

Possible Causes

Cause 1: After an IS-IS process was restarted, IS-IS received the LSP with the greater sequencenumber and the same LSP ID from the neighbor.

Cause 2: The system ID of the local switch was the same as that of another switch, causing theLSPs to be frequently refreshed.



353

Procedure

Step 1 Run the display history-command command to check whether the reset isis all command isrun on the local switch to restart an IS-IS process.

l If the reset isis all command is run to restart an IS-IS process, go to Step 5.

l If the reset isis all command is not run to restart an IS-IS process, go to Step 2.

Step 2 Run the display isis lsdb command on the local switch to continuously check whether the LSPsequence number increases rapidly, that is, whether the actual LSP refreshing period is smallerthan that set using the timer lsp-refresh command.

l If the LSP sequence number increases rapidly, go to Step 3.

l If the LSP sequence number does not increase rapidly, go to Step 4.

Step 3 Run the display current-configuration command to check whether the system ID or virtualsystem ID of another switch is the same as that of the local switch.

l If the system ID or virtual system ID of another switch is the same as that of the localswitch, go to Step 4.

l If the system ID or virtual system ID of another switch is different from that of the localswitch, go to Step 5.

Step 4 Exercise caution when running the undo network-entity or undo virtual-system command.Run the undo network-entity or undo virtual-system command in the IS-IS view of the localswitch or other switchs that have the same system ID or virtual system ID with the localswitch to delete the system ID or virtual system ID. Run the network-entity or virtual-system command to configure a new system ID or virtual system ID for the switch. Checkwhether the trap is cleared.




Step 6 End.

----End

Related Information

None

29.35 ISIS-STD_1.3.6.1.2.1.138.0.9isisAuthenticationTypeFailure

Description

ISIS-STD/3/AUTHTYPE_FAIL:OID [oid] The authentication type of received PDU is differentfrom local configuration. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer],PduFrag=[opaque])



354

The authentication type contained in a received PDU was inconsistent with the locally configuredone.

Attribute


1.3.6.1.2.1.138.0.9 Minor other(1)

Parameters

Name Meaning






1. If Hello packets do not pass authentication, IS-IS neighbor relationships cannot be set upproperly.

2. If LSPs or SNP packets do not pass authentication, LSDB synchronization will fail but IS-ISneighbor relationships will be set up properly.

Possible Causes

Cause 1: Authentication was configured on an interface or process of the local end, but theauthentication type on the peer end was different from that on the local end.

Cause 2: Authentication was configured on an interface or process of the local end, but noauthentication was configured on the peer end.

Procedure

Step 1 Obtain the IS-IS process number based on the SysInstance field and IS-IS level (1 indicates aLevel-1 packet; 2 indicates a Level-2 packet; 3 indicates a P2P Hello packet) based on theSysLevel field. Based on the IS-IS packet format defined in ISO10589, check the IfName fieldin the trap to identify the interface that receives packets. Then, find the PduFrag field and obtainthe system ID of the source switch that sends the packets and packet type.

l If the packet type is Hello, go to Step 2.

l If the packet type is LSP or SNP, go to Step 4.



355









Step 2 Run the display isis peer command on the source switch to check the interface that sends packets.Enter the view of this interface, and run the display this command to check whether an interfaceauthentication mode is configured. If an interface authentication mode is configured, checkwhether it is the same as the interface authentication mode of the local switch.

l If the interface authentication modes are the same, go to Step 6.

l If the interface authentication modes are different, go to Step 3.

Step 3 Run the isis authentication-mode command in the interface view of the source switch toconfigure the authentication mode to be the same as that of the local switch, and ensure that theauthentication passwords on the two ends are the same. Then check whether the trap is cleared.



Step 4 Run the display current-configuration configuration isis command on the source switch tocheck whether an area authentication mode or a domain authentication mode is configured inthe IS-IS process. If an area authentication mode or a domain authentication mode is configured,check whether the area or domain authentication mode is same as that of the local switch, andensure that the authentication passwords configured on the two ends are the same.

l If the area or domain authentication modes are the same, go to Step 6.

l If the area or domain authentication modes are different, go to Step 5.

Step 5 Run the area-authentication-mode command (for Level-1 packets) or the domain-authentication-mode command (for Level-2 packets) in the IS-IS view of the source switch toconfigure the authentication mode to be the same as that of the local switch. Then check whetherthe trap is cleared.




Step 7 End.

----End



356


29.36 ISIS-STD_1.3.6.1.2.1.138.0.10isisAuthenticationFailure

DescriptionISIS-STD/3/AUTH_FAIL:OID [oid] The authentication password of received PDU is differentfrom local configuration. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer],PduFrag=[opaque])

The authentication password contained in a received PDU is inconsistent with the locallyconfigured one.

Attribute



Parameters

Name Meaning





Impact on the System1. If Hello packets do not pass authentication, IS-IS neighbor relationships cannot be set upproperly.

2. If LSPs or SNP packets do not pass authentication, LSDB synchronization will fail but IS-ISneighbor relationships will be set up properly.

Possible CausesAuthentication was configured on an interface or process of the local end, the authenticationtype configured on the peer end was the same as that configured on the local end, but theauthentication passwords configured on the two ends were different.



357

ProcedureStep 1 Obtain the IS-IS process number and IS-IS level (1 indicates a Level-1 packet; 2 indicates a

Level-2 packet; 3 indicates a P2P Hello packet) contained in the PDU based on the commandoutput. Based on the IS-IS packet format defined in ISO10589, search for the if-index field (indecimal) in the trap and convert the decimal value into a hexadecimal value. Run the displayrm interface command on the interface and search the command output for the informationabout the interface that receives the packet. The value of IfnetIndex in the interface informationis the same as the hexadecimal if-index. Then, find the pdu-fragment field in the trap and obtainthe system ID of the source switch that sends the packets and packet type.l If the packet type is Hello, go to Step 2.l If the packet type is LSP or SNP, go to Step 4.









Step 2 Run the display isis peer command on the source switch to view the interface that sends thepacket. Enter the view of this interface, and run the display this command to check theauthentication password is the same as that configured on the local switch.l If the authentication passwords are the same, go to Step 6.l If the authentication passwords are different, go to Step 3.

Step 3 Run the isis authentication-mode command in the interface view of the source switch toconfigure the authentication password to be the same as that of the local switch. Then checkwhether the trap is cleared.l If the trap is cleared, go to Step 7.l If the trap is not cleared, go to Step 6.

Step 4 Run the display current-configuration configuration isis command on the source switch tocheck whether the area or domain authentication password configured in the IS-IS process isthe same as that of the local switch.l If the area or domain authentication passwords are the same, go to Step 6.l If the area or domain authentication passwords are different, go to Step 5.

Step 5 Run the area-authentication-mode command (for Level-1 packets) or the domain-authentication-mode command (for Level-2 packets) in the IS-IS view of the source switch toconfigure the authentication password to be the same as that of the local switch. Then checkwhether the trap is cleared.



358

l If the trap is cleared, go to Step 7.l If the trap is not cleared, go to Step 6.


Step 7 End.

----End


29.37 ISIS-STD_1.3.6.1.2.1.138.0.11 isisVersionSkew

DescriptionISIS-STD/2/VERSION_SKEW:OID [oid] IS-IS received a PDU with incorrectProtocolVersion. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer],PduProtocolVersion=[integer], PduFragment=[opaque])

IS-IS received a PDU carrying an incorrect protocol version number.

Attribute



Parameters

Name Meaning




PduProtocolVersion Protocol version contained in a PDU

PduFragment 64-byte PDU header

Impact on the System1. If the board modifies the packet, route flapping may occur, and the CPU usage will increase.



359

2. If the trap was triggered by a device communication failure, neighbor relationships could notbe established, and routes could not be learned from each other.

Possible CausesCause 1: The IS-IS version numbers supported by the local switch and other switchs wereinconsistent.

Cause 2: The version number field was modified during packet transmission.

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, obtain the pdu-fragment field (inhexadecimal) in the trap and the system ID of the source switch. Check whether the version fieldvalue on the source switch is 1l If the version field value is 1, go to Step 2.l If the version field value is not 1, go to Step 4.




The six consecutive bytes beginning with the10th byte in the PduFragment fieldconstitute a System ID.





Step 2 Check the logs and ping packets to determine whether a hardware fault of the board causes thepackets to be changed.l If a hardware fault of the board causes the packets to be changed, go to Step 3.l If the packets are changed due to other reasons, go to Step 6.

Step 3 Replace the board. Then check whether the trap is cleared.l If the trap is cleared, go to Step 7.l If the trap is not cleared, go to Step 6.

Step 4 Check whether the IS-IS version number on the source switch can be changed.l If the IS-IS version number can be changed, go to Step 5.l If the IS-IS version number cannot be changed, go to Step 6.

Step 5 Change the IS-IS version number of the source switch (the IS-IS version number cannot bechanged on the Huawei switch). Then check whether the trap is cleared.l If the trap is cleared, go to Step 7.



360



Step 7 End.

----End


29.38 ISIS-STD_1.3.6.1.2.1.138.0.12 isisAreaMismatch

DescriptionISIS-STD/3/AREA_MISMATCH:OID [oid] IS-IS received a level-1 Hello PDU whose areaaddress is different from the local area address. (CircIfIndex=[integer], PduFragment=[opaque])

The area address contained in a received Level-1 Hello packet was different from the local one.

Attribute



Parameters

Name Meaning




Impact on the System1. If the trap is triggered by a hardware fault on a board, route flapping may occur, and the CPUusage will increase.

2. If the trap is triggered by incorrect configurations, IS-IS neighbor relationships cannot beestablished, and routes cannot be learned from each other.

Possible CausesCause 1: Configurations were incorrect.



361

Cause 2: The area address field was modified.

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, check the pdu-fragment field (inhexadecimal) and obtain the system ID of the source switch. Run the display this command inthe IS-IS view of the source switch to check whether the source switch is configured with anarea address the same as that of the local switch.l If the area addresses are the same, go to Step 3.l If the area addresses are different, go to Step 2.




The six consecutive bytes beginning with the10th byte in the PduFragment fieldconstitute a System ID.





Step 2 Run the network-entity command in the IS-IS view of the source switch to configure an IS-ISarea address the same as that of the local switch. Exercise caution when using the undo network-entity command. Then check whether the trap is cleared.l If the trap is cleared, go to Step 4.l If the trap is not cleared, go to Step 3.


Step 4 End.

----End


29.39 ISIS-STD_1.3.6.1.2.1.138.0.13 isisRejectedAdjacency

DescriptionISIS-STD/3/REJECT_ADJ:OID [oid] IS-IS failed to establish the adjacency with its peer.(NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduFragment=[opaque])



362

The local switch received Hello packets sent from the neighboring switch but failed to establishIS-IS neighbor relationships with it.

Attribute



Parameters

Name Meaning






The neighbor relationship cannot be established properly.

Possible Causes

Cause 1: The system ID or virtual system ID on the local switch was the same as that on theneighboring switch.

Cause 2: Hello packets failed authentication because the authentication mode or password onthe local interface was different from that on the neighboring interface.

Cause 3: IS-IS Level-1 area addresses were different on the two ends of the link.

Cause 4: The local interface received Hello packets with the level mismatched that on the localinterface.

Cause 5: On a broadcast network, the local interface received Hello packets from an interfacethat is not on the network segment where the local interface resides.

Cause 6: On a P2P network, when not configured with the isis peer-ip-ignore command, thelocal interface received Hello packets from an interface that is not on the network segment wherethe local interface resides.

Procedure

Step 1 Check the IfName field in the trap to identify the interface that receives packets.

l If the interface is a broadcast interface, go to Step 2.



363

l If the interface is a P2P interface, go to Step 7.

Step 2 Check the PduFragment field, and then identify the source switch based on its system ID (sixconsecutive bytes beginning with the 10th byte). Run the display this command in the views ofinterfaces on the two ends of the link and in the IS-IS process view to check whether the IS-ISlevels and interface levels on the two ends of the link are consistent.

l If the IS-IS levels and interface levels on the two ends of the link are not consistent, go toStep 3.

l If the IS-IS levels and interface levels on the two ends of the link are consistent, go to Step6.

Step 3 Run the isis circuit-level command in the interface view to change the IS-IS levels and interfacelevels on the two ends of the link to be the same. Then check whether the trap is cleared.



Step 4 Run the display ip interface command to check whether the IP addresses of the sourceswitch interface and the local interface are on the same network segment.

l If the IP addresses of the source switch interface and the local interface are on the samenetwork segment, go to Step 8.

l If the IP addresses of the source switch interface and the local interface are not on the samenetwork segment, go to Step 5.

Step 5 Run the ip address command in the interface views of the source and local switchs to configureIP addresses of the interfaces to be on the same network segment. Then check whether the trapis cleared.



Step 6 Run the display this command in the interface views of the source and local switchs to checkwhether the isis peer-ip-ignore command is run on the interfaces.

l If the isis peer-ip-ignore command is run on the interfaces, go to Step 10.

l If the isis peer-ip-ignore command is not run on the interfaces, go to Step 7.

Step 7 Run the isis peer-ip-ignore or ip address command in the interface views of the source andlocal switchs to configure the IP addresses of the two interfaces to be on the same networksegment. Then check whether the trap is cleared.



Step 8 Check whether the Level-1 area addresses on the two ends of the link are the same.

l If the Level-1 area addresses on the two ends of the link are the same, go to Step 10.

l If Level-1 area addresses on the two ends of the link are different, go to Step 9.

Step 9 Run the network-entity command in the IS-IS view to configure a new area address to ensurethat the Level-1 area addresses on the two ends are the same. Then check whether the trap iscleared.





364

Step 10 Run the display current-configuration command to check whether the system ID of the sourceswitch is the same as the system ID or virtual system ID on the local switch.



Step 11 Exercise caution when running the undo network-entity command. Change the system ID orvirtual system ID on one switch to ensure that the system IDs or virtual system IDs on the twoends are different. Then check whether the trap is cleared.



Step 12 Check whether IS-IS authentication modes and authentication passwords configured on twoends are the same.



Step 13 Run the isis authentication-mode command in the views of interfaces on the two ends to changethe authentication mode and authentication password to ensure that IS-IS authentication modesand authentication passwords of the interfaces are consistent. Alternatively, run the undo isisauthentication-mode command in the views of interfaces on the two ends to disable IS-ISauthentication (disabling IS-IS authentication degrades the system security). Then checkwhether the trap is cleared.




Step 15 End.

----End

Related Information

None

29.40 ISIS-STD_1.3.6.1.2.1.138.0.14isisLSPTooLargeToPropagate

Description

ISIS-STD/4/LARGE_LSP:OID [oid] The length of the PDU to be sent is greater than the MTU.(NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduLspSize=[integer],PduLspId=[opaque])

The length of a PDU to be sent is greater than the MTU.



365

Attribute



Parameters

Name Meaning




PduLspSize LSP length

PduLspId LSP ID


None

Possible Causes

The length of the forwarded LSP was greater than the interface MTU.

Procedure

Step 1 Run the display ip interface interface-type interface-number command to check the interfaceMTU, namely the The Maximum Transmit Unit field value.

Step 2 Run the display current-configuration configuration isis command to check the LSP lengthset in the IS-IS process. The lsp-length originate field value indicates that maximum LSP length.If the LSP length is not found in the command output, the default LSP length is used. By default,the maximum length of an LSP generated in an IS-IS process is 1497 bytes.

Step 3 Enter the IS-IS view, and run the lsp-length originate command to change the LSP length tobe smaller than the interface MTU.

Step 4 Then check whether the trap is cleared.






366

Step 6 End.

----End

Related Information

None

29.41 ISIS-STD_1.3.6.1.2.1.138.0.15isisOrigLSPBuffSizeMismatch

Description

ISIS-STD/3/LSPMTU_MISMATCH:OID [oid] The size of the local buffer for originating IS-IS LSPs is smaller than the size of the received LSP. (NotificationSysLevelIndex=[integer],CircIfIndex=[integer], PduLspId=[opaque], PduOriginatingBufferSize=[integer],PduBufferSize=[integer])

The size of a received LSP was greater than that of the local buffer where LSPs were generated.

Attribute



Parameters

Name Meaning




PduLspId LSP ID

PduOriginatingBufferSize Length of a locally generated PDU

PduBufferSize Length of a received PDU


Routes cannot be learned, and traffic forwarding is affected.



367

Possible CausesThe size of LSPs generated on the source switch was greater than that of LSPs generated on thelocal switch.

Procedure

Step 1 Identify the source switch that generates the LSP based on the lsp-id field value in the trap.Check whether the size of the LSP generated by the source switch is greater than the size of theLSP generated by the local switch.l If the size of the LSP generated by the source switch is greater than the size of the LSP

generated by the local switch, go to Step 2.l If the size of the LSP generated by the source switch is not greater than the size of the LSP

generated by the local switch, go to Step 3.

Step 2 Run the lsp-length originate command in the IS-IS process on the source switch to change thesize of generated LSPs to be equal to or smaller than the size of the buffer where LSPs aregenerated on the local switch. Then check whether the trap is cleared.l If the trap is cleared, go to Step 4.l If the trap is not cleared, go to Step 3.


Step 4 End.

----End


29.42 ISIS-STD_1.3.6.1.2.1.138.0.16isisProtocolsSupportedMismatch

DescriptionISIS-STD/2/PROTO_MISMATCH:OID [oid] The protocol of received Protocol TLV ismismatched with local configuration. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduProtocolsSupported=[opaque], PduLspId=[opaque], PduFragment=[opaque])

The type of the protocol supported TLV carried in a received PDU was inconsistent with thelocally configured one.



368

Attribute



Parameters

Name Meaning




PduProtocolsSupported Protocol supported TLV contained in a received PDU

PduLspId LSP ID


Impact on the SystemLSPs cannot be learned and routes cannot be generated.

Possible CausesThe protocol type supported by the source switch that generated the LSP was different from thatsupported by the local switch.

Procedure

Step 1 The type of the protocol supported TLV carried in the received LSP mismatched with the typeof the protocol supported by the local device. Check whether the trap is cleared in 10 minutes.l If the trap is cleared, go to Step 3.l If the trap is not cleared, go to Step 2.


Step 3 End.

----End




369

29.43 ISIS-STD_1.3.6.1.2.1.138.0.17 isisAdjacencyChange

Description

ISIS-STD/2/ADJ_CHANGE:OID [oid] The state of IS-IS adjacency changed.(NotificationSysLevelIndex=[integer], CircuitIfIndex=[integer], LspID=[opaque], AdjState=[integer])

The status of the IS-IS neighbor relationship changed.

Attribute



Parameters

Name Meaning




LspID LSP ID

AdjState Neighbor relationship status


IS-IS may recalculate routes, which causes route flapping and interrupts IS-IS services.

Possible Causes

Cause 1: The IS-IS neighbor relationship went Up or Down.

Cause 2: IS-IS configurations were incorrect.

Cause 3: The system was busy.

Cause 4: A link fault occurred.



370

Procedure

Step 1 Based on the IS-IS packet format defined in ISO10589, check the LspID field value (inhexadecimal) and obtain the system ID of the source switch. Then check whether the neighborrelationship states on the two ends are the same.l If the neighbor relationship states on the two ends are the same, go to Step 12.l If the neighbor relationship states on the two ends are different, go to Step 2.

Step 2 Download user logs from the source switch, and check whether the neighbor relationship statuschanges because the interface status becomes Down.l If the neighbor relationship status changes because the interface status becomes Down, go

to Step 3.l If the neighbor relationship status changes due to other reasons, go to Step 10.

Step 3 Search the logs for information about the local interface and check the interface status and MTUstatus on the interface. Ensure that both the interface status and MTU status on two ends are Up.Then check whether the neighbor relationship states on the two ends are the same.l If the neighbor relationship states on the two ends are the same, go to Step 13.l If the neighbor relationship states on the two ends are different, go to Step 4.

Step 4 Check the system IDs and ensure that the system IDs on the two ends are correct. Then checkwhether the neighbor relationship states on the two ends are the same.l If the neighbor relationship states on the two ends are the same, go to Step 13.l If the neighbor relationship states on the two ends are different, go to Step 5.

Step 5 Check the levels of IS-IS processes and ensure that levels on the two ends match. Then checkwhether the neighbor relationship states on the two ends are the same.l If the neighbor relationship states on the two ends are the same, go to Step 13.l If the neighbor relationship states on the two ends are different, go to Step 6.

Step 6 Check the area ID of the switch and ensure that area IDs on the two ends are the same. Thencheck whether the neighbor relationship states on the two ends are the same.l If the neighbor relationship states on the two ends are the same, go to Step 13.l If the neighbor relationship states on the two ends are different, go to Step 7.

Step 7 Check that IP addresses of interfaces on the two ends belong to the same network segment. Thencheck whether the neighbor relationship states on the two ends are the same.l If the neighbor relationship states on the two ends are the same, go to Step 13.l If the neighbor relationship states on the two ends are different, go to Step 8.

Step 8 Check whether the authentication mode is configured on the two ends and ensure that theencryption authentication modes on the two ends are the same. If authentication is required,ensure that the authentication modes and passwords on the two ends are the same. Otherwise,authentication is disabled on the two ends (disabling authentication degrades the systemsecurity). Then check whether the neighbor relationship states on the two ends are the same.l If the neighbor relationship states on the two ends are the same, go to Step 13.l If the neighbor relationship states on the two ends are different, go to Step 9.

Step 9 Check that interfaces on the two ends can transmit Hello packets properly, and then checkwhether the neighbor relationship states on the two ends are the same.



371

l If the neighbor relationship states on the two ends are the same, go to Step 13.

l If the neighbor relationship states on the two ends are different, go to Step 10.

Step 10 Run the display cpu-usage command to check whether the CPU usage remains 100% for aperiod of time.

l If the CPU usage remains 100% for a period of time, go to Step 11.

l If the CPU usage does not remain 100% for a period of time, go to Step 12.

Step 11 Run the isis timer hello command in the interface view to set a longer interval at which Hellopackets are sent. The interval can be prolonged by 10s each time. Prolonging the interval atwhich Hello packets are sent slows down network fault detection and therefore slows down routeconvergence. Then check whether the neighbor relationship states on the two ends are the same.

l If the neighbor relationship states on the two ends are the same, go to Step 13.

l If the neighbor relationship states on the two ends are different, go to Step 12.


Step 13 End.

----End

Related Information

None

29.44 ISIS-STD_1.3.6.1.2.1.138.0.18 isisLSPErrorDetected

Description

ISIS-STD/2/LSP_ERROR:OID [oid] IS-IS received an LSP with a parse error.(NotificationSysLevelIndex=[integer], LspID=[opaque], CircuitIfIndex=[integer],PduFragment=[opaque], ErrorOffset=[integer], ErrorTLVType=[integer])

An LSP with a parse error was received.

Attribute



Parameters

Name Meaning




372

Name Meaning


LspID LSP ID



ErrorOffset Offset of an error TLV

ErrorTLVType Error TLV type

Impact on the SystemThe TLV cannot be parsed, and therefore information may be lost.

Possible CausesAn error occurred when a received LSP was parsed.

Procedure

Step 1 Search the trap information for the error TLV and the offset of the error TLV for fault location.

Step 2 Use a packet obtain tool to obtain packet headers sent by the remote device, check whether thefault occurs, and determine whether the local device incorrectly parses the packet or the remotedevice sends an incorrect packet.l If the remote device sends an incorrect packet, go to Step 4.l The local device incorrect parses the packet, go to Step 3.


Step 4 End.

----End




373

30 LACP

About This Chapter

30.1 LACP_1.3.6.1.4.1.2011.5.25.41.3.2 hwLacpNegotiateFailed

30.2 LACP_1.3.6.1.4.1.2011.5.25.41.3.3 hwLacpTotalLinkLoss

30.3 LACP_1.3.6.1.4.1.2011.5.25.41.3.4 hwLacpPartialLinkLoss

30.4 LACP_1.3.6.1.4.1.2011.5.25.41.3.13 hwLacpNegotiateResume

30.5 LACP_1.3.6.1.4.1.2011.5.25.41.3.14 hwLacpTotalLinkLossResume

30.6 LACP_1.3.6.1.4.1.2011.5.25.41.3.15 hwLacpPartialLinkLossResume

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 30 LACP


374

30.1 LACP_1.3.6.1.4.1.2011.5.25.41.3.2hwLacpNegotiateFailed

DescriptionLACP/2/MNCD:OID [oid] The member of LAG neither can take over PDU nor transmit PDUs.(TrunkIndex=[INTEGER], PortIfIndex=[INTEGER], TrunkId=[INTEGER], TrunkName=[OCTET], PortName=[OCTET])

Negotiations over member links failed.

Attribute


1.3.6.1.4.1.2011.5.25.41.3.2 Major operationalViolation(8)

Parameters

Name Meaning


TrunkIndex Indicates the index of a Trunk.

PortIfIndex Indicates the index of a member interface.

TrunkId Indicates the ID of a Trunk interface.

TrunkName Indicates the name of a Trunk interface.

PortName Indicates the name of a member interface.

Impact on the SystemThe link cannot transmit services.

Possible Causes1.

An MNCD trap was generated when the link became Down.

2.

No LACP packet was received from the remote end when the timer expired.

3.

A member interface left the LAG.

4.



375

The interface received the LACP packet sent from the interfaces on the same device.

Procedure

Step 1 Check whether the interface is Down.



Step 2 Run the undo shutdown command to check whether the alarm is cleared.






Step 4 Check whether there is an interface on the local or remote end of the link leaving the LAG.



Step 5 Check whether the interface leaves the LAG normally.



Step 6 Repair the physical link and then check whether the alarm is cleared.



Step 7 Collect information about configurations, trap messages, and log messages, and then contactHuawei technical support personnel.

Step 8 End.

----End

Related Information

None.

30.2 LACP_1.3.6.1.4.1.2011.5.25.41.3.3 hwLacpTotalLinkLoss

Description

LACP/2/TLL:OID [oid] Link bandwidth lost totally.(TrunkIndex=[INTEGER], TrunkIfIndex=[INTEGER], TrunkId=[INTEGER], TrunkName=[OCTET])

All the link bandwidths were lost.



376

Attribute



Parameters

Name Meaning



TrunkIfIndex The value of this object identifies the index of a Trunk interface.




Services are interrupted.

Possible Causes

A TLL trap was generated when all links between two devices were disconnected and packetsfailed to be forwarded.

Procedure

Step 1 Run the display interface brief command to check whether the interface is Down.

l If the alarm is cleared, go to Step 2

l If the alarm is not cleared, go to Step 4







Step 4 Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ]command to check whether there are member interfaces in the LAG.



Step 5 Run the display trunkmembership eth-trunk trunk-id command to check whether the lowerthreshold of Eth-Trunk member links that can be Up in the LAG is correctly set. (An incorrectlower threshold causes the negotiation failure between the Eth-Trunk member interfaces.)



377



Step 6 In the Eth-Trunk interface view, run the least active-linknumber link-number command tocorrectly set the lower threshold of Trunk member links that can be Up. Then, check whetherthe fault is rectified.






Step 8 Run the eth-trunk trunk-id command in the interface view and add the current Ethernet interfaceto the Eth-Trunk interface as required. Then, check whether the alarm is cleared.




Step 10 End.

----End

Related Information

None.

30.3 LACP_1.3.6.1.4.1.2011.5.25.41.3.4hwLacpPartialLinkLoss

Description

LACP/2/PLL:OID [OID] Link bandwidth lost partly. (TrunkIndex=[INTEGER],TrunkIfIndex=[INTEGER], TrunkId=[INTEGER], TrunkName=[OCTET])

The bandwidths of a link were partially lost.

Attribute





378

Parameters

Name Meaning



TrunkIfIndex Indicates the index of a Trunk interface.




Part of services were interrupted.

Possible Causes

The number of the Eth-Trunk member links that were Up was smaller than the lower thresholdvalue that was set, which caused the LAG to become Down. As a result, a PLL trap wasgenerated.

Procedure

Step 1 Run the display interface brief command to check whether the interface is Down.









Step 4 Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ]command to check whether there are member interfaces in the LAG.



Step 5 Run the display trunkmembership eth-trunk trunk-id command to check whether the lowerthreshold for Eth-Trunk member links is set in the LAG; whether the number of Eth-Trunkmember links that are successfully negotiated is smaller than the lower threshold for the Eth-Trunk member links that can be Up.





379

Step 6 In the Eth-Trunk interface view, run the least active-linknumber link-number command tocorrectly set the lower threshold of Trunk member links that can be Up. Then, check whetherthe alarm is cleared.l If the alarm is cleared, go to Step 10.l If the alarm is not cleared, go to Step 9.

Step 7 Repair the physical link and then check whether the alarm is cleared.l If the alarm is cleared, go to Step 10.l If the alarm is not cleared, go to Step 4.

Step 8 Run the eth-trunk trunk-id command in the interface view and add the current Ethernet interfaceto the Eth-Trunk interface as required. Then, check whether the alarm is cleared.l If the alarm is cleared, go to Step 10.l If the alarm is not cleared, go to Step 5.


Step 10 End.

----End


30.4 LACP_1.3.6.1.4.1.2011.5.25.41.3.13hwLacpNegotiateResume

DescriptionLACP/2/MNCR:OID [oid] Link negotiation failure is resumed. (TrunkIndex=[INTEGER],PortIfIndex=[INTEGER], TrunkId=[INTEGER], TrunkName=[OCTET], PortName=[OCTET])

It is the trap indicating the successful member link negotiation and is a matching trap ofhwLacpNegotiateFailed.

Attribute





380

Parameters

Name Meaning


TrunkIndex Indicates the index of a trunk.

PortIfIndex Indicates the index of a member interface.

TrunkId Indicates the ID of a trunk interface.

TrunkName Indicates the name of a trunk interface.

PortName Indicates the name of a member interface.


The link can transmit services.

Possible Causes

1.

Member links negotiation succeeded for the first time.

2.

When the member link negotiation failed, the trap hwLacpNegotiateFailed was generated. Afterthe fault was rectified, the trap hwLacpNegotiateResume was generated.

Procedure


----End

Related Information

LACP_1.3.6.1.4.1.2011.5.25.41.3.2 hwLacpNegotiateFailed

30.5 LACP_1.3.6.1.4.1.2011.5.25.41.3.14hwLacpTotalLinkLossResume

Description

LACP/2/TLR:OID [oid] Link bandwidth lost totally is resumed. (TrunkIndex=[INTEGER],TrunkIfIndex=[INTEGER], TrunkId=[INTEGER], TrunkName=[OCTET])

It is a trap indicating the restoration of the total link bandwidth and is a matching trap ofhwLacpTotalLinkLoss.



381

Attribute



Parameters

Name Meaning



TrunkIfIndex Indicates the index of a trunk interface.



Impact on the SystemServices are resumed.

Possible Causes1.

The trap hwLacpTotalLinkLoss was generated when no interface was selected. When the faultwas rectified, the trap hwLacpTotalLinkLossResume was generated.


----End

Related InformationLACP_1.3.6.1.4.1.2011.5.25.41.3.3 hwLacpTotalLinkLoss

30.6 LACP_1.3.6.1.4.1.2011.5.25.41.3.15hwLacpPartialLinkLossResume

DescriptionLACP/2/PLR:OID [oid] Link bandwidth lost partly is resumed. (TrunkIndex=[INTEGER],TrunkIfIndex=[INTEGER], TrunkId=[INTEGER], TrunkName=[OCTET])

It is a trap indicating the restoration of the partial link bandwidth and is a matching trap ofhwLacpPartialLinkLoss.



382

Attribute



Parameters

Name Meaning



TrunkIfIndex Indicates the index of a trunk interface.



Impact on the SystemPart of services were resumed.

Possible Causes1.

Because the number of trunk member links that could go Up through negotiation was below theminimum number of Up member links, the link aggregation group went Down, and thus the traphwLacpPartialLinkLoss was generated. When the fault was rectified, the traphwLacpPartialLinkLossResume was generated.


----End

Related InformationLACP_1.3.6.1.4.1.2011.5.25.41.3.4 hwLacpPartialLinkLoss



383

31 LINE

About This Chapter

31.1 LINE_1.3.6.1.4.1.2011.5.25.207.2.1 hwVtyNumExceed

31.2 LINE_1.3.6.1.4.1.2011.5.25.207.2.2 hwUserLogin

31.3 LINE_1.3.6.1.4.1.2011.5.25.207.2.3 hwUserLoginFail

31.4 LINE_1.3.6.1.4.1.2011.5.25.207.2.4 hwUserLogout

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 31 LINE


384

31.1 LINE_1.3.6.1.4.1.2011.5.25.207.2.1 hwVtyNumExceed

DescriptionLINE/4/VTYUSERREACHMAX:OID [oid] The number of login users reaches the maximumlimit. (MaxUserNum=[INTEGER])

The number of login users through Telnet reaches the maximum limit.

Attribute



Parameters

Name Meaning

OID Indicates the ID of a MIB object.

MaxUserNum Indicates the maximum number of users who can log in.

Impact on the SystemMore users cannot log in to the device through Telnet.

Possible CausesThe number of Telnet connections reaches the maximum limit set by the user.

Procedure

Step 1 Reduce the number of login users through Telnet.

----End


31.2 LINE_1.3.6.1.4.1.2011.5.25.207.2.2 hwUserLogin

DescriptionLINE/5/VTYUSERLOGIN:OID [oid] A user login. (UserIndex=[INTEGER], UserName=[STRING], UserIP=[STRING], UserChannel=[STRING])



385

This object indicates notification information about user login.

Attribute


1.3.6.1.4.1.2011.5.25.207.2.2 Indeterminate equipmentAlarm(5)

Parameters

Name Meaning


UserIndex Indicates the user index.

UserName Indicates the user name.

When the device fails to obtain the user name, for example, in a password-baseduser authentication scenario, asterisks (**) are used to indicate the user name.

UserIP Indicates the IP address of a user.

When the device fails to obtain the user IP address, for example, in a scenariowhere the user logs in using a Console interface or AUX interface, asterisks(**) are used to indicate the IP address.

UserChannel Indicates the channel used by the user.


This alarm message is informational only, and no action is required.

Possible Causes

When a user logs in to the device through Telnet, a notification is reported.

Procedure


----End

Related Information

None

31.3 LINE_1.3.6.1.4.1.2011.5.25.207.2.3 hwUserLoginFail



386

Description

LINE/5/VTYUSERLOGINFAIL:OID [oid] A user login fail. (UserIndex=[INTEGER],UserName=[STRING], UserIP=[STRING], UserChannel=[STRING])

A user failed to log in to the server.

Attribute



Parameters

Name Meaning

oid OID of an alarm

UserIndex Index of a user

UserName Name of a user


UserIP IP address of a user


UserChannel Channel for login


The system will not be affected.

Possible Causes

A user failed to log in to the server using Telnet.

Procedure


----End

Related Information

None.



387

31.4 LINE_1.3.6.1.4.1.2011.5.25.207.2.4 hwUserLogout

Description

LINE/5/VTYUSERLOGOUT:OID [oid] A user logout. (UserIndex=[INTEGER], UserName=[STRING], UserIP=[STRING], UserChannel=[STRING])

The user logged out of the device.

Attribute



Parameters

Name Meaning


UserIndex Indicates the user index.

UserName Indicates the user name.


UserIP Indicates the IP address of a user.


UserChannel Indicates the channel used by the user.


This log message indicates a normal situation, and no action is required.

Possible Causes

When a user logs out of the device, a notification is reported.

Procedure


----End



388

Related Information31.2 LINE_1.3.6.1.4.1.2011.5.25.207.2.2 hwUserLogin



389

32 LSPV

About This Chapter

32.1 LSPV_1.3.6.1.4.1.2011.5.25.302.3.1 hwLspPingProbe

32.2 LSPV_1.3.6.1.4.1.2011.5.25.302.3.2 hwLspTraceProbe

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 32 LSPV


390

32.1 LSPV_1.3.6.1.4.1.2011.5.25.302.3.1 hwLspPingProbe

Description

LSPV/4/LSPPINGPROBE:OID [oid] The trap of LSP ping test.(hwLspTunnelID=[INTEGER],hwLspSenderAddress=[INTEGER], hwLspEndPointAddress=[INTEGER], hwLspTTL=[INTEGER], hwLspHandle=[INTEGER])

An LSP ping test trap was sent to the NMS.

Attribute



Parameters

Name Meaning


hwLspTunnelID ID of the LSP tunnel

hwLspSenderAddress Source address of the LSP ping packet

hwLspEndPointAddress Destination address of the LSP ping packet

hwLspTTL TTL value of the LSP ping-packet

hwLspHandle Handle value of the LSP ping-packet



Possible Causes

An LSP ping packet was sent to check the link connectivity.

Procedure


----End

Related Information

None.



391

32.2 LSPV_1.3.6.1.4.1.2011.5.25.302.3.2 hwLspTraceProbe

Description

LSPV/4/LSPTRACEPROBE:OID [oid] The trap of LSP trace test.(hwLspTunnelID=[INTEGER], hwLspSenderAddress=[INTEGER], hwLspEndPointAddress=[INTEGER],hwLspTTL=[INTEGER], hwLspHandle=[INTEGER])

An LSP trace test trap was sent to the NMS.

Attribute



Parameters

Name Meaning


hwLspTunnelID ID of the LSP tunnel

hwLspSenderAddress Source address of the LSP trace packet

hwLspEndPointAddress Destination address of the LSP trace packet

hwLspTTL TTL value of the LSP trace packet

hwLspHandle Handle value of the LSP trace packet



Possible Causes

An LSP trace packet was sent to check the link connectivity.

Procedure


----End

Related Information

None.



392

33 L2BPTNL

About This Chapter

33.1 L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.15hwL2ProtocolTunnelDropThresholdRaising

33.2 L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.16 hwL2ProtocolTunnelDropThresholdFalling

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 33 L2BPTNL


393

33.1 L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.15hwL2ProtocolTunnelDropThresholdRaising

Description

L2BPTNL/1/L2BPTNL_DROP_THRESHOLD_ALARM:OID [oid] The number of theprotocol transmit on the port reach the drop threshold. (PortName=[OCTET] , ProtocolName=[OCTET], Dropthreshold=[INTEGER])

The number of Layer 2 protocol packets transmitted on the interface enabled with Layer 2protocol transparent transmission reached the threshold.

Attribute


1.3.6.1.4.1.2011.5.25.42.2.1.7.15 Critical communicationsAlarm (2)

Parameters

Name Meaning


PortName Name of the interface that is enabled with Layer 2 protocol transparenttransmission

ProtocolName Name of the protocol whose packets are transparently transmitted

Dropthreshold Threshold for discarding Layer 2 protocol packets



Possible Causes

The interface enabled with Layer 2 protocol transparent transmission was configured with thethreshold for discarding Layer 2 protocol packets, and the number of Layer 2 protocol packetsthat were transparently transmitted on the interface reached the threshold.

Procedure


----End



394

33.2 L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.16hwL2ProtocolTunnelDropThresholdFalling

Description

L2BPTNL/1/L2BPTNL_DROP_THRESHOLD_RESUME:OID [oid] The number of theprotocol transmit on the port below the drop threshold. (PortName=[OCTET], ProtocolName=[OCTET], Dropthreshold=[INTEGER])

The trap was generated when the number of Layer 2 protocol packets passing the interfaceenabled with Layer 2 protocol transparent transmission fell below the threshold. This is amatching trap of hwL2ProtocolTunnelDropThresholdRaising.

Attribute



Parameters

Name Meaning







Possible Causes

The interface enabled with Layer 2 protocol transparent transmission was configured with thethreshold for discarding Layer 2 protocol packets, and the number of Layer 2 protocol packetsthat were transparently transmitted on the interface fell below the threshold.

Procedure


----End



395

Related InformationL2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.15 hwL2ProtocolTunnelDropThresholdRaising



396

34 L2IFPPI

About This Chapter

34.1 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.6 hwPortSecRcvInsecurePktAlarm

34.2 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.9 hwPortStickyReachMaxAlarm

34.3 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.10 hwRecIllegalMacPktAlarm

34.4 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.11 hwMacLimitOverThresholdAlarm

34.5 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.1 hwMflpIfBlock

34.6 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.2 hwMflpIfResume

34.7 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.7 hwMflpVlanAlarm

34.8 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.9 hwMflpMacAddrAlarm

34.9 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.10 hwMflpMacAddrResume

34.10 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.11 hwMflpQuitVlanAlarm

34.11 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.12 hwMflpQuitVlanResume

34.12 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.1 hwMacTrapAlarm

34.13 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.2 hwPortVlanSecureMacAlarm

34.14 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.3 hwSlotMacUsageRaisingThreshold

34.15 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.4 hwSlotMacUsageFallingThreshold

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 34 L2IFPPI


397

34.1 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.6hwPortSecRcvInsecurePktAlarm

Description

L2IFPPI/4/PORTSEC_ACTION_ALARM:OID [oid] Interface ([INTEGER]/[INTEGER])[OCTET] receive insecure mac-address, and the port status is : [INTEGER]. (1:restrict;2:protect;3:error-down)

The number of MAC addresses on an interface reaches the threshold.

Attribute


1.3.6.1.4.1.2011.5.25.42.2.1.7.6 Warning qualityOfServiceAlarm(3)

Parameters

Name Meaning


[INTEGER1]/[INTEGER2] Indicates the interface index.

OCTET Indicates the interface name.

INTEGER3 Indicates the interface status.


Traffic transmission on an interface is affected.

Possible Causes

The number of secure MAC addresses or sticky MAC addresses reaches the upper limit.

Procedure

Step 1 View the interface status in the alarm information.

l If the interface status is Restrict (packets are discarded because the rate limit is exceeded),go to 2.

l If the interface status is Errordown, go to 3.

Step 2 Run the port-security max-mac-num max-number command to increase the maximum numberof MAC address learning. Check whether the alarm is cleared.

l If the alarm is cleared, go to 5.



398

l If the alarm is not cleared, go to 4.

Step 3 Perform error-down auto-recovery cause port-security interval interval-value on theinterface, and then check whether the alarm is cleared.

l If the alarm is cleared, go to 5.

l If the alarm is not cleared, go to 4.


Step 5 End.

----End

Related Information

None

34.2 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.9hwPortStickyReachMaxAlarm

Description

L2IFPPI/4/PORTSEC_STICKYMAC_ALARM:OID [OID] the number of [OCTET] reachesthe max.

The number of learned sticky MAC addresses or secure MAC addresses reached the threshold.

Attribute



Parameters

Name Meaning

[OID] Indicates the OID of the alarm.

[OCTET] Indicates the MAC address type: sticky MAC address or secure MAC address.


No more sticky MAC address entries or secure MAC address entries can be generated.

Possible Causes

The number of learned sticky MAC addresses or secure MAC addresses reached 1024.



399

Procedure


----End

Related Information

None

34.3 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.10hwRecIllegalMacPktAlarm

Description

L2IFPPI/4/MAC_ILLEGAL_MAC_ALARM:OID [OID] Receive packets with an all-0 MACaddress

The interface receives a packet with an all-0 destination or source MAC address.

Attribute



Parameters

Name Meaning


OCTET Indicates the alarm cause.


The device receives an invalid packet.

Possible Causes

Cause 1: The interface receives an all-0 source MAC address.

Cause 2: The interface receives an all-0 destination MAC address.

Procedure


----End



400

Related Information

None

34.4 L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.11hwMacLimitOverThresholdAlarm

Description

L2IFPPI/4/MAC_LIMIT_ALARM:OID [oid] MAC address learning reached the limit.(L2IfPort=[INTEGER],MacLimitVlanId=[INTEGER], MacLimitVsiName=[OCTET],L2IfPort=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER],MacDynAddressLearnNum=[INTEGER],MacLimitMaxMac=[INTEGER],L2IfPortName=[OCTET])

The number of MAC addresses learned by the interface, VLAN, or VSI reached the upper limit.

Attribute



Parameters

Name Meaning


L2IfPort Indicates the interface index.

MacLimitVlanId Indicates the VLAN ID.

MacLimitVsiName Indicates the VSI name.

L2IfPort Indicates the port index.

BaseTrapSeverity Indicates the alarm severity.

BaseTrapProbableCause Indicates the alarm cause.

BaseTrapEventType Indicates the alarm type.

MacDynAddressLearnNum Indicates the number of learned MAC addresses.

MacLimitMaxMac Indicates the maximum number of MAC addresses to be learned.

L2IfPortName Indicates the interface name.


No more MAC addresses can be learned.



401

Possible Causes

The number of MAC addresses learned by the interface, VLAN, or VSI reached the upper limit.

Procedure

Step 1 Check whether the alarm is generated on an interface, in a VLAN, or in a VSI.

Perform one of the following operations according to networking requirements and go to step2:

l Increase the upper limit on the number of MAC addresses to be learned.

l Delete unnecessary MAC addresses.

l Ignore the alarm.

Step 2 End.

----End

Related Information

None

34.5 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.1 hwMflpIfBlock

Description

L2IFPPI/4/MFLPIFBLOCK:OID [oid] Loop exists in vlan [INTEGER], Interface [OCTET1]blocked, block-time is [GAUGE] for [OCTET2], Mac Address is [OCTET3].

MAC address flapping occurs and the interface is blocked.

Attribute



Parameters

Name Meaning


INTEGER Indicates the VLAN ID.

OCTET1 Indicates the blocked interface name.

GAUGE Indicates the time when the interface is blocked.

OCTET3 Indicates the flapped MAC address.



402

Name Meaning

OCTET2 Indicates the cause why the interface is blocked.


Traffic cannot be received normally.

Possible Causes

Cause 1:

The interfaces where loops occur are added to the same VLAN.

Cause 2:

Cables are connected incorrectly.

Cause 3:

STP is enabled to remove loops on the network.

Procedure

Step 1 Check that cables are connected correctly. Then check whether the alarm is still reported.



Step 2 Check whether the two interfaces that learn the same MAC address can be added to differentVLANs according to the networking.



Step 3 Modify the configuration and add the two interfaces that learn the same MAC address to differentVLANs. Then check whether the alarm is still reported.



Step 4 Check whether the ring network meets requirements.



Step 5 Do as follows to remove loops:

(1) Run the display loop-detect eth-loop [ vlan vlan-id ] command to view the blocked interface.

(2) Run the display mac-address vlan vlan-id command to search an interface that learns theMAC address.

(3) Shut down one interface according to the networking.

(4) Run the reset loop-detect eth-loop vlan vlan-id { all | interface interface-type interface-number | mac-address mac-address } command to delete the blocked interface.



403

Step 6 Check whether the alarm recovery message is received.



Step 7 Enable STP. Then check whether the alarm is still reported.




Step 9 End.

----End

Related Information



Description

L2IFPPI/4/MFLPIFRESUME:OID [oid] Loop does not exist in vlan [INTEGER], Interface[OCTET1] resumed, block-time is [GAUGE] for [OCTET2].

The blocked interface where MAC address flapping occurs is recovered.

Attribute



Parameters

Name Meaning



OCTET1 Indicates the blocked interface name.

OCTET2 Indicates the interface recovery cause.


None



404

Possible CausesThe blocked interface is recovered.

Procedure


----End

Related Information34.5 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.1 hwMflpIfBlock

34.7 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.7hwMflpVlanAlarm

DescriptionL2IFPPI/4/MFLPVLANALARM:OID [OID] MAC move detected, VlanId = [INTEGER],[OCTET].

MAC address flapping has occurred.

Attribute



Parameters

Name Meaning


VlanId Indicates the VLAN ID.

OCTET Indicates the flapping MAC address and interfaces between which the MAC addressflaps.

Impact on the SystemTraffic cannot be received normally.

Possible Causes1:




405

2:


3:


Procedure

Step 1 Check that cables are connected correctly. Then check whether the alarm is still reported.



Step 2 Check whether the two interfaces that learn the same MAC address can be added to differentVLANs according to the networking.










Step 6 End.

----End

Related Information

None

34.8 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.9hwMflpMacAddrAlarm

Description

L2IFPPI/4/MFLPMACBLOCK:OID [oid] Loop exist in vlan [INTEGER], Mac Address[OCTET1] blocked, block-time is [GAUGE], the former Interface [OCTET2], the latter Interface[OCTET3], for [OCTET4].

MAC address flapping occurs and the MAC address is blocked.



406

Attribute



Parameters

Name Meaning


VLAN Indicates the VLAN ID.

OCTET1 Indicates the blocked MAC address.

OCTET2 Indicates the interface where the MAC address is learned before MAC addressflapping occurs.

OCTET3 Indicates the interface where the MAC address is learned after MAC addressflapping occurs.

OCTET4 Indicates the blocking cause.

Impact on the SystemTraffic cannot be received normally.



Cause 2:


Cause 3:


Procedure

Step 1 Check that cables are connected correctly. Then check whether the alarm is still reported.l If yes, go to step 2.l If not, go to step 9.

Step 2 Check whether the two interfaces that learn the same MAC address can be added to differentVLANs according to the networking.l If yes, go to step 3.l If not, go to step 4.




407



Step 4 Check whether the ring network meets requirements.



Step 5 Do as follows to remove loops:

(1) Check information about the two interfaces that learn the same MAC address in the alarm.

(2) Shut down one interface according to the networking.

(3) Run the reset loop-detect eth-loop vlan vlan-id { all | interface interface-type interface-number | mac-address mac-address } command to delete the blocked MAC address.

Step 6 Check whether the alarm recovery message is received.




l Y=>8.



Step 9 End.

----End

Related Information

34.9 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.10 hwMflpMacAddrResume

34.9 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.10hwMflpMacAddrResume

Description

L2IFPPI/4/MFLPMACRESUME:OID [OID] Loop does not exist in vlan [INTEGER], MacAddress [OCTET1] resumed, block-time is [GAUGE], the former Interface [OCTET2], the latterInterface [OCTET3], for [OCTET4].

The flapped MAC address is unblocked.

Attribute





408

Parameters

Name Meaning


VLAN Indicates the VLAN ID.

OCTET1 Indicates the blocked MAC address.

OCTET2 Indicates the interface name before MAC address flapping occurs.

OCTET3 Indicates the interface name after MAC address flapping occurs.

OCTET4 Indicates the blocking cause.



The blocked MAC address is recovered.

Procedurel This alarm is informational and no action is required.

----End

Related Information34.8 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.9 hwMflpMacAddrAlarm

34.10 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.11hwMflpQuitVlanAlarm

DescriptionL2IFPPI/4/MFLPQUITVLANALARM:OID [OID] (vlan=[INTEGER]) Interface [OCTET1]leaved from vlan [OCTET2],because mac move detected.

MAC address flapping occurs on an interface, and the interface is removed from the VLANwhere MAC address flapping occurs.



409

Attribute



Parameters

Name Meaning

oid Indicates ID of a MIB object.


OCTET1 Indicates the interface name.

OCTET2 Indicates the VLAN from which the interface is removed.

Impact on the SystemTraffic of the VLAN cannot be forwarded through the interface.

Possible Causes1:

The interfaces that form a loop belong to the same VLAN.

2:


3:

No loop prevention protocol such as STP is enabled.

Procedure

Step 1 Check that cables are connected correctly. Check whether the alarm persists.l If so, go to 2.l If not, go to 6.

Step 2 Check whether the two interfaces that learn the same MAC address can be added to differentVLANs according to the networking.l If so, go to 3.l If not, go to 4.

Step 3 Add the two interfaces to different VLANs. Check whether the alarm persists.l f so, go to 4.l If not, go to 6.

Step 4 Enable a loop prevention protocol such as STP. Check whether the alarm persists.l If so, go to 5.



410

l If not, go to 6.


Step 6 End.

----End

Related Information34.11 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.12 hwMflpQuitVlanResume

34.11 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.12hwMflpQuitVlanResume

DescriptionL2IFPPI/4/MFLPQUITVLANALARMRESUME:OID [oid] (vlan=[INTEGER]) Interface[OCTET1] has resumed of leaved from vlan [OCTET2] because mac move detected.

An interface that has been removed from a VLAN because of MAC address flapping joins theVLAN again.

Attribute



Parameters

Name Meaning

oid Indicates ID of a MIB object.



OCTET2 Indicates the VLAN from which the interface is removed.


Possible Causes1:

An interface that has been removed from a VLAN because of MAC address flapping joins theVLAN again.



411

Procedure


----End

Related Information

34.10 L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.11 hwMflpQuitVlanAlarm

34.12 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.1hwMacTrapAlarm

Description

L2IFPPI/5/MACCHANGE_TRAPINFO:OID [oid] Mac address information: [OCTET].

The MAC address changes.

Attribute



Parameters

Name Meaning


OCTET Indicates TypeIfindexVlaninvalidVlanidMac-address. The fields are described asfollows:l Type: MAC address change typel Ifindex: index of the interface where the MAC address changesl Vlaninvalid: VLAN flag bitl Vlanid: VLAN IDl Mac-address: MAC address


None.

Possible Causes

The device learns the MAC address or the MAC address is aged.



412

Procedure


----End


34.13 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.2hwPortVlanSecureMacAlarm

DescriptionL2IFPPI/4/PORTSEC_ACTION_HAVEMAC_ALARM:OID [oid] Interface ([INTEGER1]/[INTEGER2]) [OCTET1] receive insecure mac-address, and Mac address is [OCTET2], VLANis [INTEGER3], the port status is : [INTEGER4]. (1:restrict;2:protect;3:error-down)

On an interface where the number of learned secure MAC addresses reaches the maximum value,the interface sends an alarm when receiving invalid MAC addresses.

Attribute



Parameters

Name Meaning


[INTEGER1]/[INTEGER2] Indicates the index of an interface.


INTEGER3 Indicates the VLAN ID.

OCTET2 Indicates the MAC address.

INTEGER4 Indicates the interface status.


Possible CausesAfter the number of dynamic secure MAC addresses or sticky MAC addresses learned by aninterface reaches the maximum value, the interface receives packets from another MAC address.



413

Procedure

Step 1 Check whether the MAC address in the alarm is valid.

l If the MAC address is valid, go to step 2.

l If the MAC address is invalid, go to step 3.

Step 2 Run the port-security max-mac-num max-number command to increase the maximum numberof MAC address to be learned. Check whether the alarm is cleared.

l Y=>4

l N=>3

Step 3 If the alarm is not cleared, contact Huawei technical personnel.

Step 4 End.

----End

Related Information

None.

34.14 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.3hwSlotMacUsageRaisingThreshold

Description

L2IFPPI/4/MACEXCDALAR:OID [oid] The MAC Address usage exceeds the threshold.(MacUsageIndex=[INTEGER1],BaseTrapType=[INTEGER2],TrapSeverity=[INTEGER3],BaseTrapCause=[INTEGER4], MacUsage=[INTEGER5],MacUsageThreshold=[INTEGER6],PhysicalName=[OCTET])

The MAC address usage exceeds the upper alarm threshold.

Attribute



Parameters

Name Meaning


INTEGER1 Indicates the index of the MAC address usage.

INTEGER2 Indicates the sending type.

INTEGER3 Indicates the sending severity.



414

Name Meaning

INTEGER4 Indicates the sending cause.

INTEGER5 Indicates the MAC address usage.

INTEGER6 Indicates the alarm threshold for the MAC address usage.



Possible CausesThe MAC address usage exceeds the upper alarm threshold.

Procedure

Step 1 None.

----End


34.15 L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.4hwSlotMacUsageFallingThreshold

DescriptionL2IFPPI/4/MACEXCDALAR:OID [oid] The MAC Address usage falls below the threshold.(PhysicalIndex=[INTEGER1],BaseTrapType=[INTEGER2],TrapSeverity=[INTEGER3],BaseTrapCause=[INTEGER4],PhysicalName=[OCTET])

The MAC address usage is lower than the lower alarm threshold.

Attribute



Parameters

Name Meaning




415

Name Meaning

INTEGER1 Indicates the instance ID.

INTEGER2 Indicates the sending type.

INTEGER3 Indicates the sending severity.

INTEGER4 Indicates the sending cause.



Possible CausesThe MAC address usage is lower than the lower alarm threshold.

Procedure

Step 1 None.

----End




416

35 L2V

About This Chapter

35.1 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.7 hwVplsVcDeleted

35.2 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown

35.3 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp

35.4 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.8 hwVplsVcStatusChange

35.5 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.6 hwVplsVsiDeleted

35.6 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown

35.7 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp

35.8 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.5 hwVplsVcBackup

35.9 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.1 hwKompellaVcDown

35.10 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.2 hwKompellaVcUp

35.11 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.3 hwKompellaSwitchWtoP

35.12 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.4 hwKompellaSwitchPtoW

35.13 L2V_1.3.6.1.4.1.2011.5.25.119.3.2.1 hwCCCVcDown

35.14 L2V_1.3.6.1.4.1.2011.5.25.119.3.2.2 hwCCCVcUp

35.15 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.1 hwPWVcSwitchWtoP

35.16 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.2 hwPWVcSwitchPtoW

35.17 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.5 hwPWVcDeleted

35.18 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

35.19 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

35.20 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.6 hwPWVcBackup

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 35 L2V


417

35.21 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.3 hwSvcDown

35.22 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.4 hwSvcUp

35.23 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.5 hwSvcDeleted



418

35.1 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.7 hwVplsVcDeleted

DescriptionL2V/4/VPLSVC_DEL_T:OID [oid] The VPLS VC has been deleted. (VsiName=[STRING],PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER])

The VPLS VC was deleted.

Attribute



Parameters

Name Meaning

oid OID of the alarm

VsiName Name of the VSI

PwId ID of the PW

RemoteIp IP address of the remote peer

PwType Type of the PW. The values are as follows:1. normal2. other

Impact on the SystemIf the VPLS VC is Up, services on it are interrupted.


The peer was deleted in the VSI view, or the VSI was manually deleted.

Cause 2:

L2VPN or MPLS was disabled.

Procedure


----End



419

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.1.2.1_hwVplsVcDown

35.2 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown

DescriptionL2V/2/VPLSVC_DWN_ME_T:OID [oid] The status of the VPLS VC turned DOWN.(VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER],HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK],TunnelPolicyName=[STRING])

The VPLS VC changed from Up to Down.

Attribute



Parameters

Name Meaning

oid Indicates the trap OID.

VsiName Indicates the name of a VSI.

PwId Indicates the ID of a PW.

RemoteIp Indicates the IP address of the remote peer.

PwType Indicates the type of a PW:

l 1: normall 2: other

HWL2VpnStateChangeReason Indicates the cause of the VC status change.


TunnelPolicyName Indicates the name of a tunnel policy.

Impact on the SystemVPLS Services will be interrupted and the traffic will be blocked.

Possible CausesThe status of the physical link or the configurations on both ends of a link was changed.



420

Procedure

Step 1 Run the display vsi name vsi-name verbose command to check the VSIs on the local deviceand the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In thecase of the BGP VSI, check the VSIs with the same VPN target.

l If the AC interface (in the field of Interface Name in the command output) is Down, go toStep 2.

l If the status of the VSI is Admin Down, go to Step 3.

l If the MTUs or the encapsulation types on the local and peer devices are inconsistent, go toStep 4.

l If the PW does not exist, go to Step 5.

l If the PW is Down, go to Step 12.

Step 2 Restore the AC interface to Up, and check whether the alarm is cleared.



Step 3 Run the undo shutdown command in the VSI view to check whether the alarm is cleared.



Step 4 Run the mtu mtu command in the VSI view to set the MTUs of the VSIs on both ends to beconsistent. Run the encapsulation command to set the encapsulation types on both ends to beconsistent. Then, check whether the alarm is cleared.



Step 5 Run the display vsi name vsi-name verbose command to check the PW signaling.

l If it is LDP, go to Step 6.

l If it is BGP, go to Step 7.

Step 6 Run the display vsi name vsi-name verbose command to check whether the session on the VSIpeer is Up.



Step 7 Run the display bgp peer command to check whether the BGP connection with the peer in theVPLS address family is established.



Step 8 Run the display mpls ldp session command to check whether the session of the peer isoperational.



Step 9 Run the display vsi name vsi-name verbose command to check whether the session of the VSIpeer has the tunnel ID.



421



Step 10 Configure the BGP connection to be established, and check whether the alarm is cleared.



Step 11 Check whether the interface on the public network is Down. Set the interface on the publicnetwork to be Up, and then check the LDP configuration. Run the display mpls ldp sessioncommand to check that the session becomes operational, and then check whether the alarm iscleared.



Step 12 Check the configurations of the routes and public network interfaces one by one. If theconfiguration is correct, go to Step 14. If the configuration is incorrect, restore the configurationand check whether the alarm is cleared.




Step 14 End.

----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp

35.3 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp

Description

L2V/2/VPLSVC_UP_ME_T:OID [oid] The status of the VPLS VC turned UP. (VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER],HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK],TunnelPolicyName=[STRING])

The VPLS VC changed from Down to Up.

Attribute


1.3.6.1.4.1.2011.5.25.119.1.2.2 Major other(1)



422

Parameters

Name Meaning





PwType Indicates the type of a PW:l 1: normall 2: other

HWL2VpnStateChangeReason Indicates the cause of the VC status change. For details, referto hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.




Services will be recovered.

Possible Causes

The VPLS VC changed from Down to Up.

Procedure


----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown

35.4 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.8hwVplsVcStatusChange

Description

L2V/4/VPLSVC_STATUS_CHANGE_T:OID [OID] The status of the VPLS VC changed.(VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR],HWL2VpnStateChangeReason=[INTEGER], HWPwState=[INTEGER],HWPwWorkingState=[INTEGER], SysUpTime=[TIMETICK])



423

The VPLS VC status changes.

Attribute



Parameters

Name Meaning






HWPwState Indicates the PW status, which can be:l Upl Down

HWPwWorkingState Indicates the PW working status, which can be:l Masterl Backup




The status of the VPLS VC changed from Up to Down.

Cause 2:

The status of the VPLS VC changed from Down to Up.

Cause 3:

The working status of the VPLS VC changed from Master to Backup.

Cause 4:

The working status of the VPLS VC changed from Backup to Master.



424

Procedure


----End

35.5 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.6 hwVplsVsiDeleted

Description

L2V/4/VPLS_DEL_T:OID [oid] The VPLS VSI has been deleted. (VsiName=[STRING],VsiId=[GAUGE])

The VPLS VSI was deleted.

Attribute



Parameters

Name Meaning


VsiName Name of the VSI

VsiId ID of the VSI


VPLS services on the Up VCs in the VSI are interrupted.

Possible Causes

Cause 1:

The VSI was manually deleted.

Cause 2:


Procedure


----End



425

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.3_hwVplsVsiDown

35.6 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown

Description

L2V/2/VPLSVSI_DWN_T:OID [oid] The status of the VPLS VSI turned DOWN. (VsiName=[STRING], InterfaceIndex=[INTEGER], VsiId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], VsiStatus=[INTEGER], InterfaceName=[STRING])

The VPLS VSI changed from Up to Down.

Attribute



Parameters

Name Meaning



InterfaceIndex Indicates the interface index.

VsiId Indicates the ID of a VSI.

HWL2VpnStateChangeReason Indicates the cause of the VSI status change. For details, referto hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.

VsiStatus Indicates the status of the VSI:l 1: VSI Upl 2: VSI Downl 3: VSI Admin down



VPLS Services will be interrupted and the traffic will be blocked.

Possible Causes

The status of the physical link or the VPLS configuration of any VSI device was changed.



426

Procedure

Step 1 Run the display vsi name vsi-name verbose command to check the VSIs on the local deviceand the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In thecase of the BGP VSI, check the VSIs with the same VPN target.

l If the AC interface (in the field of Interface Name in the command output) is Down, go toStep 2.

l If the status of the VSI is Admin Down, go to Step 3.

l If the MTUs or the encapsulation types on the local and peer devices are inconsistent, go toStep 4.

l If the PW does not exist, go to Step 5.

l If the PW is Down, go to Step 12.

Step 2 Restore the AC interface to Up, and check whether the alarm is cleared.



Step 3 Run the undo shutdown command in the VSI view to check whether the alarm is cleared.



Step 4 Run the mtu mtu command in the VSI view to set the MTUs of the VSIs on both ends to beconsistent. Run the encapsulation command to set the encapsulation types on both ends to beconsistent. Then, check whether the alarm is cleared.



Step 5 Run the display vsi name vsi-name verbose command to check the PW signaling.

l If it is LDP, go to Step 6.

l If it is BGP, go to Step 7.

Step 6 Run the display vsi name vsi-name verbose command to check whether the session on the VSIpeer is Up.



Step 7 Run the display bgp peer command to check whether the BGP peer is established.



Step 8 Run the display mpls ldp session command to check whether the session of the peer isoperational.



Step 9 Run the display vsi name vsi-name verbose command to check whether the session of the VSIpeer has the tunnel ID.




427


Step 10 Configure the BGP connection to be established, and check whether the alarm is cleared.



Step 11 Check whether the interface on the public network is Down. Set the interface on the publicnetwork to be Up, and then change the LDP configuration. Run the display mpls ldp sessioncommand to check that the session becomes operational, and then check whether the alarm iscleared.



Step 12 Repeat the preceding steps on the remote device. Then, check whether the alarm is cleared.




Step 14 End.

----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp

35.7 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp

Description

L2V/2/VPLSVSI_UP_T:OID [oid] The status of the VPLS VSI turned UP. (VsiName=[STRING], InterfaceIndex=[INTEGER], VsiId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], VsiStatus=[INTEGER], InterfaceName=[STRING])

The VPLS VSI changed from Down to Up.

Attribute


1.3.6.1.4.1.2011.5.25.119.1.2.4 Major other(1)

Parameters

Name Meaning




428

Name Meaning



VsiId Indicates the ID of a VSI.

HWL2VpnStateChangeReason Indicates the cause of the VSI status change. For details, referto hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.

VsiStatus Indicates the status of the VSI:l 1: Upl 2: Downl 3: Admin Down


Impact on the SystemServices will be recovered.

Possible CausesThe VPLS VSI changed from Down to Up.

Procedure


----End

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown

35.8 L2V_1.3.6.1.4.1.2011.5.25.119.1.2.5 hwVplsVcBackup

DescriptionL2V/1/VPLSVC_BACKUP_T:OID [oid] The status of the VPLS VC turned BACKUP.(VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER],HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK])

The VPLS VC turned to the Backup state.



429

Attribute


1.3.6.1.4.1.2011.5.25.119.1.2.5 Critical other(1)

Parameters

Name Meaning





PwType Indicates the type of a PW:l 1: normall 2: other




If the VRRP works normally, packet loss will occur within a short period of time when the trafficis switched from the master VRRP to the backup VRRP. Services will not be affected when thetraffic is switched back from the backup VRRP to the master VRRP.

Possible Causes

1.

The PW-bound VRRP protection group turned to the non-master state.

2.

The PW-bound VRRP protection group turned to the backup state.

3.

The interface board configured with the PW-bound VRRP protection group was pulled out.

Procedure

Step 1 Check the status of the VRRP, and then rectify the fault according to the solution to theVrrpTrapNewMaster trap.

----End



430

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp

35.9 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.1hwKompellaVcDown

DescriptionL2V/2/BGPVC_DWN_T:OID [oid] The status of the Kompella VC turned DOWN.(VcVpnName=[STRING], CeId=[GAUGE], InterfaceIndex=[INTEGER], RemoteCeId=[GAUGE], SecondaryVc=[INTEGER], HWL2VpnStateChangeReason=[INTEGER],PeerAddress=[IPADDR], TunnelPolicyName=[STRING])

A Kompella VC became Down.

Attribute


1.3.6.1.4.1.2011.5.25.119.2.2.1 Major processingErrorAlarm(4)

Parameters

Name Meaning


VcVpnName Indicates the VPN name.

CeId Indicates the ID of the local CE.


RemoteCeId Indicates the ID of the remote CE.

SecondaryVc Indicates the backup VC.


PeerAddress Indicates the IP address of a peer.


Impact on the SystemServices will be interrupted and the traffic will be blocked.

Possible CausesA Kompella VC became Down.



431

Procedure

Step 1 Run the display mpls l2vpn connection interface interface-type interface-number commandto view the conn-type of the VC.

l If the conn-type is unknown, go to Step 2.

l If the conn-type is local, go to Step 14.

l If the conn-type is remote, go to Step 5.

Step 2 Run the display bgp l2vpn peer command to check whether the BGP peer is established.


l If not, check whether the BGP configuration is correct and the trap recovers.

– If so, go to Step 17.

– If not, go to Step 16.

Step 3 Check and restore the Kompella configuration on the peer.



Step 4 Check the status of the local VC, including the physical status of the local AC interface, linkstatus of the AC interface, status of the manual fault, and status of the selected tunnel.

l If the local VC is Down, go to Step 6.

l If the local VC is Up, go to Step 12.

Step 5 Run the display interface interface-type interface-number command to view the physical statusof the interface, and change the physical status of the interface to Up.



Step 6 Check information about the tunnel of the VC.

l If the tunnel does not exist, go to Step 8.

l If the tunnel exists, go to Step 9.

Step 7 Run the display tunnel-info all command to check information about the tunnel connected tothe peer. Modify the configuration on the outbound interface in a public network and restore thetunnel connected to the peer.



Step 8 Check the OAM status of the AC.

l If it is Down, go to Step 10.

l If it is Up, go to Step 11.

Step 9 Run the display interface interface-type interface-number command to check the link status ofthe interface. Restore the link status of the interface to Up.



Step 10 Check whether the manual fault is set or not. If it is set, cancel the setting on the AC interface.



432



Step 11 Run the display mpls l2vpn connection interface interface-type interface-number commandto check the status of the remote VC.



Step 12 Check and restore the status of the Kompella VC on the peer.



Step 13 Check the physical status of the AC interface.



Step 14 Restore the physical status of the interface to Up.



Step 15 Check the physical status of the local interface that is connected to the peer, and restore thephysical status to Up.




Step 17 End.

----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.2 hwKompellaVcUp

35.10 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.2 hwKompellaVcUp

Description

L2V/2/BGPVC_UP_T:OID [oid] The status of the Kompella VC turned UP. (VcVpnName=[STRING], CeId=[GAUGE], InterfaceIndex=[INTEGER], RemoteCeId=[GAUGE],SecondaryVc=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], PeerAddress=[IPADDR], TunnelPolicyName=[string])

A Kompella VC became Up.



433

Attribute


1.3.6.1.4.1.2011.5.25.119.2.2.2 Major other(1)

Parameters

Name Meaning






SecondaryVc Indicates the backup VC.




Impact on the SystemThe service will be recovered.

Possible CausesA Kompella VC became Up.

ProcedureStep 1 This trap message is informational only, and no action is required.

----End

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.2.2.1 hwKompellaVcDown

35.11 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.3hwKompellaSwitchWtoP

DescriptionL2V/2/BGPVC_W2P_T:OID [oid] The status of the Kompella VC turned protecting fromworking. (VcVpnName=[STRING], CeId=[GAUGE], InterfaceIndex=[INTEGER],



434

RemoteCeId=[GAUGE],CtrlWord=[INTEGER], SecondaryVcRemoteCeId=[GAUGE],HWL2VpnStateChangeReason=[INTEGER])

Attribute



Parameters

Name Meaning






CtrlWord Indicates whether the control word is enabled:

l 1: indicates that the control word is enabled.l 2: indicates that the control word is disabled.

SecondaryVcRemoteCeId Indicates the ID of the remote CE whose VC is in theProtection state.

HWL2VpnStateChangeReason Indicates the cause of the VC status change. For details, referto hwKompellaVcStateChangeReason in the appendix ofHUAWEI-KOMPELLA-MIB.

Impact on the SystemThe switchover between the primary VC and the backup VC has no impact on services.

Possible CausesA Kompella VC was changed from a working link to a protection link.

Procedure

Step 1 Refer to the solution to the hwKompellaVcDown trap. Then, check whether the fault is rectified.l If so, go to Step 3.l If not, go to Step 2.


Step 3 End.

----End



435

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.2.2.4 hwKompellaSwitchPtoW

35.12 L2V_1.3.6.1.4.1.2011.5.25.119.2.2.4hwKompellaSwitchPtoW

DescriptionL2V/2/BGPVC_P2W_T:OID [oid] The status of the Kompella VC turned working fromprotecting. (VcVpnName=[STRING], CeId=[GAUGE], InterfaceIndex=[INTEGER],RemoteCeId=[GAUGE], CtrlWord=[INTEGER], PrimaryVcRemoteCeId=[GAUGEs],HWL2VpnStateChangeReason=[INTEGER])

A Kompella VC was changed from protection state to working state.

Attribute



Parameters

Name Meaning







l 1: indicates that the control word is enabled.l 2: indicates that the control word is disabled.

PrimaryVcRemoteCeId Indicates the ID of the remote CE whose VC is in the Workingstate.

HWL2VpnStateChangeReason Indicates the cause of the VC status change. For details, referto hwKompellaVcStateChangeReason in the appendix ofHUAWEI-KOMPELLA-MIB.

Impact on the SystemThe switchover between the primary VC and the backup VC has no impact on services.



436

Possible Causes

A Kompella VC was changed from a protection link to a working link.

Procedure

Step 1 The trap message is informational only, and no action is required.

----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.3 hwKompellaSwitchWtoP

35.13 L2V_1.3.6.1.4.1.2011.5.25.119.3.2.1 hwCCCVcDown

Description

L2V/3/CCCVC_DWN_T:OID [oid] The status of the CCC VC turned DOWN. (CccName=[STRING], InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER],HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

The alarm was generated when the CCC VC was Down.

Attribute


1.3.6.1.4.1.2011.5.25.119.3.2.1 Minor processingErrorAlarm(4)

Parameters

Name Meaning


CccName Name of the CCC connection

InterfaceIndex Index of the interface used as the table index

InterfaceIndex Index of the interface reported to the network managementsystem as a parameter

HWL2VpnStateChangeReason Cause of the VC status change. For details, see"hwCCCVcStateChangeReason" in the appendix ofHUAWEI-CCC-MIB.

InterfaceName Name of the interface



437


Services will be interrupted and traffic cannot be forwarded properly.

Possible Causes

1.

The inbound or outbound interface of CCC services became Down, or CCC configurations weredeleted.

2.

MPLS or MPLS L2VPN was disabled.

3.

The IP address of the outbound interface of CCC services was deleted or changed into an IPaddress in a different segment.

Procedure

Step 1 Check whether the current configuration is the same as the original configuration. For example,check whether MPLS is enabled globally, or whether MPLS is enabled on the CCC outboundinterface.


l If not, go to Step 2

Step 2 Restore the original configuration. Then, check whether the alarm is cleared.



Step 3 Run the display vll ccc ccc-name command to check the status of the two interfaces of the CCCVC.

l If either interface is Down or both interfaces are Down, go to Step 4.

l If both interfaces are Up, go to Step 8.

l If one interface goes UP, and the IP address of next hop of the other interface are displayed,go to Step 5.

Step 4 View the cause that the interface is Down and restore the interface to the Up status. Then, checkwhether the alarm is cleared.

l If cleared, go to Step 9.

l If persists, go to Step 8.

Step 5 Run the display ip routing-table command to check whether the IP address is reachable.



Step 6 Run the display ip interface brief command to check whether there are addresses that are inthe same segment with the IP address.




438

l If not, it indicates that the outbound interface address is deleted or changed. In this case, goto Step 7.

Step 7 Enter the view of the outbound interface and reconfigure an IP address in consistent with theoriginal configuration. Then, check whether the alarm is cleared.




Step 9 End.

----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.3.2.2 hwCCCVcUp

35.14 L2V_1.3.6.1.4.1.2011.5.25.119.3.2.2 hwCCCVcUp

Description

L2V/3/CCCVC_UP_T:OID [oid] The status of the CCC VC turned UP. (CccName=[STRING],InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

The trap was generated when the CCC VC was Up.

Attribute


1.3.6.1.4.1.2011.5.25.119.3.2.2 Minor other(1)

Parameters

Name Meaning


CccName Indicates the name of the CCC connection.

InterfaceIndex Index of the interface used as the table index.

InterfaceIndex Index of the interface reported to the network managementsystem as a parameter.

HWL2VpnStateChangeReason Indicates the cause of the VC status change. For details, referto hwCCCVcStateChangeReason in the appendix ofHUAWEI-CCC-MIB.



439

Name Meaning



The CCC service will be recovered.

Possible Causes

1.

The trap was generated when a VC became Up.

2.

The configuration was modified. For example, the next hop address of the CCC was changed.

Procedure

Step 1 Check whether the service is restored.

l If so, it indicates that the trap message is informational only, and no action is required.


Step 2 Check whether the current configuration is the same as the original configuration. For example,check whether the next hop address of the CCC is the same as the address of the peer interfaceof the outbound interface.



Step 3 Restore the original configuration and check whether the alarm is cleared.


l If the trap is no cleared, go to Step 4.


Step 5 End.

----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.3.2.1 hwCCCVcDown

35.15 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.1hwPWVcSwitchWtoP



440

Description

L2V/4/PWE3VC_W2P_T:OID [oid] The status of the PWE3 VC turned protecting fromworking. ( VcId=[GAUGE], VcType=[INTEGER], CtrlWord=[INTEGER], SecondaryPwId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

Indicates that a PW changes from the primary state to the secondary state.

Attribute


1.3.6.1.4.1.2011.5.25.119.4.1.2.1 Warning other(1)

Parameters

Name Meaning


VcId Indicates the ID of a VC.

VcType Indicates the type of a VC:

l 0: Initial valuel 1: FRl 2: ATM AAL5l 3: ATM cell relayl 4: VLANl 5: Ethernetl 6: HDLCl 7: PPPl 9: ATM cell VCCl 10: ATM cell VPCl 11: IP-layer 2 (used for heterogeneous IP-interworking

between Huawei devices and non-Huawei devices)l 12: ATM, 1-to-1 VCC cell model 13: ATM, 1-to-1 VPC cell model 14: ATM, AAL5 PDU VCC Transportl 64: Heterogeneous IP-interworking


l 1: enabledl 2: disabled

SecondaryPwId Indicates the remote CE ID of the VC in the Protecting state.



441

Name Meaning

HWL2VpnStateChangeReason Indicates the cause for the VC status change. For details, referto hwPwStateChangeReason in the appendix of HUAWEI-PWE3-MIB.



Packet loss in millisecond may occur in the switching process. The packet loss, however, affectslittle to the PWE3 service.

Possible Causes

The VLL service is switched from the primary PW to the secondary PW.

Procedure

Step 1 Rectify the fault according to the solution to the hwPWVcDown trap. Then, check whether thefault is rectified.




Step 3 End.

----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.2 hwPWVcSwitchPtoW

35.16 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.2hwPWVcSwitchPtoW

Description

L2V/4/PWE3VC_P2W_T:OID [oid] The status of the PWE3 VC turned working fromprotecting. (VcId=[GAUGE], VcType=[INTEGER], CtrlWord=[INTEGER], PrimaryPwId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

Indicates that a PW changes from the secondary state to the primary state.



442

Attribute


1.3.6.1.4.1.2011.5.25.119.4.1.2.2 Warning other(1)

Parameters

Name Meaning



VcType Indicates the type of a VC:l 0: Initial valuel 1: FRl 2: ATM AAL5l 3: ATM cell relayl 4: VLANl 5: Ethernetl 6: HDLCl 7: PPPl 9: ATM cell VCCl 10: ATM cell VPCl 11: IP-layer 2 (used for heterogeneous IP-interworking

between Huawei devices and non-Huawei devices)l 12: ATM, 1-to-1 VCC cell model 13: ATM, 1-to-1 VPC cell model 14: ATM, AAL5 PDU VCC TRANSPORTl 64: Heterogeneous IP-interworking


l 1: enabledl 2: disabled

PrimaryPwId Indicates the remote CE ID of the VC in the Working state.

HWL2VpnStateChangeReason Indicates the cause for the VC status change. For details, referto hwPwStateChangeReason in the appendix of HUAWEI-PWE3-MIB.




443


Packet loss in millisecond may occur in the switching process. The packet loss, however, affectslittle to the PWE3 service.

Possible Causes

The primary PW is rectified, and the VLL service is switched from the secondary PW to theprimary PW.

Procedure


----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.1 hwPWVcSwitchWtoP

35.17 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.5 hwPWVcDeleted

Description

L2V/4/PWE3VC_DEL_T:OID [oid] The PWE3 VC has been deleted. (VcId=[GAUGE],VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER],VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER],InterfaceName=[STRING], SwitchVcId=[GAUGE])

The LDP VC was deleted.

Attribute


1.3.6.1.4.1.2011.5.25.119.4.1.2.5 Warning qualityOfServiceAlarm (3)

Parameters

Name Meaning


VcId ID of the VC



444

Name Meaning

VcType Type of the VC. The values are as follows:l 0: initial valuel 1: FRl 2: ATM AAL5l 3: ATM cell relayl 4: VLANl 5: Ethernetl 6: HDLCl 7: PPPl 9: ATM cell VCCl 10: ATM cell VPCl 11: IP-layer 2 (used for heterogeneous IP-interworking between

Huawei devices and non-Huawei devices)l 12: ATM, 1-to-1 VCC cell model 13: ATM, 1-to-1 VPC cell model 14: ATM, AAL5 PDU VCC transportl 64: heterogeneous interworking

PeerAddress IP address of the peer

InterfaceIndex Index of the interface

VcInboundLabel Inbound label of the VC

VcOutboundLabel Outbound label of the VC

SecondaryPw Whether the PW is a secondary PWl 1: The PW is a secondary PW.l 2: The PW is not a secondary PW.


SwitchVcId ID of the switching VC


PWE3 services are interrupted.

Possible Causes

Cause 1:

The LDP VC was manually deleted.

Cause 2:




445

Procedure


----End

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3_hwPWVcDown

35.18 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

DescriptionL2V/2/PWE3VC_DWN_ME_T:OID [oid] The status of the PWE3 VC turned DOWN. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER],VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER],HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], InterfaceName=[STRING], SwitchVcId=[GAUGE], TunnelPolicyName=[STRING])

Indicates that a VC of the PWE3 goes Down.

Attribute


1.3.6.1.4.1.2011.5.25.119.4.1.2.3 Major processingErrorAlarm(4)

Parameters

Name Meaning





446

Name Meaning





VcInboundLabel Indicates the incoming label of a VC.

VcOutboundLabel Indicates the outgoing label of a VC.


HWL2VpnStateChangeReason Indicates the cause for the VC status change.

SysUpTime Indicates the time for the system startup.

InterfaceName Indicates the name of an interface.

SwitchVcId Indicates the ID of the switching VC.


Impact on the Systemthe PWE3 service is interrupted and traffic is blocked.

Possible Causes1.

The local or peer AC interface went Down.



447

2.

The public network tunnel was faulty.

Procedure

Step 1 Run the display mpls l2vc interface interface-type interface-number command to check thestatus of the local PWE3. If the VC is in a Down state, it indicates that the PWE3 is also in theDown state. Then you need to find the cause for the Down state. The handling procedures areas follows:

1. Check whether the LDP session is in the Down state or the Up state.

l If the LDP session is Down, go to Step b.

l If the LDP session is Up, go to Step c.

2. Run the display mpls ldp session command to check the status of the LDP session to theremote end. If the LDP session of the peer does not exist, or the LDP session is not inOperational state, restore the status of the LDP session.

l If the status is restored, go to Step c.

l If the status is not restored, go to Step u.

3. Check the AC state that indicates the physical status of the interface at the AC side of PWE3.

l If the AC state is Down, go to Step d.

l If the AC state is Up, go to Step e.

4. Run the display interface interface-type interface-number command to view the physicalstatus of the interface. If the physical status of the interface is Down, restore the physicalstatus to Up.

l If so, go to Step e.

l If not, go to Step u.

5. Check the local AC OAM State that indicates the link status of the interface at the AC sideof PWE3. If AC OAM is enabled, you can check the related status of AC OAM. If ACOAM is not enabled, the local AC OAM status is Up.

l If the local AC OAM state is Down, go to Step f.

l If the local AC OAM state is Up, go to Step g.

6. Run the display interface interface-type interface-number command to check the linkstatus of the interface. If the link status of the interface is Down, restore the link status toUp.

l If so, go to Step g.


7. Check whether the local PSN state, that is, the status of BFD for LSP in PWE3, is Up. Notethat the local PSN state is Down if the tunnels selected by the L2VPN are all Down afterthe BFD for LSP detection. Otherwise, the local PSN state is Up.

l If the local PSN state is Down, go to Step h.

l If the local PSN state is Up, go to Step i.

8. Run the display bfd session all command to check the status of BFD for LSP. If the statusof BFD for LSP is Down, restore the status to Up.

l If so, go to Step i.



448

l If not, go to Step t.

9. Check the status of the local forwarding state, which indicates whether the local PWE3 canachieve forwarding. The local forwarding state indicates the AC status, status of the manualfault, and the status of the tunnel in the public network.

l If it is not in the forwarding state, go to Step j.

l If it is in the forwarding state, go to Step l.

10. Check whether the interface is enabled with the function of manual fault. If so, disable thefunction.

l If so, go to Step k.


11. Check the token information of the VC tunnel, and find whether a tunnel is selected. Theparameter 0 indicates that no tunnel is selected; other parameters indicate that the tunnel isselected.

l If the parameter is 0, perform Step l.

l If the parametric is not 0, perform Step m.

12. Run the display tunnel-info all command to check information about the tunnel connectedto the peer. Modify the configuration on the outbound interface on a public network andrestore the tunnel connected to the peer.

l If so, go to Step m.


13. Check the status of the remote PWE3, which is indicated by the remote AC OAM state,remote PSN state, and remote forwarding state.

l If the remote AC OAM state or the remote PSN state is Down, or the remote forwardingstate is not forwarding, go to Step n.

l If the remote AC OAM state and the remote PSN state are Up, and the remote forwardingstate is forwarding, go to Step o.

14. Check the PWE3 status on the remote router. If the PWE3 status is Down, restore the PWE3status.

l If the operation succeeds, go to Step o.

l If the operation fails, go to Step u.

15. Check whether the BFD state, that is, the status of BFD for PW, is Up.

l If the BFD state is Down, go to Step p.

l If the BFD state is Up or unavailable, go to Step q.

16. Run the display bfd session all command to check the status of BFD for PW.

l If the status of BFD for PW is the same as the VC state, go to Step q.

l If the status of BFD for PW is not the same as the VC state, go to Step u.

17. Check whether the local VC MTU is the same as the remote VC MTU.

l If so, go to Step s.

l If not, go to Step r.

18. Check the MTU of the local AC interface and the MTU of the PWE3 interface on the peerrouter. If two MTUs are not the same, modify them to be the same.

l If so, go to Step s.



449


19. Check whether the local control word is the same as the remote control word. Note thatthey are the same only when both are either in the enable state or in the disable state.

l If so, go to Step v.

l If not, go to Step t.

20. Ensure the local control word and the remote control word and ensure that they are thesame.

l If so, go to Step v.


21. Contact Huawei technical support personnel.

22. End.

----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

35.19 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

Description

L2V/2/PWE3VC_UP_ME_T:OID [oid] The status of the PWE3 VC turned UP. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER],VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER],HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], InterfaceName=[STRING], SwitchVcId=[GAUGE], TunnelPolicyName=[STRING])

The trap was generated when the PWE3 VC was Up.

Attribute


1.3.6.1.4.1.2011.5.25.119.4.1.2.4 Major other(1)

Parameters

Name Meaning





450

Name Meaning











SwitchVcId Switches the ID of VC.



The PWE3 service is recovered.

Possible Causes

A VC recovers from a fault.



451

Procedure


----End

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

35.20 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.6 hwPWVcBackup

DescriptionL2V/2/PWE3VC_BACKUP_T:OID [oid] The status of the PWE3 VC turned BACKUP. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER],VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER],HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], InterfaceName=[STRING], SwitchVcId=[GAUGE])

Indicates that a VC turns to the backup state.

Attribute


1.3.6.1.4.1.2011.5.25.119.4.1.2.6 Major other(1)

Parameters

Name Meaning





452

Name Meaning











SwitchVcId Switches the ID of VC.

Impact on the SystemThe VRRP status affects the service.

Possible CausesA VC turned to the backup state.



453

Procedure

Step 1 Check the status of the VRRP, and then rectify the fault according to the solution to theVrrpTrapNewMaster trap.

----End

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

35.21 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.3 hwSvcDown

DescriptionL2V/2/SVC_DWN_T:OID [oid] The status of the SVC VC turned DOWN. (InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], SvcId=[GAUGE], SVcType=[INTEGER],PeerAddress=[IPADDR], SvcInboundLabel=[GAUGE], SvcOutboundLabel=[GAUGE],HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING],TunnelPolicyName=[STRING])

Indicates an SVC goes Down.

Attribute


1.3.6.1.4.1.2011.5.25.119.4.1.4.3 Major processingErrorAlarm(4)

Parameters

Name Meaning



InterfaceIndex Index of the interface reported to the network managementsystem as a parameter.

SvcId Indicates the ID of an SVC.



454

Name Meaning

SVcType Indicates the type of an SVC:l 0: Initial valuel 1: FRl 2: ATM AAL5l 3: ATM cell relayl 4: VLANl 5: Ethernetl 6: HDLCl 7: PPPl 9: ATM cell VCCl 10: ATM cell VPCl 11: IP-layer 2 (used for heterogeneous IP-interworking

between Huawei devices and non-Huawei devices)l 12: ATM, 1-to-1 VCC cell model 13: ATM, 1-to-1 VPC cell model 14: ATM, AAL5 PDU VCC Transportl 64: Heterogeneous IP-interworking


SvcInboundLabel Indicates the incoming label of an SVC.

SvcOutboundLabel Indicates the outgoing label of an SVC.

HWL2VpnStateChangeReason Indicates the cause for the SVC status change.



Impact on the SystemThe SVC service is interrupted and the traffic is blocked.

Possible Causes1.

The local or peer AC interface went Down.

2.

The public network tunnel was faulty.



455

Procedure

Step 1 Run the display mpls static-l2vc interface interface-type interface-number command to checkwhether the AC goes Up.l If so, go to Step 3.l If not, go to Step 2.

NOTE

The SVC status can be Up if two conditions are met. That is, the AC status is Up and the tunnel is selected.

Step 2 Check whether the AC interface goes Down.l If so, rectify the fault and ensure that the AC interface goes Up. Then, check whether the

fault is rectified. If so, go to Step 7; if not, go to Step 3.l If not, go to Step 3.

Step 3 View the command output in Step 1 to check whether the number of tunnels in the VC tunnel/token info field is 0.l If so, go to Step 4.l If not, go to Step 7.

Step 4 Run the display tunnel-info all command to check whether there is information about the LSPtunnel with the destination address being the address of the peer PE.l If so, go to Step 7.l If no, go to Step 5.

Step 5 Check and rectify the configuration of the public network interface. Check whether the fault isrectified.l If so, go to Step 7.l If not, go to Step 6.


Step 7 End.

----End

Related InformationL2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.4 hwSvcUp

35.22 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.4 hwSvcUp

DescriptionL2V/2/SVC_UP_T:OID [oid] The status of the SVC VC turned UP. (InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], SvcId=[GAUGE], SVcType=[INTEGER],PeerAddress=[IPADDR], SvcInboundLabel=[GAUGE], SvcOutboundLabel=[GAUGE],HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING],TunnelPolicyName=[STRING])

The trap was generated when the SVC VC was Up.



456

Attribute


1.3.6.1.4.1.2011.5.25.119.4.1.4.4 Major other(1)

Parameters

Name Meaning



InterfaceIndex Index of the interface reported to the network managementsystem as a parameter .

SvcId Indicates the ID of an SVC.

SVcType Indicates the type of an SVC:l 0: Initial valuel 1: FRl 2: ATM AAL5l 3: ATM cell relayl 4: VLANl 5: Ethernetl 6: HDLCl 7: PPPl 9: ATM cell VCCl 10: ATM cell VPCl 11: IP-layer 2 (used for heterogeneous IP-interworking



SvcInboundLabel Indicates the incoming label of an SVC.

SvcOutboundLabel Indicates the outgoing label of an SVC.

HWL2VpnStateChangeReason Indicates the cause for the SVC status change.





457


The SVC service is recovered.

Possible Causes

An SVC goes Up.

Procedure


----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.3 hwSvcDown

35.23 L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.5 hwSvcDeleted

Description

L2V/4/SVC_DEL_T:OID [oid] The SVC has been deleted. (InterfaceIndex=[INTEGER],InterfaceIndex=[INTEGER], SvcId=[GAUGE], SVcType=[INTEGER], PeerAddress=[IPADDR], SvcInboundLabel=[GAUGE], SvcOutboundLabel=[GAUGE], InterfaceName=[STRING])

The SVC was deleted.

Attribute



Parameters

Name Meaning


InterfaceIndex Index of the interface used as the table index

InterfaceIndex Index of the interface reported to the network management system as aparameter

SvcId ID of the SVC



458

Name Meaning

SVcType Type of the SVC. The values are as follows:l 0: initial valuel 1: FRl 2: ATM AAL5l 3: ATM cell relayl 4: VLANl 5: Ethernetl 6: HDLCl 7: PPPl 9: ATM cell VCCl 10: ATM cell VPCl 12: ATM, 1-to-1 VCC cell model 13: ATM, 1-to-1 VPC cell model 14: ATM, AAL5 PDU VCC transportl 64: heterogeneous interworking

PeerAddress IP address of the peer

SvcInboundLabel Inbound label of the SVC

SvcOutboundLabel Outbound label of the SVC



SVC services are interrupted.

Possible Causes

Cause 1:

The SVC was manually deleted.

Cause 2:


Procedure


----End

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.3_hwSvcDown



459

36 L3MB

About This Chapter

36.1 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.5 hwBoardL3FwdResLack

36.2 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.6 hwBoardL3FwdResLackResume

36.3 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.7 hwBoardL3ACLResLack

36.4 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.8 hwBoardL2mcResLack

36.5 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.9 hwBoardL2mcResLackResume

36.6 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.10 hwBoardipmcResLack

36.7 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.11 hwBoardipmcResLackResume

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 36 L3MB


460

36.1 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.5hwBoardL3FwdResLack

DescriptionL3MB/4/FwdResLack:OID [OID] The layer 3 resource usage has has reached or exceeded[Threshold]%.(EntPhysicalindex=[GAUGE],EntPhysicalName=[OCTET],Slot=[OCTET],ResourceType=[INTEGER])

The Layer 3 resource usage reaches or exceeds the upper threshold. Except the IPv4 route prefixentries, all Layer 3 resources have a upper usage threshold of 85%.

NOTE

You can use the fib threshold-alarm command to set the upper threshold of the IPv4 route prefix entries.

By default, the upper threshold of the IPv4 route prefix entries is 80%.

Attribute



Parameters

Name Meaning

OID This object indicates the ID of a MIB object.

Threshold This object indicates the upper threshold of the layer 3 resource usage.

EntPhysicalindex This object indicates the index of a physical entity.

EntPhysicalName This object indicates the name of a physical entity.

Slot This object indicates the slot ID.



461

Name Meaning

ResourceType This object indicates the ID of a Layer 3 resource.l hostTablePrefixTable(27) indicates the host route prefix entry.l routingTablePrefixTable(28) indicates the IPv4 route prefix entry.l ecmpNextHopTable(29) indicates the next hop entry of the equal-cost

route.l layer3InterfaceTable(30) indicates the Layer 3 outbound interface

entry.l nextHopTable(31) indicates the next hop entry.l tunnelDecapsulationTable(32) indicates the tunnel encapsulation and

decapsulation entry.l ipv6RoutingTablePrefixTable(47) indicates the IPv6 route prefix entry.NOTE

Multiple services share Layer 3 resources, including IPv4 unicast, IPv6 unicast, ARP,ND, GRE, L3VPN, MPLS, VPLS, and VPWS.


When the Layer 3 resource usage exceeds the upper threshold, services are not affected. If theusage of all Layer 3 resources reaches 100%, new Layer 3 services are unavailable.

Possible Causes

When the Layer 3 resource usage exceeds the upper threshold, an alarm is generated. When theusage reaches 100%, an alarm is generated again.

Procedure

Step 1 Lower the Layer 3 resource usage.

l Delete unnecessary host routes, and ND and ARP entries to release host route prefixresources.

l Delete unnecessary network segment routes to release IPv4 route prefix resources.

l Delete unnecessary equal-cost routes to release next hop resources.

l Delete unnecessary Layer 3 interfaces to release Layer 3 interface resources.

l Delete unnecessary routes including host routes and network segment routes, and ND andARP entries to release next hop resources.

l Delete tunnels to release tunnel encapsulation and decapsulation resources.

l Delete unnecessary network segment routes to release IPv6 route IPv6 prefix entries.


Step 3 End.

----End



462


36.2 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.6hwBoardL3FwdResLackResume

DescriptionL3MB/4/FwdResResume:OID [OID] The layer 3 resource usage is restored to be lower than[Threshold]%.(EntPhysicalindex=[GAUGE],EntPhysicalName=[OCTET],Slot=[OCTET],ResourceType=[INTEGER])

The Layer 3 resource usage is restored to be lower than the lower threshold. Except the IPv4route prefix entries, all Layer 3 resources have a lower usage threshold of 65%.

NOTE

You can use the fib threshold-alarm command to set the lower threshold of the IPv4 route prefix entries.

By default, the lower threshold of the IPv4 route prefix entries is 80%.

Attribute



Parameters

Name Meaning

OID This object indicates the ID of a MIB object

Threshold This object indicates the lower threshold of the layer 3 resource usage.

EntPhysicalindex This object indicates the index of a physical entity.

EntPhysicalName This object indicates the name of a physical entity.

Slot This object indicates the slot ID.



463

Name Meaning

ResourceType This object indicates the ID of a Layer 3 resource.l hostTablePrefixTable(27) indicates the host route prefix entry.l routingTablePrefixTable(28) indicates the IPv4 route prefix entry.l ecmpNextHopTable(29) indicates the next hop entry of the equal-cost

route.l layer3InterfaceTable(30) indicates the Layer 3 outbound interface

entry.l nextHopTable(31) indicates the next hop entry.l tunnelDecapsulationTable(32) indicates the tunnel encapsulation and

decapsulation entry.l ipv6RoutingTablePrefixTable(47) indicates the IPv6 route prefix entry.


Services are not affected.

Possible Causes

The Layer 3 resource usage is restored to be lower than the lower threshold.

Procedure

Step 1 This message is informational only and no action is required.

----End

Related Information

None

36.3 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.7hwBoardL3ACLResLack

Description

L3MB/4/ACLRESOURCELACK:OID [OID] [OCTET].(Slot=[OCTET],ReasonID=[INTEGER])

A Layer 3 service failed because of insufficient ACL resources.

Attribute


1.3.6.1.4.1.2011.5.25.227.2.1.7 Warning equipmentAlarm (5)



464

Parameters

Name Meaning


[OCTET] Indicates a type of Layer 3 service. The value can be:l Failed to enable nd snooping: failed to enable the neighbor discovery (ND)

snooping function.l Failed to enable ipv6: failed to enable the IPv6 function.l Failed to start nqa-rtp instance: failed to start an NQA RTP test instance.

Slot Indicates a slot number.

ReasonID Indicates an alarm reason ID.l l3aclFailed (72): failed to deliver an ACL.


The Layer 3 service specified in the alarm is unavailable.

Possible Causes

ACL resources were insufficient.

Procedure

Step 1 Delete unnecessary ACLs and then deliver the Layer 3 service again.

Step 2 Collect traps, logs, and configurations, and contact Huawei technical support engineers.

Step 3 End.

----End

Related Information

None.

36.4 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.8hwBoardL2mcResLack

Description

MCAST/4/L2MCINDEXISLACK:OID 1.3.6.1.4.1.2011.5.25.227.2.1.8 The l2mc indexresource usage has exceeded [GAUGE]%.(Slot=[OCTET],ResourceType=[INTEGER])

This object indicates that the L2MC index resource usage exceeds the upper threshold.



465

Attribute



Parameters

Name Meaning

OID Object ID.

hwFwdResThreshold Alarm threshold.

Slot Slot ID.

ResourceType Index resource ID.

Impact on the SystemThe alarm does not affect services; however, if the L2MC resource usage still increases, theresource usage may reach 100%. If new L2MC services are configured in this case, the serviceswill be unavailable.

Possible CausesThe L2MC index resource usage exceeds the upper threshold.

Procedure

Step 1 Adjust L2MC resource usage when an alarm is generated.


Step 3 End.

----End


36.5 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.9hwBoardL2mcResLackResume

DescriptionMCAST/4/L2MCINDEXISRESUME:OID 1.3.6.1.4.1.2011.5.25.227.2.1.9 The l2mc indexresource usage has fallen below [GAUGE]%.(Slot=[OCTET],ResourceType=[INTEGER])

The L2MC index resource usage falls below the threshold.



466

Attribute



Parameters

Name Meaning

OID Object ID.


Slot Slot ID.


Impact on the SystemThis alarm does not affect services.

Possible CausesThe L2MC index resource usage falls below the lower threshold.

Procedure


----End


36.6 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.10hwBoardipmcResLack

DescriptionMCAST/4/IPMCINDEXISLACK:OID 1.3.6.1.4.1.2011.5.25.227.2.1.10 The ipmc indexresource usage has exceeded [GAUGE]%.(Slot=[OCTET],ResourceType=[INTEGER])

The IPMC index resource usage exceeds the threshold.



467

Attribute



Parameters

Name Meaning

OID Object ID.


Slot Slot ID.


Impact on the SystemThe alarm does not affect services; however, if the IPMC resource usage still increases, theresource usage may reach 100%. If new IPMC services are configured in this case, the serviceswill be unavailable.

Possible CausesThe IPMC index resource usage exceeds the threshold.

Procedure

Step 1 Adjust IPMC resource usage when an alarm is generated.


Step 3 End.

----End


36.7 L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.11hwBoardipmcResLackResume

DescriptionMCAST/4/IPMCINDEXISRESUME:OID 1.3.6.1.4.1.2011.5.25.227.2.1.11 The ipmc indexresource usage has fallen below [GAUGE]%.(Slot=[OCTET],ResourceType=[INTEGER])

The IPMC index resource usage falls below the threshold.



468

Attribute



Parameters

Name Meaning

OID Object ID.


Slot Slot ID.


Impact on the SystemThis alarm does not affect services.

Possible CausesThe IPMC index resource usage falls below the lower threshold.

Procedure


----End




469

37 L3VPN

About This Chapter

37.1 L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp

37.2 L3VPN_1.3.6.1.2.1.10.166.11.0.2 mplsL3VpnVrfDown

37.3 L3VPN_1.3.6.1.2.1.10.166.11.0.3 mplsL3VpnVrfRouteMidThreshExceeded

37.4 L3VPN_1.3.6.1.2.1.10.166.11.0.4 mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

37.5 L3VPN_1.3.6.1.2.1.10.166.11.0.6 mplsL3VpnNumVrfRouteMaxThreshCleared

37.6 L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 37 L3VPN


470

37.1 L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp

Description

L3VPN/2/L3V_TRAP_VRF_UP:OID [oid] The interface bound to the VPN instance went Up.(VpnInstanceName=[octet], IfIndex=[integer], BindingVpnInstanceName=[octet],IfCurRowStatus=[integer], VRFOperationStatus=[integer], IfName=[octet])

One of the interfaces in the Down state that are bound to VPN instance goes Up.

Attribute


1.3.6.1.2.1.10.166.11.0.1 Major communicationsAlarm(2)

Parameters

Name Meaning


VpnInstanceName Indicates the name of the VPN.


BindingVpnInstanceName Indicates the name of the binding VPN .

IfCurRowStatus Indicates the row status of the interface. Including:

l 1: Activel 2: Not in Servicel 3: Not Readyl 4: Create and Gol 5: Create and Waitl 6: Destroy

VRFOperationStatus Indicates the status of the VRF. Including:

l 1: Upl 2: Down

IfName Indicates the name of the interface.



471


At least one available interface is bound with the VPN instance.

Possible Causes

1. No interface was bound with the VPN instance, and the status of the first interface bound withthe VPN instance changed from Down to Up.

2. One interface was bound with the VPN instance, and the interface status changed from Downto Up.

3. Multiple interfaces were bound with the VPN instance; the status of all the interfaces wasDown, the first interface went Up.

Procedure


----End

Related Information

None

37.2 L3VPN_1.3.6.1.2.1.10.166.11.0.2 mplsL3VpnVrfDown

Description

L3VPN/2/L3V_TRAP_VRF_DOWN: OID [oid] The interface bound to the VPN instance wentDown. (VpnInstanceName=[octet], IfIndex=[integer], BindingVpnInstanceName=[octet],IfCurRowStatus=[integer], OperationStatus=[integer], IfName=[octet])

Of the interfaces that are bound to VPN instance, the last interface in the Up state goes Down.

Attribute



Parameters

Name Meaning





472

Name Meaning


BindingVpnInstanceName Indicates the name of the binding VPN.

IfCurRowStatus Indicates the row status of the interface. Including:

l 1: Activel 2: Not in Servicel 3: Not Readyl 4: Create and Gol 5: Create and Waitl 6: Destroy

OperationStatus Indicates the status of the VRF. Including:

l 1: Upl 2: Down



No available interface is bound with the VPN instance.

Possible Causes

1. One interface was bound with the VPN instance, and the interface status changed from Up toDown.

2. Multiple interfaces were bound with the VPN instance; the status of all the interfaces changedfrom Up to Down; the last interface in the Up state went Down.

3. The last interface with Up state is disassociated from the VPN instance.

Procedure

Step 1 Run the display ip vpn-instance verbose vpn-instance-name command to check whichinterfaces are bound with the VPN instance.

l If no interface is bound with the VPN instance, search the log file and find whether there isa log message containing the keywords "undo ip binding vpn-instance" and generated withthe alarm.

– If so, and the VPN instance should be unbound, the problem is resolved, go to step 6. Ifthe VPN instance cannot be unbound, run the ip binding vpn-instance vpn-instance-name command in the interface view to bound the interface with the VPN instance, andthen run ip address ipv4-address command to configure IP address for the interface.



473

– If the L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp of this VPN instanceappears later, the problem is resolved, go to step 6.

– If not, go to step 5.

– If there is not the relative log, go to step 5.

l If there are some interfaces bound with the VPN instance, go to Step 2.

Step 2 Run the display ip interface brief command to check whether there are one or more interfacesbound with the VPN instance and in Up state.



Step 3 Check whether the interfaces are configured with IP addresses.


l If not, run ip address ipv4-address command to configure IP addresses for the interfaces ifnecessary. Then,



Step 4 Run the display this command in the interface view to check whether the interfaces are shutdown.

l If so, run the undo shutdown command on the interfaces if necessary. Then,



l If all the interfaces are not shut down, go to Step 5.

Step 5 Collect the trap information, log information, and configuration information, and contact Huaweitechnical personnel.

Step 6 End.

----End

Related Information

L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp

37.3 L3VPN_1.3.6.1.2.1.10.166.11.0.3mplsL3VpnVrfRouteMidThreshExceeded

Description

L3VPN/4/L3V_TRAP_MID_EXCEED:OID [oid] The number of routes in the VPN instanceexceeded the middle threshold. (VpnInstanceName=[octet], VpnInstanceRouteCount=[gauge],MidThresholdValue=[gauge])



474

The number of routes contained by the specified VRF exceeds the value indicated bymplsL3VpnVrfMidRouteThreshold.

Attribute


1.3.6.1.2.1.10.166.11.0.3 Warning qualityOfServiceAlarm(3)

Parameters

Name Meaning


VpnInstanceName Indicates the name of a VPN instance.

VpnInstanceRouteCount Indicates the number of existing routes or prefixes.

MidThresholdValue Indicates that the alarm threshold of routes or prefixes.

Impact on the SystemWhen the total number of VPN routes or prefixes exceeds the alarm threshold, routes can stillbe installed to the routing table. That is, the routes are not discarded and traffic is not interruptedfor the moment.

Possible Causes1. The total number of the VPN routes in the VPN routing table exceeds the alarm threshold ofVPN routes specified in the routing-table limit command, and is smaller than the maximumnumber of routes.

2. The total number of the VPN route prefixes in the VPN routing table exceeds the alarmthreshold of VPN route prefixes specified in the prefix limit command, and is smaller than themaximum number of route prefixes.

Procedure

Step 1 Run the display ip routing-table limit vpn-instance vpn-instance-name command to checkwhether the number of routes or prefixes in the VPN instance exceeds the upper limit.

Step 2 Analyze the source of each route and check whether the number of existing routes or prefixesin the VPN instance meets the requirements.l If so, go to Step 4.l If not, go to Step 3.

Step 3 Check whether the number of routes or prefixes still exceeds the alarm threshold after redundantVPN routes are deleted.



475



Step 4 Enter the VPN instance view and run the display this command to view the configuration ofthe routing-table limit command and the prefix limit command. Then, check whether the setalarm threshold of VPN routes is proper.


l If not, run the routing-table limit number { alert-percent | simply-alert } or prefix limitnumber { alert-percent | simply-alert } command to set a proper alarm threshold of routesor prefixes. Then, go to Step 6.


Step 6 End.

----End

Related Information

None.

37.4 L3VPN_1.3.6.1.2.1.10.166.11.0.4mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

Description

L3VPN/2/L3V_TRAP_THRE_EXCEED:OID [oid] The number of routes in the VPN instanceexceeded the maximum value. (VpnInstanceName=[octet], VPNInstanceRouteCount=[gauge],MaxValue=[gauge])

The number of routes contained by the specified VRF exceeds or attempts to exceed themaximum allowed value as indicated by mplsVrfMaxRouteThreshold.

Attribute


1.3.6.1.2.1.10.166.11.0.4 Major qualityOfServiceAlarm(3)

Parameters

Name Meaning


VpnInstanceName Indicates the name of the VPN instance.



476

Name Meaning

VPNInstanceRouteCount Indicates the number of current routes.

MaxValue Indicates that the maximum value of routes or prefixes.


The number of private routes or prefixes exceeds the maximum value, and no routes or prefixescan be added. As a result, routes will be discarded and some traffic cannot be forwarded.

Possible Causes

1. The total number of the VPN routes in the VPN routing table exceeded the upper limit specifiedin the License or exceeded the maximum value specified in the routing-table limit command.

2. The total number of the VPN route prefixes in the VPN routing table exceeded the upper limitspecified in the License or exceeded the maximum value specified in the prefix limit command.

Procedure

Step 1 Run the display ip routing-table limit vpn-instance vpn-instance-name command to checkwhether the number of routes or prefixes in the VPN instance exceeds the upper limit.

Step 2 Analyze the source of each route and check whether the number of existing routes or prefixesin the VPN instance meets the requirements.



Step 3 Check whether the number of routes or prefixes still exceeds the maximum value after redundantVPN routes are deleted.



Step 4 Enter the VPN instance view and run the display this command to view the configuration ofthe routing-table limit number { alert-percent | simply-alert } command and the prefixlimit command. Then, check whether the set maximum value of VPN routes is proper.


l If not, run the routing-table limit number { alert-percent | simply-alert } command or theprefix limit number { alert-percent | simply-alert } command to set a proper maximumvalue of routes or prefixes. Then, go to Step 6.


Step 6 End.

----End



477

Related Information

L3VPN_1.3.6.1.2.1.10.166.11.0.6 mplsL3VpnNumVrfRouteMaxThreshCleared

37.5 L3VPN_1.3.6.1.2.1.10.166.11.0.6mplsL3VpnNumVrfRouteMaxThreshCleared

Description

L3VPN/2/L3V_TRAP_THRE_CLEARED:OID [oid] The number of routes in the VPN instancefell below the maximum value. (VpnInstanceName=[octet], VPNInstanceRouteCount=[gauge],MaxValue=[gauge])

The number of routes contained by the specified VRF exceeds the maximum allowed value asindicated by mplsVrfMaxRouteThreshold and then falls below this value.

Attribute


1.3.6.1.2.1.10.166.11.0.6 Major qualityOfServiceAlarm(3)

Parameters

Name Meaning



VPNInstanceRouteCount Indicates the number of current routes.

MaxValue Indicates that the maximum value of routes or prefixes.


The number of private routes or prefixes falls below the maximum value, and routes can bereceived and sent normally.

Possible Causes

1. The number of VRF routes reached the maximum value, and then it fell below the maximumvalue.

2. The number of VRF prefixes reached the maximum value, and then it fell below the maximumvalue.



478

3. The maximum number of VRF routes increases after the routing-table limit command is runfor the VPN instance routing table.

4. The maximum number of VRF route prefixes increases after the prefix limit command is runfor the VPN instance routing table.

Procedure


----End

Related Information

None.

37.6 L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1hwTnl2VpnTrapEvent

Description

L3VPN/4/L3V_TRAP_TUNNEL_UPDOWN_EVENT:OID [oid] The tunnel up/down event isoccurred. (VpnIndex=[gauge], NextHop=[ipaddr], Ckey=[gauge], TrapType=[gauge])

The status of the tunnel used by a VPN changed.

Attribute



Parameters

Name Meaning


VpnIndex Indicates the index of the VPN instance.

NextHop Indicates the next hop address of the public network.

TrapType Indicates the trap type:l 1: indicates that a tunnel goes Up.l 2: indicates that a tunnel goes Down.



479

Name Meaning

Ckey Indicates the Ckey value, which is used to obtain information about the currentiterated tunnel.

Impact on the SystemThe VPN services of the VPN instance with the specified index will be restored or interrupted.

Possible Causes1. The status of the tunnel currently used by VPN services changed from reachable to unreachableor from unreachable to reachable.

2. During the tunnel switchover for VPN services, the result of tunnel iteration changed fromsuccess (a tunnel is iterated) to failure (a tunnel fails to be iterated); or the opposite.

Procedure

Step 1 Collect trap messages, log messages, and configuration information, and then contact Huaweitechnical personnel.

----End



480

38 LDP

About This Chapter

NOTE

Only the S5700HI, S5710HI, and S5710EI support this alarm.

38.1 LDP_1.3.6.1.2.1.10.166.4.0.1 mplsLdpInitSessionThresholdExceeded

38.2 LDP_1.3.6.1.2.1.10.166.4.0.2 mplsLdpPathVectorLimitMismatch

38.3 LDP_1.3.6.1.2.1.10.166.4.0.3 mplsLdpSessionUp

38.4 LDP_1.3.6.1.2.1.10.166.4.0.4 mplsLdpSessionDown

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 38 LDP


481

38.1 LDP_1.3.6.1.2.1.10.166.4.0.1mplsLdpInitSessionThresholdExceeded

Description

LDP/4/SSNTHRESHOLDEXCEED: OID [oid] The number of failures in LDP sessionnegotiation reached threshold. (LdpId=[OPAQUE], LdpEntityIndex=[GAUGE], Times=[INTEGER])

The value of mplsLdpEntityInitSesThreshold is not 0, and the number of times for sessionnegotiation through Init messages exceeds this threshold.

Attribute


1.3.6.1.2.1.10.166.4.0.1 Warning environmentalAlarm(6)

Parameters

Name Meaning

oid Indicates the number of the MIB object.

LdpId Indicates the local LDP peer ID.

LdpEntityIndex Indicates the index of an LDP entity.

Times Indicates the number of session initialization messages sent.


The session cannot be set up. The original services or newly added ones that depend on thesession are interrupted.

Possible Causes

1. Label advertisement mode changes, and the label advertisement modes are inconsistent onthe two ends of the session. The version does not support the DOD mode. The trap is generatedwhen the peer supports the DOD mode during interworking.

2. The negotiation of the Keepalive period fails. The trap is generated when the Keepalive periodof the peer is 0. In this version, the minimum value of the Keepalive period is set to 30. The trapis generated when the Keepalive period of the peer can be set to 0.

Procedure

Step 1 Check whether the devices at the two ends of the session are Huawei devices.



482



Step 2 In this case, the trap message is not generated. Go to Step 6.

Step 3 Check the configurations of the Huawei devices, and run the display current-configurationconfiguration mpls-ldp command to check whether other configurations exist in the MPLSLDP view.



Step 4 The setup of the session is not affected even if other configurations exist in the MPLS LDP view.Save the configurations, and then go to Step 6.

Step 5 It can be concluded that the fault is caused by the configuration of the peer. In this case, go toStep 7.


Step 7 Contact the technical personnel of the peer vendor, and then go to Step 8.

Step 8 End.

----End

Related Information

None

38.2 LDP_1.3.6.1.2.1.10.166.4.0.2mplsLdpPathVectorLimitMismatch

Description

LDP/4/PVLIMITMISMATCH:OID [oid] PVL mismatch between entities. (PVLimitValue=[threshold])

The value of mplsLdpEntityPathVectorLimit is different from the value of themplsLdpPeerPathVectorLimit.

Attribute





483

Parameters

Name Meaning


PVLimitValue Indicates the threshold of the path vector.


Session negotiation through Init messages failed and the session cannot be set up.

Possible Causes

The set versions were different.

Procedure

l Collect the trap information, log information, and configuration of the switch, and contactHuawei technical personnel.

----End

Related Information

None

38.3 LDP_1.3.6.1.2.1.10.166.4.0.3 mplsLdpSessionUp

Description

LDP/2/SESSIONUP: OID [OID] The session went Up. (LdpId=[OPAQUE], LdpEntityIndex=[GAUGE], PeerLdpId=[OPAQUE], PeerLdpId=[OPAQUE], IfIndex=[INTEGER],SessionState=[INTEGER], DiscontinuityTime=[TIMETICK], UnknownMesTypeErrors=[COUNTER], UnknownTlvErrors=[COUNTER], DownReason=[INTEGER], IfName=[STRING])

The status of the LDP session was Up, and the LSPs maintained by the session were set up.

Attribute





484

Parameters

Name Meaning


LdpId Indicates the LSR ID of the local end and Label Space.

LdpEntityIndex Indicates the index of the LDP interface.

PeerLdpId Indicates the LSR ID of the neighbor and Label Space. Thisparameter, LdpId, and LdpEntityIndex are indexes forSessionState, DiscontinuityTime, UnknownMesTypeErrors, andUnknownTlvErrors.

PeerLdpId Indicates the LSR ID of the neighbor and Label Space. Thisparameter is the index for DownReason.

IfIndex Indicates the interface index corresponding to the session.

SessionState Indicates the session status.

DiscontinuityTime Indicates the duration when the session is set up, in milliseconds.

UnknownMesTypeErrors Indicates the number of unknown error messages and error cods.

UnknownTlvErrors Indicates the number of unknown error TLVs and error codes.

DownReason Indicates the cause that the session goes Down.

IfName Indicates the interface name corresponding to the session.



Possible Causes

1. The LDP sessions were configured.

2. New routes were installed.

3. The link state recovered.

Procedure


----End

Related Information

None

38.4 LDP_1.3.6.1.2.1.10.166.4.0.4 mplsLdpSessionDown



485

Description

LDP/2/SESSIONDOWN: OID [OID] The session went Down. (LdpId=[OPAQUE],LdpEntityIndex=[GAUGE], PeerLdpId=[OPAQUE], PeerLdpId=[OPAQUE], IfIndex=[INTEGER], SessionState=[INTEGER], DiscontinuityTime=[TIMETICK],UnknownMesTypeErrors=[COUNTER], UnknownTlvErrors=[COUNTER], DownReason=[INTEGER], IfName=[STRING])

The status of the LDP session was Down, and LSPs maintained by the session were deleted.

Attribute



Parameters

Name Meaning


LdpId Indicates the LSR ID of the local end and Label Space.

LdpEntityIndex Indicates the index of the LDP interface.

PeerLdpId Indicates the LSR ID of the neighbor and Label Space. Thisparameter, LdpId, and LdpEntityIndex are indexes forSessionState, DiscontinuityTime, UnknownMesTypeErrors, andUnknownTlvErrors.

PeerLdpId Indicates the LSR ID of the neighbor and Label Space. Thisparameter is the index for DownReason.

IfIndex Indicates the interface index corresponding to the session.

SessionState Indicates the session status.

DiscontinuityTime Indicates the duration when the session is set up, in milliseconds.

UnknownMesTypeErrors Indicates the number of unknown error messages codes.

UnknownTlvErrors Indicates the number of unknown error TLVs codes.

DownReason Indicates the cause that the session goes Down.

IfName Indicates the interface name corresponding to the session.


All the services based on this LDP session will be interrupted.

Possible Causes

1. Hello hold timer expired.



486

2. The session timer expired.

3. LDP was reset.

4. LDP was diabled.

5. MPLS was diabled.

6. The remote neighbor was deleted.

7. The GR configuration was modified.

8. The GR timer was changed.

9. The Keepalive hold timer was changed.

10. The MD5 configuration was changed.

11. The session role was changed.

12. The configuration of LDP MTU Signaling was changed.

13. The transport address was changed.

14. The LSR ID was changed.

15. A Notification message was received.

16. The transport addresses did not match.

17. The protocol entered the GR state.

18. The interface status was changed.

19. The TCP connection failed.

20. Other reasons.

Procedure

Step 1 Run the display mpls ldp session peer-id command to check the LDP session status. Ensurethat the value of the parameter peer-id is the same as the value of the PeerLdpId field in thetrap information.

l If the value of the Status field in the command output is Operational, go to Step 2.

l If no information is displayed or the value of the Status field in the command output is notOperational, go to Step 3.

Step 2 If the LDP session is already re-established, it indicates that the session may flap. In this case,services may have been interrupted. For further analysis based on the log information, go to Step19.

Step 3 Run the display mpls ldp peer peer-id command to check whether there is information aboutthe peer. Ensure that the value of the parameter peer-id is the same as the value of thePeerLdpId field in the trap information.

l If the command output is displayed, go to Step 4.

l If no information is displayed, check whether the IfName field in the trap information is null.




487


Step 4 Run the display mpls ldp session peer-id command repeatedly to check whether the LDP sessionflaps. Ensure that the value of the parameter peer-id is the same as the value of thePeerLdpId field in the trap information. If the Status field in the command output is sometimesdisplayed as Operational and sometimes displayed as Nonexistent, or no information isdisplayed, it indicates that the LDP session flaps.



Step 5 If the LDP session flaps, check whether the configurations are modified frequently.



Step 6 Stop modifying the configurations. Two minutes later, go to Step 18.

Step 7 Run the display mpls ldp peer peer-id command to check the TransportAddress field in thecommand output. Ensure that the value of the parameter peer-id is the same as the PeerLdpIdfield in the trap information. Then, run the display ip routing-table ip-address command tocheck whether information about the route to the peer exists. Ensure that the value of theparameter ip-address is the same as the value of the TransportAddress field in the displaympls ldp peer peer-id command output.



Step 8 Check whether the IGP route is correctly configured.

l If OSPF is used as an IGP, run the display current-configuration configuration ospfcommand in the OSPF view to check whether OSPF has advertised the routes destined forthe addresses of loopback interfaces and corresponding interfaces.



l If IS-IS is used as an IGP, run the display this command in the loopback interface view andthe corresponding interface view to check whether IS-IS is enabled.



Step 9 Restore the routing protocol configurations, and then check whether the configurations arenormal according to Step 8.



Step 10 Check whether the TCP status is normal. Run the display mpls ldp peer peer-id command tocheck the Peer Transport Address field (remarked as S) and the Peer Discovery Source field.Ensure that the value of the parameter peer-id is the same as the value of the PeerLdpId fieldin the trap information. Then, run the display mpls ldp interface interface-type interface-number command to check the Transport Address field (remarked as D). Ensure that the valueof the parameter interface-type interface-number is the same as the value of the Peer DiscoverySource field in the display mpls ldp peer peer-id command output. Run the display tcpstatus command to check whether the Local Add:port field is displayed as D and whether the



488

Foreign Add:port field is displayed as S. If the Local Add:port field is displayed as D and theForeign Add:port field is displayed as S, it indicates that the TCP status is normal.l If so, go to Step 18.l If not, go to Step 11.

Step 11 Run the ping -a source-ip -c destination-address command for more than 100 times to checkwhether packet loss occurs. Ensure that the parameter source-ip is the same as the value of thePeer Transport Address field in Step 10 and the value of the parameter destination-address isthe same as the value of the Transport Address field in Step 10.l If packet loss occurs, go to Step 12.l If packet loss does not occur, go to Step 19.

Step 12 If the link is unstable, it indicates that the line is abnormal or there is heavy traffic on the link.Then, check the link and ensure that the link is stable, and then go to Step 18.

Step 13 Run the display mpls ldp interface interface-type interface-number command on both endsof the link to check the interface status. Ensure that the value of the parameter interface-typeinterface-number is the same as the value of the Peer Discovery Source field in Step 10.l If the corresponding interface exists, but the Status field is displayed as Inactive, go to Step

16.l If the corresponding interface does not exist, go to Step 14.

Step 14 Run the display this command in the interface view to check whether LDP is enabled.l If mpls ldp is displayed in the command output, go to Step 19.l If mpls ldp is not displayed in the command output, go to Step 15.

Step 15 Run the mpls ldp command in the interface view, and then go to Step 18.

Step 16 Run the display this command in the interface view to check whether the interface is shut down.l If shutdown is displayed in the command output, go to Step 17.l If shutdown is not displayed in the command output, go to Step 19.

Step 17 Run the undo shutdown command in the interface view, and then go to Step 18.

Step 18 If the trap LDP_1.3.6.1.2.1.10.166.4.0.3 mplsLdpSessionUp is displayed, it indicates that thetrap LDP_1.3.6.1.2.1.10.166.4.0.4 mplsLdpSessionDown is cleared. Then, go to Step 20.


Step 20 End.

----End




489

39 LSPM

About This Chapter

NOTE


39.1 LSPM_1.3.6.1.2.1.10.166.2.0.1 mplsXCUp

39.2 LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown

39.3 LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp

39.4 LSPM_1.3.6.1.2.1.10.166.3.0.2 mplsTunnelDown

39.5 LSPM_1.3.6.1.2.1.10.166.3.0.3 mplsTunnelRerouted

39.6 LSPM_1.3.6.1.2.1.10.166.3.0.4 mplsTunnelReoptimized

39.7 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.1 hwMplsStaticLSPUp

39.8 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLSPDown

39.9 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.3 hwMplsStaticCRLSPUp

39.10 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.4 hwMplsStaticCRLSPDown

39.11 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.5 hwMplsTeFrrProtAval

39.12 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.6 hwMplsTeFrrProtNotAval

39.13 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.7 hwMplsTeFrrSwitch

39.14 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.8 hwMplsTeFrrResume

39.15 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.9 hwMplsTunnelHSBSwitch

39.16 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.10 hwMplsTunnelHSBResume

39.17 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.11 hwMplsTunnelOBSwitch

39.18 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.12 hwMplsTunnelOBResume

39.19 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.15 hwMplsTunnelChangeBw

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 39 LSPM


490

39.20 LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.1 hwMplsLdpVirtualTunnelUp

39.21 LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.2 hwMplsLdpVirtualTunnelDown

39.22 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.46 hwMplsTunnelPrimaryUp

39.23 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryDown

39.24 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp

39.25 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.49 hwMplsTunnelHotstandbyDown

39.26 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp

39.27 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.51 hwMplsTunnelOrdinaryDown

39.28 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52 hwMplsTunnelBesteffortUp

39.29 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.53 hwMplsTunnelBesteffortDown

39.30 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.54 hwMplsTeAutoTunnelDownClear

39.31 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.55 hwMplsTeAutoTunnelPrimaryDownClear

39.32 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.56 hwMplsTunnelBBSwitch

39.33 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.57 hwMplsTunnelBBResume

39.34 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.58 hwMplsExtTunnelDown

39.35 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59 hwMplsExtTunnelDownClear

39.36 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.62 hwMplsTunnelDelete

39.37 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.63 hwMplsLspThresholdExceed

39.38 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.64 hwMplsLspThresholdExceedClear

39.39 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.65 hwMplsLspTotalCountExceed

39.40 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.66 hwMplsLspTotalCountExceedClear

39.41 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.67 hwMplsDynamicLabelThresholdExceed

39.42 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.68 hwMplsDynamicLabelThresholdExceedClear

39.43 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.69 hwMplsDynamicLabelTotalCountExceed

39.44 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70 hwMplsDynamicLabelTotalCountExceedClear



491

39.1 LSPM_1.3.6.1.2.1.10.166.2.0.1 mplsXCUp

Description

LSPM/4/MPLSXCUP:OID [oid] LSP went Up. (BeginLspIndex=[octet].[octet].[octet],EndLspIndex=[octet].[octet].[octet])

A trap was generated when the LSP went Up.

Attribute


1.3.6.1.2.1.10.166.2.0.1 Warning communicationsAlarm(2)

Parameters

Name Meaning


BeginLspIndex Indicates the index of the starting LSP, which is expressed in the format of[index of the starting LSP].[index of the inbound interface on the startingLSP].[index of the outbound interface on the starting LSP].

EndLspIndex Indicates the index of the ending LSP, which is expressed in the format of[index of the ending LSP].[index of the inbound interface on the ending LSP].[index of the outbound interface on the ending LSP].



Possible Causes

The LSP was created successfully.

Procedure


----End

Related Information

LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown



492

39.2 LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown

Description

LSPM/4/MPLSXCDOWN:OID [oid] LSP went Down. (BeginLspIndex=[octet].[octet].[octet],EndLspIndex=[octet].[octet].[octet])

A trap was generated when the LSP went Down.

Attribute



Parameters

Name Meaning


BeginLspIndex Indicates the index of the starting LSP, which is expressed in the format of[index of the starting LSP].[index of the inbound interface on the startingLSP].[index of the outbound interface on the starting LSP].

EndLspIndex Indicates the index of the ending LSP, which is expressed in the format of[index of the ending LSP].[index of the inbound interface on the ending LSP].[index of the outbound interface on the ending LSP].


1. If the protection function, such as FRR, is configured, services will not be affected.

2. If the protection function is not configured, all the services to be forwarded through the LSPwill be interrupted.

Possible Causesl The interface went Down.

l LDP LSPs went Down.

l Static LSPs went Down.

l In the case that the LDP LSP or BGP LSP was set Up, routes changed; or, in the case thatthe static LSP was bound to the tunnel, the next hop configured for the static LSP wasinconsistent with the next hop in the routing table after routes changed.

l The link was faulty.



493

Procedure

Step 1 If the snmp-agent trap enable feature-name mpls_lspmtrap-name is run and the trapfunctions indicating the status of LSPs are thus enabled in the LSPM, you can check the trapsto obtain the types of the LSPs that go Down. If no trap functions indicating the status of LSPsare enabled in the LSPM, you can check the values of the BeginLspIndex and EndLspIndexfields in the traps to obtain the types of the LSPs that go Down.l If static LSPs went Down, refer to the solution described in

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLspDown. Then, go to Step 3.l If the fault persists, go to Step 2.


Step 3 End.

----End

Related InformationLSPM_1.3.6.1.2.1.10.166.2.0.1 mplsXCUp

39.3 LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp

DescriptionLSPM/2/MPLSTUNNELUP:OID [oid] Tunnel Changes to Up.(SessionTunnelId=[integer],LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], OutIfIndex=[integer],mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer], mplsTunnelIfName=[octet], OutIfName=[octet], mplsTunnelDownReason=[integer]).

A trap was generated when a tunnel was established successfully and was Up.

Attribute



Parameters

Name Meaning


SessionTunnelId Indicates the ID of the tunnel.

LocalLspId indicates the LSP ID of a session.



494

Name Meaning

IngressLsrId indicates the LSR ID of the ingress on the tunnel.

EgressLsrId indicates the LSR ID of the egress on the tunnel.

OutIfIndex indicates the outgoing interface index of the ingress of the LSP thatgoes Up.

mplsTunnelAdminStatus indicates the management status of the tunnel. 1: Up 2: Down

mplsTunnelOperStatus indicates the operation status of the tunnel: 1: Up 2: Down

mplsTunnelIfName indicates the name of a tunnel.

OutIfName indicates the name of the outgoing interface on the ingress of theLSP that goes Up.

mplsTunnelDownReason indicates the reason of Tunnel down.l 1:otherl 2:staticLspDownl 3:staticCrlspDownl 4:outIfDownl 5:resourcePreemptedl 6:rsvpMessageTimeoutl 7:rsvpNbrLostl 8:bypassTunnelDownOrUnbindedl 100:clear


Possible CausesThe tunnel was created successfully.


----End

Related InformationLSPM_1.3.6.1.2.1.10.166.3.0.2 mplsTunnelDown



495

39.4 LSPM_1.3.6.1.2.1.10.166.3.0.2 mplsTunnelDown

Description

LSPM/2/MPLSTUNNELDOWN:OID [oid] Tunnel Changes to Down.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], OutIfIndex=[integer], mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer],mplsTunnelIfName=[octet], OutIfName=[octet], mplsTunnelDownReason=[integer])

A trap was generated when the current tunnel became faulty and went Down.

Attribute



Parameters

Name Meaning



LocalLspId Indicates the LSP ID of a session.

IngressLsrId Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId Indicates the LSR ID of the egress on the tunnel.

OutIfIndex Indicates the outgoing interface index of the ingress of the LSP thatgoes Down.

mplsTunnelAdminStatus Indicates the management status of the tunnel.l 1: Upl 2: Down

mplsTunnelOperStatus indicates the operation status of the tunnel:l 1: Upl 2: Down




496

Name Meaning

OutIfName indicates the name of the outgoing interface on the ingress of theLSP that goes Down.

mplsTunnelDownReason indicates the reason of Tunnel down.l 1:otherl 2:staticLspDownl 3:staticCrlspDownl 4:outIfDownl 5:resourcePreemptedl 6:rsvpMessageTimeoutl 7:rsvpNbrLostl 8:bypassTunnelDownOrUnbindedl 100:clear

Impact on the SystemThe service traffic to be forwarded through the tunnel will be interrupted.

Possible Causes1. The interface was Down.

2. In the case that the static LSP was bound to the tunnel, the next hop configured for the staticLSP was inconsistent with the next hop in the routing table after routes changed.

3. The link was faulty.

Procedure

Step 1 Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, thenode that generates the trap) to check the configurations of the tunnel. View the Tunnel StateDesc field to check whether the tunnel is in the Down state Then, run the display mpls te tunnel-interface last-error command to view the prompt.l In the case of the following error prompts, do as required:

– If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that theingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.

– If the error prompt is "Trigger Rsvp failed", go to Step 2.

– If the error prompt is "One LSP is deleted at smooth period", go to Step 6.

– If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.

– For other types of errors, go to Step 6.l If there is no error prompt, go to Step 2.

Step 2 Run the ping command on the ingress to check whether the destination IP address of the tunnelcan be pinged.



497

l If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnelcan be pinged, and then check whether the alarmLSPM_1.3.6.1.2.1.10.166.3.0.1mplsTunnelUp is generated.



l If the ping is successful, go to Step 3.

Step 3 Run the display this command in the MPLS view of the ingress to check whether the mpls tecspf command is configured, that is, to check whether the CSPF is enabled.



Step 4 Run the display mpls te cspf destination command on the ingress to check whether a path thatmeets the bandwidth constraints is available. If so, the path of the TE tunnel is displayed,indicating that CSPF calculation is successful. If not, null is displayed, indicating that CSPFcalculation fails.

l If the path is successfully calculated, run the display current-configuration interfaceinterface-type interface-number command on the ingress to check the tunnel configurations,including the primary tunnel, protection tunnel, and the protection interface. Check whetherthe mpls te auto-frr command is configured in the MPLS view. If so, it indicates that AutoFRR is enabled. In this case, you can check the primary tunnel. If not, check whether thempls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel are configured toidentify the primary and backup tunnels.

After the primary and backup tunnels are checked, you can check the explicit-path commandto verify whether the explicit path is configured; check the mpls te affinity propertycommand to verify whether the affinity property is configured; check the mpls tebandwidth command to verify whether the bandwidth is configured.

Run the display mpls te cspf destination command and configure the parameters ofconstraints one by one, including the priority (priority setup-priority), bandwidth(bandwidth), explicit path (explicit-path path-name), affinity property (affinityproperties), and hop limit (hop-limit hop-limit-number), and you can check whether the paththat meets the constraints is available. If so, the path of the TE tunnel is displayed, indicatingthat CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculationfails.

1. If the explicit path fails to be calculated, check whether the interfaces along the explicitpath are in the Up state and are enabled with MPLS and MPLS TE. If the explicit pathis successfully calculated, check whether path calculation according to the affinityproperty and bandwidth is consistent with the explicit path by running the display mplste cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.

2. If CSPF path calculation fails after affinity attribute is configured, run the mpls teaffinity property command in the tunnel view to modify the affinity attribute of thetunnel, or run the mpls te link administrative group on the interfaces along the tunnelto modify the administrative group attribute of the link.

3. If CSPF path calculation fails because of other constraints, go to Step 6.

Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp isgenerated.



498



l If CSPF path calculation fails, go to Step 5.

Step 5 Run the display explicit-path command to check the interfaces along the tunnel. Then, run thedisplay this command in the interface view of each interface of the tunnel to check whether theinterface is enabled with MPLS, MPLS TE, and RSVP-TE.

l If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-tecommands in the view of the interface.

l If any interface along the tunnel is not in Up state, restart the interface. That is, run theshutdown and then undo shutdown commands in the interface view, or run the restartcommand in the interface view, or run the command in the interface view.

Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.




Step 7 End.

----End

Related Information

LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp

39.5 LSPM_1.3.6.1.2.1.10.166.3.0.3 mplsTunnelRerouted

Description

LSPM/4/MPLSTUNNELREROUTED: OID [oid] Tunnel Re-routed.(SessionTunnelId=[integer])

A trap was generated when FRR switchover or FRR switchback was performed.

Attribute



Parameters

Name Meaning




499

Name Meaning




Possible Causes

1. FRR switchover was performed.

2. FRR switchback was performed.

Procedure


----End

Related Information

None

39.6 LSPM_1.3.6.1.2.1.10.166.3.0.4 mplsTunnelReoptimized

Description

LSPM/4/MPLSTUNNELREOP: OID [oid] Tunnel Re-Optimized.(SessionTunnelId=[integer])

A trap was generated when the route of the tunnel was re-optimized successfully.

Attribute



Parameters

Name Meaning







500

Possible Causes

The tunnel succeeded in re-selecting the optimal route.

Procedure


----End

Related Information

None

39.7 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.1hwMplsStaticLSPUp

Description

LSPM/2/STATICLSPUP:OID [oid] Static LSP went Up. (LspIndex=[octet], InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], LspName=[octet], LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static LSP was in the Up state.

Attribute


1.3.6.1.4.1.2011.5.25.121.2.1.1 Major environmentalAlarm(6)

Parameters

Name Meaning

oid Indicates the ID of the corresponding trap.

LspIndex Indicates the index of the LSP.

InSegmentIndex Indicates the inSegment index of a static LSP.

OutSegmentIndex Indicates the outSegment index of a static LSP.

OutIfIndex Indicates the outbound interface index of a static LSP.

LspName Indicates the name of a static LSP.

LspStatus Indicates the status of a static LSP.

OutIfName Indicates the outbound interface name of a static LSP.

InIfIndex Indicates the inbound interface index of a static LSP.



501

Name Meaning

InIfName Indicates the inbound interface name of a static LSP.

DownReason Indicates the reason that the static LSP down.



Possible Causes

1. The interface was Up.

2. The next hop configured for the static LSP was consistent with the next hop in the routingtable after routes changed.

3. The link was recovered or the new static LSPs were configured.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLspDown

39.8 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2hwMplsStaticLSPDown

Description

LSPM/2/STATICLSPDOWN: OID [oid] Static LSP went Down. (LspIndex=[octet],InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], lspName=[octet],LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static LSP was in the Down state.

Attribute





502

Parameters

Name Meaning



InSegmentIndex Indicates the inSegment index of a static LSP.

OutSegmentIndex Indicates the outSegment index of a static LSP.

OutIfIndex Indicates the outbound interface index of a static LSP.

lspName Indicates the name of a static LSP.

LspStatus Indicates the status of a static LSP.

OutIfName Indicates the outbound interface name of a static LSP.

InIfIndex Indicates the inbound interface index of a static LSP.

InIfName Indicates the inbound interface name of a static LSP.


Impact on the SystemIf there is some service using this static LSP, the service is interrupted. If there is not any serviceusing this static LSP, there is no impact.

Possible Causes1. The interface was Down.

2. The next hop configured for the static LSP was inconsistent with the next hop in the routingtable after routes changed.

3. The link was damaged.

Procedure

Step 1 Run the display mpls interface. If the trap is generated on the ingress of static LSPs, you needto check the information about only the outbound interface; if the trap is generated on the egressof static LSPs, you need to check the information about only the inbound interface; if the trapis generated on the transit of static LSPs, you need to check the information about both theinbound interface and the outbound interface. You need to check whether the correspondinginterface is displayed in the command output, and whether the Status field of the interface is Up.l If the interface status is not Up, check the interface.l If the corresponding interface is not displayed in the command output, it indicates that MPLS

is not enabled on the interface. In this case, you need to enable MPLS on the interface. Then,check whether the trap is cleared.


– If not, go to Step 2.l If the trap is generated on the ingress of static LSPs, go to Step 2.



503

l If the trap is generated on the egress or transit of static LSPs, go to Step 4.

Step 2 Run the display ip routing-table ip-address mask command to check the routing information.Check whether the configured destination addresses, masks, outbound interfaces, and next hopsof static LSPs are the same as those in the routing information. Note that if a static LSP isconfigured by specifying the outbound interface, the address of the outbound interface is usedas the next hop. This configuration is used only in a small number of scenarios.


l If not, check the configuration of the static LSP route on the ingress and make it strictly matchwith the route in the RM. Then, check whether the trap is cleared.



Step 3 If the ingress is bound to the tunnel, run the display mpls interface command to check whetherthe TE Attr field is En. If not, it indicates that MPLS TE is not enabled on the interface. Run thedisplay current-configuration interface interface-type interface-number command to checkwhether the corresponding tunnel is correctly configured.

l If the MPLS TE is not enabled, enable MPLS TE on the interface.

l Run the display current-configuration interface interface-type interface-numbercommand to check whether the corresponding tunnel is correctly configured.

– If the tunnel is not consistent with the destination address of the static LSP, you need toenter the corresponding tunnel view and run the destination command to modify thedestination address of the tunnel.

– After modifying the configuration of the tunnel, run the mpls te commit command tocommit the modification.

– If the signaling mode is not static, run the mpls te signal-protocol static command tomodify the signaling mode of the tunnel.

If neither preceding operations can locate the fault, go to Step 4.


Step 5 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.1 hwMplsStaticLspUp

39.9 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.3hwMplsStaticCRLSPUp

Description

LSPM/2/STATICCRLSPUP: OID [oid] Static CR-LSP went Up. (LspIndex=[octet],InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], LspName=[octet],



504

LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static CR-LSP was in the Up state.

Attribute



Parameters

Name Meaning



InSegmentIndex Indicates the inSegment index of an Up static LSP.

OutSegmentIndex Indicates the outSegment index of an Up static LSP.

OutIfIndex Indicates the outbound interface index of an Up static LSP.

LspName Indicates the name of an Up static LSP.

LspStatus Indicates the status of an Up static LSP.

OutIfName Indicates the outbound interface name of an Up static LSP.

InIfIndex Indicates the inbound interface index of an Up static LSP.

InIfName Indicates the inbound interface name of an Up static LSP.



Possible Causes1. The interface was Up.

2. The link was recovered or the new static CR-LSPs were configured.


----End

Related InformationLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.4 hwMplsStaticCRLspDown



505

39.10 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.4hwMplsStaticCRLSPDown

Description

LSPM/2/STATICCRLSPDOWN: OID [oid] Static CR-LSP went Down. (LspIndex=[octet],InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], LspName=[octet],LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static CR-LSP was in the Down state.

Attribute



Parameters

Name Meaning



InSegmentIndex Indicates the inSegment index of a static CR-LSP.

OutSegmentIndex Indicates the outSegment index of a static CR-LSP.

OutIfIndex Indicates the outbound interface index of a static CR-LSP.

LspName Indicates the name of a static CR-LSP.

LspStatus Indicates the status of a static CR-LSP.

OutIfName Indicates the outbound interface name of a static CR-LSP.

InIfIndex Indicates the inbound interface index of a static CR-LSP.

InIfName Indicates the inbound interface name a static CR-LSP.

DownReason Indicates the reason that the static CR-LSP down.


If there is some service using the tunnel, the service is interrupted. If there is a backup path isused to protect the tunnel, the flow of the service is changed to the backup path. If there is notany service using the tunnel, there is no impact.



506

Possible Causes

1. The interface was Down.

2. The link was damaged.

Procedure

Step 1 Run the display mpls interface command. If the trap is generated on the ingress of static CR-LSPs, you need to check the information about only the outbound interface; if the trap isgenerated on the egress of static CR-LSPs, you need to check the information about only theinbound interface; if the trap is generated on the transit of static LSPs, you need to check theinformation about the outbound interface and inbound interface. You need to check whether thecorresponding interface is displayed in the command output, whether the Status field of theinterface is Up, and whether the TE Attr field is En.

l If the interface status is not Up, check the interface.

l If the MPLS or MPLS TE is not enabled, configure this function.

l If the trap is generated on the ingress, egress, or a transit node, go to Step 2.

Step 2 Run the display current-configuration interface tunnel interface-number command on theingress to check whether the corresponding tunnel is correctly configured.

l If the tunnel is not consistent with the destination address of the static CR-LSP, you need toenter the corresponding tunnel view and run the destination command to modify thedestination address of the tunnel.

l If the signaling mode is not cr-static, run the mpls te signal-protocol cr-static command tomodify the signaling mode of the tunnel.

l After modifying the configuration of the tunnel, run the mpls te commit command to committhe modification.

l If neither preceding operations can locate the fault, go to Step 3.

Step 3 If the static CR-LSP is configured with the bandwidth attribute, run the display current-configuration interface interface-number command to check the maximal bandwidth and themaximal reservable bandwidth on the outbound interface.

l If neither preceding operations can locate the fault, go to Step 4.

l If the available bandwidth of the outgoing interface is smaller than the bandwidth requiredby the static CR-LSP, you need to increase the bandwidth of the outgoing interface.

l After modifying the configuration of the tunnel, run the mpls te commit command to committhe modification.


Step 5 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.3 hwMplsStaticCRLspUp



507

39.11 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.5hwMplsTeFrrProtAval

Description

LSPM/2/HWFRRPROTAVAL:OID [oid] The primary Tunnel has been protected by bypassTunnel.(primary Tunnel index=[integer].[integer].[integer].[integer], bypass Tunnel index=[integer], inner label=[integer])

The trap message was sent when the bypass tunnel was bound to the primary tunnel.

Attribute



Parameters

Name Meaning


primary Tunnel index Indicates the index of the main tunnel.

bypass Tunnel index Indicates the index of the bypass tunnel.

inner label Indicates the inner label.



Possible Causes

The bypass tunnel was successfully bound to the primary tunnel.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.6 hwMplsTeFrrProtNotAval



508

39.12 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.6hwMplsTeFrrProtNotAval

Description

LSPM/2/HWFRRPROTNOTAVAL:OID [oid] The primary Tunnel has been unbound bybypass Tunnel.(primary Tunnel index=[integer1].[integer2].[integer3].[integer4], bypassTunnel index=[integer5])

The trap message was sent when the binding between the primary tunnel and the bypass tunnelwas deleted.

Attribute



Parameters

Name Meaning


primary Tunnel index Indicates the index of the main tunnel.

bypass Tunnel index Indicates the index of the bypass tunnel.


The binding between the primary tunnel and the bypass tunnel is deleted. This causes trafficinterruption once the working tunnel goes down.

Possible Causes

1. Configurations changed.

2. The protected tunnel went Down.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.5 hwMplsTeFrrProtAval



509

39.13 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.7hwMplsTeFrrSwitch

Description

LSPM/3/MPLSTEFRRSWITCH:OID [oid] Tunnel switches.(SessionTunnelId=[integer])

The trap message was output when the primary tunnel was Down and the traffic was switchedto the bypass tunnel.

Attribute



Parameters

Name Meaning





Possible Causes

The node or the link protected by the bypass tunnel was Down.

Procedure

Step 1 Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, thenode that generates the trap) to check the configurations of the tunnel. View the Tunnel StateDesc field to check whether the tunnel is in the Down state Then, run the display mpls te tunnel-interface last-error command to view the prompt.

l In the case of the following error prompts, do as required:







510


Step 2 Run the ping command on the ingress to check whether the destination IP address of the tunnelcan be pinged.l If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel

can be pinged, and then check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1mplsTunnelUp is generated.


– If not, go to Step 3.l If the ping is successful, go to Step 3.

Step 3 Run the display this command in the MPLS view of the ingress to check whether the mpls tecspf command is configured, that is, to check whether the CSPF is enabled.l If so, go to Step 4.l If not, go to Step 5.

Step 4 Run the display mpls te cspf destination command on the ingress to check whether a path thatmeets the constraints is available. If so, the path of the TE tunnel is displayed, indicating thatCSPF calculation is successful. If not, null is displayed, indicating that CSPF calculation fails.l If the path is successfully calculated, run the display current-configuration interface

interface-type interface-number command on the ingress to check the tunnel configurations,including the primary tunnel, protection tunnel, and the protection interface. Check whetherthe mpls te auto-frr command is configured in the MPLS view. If so, it indicates that AutoFRR is enabled. In this case, you can check the primary tunnel. If not, check whether thempls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel are configured toidentify the primary and backup tunnels.After the primary and backup tunnels are checked, you can check the explicit-path commandto verify whether the explicit path is configured; check the mpls te affinity propertycommand to verify whether the affinity property is configured.Run the display mpls te cspf destination command and configure the parameters ofconstraints one by one, including the priority (priority setup-priority), bandwidth(bandwidth), explicit path (explicit-path path-name), affinity property (affinityproperties), and hop limit (hop-limit hop-limit-number), and you can check whether the paththat meets the constraints is available. If so, the path of the TE tunnel is displayed, indicatingthat CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculationfails.


2. If CSPF path calculation fails after affinity property is configured, run the mpls teaffinity property command in the tunnel view to modify the affinity property of thetunnel, or run the mpls te link administrative group on the interfaces along the tunnelto modify the administrative group property of the link.




511

Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp isgenerated.






l If any interface along the tunnel is not in Up state, restart the interface. That is, run theshutdown and then undo shutdown commands in the interface view, or run the restartcommand in the interface view.





Step 7 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.8 hwMplsTeFrrResume

39.14 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.8hwMplsTeFrrResume

Description

LSPM/3/MPLSTEFRRRESUME:OID [oid] Tunnel resumes.(SessionTunnelId=[integer])

The trap message was output when the primary tunnel was recovered and the traffic was switchedback from the bypass tunnel.

Attribute





512

Parameters

Name Meaning




Possible CausesThe status of the node or the link protected by the bypass tunnel went to Up.


----End

Related InformationLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.7 hwMplsTeFrrSwitch

39.15 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.9hwMplsTunnelHSBSwitch

DescriptionLSPM/3/MPLSTUNNELHSBSWITCH:OID [oid] Main LSP of Tunnel switches to back upLSP in HSB.(SessionTunnelId=[integer])

The trap message was output when the primary CR-LSP went Down and traffic was switchedto a hot-standby CR-LSP.

Attribute





513

Parameters

Name Meaning




Possible CausesThe primary LSP was Down and the backup LSP was in use. The backup mode was HSB.

Procedure



– If the error prompt is "Trigger Rsvp failed", go to Step 2.– If the error prompt is "One LSP is deleted at smooth period", go to Step 6.– If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.– For other types of errors, go to Step 6.

l If there is no error prompt, go to Step 2.


can be pinged, and then check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1mplsTunnelUp is generated.– If so, go to Step 7.– If not, go to Step 3.



Step 4 Run the display mpls te cspf destination command on the ingress to check whether a path thatmeets the constraints is available. If so, the path of the TE tunnel is displayed, indicating thatCSPF calculation is successful. If not, null is displayed, indicating that CSPF calculation fails.



514

l If the path is successfully calculated, run the display current-configuration interfaceinterface-type interface-number command on the ingress to check the tunnel configurations,including the primary tunnel, protection tunnel, and the protection interface. Check whetherthe mpls te auto-frr command is configured in the MPLS view. If so, it indicates that AutoFRR is enabled. In this case, you can check the primary tunnel. If not, check whether thempls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel are configured toidentify the primary and backup tunnels.After the primary and backup tunnels are checked, you can check the explicit-path commandto verify whether the explicit path is configured; check the mpls te affinity propertycommand to verify whether the affinity property is configured.Run the display mpls te cspf destination command and configure the parameters ofconstraints one by one, including the priority (priority setup-priority), bandwidth(bandwidth), explicit path (explicit-path path-name), affinity property (affinityproperties), and hop limit (hop-limit hop-limit-number), and you can check whether the paththat meets the constraints is available. If so, the path of the TE tunnel is displayed, indicatingthat CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculationfails.




Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUpis generated.

– If so, go to Stpe 7.

– If not, go to Step 5.l If CSPF path calculation fails, go to Step 5.

Step 5 Run the display explicit-path command to check the interfaces along the tunnel. Then, run thedisplay this command in the interface view of each interface of the tunnel to check whether theinterface is enabled with MPLS, MPLS TE, and RSVP-TE.l If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te

commands in the view of the interface.l If any interface along the tunnel is not in Up state, restart the interface. That is, run the

shutdown and then undo shutdown commands in the interface view, or run the restartcommand in the interface view .






515

Step 7 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.10 hwMplsTunnelHSBResume

39.16 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.10hwMplsTunnelHSBResume

Description

LSPM/3/MPLSTUNNELHSBRESUME:OID [oid] Main LSP of Tunnel resumes from backupLSP in HSB.(SessionTunnelId=[integer])

The trap message was output when the primary CR-LSP went Up and traffic was switched backfrom the hot-standby CR-LSP to the primary CR-LSP.

Attribute



Parameters

Name Meaning





Possible Causes

When the tunnel was in the HSB inuse state, the status of the primary LSP changed from Downto Up.

Procedure


----End



516

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.9 hwMplsTunnelHSBSwitch

39.17 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.11hwMplsTunnelOBSwitch

Description

LSPM/3/MPLSTUNNELOBSWITCH:OID [oid] Main LSP of Tunnel switches to back up LSPin OB.(SessionTunnelId=[integer])

The trap message was output when the primary CR-LSP went Down and traffic was switchedto an ordinary backup CR-LSP.

Attribute



Parameters

Name Meaning




The primary LSP was Down and the backup LSP was used, and the traffic interruption occured.

Possible Causes

The primary LSP was Down and the backup LSP was Up. The backup mode was OB.

Procedure






517








interface-type interface-number command on the ingress to check the tunnel configurations,including the primary tunnel, protection tunnel, and the protection interface. Check whetherthe mpls te auto-frr command is configured in the MPLS view. If so, it indicates that AutoFRR is enabled. In this case, you can check the primary tunnel. If not, check whether thempls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel are configured toidentify the primary and backup tunnels.After the primary and backup tunnels are checked, you can check the explicit-path commandto verify whether the explicit path is configured; check the mpls te affinity propertycommand to verify whether the affinity property is configured.Run the display mpls te cspf destination command and configure the parameters ofconstraints one by one, including the priority (priority setup-priority), bandwidth(bandwidth), explicit path (explicit-path path-name), affinity property (affinityproperties), and hop limit (hop-limit hop-limit-number), and you can check whether the paththat meets the constraints is available. If so, the path of the TE tunnel is displayed, indicatingthat CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculationfails.


2. If CSPF path calculation fails after affinity property is configured, run the mpls teaffinity property command in the tunnel view to modify the affinity property of the



518

tunnel, or run the mpls te link administrative group on the interfaces along the tunnelto modify the administrative group property of the link.




– If not, go to Step 5.l If CSPF path calculation fails, go to Step 5.

Step 5 Run the display explicit-path command to check the interfaces along the tunnel. Then, run thedisplay this command in the interface view of each interface of the tunnel to check whether theinterface is enabled with MPLS, MPLS TE, and RSVP-TE.l If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls te rsvp-te

commands in the view of the interface.l If any interface along the tunnel is not in Up state, restart the interface. That is, run the

shutdown and then undo shutdown commands in the interface view, or run therestartcommand in the interface view.




Step 7 End.

----End

Related InformationLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.12 hwMplsTunnelOBResume

39.18 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.12hwMplsTunnelOBResume

DescriptionLSPM/3/MPLSTUNNELOBRESUME:OID [oid] Main LSP of Tunnel resumes from backupLSP in OB.(SessionTunnelId=[integer])

The trap message was output when the primary CR-LSP went Up and traffic was switched backfrom the ordinary backup CR-LSP to the primary CR-LSP.



519

Attribute



Parameters

Name Meaning





Possible Causes

When the tunnel was in the OB inuse state, the status of the primary LSP changed from Downto Up.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.11 hwMplsTunnelOBSwitch

39.19 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.15hwMplsTunnelChangeBw

Description

LSPM/4/HWMPLSTUNCHANGEBW:OID [oid] The bandwidth of the tunnel has changed.(SessionTunnelId=[integer1], LocalLspId=[integer2], IngressLsrId=[integer3], EgressLsrId=[integer4])

The trap message was sent when the bandwidth of the tunnel changed.



520

Attribute



Parameters

Name Meaning



LocalLspId Indicates the ID of the local LSP.

IngressLsrId Indicates the ID of the ingress LSR.

EgressLsrId Indicates the ID of the egress LSR.



Possible Causes

The bandwidth of a specified type on the tunnel was changed.

Procedure


----End

Related Information

None.

39.20 LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.1hwMplsLdpVirtualTunnelUp

Description

LSPM/1/LDPVTUNNEL_UP:OID [oid] LDP virtual tunnel went Up. (VirtualTunnelIndex=[gauge])

This alarm is generated when the LDP virtual tunnel goes Up.



521

Attribute



Parameters

Name Meaning


VirtualTunnelIndex Indicates the index of the virtual tunnel.



Possible Causes

The first LDP ingress LSP under a certain LDP virtual tunnel is successfully set up.

Procedure

l This log message is informational only, and no action is required.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.2_hwMplsLdpVirtualTunnelDown

39.21 LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.2hwMplsLdpVirtualTunnelDown

Description

LSPM/1/LDPVTUNNEL_DOWN:OID [oid] LDP virtual tunnel went Down.(VirtualTunnelIndex=[gauge])

This alarm is generated when the LDP virtual tunnel goes Down.

Attribute





522

Parameters

Name Meaning


VirtualTunnelIndex Indicates the index of the virtual tunnel.


Possible CausesAll the LDP ingress LSPs under a certain LDP virtual tunnel are deleted.

Procedurel This log message is informational only, and no action is required.

----End

Related InformationLSPM_1.3.6.1.4.1.2011.5.25.182.1.54.1_hwMplsLdpVirtualTunnelUp

39.22 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.46hwMplsTunnelPrimaryUp

DescriptionLSPM/2/MPLSTUNPRIUP:OID [oid] The primary LSP of the tunnel changes to Up.(SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelIfName=[octet])

The primary LSP of the tunnel changes to Up.

Attribute





523

Parameters

Name Meaning



TunnelInstIndex Indicates the InstIndex of the tunnel.






Possible Causes

The primary LSP of the tunnel changes to Up.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryDown

39.23 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47hwMplsTunnelPrimaryDown

Description

LSPM/2/MPLSTUNPRIDOWN:OID [oid] The primary LSP of the tunnel changes to Down.(SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer],hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer],hwMplsTunnelDownIfAddr=[binary])

The primary LSP of the tunnel changes to Down.



524

Attribute



Parameters

Name Meaning







hwMplsTunnelDownReason Indicates the reason why a tunnel goes Down.

hwMplsTunnelDownLSRId Indicates the LSR ID of the error node on a tunnel.

hwMplsTunnelDownIfAddrType Indicates the IP address type of the error interface on atunnel.

hwMplsTunnelDownIfAddr Indicates the IP address of the error interface on a tunnel.


If traffic is not forwarded along the primary LSP of the tunnel, traffic forwarding will not beaffected. If traffic is forwarded along the primary LSP of the tunnel and a backup LSP isconfigured, traffic will be switched to the backup LSP. If not, traffic forwarding will beinterrupted.

Possible Causes

Cause 1: The interface wen Up.

Cause 1: The configuration of the tunnel was deleted.

Cause 3: The link was faulty.



525

Procedure






can be pinged, and then check whether the alarmLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47hwMplsTunnelPrimaryUp is generated.– If so, go to Step 7.– If not, go to Step 3.



Step 4 Run the display mpls te cspf destination command on the ingress to check whether a path thatmeets the bandwidth constraints is available. If so, the path of the TE tunnel is displayed,indicating that CSPF calculation is successful. If not, null is displayed, indicating that CSPFcalculation fails.l If the path is successfully calculated, run the display current-configuration interface

interface-type interface-number command on the ingress to check the tunnel configurations.You can check the explicit-path command to verify whether the explicit path is configured;check the mpls te affinity property command to verify whether the affinity property isconfigured; check the mpls te bandwidth command to verify whether the bandwidth isconfigured.Run the display mpls te cspf destination command and configure the parameters ofconstraints one by one, including the priority (priority setup-priority), bandwidth(bandwidth), explicit path (explicit-path path-name), affinity property (affinityproperties), and hop limit (hop-limit hop-limit-number), and you can check whether the paththat meets the constraints is available. If so, the path of the TE tunnel is displayed, indicatingthat CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculationfails.

1. If the explicit path fails to be calculated, check whether the interfaces along the explicitpath are in the Up state and are enabled with MPLS and MPLS TE. If the explicit path



526

is successfully calculated, check whether path calculation according to the affinityproperty and bandwidth is consistent with the explicit path by running the display mplste cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.


3. If CSPF path calculation fails after bandwidth is configured, run the display mpls telink-administration bandwidth-allocation interface interface-type interface-number command to check whether the bandwidth of each interface along the tunnel isenough. If the bandwidth is enough, it is possible that the tunnel with a higher prioritypreempts the bandwidth of the current tunnel. Then run the mpls te bandwidth max-reservable-bandwidth and mpls te bandwidth commands in the interface view toincrease the bandwidth.


Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47hwMplsTunnelPrimaryUp is generated.




Step 5 Run the display explicit-path command or identify interfaces that an LSP passes through basedon the network topology to check the interfaces along the tunnel. Then, run the display thiscommand in the interface view of each interface of the tunnel to check whether the interface isenabled with MPLS, MPLS TE, and RSVP-TE.



Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47hwMplsTunnelPrimaryUp is generated.




Step 7 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.46 hwMplsTunnelPrimaryUp



527

39.24 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48hwMplsTunnelHotstandbyUp

Description

LSPM/2/MPLSTUNHSBUP:OID [oid] The hot-standby LSP of the tunnel changes to Up.(SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelIfName=[octet])

The hot-standby LSP of the tunnel changes to Up.

Attribute



Parameters

Name Meaning









Possible Causes

The hot-standby LSP of the tunnel changes to Up.



528

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.49 hwMplsTunnelHotstandbyDown

39.25 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.49hwMplsTunnelHotstandbyDown

Description

LSPM/2/MPLSTUNHSBDOWN:OID [oid] The hot-standby LSP of the tunnel changes toDown. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer],hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer],hwMplsTunnelDownIfAddr=[binary])

The hot-standby LSP of the tunnel changes to Down.

Attribute



Parameters

Name Meaning










529

Name Meaning




Impact on the SystemIf traffic is not forwarded along the hot-standby LSP of the tunnel, traffic forwarding will notbe affected. If traffic is forwarded along the primary LSP of the tunnel and other LSP of thetunnel is in up state, traffic will be switched to the other LSP. If not, traffic forwarding will beinterrupted.

Possible CausesCause 1: The interface wen Up.



Cause 4: The hot-standby LSP had nodes through which the primary LSP passed.

Procedure








can be pinged, and then check whether the alarmLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48hwMplsTunnelHotstandbyUp is generated.





530






l If the path is successfully calculated, run the display current-configuration interfaceinterface-type interface-number command on the ingress to check the tunnel configurations.You can check the explicit-path command to verify whether the explicit path is configured;check the mpls te affinity property command to verify whether the affinity property isconfigured; check the mpls te bandwidth command to verify whether the bandwidth isconfigured.






Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48hwMplsTunnelHotstandbyUp is generated.


– If not, and the hot-standby LSP is not configured with an explicit path and the overlapattribute, meanwhile the primary LSP is in the Up state, configure an explicit path or the



531

overlap attribute for the hot-standby LSP. Alternatively, configure an LSP with its nodesbeing totally different with that on the primary LSP, then got to Step 7.

– Else, go to Step 5.





Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48hwMplsTunnelHotstandbyUp is generated.




Step 7 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp

39.26 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50hwMplsTunnelOrdinaryUp

Description

LSPM/3/MPLSTUNOBKUP: OID [oid] The ordinary LSP of the tunnel changes to Up.(SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelIfName=[octet])

The ordinary LSP of the tunnel changes to Up.

Attribute





532

Parameters

Name Meaning









Possible Causes

The ordinary LSP of the tunnel changes to Up.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.51 hwMplsTunnelOrdinaryDown

39.27 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.51hwMplsTunnelOrdinaryDown

Description

LSPM/3/MPLSTUNOBKDOWN:OID [oid] The ordinary LSP of the tunnel changes to Down.(SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer],hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer],hwMplsTunnelDownIfAddr=[binary])

The ordinary LSP of the tunnel changes to Down.



533

Attribute



Parameters

Name Meaning












If traffic is not forwarded along the backup LSP of the tunnel, traffic forwarding will not beaffected. If traffic is forwarded along the backup LSP of the tunnel and another backup LSP isconfigured, traffic will be switched to the other backup LSP. If not, traffic forwarding will beinterrupted.

Possible Causes




Cause 4: An LSP with higher priority became Up.



534

Procedure

Step 1 Run the display mpls te tunnel-interface tunnel-name command on the ingress (where thealarm is generated) to check the tunnel status. The PrimaryLSP State field indicates whether theprimary LSP of the tunnel is in the Up state and the Hot-Standby LSP State field indicateswhether the Hot-standby LSP is in the Up state.

l If the primary LSPs or hot-standby LSPs are in the Up state, the backup LSP cannot go Up.To address such a problem, go to Step 8.

l If both the primary and hot-standby LSPs are in the Down state, go to Step 2.







– For other types of errors, go to Step 7.



l If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnelcan be pinged, and then check whether the alarmLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50hwMplsTunnelOrdinaryUp is generated.











535






Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50hwMplsTunnelOrdinaryUp is generated.







Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50hwMplsTunnelOrdinaryUp is generated.






536

Step 8 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp

39.28 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52hwMplsTunnelBesteffortUp

Description

LSPM/3/MPLSTUNBBKUP:OID [oid] The best-effort LSP of the tunnel changes to Up.(SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelIfName=[octet])

The best-effort LSP of the tunnel changes to Up.

Attribute



Parameters

Name Meaning











537

Possible Causes

The best-effort LSP of the tunnel changes to Up.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.53 hwMplsTunnelBesteffortDown

39.29 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.53hwMplsTunnelBesteffortDown

Description

LSPM/3/MPLSTUNBBKDOWN:OID [oid] The best-effort LSP of the tunnel changes to Down.(SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer],hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer],hwMplsTunnelDownIfAddr=[binary])

The best-effort LSP of the tunnel changes to Down.

Attribute



Parameters

Name Meaning








538

Name Meaning







If traffic is not forwarded along the best-effort LSP of the tunnel, traffic forwarding will not beaffected. If traffic is forwarded along the best-effort LSP of the tunnel and a backup LSP isconfigured, traffic will be switched to the backup LSP. If not, traffic forwarding will beinterrupted.

Possible Causes




Cause 4: An LSP with higher priority became Up.

Procedure

Step 1 Run the display mpls te tunnel-interface tunnel-name command on the ingress (where thealarm is generated) to check the tunnel status. The PrimaryLSP State field indicates whether theprimary LSP of the tunnel is in the Up state and the Hot-Standby LSP State field indicateswhether the Hot-standby LSP is in the Up state.

l If the primary LSPs or hot-standby LSPs are in the Up state, the backup LSP cannot go Up.To address such a problem, go to Step 8.

l If both the primary and hot-standby LSPs are in the Down state, go to Step 2.







539



– For other types of errors, go to Step 7.



l If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnelcan be pinged, and then check whether the alarmLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52hwMplsTunnelBesteffortUp is generated.








l If the path is successfully calculated, run the display current-configuration interfaceinterface-type interface-number command on the ingress to check the tunnel configurations.You can check the mpls te affinity property command to verify whether the affinity propertyis configured; check the mpls te hop-limit command to verify whether the number of thehops is configured.

Run the display mpls te cspf destination command and configure the parameters ofconstraints one by one, including the affinity property (affinity properties) and hop limit(hop-limit hop-limit-number), and you can check whether the path that meets the constraintsis available. If so, the path of the TE tunnel is displayed, indicating that CSPF calculation issuccessful. If not, null is displayed, indicating that CSPF calculation fails.


2. If CSPF path calculation fails after the number of hops is configured, check whetherthe number of the nodes along the tunnel is less than the number of the hops. If not,change the configuration of the number of hops or change the path to meet the hop limit.


Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52hwMplsTunnelBesteffortUp is generated.






540


Step 7 End.

----End

Related InformationLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52 hwMplsTunnelBesteffortUp

39.30 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.54hwMplsTeAutoTunnelDownClear

DescriptionLSPM/2/MPLSTEAUTOTUNNELDOWNCLEAR:OID [oid] The TE Auto tunnel Down alarmwas cleared. (SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer],EgressLsrId=[integer], mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer],mplsTunnelIfName=[octet])

The TE Auto tunnel Down alarm was cleared.

Attribute



Parameters

Name Meaning



LocalLspId Indicates the ID of local LSP.



mplsTunnelAdminStatus Indicates the administration status of the tunnel.

mplsTunnelOperStatus Indicates the operation status of the tunnel.

mplsTunnelIfName Indicates the name of the tunnel interface.




541

Possible CausesThe TE Auto tunnel was created successfully.


----End


39.31 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.55hwMplsTeAutoTunnelPrimaryDownClear

DescriptionLSPM/2/MPLSTEAUTOTUNNEL_PRIDOWNCLEAR:OID [oid] The Down alarm about theprimary LSP in the TE Auto tunnel was cleared. (SessionTunnelId=[INTEGER],TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer],mplsTunnelIfName=[octet])

The Down alarm about the primary LSP in the TE Auto tunnel was cleared.

Attribute



Parameters

Name Meaning



TunnelInstIndex Indicates the index of the tunnel.



mplsTunnelIfName Indicates the name of the tunnel interface.




542

Possible Causes

The primary LSP in the TE Auto tunnel was created successfully.

Procedure


----End

Related Information

None.

39.32 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.56hwMplsTunnelBBSwitch

Description

LSPM/3/MPLSTUNNELBBSWITCH:OID [oid] Main LSP of Tunnel switches to back up LSPin BBK.(SessionTunnelId=[integer])

Main LSP of Tunnel switches to back up LSP in BBK.

Attribute



Parameters

Name Meaning




The service traffic to be forwarded will be interrupted.

Possible Causes

The primary LSP was Down and the backup LSP was in Up state. The backup mode was OB.



543

Procedure

Step 1 Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, thenode that generates the trap) to check the configurations of the tunnel. View the Tunnel StateDesc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.l In the case of the following error prompts, do as required:









interface-type interface-number command on the ingress to check the tunnel configurations,including the primary tunnel, protection tunnel, and the protection interface. Check whetherthe mpls te auto-frr command is configured in the MPLS view. If so, it indicates that AutoFRR is enabled. In this case, you can check the primary tunnel. If not, check whether thempls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel are configured toidentify the primary and backup tunnels.After the primary and backup tunnels are checked, you can check the explicit-path commandto verify whether the explicit path is configured; check the mpls te affinity propertycommand to verify whether the affinity property is configured; check the mpls tebandwidth command to verify whether the bandwidth is configured.Run the display mpls te cspf destination command and configure the parameters ofconstraints one by one, including the priority (priority setup-priority), bandwidth(bandwidth), explicit path (explicit-path path-name), affinity property (affinityproperties), and hop limit (hop-limit hop-limit-number), and you can check whether the paththat meets the constraints is available. If so, the path of the TE tunnel is displayed, indicating



544

that CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculationfails.



3. If CSPF path calculation fails after bandwidth is configured, run the display mpls telink-administration bandwidth-allocation interface interface-type interface-number command to check whether the bandwidth of each outbound interface along thetunnel is enough. If the bandwidth is enough, it is possible that the tunnel with a higherpriority preempts the bandwidth of the current tunnel. Then run the mpls te bandwidthmax-reservable-bandwidth and mpls te bandwidth commands in the interface viewto increase the bandwidth.



– If so, go to Stpe 7.





l If any interface along the tunnel is not in Up state, restart the interface. That is, run theshutdown and then undo shutdown commands in the interface view.





Step 7 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.57 hwMplsTunnelBBResume



545

39.33 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.57hwMplsTunnelBBResume

Description

LSPM/3/MPLSTUNNELBBRESUME:OID [oid] Main LSP of Tunnel resumes from backupLSP in BBK.(SessionTunnelId=[integer])

Main LSP of Tunnel resumes from backup LSP in BBK.

Attribute



Parameters

Name Meaning





Possible Causes

When the tunnel was in the BBK inuse state, the status of the primary LSP changed from Downto Up.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.56 hwMplsTunnelBBSwitch



546

39.34 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.58hwMplsExtTunnelDown

Description

LSPM/2/MPLSEXTTUNNELDOWN:OID [oid] The TE tunnel changes to Down.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], OutIfIndex=[integer], hwMplsTunnelInterfaceName=[octet], hwMplsTunnelType=[integer], hwMplsTunnelAdminStatus=[integer], hwMplsTunnelOperStatus=[integer],hwMplsTunnelDownReason=[integer], OutIfName=[octet], hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer], hwMplsTunnelDownIfAddr=[binary])

The TE tunnel changes to Down.

Attribute



Parameters

Name Meaning



LocalLspId Indicates the local LSP ID of a tunnel.



OutIfIndex Indicates the index of the outbound interface.

hwMplsTunnelInterfaceName Indicates the name of a TE tunnel interface.

hwMplsTunnelType Indicates the type of a tunnel.

hwMplsTunnelAdminStatus Indicates the management status of a tunnel.

hwMplsTunnelOperStatus Indicates the running status of a tunnel.



547

Name Meaning


OutIfName Indicates the name of the outbound interface.




Impact on the SystemTraffic forwarded along the tunnel will be interrupted.

Possible CausesCause 1: The interface went Down.

Cause 2: The route changed.


Procedure

Step 1 Run the display mpls te tunnel-interface last-error command to view the prompt.l In the case of the following error prompts, do as required:





can be pinged, and then check whether the alarmLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59hwMplsExtTunnelDownClear is generated.– If so, go to Step 7.– If not, go to Step 3.





548










Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59hwMplsExtTunnelDownClear is generated.







549



Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59hwMplsExtTunnelDownClear is generated.




Step 7 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59 hwMplsExtTunnelDownClear

39.35 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59hwMplsExtTunnelDownClear

Description

LSPM/2/MPLSEXTTUNNELDOWNCLEAR:OID [oid] The TE tunnel Down alarm wascleared.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer],EgressLsrId=[integer], OutIfIndex=[integer], hwMplsTunnelInterfaceName=[octet],hwMplsTunnelType=[integer], hwMplsTunnelAdminStatus=[integer],hwMplsTunnelOperStatus=[integer], hwMplsTunnelDownReason=[integer], OutIfName=[octet])

The TE tunnel Down alarm was cleared.

Attribute



Parameters

Name Meaning




550

Name Meaning


LocalLspId Indicates the local LSP ID of a tunnel.



OutIfIndex Indicates the index of the outbound interface.

hwMplsTunnelInterfaceName Indicates the name of a TE tunnel interface.

hwMplsTunnelType Indicates the type of a tunnel.

hwMplsTunnelAdminStatus Indicates the management status of a tunnel.

hwMplsTunnelOperStatus Indicates the running status of a tunnel.


OutIfName Indicates the name of the outbound interface.



Possible Causes

The tunnel was successfully set up or the attributes of the tunnel changed.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.58 hwMplsExtTunnelDown

39.36 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.62hwMplsTunnelDelete



551

DescriptionLSPM/2/MPLSTUNNELDELETE:OID [oid] The MPLS TE tunnel was deleted.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer],mplsTunnelIfName=[octet])

The MPLS TE tunnel was deleted.

Attribute



Parameters

Name Meaning

oid MIB object ID

SessionTunnelId Tunnel ID

LocalLspId Local LSP ID

IngressLsrId Ingress LSR ID

EgressLsrId Egress LSR ID

mplsTunnelAdminStatus Administrative status of a tunnel. 1: Up. 2: Down.

mplsTunnelOperStatus Operating status of a tunnel. 1: Up. 2: Down.

mplsTunnelIfName Tunnel interface name


Possible CausesThe MPLS TE tunnel was deleted.

Procedure


----End



552

Related Information

None

39.37 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.63hwMplsLspThresholdExceed

Description

LSPM/3/MPLSLSPTHRESHOLDEXCEED:OID [oid] The lsp count exceeds the threshold.(hwMplsLspProtocol=[integer], hwMplsLspCurrentCount=[integer], hwMplsLspThreshold=[integer], hwMplsLspTotalCount=[integer])

The number of LSPs exceeded the upper threshold.

Attribute


1.3.6.1.4.1.2011.5.25.121.2.1.63 Minor qualityOfServiceAlarm(3)

Parameters

Name Meaning


hwMplsLspProtocol LSP protocol type

hwMplsLspCurrentCount Number of the current LSPs

hwMplsLspThreshold Upper threshold of LSPs

hwMplsLspTotalCount Upper limit of supported LDP LSPs


The number of hwMplsLspProtocol LSPs has reached the upper threshold. If the numbercontinues to increase, which exceeds the threshold, services will be affected.

Possible Causes

The number of the current hwMplsLspProtocol LSPs exceeded the upper threshold.



553

Procedure

Step 1 Run the display mpls lsp command to check whether unwanted hwMplsLspProtocol LSPs existon the device.

l If no unwanted LSPs exist, go to Step 3.

l If unwanted LSPs exist, go to Step 2.

Step 2 Use methods, such as modifying a policy for establishing LSPs, to suppress the establishmentof unwanted LSPs. Then, check whether the alarm is cleared.




Step 4 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.64 hwMplsLspThresholdExceedClear

39.38 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.64hwMplsLspThresholdExceedClear

Description

LSPM/3/MPLSLSPTHRESHOLDEXCEEDCLEAR:OID [oid] The lsp count falls from thethreshold.(hwMplsLspProtocol=[integer])

The total number of LSPs fell below the upper threshold.

Attribute


1.3.6.1.4.1.2011.5.25.121.2.1.64 Minor qualityOfServiceAlarm(3)

Parameters

Name Meaning





554


None.

Possible Causes

The number of LDP LSPs fell below the upper threshold.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.63 hwMplsLspThresholdExceed

39.39 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.65hwMplsLspTotalCountExceed

Description

LSPM/2/MPLSLSPTOTALCOUNTEXCEED:OID [oid] The lsp count reaches the upper limit.(hwMplsLspProtocol=[integer], hwMplsLspTotalCount=[integer])

The total number of LSPs exceeded the upper limit.

Attribute



Parameters

Name Meaning



hwMplsLspTotalCount Upper limit of supported LDP LSPs



555


The number of hwMplsLspProtocol LSPs has reached the upper limit. If subsequent LSPscontinue to be established, services of the new LSPs may be affected.

Possible Causes

The number of the current hwMplsLspProtocol LSPs reached the upper limit.

Procedure

Step 1 Run the display mpls lsp command to check whether unwanted hwMplsLspProtocol LSPs existon the device.

l If no unwanted LSPs exist, go to Step 3.

l If unwanted LSPs exist, go to Step 2.

Step 2 Use methods, such as modifying a policy for establishing LSPs, to suppress the establishmentof unwanted LSPs. Then, check whether the alarm is cleared.




Step 4 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.66 hwMplsLspTotalCountExceedClear

39.40 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.66hwMplsLspTotalCountExceedClear

Description

LSPM/2/MPLSLSPTOTALCOUNTEXCEEDCLEAR:OID [oid] The lsp count falls from theupper limit.(hwMplsLspProtocol=[integer])

The total number of LSPs fell below the upper limit.

Attribute





556

Parameters

Name Meaning




None.

Possible Causes

The number of LDP LSPs fell below the upper limit.

Procedure


----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.65 hwMplsLspTotalCountExceed

39.41 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.67hwMplsDynamicLabelThresholdExceed

Description

LSPM/4/LABEL_THRESHOLD_EXCEED:OID [oid] The dynamic label usage exceeds thethreshold. (hwMplsDynamicLabelTotalCount=[INTEGER],hwMplsDynamicLabelCurrentCount=[INTEGER],hwMplsDynamicLabelThresholdUpperLimit=[INTEGER],hwMplsDynamicLabelThresholdLowerLimit=[INTEGER])

Dynamic label usage reached the upper limit.

Attribute





557

Parameters

Name Meaning


hwMplsDynamicLabelTotalCount Total number of dynamic labels

hwMplsDynamicLabelCurrentCount Number of dynamic labels used

hwMplsDynamicLabelThresholdUpperLimit Upper limit of dynamic label usage

hwMplsDynamicLabelThresholdLowerLimit Lower limit of dynamic label usage


If dynamic label usage reaches a specific threshold, subsequent LSPs may fail to be establishedbecause all dynamic labels will be used.

Possible Causes

A great number of LSPs are established, and dynamic label usage reaches the upper limit.

Procedure

Step 1 Run the display mpls lsp statistics command to view statistics about LDP LSPs, RSVP-TE CR-LSPs, and BGP LSPs. Re-plan the services and delete unwanted LSPs that use dynamic labels.Then check whether LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.68hwMplsDynamicLabelThresholdExceedClear is generated.

l If this clear alarm is generated, go to step 3.

l If this clear alarm is not generated, go to step 2.

Step 2 Collect trap, log, and configuration information, and contact Huawei technical supportpersonnel.

Step 3 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.68 hwMplsDynamicLabelThresholdExceedClear

39.42 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.68hwMplsDynamicLabelThresholdExceedClear



558

Description

LSPM/4/LABEL_THRESHOLD_EXCEED_RESM:OID [oid] The dynamic label usage fallsfrom the threshold. (hwMplsDynamicLabelTotalCount=[INTEGER],hwMplsDynamicLabelCurrentCount=[INTEGER],hwMplsDynamicLabelThresholdUpperLimit=[INTEGER],hwMplsDynamicLabelThresholdLowerLimit=[INTEGER])

Dynamic label usage reached the lower limit.

Attribute



Parameters

Name Meaning




hwMplsDynamicLabelThresholdUpperLimit Upper limit of dynamic label usage

hwMplsDynamicLabelThresholdLowerLimit Lower limit of dynamic label usage


None.

Possible Causes

Unwanted LSPs were torn down, and the system reclaimed some dynamic labels.

Procedure

Step 1 The log is informational only, and no action is required.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.67 hwMplsDynamicLabelThresholdExceed



559

39.43 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.69hwMplsDynamicLabelTotalCountExceed

DescriptionLSPM/2/LABEL_TOTAL_EXCEED:OID [oid] The dynamic label count reaches the upperlimit. (hwMplsDynamicLabelTotalCount=[INTEGER], hwMplsDynamicLabelCurrentCount=[INTEGER])

Dynamic label usage reached 100%.

Attribute



Parameters

Name Meaning




Impact on the SystemAll dynamic labels are used, and no subsequent LSPs can be established.

Possible CausesA great number of LSPs were established, and all dynamic labels were used.

Procedure

Step 1 Run the display mpls lsp statistics command to view statistics about LDP LSPs, RSVP-TE CR-LSPs, and BGP LSPs. Re-plan the services and delete unwanted LSPs that use dynamic labels.Then check whether LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70hwMplsDynamicLabelTotalCountExceedClear is generated.l If this clear alarm is generated, go to step 3.l If this clear alarm is not generated, go to step 2.

Step 2 Collect log messages and contact Huawei technical support personnel.



560

Step 3 End.

----End

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70 hwMplsDynamicLabelTotalCountExceedClear

39.44 LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70hwMplsDynamicLabelTotalCountExceedClear

Description

LSPM/2/LABEL_TOTAL_EXCEED_RESM:OID [oid] The dynamic label count falls from theupper limit. (hwMplsDynamicLabelTotalCount=[INTEGER],hwMplsDynamicLabelCurrentCount=[INTEGER])

Dynamic label usage fell to 95%.

Attribute



Parameters

Name Meaning





None.

Possible Causes

Unwanted LSPs were torn down, and the system reclaimed some dynamic labels.



561

Procedure

Step 1 The log is informational only, and no action is required.

----End

Related InformationLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.69 hwMplsDynamicLabelTotalCountExceed



562

40 LBDT

About This Chapter

40.1 LBDT_1.3.6.1.4.1.2011.5.25.174.3.3 hwLdtPortLoopDetect

40.2 LBDT_1.3.6.1.4.1.2011.5.25.174.3.4 hwLdtPortLoopDetectRecovery

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 40 LBDT


563

40.1 LBDT_1.3.6.1.4.1.2011.5.25.174.3.3hwLdtPortLoopDetect

Description

LBDT/4/PORTTRAP: OID [OID] Loopback does exist on interface ([INTEGER]) [OCTET]([OCTET]), loopback detect status: [INTEGER]. (1:normal; 2:block; 3:shutdown; 4:trap;5:nolearn; 6:quitvlan)

([OID]:OID hwPortLoopDetectIfIndex=[Integer]; hwLPortLoopDetectIfName=[octet];hwLdtPortLoopDetectVlanList=[octet]; hwPortLoopDetectStatus= [Integer])

A loop is detected on the Layer 2 network connected to the interface.

Attribute



Parameters

Name Meaning

[OID] Indicates the trap OID.

hwPortLoopDetectIfIndex Indicates the interface index.

hwLPortLoopDetectIfName Indicates the interface name.

hwLdtPortLoopDetectVlanList An alarm is reported when a loop is detected in a VLAN. Ifuntagged packets are used to detect the loop, the value of thisparameter is Untagged. If tagged packets are used to detectthe loop, the value of this parameter is the VLAN ID in theVLAN tag.

hwPortLoopDetectStatus Indicates the loop detection status on the interface.


After the interface is shut down, all traffic on the interface is interrupted.

After the interface is blocked, all traffic except protocol packets is interrupted.

After nolearn is configured on the interface, the interface does not learn MAC addresses.

After the trap function is configured on the interface, the interface continuously reports traps.

After the quitvlan function is configured on the interface, the interface is deleted from the VLANwhere a loop occurs and services of traffic in the VLAN are interrupted.



564

Possible Causes

An Ethernet loop is detected between the interfaces.

Procedure

l A loop occurs on the Layer 2 network connected to the interface.

----End

Related Information

LBDT_1.3.6.1.4.1.2011.5.25.174.3.3 hwLdtPortLoopDetect

40.2 LBDT_1.3.6.1.4.1.2011.5.25.174.3.4hwLdtPortLoopDetectRecovery

Description

LBDT/4/PORTTRAP:OID [OID] Loopback disappeared on interface ([INTEGER]) [OCTET],loopback detect status: [INTEGER]. (1:normal; 2:block; 3:shutdown; 4:trap; 5:nolearn;6:quitvlan)

( [OID]:Trap OID; hwPortLoopDetectIfIndex="[Integer]";hwLPortLoopDetectIfName="[octet]"; hwPortLoopDetectStatus= "[Integer]")

The loop on the interface is removed.

Attribute



Parameters

Name Meaning

[OID] Indicates the trap OID.

hwPortLoopDetectIfIndex Indicates the interface index.

hwLPortLoopDetectIfName Indicates the interface name.

hwPortLoopDetectStatus Indicates the loop detection status on the interface.


None



565

Possible CausesThe loop between the interfaces is removed.

Procedurel

This is a clear alarm and no action is required.

----End

Related InformationLBDT_1.3.6.1.4.1.2011.5.25.174.3.4 hwLdtPortLoopDetectRecovery



566

41 LLDP

About This Chapter

41.1 LLDP_1.0.8802.1.1.2.0.0.1 lldpRemTablesChange

41.2 LLDP_1.3.6.1.4.1.2011.5.25.134.2.1 hwLldpEnabled

41.3 LLDP_1.3.6.1.4.1.2011.5.25.134.2.2 hwLldpDisabled

41.4 LLDP_1.3.6.1.4.1.2011.5.25.134.2.5 hwLldpLocManIPAddrChange

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 41 LLDP


567

41.1 LLDP_1.0.8802.1.1.2.0.0.1 lldpRemTablesChange

Description

LLDP/4/NBRCHGTRAP: OID: [oid] Neighbor information is changed.(LldpStatsRemTablesInserts=[integer], LldpStatsRemTablesDeletes=[integer],LldpStatsRemTablesDrops=[integer], LldpStatsRemTablesAgeouts=[integer])

This alarm is generated when a neighbor is added, deleted, discarded, or aged.

Attribute


1.0.8802.1.1.2.0.0.1 Warning equipmentAlarm(6)

Parameters

Name Meaning


lldpStatsRemTablesInserts Indicates the number of new neighbors.

lldpStatsRemTablesDeletes Indicates the number of neighbors that are deleted.

lldpStatsRemTablesDrops Indicates the number of neighbors that are discarded because ofinsufficient space.

lldpStatsRemTablesAgeouts Indicates the number of neighbors that are aged.


This alarm is a notification of changes in the network topology for the NMS, and no action isrequired.

Possible Causes

Cause 1

A neighbor is found.

Cause 2

A neighbor is deleted.

Cause 3

A neighbor is aged.

Cause 4



568

A neighbor is discarded because of insufficient space.

Procedure

Step 1 Check the values of LldpStatsRemTablesInserts, LldpStatsRemTablesDeletes,dpStatsRemTablesDrops, and LldpStatsRemTablesAgeouts in the alarm message.

1. If the value of LldpStatsRemTablesInserts is not 0, go to Step 2.

2. If the value of LldpStatsRemTablesDeletes is not 0, go to Step 3.

3. If the value of dpStatsRemTablesDrops is not 0, go to Step 4.

4. If the value of LldpStatsRemTablesAgeouts is not 0, go to Step 5.

Step 2 Neighbors are discovered, indicating that new devices are connected to theS2750&S5700&S6700 or LLDP is enabled on some neighbors. This message is a normalnotification and you do not need to handle it. Go to Step 6.

Step 3 Some neighbors are deleted, indicating that LLDP is disabled on these neighbors or the neighborsare disconnected from the S2750&S5700&S6700. Check whether the administrator has disabledLLDP on these devices or disconnected these devices from the S2750&S5700&S6700.

1. If the administrator has disabled LLDP on these devices or disconnected these devices fromthe S2750&S5700&S6700, go to Step 6.

2. If not, rectify the link fault and go to Step 6.

Step 4 The number of neighbors reaches the maximum (4096 on the entire S2750&S5700&S6700 and256 on each port). It is recommended that you disable LLDP on some minor ports to saveinformation about the new neighbors. Go to Step 6.

Step 5 Some neighbors are deleted after their aging time expires, indicating that the links between theneighbors and the S2750&S5700&S6700 are faulty. Rectify the link fault and go to Step 6.

Step 6 End.

----End

Related Information

None.

41.2 LLDP_1.3.6.1.4.1.2011.5.25.134.2.1 hwLldpEnabled

Description

LLDP/4/ENABLETRAP: OID: [oid] Global LLDP is enabled.

This notification is sent to the NMS when LLDP is enabled globally.

This alarm is allowed by the alarm delay.



569

Attribute



Parameters

Name Meaning



This alarm is a notification of the change of the network topology for the NMS, and does notaffect services.

Possible Causes

The LLDP is enabled globally.

Procedure


----End

Related Information

None.

41.3 LLDP_1.3.6.1.4.1.2011.5.25.134.2.2 hwLldpDisabled

Description

LLDP/4/DISABLETRAP: OID: [oid] Global LLDP is disabled.

This notification is sent to the NMS when the LLDP is disabled globally.

This alarm is allowed by the alarm delay.

Attribute





570

Parameters

Name Meaning



This alarm is a notification of the change of the network topology for the NMS, and does notaffect services.

Possible Causes

The LLDP is disabled globally.

Procedure


----End

Related Information

None.

41.4 LLDP_1.3.6.1.4.1.2011.5.25.134.2.5hwLldpLocManIPAddrChange

Description

LLDP/4/ADDCHGTRAP: OID: [oid] Local management address is changed.(LocManAddr="[OCTET]")

This alarm is generated when the management address of a device is changed.

Attribute



Parameters

Name Meaning


LocManAddr Indicates the local management address.



571

Impact on the SystemThis alarm is a notification of the change of the network topology for the NMS, and does notaffect services.

Possible CausesThe management address of a device is changed through commands manually.

Procedure

Step 1 Check whether the management address of the device is changed because of normal servicerequirements.l If it is a normal service requirement, go to Step 3.l If not, go to Step 2.

Step 2 Run the ip address command on the management interface to use the correct address.

Step 3 End.

----End




572

42 MCAST

About This Chapter

42.1 MCAST/3/TRAP

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 42 MCAST


573

42.1 MCAST/3/TRAP

Description

MCAST/3/TRAP/0xff0e2000 T/M "[STRING]"

L2MC or IPMC indexes are used up.

Attribute


None. Warning ADMC

Parameters

Name Meaning

STRING Indicates the alarm message:1. No remained Index to alloc for L2MC,Index FUll!

No L2MC index is available because all indexes are used up.2. No remained Index to alloc for L2MC!

No L2MC index is available for other reasons.3. No remained Index to alloc for IPMC,Index FUll!

No IPMC index is available because all indexes are used up.4. No remained Index to alloc for IPMC!

No IPMC index is available for other reasons.


New multicast entries cannot be generated, and multicast service is interrupted.

Possible Causes

The number of multicast entries exceeds the upper limit. The L2MC or IPMC indexes have beenused up.

Procedure

Step 1 If a L2MC alarm message is generated, Layer 2 multicast service is forwarded based on MACaddresses, and L2MC indexes are used up. Run the reset igmp-snooping group { all | vlan{ all | vlan-id [ [ source-address source-address ] group-address group-address ] } } commandto delete unneeded entries. To delete Layer 2 static multicast entries, run the undo l2-multicaststatic-group [ source-address source-ip-address ] group-address group-ip-address vlan{ all | { vlan-id1 [ to vlan-id2 ] } &<1-10> } command in the interface view.



574

Step 2 If an IPMC alarm message is generated, the IPMC entries are used up. Perform the followingoperations:l Run the display igmp-snooping port-info command to check whether too many Layer 2

multicast entries forwarded in IP mode are generated on the device. Run the reset igmp-snooping group { all | vlan { all | vlan-id [ [ source-address source-address ] group-address group-address ] } } command to delete unneeded entries. If Layer 2 static multicastentries are generated, run the undo l2-multicast static-group [ source-address source-ip-address ] group-address group-ip-address vlan { all | { vlan-id1 [ to vlan-id2 ] } &<1-10> }command in the interface view to delete the unneeded entries.

l Run the display multicast forwarding-table command to check whether too many Layer 3multicast entries are generated on the device. If so, run the reset multicast forwarding-table { group-address [ mask { group-mask | group-mask-length } ] | source-address[ mask { source-mask | source-mask-length } ] } command to delete unneeded Layer 3multicast entries.

Step 3 Check whether new multicast entries can be generated and whether the multicast service runsnormally.l If so, go to step 5.l If no, go to step 4.

Step 4 Contact the Huawei technical support personnel.

Step 5 End.

----End




575

43 MID_L2BPTNL

About This Chapter

43.1 MID_L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.15hwL2ProtocolTunnelDropThresholdRaising

43.2 MID_L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.16hwL2ProtocolTunnelDropThresholdFalling

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 43 MID_L2BPTNL


576

43.1 MID_L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.15hwL2ProtocolTunnelDropThresholdRaising

Description

MID_L2BPTNL/1/L2BPTNL_DROP_THRESHOLD_ALARM:OID [oid] The number of theprotocol transmit on the port reach the drop threshold. (PortName=[OCTET], ProtocolName=[OCTET], Dropthreshold=[INTEGER])

The number of Layer 2 protocol packets transmitted on the interface enabled with Layer 2protocol transparent transmission reached the threshold.

Attribute



Parameters

Name Meaning







Possible Causes

The interface enabled with Layer 2 protocol transparent transmission was configured with thethreshold for discarding Layer 2 protocol packets, and the number of Layer 2 protocol packetsthat were transparently transmitted on the interface reached the threshold.

Procedure


----End



577

43.2 MID_L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.16hwL2ProtocolTunnelDropThresholdFalling

Description

MID_L2BPTNL/1/L2BPTNL_DROP_THRESHOLD_RESUME:OID [oid] The number of theprotocol transmit on the port below the drop threshold. (PortName=[OCTET], ProtocolName=[OCTET], Dropthreshold=[INTEGER])

The trap was generated when the number of Layer 2 protocol packets passing the interfaceenabled with Layer 2 protocol transparent transmission fell below the threshold. This is amatching trap of hwL2ProtocolTunnelDropThresholdRaising.

Attribute



Parameters

Name Meaning







Possible Causes

The interface enabled with Layer 2 protocol transparent transmission was configured with thethreshold for discarding Layer 2 protocol packets, and the number of Layer 2 protocol packetsthat were transparently transmitted on the interface fell below the threshold.

Procedure


----End



578

Related InformationMID_L2BPTNL_1.3.6.1.4.1.2011.5.25.42.2.1.7.15hwL2ProtocolTunnelDropThresholdRaising



579

44 MONITOR

About This Chapter

NOTE

Only the S5700HI supports MONITOR alarms.

44.1 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.8 CARDABNORMAL

44.2 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.9 CARDNORMAL

44.3 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.10 INPUTLINEABNORMAL

44.4 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.11 INPUTLINENORMAL

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 44 MONITOR


580

44.1 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.8CARDABNORMAL

DescriptionMONITOR/4/CARDABNORMAL:OID [oid] Monitor card is abnormal.

The environment monitoring card has failed, and the environment monitoring function isunavailable.

Attribute



Parameters

Name Meaning

OID Indicates the ID of the alarm MIB object.


Possible CausesNone

Procedure

Step 1 Contact Huawei customer service center.

----End


44.2 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.9CARDNORMAL

DescriptionMONITOR/4/CARDNORMAL:OID [oid] Monitor card is normal.



581

The environment monitoring card has recovered.

Attribute



Parameters

Name Meaning



None

Possible Causes

None

Procedure

Step 1 This is an alarm clearance notification, and no action is required.

----End

Related Information

None

44.3 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.10INPUTLINEABNORMAL

Description

MONITOR/4/INPUTLINEABNORMAL:OID [oid] Input line [INTEGER] is abnormal.

An error is detected on an input channel of the environment monitoring card, and an environmentalarm has been generated.

Attribute





582

Parameters

Name Meaning


[INTEGER] Indicates the number of an input channel.


None

Possible Causes

None

Procedure

Step 1 Check the monitored device connected to the specified input channel and handle the environmentalarm on the monitored device.

Step 2 Contact Huawei customer service center.

----End

Related Information

None

44.4 MONITOR_1.3.6.1.4.1.2011.5.25.31.2.0.11INPUTLINENORMAL

Description

MONITOR/4/INPUTLINENORMAL:OID [oid] Input line [INTEGER] is normal.

The alarm reported on an input channel of the environment monitoring card has been cleared.

Attribute



Parameters

Name Meaning




583

Name Meaning

[INTEGER] Indicates the number of an input channel.


Possible CausesNone

Procedure

Step 1 This is an alarm clearance notification, and no action is required.

----End




584

45 MSTP

About This Chapter

45.1 MSTP_1.3.6.1.2.1.17.0.1 NEWRT

45.2 MSTP_1.3.6.1.2.1.17.0.2 TOPOC

45.3 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.1 hwMstpiPortStateForwarding

45.4 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.2 hwMstpiPortStateDiscarding

45.5 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.3 hwMstpiBridgeLostRootPrimary

45.6 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.4 hwMstpiPortRootGuarded

45.7 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.5 hwMstpiPortBpduGuarded

45.8 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.6 hwMstpiPortLoopGuarded

45.9 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.7 hwMstpiEdgePortChanged

45.10 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.15 hwMstpiTcGuarded

45.11 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.16 hwMstpProTcGuarded

45.12 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.17 hwMstpProRootChanged

45.13 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.18 hwMstpProNewPortStateForwarding

45.14 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.19 hwMstpProNewPortStateDiscarding

45.15 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.20 hwMstpProNewBridgeLostRootPrimary

45.16 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.21 hwMstpProNewPortRootGuarded

45.17 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.22 hwMstpProNewPortBpduGuarded

45.18 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.23 hwMstpProNewPortLoopGuarded

45.19 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.24 hwMstpProNewEdgePortChanged

45.20 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.25 hwMstpProLoopbackDetected

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 45 MSTP


585

45.1 MSTP_1.3.6.1.2.1.17.0.1 NEWRT

Description

MSTP/1/NEWRT:OID [OID] This bridge has changed to be the root bridge.

After the network converges, the local bridge is elected as the new root bridge in the topology.

Attribute


1.3.6.1.2.1.17.0.1 Critical communicationsAlarm(2)

Parameters

Name Meaning



The topology changes, and traffic may be lost.

Possible Causes

1. The local bridge is added into a new network topology.

2. The priority of the local bridge is increased.

3. The root bridge in the original topology is faulty.

4. The priority of the root bridge in the original topology is reduced.

Procedure

Step 1 Check whether the local bridge is added as a new node into a Layer 2 network topology.



Step 2 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [to interface-number ] }&<1-10> ] [ brief ] command to check whether thepriority of the local bridge is the lowest in the network. The lower the priority of the local bridgeis, the more possibly the bridge becomes the root bridge.



Step 3 Check whether the local bridge is specified as the root bridge in the Layer 2 network topology.



586



Step 4 Run the stp [ instance instance-id ] priority priority command to re-set the priority of the localbridge as required. Alternatively, run the undo stp [ instance instance-id ] priority commandto restore the default priority of the local bridge. Then, check whether the alarm is cleared.



Step 5 Check whether a fault occurs in the original network topology.



Step 6 Rectify the fault in the original network topology. Then, check whether the alarm is cleared.



Step 7 Check whether the priority of the root bridge in the original topology is lowered.



Step 8 Run the stp [ instance instance-id ] priority priority command or the stp [ instance instance-id ] root primary command on the original root bridge to re-specify the original root bridge asthe root bridge. Then, check whether the alarm is cleared.




Step 10 End.

----End

Related Information

None.

45.2 MSTP_1.3.6.1.2.1.17.0.2 TOPOC

Description

MSTP/1/TOPOC:OID [OID] Bridge topology change.

The topology calculated by the STP changes.



587

Attribute



Parameters

Name Meaning



The topology changes, and traffic may be lost.

Possible Causes

1. The network topology changes because a new link is added into the network topology.

2. The network topology changes because interfaces go Up or Down.

Procedure

Step 1 View physical devices on the network to check whether new physical connections enabled withSTP are added.



Step 2 Check whether the added physical link is the required one.



Step 3 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether theinterfaces are consistent with the STP calculation results.



Step 4 Check whether the interfaces enabled with the STP protocol go Up or Down in the networktopology.






Step 6 Check whether a fault occurs in the original network topology.



588



Step 7 Rectify the fault in the original network topology. Then, check whether the alarm is cleared.



Step 8 Correctly deploy the network topology, and then check whether the alarm is cleared.




Step 10 End.

----End

Related Information

None.

45.3 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.1hwMstpiPortStateForwarding

Description

MSTP/4/PFWD:OID [oid] The port has been set to forwarding state. (InstanceID=[INTEGER],PortInstanceID=[INTEGER], PortID=[INTEGER], IfIndex=[INTEGER], PortName=[STRING])

A new link is added and the port enters the forwarding state.

Attribute



Parameters

Name Meaning


InstanceID Indicates the instance ID.

PortInstanceID Indicates the ID of the instance to which the interface belongs.

PortID Indicates the interface ID.



589

Name Meaning


PortName Indicates the interface name.


The network topology will change.

Possible Causes

1.

A new link was added to the network topology, and the network topology changed.

2.

The network topology has changed, because a port may be up or down.

Procedure




Step 2 Check whether the added physical link is necessary.










Step 6 End.

----End

Related Information

None.



590

45.4 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.2hwMstpiPortStateDiscarding

Description

MSTP/4/PDISC:OID [oid] The port has been set to discarding state. (InstanceID=[INTEGER],PortInstanceID=[INTEGER], PortID=[INTEGER], IfIndex=[INTEGER], PortName=[STRING])

The link status changed, and the port enters the Discarding state.

Attribute



Parameters

Name Meaning



PortInstanceID Indicates the ID of the instance to which the interface belongs.

PortID Indicates the port ID.


PortName Indicates the interface name.


The network topology will be changed.

Possible Causes

1.

The network topology changes that the port changes from the Forwarding state into theDiscarding state.

2.

A new link is added. After the topology calculation, the port enters the Discarding state.



591

Procedure














Step 6 End.

----End

Related Information

None.

45.5 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.3hwMstpiBridgeLostRootPrimary

Description

MSTP/2/ROOT:OID [OID]: We are not the root switch of the instance [instance-id]!

The original switch lost its status as a root bridge. Another switch with a higher priority in thenetwork replaced it and became the root bridge.

Attribute





592

Parameters

Name Meaning


instance-id Indicates the instance ID.


The actual network topology may not be the same as the expected one.

Possible Causes

1.

A new link was added to the network topology, and the network topology changed. In addition,the newly-added device became the root bridge through the stp root primary command, withthe MAC address smaller than that of the previous root bridge.

2.

The priorities of some switches changed in the network.

Procedure










Step 4 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether thepriority of a bridge is changed in the network topology.



Step 5 Check whether the operation of changing the priority is correct.





593

Step 6 Run the stp priority command to re-set the priority of the local bridge as required. Alternatively,run the undo stp priority command or the undo stp root command to restore the default valueof the priority of the local bridge. Then, check whether the alarm is cleared.







Step 9 End.

----End

Related Information

None.

45.6 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.4hwMstpiPortRootGuarded

Description

MSTP/2/RGSUP:OID [oid] The ROOT-Protection port received superior message.(InstanceID=[INTEGER], PortInstanceID=[INTEGER], PortID=[INTEGER], IfIndex=[INTEGER], PortName=[STRING])

A switch with a higher priority outside the protection range of the root bridge attempted tobecome the root bridge.

Attribute



Parameters

Name Meaning



PortInstanceID Indicates the instance ID of the port.




594

Name Meaning


PortName Indicates the port name.



Possible Causes

Cause 1:

The port enabled with the root protection function received BPDUs of a higher priority than thatof the bridge.

2:

The priority of some switch changed in the network.

Procedure










Step 4 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether thepriority of a bridge is change in the network topology.






Step 6 Run the stp priority command to re-set the priority of the local bridge as required. Alternatively,run the undo stp priority command or the undo stp root command to restore the default valueof the priority of the local bridge. Then, check whether the alarm is cleared.



595






Step 8 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether aninterface under the protection of the root bridge.



Step 9 Run the undo stp root-protection command in the interface view to delete the configuration ofthe protection under the root bridge. Then, check whether the alarm is cleared.




Step 11 End.

----End

Related Information

None.

45.7 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.5hwMstpiPortBpduGuarded

Description

MSTP/2/IVBPDU:OID [oid] The edged-port that enabled BPDU-Protection will be shutdown,because it received BPDU packet. (InstanceID=[INTEGER], PortID=[INTEGER], IfIndex=[INTEGER], PortName=[STRING])

The port enabled with BPDU protection and connected to the user received BPDUs. TheseBPDUs are likely to be attack packets from the user.

Attribute





596

Parameters

Name Meaning






Impact on the SystemThe user network connected to this port will be broken down.

Possible CausesThe edge port received BPDUs, and BPDU protection was enabled globally.

Procedure

Step 1 Check whether the interface should be specified as an edge port.l If so, go to Step 2.l If not, go to Step 3.

Step 2 Locate the source of the BPDUs on the interface and check whether the malicious attack exists.l If so, go to Step 4.l If not, go to Step 3.

Step 3 Run the undo stp edged-port command and then the undo shutdown command in the interfaceview to delete the configuration of the edge port and restart the interface. Then, check whetherthe alarm is cleared.l If the alarm is cleared, go to Step 5.l If the alarm is not cleared, go to Step 4.


Step 5 End.

----End


45.8 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.6hwMstpiPortLoopGuarded



597

Description

MSTP/2/LGEXP:OID [OID] The LOOP-Protection port did not receive BPDU packets inprescriptive time. (InstanceID=[INTEGER], PortInstanceID=[INTEGER], PortID=[INTEGER], IfIndex=[INTEGER], PortName=[STRING])

A port enabled with loop protection failed to receive BPDUs within a specified period, and wasset to be in the Discarding state.

Attribute



Parameters

Name Meaning



PortInstanceID Indicates the instance ID of the port.





The interface will not forward data.

Possible Causes

1.

The peer switch did not send the BPDUs to the local switch within the specified period. Thepossible cause was that the spanning tree function was disabled on the peer switch.

2.

The links connected to the peer were congested. Check whether the traffic was normal.

Procedure

Step 1 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether STPis disabled on the interfaces that are directly connected.




598


Step 2 Check whether the congestion occurs on the link between the local device and the neighbordevice.l If so, go to Step 4.l If not, go to Step 5.

Step 3 Run the stp enable command in the interface view to enable STP. Then, check whether the alarmis cleared.l If the alarm is cleared, go to Step 6.l If the alarm is not cleared, go to Step 2.

Step 4 Repair the physical link and then check whether the alarm is cleared.l If the alarm is cleared, go to Step 6.l If the alarm is not cleared, go to Step 5.


Step 6 End.

----End


45.9 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.7hwMstpiEdgePortChanged

DescriptionMSTP/4/EDGEPORT_DISABLE:OID [oid] When the port receives a BPDU packet, the edged-port attribute will be disabled. (InstanceID=[INTEGER], PortID=[INTEGER], IfIndex=[INTEGER], EdgePortEnableState=[INTEGER], PortName=[STRING])

The edge port lost the attributes of an edge port after receiving BPDUs.

Attribute



Parameters

Name Meaning




599

Name Meaning




EdgePortEnableState Indicates whether BPDU-guard is enabled on the edge port.



The network topology may be changed.

Possible Causes

The edge port received BPDUs.

Procedure

Step 1 Check whether the interface should be specified as an edge port.



Step 2 Locate the source of the BPDUs on the interface and check whether the malicious attack exists.



Step 3 Run the undo stp edged-port and undo shutdown commands in the interface view to deletethe configuration of the edge port and restart the interface. Then, check whether the alarm iscleared.




Step 5 End.

----End

Related Information

None.

45.10 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.15hwMstpiTcGuarded



600

Description

MSTP/4/TCGUARD:OID [OID] The instance received TC message exceeded the threshold willbe deferred to deal with at the end of TC protection time. (InstanceID=[INTEGER])

After the TC protection was enabled on the device that was enabled with MSTP, the TC packets,which were received after the number of TC packets received in a specified period had exceededthe threshold, were processed after the TC protection time expired.

Attribute



Parameters

Name Meaning




If the number of TC packets exceeds the threshold, MAC entries and ARP entries will not bedeleted immediately, and network topology will not be changed immediately, either.

Possible Causes

The TC packets, which were received after the number of TC packets received in a specifiedperiod had exceeded the threshold, were processed after the TC protection time expired.

Procedure

Step 1 Check whether the network topology flaps.



Step 2 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether thenumber of TC BPDUs exceeds the set threshold on the interface.



Step 3 Locate the cause of the network topology flapping and rectify the fault. Then, check whetherthe alarm is cleared.





601

Step 4 Run the stp tc-protection threshold threshold command in the interface view to re-set themaximum number of TC BPDUs that the device can process. Then, check whether the alarm iscleared.l If the alarm is cleared, go to Step 8.l If the alarm is not cleared, go to Step 5.

Step 5 Check whether malicious attacks exist.l If so, go to Step 6.l If not, go to Step 7.

Step 6 Locate the attack source and remove the attack. Then, check whether the alarm is cleared.l If the alarm is cleared, go to Step 8.l If the alarm is not cleared, go to Step 7.


Step 8 End.

----End


45.11 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.16hwMstpProTcGuarded

DescriptionMSTP/1/PROTCGUARD:OID [OID] MSTP process's instance received TC message exceededthe threshold will be deferred to deal with at the end of TC protection time. (ProcessID=[INTEGER], InstanceID=[INTEGER])

After the TC protection of the MSTP process was enabled, the TC packets, which were receivedafter the number of TC packets received by an instance had exceeded the threshold, wereprocessed after the TC protection time expired.

Attribute





602

Parameters

Name Meaning


ProcessID Indicates the ID of an MSTP process.

InstanceID Indicates the ID of an MSTP instance.

Impact on the SystemIf the number of TC packets exceeds the threshold, MAC entries and ARP entries will not bedeleted immediately, and network topology will not be changed immediately, either.

Possible Causes1.

The TC packets, which were received after the number of TC messages received by an MSTPprocess in a specified period had exceeded the threshold, were processed after the TC protectiontime expired.

Procedure

Step 1 Check whether the network topology flaps.l If so, go to Step 3.l If not, go to Step 2.

Step 2 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether thenumber of TC BPDUs exceeds the set threshold on the interface.l If so, go to Step 4.l If not, go to Step 7.

Step 3 Locate the cause of the network topology flapping and rectify the fault. Then, check whetherthe alarm is cleared.l If the alarm is cleared, go to Step 8.l If the alarm is not cleared, go to Step 2.

Step 4 Run the stp tc-protection threshold threshold command in the MSTP process view to re-setthe maximum number of TC BPDUs that the MSTP process can process. Then, check whetherthe alarm is cleared.l If the alarm is cleared, go to Step 8.l If the alarm is not cleared, go to Step 5.

Step 5 Check whether the malicious attacks exist.l If so, go to Step 6.l If not, go to Step 7.

Step 6 Locate the attack source and remove the attack. Then, check whether the alarm is cleared.



603




Step 8 End.

----End

Related Information

None.

45.12 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.17hwMstpProRootChanged

Description

MSTP/4/PRORTCHANGED:OID [oid] The root bridge of MSTP process has changed.(ProcessID=[INTEGER], InstanceID=[INTEGER], PortID=[INTEGER],PreviousRootBridgeID=[STRING], NewRootBridgeID=[STRING])

The root bridge changed. That is, a device became the root bridge or was not the root bridge anymore.

Attribute



Parameters

Name Meaning


ProcessID Indicates the ID of an MSTP process.



PreviousRootBridgeID Indicates the ID of the previous root bridge.

NewRootBridgeID Indicates the ID of the new root bridge.


If the root bridge is not a core node, it will affect the performance of the entire network.



604

Possible Causes

1.

A new device was added, which had the optimal bridge ID.

2.

The priorities of the devices in the current network were modified.

3.

The domain configuration was modified.

Procedure

Step 1 View physical devices on the network to check whether new physical links enabled with STPare added.



Step 2 Check whether the added physical link is required.



Step 3 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether thepriority vector of the instance is changed or the domain configuration is modified.



Step 4 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether thebridge ID is optimal on the entire network.



Step 5 Correctly configure the device according to the topology, and then check whether the alarm iscleared.



Step 6 Check whether the bridge ID of the added device is the optimal one on the entire network.




Step 8 End.

----End



605

Related Information

None.

45.13 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.18hwMstpProNewPortStateForwarding

Description

MSTP/4/PROPFWD:OID [oid] The MSTP Process's Port has been set to forwarding state.(ProcessID=[INTEGER], InstanceID=[INTEGER], PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER], PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

The link status of MSTP process changed, and the port enters the forwarding state.

Attribute



Parameters

Name Meaning


ProcessID Indicates the MSTP process ID


PortID1 Indicates ID 1 of the port in the MSTP process.




PortIDFlag Indicates the port flag.

IfIndex Indicates the port index.

PortState Indicates the port state.



The network topology will change.



606

Possible Causes1.

A new link was added to the network topology, and the link status of MSTP process changed.

2.

The network topology changes that the port changes from the Blocked state into the Forwardingstate.

Procedure

Step 1 View physical devices on the network to check whether new physical connections enabled withSTP are added.l If so, go to Step 2.l If not, go to Step 3.

Step 2 Check whether the added physical link is necessary.l If so, go to Step 3.l If not, go to Step 4.

Step 3 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether theinterfaces are consistent with the STP calculation results.l If so, go to Step 6.l If not, go to Step 5.

Step 4 Correctly deploy the network topology, and then check whether the alarm is cleared.l If the alarm is cleared, go to Step 6.l If the alarm is not cleared, go to Step 3.


Step 6 End.

----End


45.14 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.19hwMstpProNewPortStateDiscarding

DescriptionMSTP/4/PROPDISC:OID [oid] The MSTP Process's Port has been set to discarding state.(ProcessID=[INTEGER], InstanceID=[INTEGER], PortID1=[INTEGER], PortID2=



607

[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER], PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

The link status of MSTP process changed, and the port enters the Discarding state.

Attribute



Parameters

Name Meaning













The network topology will be changed.

Possible Causes

1.

The network topology changes that the port changes from the Forwarding state into theDiscarding state.

2.

A new link is added. After the topology calculation, the port enters the Discarding state.

Procedure




608













Step 6 End.

----End

Related Information

None.

45.15 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.20hwMstpProNewBridgeLostRootPrimary

Description

MSTP/1/PROROOT:OID [OID] MSTP process [process-id] is no longer the root bridge of theinstance [instance-id].

The original MSTP process lost its status as a root bridge. Another MSTP process with a higherpriority in the network replaced it and became the root bridge.

Attribute





609

Parameters

Name Meaning


process-id Indicates the MSTP process ID.

instance-id Indicates the instance ID.



Possible Causes

1.

A new link was added to the network topology, and the network topology changed. In addition,the newly-added device became the root bridge through the stp root primary command, withthe MAC address smaller than that of the previous root bridge.

2.

The priority of some switch changed in the network.

Procedure

















610


Step 6 Run the stp priority command to re-set the priority of the local bridge as required. Alternatively,run the undo stp priority command or the undo stp root command to restore the default priorityof the local bridge. Then, check whether the alarm is cleared.







Step 9 End.

----End

Related Information

None.

45.16 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.21hwMstpProNewPortRootGuarded

Description

MSTP/4/PRORGSUP:OID [oid] The MSTP process's instance's ROOT-Protection port receivedsuperior message. (ProcessID=[INTEGER], InstanceID=[INTEGER], PortID1=[INTEGER],PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER], PortIDFlag=[INTEGER],IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

An MSTP process with a higher priority outside the protection range of the root bridge attemptedto become the root bridge.

Attribute



Parameters

Name Meaning





611

Name Meaning












Possible Causes

1.

In the MSTP process, the port configured with the root protection function received BPDUs ofa higher priority than that of the bridge.

2.

The priorities of some MSTP processes changed in the network.

Procedure

Step 1 View physical devices on the network to check whether new physical connections enabled withSTP are added.l If so, go to Step 2.l If not, go to Step 4.

Step 2 Check whether the added physical link is necessary.l If so, go to Step 3.l If not, go to Step 7.

Step 3 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether theinterfaces are consistent with the STP calculation results.l If so, go to Step 11.l If not, go to Step 4.




612


Step 5 Check whether the operation of changing the priority is correct.l If so, go to Step 8.l If not, go to Step 6.

Step 6 Run the stp priority command to re-set the priority of the local bridge as required. Alternatively,run the undo stp priority command or the undo stp root command to restore the default valueof the priority of the local bridge. Then, check whether the alarm is cleared.l If so, go to Step 11.l If not, go to Step 8.

Step 7 Correctly deploy the network topology, and then check whether the alarm is cleared.l If so, go to Step 11.l If not, go to Step 8.

Step 8 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether aninterface is under the protection of the root bridge.l If so, go to Step 9.l If not, go to Step 10.

Step 9 Run the undo stp root-protection command in the interface view to disable the protection underthe root bridge. Then, check whether the alarm is cleared.l If so, go to Step 11.l If not, go to Step 10.


Step 11 End.

----End


45.17 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.22hwMstpProNewPortBpduGuarded

DescriptionMSTP/4/PROIVBPDU:OID [oid] The MSTP process's edged-port that enabled BPDU-Protection will be shutdown, because it received BPDU packet. (ProcessID=[INTEGER],InstanceID=[INTEGER], PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER],PortID4=[INTEGER], PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])



613

The port of MSTP process enabled with BPDU protection and connected to the user receivedBPDUs. These BPDUs are likely to be attack packets from the user.

Attribute



Parameters

Name Meaning













The user network connected to this port will be broken down.

Possible Causes

In the MSTP process, the edge port received BPDUs, and BPDU protection was enabled globally.

Procedure









614

Step 3 Run the undo stp root-protection and undo shutdown commands in the interface view to deletethe configuration of the edge port and restart the interface. Then, check whether the alarm iscleared.




Step 5 End.

----End

Related Information

None.

45.18 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.23hwMstpProNewPortLoopGuarded

Description

MSTP/4/PROLGEXP:OID [oid] The MSTP process's instance's LOOP-Protection port did notreceive BPDU packets in prescriptive time. (ProcessID=[INTEGER], InstanceID=[INTEGER],PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER],PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

A port of MSTP process enabled with loop protection failed to receive BPDUs within a specifiedperiod, and was set to be in the Discarding state.

Attribute



Parameters

Name Meaning








615

Name Meaning








The interface will not forward data.

Possible Causes

1.

The peer switch did not send the BPDUs to the local switch within the specified period. Thepossible cause was that the spanning tree function was disabled on the peer switch.

2.

The links connected to the peer were congested. Check whether the traffic was normal.

Procedure

Step 1 Run the display stp [ process process-id ] [ instance instance-id ] [ interface { interface-typeinterface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether STPis disabled on the interfaces that are directly connected.



Step 2 Check whether congestion occurs on the link between the local device and the neighbor device.



Step 3 Run the stp enable command in the interface view to enable STP. Then, check whether the alarmis cleared.









616

Step 6 End.

----End

Related Information

None.

45.19 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.24hwMstpProNewEdgePortChanged

Description

MSTP/4/PROEDGEDISABLE:OID [oid] When the port receives a BPDU packet, the edged-port attribute will be disabled. (ProcessID=[INTEGER], InstanceID=[INTEGER], PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER], PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

The edge port of MSTP process lost the attributes of an edge port after receiving BPDUs.

Attribute



Parameters

Name Meaning














617



Possible Causes

In the MSTP process, the edge port received BPDUs.

Procedure







Step 3 Run the undo stp edged-port command and then the undo shutdown command in the interfaceview to delete the configuration of the edge port and restart the interface. Then, check whetherthe alarm is cleared.




Step 5 End.

----End

Related Information

None.

45.20 MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.25hwMstpProLoopbackDetected

Description

MSTP/4/PROLBDETECTGED:OID [OID] The MSTP Process's Port has been set to discardingstate because of detecting loopback. (ProcessID=[INTEGER], InstanceID=[INTEGER],PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER],PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

When port detected loopback, block the port and arise trap.



618

Attribute



Parameters

Name Meaning













After detecting a port blocked by local loopback, the system considers that a network stormoccurs and blocks the local port to prevent the network storm from affecting services of the entirenetwork. Services on the block port will be interrupted.

Possible Causes

When the STP port of the equipment receiving BPDU with the same designated bridge ID anddesignated port ID as this equipment and port, STP blocks this port and arises this trap forloopback detection will lead loop.

Procedure

Step 1 Check whether the port where the alarm is generated is configured with local loopback.



Step 2 Check whether there is a loop formed by a hub and devices, one of which is connected to theport.





619


Step 4 Delete the local loopback configuration to solve the problem.

Step 5 Remove the self-loop network cable from the hub to solve the problem.

Step 6 End.

----End




620

46 NAP

About This Chapter

46.1 NAP_1.3.6.1.4.1.2011.5.25.206.3.1 hwNapStatusNotify

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 46 NAP


621

46.1 NAP_1.3.6.1.4.1.2011.5.25.206.3.1 hwNapStatusNotify

Description

NAP/4/NAP_STATUSCHANGE:OID [oid] Index [index-id], the status of the nap port[interface-name] has changed to [neighbor-status], and the AbnormalReason is [reason].

Neighbor information was changed, and an alarm was generated on the master node.

Attribute



Parameters

Name Meaning

oid Indicates the OID of a MIB object.

[index-id] Indicates the ID of an index.

[interface-name] Indicates the name of an interface.

[neighbor-status] Indicates the neighbor status.

[reason] Indicates the cause of an abnormality.


The trap message indicates that the sent NAP neighbor information is changed.

Possible Causes

The NAP neighbor information changed.

Procedure

Step 1 View the trap message and analyze the service operation.

----End

Related Information

None.

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 46 NAP


622

47 NQA

About This Chapter

47.1 NQA_1.3.6.1.2.1.80.0.1 pingProbeFailed

47.2 NQA_1.3.6.1.2.1.80.0.2 pingTestFailed

47.3 NQA_1.3.6.1.2.1.80.0.3 pingTestCompleted

47.4 NQA_1.3.6.1.2.1.81.0.2 traceRouteTestFailed

47.5 NQA_1.3.6.1.2.1.81.0.3 traceRouteTestCompleted

47.6 NQA_1.3.6.1.4.1.2011.5.25.111.6.1 nqaResultsProbeFailed

47.7 NQA_1.3.6.1.4.1.2011.5.25.111.6.2 nqaResultsTestFailed

47.8 NQA_1.3.6.1.4.1.2011.5.25.111.6.3 nqaResultsTestCompleted

47.9 NQA_1.3.6.1.4.1.2011.5.25.111.6.4 nqaResultsThresholdNotification

47.10 NQA_1.3.6.1.4.1.2011.5.25.111.6.5 nqaHTTPStatsProbeFailed

47.11 NQA_1.3.6.1.4.1.2011.5.25.111.6.6 nqaHTTPStatsTestFailed

47.12 NQA_1.3.6.1.4.1.2011.5.25.111.6.7 nqaHTTPStatsTestCompleted

47.13 NQA_1.3.6.1.4.1.2011.5.25.111.6.8 nqaHTTPStatsThresholdNotification

47.14 NQA_1.3.6.1.4.1.2011.5.25.111.6.10 nqaJitterStatsTestFailed

47.15 NQA_1.3.6.1.4.1.2011.5.25.111.6.11 nqaJitterStatsTestCompleted

47.16 NQA_1.3.6.1.4.1.2011.5.25.111.6.12 nqaFTPStatsProbeFailed

47.17 NQA_1.3.6.1.4.1.2011.5.25.111.6.13 nqaFTPStatsTestFailed

47.18 NQA_1.3.6.1.4.1.2011.5.25.111.6.14 nqaFTPStatsTestCompleted

47.19 NQA_1.3.6.1.4.1.2011.5.25.111.6.15 nqaFTPStatsThresholdNotification

47.20 NQA_1.3.6.1.4.1.2011.5.25.111.6.25 nqaJitterStatsJitterThresholdNotificationSD

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 47 NQA


623

47.21 NQA_1.3.6.1.4.1.2011.5.25.111.6.26 nqaJitterStatsJitterThresholdNotificationDS

47.22 NQA_1.3.6.1.4.1.2011.5.25.111.6.16 nqaJitterStatsRTDThresholdNotification

47.23 NQA_1.3.6.1.4.1.2011.5.25.111.6.17 nqaJitterStatsOWDThresholdNotificationSD

47.24 NQA_1.3.6.1.4.1.2011.5.25.111.6.18 nqaJitterStatsOWDThresholdNotificationDS



624

47.1 NQA_1.3.6.1.2.1.80.0.1 pingProbeFailed

Description

NQA/4/DISMANPINGPROBEFAIL:OID [oid] Ping entry probe failed. (Admin=[OCTET],Tag=[OCTET])

The trap was generated when the number of continuous probe failures in a test reached the setthreshold. The default threshold was 1. You can run the probe-failtimescommand to modifythe threshold.

Attribute


1.3.6.1.2.1.80.0.1 Warning communicationsAlarm(2)

Parameters

Name Meaning


Admin Indicates the index of the test administrator.

Tag Indicates the index of a test name.


None.

Possible Causes

This trap occurred in the NQA test.

1.

The destination address was inexistent and the route was unreachable.

2.

The destination address existed, but the route was unreachable.

3.

Because of the network delay, the Round Trip Time (RTT) of the packet was longer than the settimeout period.



625

Procedure

Step 1 Run the display this command in the NQA test view to check whether the destination addressis correctly configured. If not, run the destination-address command in the NQA test view tomodify the destination address.

Perform the test again to check whether the alarm is cleared.



Step 2 Run the ping command in the NQA test view to check whether the route is reachable.

l If the destination address is correctly configured, but the route is not reachable, run the displayip routing-table command to check the routing table and rectify the routing fault. If the testfails again, go to Step 4.

l If the route is reachable, go to Step 3.

Step 3 Run the timeout command in the NQA test view to modify the timeout period according to thestatus of the current network. It is recommended that you modify the timeout period to the defaultvalue, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds.You can run the display this command in the NQA test view to view the current timeout period.





Step 5 End.

----End

Related Information

None

47.2 NQA_1.3.6.1.2.1.80.0.2 pingTestFailed

Description

NQA/4/PINGFAIL:OID [oid] Ping entry test failed. (Admin=[OCTET], Tag=[OCTET])

The trap was generated when the number of continuous test failures reached the threshold. Thedefault threshold was 1. You can run the test-failtimes command to modify the threshold.

Attribute





626

Parameters

Name Meaning



Tag Indicates the index of the test name.


None.

Possible Causes


1.


2.


3.

Because of the network delay, the RTT of the packet was longer than the set timeout period.

Procedure






l If the destination address is correctly configured, but the route is not reachable, run thedisplay ip routing-table command to check the routing table and rectify the routing fault.If the test fails again, go to Step 4.







627



Step 5 End.

----End


47.3 NQA_1.3.6.1.2.1.80.0.3 pingTestCompleted

DescriptionNQA/4/PINGCOMPLETE:OID [oid] Ping entry test completed.(Admin=[OCTET], Tag=[OCTET])

A test succeeded.

Attribute



Parameters

Name Meaning





Possible CausesThis trap occurred in the NQA test.

The ping test succeeded.

Procedure


----End



628


47.4 NQA_1.3.6.1.2.1.81.0.2 traceRouteTestFailed

DescriptionNQA/4/TRACEROUTETESTFAIL:OID [oid] TraceRoute entry test failed. (Admin=[OCTET],Tag=[OCTET])

The trap was generated when the trace test failed.

Attribute



Parameters

Name Meaning






1.


2.


3.

The destination address existed and the route was reachable, but the number of hops betweenthe start and the destination exceeded the set number of the maximum hops.

4.

Because of the network delay, the RTT of the trace packet was longer than the set timeout period.



629

Procedure




Step 2 Run the ping command in the NQA test view to check whether the route is reachable.l If the destination address is correctly configured, but the route is not reachable, run the

display ip routing-table command to check the routing table and rectify the routing fault.If the test fails again, go to Step 5.


Step 3 Run the tracert-livetime command in the NQA test view to change the Time to Live (TTL) ofpackets according to the actual packet forwarding status. (Run the display this command in theNQA test view to view the curerent TTL value.) The TTL value ranges from 1 to 255. It isrecommended that the maximum number be 255.







Step 6 End.

----End


47.5 NQA_1.3.6.1.2.1.81.0.3 traceRouteTestCompleted

DescriptionNQA/4/TRACEROUTECOMPLETE:OID [oid] TraceRoute entry test completed.(Admin=[OCTET], Tag=[OCTET])



630

A trap was generated when the trace test succeeded.

Attribute



Parameters

Name Meaning





None.

Possible Causes

The NQA traceroute test succeeded.

Procedure


----End

Related Information

None

47.6 NQA_1.3.6.1.4.1.2011.5.25.111.6.1nqaResultsProbeFailed

Description

NQA/4/PROBEFAIL:OID [oid] NQA entry probe failed. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the number of continuous probe failures in a test reaches the set threshold. Thevalue of the default threshold was 1. The probe-failtimes command could modify the threshold.



631

Attribute



Parameters

Name Meaning


OwnerIndex Indicates the administrator of an NQA test instance.

TestName Indicates the name of an NQA test instance.


Possible CausesThis trap occurs in the NQA test.

1.

The destination address was inexistent and unreachable.

2.

The destination address exists, but the route was unreachable.

3.

Because of the network latency, the RTT of the packet was longer than the set timeout period.

Procedure




Step 2 Run the Ping command in the NQA test view to check whether the route is reachable.l If the destination address is correctly configured, but the route is not reachable, run the

display ip routing-table command to check and routing table and rectify the routing fault.If the test fails again, go to Step 4.


Step 3 Run the timeout command in the NQA test view to modify the timeout period according to thestatus of the current network. It is recommended that you modify the timeout period to the default



632

value, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds.You can run the display this command in the NQA test view to see the current timeout period.




Step 5 End.

----End


47.7 NQA_1.3.6.1.4.1.2011.5.25.111.6.2 nqaResultsTestFailed

DescriptionNQA/4/TESTFAIL:OID [oid] NQA entry test failed. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the number of continuous testing failures in a test instance reached the setthreshold. The value of the default threshold was 1, that is, a trap was generated right after eachtest failure. The test-failtimes command can modify the threshold.

Attribute



Parameters

Name Meaning








633

1.

The destination address was inexistent and unreachable.

2.


3.

Because of the network latency, the RTT of the Trace packet was longer than the set timeoutperiod.

Procedure





Step 2 Run the Ping command in the NQA test view to check whether the route is reachable.

l If the destination address is correctly configured, but the route is not reachable, run thedisplay ip routing-table command to check and routing table and rectify the routing fault.If the test fails again, go to Step 4.


Step 3 Run the timeout command in the NQA test view to modify the timeout period according to thestatus of the current network. It is recommended that you modify the timeout period to the defaultvalue, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds.You can run the display this command in the NQA test view to see the current timeout period.





Step 5 End.

----End

Related Information

None

47.8 NQA_1.3.6.1.4.1.2011.5.25.111.6.3nqaResultsTestCompleted



634

DescriptionNQA/4/TESTCOMPLETE:OID [oid] NQA entry test completed. (OwnerIndex=[OCTET],TestName=[OCTET])

Indicates that a test succeeded.

Attribute



Parameters

Name Meaning






The test succeeded.

Procedure


----End


47.9 NQA_1.3.6.1.4.1.2011.5.25.111.6.4nqaResultsThresholdNotification

DescriptionNQA/4/THRESHOLD:OID [oid] NQA entry over threshold. (OwnerIndex=[OCTET],TestName=[OCTET])



635

Indicates that the period of a test exceeded the set threshold. The threshold could be set by theuser. The threshold rtd could modify the threshold.

Attribute



Parameters

Name Meaning





None.

Possible Causes

This trap occurs in the NQA test.

1.

The threshold was set too small.

2.

The network was busy.

Procedure

Step 1 Run the display cpu-usage command in the system view to check whether the CPU has anexcessive usage.



Step 2 In the NQA test view, run the display this command to know the current threshold. Then runthe threshold rtd command to modify the threshold as required. The recommended value is 20ms.







636

Step 4 End.

----End


47.10 NQA_1.3.6.1.4.1.2011.5.25.111.6.5nqaHTTPStatsProbeFailed

DescriptionNQA/4/HTTPPROBEFAIL:OID [oid] NQA entry probe failed. (OwnerIndex=[OCTET],TestName=[OCTET])

Indicates that the number of continuous probe failures in a test reached the set threshold. Thevalue of the default threshold was 1. The probe-failtimes command could modify the threshold.

Attribute



Parameters

Name Meaning





Possible CausesThis alarm occurs in the NQA test.

1.

The destination address is inexistent and unreachable, causing the number of consecutive probefailures reaches the threshold.

2.

The destination address exists but is unroutable, causing the number of consecutive probefailures reaches the threshold.



637

3.

The destination address is an incorrect URL address, causing the connection establishment tobe failed.

4.

The destination address is a URL address but the DNS server is incorrectly configured, causingthe DNS resolution to be failed.

Procedure







l If the destination address is a URL address and the route is reachable, go to Step 3.

Step 3 Run the display this command in the NQA test view to check whether the http-url is correctlyconfigured. If not, run the http-url command in the NQA test view to modify the relatedparameters.




Step 4 Run the display this command in the NQA test view to check whether the DNS server is correctlyconfigured. If not, run the dns-server command in the NQA test view to modify the relatedparameters.











638

Step 7 End.

----End


47.11 NQA_1.3.6.1.4.1.2011.5.25.111.6.6nqaHTTPStatsTestFailed

DescriptionNQA/4/HTTPTESTFAIL:OID [oid] NQA entry test failed. (OwnerIndex=[OCTET],TestName=[OCTET])

Indicates that the number of testing failures in a test instance reached the set threshold. The valueof the default threshold was 1. The test-failtimes command could modify the threshold.

Attribute



Parameters

Name Meaning


OwnerIndex Indicates the administrator of an NQA test.



Possible CausesThis alarm occurs in the NQA test.

1.

The destination address is inexistent and unreachable, causing the number of consecutive probefailures reaches the threshold.

2.

The destination address exists but is unroutable, causing the number of consecutive probefailures reaches the threshold.



639

3.

The destination address is an incorrect URL address, causing the connection establishment tobe failed.

4.

The destination address is a URL address but the DNS server is incorrectly configured, causingthe DNS resolution to be failed.

Procedure







l If the destination address is a URL address and the route is reachable, go to Step 3.

Step 3 Run the display this command in the NQA test view to check whether the http-url is correctlyconfigured. If not, run the http-url command in the NQA test view to modify the relatedparameters.















640

Step 7 End.

----End

Related Information

None

47.12 NQA_1.3.6.1.4.1.2011.5.25.111.6.7nqaHTTPStatsTestCompleted

Description

NQA/4/HTTPCOMPLETE:OID [oid] NQA entry test completed. (OwnerIndex=[OCTET],TestName=[OCTET])


Attribute



Parameters

Name Meaning





None.

Possible Causes


The test succeeded.

Procedure


----End



641


47.13 NQA_1.3.6.1.4.1.2011.5.25.111.6.8nqaHTTPStatsThresholdNotification

DescriptionNQA/4/HTTPTHRESHOLD:OID [oid] NQA entry over threshold. (OwnerIndex=[OCTET],TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by theuser. The threshold rtd command could modify the threshold.

Attribute



Parameters

Name Meaning






1.


2.


Procedure

Step 1 Run the display cpu-usage command in the system view to check whether the CPU has anexcessive load.



642






Step 4 End.

----End


47.14 NQA_1.3.6.1.4.1.2011.5.25.111.6.10nqaJitterStatsTestFailed

DescriptionNQA/4/JITTERTESTFAIL:OID [oid] NQA entry test failed. (OwnerIndex=[OCTET],TestName=[OCTET])


Attribute



Parameters

Name Meaning







643

Possible Causes


1.

The destination address was inexistent and unreachable. The number of continuous test failuresin a test reached the set threshold.

2.

The destination address existed, but the route was unreachable. The number of continuous testfailures in a test reached the set threshold.

3.

The destination port was not correctly configured, which led to the connection failure.

NOTE

The Jitter Version 1 did not check the destination port. Whether the server was configured or not, the testsucceeded.

Procedure








Step 3 Run the display this command in the NQA test view to check whether the destination port iscorrectly configured. If not, run the destination-port command in the NQA test view to modifythe related parameters.




Step 4 Run the display this command in the system view to check the Jitter's version.

l If the Jitter's version is 1, go to Step 7.

l If the Jitter's version is 2, go to Step 5.

Step 5 Run the display nqa-server command in the System view to check whether the server port iscorrectly configured.



644



Step 6 Run the nqa-server udpecho in the system view to modify the server. Restart the test instance.





Step 8 End.

----End

Related Information

None

47.15 NQA_1.3.6.1.4.1.2011.5.25.111.6.11nqaJitterStatsTestCompleted

Description

NQA/4/JITTERCOMPLETE:OID [oid] NQA entry test completed. (OwnerIndex=[OCTET],TestName=[OCTET])


Attribute



Parameters

Name Meaning





None.



645


The test succeeded.

Procedure


----End


47.16 NQA_1.3.6.1.4.1.2011.5.25.111.6.12nqaFTPStatsProbeFailed

DescriptionNQA/4/FTPPROBEFAIL:OID [oid] NQA entry probe failed. (OwnerIndex=[OCTET],TestName=[OCTET])

Indicates that the number of continuous probe failures in a test reached the set threshold. Thedefault threshold was 1. The probe-failtimes command could modify the threshold.

Attribute



Parameters

Name Meaning








646

1.

The destination address was inexistent and unreachable, and thus the number of continuous probefailures in a test reached the set threshold.

2.

The destination address existed, but the route was unreachable, and thus the number ofcontinuous probe failures in a test reached the set threshold.

3.

The source address was incorrect, and thus the number of continuous probe failures in a testreached the set threshold.

4.

The user name or password was incorrect; the file name was inexistent.

5.

The FTP service was not enabled.

6.

The file was oversized, and could not be transmitted within a specified period.

Procedure




Step 2 Run the Ping command in the NQA test view to check whether the route is reachable.l If the destination address is correctly configured, but the route is not reachable, run the

display ip routing-table command to check and routing table and rectify the routing fault.If the test fail again, go to Step 3.


Step 3 Run the display this command in the NQA test view to check whether the source address iscorrectly configured. If not, run the source-address command in the NQA test view to modifythe source address.



Step 4 Run the display this command in the NQA test view to check whether the FTP user name iscorrectly configured. If not, run the ftp-username command in the NQA test view to modifythe related parameters.




647



Step 5 Run the display this command in the NQA test view to check whether the FTP password iscorrectly configured. If not, run the ftp-password command in the NQA test view to modifythe related parameters.



Step 6 Run the display this command in the NQA test view to check whether the FTP file name iscorrectly configured. If not, run the ftp-filename command in the NQA test view to modify therelated parameters.




Step 7 Run the display ftp-server command on the FTP server to check whether the FTP service isenabled. If not, run the ftp server enable command in the system to enable the FTP service.




Step 8 The file is oversized, and cannot be transmitted within a specified period. Run the timeoutcommand in the NQA test view to modify the timeout period. The value ranges from 1 to 60.You can run the display this command in the NQA test view to view the current timeout period.Restart the test instance.





Step 10 End.

----End

Related Information

None

47.17 NQA_1.3.6.1.4.1.2011.5.25.111.6.13nqaFTPStatsTestFailed



648

Description

NQA/4/FTPFAIL:OID [oid] NQA entry test failed. (OwnerIndex=[OCTET], TestName=[OCTET])


Attribute



Parameters

Name Meaning





None.

Possible Causes


1.

The destination address was inexistent and unreachable. The number of continuous test failuresin a test reached the set threshold.

2.

The destination address existed, but the route was unreachable. The number of continuous testfailures in a test reached the set threshold.

3.

The user name or password was incorrect; the file name was inexistent.

4.

The FTP service was not enabled.

5.

The file was oversized, and could not be transmitted with a specified period.



649

Procedure








Step 3 Run the display this command in the NQA test view to check whether the FTP user name iscorrectly configured. If not, run the ftp-username command in the NQA test view to modifythe related parameters.




Step 4 Run the display this command in the NQA test view to check whether the FTP password iscorrectly configured. If not, run the ftp-password command in the NQA test view to modifythe related parameters.




Step 5 Run the display this command in the NQA test view to check whether the FTP file name iscorrectly configured. If not, run the ftp-filename command in the NQA test view to modify therelated parameters.




Step 6 Run the display ftp-server command on the FTP server to check whether the FTP service isenabled. If not, run the ftp server enable command in the system to enable the FTP service.




Step 7 The file is oversized, and cannot be transmitted within a specified period. Run the timeoutcommand in the NQA test view to modify the timeout period. The value ranges from 1 to 60.You can run the display this command in the NQA test view to view the current timeout period.



650





Step 9 End.

----End

Related Information

None

47.18 NQA_1.3.6.1.4.1.2011.5.25.111.6.14nqaFTPStatsTestCompleted

Description

NQA/4/FTPCOMPLETE:OID [oid] NQA entry test completed. (OwnerIndex=[OCTET],TestName=[OCTET])


Attribute



Parameters

Name Meaning


OwnerIndex Indicates the index of an NQA test instance.



None.

Possible Causes


The test succeeded.



651

Procedure


----End


47.19 NQA_1.3.6.1.4.1.2011.5.25.111.6.15nqaFTPStatsThresholdNotification

DescriptionNQA/4/FTPTHRESHOLD:OID [oid] NQA entry over threshold. (OwnerIndex=[OCTET],TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by theuser. The threshold rtd command could modify the threshold.

Attribute



Parameters

Name Meaning






1.


2.




652

Procedure

Step 1 Run the display cpu-usage command in the system view to check whether the CPU has anexcessive load.l If so, go to Step 3.l If not, go to Step 2.





Step 4 End.

----End


47.20 NQA_1.3.6.1.4.1.2011.5.25.111.6.25nqaJitterStatsJitterThresholdNotificationSD

DescriptionNQA/4/JITTERSDTHRESHOLD:OID [oid] NQA entry Jitter-SD over threshold.(OwnerIndex=[OCTET], TestName=[OCTET])

The jitter from the source to the destination exceeded the set threshold.

Attribute


NQA_1.3.6.1.4.1.2011.5.25.111.6.25 Warning qualityOfServiceAlarm(3)

Parameters

Name Meaning


OwnerIndex Manager of an NQA test instance

TestName Name of a test in an NQA test instance



653



Possible Causes

The jitter from the source to the destination exceeded the set threshold.

Procedure

Step 1 Cancel configurations for the jitter threshold from the source to the destination.

----End

Related Information

None.

47.21 NQA_1.3.6.1.4.1.2011.5.25.111.6.26nqaJitterStatsJitterThresholdNotificationDS

Description

NQA/4/JITTERDSTHRESHOLD:OID [oid] NQA entry Jitter-DS over threshold.(OwnerIndex=[OCTET], TestName=[OCTET])

The jitter from the the destination to the source exceeded the set threshold.

Attribute


NQA_1.3.6.1.4.1.2011.5.25.111.6.26 Warning qualityOfServiceAlarm(3)

Parameters

Name Meaning


OwnerIndex Manager of an NQA test instance

TestName Name of a test in an NQA test instance





654

Possible CausesThe jitter from the the destination to the source exceeded the set threshold.

Procedure

Step 1 Delete the configured jitter threshold from the destination to the source.

----End


47.22 NQA_1.3.6.1.4.1.2011.5.25.111.6.16nqaJitterStatsRTDThresholdNotification

DescriptionNQA/4/RTDTHRESHOLD:OID [oid] NQA entry RTD over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by theuser. You can run the threshold rtd command to modify the threshold.

Attribute



Parameters

Name Meaning






1.



655


2.


Procedure









Step 4 End.

----End

Related Information

None

47.23 NQA_1.3.6.1.4.1.2011.5.25.111.6.17nqaJitterStatsOWDThresholdNotificationSD

Description

NQA/4/SDTHRESHOLD:OID [oid] NQA entry OWD-SD over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by theuser. The threshold owd-sd command could modify the threshold.

Attribute





656

Parameters

Name Meaning





None.

Possible Causes


1.


2.


Procedure




Step 2 In the NQA test view, run the display this command to know the current threshold. Then runthe threshold owd-sd command to modify the threshold as required. The recommended valueis 20 ms.





Step 4 End.

----End

Related Information

None



657

47.24 NQA_1.3.6.1.4.1.2011.5.25.111.6.18nqaJitterStatsOWDThresholdNotificationDS

DescriptionNQA/4/DSTHRESHOLD:OID [oid] NQA entry OWD-DS over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by theuser. The threshold owd-ds command could modify the threshold.

Attribute



Parameters

Name Meaning






1.


2.


Procedure

Step 1 Run the display cpu-usage command in the system view to check whether the CPU has anexcessive load.l If so, go to Step 3.l If not, go to Step 2.



658

Step 2 In the NQA test view, run the display this command to know the current threshold. Then runthe threshold owd-ds command to modify the threshold as required. The recommended valueis 20 ms.




Step 4 End.

----End




659

48 OSPF

About This Chapter

48.1 OSPF_1.3.6.1.2.1.14.16.2.1 ospfVirtIfStateChange

48.2 OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange

48.3 OSPF_1.3.6.1.2.1.14.16.2.3 ospfVirtNbrStateChange

48.4 OSPF_1.3.6.1.2.1.14.16.2.4 ospfIfConfigError

48.5 OSPF_1.3.6.1.2.1.14.16.2.5 ospfVirtIfConfigError

48.6 OSPF_1.3.6.1.2.1.14.16.2.6 ospfIfAuthFailure

48.7 OSPF_1.3.6.1.2.1.14.16.2.7 ospfVirtIfAuthFailure

48.8 OSPF_1.3.6.1.2.1.14.16.2.8 ospfIfRxBadPacket

48.9 OSPF_1.3.6.1.2.1.14.16.2.9 ospfVirtIfRxBadPacket

48.10 OSPF_1.3.6.1.2.1.14.16.2.10 ospfTxRetransmit

48.11 OSPF_1.3.6.1.2.1.14.16.2.11 ospfVirtIfTxRetransmit

48.12 OSPF_1.3.6.1.2.1.14.16.2.12 ospfOriginateLsa

48.13 OSPF_1.3.6.1.2.1.14.16.2.13 ospfMaxAgeLsa

48.14 OSPF_1.3.6.1.2.1.14.16.2.14 ospfLsdbOverflow

48.15 OSPF_1.3.6.1.2.1.14.16.2.15 ospfLsdbApproachingOverflow

48.16 OSPF_1.3.6.1.2.1.14.16.2.16 ospfIfStateChange

48.17 OSPF_1.3.6.1.2.1.14.16.2.17 ospfNSSATranslatorStatusChange

48.18 OSPF_1.3.6.1.2.1.14.16.2.18 ospfRestartStatusChange

48.19 OSPF_1.3.6.1.2.1.14.16.2.19 ospfNbrRestartHelperStatusChange

48.20 OSPF_1.3.6.1.2.1.14.16.2.20 ospfVirtNbrRestartHelperStatusChange

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 48 OSPF


660

48.21 OSPF_1.3.6.1.4.1.2011.5.25.155.31.3 hwOspfv2IntraAreaRouteridConflict

48.22 OSPF_1.3.6.1.4.1.2011.5.25.155.31.4 hwOspfv2IntraAreaDRIpAddressConflict



661

48.1 OSPF_1.3.6.1.2.1.14.16.2.1 ospfVirtIfStateChange

Description

OSPF/3/VIFCHG:OID [oid]: The status of the virtual interface changes. (VirtIfAreaId=[area-id], VirtIfNeighbor=[neighbor-router-id], ProcessId=[process-id], RouterId=[router-id],VirtIfState=[neighbor-state], InstanceName=[instance-name])

The interface status of the OSPF virtual link changed. The possible cause was that the router IDof the neighbor changed after the virtual link was configured or the status of the physical interfaceof the virtual link changed.

Attribute


1.3.6.1.2.1.14.16.2.1 Minor environmentalAlarm (6)

Parameters

Name Meaning


VirtIfAreaId Indicates the area ID.

VirtIfNeighbor Indicates the router ID of the neighbor on the virtual link.

ProcessId Indicates the process ID.

RouterId Indicates the router ID of the local switch.

VirtIfState Indicates the status of the neighboring interface.l 1: Downl 2: Loopbackl 3: Waitingl 4: Point-to-Pointl 5: DRl 6: Backupl 7: DROther

InstanceName Indicates the instance name.



662

Impact on the SystemIf the interface status of the virtual link changes from Down to P2P (Point-to-Point), this trapmessage is informational only, and no action is required. If the interface status of the virtual linkchanges from P2P to Down, the virtual link will be disconnected, the OSPF route calculationwill be incorrect, and services may be interrupted.

Possible Causes1. The status of the physical interface of the virtual link changed.

2. Router ID of the neighbor on the virtual link changed.

Procedure

Step 1 Run the display ospf vlink command to check whether the interface status of the virtual link isP2P.l If so, it indicates that this trap message is informational only, and no action is required. Go

to Step 4.l If not, go to Step 2.

Step 2 Run the display ospf process-id routing router-id neighbor-router-id command to checkwhether the area has the route to the remote switch.l If so, collect the configuration of the remote switch, and go to Step 3.l If not, run the display ospf interface command to check whether the status of the local

interface is Down.

– If so, run the display rm interface or display ip interface command to check whetherthe local interface goes Down.

– If so, collect interface information, and go to Step 3.

– If not, collect log information, and go to Step 3

– If not, collect the configuration of the remote switch, and go to Step 3.


Step 4 End.

----End


48.2 OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange

DescriptionOSPF/2/NBRCHG:OID [oid]: The status of the non-virtual neighbor changes. (NbrIpAddress=[neighbor-ip-address], NbrAddressLessIndex=[neighbor-interface-index], ProcessId=[process-id], AreaId=[area-id], IfnetIndex=[interface-ifnet-index], LocalIfIpAddress=[local-ip-address],



663

ProcessId=[process-id], RouterId=[router-id], NbrRtrId=[neighbor-router-id], NbrState=[neighbor-state], IfName=[interface-name], InstanceName=[instance-name], NbrChgReason=[NbrStateChangeReason])

The status of the OSPF neighbor changed. The possible cause was that the status of the interfaceof the neighbor changed or the contents of the received Hello packets changed.

Attribute


1.3.6.1.2.1.14.16.2.2 Major environmentalAlarm (6)

Parameters

Name Meaning


NbrIpAddress Indicates the IP address of the neighbor.

NbrAddressLessIndex Indicates the index of a neighboring interface.


AreaId Indicates the area ID of the NSSA.

IfnetIndex Indicates the Ifnet index of the interface.

LocalIfIpAddress Indicates the IP address of the local switch.



NbrRtrId Indicates the router ID of the neighbor.



664

Name Meaning

NbrState Indicates the status of the neighbor.l 1: Downl 2: Attemptl 3: Initl 4: 2Wayl 5: ExStartl 6: Exchangel 7: Loadingl 8: Full

IfName Indicates the name of interface.


NbrChgReason Indicates the reason why the neighbor status changes:l 1 (adjacencyHoldTimerExpired): indicates that the timer of the

adjacent router times out.l 2 (physicalInterfaceChange): indicates that the status of the

physical interface on the router changes.l 3 (ospfProtocolReason): indicates that an alarm is generated

because of the OSPF protocol.l 4 (bfdSessionStateChange): indicates that the BFD session is

closed.l 5 (configureChange): indicates that the OSPF configuration

changes.l 6 (peerRouterReason): indicates that an alarm is generated because

of the neighboring router.l 100 (alarmCleared): indicates that the alarm is cleared because

services are restored or the neighbor is deleted.


When the status of the neighbor (not a neighbor of a virtual link) changes, this trap message willbe sent. This trap message indicates the status of the neighbor changes. If the neighbor changesfrom a lower status to a higher status, this trap message is informational only, and no action isrequired. If the neighbor changes from a higher status to a lower status, services may beinterrupted. (The state transition of the OSPF neighbor in an ascending order is: Down -> Init -> 2-way -> Exstart -> Exchange -> Loading -> Full).

Possible Causes

1. The status of the interface of the neighbor changed.



665

2. The configured parameters (such as Hello timer, dead timer, interface authentication, andnetwork type) of the interfaces that set up the neighbor relationship were inconsistent.

3. OSPF was restarted by using the reset ospf process command.

4. An error packet was received.

5. The overflow function is configured and the process entered the Overflow state.

6. The ping operation failed, which indicated that an error occurred during the transmission ofthe packet.

Procedure

Step 1 Run the display ospf peer command to check the neighbor status. If the neighbor is in the Fullstate, go to Step 7; otherwise, go to Step 2.

Step 2 Run the display ip interface interface-type interface-number command to check whether theinterface of the neighbor is in the Down state.l If the physical interface is Up, go to Step 3.l If the physical interface is Down, check whether the shutdown command is configured on

the interface and the link.

– If this command is configured, run the undo shutdown command and then go to Step 3.

– If this command is not configured, go to Step 8.

Step 3 Check whether the packet is correctly forwarded and ping the IP address of the remote interface.l If the ping fails, go to Step 7.l If the ping succeeds, go to Step 4.

Step 4 Run the display ospf interface interface-type interface-number command to view the state fieldand check whether the interface where the OSPF neighbor resides is in the Down state.l If the interface is in the Down state, go to Step 7.l If the interface is in another state, go to Step 5.

Step 5 Run the display ospf interface interface-type interface-number command to check whether theconfigurations (including the hello interval, dead interval, poll interval, and OSPF network-type)on the two ends of the link are consistent and whether the interface on one end is not an OSPFinterface.l If so, go to Step 6.l If not, modify the configurations to make them consistent. Then check whether the trap is

cleared.


– If not, run the following commands to modify interface configurations on the two endsto be consistent.

– ospf timer hello interval– ospf timer dead interval– ospf timer poll interval– ospf network-type { broadcast | nbma | p2mp | p2p }Then, check whether the trap is cleared.



666


– If not , go to Step 7.

Step 6 Run the display current-configuration interface interface-type interface-number command tocheck whether the interface authentication configurations on the two ends are consistent.l If so, go to Step 7.l If not, run the following commands to modify interface configurations on the two ends to be

consistent.

– ospf authentication-mode simple [ [ plain ] plain-text | cipher cipher-text ]– ospf authentication-mode { md5 | hmac-md5 } [ key-id { plain plain-text | [ cipher ]

cipher-text } ]

– ospf authentication-mode nullThen, check whether the trap is cleared.

– Y=>8.

– N=>7.

Step 7 Collect the trap information, log information, and configuration of the switch and the neighborswitch, and contact Huawei technical personnel.

Step 8 End.

----End


48.3 OSPF_1.3.6.1.2.1.14.16.2.3 ospfVirtNbrStateChange

DescriptionOSPF/3/NBBRCHG:OID [oid]: The status of the virtual neighbor changes. (VirtNbrArea=[area-id], VirtNbrRtrId=[neighbor-router-id], ProcessId=[process-id], RouterId=[router-id],VirtNbrState=[neighbor-state], InstanceName=[instance-name])

The status of the neighbor on the OSPF virtual link changed because the interface status of thevirtual link changed.

Attribute





667

Parameters

Name Meaning


VirtNbrArea Indicates the area ID.

VirtNbrRtrId Indicates the router ID of the neighbor on the virtual link.


RouterId Indicates the ID of the local switch.

VirtNbrState Indicates the status of the neighbor.l 1: Downl 2: Attemptl 3: Initl 4: 2Wayl 5: ExStartl 6: Exchangel 7: Loadingl 8: Full


Impact on the SystemThis trap message will be generated when the status of the neighbor on the virtual link changes.If the status of the neighbor on the virtual link changes from Full to lower than Full, routes areincorrectly installed to the routing table, or some routes are wrongly deleted. This may affectservices.


2. The configured parameters (such as Hello timer, dead timer and interface authentication) ofthe interfaces that set up the neighbor relationship were inconsistent.

3. OSPF was restarted by using the reset ospf process command or the active/standby switchoverwas performed.

4. An error packet was received.

5. The overflow function is configured and the process entered the Overflow state.

6. Routes of the area configured with the virtual link were added or deleted.



668

7. The ping operation failed, which indicated that an error occurred during the transmission ofthe packet.

Procedure

Step 1 Run the display ospf interface and display ip interfacebrief commands to check whether thestatus of the interface used to establish the virtual link is normal.

l If the physical interface is Down, check whether the link or interface is configured with theshutdown command.

l If the protocol status of the interface is Down, check whether the interface is configured withan IP address.

If the interface status is normal, go to Step 2.

Step 2 Run the display ospf peer command to check whether the OSPF neighbor relationship is normal.

l If the neighbor relationship is abnormal, check whether trap 1.3.6.1.2.1.14.16.2.2 exists. Ifthe trap exists, locate the problem according to the trap. If the trap does not exist, go to Step6.

l If the neighbor relationship is normal, go to Step 3.

Step 3 Run the display ospf routing router-id [ router-id ] command to check whether the switchobject exists. router-id indicates the IP address of the neighbor on the virtual link.

l If the route does not exist, go to Step 4.

l If the route exists, go to Step 5.

Step 4 Configure the route to the neighbor of the virtual link. Then check whether the trap is cleared.



Step 5 Run the display ospf vlink and display current- configuration configuration ospf commandsto check whether the configurations (including the Hello interval, Dead interval, and pollinterval) on the two ends of the virtual link are consistent.

l If the configurations are correct, check whether trap 1.3.6.1.2.1.14.16.2.14 exists.

– If the trap exists, rectify the fault according to the related procedure of the trap.

– If the trap does not exist, go to Step 6.

l If not, run the following command to modify the configurations on the two ends to beconsistent.

– vlink-peer router-id [ smart-discover ] [ hello hello-interval | retransmit retransmit-interval | trans-delay trans-delay-interval | dead dead-interval ] * [ simple [ [ plain ]plain-text | cipher cipher-text ] | { md5 | hmac-md5 } [ key-id [ plain plain-text |[ cipher ] cipher-text ] | authentication-null ] ]

Then, check whether the trap is cleared.






669

Step 7 End.

----End

Related Information

None

48.4 OSPF_1.3.6.1.2.1.14.16.2.4 ospfIfConfigError

Description

OSPF/2/IFCFGERR:OID [oid]: A packet is received on the non-virtual interface from a routerwhose configuration conflicts with the local configuration. (IfIpAddress=[ip-address],AddressLessIf=[interface-index], ProcessId=[process-id], RouterId=[router-id], PacketSrc=[source-ip-address], ConfigErrorType=[error-type], PacketType=[packet-type],InstanceName=[instance-name])

The configurations of the OSPF interfaces that set up the neighbor relationship were inconsistent.The possible cause was that the values of the Hello timer, dead timer, poll timer were notconsistent on the two interfaces or the two interfaces were not in the same area.

Attribute



Parameters

Name Meaning


IfIpAddress Indicates the IP address of non-virtual-link interface.

AddressLessIf Indicates the index of the interface.



PacketSrc Indicates the source IP address of the packet.



670

Name Meaning

ConfigErrorType Indicates the error type.l 1: Bad Versionl 2: Area Mismatchl 3: Unknown Nbma Neighbourl 4: Unknown Virtual Neighbourl 7: NetMask Mismatchl 8: Hello Interval Mismatchl 9: Dead Interval Mismatchl 10: Option Mismatchl 11: Mtu Mismatchl 12: Duplicate RouterId

PacketType Indicates the type of the packet.l 1: Hello packetl 2: DD packetl 3: Request packetl 4: Update packetl 5: Acknowledgement packetl 6: Update packet Retransl 7: Update packet flood



This trap message is generated after an interface receives a packet indicating parameters areincorrectly configured.

Possible Causes

1. Parameters configured on the two interfaces were inconsistent.

2. The routing protocol on the link layer changed.

Procedure

Step 1 Run the display ospf interface interface-type interface-number command to check whether theconfigurations on the two interfaces are consistent.



Step 2 Perform the following operations according to the networking:



671

l If it is allowed to modify the configurations on the two interfaces to be consistent, run thefollowing commands to modify the configurations on the two interfaces to be consistent.

– ospf timer hello interval

– ospf timer dead interval

– ospf timer poll interval

Then, check whether the trap is cleared.



l If it is not allowed to modify the configurations on the two interfaces to be consistent, go toStep 3.


Step 4 End.

----End

Related Information

None

48.5 OSPF_1.3.6.1.2.1.14.16.2.5 ospfVirtIfConfigError

Description

OSPF/3/VIFCFGERR:OID [oid]: A packet is received on the virtual interface from a routerwhose configuration conflicts with the local configuration. (VirtIfAreaId=[area-id],VirtIfNeighbor=[neighbor-router-id], ProcessId=[process-id], RouterId=[router-id],ConfigErrorType=[error-type], PacketType=[packet-type], InstanceName=[instance-name])

Configurations of the interfaces on the two ends of the virtual link were incorrect. The possiblecause was that the configurations of the parameters conflicted.

Attribute


1.3.6.1.2.1.14.16.2.5 Minor processingErrorAlarm (4)

Parameters

Name Meaning




672

Name Meaning





ConfigErrorType Indicates the error type.l 1: Bad Versionl 2: Area Mismatchl 3: Unknown Nbma Neighbourl 4: Unknown Virtual Neighbourl 7: NetMask Mismatchl 8: Hello Interval Mismatchl 9: Dead Interval Mismatchl 10: Option Mismatchl 11: Mtu Mismatchl 12: Duplicate RouterId



Impact on the SystemThis trap message is generated after the virtual interface receives a packet indicating parametersare incorrectly configured.

Possible CausesThe configurations of the interfaces on the two ends of the virtual link conflicted.



673

Procedure

Step 1 Run the display ospf vlink and display current- configuration configuration commands tocheck whether the configurations of the two interfaces are consistent.l If so, go to Step 3.l If not, go to Step 2.

Step 2 Perform the following operations according to the networking:l If it is allowed to modify the configurations on the two interfaces to be consistent, run the

following command to modify the configurations on the two interfaces to be consistent.

– vlink-peer router-id [ smart-discover ] [ hello hello-interval | retransmit retransmit-interval | trans-delay trans-delay-interval | dead dead-interval ] * [ simple [ [ plain ]plain-text | cipher cipher-text ] | { md5 | hmac-md5 } [ key-id [ plain plain-text |[ cipher ] cipher-text ] | authentication-null ] ]

Then, check whether the tap is cleared.


– If not, go to Step 3.l If it is not allowed to modify the configurations on the two interfaces to be consistent, go to

Step 3.


Step 4 End.

----End


48.6 OSPF_1.3.6.1.2.1.14.16.2.6 ospfIfAuthFailure

DescriptionOSPF/2/IFAUTFAIL:OID [oid]: A packet is received on a non-virtual interface from a routerwhose authentication key or authentication type conflicts with the local authentication key orauthentication type. (IfIpAddress=[ip-address], AddressLessIf=[interface-index], ProcessId=[process-id], RouterId=[router-id], PacketSrc=[source-ip-address], ConfigErrorType=[error-type], PacketType=[packet-type], InstanceName=[instance-name])

The non-virtual-link interface authentication failed. The possible cause was that theconfiguration of the non-virtual-link interface authentication was incorrect.



674

Attribute



Parameters

Name Meaning


IfIpAddress Indicates the IP address of the non-virtual-link interface.





ConfigErrorType Indicates the error type.l 5: Auth type Mismatchl 6: Auth Failure



Impact on the SystemThis trap message is generated after an interface receives a packet indicating authenticationparameters are incorrectly configured.

Possible CausesThe configuration of interface authentication was incorrect.



675

ProcedureStep 1 Run the display current-configuration configuration ospf command to check whether area

authentication configurations on the two switchs are consistent, and the display current-configuration interface interface-type interface-number command to check whether theinterface authentication configurations on the two ends are consistent. The interfaceauthentication takes precedence over the area authentication.l If so, go to Step 3.l If not, go to Step 2.

Step 2 Perform the following operations according to the networking:l If it is allowed to modify the configurations on the two ends to be consistent, go to Step 3.l If it is not allowed to modify the configurations on the two interfaces to be consistent, go to

Step 4.

Step 3 If the authentication is in plain text, modify the authentication password. If the authenticationis in cipher text, run the following commands to reconfigure the authentication on the twointerfaces as required.

Configure the interface authentication:

l ospf authentication-mode simple [ [ plain ] plain-text | cipher cipher-text ]l ospf authentication-mode { md5 | hmac-md5 } [ key-id { plain plain-text | [ cipher ]

cipher-text } ]

Configure the area authentication:

l authentication-mode simple [ [ plain ] plain-text | cipher cipher-text ]l authentication-mode { md5 | hmac-md5 } [ key-id { plain plain-text | [cipher ] cipher-

text } ]

Check whether the trap is cleared.



Step 5 End.

----End


48.7 OSPF_1.3.6.1.2.1.14.16.2.7 ospfVirtIfAuthFailure

DescriptionOSPF/3/VIFAUTFAIL:OID [oid]: A packet is received on a virtual interface from a routerwhose authentication key or authentication type conflicts with the local authentication key or



676

authentication type. (VirtIfAreaId=[area-id], VirtIfNeighbor=[neighbor-router-id], ProcessId=[process-id], RouterId=[router-id], ConfigErrorType=[error-type], PacketType=[packet-type],InstanceName=[instance-name])

The virtual-link interface authentication failed. The possible cause was that the configuration ofthe virtual-link interface authentication was incorrect.

Attribute



Parameters

Name Meaning






ConfigErrorType Indicates the error type.l 5: Auth type Mismatchl 6: Auth Failure



Impact on the SystemThis trap message is generated after the virtual link interface receives a packet indicatingauthentication parameters are incorrectly configured.



677

Possible Causes

The configuration of authentication of the virtual link interface was incorrect.

Procedure

Step 1 Run the display current-configuration configuration ospf command to check whether theinterface authentication configurations on the two ends of the virtual link are consistent.




l If it is allowed to modify the configurations on the two ends to be consistent, go to Step 3.

l If it is not allowed to modify the configurations on the two interfaces to be consistent, go toStep 4.

Step 3 If the authentication is in plain text, modify the authentication password. If the authenticationis in cipher text, run the following command to reconfigure the authentication on the twointerfaces as required.

l vlink-peer router-id [ smart-discover ] [ hello hello-interval | retransmit retransmit-interval | trans-delay trans-delay-interval | dead dead-interval ] * [ simple [ [ plain ] plain-text | cipher cipher-text ] | { md5 | hmac-md5 } [ key-id [ plain plain-text | [ cipher ] cipher-text ] | authentication-null ] ]

Check whether the trap is cleared.




Step 5 End.

----End

Related Information

None

48.8 OSPF_1.3.6.1.2.1.14.16.2.8 ospfIfRxBadPacket

Description

OSPF/4/IFBADRX:OID [oid]: An OSPF packet that is received on a non-virtual interface cannotbe parsed. (IfIpAddress=[ip-address], AddressLessIf=[interface-index], ProcessId=[process-id], RouterId=[router-id], PacketSrc=[source-ip-address], PacketType=[packet-type],InstanceName=[instance-name])



678

An OSPF packet that cannot be parsed was received from a non-virtual-link interface. Thepossible cause was that the device was attacked or the interconnection between the Huaweidevice and non-Huawei device failed.

Attribute


1.3.6.1.2.1.14.16.2.8 Warning environmentalAlarm (6)

Parameters

Name Meaning










This trap message is generated when a common interface receives an incorrect packet and thendiscards this packet. This may cause the neighbor to be Down.

Possible Causes

An incorrect packet was received from the non virtual-link interface on the peer end.



679

Procedure


Step 2 End.

----End

Related Information

None

48.9 OSPF_1.3.6.1.2.1.14.16.2.9 ospfVirtIfRxBadPacket

Description

OSPF/4/VIFBADRX:OID [oid]: An OSPF packet that is received on a virtual interface cannotbe parsed. (VirtIfAreaId=[area-id], VirtIfNeighbor=[neighbor-router-id], ProcessId=[process-id], RouterId=[router-id], PacketType=[packet-type], InstanceName=[instance-name])

An OSPF packet that cannot be parsed was received from a virtual-link interface. The possiblecause was that the device was attacked or the interconnection between the Huawei device andnon-Huawei device failed.

Attribute



Parameters

Name Meaning








680

Name Meaning

PacketType Indicates the type of a packet.

l 1: Hello packetl 2: DD packetl 3: Request packetl 4: Update packetl 5: Acknowledgement packetl 6: Update packet Retransl 7: Update packet flood


Impact on the SystemThis trap message is generated when a virtual-link interface receives a packet that cannot beparsed and then discards this packet. This may cause the neighbor to be Down.

Possible CausesAn incorrect packet was generated by the virtual-link interface on the peer end.

Procedure


Step 2 End.

----End


48.10 OSPF_1.3.6.1.2.1.14.16.2.10 ospfTxRetransmit

DescriptionOSPF/4/IFRETX:OID [oid]: An OSPF packet is retransmitted on a non-virtual interface.(IfIpAddress=[ipaddr], AddressLessIf=[integer], NbrIfIpAddress=[ipaddr],NbrAddressLessIf=[ipaddr], LsdbAreaId=[ipaddr], LsdbType=[integer], LsdbLsid=[ipaddr],LsdbRouterId=[ipaddr], ProcessId=[process-id], RouterId=[ipaddr], IfNeighbor=[ipaddr],PacketType=[integer], InstanceName=[instance-name])

OSPF packets were retransmitted on non-virtual-link interfaces. The possible cause was that thephysical link was unreachable.



681

Attribute



Parameters

Name Meaning




NbrIfIpAddress Indicates the IP address of a neighboring interface.

NbrAddressLessIf Indicates the index of the neighboring interface.

LsdbAreaId Indicates the area ID of the LSDB.

LsdbType Indicates the LSA type.l 1: Router LSAl 2: Network LSAl 3: Summary LSA type 3l 4: Summary LSA type 4l 5: AS External LSAl 7: NSSA LSAl 9: Opaque LSA - scope Locall 10: Opaque LSA - scope areal 11: Opaque LSA - scope AS

LsdbLsid Indicates the LS ID of the LSDB.

LsdbRouterId Indicates the router ID of the LSDB.



IfNeighbor Indicates the router ID of a neighboring switch.



682

Name Meaning

PacketType Indicates the type of a packet.l 1: Hello packetl 2: DD packetl 3: Request packetl 4: Update packetl 5: Acknowledgement packetl 6: Update packet Retransl 7: Update packet flood


Impact on the SystemThis trap message is generated when an OSPF packet is retransmitted on a common interface.The cause may be that the network is busy, and thus LSDB update and route calculationconvergence are slow.

Possible Causes1. The address used to forward the packet could not be pinged through.

2. The peer regarded the packet as an invalid packet.

3. Parameters configured on the two interfaces were inconsistent.

Procedure

Step 1 Check the retransmission times of each packet.l If packets are retransmitted for 1 or 2 times and the number of packets is small, the trap is

informational only and no action is required. Go to Step 5.l If lots of packets are retransmitted constantly and the number of retransmission times is large,

go to Step 2.

Step 2 Obtain the IP address of the neighbor that retransmits the packets from the alarm message, andping the IP address.l If the ping fails, go to Step 4.l If the ping succeeds, go to Step 3.

Step 3 Check whether the local switch and the neighbor have trap and locate the fault according to thetrap. Otherwise, go to Step 4.


Step 5 End.

----End



683


48.11 OSPF_1.3.6.1.2.1.14.16.2.11 ospfVirtIfTxRetransmit

DescriptionOSPF/3/VIFRETX:OID [oid]: An OSPF packet is retransmitted on a virtual interface.(VirtIfAreaId=[area-id], VirtIfNeighbor=[neighbor-router-id], LsdbAreaId=[lsdb-area-id],LsdbType=[lsa-type], LsdbLsid=[lsdb-ls-id], LsdbRouterId=[lsdb-router-id], ProcessId=[process-id], RouterId=[router-id], PacketType=[packet-type], InstanceName=[instance-name])

OSPF packets were retransmitted on virtual-link interfaces. The possible cause was that thephysical link was unreachable or the information about entries in the routing table was incorrect.

Attribute



Parameters

Name Meaning



VirtIfNeighbor Indicates the router ID of a neighboring switch.

LsdbAreaId Indicates the area ID of an LSDB.

LsdbType Indicates the type of the LSA.l 1: Router LSAl 2: Network LSAl 3: Summary LSA type 3l 4: Summary LSA type 4l 5: AS External LSAl 7: NSSA LSAl 9: Opaque LSA - scope Locall 10: Opaque LSA - scope areal 11: Opaque LSA - scope AS



684

Name Meaning

LsdbLsid Indicates the LS ID of an LSDB.

LsdbRouterId Indicates the router ID of an LSDB.



PacketType Indicates the type of a packet.l 1: Hello packetl 2: DD packetl 3: Request packetl 4: Update packetl 5: Acknowledgement packetl 6: Update packet Retransl 7: Update packet flood



This trap message is generated when an OSPF packet is retransmitted on a virtual link interface.The cause may be that the network is busy, and thus LSDB update and route calculationconvergence are slow.

Possible Causes

1. The address used to forward the packets could not be pinged through.

2. The peer regarded the packet as an invalid packet.

Procedure

Step 1 Check the retransmission times of each packet.

l If packets are retransmitted for 1 or 2 times and the number of such packets is small, the trapis informational only and no action is required. Go to Step 5.

l If lots of packets are retransmitted constantly and the number of retransmission times is large,go to Step 2.

Step 2 Run the display ospf vlink command to check the peer switch of the vlink. Then log in to thisswitch and run the display ospf vlink command again to check the vlink interface status orneighbor status.

l If the vlink interface status or neighbor status is Down, see the procedures in traps1.3.6.1.2.1.14.16.2.1 and 1.3.6.1.2.1.14.16.2.3.



685

l If the vlink neighbor status is Full, find the IP address displayed in the interface field in theoutput and ping this address from the switch that generates the alarm.

– If the ping fails, go to Step 4.

– If the ping succeeds, go to Step 3.

Step 3 Check whether the local switch and the neighbor have trap 1.3.6.1.2.1.14.16.2.9 and locate thefault according to the trap. Otherwise, go to Step 4.


Step 5 End.

----End

Related Information

None

48.12 OSPF_1.3.6.1.2.1.14.16.2.12 ospfOriginateLsa

Description

OSPF/4/OGNLSA:OID [oid]: An LSA is generated. (LsdbAreaId=[area-id], LsdbType=[lsa-type], LsdbLsid=[lsdb-ls-id], LsdbRouterId=[lsdb-router-id], ProcessId=[process-id],RouterId=[router-id], InstanceName=[instance-name])

A switch generated new LSAs. The possible cause was that the status of the interface changed,the status of the OSPF neighbor changed, or the role of the switch changed (for example, theswitch imported routes).

Attribute



Parameters

Name Meaning


LsdbAreaId Indicates the area ID of a new LSA.



686

Name Meaning

LsdbType Indicates the type of the LSA.l 1: Router LSAl 2: Network LSAl 3: Summary LSA type 3l 4: Summary LSA type 4l 5: AS External LSAl 7: NSSA LSAl 9: Opaque LSA - scope Locall 10: Opaque LSA - scope areal 11: Opaque LSA - scope AS

LsdbLsid Indicates the LS ID of an LSDB.






If the neighbor or interface status change trap is generated and no manual operations areperformed within the period, services may be affected.

Possible Causes

1. The status of the interface changed.

2. The status of the neighbor changed.

3. The routes imported by OSPF changed.

Procedure

Step 1 Check the LSA type:

l In the case of Type 1 and Type 2 LSAs, check whether the following alarms exist:

1.3.6.1.2.1.14.16.2.2

1.3.6.1.2.1.14.16.2.16

– If so, handle the alarms according to the handling procedures of these alarms.




687

l In the case of Type 3, Type 5, and Type 7 LSAs, go to Step 2.

Step 2 Run the display ip routing-table lsdb-ls-id command to check whether the routing tablechanges.l If the routing table does not change, go to Step 3.l If the routing table changes, continue to check the cause of the route change or go to Step 3.


Step 4 End.

----End


48.13 OSPF_1.3.6.1.2.1.14.16.2.13 ospfMaxAgeLsa

DescriptionOSPF/4/AGELSA:OID [oid]: An LSA is aged. (LsdbAreaId=[area-id], LsdbType=[lsa-type],LsdbLsid=[lsdb-ls-id], LsdbRouterId=[lsdb-router-id], ProcessId=[process-id], RouterId=[router-id], InstanceName=[instance-name])

LSAs in the LSDB of the switch reached the maximum aging time. The possible cause was thatthe routes imported by OSPF were deleted or the OSPF interface was Down.

Attribute



Parameters

Name Meaning


LsdbAreaId Indicates the area ID of an aged LSA.



688

Name Meaning

LsdbType Indicates the type of an LSA.l 1: Router LSAl 2: Network LSAl 3: Summary LSA type 3l 4: Summary LSA type 4l 5: AS External LSAl 7: NSSA LSAl 9: Opaque LSA - scope Locall 10: Opaque LSA - scope areal 11: Opaque LSA - scope AS

LsdbLsid Indicates the link state ID of an LSDB.





If the instance name is null, the OSPF process is a public process.


In the case of Type 1 and Type 2 LSAs, services may be affected, and thus you need to checkthe interface or neighbor status. In the case of Type 3, Type 5, and Type 7 LSAs, only the routesassociated with lsdb-ls-id will be affected.

Possible Causes

1. The interface was Up or Down.

2. The status of the neighbor changed.

3. The routes imported by OSPF changed.

Procedure

Step 1 Check the LsdbRouterId of the LSA in the trap.

l If the LSA is generated by the local switch, go to Step 2.

l If the LSA is not generated by the local switch, go to Step 4.

Step 2 Check the LSA type:



689

l In the case of Type 1 and Type 2 LSAs, check whether the following alarms exist:

1.3.6.1.2.1.14.16.2.2

1.3.6.1.2.1.14.16.2.16

– If so, handle the alarms according to the handling procedures of these alarms.


l In the case of Type 3, Type 5, and Type 7 LSAs, run the display ip routing-table lsdb-ls-id command to check whether the route exists or switch flapping occurs.

– If the route exists or switch flapping occurs, go to Step 3.

– If the route does not exist, go to Step 3.


Step 4 End.

----End

Related Information

None

48.14 OSPF_1.3.6.1.2.1.14.16.2.14 ospfLsdbOverflow

Description

OSPF/3/OVERFLOW:OID [oid]: The LSDB overflows. (ProcessId=[process-id], RouterId=[router-id], ExtLsdbLimit=[lsa-limit], InstanceName=[instance-name])

The Overflow feature restricts only the total number of Type 5 and Type 7 LSAs. The totalnumber of type 5 LSAs and type 7 LSAs in the LSDB of the switch reached or exceeded themaximum value defined by ospfExtLsdbLimit. The possible cause was that the number of routesimported by OSPF exceeded the set threshold. This trap was generated when the number ofOSPF external routes in the network reached or exceeded the configured overflow limit.

Attribute



Parameters

Name Meaning




690

Name Meaning


RouterId Indicates the ID of the switch that generates the trap message.

ExtLsdbLimit Indicates the maximum number of type 5 LSAs and type 7 LSAs.


Impact on the SystemThe number of type 5 and type 7 LSAs exceeds the limit allowed by overflow. The excessivetype 5 and type 7 LSAs are discarded.

Possible CausesToo many type 5 and type 7 LSAs existed in the LSDB.

Procedure

Step 1 Run the display ospf lsdb brief command to check whether the total number of type 5 LSAsand type 7 LSAs exceeds the overflow limit.l If so, go to Step 2.l If not, go to Step 3.

Step 2 Perform the following operations as required:l If it is allowed to adjust the maximum number of external LSAs in the OSPF LSDB, run the

lsdb-overflow-limit command to reconfigure the maximum value. The set maximum valueshould be consistent on the entire network. Wait for a period of time and check whether thetrap is cleared. If the trap is cleared, go to Step 4. If not, go to Step 3.

l If it is not allowed to adjust the maximum number of external LSAs in the OSPF LSDB, goto Step 3.


Step 4 End.

----End


48.15 OSPF_1.3.6.1.2.1.14.16.2.15ospfLsdbApproachingOverflow



691

Description

OSPF/3/APPROFLOW:OID [oid]: The LSDB is approaching overflow. (ProcessId=[process-id], RouterId=[router-id], ExtLsdbLimit=[lsa-limit], InstanceName=[instance-name])

The Overflow feature restricts only the total number of Type 5 and Type 7 LSAs. The totalnumber of type 5 and type 7 LSAs in the LSDB of the router exceeded 90% of the maximumvalue defined by ospfExtLsdbLimit. The possible cause was that the number of routes importedby OSPF reached or exceeded the configured threshold. This trap was generated when thenumber of OSPF external routes in the network reached or exceeded 90% of the configuredoverflow limit.

Attribute



Parameters

Name Meaning




ExtLsdbLimit Indicates the maximum total number of type 5 and type 7 LSAs.



The total number of type 5 and type 7 LSAs exceeds the limit allowed by overflow. The excessivetype 5 and type 7 LSAs are discarded.

Possible Causes

Too many type 5 and type 7 LSAs existed in the LSDB.

Procedure

Step 1 Run the display ospf lsdb brief command to check whether the total number of type 5 and type7 LSAs exceeds 90% of the overflow limit.





692

Step 2 Perform the following operations as required:

l If it is allowed to adjust the maximum number of external LSAs in the OSPF LSDB, run thelsdb-overflow-limit command to reconfigure the maximum value. Wait for a certain periodand check whether the alarm cleared. If so, go to Step 4. If not, go to Step 3.

l If it is not allowed to adjust the maximum number of external LSAs in the OSPF LSDB, goto Step 3.


Step 4 End.

----End

Related Information

None

48.16 OSPF_1.3.6.1.2.1.14.16.2.16 ospfIfStateChange

Description

OSPF/2/IFCHG:OID [oid]: The status of the non-virtual interface changes. (IfIpAddress=[ipaddr], AddressLessIf=[integer], ProcessId=[integer], AreaId=[ipaddr], IfnetIndex=[integer],ProcessId=[integer], RouterId=[ipaddr], IfState=[integer], IfName=[octet], InstanceName=[octet], IfChgReason=[integer])

The status of the OSPF non-virtual-link interface changed. The possible cause was that thephysical interface was Down.

Attribute



Parameters

Name Meaning







693

Name Meaning

AreaId Indicates the area ID.

IfnetIndex Indicates the Ifnet index of the interface.



IfState Indicates the status of the interface.l 1: Downl 2: Loopbackl 3: Waitingl 4: Point-to-Pointl 5: DRl 6: Backupl 7: DROther

IfName Indicates the name of interface.


IfChgReason Indicates the reason why the neighbor status changes:l 1 (adjacencyHoldTimerExpired): indicates that the timer of the adjacent

router times out.l 2 (physicalInterfaceChange): indicates that the status of the physical

interface on the router changes.l 3 (ospfProtocolReason): indicates that an alarm is generated because of the

OSPF protocol.l 4 (bfdSessionStateChange): indicates that the BFD session is closed.l 5 (configureChange): indicates that the OSPF configuration changes.l 6 (peerRouterReason): indicates that an alarm is generated because of the

neighboring router.l 100 (alarmCleared): indicates that the alarm is cleared because services are

restored or the neighbor is deleted.

Impact on the SystemIf the interface status becomes Down, services may be affected. If the interface status becomesDR, BDR, DRother, or P2P, services will not be affected.



694

Possible Causes1. The status of the physical interface changed.

2. DR election occurred on the broadcast network.

Procedure

Step 1 Run the display ospf interface command to check whether the interface is Down.l If the interface is Down, go to Step 2.l If the interface is in another state, services are not affected. Then, go to Step 4.

Step 2 Run the display interface interface-type interface-number command to check whether thecurrent interface is Up.l If so, go to Step 3.l If not, view the log file to check whether the shutdown command is run on the interface.

– If the shutdown command is run on the interface, in the case of an incorrect operation,run the undo shutdown command on the interface; otherwise, go to Step 4.

– If the shutdown command is not run on the interface, it indicates that the link is faulty.Thus, replace the link or go to Step 3.


Step 4 End.

----End


48.17 OSPF_1.3.6.1.2.1.14.16.2.17ospfNSSATranslatorStatusChange

DescriptionOSPF/2/NSSATRANCHG:OID [oid]: The status of the NSSA translator changes. (AreaId=[area-id], ProcessId=[process-id], RouterId=[router-id], NSSATranslatorState=[translator-state], InstanceName=[instance-name])

The translator role in the NSSA changed. A possible cause is that the status of the translatorchanged among Enabled, Elected, and Disabled.

Attribute





695

Parameters

Name Meaning


AreaId Indicates the area ID of the NSSA.


RouterId Indicates the ID of the switch that generates the trap.

NSSATranslatorState Indicates the new status of the translator in the NSSA.l 1: ENABLEDl 2: ELECTEDl 3: DISABLED



ASE routes may flap for a short period in the following situations. The role of the NSSA ABRchanges; the Type 5 LSAs translated from Type 7 LSAs need to be flushed; or a new translatoris translating Type 7 LSAs to Type 5 LSAs. Moreover, the translator role changes withoutmanual configuration mostly because the topology in the backbone area or the NSSA changes.

Possible Causes

1. The parameter translator-always in the nssa command was manually configured or cancelledon an ABR in the NSSA.

2. A new router ID was configured on an ABR in the NSSA and took effect.

3. A new switch joined the NSSA or a switch exited from the NSSA.

4. The OSPF protocol was restarted or the master/slave switchover was performed on a switchin the backbone area or the NSSA. This caused topology change in the NSSA.

5. The nssa command was manually configured or parameters in the nssa command weremanually modified, which caused topology flapping in the backbone area or the NSSA. Forexample, configuring or canceling the parameter no-summary or no-import-route in the nssacommand will lead to the reestablishment of the neighbor relationship between the localswitch and a switch in the backbone area and between the local switch and a switch in the NSSA.

6. The role of the of the local switch changed to ABR or changed from ABR.

7. The topology of the backbone area or the NSSA changed. As a result, the local switch cannotreach another ABR with a greater router ID or with the parameter translator-always from thebackbone area or the NSSA.



696

Procedure

Step 1 If the nssa translator-always command is configured or cancelled manually on the localswitch, run the display ospf brief command to check whether the translator role of the localswitch in the NSSA is correct.

l If the nssa translator-always command is configured, run the display ospf brief commandto check whether the status of the NSSA translator is always. If so, go to Step 8. If not, goto Step 7.

l If the configuration about nssa translator-always is cancelled, run the display ospf briefcommand to check the status of the NSSA translator. If the status is disabled, go to Step 2.If the status is elected, go to Step 8.

Step 2 A possible cause is that the nssa translator-always command is configured on an ABR in theNSSA. You can run the display ospf lsdb router command to check whether the Router-LSAof some ABR in the NSSA contains the Nt bit. Alternatively, you can check whether the nssatranslator-always is configured on the ABRs.

l If the Router-LSA of some ABR contains the Nt bit or a ABR has been configured with thenssa translator-always command, go to Step 8.

l If there is no ABR whose Router-LSA contains the Nt bit or no ABR is configured with thenssa translator-always command, go to Step 3.

Step 3 If a new router ID is configured on the local switch and already takes effect, check whether thetranslator role of the local switch in the NSSA is correct after the topology in the area becomesstable.



Step 4 A possible cause is that a new router ID is configured on an ABR in the NSSA. In this case,check the configurations of the other ABRs.

l If the router ID of an ABR is changed, check whether the newly configured router ID isgreater than the local router ID after the topology in the NSSA is stable.



l If the router ID of an ABR remains unchanged, go to Step 5.

Step 5 If a new switch joins the NSSA, do as follows as required:

l If the new joint switch is an ABR, check whether the router ID of the ABR is greater thanthe local router ID after the topology in the NSSA is stable.



l If the new joint switch is not an ABR, go to Step 6.

Step 6 Check whether the local switch and the neighboring switch have traps , 1.3.6.1.2.1.14.16.2.2, ,and 1.3.6.1.2.1.14.16.2.16.

l If the preceding traps are generated, refer to the corresponding fault location processes.

l If the preceding traps are not generated, go to Step 7.



697


Step 8 End.

----End

Related Information

None

48.18 OSPF_1.3.6.1.2.1.14.16.2.18 ospfRestartStatusChange

Description

OSPF/3/RESTARTCHG:OID [oid]: The GR status changes. (ProcessId=[process-id],RouterId=[router-id], RestartStatus=[gr-reason], RestartInterval=[gr-value],RestartExitReason=[quit-reason], InstanceName=[instance-name])

The GR status of the switch changed.

Attribute



Parameters

Name Meaning




RestartStatus Indicates the reason of entering GR.l 1: NOT RESTARTINGl 2: PLANNED RESTARTl 3: UNPLANNED RESTART

RestartInterval Indicates the GR period.



698

Name Meaning

RestartExitReason Indicates the reason why the switch exits from GR.l 1: not attemptedl 2: restart/helper in progressl 3: restart/helper completed successfullyl 4: restart/helper exit because of timeoutl 5: restart/helper exit because of topology changed


Impact on the SystemThis trap message is generated when a switch enters the GR state or leaves the GR state. GRfailure affects the normal forwarding of routes.

Possible Causes1. The switch exited from GR.

2. The switch entered GR.

Procedure

Step 1 Perform the following configurations as required:l If the active/standby switchover is performed manually or the OSPF process is restarted

through GR, go to Step 3.l If this trap is generated without any manual operation, go to Step 2.


Step 3 End.

----End


48.19 OSPF_1.3.6.1.2.1.14.16.2.19ospfNbrRestartHelperStatusChange

DescriptionOSPF/3/NBRHELPERCHG:OID [oid]: The helper status of the non-virtual neighbor changes.(NbrIpAddr=[ip-address], NbrAddressLessIndex=[interface-index], ProcessId=[process-id],



699

RouterId=[router-id], NbrRtrId=[neighbor-router-id], NbrRestartHelperStatus=[gr-helper-state], NbrRestartHelperAge=[gr-helper-value], NbrRestartHelperExitReason=[quit-reason],InstanceName=[instance-name])

The GR helper status of the OSPF neighbor changed.

Attribute



Parameters

Name Meaning


NbrIpAddr Indicates the IP address of a non-virtual-link interface.

NbrAddressLessIndex Indicates the index of the interface.



NbrRtrId Indicates the ID of a neighboring switch.

NbrRestartHelperStatus Indicates the new helper status.l 1: Normal Router, not-helpingl 2: GR Router, not-helpingl 3: Helper Router, helping

NbrRestartHelperAge Indicates the remaining time of GR.

NbrRestartHelperExitReason Indicates the reason why the switch leaves the helper status.l 1: not attemptedl 2: restart/helper in progressl 3: restart/helper completed successfullyl 4: restart/helper exit because of timeoutl 5: restart/helper exit because of topology changed




700


This trap message is generated when a switch enters or leaves the helper status. GR failure affectsthe normal forwarding of routes.

Possible Causes

During GR, the GR helper status changed.

Procedure

Step 1 Perform the following configurations as required:

l If the active/standby switchover is performed manually or the OSPF process is restartedthrough GR, go to Step 3.

l If this trap is generated without any manual operation, go to Step 2.


Step 3 End.

----End

Related Information

None

48.20 OSPF_1.3.6.1.2.1.14.16.2.20ospfVirtNbrRestartHelperStatusChange

Description

OSPF/3/VNBRHELPERCHG:OID [oid]: The helper status of the virtual neighbor changes.(VirtNbrAreaId=[area-id], VirtNbrRtrId=[neighbor-router-id], ProcessId=[process-id],RouterId=[router-id], VirtNbrRestartHelperStatus=[gr-helper-state],VirtNbrRestartHelperAge=[gr-helper-value], VirtNbrRestartHelperExitReason=[quit-reason],InstanceName=[instance-name])

The helper status of the OSPF neighbor on the virtual link changed.

Attribute





701

Parameters

Name Meaning


VirtNbrAreaId Indicates the ID of the area that the virtual link belongs to.

VirtNbrRtrId Indicates the ID of a neighbor of the virtual link.



VirtNbrRestartHelperStatus Indicates the new helper status.l 1: Normal Router, not-helpingl 2: Helper Router, helping

VirtNbrRestartHelperAge Indicates the period during which the switch is in the helperstate.

VirtNbrRestartHelperExitReason Indicates the reason why the switch leaves the helper status.l 1: not attemptedl 2: restart/helper in progressl 3: restart/helper completed successfullyl 4: restart/helper exit because of timeoutl 5: restart/helper exit because of topology changed



This alarm is generated when the neighbor on the virtual link leaves or enters the helper status.GR failure affects the normal forwarding of routes.

Possible Causes

During GR, the helper status of the neighbor on the virtual link changed.

Procedure

Step 1 Perform the following configurations as required:

l If the active/standby switchover is performed manually or the OSPF process is restartedthrough GR, go to Step 3.




702


Step 3 End.

----End

Related Information

None

48.21 OSPF_1.3.6.1.4.1.2011.5.25.155.31.3hwOspfv2IntraAreaRouteridConflict

Description

OSPF/2/RTRID_CONFLCT:OID [oid]: Router IDs conflict in an intra area. (ProcessId=[integer], AreaId=[ipaddr], SelfIfnetIndex=[integer], NbrIpAddr=[ipaddr], RouterId=[ipaddr],NbrRtrId=[ipaddr])

Router IDs conflict in an intra-area.

Attribute


1.3.6.1.4.1.2011.5.25.155.31.3 Major communicationsAlarm(2)

Parameters

Name Meaning


ProcessId Process ID

AreaId Area ID

SelfIfnetIndex Index of an interface

NbrIpAddr IP address of a neighbor

RouterId Local router ID

NbrRtrId Router ID of a neighbor



703


If the same router ID is configured for any two routers, it will cause the router lSA to be refreshedfrequently. As a result, route flapping will occur.

Possible Causes

The same router ID was configured for at least two indirectly connected switchs within one area,causing the router lSA to be refreshed frequently and route flapping.

Procedure

Step 1 Check whether the router ID in the alarm is the same as that of a neighbor.



Step 2 Check whether the automatic recovery function is enabled.

l If the function is enabled, go to Step 4.

l If the function is not enabled, go to Step 3.

Step 3 Run the undo ospf router-id auto-recover disable command to enable the automatic recoveryfunction, and select a new router ID for a switch. Then, check whether the alarm is cleared.



Step 4 Run the ospf router-id router-id command to configure a new router ID for a switch. Run thereset ospf command to restart the OSPF process. Then, check whether the alarm is cleared.




Step 6 End.

----End

Related Information

None.

48.22 OSPF_1.3.6.1.4.1.2011.5.25.155.31.4hwOspfv2IntraAreaDRIpAddressConflict

Description

OSPF/2/IPADDR_CONFLCT:OID [oid]: IP addresses of DRs in an intra area conflict.(ProcessId=[integer], AreaId=[ipaddr], SelfIfnetIndex=[integer], NbrIpAddr=[ipaddr],RouterId=[ipaddr], IntierfaceIpAddress=[ipaddr], InterfaceName=[octet])



704

IP addresses of DRs in an intra area conflict.

Attribute


1.3.6.1.4.1.2011.5.25.155.31.4 Major communicationsAlarm(2)

Parameters

Name Meaning


ProcessId Process ID

AreaId Area ID

SelfIfnetIndex Index of an interface

NbrIpAddr IP address of a neighbor

RouterId Local router ID

IntierfaceIpAddress IP address of an interface

InterfaceName Name of an interface


The same IP address is configured for two indirectly connected switchs in the same area. Ofwhich, one is selected as a DR to advertise network LSAs. As a result, route flapping occursfrequently.

Possible Causes

The same IP address was configured for two indirectly connected switchs in the same area. Ofwhich, one was selected as a DR to advertise network LSAs.

Procedure

Step 1 Check whether the IP address displayed in this alarm conflicts with that of any interface in thesame area.

l If a conflict exists, go to Step 2.

l If no conflict exists, go to Step 3.

Step 2 Change an IP address of a local interface to check whether the alarm is cleared.



705

l If the alarm is cleared, go to Step 4.l If the alarm persists, go to Step 3.


Step 4 End.

----End




706

49 OSPFV3

About This Chapter

49.1 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.1 hwOspfv3VirtIfStateChange

49.2 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.2 hwOspfv3NbrStateChange

49.3 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.3 hwOspfv3VirtNbrStateChange

49.4 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.4 hwOspfv3IfConfigError

49.5 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.5 hwOspfv3VirtIfConfigError

49.6 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.6 hwOspfv3IfRxBadPacket

49.7 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.7 hwOspfv3VirtIfRxBadPacket

49.8 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.8 hwOspfv3IfStateChange

49.9 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.9 hwOspfv3RestartStatusChange

49.10 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.10 hwOspfv3NbrRestartHelperStatusChange

49.11 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.11 hwOspfv3VirtNbrRestartHelperStatusChange

49.12 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.12 hwOspfv3NssaTranslatorStatusChange

49.13 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.13 hwOspfv3LastAuthKeyExpiry

49.14 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.14 hwOspfv3AuthSequenceNumWrap

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 49 OSPFV3


707

49.1 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.1hwOspfv3VirtIfStateChange

DescriptionOSPFV3/2/VIFCHANGE:OID [oid] The status of the virtual interface has changed. (AreaId=[integer], NbrRouterId=[gauge], RouterId=[gauge], VIfState=[integer], ChgReason=[integer])

The status of the OSPFv3 virtual link interface changed. A possible cause is that the router IDof the neighbor on the virtual link changed after the virtual link was configured or the status ofthe physical interface of the virtual link changed.

Attribute


1.3.6.1.4.1.2011.5.25.147.0.1 Major processingErrorAlarm(4)

Parameters

Name Meaning


AreaId Indicates the ID of the OSPFv3 area. The value is a decimal integer.

NbrRouterId Indicates the Router ID of the virtual neighbor. The value is a decimal integer.

RouterId Indicates the Router ID of the local switch. The value is a decimal integer.

VIfState Indicates the state of the virtual link interface.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full



708

Name Meaning

ChgReason Indicates the reason for change in the state of an OSPFv3 virtual interface.l 1: No Eventl 2: Interface Upl 3: Wait Timer Expiredl 4: Backup Seen Occurredl 5: Neighbor Change Event Occurredl 6: Loop Indl 7: Unloop Indl 8: Interface Down

Impact on the SystemThis trap message is generated when the status of a virtual interface changes. This trap mayaffect the neighbor status. If the interface goes Down, the neighbor relationship will beinterrupted.


2. The router ID of the neighbor on the virtual link changed.

Procedure

Step 1 Run the display ospfv3 vlink command to check whether the status of the virtual link interfaceis Up.l If so, it indicates that this trap message is informational only, and no action is required. Then,

go to Step 5.l If not, go to Step 2.

Step 2 Run the display ipv6 interface and display ospfv3 interface commands to check whether theinterface status is Up.l If so, go to Step 3.l If not, check the connection between physical interfaces. After the interface turns Up, check

whether the alarm is cleared.



Step 3 Run the display current-configuration configuration ospfv3 command to check whether theID of the neighbor on the virtual link changes.l If so, modify the configurations of the two ends to be the same. Then check whether the trap

is cleared.





709



Step 5 End.

----End

Related Information

None

49.2 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.2hwOspfv3NbrStateChange

Description

OSPFV3/2/NBRCHANGE:OID [oid] The status of the non-virtual neighbor has changed.(IfIndex=[integer], InstanceId=[integer], NbrRouterId=[gauge], RouterId=[gauge], NbrState=[integer], IfName=[octet], ChgReason=[integer])

The status of the OSPFv3 neighbor changed. A possible cause is that the status of the interfacewhere the neighbor resided changed or the contents of the received Hello packets changed.

Attribute



Parameters

Name Meaning


IfIndex Indicates the index of the interface. The value is a decimal integer.


InstanceId Indicates the ID of the OSPFv3 instance. The value is a decimal integer.

NbrRouterId Indicates the Router ID of the neighbor. The value is a decimal integer.




710

Name Meaning

NbrState Indicates the state of the neighbor.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full

ChgReason Indicates the reason for change in the state of an OSPFv3 neighbor.l 1: No Eventl 2: Received Hello Packetl 3: Startl 4: Received Two Wayl 5: Negotiation Donel 6: ExchangeDonel 7: Received Bad LS Requestl 8: Loading Donel 9: Established Adjacencyl 10: Mismatch In Seq Numberl 11: Received One Wayl 12: NBR Killedl 13: Inactivity Timer Expiredl 14: Link Down


This trap is generated when the status of the neighbor (not a neighbor of a virtual link) changes.This trap indicates that the status of the neighbor changes. If the neighbor changes from a lowerstatus to a higher status, this trap message is informational only, and no action is required. If theneighbor changes from a higher status to a lower status, services may be interrupted.

Possible Causes1. The status of the interface where the neighbor resided changed.

2. The configured parameters (such as the Hello timer, dead timer, interface authentication,and network type) of the interfaces on the local end or remote end were modified.

3. OSPF was restarted by using the reset ospfv3 command or the active/standby switchoverwas performed.



711

4. The ping operation failed, which indicated that an error occurred during packettransmission.

Procedure

Step 1 Run the display ipv6 interface and display ospfv3 peer commands to check the status of theinterface where the neighbor resides.

l If the physical interface is Down, check the link and make the link Up, and then go to Step2.

l If the physical interface is Up, go to Step 2.

Step 2 Check whether packets are correctly forwarded and ping the IP address of the remote interface.

l If the ping fails, go to Step 5.

l If the ping succeeds, go to Step 3.

Step 3 Run the display ipv6 interface command to check whether the interface where the OSPFv3neighbor resides is in the Up state.

l If the interface is in the Down state, go to Step 5.

l If the interface is in the Up state, go to Step 4.

Step 4 Run the display ospfv3 interface command to check whether the configurations of the two endsare correct.




Step 6 End.

----End

Related Information

None

49.3 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.3hwOspfv3VirtNbrStateChange

Description

OSPFV3/2/VNBRCHANGE:OID [oid] The status of the virtual neighbor has changed. (AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], VNbrState=[integer], ChgReason=[integer])

The status of the OSPFv3 neighbor on the virtual link changed because the status of the virtuallink interface changed.



712

Attribute



Parameters

Name Meaning



VirtualNbrRouterId Indicates the Router ID of the virtual link neighbor. The value is adecimal integer.


VNbrState Indicates the state of the virtual link neighbor.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full



713

Name Meaning

ChgReason Indicates the reason for change in the state of virtual link neighbor.l 1: No Eventl 2: Received Hello Packetl 3: Startl 4: Received Two Wayl 5: Negotiation Donel 6: ExchangeDonel 7: Received Bad LS Requestl 8: Loading Donel 9: Established Adjacencyl 10: Mismatch In Seq Numberl 11: Received One Wayl 12: NBR Killedl 13: Inactivity Timer Expiredl 14: Link Down


This trap is generated when the status of the neighbor (a neighbor of a virtual link) changes. Ifthe neighbor changes from a lower status to a higher status, this trap message is informationalonly, and no action is required. If the neighbor changes from a higher status to a lower status,services may be interrupted.

Possible Causes

1. The status of the interface of the virtual link changed.

2. The configured parameters (such as the Hello timer, dead timer, interface authentication, andnetwork type) of the virtual link interface on the local end or remote end were modified.

3. OSPFv3 was restarted by using the reset ospfv3 command or the active/standby switchoverwas performed.

4. An errored packet was received.

5. The overflow function was configured and the process entered the Overflow state.

6. Routes of the area configured with the virtual link were added or deleted.

7. The ping operation failed, which indicated that an error occurred during packet transmission.

Procedure

Step 1 Run the display ospfv3 interface and display ipv6 interface brief commands to check whetherthe physical interface of the virtual link goes Down.



714

l If the physical interface is Down, check the link and make the link Up, and then go to Step2.


Step 2 Run the display ospfv3 peer command to check whether the OSPFv3 neighbor relationship isnormal.l If the neighbor relationship is abnormal, check whether trap 1.3.6.1.4.1.2011.5.25.147.0.2

exists. If the trap exists, locate the fault according to the trap. If the trap does not exist, go toStep 6.

l If the neighbor relationship is normal, go to Step 3.

Step 3 Run the display ospfv3 routing command to check whether the route to the neighbor on thevirtual link exists.l If the route does not exist, go to Step 5.l If the route exists, go to Step 4.

Step 4 Run the display ospfv3 vlink and display current-configuration configuration ospfv3commands to check whether the configurations of the two ends are correct.l If so, go to Step 6.l If not, go to Step 5.

Step 5 Adjust the parameters correctly according to the requirements of the networking, and checkwhether the trap is cleared.l If so, go to Step 7.l If not, go to Step 6.


Step 7 End.

----End


49.4 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.4hwOspfv3IfConfigError

DescriptionOSPFV3/2/IFCFGERR:OID [oid] The configuration of the non-virtual interface is incorrect.(IfIndex=[integer], InstanceId=[integer], RouterId=[gauge], IfState=[integer], PacketSrcAdd=[octet], ErrorType=[integer], PacketType=[integer])

This trap is generated on a non-virtual-link interface when the local end refused to establish theadjacency relationship with the remote end. This trap indicated that the configurations of theinterfaces on which the neighbor relationship is to be established were inconsistent. A possible



715

cause is that the values of the Hello timer, dead timer, poll timer were not consistent on the twointerfaces or the two interfaces were not in the same area.

Attribute



Parameters

Name Meaning





IfState Indicates the status of an interface.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full

PacketSrcAdd Indicates the address of the source node that sends the packet.



716

Name Meaning

ErrorType Indicates the type of the error.l 1: badVersionl 2: areaMismatchl 3: unknownNbmaNbrl 4: unknownVirtualNbrl 5: helloIntervalMismatchl 6: deadIntervalMismatchl 7: optionMismatchl 8: mtuMismatchl 9: duplicateRouterIdl 10: noError

PacketType Indicates the type of the packet.l 1: Hellol 2: DD(Data base Description) packetl 3: LS Requestl 4: LS Updatel 5: LS Acknowledgementl 6: NULL packet


This trap is generated when an interface receives a packet indicating parameters are incorrectlyconfigured. Such configuration errors generally occur during the deployment test or cutover.You can rectify the fault by modifying the parameters on the two ends to be consistent, andservices will not be affected.

Possible Causes

1. Parameters manually configured on the two interfaces were inconsistent.

2. The routing protocol on the link layer changed.

Procedure

Step 1 Run the display ospfv3 interface command to check whether the configurations of the two endsare consistent.




l If it is allowed to modify the configurations of the two ends to be consistent, go to Step 4.



717

l If it is not allowed to modify the configurations of the two ends to be consistent, go to Step3.


Step 4 End.

----End

Related Information

None

49.5 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.5hwOspfv3VirtIfConfigError

Description

OSPFV3/2/VIFCFGERR:OID [oid] The configuration of the virtual interface is incorrect.(AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], VIfState=[integer],ErrorType=[integer], PacketType=[integer])

Configurations of the virtual link interface were incorrect. A possible cause is that theconfigurations of the parameters conflicted.

Attribute



Parameters

Name Meaning



VirtualNbrRouterId Indicates the Router ID of the virtual neighbor. The value is a decimalinteger.




718

Name Meaning

VIfState Indicates the state of the virtual neighbor.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full

Errortype Indicates the type of the error.l 1: badVersionl 2: areaMismatchl 3: unknownNbmaNbrl 4: unknownVirtualNbrl 5: helloIntervalMismatchl 6: deadIntervalMismatchl 7: optionMismatchl 8: mtuMismatchl 9: duplicateRouterIdl 10: noError

Packettype Indicates the type of the packet.l 1: Hellol 2: DD(Data base Description) packetl 3: LS Requestl 4: LS Updatel 5: LS Acknowledgementl 6: NULL packet


This trap is generated when the virtual link interface received a packet indicating parameterswere incorrectly configured. Such configuration errors generally occur during the deploymenttest or cutover. You can modify the parameters on the two ends to be consistent to rectify thefault, and services will not be affected.

Possible Causes

The configurations of the interfaces on the two ends of the virtual link conflicted.



719

Procedure

Step 1 Run the display ospfv3 vlink and display current-configuration interface commands to checkwhether the configurations of the two interfaces are consistent.




l If it is allowed to modify the configurations of the two ends to be consistent, go to Step 4.

l If it is not allowed to modify the configurations of the two ends to be consistent, go to Step3.


Step 4 End.

----End

Related Information

None

49.6 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.6hwOspfv3IfRxBadPacket

Description

OSPFV3/3/IFRXBADPKT:OID [oid] Error packet was received on the non-virtual interface.(IfIndex=[integer], InstanceId=[integer], RouterId=[gauge], IfState=[integer], PacketSrcAdd=[octet], PacketType=[integer])

An OSPFv3 packet that cannot be parsed was received from a non-virtual-link interface. Apossible cause is that the Huawei device was attacked or the interconnection between the Huaweidevice and non-Huawei device failed.

Attribute


1.3.6.1.4.1.2011.5.25.147.0.6 Minor processingErrorAlarm(4)

Parameters

Name Meaning




720

Name Meaning




IfState Indicates the status of the non-virtual link interface.

l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full

PacketSrcAdd Indicates the address of the source node that sends the packet.

PacketType Indicates the type of the packet.

l 1: Hellol 2: DD(Data base Description) packetl 3: LS Requestl 4: LS Updatel 5: LS Acknowledgementl 6: NULL packet

Impact on the SystemThis trap is generated when a common interface receives an errored packet that cannot beprocessed and then discards this packet. This may cause the neighbor to go Down.

Possible CausesAn errored packet was generated by the non-virtual-link interface on the remote end.

Procedure


Step 2 End.

----End



721


49.7 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.7hwOspfv3VirtIfRxBadPacket

DescriptionOSPFV3/3/VIFRXBADPKT:OID [oid] Error packet was received on the virtual interface.(AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], VIfState=[integer],PacketType=[integer])

An OSPFv3 packet that cannot be parsed was received from a virtual link interface. A possiblecause is that the Huawei device was attacked or the interconnection between the Huawei deviceand non-Huawei device failed.

Attribute



Parameters

Name Meaning







722

Name Meaning

VIfState Indicates the status of a virtual link interface.

l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full

Packettype Indicates the type of the packet.

l 1: Hellol 2: DD(Data base Description) packetl 3: LS Requestl 4: LS Updatel 5: LS Acknowledgementl 6: NULL packet

Impact on the SystemThis trap is generated when a virtual link interface receives a packet that cannot be parsed andthen discards this packet. This may cause the neighbor to go Down.

Possible CausesAn errored packet was generated by the interface on the remote end of the virtual link.

Procedure


Step 2 End.

----End


49.8 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.8hwOspfv3IfStateChange



723

DescriptionOSPFV3/2/IFCHANGE:OID [oid] The status of the non-virtual interface has changed.(IfIndex=[integer], InstanceId=[integer], RouterId=[gauge], IfState=[integer], IfName=[octet],ChgReason=[integer])

The status of the OSPFv3 non-virtual-link interface changed.

Attribute



Parameters

Name Meaning






IfState Indicates the status of the non-virtual neighbor.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full



724

Name Meaning

ChgReason Indicates the reason for change in the state of an OSPFv3 interface.l 1: No Eventl 2: Interface Upl 3: Wait Timer Expiredl 4: Backup Seen Occurredl 5: Neighbor Change Event Occurredl 6: Loop Indl 7: Unloop Indl 8: Interface Down


This trap is generated when the status of a common interface changes. This trap may affect theneighbor status. If the interface goes Down, the neighbor relationship will be interrupted.

Possible Causes

1. The physical interface went Up or Down.

2. The OSPFv3 neighbor relationship was being established.

Procedure

Step 1 Run the display rm interface and display ipv6 interface brief commands to check whetherthe interface is Down.

l If the physical interface is Down, check the link. Then check whether the trap is cleared.




Step 2 Run the display ospfv3 interface command to check whether the current interface is Up.




Step 4 End.

----End

Related Information

None



725

49.9 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.9hwOspfv3RestartStatusChange

DescriptionOSPFV3/3/RESTARTSTATUSCHANGE:OID [oid] The graceful restart status of the routerhas changed. (RouterId=[gauge], State=[integer], RestartInterval=[integer],RestartExitReason=[integer])

The GR status of the switch changed.

Attribute



Parameters

Name Meaning


RouterId Indicates the Router-ID of the local node. The value is a decimal integer.

State Indicates the restart status.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full

RestartInterval Indicates the interval of GR.



726

Name Meaning

RestartExitReason Indicates the cause why the switch exits from the GR.l 1: Nonel 2: In progressl 3: Completedl 4: Time outl 5: Topology change


This trap indicates that a switch enters the GR state or exists from the GR state. GR failure willaffect the normal forwarding of routes.

Possible Causes

1. OSPFv3 exited from GR.

2. The GR period exceeded the set value.

3. OSPFv3 GR is reset.

Procedure

Step 1 Run the display ospfv3 graceful-restart-information command to check the cause ofbecoming the GR and the current GR status.


l If the active/standby switchover is performed manually or the OSPFv3 process is restartedin GR mode, go to Step 4.


l If the reset ospfv3 graceful-restart command is executed, go to Step 4.


Step 4 End.

----End

Related Information

None

49.10 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.10hwOspfv3NbrRestartHelperStatusChange



727

DescriptionOSPFV3/3/NBRHELPERSTATUSCHNG:OID [oid] The helper status for the non-virtualneighbor has changed. (IfIndex=[integer], InstanceId=[integer], NbrRouterId=[gauge],RouterId=[gauge], State=[integer], HelperAge=[integer], HelperExitReason=[integer])

The GR helper status of the OSPFv3 neighbor changed.

Attribute



Parameters

Name Meaning




NbrRouterId Indicates the Router ID of the neighbor. The value is a decimal integer.


State Indicates the state of the neighbor.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full

HelperAge Indicates the remaining time of GR.



728

Name Meaning

HelperExitReason Indicates the cause why the switch exits from the GR helper status.l 1: Nonel 2: In progressl 3: Completedl 4: Time outl 5: Topology change


This trap indicates a switch enters the GR helper state or exits from the GR helper state. GRfailure will affect the normal forwarding of routes.

Possible Causes

1. The neighbor also restarts when it functions as a GR helper.

2. The grace timer expired.

3. The grace LSA was received.

Procedure

Step 1 Run the display ospfv3 graceful-restart-information command to check the reason that thelocal switch functions as the GR helper and check the current GR status.





Step 4 End.

----End

Related Information

None

49.11 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.11hwOspfv3VirtNbrRestartHelperStatusChange



729

DescriptionOSPFV3/3/VNBRHELPERSTATUSCHNG:OID [oid] The helper status for the virtualneighbor has changed. (AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge],State=[integer], HelperAge=[integer], HelperExitReason=[integer])

The GR helper status of the OSPFv3 neighbor on the virtual link changed.

Attribute



Parameters

Name Meaning





State Indicates the state of the virtual neighbor.l 1: Downl 2: Attemptl 3: Initl 4: 2-Wayl 5: Exstartl 6: Exchangel 7: Loadingl 8: Full

HelperAge indicates the remaining time of GR.

HelperExitReason Indicates the cause why the route exits from the GR helper.l 1: Nonel 2: In progressl 3: Completedl 4: Time outl 5: Topology change



730


This trap indicates that the neighbor on the virtual link enters the helper state or exits from thehelper state. GR failure will affect the normal forwarding of routes.

Possible Causes

1. The neighbor also restarts when it functions as a GR helper.

2. The grace timer expired.

3. The grace LSA was received.

Procedure

Step 1 Run the display ospfv3 graceful-restart-information command to check the reason that thelocal switch functions as the GR helper and check the current GR status.





Step 4 End.

----End

Related Information

None

49.12 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.12hwOspfv3NssaTranslatorStatusChange

Description

OSPFV3/3/NSSATRNSLTRSTSCHNG:OID [oid] The status of the NSSA translator haschanged. (AreaId=[integer], RouterId=[gauge], State=[integer])

The translator role in the NSSA changed. A possible cause is that the status of the translatorchanged among Enabled, Elected, and Disabled.

Attribute





731

Parameters

Name Meaning


AreaId Indicates the OSPFv3 area ID, which is a decimal integer.

RouterId Indicates the router ID of the local device, which is a decimal integer.

State Indicates the new status of the translator in the NSSA:l 1: enabledl 2: electedl 3: disabled

Impact on the SystemASE routes may flap for a short period in the following situations. The translator role of theNSSA ABR changes; Type 5 LSAs translated from Type 7 LSAs need to be flushed; or a newtranslator is translating Type 7 LSAs to Type 5 LSAs. In addition, the translator role changeswithout manual configuration mostly because the topology in the backbone area or the NSSAchanges.

Possible Causes1. The parameter translator-always in the nssa command was manually configured or cancelledon an ABR in the NSSA.

2. A new router ID was configured on an ABR in the NSSA and took effect.

3. A new switch joined the NSSA or a switch exited from the NSSA.

4. The OSPFv3 protocol was restarted or the master/slave switchover was performed on aswitch in the backbone area or the NSSA. This resulted in topology instability in the NSSA.

5. The nssa command was manually configured or the parameters in the nssa command weremanually modified, which caused the topology of the backbone area or the NSSA changes. Forexample, configuring or canceling the parameter no-summary or no-import-route in thenssa command will lead to the reestablishment of neighbor relationships between the localswitch and a switch in the backbone area, and between the local switch and a switch in the NSSA.

6. The role of the local switch changed to an ABR or changed from an ABR to another role.

7. The topology of the backbone area or the NSSA changed. As a result, the local switch cannotreach another ABR with a greater router ID or with the parameter translator-always from thebackbone area or the NSSA.



732

Procedure

Step 1 If the nssa translator-always command is configured or cancelled manually on the localswitch, run the display ospfv3 area command to check whether the translator role of the localswitch in the NSSA is correct.

l If the nssa translator-always command is configured, run the display ospfv3 area commandto check whether the status of the NSSA translator is always. If so, go to Step 8. If not, goto Step 7.

l If the configuration of the nssa translator-always command is cancelled, run the displayospfv3 area command to check the status of the NSSA translator. If the status is disabled,go to Step 2. If the status is elected, go to Step 8.

Step 2 A possible cause is that the nssa translator-always command is configured on an ABR in theNSSA. You can run the display ospfv3 lsdb routercommand to check whether the Router-LSAof a specific ABR in the NSSA carries the N bit. Alternatively, you can check whether thenssa translator-always is configured on other ABRs.

l If the Router-LSA of a specific ABR carries the N bit or other ABRs are configured with thenssa translator-always command, go to Step 8.

l If the Router-LSA of a specific ABR does not carry the N bit or other ABRs are not configuredwith the nssa translator-always command, go to Step 3.

Step 3 If a new router ID is configured on the local switch and already takes effect, after the topologyin the area becomes stable, check whether the translator role of the local switch in the NSSA iscorrect.



Step 4 A possible cause is that a new router ID is configured on another ABR in the NSSA. In this case,check the configurations of other ABRs.

l If the router ID of a specific ABR is changed, after the topology of the NSSA becomes stable,check whether the newly configured router ID is greater than the local router ID.



l If the router ID of a specific ABR remains unchanged, go to Step 5.

Step 5 If a new switch joins the NSSA, do as follows as required:

l If an ABR joins the NSSA, after the topology in the NSSA becomes stable, check whetherthe router ID of the ABR is greater than the local router ID.



l If a non-ABR joins the NSSA, go to Step 6.

Step 6 Check whether the local switch and the neighboring switch have traps 1.3.6.1.2.1.14.16.2.1,1.3.6.1.2.1.14.16.2.2, 1.3.6.1.2.1.14.16.2.3, and 1.3.6.1.2.1.14.16.2.16.

l If the preceding traps are generated, refer to the related fault location procedure.

l If the preceding traps are not generated, go to Step 7.



733

Step 7 Collect trap messages, log messages, and configurations of the switch, and then contact Huaweitechnical personnel.

Step 8 End.

----End

Related Information

None

49.13 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.13hwOspfv3LastAuthKeyExpiry

Description

OSPFV3/2/LASTAUTHKEYEXPIRY:OID [oid] The last authentication key in keychain hasexpired. (RouterId=[gauge], IfName=[octet])

The last active key ID in the keychain expired.

Attribute



Parameters

Name Meaning

oid MIB object ID

RouterId Local router ID with its value as a decimal integer



The system may be attacked by invalid packets.

Possible Causes

The last active key ID in the keychain expired.



734

Procedure

Step 1 Run the display keychain keychain-name [ key-id key-id ] command to check keychainconfigurations.l If the last active key ID in the keychain expires, prolong its active period or configure a new

key ID.l If there is one or more active key IDs, go to Step 2.


Step 3 End.

----End


49.14 OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.14hwOspfv3AuthSequenceNumWrap

DescriptionOSPFV3/2/AUTHSEQUENCENUMWRAP:OID [oid] The cryptographic sequence numberhas wrapped. (RouterId=[gauge], IfName=[octet])

The higher order and lower order values of the 64-bit sequence number were misplaced.

Attribute



Parameters

Name Meaning

oid MIB object ID

RouterId Local router ID with its value as a decimal integer


Impact on the SystemThe device is open to potential attacks.



735

Possible CausesThe device has been running for a long time.

Procedure

Step 1 Run the display ospfv3 interface command to view the sequence number of the sent packet bychecking Higher Order Sequence Number and Lower Order Sequence Number and run thedisplay ospfv3 peer command to view the sequence number of the received packet by checkingReceived Higher Order Sequence Number and Received Lower Order SequenceNumber. Then, check whether the sequence numbers of the sent and received packets are thesame.l If the sequence numbers of the sent and received packets are the same, reconfigure all the

key IDs.l If the sequence numbers of the sent and received packets are different, go to Step 2.


Step 3 End.

----End




736

50 PoE

About This Chapter

NOTE

S6700 does not support PoE function.

50.1 POE_1.3.6.1.4.1.2011.5.25.195.40.2 hwPoePowerOff

50.2 POE_1.3.6.1.4.1.2011.5.25.195.40.3 hwPoePowerOn

50.3 POE_1.3.6.1.4.1.2011.5.25.195.40.8 hwPoePdConnected

50.4 POE_1.3.6.1.4.1.2011.5.25.195.40.9 hwPoePdDisconnected

50.5 POE_1.3.6.1.4.1.2011.5.25.195.40.10 hwPoePdClassInvalid

50.6 POE_1.3.6.1.4.1.2011.5.25.195.40.11 hwPoePdClassOvercurrent

50.7 POE_1.3.6.1.4.1.2011.5.25.195.40.16 hwPoePdPriorityDifferent

50.8 POE_1.3.6.1.4.1.2011.5.25.195.40.17 hwPoePowerOverUtilizationThreshold

50.9 POE_1.3.6.1.4.1.2011.5.25.195.40.18 hwPoePowerOverUtilizationThresholdResume

50.10 POE_1.3.6.1.4.1.2011.5.25.195.40.20 hwPoePowerAbsent

50.11 POE_1.3.6.1.4.1.2011.5.25.195.40.21 hwPoePowerAbsentResume

50.12 POE_1.3.6.1.4.1.2011.5.25.195.40.22 hwPoeRpsPowerOutputAlarm

50.13 POE_1.3.6.1.4.1.2011.5.25.195.40.23 hwPoeRpsPowerOutputAlarmResume

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 50 PoE


737

50.1 POE_1.3.6.1.4.1.2011.5.25.195.40.2 hwPoePowerOff

Description

POE/4/POWEROFF: OID [oid] PD powered off.(IfIndex=[INTEGER], Interface="[OCTET]")

The PD connected to the interface is powered off.

Attribute



Parameters

Name Meaning





The PD connected to the interface is powered off and cannot work normally.

Possible Causes

Cause 1:

The PD is removed.

Cause 2:

The PD is faulty.

Cause 3:

When the power is insufficient, the interface with higher priority preempts the power.

Cause 4:

The interface is automatically powered off in the power-off time range.

Procedure

Step 1 Check whether the PD is removed.

(1) If yes, go to step 2.



738


Step 2 Reinstall the PD.



Step 3 Check whether the alarm is reported.



Step 4 Check whether the power is sufficient.



Step 5 Check whether the priority of the interface is low.



Step 6 Check whether the interface priority is proper according to the requirements for the interfacepriority.

(1) If yes, use the poe priority command to re-set the interface priority.

(2) If not, increase the PoE power.

Step 7 Check whether the alarm is reported.



Step 8 Check whether the PD is faulty.



Step 9 Replace the PD. Then go to step 12.

Step 10 Check whether the interface is in the power-off time range.




Step 12 End.

----End

Related InformationPOE_1.3.6.1.4.1.2011.5.25.195.40.3_hwPoePowerOn



739

50.2 POE_1.3.6.1.4.1.2011.5.25.195.40.3 hwPoePowerOn

Description

POE/4/POWERON: OID [oid] PD powered on.(IfIndex=[INTEGER], Interface="[OCTET]")

The interface meets the following power supply conditions:

1. The power is sufficient.

2. The PD is identified by the system.

Attribute



Parameters

Name Meaning






Possible Causes

The alarm recovery message is generated after power-off.

Procedure

Step 1 This alarm indicates that a fault is rectified, and no action is required.

----End

Related Information

POE_1.3.6.1.4.1.2011.5.25.195.40.2_hwPoePowerOff

50.3 POE_1.3.6.1.4.1.2011.5.25.195.40.8 hwPoePdConnected



740

Description

POE/4/PDCONNECT: OID [oid] PD connected.(IfIndex=[INTEGER], Interface="[OCTET]")

The PD is connected to an interface.

Attribute



Parameters

Name Meaning






Possible Causes

The system detects a valid PD.

Procedure

Step 1 A new PD is added. This alarm is informational and no action is required.

----End

Related Information

POE_1.3.6.1.4.1.2011.5.25.195.40.9_hwPoePdDisconnected

50.4 POE_1.3.6.1.4.1.2011.5.25.195.40.9hwPoePdDisconnected

Description

POE/4/PDDISCONNECT: OID [oid] PD disconnected.(IfIndex=[INTEGER],Interface="[OCTET]")

The PD is disconnected from an interface.



741

Attribute



Parameters

Name Meaning




Impact on the SystemThe PD is unavailable and services are not affected.

Possible CausesA valid PD is removed.

Procedure

Step 1 Check whether the PD is removed.



Step 2 Reinstall the PD.

Step 3 End.

----End

Related InformationPOE_1.3.6.1.4.1.2011.5.25.195.40.8_hwPoePdConnected

50.5 POE_1.3.6.1.4.1.2011.5.25.195.40.10hwPoePdClassInvalid

DescriptionPOE/4/PDINVALIDCLASS: OID [oid] PD of an invalid class and power denied.(IfIndex=[INTEGER], Interface=/"[OCTET]/")

The system detects that the PD class is invalid.



742

Attribute



Parameters

Name Meaning




Impact on the SystemServices are not affected.


The PD may not comply with standards, whereas the switch supports 802.3af and 802.3at. Inthis case, the PD class cannot be identified by the switch.

Cause 2:

The PD hardware is faulty.

Procedure

Step 1 Run the poe legacy enable command on the interface to enable compatibility detection. Thencheck whether the alarm is cleared.



Step 2 Replace the PD complying with standards.

Step 3 End.

----End


50.6 POE_1.3.6.1.4.1.2011.5.25.195.40.11hwPoePdClassOvercurrent



743

DescriptionPOE/4/PDCLASSOVERCURRENT: OID [oid] has detected an overcurrent PD in classificationand power denied.(IfIndex=[INTEGER], Interface="[OCTET]")

The system detects that overcurrent occurs during PD classification.

Attribute



Parameters

Name Meaning




Impact on the SystemServices are not affected.

Possible CausesThe PD does not comply with standards.

Procedure

Step 1 You can run the poe high-inrush enable slot slot-id command in the system view to configurean interface to allow generation of the high pulse current. Then check whether the alarm iscleared.



Step 2 Replace the PD and check whether the alarm is cleared.




Step 4 End.

----End




744

50.7 POE_1.3.6.1.4.1.2011.5.25.195.40.16hwPoePdPriorityDifferent

Description

POE/4/PDPRIDIFF: OID [oid] priority inconsistent.(IfIndex=[INTEGER],Interface="[OCTET]", PortPriority=[INTEGER], PDPriority=[INTEGER])

The interface priority is different from the PD priority.

Attribute



Parameters

Name Meaning




PortPriority Indicates the interface priority.

PDPriority Indicates the PD priority.



Possible Causes

The interface prioriry is low, whereas the PD priority is high.

Procedure

Step 1 Run the poe priority command to change the interface priority to be higher than the PD priority.

----End

Related Information

None



745

50.8 POE_1.3.6.1.4.1.2011.5.25.195.40.17hwPoePowerOverUtilizationThreshold

Description

POE/4/PWRUTITHRESH: OID [oid] PSE is overdrawing power.(SlotID=[I NTEGER],ConsumingPower=[INTEGER], PowerThreshold=[INTEGER])

The total PoE power consumption is equal to or greater than the alarm threshold.

Attribute



Parameters

Name Meaning


SlotID Indicates the ID of the slot where the alarm is generated.

ConsumingPower Indicates the current power consumption.

PowerThreshold Indicates the power threshold.


If the alarm persists, all the PDs may be powered off because of insufficient power supply.

Possible Causes

The total power consumption of all the PDs is greater than or equal to the alarm threshold.

Procedure

Step 1 Plan the network according to the system power supply. Increase priorities of important devicesto prevent their power from being preempted. If the alarm persists, power off some PDs to ensuresystem reliability.

----End

Related Information

POE_1.3.6.1.4.1.2011.5.25.195.40.18_hwPoePowerOverUtilizationThresholdResume



746

50.9 POE_1.3.6.1.4.1.2011.5.25.195.40.18hwPoePowerOverUtilizationThresholdResume

Description

POE/4/PWRUTITHRESHRESUME: OID [oid] PSE is not overdrawing power. (SlotID=[INTEGER], ConsumingPower=[INTEGER], PowerThreshold=[INTEGER])

The total PoE power consumption is smaller than the alarm threshold.

Attribute



Parameters

Name Meaning


SlotID Indicates the ID of the slot where the alarm is generated.

ConsumingPower Indicates the current power consumption.

PowerThreshold Indicates the power threshold.



Possible Causes

The total power consumption of all the PDs is smaller than the alarm threshold.

Procedure

Step 1 This alarm indicates that a fault is rectified, and no action is required.

----End

Related Information

POE_1.3.6.1.4.1.2011.5.25.195.40.17_hwPoePowerOverUtilizationThreshold



747

50.10 POE_1.3.6.1.4.1.2011.5.25.195.40.20hwPoePowerAbsent

Description

POE/4/POEPWABSENT:OID [OID] POE Power is absent.(FrameID = [INTEGER], SlotID =[INTEGER])

An alarm is triggered when no PoE power supply on a PoE device is working properly.

Attribute



Parameters

Name Meaning

OID Indicates the OID of an alarm.

FrameID Indicates the chassis ID of a device in a stack.

SlotID Indicates the slot ID of the PoE power supply.



Possible Causes

No PoE power supply on the PoE device is working properly.

Procedure

Step 1 Check whether a PoE power supply exists on the device.

Step 2 If no, insert a PoE power supply to the device.

Step 3 If yes, check whether PoE power supply is damaged.

Step 4 If the PoE power supply is damaged, rectify the fault or replace the PoE power supply.

----End



748

50.11 POE_1.3.6.1.4.1.2011.5.25.195.40.21hwPoePowerAbsentResume

Description

POE/4/POEPWABSENTRESUME: OID [OID] POE Power is present.(FrameID =[INTEGER], SlotID = [INTEGER])

PoE power supply on a PoE device recovers from a power failure.

Attribute



Parameters

Name Meaning


FrameID Indicates the chassis ID of a device in a stack.

SlotID Indicates the slot ID of the PoE power supply.



Possible Causes

A PoE device previously had no PoE power supply working properly. Then a PoE power supplystarts to work properly.

Procedure


----End

50.12 POE_1.3.6.1.4.1.2011.5.25.195.40.22hwPoeRpsPowerOutputAlarm



749

DescriptionPOE/3/RPSALM:OID [oid] RPS power cannot provide POE power for this device.(DevID=[INTEGER])

An alarm is generated when the RPS power fails to provide full power for the connected PoEdevice.

Attribute



Parameters

Name Meaning


DevID Indicates the device ID.

Impact on the SystemPDs may fail to be powered on because of insufficient PoE power.

Possible CausesThe RPS power is the hot backup power for PoE devices and provides full power for a maximumof two PoE switches. If there are more than two PoE switches, the remaining PoE switchesgenerate an alarm, indicating that the RPS power cannot provide full PoE power.

Procedure

Step 1 Check whether the RPS power has 4815 power modules fully installed. If not, fully install 4815power modules on the RPS power. If so, this alarm is informational only, and no action isrequired.

----End

50.13 POE_1.3.6.1.4.1.2011.5.25.195.40.23hwPoeRpsPowerOutputAlarmResume

DescriptionPOE/6/RPSALMRESUME: OID [oid] RPS power can provide POE power for this device.(DevID=[INTEGER])

An alarm is cleared when the RPS power can provide the full power for the connected PoEdevice.



750

Attribute


1.3.6.1.4.1.2011.5.25.195.40.23 Cleared equipmentAlarm(5)

Parameters

Name Meaning


DevID Indicates the device ID.


Possible CausesWhen devices to which the RPS power provides full power are disconnected from the RPSpower, the RPS can provide 800 W PoE power for the other two PoE devices.

Procedure


----End



751

51 Portal

About This Chapter

51.1 WEB_1.3.6.1.4.1.2011.5.4.2.2.1.1 hwPortalServerUp

51.2 WEB_1.3.6.1.4.1.2011.5.4.2.2.1.2 hwPortalServerDown

51.3 WEB 1.3.6.1.4.1.2011.5.4.2.2.1.3 hwPortalMaxUserAlarm

51.4 WEB 1.3.6.1.4.1.2011.5.4.2.2.1.4 hwPortalUserClearAlarm

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 51 Portal


752

51.1 WEB_1.3.6.1.4.1.2011.5.4.2.2.1.1 hwPortalServerUp

DescriptionWEB/4/PortalServerUp:OID [oid] The portal server is up. (IP:[IPADDR], Vpn-Instance:[OCTET])

After server detection is enabled and the alarm action is configured, the device detects that thePortal server changes from Down to Up.

Attribute



Parameters

Name Meaning


IP Indicates the IP address of the Portal server.

Vpn-Instance Indicates the name of a VPN instance.


Possible CausesThe Portal server changes from Down to Up.

Procedure

Step 1 This log is informational only, and no action is required.

----End




753

51.2 WEB_1.3.6.1.4.1.2011.5.4.2.2.1.2 hwPortalServerDown

Description

WEB/4/PortalServerDown warning:OID [oid] The portal server is down. (IP:[IPADDR], Vpn-Instance:[OCTET])

After server detection is enabled and the alarm action is configured, the device detects that thePortal server changes from Up to Down.

Attribute



Parameters

Name Meaning


IP Indicates the IP address of the Portal server.

Vpn-Instance Indicates the name of a VPN instance.


The Portal authentication function does not work.

Possible Causes

The Portal server changes from Up to Down.

Procedure

Step 1 Check whether the Portal server can work properly and whether the Portal service can be usedproperly.

l If the Portal server works properly, check the network connectivity between the Portal serverand device. If the network connection is disconnected, restore the network connection.

l If the Portal server cannot work properly, restore the Portal server to the normal state.

----End

Related Information

None



754

51.3 WEB 1.3.6.1.4.1.2011.5.4.2.2.1.3 hwPortalMaxUserAlarm

Description

WEB/4/hwPortalMaxUserAlarm:OID [oid] The number of portal users reached the maximum.(Slot:[INTEGER],user-num:[INTEGER],threshold:[INTEGER]%)

The number of online Portal users exceeded the upper alarm threshold.

Attribute



Parameters

Name Meaning


Slot The value is fixed as 255.

user-num Indicates the maximum number of Portal authentication users allowed on thedevice.

threshold Indicates the upper alarm threshold on the percentage of online Portal authenticationuser count against the maximum number of Portal authentication users allowed onthe device.


None

Possible Causes

The number of online Portal users exceeded the upper alarm threshold.

Procedure

Step 1 This log message is informational only, and no action is required.

----End

Related Information

None



755

51.4 WEB 1.3.6.1.4.1.2011.5.4.2.2.1.4hwPortalUserClearAlarm

Description

WEB/4/hwPortalUserClearAlarm:OID [oid] The Portal Max User Alarm is cleared.(Slot:[INTEGER],user-num:[INTEGER],threshold:[INTEGER]%)

The number of online Portal users was equal to or smaller than the lower alarm threshold.

Attribute



Parameters

Name Meaning


Slot The value is fixed as 255.

user-num Indicates the maximum number of Portal authentication users allowed on thedevice.

threshold Indicates the lower alarm threshold on the percentage of online Portal authenticationuser count against the maximum number of Portal authentication users allowed onthe device.


None

Possible Causes

The number of online Portal users was equal to or smaller than the lower alarm threshold.

Procedure

Step 1 This log message is informational only, and no action is required.

----End



756




757

52 RDS

About This Chapter

52.1 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.1 hwRadiusAuthServerUp

52.2 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.2 hwRadiusAuthServerDown

52.3 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.3 hwRadiusAcctServerUp

52.4 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.4 hwRadiusAcctServerDown

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 52 RDS


758

52.1 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.1hwRadiusAuthServerUp

DescriptionRDS/4/RDAUTHUP:OID 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.1 RADIUS authentication server isup. (IP=[IPADDR], Vpn-Instance:[OCTET])

The communication of the RADIUS authentication server is restored.

Attribute


1.3.6.1.4.1.2011.5.25.40.15.2.2.1.1 Warning Device alarm(5)

Parameters

Name Meaning


IP Indicates the IP address of the authentication server.

Vpn-Instance VPN Instance

Impact on the SystemThe communication of the RADIUS authentication server is restored.

Possible CausesThe RADIUS authentication server is UP.

Procedure

Step 1 No action is required.

----End


52.2 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.2hwRadiusAuthServerDown



759

DescriptionRDS/4/RDAUTHDOWN:OID 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.2 RADIUS authenticationserver is down. (IP=[IPADDR], Vpn-Instance:[OCTET])

The communication of the RADIUS authentication server is interrupted.

Attribute


1.3.6.1.4.1.2011.5.25.40.15.2.2.1.2 Warning Communication alarm (2)

Parameters

Name Meaning


IP Indicates the IP address of the authentication server.


Impact on the SystemThe communication of the RADIUS authentication server is interrupted.

Possible CausesThe RADIUS authentication server is Down.

Procedure

Step 1 Check and ensure that the IP address is reachable.

----End


52.3 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.3hwRadiusAcctServerUp

DescriptionRDS/4/RDACCTUP:OID 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.3 RADIUS accounting server is up.(IP=[IPADDR], Vpn-Instance:[OCTET])

The communication of the RADIUS accounting server is restored.



760

Attribute


1.3.6.1.4.1.2011.5.25.40.15.2.2.1.3 Cleared Device alarm (5)

Parameters

Name Meaning


IP Indicates the IP address of the accounting server.



The communication of the RADIUS accounting server is restored.

Possible Causes

The RADIUS accounting server is Up.

Procedure

Step 1 No action is required.

----End

Related Information

None

52.4 RDS 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.4hwRadiusAcctServerDown

Description

RDS/4/RDACCTDOWN:OID 1.3.6.1.4.1.2011.5.25.40.15.2.2.1.4 RADIUS accounting serveris down. (IP=[IPADDR], Vpn-Instance:[OCTET])

The communication of the RADIUS accounting server is interrupted.

Attribute


1.3.6.1.4.1.2011.5.25.225.1.2.4 Warning Communication alarm (2)



761

Parameters

Name Meaning


IP Indicates the IP address of the accounting server.


Impact on the SystemThe communication of the RADIUS accounting server is interrupted.

Possible CausesThe RADIUS accounting server is Down.

Procedure

Step 1 Check and ensure that the IP address is reachable.

----End




762

53 RMON

About This Chapter

53.1 RMON_1.3.6.1.2.1.16.0.1 risingAlarm

53.2 RMON_1.3.6.1.2.1.16.0.2 fallingAlarm

53.3 RMON_1.3.6.1.4.1.2011.1.3.4.0.1 pririsingAlarm

53.4 RMON_1.3.6.1.4.1.2011.1.3.4.0.2 prifallingAlarm

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 53 RMON


763

53.1 RMON_1.3.6.1.2.1.16.0.1 risingAlarm

Description

RMON/4/ALARMUP: OID [OID] Alarm table [alarm-table-index] monitors [sample-object-oid] with the sample type being [sample-type], and the sampled alarm value [alarm-value] isgreater than or equal to [rising-value].

The value of the alarm entity was higher than uprise.

Attribute



Parameters

Name Meaning


alarm-table-index Indicates the index of the alarm entry.

sample-object-oid Indicates the OID of the sampled object.

sample-type Indicates the type of the sampled alarm.

alarm value Indicates the alarm value.

rising-value Indicates the upper threshold of the alarm.


None.

Possible Causes

Cause 1:

If the current sampled value was greater than or equal to this threshold, and the last sampledvalue was smaller than this threshold, the alarm was generated.

Cause 2:

When this alarm entry became valid, the first sampled value was greater than or equal to thisthreshold, and alarmStartupAlarm was equal to risingAlarm and risingOrFallingAlarm, thealarm was generated.



764

Procedure


----End

Related Information

None.

53.2 RMON_1.3.6.1.2.1.16.0.2 fallingAlarm

Description

RMON/4/ALARMFALL: OID [OID] Alarm table [alarm-table-index] monitors [sample-object-oid] with the sample type being [sample-type], and the sampled alarm value [alarm-value]is less than or equal to [falling-value].

The value of the alarm entity was lower than fallingthreshold.

Attribute



Parameters

Name Meaning


alarm-table-index Indicates the index of the alarm entry.

sample-object-oid Indicates the OID of the sampled object.


alarm-value Indicates the alarm value.

falling-value Indicates the lower threshold of the alarm.


None.

Possible Causes

Cause 1:

If the current sampled value was smaller than or equal to this threshold, and the last sampledvalue was greater than this threshold, the alarm was generated.



765

Cause 2:

After this alarm entry became valid, when the first sampled value was smaller than or equal tothis threshold, and the values of fallingAlarm, risingAlarm, and risingOrFallingAlarm wereequal, the alarm was generated.

Procedure


----End

Related Information

None.

53.3 RMON_1.3.6.1.4.1.2011.1.3.4.0.1 pririsingAlarm

Description

RMON/3/RISING:OID [OID] Private alarm table [alarm-line-index] monitors [description]with the sample type being [sample-type], and the sampled alarm value [alarm-value] is greaterthan or equal to [alarm-upper-limit].

The value of the alarm entity was higher than prialarmFallingThreshold.

Attribute


1.3.6.1.4.1.2011.1.3.4.0.1 Minor communicationsAlarm(2)

Parameters

Name Meaning


alarm-line-index Indicates the index of the alarm entry.

description Indicates the description of the alarm entry



alarm-upper-limit Indicates the upper threshold of the alarm.


None.



766

Possible Causes

This alarm occured in the NQA test.

Cause 1:

If the current sampled value was greater than or equal to this threshold, and the last sampledvalue was smaller than this threshold, the alarm was generated.

Cause 2:

When this alarm entry became valid, the first sampled value was greater than or equal to thisthreshold, and prialarmStartupAlarm was equal to risingAlarm and risingOrFallingAlarm, thealarm was generated.

Procedure


----End

Related Information

None.

53.4 RMON_1.3.6.1.4.1.2011.1.3.4.0.2 prifallingAlarm

Description

RMON/3/FALLING:OID [oid] Private alarm table [alram-line-index] monitors [description]with the sample type being [sample-type], and the sampled alarm value [alarm-value] is lessthan or equal to [alarm-upper-limit].

The value of the alarm entity was lower than prialarmFallingThreshold.

Attribute


1.3.6.1.4.1.2011.1.3.4.0.2 Minor communicationsAlarm(2)

Parameters

Name Meaning

oid Indicates the OID of the alarm.

alram-line-index Indicates the index of the alarm entry.

description Indicates the description of the alarm entry.




767

Name Meaning


alarm-upper-limit Indicates the lower threshold of the alarm.

Impact on the SystemSystem will not be affected.

Possible CausesThis alarm occured in the NQA test.

Cause 1:

If the current sampled value was smaller than or equal to this threshold, and the last sampledvalue was greater than this threshold, the alarm was generated.

Cause 2:

After this alarm entry became valid, when the first sampled value was smaller than or equal tothis threshold, and the values of fallingAlarm, risingAlarm, and risingOrFallingAlarm wereequal, the alarm was generated.


----End




768

54 RRPP

About This Chapter

54.1 RRPP_1.3.6.1.4.1.2011.5.25.113.4.1 hwRrppRingRecover

54.2 RRPP_1.3.6.1.4.1.2011.5.25.113.4.2 hwRrppRingFail

54.3 RRPP_1.3.6.1.4.1.2011.5.25.113.4.3 hwRrppMultiMaster

54.4 RRPP_1.3.6.1.4.1.2011.5.25.113.4.4 hwRrppTrackInterfaceDown

54.5 RRPP_1.3.6.1.4.1.2011.5.25.113.4.5 hwRrppTrackInterfaceUp

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 54 RRPP


769

54.1 RRPP_1.3.6.1.4.1.2011.5.25.113.4.1 hwRrppRingRecover

Description

RRPP/2/RNGUP:OID [oid] Domain [domain-id] ring [ring-id] is restored.

The faulty links on the ring network returned to the normal state.

Attribute


1.3.6.1.4.1.2011.5.25.113.4.1 Major equipmentAlarm(5)

Parameters

Name Meaning


domain-id Indicates the ID of an RRPP domain.

ring-id Indicates the ID of an RRPP ring.


Data flows will be interrupted in milliseconds when the link is switched.

Possible Causes

1.

The initial configurations of the RRPP ring network succeeded.

2.

The faulty links on the ring network returned to the complete state.

Procedure


----End

Related Information

RRPP_1.3.6.1.4.1.2011.5.25.113.4.2 hwRrppRingFail



770

54.2 RRPP_1.3.6.1.4.1.2011.5.25.113.4.2 hwRrppRingFail

Description

RRPP/2/RNGDN:OID [oid] Domain [domain-id] ring [ring-id] is failed.

A link on the ring network was faulty.

Attribute



Parameters

Name Meaning





Data flows will be interrupted in milliseconds when the link is switched.

Possible Causes

The complete ring became incomplete because a link was faulty on the ring.

Procedure

Step 1 Run the display rrpp verbose domain domainid command to check whether the status of eachinterface is unknown.



Step 2 Run the display rrpp verbose domain domainid command to check whether the status of eachinterface is Down.



Step 3 Check whether the interface board corresponding to the port is pulled out.





771

Step 4 Run the display this command on the interface to check whether the interface is shut down.






Step 6 Check whether devices or links between devices are faulty.



Step 7 Insert the board correctly and then check whether the alarm is cleared.



Step 8 Repair devices or links between devices and then check whether the alarm is cleared.




Step 10 End.

----End

Related Information

RRPP_1.3.6.1.4.1.2011.5.25.113.4.1 hwRrppRingRecover

54.3 RRPP_1.3.6.1.4.1.2011.5.25.113.4.3 hwRrppMultiMaster

Description

RRPP/2/MULMAST:OID [oid] A conflicting master node was detected on RRPP domain[domain-id] ring [ring-id].

The RRPP ring had more than one master node.

Attribute





772

Parameters

Name Meaning




Impact on the SystemThe configuration is incorrect. The RRPP ring will fail if it has multiple master nodes.

Possible CausesThe RRPP ring had more than one master node. As a result, service traffic is interrupted.

Procedure

Step 1 Run the display rrpp verbose domain domainid command to check whether multiple masternodes exist on the RRPP ring.l If so, go to Step 2.l If not, go to Step 3.

Step 2 Update configurations of the devices that should not be configured as master nodes as follows:

1. Run the undo ring ringid enable command and then the undo ring ringid command todelete configurations of the devices that should not be configured as master nodes. Where,the ringid is the ID of the RRPP ring that has error master nodes.

2. Run the ring ringid node-mode command to reconfigure the master node as required.3. Run the ring ringid enable command to re-activate the RRPP loop.

After the preceding configurations are complete, check whether the alarm is cleared.



Step 4 End.

----End


54.4 RRPP_1.3.6.1.4.1.2011.5.25.113.4.4hwRrppTrackInterfaceDown



773

DescriptionRRPP/2/TRACKDOWN:OID [oid] The BFD status of track interface was changed to DOWN.(DomainId=[INTEGER], RingId=[INTEGER], InterfaceIndex=[INTEGER])

The monitoring interface detected that BFD status became Down.

Attribute



Parameters

Name Meaning


DomainId Indicates the ID of an RRPP domain.

RingId Indicates the ID of an RRPP ring.


Impact on the SystemThe influence over services depends on the link that is Down.

l Data flows will be interrupted in milliseconds when the link is switched.l If both the master and slave links are Down, service flows will be interrupted till the link

becomes Up.

Possible CausesThe monitoring interface detected that BFD became Down.

Procedure

Step 1 Refer to procedures in 6.1 BFD_1.3.6.1.4.1.2011.5.25.38.3.1 hwBfdSessDown.

----End

Related InformationRRPP_1.3.6.1.4.1.2011.5.25.113.4.5 hwRrppTrackInterfaceUp

54.5 RRPP_1.3.6.1.4.1.2011.5.25.113.4.5hwRrppTrackInterfaceUp



774

Description

RRPP/2/TRACKUP:OID [oid] The BFD status of track interface was changed to UP.(DomainId=[INTEGER], RingId=[INTEGER], InterfaceIndex=[INTEGER])

The monitoring interface detected that the BFD became Up.

Attribute



Parameters

Name Meaning


DomainId Indicates the ID of an RRPP domain.

RingId Indicates the ID of an RRPP ring.



The influence over services depends on the link that is Up.

l Data flows will be interrupted in milliseconds when the link is switched.

l If both the master and slave links change from Down to Up, data flows will be interruptedduring the link failure.

Possible Causes

The monitoring interface detected that BFD became Up.

Procedure


----End

Related Information

RRPP_1.3.6.1.4.1.2011.5.25.113.4.4 hwRrppTrackInterfaceDown



775

55 RSVP

About This Chapter

NOTE


55.1 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.1 hwRsvpTeHelloLost

55.2 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.2 hwRsvpTeHelloLostRecovery

55.3 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.3 hwRsvpTeAuthFail

55.4 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.4 hwRsvpTeAuthSuccess

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 55 RSVP


776

55.1 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.1hwRsvpTeHelloLost

Description

RSVP/2/HWRSVPHELLOLOST:OID [oid] The RSVP Hello neighbor is lost. (IpAddress=[ipaddr])

The RSVP neighbor relationship was interrupted.

Attribute


1.3.6.1.4.1.2011.5.25.148.1.12.2.1 Major communicationsAlarm(2)

Parameters

Name Meaning


IpAddress IP address of a neighbor


If GR has been enabled, services will not be affected. If GR has not been enabled, the LSP goesDown or a master/slave LSP switchover is performed using FRR.

Possible Causes

The RSVP neighbor or the link over which the RSVP neighbor relationship is established becamefaulty.

Procedure

Step 1 Check whether the physical link or the RSVP neighbor is faulty.l If so, repair the physical link or restart the RSVP neighbor.l If not, go to step 2.

Step 2 Run the display ip routing-table command to check whether there is a route to the RSVPneighbor.l If so, go to step 3.l If not, configure an IGP to advertise routes.

Step 3 Collect the alarm, log, and configuration information, and contact Huawei technical supportpersonnel.



777

Step 4 End.

----End

Related Information

None.

55.2 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.2hwRsvpTeHelloLostRecovery

Description

RSVP/2/HWRSVPHELLOLOSTRECOVERY: OID [oid] The RSVP Hello neighbor isresumed. (IpAddress=[ipaddr])

The device is restored from the status of interruption of RSVP neighbor relationship.

Attribute



Parameters

Name Meaning





Possible Causes

RSVP Hello packets sent from the RSVP neighbor were received.

The RSVP neighbor relationship was deleted.

RSVP was disabled.

Procedure


----End



778


55.3 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.3hwRsvpTeAuthFail

DescriptionRSVP/2/HWRSVPAUTHFAIL: OID [oid] The RSVP neighbor authentication is incorrect.(IpAddress=[ipaddr])

RSVP authentication failed.

Attribute



Parameters

Name Meaning



Impact on the SystemNot all packets sent from the RSVP neighbor are processed. As a result, RSVP services cannotrun properly.

Possible CausesIncorrect authentication packets were received from the RSVP neighbor.

Procedure

Step 1 Run the display this command in the views of directly connected interfaces on both ends tocheck whether the authentication key information displayed in the mpls rsvp-te authenticationplain fields are the same.l If so, go to step 2.l If not, modify the configuration to keep authentication key information the same on both

ends.l If the authentication key information is not displayed, the authentication key is in encrypted

text. Modify the configuration to keep the authentication key information the same on bothends.



779

Step 2 Collect the alarm, log, and configuration information, and contact Huawei technical supportpersonnel.

Step 3 End.

----End

Related Information

None.

55.4 RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.4hwRsvpTeAuthSuccess

Description

RSVP/2/HWRSVPAUTHSUCCESS: OID [oid] The RSVP neighbor authentication is normal.(IpAddress=[ipaddr])

RSVP authentication succeeded.

Attribute



Parameters

Name Meaning





Possible Causes

Correct authentication packets sent from the RSVP neighbor were received.

RSVP authentication or RSVP was disabled.

The RSVP neighbor relationship was deleted.



780


----End




781

56 SECE

About This Chapter

56.1 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.1 hwStrackUserInfo

56.2 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.2 hwStrackIfVlanInfo

56.3 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.3 hwStrackDenyPacket

56.4 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.4 hwStrackErrorDown

56.5 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.1 hwARPSGatewayConflict

56.6 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.2 hwARPSEntryCheck

56.7 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.3 hwARPSPacketCheck

56.8 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.4 hwARPSDaiDropALarm

56.9 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.5 hwARPGlobleSpeedLimitALarm

56.10 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.6 hwARPIfSpeedLimitALarm

56.11 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.7 hwARPVlanSpeedLimitALarm

56.12 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.13 hwArpIfRateLimitBlockALarm

56.13 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.8 hwARPMissGlobleSpeedLimitALarm

56.14 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.9 hwARPMissIfSpeedLimitALarm

56.15 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.10 hwARPMissVlanSpeedLimitALarm

56.16 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.11 hwARPSIPSpeedLimitALarm

56.17 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.12 hwARPMissSIPSpeedLimitALarm

56.18 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.3.1 hwIPSGDropALarm

56.19 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.4.1 hwICMPGlobleDropALarm

56.20 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.4.2 hwICMPIfDropALarm

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 56 SECE


782

56.21 SECE_1.3.6.1.4.1.2011.5.25.32.4.1.14.1 hwXQoSStormControlTrap



783

56.1 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.1 hwStrackUserInfo

Description

SECE/4/STRACKUSER:OID [oid] Attack occurred.(Interface=[OCTET], SourceMAC=[OCTET], CVLAN=[INTEGER], PVLAN=[INTEGER], EndTime=[OCTET], TotalPackets=[INTEGER])

The system detects an attack.

Attribute

Alarm ID AlarmSeverity

Alarm Type

1.3.6.1.4.1.2011.5.25.165.2.2.1.1 Warning securityServiceOrMechanismViolation(10)

Parameters

Name Meaning


Interface Indicates the access interface of the attacker.

SourceMAC Indicates the Source MAC address of packets sent from the attacker.

CVLAN Indicates the inner VLAN ID of packets sent from the attacker.

PVLAN Indicates the outer VLAN ID of packets sent from the attacker.

EndTime Indicates the end time of the attack.

TotalPackets Indicates the number of packets received from the attacker.


The CPU is busy processing attack packets. As a result, normal service packets cannot beprocessed in time or even discarded.

Possible Causes

The rate of packets with the specified MAC address and VLAN ID sent to the CPU exceeds thealarm threshold.

Procedure

Step 1 Run the display auto-defend attack-source detail command to check the possible attack sourceand check whether the system is normal according to the protocol type and packet increase rate.



784

Step 2 If the user initiates the attack, you can configure attack source tracing and set the action takenon attack packets to deny, or configure a traffic policy to discard attack packets.

Step 3 If the fault cause is unknown, collect device configurations, alarms, and logs, and then contactthe Huawei technical personnel.

Step 4 End.

----End


56.2 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.2hwStrackIfVlanInfo

DescriptionSECE/4/STRACKPORT:OID [oid] Attack occurred.(Interface=[OCTET], CVLAN=[INTEGER], PVLAN=[INTEGER], EndTime=[OCTET], TotalPackets=[INTEGER])

The system detects an attack on an interface.

Attribute


Alarm Type


Parameters

Name Meaning



CVLAN Indicates the inner VLAN ID of the attacker.


EndTime Indicates the end time of the attack.

TotalPackets Indicates the number of packets received from the attacker.

Impact on the SystemThe CPU is busy processing attack packets. As a result, normal service packets cannot beprocessed in time or even discarded.



785

Possible Causes

The number of packets with the specified interface and VLAN ID sent to the CPU exceeds thealarm threshold.

Procedure

Step 1 Run the display auto-defend attack-source detail command to check the possible attack sourceon an interface and check whether the interface is normal according to the packet increase ratein entries.

Step 2 If an attack is initiated by a user and the user is the only one connected to the interface, you canshut down the interface and check whether the interface is normal.

Step 3 If the interface is connected to multiple users and some users initiate attacks, you can configureattack source tracing and set the action taken on attack packets to deny, or configure a trafficpolicy to discard attack packets.

Step 4 If only entries exist on the interface or entries cannot be determined, collect deviceconfigurations, alarms, and logs, and then contact Huawei technical personnel.

Step 5 End.

----End

Related Information

None

56.3 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.3hwStrackDenyPacket

Description

SECE/4/STRACK_DENY:OID [oid] Some packets are dropped because an attack is detected.(Interface=[OCTET], SourceMAC=[OCTET], SourceIP=[IPADDR], CVLAN=[INTEGER],PVLAN=[INTEGER])

The system detected an attack source and dropped packets sent from the attack source.

Attribute


Alarm Type




786

Parameters

Name Meaning



SourceMAC Indicates the Source MAC address of packets sent from the attacker.

SourceIP Indicates the Source IP address of packets sent from the attacker.

CVLAN Indicates the inner VLAN ID of packets sent from the attacker.



The device detected an attack to the CPU and dropped packets sent from the attack source to theCPU.

Possible Causes

A user sent a large number of packets to the user, and the number of packets exceeded thethreshold for identifying an attack.

Procedure

Step 1 Run the display auto-defend attack-source detail command to check the detected attack sourceand check whether it is an authorized user.

Step 2 If the detected attack source is an unauthorized user, you do not need to take any actions becausethe attack packets have been dropped by the device. Go to Step 6.

Step 3 If the detected attack source is an authorized user, add the user to the whitelist to exclude theuser from attack source tracing.

Step 4 If multiple attack sources are detected and all of them are authorized users, the attack sourcetracing threshold is too low. (The default value is 128 pps). Run the auto-defend thresholdthreshold command to increase the threshold. Go to Step 6.

Step 5 If the alarm persists, collect the configuration, alarms, and logs of the device and contact Huaweitechnical support personnel.

Step 6 End.

----End

Related Information

None



787

56.4 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.1.4hwStrackErrorDown

Description

SECE/4/STRACK_ERROR_DOWN:OID [oid] Interface's status is changed to error-downbecause an attack is detected. (Interface=[OCTET])

The system detected an attack source and set the source interface of the attack packets to error-down state.

Attribute


Alarm Type


Parameters

Name Meaning




The interface in error-down state cannot work.

Possible Causes

The device received a large number of packets from the interface, and the number of receivedpackets exceeded the threshold for identifying an attack. Therefore, the device identified theinterface as an attack source.

Procedure

Step 1 Run the display auto-defend attack-source detail command to check the detected attack sourceand check whether it is an authorized user.

Step 2 If the interface is attacked and it connects to only one user, you do not need to take any actionsbecause the attack has been blocked. Go to Step 5.

Step 3 If the interface connects to multiple users and some users initiate attacks, you can configureattack source tracing and set the action taken on attack packets to deny, or configure a trafficpolicy to discard attack packets.



788

Step 4 If only entries exist on the interface or entries cannot be determined, collect deviceconfigurations, alarms, and logs, and then contact Huawei technical personnel.

Step 5 End.

----End


56.5 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.1hwARPSGatewayConflict

DescriptionSECE/4/GATEWAY_CONFLICT:OID [oid] Gateway conflict. (SourceInterface=[OCTET],SourceIP=[OCTET], SourceMAC=[OCTET], PVLAN=[INTEGER], CVLAN=[INTEGER])

The system detects attack packets whose source IP addresses are the same as the gateway IPaddress.

Attribute


1.3.6.1.4.1.2011.5.25.165.2.2.2.1 Warning equipmentAlarm(5)

Parameters

Name Meaning


SourceInterface Indicates the source interface of packets.

SourceIP Indicates the source IP address of packets.

SourceMAC Indicates the source MAC address of packets.

PVLAN Indicates the outer VLAN ID of packets.

CVLAN Indicates the inner VLAN ID of packets.

Impact on the SystemIf this alarm is generated, the user gateway information may be modified by an attacker. As aresult, the user is attacked and user services are interrupted.

Possible CausesThe device is attacked by packets whose source IP address is the same as the gateway IP address.



789

Procedure

Step 1 Find the interface where the gateway conflict occurs according to the value ofSourceInterface.

Step 2 Lock the user who sends gateway conflict packets according to the values of SourceMAC andPVLAN.

Step 3 Check whether the allocated address of the user conflicts with the gateway address. If the addressconflicts, allocate an address to the user again. If the address does not conflict, the user may bethe attacker. In this case, you can take such measures as disconnecting the user.

----End

Related Information

None

56.6 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.2hwARPSEntryCheck

Description

SECE/4/ARP_ENTRY_CHECK:OID [oid] Arp entry attack. (SourceInterface=[OCTET],SourceIP=[OCTET], SourceMAC=[OCTET], PVLAN=[INTEGER], CVLAN=[INTEGER])

The system detects attack packets used to modify ARP entries.

Attribute



Parameters

Name Meaning









790


If this alarm is generated, ARP entries on the S2750&S5700&S6700 may be changed to ARPentries of attackers. As a result, user traffic is intercepted by attackers and user services areinterrupted.

Possible Causes

The S2750&S5700&S6700 is attacked by packets used to modify ARP entries.

Procedure

Step 1 Find the interface where attacks occur according to SourceInterface.

Step 2 Check whether users who are not in the DHCP snooping binding table range are connected tothe interface.

Step 3 If new users are connected, run related DHCP snooping commands to generate the DHCPsnooping binding table. Then find the interface where the gateway conflict occurs according tothe value of SourceInterface.

----End

Related Information

None

56.7 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.3hwARPSPacketCheck

Description

SECE/4/ARP_PACKET_CHECK:OID [oid] Invalid packet. (SourceInterface=[OCTET],SourceIP=[OCTET], SourceMAC=[OCTET], PVLAN=[INTEGER], CVLAN=[INTEGER])

The system detects invalid ARP packets.

Attribute



Parameters

Name Meaning





791

Name Meaning






If this alarm is generated, the S2750&S5700&S6700 may be attacked. If the attack traffic volumeis heavy, the S2750&S5700&S6700 is busy processing attack packets. As a result, services ofauthorized users are interrupted.

Possible Causes

The S2750&S5700&S6700 receives invalid ARP packets.

Procedure

Step 1 Find the interface where the gateway conflict occurs according to the value ofSourceInterface.

Step 2 Lock the user who sends gateway conflict packets according to the values of SourceMAC andPVLAN.

Step 3 Check whether the allocated address of the user conflicts with the gateway address. If the addressconflicts, allocate an address to the user again. If the address does not conflict, the user may bethe attacker. In this case, you can take such measures as disconnecting the user.

----End

Related Information

None

56.8 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.4hwARPSDaiDropALarm

Description

SECE/4/DAI_DROP_ALARM:OID [oid] The packet number droped by DAI reches[INTEGER1], exceed the alarm threshold [INTEGER2],Interface=[OCTET].

The number of packets discarded by Dynamic ARP Inspection (DAI) exceeds the alarmthreshold.



792

Attribute



Parameters

Name Meaning


INTEGER1 Indicates the number of discarded packets.

INTEGER2 Indicates the alarm threshold.

Interface Indicates the VLAN, source MAC address, and source IP address of packets


If this alarm is generated, the S2750&S5700&S6700 may be attacked. If the attack traffic volumeis heavy, the S2750&S5700&S6700 is busy processing attack packets. As a result, services ofauthorized users are interrupted.

Possible Causes

The number of packets discarded by DAI exceeds the alarm threshold.

Procedure


----End

Related Information

None

56.9 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.5hwARPGlobleSpeedLimitALarm

Description

SECE/4/ARP_GLOBLE_SPEEDLIMIT_ALARM:OID [oid] The globle arp packet speedexceed the speed-limit value configed [INTEGER].

The rate of ARP packets exceeds the alarm threshold.



793

Attribute



Parameters

Name Meaning


INTEGER Indicates the alarm threshold.

Impact on the SystemIf the alarm is generated, it indicates that the user traffic volume exceeds the threshold. Theexcess traffic is discarded by the S2750&S5700&S6700. As a result, user traffic may beinterrupted intermittently.

Possible CausesThe global ARP packet rate exceeds the alarm threshold.

Procedure


----End


56.10 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.6hwARPIfSpeedLimitALarm

DescriptionSECE/4/ARP_IF_SPEEDLIMIT_ALARM:OID [oid] The interface arp packet speed exceed thespeed-limit value configed [INTEGER], interface=[OCTET].

The rate of ARP packets on an interface exceeds the alarm threshold.

Attribute





794

Parameters

Name Meaning



Interface Indicates the source interface of packets.


If the alarm is generated, it indicates that the user traffic volume exceeds the threshold. Theexcess traffic is discarded by the S2750&S5700&S6700. As a result, user traffic may beinterrupted intermittently.

Possible Causes

The rate of ARP packets on an interface exceeds the alarm threshold.

Procedure


----End

Related Information

None

56.11 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.7hwARPVlanSpeedLimitALarm

Description

SECE/4/ARP_VLAN_SPEEDLIMIT_ALARM:OID [oid] The vlan arp packet speed exceedthe speed-limit value configed [INTEGER], Vlan [INTEGER].

The rate of ARP packets in a VLAN exceeds the alarm threshold.

Attribute





795

Parameters

Name Meaning



Vlan Indicates the outer VLAN ID of packets.



Possible Causes

The rate of ARP packets in a VLAN exceeds the alarm threshold.

Procedure


----End

Related Information

None

56.12 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.13hwArpIfRateLimitBlockALarm

Description

SECE/4/ARP_RATELIMIT_BLOCK_ALARM:OID [oid] All arp packets will be blocked oninterface [OCTET], block time [INTEGER] seconds.

After rate limiting on ARP packets is configured, the rate of ARP packets exceeds the rate limit.

Attribute


Alarm Type




796

Parameters

Name Meaning



INTEGER Indicates the time ARP packets are blocked.


All the ARP packets received on the interface are discarded.

Possible Causes

The rate of ARP packets received on the interface exceeds the rate limit.

Procedure


----End

Related Information

None

56.13 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.8hwARPMissGlobleSpeedLimitALarm

Description

SECE/4/ARPMISS_GLOBLE_SPEEDLIMIT_ALARM:OID [oid] The globle arp-miss packetspeed exceed the speed-limit value configed [INTEGER].

The rate of ARP Miss packets of the system exceeds the alarm threshold.

Attribute



Parameters

Name Meaning




797

Name Meaning




Possible Causes

The rate of ARP Miss packets of the system exceeds the alarm threshold.

Procedure


----End

Related Information

None

56.14 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.9hwARPMissIfSpeedLimitALarm

Description

SECE/4/ARPMISS_IF_SPEEDLIMIT_ALARM:OID [oid] The interface arp-miss packetspeed exceed the speed-limit value configed [INTEGER], interface [OCTET].

The rate of ARP Miss packets on an interface exceeds the alarm threshold.

Attribute



Parameters

Name Meaning






798



Possible Causes

The rate of ARP Miss packets on an interface exceeds the alarm threshold.

Procedure


----End

Related Information

None

56.15 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.10hwARPMissVlanSpeedLimitALarm

Description

SECE/4/ARPMISS_VLAN_SPEEDLIMIT_ALARM:OID [oid] The vlan arp-miss packetspeed exceed the speed-limit value configed [INTEGER], Vlan [INTEGER].

The rate of ARP Miss packets in a VLAN exceeds the alarm threshold.

Attribute



Parameters

Name Meaning



Vlan Indicates the outer VLAN ID of packets.



799



Possible Causes

The rate of ARP Miss packets in a VLAN exceeds the alarm threshold.

Procedure


----End

Related Information

None

56.16 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.11hwARPSIPSpeedLimitALarm

Description

SECE/4/ARP_SIP_SPEEDLIMIT_ALARM:OID [oid] The arp packet speed with source ip[OCTET] exceed the speed-limit value configed [INTEGER].

The rate of ARP packets with the specified source IP address exceeds the threshold.

Attribute



Parameters

Name Meaning


OCTET Indicates the source IP address of packets.




800



Possible Causes

The rate of ARP packets with the specified source IP address exceeds the threshold.

Procedure


----End

Related Information

None

56.17 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.2.12hwARPMissSIPSpeedLimitALarm

Description

SECE/4/ARPMISS_SIP_SPEEDLIMIT_ALARM:OID [oid] The arp-miss packet speed withsource ip [OCTET] exceed the speed-limit value configed [INTEGER].

The rate of ARP Miss packets with the specified source IP address exceeds the threshold.

Attribute



Parameters

Name Meaning


OCTET Indicates the source IP address of packets.




801

Impact on the SystemIf the alarm is generated, it indicates that the user traffic volume exceeds the threshold. Theexcess traffic is discarded by the S2750&S5700&S6700. As a result, user traffic may beinterrupted intermittently.

Possible CausesThe rate of ARP Miss packets with the specified source IP address exceeds the alarm threshold.

Procedure


----End

56.18 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.3.1hwIPSGDropALarm

DescriptionSECE/4/IPSG_DROP_ALARM:OID [oid] The packet number dropped by IPSG reaches[INTEGER1], exceed the alarm threshold [INTEGER2], interface [OCTET].

The number of packets discarded by IPSG exceeds the alarm threshold.

Attribute



Parameters

Name Meaning


INTEGER1 Indicates the number of discarded packets.


interface Indicates the source interface of packets on the S6700; indicates the VLAN,source MAC address, and source IP address of packets on the S2750 and S5700.

Impact on the SystemIf this alarm is generated, the S2750&S5700&S6700 may be attacked. If the attack traffic volumeis heavy, the S2750&S5700&S6700 is busy processing attack packets. As a result, services ofauthorized users are interrupted.



802

Possible Causes

The number of packets discarded by IPSG exceeds the alarm threshold.

Procedure

Step 1 Find the interface where attacks occur according to Interface in the alarm message.

Step 2 Check whether users who are not in the DHCP snooping binding table range are connected.

Step 3 If new users are connected, run related DHCP snooping commands to generate the DHCPsnooping binding table.

----End

Related Information

None

56.19 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.4.1hwICMPGlobleDropALarm

Description

SECE/4/ICMP_GLOBLE_SPEEDLIMIT_ALARM:OID [oid]. Globle icmp packet speedexceed the speed-limit value configed [INTEGER].

The rate of ICMP packets exceeds the alarm threshold.

Attribute



Parameters

Name Meaning







803

Possible Causes

The global ICMP packet rate exceeds the alarm threshold.

Procedure


----End

Related Information

None

56.20 SECE_1.3.6.1.4.1.2011.5.25.165.2.2.4.2hwICMPIfDropALarm

Description

SECE/4/ICMP_IF_SPEEDLIMIT_ALARM:OID [oid] Interface icmp packet speed exceed thespeed-limit value configed [INTEGER], Interface [OCTET].

The rate of ICMP packets on an interface exceeds the alarm threshold.

Attribute



Parameters

Name Meaning






Possible Causes

The rate of ICMP packets on an interface exceeds the alarm threshold.



804

Procedure


----End

Related Information

None

56.21 SECE_1.3.6.1.4.1.2011.5.25.32.4.1.14.1hwXQoSStormControlTrap

Description

SECE/4/TRAP:STORMCONTROL:OID [oid],StormControlAlarm(IfIndex:[INTEGER]BroadcastMinRate:[INTEGER] BroadcastMaxRate:[INTEGER]

MulticastMinRate:[INTEGER] MulticastMaxRate:[INTEGER] Action:[INTEGER] Interval:[INTEGER] Status:[INTEGER] UnicastMinRate:[INTEGER] UnicastMaxRate:[INTEGER]BroascastMode:[INTEGER] MulticastMode:[INTEGER] UnicastMode:[INTEGER])

The interface status changes.

Status of the interface is:

l blocked: When the rate of receiving packets is greater than the value of MaxRate and thestorm control action is block, the status of the interface is block.

l normal: Packets are normally forwarded.

l shutdown: When the rate of receiving packets is greater than the value of MaxRate and thestorm control action is shutdown, the status of the interface is shutdown.

Attribute


Alarm Type


Parameters

Name Meaning



BroadcastMinRate Indicates the minimum rate of broadcast packets.

BroadcastMaxRate Indicates the maximum rate of broadcast packets.



805

Name Meaning

MulticastMinRate Indicates the minimum rate of multicast packets.

MulticastMaxRate Indicates the maximum rate of multicast packets.

Action Indicates the storm control action.

Interval Indicates the interval for detecting storms.

Status Indicates the interface status.

UnicastMinRate Indicates the minimum rate of unknown unicast packets.

UnicastMaxRate Indicates the maximum rate of unknown unicast packets.

BroascastMode Indicates the storm control mode of broadcast packets.

MulticastMode Indicates the storm control mode of multicast packets.

UnicastMode Indicates the storm control mode of unknown unicast packets.

Impact on the SystemStorms may occur if the threshold is exceeded. Services are not affected.

Possible CausesThe interface traffic volume is greater than the upper threshold or smaller than the lowerthreshold.

Procedure

Step 1 Run the display storm-control interface command to check the storm control configuration onthe interface.

Step 2 If the interface status is shutdown, check whether the interface can be enabled according to theapplication scenario.

(1) If yes, run the undo shutdown command manually. Then go to step 4.


Step 3 Collect the device configurations, alarms, and logs, and then contact Huawei technical personnel.

Step 4 End.

----End




806

57 SNMP

About This Chapter

57.1 SNMP_1.3.6.1.6.3.1.1.5.1 coldStart

57.2 SNMP_1.3.6.1.6.3.1.1.5.2 warmStart

57.3 SNMP_1.3.6.1.6.3.1.1.5.5 authenticationFailure

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 57 SNMP


807

57.1 SNMP_1.3.6.1.6.3.1.1.5.1 coldStart

Description

SNMP/4/COLDSTART:OID [oid] coldStart.

The device was cold started.

Attribute



Parameters

Name Meaning

oid Indicates the ID of the trap.


The alarm, generated because of the device cold start, brings no adverse impact on the system.

Possible Causes

The device was cold started.

Procedure


----End

Related Information

None.

57.2 SNMP_1.3.6.1.6.3.1.1.5.2 warmStart

Description

SNMP/4/WARMSTART:OID [oid] warmStart.

The device was hot started, or the SNMP agent was enabled.



808

Attribute



Parameters

Name Meaning



The alarm, generated because of the device warm start, brings no adverse impact on the system.

Possible Causes

l The device was hot started.

l The SNMP agent was enabled.

Procedure


----End

Related Information

None.

57.3 SNMP_1.3.6.1.6.3.1.1.5.5 authenticationFailure

Description

SNMP/4/AUTHFAIL:OID [oid] authenticationFailure. (RemoteIpAddressType=[INTEGER],RemoteIpAddress=[STRING])

The authentication of SNMP failed.

Attribute


1.3.6.1.6.3.1.1.5.5 Warning other(1)



809

Parameters

Name Meaning


RemoteIpAddressType Indicates the IP address type of the remote peer

RemoteIpAddress Indicates the IP address of the remote peer


Possible Causesl The incorrect community name was used to connect devices.l The incorrect user name of SNMPv3 was used to connect devices.

Procedure

Step 1 Run the display current-configuration | include snmp-agent command in the user view tocheck whether the community name or user name of SNMPv3 is set correctly.l If the community name is set incorrectly, run the snmp-agent community command in the

system view to modify it to the correct one.l If the user name of SNMPv3 is set incorrectly, run the snmp-agent usm-user command in

the system view to create the correct user.l If the modification succeeds, go to Step 3.l If the alarm persists, go to Step 2.


Step 3 End.

----End




810

58 SOCKET

About This Chapter

58.1 SOCKET_1.3.6.1.4.1.2011.5.25.34.2.1 hwTCPMD5AuthenFail

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 58 SOCKET


811

58.1 SOCKET_1.3.6.1.4.1.2011.5.25.34.2.1hwTCPMD5AuthenFail

DescriptionSOCKET/4/TCP_MD5_FAIL:OID [oid] MD5 authentication failed. (SourceAddress=[IPADDR], SourcePort=[INTEGER], ForeignAddress=[IPADDR], ForeignPort=[INTEGER],Protocol=[OCTET], VrfName=[OCTET])

The MD5 authentication of the TCP connection failed.

Attribute



Parameters

Name Meaning


SourceAddress Indicates the local IP address of the TCP connection.

SourcePort Indicates the local port number.

ForeignAddress Indicates the destination IP address of the TCP connection.

ForeignPort Indicates the destination port number.

Protocol Indicates the name of the upper layer protocol.

VrfName Indicates the VRF name.

Impact on the SystemThe TCP connection cannot be set up normally and upper layer protocols such as BGP cannotset up sessions.

Possible Causes1: The MD5 authentication passwords on the two ends of the TCP connection were inconsistent.

2: Only one end of the TCP connection was configured with the MD5 authentication password.

Procedurel 1. Run the display current-configuration command on the devices at the two ends of the

TCP connection to check whether the devices are configured with MD5 authenticationpasswords.



812

– Only one device is configured with the MD5 authentication password. Configure theMD5 authentication password for the other devices and ensure that the MD5authentication passwords on the two devices must be the same, and then go to Step 3.

– If the two devices are configured with MD5 authentication passwords but the passwordsare different, go to Step 2.

2. Reconfigure the MD5 authentication passwords to make the MD5 authenticationpasswords consistent on the two ends of the TCP connection, and then go to Step 3.

3. Check whether the MD5 authentication is successful.



4. Collect the trap information, log information, and configuration of the router, and contactHuawei technical personnel.

5. End.

----End




813

59 SRM

About This Chapter

59.1 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.13 hwEntityOffline

59.2 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.14 hwEntityOnline

59.3 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.1 hwTempRisingAlarm

59.4 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.2 hwTempRisingResume

59.5 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.3 hwTempFallingAlarm

59.6 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.4 hwTempFallingResume

59.7 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.11 hwPortPhysicalEthHalfDuplexAlarm

59.8 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.12 hwPortPhysicalEthFullDuplexClear

59.9 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.13 hwPortPhysicalPortTypeChange

59.10 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67590











S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 59 SRM


814










59.30 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67590


















59.48 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.14 hwPortPhysicalAutoNegotiateFail

59.49 SRM_1.3.6.1.4.1.2011.5.25.129.2.17.1 hwOpticalPowerAbnormal

59.50 SRM_1.3.6.1.4.1.2011.5.25.129.2.17.2 hwOpticalPowerResume

59.51 SRM_1.3.6.1.4.1.2011.5.25.31.7.2.1 NETWORKHEARTBEATTRAP



815

59.1 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.13 hwEntityOffline

Description

SRM/3/ENTITYOFFLINE:

OID [OID] fan pull out.(EntityPhysicalIndex[INTEGER1], BaseTrapSeverity=[INTEGER2],BaseTrapProbableCause=[INTEGER3], BaseTrapEventType=[INTEGER4],EntPhysicalContainedIn=[INTEGER5], EntPhysicalName=[OCTET1],RelativeResource="[OCTET2]", ReasonDescription="[OCTET3]")

This alarm was generated when the fan module was removed.

Attribute



Parameters

Name Meaning


[INTEGER1] Entity index

[INTEGER2] Severity code

[INTEGER3] Error code

[INTEGER4] Code of the event type

[INTEGER5] Entity code

[OCTET1] Entity name

[OCTET2] Name of the affected component

[OCTET3] Fault description


After the fan module is removed, the temperature of the board increases, which may result infaults on the device. That is, packet loss may occur or even more seriously, the device may besuspended or abnormally reset.

Possible Causes

The fan module was removed.



816

Procedure

l Run the display device command to check whether the fan module is inserted.


– If not, insert the fan module. Then, go to Step 4.

l Remove and insert the fan module to check whether the alarm is cleared in case the alarmis mistakenly reported.



l Contact Huawei technical support personnel.

l End.

----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.1.14 hwEntityOnline

59.2 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.14 hwEntityOnline

Description

SRM/3/ENTITYONLINE:OID [OID] fan plug in.(EntityPhysicalIndex[INTEGER1],BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

This alarm was generated when the fan module was inserted.

Attribute



Parameters

Name Meaning








817

Name Meaning






Possible CausesThe fan module was inserted.


----End

Related InformationSRM_1.3.6.1.4.1.2011.5.25.129.2.1.13 hwEntityOffline

59.3 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.1hwTempRisingAlarm

DescriptionSRM/3/TEMPRISINGALARM:

OID [OID] temperature over major threshold .(EntityPhysicalIndex=[INTEGER1],BaseThresholdEntry_entPhysicalIndex=[INTEGER2],BaseThresholdEntry_hwBaseThresholdType=[INTEGER3],BaseThresholdEntry_hwBaseThresholdIndex=[INTEGER4], BaseTrapSeverity=[INTEGER5], BaseTrapProbableCause=[INTEGER6], BaseTrapEventType=[INTEGER7],EntPhysicalName=[OCTET], BaseThresholdValue=[INTEGER8], BaseThresholdUnit=[INTEGER9], BaseThresholdHighWarning=[INTEGER10], BaseThresholdHighCritical=[INTEGER11])

This alarm was generated when the temperature exceeded the upper threshold.

Attribute





818

Parameters

Name Meaning



[INTEGER2] Index of the entity causing this temperature alarm

[INTEGER3] Type of the detected entity (The value 1 indicates the temperature sensor of acertain type that is adopted by the S-switch.)

[INTEGER4] Index of the temperature sensor (The value begins from 1.)




[OCTET] Entity name

[INTEGER8] Current temperature

[INTEGER9] Unit of the temperature

[INTEGER10] Upper threshold of the temperature

[INTEGER11] Major upper threshold of the temperature

Impact on the SystemAfter the temperature exceeds the upper threshold, the device may fail to work normally. Thatis, packet loss may occur or even more seriously, the device may be suspended or abnormallyreset.

Possible Causes1. The upper threshold of the temperature was set to a low value.

2. The fan module was unavailable or faulty.

3. The ambient temperature was too high.

Procedure

Step 1 Run the display environment command to check whether the ambient temperature is too high.

(1) If so, reduce the ambient temperature by turning down the air-conditioner or keeping thedevice ventilated.

(2) If not, go to Step 2.

Step 2 Run the display environment command to check whether the set upper threshold of thetemperature is too low.

(1) If so, set the upper threshold of the temperature to a proper value. It is recommended thatyou run the undo temperature threshold unit unit-id command to restore the upper thresholdto the default value.



819

(2) If not, check whether the device can be equipped with a fan module. If so, go to Step 3; ifnot, go to Step 5.

Step 3 Check whether the device is installed with a fan module.

(1) If so, go to Step 4.

(2) If not, install a fan module.

Step 4 Run the display device command to check whether the fan module can work normally.


(2) If not, remove and then reinstall the fan module. If the alarm persists, replace the fan module.

Step 5 Run the display trapbuffer command to check whether any alarm is generated for theabnormality of the fan module.




Step 7 End.

If the following conditions are met, it indicates that the fault is rectified:

1. The alarm is not displayed on the NMS.2. After you run the display trapbuffer command, this alarm is not displayed.3. After you run the terminal monitor and terminal trapping commands, this alarm is not

displayed.

----End

Related InformationSRM_1.3.6.1.4.1.2011.5.25.129.2.2.2 hwTempRisingResume

59.4 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.2hwTempRisingResume

DescriptionSRM/3/TEMPRISINGRESUME:

OID [OID] temperature over major threshold resumes.(EntityPhysicalIndex=[INTEGER1],BaseThresholdEntry_entPhysicalIndex=[INTEGER2],BaseThresholdEntry_hwBaseThresholdType=[INTEGER3],BaseThresholdEntry_hwBaseThresholdIndex=[INTEGER4], BaseTrapSeverity=[INTEGER5], BaseTrapProbableCause=[INTEGER6], BaseTrapEventType=[INTEGER7],EntPhysicalName=[OCTET], BaseThresholdValue=[INTEGER8], BaseThresholdUnit=[INTEGER9], BaseThresholdHighWarning=[INTEGER10], BaseThresholdHighCritical=[INTEGER11])



820

This alarm was generated when the temperature restored to a normal value from the upperthreshold.

Attribute



Parameters

Name Meaning









[OCTET] Entity name



[INTEGER10] Upper threshold of the temperature

[INTEGER11] Major upper threshold of the temperature


Possible Causes1. The upper threshold of the temperature was set to a proper value.

2. The fan module was inserted and the temperature of the device was reduced to be lower thanthe upper threshold.

3. The ambient temperature was reduced to be lower than the upper threshold.


----End



821

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.2.1 hwTempRisingAlarm

59.5 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.3hwTempFallingAlarm

Description

SRM/3/TEMPFALLING:

OID [OID] temperature below minor threshold .(EntityPhysicalIndex=[INTEGER1],BaseThresholdEntry_entPhysicalIndex=[INTEGER2],BaseThresholdEntry_hwBaseThresholdType=[INTEGER3],BaseThresholdEntry_hwBaseThresholdIndex=[INTEGER4], BaseTrapSeverity=[INTEGER5], BaseTrapProbableCause=[INTEGER6], BaseTrapEventType=[INTEGER7],EntPhysicalName=[OCTET], BaseThresholdValue=[INTEGER8], BaseThresholdUnit=[INTEGER9], BaseThresholdLowWarning=[INTEGER10], BaseThresholdLowCritical=[INTEGER11])

This alarm was generated when the temperature was lower than the lower threshold.

Attribute



Parameters

Name Meaning









[OCTET] Entity name





822

Name Meaning

[INTEGER10] Lower threshold of the temperature

[INTEGER11] Major lower threshold of the temperature


After the temperature exceeds the lower threshold, the device may fail to work normally. Thatis, packet loss may occur or even more seriously, the device may be suspended or abnormallyreset.

Possible Causes

1. The lower threshold of the temperature was too high.

2. The ambient temperature was too low.

Procedure

l

1. Run the display environment command to check whether the ambient temperature istoo low.

(1) If so, increase the ambient temperature by turning up the air-conditioner.


2. Run the display environment command to check whether the set lower threshold of thetemperature is too high.

(1) If so, set the lower threshold of the temperature to a proper value. It is recommendedthat you run the undo temperature threshold unit unit-id command to restore the lowerthreshold to the default value.


3. End.

----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.2.4 hwTempFallingResume

59.6 SRM_1.3.6.1.4.1.2011.5.25.129.2.2.4hwTempFallingResume

Description

SRM/3/TEMPFALLINGRESUME:



823

OID [OID] temperature below minor threshold resumes.(EntityPhysicalIndex=[INTEGER1],BaseThresholdEntry_entPhysicalIndex=[INTEGER2],BaseThresholdEntry_hwBaseThresholdType=[INTEGER3],BaseThresholdEntry_hwBaseThresholdIndex=[INTEGER4], BaseTrapSeverity=[INTEGER5], BaseTrapProbableCause=[INTEGER6], BaseTrapEventType=[INTEGER7],EntPhysicalName=[OCTET], BaseThresholdValue=[INTEGER8], BaseThresholdUnit=[INTEGER9], BaseThresholdLowWarning=[INTEGER10], BaseThresholdLowCritical=[INTEGER11])

This alarm was generated when the temperature restored to a normal value from the lowerthreshold.

Attribute



Parameters

Name Meaning









[OCTET] Entity name



[INTEGER10] Lower threshold of the temperature

[INTEGER11] Major lower threshold of the temperature


Possible Causes1. The lower threshold of the temperature was set to a proper value.

2. The ambient temperature increased to be higher than the lower threshold.



824

Procedure


----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.2.3 hwTempFallingAlarm

59.7 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.11hwPortPhysicalEthHalfDuplexAlarm

Description

SRM/3/PortPhysicalEthHalfDuplexAlarm:

OID [OID] The port works in half duplex mode.(EntityPhysicalIndex=[INTEGER1],BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalName=[OCTET1],RelativeResource="[OCTET2]")

This alarm was generated when the Ethernet interface worked in half-duplex mode.

Attribute



Parameters

Name Meaning









It may result in packet loss, low bandwidth usage, or even network interruption.



825

Possible Causes1. The local interface or the peer interface was configured to work in half-duplex mode.

2. One of the connected interfaces worked in auto-negotiation mode whereas the other interfaceworked in non-automatic negotiation mode.

Procedurel

1. Check whether the interface is expected to work in half-duplex mode.



2. In the interface view of the local interface and the peer interface, run the display thiscommand to check whether the half-duplex mode is configured.

(1) If so, run the duplex full command to forcibly configure the interface to work in full-duplex mode.


3. In the interface view of the local interface and the peer interface, run the display thiscommand to check whether one interface works in auto-negotiation mode whereas the otherinterface works in non-automatic negotiation mode.

(1) If so, run the negotiation auto command to configure the interface working in non-automatic negotiation mode to work in auto-negotiation mode.


4. Contact Huawei technical support personnel.

5. End.

----End


59.8 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.12hwPortPhysicalEthFullDuplexClear

DescriptionSRM/4/PortPhysicalEthHalfDuplexClear: OID [oid] The port works in full duplex mode.(EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER],BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]")

The interface working mode changed to full duplex.



826

Attribute



Parameters

Name Meaning


EntityPhysicalIndex Indicates the interface index.




EntPhysicalName Indicates the interface name.

RelativeResource Indicates the relative resource.


The interface alternates between Up and Down states.

Possible Causes

The interface begins to work in half duplex mode. When the interface works in full duplex mode,a full duplex alarm is generated.

Procedure

Step 1 Check whether the duplex state of the interface is correct according to networking requirements.

Run the display interface interface-type [ interface-number ] command to check the duplexstate of the interface.

l If the duplex state of the interface is incorrect, modify the interface configuration.

l If the duplex state of the interface is correct, go to step 2.

Step 2 End.

----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.5.11 hwPortPhysicalEthHalfDuplexAlarm



827

59.9 SRM_1.3.6.1.4.1.2011.5.25.129.2.5.13hwPortPhysicalPortTypeChange

Description

SRM/4/PortPhysicalPortTypeChange: OID [oid] port type changed. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER],BaseTrapEventType=[INTEGER], EntPhysicalName="[OCTET]",EntityPhysicalLastPortType=[INTEGER], EntityPhysicalCurPortType=[INTEGER])

The interface media type changed.

NOTE

only S5700 supports this alarm.

Attribute



Parameters

Name Meaning


EntityPhysicalIndex Indicates the interface index.




EntPhysicalName Indicates the interface name.

EntityPhysicalLastPortType Indicates the previous media type.

EntityPhysicalCurPortType Indicates the current media type.


The optical module or cable needs to be replaced.

Possible Causes

1. The working mode of the combo interface was changed.



828

Procedure


----End

Related Information

None

59.10 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid67590

Description

SRM/3/ENTITYINVALID:

OID [OID] temperature chip exception.(EntityPhysicalIndex[INTEGER1], BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3], BaseTrapEventType=[INTEGER4],EntPhysicalContainedIn=[INTEGER5], EntPhysicalName=[OCTET1],RelativeResource="[OCTET2]", ReasonDescription="[OCTET3]" )

This alarm was generated when the chip was detected abnormal.

Attribute



Parameters

Name Meaning












829


The temperature of the board cannot be obtained. As a result, the fan module cannotautomatically adjust the rotational speed according to the temperature of the board. The fanmodule thus keeps working at the full rotational speed with too much noise. The services,however, are not affected.

Possible Causes

The IIC bus was faulty.

Procedure

l

1. Run the display environment [ slot slot-id ] command to check whether a fault occurson the temperature sensor due to the faulty IIC bus.

(1) If the character string "Read Temperature Fail" is displayed in the query result, itindicates that the IIC bus is faulty. In this case, you need to replace the device.

(2) If the character string "Read Temperature Fail" is not displayed in the query result, itindicates that the fault on the IIC bus is rectified. In this case, you need to go to Step 2.

2. End.

----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67590


Description

SRM/3/ENTITYINVALID:

OID [OID] Fan loss.(EntityPhysicalIndex[INTEGER1], BaseTrapSeverity=[INTEGER2],BaseTrapProbableCause=[INTEGER3], BaseTrapEventType=[INTEGER4],EntPhysicalContainedIn=[INTEGER5], EntPhysicalName=[OCTET1],RelativeResource="[OCTET2]", ReasonDescription="[OCTET3]")


Attribute





830

Parameters

Name Meaning




[INTEGER3] Error Code







When the fan module fails to work normally, the temperature of the board increases, which mayresult in faults on the board. That is, packet loss may occur or even seriously, the device maybe suspended or abnormally reset.

Possible Causes

The cable of the fan module was connected loosely or the fan hardware was faulty.

Procedure

l

1. Remove and insert the fan module and check whether the fault is rectified.

(1) If the fault persists, it indicates that the fan hardware is faulty. In this case, replace thefan module.

(2) If the fault is rectified, go to Step 2.

2. End.

----End

Related Information





831

DescriptionSRM/3/ENTITYINVALID:

OID [OID] PHY chip abnormal.(EntityPhysicalIndex[INTEGER1], BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3], BaseTrapEventType=[INTEGER4],EntPhysicalContainedIn=[INTEGER5], EntPhysicalName=[OCTET1],RelativeResource="[OCTET2]", ReasonDescription="[OCTET3]")


Attribute



Parameters

Name Meaning










Impact on the SystemThe services on the interface corresponding to the faulty PHY chip are interrupted.

Possible CausesThe PHY chip was faulty.

Procedurel

1. If the interface corresponding to the faulty PHY chip is Up, the device automaticallyresets. Then, you need to check whether the interface sends and receives packets normally.

(1) If not, it indicates that the PHY chip is faulty. In this case, you need to replace the device.




832

2. If the interface corresponding to the faulty PHY chip is Down, the device does not resetautomatically.

(1) If you do not use the interface, no action is required.

(2) If you need to use the interface, go to Step 3.

3. Run the reboot command to reset the device, and then check whether the interface sendsand receives packets normally.

(1) If not, it indicates that the PHY chip is faulty. In this case, you need to replace the device.


4. End.

----End

Related Information

None.


Description

SRM/3/ENTITYINVALID:OID [oid] PHY is abnormal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The PHY of an interface has failed.

Attribute


1.3.6.1.4.1.2011.5.25.129.2.1.9 Minor equipmentAlarm (5)

Parameters

Name Meaning


EntityPhysicalIndex Indicates a physical entity index.




833

Name Meaning

BaseTrapProbableCause Indicates the error code of the alarm.

BaseTrapEventType Indicates the event type.

EntPhysicalContainedIn Indicates contained physical entity code.

EntPhysicalName Indicates the physical entity name.

RelativeResource Indicates a sub-entity.

ReasonDescription Describes reason of the fault.


The interface specified in the alarm cannot send or receive packets.

Possible Causes

A hardware fault has occurred.

Procedure

l Use a normally running interface to replace the faulty interface, and reconfigure serviceparameters on this interface.

----End

Related Information



Description

SRM/3/ENTITYINVALID:OID [oid] XAUI Refrence Clock is abnormal.(EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER],BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER],EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The reference clock on a 10 gigabit Ethernet Attachment Unit Interface (XAUI) is invalid.



834

Attribute



Parameters

Name Meaning











The reference clock on the XAUI interface is invalid. If the fault persists, the interface card isreset.

Possible Causes


Procedure


----End

Related Information




835


Description

SRM/3/ENTITYINVALID:OID [oid] CPU Core Clock is abnormal. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER],BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET], RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The CPU clock is abnormal.

Attribute



Parameters

Name Meaning











If the fault persists, the card is reset.



836

Possible CausesA hardware fault has occurred.

Procedurel Contact Huawei technical support personnel.

----End

Related Information59.34 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 67961


DescriptionSRM/3/ENTITYINVALID:OID [oid] Switch Chip is abnormal. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER],BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET], RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The switching chip on a card has failed.

Attribute



Parameters

Name Meaning









837

Name Meaning





The card is reset.

Possible Causes


Procedure


----End

Related Information



Description

SRM/3/ENTITYINVALID:OID [oid] CPLD is abnormal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The complex programmable logical device (CPLD) on a card has failed.

Attribute





838

Parameters

Name Meaning










Impact on the SystemThe card is reset.



----End



DescriptionSRM/3/ENTITYINVALID:OID [oid] FPGA is abnormal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=



839

[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The field programmable gate array (FPGA) of a card has failed.

Attribute



Parameters

Name Meaning











If the fault persists, the card is reset.

Possible Causes


Procedure


----End



840

Related Information



Description

SRM/3/POWERFAULT:

OID [oid] Power normal.( EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER],BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER],EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

This alarm is generated when an entity is faulty.

Attribute



Parameters

Name Meaning



BaseTrapSeverity Indicates the severity level.

BaseTrapProbableCause Indicates the error code.


EntPhysicalContainedIn Indicates the code of the physical entity.

EntPhysicalName Indicates the name of the physical entity.

RelativeResource Indicates the sub-entity.

ReasonDescription Indicates the fault description.



841



Possible Causes

Cause 1

The power supply is not powered on.

Cause 2

The electronic label of the power supply is not loaded to the device.

Procedure

l Connect the power supply to the power source and switch on the power supply.

l Load correct electronic label of the power supply.

----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume_67966


Description

SRM/3/POWERABSENT: OID [oid] Power is absent. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The power supply unit of a device is removed.

Attribute



Parameters

Name Meaning




842

Name Meaning




NOTEThe error code for a power module removal alarm is 67967.







If the device uses only one power supply, the device is powered off after the power supply isremoved and services are interrupted.

Possible Causesl The internal power module encounters a power failure.

l The internal power module is removed.

l The lithium battery is removed.

l The lead-acid battery is removed.

Procedure

l Install the power supply.

----End

Related Information

SRM 1.3.6.1.4.1.2011.5.25 .129.2.1.10 hwEntityResume 67967




843

Description

SRM/3/ENTITYINVALID:OID [oid] light is abnormal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The indicator mode setting is invalid.

Attribute



Parameters

Name Meaning











The indicator mode setting is invalid, and the current indicator state does not show the actualmeaning.

Possible Causes




844

Procedure


----End

Related Information



Description

SRM/3/ENTITYINVALID:OID [oid] USB is abnormal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The USB port has failed.

Attribute



Parameters

Name Meaning










845

Name Meaning



Impact on the SystemThe device cannot be upgraded using a USB flash drive.



----End



DescriptionSRM/4/UsbPlugIn:OID [oid] u-disk plug in.(EntityPhysicalIndex=[INTEGER1],BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

The USB disk was inserted.

Attribute





846

Parameters

Name Meaning


EntityPhysicalIndex Indicates the index of an entity.


BaseTrapProbableCause Indicates the possible causes of an alarm.

BaseTrapEventType Indicates the type of an alarm.

EntPhysicalContainedIn Indicates the index of a parent entity.

EntPhysicalName Indicates the name of an entity.

RelativeResource Indicates the entity-related resources.

ReasonDescription Indicates the reason description of an alarm.


None.

Possible Causes

The USB disk was inserted.

Procedure


----End

Related Information



Description

SRM/1/USBPOWFAULT:OID [oid] USB 5v Power is fault.(EntityPhysicalIndex=[INTEGER1], BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

USB 5 V power supply was faulty.



847

Attribute



Parameters

Name Meaning










Impact on the SystemThe USB disk cannot work properly.

Possible CausesUSB power supply was faulty.


----End

Related InformationSRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume 68074


DescriptionSRM/1/ENTITYINVALID:OID [oid] I2C is abnormal. (EntityPhysicalIndex=[INTEGER1],BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],



848

BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

The I2C was faulty.

Attribute



Parameters

Name Meaning











Interfaces cannot work properly.

Possible Causes

The I2C was faulty.

Procedure

l The I2C fault causes some interfaces to fail to forward services. After the alarm is generated,switch services from the faulty interfaces to the interfaces working normally. If you stillwant to use the faulty interface, after the interface is recovered, run the clear configurationinterface interface-type interface-num command to clear interface configurations andreconfigure the interface.

l If the fault cannot be rectified and service switching fails, contact Huawei technical supportengineers.

----End



849

Related Information



Description

SRM/1/ENTITYINVALID:OID [oid] subcard is pulled out.(EntityPhysicalIndex=[INTEGER1], BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

The subcard was pulled out.

Attribute



Parameters

Name Meaning











Subcard-based services will be interrupted.

Possible Causes

The subcard was pulled out.



850

Procedure


----End

Related Information



Description

SRM/1/ENTITYINVALID:OID [oid] RTC abnormal..(EntityPhysicalIndex=[INTEGER1],BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

The RTC was faulty.

Attribute



Parameters

Name Meaning












851


When the RTC fails, the system time becomes the default value after the device is powered off.Therefore, system time-based services, such as the time range-based ACL, are affected.

Possible Causes

The RTC chip was faulty.

Procedure


----End

Related Information



Description

SRM/3/ENTITYINVALID:OID [oid] Write Flash Error. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

An error has occurred during a write operating on the flash memory.

Attribute



Parameters

Name Meaning






852

Name Meaning








Information generated during system operation may fail to be saved in the flash memory.

Possible Causes


Procedure


----End

Related Information

None


Description

SRM/3/POECHIPFAULT:OID [oid] Poe chip fault. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The PoE chip is faulty.



853

Attribute



Parameters

Name Meaning











The PoE function is abnormal.

Possible Causes


Procedure


----End

Related Information




854

59.30 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume67590

Description

SRM/3/ENTITYRESUME:

OID [OID] temperature chip resume.(EntityPhysicalIndex[INTEGER1], BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3], BaseTrapEventType=[INTEGER4],EntPhysicalContainedIn=[INTEGER5], EntPhysicalName=[OCTET1],RelativeResource="[OCTET2]", ReasonDescription="[OCTET3]")

This alarm was generated when the fault on the chip was detected being rectified.

Attribute



Parameters

Name Meaning











None

Possible Causes

The fault on the temperature sensor was rectified.



855

Procedure


----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67590


Description

SRM/3/ENTITYRESUME:

OID [OID] Fan ok.(EntityPhysicalIndex[INTEGER1], BaseTrapSeverity=[INTEGER2],BaseTrapProbableCause=[INTEGER3], BaseTrapEventType=[INTEGER4],EntPhysicalContainedIn=[INTEGER5], EntPhysicalName=[OCTET1],RelativeResource="[OCTET2]", ReasonDescription="[OCTET3]")

This alarm was generated when the fault on the chip was detected being rectified.

Attribute



Parameters

Name Meaning












856


None

Possible Causes

The fault on the fan module was rectified.

Procedure


----End

Related Information



Description

SRM/3/ENTITYRESUME:OID [oid] PHY normal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

A PHY fault has been resolved.

Attribute


1.3.6.1.4.1.2011.5.25 .129.2.1.10 Minor equipmentAlarm (5)

Parameters

Name Meaning







857

Name Meaning







Possible CausesThe hardware fault has been resolved.

Procedure


----End

Related Information59.13 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 67958


DescriptionSRM/3/ENTITYRESUME:OID [oid] XAUI Refrence Clock normal. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER],BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET], RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The reference clock fault on a XAUI interface has been resolved.

Attribute





858

Parameters

Name Meaning












ProcedureStep 1 This alarm is informational only, and no action is required.

----End



DescriptionSRM/3/ENTITYRESUME:OID [oid] CPU Core Clock normal. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER],



859

BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET], RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

A CPU clock fault has been resolved.

Attribute



Parameters

Name Meaning











None

Possible Causes

The hardware fault has been resolved.

Procedure


----End



860

Related Information



Description

SRM/3/ENTITYRESUME:OID [oid] Switch Chip normal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

A switching chip fault has been resolved.

Attribute



Parameters

Name Meaning












861


None

Possible Causes


Procedure


----End

Related Information



Description

SRM/3/ENTITYRESUME:OID [oid] CPLD normal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

A CPLD fault has been resolved.

Attribute



Parameters

Name Meaning







862

Name Meaning








Procedure


----End



DescriptionSRM/3/ENTITYRESUME:OID [oid] FPGA normal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

A FPGA fault has been resolved.

Attribute





863

Parameters

Name Meaning












Procedure


----End



DescriptionSRM/3/POWERRESUME:



864

OID [oid] Power normal.( EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER],BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER],EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

This alarm is generated when an entity recovers.

Attribute



Parameters

Name Meaning












Possible Causes

Cause 1

The power module is switched on.

Cause 2

The correct electronic label of the power module is loaded and the power supply works normally.



865

Procedure

l None.

----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid_67966


Description

SRM/3/POWERPRESENT: OID [oid] Power is present. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The power supply unit of a device is installed again.

Attribute


1.3.6.1.4.1.2011.5.25 .129.2.1.10 Error equipmentAlarm (5)

Parameters

Name Meaning




BaseTrapProbableCause Indicates the error code.NOTE

The error code for a power supply recovery alarm is 67967.





866

Name Meaning






Possible Causesl The internal power module is powered on.

l The internal power module is installed on the device.

l A lithium battery is installed on the device.

l A lead-acid battery is installed on the device.

Procedure

l None.

----End

Related Information



Description

SRM/3/ENTITYRESUME:OID [oid] light normal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName=[OCTET],RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The indicator mode setting failure has been resolved.

Attribute





867

Parameters

Name Meaning












ProcedureStep 1 This alarm is informational only, and no action is required.

----End



DescriptionSRM/3/ENTITYRESUME:OID [oid] USB normal. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=



868


A USB port fault has been resolved.

Attribute



Parameters

Name Meaning











None

Possible Causes


Procedure


----End



869

Related Information



Description

SRM/4/UsbPlugOut:OID [oid] u-disk plug out.(EntityPhysicalIndex=[INTEGER1],BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

The USB disk was pulled out.

Attribute



Parameters

Name Meaning











The USB disk is unavailable.

Possible Causes

The USB disk was pulled out.



870

Procedure


----End

Related Information



Description

SRM/1/ENTITYRESUME:OID [oid] I2C is normal. (EntityPhysicalIndex=[INTEGER1],BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

The I2C fault was rectified.

Attribute


1.3.6.1.4.1.2011.5.25.129.2.1.10 Error equipmentAlarm(5)

Parameters

Name Meaning












871


None.

Possible Causes

The I2C fault was rectified.

Procedure


----End

Related Information



Description

SRM/1/ENTITYRESUME:OID [oid] RTC normal.(EntityPhysicalIndex=[INTEGER1],BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

The RTC fault was rectified.

Attribute



Parameters

Name Meaning








872

Name Meaning






None.

Possible Causes

The RTC fault was rectified.

Procedure


----End

Related Information



Description

SRM/1/ENTITYRESUME:OID [oid] subcard is plugged in.(EntityPhysicalIndex=[INTEGER1], BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")


Attribute





873

Parameters

Name Meaning











None.

Possible Causes


Procedure


----End

Related Information



Description

SRM/4/USBPOWRESUME:OID [oid] USB 5v Power is resume.(EntityPhysicalIndex=[INTEGER1], BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3],BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5],EntPhysicalName=[OCTET1], RelativeResource="[OCTET2]",ReasonDescription="[OCTET3]")

USB 5 V power supply fault was rectified.



874

Attribute



Parameters

Name Meaning










Impact on the SystemThe USB disk recovers and works properly.

Possible CausesUSB power supply fault was rectified.


----End

Related InformationSRM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid 68074


DescriptionSRM/3/POECHIPRESUME:OID [oid] Poe chip resume. (EntityPhysicalIndex=[INTEGER],BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=



875


A PoE chip fault has been resolved.

Attribute



Parameters

Name Meaning











None

Possible Causes


Procedure


----End



876


59.48 SRM_1.3.6.1.4.1.2011.5.25.129.2.1.14hwPortPhysicalAutoNegotiateFail

DescriptionSRM/3/PORTAUTONEGOTIATEFAILALARM:OID [oid] port auto negotiation failed.(EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER],BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalName=[OCTET], RelativeResource="[OCTET]")

Auto-negotiation on an interface has failed.

Attribute



Parameters

Name Meaning








Impact on the SystemThe interface turns to Down state.

Possible CausesNegotiation with the remote interface fails.



877

Procedure

Step 1 Check whether the remote interface is working in auto-negotiation mode. If not, enable auto-negotiation on the remote interface.

Step 2 If the remote interface is working in auto-negotiation mode but is abnormal, connect the localinterface to another interface.

Step 3 If the negotiation still fails, contact Huawei technical personnel.

----End

Related Information

None

59.49 SRM_1.3.6.1.4.1.2011.5.25.129.2.17.1hwOpticalPowerAbnormal

Description

SRM/3/OPTPWRABNORMAL: OID [oid] Optical module power is abnormal.(EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER],BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER],EntPhysicalContainedIn=[INTEGER], EntPhysicalName="[OCTET]",RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

An alarm is generated when the transmit or receive power of an optical module is out of theallowed range.

Attribute


1.3.6.1.4.1.2011.5.25.129.2.17.1 minor equipmentAlarm(5)

Parameters

Name Meaning




BaseTrapProbableCause Indicates the possible causes of the alarm.


EntPhysicalContainedIn Indicates the parent index of the entity.



878

Name Meaning

EntPhysicalName Indicates the name of the entity.

RelativeResource Indicates the part related to the alarm.




Possible Causes

Cause 1

The transmit power of the optical module exceeds the maximum value.

Cause 2

The transmit power of the optical module falls below the minimum value.

Cause 3

The receive power of the optical module exceeds the maximum value.

Cause 4

The receive power of the optical module falls below the minimum value.

NOTE

If the interface is in shutdown, errordown, or loopback state, this alarm is not generated when the transmit powerfalls below the minimum value. When a link fault occurs, the interface enabled with the ALS function sendsLOS signals. This alarm is not generated when the transmit power or the receive power falls below the minimumvalue.

Procedure

Step 1 Run the display transceiver verbose command to view and locate the abnormal optical modulepower to determine whether to replace the optical module.

----End

Related Information

SRM_1.3.6.1.4.1.2011.5.25.129.2.17.2 hwOpticalPowerResume

59.50 SRM_1.3.6.1.4.1.2011.5.25.129.2.17.2hwOpticalPowerResume



879

DescriptionSRM/4/OPTPWRRESUME: OID [oid] Optical module recovered from power abnormal.(Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER] , EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]",RelativeResource="[OCTET]",ReasonDescr="[OCTET]")

An alarm is generated when the transmit or receive power of the optical module recovers to theallowed range.

Attribute



Parameters

Name Meaning




BaseTrapProbableCause Indicates the possible causes of the alarm.


EntPhysicalContainedIn Indicates the parent index of the entity.

EntPhysicalName Indicates the name of the entity.

RelativeResource Indicates the part related to the alarm.



Possible CausesThe optical module power recovers to the allowed range.

Procedure


----End

Related InformationSRM_1.3.6.1.4.1.2011.5.25.129.2.17.1 hwOpticalPowerAbnormal



880

59.51 SRM_1.3.6.1.4.1.2011.5.25.31.7.2.1NETWORKHEARTBEATTRAP

DescriptionSRM/3/NETWORKHEARTBEATTRAP: OID [oid] Network heart beat.

The device periodically sends heartbeat packets to the NMS. The NMS considers the devicepresent if it receives heartbeat packets from the device.

Attribute



Parameters

Name Meaning



Possible CausesThe device reports this alarm after it is enabled to send heartbeat packets to the NMS.

Procedure

Step 1 This message is informational only, and no action is required.

----End




881

60 SYSMIB

About This Chapter

60.1 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.1 hwSysClockChangedNotification

60.2 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.2 hwSysReloadNotification

60.3 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.1 hwPatchErrorTrap

60.4 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.2 hwPatchActiveOverTimeTrap

60.5 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.3 hwPatchMalfunctionComebackTrap

60.6 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.8 hwSysSlaveSwitchSuccessNotification

60.7 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.9 hwSysSlaveSwitchFailNotification

60.8 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.10 hwSysIssuNotification

60.9 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.14 hwSysCfgFileErrorNotification

60.10 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.15 hwSysImageErrorNotification

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 60 SYSMIB


882

60.1 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.1hwSysClockChangedNotification

DescriptionSYSMIB/4/CLOCK_CHANGE:OID [oid] System clock changed.

Indicates that the system clock is adjusted.

Attribute



Parameters

Name Meaning



Possible CausesThis trap is used to record the adjustment of the system clock.

Procedure


----End


60.2 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.2hwSysReloadNotification

DescriptionSYSMIB/4/RELOAD_END:[OID] Reload operation completed



883

Indicates that system has restarted completely.

Attribute



Parameters

Name Meaning




Possible Causes

The device was restarted successfully by the NMS.

Procedure


----End

Related Information

None

60.3 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.1hwPatchErrorTrap

Description

SYSMIB/4/PAT_FAIL:OID [oid] Patch operation failed. (ErrorIndex=[GAUGE], ErrorSlot=[GAUGE], PatchIndex=[GAUGE], ErrorCode=[INTEGER], PatchFileName=[OCTET])

The patch operation failed due to the error in the patch file.

Attribute





884

Parameters

Name Meaning


ErrorIndex Indicates the error index.

ErrorSlot Indicates the slot ID.

PatchFileName Indicates the name of a patch file.

PatchIndex Indicates the index of a patch file.

ErrorCode Indicates an error code.


The loaded patch is not validated.

Possible Causes

1:

The patch operation failed due to the error in the patch file.

2:

The patch operation is repeated.

Procedure

Step 1 Collect user logs and the device version and loaded patches, and then contact Huawei technicalsupport personnel.

----End

Related Information

None

60.4 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.2hwPatchActiveOverTimeTrap

Description

SYSMIB/4/PAT_OVERTIME:OID [oid] The patch is active for 24 hours.

Indicates that the patch was activated for 24 hours by running the patch active command. Thepatch, however, was not in the running state by running the patch run command.



885

Attribute



Parameters

Name Meaning


Impact on the SystemThe newly-loaded patches, after the restart of the system, cannot be validated after the nextrestart.

Possible Causes1.

The patch was activated for 24 hours, but not set into the running state.

2.

The RPC was busy in communication or memory was insufficient.

Procedure

Step 1 Run the display patch-information command to check the patch status.

Step 2 Check whether the patch is in the running state.l If so, go to Step 6.l If not, go to Step 3.

Step 3 To determine whether to set the patch to the running state, check whether the patch needs to bevalidated in next restart.l If so, go to Step 4.l If not, go to Step 6.

Step 4 Check whether the patch status goes into the running state after running the patch run command.l If so, go to Step 6.l If not, go to Step 5.


Step 6 End.

----End




886

60.5 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.5.3hwPatchMalfunctionComebackTrap

DescriptionSYSMIB/1/PAT_RECOVER:OID [oid] The patch fault is removed.

Indicates that a patch operation fails for the first time, and then succeeds in the next time. Thepatch operations include:

1. Load the patch by running the patch load command.2. Activate the patch by running the patch active command.

Attribute



Parameters

Name Meaning



Possible CausesA patch operation fails for the first time, and then succeeds in the next time.

Procedure


----End


60.6 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.8hwSysSlaveSwitchSuccessNotification



887

Description

SYSMIB/3/SWITCH_SUCCESS:OID [oid] Slave switchover success.

Succeeded in performing the master-slave switchover.

Attribute



Parameters

Name Meaning




Possible Causes

The master-slave switchover is performed manually.

Procedure


----End

Related Information

None.

60.7 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.9hwSysSlaveSwitchFailNotification

Description

SYSMIB/3/SWITCH_FAIL:OID [oid] Slave switchover fail.

Failed to perform the master-slave switchover.



888

Attribute



Parameters

Name Meaning




Possible Causesl The master-slave switchover function is not enabled on the device.

l The slave main control board is unavailable.

l An error causes the master-slave switchover to be failed.

Procedure

Step 1 Run the display current-configuration command to check whether the master-slave switchoverfunction is enabled on the device.



Step 2 Run the display device command to check whether the slave main control board on the deviceis unavailable.




Step 4 End.

----End

Related Information

None.

60.8 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.10hwSysIssuNotification



889

Description

SYSMIB/4/ISSUCONDITION:OID [OID] ISSU upgrade complete. (issuState=[integer],issuConditionCheck=[integer])

ISSU upgrade was complete.

Attribute



Parameters

Name Meaning

oid Indicates the OID of an alarm.

issuState Indicates the ISSU upgrade state.

The value can only be 1, indicating that the device is not in the ISSUupgrade state.

issuConditionCheck Indicates the ISSU check status.l The value 1 indicates that no error is detected in the ISSU check.l The value 2 indicates that the standby main control board is not in

the real-time backup state.l The value 3 indicates that some LPU does not work properly.l The value 5 indicates other errors.



Possible Causes

ISSU upgrade was complete.

Procedure


----End

Related Information

None.



890

60.9 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.14hwSysCfgFileErrorNotification

Description

SYSMIB/4/CFGFILE_FAIL:OID [oid] The configuration file is invalid.(HwSysCFGFileIndex=[HwSysCFGFileIndex], HwSysCFGFileName=[HwSysCFGFileName], HwSysCfgFileReason=[HwSysCfgFileReason])

Failed to load the configuration file.

Attribute


1.3.6.1.4.1.2011.5.25.19.2.14 Warning other(1)

Parameters

Name Meaning


HwSysCFGFileIndex Index ID

HwSysCFGFileName Name of the configuration file

HwSysCfgFileReason Causes triggering the alarm



Possible Causes

Failed to load the configuration file.

Procedure

Step 1 Check whether the configuration file exists on the device.

l If the configuration file does not exist, download a configuration file from the server.

l If the configuration file exists, go to Step 2.

Step 2 Check whether the length of the configuration file name is valid.



891

l Check whether the length of the file name with the full path name exceeds 48 Englishcharacters. If the length exceeds 48 English characters, run the rename command to renamethe file.

l If the length is valid, go to Step 3.


Step 4 End.

----End

Related Information

None.

60.10 SYSMIB_1.3.6.1.4.1.2011.5.25.19.2.15hwSysImageErrorNotification

Description

SYSMIB/4/IMAGE_FAIL:OID [oid] The image file failed to upgrade. (HwSysImageIndex=[HwSysImageIndex], HwSysCurrentImageName=[HwSysCurrentImageName],HwSysUpgradeImageName=[HwSysUpgradeImageName], HwSysImageReason=[HwSysImageReason])

Failed to upgrade software.

Attribute


1.3.6.1.4.1.2011.5.25.19.2.15 Warning other(1)

Parameters

Name Meaning


HwSysImageIndex Index ID

HwSysCurrentImageName Name of the current system software package

HwSysUpgradeImageName Name of the target system software package

HwSysImageReason Causes triggering the alarm



892


Possible CausesFailed to upgrade software.

Procedure

Step 1 Check whether the target system software package exists on the device.l If the system software package does not exist, download a system software package from

the server.l If the system software package exists, go to Step 2.

Step 2 Check whether the length of the system software package name is valid.l Check whether the length of the package name with the full path name exceeds 48 English

characters. If the length exceeds 48 English characters, run the rename command to renamethe package.

l If the length is valid, go to Step 3.

Step 3 Check whether the system software package is in the root directory.l If the system software package is not in the root directory, run the copy command to copy

the package to the root directory.l If the system software package is in the root directory, go to Step 4.


Step 5 End.

----End




893

61 TRUNK

About This Chapter

61.1 TRUNK_1.3.6.1.4.1.2011.5.25.41.3.9 hwExtLinkDown

61.2 TRUNK_1.3.6.1.4.1.2011.5.25.41.3.10 hwExtLinkUp

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 61 TRUNK


894

61.1 TRUNK_1.3.6.1.4.1.2011.5.25.41.3.9 hwExtLinkDown

Description

TRUNK/2/EXT_LINKDOWN:OID [oid] The link status of the trunk member interface turnedto DOWN.(ifIndex=[INTEGER], ifAdminStatus=[INTEGER], ifOperStatus=[INTEGER],ifDescr=[STRING], hwIFExtPhyStatus=[INTEGER], hwIFExtMemberOf=[STRING])

The status of the Trunk member interface became Down.

Attribute


1.3.6.1.4.1.2011.5.25.41.3.9 Major other(1)

Parameters

Name Meaning


ifIndex Indicates the interface index.

ifAdminStatus Indicates the management status of the interface.

ifOperStatus Indicates the status of the interface.

ifDescr Indicates the name of the interface.

hwIFExtPhyStatus Indicates the physical status of the interface.

hwIFExtMemberOf Indicates the name of the Trunk interface.


The interface cannot forward packets normally.

Possible Causes

The interface became Down and the link was disconnected.

Procedure

Step 1 Run the display this command in the interface view to check whether interfaces on both endsof the aggregation group are shut down.






895



Step 3 Check whether the cable and optical module are loosened or dropped.



Step 4 Connect the physical link correctly and then check whether the alarm is cleared.




Step 6 End.

----End

Related Information

TRUNK_1.3.6.1.4.1.2011.5.25.41.3.10 hwExtLinkUp

61.2 TRUNK_1.3.6.1.4.1.2011.5.25.41.3.10 hwExtLinkUp

Description

TRUNK/2/EXT_LINKUP:OID [oid] The link status of the trunk member interface turned toUP.(ifIndex=[INTEGER], ifAdminStatus=[INTEGER], ifOperStatus=[INTEGER], ifDescr=[STRING], hwIFExtPhyStatus=[INTEGER], hwIFExtMemberOf=[STRING])

The status of the Trunk member interface became Up.

Attribute


1.3.6.1.4.1.2011.5.25.41.3.10 Major other(1)

Parameters

Name Meaning


ifIndex Indicates the interface index.

ifAdminStatus Indicates the management status of the interface.

ifOperStatus Indicates the status of the interface.

ifDescr Indicates the name of the interface.



896

Name Meaning

hwIFExtPhyStatus Indicates the physical status of the interface.

hwIFExtMemberOf Indicates the name of the Trunk interface.

Impact on the SystemTraffic will be recovered.

Possible Causes1.

The undo shutdown command was run in the interface view.

2.

The interface became Up and the link was recovered.

3.

The link layer protocol was Up.

Procedure


----End

Related InformationTRUNK_1.3.6.1.4.1.2011.5.25.41.3.9 hwExtLinkDown



897

62 TUNNEL

About This Chapter

NOTE


62.1 TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.1 hwMplsPsSwitchPtoW

62.2 TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.2 hwMplsPsSwitchWtoP

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 62 TUNNEL


898

62.1 TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.1hwMplsPsSwitchPtoW

Description

TUNNEL/4/TUNN_PS_PTOW: OID [OID] switched to work tunnel. (IfIndex=[INTEGER],WorkTunnel=[OCTET], WorkTunnelId=[INTEGER], ProtectionTunnel=[OCTET],ProtectionTunnelId=[INTEGER], SwitchResult=[INTEGER], WorkTunnelState=[INTEGER],ProtTunnelState=[INTEGER], LocalState=[INTEGER])

The protection group switched from the protection tunnel back to the work tunnel.

Attribute



Parameters

Name Meaning

OID Indicates the trap OID.

IfIndex Indicates the index value of the work tunnel.

WorkTunnel Indicates the name the work tunnel.

WorkTunnelId Indicates the tunnel ID of the work tunnel.

ProtectionTunnel Indicates the name of the protection tunnel.

ProtectionTunnelId Indicates the tunnel ID of the protection tunnel.

SwitchResult Indicates the result of the switchover. The value 1 indicates that the tunnelbecomes the work tunnel.

WorkTunnelState Indicates the status of the work tunnel.

ProtTunnelState Indicates the status of the protection tunnel.

LocalState Indicates the status of local node.



Possible Causes

The work tunnel returned to the normal state and the protection tunnel switched to the worktunnel.



899

Procedure

Step 1 Run the display mpls te protection tunnel all verbose command to check the work-tunnelname field to obtain the name of the work tunnel.

Step 2 Run the display interface tunnel interface-number command to check the status of the worktunnel.

l If the status of the work tunnel is Up, it indicates that the trap message is informational only,and no action is required.

l If the status of the work tunnel is Down, it indicates that faults occur on both the protectionand work tunnels. Do as follows on both the protection and work tunnels:

Step 3 Run the display this interface command in the tunnel interface view to check whether the routedestined for the destination exists.


l If not, configure the route destined for the destination. After that, if the fault disappears, goto Step 10; if the fault persists, go to Step 4.

Step 4 Run the display this command in the tunnel interface view to check whether the destinationaddress of the tunnel, tunnel type, and tunnel ID are correctly configured, and whether the mplste commit command is configured.


l If not, modify the configurations. After that, if the fault disappears, go to Step 10; if the faultpersists, go to Step 5.

Step 5 Run the display this command in the tunnel view to check whether the mpls te path explicit-path path-name command is configured, that is, whether the explicit path is configured.


l If not or only parts of the explicit path are configured, go to Step 9.

Step 6 Run the display explicit-path path-name command to check the IP address of each hop on theexplicit path.

Step 7 Run the display ip interface interface-type interface-number command to check whether theinterface at each hop is Up.

l If all interfaces are Up, go to Step 8.

l If an interface is Down, check whether the interface is configured with the shutdowncommand. If so, run the undo shutdown command. After that, if the fault disappears, go toStep 10; if the fault persists, go to Step 8.

Step 8 Run the display this command on each interface on the tunnel to check whether MPLS, MPLSTE, and RSVP-TE are enabled.


l If a function is disabled, enable it. After that, if the fault disappears, go to Step 10; if the faultpersists, go to Step 9.


Step 10 End.

----End



900

Related Information

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.2 hwMplsPsSwitchWtoP

62.2 TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.2hwMplsPsSwitchWtoP

Description

TUNNEL/4/TUNN_PS_WTOP: OID [OID] switched to protection tunnel. (IfIndex=[INTEGER], WorkTunnel=[OCTET], WorkTunnelId=[INTEGER], ProtectionTunnel=[octet],ProtectionTunnelId=[INTEGER], SwitchResult=[INTEGER], WorkTunnelState=[INTEGER],ProtTunnelState=[INTEGER], LocalState=[INTEGER])

The protection group switched from the work tunnel to the protection tunnel.

Attribute



Parameters

Name Meaning

OID Indicates the trap OID.

IfIndex Indicates the index value of the work tunnel.

WorkTunnel Indicates the name of the work tunnel.

WorkTunnelId Indicates the tunnel ID of the work tunnel.

ProtectionTunnel Indicates the name of the protection tunnel.

ProtectionTunnelId Indicates the tunnel ID of the protection tunnel.

SwitchResult Indicates the result of the switchover. The value 2 indicates that the worktunnel switches to the protection tunnel.

WorkTunnelState Indicates the status of the work tunnel.

ProtTunnelState Indicates the status of the protection tunnel.

LocalState Indicates the status of local node.


When the primary tunnel is faulty, traffic is switched from the primary tunnel to the backuptunnel.



901

Possible Causes1. The interface along the TE tunnel was shut down.

2. Interfaces along the TE tunnel were not enabled with MPLS, MPLS TE, or RSVP-TE.

3. The tunnel configurations such as destination address, type, or TE tunnel ID were incorrector were not committed.

4. The explicit path was not the expected one.

5. A fault was detected by an OAM session or a BFD session.

6. The TE tunnel interface failed to forward packets.

Procedure

Step 1 Run the display this command in the view of an interface along the TE tunnel to check whetherthe interface goes Up and whether MPLS, MPLS TE, and RSVP-TE are enabled.l If the interface goes Down, run the undo shutdown command.l If MPLS, MPLS TE, and RSVP-TE are disabled, run the mpls, mpls te, and mpls rsvp-te

commands in sequence.l If the fault is rectified, go to Step 8. If the fault persists, go to Step 2.

Step 2 Run the display this command in the tunnel interface view to check whether an explicit path isconfigured through the mpls te path explicit-path path-name command.l If so, go to Step 3.l If not, go to Step 4.

Step 3 Run the display explicit-path path-name command to view the address of each hop along theexplicit path. Using the address of each hop along the explicit path, run the display ipinterface interface-type interface-number command to check whether the interface along theprimary tunnel is Up.l If all interfaces are Up, go to Step 5.l If an interface is Down, run the undo shutdown command.l If the fault is rectified, go to Step 8. If the fault persists, go to Step 5.

Step 4 Run the display this command in the tunnel interface view to check whether the destinationaddress, tunnel type, and TE tunnel ID are correct and whether the mpls te commit commandis run.l If there is an incorrect configuration, run one of the following commands to correct the

configuration:

1. Run the tunnel-protocol mpls te command to configure a correct tunnel type.2. Run the destination dest-ip-address command to specify a correct destination address

of the tunnel.3. Run the mpls te tunnel-id tunnel-id command to specify a correct tunnel ID.

l If the configurations are not committed, run the mpls te commit command.l If the fault is rectified, go to Step 8. If the fault persists, go to Step 5.

Step 5 Run the ping lsp te tunnel interface-number command to check connectivity of the the tunnelLSP.



902

l If the LSP is reachable, go to Step 7.l If the LSP is unreachable, go to Step 6.

Step 6 Run the display bfd session all command to view BFD detection results.l If a BFD session is Down, refer to the troubleshooting manuals for BFD.l If BFD sessions are Up, go to Step 7.


Step 8 End.

----End

Related InformationTUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.1 hwMplsPsSwitchPtoW



903

63 UCM

About This Chapter

63.1 UCM_1.3.6.1.4.1.2011.5.25.307.2.3 hwVpVmAuthenticateFail

63.2 UCM_1.3.6.1.4.1.2011.5.25.307.2.4 hwVpVmDeliverAuthorInformationFail

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 63 UCM


904

63.1 UCM_1.3.6.1.4.1.2011.5.25.307.2.3hwVpVmAuthenticateFail

Description

CM/4/VM_AUTHENTICATE_FAIL:OID [oid] Failed to pass authentication. (VMVlan=[Vlan], VMMac=[MAC], ProfileId=[ProfileId], IfIndex=[IfIndex], IfName=[IfName]).

A virtual user failed to be authenticated.

Attribute



Parameters

Name Meaning


VMVlan Indicates the VLAN that the virtual user belongs to.

VMMac Indicates the MAC address of the virtual user.

ProfileId Indicates the policy ID of the virtual user.

IfIndex Indicates the index of the interface connected to the virtual user.

IfName Indicates the name of the interface connected to the virtual user.


None.

Possible Causes1. The RADIUS server configuration is incorrect or the device fails to communicate with the

RADIUS server.

Procedure

Step 1 Run the display radius-server configuration command to check whether the RADIUS serverconfiguration is correct.

l If the RADIUS server configuration is incorrect, correct the configuration.

l If the RADIUS server configuration is correct, contact Huawei technical support personnel.

----End



905

Related Information

None.

63.2 UCM_1.3.6.1.4.1.2011.5.25.307.2.4hwVpVmDeliverAuthorInformationFail

Description

CM/4/VM_DELIVER_AUTHORIZATION_FAIL:OID [oid] Failed to deliver authorizationinformation. (VMVlan=[Vlan], VMMac=[MAC], ProfileId=[ProfileId], IfIndex=[IfIndex],IfName=[IfName]).

Authorization information about the virtual user failed to be delivered.

Attribute



Parameters

Name Meaning


VMVlan Indicates the VLAN that the virtual user belongs to.

VMMac Indicates the MAC address of the virtual user.

ProfileId Indicates the policy ID of the virtual user.

IfIndex Indicates the index of the interface connected to the virtual user.

IfName Indicates the name of the interface connected to the virtual user.


The virtual user cannot go online.

Possible Causes

ACL resources are insufficient.

Procedure

Step 1 Run the display acl resource command to check whether there are available ACL resources.

l If there is no available ACL resources, adjust services so that ACL resources can be released.



906

l Collect alarms, logs, and configurations, and then contact Huawei technical supportpersonnel.

----End




907

64 VFS

About This Chapter

64.1 VFS_1.3.6.1.4.1.2011.6.9.1.3.1 hwFlhOperNotification

64.2 VFS_1.3.6.1.4.1.2011.6.9.1.3.2 hwFlhSyncSuccessNotification

64.3 VFS_1.3.6.1.4.1.2011.6.9.1.3.3 hwFlhSyncFailNotification

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 64 VFS


908

64.1 VFS_1.3.6.1.4.1.2011.6.9.1.3.1 hwFlhOperNotification

Description

VFS/4/CPYCOMPLETE:OID [oid] Copy operation completed. (CopyIndex=[integer],CopyStatus=[integer])

Indicates that the Flash memory finishes the copying process.

Attribute


1.3.6.1.4.1.2011.6.9.1.3.1 Warning other(1)

Parameters

Name Meaning


CopyIndex indicates the index of the copy table.

CopyStatus indicates the status of the copy table.



Possible Causes

The trap is generated when the NMS managing a device sends files to the device. This trap isused to show whether files are transmitted successfully.

Procedure


----End

Related Information

None

64.2 VFS_1.3.6.1.4.1.2011.6.9.1.3.2hwFlhSyncSuccessNotification



909

Description

VFS/4/VFS_SYNC_SUCCESS:OID [oid] Copy operation success. (CopyIndex=[integer],SyncSourceFile=[OCTET], SyncDestinationFile=[OCTET])

The copy operation was successful.

Attribute



Parameters

Name Meaning


CopyIndex Indicates the index of a table.

SyncSourceFile Indicates the source file name.

SyncDestinationFile Indicates the destination file name.



Possible Causes

1.

The NMS managing the device succeeded in copying files between storage cards of the device.

2.

The NMS managing the device succeeded in copying files within the storage card of the device.

Procedure


----End

Related Information

None

64.3 VFS_1.3.6.1.4.1.2011.6.9.1.3.3hwFlhSyncFailNotification



910

DescriptionVFS/4/VFS_SYNC_FAILED:OID [oid] Copy operation failed. (CopyIndex=[integer],SyncSourceFile=[OCTET], SyncDestinationFile=[OCTET])

Copying files failed.

Attribute



Parameters

Name Meaning


CopyIndex Indicates the index of a table.

SyncSourceFile Indicates the source file name.

SyncDestinationFile Indicates the destination file name.


Possible Causes1.

The memory device to which the NMS managing the device copies files did not exist.

2.

The memory device to which the NMS managing the device copies files had insufficient space.

3.

The memory device to which the NMS managing the device copies files had five (the maximumnumber) concurrent copying processes.

Procedure

Step 1 Check for available memory devices on the NMS.

Copy files again on the NMS.


Step 2 Delete useless files on the NMS to leave enough space for the files to be copied.

Copy files again on the NMS managing the device and check whether the copying succeeds.



911


Step 3 Wait for a period and then copy files again on the NMS managing the device.

Check whether the copying succeeds.



Step 5 End.

----End




912

65 VRRP

About This Chapter

NOTE

The S2750, S5700LI, S5700SI, and S5700S-LI do not support this trap.

65.1 vrrp_1.3.6.1.2.1.68.0.1 vrrpTrapNewMaster

65.2 vrrp_1.3.6.1.2.1.68.0.2 vrrpTrapAuthFailure

65.3 VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.1 hwVrrpExtTrapMasterDown

65.4 VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.2 hwVrrpExtTrapNonMaster

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 65 VRRP


913

65.1 vrrp_1.3.6.1.2.1.68.0.1 vrrpTrapNewMaster

DescriptionVRRP/2/VRRPCHANGETOMASTER:OID [oid] The status of VRRP changed to master.(VrrpIfIndex=[VrrpIfIndex], VrId=[VrId], IfIndex=[IfIndex], IPAddress=[IPAddress],NodeName=[NodeName], IfName=[IfName], ChangeReason=[ChangeReason])

The state of switch changed to master.

Attribute



Parameters

Name Meaning

oid MIB object ID

VrrpIfIndex Index of the interface on which a VRRP backup group is configured

VrId ID of a VRRP backup group

IfIndex Index of the interface on which a VRRP backup group is configured

IPAddress IP address of the interface where a VRRP backup group is configured

NodeName Device name

IfName Name of the interface where a VRRP backup group is configured

ChangeReason Cause for the change of the VRRP backup group status

Impact on the Systeml If master/backup switchover occurs in normal cases, services are not affected.l If master/backup switchover occurs in exceptional cases, services may be interrupted.


The former master switch was faulty.

Cause 2:

The former master link was faulty.

Cause 3:

The priority of the former master switch or backup switch changed.



914

Cause 4:

The logical interface where the VRRP backup group resides on the master switch is deleted orthe configuration of the VRRP backup group is deleted.

Cause 5:

The former master switch recovers from a fault.

Cause 6:

The former active link recovers from a fault.

Procedure

Step 1 View user logs to check the causes of the VRRP change. You can perform operations accordingto the specific cause.l If the cause is priority calculation, go to Step 6.l If the cause is that the MASTER_DOWN timer expired, go to Step 2.l If the cause is the change of the BFD session status, go to Step 2.l If the cause is the change of the interface status, go to Step 2.l If the cause is admin-vrrp DROVE, go to Step 6.

Step 2 Run the display vrrp command to check the status of the VRRP backup group on the formermaster switch.l If the VRRP backup group is in the Initialize state, it indicates that the former switch is faulty.

Locate the cause of the fault and restore the master switch. Go to Step 8.l If the VRRP backup group is in the Backup state, go to Step 6.l If the VRRP backup group is in the Master state, go to Step 3.

Step 3 Check whether the master link is faulty.l If BFD is configured, go to Step 4.l If BFD is not configured, go to Step 5.

Step 4 Run the display vrrp command to check the status of the BFD session.l If the BFD session is Down, it indicates that the former master link is faulty. Locate the cause

of the fault and restore the master link. Go to Step 8.l If the BFD session is Up, go to Step 7.

Step 5 Run the display vrrp [ interface interface-type interface-number ] [virtual-router-id ]statistics command to check whether the VRRP packets are normally forwarded.l If not, it indicates that the link is faulty. Locate the cause of the fault and restore the link. Go

to Step 8.l If so, go to Step 7.

Step 6 On the former master switch and backup switch, run the display vrrp command to check whetherthe configured priority of the VRRP is consistent with the running priority.l If not, it indicates that the link monitored through VRRP is faulty. Locate the cause of the

fault and restore the monitored link. Go to Step 8.l If so, go to Step 7.



915


Step 8 End.

----End

65.2 vrrp_1.3.6.1.2.1.68.0.2 vrrpTrapAuthFailure

Description

VRRP/1/VRRPAUTHFAILED:OID [oid] VRRP failed to authentication. (IPAddress=[IPAddress], AuthErrorType=[AuthErrorType])

The authentication mode or authentication key of the received VRRP multicast packets wasinconsistent with that of the local switch.

Attribute



Parameters

Name Meaning

oid MIB object ID


AuthErrorType Authentication failure types in the VRRP group.l 1: invalid authentication model 2: inconsistent authentication types on two devices in a VRRP backup

groupl 3: authentication failure


The failure of the negotiation between the VRRP backup group may cause the services to beinterrupted.

Possible Causes

Cause 1:

The authentication mode or authentication key of the received VRRP packets was inconsistentwith that of the local switch.

Cause 2:



916

Authentication configured on one end is deleted.

Procedure

Step 1 Run the display vrrp command to view the Auth Type field. Check whether the authenticationtypes are configured to be the same on both devices in a VRRP backup group.

l If not, configure the authentication modes to be consistent. Go to Step 3.



Step 3 End.

----End

65.3 VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.1hwVrrpExtTrapMasterDown

Description

VRRP/2/VRRPMASTERDOWN:OID [oid] The state of VRRP changed from master to otherstate. (VrrpIfIndex=[VrrpIfIndex], VrId=[VrId], IfIndex=[IfIndex], IPAddress=[IPAddress],NodeName=[NodeName], IfName=[IfName], CurrentState=[CurrentState], ChangeReason=[ChangeReason])

The VRRP backup group was changed from the Master state to another state.

Attribute



Parameters

Name Meaning

oid MIB object ID




IpAddress Router id of the interface where VRRP resides





917

Name Meaning

CurrentState VRRP backup group status after the change:l Notactive: Indicates that the VRRP backup group in the master state is

deleted. Configurations of this VRRP backup group cannot be viewed byusing the display vrrp command.

l Initializel Backup



l If master/backup switchover occurs normally, services are not affected.

l If master/backup switchover occurs abnormally, services may be interrupted.

Possible Causes

Cause 1:

The master switch was faulty.

Cause 2:

The active link was faulty.

Cause 3:

The priority of the VRRP backup group on the master switch or the slave switch changed.

Cause 4:

The logical interface where the VRRP backup group resides on the master switch is deleted orthe configuration of the VRRP backup group is deleted.

Cause 5:

The former master switch recovers from a fault.

Cause 6:

The former active link recovers from a fault.

Procedure

Step 1 View the value of CurentState in the trap, check the status after the VRRP backup group changes,and perform operations according to the specific cause.

l If the value of CurentState is Notactive, go to Step 2.

l If the value of CurentState is Backup, go to Step 3.

l If the value of CurentState is Initialize, go to Step 4.



918

Step 2 If the VRRP backup group in the Master state is deleted, you cannot view the configurations ofthe VRRP backup group by using the display vrrp command. You can check the operationrecords of command lines by viewing log information.

Step 3 Run the display vrrp command to check whether the set priorities of the VRRP backup groupon the original master switch and backup switch are the same as the running priorities.


l If not, it indicates that the link monitored by the VRRP backup group is faulty and thepriorities are increased or reduced. Locate the cause of the fault and restore the monitoredlink. Then, go to Step 4.

Step 4 If the original master switch is faulty, locate the cause of the fault and restore the masterswitch.

l Check whether the interface where the VRRP backup group resides is normal, and then goto Step 6.

l Check whether the link that the VRRP backup group monitors is normal, and then go to Step7.

l If the VRRP backup group and BFD are associated, check the link that BFD monitors andgo to Step 5.

Step 5 Run the display vrrp command to check the status of the BFD session.

l If the BFD session is Up, go to Step 8.

l If the BFD session is Down, it indicates that the original active link is faulty. Locate the causeof the fault and restore the active link. Then, go to Step 9.

Step 6 Run the display vrrp [ interface interface-type interface-number ] [virtual-router-id ]statistics command to check whether VRRP Advertisement packets can be normally receivedand sent.


l If not, it indicates that the link is faulty. Locate the cause of the fault and restore the link.Then, go to Step 9.

Step 7 Run the display vrrp command to view the interface that is monitored by the BFD sessionassociated with the VRRP backup groups and then enter the interface view to run the displaythis interface command to detect the interface status.

l If the interface status is Up, go to Step 8.

l If the interface status is Down, it indicates that the link is faulty. Locate the cause of the faultand restore the active link. Then, go to Step 9.


Step 9 End.

----End

65.4 VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.2hwVrrpExtTrapNonMaster



919

DescriptionVRRP/2/VRRPNONMASTER:OID [oid] The state of VRRP changed between backup andInitialize state. (VrrpIfIndex=[VrrpIfIndex], VrId=[VrId], IfIndex=[IfIndex], IPAddress=[IPAddress], NodeName=[NodeName], IfName=[IfName], CurrentState=[CurrentState],ChangeReason=[ChangeReason])

The status of a VRRP backup group changes from Backup to Initialize or from Initialize toBackup.

Attribute



Parameters

Name Meaning

oid MIB object ID







CurrentState VRRP backup group status after the change:l Initializel Backup


Impact on the SystemIf the VRRP backup group status changes from Backup to Initialize, services may be interrupted.

If the VRRP backup group status changes from Initialize to Backup, services will not be affected.

Possible CausesThe possible causes for changing VRRP status from Backup to Initialize are as follows:l Cause 1: The device on which VRRP resides becomes faulty.l Cause 2: The interface or directly-connected link on which VRRP resides becomes faulty.

The possible causes for changing VRRP status from Initialize to Backup are as follows:l Cause 1: A fault on the device on which VRRP resides is rectified.



920

l Cause 2: A fault on the interface or directly-connected link on which VRRP resides isrectified.

Procedurel Change the VRRP backup group status from Backup to Initialize.

1. Check whether the device is functioning properly.

– If the device is not functioning properly, go to step 3.

– If the device is functioning properly, go to step 2.2. Run the display vrrp command to view the bound interface. Then run the display

this interface command in the interface view to view the interface status.

– If the interface is in the Up state, go to step 3.

– If the interface is in the Down state, the interface or its directly connected link fails.After the interface or link fault is rectified, go to step 4.

3. Collect trap, log, and configuration information, and contact Huawei technical supportpersonnel.

4. End.l Change the VRRP backup group status from Initialize to Backup.

1. This trap message is informational only, and no action is required.

----End



921

66 Appendix

About This Chapter

66.1 BGP Error Code

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 66 Appendix


922

66.1 BGP Error Code

Error Code Error Subcode

1: Message header error l 1: connection not synchronizedl 2: error message lengthl 3: error message type

2: Open message error l 1: unsupported version numberl 2: error peer ASl 3: error BGP identifierl 4: unsupported optional parameterl 5: authentication failedl 6: unacceptable hold-timel 7: unsupported capability

3: Update message error l 1: malformed attribute listl 2: unrecognized well-known attributel 3: well-known attribute is missingl 4: attribute flags errorl 5: attribute length errorl 6: invalid origin attributel 7: AS routing loopl 8: invalid Next-Hop attributel 9: error optional attributel 10: invalid network fieldl 11: abnormal AS-Path

4: Hold timer expired 0: no special definition of the error subcode

5: Finite state machine error 0: no special definition of the error subcode

6: Cease l 1: maximum number of prefixes reachedl 2: administrative shutdownl 3: peer deletedl 4: administrative resetl 5: connection rejectedl 6: other configuration changel 7: connection collision resolutionl 8: out of resourcesl 9: BFD session Down

S2750&S5700&S6700 Series Ethernet SwitchesAlarm Handling 66 Appendix


923

huawei series ethernet switches alarm handling s2750&5700&6700.pdf

Documents