-
Cisco IOS Debug Command Reference
-
Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
debug aaa accounting through debug auto-config
-
debug backhaul-session-manager session through debug channel packets
-
debug clns esis events through debug dbconn tcp
-
debug decnet adj through debug events
-
debug fax dmsp through debug gvrp
-
debug h225 asn1 through debug ip ftp
-
debug ip http all through debug ip rsvp
-
debug ip rtp header-compression through debug ipv6 icmp
-
debug ipv6 inspect through debug local-ack state
-
debug management event through debug mpls ldp bindings
-
debug mpls ldp checkpoint through debug mwi relay events
-
debug ncia circuit through debug pxf tbridge
-
debug qllc error through debug snmp sync
-
debug sntp adjust through debug tag-switching xtagatm vc
-
debug tag-template event through debug voip application vxml
-
debug voip avlist through debug vpm signaling
-
debug vpm spi through voice call debug
-
X.25 Cause and Diagnostic Codes
-
ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug oer border traceroute reporting
debug oer master cost-minimization
debug oer master traceroute reporting
debug ppp multilink negotiation
debug ncia circuit
To display circuit-related information between the native client interface architecture (NCIA) server and client, use the debug ncia circuit command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ncia circuit [error | event | flow-control | state]
no debug ncia circuit [error | event | flow-control | state]
Syntax Description
Command Modes
Privileged EXEC (#)
Usage Guidelines
NCIA is an architecture developed by Cisco for accessing Systems Network Architecture (SNA) applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones.
You cannot enable debugging output for a particular client or particular circuit.
CautionDo not enable the debug ncia circuit command during normal operation because this command generates a substantial amount of output messages and could slow down the router.
Examples
The following is sample output from the debug ncia circuit error command. In this example, the possible errors are displayed. The first error message indicates that the router is out of memory. The second message indicates that the router has an invalid circuit control block. The third message indicates that the router is out of memory. The remaining messages identify errors related to the finite state machine.
Router# debug ncia circuit errorNCIA: ncia_circuit_create memory allocation failNCIA: ncia_send_ndlc: invalid circuit control blockNCIA: send_ndlc: fail to get buffer for ndlc primitive xxxNCIA: ncia circuit fsm: Invalid inputNCIA: ncia circuit fsm: Illegal stateNCIA: ncia circuit fsm: Illegal inputNCIA: ncia circuit fsm: Unexpected inputNCIA: ncia circuit fsm: Unknown error rtn codeThe following is sample output from the debug ncia circuit event command. In this example, a session startup sequence is displayed.
Router# debug ncia circuit eventNCIA(IN): Ver_Id: 0x81, MsgType: NDLC_START_DL, Len: 24, tmac: 4000.1060.1000,tsap: 4, csap 8, oid: 8A91E8, tid 0, lfs 16, ws 1NCIA: create circuit: saddr 4000.1060.1000, ssap 4, daddr 4000.3000.0003, dsap 8 sid:8B09A8NCIA: send NDLC_DL_STARTED to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_DL_STARTED, Len: 2,4 tmac: 4000.1060.1000,tsap: 4, csap 8, oid: 8A91E8, tid 8B09A8, lfs 16, ws 1NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8B09A8, FC 0x81NCIA: send NDLC_XID_FRAME to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8A91E8, FC 0xC1NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 18, sid: 8B09A8, FC 0xC1NCIA: send NDLC_CONTACT_STN to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_CONTACT_STN, Len: 12, sid: 8A91E8, FC 0xC1NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_STN_CONTACTED, Len: 12, sid: 8B09A8, FC 0xC1NCIA: send NDLC_INFO_FRAME to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_INFO_FRAME, Len: 30, sid: 8A91E8, FC 0xC1Table 245 describes the significant fields shown in the display.
In the following messages, an NDLC_START_DL messages is received from a client to start a data-link session:
NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_START_DL, Len: 24, tmac: 4000.1060.1000,tsap: 4, csap 8, oid: 8A91E8, tid 0, lfs 16, ws 1NCIA: create circuit: saddr 4000.1060.1000, ssap 4, daddr 4000.3000.0003, dsap 8 sid:8B09A8The next two messages indicate that an NDLC_DL_STARTED message is sent to a client. The server informs the client that a data-the link session is started.
NCIA: send NDLC_DL_STARTED to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_DL_STARTED, Len: 2,4 tmac: 4000.1060.1000,tsap: 4, csap 8, oid: 8A91E8, tid 8B09A8, lfs 16, ws 1In the following two messages, an NDLC_XID_FRAME message is received from a client, and the client starts an XID exchange:
NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8B09A8, FC 0x81NCIA: send NDLC_XID_FRAME to client 10.2.20.3 for ckt: 8B09A8In the following two messages, an NDLC_XID_FRAME message is sent from a client, and an DLC_XID_FRAME message is received from a client:
NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8A91E8, FC 0xC1NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 18, sid: 8B09A8, FC 0xC1The next two messages show that an NDLC_CONTACT_STN message is sent to a client:
NCIA: send NDLC_CONTACT_STN to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_CONTACT_STN, Len: 12, sid: 8A91E8, FC 0xC1In the following message, an NDLC_STN_CONTACTED message is received from a client. The client informs the server that the station has been contacted.
NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_STN_CONTACTED, Len: 12, sid: 8B09A8, FC 0xC1In the last two messages, an NDLC_INFO_FRAME is sent to a client, and the server sends data to the client:
NCIA: send NDLC_INFO_FRAME to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_INFO_FRAME, Len: 30, sid: 8A91E8, FC 0xC1The following is sample output from the debug ncia circuit flow-control command. In this example, the flow control in a session startup sequence is displayed:
Router# debug ncia circuit flow-controlNCIA: no flow control in NDLC_DL_STARTED frameNCIA: receive Increment Window Op for circuit 8ADE00NCIA: ncia_flow_control_in FC 0x81, IW 1 GP 2 CW 2, Client IW 1 GP 0 CW 1NCIA: grant client more packet by sending Repeat Window OpNCIA: ncia_flow_control_out FC: 0xC1, IW 1 GP 2 CW 2, Client IW 1 GP 2 CW 2NCIA: receive FCA for circuit 8ADE00NCIA: receive Increment Window Op for circuit 8ADE00NCIA: ncia_flow_control_in FC 0xC1, IW 1 GP 5 CW 3, Client IW 1 GP 2 CW 2NCIA: grant client more packet by sending Repeat Window OpNCIA: ncia_flow_control_out FC: 0xC1, IW 1 GP 5 CW 3, Client IW 1 GP 5 CW 3NCIA: receive FCA for circuit 8ADE00NCIA: receive Increment Window Op for circuit 8ADE00NCIA: ncia_flow_control_in FC 0xC1, IW 1 GP 9 CW 4, Client IW 1 GP 5 CW 3NCIA: grant client more packet by sending Repeat Window OpNCIA: ncia_flow_control_out FC: 0xC1, IW 1 GP 8 CW 4, Client IW 1 GP 9 CW 4NCIA: reduce ClientGrantPacket by 1 (Granted: 8)NCIA: receive FCA for circuit 8ADE00NCIA: receive Increment Window Op for circuit 8ADE00Table 246 describes the significant fields shown in the display.
Table 246 debug ncia circuit flow-control Field Descriptions
IW
Initial window size.
GP
Granted packet number.
CW
Current window size.
The following is sample output from the debug ncia circuit state command. In this example, a session startup sequence is displayed:
Router# debug ncia circuit stateNCIA: pre-server fsm: event CONN_OPENEDNCIA: pre-server fsm: event NDLC_PRIMITIVESNCIA: server event: WAN - STDL state: CLSOEDNCIA: ncia server fsm action 32NCIA: circuit state: CLOSED -> START_DL_RCVDNCIA: server event: DLU - TestStn.Rsp state: START_DL_RCVDNCIA: ncia server fsm action 17NCIA: circuit state: START_DL_RCVD -> DL_STARTED_SNDNCIA: pre-server fsm: event NDLC_PRIMITIVESNCIA: server event: WAN - XID state: DL_STARTED_SNDNCIA: ncia server fsm action 33NCIA: circuit state: DL_STARTED_SND -> DL_STARTED_SNDNCIA: server event: DLU - ReqOpnStn.Req state: DL_STARTED_SNDNCIA: ncia server fsm action 33NCIA: circuit state: DL_STARTED_SND -> OPENEDNCIA: server event: DLU - Id.Rsp state: OPENEDNCIA: ncia server fsm action 11NCIA: circuit state: OPENED -> OPENEDNCIA: pre-server fsm: event NDLC_PRIMITIVESNCIA: server event: WAN - XID state: OPENEDNCIA: ncia server fsm action 33NCIA: circuit state: OPENED -> OPENEDNCIA: server event: DLU - Connect.Req state: OPENEDNCIA: ncia server fsm action 6NCIA: circuit state: OPENED -> CONNECT_PENDINGNCIA: pre-server fsm: event NDLC_PRIMITIVESNCIA: server event: WAN - CONR state: CONNECT_PENDINGNCIA: ncia server fsm action 33 --> CLS_CONNECT_CNF sets NciaClsBusyNCIA: circuit state: CONNECT_PENDING -> CONNECTEDNCIA: server event: DLU - Flow.Req (START) state: CONNECTEDNCIA: ncia server fsm action 25 --> unset NciaClsBusyNCIA: circuit state: CONNECTED -> CONNECTEDNCIA: server event: DLU - Data.Rsp state: CONNECTEDNCIA: ncia server fsm action 8NCIA: circuit state: CONNECTED -> CONNECTEDTable 247 describes the significant fields shown in the display.
Related Commands
debug ncia client
To display debug information for all native client interface architecture (NCIA) client processing that occurs in the router, use the debug ncia client command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ncia client [ip-address | error [ip-address] | event [ip-address] | message [ip-address]]
no debug ncia client [ip-address | error [ip-address] | event [ip-address] | message [ip-address]]
Syntax Description
Command Modes
Privileged EXEC (#)
Usage Guidelines
NCIA is an architecture developed by Cisco for accessing Systems Network Architecture (SNA) applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones.
Use the debug ncia client error command to see only certain error conditions that occur.
Use the debug ncia client event command to determine the sequences of activities that occur while an NCIA client is in different processing states.
Use the debug ncia client message command to see only the first 32 bytes of data in a TCP packet sent to or received from an NCIA client.
The debug ncia client command can be used in conjunction with the debug ncia server and debug ncia circuit commands to get a complete picture of NCIA activity.
Examples
The following is sample output from the debug ncia client command. Following the example is a description of each sample output message.
Router# debug ncia clientNCIA: Passive open 10.2.20.123(1088) -> 1973NCIA: index for client hash queue is 27NCIA: number of element in client hash queue 27 is 1NCIA: event PASSIVE_OPEN, state NCIA_CLOSED for client 10.2.20.123NCIA: Rcvd msg type NDLC_CAP_XCHG in tcp packet for client 10.2.20.123NCIA: First 17 byte of data rcvd: 811200110000000000000400050104080CNCIA: Sent msg type NDLC_CAP_XCHG in tcp packet to client 10.2.20.123NCIA: First 17 byte of data sent: 811200111000000010000400050104080CNCIA: event CAP_CMD_RCVD, state NCIA_CAP_WAIT, for client 10.2.20.123, cap xchg cmd sentNCIA: Rcvd msg type NDLC_CAP_XCHG in tcp packet for client 10.2.20.123NCIA: First 17 byte of data rcvd: 811200111000000010000000050104080CNCIA: event CAP_RSP_RCVD, state NCIA_CAP_NEG for client 10.2.20.123NCIA: Rcvd msg type NDLC_PEER_TEST_REQ in tcp packet for client 10.2.20.123NCIA: First 4 byte of data rcvd: 811D0004NCIA: event KEEPALIVE_RCVD, state NCIA_OPENED for client 10.2.20.123NCIA: Sent msg type NDLC_PEER_TEST_RSP in tcp packet to client 10.2.20.123NCIA: First 4 byte of data sent: 811E0004IANCIA: event TIME_OUT, state NCIA_OPENED, for client 10.2.20.123, keepalive_count = 0NCIA: Sent msg type NDLC_PEER_TEST_REQ, in tcp packet to client 10.2.20.123NCIA: First 4 byte of data sent: 811D0004NCIA: Rcvd msg type NDLC_PEER_TEST_RSP in tcp packet for client 10.2.20.123NCIA: First 4 byte of data rcvd: 811E0004NCIA: event KEEPALIVE_RSP_RCVD, state NCIA_OPENED for client 10.2.20.123NCIA: Error, event PASIVE_OPEN, state NCIA_OPENED, for client 10.2.20.123, should not have occurred.NCIA: Error, active_open for pre_client_fsm while client 10.2.20.123 is active or not configured, registered.Messages in lines 1 through 12 show the events that occur when a client connects to the router (the NCIA server). These messages show a passive_open process.
Messages in lines 13 to 17 show the events that occur when a TIME_OUT event is detected by a client PC workstation. The workstation sends an NDLC_PEER_TEST_REQ message to the NCIA server, and the router responds with an NDLC_PEER_TEST_RSP message.
Messages in lines 18 to 23 show the events that occur when a TIME_OUT event is detected by the router (the NCIA server). The router sends an NDLC_PEER_TEST_REQ message to the client PC workstation, and the PC responds with an NDLC_PEER_TEST_RSP message.
When you use the debug ncia client message command, the messages shown on lines 6, 8, 11, 14, 17, 20, and 22 are output in addition to other messages not shown in this example.
When you use the debug ncia client error command, the messages shown on lines 24 and 25 are output in addition to other messages not shown in this example.
Related Commands
debug ncia server
To display debug information for the native client interface architecture (NCIA) server and its upstream software modules, use the debug ncia server command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ncia server
no debug ncia server
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Usage Guidelines
NCIA is an architecture developed by Cisco for accessing Systems Network Architecture (SNA) applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones.
The debug ncia server command displays all Cisco Link Services (CLS) messages between the NCIA server and its upstream modules, such as data-link switching (DLSw) and downstream physical units (DSPUs). Use this command when a problem exists between the NCIA server and other software modules within the router.
You cannot enable debugging output for a particular client or particular circuit.
Examples
The following is sample output from the debug ncia server command. In this example, a session startup sequence is displayed. Following the example is a description of each group of sample output messages.
Router# debug ncia serverNCIA: send CLS_TEST_STN_IND to DLUNCIA: Receive TestStn.RspNCIA: send CLS_ID_STN_IND to DLUNCIA: Receive ReqOpnStn.ReqNCIA: send CLS_REQ_OPNSTN_CNF to DLUNCIA: Receive Id.RspNCIA: send CLS_ID_IND to DLUNCIA: Receive Connect.ReqNCIA: send CLS_CONNECT_CNF to DLUNCIA: Receive Flow.ReqNCIA: Receive Data.ReqNCIA: send CLS_DATA_IND to DLUNCIA: send CLS_DISC_IND to DLUNCIA: Receive Disconnect.RspIn the following messages, the client is sending a test message to the host and the test message is received by the host:
NCIA: send CLS_TEST_STN_IND to DLUNCIA: Receive TestStn.RspIn the next message, the server is sending an exchange identification (XID) message to the host:
NCIA: send CLS_ID_STN_IND to DLUIn the next two messages, the host opens the station and the server responds:
NCIA: Receive ReqOpnStn.ReqNCIA: send CLS_REQ_OPNSTN_CNF to DLUIn the following two messages, the client is performing an XID exchange with the host:
NCIA: Receive Id.RspNCIA: send CLS_ID_IND to DLUIn the next group of messages, the host attempts to establish a session with the client:
NCIA: Receive Connect.ReqNCIA: send CLS_CONNECT_CNF to DLUNCIA: Receive Flow.ReqIn the next two messages, the host sends data to the client:
NCIA: Receive Data.ReqNCIA: send CLS_DATA_IND to DLUIn the last two messages, the client closes the session:
NCIA: send CLS_DISC_IND to DLUNCIA: Receive Disconnect.RspRelated Commands
debug netbios error
To display information about Network Basic Input/Output System (NetBIOS) protocol errors, use the debug netbios error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug netbios error
no debug netbios error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Usage Guidelines
For complete information on the NetBIOS process, use the debug netbios packet command along with the debug netbios error command.
Examples
The following is sample output from the debug netbios error command. This example shows that an illegal packet has been received on the asynchronous interface.
Router# debug netbios errorAsync1 nbf Bad packetRelated Commands
debug netbios-name-cache
Displays name caching activities on a router.
debug netbios packet
Displays general information about NetBIOS packets.
debug netbios packet
To display general information about Network Basic Input/Output System (NetBIOS) packets, use the debug netbios packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug netbios packet
no debug netbios packet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Usage Guidelines
For complete information on the NetBIOS process, use the debug netbios error command along with the debug netbios packet command.
Examples
The following is sample output from the debug netbios packet and debug netbios error commands. This example shows the Logical Link Control (LLC) header for an asynchronous interface followed by the NetBIOS information. For additional information on the NetBIOS fields, refer to IBM LAN Technical Reference IEEE 802.2.
Router# debug netbios packetAsync1 (i) U-format UI C_R=0x0(i) NETBIOS_ADD_NAME_QUERYResp_correlator= 0x6F 0x0Src name=CS-NT-1Async1 (i) U-format UI C_R=0x0(i) NETBIOS_ADD_GROUP_QUERYResp_correlator= 0x6F 0x0Src name=COMMSERVER-WGAsync1 (i) U-format UI C_R=0x0(i) NETBIOS_ADD_NAME_QUERYResp_correlator= 0x6F 0x0Src name=CS-NT-1Ethernet0 (i) U-format UI C_R=0x0(i) NETBIOS_DATAGRAMLength= 0x2C 0x0Dest name=COMMSERVER-WGSrc name=CS-NT-3Related Commands
debug netbios error
Displays information about NetBIOS protocol errors.
debug netbios-name-cache
Displays name caching activities on a router.
debug netbios-name-cache
To display name caching activities on a router, use the debug netbios-name-cache command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug netbios-name-cache
no debug netbios-name-cache
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Usage Guidelines
Examine the display to diagnose problems in Network Basic Input/Output System (NetBIOS) name caching.
Examples
The following is sample output from the debug netbios-name-cache command:
Router# debug netbios-name-cacheNETBIOS: L checking name ORINDA, vrn=0NetBIOS name cache table corrupted at offset 13NetBIOS name cache table corrupted at later offset, at location 13NETBIOS: U chk name=ORINDA, addr=1000.4444.5555, idb=TR1, vrn=0, type=1NETBIOS: U upd name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1NETBIOS: U add name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1NETBIOS: U no memory to add cache entry. name=ORINDA,addr=1000.4444.5555NETBIOS: Invalid structure detected in netbios_name_cache_agerNETBIOS: flushed name=ORINDA, addr=1000.4444.5555NETBIOS: expired name=ORINDA, addr=1000.4444.5555NETBIOS: removing entry. name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0NETBIOS: Tossing ADD_NAME/STATUS/NAME/ADD_GROUP frameNETBIOS: Lookup Failed -- not in cacheNETBIOS: Lookup Worked, but split horizon failedNETBIOS: Could not find RIF entryNETBIOS: Cannot duplicate packet in netbios_name_cache_proxy
Note
Table 248 describes the significant fields shown in the display.
With the first line of output, the router declares that it has examined the NetBIOS name cache table for the machine name ORINDA and that the packet that prompted the lookup came from virtual ring 0. In this case, this packet comes from a real interface—virtual ring number 0 is not valid.
NETBIOS: L checking name ORINDA, vrn=0The following two lines indicate that an invalid NetBIOS entry exists and that the corrupted memory was detected. The invalid memory will be removed from the table; no action is needed.
NetBIOS name cache table corrupted at offset 13NetBIOS name cache table corrupted at later offset, at location 13The following line indicates that the router attempted to check the NetBIOS cache table for the name ORINDA with MAC address 1000.4444.5555. This name was obtained from Token Ring interface 1. The type field indicates that the name was learned from traffic.
NETBIOS: U chk name=ORINDA, addr=1000.4444.5555, idb=TR1, vrn=0, type=1The following line indicates that the NetBIOS name ORINDA is in the name cache table and was updated to the current value:
NETBIOS: U upd name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1The following line indicates that the NetBIOS name ORINDA is not in the table and must be added to the table:
NETBIOS: U add name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1The following line indicates that there was insufficient cache buffer space when the router tried to add this name:
NETBIOS: U no memory to add cache entry. name=ORINDA,addr=1000.4444.5555The following line indicates that the NetBIOS ager detects an invalid memory in the cache. The router clears the entry; no action is needed.
NETBIOS: Invalid structure detected in netbios_name_cache_agerThe following line indicates that the entry for ORINDA was flushed from the cache table:
NETBIOS: flushed name=ORINDA, addr=1000.4444.5555The following line indicates that the entry for ORINDA timed out and was flushed from the cache table:
NETBIOS: expired name=ORINDA, addr=1000.4444.5555The following line indicates that the router removed the ORINDA entry from its cache table:
NETBIOS: removing entry. name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0The following line indicates that the router discarded a NetBIOS packet of type ADD_NAME, STATUS, NAME_QUERY, or ADD_GROUP. These packets are discarded when multiple copies of one of these packet types are detected during a certain period of time.
NETBIOS: Tossing ADD_NAME/STATUS/NAME/ADD_GROUP frameThe following line indicates that the system could not find a NetBIOS name in the cache:
NETBIOS: Lookup Failed -- not in cacheThe following line indicates that the system found the destination NetBIOS name in the cache, but located on the same ring from which the packet came. The router will drop this packet because the packet should not leave this ring.
NETBIOS: Lookup Worked, but split horizon failedThe following line indicates that the system found the NetBIOS name in the cache, but the router could not find the corresponding RIF. The packet will be sent as a broadcast frame.
NETBIOS: Could not find RIF entryThe following line indicates that no buffer was available to create a NetBIOS name cache proxy. A proxy will not be created for the packet, which will be forwarded as a broadcast frame.
NETBIOS: Cannot duplicate packet in netbios_name_cache_proxyRelated Commands
debug netbios error
Displays information about NetBIOS protocol errors.
debug netbios packet
Displays general information about NetBIOS packets.
debug netconf
To enable debugging of network configuration protocol (NETCONF) sessions, use the debug netconf command in privileged EXEC mode. To turn off NETCONF debugging, use the no form of this command.
debug netconf {all | error}
no debug netconf {all | error}
Syntax Description
all
Enables debugging of NETCONF sessions, including NETCONF errors.
error
Enables debugging of NETCONF errors.
Command Default
NETCONF debugging is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug netconf command issues debug information only when an operational error has happened. In most situations, the NETCONF notifications sent between the NETCONF Network Manager and the client are sufficient to diagnose most NETCONF problems.
To view Extensible Markup Language (XML) parsing errors when using NETCONF over SSHv2, you must also configure the debug cns xml all command.
Examples
The following example shows how to enable debugging of all NETCONF sessions:
Router# debug netconf00:14:03: NETCONF-ERROR: could not find user1 00:14:03: NETCONF-ERROR: could not find tftp://samplelocation/samplefile 00:14:03: NETCONF: locking 1 by session 646B7038 00:14:03: NETCONF: locking 2 by session 646B7038 00:14:03: NETCONF: locking 1 by session 646B7038 00:14:03: NETCONF-ERROR: invalid session unlock attempt 00:14:03: NETCONF: locking 1 by session 646B7038 00:14:03: NETCONF-ERROR: lock already active 00:14:13: NETCONF-ERROR: lock time 1 expired closing session 646B7038Table 249 describes the significant fields shown in the display.
Related Commands
debug nextport vsmgr detail
To turn on debugging for NextPort voice services, use the debug nextport vsmgr detail command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug nextport vsmgr detail
no debug nextport vsmgr detail
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command debugs digital signal processor (DSP) message exchanges between applications and the DSP.
Examples
The following examples turn on debugging for NextPort voice services:
debug nextport vsmgr detail Command on the Originating Gateway
Router# debug nextport vsmgr detailNextPort Voice Service Manager:NP Voice Service Manager Detail debugging is on...May 7 21:09:49.135 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:09:49.195 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:09:49.291 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVEMay 7 21:09:51.191 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:09:51.331 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVEMay 7 21:09:51.803 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF ReceivedMay 7 21:09:51.803 UTC: request_id = 0x01, request_type = 0x0FMay 7 21:09:51.803 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 4 num_sig_packets 0 num_cn_packets 1 transmit_duration 8FC end_point_detection 0May 7 21:09:51.803 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 4 num_sig_packets 0 num_cn_packets 1 receive_duration 8FC voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0May 7 21:09:51.803 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 0 min_playout_delay 0 max_playout_delay 0 clock offset 0May 7 21:09:51.803 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0May 7 21:09:53.231 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF ReceivedMay 7 21:09:53.231 UTC: request_id = 0x01, request_type = 0x0FMay 7 21:09:53.231 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 1E num_sig_packets 0 num_cn_packets 1 transmit_duration E92 end_point_detection 0May 7 21:09:53.231 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 4 num_sig_packets 0 num_cn_packets 1 receive_duration E92 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0May 7 21:09:53.231 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 5A min_playout_delay 5A max_playout_delay 5A clock offset 19778906May 7 21:09:53.231 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0May 7 21:09:56.055 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF ReceivedMay 7 21:09:56.055 UTC: request_id = 0x01, request_type = 0x0FMay 7 21:09:56.055 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 23 num_sig_packets 0 num_cn_packets 2 transmit_duration 19A0 end_point_detection BB8May 7 21:09:56.055 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 8A num_sig_packets 0 num_cn_packets 1 receive_duration 19A0 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 1May 7 21:09:56.055 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 3C min_playout_delay 3C max_playout_delay 64 clock offset 197788E4May 7 21:09:56.055 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x1 endpt_det_error 0x0May 7 21:09:56.855 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:09:57.907 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVEMay 7 21:09:57.907 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 2 timestamp 68137565 fr-entered (20ms)May 7 21:09:57.907 UTC: chan_id [3/1:D] np_vsmgr_fax_relay_link_info_response:May 7 21:10:15.047 UTC: np_fax_relay_t30_decode : Tx DirectionMay 7 21:10:15.067 UTC: FARELAY_INIT_HS_MOD : 0xCMay 7 21:10:51.579 UTC: FAX_RELAY_DATA_PUMP_STATS(1/2) - valid:0x3FFC1F55 state_code:0x0 level:0x18 phase_jitter:0x5 freq_offset:0x0 eqm:0x7FFE jit_depth:0x230 jit_buf_ov:0x0 tx_paks:0x626 rx_pkts:0x5A inv_pkts:0x0 oos_pkts:0x0 hs_mod:0x8 init_hs_mod:0xC tx_pgs:0x1 rx_pgs:0x0 ecm:0x1 nsf_country:0x0 nsf_manuf_len:0x20 nsf_manuf:0031B8EE80C48511DD0D0000DDDD0000DDDD000000000000000022ED00B0A400 encap:0x1 pkt_loss_con:0x0May 7 21:10:52.463 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:10:52.463 UTC: vsm(1/2): np_vsmgr_voice_state_change - NULL DSP Interface Handledebug nextport vsmgr detail Command on the Terminating Gateway
Router# debug nextport vsmgr detailNextPort Voice Service Manager:NP Voice Service Manager Detail debugging is on..Router#May 7 21:09:51.179 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:09:51.263 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVEMay 7 21:09:51.303 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:09:51.443 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVEMay 7 21:09:51.467 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF ReceivedMay 7 21:09:51.467 UTC: request_id = 0x01, request_type = 0x0FMay 7 21:09:51.467 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 0 num_sig_packets 0 num_cn_packets 0 transmit_duration 0 end_point_detection 0May 7 21:09:51.467 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 0 num_sig_packets 0 num_cn_packets 0 receive_duration 0 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0May 7 21:09:51.467 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 0 min_playout_delay 0 max_playout_delay 0 clock offset 0May 7 21:09:51.467 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0May 7 21:09:53.787 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF ReceivedMay 7 21:09:53.787 UTC: request_id = 0x01, request_type = 0x0FMay 7 21:09:53.787 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 19 num_sig_packets 0 num_cn_packets 1 transmit_duration 910 end_point_detection 0May 7 21:09:53.787 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 1F num_sig_packets 0 num_cn_packets 2 receive_duration 910 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0May 7 21:09:53.787 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 5A min_playout_delay 5A max_playout_delay 5A clock offset 68877C4May 7 21:09:53.787 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0May 7 21:09:56.571 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF ReceivedMay 7 21:09:56.571 UTC: request_id = 0x01, request_type = 0x0FMay 7 21:09:56.571 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets A5 num_sig_packets 0 num_cn_packets 1 transmit_duration 13F6 end_point_detection 0May 7 21:09:56.571 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 30 num_sig_packets 0 num_cn_packets 2 receive_duration 13F6 voice_receive_duration 7D0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0May 7 21:09:56.571 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 64 min_playout_delay 5A max_playout_delay 64 clock offset 68877D4May 7 21:09:56.571 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0May 7 21:09:56.807 UTC: VOICE_DET_STATUS_CHANGE_NTF(1/2): detector mask: 1 timestamp 791687D5May 7 21:09:56.855 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:09:57.911 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVEMay 7 21:09:57.911 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 2 timestamp 65325022 fr-entered (20ms)May 7 21:09:57.911 UTC: chan_id [3/1:D (6)] np_vsmgr_fax_relay_link_info_response:May 7 21:10:15.043 UTC: np_fax_relay_t30_decode : Rx DirectionMay 7 21:10:15.107 UTC: FARELAY_INIT_HS_MOD : 0x8May 7 21:10:51.376 UTC: FAX_RELAY_DET_STATUS_CHANGE: slot: 1 port: 2 detector mask 0x2May 7 21:10:51.404 UTC: FAX_RELAY_DATA_PUMP_STATS(1/2) - valid:0x3FFC1F55 state_code:0x1 level:0x18 phase_jitter:0x0 freq_offset:0x0 eqm:0x7FFE jit_depth:0x39E jit_buf_ov:0x0 tx_paks:0x5A rx_pkts:0x626 inv_pkts:0x0 oos_pkts:0x0 hs_mod:0x8 init_hs_mod:0x8 tx_pgs:0x0 rx_pgs:0x1 ecm:0x1 nsf_country:0x0 nsf_manuf_len:0x20 nsf_manuf:0031B8EE80C48511DD0D0000DDDD0000DDDD000000000000000022ED00B0A400 encap:0x1 pkt_loss_con:0x0May 7 21:10:52.288 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 2 timestamp 65760060 fr-endMay 7 21:10:52.304 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:10:52.388 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVEMay 7 21:10:52.416 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF ReceivedMay 7 21:10:52.416 UTC: request_id = 0x05, request_type = 0x30May 7 21:10:52.416 UTC: VOICE_LEVELS_STATS(1/2): tx_power FF7E tx_mean FF7F rx_power FDBD rx_mean FB48 bnl FD81 erl FD acom 1EA tx_act 1 rx_act 0May 7 21:10:52.440 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLEMay 7 21:10:52.440 UTC: vsm(1/2): np_vsmgr_voice_state_change - NULL DSP Interface HandleRelated Commands
debug nhrp
To enable Next Hop Resolution Protocol (NHRP) debugging, use the debug nhrp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug nhrp {ipv4 | ipv6} [cache | extension | packet | rate]
no debug nhrp
Syntax Description
(
Command Default
NHRP debugging is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows NHRP debugging output for IPv6:
Router# debug nhrp ipv6Aug 9 13:13:41.486: NHRP: Attempting to send packet via DEST- 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32Aug 9 13:13:41.486: NHRP: Encapsulation succeeded.Aug 9 13:13:41.486: NHRP: Tunnel NBMA addr 11.11.11.99Aug 9 13:13:41.486: NHRP: Send Registration Request via Tunnel0 vrf 0, packet size: 105Aug 9 13:13:41.486: src: 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32,dst: 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32Aug 9 13:13:41.486: NHRP: 105 bytes out Tunnel0Aug 9 13:13:41.486: NHRP: Receive Registration Reply via Tunnel0 vrf 0, packet size: 125The following example shows NHRP debugging output for IPv4:
Router# debug nhrp ipv4Aug 9 13:13:41.486: NHRP: Attempting to send packet via DEST 10.1.1.99Aug 9 13:13:41.486: NHRP: Encapsulation succeeded. Tunnel IP addr 10.11.11.99Aug 9 13:13:41.486: NHRP: Send Registration Request via Tunnel0 vrf 0, packet size: 105Aug 9 13:13:41.486: src: 10.1.1.11, dst: 10.1.1.99Aug 9 13:13:41.486: NHRP: 105 bytes out Tunnel0Aug 9 13:13:41.486: NHRP: Receive Registration Reply via Tunnel0 vrf 0, packet size: 125Aug 9 13:13:41.486: NHRP: netid_in = 0, to_us = 1Related Commands
debug dmvpn
Displays DMVPN session debugging information.
debug nhrp error
Displays NHRP error level debugging information.
debug nhrp condition
To enable Next Hop Resolution Protocol (NHRP) conditional debugging, use the debug nhrp condition command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug nhrp condition [peer [nbma | tunnel | ip-address | ipv6-address]] | [interface tunnel number] | [vrf vrf-name]
no debug nhrp condition [peer {nbma | tunnel} ip-address | ipv6-address] | [interface tunnel number] | [vrf vrf-name]
Syntax Description
Command Default
Conditional NHRP debugging is not enabled.
Command Modes
Privileged EXEC (#)
Command History
12.4(9)T
This command was introduced.
12.4(20)T
The ipv6-address argument was added.
Examples
The following example shows how to enable conditional NHRP debugging for a specific tunnel:
Router# debug nhrp condition peer tunnel 192.0.2.1Related Commands
debug dmvpn
Displays DMVPN session debugging information.
debug nhrp error
Displays NHRP error level debugging information.
debug nhrp error
To display Next Hop Resolution Protocol (NHRP) error level debugging information, use the debug nhrp error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug nhrp {ipv4 | ipv6} error
no debug nhrp {ipv4 | ipv6} error
Syntax Description
Command Default
Error level NHRP debugging is not enabled.
Command Modes
Privileged EXEC (#)
Command History
12.4(9)T
This command was introduced.
12.4(20)T
The ipv4 and ipv6 keywords were added.
Examples
The following example shows how to enable error level debugging for IPv4 NHRP:
Router# debug nhrp ipv4 errorNHRP errors debugging is onRelated Commands
debug dmvpn
Displays DMVPN session debugging information.
debug nhrp condition
Enables NHRP conditional debugging.
debug nhrp extension
To display the extensions portion of a NHRP packet, use the debug nhrp extension privileged EXEC command. The no form of this command disables debugging output.
debug nhrp extension
no debug nhrp extension
Syntax Description
This command has no arguments or keywords.
Examples
The following is sample output from the debug nhrp extension command:
Router# debug nhrp extensionNHRP extension processing debugging is onRouter#Forward Transit NHS Record Extension(4):(C-1) code: no error(0)prefix: 0, mtu: 9180, hd_time: 7200addr_len: 20(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0client NBMA: 47.0091810000000002ba08e101.525354555354.01client protocol: 135.206.58.54Reverse Transit NHS Record Extension(5):Responder Address Extension(3):(C) code: no error(0)prefix: 0, mtu: 9180, hd_time: 7200addr_len: 20(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0client NBMA: 47.0091810000000002ba08e101.525354555355.01client protocol: 135.206.58.55Forward Transit NHS Record Extension(4):(C-1) code: no error(0)prefix: 0, mtu: 9180, hd_time: 7200addr_len: 20(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0client NBMA: 47.0091810000000002ba08e101.525354555354.01client protocol: 135.206.58.54Reverse Transit NHS Record Extension(5):Responder Address Extension(3):Forward Transit NHS Record Extension(4):Reverse Transit NHS Record Extension(5):debug nhrp options
To display information about NHRP option processing, use the debug nhrp options privileged EXEC command. The no form of this command disables debugging output.
debug nhrp options
no debug nhrp options
Syntax Description
This command has no arguments or keywords.
Usage Guidelines
Use this command to show you whether there are problems or error situations with NHRP option processing (for example, unknown options).
Examples
The following is sample output from the debug nhrp options command:
Router# debug nhrp optionsNHRP-OPT: MASK 4NHRP-OPT-MASK: FFFFFFFFNHRP-OPT: NETID 4NHRP-OPT: RESPONDER 4NHRP-OPT: RECORD 0NHRP-OPT: RRECORD 0Table 250 describes the significant fields shown in the display.
Related Commands
debug nhrp
Displays information about NHRP activity.
debug nhrp packet
Displays a dump of NHRP packets.
debug nhrp packet
To display a dump of NHRP packets, use the debug nhrp packet privileged EXEC command. The no form of this command disables debugging output.
debug nhrp packet
no debug nhrp packet
Syntax Description
This command has no arguments or keywords.
Examples
The following is sample output from the debug nhrp packet command:
Router# debug nhrp packetNHRP activity debugging is onRouter#NHRP: Send Purge Request via ATM3/0.1, packet size: 72src: 135.206.58.55, dst: 135.206.58.56(F) afn: NSAP(3), type: IP(800), hop: 255, ver: 1shtl: 20(NSAP), sstl: 0(NSAP)(M) flags: "reply required", reqid: 2src NBMA: 47.0091810000000002ba08e101.525354555355.01src protocol: 135.206.58.55, dst protocol: 135.206.58.56(C-1) code: no error(0)prefix: 0, mtu: 9180, hd_time: 0addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0client protocol: 135.206.58.130NHRP: Receive Purge Reply via ATM3/0.1, packet size: 72(F) afn: NSAP(3), type: IP(800), hop: 254, ver: 1shtl: 20(NSAP), sstl: 0(NSAP)(M) flags: "reply required", reqid: 2src NBMA: 47.0091810000000002ba08e101.525354555355.01src protocol: 135.206.58.55, dst protocol: 135.206.58.56(C-1) code: no error(0)prefix: 0, mtu: 9180, hd_time: 0addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0client protocol: 135.206.58.130debug nhrp rate
To display information about NHRP traffic rate limits, use the debug nhrp rate privileged EXEC command. The no form of this command disables debugging output.
debug nhrp rate
no debug nhrp rate
Syntax Description
This command has no arguments or keywords.
Usage Guidelines
Use this command to verify that the traffic is consistent with the setting of the NHRP commands (such as ip nhrp use and ip max-send commands).
Examples
The following is sample output from the debug nhrp rate command:
Router# debug nhrp rateNHRP-RATE: Sending initial requestNHRP-RATE: Retransmitting request (retrans ivl 2)NHRP-RATE: Retransmitting request (retrans ivl 4)NHRP-RATE: Ethernet1: Used 3Table 251 describes the significant fields shown in the display.
Related Commands
debug nhrp
Displays information about NHRP activity.
debug nhrp options
Displays information about NHRP option processing
debug ntp
To display debugging messages for Network Time Protocol (NTP) features, use the debug ntp command in prvileged EXEC mode. To disable debugging output, use the no form of this command.
debug ntp {adjust | all | authentication | core | events | loopfilter | packet | params | refclock | select | sync | validity}
no debug ntp {adjust | all | authentication | core | events | loopfilter | packet | params | refclock | select | sync | validity}
Syntax Description
Command Default
Debugging is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Starting from Cisco IOS Release 12.4(20)T, NTP version 4 is supported. In NTP version 4 the debugging options available are adjust, all, core, events, packet, and refclock. In NTP version 3 the debugging options available were events, authentication, loopfilter, packets, params, select, sync and validity.
Examples
The following example shows how to enable all debugging options for NTP:
Router# debug ntp allNTP events debugging is onNTP core messages debugging is onNTP clock adjustments debugging is onNTP reference clocks debugging is onNTP packets debugging is onRelated Commands
debug oam
To display operation and maintenance (OAM) events, use the debug oam command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug oam
no debug oam
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug oam command:
Router# debug oam4/0(O): VCD:0x0 DM:0x300 *OAM Cell* Length:0x390000 0300 0070 007A 0018 0100 0000 05FF FFFF FFFF FFFF FFFF FFFF FFFF FFFFFFFF FFFF FFFF FFFF FF6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A00 0000Table 252 describes the significant fields shown in the display.
debug oer api
To display Optimized Edge Routing (OER) application interface debugging information, use the debug oer api command in privileged EXEC mode. To stop the display of OER application interface debugging information, use the no form of this command.
debug oer api [detail]
no debug oer api
Syntax Description
Command Default
Detailed OER application interface debugging messages are not displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug oer api command is used to display messages about any configured OER application interface providers or host devices. The OER application interface defines the mode of communication and messaging between applications and the network for the purpose of optimizing the traffic associated with the applications. A provider is defined as an entity outside the network in which the router configured as an OER master controller exists, for example, an ISP, or a branch office of the same company. The provider has one or more host devices running one or more applications that use the OER application interface to communicate with an OER master controller. A provider must be registered with an OER master controller before an application on a host device can interface with OER. Use the api provider command to register the provider, and use the host-address command to configure a host device. After registration, a host device in the provider network can initiate a session with an OER master controller. The application interface provides an automated method for networks to be aware of applications and provides application-aware performance routing.
Caution
Examples
The following example enables the display of OER application interface debugging messages and the output shows that an OER policy failed due to a prefix that is not found:
Router# debug oer apiOER api debugging is on*May 26 01:04:07.278: OER API: Data set id received 5, data set len 9, host ip 10.3.3.3, session id 1, requies2*May 26 01:04:07.278: OER API: Received get current policy, session id 1 request id 22*May 26 01:04:07.278: OER API: Recvd Appl with Prot 256 DSCP 0 SrcPrefix 0.0.0.0/0 SrcMask 0.0.0.0*May 26 01:04:07.278: OER API: DstPrefix 10.2.0.0/24 DstMask 255.255.255.0 Sport_min 0 Sport_max 0 Dport_mi0*May 26 01:04:07.278: OER API: get prefix policy failed - prefix not found*May 26 01:04:07.278: OER API: Get curr policy cmd received. rc 0*May 26 01:04:07.278: OER API: Received send status response, status 0, session id 1, request id 22, sequence0*May 26 01:04:07.278: OER API: rc for data set 0Table 253 describes the significant fields shown in the display. The content of the debugging messages depends on the commands that are subsequently entered at the router prompt.
Table 253 debug oer api Field Descriptions
OER api debugging is on
Shows that application interface debugging is enabled.
OER API
Displays an OER application interface message.
Related Commands
debug oer api client
To display Optimized Edge Routing (OER) application programming interface (API) client debugging information for master controller and border router communication, use the debug oer api client command in privileged EXEC mode. To stop the display of OER debugging information, use the no form of this command.
debug oer api client [detail]
no debug oer api client [detail]
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer api client command can be entered on a master controller. This command is used to display messages about a configured OER API client. When the detail keyword is entered, the amount of detailed output to be displayed can utilize a considerable amount of system resources. Use the detail keyword with caution in a production network.
Examples
The following example enables the display of OER API client debugging messages:
Router# debug oer api clientAPI Client debugging enabledRelated Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer border
To display general OER border router debugging information, use the debug oer border command in privileged EXEC mode. To stop the display of OER debugging information, use the no form of this command.
debug oer border
no debug oer border
Syntax Description
This command has no arguments or keywords.
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer border command is entered on a border router. This command is used to display debugging information about the OER border process, controlled routes and monitored prefixes.
Examples
The following example displays general OER debugging information:
Router# debug oer border*May 4 22:32:33.695: OER BR: Process Message, msg 4, ptr 33272128, value 140*May 4 22:32:34.455: OER BR: Timer event, 0Table 254 describes the significant fields shown in the display.
Table 254 debug oer border Field Descriptions
OER BR:
Indicates debugging information for OER Border process.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer border active-probe
To display debugging information for active probes configured on the local border router, use the debug oer border active-probe command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.
debug oer border active-probe
no debug oer border active-probe
Syntax Description
This command has no arguments or keywords.
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer border active-probe command is entered on a master controller. This command is used to display the status and results of active probes that are configured on the local border router.
Examples
The following example enables the display of active-probe debug information on a border router:
Router# debug oer border active-probe*May 4 23:47:45.633: OER BR ACTIVE PROBE: Attempting to retrieve ProbeStatistics.probeType = echo, probeTarget = 10.1.5.1, probeTargetPort = 0probeSource = Default, probeSourcePort = 0, probeNextHop = DefaultprobeIfIndex = 13*May 4 23:47:45.633: OER BR ACTIVE PROBE: Completed retrieving ProbeStatistics.probeType = echo, probeTarget = 10.1.5.1, probeTargetPort = 0probeSource = Default, probeSourcePort = 0, probeNextHop = 10.30.30.2probeIfIndex = 13, SAA index = 15*May 4 23:47:45.633: OER BR ACTIVE PROBE: Completions 11, Sum of rtt 172,Max rtt 36, Min rtt 12*May 4 23:47:45.693: OER BR ACTIVE PROBE: Attempting to retrieve ProbeStatistics.probeType = echo, probeTarget = 10.1.4.1, probeTargetPort = 0probeSource = Default, probeSourcePort = 0, probeNextHop = DefaultprobeIfIndex = 13*May 4 23:47:45.693: OER BR ACTIVE PROBE: Completed retrieving ProbeStatistics.probeType = echo, probeTarget = 10.1.4.1, probeTargetPort = 0probeSource = Default, probeSourcePort = 0, probeNextHop = 10.30.30.2probeIfIndex = 13, SAA index = 14Table 255 describes the significant fields shown in the display.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer border learn
To display debugging information about learned prefixes on the local border router, use the debug oer border learn command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.
debug oer border learn [top number]
no debug oer border learn [top number]
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug oer border learn command is entered on a border router. This command is used to display debugging information about prefixes learned on the local border router.
Examples
The following example enables the display of active-probe debug information on a border router:
Router# debug oer border learn*May 4 22:51:31.971: OER BR LEARN: Reporting prefix 1: 10.1.5.0, throughput 201*May 4 22:51:31.971: OER BR LEARN: Reporting 1 throughput learned prefixes*May 4 22:51:31.971: OER BR LEARN: State change, new STOPPED, old STARTED, reason Stop LearnTable 256 describes the significant fields shown in the display.
Table 256 debug oer border learn Field Descriptions
OER BR LEARN:
Indicates debugging information for the OER border router learning process.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer border routes
To display debugging information for OER controlled or monitored routes on the local border router, use the debug oer border routes command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.
debug oer border routes {bgp | static}
no debug oer border routes {bgp | static}
Syntax Description
bgp
Displays debugging information for only BGP routes.
static
Displays debugging information for only static routes.
Command Default
No debugging is enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer border routes command is entered on a border router. This command is used to display the debugging information about OER controlled or monitored routes on the local border router.
Examples
The following example enables the display of active-probe debug information on a border router:
Router# debug oer border routes*May 4 22:35:53.239: OER BGP: Control exact prefix 10.1.5.0/24*May 4 22:35:53.239: OER BGP: Walking the BGP table for 10.1.5.0/24*May 4 22:35:53.239: OER BGP: Path for 10.1.5.0/24 is now under OER control*May 4 22:35:53.239: OER BGP: Setting prefix 10.1.5.0/24 as OER net#Table 257 describes the significant fields shown in the display.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer border traceroute reporting
To display debugging information for traceroute probes on the local border router, use the debug oer border traceroute reporting command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.
debug oer border traceroute reporting [detail]
no debug oer border traceroute reporting [detail]
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug oer border traceroute reporting command is entered on a border router. This command is used to display the debugging information about traceroute probes sourced on the local border router.
Examples
The following example enables the display of active-probe debug information on a border router:
Router# debug oer border traceroute reportingMay 19 03:46:23.807: OER BR TRACE(det): Received start message: msg1 458776, msg2 1677787648, if index 19, host addr 100.1.2.1, flags 1, max ttl 30, protocol 17, probe delay 0May 19 03:46:26.811: OER BR TRACE(det): Result msg1 458776, msg2 1677787648 num hops 30 sent May 19 03:47:20.919: OER BR TRACE(det): Received start message: msg1 524312, msg2 1677787648, if index 2, host addr 100.1.2.1, flags 1, max ttl 30, protocol 17, probe delay 0May 19 03:47:23.923: OER BR TRACE(det): Result msg1 524312, msg2 1677787648 num hops 3 sentTable 258 describes the significant fields shown in the display.
Table 258 debug oer border traceroute reporting Field Descriptions
OER BR TRACE:
Indicates border router debugging information for traceroute probes.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer cc
To display OER communication control debugging information for master controller and border router communication, use the debug oer cc command in privileged EXEC mode. To stop the display of OER debugging information, use the no form of this command.
debug oer cc [detail]
no debug oer cc [detail]
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer cc command can be entered on a master controller on a border router. This command is used to display messages exchanged between the master controller and the border router. These messages include control commands, configuration commands, and monitoring information. Enabling this command will cause very detailed output to be displayed and can utilize a considerable amount of system resources. This command should be enabled with caution in a production network.
Examples
The following example enables the display of OER communication control debugging messages:
Router# debug oer cc*May 4 23:03:22.527: OER CC: ipflow prefix reset received: 10.1.5.0/24Table 259 describes the significant fields shown in the display.
Table 259 debug oer cc Field Descriptions
OER CC:
Indicates debugging information for OER communication messages.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer master border
To display debugging information for OER border router events on an OER master controller, use the debug oer master border command in privileged EXEC mode. To stop border router event debugging, use the no form of this command.
debug oer master border [ip-address]
no debug oer master border
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer master border command is entered on a master controller. The output displays information related to the events or updates from one or more border routers.
Examples
The following example shows the status of 2 border routers. Both routers are up and operating normally.
Router# debug oer master borderOER Master Border Router debugging is onRouter#1d05h: OER MC BR 10.4.9.7: BR I/F update, status UP, line 1 index 1, tx bw 100000, rx bw 100000, time, tx ld 0, rx ld 0, rx rate 0 rx bytes 3496553, tx rate 0,tx bytes 50160331d05h: OER MC BR 10.4.9.7: BR I/F update, status UP, line 1 index 2, tx bw 100000, rx bw 100000, time, tx ld 0, rx ld 0, rx rate 0 rx bytes 710149, tx rate 0, tx bytes 10289071d05h: OER MC BR 10.4.9.6: BR I/F update, status UP, line 1 index 2, tx bw 100000, rx bw 100000, time, tx ld 0, rx ld 0, rx rate 0 rx bytes 743298, tx rate 0, tx bytes 10279121d05h: OER MC BR 10.4.9.6: BR I/F update, status UP, line 1 index 1, tx bw 100000, rx bw 100000, time, tx ld 0, rx ld 0, rx rate 0 rx bytes 3491383, tx rate 0,tx bytes 5013993Table 260 describes the significant fields shown in the display.
Table 260 debug oer master border Field Descriptions
OER MC BR ip-address:
Indicates debugging information for a border router process. The ip-address identifies the border router.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer master collector
To display data collection debugging information for OER monitored prefixes, use the debug oer master collector command in privileged EXEC mode. To disable the display of this debugging information, use the no form of this command.
debug oer master collector {active-probes [detail [trace]] | netflow}
no debug oer master collector {active-probes [detail [trace]] | netflow}
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer master collector command is entered on a master controller. The output displays data collection information for monitored prefixes.
Examples
debug oer master collector active-probes Example
The following example displays aggregate active probe results for the 10.1.0.0/16 prefix on all border routers that are configured to execute this active probe:
Router# debug oer master collector active-probes*May 4 22:34:58.221: OER MC APC: Probe Statistics Gathered for prefix 10.1.0.0/16 on all exits,notifying the PDP*May 4 22:34:58.221: OER MC APC: Summary Exit Data (pfx 10.1.0.0/16, bdr 10.2.2.2, if 13, nxtHop Default):savg delay 13, lavg delay 14, sinits 25, scompletes 25*May 4 22:34:58.221: OER MC APC: Summary Prefix Data: (pfx 10.1.0.0/16) sloss 0, lloss 0, sunreach 25, lunreach 25, savg raw delay 15, lavg raw delay 15, sinits 6561, scompletes 6536, linits 6561, lcompletes 6536*May 4 22:34:58.221: OER MC APC: Active OOP check doneTable 261 describes the significant fields shown in the display.
Table 261 debug oer master collector active-probes Field Descriptions
OER MC APC:
Indicates debugging information for active probes from the r OER master collector.
debug oer master collector active-probes detail Example
The following example displays aggregate active probe results from each target for the 10.1.0.0/16 prefix on all border routers that are configured to execute this active probe:
Router# debug oer master collector active-probes detail*May 4 22:36:21.945: OER MC APC: Rtrv Probe Stats: BR 10.2.2.2, Type echo,Tgt 10.1.1.1,TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13*May 4 22:36:22.001: OER MC APC: Remote stats received: BR 10.2.2.2, Typeecho, Tgt 10.15.1, TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13*May 4 22:36:22.313: OER MC APC: Perf data point (pfx 10.1.0.0/16, bdr10.2.2.2, if 13, xtHop Default): avg delay 20, loss 0, unreach 0,initiations 2, completions 2, delay sum40, ldelay max 20, ldelay min 12*May 4 22:36:22.313: OER MC APC: Perf data point (pfx 10.1.0.0/16, bdr10.2.2.2, if 13, xtHop Default): avg delay 20, loss 0, unreach 0,initiations 2, completions 2, delay sum40, ldelay max 20, ldelay min 12*May 4 22:36:22.313: OER MC APC: Probe Statistics Gathered for prefix10.1.0.0/16 on al exits, notifying the PDP*May 4 22:36:22.313: OER MC APC: Active OOP check doneTable 262 describes the significant fields shown in the display.
Table 262 debug oer master collector active-probes detail Field Descriptions
OER MC APC:
Indicates debugging information for active probes from the r OER master collector.
debug oer master collector active-probes detail trace Example
The following example displays aggregate active probe results and historical statistics from each target for the 10.1.0.0/16 prefix on all border routers that are configured to execute this active probe:
Router# debug oer master collector active-probes detail trace*May 4 22:40:33.845: OER MC APC: Rtrv Probe Stats: BR 10.2.2.2, Type echo,Tgt 10.1.5.1, TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13*May 4 22:40:33.885: OER MC APC: Remote stats received: BR 10.2.2.2, Typeecho, Tgt 10.1.5.1, TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13*May 4 22:40:34.197: OER MC APC: Remote stats received: BR 10.2.2.2, Typeecho, Tgt 10.1.2.1, TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13*May 4 22:40:34.197: OER MC APC: Updating Probe (Type echo Tgt 10.1.2.1TgtPt 0) Total Completes 1306, Total Attempts 1318*May 4 22:40:34.197: OER MC APC: All stats gathered for pfx 10.1.0.0/16Accumulating Stats*May 4 22:40:34.197: OER MC APC: Updating Curr Exit Ref (pfx 10.1.0.0/16,bdr 10.2.2.2, if 13, nxtHop Default) savg delay 17, lavg delay 14, savg loss0, lavg loss 0, savg unreach 0, lavg unreach 0*May 4 22:40:34.197: OER MC APC: Probe Statistics Gathered for prefix10.1.0.0/16 on all exits, notifying the PDP*May 4 22:40:34.197: OER MC APC: Active OOP check doneTable 263 describes the significant fields shown in the display.
Table 263 debug oer master collector active-probes detail trace Field Descriptions
OER MC APC:
Indicates debugging information for active probes from the r OER master collector.
debug oer master collector netflow Example
The following example displays passive monitoring results for the 10.1.5.0/24 prefix:
Router# debug oer master collector netflow*May 4 22:31:45.739: OER MC NFC: Rcvd egress update from BR 10.1.1.2prefix 10.1.5.0/24 Interval 75688 delay_sum 0 samples 0 bytes 20362 pkts 505 flows 359 pktloss 1 unreach 0*May 4 22:31:45.739: OER MC NFC: Updating exit_ref; BR 10.1.1.2 i/f Et1/0, s_avg_delay 655, l_avg_delay 655, s_avg_pkt_loss 328, l_avg_pkt_loss 328, s_avg_flow_unreach 513, l_avg_flow_unreach 513*May 4 22:32:07.007: OER MC NFC: Rcvd ingress update from BR 10.1.1.3prefix 10.1.5.0/24 Interval 75172 delay_sum 42328 samples 77 bytes 22040 pkts 551 flows 310 pktloss 0 unreach 0Table 264 describes the significant fields shown in the display.
Table 264 debug oer master collector netflow Field Descriptions
OER MC NFC:
Indicates debugging information for the OER master collector from passive monitoring (NetFlow).
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer master cost-minimization
To display debugging information for cost-based optimization policies, use the debug oer master cost-minimization command in privileged EXEC mode. To disable the display of this debugging information, use the no form of this command.
debug oer master cost-minimization [detail]
no debug oer master cost-minimization [detail]
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer master cost-minimization command is entered on a master controller. The output displays debugging information for cost-minimization policies.
Examples
The following example displays detailed cost optimization policy debug information:
Router# debug oer master cost-minimization detailOER Master cost-minimization Detail debugging is on*May 14 00:38:48.839: OER MC COST: Momentary target utilization for exit 10.1.1.2 i/fEthernet1/0 nickname ISP1 is 7500 kbps, time_left 52889 secs, cumulative 16 kb, rollup period 84000 secs, rollup target 6000 kbps, bw_capacity 10000 kbps*May 14 00:38:48.839: OER MC COST: Cost OOP check for border 10.1.1.2, current util: 0 target util: 7500 kbps*May 14 00:39:00.199: OER MC COST: ISP1 calc separate rollup ended at 55 ingress Kbps*May 14 00:39:00.199: OER MC COST: ISP1 calc separate rollup ended at 55 egress bytes*May 14 00:39:00.199: OER MC COST: Target utilization for nickname ISP1 set to 6000, rollups elapsed 4, rollups left 24*May 14 00:39:00.271: OER MC COST: Momentary target utilization for exit 10.1.1.2 i/f Ethernet1/0 nickname ISP1 is 7500 kbps, time_left 52878 secs, cumulative 0 kb, rollup period 84000 secs, rollup target 6000 kbps, bw_capacity 10000 kbps*May 14 00:39:00.271: OER MC COST: Cost OOP check for border 10.1.1.2, current util: 0 target util: 7500 kbpsTable 265 describes the significant fields shown in the display.
Table 265 debug oer master cost-minimization detail Field Descriptions
OER MC COST:
Indicates debugging information for cost-based optimization on the master controller.
Related Commands
debug oer master exit
To display debug event information for OER managed exits, use the debug oer master exit command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.
debug oer master exit [detail]
no debug oer master exit [detail]
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer master exit command is entered on a master controller. This command is used to display debugging information for master controller exit selection processes.
Examples
The following example shows output form the debug oer master exit command, entered with the detail keyword:
Router# debug oer master exit detail*May 4 11:26:51.539: OER MC EXIT: 10.1.1.1, intf Fa4/0 INPOLICY*May 4 11:26:52.195: OER MC EXIT: 10.2.2.3, intf Se2/0 INPOLICY*May 4 11:26:55.515: OER MC EXIT: 10.1.1.2, intf Se5/0 INPOLICY*May 4 11:29:14.987: OER MC EXIT: 7 kbps should be moved from 10.1.1.1, intf Fa4/0*May 4 11:29:35.467: OER MC EXIT: 10.1.1.1, intf Fa4/0 in holddown state so skip OOP check*May 4 11:29:35.831: OER MC EXIT: 10.2.2.3, intf Se2/0 in holddown state so skip OOP check*May 4 11:29:39.455: OER MC EXIT: 10.1.1.2, intf Se5/0 in holddown state so skip OOP checkTable 266 describes the significant fields shown in the display.
Table 266 debug oer master exit detail Field Descriptions
OER MC EXIT:
Indicates OER master controller exit event.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer master learn
To display debug information for OER master controller learning events, use the debug oer master learn command in privileged EXEC mode. To stop the display of debug information, use the no form of this command.
debug oer master learn
no debug oer master learn
Syntax Description
This command has no arguments or keywords.
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer master learn command is entered on a master controller. This command is used to display debugging information for master controller learning events.
Examples
The following example shows output from the debug oer master learn command. The output an shows OER Top Talker debug events. The master controller is enabling prefix learning for new border router process:
Router# debug oer master learn06:13:43: OER MC LEARN: Enable type 3, state 006:13:43: OER MC LEARN: OER TTC: State change, new RETRY, old DISABLED, reason TT start06:13:43: OER MC LEARN: OER TTC: State change, new RETRY, old DISABLED, reason TT start request06:13:43: OER MC LEARN: OER TTC: State change, new RETRY, old DISABLED, reason TT start request06:14:13: OER MC LEARN: TTC Retry timer expired06:14:13: OER MC LEARN: OER TTC: State change, new STARTED, old RETRY, reason Atleast one BR started06:14:13: %OER_MC-5-NOTICE: Prefix Learning STARTED06:14:13: OER MC LEARN: MC received BR TT status as enabled06:14:13: OER MC LEARN: MC received BR TT status as enabled06:19:14: OER MC LEARN: OER TTC: State change, new WRITING DATA, old STARTED, reason Updating DB06:19:14: OER MC LEARN: OER TTC: State change, new SLEEP, old WRITING DATA, reason Sleep stateTable 267 describes the significant fields shown in the display.
Table 267 debug oer master learn Field Descriptions
OER MC LEARN:
Indicates OER master controller learning events.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer master prefix
To display debug events related to prefix processing on an OER master controller, use the debug oer master prefix command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug oer master prefix [prefix | appl] [detail]
no debug oer master prefix [prefix | appl] [detail]
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer master prefix command is entered on a master controller. This command displays debugging information related to prefix monitoring and processing.
Examples
The following example shows the master controller searching for the target of an active probe after the target has become unreachable.
Router# debug oer master prefixOER Master Prefix debugging is on06:01:28: OER MC PFX 10.4.9.0/24: APC last target deleted for prefix, no targetsleft assigned and running06:01:38: OER MC PFX 10.4.9.0/24: APC Attempting to probe all exits06:02:59: OER MC PFX 10.4.9.0/24: APC last target deleted for prefix, no targetsleft assigned and running06:03:08: OER MC PFX 10.4.9.0/24: APC Attempting to probe all exits06:04:29: OER MC PFX 10.4.9.0/24: APC last target deleted for prefix, no targetsleft assigned and running06:04:39: OER MC PFX 10.4.9.0/24: APC Attempting to probe all exits06:05:59: OER MC PFX 10.4.9.0/24: APC last target deleted for prefix, no targetsleft assigned and running06:06:09: OER MC PFX 10.4.9.0/24: APC Attempting to probe all exitsTable 268 describes the significant fields shown in the display.
Table 268 debug oer master prefix Field Descriptions
OER MC PFX ip-address:
Indicates debugging information for OER monitored prefixes. The ip-address identifies the prefix.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer master prefix-list
To display debug events related to prefix-list processing on an OER master controller, use the debug oer master prefix-list command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug oer master prefix-list list-name [detail]
no debug oer master prefix-list list-name
Syntax Description
list-name
Specifies a single prefix or prefix range. The prefix address and mask are entered with this argument.
detail
(Optional) Displays detailed OER prefix-list processing information.
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer master prefix-list command is entered on a master controller. This command displays debugging information related to prefix-list processing.
Examples
The following example shows output from the debug oer master prefix-list command.
Router# debug oer master prefix-list23:02:16.283: OER MC PFX 10.1.5.0/24: Check PASS REL loss: loss 0, policy 10%, notify TRUE23:02:16.283: OER MC PFX 10.1.5.0/24: Passive REL loss in-policy23:02:16.283: OER MC PFX 10.1.5.0/24: Check PASS REL delay: delay 124, policy 50%, notify TRUE23:02:16.283: OER MC PFX 10.1.5.0/24: Passive REL delay in policy23:02:16.283: OER MC PFX 10.1.5.0/24: Prefix not OOP23:02:16.283: OER MC PFX 10.1.5.0/24: Check PASS REL unreachable: unreachable 0, policy 50%, notify TRUE23:02:16.283: OER MC PFX 10.1.5.0/24: Passive REL unreachable in-policy23:02:16.283: OER MC PFX 10.1.5.0/24: Check PASS REL loss: loss 0, policy 10%, notify TRUE23:02:16.283: OER MC PFX 10.1.5.0/24: Passive REL loss in policyTable 269 describes the significant fields shown in the display.
Table 269 debug oer master prefix-list Field Descriptions
OER MC PFX ip-address:
Indicates debugging information for OER monitored prefixes. The ip-address identifies the prefix.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer master process
To display debug information about the OER master controller process, use the debug oer master process command in privileged EXEC mode. To stop displaying debug information, use the no form of this command.
debug oer master process
no debug oer master process
Syntax Description
This command has no arguments or keywords.
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug oer master process command is entered on a master controller.
Examples
The following sample debug output for a master controller process:
Router# debug oer master process01:12:00: OER MC PROCESS: Main msg type 15, ptr 0, value 0Table 270 describes the significant fields shown in the display.
Table 270 debug oer master process Field Descriptions
OER MC PROCESS:
Indicates a master controller master process debugging message.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug oer master traceroute reporting
To display debug information about traceroute probes, use the debug oer master traceroute reporting command in privileged EXEC mode. To stop displaying debug information, use the no form of this command.
debug oer master traceroute reporting [detail]
no debug oer master traceroute reporting [detail]
Syntax Description
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug oer master traceroute reporting command is entered on a master controller. This command is used to display traceroute events on a master controller.
Examples
The following sample debug output for a master controller process:
Router# debug oer master traceroute reporting detail*May 12 18:55:14.239: OER MC TRACE: sent start message msg1 327704, msg2 167838976, if index 2, host add 10.1.5.2, flags 1, max ttl 30, protocol 17*May 12 18:55:16.003: OER MC TRACE: sent start message msg1 393240, msg2 167838976, if index 2, host add 10.1.5.2, flags 1, max ttl 30, protocol 17master#*May 12 18:55:17.303: OER MC TRACE: Received result: msg_id1 327704, prefix 10.1.5.0/24, hops 4, flags 1*May 12 18:55:19.059: OER MC TRACE: Received result: msg_id1 393240, prefix 10.1.5.0/24, hops 4, flags 1Table 271 describes the significant fields shown in the display.
Table 271 debug oer master traceroute reporting detail Field Descriptions
OER MC PROCESS:
Indicates master controller debugging information for traceroute probes.
Related Commands
oer
Enables an OER process and configures a router as an OER border router or as an OER master controller.
debug packet
To display per-packet debugging output, use the debug packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug packet [interface number [vcd vcd-number] | vc vpi/vci | vc-name]
no debug packet [interface number [vcd vcd-number] | vc vpi/vci | vc-name]
Syntax Description
Defaults
Debugging for packets is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug packet command displays all process-level packets for both outbound and inbound packets. This command is useful for determining whether packets are being received and sent correctly. The output reports information online when a packet is received or a transmission is attempted.
For sent packets, the information is displayed only after the protocol data unit (PDU) is entirely encapsulated and a next hop VC is found. If information is not displayed, the address translation probably failed during encapsulation. When a next hop VC is found, the packet is displayed exactly as it will be presented on the wire. Having a display indicates that the packets are properly encapsulated for transmission.
For received packets, information is displayed for all incoming frames. The display can show whether the sending station properly encapsulates the frames. Because all incoming frames are displayed, this information is useful when performing back-to-back testing and corrupted frames cannot be dropped by an intermediary switch.
The debug packet command also displays the initial bytes of the actual PDU in hexadecimal. This information can be decoded only by qualified support or engineering personnel.
Caution
Examples
The following is sample output from the debug packet command:
Router# debug packet2/0.5(I): VCD:0x9 VCI:0x23 Type:0x0 SAP:AAAA CTL:03 OUI:000000 TYPE:0800 Length0x704500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105Table 272 describes the significant fields shown in the display.
The following two lines of output are the binary data, which are the contents of the protocol data unit (PDU) before encapsulation:
4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105The following is sample output from the debug packet command:
Router# debug packetEthernet0: Unknown ARPA, src 0000.0c00.6fa4, dst ffff.ffff.ffff, type 0x0a0data 00000c00f23a00000c00ab45, len 60Serial3: Unknown HDLC, size 64, type 0xaaaa, flags 0x0F00Serial2: Unknown PPP, size 128Serial7: Unknown FRAME-RELAY, size 174, type 0x5865, DLCI 7aSerial0: compressed TCP/IP packet droppedTable 273 describes the significant fields shown in the display.
debug packet-capture
To enable packet-capture infra debugs, use the debug packet-capture command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug packet-capture
no debug packet-capture
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows output from a successful request when using the debug packet-capture command
Router# debug packet-captureBuffer Capture Infrastructure debugging is onRelated Commands
debug pad
To display debugging messages for all packet assembler/disassembler (PAD) connections, use the debug pad command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug pad
no debug pad
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
Use the debug pad command to gather information to forward to the Cisco Technical Assistance Center (TAC) to assist in troubleshooting a problem that involves PAD connections.
The following example shows output of the debug pad and debug x25 event commands for an incoming PAD call destined for a terminal line. The incoming PAD call is rejected by the terminal line because the selected network closed user group (CUG) has not been subscribed to by the caller:
Router# debug padRouter# debug x25 eventSerial1/1:X.25 I R1 Call (16) 8 lci 8From (7):2001534 To (9):200261150Facilities:(2)Closed User Group (basic):99Call User Data (4):0x01000000 (pad)pad_svc_announce:destination matched 1PAD:incoming call to 200261150 on line 130 CUD length 4!PAD130:Incoming Call packet, Closed User Group (CUG) service protection, selected network CUG not subscribedPAD:CUG service protection Cause:11 Diag:65Serial1/1:X.25 O R1 Clear (5) 8 lci 8Cause 0, Diag 65 (DTE originated/Facility code not allowed)Serial1/1:X.25 I R1 Clear Confirm (3) 8 lci 8The following example shows the output of the debug pad command for an outgoing PAD call initiated from a terminal line with a subscribed CUG that bars outgoing access:
!PAD130:Outgoing Call packet, Closed User Group - CUG service validation, selected CUG !bars outgoing accessPAD130:Closing connection to . In 0/0, out 0/0debug piafs events
To check the debugging messages for Personal Handyphone Internet Access Forum Standard (PIAFS) calls, use the debug piafs events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug piafs events
no debug piafs events
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug piafs events command provides debugging information for the PIAFS calls on the router, including the inband negotiation process.
Examples
The debug piafs events command was configured to provide the following information for PIAFS calls:
Router# debug piafs events02:16:39:PIAFS events debugging is on02:16:167516180371:PIAFS: RX <- CDAPI :cdapi_route_call Request02:16:167517398148:PIAFS: RX <- CDAPI :CDAPI_MSG_CONNECT_IND02:16:171798691839:PIAFS: TX -> CDAPI :CDAPI_MSG_SUBTYPE_ALERT_REQ02:16:167503724545:PIAFS: TX -> CDAPI :CDAPI_MSG_CONNECT_RESP02:16:167503765504:PIAFS: TX -> CDAPI :CDAPI_MSG_CONN_ACTIVE_REQ02:16:167503724544:PIAFS: RX <- CDAPI :CDAPI_MSG_CONN_ACTIVE_IND02:16:171798691839:PIAFS:Network allotted Channel :B102:16:167503765504:PIAFS:Enabling QMC in PIAFS mode for B102:16:171798691839:PIAFS:piafs_driver_enable_settings()02:16:167503765504:PIAFS:The speed is :6402:16:167503724544:PIAFS:Starting 64 kbps PIAFS Incoming02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:13 RSN:1 CRSN:1 SISN:255]02:16:39:PIAFS:Updating conf resp num02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:1 RSN:1 CRSN:13 SISN:255]02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:14 RSN:1 CRSN:1 SISN:255]02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:2 RSN:2 CRSN:13 SISN:255]02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:15 RSN:1 CRSN:1 SISN:255]02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:3 RSN:3 CRSN:13 SISN:255]02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:16 RSN:1 CRSN:1 SISN:255]02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:4 RSN:4 CRSN:13 SISN:255]02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:17 RSN:1 CRSN:1 SISN:255]02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:5 RSN:5 CRSN:13 SISN:255]02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:18 RSN:1 CRSN:1 SISN:255]02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:6 RSN:6 CRSN:13 SISN:255]02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:19 RSN:1 CRSN:1 SISN:255]02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:7 RSN:7 CRSN:13 SISN:255]02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]02:16:39:PIAFS:Rx Parameters:02:16:39:PIAFS: Data Protocol:Version 102:16:39:PIAFS: Control Protocol:Version 102:16:39:PIAFS: RTF value:902:16:39:PIAFS: Compression:V.42bis02:16:39:PIAFS: Frame Length:8002:16:39:PIAFS: Frame Number:6302:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]02:16:39:PIAFS:ACKed all the Rx control parameters02:16:39:PIAFS:Piafs layer up & Main FSM set to DATA02:16:39:PIAFS:Compression v42bis enabled02:16:39:PIAFS:V42BIS:v42bis_init()02:16:39:PIAFS:V42BIS:v42bis_init()02:16:39:PIAFS:V42BIS:Negotiated Values for P1, P2 are - 4096 , 25002:16:39:PIAFS:Incoming call invoking ISDN_CALL_CONNECT02:16:39:%LINK-3-UPDOWN:Interface BRI0:1, changed state to up02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]02:16:39:PIAFS:Rx Parameters:02:16:39:PIAFS: Data Protocol:Version 102:16:39:PIAFS: Control Protocol:Version 102:16:39:PIAFS: RTF value:902:16:39:PIAFS: Compression:V.42bis02:16:39:PIAFS: Frame Length:8002:16:39:PIAFS: Frame Number:6302:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]02:16:39:PIAFS:ACKed all the Rx control parameters02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]02:16:39:PIAFS:Rx Parameters:02:16:39:PIAFS: Data Protocol:Version 102:16:39:PIAFS: Control Protocol:Version 102:16:39:PIAFS: RTF value:902:16:39:PIAFS: Compression:V.42bis02:16:39:PIAFS: Frame Length:8002:16:39:PIAFS: Frame Number:6302:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]02:16:39:PIAFS:ACKed all the Rx control parameters02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]02:16:39:PIAFS:Rx Parameters:02:16:39:PIAFS: Data Protocol:Version 102:16:39:PIAFS: Control Protocol:Version 102:16:39:PIAFS: RTF value:902:16:39:PIAFS: Compression:V.42bis02:16:39:PIAFS: Frame Length:8002:16:39:PIAFS: Frame Number:6302:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]02:16:39:PIAFS:ACKed all the Rx control parameters02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]02:16:39:PIAFS:Rx Parameters:02:16:39:PIAFS: Data Protocol:Version 102:16:39:PIAFS: Control Protocol:Version 102:16:39:PIAFS: RTF value:902:16:39:PIAFS: Compression:V.42bis02:16:39:PIAFS: Frame Length:8002:16:39:PIAFS: Frame Number:6302:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]02:16:39:PIAFS:ACKed all the Rx control parameters02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]02:16:39:PIAFS:Rx Parameters:02:16:39:PIAFS: Data Protocol:Version 102:16:39:PIAFS: Control Protocol:Version 102:16:39:PIAFS: RTF value:902:16:39:PIAFS: Compression:V.42bis02:16:39:PIAFS: Frame Length:8002:16:39:PIAFS: Frame Number:6302:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]02:16:39:PIAFS:ACKed all the Rx control parameters02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]02:16:39:PIAFS:Rx Parameters:02:16:39:PIAFS: Data Protocol:Version 102:16:39:PIAFS: Control Protocol:Version 102:16:39:PIAFS: RTF value:902:16:39:PIAFS: Compression:V.42bis02:16:39:PIAFS: Frame Length:8002:16:39:PIAFS: Frame Number:6302:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]02:16:39:PIAFS:ACKed all the Rx control parameters02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]02:16:39:PIAFS:Rx Parameters:02:16:39:PIAFS: Data Protocol:Version 102:16:39:PIAFS: Control Protocol:Version 102:16:39:PIAFS: RTF value:902:16:39:PIAFS: Compression:V.42bis02:16:39:PIAFS: Frame Length:8002:16:39:PIAFS: Frame Number:6302:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]02:16:39:PIAFS:ACKed all the Rx control parameters02:16:39:PIAFS:piafs_setmap() tx_map FFFFFFFF02:16:39:PIAFS:piafs_setmap() rx_map 002:16:41:PIAFS:PPP:Autoselect sample 7E02:16:41:PIAFS:PPP:Autoselect sample 7EFF02:16:41:PIAFS:PPP:Autoselect sample 7EFF7D02:16:41:PIAFS:PPP:Autoselect sample 7EFF7D2302:16:41:PIAFS:piafs_setmap() tx_map FFFFFFFF02:16:41:PIAFS:piafs_setmap() rx_map 002:16:42:PIAFS:piafs_setmap() tx_map A000002:16:42:PIAFS:piafs_setmap() rx_map 0Table 274 describes the significant fields shown in the display.
debug platform link-dc
To display debugging messages for the link daughter card, use the debug platform link-dc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug platform link-dc {dwdm | interface | interrupt | netclk | serdes | transceiver | wanphy}
no debug platform link-dc {dwdm | interface | interrupt | netclk | serdes | transceiver | wanphy}
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command with the remote command command or the attach command in privileged EXEC mode.
Examples
The following examples show the output for both the debug platform link-dc tranceiver command and the debug platform link-dc interrupt command. Notice that the show platform hardware transceiver command shows the status for the port.
Router# remote command module 1 debug platform link-dc tranceiverLink-DC transceiver debugging is onRouter# remote command module 1 debug platform link-dc interruptLink-DC interrupt debugging is onRouter# remote command module 1 show debugx40g subsystem:Link-DC transceiver debugging is onLink-DC interrupt debugging is onRouter# remote command module 1 show platform hardware transceiver status 1Show status info for port 1:TenGigabitEthernet1/1:State: EnabledEnvironmental Information - raw valuesTemperature: 7616Tx voltage: 0 in units of 100uVoltTx bias: 28722 uATx power: -2 dBm (5441 in units of 0.1 uW)Rx power: 0 dBm (7712 in units of 0.1 uW)(AUX1) Laser Temperature: 8704(AUX2) +3.3V Supply Voltage: 32928XFP TX is enabled.XFP TX is soft enabled.XFP is ready.XFP is not power down.XFP is not soft power down.XFP doesn't have interrupt(s).XFP is not LOS.XFP data is ready.XFP TX path is ready.XFP TX laser is not in fault condition.XFP TX path CDR is locked.XFP RX path is ready.XFP RX path CDR is locked.No active alarmsNo active warningRouter-dfc1#*Aug 15 11:20:26.436 PDT: DFC1: TenGigabitEthernet1/1 XFP: show status*Aug 15 11:20:26.436 PDT: DFC1: TenGigabitEthernet1/1 XFP: show environmental monitoring*Aug 15 11:20:26.436 PDT: DFC1: pluggable optics read - addr: 50, offset: 60, len: 14, dataptr: 2377A668*Aug 15 11:20:26.448 PDT: DFC1: pluggable optics read - addr: 50, offset: 6E, len: 2, dataptr: 21AA028E*Aug 15 11:20:26.452 PDT: DFC1: pluggable optics read - addr: 50, offset: 50, len: 2, dataptr: 2377A6A0*Aug 15 11:20:26.456 PDT: DFC1: pluggable optics read - addr: 50, offset: 52, len: 2, dataptr: 2377A6A2
Note
Router-dfc1#*Aug 15 11:23:52.127 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:23:52.127 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:23:52.127 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:23:52.127 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 0*Aug 15 11:23:52.131 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:23:52.131 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:23:52.131 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:23:52.131 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 1*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_dc_process: interrupt msg_id 6, msg_num 1*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:23:52.135 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 0*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x4000*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_xcvr_isr: intr_st 0x2, start 0, end 4, type 2,port_offset 0x0*Aug 15 11:23:52.135 PDT: DFC1: Link xcvr port 1: Rx LOS interrupt*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_dc_process: interrupt msg_id 2, msg_num 1*Aug 15 11:23:52.135 PDT: DFC1: Port 2: transceiver Rx LOS event*Aug 15 11:23:52.147 PDT: DFC1: x40g_link_dc_process: xcvr oir timer timeout00:12:37: %LINEPROTO-DFC1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/2, changed state to down*Aug 15 11:24:46.576 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x4000*Aug 15 11:24:46.576 PDT: DFC1: x40g_link_xcvr_isr: intr_st 0x2, start 0, end 4, type 2,port_offset 0x0*Aug 15 11:24:46.576 PDT: DFC1: Link xcvr port 1: Rx LOS interrupt*Aug 15 11:24:46.576 PDT: DFC1: x40g_link_dc_process: interrupt msg_id 2, msg_num 1*Aug 15 11:24:46.576 PDT: DFC1: Port 2: transceiver Rx LOS recovered*Aug 15 11:24:46.580 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:24:46.580 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:24:46.580 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:24:46.580 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 0*Aug 15 11:24:46.584 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:24:46.584 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:24:46.584 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:24:46.584 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 1*Aug 15 11:24:46.584 PDT: DFC1: x40g_link_dc_process: interrupt msg_id 6, msg_num 1*Aug 15 11:24:46.600 PDT: DFC1: x40g_link_dc_process: xcvr oir timer timeout00:13:31: %LINEPROTO-DFC1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/2, changed state to upThe following example shows the output for the debug platform link-dc dwdm command.
Router-dfc1# debug platform link-dc dwdmLink-DC OTN G.709/DWDM debugging is on*Jan 28 12:10:38.784 PDT: DFC1: Port 1: OTN Alarm Query, return ptr 228E877Clos 1, oof 0, lof 0, mfas 1, lom 0otuAis 0, otuIae 0-0, otuBdi 0, otuTim 0oduAis 0, oduBdi 0, oduLck 0, oduOci 0, oduPtim 0*Jan 28 12:10:38.864 PDT: DFC1: x40g_link_pemaquid_pm_tick_timer_event(1): pm_tick timer timeout*Jan 28 12:10:39.364 PDT: DFC1: x40g_link_pemaquid_pm_tick_timer_event(1): pm_tick timer timeout*Jan 28 12:10:39.840 PDT: DFC1: Port 1: OTN Alarm Query, return ptr 228E877Clos 1, oof 0, lof 0, mfas 1, lom 0otuAis 0, otuIae 0-0, otuBdi 0, otuTim 0oduAis 0, oduBdi 0, oduLck 0, oduOci 0, oduPtim 0The following example shows the output for the debug platform link-dc wanphy command.
Router-dfc1# debug platform link-dc wanphyLink-DC WAN PHY debugging is on*Jan 28 11:59:16.184 PDT: DFC1: Port 1 WIS alarms:ser 0, plm_p_far 0, ais_p_far 0, lof 0, los 0rdi 0, ais_l 0, lcd_p 0, plm_p 0, ais_p 0, lop 0*Jan 28 11:59:17.184 PDT: DFC1: Port 1 WIS alarms:ser 0, plm_p_far 0, ais_p_far 0, lof 0, los 0rdi 0, ais_l 0, lcd_p 0, plm_p 0, ais_p 0, lop 0*Jan 28 11:59:17.184 PDT: DFC1: Port 1 WIS counters: b1 0, b2 0, b3 0, fe_b2 0, fe_b3 0*Jan 28 11:59:17.184 PDT: DFC1: Port 1 WIS J1RX: 0x0000000000000089.0x302E302E302E3000...*Jan 28 11:59:22.288 PDT: DFC1: Port 1 WIS alarms:ser 0, plm_p_far 0, ais_p_far 0, lof 0, los 0rdi 0, ais_l 0, lcd_p 0, plm_p 0, ais_p 0, lop 0*Jan 28 11:59:22.288 PDT: DFC1: Port 1 WIS counters: b1 0, b2 0, b3 0, fe_b2 0, fe_b3 0*Jan 28 11:59:22.288 PDT: DFC1: Port 1 WIS J1RX: 0x0000000000000089.0x302E302E302E3000Related Commands
debug policy-firewall
Note
To display messages about Cisco IOS firewall events, including details about the packets of the protocol, use the debug policy-firewall command in EXEC mode. To disable debugging output, use the no form of this command.
debug policy-firewall {function-trace | object-creation | object-deletion | list {access-list | extended-access-list} | events | timers | packet-path | protocol protocol-name | L2-transparent | control-plane | detailed}
no debug policy-firewall {function-trace | object-creation | object-deletion | list {access-list | extended-access-list} | events | timers | packet-path | protocol protocol-name | L2-transparent | control-plane | detailed}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.4(20)T
This command was introduced. This command replaces the debug ip inspect command.
15.0(1)M
The list and packet-path keywords were added.
Usage Guidelines
The debug policy-firewall command is used to troubleshoot firewall problems. The output of this command can be used to analyze the behavior of the firewall and to diagnose the root cause of the problem.
Examples
The following is sample output from the debug policy-firewall function-trace command:
Router# debug policy-firewall function-traceFeb 13 08:13:43: FIREWALL: fw_dp_tcp_init_sis():Feb 13 08:13:43: FIREWALL: fw_dp_insp_init_sis():Feb 13 08:13:43: FIREWALL: fw_dp_tcp_inspect(): , i2r = 1Feb 13 08:13:43: FIREWALL: fw_dp_insp_listen_state():Feb 13 08:13:43: FIREWALL: fw_dp_insp_ensure_return_traffic():Feb 13 08:13:43: FIREWALL: fw_dp_insp_process_syn_packet():Feb 13 08:13:43: FIREWALL: fw_dp_insp_create_tcp_host_entry():Feb 13 08:13:43: FIREWALL*: fw_dp_tcp_inspect(): , i2r = 0Feb 13 08:13:43: FIREWALL*: fw_dp_insp_synsent_state():Feb 13 08:13:44: FIREWALL*: fw_dp_tcp_inspect(): , i2r = 1Feb 13 08:13:44: FIREWALL*: fw_dp_insp_synrcvd_state():Feb 13 08:13:44: FIREWALL*: fw_dp_insp_remove_sis_from_host_entry():Feb 13 08:13:44: FIREWALL*: fw_dp_insp_remove_host_entry():Feb 13 08:13:44: FIREWALL*: fw_dp_insp_delete_host_entry():Feb 13 08:13:44: FIREWALL*: fw_dp_insp_handle_icq_control_stream():Feb 13 08:13:44: FIREWALL*: fw_dp_tcp_inspect(): , i2r = 0Feb 13 08:13:44: FIREWALL*: fw_dp_insp_estab_state():Feb 13 08:13:44: FIREWALL*: fw_dp_insp_handle_icq_control_stream():Feb 13 08:13:44: FIREWALL*: fw_dp_tcp_inspect(): , i2r = 1Feb 13 08:13:44: FIREWALL*: fw_dp_insp_estab_state():Feb 13 08:13:44: FIREWALL*: fw_dp_insp_handle_icq_control_stream():Feb 13 08:13:44: FIREWALL*: fw_dp_tcp_inspect(): , i2r = 0Feb 13 08:13:44: FIREWALL*: fw_dp_insp_estab_state():Feb 13 08:13:44: FIREWALL*: fw_dp_insp_handle_icq_control_stream():Feb 13 08:13:44: FIREWALL*: fw_dp_tcp_inspect(): , i2r = 1Feb 13 08:13:44: FIREWALL*: fw_dp_insp_estab_state():Feb 13 08:13:44: FIREWALL*: fw_dp_insp_handle_icq_control_stream():Feb 13 08:13:44: FIREWALL*: fw_dp_tcp_inspect(): , i2r = 0Feb 13 08:13:44: FIREWALL*: fw_dp_insp_estab_state():Feb 13 08:13:44: FIREWALL*: fw_dp_tcp_inspect(): , i2r = 1Feb 13 08:13:44: FIREWALL*: fw_dp_insp_estab_state():Feb 13 08:13:44: %APPFW-6-IM_ICQ_SESSION: im-icq text-chat service session initiator sends 77 bytes session 192.168.3.3:36091 192.168.103.3:5190 on zone-pair zp_test_in class test_im appl-class test_icq_1The date in each line of the output is the timestamp. This output shows the functions called by the Cisco IOS firewall as a session is inspected. Entries with an asterisk (*) after the word "FIREWALL" are entries when the fast path is used; otherwise, the process path is used.
The following is sample output from the debug policy-firewall object-creation, debug policy-firewall object-deletion, debug policy-firewall timers and debug policy-firewall events commands:
Router# debug policy-firewall object-creationRouter# debug policy-firewall object-deletionRouter# debug policy-firewall timersRouter# debug policy-firewall eventsLog Buffer (600000 bytes):Feb 13 08:16:17: FIREWALL: FW CCE got packet 0x66030694 in process pathFeb 13 08:16:17: FIREWALL: Router gen or router destined pak 0x66030694, let it passFeb 13 08:16:17: FIREWALL: FW CCE got packet 0x660311F8 in process pathFeb 13 08:16:17: FIREWALL: Router gen or router destined pak 0x660311F8, let it passFeb 13 08:16:17: FIREWALL: FW CCE got packet 0x66030A60 in process pathFeb 13 08:16:17: FIREWALL: Router gen or router destined pak 0x66030A60, let it passFeb 13 08:16:19: FIREWALL: FW CCE got packet 0x660328C0 in process pathFeb 13 08:16:19: FIREWALL: Router gen or router destined pak 0x660328C0, let it passFeb 13 08:16:21: FIREWALL: FW CCE got packet 0x66031D5C in process pathFeb 13 08:16:21: FIREWALL: Router gen or router destined pak 0x66031D5C, let it passFeb 13 08:16:22: FIREWALL: FW CCE got packet 0x66032128 in process pathFeb 13 08:16:22: FIREWALL: Router gen or router destined pak 0x66032128, let it passFeb 13 08:16:22: FIREWALL: FW CCE got packet 0x660324F4 in process pathFeb 13 08:16:22: FIREWALL: Router gen or router destined pak 0x660324F4, let it passFeb 13 08:16:24: FIREWALL: FW CCE got packet 0x66033424 in process pathFeb 13 08:16:24: FIREWALL: Router gen or router destined pak 0x66033424, let it passFeb 13 08:16:25: FIREWALL: fw_dp_insp_handle_timer_eventFeb 13 08:16:25: FIREWALL: fw_dp_insp_sample_session_rateFeb 13 08:16:26: FIREWALL: FW CCE got packet 0x66032C8C in process pathFeb 13 08:16:26: FIREWALL: Router gen or router destined pak 0x66032C8C, let it passFeb 13 08:16:26: FIREWALL: FW CCE got packet 0x6602DCD0 in process pathFeb 13 08:16:26: FIREWALL: Router gen or router destined pak 0x6602DCD0, let it passFeb 13 08:16:26: FIREWALL: FW CCE got packet 0x5011DDB4 in process pathFeb 13 08:16:26: FIREWALL: Router gen or router destined pak 0x5011DDB4, let it passFeb 13 08:16:28: FIREWALL: FW CCE got packet 0x5011D9E8 in process pathFeb 13 08:16:28: FIREWALL: sis 20491840 : Timer Start: Timer: 20491964 Time: 30000 milisecsFeb 13 08:16:28: FIREWALL: sis 20491840 : Timer Init LeafFeb 13 08:16:28: FIREWALL: sis 20491840 : Allocating L7 sis extensionL4 protocol = 1, L7 protocol = 62, granular = 5Feb 13 08:16:28: FIREWALL: sis 20491840 : create host entry 669F3180 addr 192.168.103.3 bucket 12 (vrf 0:0) fwfo 0x507E39C0Feb 13 08:16:29: FIREWALL*: sis 20491840 : Timer Start: Timer: 20491964 Time: 3600000 milisecsFeb 13 08:16:29: %APPFW-6-IM_ICQ_SESSION: im-icq text-chat service session initiator sends 77 bytes session 192.168.3.3:36091 192.168.103.3:5190 on zone-pair zp_test_in class test_im appl-class test_icq_1Feb 13 08:16:29: %APPFW-6-IM_ICQ_SESSION: im-icq text-chat service session initiator gets 198 bytes session 192.168.103.3:5190 192.168.3.3:36091 on zone-pair zp_test_in class test_im appl-class test_icq_1Feb 13 08:16:29: FIREWALL: FW CCE got packet 0x20159864 in process pathFeb 13 08:16:29: FIREWALL: Router gen or router destined pak 0x20159864, let it passFeb 13 08:16:29: FIREWALL: fw_dp_insp_handle_timer_eventFeb 13 08:16:29: FIREWALL: delete host entry 669F3180 addr 192.168.103.3Feb 13 08:16:30: FIREWALL: FW CCE got packet 0x66033058 in process pathFeb 13 08:16:30: FIREWALL: Router gen or router destined pak 0x66033058, let it passFeb 13 08:16:31: FIREWALL: FW CCE got packet 0x660337F0 in process pathFeb 13 08:16:31: FIREWALL: Router gen or router destined pak 0x660337F0, let it passFeb 13 08:16:31: FIREWALL: FW CCE got packet 0x20159C30 in process pathFeb 13 08:16:31: FIREWALL: Router gen or router destined pak 0x20159C30, let it passFeb 13 08:16:34: FIREWALL: FW CCE got packet 0x20159FFC in process pathFeb 13 08:16:34: FIREWALL: Router gen or router destined pak 0x20159FFC, let it passFeb 13 08:16:35: FIREWALL: FW CCE got packet 0x5011E54C in process pathFeb 13 08:16:35: FIREWALL: Router gen or router destined pak 0x5011E54C, let it passFeb 13 08:16:36: FIREWALL: FW CCE got packet 0x665E6304 in process pathFeb 13 08:16:36: FIREWALL: Router gen or router destined pak 0x665E6304, let it passFeb 13 08:16:36: FIREWALL: FW CCE got packet 0x5011E180 in process pathFeb 13 08:16:36: FIREWALL: Router gen or router destined pak 0x5011E180, let it passFeb 13 08:16:38: FIREWALL: fw_dp_insp_handle_timer_eventFeb 13 08:16:38: FIREWALL: fw_dp_insp_sample_session_rateFeb 13 08:16:38: FIREWALL: FW CCE got packet 0x2015A3C8 in process pathFeb 13 08:16:38: FIREWALL: Router gen or router destined pak 0x2015A3C8, let it passFeb 13 08:16:39: FIREWALL: FW CCE got packet 0x5011E918 in process pathFeb 13 08:16:39: FIREWALL: Router gen or router destined pak 0x5011E918, let it passFeb 13 08:16:40: FIREWALL: FW CCE got packet 0x665E6E68 in process pathFeb 13 08:16:40: FIREWALL: Router gen or router destined pak 0x665E6E68, let it passFeb 13 08:16:40: FIREWALL: FW CCE got packet 0x2015A794 in process pathFeb 13 08:16:40: FIREWALL: Router gen or router destined pak 0x2015A794, let it passFeb 13 08:16:43: FIREWALL: FW CCE got packet 0x665E7234 in process pathFeb 13 08:16:43: FIREWALL: Router gen or router destined pak 0x665E7234, let it passFeb 13 08:16:44: FIREWALL: FW CCE got packet 0x5011ECE4 in process pathFeb 13 08:16:44: FIREWALL: Router gen or router destined pak 0x5011ECE4, let it passFeb 13 08:16:44: FIREWALL: FW CCE got packet 0x2015AB60 in process pathFeb 13 08:16:44: FIREWALL: Router gen or router destined pak 0x2015AB60, let it passFeb 13 08:16:45: FIREWALL: FW CCE got packet 0x665E7600 in process pathFeb 13 08:16:45: FIREWALL: Router gen or router destined pak 0x665E7600, let it passFeb 13 08:16:48: FIREWALL: FW CCE got packet 0x665E79CC in process pathFeb 13 08:16:48: FIREWALL: Router gen or router destined pak 0x665E79CC, let it passFeb 13 08:16:48: FIREWALL: FW CCE got packet 0x5011F47C in process pathFeb 13 08:16:48: FIREWALL: Router gen or router destined pak 0x5011F47C, let it passFeb 13 08:16:49: FIREWALL: FW CCE got packet 0x6602E468 in process pathFeb 13 08:16:49: FIREWALL: Router gen or router destined pak 0x6602E468, let it passFeb 13 08:16:50: FIREWALL: fw_dp_insp_handle_timer_eventFeb 13 08:16:50: FIREWALL: fw_dp_insp_sample_session_rateFeb 13 08:16:50: FIREWALL: FW CCE got packet 0x2015B2F8 in process pathFeb 13 08:16:50: FIREWALL: Router gen or router destined pak 0x2015B2F8, let it passFeb 13 08:16:52: FIREWALL: FW CCE got packet 0x6602E09C in process pathFeb 13 08:16:52: FIREWALL: Router gen or router destined pak 0x6602E09C, let it passFeb 13 08:16:53: FIREWALL: FW CCE got packet 0x6602EC00 in process pathFeb 13 08:16:53: FIREWALL: Router gen or router destined pak 0x6602EC00, let it passFeb 13 08:16:54: FIREWALL: FW CCE got packet 0x6602EFCC in process pathFeb 13 08:16:54: FIREWALL: Router gen or router destined pak 0x6602EFCC, let it passFeb 13 08:16:55: FIREWALL: FW CCE got packet 0x6602F764 in process pathFeb 13 08:16:55: FIREWALL: Router gen or router destined pak 0x6602F764, let it passFeb 13 08:16:57: FIREWALL: FW CCE got packet 0x6602F398 in process pathFeb 13 08:16:57: FIREWALL: Router gen or router destined pak 0x6602F398, let it passFeb 13 08:16:57: FIREWALL: FW CCE got packet 0x6602FB30 in process pathFeb 13 08:16:57: FIREWALL: Router gen or router destined pak 0x6602FB30, let it passFeb 13 08:16:59: FIREWALL: FW CCE got packet 0x66030E2C in process pathFeb 13 08:16:59: FIREWALL: Router gen or router destined pak 0x66030E2C, let it passFeb 13 08:16:59: FIREWALL: FW CCE got packet 0x66030694 in process pathFeb 13 08:16:59: FIREWALL: Router gen or router destined pak 0x66030694, let it passFeb 13 08:17:00: FIREWALL*: sis 20491840 : Timer Start: Timer: 20491964 Time: 5000 milisecsFeb 13 08:17:00: FIREWALL*: sis 20491840 : Timer Start: Timer: 20491964 Time: 1000 milisecsFeb 13 08:17:01: FIREWALL: fw_dp_insp_handle_timer_eventFeb 13 08:17:01: FIREWALL: sis 20491840 : Idle Timer Expires: Timer: 20491964Feb 13 08:17:01: FIREWALL: sis 20491840 : Delete sis half_open 0Feb 13 08:17:01: FIREWALL: sis 20491840 : Timer Stop: Timer: 20491964Feb 13 08:17:01: FIREWALL: sis 20491840 : Delete sisFeb 13 08:17:01: FIREWALL: sis 20491840 : session on temporary delete listFeb 13 08:17:01: FIREWALL: sis 20491840 : Calling l4 cleanupFeb 13 08:17:01: FIREWALL: FW CCE got packet 0x660311F8 in process pathFeb 13 08:17:01: FIREWALL: Router gen or router destined pak 0x660311F8, let it passFeb 13 08:17:02: FIREWALL: FW CCE got packet 0x66030A60 in process pathFeb 13 08:17:02: FIREWALL: Router gen or router destined pak 0x66030A60, let it passFeb 13 08:17:02: FIREWALL: fw_dp_insp_handle_timer_eventFeb 13 08:17:02: FIREWALL: fw_dp_insp_sample_session_rateFeb 13 08:17:04: FIREWALL: FW CCE got packet 0x66031990 in process pathFeb 13 08:17:04: FIREWALL: Router gen or router destined pak 0x66031990, let it passFeb 13 08:17:04: FIREWALL: FW CCE got packet 0x660315C4 in process pathFeb 13 08:17:04: FIREWALL: Router gen or router destined pak 0x660315C4, let it passFeb 13 08:17:06: FIREWALL: FW CCE got packet 0x660328C0 in process pathFeb 13 08:17:06: FIREWALL: Router gen or router destined pak 0x660328C0, let it passFeb 13 08:17:07: FIREWALL: FW CCE got packet 0x66031D5C in process pathFeb 13 08:17:07: FIREWALL: Router gen or router destined pak 0x66031D5C, let it passFeb 13 08:17:08: FIREWALL: FW CCE got packet 0x66033424 in process pathFeb 13 08:17:08: FIREWALL: Router gen or router destined pak 0x66033424, let it passFeb 13 08:17:09: FIREWALL: FW CCE got packet 0x66032C8C in process pathFeb 13 08:17:09: FIREWALL: Router gen or router destined pak 0x66032C8C, let it passFeb 13 08:17:11: FIREWALL: FW CCE got packet 0x6602DCD0 in process pathFeb 13 08:17:11: FIREWALL: Router gen or router destined pak 0x6602DCD0, let it passFeb 13 08:17:11: FIREWALL: FW CCE got packet 0x5011DDB4 in process pathFeb 13 08:17:11: FIREWALL: Router gen or router destined pak 0x5011DDB4, let it passFeb 13 08:17:13: FIREWALL: FW CCE got packet 0x20159498 in process pathFeb 13 08:17:13: FIREWALL: Router gen or router destined pak 0x20159498, let it passFeb 13 08:17:13: FIREWALL: FW CCE got packet 0x665E5F38 in process pathFeb 13 08:17:13: FIREWALL: Router gen or router destined pak 0x665E5F38, let it passFeb 13 08:17:14: FIREWALL: fw_dp_insp_handle_timer_eventFeb 13 08:17:14: FIREWALL: fw_dp_insp_sample_session_rateFeb 13 08:17:16: FIREWALL: FW CCE got packet 0x5011D9E8 in process pathFeb 13 08:17:16: FIREWALL: Router gen or router destined pak 0x5011D9E8, let it passFeb 13 08:17:16: FIREWALL: FW CCE got packet 0x20159864 in process pathFeb 13 08:17:16: FIREWALL: Router gen or router destined pak 0x20159864, let it passblr6-7200b#blr6-7200b#The event debug output declares the packet path from which the firewall got the packet. The packet path can be either the Cisco Express Forwarding (CEF) or the process path. The debug policy-firewall command is used when the firewall sends out a packet acting like a proxy.
The timer debug output specifies timer related events. Timers are used to close the sessions created by the firewall. Whenever a timeout happens, the timer debugging output specifies whether it needs to close the session or keep it open for longer.
The following is sample output from the debug policy-firewall protocol icq command:
Router# debug policy-firewall protocol icqApr 2 23:55:21: CCE*: I2R = 1, state_object = 0x0, data_len = 0Apr 2 23:55:21: CCE*: ICQ protocol found...Apr 2 23:55:21: CCE*: cce_dp_named_db_inspect_icq_create_csoApr 2 23:55:21: CCE*: I2R = 0, state_object = 0x508A1014, data_len = 10Apr 2 23:55:21: CCE*: ICQ:state = 1Apr 2 23:55:21: CCE*: ICQ:FLAP Channel = 1 , Packet length = 4Apr 2 23:55:21: CCE*: I2R = 1, state_object = 0x508A1014, data_len = 270Apr 2 23:55:21: CCE*: ICQ:state = 1Apr 2 23:55:21: CCE*: ICQ:FLAP Channel = 1 , Packet length = 264Apr 2 23:55:21: CCE*: ICQ:Find the client versionApr 2 23:55:21: CCE*: ICQ:Get the client stringApr 2 23:55:21: CCE*: ICQ:Object Type = 6,Object Length = 256Apr 2 23:55:21: CCE*: icq_setstate_on_servicetypeApr 2 23:55:21: CCE*: ICQ:Obj Data Skipping :prev state =4Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 0,Curr state = 1 , Prev state = 0Apr 2 23:55:21: CCE*: I2R = 0, state_object = 0x508A1014, data_len = 42Apr 2 23:55:21: CCE*: ICQ:state = 1Apr 2 23:55:21: CCE*: ICQ:FLAP Channel = 2 , Packet length = 36Apr 2 23:55:21: CCE*: ICQ:Family Service Id = 1,Subtype Id = 3Apr 2 23:55:21: CCE*: ICQ:curr state = 9Apr 2 23:55:21: CCE*: I2R = 1, state_object = 0x508A1014, data_len = 56Apr 2 23:55:21: CCE*: ICQ:state = 1Apr 2 23:55:21: CCE*: ICQ:FLAP Channel = 2 , Packet length = 50Apr 2 23:55:21: CCE*: ICQ:Family Service Id = 1,Subtype Id = 23Apr 2 23:55:21: CCE*: ICQ:curr state = 22Apr 2 23:55:21: CCE*: ICQ:service = 1 , version = 4Apr 2 23:55:21: CCE*: ICQ:service = 19 , version = 4Apr 2 23:55:21: CCE*: ICQ:service = 2 , version = 1Apr 2 23:55:21: CCE*: ICQ:service = 3 , version = 1Apr 2 23:55:21: CCE*: ICQ:service = 21 , version = 1Apr 2 23:55:21: CCE*: ICQ:Detected ICQ ProtocolApr 2 23:55:21: CCE*: I2R = 1, state_object = 0x508A1014, data_len = 230Apr 2 23:55:21: CCE*: ICQ:state = 1Apr 2 23:55:21: CCE*: ICQ:FLAP Channel = 2 , Packet length = 224Apr 2 23:55:21: CCE*: ICQ:Family Service Id = 4,Subtype Id = 6Apr 2 23:55:21: CCE*: ICQ:curr state = 14Apr 2 23:55:21: CCE*: icq_process_client_messageApr 2 23:55:21: CCE*: ICQ:Message Channel ID = 2Apr 2 23:55:21: CCE*: icq_skip_client_msgApr 2 23:55:21: CCE*: ICQ:TLV Service Type = 5Apr 2 23:55:21: CCE*: ICQ:length = 190,obj length = 186Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 4,Curr state = 19 , Prev state = 19Apr 2 23:55:21: CCE*: ICQ:TLV Service Type = 3Apr 2 23:55:21: CCE*: ICQ:length = 0,obj length = 0Apr 2 23:55:21: CCE*: I2R = 1, state_object = 0x508A1014, data_len = 66Apr 2 23:55:21: CCE*: ICQ:state = 21Apr 2 23:55:21: CCE*: ICQ:FLAP Channel = 2 , Packet length = 60Apr 2 23:55:21: CCE*: ICQ:Family Service Id = 4,Subtype Id = 6Apr 2 23:55:21: CCE*: ICQ:curr state = 14Apr 2 23:55:21: CCE*: icq_process_client_messageApr 2 23:55:21: CCE*: ICQ:Message Channel ID = 2Apr 2 23:55:21: CCE*: icq_skip_client_msgApr 2 23:55:21: CCE*: ICQ:TLV Service Type = 5Apr 2 23:55:21: CCE*: ICQ:length = 26,obj length = 26Apr 2 23:55:21: CCE*: ICQ:Obj Data Skipping :prev state =19Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 0,Curr state = 1 , Prev state = 0Apr 2 23:55:21: CCE*: ICQ:service found = 2Apr 2 23:55:21: CCE*: ICQ: Found IM default serviceApr 2 23:55:21: %APPFW-6-IM_ICQ_SESSION: im-icq un-recognized service session initiator sends 66 bytes session 192.168.5.3:25610 63.147.175.30:5190 on zone-pair zp_test_in class test_im appl-class test_icq_1Apr 2 23:55:21: CCE*: I2R = 0, state_object = 0x508A1014, data_len = 36Apr 2 23:55:21: CCE*: ICQ:state = 1Apr 2 23:55:21: CCE*: ICQ:FLAP Channel = 2 , Packet length = 30Apr 2 23:55:21: CCE*: ICQ:Family Service Id = 4,Subtype Id = 12Apr 2 23:55:21: CCE*: ICQ:curr state = 9Apr 2 23:55:21: CCE*: I2R = 0, state_object = 0x508A1014, data_len = 285Apr 2 23:55:21: CCE*: ICQ:state = 1Apr 2 23:55:21: CCE*: ICQ:FLAP Channel = 2 , Packet length = 279Apr 2 23:55:21: CCE*: ICQ:Family Service Id = 4,Subtype Id = 7Apr 2 23:55:21: CCE*: ICQ:curr state = 14Apr 2 23:55:21: CCE*: icq_process_client_messageApr 2 23:55:21: CCE*: ICQ:Message Channel ID = 2Apr 2 23:55:21: CCE*: icq_skip_client_msgApr 2 23:55:21: CCE*: ICQ:TLV Service Type = 1Apr 2 23:55:21: CCE*: ICQ:length = 241,obj length = 2Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 239,Curr state = 19 , Prev state = 19Apr 2 23:55:21: CCE*: ICQ:TLV Service Type = 6Apr 2 23:55:21: CCE*: ICQ:length = 235,obj length = 4Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 231,Curr state = 19 , Prev state = 19Apr 2 23:55:21: CCE*: ICQ:TLV Service Type = 5Apr 2 23:55:21: CCE*: ICQ:length = 227,obj length = 4Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 223,Curr state = 19 , Prev state = 19Apr 2 23:55:21: CCE*: ICQ:TLV Service Type = 15Apr 2 23:55:21: CCE*: ICQ:length = 219,obj length = 4Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 215,Curr state = 19 , Prev state = 19Apr 2 23:55:21: CCE*: ICQ:TLV Service Type = 3Apr 2 23:55:21: CCE*: ICQ:length = 211,obj length = 4Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 207,Curr state = 19 , Prev state = 19Apr 2 23:55:21: CCE*: ICQ:TLV Service Type = 5Apr 2 23:55:21: CCE*: ICQ:length = 203,obj length = 190Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 13,Curr state = 19 , Prev state = 19Apr 2 23:55:21: CCE*: ICQ:TLV Service Type = 22Apr 2 23:55:21: CCE*: ICQ:length = 9,obj length = 4Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 5,Curr state = 19 , Prev state = 19Apr 2 23:55:21: CCE*: ICQ:TLV Service Type = 19Apr 2 23:55:21: CCE*: ICQ:length = 1,obj length = 1Apr 2 23:55:21: CCE*: ICQ:Obj Data Skipping :prev state =19Apr 2 23:55:21: CCE*: ICQ:ICQ Data length = 0,Curr state = 1 , Prev state = 0Apr 2 23:56:10: CCE*: I2R = 1, state_object = 0x508A1014, data_len = 0Apr 2 23:56:11: FIREWALL sis 65A1C100: Sis extension deletedApr 2 23:56:11: CCE: cce_dp_named_db_inspect_icq_delete_csoblr2-7200b#The debug output details the different states the state machine sees while parsing the Layer 7 ICQ payload.
The sample output from the debug policy-firewall protocol winmsgr command includes information on the IM service. For example, the following lines declare that the type of IM service the user is running is Windows Messenger (WINMSGR):
Apr 3 00:21:46: CCE*: WINMSGR:service found = 2Apr 3 00:21:46: CCE*: WINMSGR: Found IM default serviceThe following is sample output from the debug policy-firewall protocol winmsgr command:
Router# debug policy-firewall protocol winmsgrApr 3 00:21:46: CCE*: I2R = 1, state_object = 0x0, data_len = 0Apr 3 00:21:46: CCE*: WINMSGR protocol found...Apr 3 00:21:46: CCE*: cce_dp_named_db_inspect_winmsgr_create_csoApr 3 00:21:46: CCE*: I2R = 1, state_object = 0x660CF5B4, data_len = 19Apr 3 00:21:46: CCE*: WINMSGR:datalen=19,matchflag=11,matchlen=19Apr 3 00:21:46: CCE*: WINMSGR:Initial trafficfoundApr 3 00:21:46: CCE*: I2R = 0, state_object = 0x660CF5B4, data_len = 19Apr 3 00:21:46: CCE*: WINMSGR:datalen=19,matchflag=11,matchlen=19Apr 3 00:21:46: CCE*: WINMSGR:Initial trafficfoundApr 3 00:21:46: CCE*: I2R = 1, state_object = 0x660CF5B4, data_len = 82Apr 3 00:21:46: CCE*: WINMSGR:datalen=82,matchflag=6,matchlen=4Apr 3 00:21:46: CCE*: WINMSGR:version msg : CVR 31 0x0409 winnt 5.0 i386 MSMSGS 5.1.0701 WindowsMessenger fwuser@example.comApr 3 00:21:46: CCE*: I2R = 0, state_object = 0x660CF5B4, data_len = 96Apr 3 00:21:46: CCE*: WINMSGR:datalen=96,matchflag=6,matchlen=4Apr 3 00:21:46: CCE*: I2R = 1, state_object = 0x660CF5B4, data_len = 33Apr 3 00:21:46: CCE*: WINMSGR:datalen=33,matchflag=12,matchlen=33Apr 3 00:21:46: CCE*: WINMSGR:Initial trafficfoundApr 3 00:21:46: CCE*: I2R = 0, state_object = 0x660CF5B4, data_len = 162Apr 3 00:21:46: CCE*: I2R = 1, state_object = 0x660CF5B4, data_len = 324Apr 3 00:21:46: CCE*: I2R = 0, state_object = 0x660CF5B4, data_len = 37Apr 3 00:21:46: CCE*: WINMSGR:datalen=37,matchflag=12,matchlen=37Apr 3 00:21:46: CCE*: WINMSGR:Initial trafficfoundApr 3 00:21:46: CCE*: I2R = 1, state_object = 0x660CF5B4, data_len = 307Apr 3 00:21:46: CCE*: WINMSGR:datalen=307,matchflag=5,matchlen=118Apr 3 00:21:46: CCE*: WINMSGR:service found = 2Apr 3 00:21:46: CCE*: WINMSGR: Found IM default serviceApr 3 00:21:46: %APPFW-6-IM_WINMSGR_SESSION: im-winmsgr un-recognized service session initiator sends 307 bytes session 192.168.5.3:24601 209.165.200.230:1863 on zone-pair zp_test_in class test_im appl-class test_winmsgr_1Apr 3 00:21:46: CCE*: I2R = 0, state_object = 0x660CF5B4, data_len = 320Apr 3 00:21:46: CCE*: I2R = 0, state_object = 0x660CF5B4, data_len = 332Apr 3 00:21:46: CCE*: WINMSGR:datalen=332,matchflag=5,matchlen=143Apr 3 00:21:46: CCE*: WINMSGR:service found = 2Apr 3 00:21:46: CCE*: WINMSGR: Found IM default serviceApr 3 00:21:46: %APPFW-6-IM_WINMSGR_SESSION: im-winmsgr un-recognized service session initiator gets 332 bytes session 209.165.200.230:1863 192.168.5.3:24601 on zone-pair zp_test_in class test_im appl-class test_winmsgr_1Apr 3 00:23:11: CCE*: I2R = 1, state_object = 0x660CF5B4, data_len = 0Apr 3 00:23:11: FIREWALL sis 65A1D540: Sis extension deletedThe following is sample output from the debug policy-firewall control-plane command:
Router# show debugpolicy_fw:Policy-Firewall control-plane debugging is onvoice-gw-118.03#Syslog logging: enabled (0 messages dropped, 0 messages rate-limited,0 flushes, 0 overruns, xml disabled, filtering disabled)No Active Message Discriminator.No Inactive Message Discriminator.Console logging: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 247 messages logged, xml disabled,filtering disabledLogging Exception size (4096 bytes)Count and timestamp logging messages: disabledPersistent logging: disabledTrap logging: level informational, 44 message lines loggedLog Buffer (60000000 bytes):FIREWALL CP: fw_cp_prot_num_to_name() l4 1, l7 5, gran 0FIREWALL CP: fw_cp_get_flow_policy_and_class() Flow policy does not existFIREWALL CP: fw_cp_check_create_default_l7_policy() Could not retrieve flow policy for L4 policy l4-pmap L4 class l4-cmapFIREWALL CP: fw_classmap_filter_update_in_policymap() Adding filter 0x650187F0 to class l4-cmap in policy l4-pmapFIREWALL CP: fw_policy_action_cmd() PPM create action inspect with params 0x64CAF8E8FIREWALL CP: fw_inspect_class_params() inspect config-plane CLASS-ADD action 0x66315C5C,params 0x64CAF8E8FIREWALL CP: fw_validate_class_for_matchprot() Validating protocols in class l4-cmapFIREWALL CP: fw_validate_class_for_matchprot() protocol filter foundFIREWALL CP: fw_inspect_class_params() Attached config-plane action_params 0x663BD280FIREWALL CP: fw_cp_create_attach_flow_policy()FIREWALL CP: fw_cp_get_string_from_random_num() Random number generated is 2697258553FIREWALL CP: fw_cp_generate_random_string() Allocated random str 2697258553 for policy l4-pmap class l4-cmapFIREWALL CP: fw_cp_get_random_string() Found random string for policy l4-pmap class l4-cmapFIREWALL CP: fw_cp_get_random_string() Found random string for policy l4-pmap class l4-cmapFIREWALL CP: fw_cp_get_random_string() Found random string for policy l4-pmap class l4-cmapFIREWALL CP: fw_cp_prot_num_to_name() l4 2, l7 5, gran 0FIREWALL CP: fw_inspect_int_class_params()FIREWALL CP: fw_create_attach_template_class()FIREWALL CP: fw_create_attach_template_class() Creating template class for trigger 15udp_2697258553 in 15_2697258553FIREWALL CP: fw_create_attach_template_class() Trying to create a PPM filter with id 0x64CA73ECFIREWALL CP: fw_cp_prot_num_to_name() l4 4, l7 5, gran 0FIREWALL CP: fw_inspect_int_class_params()FIREWALL CP: fw_create_attach_template_class()FIREWALL CP: fw_create_attach_template_class() Creating template class for trigger 15icmp_2697258553 in 15_2697258553FIREWALL CP: fw_create_attach_template_class() Trying to create a PPM filter with id 0x64CA73ECFIREWALL CP: fw_cp_create_attach_vtcp_classes() Create policy 15FIREWALL CP: fw_cp_create_tcp_15()FIREWALL CP: fw_cp_vtcp_support_get_tcp_init_class() Creating TCP Class with Pure SYN filterFIREWALL CP: fw_inspect_int_class_params()FIREWALL CP: fw_create_attach_template_class()FIREWALL CP: fw_create_attach_template_class() Creating template class for trigger 15tcp_2697258553 in 15_2697258553FIREWALL CP: fw_create_attach_template_class() Trying to create a PPM filter with id 0x64CA73A4FIREWALL CP: fw_cp_create_attach_flow_policy() Success-creating flow policyFIREWALL CP: fw_cp_create_attach_flow_policy() Attach flow policy to trigger class as child policyFIREWALL CP: fw_cp_create_attach_flow_policy() Success- Attached flow policy to trigger classFIREWALL CP: fw_cp_create_attach_flow_policy() Creating P20 & P21 for vtcpFIREWALL CP: fw_cp_generate_random_string() Found random string for policy l4-pmap class l4-cmapFIREWALL CP: fw_cp_get_flow_policy_and_class() Found flow policy 0x64FFC838FIREWALL CP: fw_cp_get_random_string() Found random string for policy l4-pmap class l4-cmapFIREWALL CP: fw_cp_get_random_string() Found random string for policy l4-pmap class l4-cmapFIREWALL CP: fw_cp_get_flow_policy_and_class() Found flow TCP 0x6585718C and UDP 0x645D1794 classesFIREWALL CP: fw_cp_check_create_default_l7_class() Checking the class l4-cmapFIREWALL CP: fw_reverse_policy_handle_zp_event()FIREWALL CP: fw_reverse_policy_handle_zp_event() Reverse_policy Zone pair add eventFIREWALL CP: fw_get_ppm_policy_on_zp() Did not find ppm policy on zp zp p_type 0x7FIREWALL CP: fw_get_name_type_and_client_of_first_class_in_policy()FIREWALL CP: fw_create_cp_dynamic_class()FIREWALL CP: fw_create_cp_dynamic_class() Trying to create a PPM filter with id 0x10000000FIREWALL CP: fw_create_cp_dynamic_class() SuccessFIREWALL CP: fw_drop_class_params() action 0x6637A5C0, cmd_params 0x64CA7550, event 0x21FIREWALL CP: fw_create_noop_feature_object()FIREWALL CP: fw_create_inspect_feature_object()FIREWALL CP: fw_create_fo_internal() Create FO for class 0xC0000002 target_class 0xA0000000 action CCE_INSPECT_CONFIGUREDFIREWALL CP: fw_cp_get_inspect_params()FIREWALL CP: fw_cp_get_inspect_params() Creating the FO with default parametersFIREWALL CP: fw_create_fo_internal() Created FO with id 0xAAAA0006 action CCE_INSPECT_CONFIGUREDFIREWALL CP: fw_cp_store_fo_id() Enqueue 0xAAAA0006 to fo_param_listFIREWALL CP: fw_create_noop_feature_object()FIREWALL CP: fw_create_inspect_int_feature_object()FIREWALL CP: fw_create_fo_internal() Create FO for class 0xC0000005 target_class 0xA0000000 action CCE_INSPECTFIREWALL CP: fw_cp_get_inspect_params()FIREWALL CP: fw_cp_get_inspect_params() Creating the FO with default parametersFIREWALL CP: fw_create_fo_internal() Created FO with id 0xAAAA0007 action CCE_INSPECTFIREWALL CP: fw_cp_store_fo_id() Enqueue 0xAAAA0007 to fo_param_listFIREWALL CP: fw_create_noop_feature_object()FIREWALL CP: fw_create_inspect_int_feature_object()FIREWALL CP: fw_create_fo_internal() Create FO for class 0xC0000007 target_class 0xA0000000 action CCE_INSPECTFIREWALL CP: fw_cp_get_inspect_params()FIREWALL CP: fw_cp_get_inspect_params() Creating the FO with default parametersFIREWALL CP: fw_create_fo_internal() Created FO with id 0xAAAA0008 action CCE_INSPECTFIREWALL CP: fw_cp_store_fo_id() Enqueue 0xAAAA0008 to fo_param_listFIREWALL CP: fw_create_noop_feature_object()FIREWALL CP: fw_create_inspect_int_feature_object()FIREWALL CP: fw_create_fo_internal() Create FO for class 0xC0000009 target_class 0xA0000000 action CCE_INSPECTFIREWALL CP: fw_cp_get_inspect_params()FIREWALL CP: fw_cp_get_inspect_params() Creating the FO with default parametersFIREWALL CP: fw_create_fo_internal() Created FO with id 0xAAAA0009 action CCE_INSPECTFIREWALL CP: fw_cp_store_fo_id() Enqueue 0xAAAA0009 to fo_param_listFIREWALL CP: fw_create_drop_feature_object()FIREWALL CP: fw_create_fo_internal() Create FO for class 0xC0000003 target_class 0xA0000000 action CCE_FW_DROPFIREWALL CP: fw_create_fo_internal() Created FO with id 0xAAAA000A action CCE_FW_DROPFIREWALL CP: fw_create_internal_reverse_policy()FIREWALL CP: fw_create_ppm_reverse_policy()FIREWALL CP: fw_get_name_type_and_client_of_first_class_in_policy()FIREWALL CP: fw_create_cp_dynamic_class()FIREWALL CP: fw_create_noop_feature_object()FIREWALL CP: fw_create_noop_feature_object()%SYS-5-CONFIG_I: Configured from console by consoleFIREWALL CP: fw_cp_prot_num_to_name() l4 1, l7 5, gran 0FIREWALL CP: fw_drop_class_params() action 0x6637A5C0, cmd_params 0x00000000, event 0x40FIREWALL CP: fw_get_ppm_policy_on_zp() Found ppm policy l4-pmap on zp zp p_type 0x7The following is sample output from the debug policy-firewall L2-transparent command:
Router# debug policy-firewall L2-transparent*Apr 4 08:28:23.554: L2FW*:insp_l2_fast_inspection: pak 673DBD90, input-interface FastEthernet1/1, output-interface FastEthernet1/0*Apr 4 08:28:23.554: L2FW*:Src 17.3.39.1 dst 17.3.39.3 protocol tcp*Apr 4 08:28:23.554: TBAP: Check AuthProxy is configured on idb=FastEthernet1/1 path=1 linktype=38*Apr 4 08:28:23.554: L2FW:Input ACL not configured or the ACL is bypassed*Apr 4 08:28:23.554: L2FW:Output ACL is not configured or ACL is bypassed*Apr 4 08:28:23.554: L2FW*:IP inspect firewall is not cfged on input or output interface.PASS*Apr 4 08:28:23.554: L2FW* 2:insp_l2_fast_inspection: pak 673DBD90, input-interface FastEthernet1/1, output-interface FastEthernet1/0*Apr 4 08:28:23.554: CCE L2 FW*Apr 4 08:28:23.554: L2FW* -3:insp_l2_fast_inspection: pak 673DBD90, input-interface FastEthernet1/1, output-interface FastEthernet1/0The following is sample output from the debug policy-firewall detailed command:
Router# debug policy-firewall detailedLog Buffer (600000 bytes):Feb 13 08:40:01: FIREWALL: ret_val 0 is not FW_DP_INSP_PASS_PAK<snip>Feb 13 08:41:22: FIREWALL: ret_val 0 is not FW_DP_INSP_PASS_PAKFeb 13 08:41:24: FIREWALL: ret_val 0 is not FW_DP_INSP_PASS_PAKFeb 13 08:41:25: FIREWALL*: Searching for FSO in class 0x50793C20class group 0x10000000,target 0x1, cce class type 0x2BFeb 13 08:41:25: FIREWALL*: not foundFeb 13 08:41:25: FIREWALL*: Try to create session in fastpathFeb 13 08:41:25: FIREWALL: Searching for FSO in class 0x50793C20class group 0x10000000,target 0x1, cce class type 0x2BFeb 13 08:41:25: FIREWALL: not foundFeb 13 08:41:25: FIREWALL: Create FSOFeb 13 08:41:25: FIREWALL: sis 204925C0 : fw_dp_state_object_linkFeb 13 08:41:25: FIREWALL: sis 204925C0 : FO class 0x50793C20 class group 0x10000000, target 0x1, FO 0x20255D80Feb 13 08:41:25: FIREWALL: sis 204925C0 : alert = 1, audit_trail = 0Feb 13 08:41:25: FIREWALL: sis 204925C0 : l7 protocol 62, granular = 5Feb 13 08:41:25: FIREWALL: sis 204925C0 : fw_dp_state_object_attach_forwardFeb 13 08:41:25: FIREWALL: sis 204925C0 : fw_dp_state_object_create_and_attach_reverseFeb 13 08:41:25: FIREWALL: sis 204925C0 : FSO bind success for reverse class 0x50793C80class group 0x10000000, target 0x1Feb 13 08:41:25: FIREWALL: sis 204925C0 :Session Info :Feb 13 08:41:25: session->fwfo 0x507E39C0Feb 13 08:41:25: class type 0x2B, target 0x1, policy id 0x10000000, class id 0x50793C20Feb 13 08:41:25: class type 0x2B, reverse target 0x1, reverse policy id 0x10000000, reverse class id 0x50793C80Feb 13 08:41:25: src addr 192.168.3.3, port 36091, vrf id 0Feb 13 08:41:25: dst addr 192.168.103.3, port 5190, vrf id 0Feb 13 08:41:25: L4 Protocol : TCPFeb 13 08:41:25: FIREWALL: sis 204925C0 : L4 inspection returned 3Feb 13 08:41:25: FIREWALL*: FSO feature object 0x204925C0 foundFeb 13 08:41:25: FIREWALL*: sis 204925C0 : L4 inspection returned 3Feb 13 08:41:25: FIREWALL*: FSO feature object 0x204925C0 foundFeb 13 08:41:25: FIREWALL*: sis 204925C0 : max_sessions 2147483647; current sessions 0Feb 13 08:41:25: FIREWALL*: sis 204925C0 : IM : Token set for L7 named-dbFeb 13 08:41:25: FIREWALL*: sis 204925C0 : cce_sb 0x66A5BA00, pak 0x50028974, data_len 0 in_fast_path 1, dir = 1Feb 13 08:41:25: FIREWALL*: sis 204925C0 : p_app_data = C174268, p_data_len = 6p_offset = 0Feb 13 08:41:25: FIREWALL*: sis 204925C0 : Found particle offset token, data1 = 0Feb 13 08:41:25: FIREWALL*: sis 204925C0 : Opening 0 channels for icqFeb 13 08:41:25: FIREWALL*: sis 204925C0 : icq L7 inspect result: PASS packetFeb 13 08:41:25: FIREWALL*: sis 204925C0 : L4 inspection returned 3Feb 13 08:41:25: FIREWALL*: FSO feature object 0x204925C0 foundFeb 13 08:41:25: FIREWALL*: sis 204925C0 : cce_sb 0x66A5BA00, pak 0x5004CAC8, data_len 10 in_fast_path 1, dir = 2Feb 13 08:41:25: FIREWALL*: sis 204925C0 : p_app_data = C210848, p_data_len = Ap_offset = 0Feb 13 08:41:25: FIREWALL*: sis 204925C0 : Found particle offset token, data1 = 0Feb 13 08:41:25: FIREWALL*: sis 204925C0 : Opening 0 channels for icqFeb 13 08:41:25: FIREWALL*: sis 204925C0 : icq L7 inspect result: PASS packetFeb 13 08:41:25: FIREWALL*: sis 204925C0 : L4 inspection returned 3Feb 13 08:41:25: FIREWALL*: FSO feature object 0x204925C0 foundFeb 13 08:41:25: FIREWALL*: sis 204925C0 : cce_sb 0x66A5BA00, pak 0x50028974, data_len 270 in_fast_path 1, dir = 1debug pots
To display information on the telephone interfaces, use the debug pots command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug pots {driver | csm} [1 | 2]
no debug pots {driver | csm} [1 | 2]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
The debug pots command displays driver and CSM debug information for telephone ports 1 and 2.
Examples
The following is sample output from the debug pots driver 1 command. This sample display indicates that the telephone port driver is not receiving caller ID information from the ISDN line. Therefore, the analog caller ID device attached to the telephone port does not display caller ID information.
Router# debug pots driver 100:01:51:POTS DRIVER port=1 activate ringer: cadence=0 callerId=Unknown00:01:51:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT00:01:51:POTS DRIVER port=1 enter_ringing00:01:51:POTS DRIVER port=1 cmd=1900:01:51:POTS DRIVER port=1 activate disconnect00:01:51:POTS DRIVER port=1 state=Ringing drv_event=DISCONNECT_EVENT00:01:51:POTS DRIVER port=1 cmd=1A00:01:51:POTS DRIVER port=1 enter_idle00:01:51:POTS DRIVER port=1 ts connect: 0 000:01:51:POTS DRIVER port=1 cmd=D00:01:51:POTS DRIVER port=1 report onhook00:01:51:POTS DRIVER port=1 activate tone=SILENCE_TONE00:01:51:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT00:01:51:POTS DRIVER port=1 activate tone=SILENCE_TONE00:01:51:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT00:01:53:POTS DRIVER port=1 activate ringer: cadence=0 callerId=Unknown00:01:53:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT00:01:53:POTS DRIVER port=1 enter_ringing00:01:53:POTS DRIVER port=1 cmd=1900:01:55:POTS DRIVER port=1 cmd=1A00:02:49:POTS DRIVER port=1 state=Ringing drv_event=OFFHOOK_EVENT00:02:49:POTS DRIVER port=1 cmd=1A00:02:49:POTS DRIVER port=1 enter_suspend00:02:49:POTS DRIVER port=1 cmd=A00:02:49:POTS DRIVER port=1 report offhook00:02:49:POTS DRIVER port=1 activate connect: endpt=1 calltype=TWO_PARTY_CALL00:02:49:POTS DRIVER port=1 state=Suspend drv_event=CONNECT_EVENT00:02:49:POTS DRIVER port=1 enter_connect: endpt=1 calltype=000:02:49:POTS DRIVER port=1 cmd=A00:02:49:POTS DRIVER port=1 ts connect: 1 000:02:49:POTS DRIVER port=1 activate connect: endpt=1 calltype=TWO_PARTY_CALL00:02:49:POTS DRIVER port=1 state=Connect drv_event=CONNECT_EVENT00:02:49:POTS DRIVER port=1 enter_connect: endpt=1 calltype=000:02:49:POTS DRIVER port=1 cmd=A00:02:49:POTS DRIVER port=1 ts connect: 1 000:02:55:POTS DRIVER port=1 state=Connect drv_event=ONHOOK_EVENT00:02:55:POTS DRIVER port=1 enter_idle00:02:55:POTS DRIVER port=1 ts connect: 0 000:02:55:POTS DRIVER port=1 cmd=D00:02:55:POTS DRIVER port=1 report onhook00:02:55:POTS DRIVER port=1 activate tone=SILENCE_TONE00:02:55:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT00:02:55:POTS DRIVER port=1 activate tone=SILENCE_TONE00:02:55:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENTThe following is sample output from the debug pots csm 1 command. This sample display indicates that a dial peer contains an invalid destination pattern (555-1111).
Router# debug pots csm 101:57:28:EVENT_FROM_ISDN:dchanidb=0x66CB38, call_id=0x11, ces=0x2 bchan=0x0, event=0x1, cause=0x001:57:28:Dial peer not found, route call to port 101:57:28:CSM_PROC_IDLE:CSM_EVENT_ISDN_CALL, call_id=0x11, port=101:57:28:Calling number `5551111'01:57:40:CSM_PROC_RINGING:CSM_EVENT_VDEV_OFFHOOK, call_id=0x11, port=101:57:40:EVENT_FROM_ISDN:dchan_idb=0x66CB38, call_id=0x11, ces=0x2 bchan=0x0, event=0x4, cause=0x001:57:40:CSM_PROC_CONNECTING:CSM_EVENT_ISDN_CONNECTED, call_id=0x11, port=101:57:47:CSM_PROC_CONNECTING:CSM_EVENT_VDEV_ONHOOK, call_id=0x11, port=101:57:201863503872: %ISDN-6-DISCONNECT:Interface BRI0:1 disconnected from unknown, call lasted 5485 seconds01:57:47: %ISDN-6-DISCONNECT:Interface BRI0:1 disconnected from unknown, call lasted 5485 seconds01:57:47:EVENT_FROM_ISDN:dchan _idb=0x66CB38, call_id=0x11, ces=0x2 bchan=0xFFFFFFFF, event=0x0, cause=0x101:57:47:CSM_PROC_NEAR_END_DISCONNECT:CSM_debug pots csm
To activate events from which an application can determine and display the status and progress of calls to and from plain old telephone service (POTS) ports, use the debug pots csm command in privileged EXEC mode.
debug pots csm
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
To see debugging messages, enter the logging console global configuration mode command as follows:
Router(config)# logging consoleRouter(config)# exitDebugging messages are displayed in one of two formats that are relevant to the POTS dial feature:
hh:mm:ss: CSM_STATE: CSM_EVENT, call id = ??, port = ?or
hh:mm:ss: EVENT_FROM_ISDN:dchan_idb=0x???????, call_id=0x????, ces=? bchan=0x????????, event=0x?, cause=0x??Table 275 describes the significant fields shown in the display.
Table 275 debug pots csm Field Descriptions
hh:mm:ss
Timestamp (in hours, minutes, and seconds).
CSM_STATE
One of the call CSM states listed in Table 276.
CSM_EVENT
One of the CSM events listed in Table 277.
call id
Hexadecimal value from 0x00 to 0xFF.
port
Telephone port 1 or 2.
EVENT_FROM_ISDN
A CSM event. Table 277 shows a list of CSM events.
dchan_idb
Internal data structure address.
ces
Connection end point suffix used by ISDN.
bchan
Channel used by the call. A value of 0xFFFFFFFF indicates that a channel is not assigned.
event
A hexadecimal value that is translated into a CSM event. Table 278 shows a list of events and the corresponding CSM events.
cause
A hexadecimal value that is given to call-progressing events. Table 279 shows a list of cause values and definitions.
Table 276 shows the values for CSM states.
Table 277 shows the values for CSM events.
