HP Comware 5 Comware 5 Debug Manual Volume 2 Part number: 5998-5837
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 Ethernet interface debugging commands ······················································································································ 1 debugging ethernet packet ····································································································································· 1 Ethernet link aggregation debugging commands ········································································································ 4 debugging link-aggregation all
debugging debugging debugging debugging fr inarp ················································································································································ 77 fr ipc ···················································································································································· 78 fr packet·············································································································································· 79
IPC debugging commands········································································································································· 140 debugging ipc packet ········································································································································· 140 debugging ipc link ·············································································································································· 141 debugging ipc error
IRF debugging commands ········································································································································· 257 debugging ha ······················································································································································ 257 debugging stm all················································································································································ 259 debugging stm
Ethernet interface debugging commands The Ethernet interface module name is identified as "ETH" in debugging messages. The output description tables in this document only contain fields and messages that require an explanation. debugging ethernet packet Use debugging ethernet packet to enable Ethernet packet debugging. Use undo debugging ethernet packet to disable Ethernet packet debugging.
Field Description prototype Ethernet protocol type. src_addr Source MAC address. dst_addr Destination MAC address. length Ethernet frame length. eth_l2_send:Send an eth L2-protocol packet Ethernet sent a Layer 2 protocol frame. port index Port index of the Layer 2 protocol Ethernet frame. src_eth_addr Source MAC address of the Ethernet frame. dst_eth_addr Destination MAC address of the frame. Examples # Enable Ethernet packet debugging.
%Dec 8 11:24:11:712 2006 Sysname MSTP/2/STPSTART:STP is now enabled on the device. *Dec 8 11:24:11:713 2006 Sysname ETH/7/eth_l2_send:Send an eth L2-protocol packet,port index: 983043, prototype: 0003, src_eth_addr : 00e0-fc12-3456, dst_eth_addr : 0180-c200-0000 // Ethernet sent a Layer 2 protocol frame. # Enable Ethernet packet debugging. Output similar to the following example is generated when you ping the directly connected device under the following conditions: • An ACL is created.
Ethernet link aggregation debugging commands The Ethernet Link Aggregation module name is identified as "LAGG" in debugging messages. The output description tables in this document only contain fields and messages that require an explanation. debugging link-aggregation all Use debugging link-aggregation all to enable all types of debugging for link aggregation. Use undo debugging link-aggregation all to disable all types of debugging for link aggregation.
debugging link-aggregation error *Nov 2 15:51:21:15 2007 Sysname LAGG/7/LAGG_DEBUG: ERROR.203.0-14788557: Send configuration change message of member port failed // LAGG failed to send member port configuration change messages. debugging link-aggregation event Use debugging link-aggregation event to enable link aggregation event debugging. Use undo debugging link-aggregation event to disable link aggregation event debugging.
Views User view Default command level 1: Monitor level Parameters actorchurn: Specifies debugging for the actor-churn state machine. mux: Specifies debugging for the mux state machine. partnerchurn: Specifies debugging for the partner-churn state machine. ptx: Specifies debugging for the PTX state machine. rx: Specifies debugging for the RX state machine. all: Specifies debugging for all state machines.
Table 2 Output from the debugging link-aggregation lacp fsm command Field Description state1-->state2 State transition of a state machine. state1 indicates the state before transition. state2 indicates the state after transition. The possible states include: • BEGIN—The state machine was created, but it was in inactive state. • INITIALIZE—The RX state machine completed initialization. • PORT_DISABLED—The RX state machine was in port unselected and out of synchronization state.
Field Description conditions Events that trigger state transitions. The possible events include: • • • • • • • • • • • • • • • • • • • • • • • • Begin_False—The state machine had been started. Begin_True—The state machine started. UCT—Unconditional transition. Port_Moved_True—A Port Move event occurred on the port. Port_Moved_False—A Port Move event was completed on the port. Port_Enabled—The port became available. Port_Disabled—The port became unavailable. LACP_Enabled—LACP was enabled on the port.
Syntax debugging link-aggregation lacp packet { all | { receive | send } * } [ interface-list ] undo debugging link-aggregation lacp packet { all | { receive | send } * } [ interface-list ] Default LACPDU debugging is disabled on ports. Views User view Default command level 1: Monitor level Parameters all: Specifies debugging for sent and received LACPDU. send: Specifies debugging for sent LACPDUs. receive: Specifies debugging for received LACPDUs.
Field Description Partner Remote port information carried in the LACPDUs: • • • • • • • • Collector type valued 2—Remote port information. len—Information length. sys-pri—LACP system priority of the remote end (the partner) sys-mac—System MAC address of the partner. key—Operational key of the remote port. pri—LACP priority of the remote port. port-index—Remote port number. state—Current LACP state flag of the remote port. Collector field in an LACPDU: • type valued 3—Collector field information.
Ethernet OAM debugging commands The output description tables in this document only contain fields and messages that require an explanation. The Ethernet OAM module name is identified as "ETHOAM" in debugging messages. debugging oam Use debugging oam to enable Ethernet OAM debugging. Use undo debugging oam to disable Ethernet OAM debugging.
Table 4 Output from the debugging oam critical-event command a. Field b. Description c. OAM Port XXX: XXX d. A critical link event occurred on an occurs Ethernet OAM-enabled interface. Table 2 describes output fields and messages for the debugging oam error command. Table 5 Output from the debugging oam error command a. Field b. Description c. OAM Port XXX: XXX d. Errors occurred on an Ethernet OAM-enabled interface. Table 3 describes output fields and messages for the debugging oam fsm command.
# Enable the debugging for Ethernet OAM errors on Ethernet 1/1. The output in this example was created when Ethernet OAM is enabled on Ethernet 1/1. debugging oam error interface ethernet 1/1 *0.10030698 Sysname ETHOAM/8/EncapOam: OAM Port Ethernet1/1: Encapsulating OAMPDU fails. // Encapsulating OAMPDU failed. # Enable the debugging for Ethernet OAM state machines on Ethernet 1/1.
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: 50 // The packet length is 50.
EtoPPP and EtoFR debugging commands The EtoPPP and EtoFR module name is identified as "ETOTDM" in debugging messages. The output description tables in this document only contain fields and messages that require an explanation. EtoPPP debugging commands debugging etoppp Use debugging etoppp to enable a type of EtoPPP debugging on the specified interface or globally if no interface is specified.
Field Description Receive a arp packet, interface : [string], opertype: [string], Src IP: [string], Des IP: [string] An ARP packet was received on the displayed interface. The operation code for the packet and the source and destination IP addresses of the packet are displayed. Send a ip packet, interface : [string] An IP packet was sent out the displayed interface.
# Enable EtoPPP event debugging.
Table 12 Output from the debugging etofr packet command Field Description Receive a ip packet, interface : [string] An IP packet was received on the displayed interface. Receive a arp packet, interface : [string], opertype: [string], Src IP: [string], Des IP: [string] An ARP packet was received on the displayed interface. The operation code for the packet and the source and destination IP addresses of the packet are displayed.
*Mar 10 18:41:39:742 2008 Router ETOTDM/7/etotdm_send_ip:Send a ip packet, interface : Ethernet1/1 # Enable EtoFR event debugging to observe EtoFR event debugging output. Output similar to the following example is generated when an EtoFR translation entry is created to map Ethernet 1/1 to FR-enabled interface Serial 2/0.
FC debugging commands The output description tables in this document only contain fields and messages that require an explanation. FC interface debugging commands The FC interface module name is identified as "FCLINK" in debugging messages. debugging fc link Use debugging fc link to enable FC link debugging. Use undo debugging fc link to disable FC link debugging.
Table 15 Output from the debugging fc link elp command Field Description Encapsulate request frame FCLINK encapsulated an ELP request frame. Select parameters result: The two ports names are equal During the ELP negotiation, the port names are the same. Select parameters result: The two switches names are equal During the ELP negotiation, the switch names are the same. Concurrent process, WWN compared Result Both ends initiated the ELP negotiation at the same time.
Table 19 Output from the debugging fc link evfp command Field Description WWN comparison result for concurrent processes on interface interface-name: result-code Interface interface-name performed the concurrent process processing, and the WWN comparison result was result-code. The result-code values include: • 1—The WWN of the local end is greater than the peer end. • 0—The WWN of the local end is the same as the peer end. • -1—The WWN of the local end is smaller than the peer end.
*Sep 25 10:10:35:328 2009 Sysname FCLINK/7/ELP: Select parameters result: Negotiatio n succeeded, interface Fc0/3/0, VSAN 1. // ELP successfully negotiated parameters. *Sep 25 10:10:35:328 2009 Sysname FCLINK/7/ELP: Send ACC frame, interface Fc0/3/0, V SAN 1. // ELP sent ACC frames out interface FC 0/3/0 and VSAN 1 to which the interface belongs. %Sep 25 10:10:35:343 2009 Sysname IFNET/4/UPDOWN: Line protocol on the interface Fc0/3/0 is UP // The link layer state of interface FC 0/3/0 is UP.
// FCLINK received upstream interface events on interface FC 0/3/0 (command 0 indicates that the interface is UP). *Nov 12 10:19:41:875 2009 Sysname FCLINK/7/EVENT: Receive the success of elp negotia tion in Init state and change to E state, interface Fc0/3/0, VSAN 1 . // Interface FC 0/3/0 in VSAN 1 received the success of ELP negotiation in the INIT state, and changed to the E state. *Nov 12 10:19:41:891 2009 Sysname FCLINK/7/EVENT: Receive the success of ESC negotia tion in E state, interface Fc0/3/0.
// Interface FC 0/3/0 received ACK events. *Nov 25 11:05:59:750 2009 Sysname FCLINK/7/EVFP: Received EVFP_COMMIT ACC frames, interface Fc0/3/0. // Interface FC 0/3/0 received EVFP_COMMIT ACC frames. # Enable packet debugging. Output similar to the following example is generated when the following conditions exist: • The FC device is started. • Both ends of a link go up physically.
c0/3/0 join queue successfully. // Packets received on interface FC 0/3/0 were successfully assigned to the input packet queue. # Enable timer debugging. Output similar to the following example is generated when the following conditions exist: • The FC device is started. • Both ends of a link go up physically. debugging fc link timer %Nov 12 10:57:37:360 2009 Sysname IFNET/4/LINK UPDOWN: Fc0/3/0: link status is UP // Interface FC 0/3/0 went UP physically.
Examples # Enable debugging for FC login and logout. Output similar to the following example is generated when an N_Port connects to a VFC interface and initiates FLogin: debugging fc link login-out *Jan 22 14:44:05:031 2010 Sysname FCLINK/7/LOGINOUT: Received a FLOGI packet from interface Vfc1. // Interface VFC 1 received a FLOGI packet.
Default The debugging for the fabric configuration module is disabled. Views User view Default command level 1: Monitor level Parameters all: All types of debugging. error: Error debugging. event: Event debugging. packet: Packet debugging. timer: Timer debugging. vsan vsan-id: Enables debugging for the specified VSAN. The vsan-id argument ranges from 1 to 3839. If you do not specify a VSAN, this command enables debugging for all VSANs.
Field Description Processed event-id event in state-id state. Fabric processed event-id event in state-id state. The values of state-id include: • 0—INIT. • 1—BF. • 2—RCF. • 3—EFP. • 4—PRINCIPAL. • 5—REQUEST. • 6—SUBORDINATE. • 7—STATIC. The values of event-id include: • 0—E_Port up event. • 1—PSST timer timeout. • 2—Receiving DIA request frames. • 3—Receiving RDI request frames. • 4—Receiving SW_RJT responses to RDI request frames. • 5—Receiving SW_ACC responses to RDI request frames.
Field Description Notified fabric event event-id. Fabric notified event event-id of the fabric module. The values of event-id include: • 0x01—WWN change event. • 0x02—Domain ID change event. • 0x04—F_S_TOV change event. • 0x08—D_S_TOV change event. • 0x10—E_D_TOV change event. • 0x20—R_A_TOV change event. • 0x40—Fabric name change event. Exchange exch-id notified event event-id, with flag: flag. The exchange notified whether the Sequence was successfully sent.
Field Description pkttype timer timed out, exch: exch-id, interface: interface-name. The timer for requests of the pkttype type timed out. The values of pkttype include BF, RCF, EFP, RDI, and DIA. exch-id indicates the Exchange ID, and interface-name indicates the outgoing interface of the requests. Examples # Enable error debugging for the fabric configuration module in all VSANs.
*Jan 22 11:04:45:031 2010 Sysname FABRIC/7/EVT:(VSAN 1): Fabric Name changed from 00:00:00:00:00:00:00:00 to 48:33:43:2d:46:43:0a:0c. *Jan 22 11:04:45:047 2010 Sysname FABRIC/7/EVT:(VSAN 1): Notified fabric event 0x40. // The fabric name changed from 00:00:00:00:00:00:00:00 to 48:33:43:2d:46:43:0a:0c, and the fabric name change event was notified. *Jan 22 11:04:45:063 2010 Sysname FABRIC/7/EVT:(VSAN 1): Running domain ID changed from 0 to 0x1.
debugging fc name-service Use debugging fc name-service to enable debugging for the FC name service. Use undo debugging fc name-service to disable debugging for the FC name service. Syntax debugging fc name-service { all | error | event | packet } [ vsan vsan-id ] undo debugging fc name-service { all | error | event | packet } [ vsan vsan-id ] Default Debugging is disabled for the FC name service. Views User view Default command level 1: Monitor level Parameters all: All types of debugging.
in 2 succeeded. // ESS negotiation succeeded. # Enable packet debugging for the FC name service in all VSANs. Output similar to the following example is generated when the name service packets are being transmitted or received: debugging fc name-service packet *Feb 22 11:17:21:438 2010 Sysname FCGS/7/PACKET:(VSAN 1): Received GPT_ID frame from Name Server. // FCGS received the GPT_ID packets from the name server.
Usage guidelines Table 11 describes the output fields and messages for the debugging fc exchange error command. Table 25 Output from the debugging fc exchange error command Field Description Regist ExchmanagerID or protocol type is invalid Exchange manager ID or protocol type is invalid. When creating a new exchange, no free XID is available, Manager is Manager-type No free XID is available when the exchange manager creates a new exchange.
*Nov 12 16:39:15:437 2009 Sysname FCEXCH/7/PACKET: Exchange transfer sequence initia tive. // FCEXCH transferred the Sequence initiative. *Nov 12 16:39:15:437 2009 Sysname FCEXCH/7/PACKET: Receive ACK_0 packet,the header: R_CTL : 0xc1, D_ID : 0xfffffd CS_CTL: 0x00, S_ID : 0xfffffd Type F_CTL : 0xe10000 : 0x00, Seq_ID: 0x01, DF_CTL: 0x00, Seq_Cnt: 0x0001 OX_ID : 0xf041, RX_ID : 0xf0d0 Parameter Field: 0x00000000 // Detailed fields in the header of the received ACK packet.
debugging fc forward Use debugging fc forward to enable debugging for FC forwarding. Use undo debugging fc forward to disable debugging for FC forwarding. Syntax debugging fc forward { all | error | fib | packet } [ vsan vsan-id ] undo debugging fc forward { all | error | fib | packet } [ vsan vsan-id ] Default Debugging is disabled for FC forwarding. Views User view Default command level 1: Monitor level Parameters all: All types of debugging. error: Error debugging.
debugging fc rm Use debugging fc rm to enable debugging for the FC route management module. Use undo debugging fc rm to disable debugging for the FC route management module. Syntax debugging fc rm { all | fib | im | static | table | timer } [ vsan vsan-id ] undo debugging fc rm { all | fib | im | static | table | timer } [ vsan vsan-id ] Default Debugging is disabled for the FC route management module. Views User view Default command level 1: Monitor level Parameters all: All types of debugging.
%Mar 10 11:35:05:875 2010 Sysname IFNET/3/LINK_UPDOWN: Fc0/1/0 link status is UP. *Mar 10 11:35:06:234 2010 Sysname FCRM/7/IM: (VSAN 1): Added Fc0/1/0 to interface database. // FCRM added interface FC 0/1/0 to the interface database. # Enable timer debugging for the FC route management module in all VSANs.
*Nov 24 17:49:21:719 2009 Sysname FCVSAN/7/EVENT: Notify the VSAN 2 deletion event // FCVSAN notified the event of deleting VSAN 2. *Nov 24 17:49:21:719 2009 Sysname FCVSAN/7/EVENT: Notify the driver of the VSAN 2 de letion event // FCVSAN notified the driver of the event of deleting VSAN 2. *Nov 24 17:49:21:719 2009 Sysname FCVSAN/7/EVENT: VSAN 2 was deleted successfully // VSAN 2 was deleted successfully.
Table 28 Output from the debugging bundle error command Field Description Failed to execute the operation: operation on bundle bundle-id. BNDL failed to execute operation on FC link bundle interface bundle-id. The operation can be one of the following: • create—Creating a link bundle. • modify—Modifying the selected member interfaces in the link bundle. • delete—Deleting the link bundle. Table 15 describes the output fields and messages for the debugging bundle event command.
The local end has not been assigned to the link bundle. • debugging bundle event fc-bundle *Nov 12 11:20:48:937 2009 Sysname BNDL/7/Event: The member interface Fc0/2/1 in bundle 1 is blocked. // Member interface FC 0/2/1 in FC link bundle 1 was blocked. *Nov 12 11:20:48:937 2009 Sysname BNDL/7/Event: The interface Fc0/2/1 joins in bundle 1. The attributes of Fc0/2/1: speed = 4000000kbps, linkState = DOWN, restriction = 0, DrvMaxNum = 4294967295. // Interface FC 0/2/1 joined FC link bundle 1.
Views User view Default command level 1: Monitor level Usage guidelines Table 16 describes output fields and messages for the debugging fc ping command Table 30 Output from the debugging fc ping command Field Description Failed to set the option of exchange. FCPING failed to set attributes for the exchange. Examples # Enable FC ping debugging.
FCoE debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging fcoe Use debugging fcoe to enable debugging for FCoE. Use undo debugging fcoe to disable debugging for FCoE.
Table 1 describes the output fields and messages for the debugging fcoe error command. Table 31 Output from the debugging fcoe error command − Field − Description − Failed to check flow for a too short period − FCoE failed to check the flow because the current update time is no later than the last update time. Table 2 describes the output fields and messages for the debugging fcoe packet fcm command.
− Field − T: Descriptor Type Descriptor Length L: − Description − The descriptor type is Descriptor Type, and the descriptor length is Descriptor Length. − The Descriptor Type values include: • 0x01—Priority. • 0x02—MAC address. • 0x03—FC-MAP. • 0x04—Name_Identifier. • 0x05—Fabric. • 0x06—Maximum packet size. • 0x07—FLOGI. • 0x09—LOGO. • 0x0B—Vx_Port. • 0x0C—FKA_ADV_Period. − Max_FCoE_Size is − Maximum packet size. − VF_ID − VSAN_ID. − Version − FIP frame version.
# Enable encapsulated FC packet debugging for FCoE. Output similar to the following example is generated when an N_Port initiates FLOGIN under the following conditions: • The N_Port connects to a VFC interface. • FIP is disabled. debugging fcoe packet fcm %Jan 22 15:44:14:156 2010 Sysname IFNET/4/LINK UPDOWN: Vfc1: link status is UP. *Jan 22 15:44:14:156 2010 Sysname FCOE/7/Packet FCM: Input FCoE packet to FCoE queue successfully. // FCoE packets were successfully assigned to the FCoE queue.
*Jan 22 15:09:58:953 2010 Sysname FCOE/7/Packet FIP: T: 1 *Jan 22 15:09:58:953 2010 Sysname FCOE/7/Packet FIP: Priority: 128 *Jan 22 15:09:58:953 2010 Sysname FCOE/7/Packet FIP: MAC Descriptor: L: 1 *Jan 22 15:09:58:953 2010 Sysname FCOE/7/Packet FIP: T: 2 *Jan 22 15:09:58:953 2010 Sysname FCOE/7/Packet FIP: MAC address: 0000-560b-0006 *Jan 22 15:09:58:953 2010 Sysname FCOE/7/Packet FIP: *Jan 22 15:09:58:953 2010 Sysname FCOE/7/Packet FIP: *Jan 22 15:09:58:953 2010 Sysname FCOE/7/Packet FIP: *Jan
Default Debugging for firewall is disabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of debugging for firewall. eff: Specifies debugging for Ethernet frame filtering. Only single-core device supports this keyword. dlsw: Specifies debugging for DLSw. Only single-core device supports this keyword. fragments-inspect: Specifies debugging for fragment inspection. Only single-core device supports this keyword.
Field Description OutBound Filters packets to be sent. List listNumber: RuleNumber ACL listNumber and matching rule RuleNumber used in packet filtering. deny The action for the matching packets is deny. permit The action for the matching packets is permit. icmp The protocol is ICMP. interface Interface that filters packets. Table 4 describes output fields and messages for the debugging firewall icmp command.
// Firewall found a matching fragment inspection entry 0x9465044 with fragment ID 57687 for the received fragment. *Mar 18 14:28:43:746 2006 Sysname FILTER/7/FRAG_PKT: Non-Initial fragment 20.0.0.2 20.0.0.3 frag-ID 57687 protocol tcp 44 bytes from interface GigabitEthernet0/1 // Firewall received a non-initial fragment on GigabitEthernet 0/1. *Mar 18 14:28:43:778 2006 Sysname FILTER/7/FRAG_DELETE: Delete fragments inspection entry 0x9465044 bucket 343 protocol TCP address 20.0.0.2:1055 - 20.0.0.
Default command level 1: Monitor level Parameters tcp Specifies debugging for TCP packet filtering. udp: Specifies debugging for UDP packet filtering. icmp: Specifies debugging for ICMP packet filtering. others: Specifies debugging for packet filtering of other protocols except ICMP, TCP, and UDP. all: Specifies all types of debugging for packet filtering. acl acl-number: Specifies an ACL for packet filtering. The acl-number argument refers to an ACL number in the range of 2000 to 3999.
Thread 29, tcp packet is permitted from trust to untrust: (192.168.144.2 1618)->(10.0.144.1 21), 48 bytes, ACL none. // Packet filter permitted a TCP packets from trust zone to untrust zone. No ACL is applied between the zones. # Enable debugging for UDP packet filtering on the device with firewall enabled. debugging firewall packet-filter udp *May 31 12:19:39:710 2006 Sysname DPFILTER/7/debug: Thread 15, udp packet is permitted from trust to untrust: (192.168.144.2 1619)->(10.0.144.
Usage guidelines NOTE: Support for this command depends on the device model. Table 8 describes output fields and messages for the debugging firewall ipv6 icmpv6 command. Table 41 Output from the debugging firewall ipv6 icmpv6 command (only for single-core devices) Field Description inbound Filters incoming packets. outbound Filters packets to be sent. Icmpv6 The protocol is ICMPv6. interface Interface that filters packets. ACL6 IPv6 ACL used to filter packets.
Field Description interface Interface that filter packets. ACL6 IPv6 ACL used to filter packets. Table 12 describes output fields and messages for the debugging firewall ipv6 tcp command. Table 45 Output from the debugging firewall ipv6 tcp command (only for single-core devices) Field Description inbound Inbound direction, indicating to filter incoming packets. outbound Outbound direction, indicating to filter sent packets. tcp The protocol is TCP. interface Interface to filter packets.
Field Description outbound Outbound direction, indicating to filter sent packets. udp The protocol is UDP. interface Interface that filters packets. ACL6 IPv6 ACL used to filter packets. Examples # Enable IPv6 firewall. Configure packet filtering to deny incoming ICMPv6, TCP, UDP, and GRE packets from passing through GigabitEthernet 1/1.
debugging firewall ipv6 others *Oct 13 14:52:23:806 2008 Sysname FLT6/7/debug: The inbound packet is denied on the interface GigabitEthernet1/1: (5600::12)->(5000::1), 60 bytes, ACL6 3000. // IP-v6 packet filter used IPv6 ACL 3000 to deny the packet on GigabitEthernet 1/1. • For a multi-core device: # Enable debugging for ICMPv6 packet filtering.
Default Debugging for ASPF is disabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of debugging for ASPF. events: Specifies debugging for events. ftp: Specifies debugging for FTP inspection. h323: Specifies debugging for H.323 inspection. http: Specifies debugging for HTTP inspection. rtsp: Specifies debugging for RTSP inspection. session: Specifies debugging for sessions. smtp: Specifies debugging for SMTP inspection.
Table 51 Output from the debugging aspf rtsp command Field Description process SETUP command address:port Process the SETUP command from the specified IP address and port. process TEARDOWNcommand address:port Process the TEARDOWN command from the specified IP address and port. Table 19 describes output fields and messages for the debugging aspf smtp command.
src Port = 1720, src Port = 1720 dst Port = 1036, dst Port = 1036 Aproto Aproto = 1720, = 1036 // ASPF displayed the temporary ACL and packet information. # Enable ASPF event debugging. debugging aspf events *Mar 18 14:30:41:217 2010 Sysname ASPF/7/EVENT: Source address :20.0.0.2 port number:(1:65535) destination address :20.0.0.3 port number:(1800:1800) // ASPF detected a session. # Enable ASPF session debugging.
// H.323 turned Q.931 call state into 0x92. # Enable debugging for TCP inspection on the device with TCP protocol inspection is configured.
• display aspf session • display aspf interface debugging aspf packet Use debugging aspf packet to enable debugging for ASPF packet filtering. Use undo debugging aspf packet to disable debugging for ASPF packet filtering. Syntax debugging aspf packet undo debugging aspf packet Default Debugging for ASPF packet filtering is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 21 describes output fields and messages for the debugging aspf packet command.
# Enable debugging for packet filtering. Output similar to the following example is generated when an ICMP error packet is to be sent through Ethernet 1/1 under the following conditions: • ASPF is enabled on the device. • An ASPF policy configured to drop ICMP error packets is applied to Ethernet 1/1. • The device acts as a middle node of a route.
Frame relay debugging commands The frame relay module name is identified as "FR" in debugging messages. The output description tables in this document only contain fields and messages that require an explanation. debugging fr Use debugging fr to enable a type of debugging or all types of debugging for the specified interface. If no interface is specified, FR debugging is enabled globally. Use undo debugging fr to disable a type of FR debugging or all types of debugging for the specified interface.
Table 55 Output from the debugging fr congestion command Field Description configured an FECN pkt The forward explicit congestion notification (FECN) bit in a frame was set to 1. This is to signal the downstream nodes (towards the destination) of congestion. configured a BECN pkt The backward explicit congestion notification (BECN) bit in a frame was set to 1. This is to signal the upstream nodes of congestion. Sent a Q922 response pkt A Q.
Field Description status, full Full report on PVCs. It is sent in response to a full status inquiry. status, liv Reply to a LIV request. ssn Send sequence number. rsn Receive sequence number. status dlci = [ulong] Information about PVCs act Active state of the PVC: • 1—Active. • 0—Inactive. new Indicates whether the PVC is a new one: • 1—Yes. • 0—No. PVCs Number of PVCs for which information is carried. (up) DTE timeout The DTE has timed out, and the interface is up.
Table 4 describes the output fields and messages for the debugging fr mfr control command. Table 58 Output from the debugging fr mfr control command Field Description MFR msg Type of the control message sent or received on the bundle link. ADD_LINK The message sent to notify the remote end that the local end can process MFR frames. ADD_LINK_ACK The message sent to acknowledge the receipt of an ADD_LINK message. ADD_LINK_REJ The message sent to indicate rejection of an ADD_LINK message.
debugging fr congestion # Enable FR congestion management debugging. Output similar to the following example is generated when congestion occurs on DLCI 200 and congestion management is configured on the outbound interface Serial 2/0 for FR switching. debugging fr congestion *0.15643800 Sysname FR/7/debug8: CONGEST: Serial2/0:0 DLCI:200 configured an FECN pkt // A frame was sent with FECN bit set to 1 on DLCI 200 towards the downstream device towards the destination. *0.
*0.266083765 RouterA FR/7/debug8: ssn = 1, rsn = 1 *0.266083765 RouterA FR/7/debug8: status dlci = 200, act = 1, new = 0 *0.266083765 RouterA FR/7/debug8: PVCs = 1 // A full status report on PVCs carrying SSN and RSN was received on DLCI 200 on Serial 2/1. *0.266103750 RouterA FR/7/debug8: LMI: Serial2/1 (out) status enquiry, liv *0.266105625 RouterA FR/7/debug8: ssn = 3, rsn = 2 // A LIV status inquiry carrying SSN and RSN was sent out DLCI 200 on Serial 2/1. *0.
*0.266617688 RouterA FR/7/debug8: MFR msg=Add_link, Length=30, Link=Seri al2/0, BL state=Add_rx *0.266617688 RouterA FR/7/debug8: E1 00 01 01 07 4D 46 52 31 00 02 0E 53 65 72 69 61 6C 30 2F 32 2F 30 00 03 06 0E 2A 21 BC *0.266617688 RouterA FR/7/debug8: Serial2/0(out): *0.266617703 RouterA FR/7/debug8: MFR msg=Add_link_ack, Length=30, Link= Serial2/0, BL state=Add_rx *0.266617703 RouterA FR/7/debug8: E1 00 02 01 07 4D 46 52 31 00 02 0E 53 65 72 69 61 6C 30 2F 32 2F 30 00 03 06 0E 29 A9 31 *0.
k=Serial2/0, BL state=Up // A message was sent to notify the remote end of receipt of the Remove_link message. debugging fr transmit-rate # Enable FRTS rate tuning debugging on Router A. Output similar to the following example is generated when Router B is congested because Router A sends enormous traffic under the following conditions: • On a frame relay network formed by Routers A, B, and C, Router B is the switching device.
Parameters interface-type interface-number: Specifies an interface by its type and number. Usage guidelines Table 6 describes output fields and messages for the debugging fr compress command. Table 60 Output from the debugging fr compress command Field Description Begin negotiation: send first Mode_1 request Negotiation started, and the first mode-1 request was sent. Mode_1 Response Received The response to a mode-1 request was received.
*0.425257438 RouterB FR/7/debug8:Serial2/0 DLCI:200 Frf9: Begin negotiation: send first Mode_1 request // Negotiation started, and the first mode-1 request was sent. *0.425257454 RouterB FR/7/debug8:Serial2/0 DLCI:200 Frf9: Mode_1 Request Received // The response to a mode-1 request was received. *0.425257454 RouterB FR/7/debug8:Serial2/0 DLCI:200 Frf9: State=initialization HandShakeStatus=13 // The router was in initialization state, and the handshake state was 13. *0.
*0.782297 RouterA FR/7/debug8:Serial2/0 DLCI:200 Frf9: re-sending mode 1 request :NO. 6 times // The mode-1 request was retransmitted for the sixth time. *0.785297 RouterA FR/7/debug8:Serial2/0 DLCI:200 Frf9: re-sending mode 1 request :NO. 7 times // The mode-1 request was retransmitted for the seventh time. *0.788297 RouterA FR/7/debug8:Serial2/0 DLCI:200 Frf9: re-sending mode 1 request :NO. 8 times // The mode-1 request was retransmitted for the eighth time. *0.
Field Description Fail to insert FR switch Inserting a frame relay switch failed. No buffer available There was a memory allocation failure. insert map fail, exceed number limit on single pvc FR failed to insert a mapping because the maximum number of mappings allowed for the PVC was exceeded. ip addr added to interface An IP address was assigned to the interface. ip addr of interface deleted The IP address of an interface was deleted.
Default command level 1: Monitor level Usage guidelines Table 8 describes output fields and messages for the debugging fr fragment command. Table 62 Output from the debugging fr fragment command Field Description Type ETE The fragment type is end-to-end. DLCI Data link connection identifier. SeqNum Sequence number of a fragment. Header:18 41 3 b1 80 16 The first six bytes (the fragment header) of an FR fragment. B Indicates the first fragment. E Indicates the last fragment.
debugging fr inarp Use debugging fr inarp to enable InARP debugging for frame relay. Use undo debugging fr inarp to disable InARP debugging for frame relay. Syntax debugging fr inarp [ interface interface-type interface-number [ dlci dlci-number ] ] undo debugging fr inarp [ interface interface-type interface-number [ dlci dlci-number ] ] Default InARP debugging for frame relay is disabled.
// An InARP request was sent out DLCI of 200 on Serial2/0. *0.265583484 RouterA FR/7/debug8: INARP: Serial2/0 (in) reply, dlci =200 *0.265583484 RouterA FR/7/debug8: hard len = 2, hard = 0x000F *0.265583484 RouterA FR/7/debug8: prot len = 4, prot = 0x0800 *0.265583484 RouterA FR/7/debug8: sender: 2.2.2.2, target: 2.2.2.1 // The response to the InARP request was received on DLCI of 200 on Serial2/0. debugging fr ipc Use debugging fr ipc to enable IPC debugging for frame relay.
*Apr 26 13:31:26:674 2007 RouterA FR/7/debug8: IPC/RPC: main board #6 out cfg msg: fr class *Apr 26 13:31:26:738 2007 RouterA FR/7/debug8:Slot=5; IPC/RPC: io board #5 in cfg msg: fr ts // The fr class command was configured and applied globally.
Field Description pvc unavailable The PVC is not configured or is inactive. switch unavailable No switching table is available. map unavailable No map is available. Examples # Enable frame relay packet debugging on Router A and Router B. Output similar to the following example is generated when Router A and Router B are connected through FR. debugging fr mfr packet *0.415900015 RouterA FR/7/debug8: PACKET: Serial2/0 (out), dlci 200 *0.
packet: Packet debugging for PPPoFR packets. Usage guidelines Table 12 describes output fields and messages for the debugging pppofr event command. Table 66 Output from the debugging pppofr event command Field Description VT [ulong] VT interface in a PPPoFR mapping. PPPOFR: Receive packet from PPP The PPPoFR module received a packet from PPP. PPPOFR: Cut Head The PPPoFR module removed the Address and Control fields of the PPP packet.
*0.2661250 RouterA FR/7/debug8: PoF: Receive Packet From PPP *0.2661266 RouterA FR/7/debug8: PoF: A=0xFF C=0x03 Len=88 P=0xFF03 *0.2661266 RouterA FR/7/debug8: PoF: VT:1, Fr:Serial2/0, DLCI:100 *0.2661266 RouterA FR/7/debug8: PoF: Send packet to FR Len=86 *0.2661266 RouterA FR/7/debug8: PoF: P=0x0021 *0.2661266 RouterA FR/7/debug8: PoF: VT:1, Fr:Serial2/0, DLCI:100 *0.2661266 RouterA FR/7/debug8: PoF: Send packet to PPP Len=86 *0.
FTP and TFTP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ftp-server Use debugging ftp-server to enable FTP server debugging. Use undo debugging ftp-server to disable FTP server debugging. Syntax debugging ftp-server undo debugging ftp-server Default FTP server debugging is disabled.
Examples # Enable FTP server and FTP server debugging on the device. When a user connects to the device through FTP, output similar to the following example is generated: system-view [Sysname] ftp server enable [Sysname] quit terminal monitor terminal debugging debugging ftp-server *May 12 15:02:05:781 2007 AR29.46 FTPD/7/REQUEST:User (192.168.1.44) requested:USER ftp *May 12 15:02:09:570 2007 AR29.46 FTPD/7/REQUEST:User ftp(192.168.1.
*May 12 15:14:12:989 2007 AR29.46 FTPD/7/REQUEST:User ftp(192.168.1.44) requested: STOR aa.cfg *May 12 15:14:13:21 2007 AR29.46 FTPD/7/RECVDATA:FTP server received 3304 byte(s) from client ftp(192.168.1.44) *May 12 15:14:13:46 2007 AR29.46 FTPD/7/DATACONN:User ftp(192.168.1.44) closed data connection // The user at 192.168.1.44 did the following: Initiated a data connection (passive mode). Uploaded a file to the FTP server. Saved the file as aa.cfg. Closed the connection.
GRE debugging commands debugging gre Use debugging gre to enable GRE debugging. Use undo debugging gre to disable GRE debugging. Syntax debugging gre { all | error | packet } undo debugging gre { all | error | packet } Default GRE debugging is disabled. Views User view Default command level 1: Monitor level Parameters all: All types of GRE debugging. error: GRE error debugging. error: GRE packet debugging.
// The physical layer transmitted a GRE encapsulated packet, with the length 128 and encapsulation type IPv6. *May 15 15:29:06:552 2007 Sysname GRE/7/debug: gre packet: Decapsulate tunnel packet Outer packet header 1.1.1.2->1.1.1.1(length = 128) // GRE de-encapsulated a tunnel packet. Before de-encapsulation, the source and destination addresses of the packet are 1.1.1.2 and 1.1.1.1 respectively, and the packet length is 128.
Tunnel0 packet: After decapsulation, outgoing packet header 22::2->1::1(length = 104). // After de-encapsulation, the source and destination addresses of a packet are 22::2 and 1::1, respectively, and the packet length is 104. # On the peer device, create a GRE tunnel, and configure parameters to make the tunnel interfaces go up. On the local device, create no tunnel interface, and enable GRE error debugging.
GVRP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging garp event Use debugging garp event to enable GARP event debugging. Use undo debugging garp event to disable GARP event debugging. Syntax debugging garp event [ interface interface-type interface-number ] undo debugging garp event [ interface interface-type interface-number ] Default The debugging for GARP events is disabled.
// The join timer expired on Ethernet 1/1. debugging gvrp event Use debugging gvrp event to enable GVRP event debugging. Use undo debugging gvrp event to disable GVRP event debugging. Syntax debugging gvrp event undo debugging gvrp event Default GVRP event debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 2 describes output fields and messages for the debugging gvrp event command.
Default command level 1: Monitor level Parameters interface interface-type interface-number: Specifies a port by its type and number. Usage guidelines If you do not specify a port, the command enables GVRP packet debugging on all ports. Table 3 describes output fields and messages for the debugging gvrp packet command. Table 71 Output from the debugging gvrp packet command Field Description Tx GARP transmitted a packet. Rx GARP received a packet. GVRP message GVRP protocol message.
Default GVRP state machine debugging is disabled. Views User view Default command level 1: Monitor level Parameters interface interface-type interface-number: Specifies a port by its type and number. Usage guidelines If you do not specify a port, the command enables GVRP state machine debugging on all ports. Table 3 describes output fields and messages for the debugging gvrp state command. Table 72 Output from the debugging gvrp state command Field Description VLAN n VLAN ID.
HABP debugging commands debugging habp Use debugging habp to enable HABP packet debugging. Use undo debugging habp to disable HABP packet debugging. Syntax debugging habp undo debugging habp Default HABP packet debugging is disabled. Views User view Default command level 1: Monitor level Examples # Enable HABP packet debugging. The output in this example was created when the following conditions exist: • The device is configured with clustering. • HABP is enabled on the device.
HDLC debugging commands The output description tables in this document only contain fields and messages that require an explanation. HDLC debugging commands debugging hdlc Use debugging hdlc to enable a specific type of HDLC debugging on an interface. Use undo debugging hdlc to disable a specific type of HDLC debugging on an interface.
Table 73 Output from the debugging hdlc event command Field Description interface-type interface-number The interface where the event occurred. Event Information about the event. Table 2 describes the output fields and messages for the debugging hdlc ip command. Table 74 Output from the debugging hdlc ip command Field Description interface-type interface-number The interface through which packets were received/transmitted. I Inbound packets. O Outbound packets. Length Packet length.
Table 77 Output from the debugging hdlc keepalive command Field Description interface-type interface-number The interface through which packets were received or transmitted. I Inbound packets. O Outbound packets. Length: length Packet length. Address: address HDLC address of a packet. Protocol KEEPALIVE The type of the packet is keepalive. Keepalive-type The specific type of a keepalive packet. NotifyingRemoteSeq The sequence number of the current protocol packet of the receiver.
debugging hdlc compression stac Use debugging hdlc compression stac to enable debugging for packet compression on an HDLC link. Use undo debugging hdlc compression stac to disable debugging for packet compression on an HDLC link.
HDLC link bundling debugging commands NOTE: Support for this debugging command depends on your device model. The HDLC link bundling module name is identified as "BNDL" in debugging messages. debugging bundle Use debugging bundle to enable debugging for an HDLC link bundle interface. Use undo debugging bundle to disable debugging for an HDLC link bundle interface.
Table 79 Output from the debugging bundle error command Field Description Failed to execute the operation: operation on bundle bundle-id. One of the following operations failed on the link bundle specified by bundle-id: • create—Creating the link bundle. • modify—Modifying the selected member interfaces in the link bundle. • delete—Deleting the link bundle. Table 8 describes the output fields and messages for the debugging bundle event command.
The member interface Pos5/1 in bundle 1 is blocked. *Aug 26 15:49:56:359 2008 Sysname BNDL/7/Event:Slot=1; The interface Pos5/1 joins in bundle 1. The attributes of Pos5/1: speed = 155520kbps, linkState = UP, Restriction = 0, Drv MaxNum = 4294967295. // POS 5/1 was assigned to HDLC link bundle 1. *Aug 26 15:49:56:640 2008 Sysname BNDL/7/Event: The main board processes the join message. The attributes of member interface Pos5/1: speed = 155520kbps, linkState = UP, Restriction = 0, DrvMaxNum = 4294967295.
IGMP debugging commands Support for VPN instances depends on your device model. The output description tables in this document only contain fields and messages that require an explanation. debugging igmp Use debugging igmp to enable IGMP debugging. Use undo debugging igmp to disable IGMP debugging.
Usage guidelines If neither all-instance nor vpn-instance is specified, this command enables IGMP debugging for the public network. Table 1 describes output fields and messages for the debugging igmp event command.
Table 85 Output from the debugging igmp report command Field Description Ignoring This IGMP report was ignored. IS_IN/IS_EX/TO_IN/TO_EX/ALLOW/BLOCK Record type of IGMPv3 membership report: • • • • • • IS_IN IS_EX TO_IN TO_EX ALLOW BLOCK Group gadd Reported group address. (sadd, gadd) (S, G) entry. v1/v2/v3 Version of IGMP membership report. Interfacename(ifadd) Interface that sent/received this message. The interface address is displayed in the brackets.
*0.5532846 Sysname IGMP/7/EVENT:(public net):Elected querier on interface Vlan-interface20(1.1.1.1) (G10297) // VLAN-interface 20 was elected as the IGMP querier. *0.7509231 Sysname IGMP/7/EVENT:(public net):IGMP receiving aux join, adding downstream interface Vlan-interface20(1.1.1.1). (B01494) *0.7509231 Sysname IGMP/7/EVENT:(public net):IGMP receiving aux join: group 235.1.1.1 joined on interface Vlan-interface20(1.1.1.1). (B01528) *0.7509231 Sysname IGMP/7/EVENT:(public net):Creating group record 235.
debugging igmp query *0.20244493 Sysname IGMP/7/QUERY:(public net):Send version 3 general query on Vlan-interface20(1.1.1.1) to destination 224.0.0.1 (B03939) // IGMP sent out an IGMPv3 general query message out of VLAN-interface 20. # When IGMP SSM mapping is enabled, enable IGMP SSM mapping debugging for the public network. debugging igmp ssm-mapping *0.20301209 Sysname IGMP/7/SSM-MAPPING:(public net):Receive ssm-mapping report for group 232.1.1.1 on interface Vlan-interface20(1.1.1.
*0.70447221 85 IGMP/7/TIMER:(public net):Deleting lmqi timer for ssm-mapping group 232.1.1.1 on Vlan-interface20(1.1.1.1) (G016110) // IGMP sent out queries for group 232.1.1.1. IGMP did not receive any report messages and deleted the last-member query timer. debugging igmp proxying Use debugging igmp proxying to enable IGMP proxy debugging. Use undo debugging igmp proxying to disable IGMP proxy debugging.
Field Description Number of joins Number of joined sources. Table 8 describes output fields and messages for the debugging igmp proxying packet command. Table 89 Output from the debugging igmp proxying packet command Field Description proxying interface IGMP proxy interface. query IGMP query message. report IGMP report message. record Group record. type 1 Group record types: type 2 • • • • • • • • type 3 type 4 type 5 type 6 type 7 type 8 Type 1—IS_IN. Type 2—IS_EX. Type 3—TO_IN.
*0.5532846 Sysname IGMP/7/PRY_EVT:(public net): Group 225.1.1.1 enqueued in proxy_calq. (G363784) // Upon receiving a query message for group 225.1.1.1, the upstream interface started the delay timer and placed this group in the CALQ queue. *0.5532846 Sysname IGMP/7/PRY_EVT:(public net): Group 225.1.1.1 dequeued from proxy_calq. (G363784) // When the upstream interface went down, it removed the group from the CALQ queue. *0.5532846 Sysname IGMP/7/PRY_EVT:(public net): Group record created for group 225.1.
// IGMP detected that the route was lost and removed the associated forwarding entry. *0.58034165 Sysname IGMP/7/PRY_RT:(public net): Recovery of route for (10.10.10.1, 225.1.1.1) detected, (S,G) entry created. (G361460) // IGMP detected that the route was recovered and thus created the associated forwarding entry.
IGMP snooping debugging commands The MCS module name is identified as "multicast" in debugging messages. 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. This document categorizes devices depending on their IRF capability and support for interface cards that use independent processors for forwarding traffic, as shown in Table 1.
Default IGMP snooping debugging is disabled. Views User view Default command level 1: Monitor level Parameters abnormal: Specifies IGMP snooping exception debugging. all: Specifies all types of IGMP snooping debugging. driver: Specifies IGMP snooping interface driver debugging. event: Specifies IGMP snooping event debugging. group: Specifies IGMP snooping group debugging. ipc { receive | send }: Specifies inbound/outbound IPC packet debugging. packet: Specifies IGMP snooping packet debugging.
Field Description (saddr, gaddr) (S, G) entry. Table 3 describes output fields and messages for the debugging igmp-snooping event command. Table 93 Output from the debugging igmp-snooping event command Field Description Succeed to enable/disable IGMP snooping globally IGMP snooping was globally enabled or disabled. Succeed to enable/disable IGMP snooping drop-unknown globally The function of dropping unknown multicast packets was globally enabled or disabled.
Field Description destination address addr Destination address of the message. Table 7 describes output fields and messages for the debugging igmp-snooping timer command. Table 97 Output from the debugging igmp-snooping timer command Field Description Create/Set IGMP snooping created/set a timer.
# Enable outbound IPC packet debugging. When IGMP snooping is enabled on the device, output similar to the following example is generated: debugging igmp-snooping ipc send *Nov 7 17:17:38:880 2006 Sysname MCS/7/ipcsend:Inform other boards: this board is not router board any more. (G143361) // IGMP snooping sent an IPC packet. # Enable IGMP snooping packet debugging.
Interface backup debugging commands The output description tables in this document only contain fields and messages that require an explanation. The interface backup module name is identified as "STANDBY" in debugging messages. debugging standby Use debugging standby to enable interface backup debugging. Use undo debugging standby event to disable interface backup debugging. Syntax debugging standby { event | track } undo debugging standby { event | track } Default Interface backup debugging is disabled.
Field Description DOWN indicates the backup interface is down at the physical layer and the physical link is not available. DOWN/MDOWN MDOWN indicates the main interface is down at the data link layer and cannot work correctly. UPDELAY/MDOWNDELAY Starting up the UPDELAY or MDOWNDELAY timer. up-timer/down-timer The UPDELAY or MDOWNDELAY timer timed out. hypnotized/wakeuped Hypnotized state/waken up state. Table 2 describes output fields and messages for the debugging standby track command.
// Interface Ethernet 0/0 changed to the main interface state, and Ethernet 0/1 changed to the backup interface state.
%Jan 16 15:35:33:484 2007 Sysname IFNET/4/UPDOWN: Line protocol on the interface Ethernet0/1 is DOWN %Jan 16 15:35:33:484 2007 Sysname DRVMSG/1/DRVMSG: Ethernet0/1: change status to down *Jan 16 15:35:33:485 2007 Sysname STANDBY/7/DEBUGGING: Ethernet0/0: main interface up-timer expires *Jan 16 15:35:33:486 2007 Sysname STANDBY/7/DEBUGGING: Ethernet0/0: standby-state turns to MUP *Jan 16 15:35:33:486 2007 Sysname STANDBY/7/DEBUGGING: Ethernet0/1: the interface is hypnotized *Jan 16 15:35:33:487 2007 Sysname
IP accounting debugging commands The IP accounting module name is identified as "IPA" in debugging messages. debugging ip count Use debugging ip count to enable IP accounting debugging. Use undo debugging ip count to disable IP accounting debugging. Syntax debugging ip count { all | dada | error } undo debugging ip count { all | dada | error } Default IP accounting debugging is disabled.
[Sysname] ip count enable [Sysname] ip count rule 13.13.13.0 255.255.255.0 [Sysname] interface Ethernet 1/0 [Sysname-Ethernet1/0] port link-mode route [Sysname-Ethernet1/0] ip address 13.13.13.46 255.255.255.0 [Sysname-Ethernet1/0] ip count outbound-packets [Sysname-Ethernet1/0] ip count inbound-packets [Sysname-Ethernet1/0] quit [Sysname] interface Ethernet 1/1 [Sysname-Ethernet1/1] port link-mode route [Sysname-Ethernet1/1] ip address 33.33.33.46 255.255.255.
IP performance optimization debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ip error Use debugging ip error to enable IP forwarding error debugging. Use undo debugging ip error to disable IP forwarding error debugging. Syntax debugging ip error undo debugging ip error Default IP forwarding error debugging is disabled.
Views User view Default command level 1: Monitor level Examples # Enable ICMP debugging. terminal debugging debugging ip icmp # Ping 10.1.1.2. ping –c 1 10.1.1.2 Output similar to the following example is generated: PING 10.1.1.2: 56 *Aug data bytes, press CTRL_C to break 3 02:38:57:66 2006 Sysname IPDBG/7/debug_icmp: ICMP Send: echo(Type=8, Code=0), Dst = 10.1.1.2 // ICMP sent an echo request to the destination IP address 10.1.1.2.
Examples # Configure an ACL. system-view [Sysname] acl number 3050 [Sysname-acl-adv-3050] rule permit ip source 10.1.1.0 0.0.0.255 destination 10.1.1.0 0.0.0.255 [Sysname-acl-adv-3050] quit [Sysname] quit # Enable IP packet debugging. terminal debugging debugging ip packet acl 3050 # Ping 10.1.1.2. ping –c 1 10.1.1.2 Output similar to the following example is generated: PING 10.1.1.
Syntax debugging ip virtual-reassembly undo debugging ip virtual-reassembly Default IP virtual fragment reassembly debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 1 describes output fields and messages for the debugging ip virtual-reassembly command. Table 101 Output from the debugging ip virtual-reassembly command Field Description vfr_rcv: fragment A VFR request was received. target_ip_addr Destination IP address.
vfr_operation: dgrm incomplete offset:0, waiting... // IP virtual fragment reassembly for the datagram does not finish because the fragment with the offset 0 is not received. *May 10 17:54:21:328 2000 Sysname VFR/7/IPVFR_DEBUG_COMMON: vfr_rcv: fragment, target_ip_addr: 10.1.1.1, sender_ip_addr: 10.1.1.2, id: 54, offset: 1480, len: 548. // IP virtual fragment reassembly received a fragment. *May 10 17:54:22:88 2000 Sysname VFR/7/IPVFR_DEBUG_COMMON: vfr_operation: dgrm complete.
Examples # Enable the Telnet server. system-view [Sysname] telnet server enable # Create VTY users. [Sysname] user-interface vty 0 4 [Sysname-ui-vty0-4] authentication-mode none [Sysname-ui-vty0-4] user privilege level 3 # Enable TCP event debugging.
Syntax debugging tcp md5 undo debugging tcp md5 Default MD5 authentication debugging for TCP connections is disabled. Views User view Default command level 1: Monitor level Examples # Enable MD5 authentication debugging for TCP connections.
Default command level 1: Monitor level Parameters task-id: Specifies the task ID in the range 1 to 100. socket-id: Specifies the socket ID in the range 0 to 3072. slot-number: Specifies the number of the slot that holds the card. (Distributed devices.) slot-number: Specifies the ID of the IRF member device. (Centralized IRF member devices.) chassis-number slot-number: Specifies the slot number of the card on an IRF member device.
debugging udp packet Use debugging udp packet to enable UDP packet debugging. Use undo debugging udp packet to disable UDP packet debugging.
1123049125: Output: task = vt0(2), socketid = 1, src = 192.168.1.40:1031, dst = 192.168.1.56:69, datalen = 14 // UDP sent a UDP packet. *Aug 3 06:05:25:810 2006 Sysname SOCKET/7/UDP: 1123049125: Input: task = vt0(2), socketid = 1, src = 192.168.1.56:1394, dst = 192.168.1.40:1031, datalen = 417\ // UDP received a UDP packet. *Aug 3 06:05:25:812 2006 Sysname SOCKET/7/UDP: 1123049125: Output: task = vt0(2), socketid = 1, src = 192.168.1.40:1031, dst = 192.168.1.
IP source guard 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.
Views User view Parameters error: Specifies error debugging. event: Specifies event debugging. all: Specifies all types of debugging. slot slot-number: Specifies a card by its slot number. (Distributed devices.) chassis chassis-number slot slot-number: Specifies a card in an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the number of the slot where the card resides. (Distributed IRF fabric.
Field Description Failed to query data (handle-del-if). Failed to query the bindings to be removed when processing binding removal by interface. Failed to malloc (handle-del-MID). Failed to allocate memory for the bindings to be removed when processing binding removal by module ID. Failed to get CB of a port (hangdle-add). Failed to get port control block when adding a binding. Failed to malloc for RPC messages when requesting to add a binding.
Field Description Processed IF_IFMSG_CLEAR_DRVINFO event for ipv6 binding. An event of deleting the interface drive information for IPv6 binding was processed successfully. Processed IF_IFMSG_RESET_DRVINFO event for ipv6 binding. An event of resetting the interface drive information for IPv6 binding was processed successfully. Examples # Enable debugging for user binding errors.
IP terminal access debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ipta all Use debugging ipta all to enable all IP terminal access debugging. Use undo debugging ipta all to disable all IP terminal access debugging. Syntax debugging ipta all [ service service-name | terminal ttyid ] undo debugging ipta all [ service service-name | terminal ttyid ] Default All IP terminal access debugging is disabled.
*Jun 12 09:51:19:884 2007 ipta IPTA/7/EVENT: Service = duigong, TtyID = 1, Get server and its priority is 0 // A server with priority 0 is available for the duigong service and terminal 1. *Jun 12 09:51:19:899 2007 ipta IPTA/7/PACKET: Service = duigong, TtyID = 1, Direction: Send data to terminal. ----------------------------------------------000: 0d 0a 3c 48 33 43 3e .. // The access router sent data to terminal 1 with content 0d 0a 3c 48 33 43 3 representing . The service name is duigong.
Field Description Fail to send disconnecting by terminal message! IP terminal access failed to send the message for disconnecting connections from the specified terminal. Fail to send disconnecting all terminal message! IP terminal access failed to send the message for disconnecting all connections at the terminal side. Fail to send disconnecting all service message! IP terminal access failed to send the message for disconnecting all connections at the server side.
Parameters service service-name: Specifies a service by its name, a case-insensitive string of 1 to 15 characters, including spaces. terminal ttyid: Specifies a terminal by its ID, an integer in the range of 1 to 255. Usage guidelines Table 2 describes output fields and messages for the debugging ipta event command. Table 106 Output from the debugging ipta event command Field Description IPTA state: IPTA_TM_AAA_WAITINGPASSWORD The IPTA connection is in waiting for the password state.
Default IP terminal access packet debugging is disabled. Views User view Default command level 1: Monitor level Parameters service service-name: Specifies a service by its name, a case-insensitive string of 1 to 15 characters, including spaces. terminal ttyid: Specifies a terminal by its ID, an integer in the range of 1 to 255. Examples # Enable IP terminal access packet debugging.
IPC debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ipc packet Use debugging ipc packet to enable IPC packet debugging. Use undo debugging ipc packet to disable IPC packet debugging. Syntax debugging ipc packet [ node node-id | self-node ] [ channel channel-id ] undo debugging ipc packet [ node node-id | self-node ] [ channel channel-id ] Default IPC packet debugging is disabled.
Field Description Fragment flag: Fragment flag • Non-fragmented packet. • Fragmented packet, but not the last fragment. • The last fragment of a packet. Examples # Enable IPC packet debugging for the local node's channel 94.
Usage guidelines Table 2 describes output fields and messages for the debugging ipc link command. Table 108 Output from the debugging ipc link command Field Description node1 and node2 represent node numbers. Link status between node node1 and node node2 changed from status1 to status2. status1 and status2 represent link status. Possible status values: • UP—A connection has been established. • DOWN—A connection has been terminated. • UPDOWN—Intermediate state of a connection.
self-node: Enables IPC error debugging of the local node. For a centralized device, "local node" refers to the local device. For a distributed device, "local node" refers to the MPU of the device. Examples # Enable IPC error debugging for the local node. terminal debugging terminal monitor debugging ipc error self-node debugging ipc event Use debugging ipc event to enable IPC event debugging. Use undo debugging ipc event to disable IPC event debugging.
Table 109 Output from the debugging ipc event ack command Field Description Process ACK from node node1, queue type: type1, queue ID:id1, ACK: sqn1. The node received an acknowledgement from node1. The queue type is type1, queue number is id1, and packet sequence number is sqn1, where: Values for the queue type include unicast, multicast, and mixcast. Table 4 describes output fields and messages for the debugging ipc event flow-control command.
terminal monitor debugging ipc event flowcontrol self-node debugging ipc event flowcontrol node 5. *Nov 28 16:57:51:173 2007 Sysname IPC/4/IPC EVENT: IPC procedure flow-control event, node 5, queue type mixcast, queue ID 1. // The local node (node 1) sent a flow control request to node 5. *Nov 28 16:57:51:285 2007 Sysname IPC/4/IPC EVENT:Slot=5; Received flow control request from node 1, queue type: mixcast, queue ID: 1. // Node 5 received a flow control request from node 1.
IPsec/IKE debugging commands The output description tables in this document only contain fields and messages that require an explanation. IPsec debugging commands debugging ipsec Use debugging ipsec to enable IPsec debugging. Use undo debugging ipsec to disable IPsec debugging.
Usage guidelines Table 1 describes output fields and messages for the debugging ipsec error command on devices with multi-core CPUs. Table 112 Output from the debugging ipsec error command (for devices with multi-core CPUs) Field Description Failed to process VPN route, error code: error-code value, event type: event-value, dest/mask: dst-ip-net/mask, nexthop : nexthop-addr, exit interface: interface-type interface-number with tag tag-value preference pre-value.
Table 115 Output from the debugging ipsec sa command (for devices with single-core CPUs) Field Description Enc Alg Encryption algorithm. Table 5 describes output fields and messages for the debugging ipsec sa command on devices with multi-core CPUs. Table 116 Output from the debugging ipsec sa command (for devices with multi-core CPUs) Field Description Failed to check IPsec SA's parameters in DP. Failed to check IPsec SA parameters in the data plane.
// The IPsec module is sending the data to the IP layer for processing. *0.1139906 Sysname IPSEC/7/DBG:--- Receive IPsec(ESP) packet --*0.1139906 Sysname IPSEC/7/DBG:Src:3.0.0.1 Dst:3.0.0.2 SPI:2556898176(0x98672b80) // The responder received a packet whose source address is 3.0.0.1, destination address is 3.0.0.2, and SPI is 2556898176. *0.1139906 Sysname IPSEC/7/DBG:New ESP(RFC2406) Enc Alg:DES Auth Alg:HMAC-MD5-96 // The encryption algorithm is DES, and the authentication algorithm is MD5. *0.
Protect Flow: Peer IP :15.1.1.2 Mask :255.255.255.0 Source IP :14.1.1.2 Mask : 255.255.255.0 Protocol Number :0 // The IPsec module created an inbound IPsec SA. The IPsec SA has the following details: Security protocol is ESP. Authentication algorithm is MD5. Encryption algorithm is DES. *Jun 28 19:32:44:252 2006 Sysname DPIPSEC/7/debug: IPsec Command Operation :Create IPsec SA.
// The IPsec module created an IPsec policy control block. IPsec Command Operation :Delete Driver Control Block. Control Block ID :2 Interface Index :1048579 // The IPsec module deleted an IPsec policy control block. # Enable IPsec debugging on the local end.
*Jan 11 08:41:54:917 2012 Sysname DPIPSEC/7/debug:IPsec_Packet: thread 15, esp authentication succeed. // The output is the IPsec processing information on the responder after the IPsec SA negotiation succeeded. • On a firewall device with multi-core CPUs # Enable IPsec stateful failover debugging.
Table 118 Output from the debugging encrypt-card all command Field Description Send data to encrypt card retry: success to send data to encrypt card! The IPsec module sent a packet that needs to be IPsec encapsulated to the encryption card. Receive outbound packet: send packet to IP output. The encryption card has encapsulated the packet and placed it into the outbound IP queue.
undo debugging ike { all | dpd | error | exchange | message | synchronization } Default IKE debugging is disabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of IKE debugging. dpd: Specifies Dead peer detection (DPD) debugging. error: Specifies IKE error debugging. exchange: Specifies IKE exchange mode debugging. message: Specifies IKE message debugging. synchronization: Specifies IKE stateful failover debugging.
Field Description finalize exchange The IKE module was performing the final exchange of IPsec packets. exchange release The IKE module was releasing the data structure for the exchange. Table 10 describes output fields and messages for the debugging ike packet command. Table 121 Output from the debugging ike packet command Field Description message alloc Memory allocated for messages. ICOOKIE: Cookie of the initiator. RCOOKIE: Cookie of the responder.
*Mar 27 14:31:20:277 2007 Sysname IKE/7/DEBUG:02060000 00800000 00000000 00000000 00000000 00000000 00060005 00000000 …… (Some debugging information is omitted) *Mar 27 14:31:21:727 2007 Sysname IKE/7/DEBUG:00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 *Mar 27 14:31:21:826 2007 Sysname IKE/7/DEBUG:Add message: type 5 *Mar 27 14:31:21:975 2007 Sysname IKE/7/DEBUG:Add message: type 6 *Mar 27 14:31:22:74 2007 Sysname IKE/7/DEBUG:Add message: type 10 *Mar 27 14:31:22:222 2007 Sysname I
*Mar 27 14:31:25:370 2007 Sysname IKE/7/DEBUG: VERSION: 16 *Mar 27 14:31:25:469 2007 Sysname IKE/7/DEBUG: EXCH_TYPE: AGGRESSIVE *Mar 27 14:31:25:568 2007 Sysname IKE/7/DEBUG: FLAGS: [ ] *Mar 27 14:31:25:667 2007 Sysname IKE/7/DEBUG: MESSAGE_ID: 0x00000000 *Mar 27 14:31:25:776 2007 Sysname IKE/7/DEBUG: LENGTH: 236 // The IKE module sent the first message in aggressive mode and printed the contents of the message.
*Mar 27 14:31:29:528 2007 Sysname IKE/7/DEBUG:3abafcd7 ec9a7d65 d5118eaf 7588efe7 01100400 00000000 00000104 04000038 *Mar 27 14:31:29:578 2007 Sysname IKE/7/DEBUG:00000001 00000001 0000002c 01010001 00000024 00010000 80010001 80020002 *Mar 27 14:31:29:677 2007 Sysname IKE/7/DEBUG:80030001 80040001 800b0001 000c0004 00015180 0a000064 807af36c e4b92536 *Mar 27 14:31:29:726 2007 Sysname IKE/7/DEBUG:d7e9e4f5 2745d1a0 2d6ae79a 5c2fcb5c 0e220f8d ead429f7 826d119a 20e605e6 *Mar 27 14:31:29:825 2007 Sysname IKE/7/
*Mar 27 14:31:32:983 2007 Sysname IKE/7/DEBUG: PRE_SHARED Attribute AUTHENTICATION_METHOD: *Mar 27 14:31:33:33 2007 Sysname IKE/7/DEBUG: Attribute GROUP_DESCRIPTION : MODP_768 *Mar 27 14:31:33:82 2007 Sysname IKE/7/DEBUG: Attribute LIFE_TYPE : SECONDS *Mar 27 14:31:33:181 2007 Sysname IKE/7/DEBUG: Attribute LIFE_DURATION : 86400 // The IKE module validated the proposal payload of the response message.
*Mar 27 14:31:35:587 2007 Sysname IKE/7/DEBUG:afcad713 68a1f1c9 6b8696fc 77570100 *Mar 27 14:31:35:686 2007 Sysname IKE/7/DEBUG:recv_VID: afcad713 68a1f1c9 6b8696fc 77570100 (DPD) *Mar 27 14:31:35:735 2007 Sysname IKE/7/DEBUG:post exchange KE_NONCE: g^xy: *Mar 27 14:31:35:884 2007 Sysname IKE/7/DEBUG:a466b9d0 51924c0d d9120cbb 571642f1 5b21d0d7 173c28e9 27d6b02a c8ea268b *Mar 27 14:31:35:983 2007 Sysname IKE/7/DEBUG:2ae664c4 39ea3def 14348dce c89bc3b9 54ba961e 3d722ca5 9a3b1a3d 8e88b4c1 *Mar 27 14:31:36:131
*Mar 27 14:31:39:141 2007 Sysname IKE/7/DEBUG:0a61f134 1c631f1a 507f2868 2435e397 f804b8d5 604f805a *Mar 27 14:31:39:191 2007 Sysname IKE/7/DEBUG:exchange run(i): finished step 2, advancing... *Mar 27 14:31:40:191 2007 Sysname IKE/7/DEBUG:create ike tunnel: ike tunnel 88ad044 added to tunnel list // After the third packet for IKE negotiation was sent, the IKE tunnel was created. The IKE negotiation in phase 1 finished and the system could perform IKE negotiation in phase 2.
*Mar 27 14:31:43:240 2007 Sysname IKE/7/DEBUG:00195000 001c2000 00000ca8 00000e10 00000000 00000000 00000000 00050017 *Mar 27 14:31:43:339 2007 Sysname IKE/7/DEBUG:00000001 00100000 64656275 67000000 // The IKE module triggered the internal processing message in phase 2 *Mar 27 14:31:43:388 2007 Sysname IKE/7/DEBUG:Add message: type 13 *Mar 27 14:31:43:487 2007 Sysname IKE/7/DEBUG:Add message: type 23 *Mar 27 14:31:43:547 2007 Sysname IKE/7/DEBUG:Add message: type 5 *Mar 27 14:31:43:646 2007 Sysname IKE/7/
*Mar 27 14:31:46:546 2007 Sysname IKE/7/DEBUG:initiator send HASH-SA-NONCE: payload 3 after HASH(1): *Mar 27 14:31:46:645 2007 Sysname IKE/7/DEBUG:00000028 01020000 80010001 00020004 00000e10 80010002 00020004 001c2000 *Mar 27 14:31:46:744 2007 Sysname IKE/7/DEBUG:80040001 80050001 *Mar 27 14:31:46:843 2007 Sysname IKE/7/DEBUG:initiator send HASH-SA-NONCE: payload 4 after HASH(1): *Mar 27 14:31:46:893 2007 Sysname IKE/7/DEBUG:05000014 44e015a2 04f6fc38 5188caf3 fc8979af *Mar 27 14:31:47:02 2007 Sysname IKE/
// The IKE module finished processing the contents of the first message in quick mode and entered the next negotiation state to wait for a response from the responder.
*Mar 27 14:31:52:803 2007 Sysname IKE/7/DEBUG:message parse payloads: payload SA *Mar 27 14:31:52:952 2007 Sysname IKE/7/DEBUG:message parse payloads: payload NONCE *Mar 27 14:31:53:51 2007 Sysname IKE/7/DEBUG:message parse payloads: payload ID *Mar 27 14:31:53:199 2007 Sysname IKE/7/DEBUG:message parse payloads: payload ID *Mar 27 14:31:53:298 2007 Sysname IKE/7/DEBUG:validate payload SA of message 8891984 *Mar 27 14:31:53:348 2007 Sysname IKE/7/DEBUG: DOI: 1 *Mar 27 14:31:53:447 2007 Sysname IKE/7/DEBUG
*Mar 27 14:31:56:11 2007 Sysname IKE/7/DEBUG:add transform sa: proto 88b4904 no 1 proto 3 chosen 796e004 sa 88acbc4 id 2 *Mar 27 14:31:56:110 2007 Sysname IKE/7/DEBUG:add transform sa: proto 88ac384 no 1 proto 3 chosen 796e004 sa 88acbc4 id 2 *Mar 27 14:31:56:159 2007 Sysname IKE/7/DEBUG:ipsec_decode_transform: transform 1 chosen *Mar 27 14:31:56:258 2007 Sysname IKE/7/DEBUG:initiator recv HASH-SA-NONCE: SKEYID_a: *Mar 27 14:31:56:357 2007 Sysname IKE/7/DEBUG:43204db5 5335400b 5f7faabe 0c5ba374 4f62cc28 *Ma
*Mar 27 14:31:59:713 2007 Sysname IKE/7/DEBUG: VERSION: 16 *Mar 27 14:31:59:812 2007 Sysname IKE/7/DEBUG: EXCH_TYPE: QUICK_MODE *Mar 27 14:31:59:862 2007 Sysname IKE/7/DEBUG: FLAGS: [ ENC ] *Mar 27 14:31:59:961 2007 Sysname IKE/7/DEBUG: *Mar 27 14:32:00:60 2007 Sysname IKE/7/DEBUG: MESSAGE_ID: 0x62270366 LENGTH: 52 // The IKE module sent the third message in quick mode and printed the contents of the message.
*Mar 27 14:32:04:416 2007 Sysname IKE/7/DEBUG:post quick mode: Nr_b: *Mar 27 14:32:04:515 2007 Sysname IKE/7/DEBUG:992ba874 c0d75339 cbd47f5d a7750824 *Mar 27 14:32:04:614 2007 Sysname IKE/7/DEBUG:post quick mode: KEYMAT: *Mar 27 14:32:04:713 2007 Sysname IKE/7/DEBUG:fbeaae3d 9b1bb873 fa4a03e3 5bdfb0e2 620d4452 cd7b117e *Mar 27 14:32:04:772 2007 Sysname IKE/7/DEBUG:Add message: type 1 *Mar 27 14:32:04:871 2007 Sysname IKE/7/DEBUG:Add message: type 3 *Mar 27 14:32:04:921 2007 Sysname IKE/7/DEBUG:Add message:
*Mar 27 14:32:07:871 2007 Sysname IKE/7/DEBUG:Add message: type 4 *Mar 27 14:32:07:920 2007 Sysname IKE/7/DEBUG:Add message: type 5 *Mar 27 14:32:08:19 2007 Sysname IKE/7/DEBUG:Add message: type 6 *Mar 27 14:32:08:69 2007 Sysname IKE/7/DEBUG:Add message: type 8 *Mar 27 14:32:08:128 2007 Sysname IKE/7/DEBUG:Add message: type 9 *Mar 27 14:32:08:227 2007 Sysname IKE/7/DEBUG:Write message: iov[0]: *Mar 27 14:32:08:277 2007 Sysname IKE/7/DEBUG:02020002 002d0000 00000048 0000003c 00000000 00100000 *Mar 27 14:32:0
*Mar 27 14:32:11:128 2007 Sysname IKE/7/DEBUG:02100002 002c0000 00000049 0000003c 00000000 00100000 *Mar 27 14:32:11:227 2007 Sysname IKE/7/DEBUG:Write message: iov[1]: *Mar 27 14:32:11:276 2007 Sysname IKE/7/DEBUG:00070001 80c24193 00000004 00000000 00000000 00000080 057593c0 *Mar 27 14:32:11:375 2007 Sysname IKE/7/DEBUG:Write message: iov[2]: *Mar 27 14:32:11:435 2007 Sysname IKE/7/DEBUG:00050017 07970001 02aa9e40 64656275 67000800 *Mar 27 14:32:11:484 2007 Sysname IKE/7/DEBUG:Write message: iov[3]: *Mar
*Mar 27 14:32:14:286 2007 Sysname IKE/7/DEBUG:0004001a 00000000 00000008 02100002 *Mar 27 14:32:14:385 2007 Sysname IKE/7/DEBUG:Read message: message: *Mar 27 14:32:14:484 2007 Sysname IKE/7/DEBUG:02100002 00060000 0000004a 0000003c 00000000 00100000 *Mar 27 14:32:14:583 2007 Sysname IKE/7/DEBUG:finalize exchange: 0/0 -> 0/0 *Mar 27 14:32:14:633 2007 Sysname IKE/7/DEBUG:message free: freeing 8891984 *Mar 27 14:32:14:741 2007 Sysname IKE/7/DEBUG:release transport: transport 887f224 had 3 references *Mar 27 1
packet seq = 0, packet msg num = 1, packet length = 251. // The IKE module parsed the received backup packet. *Nov 20 15:31:36:009 2010 Backup IKE/7/DEBUG: IKE_SYNCH: Processing synch-phase1-sa message, length = 239. // The IKE module was processing the synch-phase1-sa message. IKEv2 debugging commands debugging ikev2 Use debugging ikev2 to enable IKEv2 debugging. Use undo debugging ikev2 to disable IKEv2 debugging.
Field Description IKE_AUTH[R] Msg_Receive: Messages received by the responder in the IKE_ AUTH phase. IKE_AUTH[R] Msg_Proc: Messages processed by the responder in the IKE_ AUTH phase. IKE_AUTH[I] Msg_Receive: Messages received by the initiator in the IKE_ AUTH phase. CHILD_SA[R] Msg_Receive: Messages received by the responder in the CHILD_SA phase. CHILD_SA[I] Msg_Receive: Messages received by the initiator in the CHILD_SA phase.
Table 123 Output from the debugging ikev2 fsm command Field Description Child SA state machine information: • [sa-type]—Child SA type: RESERVE. IPSECSA . INFO_INIT_NOTIFY. INFO_INIT_DELETE. CHILD_DELETE. REKEY_IKEV2SA. IKEV2SA_DELETE. IKE CHILD SA TYPE[UNKNOWN] . • [side]—[I] is the initiator, and [R] is the responder. • ID—Message ID. • Local—Local end IP address. CHILD SA[sa-type], [side], ID: child-id, • Remote—Remote end IP address.
Field Description IKEv2 SA state machine information: • init-cookie—Initiator's cookie. • resp-cookie—Responder's cookie. • Local—Local end IP address. • Remote—Remote end IP address. • [side]—[I] is the initiator, and [R] is the responder. • Seq—IKE SA serial number. Cookie: [init-cookie] [resp-cookie] • StatusA->StatusB—State A to state B. The states Local: local-ip ,Remote: remote-ip, are: [side], Seq: seq-num, IDLING. StatusA->StatusB INI_IKE_SA_INIT_SENT. RES_IKE_SA_INIT_SENT.
Field Description IKEv2 SA payload information, which includes multiple IKEv2 proposals and multiple transform sets: • Len—SA payload length. • Proposal—IKEv2 proposal sequence number. • Protocol-ID—IKE, AH, or ESP. • Trans-num—Number of transform sets. • Prop-len—Proposal length. • SPI—SPI value in hexadecimal notation. • Transform—Transform set sequence number. • Trans-type—Transform set type, which can be ENCR, PRF, INTEG, D-H, and ESN.
Field Description Notify message payload information: • Protocol-ID—The value can be 0, AH, or ESP. • Notify-type—Notify message payload type: [N: Protocol-ID=protocol-id, Notify-type= Notify-type] UNSUPPORTED_CRITICAL_PAYLOAD. INVALID_IKE_SPI. INVALID_MAJOR_VERSION. INVALID_SYNTAX. INVALID_MESSAGE_ID. INVALID_SPI. NO_PROPOSAL_CHOSEN. INVALID_KE_PAYLOAD. AUTHENTICATION_FAILED. SINGLE_PAIR_REQUIRED. NO_ADDITIONAL_SAS. INTERNAL_ADDRESS_FAILURE.
Field Description Initiator TS payload information: • Len—Initiator TS payload length. [TSi: Len=TSi-len value] • value—Initiator TS payload value. Responder TS payload information: • Len—Responder TS payload length. [TSr: Len=TSr-len value] • value—Responder TS payload value. CP payload information: • Len—CP payload length. [CP: Len=cp-len value] • value—CP payload value. Delete message payload information: • Len—Delete message payload length.
[Proposal: #1 Protocol-ID=IKE Trans-num=7 Prop-len=68 [Transform: #1 Trans-type=ENCR Trans-ID=3DES ] [Transform: #2 Trans-type=ENCR Trans-ID=DES ] [Transform: #3 Trans-type=ENCR Trans-ID=AES_CBC [Attr-type=keylen Attr-value=0080]] [Transform: #4 Trans-type=PRF Trans-ID=HMAC_MD5 ] [Transform: #5 Trans-type=INTEG Trans-ID=HMAC_MD5 ] [Transform: #6 Trans-type=D-H Trans-ID=MODP1536 ] [Transform: #7 Trans-type=D-H Trans-ID=MODP2048 ]] [Proposal: #2 Protocol-ID=IKE Trans-num=7 Prop-len=68 [Transform: #1 Trans-typ
[I], Seq:4 INI_IKE_SA_INIT_SENT->INI_IKE_AUTH_SENT // The state of the IKE SA of the initiator changed to INI_IKE_AUTH_SENT from INI_IKE_SA_INIT_SENT.
[CERT: Len=773] [CERT: Len=571] [AUTH: Len=132 Auth-method=RSA-SIG] [SA: Len=36 [Proposal: #1 Protocol-ID=ESP Trans-num=3 Prop-len=36 SPI=09047e7a [Transform: #1 Trans-type=ENCR Trans-ID=3DES ] [Transform: #2 Trans-type=INTEG Trans-ID=HMAC_SHA ] [Transform: #3 Trans-type=ESN Trans-ID=NO-ESN ]]] [TSi: Len=20 01000000070000100000ffff28010100280101ff] [TSr: Len=20 01000000070000100000ffff2b0101002b0101ff] // The responder sent an IKE AUTH message.
20.00% packet loss round-trip min/avg/max = 1/27/70 ms # Enable IKEv2 error debugging. When you configure IKEv2 on the device, output similar to the following example is generated: debugging ikev2 error *Mar 11 15:44:48:860 2011 Sysname IKEV2/7/DEBUG: IKE_AUTH[R] Msg_Receive: Failed to f ind IKEv2 profile. *Mar 11 15:44:49:828 2011 Sysname IKEV2/7/DEBUG: IKE_AUTH[R] Msg_Receive: Failed to f ind IKEv2 profile.
[I], Seq:5 INI_IKE_SA_INIT_SENT->INI_IKE_AUTH_SENT *Mar 11 15:57:05:297 2011 Sysname IKEV2/7/DEBUG: CHILD SA[IPSECSA], [I], ID:21, Local:111.0.0.1,Remote:111.0.0.2 GETSPI_DONE->WAIT_RESPONSE Parent:0,5,5,5 // The initiator triggered IKE SA negotiation, and the state of the CHILD SA changed.
IPv6 basics debugging commands The output description tables in this document only contain fields and messages that require an explanation. The IPv6 Packet Process module name is identified as "IPV6PP" in debugging messages. 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.
terminal debugging debugging ipv6 icmpv6 # Ping 1::2. ping ipv6 -c 1 1::2 When an ICMPv6 packet arrives at an interface with an IPv6 address configured, output similar to the following example is generated: PING 1::2 : 56 *Aug data bytes, press CTRL_C to break 4 00:11:08:147 2006 Sysname ICMPV6/7/debug_ipv6 ICMPv6: ICMPv6 Sent: Type=128, Code=0, Dst = 1::2 // An ICMPv6 packet was sent.
ping ipv6 –c 1 1::2 Output similar to the following example is generated under the condition that IPv6 ND is configured on the interfaces: PING 1::2 : 56 *Aug data bytes, press CTRL_C to break 4 01:13:02:703 2006 Sysname ND/7/debug_ipv6 ND: Adding INCOMPLETE NB Entry: 1::2 on Ethernet1/1 // A neighbor entry whose state is INCOMPLETE was added.
Parameters all: Specifies all types of debugging for ND snooping. error: Specifies ND snooping error debugging. event: Specifies ND snooping event debugging. packet: Specifies ND snooping packet debugging. interface interface-type interface-number: Specifies ND snooping debugging for an interface specified by its type and number. Table 2 describes output fields and messages for the debugging ipv6 nd snooping packet command.
Remove interface ethernet1/1. // Interface Ethernet 1/1 was removed. # Display ND snooping entries. display ipv6 nd snooping IPv6 Address MAC Address VID 3001::3 0015-e943-820e 1 Interface Aging Status Eth1/1 24 Bound ---- Total entries: 1 ---- # Enable ND snooping packet debugging.
// Three DAD NS messages were sent out to check the validity of the received packet. *Jun 23 16:36:26:016 2009 Sysname ND/7/ ND SNOOPING_PACKET: ND Active-ACK Status Changed (IP: 3001::3 VLAN ID: 0x1): State: NewSent ----> Bound Trigger: Time out for new user. // Receiving NA messages timed out. The entry was not updated, and the active acknowledgement status of the ND snooping entry changed from NewSent to Bound. debugging ipv6 packet Use debugging ipv6 packet to enable IPv6 packet debugging.
flow label = 0, payload length = 64, protocol = 58, hop limit = 64, Src = 1::2, Dst = 1::1, prompt: Input an IPv6 packet // The IPv6 packet was received. *Aug 4 01:42:06:378 2006 Sysname IPV6PP/7/debug_ipv6: Delivering, interface = Ethernet1/1, version = 6, traffic class = 0, flow label = 0, payload length = 64, protocol = 58, hop limit = 64, Src = 1::2, Dst = 1::1, prompt: IPv6 packet is delivering up! // IPv6 packet process delivered the received packet to the upper layer.
Prompt-> Successful Addition of PMTU entry // A PMTU entry was added successfully. # Delete a PMTU entry. [Sysname] undo ipv6 pathmtu 1::2 Output similar to the following example is generated: *Aug 4 01:55:47:629 2006 Sysname IPV6PMTU/7/Debug_ipv6_pathmtu: Information-> Delete PMTU Entry at Multiple Index, Value = 1025, Prompt-> Successful Deletion of PMTU Entry // A PMTU entry was deleted successfully. debugging tcp ipv6 event Use debugging tcp ipv6 event to enable IPv6 TCP event debugging.
Usage guidelines If no parameter is specified, this command enables the IPv6 TCP event debugging of all tasks and sockets. (Centralized devices.) If no parameter is specified, this command enables the IPv6 TCP event debugging of all tasks, sockets, and interface cards. (Distributed devices.) If no parameter is specified, this command enables the IPv6 TCP event debugging of all tasks, sockets, and member devices. (Centralized IRF devices.
// The TCP connection state changed to Established. %Aug 4 02:09:23:686 2006 Sysname SHELL/4/LOGIN: VTY login from 2::3 debugging tcp ipv6 md5 Use debugging tcp ipv6 md5 to enable IPv6 TCP MD5 authentication debugging. Use undo debugging tcp ipv6 md5 to disable IPv6 TCP MD5 authentication debugging. Syntax debugging tcp ipv6 md5 undo debugging tcp ipv6 md5 Default IPv6 TCP MD5 authentication debugging is disabled.
0000003400000006083D00B37A9CDD8E0C02658AD010200000000000, TCP6 data: , MD5 info: 30313233 *Jun 22 14:31:31:615 2009 Sysname IPV6TCP/7/TCP6 MD5: TCP6 MD5 authentication succeeded, total option length is 32, MD5 digest is 2f2641c fd0337c4f19ba5255c89737ed // MD5 decryption was performed on the received TCP packets, and MD5 authentication was passed. debugging tcp ipv6 packet Use debugging tcp ipv6 packet to enable IPv6 TCP packet debugging.
If no parameter is specified, this command enables the IPv6 TCP packet debugging of all tasks, sockets, and interface cards. (Distributed devices.) If no parameter is specified, this command enables the IPv6 TCP packet debugging of all tasks, sockets, and member devices. (Centralized IRF devices.) Examples # Enable IPv6 TCP packet debugging on the device that supports IPv6. The device's interfaces have IPv6 addresses.
undo debugging udp ipv6 packet [ task-id socket-id ] Default IPv6 UDP packet debugging is disabled. Views User view Default command level 1: Monitor level Parameters task-id: Specifies the task ID in the range of 1 to 100. socket-id: Specifies the socket ID in the range of 0 to 3072. Usage guidelines If no parameter is specified, this command enables the IPv6 UDP packet debugging of all tasks and sockets. Examples # Enable IPv6 UDP packet debugging of all sockets and tasks.
IPv6 MBGP debugging commands debugging bgp update ipv6 multicast Use debugging bgp update ipv6 multicast to enable BGP update debugging for IPv6-MBGP address family. Use the undo debugging bgp update ipv6 command to disable BGP update debugging for IPv6-MBGP address family.
Field Description Err/SubEr Error code/sub-error code. Errdata: Error data. Send UPDATE to x.x.x.x BGP sent an update message to BGP neighbor x.x.x.x. Send UPDATE(Withdraw) to peer x.x.x.x BGP sent an update withdraw message to BGP neighbor x.x.x.x. x.x.x.x/xx Destination IP address/mask. INBOUND Inbound policy. LocRemCross:Export Policy Check Failed BGP exported policy check error when importing routes to VRF routing table.
debugging bgp update ipv6 multicast packet *Apr 2 17:46:55:830 2007 Sysname-Comware RM/6/RMDEBUG: BGP_MBGP.
IPv6 multicast routing and forwarding 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.
debugging mfib ipv6 { all | { driver | no-cache | packet | register | route | sync | upcall | wrong-iif } [ advanced-acl6-number ] } [ chassis chassis-number slot slot-number ] undo debugging mfib ipv6 { all | { driver | no-cache | packet | register | route | sync | upcall | wrong-iif } [ advanced-acl6-number ] } [ chassis chassis-number slot slot-number ] Default IPv6 MFIB debugging is disabled.
Table 3 describes output fields and messages for the debugging mfib ipv6 no-cache command. Table 130 Output from the debugging mfib ipv6 no-cache command Field Description Receive no cache report The IPv6 MFIB received an unknown IPv6 multicast data packet. No MFIB entry matches The IPv6 MFIB failed to find the matching entry. (sadd, gadd) (S, G) entry. Cache the packet The IPv6 MFIB cached IPv6 data packets. Table 4 describes output fields and messages for the debugging mfib ipv6 packet command.
Field Description del-entry message The IPv6 MFIB received a del-entry message from IPv6 MRM. set-IIF message The IPv6 MFIB received a set-IIF message from IPv6 MRM. del-OIF message The IPv6 MFIB received a del-OIF message from IPv6 MRM. add-OIF message The IPv6 MFIB received an add-OIF message from IPv6 MRM. MRM IPv6 multicast routing module. The Following OIFs are added The following outgoing interfaces were added. (sadd, gadd) (S, G) entry.
Field Description (sadd, gadd) (S, G) entry. Examples • On multi-core devices: # Enable IPv6 MFIB packet debugging. When IPv6 PIM-DM is enabled , output similar to the following example is generated: debugging mfib ipv6 packet *Apr 26 12:11:42:03 2008 Sysname DP_MFIB/7/PACKET: (IPv6 0): (40::2, FF1E::101:101) Receive packet from interface Ethernet1/1 in vcpu 7. (D46144) // The IPv6 MFIB received a multicast packet (40::2, FF1E::101:101) from Ethernet 1/1 on VCPU 7.
// The data plane also created an entry for the IPv6 multicast packet (40::2, FF1E::101:101). *Apr 26 12:17:11:59 2008 Sysname MFIB/7/MFIB ROUTE: IPv6 (public net): Receive add-entry message of (40::2, FF1E::101:101) from MRM, OIF num is 1.(A112176) // An add-entry message was received from the IPv6 MRM for adding an entry for (40::2, FF1E::101:101) with the outgoing interface number of 1.
debugging mfib ipv6 packet *Apr 26 12:33:31:267 2000 Sysname MFIB/7/MFIB PACKET: IPv6 (public net): Receive packet (40::2, FF1E::101:101), iif = Vlan-interface20, TTL = 128(A08482) // The IPv6 MFIB received the IPv6 multicast data (40::2, FF1E::101:101) with the TTL value of 128 from VLAN-interface 20.
// The IPv6 MFIB received the multicast packet (40::2, FF1E::101:101). No forwarding entry for the packet was found. The IPv6 MFIB created a dummy forwarding entry. *Apr 26 12:40:31:466 2000 Sysname MFIB/7/MFIB ROUTE: IPv6 (public net): Receive add-entry message of IPv6 entry (40::2, FF1E::101:101) from MRM, OIF num is 1.(A112030) // The IPv6 MFIB received an add-entry message from MRM for adding the (40::2, FF1E::101:101) entry with the outgoing interface number of 1.
Syntax debugging mrm ipv6 { all | event | packet [ advanced-acl6-number ] | route [ advanced-acl6-number ] } undo debugging mrm ipv6 { all | event | packet | route } Default IPv6 MRM debugging is disabled. Views User view Default command level 2: System level Parameters all: Specifies all types of debugging for IPv6 multicast routing management (MRM). event: Specifies IPv6 MRM event debugging. packet: Specifies debugging for IPv6 MRM packets. route: Specifies IPv6 MRM route debugging.
Table 139 Output from the debugging mrm ipv6 route command Field Description lost the route A route was deleted. a new route A new route was added. (sadd, gadd) (S, G) entry. Examples # Enable IPv6 MRM event debugging. When IPv6 PIM-SM is enabled, output similar to the following example is generated: debugging mrm ipv6 event *0.
IPv6 NetStream debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ipv6 netstream event Use debugging ipv6 netstream event to enable IPv6 NetStream event debugging. Use undo debugging ipv6 netstream event to disable IPv6 NetStream event debugging. Syntax debugging ipv6 netstream event undo debugging ipv6 netstream event Default IPv6 NetStream event debugging is disabled.
Field Description IPv6 Stream Age 1 streams (inactive timeout) An IPv6 stream entry aged out due to inactive flow aging. IPv6 Stream Age 1 streams (age all) An IPv6 stream entry aged out due to forced aging. IPv6 Stream Age 1 streams (cache full) An IPv6 stream entry aged out due to entry overflow. IPv6 Stream Age all streams (cache modify) All IPv6 stream entries aged out due to cache modification. IPv6 Stream Age all streams (reset) All IPv6 stream entries aged out (reset).
Field Description Send 1 packets (enter queue) A packet was sent and entered the packet export queue. A packet was successfully sent: Succeed in sending (Now queue length is 0) Packet Type: Normal IPv6 Version No: 9 Records: 1 • • • • Packet export queue is 0. Packet type is single IP stream. Packet format is v9. Number of IP stream entries is 1.
Field Description Fields in an IPv6 stream entry: CPU 0 IPv6 Stream Add to active list: Direct: O Stream Type: IPv6 IP version: 6 InIf: 0 OutIf: 51314696 InVrf: 0 OutVrf: 0 SrcIP: 1:2::3:4 DstIP: 1:2::3:5 Prot: 58 SrcPort: 0 DstPort: 32768 Tos: 0x0 FlowLabel: 0x0 TcpFlag: 0x0 SrcAS: 0 DstAS: 0 SrcMask: 0 DstMask: 0 Nexthop: 1:2::3:5 BGP Nexthop: :: Lable 1:0-0-0 2:0-0-0 3:0-0-0 TopLabel Type: UNKNOWN IP: 0.0.0.0 Mask: 0.0.0.
• AS aggregation is enabled. • Version 9 is configured. • The inactive timer is set to 10 seconds. # Enable IPv4 NetStream event debugging. Output similar to the following example is generated when an IP packet arrives at Ethernet 1/0.
Nexthop: 1:2::3:5 BGP Nexthop: :: Lable 1:0-0-0 2:0-0-0 3:0-0-0 TopLabel Type: UNKNOWN IP: 0.0.0.0 Mask: 0.0.0.0 SrcMAC: 0000-0000-0000 DstMAC: 0000-0000-0000 SrcVlan: 0 DstVlan: 0 First: 12381680 Last: 12381680 Pkts: 0 1 Bytes: 0 104 // An IP stream entry was exported.
// IPv6 NetStream was sending a packet. *Mar 21 12:53:37:765 2008 H3C NS6/7/NS6_EVENT: Succeed in sending (Now queue length is 0): Packet Type: Aggre as Version No: 0 Records: 1 // A packet was successfully sent. *Mar 21 12:53:37:765 2008 H3C NS6/7/NS6_EVENT: CPU 0 as Aggre Export 1 packets for timeout // An AS aggregation packet was sent. debugging ipv6 netstream packet Use debugging ipv6 netstream packet to enable IPv6 NetStream packet debugging.
debugging ipv6 netstream packet *Mar 21 13:17:33:562 2008 H3C NS6/7/NS6_PACKET: Send succeed! Packet Type: Normal IPv6 Version No: 0 Records: 1 SrcIP(Port): 192.168.20.173(40000) DstIP(Port): 192.168.20.180(138) VrfID: 0 // A normal IPv6 stream was sent successfully.
IPv6 PIM debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging pim ipv6 Use debugging pim ipv6 to enable IPv6 PIM debugging. Use undo debugging pim ipv6 to disable IPv6 PIM debugging.
rp: Specifies debugging for IPv6 PIM packets related to the BSR and the RP. state-refresh: Specifies IPv6 PIM state refresh message debugging. Usage guidelines Table 1 describes output fields and messages for the debugging pim ipv6 assert command. Table 142 Output from the debugging pim ipv6 assert command Field Description pref Preference value. metric Metric value. rpt set/unset The RPT bit is 1/0. reserved field non-zero The reserved field is non-zero.
Table 144 Output from the debugging pim ipv6 event command Field Description unsupported PIM version The IPv6 PIM packet version is not supported. PIM packet too short The IPv6 PIM packet is too short. checksum error Incorrect packet checksum. non-pim interface An IPv6 PIM message was received on a non-PIM-enabled interface. unsupported type The specified IPv6 PIM packet type is not supported. Socket set option error Socket option setting failed.
Field Description Failed to pass MSF Failed to pass IPv6 multicast source filtering. NotOriginator/Originator The Originator state machine was in not-originator/originator state. SAT Expired The source-alive timer timed out. Join suppressed The device received a join message to the upstream neighbor on the incoming interface and suppressed its own join message. Override it The device received a prune message to the upstream neighbor on the incoming interface and sent a join message.
Field Description group boundary detected for address1 on address2 Address 1 is within the multicast boundary range configured on the interface corresponding to Address 2. Group address1 ignored in message on address2 Address 1 is within the multicast boundary configured on the interface corresponding to Address 2. This group is ignored. Message from unknown neighbor A message was received from an unknown neighbor.
Field Description Failed to create PIM neighbor address, PIM Hello denied by neighbor policy on interfacename A PIM neighbor relationship failed to be established because the source address in the hello message failed to pass the configured hello message filtering. Table 6 describes output fields and messages for the debugging pim ipv6 register command. Table 147 Output from the debugging pim ipv6 register command Field Description REG Register message. RSP Register-stop message.
Field Description BSR Bootstrap router. prefix count Prefix count field in the C-RP advertisement message. priority Priority field in the C-RP advertisement message. holdtime Holdtime field in the C-RP advertisement message. Admin Scope Zone Administratively scoped zone. Bad BSR address Incorrect BSR address. frag Fragment tag field in the BSR bootstrap message. pri Priority field in the BSR bootstrap message. hash mask len Hash mask length field in the BSR bootstrap message.
Field Description no BSR is available No BSR is available. add/remove register vif A register virtual interface was added or removed. Expiring CRP C-RP that aged out. Lose the ASBSR election The device lost the BSR election in the BSR admin-scope region. Lose the BSR election The device lost the BSR election. locally scoped Node-local or link-local scope. RP changed The RP has changed. pending state The BSR changed to the pending state.
// IPv6 PIM received an IPv6 PIMv2 assert message from FE80::2E0:FCFF:FE02:1A01 to FF02::D on VLAN-interface 2. # Enable debugging for outbound IPv6 PIM assert messages. debugging pim ipv6 assert send *0.7328718 Sysname PIM/7/ASSERT:IPv6:(public net): PIM ver 2 AST sending FE80::2E0:FCFF:FE02:1A01 -> FF02::D on Vlan-interface20 (P012343) *0.
*May 21 17:06:04:672 2010 Sysname PIM/7/DF: IPv6:(public net): DF election state changed from Offer to Win for RP: 2010::1 on interface Vlan-interface2 (P51273) *May 21 17:06:04:687 2010 Sysname PIM/7/DF: IPv6:(public net): Set DF to FE80::2002(pref: 0, metric: 0) for RP: 2010::1 on interface Vlan-interface2 (P51411) *May 21 17:06:04:687 2010 Sysname PIM/7/DF: IPv6:(public net): Send bidir-pim Winner packet at interface Vlan-interface2 (P501065) *May 21 17:06:04:703 2010 Sysname PIM/7/DF: IPv6:(public net):
*0.3275671 Sysname PIM/7/NBR:IPv6:(public net): PIM ver 2 HEL receiving FE80::2E0:FCFF:FE02:1E01 -> FF02::D on Vlan-interface20 (P011857) *0.3275671 Sysname PIM/7/NBR:IPv6:(public net): Option: 1, length: 2 (P011891) *0.3275671 Sysname PIM/7/NBR:IPv6:(public net): Holdtime: 105 (P011898) *0.3275671 Sysname PIM/7/NBR:IPv6:(public net): Option: 2, length: 4 (P011891) *0.3275687 Sysname PIM/7/NBR:IPv6:(public net): Tbit: unset (P011907) *0.
*0.6489328 Sysname PIM/7/REG:IPv6:(public net): Register Stop: (100:100::168, FF0E::101:101) (S01650) // IPv6 PIM received a register-stop message from 130::130:130 to 100:100::1 on VLAN-interface 20. In the register-stop message, the group address is FF0E::101:101 and the source address is 100:100::168. # Enable debugging for outbound IPv6 PIM register messages. debugging pim ipv6 register send *0.
*0.5358204 Sysname PIM/7/RP:IPv6:(public net): PIM ver 2 CRP sending 130::130:130 -> 120::120:120 on Vlan-interface20 (S01409) *0.5358204 Sysname PIM/7/RP:IPv6:(public net): C-RP 130::130:130, prefix count 1, priority: 0, holdtime 150 (S01433) *0.5358204 Sysname PIM/7/RP:IPv6:(public net): FF00::/8 (S01454) *0.
// IPv6 PIM sent a state refresh message from FE80::2E0:FCFF:FE02:1A01 to FF02::D out of VLAN-interface 20.
IPv6 policy-based routing debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging ipv6 policy-based-route Use debugging ipv6 policy-based-route to enable IPv6 policy-based routing (PBR) debugging. Use undo debugging ipv6 policy-based-route to disable IPv6 PBR debugging. Syntax debugging ipv6 policy-based-route undo debugging ipv6 policy-based-route Default IPv6 PBR debugging is disabled.
Field Description Failed to modify policy policyname by deleting policy node by ID IPv6 PBR failed to delete a node with the specified ID from policy policyname. Succeeded to modify policy policyname by deleting policy node by mode IPv6 PBR succeeded in deleting a node with the specified node mode from policy policyname. Failed to modify policy policyname by deleting policy node by mode IPv6 PBR failed to delete a node with the specified node mode from policy policyname.
Field Description Failed to modify policy policyname by deleting all default output interface items IPv6 PBR failed to delete all default outgoing interfaces for permitted IPv6 packets from policy policyname. Succeeded to modify policy policyname by deleting a default output interface item IPv6 PBR succeeded in deleting a default outgoing interface for permitted IPv6 packets from policy policyname.
Field Description Succeeded to create policy policyname by setting an apply item IPv6 PBR succeeded in setting an apply clause for creating policy policyname. Failed to create policy policyname by setting an apply item IPv6 PBR failed to set an apply clause for creating policy policyname. Succeeded to rebind policy by setting an apply item IPv6 PBR succeeded in setting an apply clause for rebinding policy policyname to an interface or the local system.
Field Description Binding policy: Interfacename : policyname IPv6 PBR is bounding interface Interfacename to policy policyname. Rebinding policy: Interfacename : policyname1 -> policyname2 IPv6 PBR removed the binding of policy policyname1 from an interface, and bound policy policyname2 to the interface. Unbinding policy: interfacename : policyname IPv6 PBR removed the binding of policy policyname from interface interfacename.
Field Description Outputting packets IPv6 PBR is sending out local packets. Failed to forward packets for an unspecified source address is detected IPv6 PBR failed to forward packets because of unspecified source addresses. Failed to forward packets for the source address is a link-local address but the destination address isn't IPv6 PBR failed to forward packets because the source address is a local address of the link but the destination address is not a local address of the link.
IPX debugging commands debugging ipx packet Use debugging ipx packet to enable IPX packet debugging. Use undo debugging ipx packet to disable IPX packet debugging. Syntax debugging ipx packet [ interface-type interface-number ] undo debugging ipx packet [ interface-type interface-number ] Default IPX packet debugging is disabled. Views User view Default command level 1: Monitor level Parameters interface-type interface-number: Type and number of the specified interface.
Field Description promt Packet processing result or discarding reason. IPX packet is delivering up Received IPX packet is delivered to the upper layers for processing. Sending the packet System is sending the IPX packet at the network layer. Invalid MBuf Invalid buffer for packets. Getting interface failed Inbound interface of a packet does not exist. Not IPX interface IPX protocol is disabled on the receiving interface.
prompt: IPX packet is delivering up! // Ethernet 1/1 received an IPX packet. debugging ipx ping Use debugging ipx ping to enable IPX ping debugging. Use undo debugging ipx ping to disable IPX ping debugging. Syntax debugging ipx ping undo debugging ipx ping Default IPX ping debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 2 describes output fields and messages for the debugging ipx ping command.
debugging ipx rip Use debugging ipx rip to enable IPX RIP debugging. Use undo debugging ipx rip to disable IPX RIP debugging. Syntax debugging ipx rip { event | packet [ verbose ] } undo debugging ipx rip { event | packet [ verbose ] } Default IPX RIP debugging is disabled. Views User view Default command level 1: Monitor level Parameters event: IPX RIP event debugging. packet: IPX RIP packet debugging. verbose: Displays detailed information about IPX RIP packet debugging.
Field Description The interface interface-name is down, can't send packet Interface failed to send IPX RIP packets because the IPX protocol is down on the interface. Table 4 describes output fields and messages for the debugging ipx rip packet command. Table 155 Output from the debugging ipx rip packet command Field Description Routing information for an IPX RIP packet: Network network, hops hops, delay ticks • network—Destination IPX network number. • hops—Number of hops.
debugging ipx rtpro-flush Use debugging ipx rtpro-flush to enable IPX routing flush debugging. Use undo debugging ipx rtpro-flush to disable IPX routing flush debugging. Syntax debugging ipx rtpro-flush undo debugging ipx rtpro-flush Default IPX routing flush debugging is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 5 describes output fields and messages for the debugging ipx rtpro-flush command.
Default Interface change debugging for IPX routing is disabled. Views User view Default command level 1: Monitor level Usage guidelines Table 6 describes output fields and messages for the debugging ipx rtpro-interface command. Table 157 Output from the debugging ipx rtpro-interface command Field Description msg type Type of the interface change message. if_index Internal index of the interface. if_index is ifIndex . Name of the interface.
Interface name is Ethernet1/1 . // IPXRM received a message that the IPX protocol is down on Ethernet 1/1. [Sysname-Ethernet1/1] undo shutdown %Jul 24 15:33:17:297 2006 Sysname IFNET/4/UPDOWN: Line protocol on the interface Ethernet1/1 is UP %Jul 24 15:33:17:297 2006 Sysname IFNET/4/UPDOWN: Protocol IPX on the interface Ethernet1/1 is UP *Jul 24 15:33:17:297 2006 Sysname RMX/7/DBG: IPXRM receive interface change msg, msg type IPX_IF_UP . if_index is 0xf0018 . Interface name is Ethernet1/1 .
Field Description FREE route Router memory is released. rt add failed because exceed rt capacity Adding a route failed because the number of routes reached the maximum. rt add failed because exceed static rt capacity Adding a static route failed because the number of static routes reached the maximum. rt add failed because exceed dest network capacity Adding a route failed because the network number reached the upper limit supported.
verbose: Displays detailed information about IPX SAP packet debugging. Usage guidelines The debugging ipx sap command generates a large number of outputs. Disable IPX SAP debugging once debugging is completed. Table 8 describes output fields and messages for the debugging ipx sap event command. Table 159 Output from the debugging ipx sap event command Field Description Net-ID Destination network number of a RIP route. Route UP Event Received System receives an event that a RIP route is up.
Examples # Enable IPX SAP packet debugging. When the router receives service information, output similar to the following example is generated: debugging ipx sap packet verbose *Jul 24 18:18:50:844 2007 Sysname IPXSAP/7/IPX SAP : MSG:Recieve Response Packet From Eth1/1,Length 160 Src: 0001.0000-5e01-180a (0452) Dest: 0001.ffff-ffff-ffff (0452) *Jul 24 18:18:50:844 2007 Sysname IPXSAP/7/: Number of entries in pkt: 2 Server type 0003 "Print" 0200.
IRF debugging commands IRF is managed by the stack topology management (STM) module. The output description tables in this document only contain fields and messages that require an explanation. debugging stm all Use debugging stm all to enable all types of IRF debugging. Use undo debugging stm all to disable all types of IRF debugging.
Default command level 1: Monitor level Parameters all: Specifies all types of IRF topology collection debugging. error: Specifies topology collection error debugging. event: Specifies topology collection event debugging. notify: Specifies topology notification debugging. This keyword is reserved for future use. packet: Specifies topology collection packet debugging. state: Specifies topology collection state debugging. This keyword is reserved for future use.
Field Description Set irf port failed. Ret: ret Enabling or disabling an IRF port failed because of a driver interface call failure. Irf-port is already down. Irf-port: irf port The IRF port had been down when STM received the down event message from the driver. Irf-port is already up. Irf-port: irf port The IRF port had been up when STM received the up event message from the driver. Write queue failed.
Table 3 describes output fields and messages for the debugging stm topology packet command. Table 163 Output from the debugging stm topology packet command Field Description src_MAC_addr: mac_addr Source MAC address. dst_MAC_addr: mac_addr Destination MAC address. op: opration Packet type. It is 1 for hello packet. ver: version Version of the STM module. This field is always 1. Source IRF port index: • 1—IRF-port 1. • 2—IRF-port 2.
Default command level 1: Monitor level Parameters all: Specifies all types of master election debugging. b-mac: Specifies master election MAC address debugging. This keyword is reserved for future use. error: Specifies master election error debugging. event: Specifies master election event debugging. packet: Specifies master election packet debugging. state: Specifies master election state debugging. timer: Specifies master election timer debugging.
Field Description The configured IRF bridge MAC persistence setting was the same as the existing setting. IRF bridge MAC persistence settings for the type field: Function type set is same with local configuration. Type: type • 0—Bridge MAC address of the IRF fabric does not change after the master leaves. • 1—Bridge MAC address of the IRF fabric persists for six minutes after the master leaves. • 2—Bridge MAC address of the new master replaces the original one as soon as the old master leaves.
Table 168 Output from the debugging stm election timer command Field Description Failed to create ELECT timer, error code errcode STM failed to create a timer for sending election packets. Examples # Enable master election debugging on the IRF fabric. The output in this example was created on a daisy-chained two-member IRF fabric. debugging stm election packet *Nov 18 16:39:38:00 2008 Sysname STM/4/ROLE PACKET:Chassis=2-Slot=1; Receieve election packet.
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. The value range varies by device model. all: Specifies all cards. Usage guidelines Table 9 describes output fields and messages for the debugging mad error command.
IRF debugging commands The IRF module name is identified as "HA" in debugging messages. IRF is managed by the stack topology management (STM) module. The output description tables in this document only contain fields and messages that require an explanation. debugging ha Use debugging ha to enable IRF debugging. Use undo debugging ha to disable IRF debugging.
Table 171 Output from the debugging ha message command Field Description Sending STM sent messages to the destination module. Deliver up STM sent control messages to application modules. From Module STM received messages from application modules. Src MID Source module ID. Src SID Source module sub-ID. Dst MID Destination module ID. Dst SID Destination module sub-ID. Type Message type. Table 3 describes values available for this field. Len Message length.
Field Description Type = 11 Smoothing information of an internal module. Type = 12 Batch backup of all modules was completed. Table 4 describes output fields and messages for the debugging ha state command. Table 173 Output from the debugging ha state command Field Description FSM state (standby slaveID): Receiving batch data. The subordinate device slaveID was receiving backup data in batch from the master device. FSM state (standby slaveID): Receiving real-time and routine data.
Default All types of IRF STM debugging are disabled. Views User view Default command level 1: Monitor level Parameters slot slot-number: Specifies an IRF member device by its member ID. Usage guidelines This debugging command enables both IRF topology debugging and master election debugging. Examples # Enable all types of STM debugging on the IRF fabric.
Default All types of IRF topology collection debugging are disabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of IRF topology collection debugging. error: Specifies topology collection error debugging. event: Specifies topology collection event debugging. packet: Specifies topology collection packet debugging. slot slot-number: Specifies an IRF member device by its member ID.
debugging stm election Use debugging stm election to enable master election debugging. Use undo debugging stm election to disable master election debugging. Syntax debugging stm election { all | event | packet | timer | state } [ slot slot-number ] undo debugging stm election { all | event | packet | timer | state } [ slot slot-number ] Default Master election debugging is disabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of master election debugging.
Table 176 Output from the debugging stm election packet command Field Description Operation type: Op: opration • 18—Election acknowledgement packet. • 19—Notification packet. Num: num Number of member devices. Ms: index Index of the current master in the topology database. Len: len Total length of the packet. Port: port IRF port that received or sent the packet. Version: version Software version of the master. Content is: packet content Packet content in binary.
Send election packet. Summary: Op:19 Num:2 Ms:0 Len:32 Port:2 Version: V200R002B60D002 Content is: 000: 00 0f e2 69 5b 76 00 0f e2 69 5b 76 00 05 01 01 00 0f e2 69 47 e6 00 00 018: 00 00 00 00 00 04 01 03 // Member device 1 sent a master election packet.
ISDN debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging isdn Use debugging isdn to enable ISDN debugging. Use undo debugging isdn to disable ISDN debugging. Syntax debugging isdn { cc | q921 | q931 | qsig | spid } [ interface interface-type interface-number ] undo debugging isdn { cc | q921 | q931 | qsig | spid } [ interface interface-type interface-number ] Default All types of ISDN debugging are disabled.
Field Description ISDN_CONN_REQ Connect request sent to CC by USER. ISDN_DISC_REQ Disconnect request sent to CC by USER. ISDN_DISC_RES Disconnect response sent to CC by USER. ISDN_CALLPROC_REQ Call-proceeding request sent to CC by USER. ISDN_PROGRESS_REQ Progress request sent to CC by USER. ISDN_ALERTING_REQ Alerting request sent to CC by USER. ISDN_INFORMATION_REQ Information request sent to CC by USER. ISDN_FACILITY_REQ Facility request sent to CC by USER.
Field Description szCallingNum Caller number. Channel Channel ID. chan_id Channel ID information element. Table 2 describes output fields and messages for the debugging isdn q931 command. Table 180 Output from the debugging isdn q931 command Field Description DL_I_Data_Req Packet request sent to the Q.921 module by the Q.931 module. DL_I_Data_Ind Packet instruction sent to the Q.931 module by the Q.921 module. CES Connect point ID. cr_length Call reference value length. cr Call reference.
Field Description p/f Value of the P/F bit. Examples # Configure the E1/PRI interface Serial 0/1/0:15 on Router A to operate as the network side. system-view [RouterA] interface Serial0/1/0:15 [RouterA-Serial1/0:15] link-protocol ppp [RouterA-Serial1/0:15] ip address 10.0.0.1 255.255.255.
// The Q931 module sent a Setup request to Q921 module. *0.4719793 Sysname-Comware Q931/8/Q931_Debug: Serial0/1/0:15 ISDN L3 timer T303 started, Call Reference = 0x0005. // The Q931 module triggered the timer. *0.4719793 Sysname-Comware Q931/8/Q931_Debug: Serial0/1/0:15 ISDN Layer 3 call state change: CS_NULL -> CS_CALL_PRESENT // The Q931 module turned from Null state to Call-present state. *0.
// CC sent a request to the Q931 module. *0.4719813 Sysname-Comware Q931/8/Q931_Debug: Serial0/1/0:15 Q931->Q921 cr_length= 2 DL_I_Data_Req CES = 1 cr= 02 00 05 CONNECT_ACK // The Q931 module sent an active message to Q921. *0.4719813 Sysname-Comware Q931/8/Q931_Debug: Serial0/1/0:15 ISDN Layer 3 call state change: CS_CONNECT_REQUEST -> CS_ACTIVE // The Q931 module turned from Connect request state to Active state. *0.
IS-IS debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging isis Use debugging isis to enable debugging for IS-IS. Use undo debugging isis to disable debugging for IS-IS.
graceful-restart: Specifies debugging for IS-IS GR. ha-events: Specifies debugging for data hot backup. This keyword takes effect only on a distributed device. interface-information: Specifies IS-IS interface debugging. memory-allocating: Specifies debugging for IS-IS memory allocation. non-stop-routing: Specifies debugging for IS-IS non-stop routing (NSR). receiving-packet-content: Specifies debugging for received IS-IS packet contents. self-originate-update: Specifies debugging for IS-IS local updates.
Field Description IS-IS is declaring the new DIS. Declaring as DIS,DIS Type type,on circuitName, Old DIS (net1), New DIS net2 • type—L1 or L2. • net1—Net entity title of the old DIS. • net2—Net entity title of the new DIS. Send Failure IS-IS failed to send a hello packet. Update DIS Down Processing Failure IS-IS failed to process the DIS Down event. Circuit State change reported for Unknown Circuit Type Interface type change error due to unknown interface type.
Field Description Rxed Serial IIH on circuitName, Protocol supported mismatch. IIH Discarded Rxed P2P IIH on % circuitName contains no Protocol Support at all. IIH Ignored The received hello packet was discarded because of a protocol mismatch. circuitName indicates the interface name. The received hello packet was discarded because there was no protocol support. circuitName indicates the interface name. The received Ethernet IIH packet was discarded because the interface type was not broadcast.
Table 4 describes output fields and messages for the debugging isis circuit-information command. Table 185 Output from the debugging isis circuit-information command Field Description IPv4 is not enabled on the interface. circuitName not enabled for Ipv4 circuitName indicates the interface name. IPv6 is not enabled on the interface. circuitName not enabled for Ipv6 circuitName indicates the interface name. IS-IS is not enabled on the interface.
Table 186 Output from the debugging isis datalink-receiving-packet command Field Description Circuit NOT operationally ON Interface is not on for operation. SYS not functional. Ignoring recvd packet System is not functioning and it ignores the received packets. Rxed IS-IS PDU on Circuit circuitName, PDU's type is packetType IS-IS received a PDU on the interface. • circuitName—Interface name. • packetType—Interface type.
Table 189 Output from the debugging isis graceful-restart command Field Description GR timer started. • levelType—System type: L1 or L2. • count—Number of times GR timer has started. • circName—Interface name. RST: levelType T1 Timer Started on circName, Counter: count RST: Notifying RM that the Process is Entering Restart. IS-IS notifies RM that the process is entering the GR state. RST: Notifying RM that the Process is Leaving Restart (Due to Rst Disable).
Table 191 Output from the debugging isis interface-information command Field Description CIRC: MTU Size Exceeds Max PDU Size mtuSize, Setting it to Max PDU Size. The interface MTU exceeds the maximum PDU size. The interface MTU is being set to the maximum PDU size. IF: Disable ip route isis Failed IS-IS failed to disable IP routing on the interface. IF:Can't get the interface index IS-IS cannot obtain the interface index. IF:Can't get the interface type IS-IS cannot obtain the interface type.
Field Description NSR completes recovering adjacency information. ISIS-procId-NSR_EVE: End to smooth enable levelType adjacency. levelType indicates the neighbor level, Level-1 and Level-2. NSR_EVE: Begin to flush routes. NSR starts aging routes. NSR_EVE: End to flush routes. NSR completes aging routes. NSR starts purging local backup LSPs. NSR_EVE: Begin to purge local LevelType LSP. levelType indicates the LSP level, Level-1 and Level-2. NSR completes purging local backup LSPs.
Field Description The IPv4/IPv6 address was added to the interface. UPDT: Circuit Ipv4/v6 Addr add ipAddress ipAddress indicates the interface IP address. The IPv4/IPv6 address was deleted from the interface. UPDT: Circuit Ipv4/v6 Addr Del ipAddress ipAddress indicates the interface IP address. The default cost of the local interface changed. UPDT: Rxed levelType Default cost Change levelType indicates the interface level type: L1 or L2.
Field Description IS-IS received PDUs. • pduType—PDU type: PSNP or CSNP. • sourceId—Source NSAP address of the packet. • circuitName—Name of the receiving interface. Rxed pduType From sourceId (circuitName) SNP PDU Dropped SNP PDU was dropped. IS-IS failed to send a PSNP packet. Sending Level pduLevel PSNP PDU fails pduLevel indicates the PDU packet level: L1 or L2. IS-IS is sending a PSNP packet. • circuitName—Name of the sending interface. • content—PSNP packet content.
Table 198 Output from the debugging isis update-packet command Field Description pdu length: pduLen Length of received PDU. Adjacency Usage: adjType Adjacency type. LSPs are fast-flooded before SPF calculation. Fast Flood levelType LSP before SPF levelType: LSP level: L1 or L2. RECV: Rxed IS-IS PDU of pduLen which is greater than receive size(receiveLen) IS-IS received a PDU with a pduLen greater than receive size (receiveLen).
Field Description UPDT: Received LSP Not processed on Broadcast Circuit due to Low Memory, LSP Dropped The received LSP was dropped because of insufficient memory of the broadcast interface. UPDT: Received LSP Not processed on P2P Circuit due to Low Memory, Sending Acknowledgement) The received LSP was dropped because of insufficient memory of the P2P interface and an acknowledgement packet was sent. UPDT: LSP newer than data base copy The received LSP is newer and the local LSDB is updated.
When you disable IS-IS and then enable it on VLAN-interface 100 of Router A, output similar to the following example is generated: debugging isis circuit-information system-view [Sysname] interface vlan-interface 100 [Sysname-Vlan-interface100] undo isis enable [Sysname-Vlan-interface100] isis enable ISIS-1-CIRC: Received Circuit OperState ON : Enabling the Circuit ISIS-1-CIRC: The IP is set to UP for IS-IS on interface Vlan100 // The IP address took effect on the IS-IS interface.
// IS-IS added the neighbor TLV to the local LSPs, and IS-IS added the reachable TLV with an IP prefix of 100.1.1.0/24 to L1 and L2 LSPs. # Enable IS-IS NSR debugging on Router A. The output in this example was created when the following conditions exist: • Router A and Router B are interconnected. • IS-IS is enabled on Router A and Router B.
ISIS-1-NSR_EVE: End to purge local Level-2 LSP. // NSR completed purging local Level-2 LSPs. debugging isis bfd-event Use debugging isis bfd-event to enable IS-IS BFD event debugging. Use undo debugging isis bfd-event to disable IS-IS BFD event debugging. Syntax debugging isis bfd-event [ process-id | vpn-instance vpn-instance-name ] undo debugging isis bfd-event [ process-id | vpn-instance vpn-instance-name ] Default IS-IS BFD event debugging is disabled.
Table 199 Output from the debugging isis bfd-event command Field Description BFD session information that IS-IS notifies to the BFD module. • process-id—IS-IS process ID. • Msg type typevalue—Message type: ISIS- process-id -BFD: Success to send msg. Msg type typevalue . IfPhyIndex: nn ,DstIPAddr: XX.XX.XX.XX , SrcIPAddr:YY.YY.YY.YY, NeighborType: leveltype 0—Create a session. 1—Remove a session. 2—Disable a session. • IfPhyIndex—Physical index of the session interface.
undo debugging isis ldp-sync [ process-id | vpn-instance vpn-instance-name ] Default IS-IS LDP synchronization debugging is disabled. Views User view Default command level 1: Monitor level Parameters process-id: Specifies an IS-IS process by its ID, in the range of 1 to 65535. If no process ID is specified, the command enables or disables IS-IS LDP synchronization debugging for all the IS-IS processes of the current VPN instance.
Field Description LDP-IGP synchronization state changed to circstate on interface circuitname. The circstate can be: LDP-Sync state changed to circstate on circuitname. • Init—Initialization state. • Hold Down—IS-IS does not establish neighbor relationship but waits for the LDP session convergence. • Max Cost—IS-IS advertises the maximum cost in LSPs. • Achieved—LDP-IGP synchronization is complete. LDP-Sync state changed from adjstate1 to adjstate2 with nexthop nexthopaddr on circuitname.
Default command level 1: Monitor level Usage guidelines Table 20 describes output fields and messages for the debugging isis miscellaneous-errors command. Table 201 Output from the debugging isis miscellaneous-errors command Field Description ISIS-Total Chars must be Even The total number of characters of the NET address must be an even number. ISIS-Check Net Len Min-8,Max-20 .
debugging isis { spf-event | spf-summary | spf-timer } Use debugging isis { spf-event | spf-summary | spf-timer } to enable debugging for IS-IS route calculation. Use undo debugging isis { spf-event | spf-summary | spf-timer } to disable debugging for IS-IS route calculation.
Field Description The previous SPF job is rescheduled. The job phase is displayed. SPF-PRCS: (MT topoId) SPF Job Re-Scheduled. Continue to run from phase jobphase topoId indicates the topology number. SPF node-related information. ISIS-procId-ISPF-NODE procId indicates the IS-IS process ID. IS-IS created the root node when the direct neighbor relationship was established.
Field Description ISPF-ADJ :(L sysLevel)(MT topoId) Adding P2P ADJ sourceId IS-IS is adding a point-to-point neighbor. • sysLevel—System level. • topoId—Topology number. IS-IS is creating a P2P link. ISPF-LINK :(L sysLevel)(MT topoId) Create(New) LINK sourceId --> destId OldCost: oldCost NewCost: newCost [AttAdjs: attAdjNum] [Ingore2way] [Tree] [Back] [Incr] [Decr] [Del] [Usage] [Nhop] [Involved] [NewPath] • • • • • • • sysLevel—System level. topoId—Topology number. sourceId—Source system ID.
Field Description Links changed. ISPF-EVE:Changed Link... sourceId --> destId OldCost: oldCost NewCost: newCost [AttAdjs: attAdjNum] [Ingore2way] [Tree] [Back] [Incr] [Decr] [Del] [Usage] [Nhop] [Involved] [NewPath] CHG: Node's usage/nexthop will be changed.Dist: distanceValue Nexthops: nexthopNum Nbrs: nbrNum Parents: parentNum [RmtNbr] [Tree] [Tent] [Direct ] [Overload] [Del] [Isolated] CHG: Ignore2way Link of the ROOT node is considered.
Field Description SPF-PRC:(L sysLevel)(MT topoId) Received System Change Event for msgString, Change = chgEvent SPF-PRC:Inform L sysLevel Change to Area and Route, Total Change Node:totalNum SpfNode change was sent to PRC for processing. • topoId—Topology number. • msgString—Node change event type. Inform system ID changes to the area address and route update module. • sysLevel—System level. • totalNum—Total node changes. Area address-related information and ATT-related information.
Examples # Enable route calculation debugging on Router A. The output in this example was created when the following conditions exist: • Router A and Router B are interconnected. • IS-IS is enabled on Router A and Router B. debugging isis spf-event // SPF calculation started, with a system level of L12 and SPF running level of 3. ISIS-1-SPF-TRIG: Starting SPF, Scheduled Event : IS_SPFTRIG_NEWLSP.
L2TP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging l2tp Use debugging l2tp to enable debugging for L2TP. Use undo debugging l2tp to disable debugging for L2TP. Syntax debugging l2tp { all | control | dump | error | event | hidden | payload | time-stamp } undo debugging l2tp { all | control | dump | error | event | hidden | payload | time-stamp } Default Debugging for L2TP is disabled.
Field Description AVP Vendor name AVP that indicates the vendor name of the sending device. AVP Framing capability AVP that indicates the types of frames received or requested by the sending device. AVP Assigned Tunnel ID AVP that indicates the assigned tunnel ID. AVP Receive window size AVP that indicates the receive window size of the sending device. AVP Challenge AVP that indicates that the sending devices wants to perform CHAP authentication to the tunnel peer.
Field Description Tunnel 1 Create 60 seconds Hello timer Tunnel 1 created a 60-second Hello timer. O Tunnel 1 Send SCCRQ Tunnel 1 sent the start control connection request message SCCRQ. Tunnel 1 recv ctrl message Resume Hello timer Tunnel 1 resumed the hello timer when receiving the control message. Proc Peer control type=type, len = length L2TP processed the control packet from the peer, with the packet type type and length length.
Examples # Enable debugging for L2TP control packets. Output similar to the following example is generated when the following conditions exist: • Two devices act as LAC and LNS. • L2TP is enabled on the two devices. • Tunnel authentication is configured on the two devices. debugging l2tp control *0.1798797 lac L2TP/7/L2TDBG: L2TP::Put AVP Message Type: START_CONTROL_CONNECTION_REQUEST // The connection request type of the control packet is START_CONTROL_CONNECTION_REQUEST. *0.
*0.1798829 lac L2TP/7/L2TDBG: L2TP::Parse AVP Challenge response: 9A D4 4B 91 6B 99 B9 A6 5A 2E 4A 4B 87 20 50 C8 // L2TP parsed the CHAP authentication challenge code as 9A D4 4B 91 6B 99 B9 A6 5A 2E 4A 4B 87 20 50 C8. *0.1798829 lac L2TP/7/L2TDBG: L2TP::Put AVP Message Type: START_CONTROL_CONNECTION_CONNECTED // The connection response type of the control packet is START_CONTROL_CONNECTION_ CONNECTED. *0.
*0.1798875 lac L2TP/7/L2TDBG: L2TP::Put AVP Proxy private group number : 0 *0.1798875 lac L2TP/7/L2TDBG: L2TP::Put AVP Rx connect speed: 0 // L2TP configured AVP identifications. *0.1798875 lac L2TP/7/L2TDBG: L2TP:: O Call 8680 send ICCN to Remote Call 27710 *0.1798875 lac L2TP/7/L2TDBG: L2TP::Tunnel 1 recv ctrl message Resume Hello timer *0.1798875 lac L2TP/7/L2TDBG: L2TP::Proc Peer control type=16, len = 36 # Enable debugging for L2TP PPP packets.
// The LNS address in Radius is 100.1.1.2. *0.3139156 lac L2TP/7/L2TDBG: L2TP::VPDN Group Number in Radius = 1 // The VPDN group number in Radius is 1. *0.3139156 lac L2TP/7/L2TDBG: L2TP::LNS Address = 100.1.1.2 // The LNS address is 100.1.1.2. *0.3139156 lac L2TP/7/L2TDBG: L2TP::Add New Call 27585 to Tunnel 1 call list(total 1) // L2TP added new call 27585 to the call list of Tunnel 1. *0.3139156 lac L2TP/7/L2TDBG: L2TP::Get udp port successfully : port 1701 // L2TP got UDP port 1701 successfully. *0.
• Tunnel authentication is not enabled on the two devices. debugging l2tp payload *0.1258360 lac L2TP/7/L2TDBG: L2TP::Tunnel 1 send control (SendUp & RcvLow):Ns(5) Nr(3) // Tunnel 1 sent a control packet. *0.1258360 lac L2TP/7/L2TDBG: L2TP::Tunnel 1 first ctrl in send window, start ack timer // The output above shows the first control packet of Tunnel 1 in the send window. L2TP started the ACK timer. *0.1258375 lac L2TP/7/L2TDBG: L2TP::Recv data Len = 12 *0.
L2VPN access to L3VPN or IP backbone debugging commands debugging ve-group Use debugging ve-group to enable debugging for VE groups. Use undo debugging ve-group to disable debugging for VE groups. Syntax debugging ve-group [ ve-group-id ] { all | error | event | packet } undo debugging ve-group [ ve-group-id ] { all | error | event | packet } Default All types of debugging for VE groups are disabled.
# Enable VE group event debugging. When a VE interface is added to a VE group, output similar to the following example is generated: debugging ve-group event *Apr 1 17:38:13:437 2010 Sysname VEG/7/Event: An interface was added to the VE group to access L3VPN or IP network. *Apr 1 17:38:13:437 2010 Sysname VEG/7/Event: Notified other boards that the interface was added to an VE group.
LAPB and X.25 debugging commands The output description tables in this document only contain fields and messages that require an explanation. LAPB debugging commands debugging lapb Use debugging lapb to enable LAPB debugging. Use undo debugging lapb to disable LAPB debugging.
Table 208 Output from the debugging lapb error command Field Description Fail to Malloc memory for build run Failed to allocate memory for buildrun. Fail to make memory continuous Failed to allocate continuous memory space for packets. Fail to prepend memory Failed to allocate continuous memory for packet headers. The upper protocol in MBUF is error Upper layer protocol type error in packets. Frame protocol error Upper layer protocol type error in information frames.
Field Description CMD/RSP Command frame/response frame. MOD modulo Modulo. encapsulation-type ENCAP • SINGLE—Single protocol. • MULTI—Multiple protocols. IFRAME Frame type. NS Sending sequence number. NR Receiving sequence number. P Polling bit. LEN Frame length. Encapsulation type: Table 4 describes the output fields and messages for the debugging lapb us-frame command.
Reply from 22.2.2.43: bytes=56 Sequence=1 ttl=255 time=27 ms --- 22.2.2.43 ping statistics --1 packet(s) transmitted 1 packet(s) received 0.00% packet loss round-trip min/avg/max = 27/27/27 ms // The state value of the data link layer protocol is 3 (data transmission state). A single-protocol-encapsulated information frame was received on interface Serial 2/0. X.25 debugging commands debugging pad Use debugging pad to enable a type of PAD debugging.
Table 213 Output from the debugging pad event command Field Description PAD: start clear procedure The clearing procedures started. PAD: Fragment and ReEnqueue the MBUF X.25 fragments and enqueues the MBUF. PAD: Parameter is negotiatory Parameter negotiation is being performed. PAD: Parameter negotiatory end Parameter negotiation is completed. PADX Closed by Line PAD closes the PADX link. X is the PAD ID. Table 7 describes the output fields and messages for the debugging pad packet command.
# domain default enable system # local-user pad2 password simple 2 service-type pad level 3 # interface Serial2/0 link-protocol x25 x25 x121-address 2 # user-interface vty 0 4 authentication-mode scheme user privilege level 3 # return debugging pad *0.685313091 Sysname X25/7/debug2: PAD0: Receive a control packet *0.685313092 Sysname X25/7/debug2:--Packet is Read PAD message // Router A received from Router B a PAD control packet asking for the X.3 parameters of Router A. *0.
PAD0: Receive a user data packet,Length:4 // Router A received user data packets. The packets contains the banner information displayed above. Login authentication Username: // After the X.3 parameter negotiation completed, the device prompts you for a username and password. After passing the authentication, you can log in to Router B successfully. debugging x25 Use debugging x25 to enable X.25 debugging. Use undo debugging x25 to disable X.25 debugging.
Field Description S2/0 X.25 LCI 1024: Called address != local address The called number of the VC with LCI 1024 is not a local address. DXE can not accept call( incorrect channel ) DXE cannot accept a call because the call uses an incorrect channel. CUG number error, forbid call in CUG number is incorrect and incoming calls are denied. CUG number error, forbid call out CUG number is incorrect and outgoing calls are denied.
Field Description Stop call timer The call timer Tx1 was stopped. Start reset timer The reset timer Tx2 was triggered. Stop reset timer The reset timer Tx2 was stopped. Start clear timer The clear timer Tx3 was triggered. Stop clear timer The clear timer Tx3 was stopped. Start idle timer The idle timer was triggered. Stop idle timer The idle timer was stopped. Start dellcd timer The DelLCD timer was triggered. Stop dellcd timer The DelLCD timer was stopped.
# interface Serial2/0 link-protocol x25 dce x25 x121-address 1 x25 map ip 3.3.3.2 x121-address 2 ip address 3.3.3.1 255.255.255.0 # return • The configuration on Router B is as follows: display current-configuration interface Serial 2/0 # interface Serial2/0 link-protocol x25 x25 x121-address 2 x25 map ip 3.3.3.1 x121-address 1 ip address 3.3.3.2 255.255.255.0 # return debugging x25 packet *0.683315037 Sysname X25/7/debug2: Serial2/0: X.
1 packet(s) transmitted 1 packet(s) received 0.00% packet loss round-trip min/avg/max = 6/6/6 ms // Router A received the ping response from Router B. debugging x25 x2t Use debugging x25 x2t to enable X2T debugging. Use undo debugging x25 x2t to disable X2T debugging. Syntax debugging x25 x2t { all | event | packet } undo debugging x25 x2t { all | event | packet } Default All types of X2T debugging are disabled.
Field Description X2T: Get an error while creating a tcp socket! X25 failed to create a socket. X2T: Get an error when accepting a tcp connection Error occurred when X25 was accepting a socket. X2T: Fail to receive when reading true data X25 failed to read data. X2T: Get an error when sending data to tcp X25 failed to send data. X2T: Receive invalid packet header Packet header is invalid.
# interface Ethernet1/0 ip address 1.1.1.2 255.255.255.0 # interface Serial2/0 link-protocol x25 dce x25 x121-address 1 # x25 switch svc 2 interface Serial2/0 translate ip 1.1.1.2 port 102 x25 2 translate x25 1 ip 1.1.1.1 port 102 # Configuration on Router B: # x25 switching # interface Ethernet1/0 ip address 11.1.1.2 255.255.255.0 # interface Serial2/0 link-protocol x25 x25 x121-address 2 # x25 switch svc 1 interface Serial2/0 translate ip 11.1.1.2 port 102 x25 1 translate x25 2 ip 11.1.1.
// Router B tried to establish a socket connection to PC 2 to forward the packet to PC 2. debugging x25 xot Use debugging x25 xot to enable XOT debugging. Use undo debugging x25 xot to disable XOT debugging. Syntax debugging x25 xot { all | event | packet } undo debugging x25 xot { all | event | packet } Default All types of XOT debugging are disabled. Views User view Default command level 1: Monitor level Parameters all: All types of XOT (X.25 over TCP) debugging. event: Debugging for XOT events.
Field Description XOT: Lcd SndQue is full The output queue on an XOT VC is full. XOT: Received Pvc_Setup packet's PTI incorrect The protocol type in the received PVC SETUP packet is invalid. XOT: Received Pvc_Setup packet's version incorrect The version in the received PVC SETUP packet is invalid. XOT: Can't match pvc entry No matched PVC entry was found. XOT: Input packet is too short The size of the input packet is less than the allowed minimum X.25 packet size. XOT: X.
Field Description STAT state XOT PVC state. Init Interface: interface-name LCD: lcd-num Interface and VC number through which the XOT PVC connection was initiated. Resp Interface: interface-name LCD: lcd-num Destination interface and VC number of the XOT PVC connection. Win window-size WOut window-size Sizes of the input window and the out-window on the interface that initiated the XOT PVC connection.
x25 switching # interface Ethernet1/0 ip address 2.2.2.2 255.255.255.0 # interface Serial2/0 link-protocol x25 dce # x25 switch svc 2 interface Serial2/0 x25 switch svc 1 xot 2.2.2.1 # Configuration on Router D: display current-configuration interface serial 2/0 # interface Serial2/0 link-protocol x25 x25 x121-address 2 x25 map ip 1.1.1.1 x121-address 1 ip address 1.1.1.2 255.255.255.0 # # Enable XOT packet and event debugging on Router B. debugging x25 xot event *0.
LLDP debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging dcbx Use debugging dcbx to enable DCBX debugging. Use undo debugging dcbx to disable DCBX debugging. Syntax debugging dcbx { all | error | event } [ interface interface-type interface-number ] undo debugging dcbx { all | error | event } [ interface interface-type interface-number ] Default DCBX debugging is disabled.
• Field • Description • Failed to update by local(sym) • LLDP failed to update the local end by local data (symmetrical state machine). • Failed to update local peer by remote TLV(sym) • LLDP failed to update the local end with the remote TLV (symmetrical state machine). • Failed to update local peer by remote data(Asy) • LLDP failed to update the local end by remote data (asymmetrical state machine). • The slot is not up • The card in the target slot is not up.
Table 223 Output from the debugging dcbx event command • Field • Description • Not to update by local(sym) • The local operating parameters were not updated (symmetrical state machine). • Not to set changed flag(sym) • The change flag was not set (symmetrical state machine). • Not to set driver by remote TLV(sym) • The configuration parameters were updated by the remote TLV, but the driver was not set (symmetrical state machine).
*Mar 23 14:38:34:282 2010 DeviceA DCBX/7/EVENT: -Slot=1; DCBX Adapter PFCADP Interface Ethernet1/1(If-Index 9437192):Received the interface deleting event. *Mar 23 14:38:34:282 2010 DeviceA DCBX/7/EVENT: -Slot=1; DCBX Adapter PFCADP Interface Ethernet1/1(If-Index 9437192):The DCBX entity has been deleted. // The PFC module received an interface delete event, and it deleted the DCBX entity. debugging lldp Use debugging lldp to enable a type of LLDP debugging.
• Field • Description • Get port information error • LLDP failed to get port information. • Port LLDP is disabled • LLDP is disabled on the port. • Port admin status do not support to receive message • The port is administratively disabled to receive packets. • The message length is error • The message length was invalid. • No end TLV • There was no End of LLDPDU TLV. • End TLV length error • The length of the End of LLDPDU TLV was invalid.
• Field • Description • Receive the MED capabilities TLV already • A packet carrying the LLDP-MED Capabilities TLV was received. • Receive the this type network policy TLV already • A packet carrying the type of Network Policy TLV was received. • Receive the MED power MDI TLV already • A packet carrying the MED power MDI TLV was received. • Receive this type location ID TLV already • A packet carrying the type of Location Identification TLV was received.
• Field • Description • Failure to set the global variable trap_interval • LLDP failed to set the trap message transmission interval. • Failure to write the packet receive event • LLDP failed to write the packet receive event. • Failure to synchronize the global config • LLDP failed to synchronize the global configuration. • • Failure to malloc the port portNum (IfIndex IfIndex) 's memory LLDP failed to allocate memory for port information. • portNum—Port number. • Ifindex—Port index.
Table 225 Output from the debugging lldp fsm command • • Field Receive state machine change from state1 state to state2 state • • • • • • • Description • The receive state machine changed from state 1 to state 2. State 1 and state 2 can be: LLDP_RX_WAIT_PORT—The port is not enabled. LLDP_RX_DEL_AGEDINFO—An aged neighbor information is removed. LLDP_RX_INIT—The port is initialized for receiving packets. LLDP_RX_WAIT_FRAME—The port is waiting for receiving packets.
Sys desc: H3C Comwar... Sys cap supported: 0x0016 enabled: 0x0006 Mana addr length: 16, subtype: 1, addr: 192.168.111.
Max frame size: 1552 Port VLAN ID: 1 Proto VLAN: flag: 0x02, ID: 1 VLAN name: ID: 1, length: 9, name: VLAN 0001 // The output shows detailed information about the packets received by LLDP and the packets transmitted by LLDP.
Load balancing debugging commands The output description tables in this document only contain fields and messages that require an explanation. debugging load-balance Use debugging load-balance to enable LB debugging. Use undo debugging load-balance to disable LB debugging. Syntax debugging load-balance { error | event | packet [ acl acl-number [ session ] ] } undo debugging load-balance { error | event | packet } Default LB debugging is disabled.
Field Description Forwarding modes of LB outbound packets: Forward mode • NAT. • Direct Routing. • Firewall Forwarding. This prompt is displayed only when the forwarding mode is Direct Routing or Firewall Forwarding. Prompt: Sending the packet to the real server rserveripaddr The destination address in these two modes cannot identify the device or server that processes the packets. Therefore, this prompt is needed to identify the device or server that processes the packets.
Login management debugging commands debugging http Use debugging http to enable HTTP debugging. Use undo debugging http to disable HTTP debugging. Syntax debugging http { all | message | parameter } undo debugging http { all | message | parameter } Default HTTP debugging is disabled. Views User view Default command level 1: Monitor level Parameters all: Specifies all types of HTTP debugging. message: Specifies HTTP message debugging. parameter: Specifies HTTP parameter debugging.
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Connection: Keep-Alive // The contents in the header were printed. *Jul 1 10:41:00:689 2007 Sysname HTTPD/7/PARAMETER: HTTPD_SEND_HTTP_MSG_BODY: Body is null. // An HTTP message was sent. The body of the message was null. *Jul 1 10:41:00:689 2007 Sysname HTTPD/7/PARAMETER: HTTP_UPDATE_HEADER_FIELD: Header field already exists. // The header has already existed, and the message header did not need to be updated.
debugging vty Use debugging vty to enable VTY debugging. Use undo debugging vty to disable VTY debugging. Syntax debugging vty { fsm | negotiate } undo debugging vty { fsm | negotiate } Views User view Parameters fsm: Telnet state machine debugging. negotiate: VTY option debugging. Examples # Enable VTY option debugging.
Loopback detection debugging commands The loopback detection module name is identified as "LPDT" in debugging messages. debugging loopback-detection Use debugging loopback-detection to enable loopback detection debugging. Use undo debugging loopback-detection to disable loopback detection debugging.
Table 227 Output from the debugging loopback-detection abnormal command Field Description Failed to set interface handle ( ulRet: 0x2 ) LPDT failed to set interface handle (error code: 0x2). Failed to get interface handle ( ulRet :0x3 ) LPDT failed to obtain interface handle (error code: 0x3). Received MBuf is null LPDT received a packet without data. Failed to get slot of interface LPDT failed to obtain the slot ID of the interface.
Field Description Received IPC ack "fail", destination node[1] was down and dropped the message[type:5] LPDT failed to receive an IPC ACK message. The destination node 1 was down and the message was dropped. The message type is 5.
Received loopback detection packet with invalid interface index // LPDT received a loopback detection packet with an invalid interface index.
