HP Comware 5 Comware 5 Debug Manual Volume 1 Part number: 5998-5836
Legal and notice information © Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents 802.
ARP debugging commands ··········································································································································96 debugging arp packet ·········································································································································· 96 debugging arp status ············································································································································ 97 ARP snooping debuggi
BGP debugging commands ······································································································································· 176 debugging bgp ···················································································································································· 176 debugging bgp all ·············································································································································· 179 debugging bgp bfd
Connection limit debugging commands ··················································································································· 318 debugging connection-limit ································································································································ 318 Content filtering debugging commands ··················································································································· 321 debugging content-filter ··············
DNS debugging commands ······································································································································ 413 debugging dns····················································································································································· 413 debugging dns proxy·········································································································································· 415 DDNS debugging comman
02.1X debugging commands Some information in this chapter is device type specific. Devices in this chapter are categorized depending on their IRF capability and support for interface cards that use independent processors for forwarding traffic, as shown in Table 1.
Views User view Default command level 1: Monitor level Parameters all: Specifies all types of 802.1X debugging. error: Specifies 802.1X error debugging. event: Specifies 802.1X event debugging. packet: Specifies 802.1X packet debugging. slot slot-number: Specifies a card by its slot number. (Distributed devices—In standalone mode.) slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) chassis chassis-number slot slot-number: Specifies a card on an IRF member device.
Field Description DOT1X UnauthorTrans Receive an Error msg(ErrCode)... 802.1X received a message that should not be received in unauthorized state. Bad msg. The message had invalid parameters. SlaveBoard/IO: DOT1X Config By Port failed 802.1X failed to configure ports on the standby MPU or interface cards. MAIN/Slave: RPC get DOT1X Config By Port res: failed The active MPU or the standby MPU failed to obtain the port-specific 802.1X configuration from interface cards.
Table 3 Output from the debugging dot1x event command Field Description IfIndex : IfIndex Interface index. port :PortIndex Port index. Status : Status MAC address type. cmd = CmdType Command. return code: Errcode Return value or error code. EAPoL-Logoff... 802.1X received an EAPOL-Logoff frame. Executed Unauthoring op first for Reauth... 802.1X is processing the first unauthorization request of re-authentication. DOT1X SuccessTrans Receive an Error Code ulParam2(ErrCode) of MSG:VlanAsgnResp.
Field Description Recv:Broadcast Kickoff PreUser IPC Request. 802.1X received a broadcast to log off logged-in users. DOT1XSOP: Vlan HashTable Created.[port and auth index is nonsense.] The SOP module created a VLAN authorization hash table. DOT1XSOP: Vlan HashTable Deleted.[port and auth index is nonsense.] The SOP module deleted the VLAN authorization hash table. Notify DOT1X of vlan UnAsgn success The device sent a message to notify 802.1X that a VLAN was removed successfully.
Field Description Receive shakehanding-pkt with proxy-chk tag A port received a handshake packet with a proxy-check tag. Port control mode is portbase and there's users on port portindex The port control mode is port-based, and there are users on port portindex. Auth-Fail VLAN status is set to INITIAL because unauthorization is successful. The status of the Auth-Fail VLAN was set to INITIAL because unauthorization was successful.
*May 1 12:29:15:200 2000 Sysname 8021X/7/EVENT:Port:GigabitEthernet1/1,No resource exist. *May 1 12:29:15:207 2000 Sysname 8021X/7/EVENT:Port:GigabitEthernet1/1 Auth:204,Alloc or search resource successfully. *May 1 12:29:15:217 2000 Sysname 8021X/7/EVENT:Port:GigabitEthernet1/1, Auth:204,Band the resource to port successfully. // 802.1X allocated resources for the new connection because it does not conflict with existing ones.
*May 1 12:29:15:436 2000 Sysname 8021X/7/EVENT:Auth:204,Failed to send EAPoL-Notification... // 802.1X failed to send notification to the client. # Enable 802.1X packet debugging. Output similar to the following example is generated when a user requests authentication under the following conditions: • 802.1X is enabled on the device. • A RADIUS scheme is configured for user authentication.
AAA debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging aaa Use debugging aaa to enable AAA debugging. Use undo debugging aaa to disable AAA debugging. Syntax debugging aaa { all | error | event } service-type { ssl-vpn | super | wapi } undo debugging aaa { all | error | event } service-type wapi { ssl-vpn | super | wapi } Default AAA debugging is disabled.
Field Description Author-resp: Authorization response. Acct-start-req: Accounting-start request. Acct-stop-resp: Accounting-stop response. Acct-RLT-req: Real-time accounting request. Acct-RLT-res: Real-time accounting response. Table 6 describes output fields and messages for the debugging aaa event command. Table 6 Output from the debugging aaa event command Field Description Cut: Send message to access. AAA sent a cut response to the access module. Authen-req: Authentication request.
[AAA_FramedServiceType , 5, 1] [AAA_AccessUserType , 62, 10] [AAA_AuthType , 64, 3] [AAA_CalledStationID , 21, 0012-3F94-0394] [AAA_IfIndex , 49, -1] [AAA_PortVlanID , 50, 1] [AAA_NASPortType , 34, 19] [AAA_MacAddr , 66, 0012-3f94-0394] [AAA_UserIPAddress , 6, 192.168.0.78] [AAA_WAI , 57, 00010106000003EC00010000 *Apr 26 12:05:36:669 2000 Sysname AAA/7/Event:000FE2A0789000+] // AAA attributes carried in the access authentication request.
[AAA_CalledStationID , 21, 0012-3F94-0394] [AAA_IfIndex , 49, -1] [AAA_PortVlanID , 50, 1] [AAA_NASPortType , 34, 19] [AAA_MacAddr , 66, 0012-3f94-0394] [AAA_UserIPAddress , 6, [AAA_WAI , 57, 192.168.0.78] 000101060 *Apr 26 12:05:36:831 2000 Sysname AAA/7/Event:000000C00020000] [AAA_State , 53, 323132616365643668B49D46BB0A72E9] // AAA user information and AAA attributes carried in the request.
*Apr 26 12:05:36:992 2000 Sysname AAA/7/Event:UserID=0x0,Service-type=0x6000 Author-req (AccessHandle = 0, AccessID = 0) *Apr 26 12:05:37:02 2000 Sysname AAA/7/Event: [AAA_UserName , 1, wapi] [AAA_DomainName , 63, wapi] [AAA_Service , 4, 2] [AAA_FramedServiceType , 5, 1] [AAA_AccessUserType , 62, 10] [AAA_AuthType , 64, 3] [AAA_CalledStationID , 21, 0012-3F94-0394] [AAA_IfIndex , 49, -1] [AAA_PortVlanID , 50, 1] [AAA_NASPortType , 34, 19] [AAA_MacAddr , 66, 0012-3f
[AAA_AccessUserType , 62, 10] [AAA_AuthType , 64, 3] [AAA_CalledStationID , 21, 0012-3F94-0394] [AAA_IfIndex , 49, -1] [AAA_PortVlanID , 50, 1] [AAA_NASPortType , 34, 19] [AAA_MacAddr , 66, 0012-3f94-0394] [AAA_UserIPAddress , 6, [AAA_State , 53, 192.168.0.
// AAA created an online user. *Apr 26 12:05:37:325 2000 Sysname AAA/7/Event:UserID=0x0,Service-type=0x600b Acct-start-resp: Send message to access. // AAA sent an accounting response to the access module. # On the wireless AC, enable AAA error debugging. debugging aaa error service-type wapi *Nov 27 20:58:59:912 2007 Sysname AAA/7/Error:UserID=0x18,Service-type=0x600b Authen-req was rejected because the last one is being processing.
RADIUS debugging commands Some information in this chapter is device type specific. Devices in this chapter are categorized depending on their IRF capability and support for interface cards that use independent processors for forwarding traffic, as shown in Table 7.
Views User view Default command level 1: Monitor level Parameters packet: Specifies debugging for packets. acl acl-number: Specifies the ACL for matching RADIUS packets to be used for debugging. The acl-number argument is in the range 2000 to 3999. If this argument is configured multiple times, the most recent setting takes effect. Only the source IP address information in the ACL rules is used for matching packets. user username: Specifies the username string for matching online users' usernames.
Field Description Packet type identified by the code number: Code = [code-number] • • • • • • 1—Access-request. 2—Access-accept. 3—Access-reject. 4—Accounting-request. 5—Accounting-response. 11—Access-challenge. State State information when CHAP authentication was operating between the supplicant and server. Termination-Action The NAS termination action after the service ended. Remanent_Volume Remaining traffic that was allowed for the session.
// The connect_port attribute could not be transmitted because of a long NAS name. *Dec *Dec 6 15:36:38:956 2006 Sysname RDS/7/DEBUG:Send attribute list: 6 15:36:38:956 2006 Sysname RDS/7/DEBUG: [1 User-name ] [12] [yangliping] [2 Password ] [18] [04E3336BFA6E7E8AADBC6B4687AB2DF1] [4 NAS-IP-Address ] [6 ] [192.168.0.
0f 06 00 a0 00 00 55 06 00 00 02 58 1a 0c 00 00 07 db 1a 06 00 00 00 05 1a 7f 00 00 07 db 3d 79 36 06 00 00 00 00 37 06 00 00 00 00 38 06 00 00 00 00 3a 06 00 00 00 00 3b 3e 68 74 74 70 3a 2f 2f 31 39 32 2e 31 36 38 2e 30 2e 31 31 31 3a 38 30 2f 73 65 6c 66 73 65 72 76 69 63 65 2f 6d 6f 64 50 61 73 73 77 64 31 78 2e 6a 73 70 7c 75 73 65 72 4e 61 6d 65 42 06 00 00 00 00 43 11 56 31 30 30 52 30 30 32 42 30 33 44 31 30 35 3d 0a 32 67 44 77 35 33 76 76 // RADIUS displayed the contents of the received raw packe
*Dec [1 6 15:36:39:336 2006 Sysname RDS/7/DEBUG: User-name ] [12] [yangliping] [32 NAS-Identifier ] [17] [Sysname] [5 ] [6 ] [20975618] NAS-Port [87 NAS_Port_Id ] [18] [0100001000000002] [61 NAS-Port-Type ] [6 ] [15] [31 Caller-ID ] [16] [303030302D303030302D30303030] *Dec 6 15:36:39:367 2006 Sysname RDS/7/DEBUG: [40 Acct-Status-Type ] [6 ] [1] [45 Acct-Authentic ] [6 ] [1] [44 Acct-Session-Id ] [14] [106110615361] [8 Framed-Address ] [6 ] [19.19.19.
*Dec 6 15:36:39:472 2006 Sysname RDS/7/DEBUG:Receive Raw Packet is: *Dec 6 15:36:39:487 2006 Sysname RDS/7/DEBUG: 05 00 00 5f 27 5a b4 d3 4b b6 1e 19 b6 89 1b 30 40 42 2f 8e 1a 0c 00 00 07 db 1a 06 00 00 00 05 1a 3f 00 00 07 db 3d 39 33 21 c4 fa b5 c4 d5 ca ba c5 d3 e0 b6 ee ca c7 a3 ba 39 39 36 34 30 34 32 2e 34 39 20 d4 aa a1 a3 3d 0a 32 67 44 77 35 33 76 76 3e 06 6f 00 a8 c0 3f 06 3b 23 00 00 // RADIUS displayed the raw contents of the received response.
HWTACACS debugging commands Some information in this chapter is device type specific. Devices in this chapter are categorized depending on their IRF capability and support for interface cards that use independent processors for forwarding traffic, as shown in Table 9.
Default HWTACACS debugging is disabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of debugging for HWTACACS. error: Specifies debugging for errors. event: Specifies debugging for events. message: Specifies debugging for messages. receive-packet: Specifies debugging for received packets. send-packet: Specifies debugging for sent packets. slot slot-number: Specifies debugging for the card in a slot by the slot number. (Distributed devices.
Field Description TAC_AUTHEN_RecvCallBack:tacacs packet is null or userid>MAX Invalid TAC_AUTHEN_RecvCallBack. TAC_AUTHEN_RecvCallBack:replay node isn't in sendlist The received node was not in the to-be-sent list. Failed to create continue authentication request HWTACACS failed to create continue-authentication requests. Can not find a valid server when send authen packet fail HWTACACS failed to send authentication packet because no available server was found.
Field Description Error: hwtacacs, switch type error in TAC_HandleNode Type error. TAC get session fail HWTACACS failed to get the session. Error: hwtacacs, the packet to be sent is too big in TAC_HandleReqMsg The packet to be sent was too long. Error: hwtacacs, session status error in TAC_GetSession Session status error in the session to be obtained. Warning: hwtacacs, used up all sessions before process a require HWTACACS could not generate new session ID because the upper limit was reached.
Field Description Packet type: • 1—Authentication. • 2—Authorization. • 3—Accounting. type:type Packet flag: • 0—Encrypted. • 1—Not encrypted. flag:flag-id Table 12 describes output fields and messages for the debugging hwtacacs message command. Table 12 Output from the debugging hwtacacs message command Field Description TAC_MESSAGE for AAA->TAC HWTACACS message sent from the AAA module to the HWTACACS module.
Field Description Authorization type: AuthorType=author-type • • • • 4—EXEC user authorization request. 5—VPDN user. 6—PPP user. 7—VLAN user. Authentication method: AuthenMethod = method ArgNum = number • • • • • • • 0—Not set. 1—None. 2—KRB5. 3—Line. 4—Enable. 5—Local. 6—Tacacsplus. Number of authorization request attributes. Service type: Service=service • • • • • 0—None. 1—Login. 2—Password authentication. 3—PPP. 4—ARAP. Protocol= protocol-type Protocol type: IP, VPDN, or LCP.
Field Description TunnelAuthen=bool-value Whether or not tunnel authentication was enabled. UDPCheckSum=bool-value Whether or not the L2TP UDP CheckSum function was enabled. ucflag=flag-number Authentication result flag. ServerMsg=msg Server message to login user. Echo=number Username and password echo flag. MutilinkMax Maximum number of aggregated links. MutilinkCurrent Current number of aggregated links. PacketIn Number of transmitted incoming packets upon an action.
Field Description data Failure causes returned from the server. arg_cnt Number of authorization attributes. arg mm len Length of the attribute pair. arg Attribute pair. Table 14 describes output fields and messages for the debugging hwtacacs send-packet command. Table 14 Output from the debugging hwtacacs send-packet command Field Description version Version number. type Packet type. seq_no Session packet. session_id Session ID. length Packet body length, excluding the packet header.
# Enable HWTACACS event debugging. debugging hwtacacs event *Dec 6 10:33:58:772 2006 Sysname TAC/7/Event: Create HWTACACS authentication request packet success // HWTACACS created an authentication request. *Dec 6 10:33:58:804 2006 Sysname TAC/7/Event: hwtacacs create new session : // HWTACACS created a new session. session id: 41, user id: 0, server ip: 192.168.31.
session id: 45, user id: 0, server ip: 192.168.31.178 // Packet exchange completed. HWTACACS ended and removed the session. *Dec 6 10:33:59:566 2006 Sysname TAC/7/Event: hwtacacs create new session : session id: 48, user id: 0, server ip: 192.168.31.178 // HWTACACS created a new session.
UserID=2 PacketType=3 TemplateNum=0 UserName=lq UserMsg= *Dec AuthenType=1 PortName=vty0 AuthenService=1 PrivLevel=0 Version=c0 RemAddress=192.168.31.56 DataMsg= 6 10:38:14:336 2006 Sysname TAC/7/Event: TAC_MESSAGE for AAA->TAC: *Dec 6 10:38:14:336 2006 Sysname TAC/7/Event: UserID=2 PacketType=3 TemplateNum=0 UserName=lq UserMsg= AuthenType=1 AuthenService=1 PortName=vty0 PrivLevel=0 Version=c0 RemAddress=192.168.31.
*Dec 6 10:38:15:00 2006 Sysname TAC/7/Event: UserID= 2 Flag AuthenMethod= 6 AuthenType= 1 UserName=lq = 2 TemplateNum = 0 AuthenService= 1 UserPort=vty0 UserAddress=192.168.31.
2.168.31.56 *Dec 6 10:38:24:250 2006 Sysname TAC/7/Event: TAC_MESSAGE for AAA->TAC: *Dec 6 10:38:24:250 2006 Sysname TAC/7/Event: UserID= 2 Flag AuthenMethod= 6 UserName=lq = 4 TemplateNum = 0 AuthenType= 1 AuthenService= 1 UserPort=vty0 UserAddress=192.168.31.
# Enable debugging for received HWTACACS packets. debugging hwtacacs receive-packet *Dec 6 10:43:07:662 2006 Sysname TAC/7/Event: version:c0 seq_no:2 type:AUTHEN_REPLY flag:ENCRYPTED_FLAG session_id:51 length:16 status:AUTHEN_STATUS_GETPASS server_msg len:10 flag:REPLY_FLAG_NOECHO data len:0 server_msg:Password: data: // HWTACACS received an authentication response message. The server required the password be entered.
server_msg len:0 data len:0 status:ACCT_STATUS_SUCCESS server_msg: data: // HWTACACS received an accounting-stop message. # Enable debugging for sent HWTACACS packets.
arg1 :task_id=0 arg2 :timezone=0 arg3 :service=shell // HWTACACS sent an accounting-start request message. %Dec 6 10:46:36:206 2006 Sysname SHELL/4/LOGIN: lq@yang login from 192.168.31.56 %Dec 6 10:46:37:630 2006 Sysname SHELL/4/LOGOUT: lq@yang logout from 192.168.31.56 // A user logged in and logged out.
LDAP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging aaa-ldap Use debugging aaa-ldap to enable LDAP debugging. Use undo debugging aaa-ldap to disable LDAP debugging. Syntax debugging aaa-ldap { all | error | event | fsm } undo debugging aaa-ldap { all | error | event | fsm } Default LDAP debugging is disabled.
Field Description LDAP received an invalid message during authentication. Message type: • 0—AAA request. • 1—LDAP response. • 2—Timer timeout. The fsm-state-name argument indicates the current status of the state machine: Received invalid message (type=message-type) in state fsm-state-name • • • • • • • • • • AUTHEN_INIT. AUTHEN_ADMINBIND. AUTHEN_USRSEARCH. AUTHEN_USRBIND. AUTHOR_INIT. AUTHOR_ADMINBIND1. AUTHOR_USRSEARCH. AUTHOR_USRBIND. AUTHOR_ADMINBIND2. AUTHOR_GRPSEARCH.
Table 16 describes output fields and messages for the debugging aaa-ldap event command. Table 16 Output for the debugging aaa-ldap event command Field Description user Authentication/authorization user name. user id User ID assigned by AAA. scheme name LDAP scheme name. session id LDAP session ID. Failure reason: Sent response message to AAA (user id=user-id, operation-result). • • • • • • • • 68—Connection with the LDAP server failed. 69—No response is from the LDAP server.
*Dec 26 17:30:28:47 2007 Sysname ALDP/7/EVENT: Created timer (session id=5, timer id=272). *Dec 26 17:30:28:94 2007 Sysname ALDP/7/EVENT: Received LDAP response message (session id=5). // LDAP received a response and established the connection. *Dec 26 17:30:28:94 2007 Sysname ALDP/7/EVENT: Sent bindAdminRequest to server successfully (message id=1, session id=5, login name="cn=root"). // LDAP sent a request to bind the administrator DN.
// LDAP was unbound from the LDAP server and tore down the connection. *Dec 26 17:30:28:375 2007 Sysname ALDP/7/EVENT: Received authorization request from AAA (user=xyz@aaa, user id=2, scheme=scheme1). *Dec 26 17:30:28:375 2007 Sysname ALDP/7/EVENT: Created a session successfully (session id=6). // LDAP received an authorization request and created a session. *Dec 26 17:30:28:390 2007 Sysname ALDP/7/EVENT: Connecting with LDAP server (session id=6, server ip=192.168.6.2, server port=389).
*Dec 26 17:30:28:672 2007 Sysname ALDP/7/EVENT: Unbound the connection from LDAP server (session id=6). *Dec 26 17:30:28:687 2007 Sysname ALDP/7/EVENT: Connecting with LDAP server (session id=6, server ip=192.168.6.2, server port=389). *Dec 26 17:30:28:687 2007 Sysname ALDP/7/EVENT: Created timer (session id=6, timer id=278). *Dec 26 17:30:28:734 2007 Sysname ALDP/7/EVENT: Received LDAP response message (session id=6).
*Dec 10 11:25:33:858 2007 Sysname ALDP/7/FSM: Session (session id=2) state changed from AUTHOR_USRSEARCH to AUTHOR_USRBIND. *Dec 10 11:25:34:58 2007 Sysname ALDP/7/FSM: Session(session id=2) state changed from AUTHOR_USRBIND to AUTHOR_ADMINBIND2. *Dec 10 11:25:34:158 2007 Sysname ALDP/7/FSM: Session(session id=2) state changed from AUTHOR_ADMINBIND2 to AUTHOR_GRPSEARCH. // Authorization state machine's state was changed. # Enable LDAP error debugging.
SC debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging sc Use debugging sc to enable debugging for the SC module. Use undo debugging sc to disable debugging for the SC module. Syntax debugging sc { all | error | event } undo debugging sc { all | error | event } Default Debugging for the SC module is disabled.
Field Description szPassword Password. ulIsStopOnlyAcct Whether stop-only accounting is used. ulVOIPAcctPacketType Accounting packet type. ulVOIPServiceType Service type: card user or calling user. ulVOIPRemainMoney Remaining money. ulVOIPRemainTime Remaining time. ulVOIPAcctConnectionTime Accounting connection time. ulVOIPErrorReason AAA service error reason. ulVOIPCodecType Code of a call, reserved. ulVOIPCallRefrence Call reference that identifies a call.
Local server debugging commands debugging local-server Use debugging local-server to enable debugging for the local server function. Use undo debugging local-server to disable debugging for the local server function. Syntax debugging local-server { all | error | event | packet } undo debugging local-server { all | error | event | packet } Default Debugging for the local server function is disabled.
*Mar 28 09:52:58:860 2008 Sysname LS/7/EVENT: EAP_Type: 1 // The EAP server received a response of the ID type. *Mar 28 09:52:59:313 2008 Sysname LS/7/EVENT: EAP_Type: 4 // The EAP server received a response of the type MD5 challenge. *Mar 28 09:52:59:313 2008 Sysname LS/7/EVENT: EAP_MD5 passwords matched // The password for EAP_MD5 authentication was matched. # Enable local server packet debugging. Output similar to the following example is generated when an 802.
RADIUS server debugging commands debugging radius-server Use debugging radius-server to enable debugging for the RADIUS server function. Use undo debugging radius-server to disable debugging for the RADIUS server function. Syntax debugging radius-server { all | error | event | packet } undo debugging radius-server { all | error | event | packet } Default Debugging for the RADIUS server function is disabled.
01 02 00 76 31 51 00 00 18 5b 00 00 e2 5c 00 00 41 1f 00 00 01 03 31 02 12 c1 3a 0f 40 3c bf 3a 24 d1 fc 8e 0f ae 32 fb 86 04 06 7f 00 00 01 20 04 45 49 05 06 01 00 d0 02 57 12 30 31 30 30 30 31 33 30 30 30 30 30 30 30 30 32 3d 06 00 00 00 0f 06 06 00 00 00 02 07 06 00 00 00 ff 1f 13 30 30 2d 30 44 2d 38 38 2d 46 37 2d 43 32 2d 36 38 08 06 09 09 00 03 // The device displayed packet data in hexadecimal format.
ACFP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging acfp client Use debugging acfp client to enable ACFP client debugging. Use undo debugging acfp client to disable ACFP client debugging. Syntax debugging acfp client error [ verbose ] undo debugging acfp client error Default ACFP client debugging is disabled.
Filed Description getting the context ID The ACFP client was getting the context ID of a policy. getting/adding/deleting the rule The ACFP client was getting, adding, or deleting a rule from the server. getting operation status of a rule The ACFP client was getting the operation status of a rule from the server. Examples # Enable ACFP client error debugging.
Usage guidelines Table 20 describes output fields and messages for the debugging acfp client error command. Table 20 Output from the debugging acfp server error command Field Description Must bind EndTime with StartTime The policy end time must be bound with the start time. This information is output when the end time is not configured. Must bind StartTime with EndTime The policy start time must be bound with the end time. This information is output when the end time is not configured.
# Enable ACFP server packet debugging. If you configure the ACFP rule as dropping all packets received on Ethernet 1/1, output similar to the following example is generated: debugging acfp server packet *Feb 24 10:56:16:256 2006 Sysname ACFP/7/debug: ACFP_Packet: IP packet was dropped. // IP packets received on Ethernet 1/1 were dropped.
ACSEI debugging commands The output description tables in this document only contain fields and messages that require an explanation. ACSEI server debugging commands debugging acsei server Use debugging acsei server to enable ACSEI debugging. Use undo debugging acsei server to disable ACSEI debugging. Syntax debugging acsei server { all | error | event | packet } undo debugging acsei server { all | error | event | packet } Default ACSEI debugging is disabled.
Field Description Ver: Version ACSEI version. Packet sender: clientOrserver: 0 or 1 • 0–ACSEI client. • 1–ACSEI server. Packet type: Type: Message-Type • • • • • 0X01–Registration packets. 0X02–Information notifications. 0X03–Operation notifications. 0X04–Monitoring packets. 0X05–Deregistration packets. clientID: clientID Client with which the server is communicating. A client ID uniquely identifies a client. Length: Length Length of the ACSEI packet excluding the Ethernet header.
DstMac :000d-88f7-6701 FrameType : 88a7 SrcMac :00e0-fc34-ec14 ProtocolType : 0007 Reserved : 0000 Ver : 1 clientOrserver : 1 Type: 1 clientID : 1 Length : 10 Inner Code : 2 Identifier : 72 Length : 4 // Packet debugging information: The ACSEI server sent a registration acknowledgement to the ACSEI client and assigned the client the ID 1. #Jul 17 07:54:21:921 2007 Sysname ACSEI/8/Debug_ACSEI_Event: ACSEI Event: Status of client 1 is Open.
#Jul 17 07:54:21:921 2007 Sysname ACSEI/8/Debug_ACSEI_Send_Pkt: Sending ACSEI packet: Interface : Ethernet1/0 DstMac :000d-88f7-6701 FrameType : 88a7 SrcMac :00e0-fc34-ec14 ProtocolType : 0007 Reserved : 0000 Ver : 1 clientOrserver : 1 Type: 4 clientID : 1 Inner Code : 2 Length : 16 Identifier : 1 Length : 10 // Packet debugging information: The ACSEI server sent a monitoring acknowledgement to the ACSEI client.
packet: Specifies ACSEI client packet debugging. Usage guidelines Table 23 describes output fields and messages for the debugging acsei-client packet command. Table 23 Output from the debugging acsei-client packet command Field Description Interface: interface Interface enabled with ACSEI client. DstMac: dst-mac Destination MAC address of the packet. SrcMac: src-mac Source MAC address of the packet. FrameType: frame-type Frame type of the packet.
debugging acsei-client all #Jul 17 08:01:12:00 2007 Sysname ACSEI/8/Debug_ ACSEI_Send_Pkt: Sending ACSEI packet: Interface: Ethernet 1/0 DstMac : 010f-e200-0021 SrcMac : 000d-88f7-6701 FrameType: 88a7 ProtocolType: 0007 Reserved: 0000 Ver: 1 clientOrserver : 0 Type: 1 clientID : 0 Length: 10 Inner Code: 1 Identifier: 72 Length: 4 // Packet debugging information: The ACSEI client sent a registration request to an ACSEI server. The MAC address of the ACSEI server is 010f-e200-0021.
Receiving ACSEI packet: Interface : Ethernet 1/0 DstMac :000d-88f7-6701 FrameType : 88a7 SrcMac :010f-e200-0021 ProtocolType : 0007 Reserved : 0000 Ver : 1 clientOrserver : 1 Type: 4 clientID : 1 Length : 10 Inner Code : 2 Identifier : 5 Length : 10 // Packet debugging information: The ACSEI client received a monitoring acknowledgement from the ACSEI server.
clientID : 0 Length: 10 Inner Code: 1 Identifier: 72 Length: 4 // The ACSEI client sent a registration request to an ACSEI server. The MAC address of the ACSEI server is 010f-e200-0021.
Active and standby switchover debugging commands The output description tables in this document only contain fields and messages that require an explanation. The active and standby switchover module name is identified as "HA" in debugging messages. debugging ha Use debugging ha to enable active and standby switchover debugging. Use undo debugging ha to disable active and standby switchover debugging.
Table 24 Output from the debugging ha error command Field Description Output for Inter-Process Communication (IPC) failure: • NextSend—Next sending position. HA IPC Information: NextSend NextFreeSlot WindowAllowed Acked NumOfMsg • NextFreeSlot—Next free position. • Acked—Last acknowledge position. • NumOfMsg—Number of messages. • WindowAllowed—Free space of the window.
Field Description NOT Resetting the send position The sending position was not reset although the replied serial number was wrong. Received seqnum seq-number, expected exp-number dropping... The standby MPU discarded the packet because the serial number was wrong. WARNING: IPC Queue is Full, Will be Resent Later size:%d MID=%x SID=%x The IPC queue was full when HA was sending a message. Event Write Failed ..... Failed to write events to the HA module.
Table 26 Output from the debugging ha message command Field Description HA sent a message to the destination module: • src-mid—Source module ID. • src-sid—Source module sub ID. Sending Src MID = src-mid, Src SID = src-sid, Dst MID = dst-mid, Dst SID = dst-sid, type = msg-type, Len = length, Seq Num = msg-seq • dst-mid—Destination module ID. • dst-sid—Destination module sub ID. • msg-type—Message type. • length—Message length. • msg-seq—Message sequence number.
debugging ha event *Jan 29 14:56:54:32 2007 Sysname HA/7/DEBUG:From Module Src MID=2150000, Src SID=1, Dst MID=2150000, Dst SID=1, type=c, Len=124, Seq Num = 0 // HA received a message from the VLAN module. # Enable active and standby switchover message debugging. debbugging ha message *Jan 29 14:44:52:299 2007 Sysname HA/7/DEBUG:Deliver up Src MID=2800000, Src SID=0, Dst MID=3440000, Dst SID=0, type=b, Len=0, Seq Num = 0 // HA sent a backup message to the application module.
Adjacency table debugging commands The output description tables in this document only contain fields and messages that require an explanation. IPv4 adjacency table debugging commands debugging adjacent-table all Use debugging adjacent-table all to enable both IPv4 adjacency entry debugging and IPv4 adjacency table event debugging. Use undo debugging adjacent-table all to disable IPv4 adjacency entry debugging and IPv4 adjacency table event debugging.
Default command level 1: Monitor level Usage guidelines Table 28 describes output fields and messages for the debugging adjacent-table entry command. Table 28 Output from the debugging adjacent-table entry command Field Description IP Address Next hop address of the outgoing interface of the adjacency table. ulRouteIfIndex Routing interface. ulPhyIfIndex Physical interface. ulLogicIfIndex Logical interface. ucServiceType Service type of the adjacency entry, such as PPP and IP over ATM.
// Debugging information for adding an adjacency entry. *Aug 19 14:28:39:875 2007 Sysname ADJ4/7/Adj4_Entry_Delete: IP Address : 0.0.0.0 ulRouteIfIndex : S2/0 ulPhyfIndex : S2/0 ulLogicIfIndex : N/A ucServiceType : PPP ucActionType : FORWARDING usSlot : 0 ulMtu : 1500 LinkHeadLen(IP): 4 LinkHead(IP) ucLinkMediaType ulTimeStamp : P2P : 99013 ulVirtualCircuitInfo : N/A LinkHeadLen(MPLS) : 4 : ff030021 LinkHead(MPLS) : ff030281 // Debugging information for deleting an adjacency entry.
Field Description ucSynFlag Flag indicating whether the entry is synchronized. ulVirtualCircuitInfo Virtual link information of the adjacency entry, such as PVC and DLCI. N/A is displayed for the virtual link of ATM, because the adjacency table does not support ATM. ulMtu MTU value. ADJ4 slot insert(remove) information Information of the card that is inserted or removed. The Inserted(Removed) Slot ID is 2 Number of the slot where the card is inserted or removed.
Views User view Default command level 1: Monitor level Usage guidelines See Table 30 and Table 31 for output fields and messages for the debugging command. debugging ipv6 adjacent-table entry Use debugging ipv6 adjacent-table entry to enable IPv6 adjacency entry debugging. Use undo debugging ipv6 adjacent-table entry to disable IPv6 adjacency entry debugging. Syntax debugging ipv6 adjacent-table entry undo debugging ipv6 adjacent-table entry Default IPv6 adjacency entry debugging is disabled.
Examples # Enable IPv6 adjacency entry debugging. debugging ipv6 adjacent-table entry *Jun 5 11:19:37:250 2007 Sysname ADJ6/7/Adj6_Entry_Add: IPv6 Address : N/A ulRouteIfIndex : Pos1/0 ulLogicIfIndex : N/A ucServiceType : PPP ucSlot : 1 ucSynFlag : Y ulMtu : 4478 ulPhyfIndex ulVirtualCircuitInfo : N/A : Pos1/0 // IPv6 adjacency table added an entry.
Field Description ulRouteIfIndex IPv6 routing interface. ulPhyIfIndex IPv6 physical interface. ulLogicIfIndex IPv6 logical interface. ucServiceType Service type of the adjacency entry, such as PPP and IP over ATM. Only PPP is supported. ucslot Slot number. ucSynFlag Flag indicating whether the entry is synchronized. ulVirtualCircuitInfo Virtual link information of the IPv6 adjacency entry, such as PVC and DLCI.
Service flow redirection debugging commands The data plane flow redirection module name is identified as "DPFLWRDR" in debugging messages. The output description tables in this document only contain fields and messages that require an explanation. debugging flow-redirect Use debugging flow-redirect to enable debugging for service flow redirection. Use undo debugging flow-redirect to disable debugging for service flow redirection.
Table 33 Output from the debugging flow-redirect packet command Field Description Thread thread-id, received xxx packets: (src-ip-addr)->(dst-ip-addr), mm bytes. Thread thread-id received mm bytes of xxx packets. The packet source IP address is src-ip-addr, destination IP address is dst-ip-addr. The xxx indicates the type of the received packets, including TCP RST, TCP RST, and other.
AFT debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging aft Use debugging aft to enable AFT debugging. Use undo debugging aft to disable AFT debugging. Syntax debugging aft { alg | all | event | packet } [ interface interface-type interface-number ] undo debugging aft { alg | all | event | packet } [ interface interface-type interface-number ] Default AFT debugging is disabled.
Field Description Failed to update FTP data. AFT failed to update FTP data. The SessionInfo does not exist. Session information did not exist. The SessionAttachInfo does not exist. Session attach information did not exist. Failed to translate ICMPv6 type and code. AFT failed to translate the ICMPv6 type and code fields. Failed to translate ICMPv6 inner IPv6 header. AFT failed to translate the inner IPv6 header of an ICMPv6 packet. Failed to translate ICMPv6 data.
Field Description Failed to get the packet information, dropping packet. AFT failed to read the packet and dropped it. The SessionInfo or AttachInfo does not exist, dropping packet. AFT dropped the packet because the SessionInfo or AttachInfo field of the packet did not exist. Invalid IPv4 address, dropping packet. AFT dropped the packet because its IPv4 address was invalid. Unexpired source route option found. An ICMPv6 error generated.
Field Description AFT translated the IPv6 packet into an IPv4 packet. Before address translation: IPv6 packet is translated to IPv4 packet. (ipv6-address1 : port1 – ipv6-address2 : port2) (ipv4-address1 : port3 – ipv4-address2 : port4) • • • • ipv6-address1—Source IPv6 address. port1—Source port, ipv6-address2—Destination IPv6 address. port2—Destination port. After address translation: • • • • ipv4-address1—Source IPv4 address. port3—Source port. ipv4-address2—Destination IPv4 address.
debugging aft event *Mar 10 14:34:02:547 2010 Sysname AFT/7/EVENT: The outgoing interface is disabled, dropping packet. // AFT dropped the packet because it was disabled on the outgoing interface.
ALG debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging alg Use debugging alg to enable ALG debugging. Use undo debugging alg to disable ALG debugging. Syntax debugging alg { event | packet } undo debugging alg { event | packet } Default ALG debugging is disabled. Views User view Default command level 2: System level Parameters event: Specifies debugging for events. packet: Specifies debugging for packets.
Field Description NAT information: (interface-type interface-number) from VPN : vpnindex, Pro : protocol, Direction : direction (original ip: original port) ----> (new ip: new port ). • • • • • • • • interface-type interface-number—NAT applied interface. VPN—VPN with the index of vpnindex. Pro—NAT protocol. Direction—NAT direction (in/out). original ip—Original IP address. original port—Original port. new ip—IP address after NAT. new port—Port after NAT. Alloc IPC_RPC_MSG error.
Field Description The H.245 state machine supports the following states: • H245_TCP_READY—The TCP connection has been established, but H.245 packet is not sent yet. H.245 FSM has changed from A to B. • H245_OPEN—Begins capability exchange. • H245_CLOSE—The H.245 session ends. The SIP state machine supports the following states: • SIP_READY—Ready state. The party is ready to receive and initiate multimedia session. • SIP_CALL—Calling state.
Field Description NBT response types: Received a NBT type RESPONSE. • • • • • • • • • • POSITIVE NAME REGISTRATION. NEGATIVE NAME REGISTRATION. POSITIVE NAME RELEASE. NEGATIVE NAME RELEASE. POSITIVE NAME QUERY. NEGATIVE NAME QUERY. REDIRECT NAME QUERY. WAIT FOR ACKNOWLEDGEMENT. NODE STATUS. END-NODE CHALLENGE REGISTRATION. NBT session FSM error, dropping packet. NBT session service state machine error. ALG discarded the packet. RTSP FSM error, dropping packet. RTSP state machine error.
Field Description SIP request types: Received a SIP type REQUEST. • • • • • • • • • • • • • • • INVITE. ACK. OPTIONS. BYE. CANCEL. REGISTER. INFO. PRACK. SUBSCRIBE. NOTIFY. UPDATE MESSAGE. UNSUBSCRIBE. REFER. PUBLISH. FEATURE. ALG received a SIP response. The packet type can be: Received a SIP type RESPONSE. SCCP FSM error. • • • • • • INFORMATIONAL. SUCCESSFUL. REDIRETION. CLIENT ERROR. SERVER ERROR. GLOBAL FAILURE. SCCP state machine error. ALG failed to translate the SCCP packet.
Field Description ALG received an SCCP packet. The packet type can be: Received SCCP type packet. • • • • • • • • • • Register. IPPort. OpenReceiveChannelAck. StartMediaTransmission. RegisterAck. Keepalive. UnRegister. KeepaliveACK. OpenMultiMediaReceiveChannelAck. StartMultiMediaTransmission. ALG received an SCCP CallState packet. The packet type can be: Received SCCP type CallState packet. Received SCCP packet (Type: id). • • • • • • • • • • • • • • OffHook. OnHook. RingOut. RingIn. Connected.
// The ALG module obtained NAT information in the packet payload after the PORT command was executed. # Enable ALG packet debugging on the device with DNS ALG enabled. Output similar to the following example is generated when a host on the private network accesses a DNS server on the public network in type-A query mode. In this mode, the host queries an IPv4 address by domain name. debugging alg packet *0.418080 Sysname ALG/8/PACKETS: Receive a DNS query packet.
# Enable ALG event debugging on the device with H.323 ALG enabled. Output similar to the following example is generated when an H.323 terminal on the private network calls another H.323 terminal on the public network. debugging alg event *Aug 24 10:50:58:500 2007 Sysname DPALG/7/debug: H.225 FSM has changed from H225_CALL_TCP_READY to H225_CALL_DELIVERED. // The ALG module received a setup packet from the calling party and its state changed from H225_CALL_TCP_READY to H225_CALL_DELIVERED.
ARP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging arp packet Use debugging arp packet to enable ARP packet debugging. Use undo debugging arp packet to disable ARP packet debugging. Syntax debugging arp packet [ ipacl ipacl-number | macacl macacl-number ] * undo debugging arp packet Default ARP packet debugging is disabled.
*Apr 19 16:02:20:832 2006 Sysname ARP/7/arp_rcv:Receive an ARP Packet, operation : 1, sender_eth_addr : 0000-0000-0001, sender_ip_addr : 2.2.1.1, target_eth_addr : 0000-0000-0000, target_ip_addr : 2.253.253.1 //ARP received an ARP request with target IP address 2.253.253.1 and sender IP address 2.2.1.1. *Apr 19 16:02:21:422 2006 Sysname ARP/7/arp_send:Send an ARP Packet, operation : 2, sender_eth_addr:00e0-fc5a-ed28, sender_ip_addr : 2.253.253.1, target_eth_addr : 0000-0000-0001, target_ip_addr : 2.2.1.
Table 40 Output from the debugging arp status command Field Description ARP Item Status Change Status change of the ARP entry. eth_addr Hardware address of the ARP entry. ip_addr IP address of the ARP entry. The status of the ARP entry changed from state1 to state2. ARP entry status: state1 -> state2 • INITIALIZE—The ARP entry is not generated. • NO_AGE—The ARP entry does not begin to age for it is a newly generated one. • AGING—The ARP entry is in the aging process.
ARP snooping debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging arp-snooping Use debugging arp-snooping to enable ARP snooping debugging. Use undo debugging arp-snooping to disable ARP snooping debugging.
Table 42 describes output fields and messages for the debugging arp-snooping info command. Table 42 Output from the debugging arp-snooping info command Field Description Receive an ARP and begin to modify existed entry ARP updated the existing entry. Receive an ARP and begin to add one entry ARP added an ARP entry. TCN VLAN bitmap: xx xx xx xx Port num: n Content of the TCN message.
*Jul 30 09:05:39:844 2007 Sysname ARP/7/Debug_ARP_Snooping_Information: ARP_Snooping Information: ARP snooping begin to forward the packet // ARP snooping forwarded the ARP packet. *Jul 30 09:24:45:703 2007 Sysname ARP/7/Debug_ARP_Snooping_Information: ARP_Snooping Information: Receive an ARP and begin to add one entry // ARP snooping received an ARP reply and creates a new entry to save the resolution result.
ARP fast-reply debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging arp fast-reply Use debugging arp fast-reply to enable ARP fast-reply debugging. Use undo debugging arp fast-reply to disable ARP fast-reply debugging. Syntax debugging arp fast-reply { all | error | packet | info } undo debugging arp fast-reply { all | error | packet | info } Default ARP fast-reply debugging is disabled.
Table 45 Output from the debugging arp fast-reply packet command Field Description Receive ARP packet: ARP received ARP packets. The received ARP packets include the following information: Src Interface : ifName • • • • • • VLAN ID : vlan id SrcArpMac : xxxx-xxxx-xxxx SrcIp : x.x.x.x DstArpMac : xxxx-xxxx-xxxx DstIp : x.x.x.x SrcEthMac:xxxx-xxxx-xxxx xxxx-xxxx-xxxx DstEthMac : PacketType :packet Type Send ARP packet: Sending interface. VLAN to which the sending interface belongs.
DstArpMac :0000-0000-0000 DstIp :6.0.0.1 SrcEthMac :0000-0000-0012 DstEthMac :ffff-ffff-ffff PacketType :REQUEST // ARP received an ARP request. *Sep 12 11:42:33:969 2007 Sysname ARP/7/Debug_ARP_FastReply_Information: ARP_FastReply Information: Get info from ARP Snooping: VLAN ID: 1, Port: Ethernet1/2 IP Addr: 6.0.0.5, MAC Addr: 0000-0000-0012, // ARP found a matching entry in the ARP snooping table.
ATM debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging atm all Use debugging atm all to enable all types of ATM debugging. Use undo debugging atm all to disable all types of ATM debugging. Syntax debugging atm all undo debugging atm all Default All types of ATM debugging are disabled.
undo debugging atm error [ interface interface-type interface-number [ pvc { pvc-name | vpi/vci } ] ] Default Debugging for ATM errors is disabled. Views User view Default command level 1: Monitor level Parameters interface-type interface-number: Specifies an interface by its type and number. pvc-name: PVC name, a string of 1 to 16 characters. A PVC name is unique on an ATM interface and is not case-sensitive. It cannot be a valid VPI/VCI pair (such as 1/20).
• Only one side of the connection is assigned an IP address. • Router A is configured as follows: system-view [RouterA] interface Atm5/0 [RouterA-Atm5/0] pvc 10/33 [RouterA-atm-pvc-Atm1/10/33] map ip inarp • Router B is configured as follows: system-view [RouterB] interface Atm6/0 [RouterB-Atm6/0] pvc 10/33 [RouterB-atm-pvc-Atm1/10/33] map ip inarp [RouterB-atm-pvc-Atm1/10/33] quit [RouterB-Atm6/0] ip address 100.1.1.2 255.255.255.0 debugging atm error *0.
If you do not specify the PVC name or VPI/VCI pair, the operation applies to all PVCs. Table 49 describes output fields and messages for the debugging atm event command. Table 49 Output from the debugging atm event command Field Description interface name Interface name. pvc VPI/VCI VPI/VCI pair. event Event description. no local ip, in inarp msg ignored An InARP packet was dropped because the local IP address is not available. inarp timeout, map cleared for no reply An InARP packet timed out.
debugging atm oam Use debugging atm oam to enable debugging for ATM OAM, which displays information about the OAM packets sent/received on an ATM interface. Use undo debugging atm oam to disable debugging for ATM OAM. Syntax debugging atm oam [ interface interface-type interface-number ] undo debugging atm oam [ interface interface-type interface-number ] Default Debugging for ATM OAM is disabled.
Use undo debugging atm packet to disable debugging for ATM packets. Syntax debugging atm packet [ interface interface-type interface-number [ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] undo debugging atm packet [ interface interface-type interface-number [ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] Default Debugging for ATM packets is disabled. Views User view Default command level 1: Monitor level Parameters interface-type interface-number: Specifies an interface by its type and number.
Examples # Enable debugging for ATM packets on all ATM interfaces. debugging atm packet …… *0.263288 Sysname ATM/7/debug8: Atm5/0 pvc 10/33 out ip pkt, snap, 92 *0.263288 Sysname ATM/7/debug8: AA AA 03 00 00 00 08 00 45 00 00 54 00 05 00 00 *0.263288 Sysname ATM/7/debug8: FF 01 F1 9E 64 01 01 01 64 01 01 02 08 00 53 9D // ATM sent an IP packet through PVC 10/33 on ATM 5/0 interface. The packet is 92 bytes in length, with the encapsulation type SNAP.
Attack detection and protection debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging attack-defense Use debugging attack-defense to enable attack detection and protection debugging. Use undo debugging attack-defense to disable attack detection and protection debugging.
Table 52 Output from the debugging attack-defense event command Field Description Information about the detected attack: • Attack type—The attack type, Scan, UDP Flood, ICMP Flood, or SYN Flood. Attack begin. • Interface—Interface where attack protection is configured. • Action—Action against the attack. Available action parameters Attack type: type are: Interface: interface-type interface-number none—Takes no actions but outputs the attack alarm logs.
Examples # Enable attack protection error debugging. Output similar to the following example is generated when the device detects a scanning attack sourced from 1.1.1.1 under the following conditions: 1. A scanning attack protection policy is configured on the device. 2. A blacklist entry is manually added for the IP address 1.1.1.1. debugging attack-defense error *Apr 10 21:07:53:78 2008 Sysname ATTACK/7/Attack-defend Error: Failed to add 1.1.1.1 to blacklist for already existing.
debugging blacklist Use debugging blacklist to enable blacklist debugging. Use undo debugging blacklist to disable blacklist debugging. Syntax debugging blacklist { all | error | event } undo debugging blacklist { all | error | event } Default No blacklist debugging is enabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of blacklist debugging. error: Specifies blacklist error debugging. event: Specifies blacklist event debugging.
debugging blacklist error *Apr 10 20:47:54:734 2008 Sysname BLS/7/BLS Error: Failed to create new blacklist. // The device failed to add a new entry to the blacklist because the blacklist is full. # Enable blacklist event debugging. Output similar to the following example is generated when the device detects a scanning attack under the following conditions: • A scanning attack protection policy is configured on the device. • The blacklist function is enabled for scanning attack protection.
Table 57 describes output fields and messages for the debugging flow-statistics event command Table 57 Output from the debugging flow-statistics event command Field Description Operation: create source IP statistic node The attack protection module created an IP traffic statistics node. • IP address—Source IP address of the statistics object. • VPN Instance ID—VPN instance to which the traffic IP address: source-ip VPN Instance ID: vpn-instance-id belongs.
Views User view Default command level 1: Monitor level Parameters all: Specifies all types of TCP proxy debugging. dhbk: Specifies TCP proxy stateful failover debugging. error: Specifies TCP proxy error debugging. event: Specifies TCP proxy event debugging. packet: Specifies TCP proxy packet debugging. timer: Specifies TCP proxy timer debugging. Usage guidelines Table 58 describes output fields and messages for the debugging tcp-proxy dhbk command.
Basic IP routing debugging commands The output description tables in this document only contain fields and messages that require an explanation. Enabling any debugging command in this chapter might affect system performance, especially when the system is busy. Therefore, disable the debugging once the debugging operation is complete. debugging rm all Use debugging rm all to enable all route management (RM) debugging. Use undo debugging rm all to disable all RM debugging.
Usage guidelines Table 59 describes output fields and messages for the debugging rm backup command. Table 59 Output from the debugging rm backup command Field Description Module XXX Module name. backup data(XXX) Backup data size in bytes. routine backup Scheduled backup. realtime backup Realtime backup. batch backup Batch backup. Examples # Enable RM data backup debugging.
Table 60 Output from the debugging rm bfd command Field Description InstanceID Instance ID. MsgType Message type. ConnectType Session type. IntfIdx Interface index. AppProto Protocol type. SrcIPAddr Source IP address of the BFD session. DstIPAddr Destination IP address of the BFD session. Examples # Enable RM BFD debugging.
rr: Specifies IPv4 recursive route debugging. rtmsg: Specifies IPv4 routing table message debugging. urt: Specifies IPv4 routing table debugging. usr: Specifies IPv4 unicast static route debugging. Usage guidelines Table 61 describes output fields and messages for the debugging rm ipv4 im command. Table 61 Output from the debugging rm ipv4 im command Field Description IfnetIdx Interface index. IfState Interface state. Slot Slot number. IfName Interface name. IfType Interface type.
Field Description for: dest/mask Destination address/mask. ExitIf Index of the outgoing interface. Table 65 describes output fields and messages that for the debugging rm ipv4 urt command. Table 65 Output from the debugging rm ipv4 urt command Field Description Add/Delete route Add/delete a route. Dest Destination address. Mask Mask of the destination address. Nexthop Next hop. Neighbour Neighbor address. Protocol Protocol. TableID Routing table ID of the route.
Syntax debugging rm ipv6 { im | rcom [ ip-prefix prefix-name ] | rr | urt [ ip-prefix prefix-name ] | usr } undo debugging rm ipv6 { im | rcom | rr | urt | usr } Default RM IPv6 route debugging is disabled. Views User view Default command level 1: Monitor level Parameters im: Specifies IPv6 routing interface debugging. rcom: Specifies IPv6 route sending debugging. ip-prefix prefix-name: References an IPv6 prefix list. rr: Specifies IPv6 recursive route debugging.
Field Description deleted from FIB6 Deleted from the FIB table. Table 68 describes output fields and messages for the debugging rm ipv6 urt command. Table 68 Output from the debugging rm ipv6 urt command Field Description RM Route management. addition msg Route addition message. deletion msg Route deletion message. modification msg Route modification message. setflag msg Route flag setting message. resetflag msg Route flag resetting message.
//RM added IPv6 routes.
Table 69 Output from the debugging rm job command Field Description Job name: Job XXX • SelActRt—Optimal route selection job. • NotifyRoute—Route notification job. Examples # Enable RM job debugging. When you configure an IPv4 static route, output similar to the following example is generated: debugging rm job system-view [Sysname] ip route-static 1.1.1.
Field Description route-map ' XXX' Routing policy XXX. Examples # Display routing policy debugging information matching IP prefix list test. debugging rm policy ip-prefix test [Sysname] ip as-path 10 permit test *Aug 26 15:01:01:64 2006 Sysname RM/3/RMDEBUG: Aspath filter created for List ID : 10 // RM created AS path list 10. [Sysname] undo ip as-path 10 *Aug 26 15:01:53:706 2006 Sysname RM/3/RMDEBUG: Aspath filter with list ID :10 is deleted // RM deleted AS path list 10.
Prefix filter6 'test' deleted with seq-no 10 // RM deleted IPv6 prefix list test. [Sysname] route-policy test permit node 10 *Aug 26 15:34:27:460 2006 Sysname RM/3/RMDEBUG: route-map 'test' created successfully // RM created Routing policy test with node 11. [Sysname] route-policy test permit node 11 *Aug 26 15:35:29:396 2006 Sysname RM/3/RMDEBUG: route-map 'test' new sequence number 11 added! // RM added Node 11 to routing policy test.
ReDistribute policy6 deleted successfully // RM deleted routing policy test for IPv6 static route redistribution. debugging rm system Use debugging rm system to enable RM system debugging. Use undo debugging rm system to disable RM system debugging. Syntax debugging rm system undo debugging rm system Default RM system debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 71 describes output fields and messages for the debugging rm system command.
Syntax debugging rm task undo debugging rm task Default RM task debugging is disabled. Views User view Default command level 1: Monitor level debugging rm timer Use debugging rm timer to enable timer debugging. Use undo debugging rm timer to disable timer debugging. Syntax debugging rm timer [ timerfilter timer-name ] undo debugging rm timer Default Timer debugging is disabled. Views User view Default command level 1: Monitor level Parameters timerfilter timer-name: Name of a timer to be filtered.
Examples # Enable timer debugging. The output in this example was created when IPv4 static routes are configured. debugging rm timer *Aug 26 14:25:38:478 2006 Sysname RM/3/RMDEBUG:WaitQ timer created *Aug 26 14:25:38:478 2006 Sysname RM/3/RMDEBUG:GotQ timer created // RM created WaitQ and GotQ timers. *Aug 26 14:25:38:478 2006 Sysname RM/3/RMDEBUG:Timer WaitQ expires, begin processing. *Aug 26 14:25:43:478 2006 Sysname RM/3/RMDEBUG:Timer GotQ expires, begin processing.
Basic MPLS debugging commands The output description tables in this document only contain fields and messages that require an explanation. Some information in this chapter is device type specific. Devices in this chapter are categorized depending on their IRF capability and support for interface cards that use independent processors for forwarding traffic, as shown in Table 1.
Table 74 Output from the debugging mpls fast forwarding command Field Description MPLS fast switching : IP Packet for swap 3 label bottom of stack ! The packet is an IP packet after label 3 was popped off. MPLS fast switching : L2VPN Packet ! The packet forwarded is an L2VPN packet. Examples # Configure MPLS L3VPN basic capability. Enable debugging for MPLS fast forwarding on a P device.
Parameters advertisement: Specifies debugging for advertisement events. all: Specifies debugging for all events. error: Specifies debugging for error events. main: Specifies debugging for main interface events related to the external modules. notification: Specifies debugging for notification events. pdu: Specifies debugging for PDU events. session: Specifies debugging for session events. socket: Specifies debugging for socket events. timer: Specifies debugging for timer events.
Examples The output in the following examples was created under the following conditions: • Two routers are connected directly. • MPLS and MPLS LDP are configured on both routers. An LDP session has been successfully established between the routers. # Enable debugging for MPLS LDP advertisement on one router (PE 1, in this example). Restart LDP on the other router. Output similar to the following example is generated: debugging mpls ldp advertisement *0.
Start to process Route add (FEC: 140.2.2.2/0xffffffff, OutIf: Serial0/2/0 Nexthop: 140.12.1.2) // LDP was processing route addition event. *0.16868001 PE1 LDP/8/Advertisement: Serial0/2/0 Receive Label Mapping Message from Peer(140.2.2.2:0) for FEC: 140.2.2.2/0xffffffff // LDP received a label mapping message. *0.16868001 PE1 LDP/8/Advertisement: Create FEC Radix Tree Node, Destination: 140.2.2.2, Mask: 0xffffffff *0.16868001 PE1 LDP/8/Advertisement: Create cross node for FEC: 140.2.2.2, Mask: 0xffffffff.
*0.19201475 PE1 LDP/8/Session: Session(140.3.3.3) received keep alive message on Operational state. // LDP received a keepalive message. *0.19202353 PE1 LDP/8/Session: Serial0/2/0 Link Hello message received on interface: Serial0/2/0 // LDP received a hello message. *0.19202695 PE1 LDP/8/Session: Sent keep alive message to LSR: 140.3.3.3. // LDP sent a keepalive message. #Dec 22 15:32:40:498 2005 PE1 LDP/5/SessionDown: Session(140.2.2.2:0.
// LDP received an initialization message. *0.19215421 PE1 LDP/8/Session: Session Init message sent to LSR: 140.2.2.2 // LDP sent an initialization message. *0.19215421 PE1 LDP/8/Session: Serial0/2/0 Sent keep alive message to LSR: 140.2.2.2. // LDP sent a keepalive message. *0.19215421 PE1 LDP/8/Session: Serial0/2/0 Session(140.2.2.2)'s state changed from Initialized to Open received. // The session's status changed to Open received. #Dec 22 15:32:43:437 2005 PE1 LDP/5/SessionUp: Session(140.2.2.2:0.
04 01 00 04 8c 01 01 01 04 02 00 04 00 00 00 00 The message type: Hello Message. // LDP sent a hello message. *0.19807692 PE1 LDP/8/PDU: Receive UDP Message from Peer: 140.2.2.2. Message content: 01 00 00 1c 00 00 2a 05 04 00 00 04 00 0f 00 00 04 01 00 04 8c 02 02 02 04 02 00 04 00 00 00 00 The message type: Hello Message. // LDP received a hello message from 140.2.2.2. *0.19810159 PE1 LDP/8/PDU: Received an LDP PDU from LSR: 140.2.2.2 *0.
undo debugging mpls lfib [ code | sync ] Default Debugging for MPLS entry synchronization and encoding/decoding is disabled. Views User view Default command level 1: Monitor level Parameters code: Specifies debugging for MPLS entry encoding and decoding. sync: Specifies debugging for MPLS entry synchronization. Usage guidelines CAUTION: Do not enable debugging for MPLS entry encoding and decoding when a large number of entries are to be sent.
Table 78 Output from the debugging mpls lfib command Field Description MFW-BFD Interaction between the MFW module and the BFD module. Begin Process Begun creating/canceling BFD sessions. End Process Stopped creating/canceling BFD sessions. BFD MSG BFD message type. SESS BFD session information: source address, destination address, and egress interface.
// MPLS decoded the entry: the ID is 12, operation type is 25, and number of valid bytes is 12. *Oct 9 09:44:54:384 2006 PE1 MFW/7/MPLSFW PACKET:Slot=1; End decoding... // Decoding ended. # On the router, enable debugging for MPLS entry synchronization. debugging mpls lfib sync … [PE1-Vlan-interface23] *Oct 9 09:44:29:194 2006 PE1 MFW/7/MPLSFW PACKET: Send entry, count: 2, time cost: 33640 // MPLS sent two entries in 33640 milliseconds.
slot slot-number: Specifies debugging for an IRF member device. The slot-number argument specifies the ID of an IRF member device. (Centralized IRF devices.) drv: Specifies debugging for distribution to driver. chassis chassis-number slot slot-number: Specifies debugging for a card on an IRF member device. The chassis-number argument specifies the ID of the IRF member device. The slot-number argument specifies the number of the slot that holds the card. (Distributed IRF devices.
Examples As shown in Figure 1, PE 1 and PE 2 are directly connected. PE 2 is connected to PE 3 through P 1 and P 2. Two equal-cost Martini VCs are established between PE 2 and PE 3. One VC is through P 1 and the other through P 2. Figure 1 Network diagram for equal cost LSPs P1 PE 1 PE 2 PE 3 P2 # On PE 2, enable debugging for MFW entry distribution to the driver.
In VCLabel is 98350 TunnelId is 0xab0003 EncapType is 0 VlanID is 4 DrvContext is 50266404, 4294901764 // The first equal-cost VC entry was deleted. *Apr 19 15:59:59:888 2008 PE2 MFW/7/MPLSFW PACKET:Slot=3; MFW-VLL: The content of VLL DelInfo to Drv is: In IfIndex is 0x190006d In VCLabel is 98350 TunnelId is 0xab0004 EncapType is 0 VlanID is 4 DrvContext is 0, 0 // The second equal-cost VC entry was deleted. *Apr 19 16:00:00:178 2008 PE2 MFW/7/MPLSFW PACKET:Slot=3; MFW-DRV: Modify VLL VC equal entry.
INFO : The content of send entry to Drv is: AccessType is 0 Transtype is 4 CtrlWord is 0 Mtu is 1500 InIfIndex is 0x190006d InVcLabel is 98350 OutVCLabel is 98331 RmtVTag is 4 LspTnlId is 11206660 CEType is 0 VlanID is 4 OutIfIndex is 0x1900063 OutAtIndex is 0 SlotNumber is 3 LabelStackDepth is : 1 , label is :1083 TnlNextHop is 20.20.20.
Default Debugging for the LSP control module is disabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of debugging. error: Specifies error debugging. event: Specifies event debugging. packet: Specifies packet debugging. Usage guidelines Table 80 describes the output fields and messages for the debugging mpls lspc command. Table 80 Output from the debugging mpls lspc command Field Description DS TLV is invalid. The downstream mapping TLV was invalid.
*Nov 29 17:01:54:549 2006 Sysname LSPC/7/Packet: Send echo reply message on egress. Lenth: 100 00 01 00 00 02 02 03 01 00 00 00 01 00 00 00 01 00 1d 4c c6 00 00 02 a5 00 1e 39 fc 00 00 01 15 00 01 00 0c 00 01 00 05 30 30 30 30 20 00 00 00 00 03 00 30 02 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 // LSP control received an echo reply message on the egress. The packet is 100bytes long.
Table 81 describes output fields and messages for the debugging mpls management interface command. Table 81 Output from the debugging mpls management interface command Field Description Received Signal XX message LSPM received a message from the signaling module, such as a signaling DELETE or signaling CREATE message. OutIfIndex Outgoing interface index. InIfIndex Incoming interface index. Received Route XX message LSPM received a message from the routing module, such as a CREATE or DELETE message.
Examples The output in the following examples was created under the following conditions: • Two routers are connected directly. • MPLS and MPLS LDP are configured on both routers. An LDP session has been successfully established between the routers. # Enable debugging for MPLS management interface on one router (PE 1, in this example). When MPLS LDP is reset on the other router, output similar to the following example is generated: debugging mpls management interface *0.
// LSPM deleted an LSP. *0.92036640 PE1 LSPM/8/LSPM POLICY: Route Doesnot Satisfy Policy!. Sig Prot is informed. // The route did not satisfy the policy. LSPM notified the signaling module. *0.92036640 PE1 LSPM/8/LSPM POLICY: Calling Signalling protocol for VRF:0 Dst Addr:0x8c030303 Dst Mask:0xffffffff NextHop: 0x8c0c0102 If Index: 0x300010 Event: 13 // LSPM called the signaling protocol. *0.92036640 PE1 LSPM/8/LSPM POLICY: Route Doesnot Satisfy Policy!. Sig Prot is informed.
#Dec 22 17:05:57:766 2005 PE1 LDP/5/SessionDown: Session(140.2.2.2:0. public Instance)'s state change to Down // The peer restarted and the session went down. *0.25271766 PE1 LSPM/8/LSPM PROCESS: Rcv delete lsp msg from signaling protocol 0x8c010101/0xffffffff ! // LSPM received a delete LSP message from the signaling protocol. *0.25271766 PE1 LSPM/8/LSPM PROCESS: Rcv delete lsp msg from signaling protocol 0x8c020202/0xffffffff ! // LSPM received a delete LSP message from the signaling protocol. *0.
*0.25271860 PE1 LSPM/8/LSPM PROCESS: Setting MTU = LSP MTU *0.25271860 PE1 LSPM/8/LSPM PROCESS: Succeeded in sending forwarding message to MFW. *0.25271860 PE1 LSPM/8/LSPM PROCESS: Notify to TNLM SUCCESS. Event: 2, LspIndex: 9267, 0x8c030303/0x20/token557248. *0.25271860 PE1 LSPM/8/LSPM PROCESS: Free Token success: 557248 // LSPM freed the token successfully. #Dec 22 17:05:59:280 2005 PE1 LDP/5/SessionUp: Session(140.2.2.2:0. public Instance)'s state change to Up // The session came up again. *0.
Received Signaling message. *0.25275812 PE1 LSPM/8/LSPM PROCESS: Received Signal CREATE message, VRF Index: 0 destination: 0x8c010101 destination mask: 0xffffffff Nexthop: 0x7f000001 OutIfIndex: 0x150000 InIfIndex: 0x300010 *0.25275812 PE1 LSPM/8/LSPM PROCESS: Setting MTU = LSP MTU *0.25275812 PE1 LSPM/8/LSPM PROCESS: Error: No LSP found for the route. *0.25275812 PE1 LSPM/8/LSPM PROCESS: Added LSP in LM Successfully *0.25275812 PE1 LSPM/8/LSPM PROCESS: Succeeded in sending forwarding message to MFW.
debugging mpls packet Use debugging mpls packet to enable debugging for MPLS packet forwarding. Use undo debugging mpls packet to disable debugging for MPLS packet forwarding. Syntax debugging mpls packet [ acl acl-number ] [ error ] [ inlabel outer-in-label [ inner-in-label ] ] [ l2vpn-in-interface interface-type interface-number ] undo debugging mpls packet Default Debugging for MPLS packet forwarding is disabled.
Table 86 Output from the debugging mpls packet command (on multi-core devices) Field Description L2VPN Input L2VPN packet forwarding from PE to PE. L2VPN Output Sent L2VPN packets from PE to CE. CCC L2VPN local CCC packets. REMOTE L2VPN remote CCC packets. VCLabel L2VPN VC label. PktLen Packet length. Label(s) Labels, including the inner label (private network) and outer label (public network).
MPLSFW_Input: Receiving from Vlan3, PktLen=88, Label(s)=1024, EXP=0, TTL=254 POP Label=1024, EXP=0, TTL=254 Delivering up to IP! // MPLS received a packet with the length 88 and label 1024 from VLAN3, popped label 1024, and forwarded the packet as an IP packet. *0.3824779 F-RT1 MFW/8/MPLSFW PACKET:Slot=2; PKTTYPE_IP :Sending to Slot 6, Dest=15.40.1.1, InnerLabel=1024, Vpn=1, Token=9371650 // MPLS sent the interface a packet with the destination address 15.40.1.1 and inner label 1024. *0.
MPLS Output: Sending the packet to GE0/1, PktLen = 92, Label(s) = 1071,1024, EXP = 0, TTL = 255! // MPLS received an MPLS packet with the length 92, outer label 1071, inner label 1024, EXP 0, and TTL 255 from interface GigabitEthernet 0/1. debugging tnlm Use debugging tnlm to enable debugging for tunnel management. Use undo debugging tnlm to disable debugging for tunnel management.
BFD debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging bfd all Use debugging bfd all to enable all BFD debugging. Use undo debugging bfd all to disable all BFD debugging. Syntax debugging bfd all undo debugging bfd all Default All BFD debugging is disabled.
debugging bfd all *0.6557078 Sysname BFD/8/PKT_RCV: Chassis=1-Slot=1;Src:192.168.12.10, Dst:192.168.12.1 1,Ver:1,Diag:0,Sta:1,P/F/C/A/D/R:0/0/1/0/0/0,multi:6,LD/RD:4/0,Tx:100ms, Rx:100ms *0.6557078 Sysname BFD/8/PKT_RCV: Chassis=1-Slot=1;Transfer MBuf to master board // The interface card (Slot 1) received the Init message from the peer and sent the message to the active MPU. *0.6557078 Sysname BFD/8/FSM:Sess[192.168.12.11/192.168.12.
*0.6557156 Sysname BFD/8/SCM: Chassis=1-Slot=1;The bfd-int of the session doesn't exist, create bfd-if *0.6557156 Sysname BFD/8/SCM: Chassis=1-Slot=1;Bfd-int[Ethernet1/1], Oper: create *0.6557156 Sysname BFD/8/SCM: Chassis=1-Slot=1;Create session entry *0.6557156 Sysname BFD/8/SCM: Chassis=1-Slot=1;Add session to bfd interface *0.6557156 Sysname BFD/8/SCM: Chassis=1-Slot=1;Add session to IP hash table // The interface card (Slot 1) created the session. *0.
Field Description Send Msg failed to BFD VCPU,ret (return value),msgtype (msgtype),sess (session index) The control VCPU failed to send messages to the BFD VCPU. Receive Msg on Ctrl VCPU,msgtype (msgtype),para1 (para1) The control VCPU received messages on the control VCPU. Cannot find session on BFD VCPU,msgtype (msgtype), sessindex (session index) No corresponding session exists on the BFD VCPU.
// BFD notified the driver on interface card No. 5 to add a BFD session with the following session information: source address 100.1.2.2, destination address 100.1.2.1, VLAN-interface 2, control packet mode, and local discriminator 103. *Mar 22 18:38:20:305 2007 Sysname BFD/7/DRV: Chassis=1-Slot=3;Notify driver to add bfd session [100.1.2.2/100.1.2.1,Vlan2,Ctrl], Discr: 103 // BFD notified the driver on interface card No. 3 to add a BFD session with the following session information: source address 100.1.
*Apr 28 06:34:08:941 2008 Sysname BFD/7/DRV:Received BFD session first-detect-start message from driver, sess[12.1.1.61/12.1.1.88,GE0/2,Ctrl] *Apr 28 06:34:08:942 2000 6602 BFD/7/DRV:Notify driver session [12.1.1.61/12.1.1.88,GE0/2,Ctrl] start, Discr: 121 *Apr 28 06:34:08:942 2008 Sysname DPBFD/7/debug:Send Msg to BFD VCPU,msgtype 0xcf2000a,sess 120 // Sending a message to the BFD VCPU. The message type is 0xcf2000a (indicating that the first packet detection succeeded), and the session index is 120.
[Sysname] bfd min-receive-interval 500 *0.6557156 Sysname BFD/8/ERR: Failed to create interface: ethernet1/1 // BFD failed to create the interface. debugging bfd event Use debugging bfd event to enable BFD event debugging. Use undo debugging bfd event to disable BFD event debugging. Syntax debugging bfd event undo debugging bfd event Default BFD event debugging is disabled.
Field Description Process sync sess: Failed to create session The newly inserted interface card failed to create the session after receiving the IPC message with session structure from the active MPU. (session index) When the newly inserted interface card used the IPC message with session structure received from the active MPU to create the session, an error occurred due to the existence of the session.
Usage guidelines Table 90 describes output fields and messages for the debugging bfd fsm command. Table 90 Output from the debugging bfd fsm command Field Description Pkt Sta: AdminDown, Sess Sta: AdminDown, Oper: none The incoming AdminDown packet was not processed when the session state was AdminDown. Pkt Sta: Down, Sess Sta: AdminDown, Oper: None The incoming down packet was not processed when the session state was AdminDown.
debugging bfd ha Use debugging bfd ha to enable BFD HA event debugging. Use undo debugging bfd ha to disable BFD HA event debugging. Syntax debugging bfd ha undo debugging bfd ha Default BFD HA event debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines This command applies only to distributed devices. Examples # Enable BFD HA event debugging on a BFD-capable device.
Default BFD IPC event debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines This command applies only to distributed devices. Table 91 describes output fields and messages for the debugging bfd ipc command. Table 91 Output from the debugging bfd ipc command Field Description [SND] Sess (session information), MAIN->IO, Mode: Unicast.
Field Description [SND] Interface[interface name], MAIN->IO, Mode: Multicast, Oper: Synchronize Detecting Multiplier BFD synchronized the configured detecting multiplier to all the cards. [SND] Interface[interface name], MAIN->IO, Mode: Multicast, Oper: Synchronize Auth Info BFD synchronized the configured authentication information to all the cards. [SND] MAIN->IO, Mode: Multicast, Oper: Synchronize Debugging Switch(debugging flag) BFD synchronized the debugging switch information to all the cards.
Board state changes to NORMAL in Frame 0 Chassis 1 Slot 1, type is Wvrp board. System is busy with VIU configuration recovery, please wait a moment... *Dec 31 16:31:05:336 2006 Sysname BFD/7/IPC:[SND] MAIN->IO, Mode: Unicast, Oper: Synchronize Debugging Switch 32, Dst chassis/slot: 1/1 *Dec 31 16:31:05:360 2006 Sysname BFD/7/IPC: Chassis=1-Slot=0;[RCV] Oper: Interface Download //After a new interface card was inserted, BFD information was synchronized to the interface card through IPC.
terminal debugging terminal monitor *Jan 4 09:26:07:674 2009 Sysname BFD/7/PKT_RCV: Ctrl packet, Src:2001::1, Dst:2001::2, Ver:1, Diag:0, Sta:3, P/F/C/A/D/R:0/0/1/0/0/0, multi:5, LD/RD:1/1, Tx:400ms, Rx:400ms // BFD received a control packet. debugging bfd scm Use debugging bfd scm to enable BFD session control management debugging. Use undo debugging bfd scm to disable BFD session control management debugging.
*Jan 4 09:30:09:642 2007 Sysname BFD/7/SCM:Interface of the session doesn't exist, create it *Jan 4 09:30:09:642 2007 Sysname BFD/7/SCM:Bfd-int[Dialer0], Oper: Create *Jan 4 09:30:09:658 2007 Sysname BFD/7/SCM:Create session entry *Jan 4 09:30:09:658 2007 Sysname BFD/7/SCM:Allocate global resource to a session *Jan 4 09:30:09:658 2007 Sysname BFD/7/SCM:Add session to bfd interface *Jan 4 09:30:09:658 2007 Sysname BFD/7/SCM:Add session to IP hash table *Jan 4 09:30:09:658 2007 Sysname BFD/7/SCM:Se
*Jan 4 09:34:24:54 2007 Sysname BFD/7/TMR:Create send-packet timer *Jan 4 09:34:24:54 2007 Sysname BFD/7/TMR:Send-packet timer[1000ms] of session[10.1.1.1/10.1.1.2,Eth1/1,Ctrl] is created %Jan 4 09:34:24:66 2007 Sysname BFD/4/LOG: Sess [10.1.1.1/10.1.1.2, Eth1/1, Ctrl], Sta: DOWN->UP, Diag: 0 *Jan 4 09:34:24:66 2007 Sysname BFD/7/TMR:Reset send-packet timer *Jan 4 09:34:24:66 2007 Sysname BFD/7/TMR:Send-packet timer[400ms] of session[10.1.1.1/10.1.1.
BGP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging bgp Use debugging bgp to enable debugging for specific BGP message types. Use undo debugging bgp to disable debugging for specific BGP message types.
Table 93 Output from the debugging bgp command Field Description Recv Received packets. Send Sent packets. Length: LengthNumber Packet length. Table 94 describes output fields and messages for the debugging bgp open command. Table 94 Output from the debugging bgp open command Field Description Version: X BGP protocol version. Local AS: X Local AS number. OPT Type: 2 (Capability) Capability negotiation. CAP Type: 1 (Multiprotocol) CAP Len: 4 Multiprotocol capability: afi: 1; safi: 1.
Examples # Enable debugging for all BGP messages. When a BGP peer relationship is being established, output similar to the following example is generated: debugging bgp system-view [Sysname] bgp 100 [Sysname-bgp] undo synchronization [Sysname-bgp] peer 11.1.1.2 group 200 *0.2683484 4945 RM/6/RMDEBUG: BGP.: 11.1.1.2 Send OPEN, Version: 4 Local AS: 100, HoldTime: 180, Router ID: 192.168.74.
111.1.1.1/32, // Information about the sent BGP update of a redistributed static route was displayed. *0.2728250 4945 RM/6/RMDEBUG: BGP.: Recv UPDATE from 11.1.1.2 with following destinations : Update message length : 53 MED : 0 Origin : Incomplete AS Path : 200 Next Hop : 11.1.1.2 222.1.1.1/32 // Information about the received BGP Update of a redistributed static route was displayed.
Parameters ipv4-address: Specifies the IPv4 address of a peer. ipv6-address: Specifies the IPv6 address of a peer. Usage guidelines This command enables all BGP debugging, which might cause heavy traffic and decrease system performance. Therefore, use this command only when necessary. Disable debugging after the debugging operation is complete. Examples # Display BGP configuration on Device A and Device B. [Sysname-bgp]display this # bgp 100 undo synchronization peer 10.1.1.
Total CAPB Len : 8 Total OPT Len : 10 Total Message Len : 39 *Aug 24 15:32:02:630 2006 Sysname RM/6/RMDEBUG: BGP.: 10.1.1.2 State is changed from ACTIVE to OPENSENT. // After the connection is established, BGP sent an OPEN message to the peer. *Aug 24 15:32:02:630 2006 Sysname RM/6/RMDEBUG: BGP.: 10.1.1.2 Recv OPEN Length: 39 Version: 4, Local AS: 100, HoldTime : 180, BGP ID: 10.1.1.
undo debugging bgp bfd [ [ vpn-instance vpn-instance-name ] { ipv4-address | ipv6-address } ] Default BGP BFD debugging is disabled. Views User view Default command level 1: Monitor level Parameters vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If no VPN instance is specified, BGP BFD debugging is enabled for the public network. Support for this option depends on the device model.
Field Description BGP_BFD: BGP session dst-ip not configure bfd when recv BFD DOWN msg. A DOWN BFD session message was received, but BFD was not enabled for the BGP session with destination address dst-ip. Table 97 describes output fields and messages for the debugging bgp bfd command for IPv6 environment. Table 97 Output from the debugging bgp bfd command (for IPv6 environment) Field Description The XXX can be one of the following: • CREATE. • DELETE. • Disable.
Syntax debugging bgp detail undo debugging bgp detail Default Detailed debugging for BGP is disabled. Views User view Default command level 1: Monitor level Usage guidelines Enabling debugging might decrease system performance. Therefore, use this command only when necessary. Disable debugging after the debugging operation is complete. Table 98 describes output fields and messages for the debugging bgp detail command. Table 98 Output from the debugging bgp detail command Field Description BGP.
*Aug 24 14:12:13:674 2006 Sysname RM/6/RMDEBUG: BGP_L3VPN: Recv UPDATE with following RD 100:1 destination 11.1.1.1 - Received New VPNv4 Route with Ext-Community NULL..Ignoring Route // BGP received an Update message with RD 100:1 and destination address 11.1.1.1. The Ext-Community of the new VPNv4 route is NULL. Therefore, the route was ignored. DeLocRemCross: Deleting route From Target Instance. // The route was deleted from the instance.
*Aug 24 14:12:13:674 2006 Sysname RM/6/RMDEBUG: BGP.: 10.1.1.2 State is changed from ACTIVE to CONNECT. *Aug 24 14:12:14:690 2006 Sysname RM/6/RMDEBUG: BGP.: 10.1.1.2 State is changed from CONNECT to ACTIVE. *Aug 24 14:12:13:706 2006 Sysname RM/6/RMDEBUG: BGP.: 10.1.1.2 State is changed from ACTIVE to OPENSENT. *Aug 24 14:12:13:706 2006 Sysname RM/6/RMDEBUG: BGP.: 10.1.1.2 Current event is ReceiveOpenMessage. // BGP received an Open message. *Aug 24 14:12:13:706 2006 Sysname RM/6/RMDEBUG: BGP.: 10.1.1.
IP address. If a fault occurs to the GR operation of BGP, you can display the debugging information for fault location. Enabling debugging might decrease system performance. Therefore, use this command only when necessary, and disable debugging after the debugging operation is complete. Examples # Enable BGP GR event debugging on the BGP GR helper.
*0.92311078 Sysname RM/6/RMDEBUG: BGP NSR: Prifex 1.1.1.1 Mask 32 is found in the synchronization message. *0.92311078 Sysname RM/6/RMDEBUG: BGP NSR: Batch backup of NSR data starts. *0.92311078 Sysname RM/6/RMDEBUG: BGP NSR: Batch backup of Neighbor routes received from neighbors starts. *0.92311078 Sysname RM/6/RMDEBUG: BGP NSR: Batch backup of Neighbor routes is complete. *0.92311078 Sysname RM/6/RMDEBUG: BGP NSR: Packet with length 50 is expected from socket 1, but the received packet length is 50. *0.
Usage guidelines Enabling debugging might decrease system performance. Therefore, use this command only when necessary, and disable debugging after the debugging operation is complete. Table 100 describes output fields and messages for the debugging bgp timer command. Table 100 Output from the debugging bgp timer command Field Description CR Timer Connection retry timer. HOLD Timer Hold timer. Examples # Enable BGP timer debugging on the device.
Parameters acl acl-number: Specifies an ACL in the range of 2000 to 3999 for filtering packet debugging information. ip-prefix ip-prefix-name: Specifies an IP prefix list for filtering the packet debugging information. ip-prefix-name is a string of 1 to 19 characters. receive: Enables the debugging for received BGP packets. send: Enables the debugging for sent BGP packets. verbose: Displays detailed debugging information. Usage guidelines Enabling debugging might decrease system performance.
Views User view Default command level 1: Monitor level Parameters peer { ipv4-address | ipv4-group-name }: Specifies BGP IPv4 update debugging for the specified IPv4 peer/peer group. ip-prefix ip-prefix-name: Filters the output message debugging information with the specified IP prefix list. receive: Specifies debugging for received BGP updates. send: Specifies debugging for sent BGP updates. verbose: Displays detailed debugging information.
*Sep 4 16:08:37:272 2006 Sysname RM/6/RMDEBUG: BGP.: Recv UPDATE from 11.1.1.2 with following destinations : Update message length : 56 Local Pref : 100 MED : 0 Origin : Incomplete AS Path : Next Hop : 11.1.1.2 2.2.2.2/32, *Sep 4 16:08:37:304 2006 Sysname RM/6/RMDEBUG: BGP.: Recv UPDATE from 11.1.1.2 with following destinations : Update message length : 55 Local Pref : 100 MED : 0 Origin : Incomplete AS Path : Next Hop : 11.1.1.2 11.1.1.
Default command level 1: Monitor level Parameters peer { ipv6-address | ipv6-group-name }: Specifies BGP IPv6 update debugging for the specified IPv6 peer/peer group. ipv6-prefix ipv6-prefix-name: Filters the output message debugging information with the specified IP prefix list. receive: Specifies debugging for received BGP packets. send: Specifies debugging for sent BGP packets. verbose: Displays detailed debugging information. Usage guidelines Enabling debugging might decrease system performance.
Origin : Incomplete AS Path : Next Hop : 100::2 22::22/128, *Sep 4 16:17:20:708 2006 Sysname RM/6/RMDEBUG: BGP_IPV6.: Recv UPDATE from peer 100::2 with following destinations : Update message length : 78 Local Pref : 100 MED : 0 Origin : Incomplete AS Path : Next Hop : 100::2 100::/64, // Update messages of IPv6 address family were displayed.
Usage guidelines See the previous command for the description of the Update message information. debugging bgp update l2vpn Use debugging bgp update l2vpn to enable debugging for BGP L2VPN Update messages. Use undo debugging bgp update l2vpn to disable debugging for BGP L2VPN Update messages.
Route Distinguisher:100:1 CE-ID:1 label offset:0 label base:20480 *0.92566 Sysname RM/7/RMDEBUG: BGP.L2VPN: Recv UPDATE from 1.1.1.1 with following destinations : Update message length : 88 Origin : IGP AS Path : 100 Next Hop : 1.1.1.1 afi = 196(l2vpn) safi = 128(l2vpn) Route Distinguisher:100:1 CE-ID:0 label offset:0 label base:8192 // Update messages in an L2VPN environment were displayed.
verbose: Displays detailed debugging information. Usage guidelines Enabling debugging might decrease system performance. Therefore, use this command only when necessary, and disable debugging after the debugging operation is complete. Examples The output in the following example is created when the following conditions exist: • Device A and Device B have established a BGP peer relationship. • MPLS has been enabled on the connected interfaces.
Local Pref : 100 MED : 0 Origin : Incomplete AS Path : Next Hop : 100::2 22::22/128(1027) // Update message information for IPv6 labeled routes were displayed. debugging bgp update mdt Use debugging bgp update mdt to enable debugging for BGP MDT Update messages. Use undo debugging bgp update mdt to disable debugging for BGP MDT Update messages.
Field Description Send UPDATE(Withdraw) to peer x.x.x.x A route update (withdraw) message was sent to BGP neighbor x.x.x.x. Source x.x.x.x Source address of multicast VPN in the Update message. ShareGrp x.x.x.x Share-Group of multicast VPN in the Update message. Examples # Device A and Device B have established a BGP peer relationship in MDT instance. Enable debugging for BGP MDT messages on either device.
undo debugging bgp update peer { ipv4-address | group-name } [ receive | send ] [ verbose ] Default BGP Update message debugging for the specified peer/peer group is disabled. Views User view Default command level 1: Monitor level Parameters ipv4-address: Specifies the IPv4 peer address. group-name: Specifies the peer group name. acl acl-number: Filters the output message debugging information with the specified ACL.
receive: Specifies the debugging for the received BGP packets. send: Specifies the debugging for the sent BGP packets. verbose: Displays detailed debugging information. Usage guidelines Enabling debugging might decrease system performance. Therefore, use this command only when necessary, and disable debugging after the debugging operation is complete. Table 104 describes output fields and messages for the debugging bgp update vpls command.
Use the undo debugging bgp update instance command to disable BGP Update message debugging for a VPN instance. Syntax debugging bgp update vpn-instance vpn-instance-name [ ip-prefix ip-prefix-name | peer { ipv4-address | group-name } ] [ receive | send ] [ verbose ] undo debugging bgp update vpn-instance vpn-instance-name [ ip-prefix ip-prefix-name | peer { ipv4-address | group-name } ] [ receive | send ] [ verbose ] Default BGP Update message debugging for a VPN instance is disabled.
Default command level 1: Monitor level Parameters peer { ipv4-address | group-name }: Specifies BGP Update message debugging for the specified peer/peer group. receive: Specifies the debugging for the received BGP VPNv4 packets. send: Specifies the debugging for the sent BGP VPNv4 packets. verbose: Displays detailed debugging information. Usage guidelines Enabling debugging might decrease system performance.
BGP_L3VPN: L3VPN Process IP Address 111.2.2.2 src instance VPNV4 dest instance red LocRemCross:No Import Policy .Route Added To Target Instance // Update message information for VPNv4 was displayed. debugging bgp update vpnv6 Use debugging bgp update vpnv6 to enable debugging for BGP VPNv6 Update messages. Use undo debugging bgp update vpnv6 to disable debugging for BGP VPNv6 Update messages.
Bridging debugging commands The bridging module name is identified as "BRIDGE" in debugging messages. The output description tables in this document only contain fields and messages that require an explanation. debugging bridge error Use debugging bridge error to enable debugging for transparent bridging errors. Use undo debugging bridge error to disable debugging for transparent bridging errors. Syntax debugging bridge error undo debugging bridge error Default Debugging for bridging errors is disabled.
Field Description Static mac-addresses of TB has reached the maximum. The number of static MAC entries had reached the upper limit, and no more static MAC entries can be configured. TB failed to learn address:the source mac address is invalid BRIDGE failed to learn a MAC address, because the MAC address is invalid. Broadcast, multicast, and all-0 MAC addresses are all invalid MAC addresses.
Field Description An error occurred during packet delivery within the specified transparent bridge set. The error is of one of the following types: Send DLSw packet on set failed,error description • • • • • • Null packet. The specified bridge set ID is invalid. The specified bridge set is not enabled. The bridge set contains no DLSw virtual interface. Some interfaces in the bridge set are invalid. Some interfaces in the bridge set are not Ethernet interfaces.
Default command level 1: Monitor level Parameters dlsw: Debugging for DLSw virtual interfaces. interface: Debugging for the specified interface. interface-type interface-number: Specifies an interface by its type and number. Usage guidelines Table 106 describes output fields and messages for the debugging bridge eth-forwarding command. Table 106 Output from the debugging bridge eth-forwarding command Field Description Forward a frame Action for the packet.
// BRIDGE received a ping packet on Ethernet 1/2 and forwarded the ping packet to Ethernet 1/3. *0.63325963 Sysname BRIDGE/7/DEBUGGING: Forward a frame; received from interface Ethernet1/3;and try to send to interface Ethernet1/2, with following frame head : 00 0f e2 00 00 21 00 e0 fc 3a 5f 07 08 00 // BRIDGE received a ping reply packet on Ethernet 1/3 and forwarded the ping replay packet to Ethernet 1/2.
Field Description Interface doesn't belong to any bridge-set. PASS The incoming interface of a packet is not in any bridge set, so the packet does not need to be forwarded through transparent bridging. The packet undergoes other types of forwarding or is passed to the upper application protocols. Broadcast or multicast packet received, intercept and proc PASS The packet to be processed is a broadcast or multicast packet.
Field Description TB Filter: COS has been set This event is printed if the Ethernet frame filter function is configured on the incoming/outgoing interface for transparent bridge forwarding and the packet carries a VLAN tag. TB Filter: Packet has no VLAN tag, ignore COS This event is printed if the Ethernet frame filter function is configured on the incoming/outgoing interface for transparent bridge forwarding and the packet carries no VLAN tag.
// The transparent bridging module found the outgoing interface of the packet, which is Ethernet 1/2, and forwarded the packet. Packet is being handled by TB intercepter. *0.64267110 Sysname BRIDGE/7/EVENT: 00.0f.e2.00.00.21.00.e0.fc.3a.5f.07.08.00.45.00.00.54.00.0a.00.00.ff.01.b7.*0.6426711 0 Sysname BRIDGE/7/EVENT: TB_Receive process,from Ethernet1/2. *0.64267310 Sysname BRIDGE/7/EVENT:frame type:0,protocol type:2048 *0.64267310 Sysname BRIDGE/7/EVENT:Packet is received from interface Ethernet1/2 *0.
Call services debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging voice ss cb Use debugging voice ss cb to enable call backup debugging. Use undo debugging voice ss cb to disable call backup debugging. Syntax debugging voice ss cb { all | error | event | info | timer } undo debugging voice ss cb { all | error | event | info | timer } Default Call backup debugging is disabled.
Table 109 describes output fields and messages for the debugging voice ss cb event command. Table 109 Output from the debugging voice ss cb event command Field Description Receive CMC_RELEASE message from SA module. A CMC_RELEASE message was received from the SA module. Table 110 describes output fields and messages for the debugging voice ss cb info command.
CB_INFO: [0x00030001] The CMC_RELEASE message's release cause: Wait alerting message timeout // The cause for the RELEASE message was checked. *Nov 14 08:18:11:38 2005 RouterA SS/7/VOICE: CB_TMR: [0x00030000] Timer deleted, Timer ID: TIMER_INLEG_WAIT_ALERTING. // A call was ready to be re-originated, and the INLEG_WAIT_ALERTING timer was restarted. *Nov 14 08:18:11:38 2005 RouterA SS/7/VOICE: CB_INFO: [0x00030000] Send CMC_SETUP message to start a new call.
Field Description The message is null on CFR idle state The input message was null in the CFR idle state. This information is output when the input message is incorrect. The service handle notify is null on CFR idle state The input service handle notify was null in the CFR idle state. This information is output when the input service handle notify is incorrect. The CCB is null on CFR idle state The input CCB was null in the CFR idle state. This information is output when the input CCB is incorrect.
Field Description Received brother leg is wrong on CFO Idle state The type of the received brother leg was incorrect in the call forwarding originator (CFO) idle state. Failed to find VIM index on CFO idle state The CFO failed to find a VIM interface. CF number is same to the local's on CFO idle state The CFO in the idle state found that the forwarded-to number was a local number. This information is output when the forwarded-to number is a local number in different states of the CFO and the CFR.
Field Description The new user information is null in get new number process The user information of a new number was null. Current call number is zero in getting new number process The new number obtained was 0 (no number was available to originate a new call). The original user information is null in setuping new call process Input parameter check for a new call origination: The information of the original forwarded-to user was null.
Field Description Leg's father CCB is null in recording setup's information process The father CCB of the leg was found to be null in the special processing of the SETUP message. Input parameter is null in predicting CF service process The call number was found to be null in predicting the CF service. Dial peer is null in predicting process The dial peer was found to be null in predicting the CF service.
Field Description Send CMC_RELEASE message to CMC module in CFO Idle state The CFO in the idle state sent a CMC_ RELEASE message to the CMC module. Send CMC_RELEASE message to CMC module in CFO wait service ack state The CFO in the waiting-for-service-ack state sent a CMC_ RELEASE message to the CMC module. Send CMC_RELEASE message to CMC module in CF interface process state A CMC_RELEASE message was sent to the CMC module in CF interface processing. Delete CF CCB successfully.
Field Description Failed to find CFU voice entity in CFO idle state The CFO failed to find a voice entity for CFU in the idle state. Find CFU voice entity successfully in CFO idle state. The CFO found a voice entity for CFU in the idle state. Caller number: Calling number and called number: Forwarding number : Go to the unsupported process on CFO idle state The CFO in the idle state went into local processing. Send service CFU successfully, state changed from idle to waiting ack.
Field Description Send CF service to CMC process: The CFO sent a SERVICE message. Address type: Address type: Forwarding number Forwarded-to number: IP addr: IP address: Port: Port: Redirection reason Redirection cause: Redirection count Redirection count: Original direction reason Original redirection cause: Original direction count Original redirection count: Forward number count Forwarded-to number count: Has disconnected the media in CFO unsupported process.
Field Description Create CFO successfully in interface process A CFO module was successfully created in interface processing. Go to the originator idle state in interface process The processing of the CFO's idle state started. Go to the originator wait release state in interface process The processing of the CFR's waiting-for-release state started. Go to the originator wait service ack state in interface process The processing of the CFO's waiting-for-ack state started.
CF_FSM: [0x00690001] CFO state changed from wait release to wait service ack. // The state of the CFO changed from waiting-for-release to waiting-for-service-ack. # Enable debugging for call forwarding information on the router. debug voice ss cf info SS CF information debugging switch is on *May 10 14:54:53:796 2007 RouterB SS/7/VOICE: CF_INFO: [0x00770000] Has register CF service and will process the CF service. // The call forwarding service was processed.
// The processing of the CFO's waiting-for-release state started. *May 10 14:54:53:943 2007 RouterB SS/7/VOICE: CF_INFO: [0x00770000] Caller number: 1000, called number: 5000 in finding voice entity process. // The calling number is 1000, and the forwarded-to number is 5000. *May 10 14:54:54:44 2007 RouterB SS/7/VOICE: CF_INFO: [0xffffffff] Get user information process: Forward ip address is 3.1.1.49, port is 5060 // The forward IP address is 3.1.1.49, and the port number is 5060.
*May 10 14:54:54:799 2007 RouterB SS/7/VOICE: CF_INFO: [0x00770000] CFO service end, return value [0], service flag [2]. // The CF service ended. # Enable debugging for call forwarding timers on the router. debug voice ss cf timer SS CF timer debugging switch is on *May 10 15:38:12:85 2007 RouterB SS/7/VOICE: CF_TMR: [0x00780001] Timer created, Timer ID: TIMER_SS_CF_ORIGINATOR_WAITACK, Timer length: 5000. // A 5000-millisecond timer was created for the CFO to wait for an ACK message.
Table 117 Output from the debugging voice ss ch error command Field Description Received service message xxx in xxx state, return fail message to SA. A SERVICE message was received, and a FAIL message was returned to the SA module. Received error service acknowledge message: XXX in state: XXX. An invalid SERVICE ACK message was received in xxx state. Received error service message XXX in XXX state An invalid SERVICE message was received in xxx state.
Field Description Failed to create XXX timer when enter new call operation. Call hold failed to create the xxx timer in the call setup process. Failed to create XXX timer in XXX state. Call hold failed to create the xxx timer in xxx state. Failed to get call information table, when dial a new number. Call hold failed to obtain the call information table after the forwarded-to number was dialed. Failed to close DTMF, after dial the number in CH.
Field Description Failed to get the hookflash call leg to receive number. No call leg could be found to receive the number. Failed to get the new setup call leg for hookflash handling in XXX state. Call hold failed to obtain a new call leg in handing hookflash. Failed to get the hookflash call leg for hookflash handling in XXX state. No hookflash leg was found in handing hookflash. Failed to switch the hookflash call leg for new call's error handling.
Field Description Failed to find the remote inactive leg in %s state. The remote inactive leg (corresponding to the leg held with the call hold originator) could not be found. Failed to find the remote active leg in %s state. The remote active leg (corresponding to the leg in conversation with the call hold originator) could not be found. Failed to find the leg's talk path in %s state. The talk path of the leg could not be found. Failed to find the remote holding leg in %s state.
Field Description Failed to play busy tone after fail to switch leg in %s state. Call hold failed to play busy tones after failure to switch the leg. Failed to play busy tone when receive time out message in %s state. Call hold failed to play busy tones after a TIMEOUT message was received. Receive wrong type CMC INFOMATION message in %s state. An invalid type of information message was received. Receive wrong service ack message in %s state. An incorrect SERVICE ACK message was received.
Table 119 describes output fields and messages for the debugging voice ss ch fsm command. Table 119 Output from the debugging voice ss ch fsm command Field Description CH state move to XXX from XXX The CH state changed from xxx to xxx. The service state of MCH changed from XXX to XXX. The MCH state changed from xxx to xxx. Table 120 describes output fields and messages for the debugging voice ss ch info command.
Field Description Enter the unhold service. The call was resumed. Finish handling, release new call info Table The recorded new call information table was released when the service CCB was deleted. Release new call info Table in XXX state. The new call information table was released. Switch leg type successfully. The leg type was successfully switched. Succeed to create XXX timer when enter new call operation. The xxx timer was successfully created in handling the setup of the new call.
Field Description MCH CCB is initialized successfully. The MCH CCB was successfully initialized. MCH CCB is deleted successfully. The MCH CCB was successfully deleted. The hookflash is counted successfully. The hookflash was successfully cached. The current state is XXX. The current state of the MCH service is xxx. Table 121 describes output fields and messages for the debugging voice ss ch timer command.
*Nov 20 00:38:37:851 2005 RouterA SS/7/VOICE: CH_INFO: [0x00000000] Send the service message successfully in [S_CH_IDLE] state. // A SERVICE (CH) message was sent successfully. *Nov 20 00:38:37:851 2005 RouterA SS/7/VOICE: CH_FSM: [0x00000000] CH state move to [S_CH_PRE] from [S_CH_IDLE]. // The state of the call hold module changed from idle to preparation.
CH_EVT: [0x00030000] Receive CMC_INFORMATION message from SA module. // DTMF digits were received. *Nov 20 01:32:15:241 2005 RouterA SS/7/VOICE: CH_TMR: [0x00030000] Timer deleted, Timer ID: TIMER_SS_CH_WAIT_DIALNUM. // The timer waiting for dialing the first digit was deleted. *Nov 20 01:32:15:241 2005 RouterA SS/7/VOICE: CH_TMR: [0x00030000] Timer created, Timer ID: TIMER_SS_CH_WAIT_DIALSPAN, Timer length: 10000. // The 10000-ms timer waiting for the next digit was started.
CH_INFO: [0x00030000] Close DTMF successfully, when dial the number. // The number matched a voice entity, and DTMF detection was disabled. *Nov 20 01:32:17:492 2005 RouterA SS/7/VOICE: CH_INFO: [0x00030002] Setup a new call when call hold. // A new call was originated while the first call was put on hold. *Nov 20 01:32:17:492 2005 RouterA SS/7/VOICE: CH_FSM: [0x00030000] CH state move to [S_SCH_WA] from [S_CH_NC]. // The state of the call hold module changed from digit collection to call origination.
*Nov 20 01:15:05:754 2005 RouterA SS/7/VOICE: CH_TMR: [0x00010000] Timer deleted, Timer ID: TIMER_SS_CH_WAIT_DIALNUM. // The timer waiting for dialing the first digit was deleted. *Nov 20 01:15:05:754 2005 RouterA SS/7/VOICE: CH_FSM: [0x00010000] CH state move to [S_CH_O] from [S_CH_NC]. // The state of the call hold module changed from digit collection to onhold. *Nov 20 01:15:05:754 2005 RouterA SS/7/VOICE: CH_EVT: [0x00010000] Received message [CMC_INFORMATION] in [S_CH_O] state.
SS CH all debugging switches are on *May 18 10:42:03:469 2007 RouterB SS/7/VOICE: CH_EVT: [0x00060000] CH Service Interface received message [CMC_SERVICE] from SPL [SPL_DISCRIM_SIP]. // A call hold request message was received from the SIP module. *May 18 10:42:03:469 2007 RouterB SS/7/VOICE: CH_INFO: [0x00060000] Start a new CH service successfully. // The call hold service was successfully started.
*May 18 10:42:05:879 2007 RouterB SS/7/VOICE: CH_TMR: [0x00060000] Timer deleted, Timer ID: TIMER_SS_CH_WAIT_MAXHOLDED. // The timer for the held party to wait was deleted. *May 18 10:42:05:879 2007 RouterB SS/7/VOICE: CH_INFO: [0x00060000] CH service is finished at cause [E_CH_OK]. // The call was resumed successfully, and the call hold service ended. debugging voice ss conf Use debugging voice ss conf to enable three-party conference debugging.
• Telephone A, Telephone B, and Telephone C are attached to Router A, Router B, and Router C, respectively. • Telephone A, Telephone B, and Telephone C are enabled with call hold, call hold and three-party conferencing, and call hold, respectively. • After Telephone A establishes a call with Telephone B, the user at Telephone B presses hookflash to place the call on hold and then calls Telephone C. Then, Telephone C goes off-hook.
CONF_TMR: [0x00000001] Timer created, Timer ID: TIMER_SS_CONF_WAIT_CUHACK, Timer length: 20000. *Jan 10 10:55:57:254 2008 ipp44-UP SS/7/VOICE: CONF_FSM: [0x0000000c] Conference state move from S_CONF_WDRV to S_CONF_WCUH. *Jan 10 10:55:57:355 2008 ipp44-UP SS/7/VOICE: CONF_INFO: [0x00000001] Conference receive CMC_SERVICE_ACK message. *Jan 10 10:55:57:506 2008 ipp44-UP SS/7/VOICE: CONF_EVT: [0x00000001] Receive CMC_SERVICE_ACK message at S_CONF_WCUH state.
undo debugging voice ss cr { all | error | info } Default Call barring debugging is disabled. Views User view Default command level 2: System level Parameters all: Specifies all types of debugging for call barring. error: Specifies error debugging. info: Specifies information debugging. Usage guidelines Table 123 describes output fields and messages for the debugging voice ss cr error command.
Field Description Dial-in restriction service has been disabled in local callee. Incoming call barring was disabled for the local callee. No CR config in CR analyse process in local caller. Call barring configuration of the local caller was unavailable. Examples # Enable all types of debugging for call barring on Router A. Call barring is enabled for Telephone A.
error: Specifies error debugging. event: Specifies event debugging. fsm: Specifies finite state machine debugging. info: Specifies information debugging. timer: Specifies timer debugging. Usage guidelines Table 125 describes output fields and messages for the debugging voice ss ct error command. Table 125 Output from the debugging voice ss ct error command Field Description Call transfer failed to find a CMC CCB in the call transfer originator (CTO) interface.
Field Description Received invalid service message when CTR ccb is null in CTR interface The received SERVICE message was not a CT message, and the call service could not be triggered. Received invalid message when CTR ccb is null in CTR interface The received message was not a SERVICE message, and the call transfer recipient (CTR) could not process it. The state of CTR is invalid in CTR interface. State = 4 The state of the CTR was invalid.
Field Description The final recipient cannot find the leg to be replaced. Cannot find XXX in SSS. Similar debugging information includes: Can not find the replaced leg in CTT interface Cannot get XXX in SSS. Cannot process XXX in SSS. This information indicates that something cannot be done. XXX indicates the task that cannot be done. SSS indicates the position where an error occurs. Invalid connect state in CTT process for CH The connection state of the held call to be replaced was invalid.
Field Description The CTO in the idle state sent a SERVICE(CT) message to the CMC module. Similar debugging information is in the following format: Send SERVICE(CT) message to CMC module in S_CTO_IDLE state Send MMM message to FFF module (in SSS state) This information indicates that the CTO in xxx state sent an xxx message to the xxx module. MMM indicates the message that was sent. FFF indicates the module to which the message was sent.
Field Description A RELEASE message was received from the CTR when the CRO's WACK state was not notified of, and the CT service ended. Similar debugging information is in the following format: Receive the recipient's release message at BCT in CTO's WACK status process. Service process ends Receive RRR's MMM message at TTT in SSS. (Service process ends) This information indicates that an event occurred after a message was received from a role in the CT service. RRR indicates a role in the CT service.
Field Description The original active leg is null. Service ends The original active leg could not be found, and the CT service ended. Release CTR ccb and CT ends in CTR's WREL status process The service resources of the CTR were released. Service ends after waiting originator's release message timeout Because a RELEASE message was not received from the CTO within the specified time, the CT service ended and returned to the normal call state. The original call was released after replacement succeeded.
• Telephone A, Telephone B, and Telephone C are attached to Router A, Router B, and Router C, respectively. • Telephone B and Telephone C are both enabled with call hold. Telephone A is enabled with call transfer. • After Telephone A establishes a call with Telephone B, the user at Telephone A presses hookflash to place the call on hold and then calls Telephone C. Then, the user at Telephone A hangs up after hearing ringback tones from Telephone C.
*Nov 20 02:33:39:286 2005 RouterA SS/7/VOICE: CT_FSM: [0x00070001] State changed from S_CTO_WACK to S_CTO_PENDING. // The state of the CT module changed from WACK to pending. *Nov 20 02:33:39:438 2005 RouterA SS/7/VOICE: CT_EVT: [0x00070001] Receive CMC_SERVICE message from SA module in CTO interface. *Nov 20 02:33:39:589 2005 Router A SS/7/VOICE: CT_EVT: [0x00070001] Receive CMC_SERVICE message from SA module in originator's PENDING state. // A NOTIFY message was received.
SS CT all debugging switches are on *May 18 11:40:49:15 2007 RouterB SS/7/VOICE: CT_EVT: [0x000b0000] Receive CMC_SERVICE message from SA module in CTR interface. *May 18 11:40:49:15 2007 RouterB SS/7/VOICE: CT_EVT: [0x000b0000] Receive CMC_SERVICE message from SA module in recipient's IDLE state. // A CMC_SERVICE message was received. *May 18 11:40:49:15 2007 RouterB SS/7/VOICE: CT_EVT: [0x000b0000] Send SERVICE_ACK(CT_OK) message to CMC module in S_CTR_IDLE state.
*May 18 11:40:55:242 2007 RouterB SS/7/VOICE: CT_EVT: [0x000b0003] Receive CMC_CONNECT message from SA module in CTR interface. *May 18 11:40:55:242 2007 RouterB SS/7/VOICE: CT_EVT: [0x000b0003] Receive CMC_CONNECT message from SA module in recipient's SCWC state. // A CMC_CONNECT message was received from the final recipient. *May 18 11:40:55:242 2007 RouterB SS/7/VOICE: CT_FSM: [0x000b0003] State changed from S_CTR_SCWC to S_CTR_WREL.
debugging voice ss cw Use debugging voice ss cw to enable call waiting debugging. Use undo debugging voice ss cw to disable call waiting debugging. Syntax debugging voice ss cw { all | error | event | fsm | info | timer } undo debugging voice ss cw { all | error | event | fsm | info | timer } Default The FEATURE service debugging is disabled. Views User view Default command level 2: System level Parameters all: Specifies all types of debugging for call waiting. error: Specifies error debugging.
Field Description Get brother leg fail on CW idle state. The FEATURE service failed to obtain a brother leg in the CW_IDLE state. Get original call leg fail on CW idle state The FEATURE service failed to obtain the originator leg in the CW_IDLE state. Failed to find new talk path in idle process. The FEATURE service failed to find the new talk path in the CW_IDLE state. Failed to create CW SRVACK timer on CW idle state. The FEATURE service failed to create the CW SRVACK timer in the CW_IDLE state.
Field Description The leg is already invalid on CW penging state. The call leg was invalid in the pending state. Failed to send connect message on CW penging state. The FEATURE service failed to send a CONNECT message in the pending state. Failed to create intsend alerting timer on CW pending state. The FEATURE service failed to create the ALERTING timer in the pending state. The leg may be deleted on CW penging state. The call leg was deleted in the pending state.
Table 133 Output from the debugging voice ss cw info command Field Description The CW CCB is initialized in create CW CCB. The CW CCB was initialized successfully. The CW CCB is deleted successfully. The CW CCB was deleted successfully. No find original call leg in judge talking process. No call leg was found in talk path judgment. The talk path number is [%d] in judge talking process. The number of talk paths in talk path judgment is xxx. Both legs are active,in judge talking process.
• Telephone A, Telephone B, and Telephone C are attached to Router A, Router B, and Router C, respectively. • Telephone A is enabled with call waiting. • Telephone B places a call to Telephone A that is conversation with Telephone C. debugging voice ss cw all SS CW all debugging switches are on *Nov 20 03:10:02:712 2005 RouterA SS/7/VOICE: CW_EVT: [0x000a0001] Receive CMC_RELEASE message from SA module.
// Announcement play needed to be controlled. *Nov 20 03:10:03:08 2005 RouterA SS/7/VOICE: CW_INFO: [0x00090003] Play call waiting signal tone. // The FEATURE service tones were played. *Nov 20 03:10:03:109 2005 RouterA SS/7/VOICE: CW_TMR: [0x00090003] Timer created, Timer ID: TIMER_SS_CW_PLAY_SOUND_INTERVAL, Timer length: 400. // A 400-ms timer was started to control the interval for playing call waiting tones.
*Nov 20 03:10:04:731 2005 RouterA SS/7/VOICE: CW_TMR: [0x00090003] Timer created, Timer ID: TIMER_SS_CW_PLAY_SOUND_INTERVAL, Timer length: 400. *Nov 20 03:10:04:883 2005 AR30-40 SS/7/VOICE: CW_EVT: [0x00090003] Receive TIMER_SS_CW_PLAY_SOUND_INTERVAL message from SA module. *Nov 20 03:10:04:983 2005 RouterA SS/7/VOICE: CW_EVT: [0x00090003] Receive TIMER_SS_CW_PLAY_SOUND_INTERVAL message from SA module in PENGING state.
CW_EVT: [0x000b0001] Receive CMC_SERVICE_ACK message from SA module in MCH state. // The CMC_SERIVCE_ACK message was processed in the multi-call hold state. *Nov 20 05:29:41:296 2005 RouterA SS/7/VOICE: CW_INFO: [0x000b0001] Received CH_OK CMC message on CW MCH state. // A CH_OK CMC message was received. *Nov 20 05:29:41:296 2005 RouterA SS/7/VOICE: CW_FSM: [0x000b0001] State changed from S_CW_MCH to S_CW_IDLE. // The CW service ended, and the state changed to idle.
Field Description It's not called party input password in Door-Relay service This error information indicates that the password was entered by the calling party. However, in the door opening control service, the password should be entered by the called party. Failed to send door-relay command to driver The door opening control service failed to send the door-relay command to the driver. Table 136 describes output fields and messages for the debugging voice ss dr info command.
*Sep 28 14:48:25:411 2009 RouterA SS/7/VOICE: DR_TMR: [0x00000001] Timer created, Timer ID: TIMER_SS_DR_DIALINTERVAL, Timer length: 10000. *Sep 28 14:48:25:541 2009 RouterA SS/7/VOICE: DR_TMR: [0x00000001] Timer deleted, Timer ID: TIMER_SS_DR_DIALINTERVAL. *Sep 28 14:48:25:651 2009 RouterA SS/7/VOICE: DR_TMR: [0x00000001] Timer created, Timer ID: TIMER_SS_DR_DIALINTERVAL, Timer length: 10000.
info: Specifies information debugging. timer: Specifies timer debugging. Usage guidelines Table 137 describes output fields and messages that for the debugging voice ss ft error command. Table 137 Output from the debugging voice ss ft error command Field Description The call leg parameter is null in invalid FT CCB state. The call leg parameter was null in the invalid feature (FT) CCB state. The call leg's father CMC CCB parameter is null in invalid FT CCB state.
Field Description Attach IPP CCB failed when proceed barge in service! The FEATURE service failed to attach the IPP CCB in the processing of the barge-in service. The IPP CCB is null when proceed barge in service. The IPP CCB was null in the processing of the barge-in service. The SIP CCB is null when proceed block barge in service. The SIP CCB was null in the processing of the block-barge-in service.
Field Description Can not find cmc CCB when delete FT CCB. The FT CCB to be deleted could not be found. Invalid leg in call out state when send service(feature) message. The leg parameter was invalid in the callout state when a SERVICE (FEATURE) message was sent. Failed to create brother leg when send feature message. The FEATURE service failed to create a brother leg when a FEATURE message was sent. Failed to create message table to brother leg when send feature message.
Field Description The result in SERVICE_ACK(Feature) message is "fail". The result in the SERVICE_ACK (FEATURE) message was fail. The fail cause is "Unknown user". The failure cause in the SERVICE_ACK message was unknown user. The fail cause is "9499". The failure cause in the SERVICE_ACK message was 9499. This cause code was directly displayed because it could not be parsed according to H3C's documents. Release call in SENDSRV state, the fail cause is "No calls to supervise".
Field Description Timer timeout, TimerId : TIMER_SS_FT_PLAYSOUND_INTERVAL. The interval timer for playing announcements expired. This timer was used for control over announcement play. Examples Output similar to the following example is generated when the user at Telephone A attached to Router A picks up the headset and dials *446# for Do Not Disturb Toggle: # Enable debugging for FEATURE service errors on Router A.
// The state changed from idle to SENDSRV. # Enable debugging for FEATURE service information on Router A. debugging voice ss ft info SS FT information debugging switch is on *May 14 15:18:27:894 2007 RouterA SS/7/VOICE: FT_INFO: [0x00090000] Create a FT CCB. // An FT CCB was created. *May 14 15:18:27:894 2007 RouterA SS/7/VOICE: FT_INFO: [0x00090000] The feature code "*446" match to service "do not disturb". // The feature code *446 matched the do-not-disturb service.
*May 14 15:28:36:787 2007 RouterA SS/7/VOICE: FT_TMR: [0x000a0000] Timer created, Timer ID: TIMER_SS_FT_WAITSRVACK, Timer length: 20000. // A 20000-ms SS_FT_WAITSRVACK timer was created. *May 14 15:28:36:806 2007 RouterA SS/7/VOICE: FT_TMR: [0x000a0001] Timer deleted, Timer ID: TIMER_SS_FT_WAITSRVACK. // The SS_FT_WAITSRVACK timer was deleted. // The following repeatedly announced the successful setting of a feature service five times by repeatedly creating and deleting such a timer five times .
Default Hunt group debugging is disabled. Views User view Default command level 2: System level Parameters all: Specifies all types of debugging for hunt group. error: Specifies error debugging. event: Specifies event debugging. info: Specifies information debugging. Usage guidelines Table 142 describes output fields and messages for the debugging voice ss hg error command. Table 142 Output from the debugging voice ss hg error command Field Description The Leg parameter received is null.
Field Description Receive release message from SA, but is of wrong type. A RELEASE message was received. Can not get the new entity. The hunt group module failed to obtain the index of a new entity. Can not find the new entity. The hunt group module failed to find an available entity. Examples # Enable all types of debugging for the hunt group on Router A.
Views User view Default command level 2: System level Parameters all: Specifies all types of debugging for message waiting indication (MWI). error: Specifies error debugging. event: Specifies event debugging. info: Specifies information debugging. Usage guidelines Table 145 describes output fields and messages for the debugging voice ss mwi error command. Table 145 Output from the debugging voice ss mwi error command Field Description MessagesAccount is invalid. The message account was invalid.
Field Description Reach the max redirect times limit. The maximum number of redirection times was reached. Table 147 describes output fields and messages for the debugging voice ss mwi info command. Table 147 Output from the debugging voice ss mwi info command Field Description The IfIndex is XXX. The interface index was xxx. Needed to update vpIndex of entity. MWI needed to update the virtual path index of the entity is needed. Handle undo enable MWI server.
*Jan 25 10:05:24:45 2008 Sysname SIP/7/VOICE: MWI_Info: Handle execute timeout: The execute count is 0. // The Execute timer timed out. *Jan 25 10:05:24:46 2008 Sysname SIP/7/VOICE: MWI_Event: Dispatch to FSM[0x0000]: Process the event of ADD_TIMEOUT in WAIT_ADD_TIMEOUT state. // The ADD_TIMEOUT event was processed in the WAIT_ADD_TIMEOUT state. *Jan 25 10:05:24:46 2008 Sysname SIP/7/VOICE: MWI_Info: Handle execute timeout: Delete execute timer. // The Execute timer timed out and was deleted.
event: Specifies event debugging. info: Specifies information debugging. Usage guidelines Table 148 describes output fields and messages for the debugging voice ss sa error command. Table 148 Output from the debugging voice ss sa error command Field Description Failed to get brother leg The service analysis module failed to obtain the brother leg of the current leg. The type of leg is invalid in checking setup message sending The leg type was invalid when a SETUP message was sent.
Table 150 describes output fields and messages for the debugging voice ss sa info command. Table 150 Output from the debugging voice ss sa info command Field Description No need to attach call ID to VIM The CALL ID did not need to be bound to the VIM module. To updating DTMF isn't processed in CS to CS call Updating the DTMF setting was unnecessary for a local call. Success to send DTMF capability to SPL The service analysis module succeeded in sending the DTMF capability to the SPL.
SA_EVT: [0x00180000] Receive CMC_SETUP message from CMC module in S_IDLE state. // The SETUP message was processed in the normal state. *Nov 20 07:42:18:390 2005 RouterA SS/7/VOICE: SA_EVT: [0x00180000] No matched message item is found, send it to CMC module. // No matched message was found, and the normal call flow was applied. *Nov 20 07:42:18:390 2005 RouterA SS/7/VOICE: SA_INFO: [0x00180001] The brother IF index of this leg is invalid, find it from brother leg.
Parameters all: Specifies all types of debugging for the service match module. error: Specifies error debugging. event: Specifies event debugging. fsm: Specifies finite state machine debugging. info: Specifies information debugging. timer: Specifies timer debugging. Usage guidelines Table 151 describes output fields and messages for the debugging voice ss sm error command.
Field Description Failed to create dial interval number in invalid SM CCB state. The service match module failed to create a timer waiting for dialing the next digit when no SM CCB existed. Receive unknown CMC message from SM module in RECVCODE state. An unknown CMC message was received in the RECVCODE state. Receive unknown TIMER message from SM module in RECVCODE state. An unknown TIMER message was received in the RECVCODE state. Receive unknown ACCP message from SM module in RECVCODE state.
Field Description The feature string is too long after substitute the called number. The FEATURE string exceeded the limited length after called number substitution. Could not find any voice entity. No voice entity could be matched. Stop DTMF detect error. Disabling DTMF detection failed. Play signal tone error when succeed to set local service. The service match module failed to play announcements after a local service was set successfully.
Field Description The affix number template not allow to input '*'. No asterisk was allowed in the additional code template. Match failed, the affix number's length must between 1 and 31. The match failed. The additional code must be 1 to 31 characters in length. Match failed, the affix number is not 4 digits or state is not RECVNUM. The match failed. The additional code was not a four-digit code, and the state was not RECVCODE.
Field Description invalid operate type parameter when save call-forwarding configuration. The operation type was invalid when the call forwarding configuration was being saved. Can not find CMC CCB when create SM CCB. The service match module failed to obtain the CMC CCB when an SM CCB was being created. The SM service CCB pointer in CMC CCB is existed when create SM CCB. The pointer to the SM CCB in the CMC CCB already existed when an SM CCB was being created.
Field Description The destination feature code parameter is null when reverse code. The pointer to the destination feature code was null during reversal of a feature code. The feature index is invalid when reverse feature code. The feature index obtained through parsing was invalid during reversal of a feature code. Failed to reverse code because of invalid operate type. Reversing a feature code failed because the operation type was invalid. Can not find join character when reverse feature code.
Field Description The feature service is denied, transmit the ACCP_INFORMATION message to other side. The FEATURE service was disabled, and an ACCP_INFORMATION message was transparently transmitted to the peer end. Feature service is permit, hold back the ACCP_INFORMATION message. The FEATURE service was enabled, and an ACCP_INFORMATION message was intercepted. Receive ACCP_INFORMATION message when SM CCB is invalid and not in talking state.
Field Description The matched service is execute type, so only check the first affix number item. An execution service was matched, and only the first additional code in the template was checked. Check the first affix number item when matched feature service. The first additional code was checked when a FEATURE service was matched. Succeed to match service when the template defines an affix number item. A service with an additional code was successfully matched.
Table 155 Output from the debugging voice ss sm timer command Field Description Timer created, TimerId: TIMER_SS_SM_DIALINTERVAL, Timer length: 11000. An 11-second timer for dialing the next digit was created. Timer deleted, TimerId: TIMER_INLEG_WAIT_ALERTING. The WAIT_ALERTING timer for the input leg was deleted. Timer timeout, TimerId : TIMER_SS_SM_PLAYSOUND_INTERVAL. The interval timer for playing announcements expired.
SM_EVT: [0x00000000] Receive TIMER_SS_SM_PLAYSOUND_INTERVAL message from SA module in RECVCODE state. # Enable debugging for service match module finite state machines on Router A. debugging voice ss sm fsm SS SM FSM debugging switch is on *May 14 11:50:46:497 2007 RouterA SS/7/VOICE: SM_FSM: [0x00010000] State changed from IDLE to RECVCODE. // The state changed from idle to RECVCODE. # Enable debugging for service match module information on Router A.
*May 14 14:00:32:350 2007 RouterA SS/7/VOICE: SM_INFO: [0x00030000] Match number in service register mode. *May 14 14:00:32:350 2007 RouterA SS/7/VOICE: SM_INFO: [0x00030000] Feature service is permitted, will check the feature template record. *May 14 14:00:32:393 2007 RouterA SS/7/VOICE: SM_INFO: [0x00030000] Matched service code all, id = 4, name = call waiting. *May 14 14:00:32:544 2007 RouterA SS/7/VOICE: SM_INFO: [0x00030000] The number is partially matched, continue to receive DTMF number.
# Enable debugging for service match module timers on Router A. debugging voice ss sm timer SS SM timer debugging switch is on *May 14 14:50:44:589 2007 RouterA SS/7/VOICE: SM_TMR: [0x00060000] Timer created, Timer ID: TIMER_SS_SM_DIALINTERVAL, Timer length: 11000. // A 11000-ms interval timer for dialing the next digit was created. *May 14 14:50:46:658 2007 RouterA SS/7/VOICE: SM_TMR: [0x00060000] Timer deleted, Timer ID: TIMER_INLEG_WAIT_ALERTING.
SM_TMR: [0x00060000] Timer timeout, Timer ID: TIMER_SS_SM_PLAYSOUND_INTERVAL. *May 14 14:50:48:919 2007 RouterA SS/7/VOICE: SM_TMR: [0x00060000] Timer created, Timer ID: TIMER_SS_SM_PLAYSOUND_INTERVAL, Timer length: 200. *May 14 14:50:49:120 2007 RouterA SS/7/VOICE: SM_TMR: [0x00060000] Timer timeout, Timer ID: TIMER_SS_SM_PLAYSOUND_INTERVAL. *May 14 14:50:49:120 2007 RouterA SS/7/VOICE: SM_TMR: [0x00060000] Timer created, Timer ID: TIMER_SS_SM_PLAYSOUND_INTERVAL, Timer length: 200.
Table 156 Output from the debugging voice ss rc error command Field Description Allocate memory failed for creating Release-control CB. The release control module failed to allocate memory for creating release control block (RCB). Receive invalid message of %s. An invalid message of %s was received. Table 157 describes output fields and messages for the debugging voice ss sm event command.
// A RELEASE message was received. *Jul 7 19:17:37:232 2008 RouteA SS/7/VOICE: RC_INFO: [0x00090001] The Release control CB is initialized successfully. // The initialization of RCB is successful. *Jul 7 19:17:37:232 2008 RouteA SS/7/VOICE: RC_EVT: [0x00090001] Process the message of CMC_RELEASE in S_RC_IDLE state. // The RELEASE message was received in idle state. *Jul 7 19:17:37:232 2008 RouteA SS/7/VOICE: RC_TMR: [0x000000ca] Timer created, Timer ID: RC_DELAY_ONHOOK, Timer length: 90000.
// A CONNECT message was received. *Jul 7 19:17:39:242 2008 RouteA SS/7/VOICE: RC_EVT: [0x00090001] Process the message of CMC_CONNECT in S_RC_WAIT_OFFHOOK state. // A CONNECT message was received in wait-for-off-hook state. *Jul 7 19:17:39:242 2008 RouteA SS/7/VOICE: RC_TMR: [0x00090001] Timer deleted, Timer ID: RC_DELAY_ONHOOK. // The on-hook delay timer was deleted. *Jul 7 19:17:39:242 2008 RouteA SS/7/VOICE: RC_INFO: [0x00090000] The Release-control CB is deleted successfully.
fsm: Specifies finite state machine debugging. info: Specifies information debugging. timer: Specifies timer debugging. Examples # Enable all types of debugging for Join header services on Router A. Output similar to the following example is generated when Telephone C dials *425*1000# to monitor Telephone A under these conditions: • Telephone A at 1000 is attached to Router A, on which all types of debugging for Join header related services are enabled. • Telephone B is attached to Router B.
*Jun 24 20:34:06:566 2009 MSR30-12 SS/7/VOICE: JOIN_TMR: [0x00000001] Timer deleted, Timer ID: TIMER_SS_JOIN_WAIT_DRVACK. *Jun 24 20:34:06:667 2009 MSR30-12 SS/7/VOICE: JOIN_INFO: [0x00000001] Succeed to initialize DSP in WDRV state. // DSP was initialized successfully. *Jun 24 20:34:06:817 2009 MSR30-12 SS/7/VOICE: JOIN_FSM: [0x00000001] Join state moves from JOIN_WDRV to JOIN_ACTIVE. // The state of the Join service changed from WDRV to ACTIVE.
Call-watch debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging call-watch event Use debugging call-watch event to enable call-watch event debugging. Use undo debugging call-watch event to disable call-watch event debugging. Syntax debugging call-watch event undo debugging call-watch event Default Call-watch event debugging is disabled.
Examples # Enable call-watch event debugging, and enable terminal monitoring. Output similar to the following example is generated when VLAN interface 111 is shut down under the following conditions exist: • Interface T1 2/0 is associated with call-watch group 1. • Call-watch group 1 monitors VLAN interface 111.
*0.34932553 Sysname CW/7/debug2: Call-Watch debug information: controller T1 2/0 associate group 1 Call-Watch debug information: controller T1 2/0 state from Watch-Out to No-Watch-Out // The state of call-watch group 1 changed from up to down, and the state of interface T1 2/0 changed from No-Watch-Out to Watch-Out. [Sysname-Vlan-interface111] %May 28 16:50:14:379 2008 Sysname IFNET/4/LINK UPDOWN: T1 2/0: link status is UP // The state of interface T1 1/0 changed to up.
CFD debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging cfd Use debugging cfd to enable CFD debugging. Use undo debugging cfd to disable CFD debugging.
Usage guidelines If neither the send keyword nor the receive keyword are specified, debugging for both received and sent CFD packets is enabled. If none of the ais, cci, fng, lbi, mcc, mme, and rmep keywords are specified, debugging for all CFD state machines is enabled. If you do not specify a port, debugging for all ports is enabled. If you enable debugging for sent packets on a port with inbound MEPs configured, only CCM packets are printed, while LT and LB packets are not printed.
Field Description Reply Ingress TLV's Ingress MAC is multicast address The destination MAC address in the reply ingress TLV is a multicast address. Reply Egress TLV's Egress Action is invalid The egress action of the reply egress TLV is invalid. Reply Egress TLV's Egress MAC is multicast address The destination MAC address in the reply egress TLV is a multicast address. Sequence number is not accordant The sequence number does not match.
Table 164 describes output fields and messages for the debugging cfd packet command. Table 164 Output from the debugging cfd packet command Field Description Send/Receive CFD Packet via port interface-type interface-number The device sent/received a CFD packet through a port. Pkt length Packet length. Example # Enable debugging for EAIS.
// The device sent a CFD packet out of Ethernet 1/1. The value 03 in the beginning of the packet indicates that the packet is a LBM packet. *0.17263340 Sysname CFD/8/Pkt: Receive CFD Packet via port Ethernet1/1: 00 04 00 04 00 1a 77 f8 04 00 05 3f 00 00 00 00 05 00 07 00 00 e0 fc 52 ba a0 00 Pkt length: 27 // The device received a CFD packet through Ethernet 1/1. The value 04 in the beginning of the packet indicates that the packet is a LTR packet. *0.
00 25 00 04 00 00 00 01 20 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Pkt length: 77 // The device sent a CFD frame out of port Ethernet1/1. The value 25 in the beginning of the packet indicates that the packet is a TST packet. *0.
// The CFD MME state machine transited from the ERRCCM_NO_DEFECT state to the ERRCCM_DEFECT state.
Cluster management debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ndp packet Use debugging ndp packet to enable NDP packet debugging. Use undo debugging ndp packet to disable NDP packet debugging. Syntax debugging ndp packet undo debugging ndp packet Default NDP packet debugging is disabled.
Syntax debugging ntdp { all | data | error | message | packet } undo debugging ntdp { all | data | error | message | packet } Default NTDP debugging is disabled. Views User view Default command level 1: Monitor level Parameters all: All types of NTDP debugging. data: Debugging for NTDP data operation. error: Debugging for NTDP errors. message: Debugging for NTDP messages. packet: Debugging for NTDP packets.
Field Description TTL Hop count of the NTDP topology collection request packet. Dest MAC Destination MAC address. Snd Port Outgoing port. Segment/Serial Fragment information. Examples # Enable NTDP packet debugging. debugging ntdp message *0.349815585 Sysname NTDP/8/Debug_Rcv_Msg: Receiving Msg: Topology-Candidate Request // A topology collection request message was received from the candidate device. *0.
Usage guidelines Table 170 describes output fields and messages for the debugging cluster event command. Table 170 Output from the debugging cluster event command Field Description ucStringt Information description. Table 171 describes output fields and messages for the debugging cluster handshake command. Table 171 Output from the debugging cluster handshake command Field Description usClusterMode The cluster mode of the device. ucTopState Flag of a topology change.
Field Description ulExtendedLen Length of the extended field. CheckSumVal Total checksum of the cluster data. CmdFlag Return flag. CmdRec Return word. Table 174 describes output fields and messages for the debugging cluster nat command. Table 174 Output from the debugging cluster nat command Field Description NAT_Server_Add A NAT server was added. NAT_Server_Del A NAT server was removed. IfIndex Interface index. GlobalPort Global port number. GlobalIP Global IP address.
Field Description DateLen Data length. Content Parameter content. Table 176 describes output fields and messages for the debugging cluster state command. Table 176 Output from the debugging cluster state command Field Description ID Member ID. Pre state The previous state. State The current state. Time Hold time of the current state. Examples # Enable cluster packet debugging. debugging cluster packet *0.93214687 h3c_0.
# Enable NTDP packet data operation debugging. debugging ntdp data *Apr 27 04:48:33:891 2000 Sysname NTDP/7/Debug_NTDP_DATA_Operate: NTDP data operation: Type--REFRESH, Device ID--0000-0000-00e0-fc00-3333 // An NTDP data operation was performed. debugging cluster ext Use debugging cluster ext to enable SNMP configuration synchronization debugging. Use undo debugging cluster ext to disable SNMP configuration synchronization debugging.
Field Description PortIndex Port index. PortName Port name. Command word of the synchronization sub-packet: SynSubCmd • • • • 0—Configures a read community. 1—Configures a write community. 2—Configures an SNMPv3 group name. 3—Creates or updates the MIB view that is shared by the cluster. • 4—Adds a user to the SNMPv3 group that is shared by the cluster. Undo flag: ulFlag • 0—Not to undo. • 1—To undo. ComName Community name. ComView MIB view for the community name.
Field Description Authentication mode of the newly added SNMPv3 group user: AuthFlag • 1—MD5. • 2—SHA. PacketLen Data length. Examples In the following examples, Device A is the management device in a cluster and it is communicating with a managed member device on the whitelist. # Enable SNMP configuration synchronization event debugging on both Device A and its managed device.
DstMAC :00e0-fc00-2000 ParaLen :81 PortIndex : PortName : SynSubCmd: 0 ulFlag: 0 PacketLen :66 ComName :read ComView : Member 1 succeeded in the read-community configuration. Finish to synchronize the command. // Device A sent a request to configure the SNMP read-community on the managed device. *0.
Connection limit debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging connection-limit Use debugging connection-limit to enable debugging for connection limit. Use undo debugging connection-limit to disable debugging for connection limit. Syntax debugging connection-limit undo debugging connection-limit Default Debugging for connection limit is disabled.
Field Description Current-amount Number of connections. ConnLmt Inc: Connection limit statistics entry is incremented by 1. Whether new connections are allowed: Limit-Flag • 0—Yes. • 1—No. The limit limit-id is enabled. Connection limit rule limit-id has been enabled successfully. The limit limit-id is disabled. Connection limit rule limit-id has been disabled successfully. Matched limit: limit-id. Connection limit rule limit-id is matched.
// There is one connection at present, and the number of connections has reached the upper limit. No more connections are allowed. • Multi-core device: # Enable connection limit debugging on the device. Output similar to the following example is generated when TCP connections are set up between the source and the destination under the following condition: Connection limit policy 0 with connection limit rule 0 is configured.
Content filtering debugging commands debugging content-filter NOTE: Support for the command depends on the device model. Use debugging content-filter to enable debugging for content filtering. Use undo debugging content-filter to disable debugging for content filtering. Syntax debugging content-filter { all | error | event | packet } [ acl acl-number ] undo debugging content-filter { all | error | event | packet } Default Debugging for content filtering is disabled.
*May 14 17:45:53:344 2009 H3C DPDPI/7/EVENT: HTTP URL IP filtering dropped the packet. // HTTP URL IP blocking dropped the packet. # Enable packet debugging of content filtering. When a host in zone Trust sends an email to a mail server in zone Untrust, output similar to the following example is generated: debugging content-filter packet *May 14 17:48:30:141 2009 H3C DPDPI/7/PACKET: Receiving packet.Session state : 0 , Application type : 5 // An SMTP packet was received.
COPS debugging commands debugging cops client-type Syntax Centralized devices: debugging cops client-type dot1x { all | error | event | packet } undo debugging cops client-type dot1x [ all | error | event | packet ] Distributed devices–Centralized IRF devices: debugging cops client-type dot1x{ all | error | event | packet } [ slot slot-number ] undo debugging cops client-type dot1x [ all | error | event | packet ] [ slot slot-number ] Distributed IRF devices: debugging cops client-type dot1x { all | error |
Usage guidelines Use the debugging cops command to enable debugging for COPS. Use the undo debugging cops command to disable debugging for COPS. Table 180 describes output fields and messages for the debugging cops client-type dot1x error command. Table 180 Output from the debugging cops client-type dot1x error command Field Description Failed to create packet Failed to create COPS packet, which can be SSC, DRQ, KA, CC, REQ, OPN, or RPT.
debugging cops client-type dot1x event *Feb 8 11:08:28:046 2010 Sysname COPS/7/EVENT: Creating Timer, OPN timer created. *Feb 8 11:08:28:078 2010 Sysname COPS/7/EVENT: Creating Timer, KA send-timer created. *Feb 8 11:08:28:078 2010 Sysname COPS/7/EVENT: Creating Timer, KA wait-timer created. *Feb 8 11:08:28:078 2010 Sysname COPS/7/EVENT: Creating client type, set client connection state to DOWN. # Enable debugging for COPS errors.
Customizable IVR debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging voice ivr fes Use debugging voice ivr fes to enable FES debugging in the IVR system. Use undo debugging voice ivr fes to disable FES debugging in the IVR system. Syntax debugging voice ivr fes { all | error | event | fsm | info | timer } undo debugging voice fes { all | error | event | fsm | info | timer } Default FES debugging is disabled.
Table 184 Output from the debugging voice ivr fes event command Field Description CMC --> IVR : Accp Setup. The IVR received an Accp Setup message from the CMC. CMC --> IVR : Accp Channel Ready Ack. The IVR received an Accp Channel Ready Ack message from the CMC. CMC --> IVR : Accp Fax Voice Switch. The IVR received an Accp Fax Voice Switch message from the CMC. CMC --> IVR : Accp Information. The IVR received an Accp Information message from the CMC. CMC --> IVR : Accp Service.
Table 186 Output from the debugging voice ivr fes info command Field Description Input error, RepeatTimes = %d, InputErrorTimes = %d. Subscriber input errors: the allowed maximum number of repeated input errors was xx, and the actual number of repeated input errors was xxx. Timeout, RepeatTimes = %d, TimeoutTimes = %d. Subscriber timeout time: the allowed maximum number of repeated subscriber timeout was xx, and the actual number of repeated subscriber timeout was xxx.
IVR_FES_Fsm: IDLE --> WAIT_CHY_ACK, CallId = 131073, LocalId = 0. // The state of the call FSM changed from IDLE to WAIT_CHY_ACK. *Jun 27 11:20:26:79 2008 71_C IVRF/7/VOICE: IVR_FES_Event: CMC --> FES : Accp Channel Ready Ack. // The IVR_FES received an Accp Channel Ready Ack message from the CMC. *Jun 27 11:20:26:80 2008 71_C IVRF/7/VOICE: IVR_FES_Timer: Delete Timer, TmrId = 977, TmrType = WAIT CHANNEL READY ACK. // The timer for receiving a Channel Ready Ack message was deleted.
// The subscriber input timeout timer under the node was deleted. *Jun 27 12:05:11:215 2008 71_C IVRF/7/VOICE: IVR_FES_Timer: Start Timer, TmrId = 250, TmrType = CALL WAIT INPUT INTERVAL, TmrLength = 10000. // The timer specifies the interval between key-presses under the Call node was started. *Jun 27 12:05:11:215 2008 71_C IVRF/7/VOICE: IVR_FES_Info: CALL_WAIT_INPUT --> CALL_WAIT_INPUT, LocalId = 0. // The state of the node FSM was CALL_WAIT_INPUT.
*Jun 27 12:05:13:555 2008 71_C IVRF/7/VOICE: IVR_FES_Timer: Start Timer, TmrId = 317, TmrType = WAIT SERVICE ACK, TmrLength = 20000. // The timer for receiving a Service Ack message was started. *Jun 27 12:05:13:556 2008 71_C IVRF/7/VOICE: IVR_FES_Event: FES --> CMC: Accp Service. // The IVR_FES sent an Accp Service message to the CMC. *Jun 27 12:05:13:556 2008 71_C IVRF/7/VOICE: IVR_FES_Fsm: ACTIVE --> WAIT_SERVICE_ACK, CallId = 720897, LocalId = 0.
// The IVR system processed services in the Alerting state. *Jun 27 12:05:15:686 2008 71_C IVRF/7/VOICE: IVR_FES_Info: Receive message from SA module. // The IVR_FES received a message from the SA module. *Jun 27 12:05:15:687 2008 71_C IVRF/7/VOICE: IVR_FES_Info: Connect state process. // The IVR system processed services in the Connect state. debugging voice ivr mps Use debugging voice ivr mps to enable MPS debugging in the IVR system.
Table 188 Output from the debugging voice ivr mps event command Field Description Free read control block, CodecType = %d, FileName = %s. The read control block was released: the codec type was x and the filename was xxx. Free resource control block, CodecType = %d, FileName = %s. The resource control block was released: the codec type was x and the filename was xxx. Examples # Enable all types of debugging for the MPS.
// The read control block was released. *Jun 27 14:18:08:372 2008 71_C IVRM/7/VOICE: IVR_MPS_Event: Free resource control block, CodecType = 0x0, FileName = cfa0:/wav/ g729r8/callSecDial_g729.wav. // The resource control block was released. • Output similar to the following messages is generated when the subscriber (500) hangs up without originating a secondary call: *Jun 27 14:20:42:677 2008 71_C IVRM/7/VOICE: IVR_MPS_Event: End playing media, MediaID = 1000 FESCallID = 0.
CWMP (TR-069) debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging cwmp all Use debugging cwmp all to enable all types of debugging for CWMP. Use undo debugging cwmp all to disable all CWMP debugging. Syntax debugging cwmp all undo debugging cwmp all Default CWMP debugging is disabled.
information:Serial number: 210231A73F1034103445 . // The CWMP device serial ID was displayed. *Aug 10 17:57:39:203 2007 Sysname CWMP/7/DebugInfo: information:Construct messagse. length = 1325, message = PAGE 339xmlns:cwmp="urn:dslforum-org:cwmp-1-0" xmlns:soap="http://schemas.xmlSOAP.org/soap/envelope/" xmlns:encodingStyle="http://schemas.xmlSOAP.
// CWMP finished receiving the HTTP header. *Aug 10 17:57:44:344 2007 Sysname CWMP/7/DebugInfo: information:Continue to receive HTTP message . // CWMP continued to receive the HTTP message body. *Aug 10 17:57:44:344 2007 Sysname CWMP/7/DebugInfo: information:Message received. length = 564. // CWMP received a message. The message length is 564. *Aug 10 17:57:44:344 2007 Sysname CWMP/7/DebugInfo: receive:Message received. message = PAGE 341nvelopes>. // CWMP succeeded in popping . the label with the long *Aug 10 17:57:44:375 2007 Sysname CWMP/7/DebugInfo: information:Poping label succeeded. full-label = // CWMP succeeded in pushing the label with the long label . *Aug 10 17:57:44:375 2007 Sysname CWMP/7/DebugInfo: information:Poping label succeeded. full-label = . // CWMP succeeded in popping the label with the long label empty.
error:Failed to create CWMS queue. // CWMP failed to create CWMS queue when CWMP was enabled. *Aug 13 16:40:52:719 2007 Sysname CWMP/7/DebugInfo: error:Failed to initialize CWMP task. // CWMP failed to initialize the CWMP task. *Aug 13 16:40:52:719 2007 Sysname CWMP/7/DebugInfo: error:Failed to get queue length. // CWMP failed to get queue length. debugging cwmp information Use debugging cwmp information to enable CWMP information debugging.
Default CWMP received packet debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 189 describes output fields and messages for the debugging cwmp packet receive command. Table 189 Output from the debugging cwmp packet receive command Field Description PAGE 344xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:cwmp="urn:dslforum-org:cwmp-1-0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 1 5
// CWMP received a message.
debugging soap all Use debugging soap all to enable all types of SOAP debugging. Use undo debugging soap all to disable all types of SOAP debugging. Syntax debugging soap all undo debugging soap all Default SOAP debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines This command might cause heavy traffic and affect system performance. To ensure system performance, use this command only when necessary, and disable the command when you complete debugging.
Default SOAP error debugging is disabled. Views User view Default command level 1: Monitor level Examples # Enable SOAP error debugging. If CWMP failed to create an XML parser for a received HTTP message, output similar to the following example is generated: terminal debugging terminal monitor debugging soap error *Aug 13 16:26:21:531 2007 Sysname SOAP/7/DebugInfo: error:Failed to create XML parser.
DCC debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging dialer Use debugging dialer to enable a specific type of DCC (Dial Control Center) debugging. Use undo debugging dialer to disable a specific type of DCC debugging. Syntax debugging dialer { all | event | packet } undo debugging dialer { all | event | packet } Default All types of DCC debugging are disabled.
Table 191 describes output fields and messages for the debugging dialer packet command. Table 191 Output from the debugging dialer packet command Field Description the packet is interesting The packet conforms to the dial-up rules and can trigger the device to dial a number. try to find routing to ip-address on interface interface-type interface-number DCC tried to find a route to ip-address on interface interface-type interface-number.
# interface Serial2/0:15 link-protocol ppp dialer enable-circular dialer-group 1 dialer circular-group 0 # interface Dialer0 link-protocol ppp ip address 10.0.0.2 255.255.255.0 dialer enable-circular dialer-group 1 # debugging dialer event terminal monitor ping 10.0.0.2 PING 10.0.0.2: 56 data bytes, press CTRL_C to break *0.
*0.20467140 RouterA DCC/8/debug:DCC: Serial2/0:9's link-layer NCP negotiation is successful! // NCP negotiation was successful on Serial2/0:9 interface. *0.20467140 RouterA DCC/8/debug:DCC: Add VLink 9 OK, father interface = Dialer0 // Virtual link 9 was successfully created. The parent interface is Dialer0. # Enable debugging for DCC packets. debugging dialer packet terminal monitor ping 10.0.0.2 PING 10.0.0.2: 56 data bytes, press CTRL_C to break *0.
DDoS protection debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ddos packet Use debugging ddos packet to enable DDoS protection packet debugging. Use undo debugging ddos packet to disable DDoS protection packet debugging. Syntax debugging ddos packet undo debugging ddos packet Default DDoS protection packet debugging is disabled.
User-service: example Src-ip: 114.89.14.154 Dst-ip: 1.1.1.1 Src-port: 1024 Dst-port: 1025 Protocol: 6 // The Guard received a TCP packet for the user service example. debugging ddos error Use debugging ddos error to enable DDoS protection error debugging. Use undo debugging ddos error to disable DDoS protection error debugging. Syntax debugging ddos error undo debugging ddos error Default DDoS protection error debugging is disabled.
Examples # Enable DDoS protection error debugging on the Guard. Output similar to the following example is generated when the IP address 1.1.1.1 is attacked under the following conditions: • On the SecCenter, traffic filtering devices are added, and a user service named example is defined to protect IP address 1.1.1.1 against DDoS attacks. • A DDoS Guard detection interface is specified on the Guard. • The NetStream log function is enabled on the Detector.
Table 194 Output from the debugging ddos event command Field Description The packet was discarded by the filter of the user service named user-service-name. Packet dropped by the filter of the user-service user-service-name. method: Filter type. • 0—Filtering based on source IP address. • 1—Filtering based on destination IP address. Protocol: protocol-type, dst-port: dst-port-num, method: method-type, address: ip-address.
Refreshed policy dst-ip(1.1.1.1) when deleting session. Related sessions: 887, new sessions: 40, current sessions: 887, current sequence : 1. // The policy was refreshed during session deletion. *Feb 26 16:01:58:516 2009 Sysname DDOS/7/EVENT: Aging an IP statistics entry (1.1.1.1). // The IP statistics entry of 1.1.1.1 aged out. *Feb 26 16:01:58:516 2009 Sysname DDOS/7/EVENT: Aging policy of the user-service example. // The policy of the user service example aged out.
Device management debugging commands debugging device Use debugging device to enable device debugging. Use undo debugging device to disable device debugging. Syntax debugging device undo debugging device Default Device debugging is disabled. Views User View Default command level 1: Monitor level Examples # Enable device debugging.
DHCP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging dhcp server Use debugging dhcp server to enable DHCP server debugging. Use undo debugging dhcp server to disabled DHCP server debugging. Syntax debugging dhcp server { all | error | event | packet } undo debugging dhcp server { all | error | event | packet } Default DHCP server debugging is disabled.
Client IP address: 0.0.0.0 Your IP address: 0.0.0.0 Server IP address: 0.0.0.0 Relay agent IP address: 22.0.0.1 Client hardware address: 00e0-fc14-1601 Server host name: Not Configured, Boot file name: Not Configured DHCP message type: DHCP Discover // The DHCP server received a DHCP-DISCOVER packet. *0.278312 Sysname DHCPS/7/DHCPS_EVENT: DHCPServer: Sending ICMP ECHOREQUEST to target IP: 22.0.0.1. *0.278312 Sysname DHCPS/7/DHCPS_EVENT: DHCPServer: Assign free lease from global pool.
Rx, interface Vlan-interface1 Message type: request Hardware type: 1, Hardware address length: 6 Hops: 1, Transaction ID: 2294688324 Seconds: 0, Broadcast flag: 0 Client IP address: 0.0.0.0 Your IP address: 0.0.0.0 Server IP address: 0.0.0.0 Relay agent IP address: 22.0.0.1 Client hardware address: 00e0-fc14-1601 Server host name: Not Configured, Boot file name: Not Configured DHCP message type: DHCP Request // The DHCP server received a DHCP-REQUEST message. *0.
Parameters all: Specifies all types of debugging for DHCP relay agent. error: Specifies DHCP relay agent error debugging. event: Specifies DHCP relay agent event debugging. packet: Specifies DHCP relay agent packet debugging. client mac mac-address: Specifies debugging for packets that the DHCP relay agent forwards for a specific DHCP client. The mac-address argument is the MAC address of the DHCP client, in the format of H-H-H. Examples # Enable all types of debugging for DHCP relay agent.
Server IP address: 0.0.0.0 Relay agent IP address: 22.0.0.1 Client hardware address: 00e0-fc14-1601 Server host name: Not Configured, Boot file name: Not Configured DHCP message type: DHCP Offer *0.230891 Sysname DHCPR/7/DHCPR_DEBUG_RELAYPKT: Pkt Sent: send reply interface Vlan-interface22, dest IP: 255.255.255.255, chardAddr: 00e0.fc14.1601, server-group: 0 // The DHCP relay agent received a DHCP-OFFER message and broadcast it. *0.
*0.231063 Sysname DHCPR/7/DHCPR_DEBUG_RELAYPKT: Pkt Sent: send reply interface Vlan-interface22, dest IP: 255.255.255.255, chardAddr: 00e0.fc14.1601, server-group: 0 // The DHCP relay agent received a DHCP-ACK message from the DHCP server and broadcast it. debugging dhcp client Use debugging dhcp client to enable DHCP/BOOTP client debugging. Use undo debugging dhcp client to disable DHCP/BOOTP client debugging.
*0.105359 Sysname DHCPC/7/DHCPC_EVENT: Vlan-interface2: DHCPDISCOVER will be sent in 5 ms. *0.110343 Sysname DHCPC/7/DHCPC_PACKET: Vlan-interface2: Send a DHCP packet... Head: op(1); htype(ETHERNET); hlen(6); xid(0x43c130ff); ciaddr(0.0.0.0); yiaddr(0.0.0.
// The DHCP client sent a DHCP-REQUEST message, and the state of the DHCP client changed from SELECTING to REQUESTING. *0.111421 Sysname DHCPC/7/DHCPC_EVENT: Vlan-interface2: Receive a packet. *0.111421 Sysname DHCPC/7/DHCPC_PACKET: Vlan-interface2: Receive a DHCP packet... Head: op(BOOTPREPLY); htype(ETHERNET); hlen(6); xid(0x442ac688); ciaddr(0.0.0.0); yiaddr(22.0.0.2); chaddr(00e0-fc14-1601); Option: type(DHCPACK); mask(255.255.255.0); lease(86400); T1(43200); T2(75600); server(11.0.0.1); *0.
Parameters all: Specifies all types of DHCP snooping debugging. error: Specifies DHCP snooping error debugging. event: Specifies DHCP snooping event debugging. information: Specifies debugging for DHCP snooping Option 82. packet: Specifies DHCP snooping packet debugging. Usage guidelines Table 195 describes output fields and messages for the debugging dhcp-snooping error command.
Field Description DHCP snooping processed DHCP snooping entries. DHCP snooping entry type: • • • • • • • Process DHCP snooping security item, type is type, operate is operation-type. 0—No entry. 1—Static entry. 2—Temporary dynamic entry. 3—Valid dynamic entry. 7—Dynamic entry, including 2 and 3. 8—Valid entry, including 1 and 3. 9—All entries. DHCP snooping operation type: • • • • • • • • • • 0—Create. 1—Destroy. 2—Add. 3—Delete. 4—Update. 5—Age. 6—Delete based on type. 7—Delete based on interface.
*Sep 10 02:23:17:75 2007 SNOOP DHCPSP/7/PACKET: Received a DHCP OFFER packet. // DHCP snooping received a DHCP-OFFER message. *Sep 10 02:23:17:219 2007 Sysname DHCPSP/7/PACKET: Send DHCP snooping packet to VLAN (length: 350). *Sep 10 02:23:17:219 2007 Sysname DHCPSP/7/PACKET: Succeeded in sending a packet to all ports in vlan 1. // DHCP snooping forwarded the DHCP-OFFER message to all ports in VLAN 1. *Sep 10 02:23:22:078 2007 SNOOP DHCPSP/7/PACKET: Received a DHCP REQUEST packet.
Send DHCP snooping packet to ethernet port(length:350). *Sep 10 02:23:22:312 2007 Sysname DHCPSP/7/EVENT: Succeed in sending DHCP snooping packet to trusted port Ethernet1/1 in VLAN 1 // DHCP snooping forwarded the packet through trusted port Ethernet 1/1. *Sep 10 02:23:27:625 2007 SNOOP DHCPSP/7/PACKET: DHCP snooping begins to process packets on the main board. // DHCP snooping is processing the packet.
*Sep 10 02:23:29:391 2007 Sysname DHCPSP/7/EVENT: Updating DHCP snooping security item statistics, type: 3, op: 2. // DHCP snooping was updating the DHCP snooping entry statistics: the entry type is 3 (valid dynamic entry), and the operation type is 2 (add). *Sep 10 02:23:29:391 2007 Sysname DHCPSP/7/ERROR: Failed to request IPCIM to add a DHCP snooping security item (1.1.1.2 00e0-fc00-160 1). // DHCP snooping failed to notify the user information management module to add the DHCP snooping entry.
DHCPv6 debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ipv6 dhcp client Use debugging ipv6 dhcp client to enable DHCPv6 client debugging. Use undo debugging ipv6 dhcp client to disable DHCPv6 client debugging. Syntax debugging ipv6 dhcp client { all | error | event | packet | state } undo debugging ipv6 dhcp client { all | error | event | packet | state } Default DHCPv6 client debugging is disabled.
Vlan-interface2, Packet Sent: Type Information-request(11) Transaction-id 0x07e0d3 *Dec 12 09:52:12:990 2006 Sysname DHCPC6/7/PacketOption: Option Length Information CLIENTID(1) 10 DUID type: Link-layer address(3) Hardware type: 1 Link-layer address: 0x000fea23de30 ORO(6) 4 ELAPSED-TIME(8) 2 DNS-SERVERS(23) DOMAIN-LIST(24) 0 centisecond(s) // The DHCPv6 client sent an Information-request message.
// The timer for sending packets was removed. *Aug 9 14:37:40:312 2011 Sysname DHCPC6/7/DebugEvent: Try to add link-local address on interface Ethernet1/1. // The DHCPv6 client tried to add a link-local address on the interface Ethernet 1/1. *Aug 9 14:37:40:312 2011 Sysname DHCPC6/7/DebugEvent: Timer Event: Timer for sending the initial packet expired. // The timer for sending the initial packets expired.
Link-layer address: 0x000fe20a4d00 SERVERID(2) 14 DUID type: Link-layer address plus time(1) Hardware type: 6 Time: 328711988 seconds Link-layer address: 0x001143bbb78c IA_NA(3) 74 IAID: 0xf0019 T1: 300 T2: 400 IAADDR(5) 24 Address: 100::9DD8:D090:A1A6:7858 Preferred lifetime: 500 Valid lifetime: 600 STATUS_CODE(13) 30 status-code: Success(0) All addresses have been assigned. DNS_SERVERS(23) 32 2000::FF 2000::FE DOMAIN_LIST(24) 32 example.com example2.test.
Added network parameters on interface Ethernet1/1. // Network parameters were added on interface Ethernet 1/1. debugging ipv6 dhcp relay Use debugging ipv6 dhcp relay to enable DHCPv6 relay agent debugging. Use undo debugging ipv6 dhcp relay to disable DHCPv6 relay agent debugging. Syntax debugging ipv6 dhcp relay { all | error | event | packet | timer } undo debugging ipv6 dhcp relay { all | error | event | packet | timer } Default DHCPv6 relay agent debugging is disabled.
Field Description Failed to send a msg-type message for its length exceeds the maximum. Socket ID: socket-ID. The length of the message sent to the client exceeds the maximum value. Examples # Enable DHCPv6 relay agent packet debugging. When a DHCPv6 client requests an IPv6 address through a DHCPv6 relay agent, output similar to the following example is generated: debugging ipv6 dhcp relay packet *Jan 8 09:04:22:985 2008 Sysname DHCPR6/7/Packet: Packet received on interface Vlan-interface1.
Views User view Default command level 1: Monitor level Parameters all: Specifies all DHCPv6 server debugging. error: Specifies DHCPv6 server error debugging. event: Specifies DHCPv6 server event debugging. packet: Specifies DHCPv6 server packet debugging. verbose: Specifies Detailed DHCPv6 packet debugging information. Usage guidelines Table 198 describes output fields and messages for the debugging ipv6 dhcp server error command.
Examples # Enable all DHCPv6 server debugging on the DHCPv6 server.
aaa.com option SIP_SERVER_A (22), len 16 2:2::4 option SIP_SERVER_D (21), len 9 bbb.com // The DHCPv6 server sent to the client an Advertise message containing the prefix 2001:410::/48.
option SIP_SERVER_D (21), len 9 bbb.com // The DHCPv6 server sent a Reply message to the client, confirming that prefix assigned to the client is 2001:410::/48. debugging ipv6 dhcp snooping Use debugging ipv6 dhcp snooping to enable DHCPv6 snooping debugging. Use undo debugging ipv6 dhcp snooping to disable DHCPv6 snooping debugging.
Sending the DHCPv6 packet to VLAN. // The DHCPv6 packet was forwarded to the VLAN. *Aug 19 16:53:46:265 2009 Sysname DHCPSP6/7/PACKET: Sending the packet to all ports in VLAN 1. // The DHCPv6 packet was forwarded through all ports in VLAN 1.
Dial plan debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging voice dpl Use debugging voice dpl to enable dial plan debugging. Use undo debugging voice dpl to disable dial plan debugging. Syntax debugging voice dpl { all | error | general } undo debugging voice dpl { all | error | general } Default Dial plan debugging is disabled.
Field Description DPL_INTF: [GetCallInfoTab]Cannot get CallInfoTab! Perhaps, the table have been use up! The call information table was unavailable. It was possible that the table had been used up. DPL_INTF: [UpdateEntityInfoForCall]Update failed! Cannot find the entity 100! Updating failed, and voice entity 100 was not found. DPL_INTF: [GetNextEntityForCall]Entity 100 update failed! The other process will be continued! Updating voice entity 100 failed, and the other processing continued.
Field Description DPL_SUBST: [SingleTabMainProc]Found suitable substitute rule: The following number substitution rule was found for a voice subscriber line or entity: szInputFormat: ^010100$ >> szOutputFormat: 100 Input Numbering Plan: any(0x05) >> Output Numbering Plan: telex(0x04) • • • • • • DPL_SUBST: [SingleTabMainProc]The user number has been substituted successfully.
*Feb 27 12:02:11:499 2007 Sysname DPL/7/VOICE: DPL_SRCH: [GetEntity]Cannot find suitable entity! // After the subscriber dialed 01, no entity was matched. *Feb 27 12:02:11:678 2007 Sysname DPL/7/VOICE: DPL_SUBST: [MultTabMainProc]No suitable substitute rule found! The user number 010 have not been substituted. *Feb 27 12:02:11:679 2007 Sysname DPL/7/VOICE: DPL_SRCH: [GetEntity]Cannot find suitable entity! // After the subscriber dialed 010, no entity was matched.
• No number substitution rule is configured. • The calling party hears busy tones. debugging voice dpl error *Feb 27 13:40:17:330 2007 Sysname DPL/7/VOICE: DPL_SRCH: [GetEntity]Cannot find suitable entity! // No dial plan is configured, and any dialed number is unable to match an entity.
DLDP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging dldp Use debugging dldp to enable DLDP debugging. Use undo debugging dldp to disable DLDP debugging. Syntax debugging dldp { all | error | neighbor | packet | state } undo debugging dldp { all | error | neighbor | packet | state } Default DLDP debugging is disabled.
Table 202 Output from the debugging dldp error command Field Description Types of error DLDP packets: • DLDP NOT ENABLE—DLDP is not enabled. • CURRENT STATE CANN'T RECEIVE PACKET—A port in the current DLDP state cannot receive packets. Reason types of error packet • PROTOCOL ID ERROR—The protocol ID of the packet is invalid. • VERSION ID ERROR—The version ID of the packet is invalid. • INTERVAL ERROR—The interval for sending Advertisement packets carried in the packet is invalid.
Field Description DLDP packet type: DLDP Packet Type • • • • • • • • • • ERROR—Error DLDP packet. ADVERTISEMENT—Advertisement packet. PROBE—Probe packet. ECHO—Echo packet. ADVERTISEMENT-RSY—RSY packet. ADVERTISEMENT-FLUSH—Flush packet. DLDP-DOWN—Disable packet. LINK-DOWN—Linkdown packet. RECOVER-PROBE—RecoverProbe packet. RECOVER-ECHO—RecoverEcho packet. RSY tag carried in DLDP packets: Flags • • • • NO_RSY—Common Advertisement packet. RSY—RSY packet. FLUSH—Flush packet.
Add a neighbor to the neighbor table of port Ethernet1/1. Neighbor BridgeMac : 00e0-fc00-3333, Neighbor PortIndex : 35 Neighbor State : UNKNOWN, RSY Flag: RSY AgedTime: 15 seconds, EchoTime : 10 seconds. // A neighbor entry was added on Ethernet 1/1 of Device B. # Enable debugging for DLDP packets on Device B. The output in this example was created when DLDP is enabled on Device A and Device B globally and on Ethernet 1/1 of both devices.
DLSw debugging commands The output description tables in this document only contain fields and messages that require an explanation. DLSw debugging commands debugging dlsw Use debugging dlsw to enable DLSw debugging. Use undo debugging dlsw to disable DLSw debugging.
upstream: Specifies packets sent from the local SNA device. receive: Specifies packets received from the specified remote DLSw router or all remote DLSw routers. send: Specifies packets sent to the specified remote DLSw router or all remote DLSw routers. remote: Debugging for the specified remote peer or all remote peers. ip-address: IP address of the remote peer. Usage guidelines Table 206 describes output fields and messages for the debugging dlsw circuit command.
Table 210 describes output fields and messages for the debugging dlsw ethernet-backup command. Table 210 Output from the debugging dlsw ethernet-backup command Field Description DLSW_EB: Hold timeout The IWANTIT timer expired. The UGOTIT or CKT_TKN was sent. DLSW_EB: Start hold timer interval = %d. Started the timer waiting for the IWANTIT frames. DLSW_EB: There is no neighbor, master get the circuit. There is no neighbor. The primary router established the circuit. DLSW_EB: Master get the circuit.
Field Description TCP/UDP Packet sent/received via TCP/UDP. Output/Input Packet direction, where "output" or "input" corresponds to the send or receive keyword respectively. Partial data Part of the packet data. Table 214 describes output fields and messages for the debugging dlsw tcp error command. Table 214 Output from the debugging dlsw tcp error command Field Description Error An error that occurred in the TCP sub-module.
• The state transition process of the virtual circuit from DISCONNECTED state to CONNECTED state.
085be223 00 00 00 00 00 00 00 00 00 a9 15 20 05 81 00 e0 085be233 fc 04 82 02 00 04 83 00 28 12 86 ff 00 00 00 00 085be243 00 00 00 00 00 00 00 00 00 00 00 75 84 56 52 50 085be253 20 73 6f 66 74 77 61 72 65 2c 20 56 65 72 73 69 085be263 6f 6e 20 35 2e 32 30 2c 20 42 65 74 61 20 31 31 085be273 30 35 0d 0a 20 20 43 6f 70 79 72 69 67 68 74 20 085be283 28 63 29 20 31 39 39 38 2d 32 30 30 36 20 48 75 085be293 61 77 65 69 20 54 65 63 68 6e 6f 6c 6f 67 69 65 085be2a3 73 20 43 6f 2e 2c 20 4c 74 64
*0.2407610 Sysname DLSW/7/DLSw_SSP: 083398e3 31 48 00 00 00 00 00 00 00 00 00 00 00 00 03 00 083398f3 42 01 00 00 88 80 00 03 00 20 35 7b e0 65 00 00 08339903 17 38 6d fd 04 00 01 00 00 00 00 00 00 00 00 00 08339913 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08339923 00 00 00 00 00 00 00 00 *0.2407610 Sysname DLSW/7/DLSw_RCH: DLSw_RCH: Rcv 0000-1738-6dfd from:1.1.1.
085c9733 42 01 00 00 88 80 00 04 00 20 35 7b e0 65 00 00 085c9743 17 38 6d fd 04 00 02 00 00 00 00 00 00 00 00 00 085c9753 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 085c9763 00 00 00 00 00 00 00 00 *0.2416669 Sysname DLSW/7/DLSw_TCP: DLSw_TCP 1.1.1.2: send whole packet, len=72 // The CANUREACH_ex packet queried whether the local reachability entry that matches the MAC address 0020-357b-e065. The query result is FOUND. The device responds to the remote peer with an ICANREACH_ex packet. *0.
Event DLC_DL_STARTED State RESOLVE_PENDING --> CIRCUIT_PENDING. Action SSP_TYPE_ICANREACH_CS. *0.2427260 Sysname DLSW/7/DLSw_TCP: DLSw_PACKET 1.1.1.2 ( TCP Output) *0.2427460 Sysname DLSW/7/DLSw_SSP: 08041109 31 48 00 00 00 ce 00 0a 00 0f 00 00 00 00 04 00 08041119 42 01 00 00 88 00 00 04 00 20 35 7b e0 65 00 00 08041129 17 38 6d fd 04 04 02 00 00 00 00 00 00 0f 00 00 08041139 00 ce 00 0a ff ff ff ff 00 0f 00 00 00 ce 00 0a 08041149 00 00 00 00 00 00 00 00 *0.
0833b27a 00 20 35 7b e0 65 00 00 17 38 6d fd 00 03 04 04 0833b28a bf *0.2429470 Sysname DLSW/7/DLSw_CIR: DLSW FSM, Circuit ce000a: Event RCV_XIDFRAME State CIRCUIT_ESTABLISHED --> CIRCUIT_ESTABLISHED. Action LLC2_CTRL_XID_CMD. *0.
08042149 31 48 00 46 00 ce 00 0a 00 0f 00 00 00 00 07 80 08042159 42 01 00 00 88 00 00 07 00 20 35 7b e0 65 00 00 08042169 17 38 6d fd 04 04 02 00 00 00 00 00 00 0f 00 00 08042179 00 ce 00 0a 00 00 00 00 00 0f 00 00 00 ce 00 0a 08042189 00 00 00 00 00 00 00 00 32 46 05 62 e5 50 00 00 08042199 00 08 00 00 00 00 00 00 15 01 0b 70 00 05 d8 00 080421a9 00 00 00 07 00 0e 0e f4 c1 d7 d7 d5 4b e2 f6 f5 080421b9 c3 f2 c6 c2 c1 10 17 f1 16 11 01 13 00 11 f9 f4 080421c9 f0 f6 f1 f7 f0 f6 f5 c3 f2 c6
08041943 17 38 6d fd 04 04 01 00 00 00 00 00 00 0f 00 00 08041953 00 ce 00 0a 00 00 00 00 00 0f 00 00 00 ce 00 0a 08041963 00 00 00 00 00 00 00 00 32 4a 05 60 00 01 00 00 08041973 00 b7 d1 00 00 00 00 80 00 01 0b 71 00 01 09 00 08041983 00 00 00 07 00 0e 0b f4 c1 d7 d7 d5 4b e2 d5 c1 08041993 f0 f1 10 1e 00 1d 11 0c 08 04 f0 f5 f0 f1 f0 f1 080419a3 09 06 e6 c1 d5 e6 c1 d9 c5 09 08 e4 e2 c5 d9 f0 080419b3 40 40 *0.2433890 Sysname DLSW/7/DLSw_CIR: Circuit ce000a Receive a Rpt FCI *0.
080429d9 c3 f2 c6 c2 c1 10 17 f1 16 11 01 13 00 11 f9 f4 080429e9 f0 f6 f1 f7 f0 f6 f5 c3 f2 c6 c2 c1 40 40 *0.2436300 Sysname DLSW/7/DLSw_TCP: DLSw_TCP 1.1.1.2: send whole packet, len=142 *0.
*0.2439110 Sysname DLSW/7/DLSw_CIR: Circuit ce000a Receive a Rpt FCI *0.
*0.2441120 Sysname DLSW/7/DLSw_DLC: DLSw_DLC Packet Upstream, Packet Len = 60, Partial data as follows: 080439e0 00 00 17 38 6d fd 00 20 35 7b e0 65 00 03 04 04 080439f0 7f 02 f5 60 01 e5 f5 a0 00 00 00 7a 00 00 00 00 08043a00 01 e5 f5 70 01 d9 8f c0 00 0c 09 84 01 e5 f5 50 08043a10 00 00 00 2c e1 e5 f0 01 01 e5 f5 94 *0.2441520 Sysname DLSW/7/DLSw_CIR: DLSW FSM, Circuit ce000a: Event DLC_CONTACTED_SABME State CIRCUIT_ESTABLISHED --> CONNECT_PENDING. Action SSP_TYPE_CONTACT. *0.
transited from CONNECT_PENDING to CONNECTED, and the UA packet was sent to the local SNA host. The DLSw virtual circuit is successfully established. # Enable debugging for the DLSw SAP address-based filtering. Output similar to the following example is generated when you configure DLSw SAP address-based filtering on the router connected to the terminal. debugging dlsw filter *Mar 9 16:28:38:088 2011 Sysname DLSW/7/DLSw filter: DLSw filter: The packet to 1.1.1.
DLSW_EB: LLC circuit timer with neighbor 000f.e21d.a5fb stop *Mar 9 16:04:48:679 2011 Sysname DLSW/7/DLSw_EB: DLSw_EB: Received UA frame from GigabitEthernet0/0 *Mar 9 16:04:48:779 2011 Sysname DLSW/7/DLSw_EB: DLSw_EB: SABMESENT -> CONNECT *Mar 9 16:04:48:930 2011 Sysname DLSW/7/DLSw_EB: DLSw_EB: Sending DN frame from 00f0.47b8.a0dc to 00f0.47b8.
Field Description LLC2 FSM event: event State machine event of the LLC2 virtual circuit. LLC2 FSM action: action Action taken by the DLSw virtual circuit state machine for the event. Table 218 describes output fields and messages for the debugging llc2 error command. Table 218 Output from the debugging llc2 error command Field Description Error An error that occurred in the LLCP sub-module.
*0.191649 Sysname LLC2/7/LLC2_PKT: LLC2_PACKET Ethernet1/0 (Output) U frame *0.191649 Sysname LLC2/7/LLC2_PKT: 082f9ada 00 04 ac de 07 a6 00 00 e8 1c b6 bf 00 03 04 04 082f9aea bf *0.191776 Sysname LLC2/7/LLC2_PKT: LLC2_PACKET Ethernet0/0 (Input) U frame *0.
*0.192580 Sysname LLC2/7/LLC2_PKT: LLC2_PACKET Ethernet1/0 (Output) U frame *0.192780 Sysname LLC2/7/LLC2_PKT: 082fe4fa 00 04 ac de 07 a6 00 00 e8 1c b6 bf 00 4d 04 04 082fe50a bf 32 4a 05 60 00 01 00 00 00 b7 d1 00 00 00 00 082fe51a 80 15 01 0b 41 00 01 09 00 00 00 00 07 00 0e 0b 082fe52a f4 c1 d7 d7 d5 4b e2 d5 c1 f0 f1 10 1e 00 1d 11 082fe53a 0c 08 04 f0 f5 f0 f1 f0 f1 09 06 e6 c1 d5 e6 c1 082fe54a d9 c5 09 08 e4 e2 c5 d9 f0 40 40 *0.
*0.195190 Sysname LLC2/7/LLC2_CIR: Nr = 0 *0.195590 Sysname LLC2/7/LLC2_CIR: LLC2 FSM event: Receive an RR PDU(CMD&POLL) LLC2 FSM action: SEND_RR_RSP(F=1) // The output is the LLC2 debugging information output after the DLSw virtual circuit is successfully established. SDLC debugging commands debugging sdlc Use debugging sdlc to enable SDLC debugging. Use undo debugging sdlc to disable SDLC debugging.
Field Description State: state State transition of the state machine of the SDLC virtual circuit. Table 221 describes output fields and messages for the debugging sdlc packet command. Table 221 Output from the debugging sdlc packet command Field Description interface-type interface-number (Output / Input) The local interface on which the packet is sent out/received and the packet direction. SDLC PDU: frame type Packet type. Frame head The first two bytes of the packet.
// The device received an XID packet from the terminal. The state of the SDLC virtual circuit transited from SDLC_DISCONNECT to SDLC_XIDSTOP. The packet was sent to the DLSw module, which then passed the packet to the remote endpoint. *0.4071066 Sysname SDLC/7/debug2: SDLC: Event:SDLC_SEND_NULL_XID_REQUEST Action:SDLC_SEND_NULL_XID SDLC_XIDSTOP->SDLC_XIDSENT *0.4071270 Sysname SDLC/7/debug2: SDLC PDU: SDLC_XID Send to Serial2/0 c1 bf *0.
086b28e2 32 4a 05 60 00 01 00 00 00 b5 d1 00 00 00 00 80 2J.`............ *0.4073290 Sysname SDLC/7/debug2: 086b28f2 00 01 0b 30 00 01 09 00 20 00 00 07 00 0e 0b f4 ...0............ *0.4073500 Sysname SDLC/7/debug2: 086b2902 c1 d7 d7 d5 4b e2 d5 c1 f0 f1 10 1e 00 1d 11 0c ....K........... *0.4073700 Sysname SDLC/7/debug2: 086b2912 08 04 f0 f5 f0 f1 f0 f1 09 06 e6 c1 d5 e6 c1 d9 ................ *0.4073700 Sysname SDLC/7/debug2: 086b2922 ........ *0.
0839a8c2 c1 d7 d7 d5 4b e2 d5 c1 f0 f1 10 1e 00 1d 11 0c ....K........... *0.4075920 Sysname SDLC/7/debug2: 0839a8d2 08 04 f0 f5 f0 f1 f0 f1 09 06 e6 c1 d5 e6 c1 d9 ................ *0.4076120 Sysname SDLC/7/debug2: 0839a8e2 ........ *0.4076320 Sysname SDLC/7/debug2: SDLC: Event:SDLC_RECEIVE_FULL_XID Action:SDLC_SEND_FULL_XID_REMOTE SDLC_XIDSENT->SDLC_XIDSTOP // The output shows the XID packets exchange process between the host and the terminal. *0.
DNS debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging dns Use debugging dns to enable DNS debugging. Use undo debugging dns to disable DNS debugging. Syntax debugging dns undo debugging dns Default DNS debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 222 describes output fields and messages for the debugging dns command.
Field Description The answers for query name domain-name (type: type, TTL: num seconds): result-desc. The answers for query name domain-name (type: type): result-desc. The name resolution result for domain name domain-name has been obtained from the DNS reply packet. The query type can be NAPTR or SRV. The name resolution result for domain name domain-name has been obtained from the DNS reply packet. The query type can be A or AAAA. The TTL is not recorded for type A and AAAA queries.
Trying DNS server (192.168.10.1) *Feb 9 17:21:40:719 2010 H3C DNS/7/dns: There is no resolve result matching the query name sample.com in the local dynamic cache. // DNS did not find a resolution result for domain name sample.com in the local dynamic cache. *Feb 9 17:21:40:719 2010 H3C DNS/7/dns: Succeeded in making a DNS query packet for name sample.com. // DNS constructed a DNS query packet for resolving domain name sample.com. *Feb 9 17:21:40:735 2010 H3C DNS/7/dns: Send the packet to DNS server 192.
packet: Specifies DNS proxy packet debugging. error: Specifies DNS proxy error debugging. Usage guidelines Table 223 describes output fields and messages for the debugging dns proxy event command. Table 223 Output from the debugging dns proxy event command Field Description DNS proxy starts searching information locally according to the client's query. Operation code of the query: Begin to find query information locally. Query type: query-type • 0—Standard query. • 1—Inverse query.
debugging dns proxy all terminal debugging terminal monitor Output similar to the following messages is generated on the DNS proxy when the client pings www.aabbcc.com: *Apr 19 14:07:29:554 2007 Syaname DNS/7/DNS_Proxy: Receive a DNS query from 192.168.5.212, port: 3931, trans ID: 1. // DNS received a DNS request from the client at 192.168.5.212. *Apr 19 14:07:29:554 2007 Sysname DNS/7/DNS_Proxy: Begin to find query information locally.
418
DDNS debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ddns Use debugging ddns to enable DDNS debugging. Use undo debugging ddns to disable DDNS debugging. Syntax debugging ddns undo debugging ddns Default DDNS debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 225 describes output fields and messages for the debugging ddns command.
Field Description Interface is not ready. The interface is not ready to initiate the DDNS update. The interface is either down or not configured with an IP address. Invalid server name. The host name of the DDNS server is invalid. The system does not start domain name translation. Failed to send connection request, with error code error-code. The system failed to establish the update request connection to the DDNS server. The error code is error-code. Failed to connect server.
system-view [Sysname] ddns policy 3322.org [Sysname-ddns-policy-3322.org] url Output similar to the following messages is generated: http://steven:nevets@members.3322.org/dyndns/update?system=dyndns&hostname=&myip=< a> [Sysname-ddns-policy-3322.org] interval 0 0 15 [Sysname-ddns-policy-3322.org] quit [Sysname] interface ethernet 1/1 [Sysname-Ethernet1/1] ddns apply policy 3322.org fqdn whatever.3322.
DDNS event (Interface: Ethernet1/1, policy: oray.cn): Starting DDNS update for the 1st time. // The device was trying to connect to the DDNS server to initiate the first DDNS update. *Jun 12 17:52:04:733 2008 Sysname DDNS/7/Debug: DDNS server reply (Interface: Ethernet1/1, policy: oray.cn): 220 Oray.cn DHRP server ready // The device connected to the DDNS server and received the welcome information. *Jun 12 17:52:04:733 2008 Sysname DDNS/7/Debug: DDNS event (Interface: Ethernet1/1, policy: oray.
DVPN debugging commands debugging dvpn Use debugging dvpn to enable DVPN debugging. Use undo debugging dvpn to disable DVPN debugging. Syntax debugging dvpn { all | error | event | packet } undo debugging dvpn { all | error | event | packet } Default DVPN debugging is disabled. Views User view Default command level 1: Monitor level Parameters all: All types of DVPN debugging. error: DVPN error debugging. event: DVPN event debugging. packet: DVPN packet debugging.
*Jul 28 16:44:07:985 2010 Spoke1 DVPN/7/EVENT: Initialized session 10.0.1.1. // DVPN initialized the session to peer 10.0.1.1. *Jul 28 16:44:08:000 2010 Spoke1 DVPN/7/EVENT: Created KEEPALIVE timer for session 10.0.1.1. // DVPN started a keepalive timer for session 10.0.1.1. # Enable DVPN packet debugging.
Before encapsulation: from 192.168.1.1 to 192.168.3.1. // The data packet before DVPN encapsulation is from 192.168.1.1 to 192.168.3.1. *Jul 29 15:29:53:547 2010 Hub-1 DVPN/7/PACKET: After encapsulation: from 202.10.19.71 to 202.10.19.73. // The data packet after DVPN encapsulation is from 202.10.19.71 to 202.10.19.73. *Jul 29 15:29:53:547 2010 Hub-1 DVPN/7/PACKET: Received a DVPN GRE packet. // DVPN received a DVPN packet encapsulated in GRE.
Field Description Sent a packet (length bytes) to IP ip-address port port VRF Index vrf-index successfully. The vrf-index argument indicates the index of a VPN instance. A value of 0 for the vft-index indicates the public network. Examples # Enable VAM client error debugging on the VAM client.
Views User view Default command level 1: Monitor level Parameters all: All types of VAM server debugging. error: VAM server error debugging. event: VAM server event debugging. packet: VAM server packet debugging. Usage guidelines Table 227 describes output fields and messages for the debugging vam server event command.
debugging vam server event *Jul 28 15:34:22:312 2010 Mainserver VAM/7/EVENT: VAM_Server: Created client aging timer successfully. *Jul 28 15:34:22:312 2010 Mainserver VAM/7/EVENT: VAM_Server: Received a packet of type 1. *Jul 28 15:34:22:312 2010 Mainserver VAM/7/EVENT: VAM_Server: Received connect request successfully. *Jul 28 15:34:22:312 2010 Mainserver VAM/7/EVENT: VAM_Server: Received server FSM event of type 1.
Received authentication success message from AAA. *Jul 28 15:34:22:484 2010 Mainserver VAM/7/EVENT: VAM_Server: Received server FSM event of type 9. *Jul 28 15:34:22:484 2010 Mainserver VAM/7/EVENT: VAM_Server: State changed on Server. *Jul 28 15:34:22:500 2010 Mainserver VAM/7/EVENT: VAM_Server: Sent account request to AAA module successfully. *Jul 28 15:34:22:500 2010 Mainserver VAM/7/EVENT: VAM_Server: Received accounting success message from AAA.
