所选语种没有对应资源,请选择:

本站点使用Cookies,继续浏览表示您同意我们使用Cookies。Cookies和隐私政策>

提示

尊敬的用户,您的IE浏览器版本过低,为获取更好的浏览体验,请升级您的IE浏览器。

升级

CX916, CX916L, CX930 交换模块 V100R001 诊断命令参考 04

评分并提供意见反馈 :
华为采用机器翻译与人工审校相结合的方式将此文档翻译成不同语言,希望能帮助您更容易理解此文档的内容。 请注意:即使是最好的机器翻译,其准确度也不及专业翻译人员的水平。 华为对于翻译的准确性不承担任何责任,并建议您参考英文文档(已提供链接)。
pads diagnose system health

pads diagnose system health

命令功能

pads diagnose system health命令用来查看组件健康度检查信息。

命令格式

pads diagnose system health { all | bgp | fes | rm | stack | isis | multicast | te | ldp | issu | ssp | ospf | mstp | arp }

参数说明

参数 参数说明 取值
all 查看所有组件的健康度检查信息。 -
bgp 指定查看BGP健康度检查信息。 -
fes 指定查看FES健康度检查信息。 -
rm 指定查看RM健康度检查信息。 -
stack 指定查看Stack健康度检查信息。 -
isis 指定查看IS-IS健康度检查信息。 -
multicast 指定查看组播健康度检查信息。 -
te 指定查看TE健康度检查信息。 -
ldp 指定查看LDP健康度检查信息。 -
issu 指定查看ISSU健康度检查信息。 -
ssp 指定查看SSP健康度检查信息。 -
ospf 指定查看OSPF健康度检查信息。 -
mstp 指定查看MSTP健康度检查信息。 -
arp 指定查看ARP健康度检查信息。 -

视图

诊断视图

缺省级别

3:管理级

使用指南

应用场景

此命令主要用于故障定位。当用户需要查看对应组件健康度检查信息时,可以执行pads diagnose system health命令。

注意事项

执行该命令前,需确保协议辅助诊断系统已开启,并确保系统中已配置了需要检查健康度的功能。协议辅助诊断系统缺省已开启,关闭后可通过在系统视图下执行undo pads disablepads switch命令打开。

使用实例

# 查看FES组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health fes
last system health for fes:
 -----------------------------------------------------------------------------------
 -----------------------------------------------------------------------------------
 Show FESDS(Cid=0x806A0416, Slot=17) Health Record
 -----------------------------------------------------------------------------------
 PADS_Type       Detect-Time    Description
 -----------------------------------------------------------------------------------
 CFG-RESTORE-ERR 05-31 11:41:53 An error occurs during configuration restoration.(Dsc=[CFG_RestoreProcElm] no find cfg class 0x853a38f)
 -----------------------------------------------------------------------------------
 Show FESDS(Cid=0x806A271B, Slot=3) Health Record
 -----------------------------------------------------------------------------------
 PADS_Type       Detect-Time    Description
 -----------------------------------------------------------------------------------
 CFG-RESTORE-ERR 05-31 11:42:00 An error occurs during configuration restoration.(Dsc=[CFG_RestoreProcElm] no find cfg class 0x853a38f)
 -----------------------------------------------------------------------------------
表12-172 pads diagnose system health fes命令输出信息描述

项目

描述

Show FESDS(Cid=xx, Slot=xxx) Health Record

显示FESDS(Cid=组件Cid,Slot=单板号)健康度检查信息。

PADS_Type

辅助诊断类型,具体描述请参见表12-173

Detect-Time

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-173

表12-173 pads diagnose system health fes命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

TABLE-OVERLOAD

The table is overloaded. (TableID=%u, TableName=%s)

表项过载。

TABLE-AGE

The table is aged. ((TableID=%u, TableName=%s, AgeCnt=%u), (TableID=%u, TableName=%s, AgeCnt=%u))

表项老化。

PSUB-FLOW

The flow control of the producer expires. (Pid=%08x, CompName=%s, Time=%u)

流控生产者时间超时。

REG-FLOW-CTL

The flow control by the consumer expires. (Pid=0x%08x, CompName=%s, Time=%u, FlowType=%s)

被消费者流控时间超时。

POOL-CHANGE

An error occurs when the resource pool is changed. (ResId=%u, ResName=%s, ResType=%u, NodeID=%x, ErrType=%s, ChangeType=%s)

资源池变更时发生错误。

REG-KICK-MEMBER

The FES detects a slow board and isolates it. (Pid= 0x%08x, CompName=%s, Slot=%s)

FES检测到慢单板并隔离慢单板。

CFG-RESTORE-ERR

An error occurs during configuration restoration. (Dsc=%s)

配置恢复时发生错误。

SR-BIM-ERR

An SR Bim error occurs. (TableID=%u, TableName=%s, Dsc=%s, Reason=%u)

SR BIM时发生错误。

MSG-RESEND-LOAD

The message retransmission expires. (Pid=%08x, CompName=%s, IntfType=%s, MsgType=%s, Times=%u)

消息重传时间超时。

PSUB-SEQ-ERR

The producer has a message sequence error. (Pid=%08x, CompName=%s, Count=%u)

生产者与FES发生序列号失序。

REG-MSG-SEQERR

The FES notifies the consumer of a sequence error. (CompType=%x, CompName=%s, Reason=%s)

FES通知消费者序列号失序。

RES-OVER-LOAD

The resource is overloaded. (ResId=%x, ResName=%s, ResType=%u, NodeID=%x)

资源发生超限。

FEISW-HQUE-LOAD

The FEISW high priority queue is overloaded.

FEISW高优先级队列超限。

FEISW-NQUE-LOAD

The FEISW normal priority queue is overloaded.

FEISW普通优先级队列超限。

PROMPT-PRIMAY

The slave board becomes master but the backup is still going on.

备升主时批备不结束。

PATCHLOAD-TIMEOUT

The patch loading of the PATH file times out.

PATH文件补丁加载超时。

SMOOTH-TIME-OUT

The smoothing between the main FES and the board FES does not end.

主控板FES与接口板FES之间平滑不结束。

SMOOTH-TIME-OUT

The smoothing between the producer and the FES does not end.

生产者与FES平滑不结束。

PSUB-CUR-FLOW

Flow control is being performed on the producer and times out. (Pid=%08x, CompName=%s, Time=%u)

当前正在流控生产者且时间超时。

REG-CUR-FLOW

Flow control is being performed by the consumer and times out. (Pid=0x%08x, CompName=%s, Time=%u, FlowType=%s)

当前正在被消费者流控且时间超时。

PSUB-ACC-FLOW

The accumulated flow control on the producer within %u1 minutes exceeds %u2 minutes.

%u1分钟内累计流控生产者时间超过%u2分钟。

REG-ACC-FLOW

The accumulated flow control by the consumer within %u1 minutes exceeds %u2 minutes.

%u1分钟内被消费者流控时间超过%u2分钟。

# 查看IS-IS组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health isis
last system health for isis:
-----------------------------------------------------------------------------------

Show ILSDB Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime Description                                         
--------------------------------------------------------------------------------
RECV_ERR_PIPE_MSG   2018-06-14 test1 0x7b component received exceptional pipe contr
                     11:07:49  ol message.(PipeId=336, ReturnValue=33, MessageType=
                    779        Pipe type)                                          
RECV_ERR_MSG        2018-06-14 Drop error message.(MsgType=22, MsgSubType=222, Loca
                     11:07:49  lComp=ILSDB, PeerComp=ICRM, ProcessId=666, ErrReason
                    779        =669, ErrCount=663)                                 
NORECV_MSG          2018-06-14 No expected messages were received within the specif
                     11:07:49  ied time. (MsgType=21, PeerComp=ICRM 0x1c8, LocalCom
                    779        p=ILSDB 0x7b, Time=999)                             
PIPE_SEND_FAIL      2018-06-14 ILSDB 0x808604da component failed to send pipe contr
                     11:07:49  ol message.(PipeId=99, ReturnValue=111, MessageType=
                    779        Pipe close local)                                   
MSG_SEND_FAIL       2018-06-14 ISIS send message failure.(Local-comp=ILSDB, Peer-co
                     11:07:49  mp=INM, Count=666)                                  
                    779                                                            
MSG_MISMATCH        2018-06-14 ISIS msg seqnum mismatch.(Local-comp=ILSDB,Peer-comp
                     11:07:49  =INM, Count=666)                                    
                    779                                                            
SYSTEMID_CONFLICT   2018-06-14 System ID may conflict.(ProcId=100, Level=1, OwnSyst
                     11:07:49  emId=1111.1111.1111, AdjSystemId=2222.2222.2222, Loc
                    779        alIP=1.1.1.1, AdjIP=2.2.2.2, RemoteIP=3.3.3.3)      
ROUTE_AGE           2018-06-14 ISIS deleted 99 routes during import-route verificat
                     11:07:49  ion.(ProcessId=100, AddressFamily=IPV4)             
                    779                                                            
FAIL_ALLOC_RES      2018-06-14 IS-IS failed to apply for resources.(ResType=LABEL) 
                     11:07:49                                                      
                    779                                                            
IID_WITHDRAW        2018-06-14 Ecm group node is withdrawn.(NodeCount=30)          
                     11:07:49                                                      
                    779                                                            
QUEUE_OVERFLOW      2018-06-14 The data sending queue of IS-IS was overloaded.(Comp
                     11:07:49  Name=ICRM, PeerCompName=ILSDB, DataType=IID, DataNum
                    779        =6000)                                              
SMOOTH_OVERTIME     2018-06-14 Data smoothing of IS-IS 100 timed out.(CompName=ICRM
                     11:07:49  , PeerCompName=ILSDB, DataType=IID, OverTime=6000S) 
                    779                                                            
FLOWCTL_OVERTIME    2018-06-14 Component flowcontrol overtime.(CompName=test1, Peer
                     11:07:49  CompName=test2, PeerCID=0x7e, OverTime=129S)        
                    779                                                            
MSG_FLOWCTRL        2018-06-14 ISIS enter flowctrl.(Local-comp=test1, Peer-comp=tes
                     11:07:49  t2, Time=126)                                       
                    779                                                            
COMMAND_FAIL        2018-06-14 The component configuration failed.(Comp=abc, MsgTyp
                     11:07:49  e=11, OperCode=BATCH_DELETE, ClassId=200, ErrCode=30
                    779        0, Reason=test)                                     
HELLO_DELAY         2018-06-14 ISIS delay to send IIH.(Proc=100, IfIndex=100, Hello
                     11:07:49  Interval=10, TotalNumber=1000)                      
                    779                                                            
RTCALC_OVERTIME     2018-06-14 The route calculation of IS-IS 100 timed out.       
                     11:07:49                                                      
                    779                                                            
IP_CONFLICT         2018-06-14 IP address conflict.(ProcId=100, ConflictLevel=2, Co
                     11:07:49  nflictIP=1.1.1.1, Conflict router is 11111111 and 2)
                    779                                                            
ROUTE_CYCLE         2018-06-14 A loop may have occurred on the routes imported by I
                     11:07:49  S-IS 100.(IpPrefix=1.1.1.1)                         
                    779                                                            
CHGLSP_INCR         2018-06-14 IS-IS 100 received 100 LSPs with changed content wit
                     11:07:49  hin 5 minutes.                                      
                    779                                                            
GENPURGE_INCR       2018-06-14 IS-IS 100 generated 100 purged LSPs within 5 minutes
                     11:07:49  .                                                   
                    779                                                            
RECVPURGE_INCR      2018-06-14 IS-IS 100 received 100 purged LSPs within 5 minutes.
                     11:07:49                                                      
                    779                                                            
ROUTE_OVERRUN       2018-06-14 The number of routes in IS-IS 100 reached the maximu
                     11:07:49  m value.(RouteNum=3000000)                          
                    778                                                            
ROUTE_OVERRUN       2018-06-14 The number of routes in IS-IS 100 reached the maximu
                     11:07:49  m value.(RouteNum=3000000)                          
                    778                                                            
LSDB_OVER_FLOW      2018-06-14 ISIS 100 Level-2 LSDB overflow.The imported routes a
                     11:07:49  re not advertised.                                  
                    778                                                          

Show INM Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime Description                                         
--------------------------------------------------------------------------------
NORECV_MSG          2018-06-14 No expected messages were received within the specif
                     11:07:49  ied time. (MsgType=26, PeerComp=ILSDB 0x86, LocalCom
                    781        p=INM 0x808904e0, Time=1000)                        
MSG_MISMATCH        2018-06-14 ISIS msg seqnum mismatch.(Local-comp=INM,Peer-comp=I
                     11:07:49  LSDB, Count=200)                                    
                    781                                                            
ROUTE_AGE           2018-06-14 ISIS deleted 1000 routes during import-route verific
                     11:07:49  ation.(ProcessId=100, AddressFamily=IPV4)           
                    781                                                            
FLOWCTL_OVERTIME    2018-06-14 Component flowcontrol overtime.(CompName=INM, PeerCo
                     11:07:49  mpName=ILSDB, PeerCID=0x3e8, OverTime=3000S)        
                    781                                                            
MSG_FLOWCTRL        2018-06-14 ISIS enter flowctrl.(Local-comp=INM, Peer-comp=ILSDB
                     11:07:49  , Time=3000)                                        
                    781                                                            
HELLO_DELAY         2018-06-14 ISIS delay to send IIH.(Proc=100, IfIndex=8, HelloIn
                     11:07:49  terval=10, TotalNumber=3000)                        
                    781                                                            
-----------------------------------------------------------------------------------

表12-174 pads diagnose system health isis命令输出信息描述

项目

描述

Show xxx Health Record

显示xxx组件健康度检查信息。

PadsType

辅助诊断类型,具体描述请参见表12-175

DetectTime

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-175

表12-175 pads diagnose system health isis命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

LSDB_OVER_FLOW

ISIS %u Level-%u LSDB overflow.The imported routes are not advertised.

ISIS LSDB溢出,影响引入路由发布。

ROUTE_OVERRUN

The number of routes in IS-IS %u reached the maximum value.(RouteNum=%u)

IS-IS路由表项达到最大值。

RECVPURGE_INCR

IS-IS %u received %u purged LSPs within 5 minutes.

IS-IS进程在5分钟内收到的Purge LSP报文个数。

GENPURGE_INCR

IS-IS %u generated %u purged LSPs within 5 minutes.

IS-IS进程在5分钟内产生的Purge LSP报文个数。

CHGLSP_INCR

IS-IS %u received %u LSPs with changed content within 5 minutes.

IS-IS进程在5分钟内收到的变化的LSP报文个数。

ROUTE_CYCLE

A loop may have occurred on the routes imported by IS-IS %u.(IpPrefix=%s)

IS-IS进程引入路由可能存在环路。

IP_CONFLICT

IP address conflict.(ProcId=%u, ConflictLevel=%u, ConflictIP=%s, Conflict router is %s and %s)

IP地址冲突。

RTCALC_OVERTIME

The route calculation of IS-IS %u timed out.

IS-IS进程路由计算超时。

HELLO_DELAY

ISIS delay to send IIH.(Proc=%u, IfIndex=%u, HelloInterval=%u, TotalNumber=%u)

IS-IS延迟发送Hello报文。

COMMAND_FAIL

The component configuration failed.(Comp=%s, MsgType=%hu, OperCode=%s, ClassId=%u, ErrCode=%u, Reason=%s)

组件配置失败。

MSG_FLOWCTRL

ISIS enter flowctrl.(Local-comp=%s, Peer-comp=%s, Time=%u)

IS-IS组件进入流控。

FLOWCTL_OVERTIME

Component flowcontrol overtime.(CompName=%s, PeerCompName=%s, PeerCID=0x%x, OverTime=%uS)

组件流控超时。

SMOOTH_OVERTIME

Data smoothing of IS-IS %u timed out.(CompName=%s, PeerCompName=%s, DataType=%s, OverTime=%uS)

IS-IS组件数据平滑超时。

QUEUE_OVERFLOW

The data sending queue of IS-IS was overloaded.(CompName=%s, PeerCompName=%s, DataType=%s, DataNum=%u)

IS-IS数据发送队列过载。

IID_WITHDRAW

Ecm group node is withdrawn.(NodeCount=%u)

IS-IS IID回收。

FAIL_ALLOC_RES

IS-IS failed to apply for resources.(ResType=%s)

IS-IS申请资源失败。

ROUTE_AGE

ISIS deleted %u routes during import-route verification.(ProcessId=%u, AddressFamily=%s)

IS-IS引入路由对账期间老化的路由数量。

SYSTEMID_CONFLICT

System ID may conflict.(ProcId=%u, Level=%u, OwnSystemId=%s, AdjSystemId=%s, LocalIP=%s, AdjIP=%s, RemoteIP=%s)

System ID可能冲突。

MSG_MISMATCH

ISIS msg seqnum mismatch.(Local-comp=%s,Peer-comp=%s, Count=%u)

IS-IS组件消息序列号失序。

MSG_SEND_FAIL

ISIS send message failure.(Local-comp=%s, Peer-comp=%s, Count=%u)

IS-IS组件发送消息失败。

PIPE_SEND_FAIL

%s component failed to send pipe control message.(PipeId=%u, ReturnValue=%u, MessageType=%s)

IS-IS组件发送管道控制消息失败。

NORECV_MSG

No expected messages were received within the specified time. (MsgType=%u, PeerComp=%s, LocalComp=%s, Time=%u)

IS-IS组件指定时间内未收到期望的消息。

RECV_ERR_MSG

Drop error message.(MsgType=%u, MsgSubType=%u, LocalComp=%s, PeerComp=%s, ProcessId=%u, ErrReason=%s, ErrCount=%u)

IS-IS组件丢弃错误消息。

RECV_ERR_PIPE_MSG

%s component received exceptional pipe control message.(PipeId=%u, ReturnValue=%u, MessageType=%s)

IS-IS组件收到多余的管道控制消息。

# 查看BGP组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health bgp
last system health for bgp:
-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Show BGP_RM_IPV4 BGP-Health Record
-----------------------------------------------------------------------------------
PADS_Type               Detect-Time       Description
-----------------------------------------------------------------------------------
PEER-ROUTE-LIMIT        06-02 03:52:10    The number of Peer routes reached the upp
                                          er limit. (CompType=BGP_RM_IPV4, VrfId=0,
                                           Peer=10.1.1.2, LimitValue=3, ActualValue
                                          =4).
PEER-ROUTE-LIMIT        06-02 03:51:39    The number of Peer routes reached the upp
                                          er limit. (CompType=BGP_RM_IPV4, VrfId=0,
                                           Peer=10.1.1.2, LimitValue=3, ActualValue
                                          =4).
BRM-GR-FAILED           06-02 03:24:59    BRM GR Failed, Quit GR Reason: The GR res
                                          tart timer for the peer expired. (CompTyp
                                          e=BGP_RM_IPV4, VrfId=0, Peer=70.1.1.2).
BRM-GR-FAILED           06-02 03:24:58    BRM GR Failed, Quit GR Reason: The GR res
                                          tart timer for the peer expired. (CompTyp
                                          e=BGP_RM_IPV4, VrfId=0, Peer=30.1.1.2).
BE-FC-BY-BNM            06-02 03:14:15    BRM(BGP_RM_IPV4) Is Flow Controled By BGP
                                          _NM(CompType=19) Time Is Over 20s, (Flow 
                                          Control TimeoutCnt=1, BeginTime=2018-6-2 
                                          3:13:56, EndTime=1970-1-1 0:0:0).
-----------------------------------------------------------------------------------
表12-176 pads diagnose system health bgp命令输出信息描述

项目

描述

Show xxx Health Record

显示xxx组件健康度检查信息。

PADS_Type

辅助诊断类型,具体描述请参见表12-177

Detect-Time

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-177

表12-177 pads diagnose system health bgp命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

PEER-RECEIVE-BUFF

The length of the data buffer that BNM received from the socket exceeded 1M. (CompType=%s, vrfid=%u, bufferlenth=%u, peer ip=%s)

BNM从Socket收到的数据缓存长度超过1M。

PEER-SEND-LIMIT

The linked list of sent Update messages exceeded %d. (CompType=%s, vrfid=%u, bufferlenth=%u, peer ip=%s)

发送的Update报文链表超过了%d。

UPG-SEND-BUFF

The number of buffer lists applied by the update peer-group exceeded 1000. (CompType=%s, real number= %u)

打包组申请的缓存列表数超过了1000。

UPG-SLOW-PEER-80%

A slow peer was detected, and 80% of the slow peer detection threshold was reached. (CompType=%s, vrfid=%d, Address Family=%s,peer ip=%s, Group ID=%d, Flag=%x, Reason=%s)

检测到慢邻居风险,已达到慢邻居检测门限的80%。

UPG-SLOW-PEER

A slow peer was detected and switched to the slow peer group. (CompType=%s, vrfid=%d, Address Family=%s, peer ip=%s, Group ID=%d, Flag=%x, Reason=%s)

检测到慢邻居并切换慢邻居到慢邻居组。

SEND-ROUTEID-ZERO

The local router ID of BGP is 0. (CompType=%s, vrfid=%d)

BGP的本地 Router ID是0。

RECV-OPEN-LEN-ERR

An Open message with an incorrect length was received. The length of the Open message is %d, and the expected minimum length is 29 (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Open消息,Open报文长度错误,期望最小长度为29。

RECV-KA-LEN-ERR

A Keepalive message with an incorrect length was received. The length of the Keepalive message is %d, and the expected length is 19 (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Keep alive消息,Keep alive报文长度错误,期望长度为19。

RECV-UPDATE-LEN-ERR

An Update message with an incorrect length was received. The length of the Update message is %d, and the expected minimum length is 21 (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Update消息,Update报文长度错误,期望最小长度为21。

RECV-RERESH-LEN-ERR

A Route-refresh message with an incorrect length was received. The length of the Route-refresh message is %d, and the expected minimum length is 23 (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Refresh消息,Refresh报文长度错误,期望最小长度为23。

RECV-NOTIFY-LEN-ERR

A Notification message with an incorrect length was received. The length of the Notification message is %d, and the expected minimum length is 21 (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Notification消息,Notification报文长度错误,期望最小长度为21。

RECV-MSG-LEN-ERR

A BGP message with an incorrect length was received. The length of the message is %d, the expected minimum length is 19, and the maximum length is 4096. (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的BGP 消息,报文消息长度错误,期望最小长度为19,最大长度为4096。

RECV-MARKER-ERR

A BGP message with an incorrect marker was received from a peer. The marker is supposed to be all 1s (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的BGP消息,报文Marker错误,从Peer接收到的消息头Market不全为1。

RECV-UNKNOWN-MSG-ERR

An incorrect BGP message with an unknown message type was received. The type of the received message is %d (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的BGP消息,消息类型未知。

RECV-ATR-PRO-ERR

An incorrect Update message with an incorrect AS_Path attribute was received. The error code is %d, and the error sub-code is %d (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Update消息,Path属性错误。

RECV-WITHDRAW-LEN-ERR

An Update message with an incorrect Withdraw length was received. The length of the received Withdraw is %d, and the length of the remaining data is %d (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Update消息,withdraw长度错误。

RECV-PATH-LEN-ERR

An Update message with an incorrect AS_Path length was received. The length of the received AS_Path is %d, and the length of the remaining data is %d (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Update消息,Path属性长度错误。

RECV-NLRI-LEN-ERR

An Update message with an incorrect NLRI length was received. The length of the NLRI is %d, and the expected minimum length is 5 (CompType=BGP_NM, VRFID=%d, peer ip=%s).

接收到错误的Update消息,NLRI长度错误,期望最小长度为5。

RECV-NLRI-AF-ERR

An incorrect Update message with an incorrect NLRI address family was received. The NLRI address family in the received message is %s (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Update消息,NLRI地址族错误。

RECV-UNLRI-LEN-ERR

An Update message with an incorrect UNLRI length was received. The length of the UNLRI is %d, and the expected minimum length is 3 (CompType=BGP_NM, VRFID=%d, peer ip=%s).

接收到错误的Update消息,UNLRI长度错误,期望最小长度为3。

RECV-UNLRI-AF-ERR

An incorrect Update message with an incorrect UNLRI address family was received. The UNLRI address family in the received message is %s (CompType=BGP_NM, VrfId=%d, peer ip=%s).

接收到错误的Update消息,UNLRI地址族错误。

RECV-OPEN-VER-ERR

An Open message with an incorrect version was received. The version of the received message is %d, and the expected version is 4.

接收到错误的Open消息,Open版本错误,期望版本为4。

BNM-HA-SN-MIS

The BNM backup message sequence number was incorrect (CompType=%s,msg-type=%d, class id=%d, Current SN=%d, Revc SN=%d).

BNM备份消息序列号错误。

BNM-BRM-SN-MIS

The message sequence number between BNM and BRM was incorrect. (CompType=%s,msg-type=%d, class id=%d, Current SN=%d, Revc SN=%d)

BNM-BRM之间消息序列号错误。

BNM-HA-SMOOTH-LONG

The data smoothing after the BNM component became the master component lasted for more than 60 minutes. (start time: %s, end time: %s)

BNM组件升主平滑超过60分钟。

BNM-HA-BB-LONG

BNM batch backup lasted for over 3600s and timed out (CurrentState=%u, LastState=%u, CurrentEvent=%u, LastEvent=%u).

BNM批备超时,超过了3600s。

BE-FC-BY-SOCKET

The flow control of BNM by the socket (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被Socket流控时间超过了20s。

BE-FC-BY-IFM

The flow control of BNM by IFM (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被IFM流控时间超过了20s。

BE-FC-BY-BFD

The flow control of BNM by BFD (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BFD流控时间超过了20s。

BE-FC-BY-GFD

The flow control of BNM by GFD (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被GFD流控时间超过了20s。

BE-FC-BY-BNM_SL

The flow control of BNM by BNM_BACKUP (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BNM_BACKUP流控时间超过了20s。

BE-FC-BY-SMP

The flow control of BNM by SMP (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被SMP流控时间超过了20s。

BE-FC-BY-SSP

The flow control of BNM by SSP (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被SSP流控时间超过了20s。

BE-FC-BY-BMP

The flow control of BNM by BMP (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BMP流控时间超过了20s。

BE-FC-BY-BRMIPV4

The flow control of BNM by BGP_RM_IPv4 (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BGP_RM_IPV4流控时间超过了20s。

BE-FC-BY-BRMVPNV4

The flow control of BNM by BGP_RM_VPNv4 (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BGP_RM_VPNV4流控时间超过了20s。

BE-FC-BY-BRMFLOWV4

The flow control of BNM by BGP_RM_FLOWv4 (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BGP_RM_FLOWV4流控时间超过了20s。

BE-FC-BY-BRMLABELV4

The flow control of BNM by BGP_RM_LABELv4 (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BGP_RM_LABELV4流控时间超过了20s。

BE-FC-BY-BRMMVPNV4

The flow control of BNM by BGP_RM_MCVPNv4 (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BGP_RM_MCVPNV4流控时间超过了20s。

BE-FC-BY-BRMMDTV4

The flow control of BNM by BGP_RM_MDTVPNv4 (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被BGP_RM_MDTVPNV4流控时间超过了20s。

BE-FC-BY-PIPE

The flow control of BNM by PIPE (component type=%u, component ID=0x%x) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM被PIPE流控时间超过了20s。

FC-PIPE

The flow control of PIPE (component type=%u, component ID=0x%x) by BNM lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM流控PIPE时间超过了20S。

FC-BRM

The BNM's flow control of BRM lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM流控BRM时间超过了20s。

STOP-PIPE

The BNM's pipe stop lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BNM停管道时间超过了20s。

STOP-PIPE

The BNM's pipe stop within 30 minutes lasted for over 6 minutes. (flow control duration =%us, and flow control count =%u).

30分钟内BNM停管道时间超过了6分钟。

FC-BRM

The flow control of BRM by BGP_NM within 30 minutes lasted for over 6 minutes. (flow control duration =%us, and flow control count =%u).

30分钟内BRM被BGP_NM流控时间超过了6分钟。

BE-FC-BY-PIPE

The flow control of BGP_NM by PIPE within 30 minutes lasted for over 6 minutes.(flow control duration =%us, and flow control count =%u, vrfid = %u, peer ip =%s).

30分钟内BGP_NM被管道流控时间超过了6分钟。

FC-PIPE

The flow control of PIPE by BGP_NM within 30 minutes lasted for over 6 minutes.(flow control duration =%us, and flow control count =%u, vrfid = %u, peer ip =%s).

30分钟内PIPE被BGP_NM流控时间超过了6分钟。

BE-FC-BY-SOCKET

The flow control of BGP_NM by SOCKET (Component type =0x%x, Component ID=0x%x) within 30 minutes lasted for over 6 minutes.

30分钟内BGP_NM被Socket流控时间超过了6分钟。

BE-FC-BY-BRMIPV4

The flow control of BGP_NM by BGP_RM_IPV4 (Component type =0x%x, Component ID=0x%x) within 30 minutes lasted for over 6 minutes.

30分钟内BGP_NM被BGP_RM_IPV4流控时间超过了6分钟。

BE-FC-BY-BRMVPNV4

The flow control of BGP_NM by BGP_RM_VPNV4 (Component type =0x%x, Component ID=0x%x) within 30 minutes lasted for over 6 minutes.

30分钟内BGP_NM被BGP_RM_VPNV4流控时间超过了6分钟。

PEER-ROUTE-LIMIT

The number of routes received from the peer reached the upper limit. (CompType=%s, VrfId=%u, Peer=%s,LimitValue=%u, ActualValue=%u)

从peer接收到的路由达到了上限。

TOTAL-ROUTE-LIMIT

The total number of received routes reached the upper limit. CompType=%s, VrfId=%u, Peer=%s,LimitValue=%u, ActualValue=%u

接收总路由达到了上限。

LABEL-LIMIT

The number of applied labels reached the upper limit. (CompType=%s,LimitValue=%u, ActualValue=%u)

申请标签达到了上限。

FES-TOKEN-LIMIT

The number of FES tokens exceeded the upper limit. CompType=%s, Token Exceed Node: LspXcType=%u,LspXcIndex=%u,IIDIndex=%u

FES Token超过了上限。

VPN-CROSS-LIST-BIG

The VPNv4 cross buffer list created by BRM exceeded the maximum length. (CompType=%s, LimitCnt=%u, ActualCnt=%u)

BRM创建的VPNV4交叉缓存列表超长。

GRESM-LBBUF-LIST-BIG

The label buffer list that BRM applied for from GRESM is too long. (CompType=%s, LimitCnt=%u,ActualSumCnt=%u, PerRouteLabelCnt=%u, PerVrfLabeCnt=%u, PerNexthopLabelCnt=%u)

BRM向GRESM申请标签的缓存列表超长。

TNLM-BUF-LIST-BIG

The buffer list in which BRM adds nodes to TNLM is too long. (CompType=%s, Vrfid=%u, LimitCnt=%u, ActualCnt=%u)

BRM向TNLM添加节点的缓存列表超长。

FES-LSPBUF-LIST-BIG

The buffer list in which BRM adds LSPs to FES is too long. (CompType=%s, Vrfid=%u ClassId=%u,LimitCnt=%u, ActualCnt=%u)

BRM向FES添加LSP的缓存列表超长。

BRM-ITERATIVE-IPRLY

BRM IP cyclic iteration occurred. (CompType=%s, VrfId=%u, OriginNexthop=%s,IterativeDepth=%u, Restraincount=%u, RestrainTime=%u)

BRM IP循环迭代。

BRM-ITERATIVE-TNLRLY

BRM tunnel cyclic iteration occurred. (CompType=%s, VrfId=%u, OriginNexthop=%s,IterativeDepth=%u, Restraincount=%u, RestrainTime=%u)

BRM隧道循环迭代。

GRESM-WITHDRAW-LABEL

A GREM label resource conflict occurred, and labels were withdrawn. (CompType=%s, Label=%u, Type=%s)

GREM标签资源冲突,撤销了标签。

GRESM-WITHDRAW-IID

A GREM IID resource conflict occurred, and IIDs were withdrawn. (CompType=%s, IID=%u, VrfId=%u, RelayFlag=0x%x, NextHop=%s, TnlPolicy=%u)

GRESM IID资源冲突,撤销了IID。

RM-SMOOTH-RT-AGED

During the smoothing, the imported routes were aged. (CompType=%s, VrfId=%u, Route=%s/%u)

平滑期间老化了引入路由。

RM-SMOOTH-RT-ADD

During the smoothing, the imported routes were added. (CompType=%s, VrfId=%u, Route=%s/%u)

平滑期间添加了引入路由。

RM-SMOOTH-RT-MODIFY

During the smoothing, the imported routes were modified. (CompType=%s, VrfId=%u, Route=%s/%u)

平滑期间修改了引入路由。

RM-VERIFY-RT-AGED

During the verification, the imported routes were aged. (CompType=%s, VrfId=%u, Route=%s/%u)

对账期间老化了引入路由。

RM-VERIFY-RT-ADD

During the verification, the imported routes were added. (CompType=%s, VrfId=%u, Route=%s/%u)

对账期间添加了引入路由。

RM-VERIFY-RT-MODIFY

During the verification, the imported routes were modified. (CompType=%s, VrfId=%u, Route=%s/%u)

对账期间修改了引入路由。

BEST-RT-CHANGED

The optimal route changed after periodic all-route selection. (CompType=%s, VrfId=%u, OldRt=%s, NewRt=%s)

定时全选路后最优路由发生变化。

BRM-HA-RCV-SN-MIS

The sequence numbers of received BRM HA messages did not match. (CompType=%s, MsgTpye=%u, ClassId=%u, RcvSn=%u, CurSn=%u)

BRM主备消息,接收序列号不匹配。

BRM-BNM-SN-MIS

The sequence numbers of the messages between BRM and BNM did not match. (CompType=%s, MsgTpye=%u, ClassId=%u, RcvSn=%u, CurSn=%u)

BRM与BNM之间消息,序列号不匹配。

BRM-GR-FAILED

BRM GR Failed, and the quit reason is %s (CompType=%s, VrfId=%u, Peer=%s).

reason:

The GR restart timer for the peer expired.

The GR EOR timer expired.

The device quitted GR when clearing peer data.

The device quitted GR to negotiate the GR capability when the peer was Up.

The GR Helper was not enabled.

BRM GR失败,退出GR的原因:
  • 邻居 GR Restart 定时器超时;
  • GR EOR定时器超时;
  • 清除邻居数据时退出GR;
  • 邻居Up但未协商GR能力,退出GR;
  • GR Helper未使能,退出GR。

BRM-HA-BB-LONG

The BRM batch backup lasted for more than 60 minutes. (CompType=%s,start time=%s, end time=%s)

BRM批量备份时间超过60分钟。

BRM-HA-SMOOTH-LONG

The smoothing after the slave BRM component became the master component lasted for more than 60 minutes. (CompType=%s,start time=%s, end time=%s)

BRM备升主平滑时间超过60分钟。

FES-SMOOTH-LONG

The FES entry smoothing between BRM and FESDS lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同FESDS平滑FES表项时间超过了180分钟。

GRESM-SMOOTH-LB-LONG

The label smoothing between BRM and GRESM lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同GRESM平滑标签时间超过了180分钟。

GRESM-SMO-STLB-LONG

The static label smoothing between BRM and GRESM lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同GRESM平滑静态标签时间超过了180分钟。

GRESM-SMO-IID-LONG

The IID smoothing between BRM and GRESM lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同GRESM平滑IID时间超过了180分钟。

RM_SMOOTH-IMP-LONG

The imported route smoothing between BRM and RM_IPv4 lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同RM_IPV4平滑引入路由时间超过了180分钟。

FES-VERIFY-LONG

The FES entry verification between BRM and FESDS lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同FESDS对账FES表项时间超过了180分钟。

GRESM-VERIFY-LB-LONG

The label verification between BRM and GRESM lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同GRESM对账标签时间超过了180分钟。

GRESM-VERI-STLB-LONG

The static label verification between BRM and GRESM lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同GRESM对账静态标签时间超过了180分钟。

GRESM-VERI-IID-LONG

The IID verification between BRM and GRESM lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同GRESM对账IID时间超过了180分钟。

RM-VERFIY_IMP-LONG

The imported route verification between BRM and RM_IPv4 lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同RM_IPV4对账引入路由时间超过了180分钟。

RM-VERFIY_NWK-LONG

The network route verification between BRM and RM_IPv4 lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同RM_IPV4对账网络路由时间超过了180分钟。

RM-VERIFY-PRO-LONG

The verification between BRM (producer) and RM_IPv4 lasted for more than 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM作为生产者同RM_IPV4对账时间超过180分钟。

TNLM-VERIFY-PRO-LONG

The verification between BRM (producer) and TNLM lasted for more than 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM作为生产者同TNLM对账时间超过180分钟。

BRM-VERIFY-GL-RT-LONG

The global route verification between BRM and RM_IPv4 lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同RM_IPV4对账全局路由时间超过了180分钟。

BRM-VERIFY-LC-RTLONG

The local route verification between BRM and RM_IPv4 lasted for over 180 minutes. (CompType=%s,start time=%s, end time=%s)

BRM同RM_IPV4对账本地路由时间超过了180分钟。

BE-FC-BY-BNM

The flow control of BRM (%s) by BGP_NM (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被BGP_NM流控时间超过了20s。

BE-FC-BY-GRESM

The flow control of BRM (%s) by GRESM (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被GRESM流控时间超过了20s。

BE-FC-BY-BMP

The flow control of BRM (%s) by BMP (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被BMP流控时间超过了20s。

BE-FC-BY-LDPM

The flow control of BRM (%s) by LDPM (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被LDPM流控时间超过了20s。

BE-FC-BY-FES

The flow control of BRM (%s) by FESDS (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被FESDS流控时间超过了20s。

BE-FC-BY-BFD

The flow control of BRM (%s) by BFD (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被BFD流控时间超过了20s。

BE-FC-BY-TNLM

The flow control of BRM (%s) by TNLM (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被TNLM流控时间超过了20s。

BE-FC-BY-BRMIPV4

The flow control of BRM (%s) by BGP_RM_IPv4 (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被BGP_RM_IPV4流控时间超过了20s。

BE-FC-BY-BRMVPNV4

The flow control of BRM (%s) by BGP_RM_VPNv4 (component type=%u) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM被BGP_RM_VPNV4流控时间超过了20s。

FC-BNM

The flow control of BRM (%s) by another component (component ID=%0x%x, component type=BGP_NM) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM流控其它组件时间超过了20s。

FC-BRMIPV4

The flow control of BRM (%s) by another component (component ID=%0x%x, component type=BRM_IPv4) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM流控其它组件时间超过了20s。

FC-BRMVPNV4

The flow control of BRM (%s) by another component (component ID=%0x%x, component type=BRM_VPNv4) lasted for over 20s. (TimeoutCnt=%u, start time=%s, end time=%s)

BRM流控其它组件时间超过了20s。

BE-FC-BY-BNM

The flow control of BRM (%s) by BGP_NM (component type=%u, Component ID=0x%x) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BRM被BGP_NM流控时间超过了6分钟。

BE-FC-BY-GRESM

The flow control of BRM (%s) by GRESM (component type=%u, Component ID=0x%x) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BRM被GRESM流控时间超过了6分钟。

BE-FC-BY-LDPM

The flow control of BRM (%s) by LDPM (component type=%u, Component ID=0x%x) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BRM被LDPM流控时间超过了6分钟。

BE-FC-BY-FES

The flow control of BRM (%s) by FESDS (component type=%u, Component ID=0x%x) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BRM被FESDS流控时间超过了6分钟。

BE-FC-BY-TNLM

The flow control of BRM (%s) by TNLM (component type=%u, Component ID=0x%x) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BRM被TNLM流控时间超过了6分钟。

BE-FC-BY-BRMIPV4

The flow control of BRM (%s) by BGP_RM_IPV4 (component type=%u, Component ID=0x%x) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BRM被BGP_RM_IPV4流控时间超过了6分钟。

BE-FC-BY-BRMVPNV4

The flow control of BRM (%s) by BGP_RM_VPNV4 (component type=%u, Component ID=0x%x) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BRM被BGP_RM_VPNV4流控时间超过了6分钟。

BE-FC-BY-RMIPV4

The flow control of BRM (%s) by RM_IPV4 (component type=%u, Component ID=0x%x) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BRM被RM_IPV4流控时间超过了6分钟。

FC-BNM

The flow control of BGP_NM (component type=%u, Component ID=0x%x) by BGP_RM (%s) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BGP_NM被BGP_RM流控时间超过了6分钟。

FC-BRMIPV4

The flow control of BGP_RM_IPV4 (component type=%u, Component ID=0x%x) by BGP_RM (%s) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BGP_RM_IPV4被BGP_RM流控时间超过了6分钟。

FC-BRMVPNV4

The flow control of BGP_RM_VPNV4 (component type=%u, Component ID=0x%x) by BGP_RM (%s) within 30 minutes lasted for over 6 minutes. (flow control duration=%us, and flow control count=%u)

30分钟内BGP_RM_VPNV4被BGP_RM流控时间超过了6分钟。

# 查看组播组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health multicast
last system health for multicast:
-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Show DGMP(Cid=0x80e22739) Health Record
-----------------------------------------------------------------------------------
PADS_Type            Detect-Time           Description
-----------------------------------------------------------------------------------

GROUP_TIMESOUT       06-13 09:07:06:208    The group timer expired.(VPNName:public 
                                           net,GrpAddr:225.0.0.1,IfName:GigabitEthe
                                           rnet1/0/1)
-----------------------------------------------------------------------------------
表12-178 pads diagnose system health multicast命令输出信息描述

项目

描述

Show DGMP(Cid=0x80e22739) Health Record

显示组播(Cid=组件ID)健康度检查信息。

PADS_Type

辅助诊断类型,具体描述请参见表12-179

Detect-Time

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-179

表12-179 pads diagnose system health multicast命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

ADD_ENTRY_FAIL

The number of IGMP entries exceeds the upper limit.

IGMP表项数量超出上限。

A multicast boundary policy is configured on the interface.

接口上配置了组播转发边界策略。

An IGMP group filtering policy is configured on the interface.

接口上配置了IGMP组过滤策略。

The IGMPv1 Join packet is discarded because IGMP On-demand is configured on the interface.

接口上配置了IGMP on-demand特性,导致IGMPv1加入报文被丢弃

The IGMP version set on the interface is inconsistent with the version in the received packet.

接收到报文的IGMP版本与接口上配置的IGMP版本不一致。

IGMP SSM mapping is disabled on the interface.

接口上禁用了IGMP SSM Mapping功能。

The SSM mapping policy does not contain rules with the specified source.

SSM Mapping策略未包含与指定组播源匹配的规则。

The IGMP packet may be filtered out by the source address policy.

IGMP报文可能被源地址策略过滤。

The number of PIM entries exceeds the upper limit.

PIM表项数量超出上限。

A multicast source filtering policy is configured.

配置了组播源过滤策略。

The upstream for the PIM entry does not exist.

PIM表项的上游不存在。

The group address is in the SSM range, and (*, G) join is not supported.

组地址属于SSM范围,不支持(*, G)加入。

The PIM Join packet is discarded because the RP address in the packet is incorrect.

报文中的RP地址不正确,导致PIM加入报文被丢弃。

ADD_OIF_FAIL

A multicast boundary policy is configured on the interface.

接口上配置了组播转发边界策略。

A multicast source filtering policy is configured.

配置了组播源过滤策略。

The group address is in the SSM range, and (*, G) join is not supported.

组地址属于SSM范围,不支持(*, G)加入。

The PIM Join packet is discarded because the RP address in the packet is incorrect.

报文中的RP地址不正确,导致PIM加入报文被丢弃。

The PIM Join packet is discarded because the upstream neighbor addresses in the packet is incorrect.

报文中的上游邻居地址不正确,导致PIM加入报文被丢弃。

The CPU usage is too high.

CPU使用率过高。

PIM is disabled on the interface.

接口上禁用了PIM功能。

OIF_JOIN_TIMESOUT

The device does not receive PIM Join packets.

设备未收到PIM加入报文。

OIF_ASSERT_TIMESOUT

The assert timer expired.

断言时间超期。

IIF_ASSERT_TIMESOUT

The assert timer expired.

断言时间超期。

ENTRY_SMOOTH_AGING

The entry is deleted because of smooth aging.

表项因平滑老化被删除。

GROUP_TIMESOUT

The group timer expired.

组播组定时器超期。

SOURCE_TIMESOUT

The source timer expired.

组播源定时器超期。

# 查看RM组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health rm
last system health for rm:
-----------------------------------------------------------------------------------
Show DIRECTRT_IPV4 Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime Description                                         
--------------------------------------------------------------------------------
AGING-INTERFACE     2018-06-13 DIRECTRT_IPV4 aged an interface.(IfIndex=1,Iftype=18
                     07:28:57  , Vrfindex=0, Address=0.0.0.0, Masklenth=0, VS=0).  
AGING-INTERFACE     2018-06-13 DIRECTRT_IPV4 aged an interface.(IfIndex=2,Iftype=17
                     07:28:57  , Vrfindex=0, Address=127.0.0.1, Masklenth=8, VS=0).
SMOOTH-NOT-END      2018-06-13 DIRECTRT_IPV4 check 30 minutes smooth state with com
                     07:28:12  ponent RM,the smooth state is not end.(VS=0).       
SMOOTH-NOT-END      2018-06-13 DIRECTRT_IPV4 check 30 minutes smooth state with com
                     07:28:14  ponent IFM,the smooth state is not end.(VS=0).      
Show TNLM Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime Description                                         
--------------------------------------------------------------------------------
AGING-TUNNEL        2018-06-13 Statistics about aged tunnels were collected.(CID=0x
                     07:26:08  11212334, virtual process ID=0x12456455, instance ID
                               =22068, number of aged tunnels=2, address family=IPv
                               4).                                                 
AGING-TUNNEL        2018-06-13 Statistics about aged tunnels were collected.(CID=0x
                     07:26:11  11212334, virtual process ID=0x12456455, instance ID
                               =22068, number of aged tunnels=3, address family=IPv
                               4).                                                 
Show GRESM Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime Description                                         
--------------------------------------------------------------------------------
RESOURCE-EXCEED     2018-06-13 The number of GRESM resources exceeded the upper lim
                     07:26:37  it.(ResType=LABEL, TotalNum=1000, VacancyNum=0, Exce
                               edState=START).                                     
RESOURCE-EXCEED     2018-06-13 The number of GRESM resources exceeded the upper lim
                     07:26:38  it.(ResType=LABEL, TotalNum=1000, VacancyNum=300, Ex
                               ceedState=END).                                     
RESOURCE-CONFLICT   2018-06-13 Resouce conflicts, GRESM withdraw this resource from
                     07:26:35   two users at the same time.(ResourceType=RESV, user
                               1Pid=0x8079040e, user1Type=0x70, user2Pid=0x8079040e
                               , user2Type=0x70).                                  
LABLE-FREE-FAILED   2018-06-13 GRESM failed to release labels.(ResType=SRLABEL, Res
                     07:26:34  ID=0x64, UserPid=0x8079040e).                       
RESOURCE-AGING      2018-06-13 After checking resource with component,GRESM aging s
                     07:26:48  ome resource not belong to this component. (PID=0x80
                               79040e, ResType=IID, ResCount=10, ResList=11 1 2 3 4
                                5 6 7 8 9 ).                  
表12-180 pads diagnose system health rm命令输出信息描述

项目

描述

Show FESDS(Cid=xx, Slot=xxx) Health Record

显示RM各组件健康度检查信息。

PadsType

辅助诊断类型,具体描述请参见表12-181

DetectTime

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-181

表12-181 pads diagnose system health rm命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

REQUEST-IID-FAILED

The IPv4 direct route component failed to apply for an IID. (Retcode=%u, IIDType=%u, IfIndex=%u, AddrOrigin=%u, Address=%s, VS=%u).

直连路由IPv4组件申请IID失败。

AGING-INTERFACE

The IPv4 direct route component aged an interface. (IfIndex=%u,Iftype=%u, Vrfindex=%u, Address=%s, Masklenth=%u, Aagecount=%u, VS=%u).

直连路由IPv4组件老化一个接口信息。

SMOOTH-NOT-END

The data smoothing between the IPv4 direct route component and the %s component exceeded %u minutes. (Start time=%s, End time=%s, VS=%u)

直连路由IPv4组件检查到与组件%s的平滑状态超过%u分钟不结束。

AGING-TUNNEL

The TNLM tunnel aged. (Tunnel PID=0x%x, Virtual Process ID=0x%x, Instance ID=%u, Number of Aged Tunnels=%u, Address Family=%s).

TNLM发生隧道老化。

RESOURCE-EXCEED

The number of %s resources of the GRESM component exceeded the upper limit. (TotalNum=%u, VacancyNum=%u, ExceedState=%s).

GRESM组件资源数量已超限。

RESOURCE-CONFLICT

The %s resources were used by two components. The GERSM component reclaimed resources from the two components. (User1Pid=0x%x, User1Type=0x%x, User2Pid=0x%x, User2Type=0x%x).

资源被两个组件同时使用而发生冲突,GERSM从两个组件回收资源。

LABLE-FREE-FAILED

GRESM failed to release %s resources. (ResID=0x%x, UserPid=0x%x).

GRESM释放资源失败。

RESOURCE-AGING

After data verification, GRESM aged %s resources. (Resource user PID=0x%x, ResCount=%u, ResList=%s).

对账之后,GRESM老化的资源数量。

ROUTE-INACTIVE

The nexthop of the static route is reachable, but the static route is inactive.(VPID=0x%x,VrfIndex=%u,TopoID=%u,TableID=%u,DestAddr=%s,MaskLen=%u,NextHop=%s,NexthopVrfId=%u)

静态路由下一跳可达但未活跃。

ALLOC-IID-FAILED

The static route failed to apply for IID resources.(%s)

静态路由申请IID资源失败。

ALLOC-LABEL-FAILED

The static route failed to apply for LABEL resources.(%s)

静态路由申请标签资源失败。

RELAY-DEPTH-EXCEED

The iteration depth of the static route exceeded the threshold.(Threshold depth=%u,VPID=0x%x,VrfIndex=%u,TopoID=%u,TableID=%u,OriginNH=%s)

静态路由迭代深度超限。

SMOOTH-NOT-END

The data smoothing between the static-route component (%s) and component 0x%x does not end.(ThresholdValue=%u,StartTime=%s,EndTime=%s)

静态路由作为生产者或者消费者和组件PID平滑未结束。

AGE-PRODUCER

The RM component aged the producer after data smoothing.(Partner=0x%x,ProcessID=%u,VPID=%u,Instance=%u,TopoID=%u,TableID=%u,ProtocolID=%u,Reason=%s)

路由管理组件平滑后老化生产者。

AGE-ROUTE

The prefix was aged. (AgedNum=%u, CompID=0x%x, VirtualProcessID=0x%x, InstanceID=%u, TopoID=%u, TableID=%u, Prefix=%s, MaskLen=%u)

前缀被老化。

AGE-ROUTE

The IID was aged. (AgedNum=%u, CompID=0x%x, VirtualProcessID=0x%x, InstanceID=%u, TopoID=%u, TableID=%u, IIDindex=%u)

IID被老化。

AGE-ROUTE

The attribute table was aged. (AgedNum=%u, CompID=0x%x, VirtualProcessID=0x%x, InstanceID=%u, TopoID=%u, TableID=%u, AttributeIndex=%u)

属性表被老化。

ROUTE-EXCEED

The number of prefixes exceeded the upper limit. (ExceedState=%s, VrfIndex=%u, TotalNum=%u, MaxLimitNum=%u)

前缀超限。

ROUTE-EXCEED

The number of routes exceeded the upper limit. (ExceedState=%s, VrfIndex=%u, TotalNum=%u, MaxLimitNum=%u)

路由超限。

LIST-LONG

The linked list is too long.(ListState=%s,ListType=%s,ListNodeNum=%u,ThresholdValue=%u,StartTime=%s,EndTime=%s)

链表过长。

BOARD-ISOLATION

Board isolate information.(IsolationState=%s,SlotName=%s,FeNodeId=%u,PID=0x%x,MGType=%s)

单板隔离信息。

CONGEST-NOT-END

The flow control between the RM module and component 0x%x exceeded the threshold.(FlowCtrlType=%s,DurationThreshold=%s,StartTime=%s,EndTime=%s)

路由管理和组件PID流控超过阈值。

SMOOTH-NOT-END

The data smoothing between the RM component (%s) and component 0x%x does not end."(ThresholdValue=%u,StartTime=%s,EndTime=%s)

路由管理组件作为生产者和组件PID平滑未结束。

SMOOTH-NOT-END

The data smoothing between the RM component (%s) and component 0x%x does not end."(ThresholdValue=%u,StartTime=%s,EndTime=%s)

路由管理组件作为消费者和组件PID平滑未结束。

VERIFY-NOT-END

The data verification between the RM component (%s) and component 0x%x does not end.(ThresholdValue=%u,StartTime=%s,EndTime=%s)

路由管理组件作为生产者和组件PID对账未结束。

VERIFY-NOT-END

The data verification between the RM component (%s) and component 0x%x does not end.(ThresholdValue=%u,StartTime=%s,EndTime=%s)

路由管理组件作为消费者和组件PID对账未结束。

RELIAB-INVALID

The %s of the data sent by the RM module is invalid.(PID=0x%x,Invalid ID=%u)

路由管理发送数据的类型失效。

# 查看SSP组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health ssp
last system health for ssp:
-----------------------------------------------------------------------------------
Show SSP Health Record
-----------------------------------------------------------------------------------
PADS_Type               Detect-Time       Description
-----------------------------------------------------------------------------------
SYS_CPU_OVERLOAD        07-23 16:47:20    Cpu overload.(Slot=1/17, CpuUsage=50%, Th
                                          reshold=4%)                              
SYS_CPU_HOP             07-23 16:46:52    Cpu hop.(Slot=1/17, latest CpuUsage=[50%,
                                           50%, 50%, 50%, 50%, 50%, 50%, 50%, 50%, 
                                          51%], SampleLen=10S, LastCpuUseage=40%, T
                                          hreshold=10%)                            
SYS_MEMORY_DAMAGE       07-23 16:46:48    Memory damage.(Slot=1/17, ProcessID=1021,
                                           ProcessName=APPLocation10001, DamageType
                                          =0x2118271b, File=/usr1/code/code_NOSV4_V
                                          RPV8/code/current/VRP/sysbase/ssp/src/app
                                          sample/compa/compa_debug_api_test.c, Line
                                          =1585)                                   
-----------------------------------------------------------------------------------
表12-182 pads diagnose system health ssp命令输出信息描述

项目

描述

Show SSP Health Record

显示SSP组件健康度检查信息。

PADS_Type

辅助诊断类型,具体描述请参见表12-183

Detect-Time

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-183

表12-183 pads diagnose system health ssp命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

SYS_MEMORY_LEAK

Memory leak.(Slot=%s, SystemMemUsed=%d, ProcessID=%d, ProcessName=%s, ProcessMemUsed=%d, HandleName=%s, HandleMemUsed=%d, MemType=%d, SimplePeriod=%d Day)

内存泄露。

SYS_MEMORY_DAMAGE

Memory damage.(Slot=%s, ProcessID=%d, ProcessName=%s, DamageType=0x%x, File=%s, Line=%d)

内存破坏。

SYS_MEMORY_REFREE

Memory refree.(Slot=%s, ProcessID=%d, ProcessName=%s, DamageType=0x%x, File=%s, Line=%d, LastFreeFile=%s, LastFreeLine=%d)

内存重复释放。

SYS_MEMORY_OVERLOAD

Memory ovload occur in the system.(Slot=%s, MemUsed=%dK, UseRate=%d%%, Threshold=%d%%)

系统发生了内存过载。

SYS_CPU_OVERLOAD

Cpu overload.(Slot=%s, CpuUsage=%d%%, Threshold=%d%%)

CPU过载。

SYS_CPU_HOP

Cpu hop.(Slot=%s, latest CpuUsage=[%d%%, %d%%, %d%%, %d%%, %d%%, %d%%, %d%%, %d%%, %d%%, %d%%], SampleLen = %ds, LastCpuUseage=%d%%, Threshold=%d%%)

CPU突增。

SYS_FLOWCTRLTIMEOUT

Flow control timeout.(Slot=%s, ProcessID=%d, ProcessName=%s, Type=%d, SendID=0x%x, RecvID=0x%x, Timelen=%d)

流控超时。

SYS_MSGPROCTIMEOUT

Message process timeout. (Slot=%s, ProcessID=%d, ProcessName=%s, SendID=0x%x, RecvID=0x%x, Intf=%d, SubIntf=%d, MsgType=%d, Timelen=%d)

消息处理超时。

SYS_PIPEPROCTIMEOUT

Pipe process timeout. (Slot=%s, ProcessID=%d, ProcessName=%s, ServiceID=%d, SendCpi=0x%x, RecvCpi=0x%x, LocalPipeID=%d, PeerPipeID=%d, Timelen=%d)

管道消息处理超时。

SYS_MSGSTARVE

Message starve timeout. (Slot=%s, ProcessID=%d, ProcessName=%s, SendID=0x%x, RecvID=0x%x, Intf=%d, SubIntf=%d, MsgType=%d, Timelen=%d)

消息饿死超时。

SYS_COMPSTARVE

Component starve timeout. (Slot=%s, ProcessID=%d, ProcessName=%s, CompCid=0x%x, Timelen=%d)

组件饿死超时。

SYS_THREADTIMEOUT

Thread process timeout. (Slot=%s, ProcessID=%d, ProcessName=%s, ThreadID=%d, ThreadName=%s TimeLen=%d)

线程处理超时。

SYS_MSGQUEUE_OVERLOAD

Message queue overload. (Slot=%s, ProcessID=%d, ProcessName=%s, CompCid=0x%x, CompName=%s MsgQueue=%d, MsgNum=%d)

消息队列过载。

# 查看OSPF组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health ospf
last system health for ospf:
-----------------------------------------------------------------------------------

Show ONM Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime          Description                                
--------------------------------------------------------------------------------
OSPF_FLOW_ENTER     2018-08-31 02:48:18 Component enter flowcontrol, CompName=ONM, 
                                        PeerCompName=SOCK, Time=0S.                
OSPF_FLOW_ENTER     2018-08-31 02:46:58 Component enter flowcontrol, CompName=ONM, 
                                        PeerCompName=SOCK, Time=0S.                
RECV_ERR_PACKET     2018-08-30 11:57:28 OSPFV3 receive error packet(IfName=GigabitE
                                        thernet1/0/1, IfIndex=8, Reason=Nbr state l
                                        ow).   
RECV_ERR_PACKET     2018-08-30 11:57:25 OSPFV3 receive error packet(IfName=GigabitE
                                        thernet1/0/1, IfIndex=8, Reason=Nbr state l
                                        ow).   

Show OLSDB Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime          Description                                
--------------------------------------------------------------------------------
OSPF_FLOW_ENTER     2018-08-31 02:48:37 Component enter flowcontrol, CompName=OLSDB
                                        , PeerCompName=DCN, Time=0S.               
OSPF_FLOW_ENTER     2018-08-31 02:48:19 Component enter flowcontrol, CompName=OLSDB
                                        , PeerCompName=IFM, Time=0S.               
OSPFV3_CONFLICT_RT_ 2018-08-29 06:47:15 Ospfv3 1 AreaId 0.0.0.0 Router IDs conflict
INTRA_RECOVER                           ion is recovered. OldRouterId is 1.1.1.1, n
                                        ewRouterId is 0.25.230.235.                
OSPFV3_CONFLICT_RT_ 2018-08-29 06:44:45 Ospfv3 1 AreaId 0.0.0.0 router ID 1.1.1.1 h
INTRA                                   ave conflict in an intra area.             
LARGE_QUEUE_BGPLS   2018-08-28 13:08:45 OSPFV3 1 has a large queue to communicate w
                                        ith Bgpls, RealUpdateCount is 100, RealRxmt
                                        Count is 100.                              
LARGE_QUEUE_SOCKET  2018-08-28 13:08:45 OSPFV3 1 has a large queue to communicate w
                                        ith Socket, WaitListCount is 100, RxmtListC
                                        ount is 100.                               
LARGE_QUEUE_RM      2018-08-28 13:08:45 OSPFV3 1 has a large queue to communicate w
                                        ith RM, RouteCount is 100, IidCount is 100,
                                         EcaAttrCount is 100.                      
FAIL_ALLOC_RES      2018-08-28 13:08:45 OSPF failed to apply for resources.(ResType
                                        =IID)                                      
FAIL_ALLOC_RES      2018-08-28 13:08:45 OSPF failed to apply for resources.(ResType
                                        =LABEL)                                    
OSPFV3_EXIT_PROTECT 2018-08-28 13:08:45 Ospfv3 1 has worked well for one hour, LSAs
                                         can be processed normally.                
OSPFV3_ENTER_PROTEC 2018-08-28 13:08:45 Ospfv3 1 delete lots of LSAs, and this boar
T                                       d had been reset recently for the same reas
                                        on. So don't reset board again, and don't d
                                        elete those LSAs whose age timer expired.  
OSPFV3_FLUSH_REBOOT 2018-08-28 13:08:45 Ospfv3 1 delete lots of LSAs, this board do
                                        esn't work well any more and need be reset.
LARGE_QUEUE_BGPLS   2018-08-28 13:07:00 OSPFV3 1 has a large queue to communicate w
                                        ith Bgpls, RealUpdateCount is 100, RealRxmt
                                        Count is 100.                              
LARGE_QUEUE_SOCKET  2018-08-28 13:07:00 OSPFV3 1 has a large queue to communicate w
                                        ith Socket, WaitListCount is 100, RxmtListC
                                        ount is 100.                               
LARGE_QUEUE_RM      2018-08-28 13:07:00 OSPFV3 1 has a large queue to communicate w
                                        ith RM, RouteCount is 100, IidCount is 100,
                                         EcaAttrCount is 100.                      
OSPFV3_EXIT_PROTECT 2018-08-28 13:07:00 Ospfv3 1 has worked well for one hour, LSAs
                                         can be processed normally.                
OSPFV3_ENTER_PROTEC 2018-08-28 13:07:00 Ospfv3 1 delete lots of LSAs, and this boar
T                                       d had been reset recently for the same reas
                                        on. So don't reset board again, and don't d
                                        elete those LSAs whose age timer expired.  
OSPFV3_FLUSH_REBOOT 2018-08-28 13:07:00 Ospfv3 1 delete lots of LSAs, this board do
                                        esn't work well any more and need be reset.

Show OCRM Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime          Description                                
--------------------------------------------------------------------------------
OSPF_PREFIX_SID_CON 2018-08-31 02:49:14 The prefix-sid conflict is clear. ProcessId
FLICT_CLEAR                              is 1, SrPrefixSid is 1, SrPrefixAddress is
                                         1.1.1.2/32, ConflictType is Sid conflict, 
                                        SrConflictState is ConflictSolve.          
OSPF_PREFIX_SID_CON 2018-08-31 02:49:14 The prefix-sid conflict is detected. Proces
FLICT                                   sId is 1, SrPrefixSid is 1, SrPrefixAddress
                                         is 1.1.1.2/32, SrConflictType is Sid confl
                                        ict, SrConflictState is InConflict.        
OSPF_FLOW_ENTER     2018-08-31 02:48:57 Component enter flowcontrol, CompName=OCRM,
                                         PeerCompName=RM_IPV4, Time=0S.            
OSPF_FLOW_ENTER     2018-08-31 02:48:50 Component enter flowcontrol, CompName=OCRM,
                                         PeerCompName=GRESM, Time=0S.              
OSPF_PREFIX_SID_CON 2018-08-29 12:44:57 The prefix-sid conflict is clear. ProcessId
FLICT_CLEAR                              is 1, SrPrefixSid is 1, SrPrefixAddress is
                                         1.1.1.2/32, ConflictType is Sid conflict, 
                                        SrConflictState is ConflictSolve.   
表12-184 pads diagnose system health ospf命令输出信息描述

项目

描述

Show xxx Health Record

显示xxx组件健康度检查信息。

PadsType

辅助诊断类型,具体描述请参见表12-185

DetectTime

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-185

表12-185 pads diagnose system health ospf命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

IP_CONFLICT IP address conflict, ProcId is %u, AreaId is %s, ConflictType is %s, Conflict IP is %s, Conflict router is %s and %s. IP地址冲突。
IP_CONFLICT_CHG Some router fix the conflict ip address, but conflict not resume, ProcId is %u, AreaId is %s, ConflictType is %s, Conflict IP is %s, fixed router is %s, Conflict router is %s and %s. 修正路由器冲突地址,但依然有其他冲突存在。
IP_CONFLICT_RESUME Some router fix the conflict ip address, conflict resume, ProcId is %u, AreaId is %s, ConflictType is %s, Conflict IP is %s, fixed router is %s, other advertise router is %s. 修正路由器冲突地址,冲突解除。
LIMIT_OSPFV2_NBR Ospfv2 %u nbr number (%u) is more than the limit(%u). OSPF邻居数量已超过上限。
LIMIT_OSPFV3_NBR Ospfv3 %u nbr number (%u) is more than the limit(%u). OSPFv3邻居数量已超过上限。
LIMIT_SR_NEXTHOP SR nexthop is not generated because the SR nexthop outgoing interface does not support Segment-routing, IfIndex is %u, max label stack num is %u, current label stack num is %u. SR下一跳不会生成,因为SR下一跳的出接口不支持Segment-routing。
LIMIT_IMPORT_NSSA_LSA Ospf %u area %s import nssa lsa (%u) is more than the limit(%u). OSPF区域引入的NSSA LSA已超过上限。
LIMIT_IMPORT_NSSA_LSA_CLEAR Ospf %u area %s import nssa lsa (%u) is no more than the limit. OSPF区域引入的NSSA LSA不再超过上限。
LIMIT_IMPORT_ASE_LSA Ospf %u import ase lsa (%u) is more than the limit(%u). OSPF引入的ASE LSA已超过上限。
LIMIT_IMPORT_ASE_LSA_CLEAR Ospf %u import ase lsa (%u) is no more than the limit. OSPF引入的ASE LSA不再超过上限。
OSPF_FLOW_ENTER Component enter flowcontrol, CompName=%s, PeerCompName=%s, Time=%uS. 组件进入流控。
OSPF_FLOW_OVERTIME Component flowcontrol overtime, CompName=%s, PeerCompName=%s, PeerCID=0x%x, OverTime=%uS. 组件流控超时。
LIMIT_LSDB_OVERFLOW_ENTER Ospf %u Component LSDB enter overflow, ase lsa count is %u, overflow limit is %u. OSPF LSDB组件数据库溢出。
LIMIT_LSDB_OVERFLOW_EXIT Ospf %u Component LSDB exit overflow, ase lsa count is %u. OSPF LSDB组件退出溢出状态。
OSPF_FLUSH_REBOOT Ospf %u delete lots of LSAs, this board doesn't work well any more and need be reset. OSPF删除了大量的LSA,当前单板工作异常,需要重新启动。
OSPF_ENTER_PROTECT Ospf %u delete lots of LSAs, and this board had been reset recently for the same reason. So don't reset board again, and don't delete those LSAs whose age timer expired. OSPF删除了大量的LSA,并且当前单板最近因为相同原因重启过。所以不再重启单板,不再删除本地超期的LSA。
OSPF_EXIT_PROTECT Ospf %u has worked well for one hour, LSAs can be processed normally. OSPF已经正常工作超过一小时,LSA可以按照正常流程处理。
OSPF_ERR_PACK_MORE Ospf %u receive lots of error packets , %u error packets received more than expert %u. OSPF收到大量错误报文。
OSPFV3_ERR_PACK_MORE Ospfv3 %u receive larger error packet , %u error packet received more than expert %u. OSPFv3收到大量错误报文。
OSPF_PREFIX_SID_CONFLICT The prefix-sid conflict is detected. ProcessId is %u, SrPrefixSid is %u, SrPrefixAddress is %s, SrConflictType is %s, SrConflictState is %s. 检测到前缀SID冲突。
OSPF_PREFIX_SID_CONFLICT_CLEAR The prefix-sid conflict is clear. ProcessId is %u, SrPrefixSid is %u, SrPrefixAddress is %s, ConflictType is %s, SrConflictState is %s. 检测到前缀SID冲突已解除。
RECEIVE_MY_OWN_PACKET Ospf %u IfIndex %u receive my own packet, srcAddr is %s. OSPF接口索引收到了自己的报文。
OSPF_CONFLICT_RT_INTF Ospf %u AreaId %s router ID %s conflict is detected on the interface, ifIndex is %u. OSPF在某一区域内的Router ID在接口上发生了冲突。
OSPF_CONFLICT_RT_INTER Ospf %u router ID %s may have occurred in inter-area. OSPF可能发生了区域间Router ID冲突。
OSPF_CONFLICT_RT_INTRA Ospf %u AreaId %s router ID %s have conflict in an intra area, selfIfIndex is %u, nbrIpAddr is %s, nbrRtrId is %s. OSPF在某一区域内检测到Router ID冲突。
OSPF_CONFLICT_RT_INTRA_RECOVER Ospf %u AreaId %s Router IDs confliction is recovered. OldRouterId is %s, newRouterId is %s. OSPF在某一区域内的Router ID冲突解决。
OSPFV3_CONFLICT_RT_INTF Ospfv3 %u AreaId %s router ID %s conflict is detected on the interface, ifIndex is %u. OSPFv3在某一区域内的Router ID在接口上发生了冲突。
OSPFV3_CONFLICT_RT_INTER Ospfv3 %u router ID %s may have occurred in inter-area. OSPFv3可能发生了区域间Router ID冲突。
OSPFV3_CONFLICT_RT_INTRA Ospfv3 %u AreaId %s router ID %s have conflict in an intra area. OSPFv3在某一区域内检测到Router ID冲突。
OSPFV3_CONFLICT_RT_INTRA_RECOVER Ospfv3 %u AreaId %s Router IDs confliction is recovered. OldRouterId is %s, newRouterId is %s. OSPFv3在某一区域内的Router ID冲突解决。
RCV_ERR_MESSAGE Ospf %u receive error message was discarded, MsgType is %u, ErrMsgCnt is %u, LocalComp is %s, PeerComp is %s. OSPF收到错误的消息后丢弃。
FAIL_ALLOC_RES OSPF failed to apply for resources.(ResType=%s). OSPF申请资源失败。
LARGE_QUEUE_RM %s %u has a large queue to communicate with RM, RouteCount is %u, IidCount is %u, EcaAttrCount is %u. 跟RM通讯的队列超长。
LARGE_QUEUE_SOCKET %s %u has a large queue to communicate with Socket, WaitListCount is %u, RxmtListCount is %u. 跟Socket通讯队列超长。
LARGE_QUEUE_BGPLS %s %u has a large queue to communicate with Bgpls, RealUpdateCount is %u, RealRxmtCount is %u. 跟BGP-LS通讯队列超长。
IF_FLAP %s %u`s interface %s has flapped %u times in 5 minutes(ifIndex=%u). %s %u的接口在5分钟内震荡的次数。
PEER_FLAP %s %u`s peer has flapped %u times in 5 minutes(peerRouterId=0x%08x, ifIndex=%u). %s %u的邻居在5分钟内震荡的次数。
ROUTE_AGE OSPF deleted route during import-route verification(ProcessId=%u, MT=%u, Route=%s). OSPF在引入路由对账期间删除了路由。
IID_AGE OSPF deleted iid during import-route verification(ProcessId=%u, IID=%u, NextHop=%s). OSPF在引入路由对账期间删除了IID。
RECV_ERR_PACKET %s receive error packet(IfName=%s, IfIndex=%u, Reason=%s). 收到了错误报文。
RECV_NOBODY_LSA OSPF receive nobody LSA(ProcessId=%u, AddrFamily=%u, IfName=%s, IfIndex=%u). OSPF收到的LSA只有报文头。

# 查看MSTP组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health mstp
last system health for mstp:
-----------------------------------------------------------------------------------
Show Mstp Health Record
--------------------------------------------------------------------------------
PadsType            DetectTime Description                                         
--------------------------------------------------------------------------------
PROCESS-INFO        2018-09-11 The bridge loses the position of root bridge.(VrId=0
                     03:24:28  ,ProcId=0,InstId=0,PreRoot=38ba-0205-a501,NewRoot=38
                               ba-455f-df02,RootPort=0,LogType=ROOTCHANGE)         
PROCESS-INFO        2018-09-11 The bridge loses the position of root bridge.(VrId=0
                     03:24:32  ,ProcId=0,InstId=0,PreRoot=38ba-455f-df02,NewRoot=38
                               ba-0205-a501,RootPort=1,LogType=ROOTCHANGE)         
PROCESS-INFO        2018-09-11 This notification indicates that the root bridge rol
                     03:24:32  e flapped.(VrId=0,ProcId=0,InstId=0)                
-----------------------------------------------------------------------------------
表12-186 pads diagnose system health mstp命令输出信息描述

项目

描述

Show Mstp Health Record

显示MSTP组件健康度检查信息。

PadsType

辅助诊断类型,具体描述请参见表12-187

DetectTime

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-187

表12-187 pads diagnose system health mstp命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

GLOBAL-INFO

The flow control of MSTP (Pid=0x%x) by SLAVE(PeerPid=0x%x) lasted for over (Duration=%u(s)).

MSTP主备持续流控时间超过了300s。

PORT-INFO

The type(0x%x)and length(%u byte)of the received BPDU packets do not match.(ProcessId=%u,IfIndex=%u,VrId=%u,PortType=%s)[type: 0x0-STP,0x80-TCN,0x2-RST]

接收到BPDU报文类型与长度不匹配。

PROCESS-INFO

The bridge loses the position of root bridge.(VrId=%u,ProcId=%u,InstId=%u,PreRoot=%s,NewRoot=%s,RootPort=%u,LogType=%s)

网络中存在一个更优的设备并且已经成为根桥,当前设备根桥地位不能再保持时,产生此异常告警。

GLOBAL-INFO

The flow control of MSTP (Pid=0x%x) by VLAN(PeerPid=0x%x) lasted for over (Duration=%u(s)).

MSTP被VLAN持续流控时间超过了300s。

GLOBAL-INFO

The flow control of MSTP (Pid=0x%x) by L2VPN(PeerPid=0x%x) lasted for over (Duration=%u(s)).

MSTP被L2VPN持续流控时间超过了300s。

GLOBAL-INFO

The flow control of MSTP (Pid=0x%x) by IFM(PeerPid=0x%x) lasted for over (Duration=%u(s)).

MSTP被IFM持续流控时间超过了300s。

PORT-INFO

The MSTP process's edge port with BPDU protection enabled will be shut down, because it received a BPDU packet.(ProcessId=%u,IfIndex=%u,VrId=%u,PortType=%s)

MSTP进程的端口上(启动了BPDU保护功能)收到了BPDU报文,该报文可能是用户恶意攻击的报文。

PROCESS-INFO

This notification indicates that the root bridge role flapped.(VrId=u,ProcId=u,InstId=%u)

此信息表示根桥角色发生了震荡。当MSTP网络中,存在BPDU报文透传时,会导致某些端口收到多份BPDU报文,当多份BPDU报文中根桥信息不一致时,会导致根桥震荡。

PROCESS-INFO

[PW_ON]MSTP has a message sequence error with L2VPN.(msgSeq=%u,localSeq=%u,vrId=%u,Pid=0x%x)

MSTP与L2VPN交互的流程PW_ON阶段出现消息失序。

PROCESS-INFO

[PW_END]MSTP has a message sequence error with L2VPN.(msgSeq=%u,localSeq=%u,vrId=%u,Pid=0x%x)

MSTP与L2VPN交互的流程PW_END阶段出现消息失序。

PROCESS-INFO

[PI_SubscribeOn]MSTP has a message sequence error with VLAN.(msgSeq=%u,localSeq=%u,vrId=%u,Pid=0x%x)

MSTP与VLAN交互的流程PI订阅ON阶段出现消息失序。

PROCESS-INFO

[PI_SubscribeEnd]MSTP has a message sequence error with VLAN.(msgSeq=%u,localSeq=%u,vrId=%u,Pid=0x%x)

MSTP与VLAN交互的流程PI订阅END阶段出现消息失序。

PROCESS-INFO

[LPSI_FinalEnd]MSTP has a message sequence error with VLAN.(msgSeq=%u,localSeq=%u,vrId=%u,Pid=0x%x)

MSTP与VLAN交互的流程LPSIEND阶段出现消息失序。

# 查看ARP组件健康度检查信息。

<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] pads diagnose system health arp
last system health for arp:
-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Show ARP(Cid=0x807704B3) Health Record
-----------------------------------------------------------------------------------
PADS_Type            Detect-Time       Description
-----------------------------------------------------------------------------------
ARP_EXCEED           09-14 03:43:52    The number of ARP entries exceeded the thres
                                       hold. (entPhysicalIndex=1, Slot name=1, Thre
                                       shold=147456, Number of dynamic ARP entries=
                                       10, Number of static ARP entries=0 TriggerTi
                                       me=09-14 03:43:52 RecoverTime=00-00 00:00:00
                                       )
ARP_EXCEED           09-14 03:43:50    The number of ARP entries exceeded the thres
                                       hold. (entPhysicalIndex=1, Slot name=1, Thre
                                       shold=147456, Number of dynamic ARP entries=
                                       10, Number of static ARP entries=0 TriggerTi
                                       me=09-14 03:43:50 RecoverTime=00-00 00:00:00
                                       )
IP_CONFLICT          09-14 03:42:48    Received an ARP packet with a duplicate IP a
                                       ddress from the interface. (VR=0, IfIndex=8,
                                        IpAddress=10.1.1.1, MacAddress=38e8-5e21-03
                                       00, PE-VLAN=0, CE-VLAN=0)
IP_CONFLICT          09-14 03:42:43    Received an ARP packet with a duplicate IP a
                                       ddress from the interface. (VR=0, IfIndex=8,
                                        IpAddress=10.1.1.1, MacAddress=38e8-5e21-03
                                       00, PE-VLAN=0, CE-VLAN=0)
-----------------------------------------------------------------------------------
表12-188 pads diagnose system health arp命令输出信息描述

项目

描述

Show ARP(Cid=0x807704B3) Health Record

显示ARP(Cid=组件Cid)健康度检查信息。

PADS_Type

辅助诊断类型,具体描述请参见表12-189

Detect-Time

检测到异常的时间。

Description

异常描述信息,具体描述请参见表12-189

表12-189 pads diagnose system health arp命令输出信息详细内容列表

辅助诊断类型

异常描述信息

异常描述信息解释

ARP_EXCEED

The number of ARP entries exceeded the threshold. (entPhysicalIndex=%u, Slot name=%s, Threshold=%u, Number of dynamic ARP entries=%u, Number of static ARP entries=%u TriggerTime=%02u-%02u %02u:%02u:%02u RecoverTime=%02u-%02u %02u:%02u:%02u).

ARP表项数量超过阈值。

IP_CONFLICT

Received an ARP packet with a duplicate IP address from the interface. (VR=%u, IfIndex=%u, IpAddress=%s, MacAddress=%02x%02x-%02x%02x-%02x%02x, PE-VLAN=%u, CE-VLAN=%u).

从接口上接收到IP地址冲突的ARP报文。

翻译
下载文档
更新时间:2019-08-09

文档编号:EDOC1000178140

浏览量:5601

下载量:56

平均得分:
本文档适用于这些产品
相关版本
相关文档
Share
上一页 下一页