|
|
Table Of Contents
debug resource policy notification
debug resource policy registration
debug redundancy as5850
To enable specific redundancy-related debug options, use the debug redundancy as5850 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug redundancy as5850 {fsm | lines | master | mode | rf-client}
no debug redundancy as5850
Syntax Description
Defaults
This command is disabled
Command Modes
Privileged EXEC
Command History
12.2(2)XB1
This command was introduced.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
Use the master form of the command to view redundancy-related debug entries. All debug entries continue to be logged even if you do not specify an option here, and you can always use the show redundancy debug-log command to view them.
Examples
The output from this command consists of event announcements that can be used by authorized troubleshooting personnel.
Related Commands
debug resource policy notification
To trace the Embedded Resource Manager (ERM) notification activities for resources using the ERM feature, use the debug resource policy notification command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug resource policy notification [owner resource-owner-name]
no debug resource policy notification [owner resource-owner-name]
Syntax Description
Command Default
Disabled
Command Modes
Privileged EXEC
Command History
Examples
The following example shows different instances of the debug resource policy notification command:
Router# debug resource policy notificationEnabled notif. debugs on all ownersWhen a threshold is violated, the following messages are displayed:
*Mar 3 09:50:44.081: Owner: 'memory' initiated a notification:*Mar 3 09:50:44.081: %SYS-4-RESMEMEXCEED: Resource user usrr1 has exceeded the Major memory thresholdPool: Processor Used: 42932864 Threshold :42932860*Mar 3 09:50:46.081: Notification from Owner: 'memory' is dispatched for User: 'usrr1' (ID: 0x10000B9)*Mar 3 09:50:46.081: %SYS-4-RESMEMEXCEED: Resource user usrr1 has exceeded the Major memory thresholdPool: Processor Used: 42932864 Threshold :42932860Router# no debug resource manager notificationDisabled notif. debugs on all ownersRouter# debug resource manager notification owner cpuEnabled notif. debugs on owner 'cpu'Router# no debug resource manager notification owner cpuDisabled notif. debugs on owner 'cpu'Router# debug resource manager notification owner memoryEnabled notif. debugs on owner 'memory'Router# no debug resource manager notification owner memoryDisabled notif. debugs on owner 'memory'Router# debug resource manager notification owner BufferEnabled notif. debugs on owner 'Buffer'Router# no debug resource manager notification owner BufferDisabled notif. debugs on owner 'Buffer'Router# no debug resource manager notification owner BufferDisabled notif. debugs on owner 'Buffer'Related Commands
debug resource policy registration
Displays the resource policy registration debug information for the ERM resources.
debug resource policy registration
To trace the Embedded Resource Manager (ERM) registration activities for resources using the ERM feature, use the debug resource policy registration command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug resource policy registration
no debug resource policy registration
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
Privileged EXEC
Command History
Examples
The following example shows output from the debug resource policy registration command:
Router# debug resource policy registrationRegistrations debugging is onWhen an RU is created, the following message is displayed:
*Mar 3 09:35:58.304: resource_user_register: RU: ruID: 0x10000B8, rutID: 0x1, rg_ID: 0x0 name: usrr1When an RU is deleted, the following message is displayed:
*Mar 3 09:41:09.500: resource_user_unregister: RU: ruID: 0x10000B8, rutID: 0x1, rg_ID: 0x0 name: usrr1Related Commands
debug resource policy notification
Displays the resource policy notification debug information for the ERM resources.
debug resource-pool
To see and trace resource pool management activity, use the debug resource-pool command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug resource-pool
no debug resource-pool
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Enter the debug resource-pool command to see and trace resource pool management activity. Table 279 describes the resource pooling states.
You can use the resource pool state to isolate problems. For example, if a call fails authorization in the RM_RES_AUTHOR state, investigate further with AAA authorization debugs to determine whether the problem lies in the resource-pool manager, AAA, or dispatcher.
Examples
The following example shows different instances where you can use the debug resource-pool command:
Router# debug resource-poolRM general debugging is onRouter# show debugGeneral OS:AAA Authorization debugging is onResource Pool:resource-pool general debugging is onRouter #Router #ping 21.1.1.10Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 21.1.1.10, timeout is 2 seconds:*Jan 8 00:10:30.358: RM state:RM_IDLE event:DIALER_INCALL DS0:0:0:0:1*Jan 8 00:10:30.358: RM: event incoming call/* An incoming call is received by RM */*Jan 8 00:10:30.358: RM state:RM_DNIS_AUTHOR event:RM_DNIS_RPM_REQUESTDS0:0:0:0:1/* Receives an event notifying to proceed with RPM authorization whilein DNIS authorization state */*Jan 8 00:10:30.358: RM:RPM event incoming call*Jan 8 00:10:30.358: RPM profile cp1 found/* A customer profile "cp1" is found matching for the incoming call, inthe local database */*Jan 8 00:10:30.358: RM state:RM_RPM_RES_AUTHORevent:RM_RPM_RES_AUTHOR_SUCCESS DS0:0:0:0:1/* Resource authorization success event received while in resourceauthorization state*/*Jan 8 00:10:30.358: Allocated resource from res_group isdn1*Jan 8 00:10:30.358: RM:RPM profile "cp1", allocated resource "isdn1"successfully*Jan 8 00:10:30.358: RM state:RM_RPM_RES_ALLOCATINGevent:RM_RPM_RES_ALLOC_SUCCESS DS0:0:0:0:1/* Resource allocation sucess event received while attempting toallocate a resource */*Jan 8 00:10:30.358: Se0:1 AAA/ACCT/RM: doing resource-allocated(local) (nothing to do)*Jan 8 00:10:30.366: %LINK-3-UPDOWN: Interface Serial0:1, changed stateto up*Jan 8 00:10:30.370: %LINK-3-UPDOWN: Interface Serial0:1, changed stateto down*Jan 8 00:10:30.570: Se0:1 AAA/ACCT/RM: doing resource-update (local)cp1 (nothing to do)*Jan 8 00:10:30.578: %LINK-3-UPDOWN: I.nterface Serial0:0, changedstate to up*Jan 8 00:10:30.582: %DIALER-6-BIND: Interface Serial0:0 bound toprofile Dialer0...Success rate is 0 percent (0/5)Router #*Jan 8 00:10:36.662: %ISDN-6-CONNECT: Interface Serial0:0 is nowconnected to 71017*Jan 8 00:10:52.990: %DIALER-6-UNBIND: Interface Serial0:0 unbound fromprofile Dialer0*Jan 8 00:10:52.990: %ISDN-6-DISCONNECT: Interface Serial0:0disconnected from 71017 , call lasted 22 seconds*Jan 8 00:10:53.206: %LINK-3-UPDOWN: Interface Serial0:0, changed stateto down*Jan 8 00:10:53.206: %ISDN-6-DISCONNECT: Interface Serial0:1disconnected from unknown , call lasted 22 seconds*Jan 8 00:10:53.626: RM state:RM_RPM_RES_ALLOCATED event:DIALER_DISCONDS0:0:0:0:1/* Received Disconnect event from signalling stack for a call whichhas a resource allocated. */*Jan 8 00:10:53.626: RM:RPM event call drop/* RM processing the disconnect event */*Jan 8 00:10:53.626: Deallocated resource from res_group isdn1*Jan 8 00:10:53.626: RM state:RM_RPM_DISCONNECTINGevent:RM_RPM_DISC_ACK DS0:0:0:0:1/* An intermediate state while the DISCONNECT event is being processedby external servers, before RM goes back into IDLE state.*/Table 280 describes the significant fields shown in the display.
debug rif
To display information on entries entering and leaving the routing information field (RIF) cache, use the debug rif command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rif
no debug rif
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
In order to use the debug rif command to display traffic source-routed through an interface, fast switching of source route bridging (SRB) frames must first be disabled with the no source-bridge route-cache interface configuration command.
Examples
The following is sample output from the debug rif command:
The first line of output is an example of a RIF entry for an interface configured for SDLC Logical Link Control (SDLLC) or Local-Ack. Table 281 describes significant fields shown in the display.
The following line of output is an example of a RIF entry for an interface that is not configured for SDLLC or Local-Ack:
RIF: U chk da=0000.3080.4aed,sa=0000.0000.0000 [] type 8 on TokenRing0/0Notice that the source address contains only zero values (0000.0000.0000), and that the RIF string is null ([ ]). The last element in the entry indicates that this route was learned from a virtual ring, rather than a real Token Ring port.
The following line shows that a new entry has been added to the RIF cache:
RIF: U add 1000.5a59.04f9 [4880.3201.00A1.0050] type 8The following line shows that a RIF cache lookup operation has taken place:
RIF: L checking da=0000.3080.4aed, sa=0000.0000.0000The following line shows that a TEST response from address 9000.5a59.04f9 was inserted into the RIF cache:
RIF: rcvd TEST response from 9000.5a59.04f9The following line shows that the RIF entry for this route has been found and updated:
RIF: U upd da=1000.5a59.04f9,sa=0110.2222.33c1 [4880.3201.00A1.0050]The following line shows that an XID response from this address was inserted into the RIF cache:
RIF: rcvd XID response from 9000.5a59.04f9The following line shows that the router sent an XID response to this address:
SR1: sent XID response to 9000.5a59.04f9Table 282 explains the other possible lines of debug rif command output.
Related Commands
debug list
Filters debugging information on a per-interface or per-access list basis.
debug route-map ipc
To display a summary of the one-way Inter-process Communications (IPC) messages set from the route processor (RP) to the Versatile Interface Processor (VIP) about NetFlow policy routing when distributed Cisco Express Forwarding (dCEF) is enabled, use the debug route-map ipc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug route-map ipc
no debug route-map ipc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is especially helpful for policy routing with dCEF switching.
This command displays a summary of one-way IPC messages from the RP to the VIP about NetFlow policy routing. If you execute this command on the RP, the messages are shown as "Sent." If you execute this command on the VIP console, the IPC messages are shown as "Received."
Examples
The following is sample output from the debug route-map ipc command executed at the RP:
Router# debug route-map ipcRoutemap related IPC debugging is onRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# ip cef distributedRouter(config)#^ZRouter#RM-IPC: Clean routemap config in slot 0RM-IPC: Sent clean-all-routemaps; len 12RM-IPC: Download all policy-routing related routemap config to slot 0RM-IPC: Sent add routemap test(seq:10); n_len 5; len 17RM-IPC: Sent add acl 1 of routemap test(seq:10); len 21RM-IPC: Sent add min 10 max 300 of routemap test(seq:10); len 24RM-IPC: Sent add preced 1 of routemap test(seq:10); len 17RM-IPC: Sent add tos 4 of routemap test(seq:10); len 17RM-IPC: Sent add nexthop 50.0.0.8 of routemap test(seq:10); len 20RM-IPC: Sent add default nexthop 50.0.0.9 of routemap test(seq:10); len 20RM-IPC: Sent add interface Ethernet0/0/3(5) of routemap test(seq:10); len 20RM-IPC: Sent add default interface Ethernet0/0/2(4) of routemap test(seq:10); len 20The following is sample output from the debug route-map ipc command executed at the VIP:
VIP-Slot0# debug route-map ipcRoutemap related IPC debugging is onVIP-Slot0#RM-IPC: Rcvd clean-all-routemaps; len 12RM-IPC: Rcvd add routemap test(seq:10); n_len 5; len 17RM-IPC: Rcvd add acl 1 of routemap test(seq:10); len 21RM-IPC: Rcvd add min 10 max 300 of routemap test(seq:10); len 24RM-IPC: Rcvd add preced 1 of routemap test(seq:10); len 17RM-IPC: Rcvd add tos 4 of routemap test(seq:10); len 17RP-IPC: Rcvd add nexthop 50.0.0.8 of routemap test(seq:10); len 20RP-IPC: Rcvd add default nexthop 50.0.0.9 of routemap test(seq:10); len 20RM-IPC: Rcvd add interface Ethernet0/3 of routemap tes; len 20RM-IPC: Rcvd add default interface Ethernet0/2 of routemap test(seq:10); len 20debug rpms-proc preauth
To enable diagnostic reporting of preauthentication information, use the debug rpms-proc preauth command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rpms-proc preauth {all | h323 | sip}
no debug rpms-proc preauth {all | h323 | sip}
Syntax Description
all
Provides information for all calls.
h323
Provides information for H.323 calls.
sip
Provides information for Session Initiation Protocol (SIP) calls.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example shows debugging output for two calls. The first is a leg 3 SIP call, and the second is a leg 3 H.323 call:
Router# debug rpms-proc preauth allAll RPMS Process preauth tracing is enabledFeb 10 14:00:07.236: Entering rpms_proc_print_preauth_reqFeb 10 14:00:07.236: Request = 0Feb 10 14:00:07.236: Preauth id = 8Feb 10 14:00:07.236: EndPt Type = 1Feb 10 14:00:07.236: EndPt = 192.168.80.70Feb 10 14:00:07.236: Resource Service = 1Feb 10 14:00:07.236: Call_origin = answerFeb 10 14:00:07.236: Call_type = voipFeb 10 14:00:07.236: Calling_num = 2220001Feb 10 14:00:07.236: Called_num = 1120001Feb 10 14:00:07.236: Protocol = 1Feb 10 14:00:07.236:rpms_proc_create_node:Created node with preauth_id = 8Feb 10 14:00:07.236:rpms_proc_send_aaa_req:uid got is 19Feb 10 14:00:07.240:rpms_proc_preauth_response:Context is for preauth_id 8, aaa_uid 19Feb 10 14:00:07.240:rpms_proc_preauth_response:Deleting Tree node for preauth id 8 uid 19Feb 10 14:00:07.284: Entering rpms_proc_print_preauth_reqFeb 10 14:00:07.284: Request = 0Feb 10 14:00:07.284: Preauth id = 9Feb 10 14:00:07.284: EndPt Type = 1Feb 10 14:00:07.284: EndPt = 192.168.81.102Feb 10 14:00:07.284: Resource Service = 1Feb 10 14:00:07.284: Call_origin = answerFeb 10 14:00:07.284: Call_type = voipFeb 10 14:00:07.284: Calling_num = 2210001Feb 10 14:00:07.284: Called_num = 1#1110001Feb 10 14:00:07.284: Protocol = 0Feb 10 14:00:07.288:rpms_proc_create_node:Created node with preauth_id = 9Feb 10 14:00:07.288:rpms_proc_send_aaa_req:uid got is 21Feb 10 14:00:07.300:rpms_proc_preauth_response:Context is for preauth_id 9, aaa_uid 21Feb 10 14:00:07.300:rpms_proc_preauth_response:Deleting Tree node for preauth id 9 uid 21The following example shows the output for a single leg 3 H.323 call:
Router# debug rpms-proc preauth h323RPMS Process H323 preauth tracing is enabledFeb 10 14:04:57.867: Entering rpms_proc_print_preauth_reqFeb 10 14:04:57.867: Request = 0Feb 10 14:04:57.867: Preauth id = 10Feb 10 14:04:57.867: EndPt Type = 1Feb 10 14:04:57.867: EndPt = 192.168.81.102Feb 10 14:04:57.867: Resource Service = 1Feb 10 14:04:57.867: Call_origin = answerFeb 10 14:04:57.867: Call_type = voipFeb 10 14:04:57.867: Calling_num = 2210001Feb 10 14:04:57.867: Called_num = 1#1110001Feb 10 14:04:57.867: Protocol = 0Feb 10 14:04:57.867:rpms_proc_create_node:Created node with preauth_id = 10Feb 10 14:04:57.867:rpms_proc_send_aaa_req:uid got is 25Feb 10 14:04:57.875:rpms_proc_preauth_response:Context is for preauth_id 10, aaa_uid 25Feb 10 14:04:57.875:rpms_proc_preauth_response:Deleting Tree node for preauth id 10 uid 25The following example shows output for a single leg 3 SIP call:
Router# debug rpms-proc preauth sipRPMS Process SIP preauth tracing is enabledFeb 10 14:08:02.880: Entering rpms_proc_print_preauth_reqFeb 10 14:08:02.880: Request = 0Feb 10 14:08:02.880: Preauth id = 11Feb 10 14:08:02.880: EndPt Type = 1Feb 10 14:08:02.880: EndPt = 192.168.80.70Feb 10 14:08:02.880: Resource Service = 1Feb 10 14:08:02.880: Call_origin = answerFeb 10 14:08:02.880: Call_type = voipFeb 10 14:08:02.880: Calling_num = 2220001Feb 10 14:08:02.880: Called_num = 1120001Feb 10 14:08:02.880: Protocol = 1Feb 10 14:08:02.880:rpms_proc_create_node:Created node with preauth_id = 11Feb 10 14:08:02.880:rpms_proc_send_aaa_req:uid got is 28Feb 10 14:08:02.888:rpms_proc_preauth_response:Context is for preauth_id 11, aaa_uid 28Feb 10 14:08:02.888:rpms_proc_preauth_response:Deleting Tree node for preauth id 11 uid 28Table 283 describes the significant fields shown in the display.
debug rtpspi all
To debug all Routing Table Protocol (RTP) security parameter index (SPI) errors, sessions, and in/out functions, use the debug rtpspi all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtpspi all
no debug rtpspi all
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620).
Usage Guidelines
CautionBe careful when you use this command because it can result in console flooding and reduced voice quality.
Examples
The following example shows a debug trace for RTP SPI errors, sessions, and in/out functions on a gateway:
Router# debug rtpspi allRTP SPI Error, Session and function in/out tracings are enabled.*Mar 1 00:38:59.381:rtpspi_allocate_rtp_port:Entered.*Mar 1 00:38:59.381:rtpspi_allocate_rtp_port:allocated RTP port 16544*Mar 1 00:38:59.381:rtpspi_allocate_rtp_port:Success. port = 16544. Leaving.*Mar 1 00:38:59.381:rtpspi_call_setup_request:entered.Call Id = 5, dest = 0.0.0.0; callInfo:final dest flag = 0,rtp_session_mode = 0x2,local_ip_addrs = 0x5000001,remote_ip_addrs = 0x0,local rtp port = 16544, remote rtp port = 0*Mar 1 00:38:59.381:rtpspi_call_setup_request:spi_info copied for rtpspi_app_data_t.*Mar 1 00:38:59.385:rtpspi_call_setup_request:leaving*Mar 1 00:38:59.385:rtpspi_call_setup() entered*Mar 1 00:38:59.385:rtpspi_initialize_ccb:Entered*Mar 1 00:38:59.385:rtpspi_initialize_ccb:leaving*Mar 1 00:38:59.385:rtpspi_call_setup:rtp_session_mode = 0x2*Mar 1 00:38:59.385:rtpspi_call_setup:mode = CC_CALL_NORMAL.destianation number = 0.0.0.0*Mar 1 00:38:59.385:rtpspi_call_setup:Passed local_ip_addrs=0x5000001*Mar 1 00:38:59.385:rtpspi_call_setup:Passed local_rtp_port = 16544*Mar 1 00:38:59.385:rtpspi_call_setup:Saved RTCP Session = 0x1AF57E0*Mar 1 00:38:59.385:rtpspi_call_setup:Passed remote rtp port = 0.*Mar 1 00:38:59.389:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=0, rem ip=0x0*Mar 1 00:38:59.389:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:38:59.389:rtpspi_start_rtcp_session:Starting RTCP session.Local IP addr = 0x5000001, Remote IP addr = 0x0,Local RTP port = 16544, Remote RTP port = 0, mode = 0x2*Mar 1 00:38:59.389:rtpspi_start_rtcp_session:RTP Session creation Success.*Mar 1 00:38:59.389:rtpspi_call_setup:RTP Session creation Success.*Mar 1 00:38:59.389:rtpspi_call_setup:calling cc_api_call_connected()*Mar 1 00:38:59.389:rtpspi_call_setup:Leaving.*Mar 1 00:38:59.393:rtpspi_bridge:entered. conf id = 1, src i/f = 0x1859E88,dest i/f = 0x1964EEC, src call id = 5, dest call id = 4call info = 0x1919140, xmit fn = 0xDA7494, tag = 0*Mar 1 00:38:59.393:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:38:59.393:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494,dstIF=0x1964EEC, dstCallID=4, voip_mode=0x2, rtp_mode=0x2, ssrc_status=0*Mar 1 00:38:59.393:rtpspi_bridge:Calling cc_api_bridge_done() for 5(0x1AF5400) and 4(0x0).*Mar 1 00:38:59.393:rtpspi_bridge:leaving.*Mar 1 00:38:59.397:rtpspi_caps_ind:Entered. vdb = 0x1859E88 call id = 5, srcCallId = 4*Mar 1 00:38:59.397:rtpspi_caps_ind:caps from VTSP:codec=0x83FB, codec_bytes=0x50,fax rate=0x7F, vad=0x3 modem=0x0*Mar 1 00:38:59.397:rtpspi_get_rtcp_session_parameters():CURRENT VALUES:dstIF=0x1964EEC, dstCallID=4, current_seq_num=0x0*Mar 1 00:38:59.397:rtpspi_get_rtcp_session_parameters():NEW VALUES:dstIF=0x1964EEC, dstCallID=4, current_seq_num=0x261C*Mar 1 00:38:59.397:rtpspi_caps_ind:Caps Used:codec=0x1, codec bytes=80,fax rate=0x1, vad=0x1, modem=0x1, dtmf_relay=0x1, seq_num_start=0x261D*Mar 1 00:38:59.397:rtpspi_caps_ind:calling cc_api_caps_ind().*Mar 1 00:38:59.397:rtpspi_caps_ind:Returning success*Mar 1 00:38:59.397:rtpspi_caps_ack:Entered. call id = 5, srcCallId = 4*Mar 1 00:38:59.397:rtpspi_caps_ack:leaving.*Mar 1 00:38:59.618:rtpspi_call_modify:entered. call-id=5, nominator=0x7, params=0x18DD440*Mar 1 00:38:59.618:rtpspi_call_modify:leaving*Mar 1 00:38:59.618:rtpspi_do_call_modify:Entered. call-id = 5*Mar 1 00:38:59.622:rtpspi_do_call_modify:Remote RTP port changed. New port=16432*Mar 1 00:38:59.622:rtpspi_do_call_modify:Remote IP addrs changed. New IP addrs=0x6000001*Mar 1 00:38:59.622:rtpspi_do_call_modify:new mode 2 is the same as the current mode*Mar 1 00:38:59.622:rtpspi_do_call_modify:Starting new RTCP session.*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=16432, rem ip=0x6000001*Mar 1 00:38:59.622:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:Removing old RTCP session.*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:Starting RTCP session.Local IP addr = 0x5000001, Remote IP addr = 0x6000001,Local RTP port = 16544, Remote RTP port = 16432, mode = 0x2*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:RTCP Timer creation Success. (5)*(5000)*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:RTP Session creation Success.*Mar 1 00:38:59.622:rtpspi_do_call_modify:RTP Session creation Success.*Mar 1 00:38:59.622:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0*Mar 1 00:38:59.626:rtpspi_do_call_modify:success. leaving*Mar 1 00:39:05.019:rtpspi_call_modify:entered. call-id=5, nominator=0x7, params=0x18DD440*Mar 1 00:39:05.019:rtpspi_call_modify:leaving*Mar 1 00:39:05.019:rtpspi_do_call_modify:Entered. call-id = 5*Mar 1 00:39:05.019:rtpspi_do_call_modify:New remote RTP port = old rtp port = 16432*Mar 1 00:39:05.019:rtpspi_do_call_modify:New remote IP addrs = old IP addrs = 0x6000001*Mar 1 00:39:05.019:rtpspi_do_call_modify:Mode changed. new = 3, old = 2*Mar 1 00:39:05.019:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3*Mar 1 00:39:05.023:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494,dstIF=0x1964EEC, dstCallID=4, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2*Mar 1 00:39:05.023:rtpspi_do_call_modify:RTCP Timer start.*Mar 1 00:39:05.023:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0*Mar 1 00:39:05.023:rtpspi_do_call_modify:success. leaving*Mar 1 00:40:13.786:rtpspi_bridge_drop:entered. src call-id=5, dest call-id=4, tag=0*Mar 1 00:40:13.786:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3*Mar 1 00:40:13.786:rtpspi_modify_rtcp_session_parameters():xmit fn=0x0,dstIF=0x0, dstCallID=0, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2*Mar 1 00:40:13.786:rtpspi_bridge_drop:leaving*Mar 1 00:40:13.790:rtpspi_call_disconnect:entered. call-id=5, cause=16, tag=0*Mar 1 00:40:13.790:rtpspi_call_disconnect:leaving.*Mar 1 00:40:13.790:rtpspi_do_call_disconnect:Entered. call-id = 5*Mar 1 00:40:13.790:rtpspi_do_call_disconnect:calling rtpspi_call_cleanup(). call-id=5*Mar 1 00:40:13.794:rtpspi_call_cleanup:entered. ccb = 0x1AF5400, call-id=5, rtp port = 16544*Mar 1 00:40:13.794:rtpspi_call_cleanup:releasing ccb cache. RTP port=16544*Mar 1 00:40:13.794:rtpspi_store_call_history_entry():Entered.*Mar 1 00:40:13.794:rtpspi_store_call_history_entry():Leaving.*Mar 1 00:40:13.794:rtpspi_call_cleanup:RTCP Timer Stop.*Mar 1 00:40:13.794:rtpspi_call_cleanup:deallocating RTP port 16544.*Mar 1 00:40:13.794:rtpspi_free_rtcp_session:Entered.*Mar 1 00:40:13.794:rtpspi_free_rtcp_session:Success. Leaving*Mar 1 00:40:13.794::rtpspi_call_cleanup freeing ccb (0x1AF5400)*Mar 1 00:40:13.794:rtpspi_call_cleanup:leaving*Mar 1 00:40:13.794:rtpspi_do_call_disconnect:leavingRelated Commands
debug rtpspi errors
To debug Routing Table Protocol (RTP) security parameter index (SPI) errors, use the debug rtpspi errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtpspi errors
no debug rtpspi errors
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 device and Cisco 3600 series routers (except the Cisco 3620).
Usage Guidelines
Caution
Examples
This example shows a debug trace for RTP SPI errors on two gateways. The following example shows the debug trace on the first gateway:
Router# debug rtpspi errors00:54:13.272:rtpspi_do_call_modify:new mode 2 is the same as the current mode00:54:18.738:rtpspi_do_call_modify:New remote RTP port = old rtp port = 1645200:54:18.738:rtpspi_do_call_modify:New remote IP addrs = old IP addrs = 0x6000001The following example shows the debug trace on the second gateway:
Router# debug rtpspi errors00:54:08:rtpspi_process_timers:00:54:08:rtpspi_process_timers:Timer 0x1A5AF9C expired.00:54:08:rtpspi_process_timers:Timer expired for callID 0x300:54:08:rtpspi_process_timers:00:54:08:rtpspi_process_timers:Timer 0x1A5AF9C expired.00:54:08:rtpspi_process_timers:Timer expired for callID 0x300:54:08:rtpspi_process_timers:00:54:08:rtpspi_process_timers:Timer 0x1A5AF9C expired.00:54:08:rtpspi_process_timers:Timer expired for callID 0x300:54:09:rtpspi_process_timers:00:54:09:rtpspi_process_timers:Timer 0x1A5AFBC expired.00:54:09:rtpspi_process_timers:Timer expired for callID 0x300:54:09:rtpspi_process_timers:00:54:09:rtpspi_process_timers:Timer 0x1A5B364 expired.00:54:09:rtpspi_process_timers:Timer expired for callID 0x3Related Commands
debug rtpspi inout
To debug Routing Table Protocol (RTP) security parameter index (SPI) in/out functions, use the debug rtpspi inout command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtpspi inout
no debug rtpspi inout
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 device and Cisco 3600 series routers (except the Cisco 3620 device).
Usage Guidelines
Caution
Examples
The following example shows a debug trace for RTP SPI in/out functions on a gateway:
Router# debug rtpspi inout*Mar 1 00:57:24.565:rtpspi_allocate_rtp_port:Entered.*Mar 1 00:57:24.565:rtpspi_allocate_rtp_port:Success. port = 16520. Leaving.*Mar 1 00:57:24.565:rtpspi_call_setup_request:entered.Call Id = 9, dest = 0.0.0.0; callInfo:final dest flag = 0,rtp_session_mode = 0x2,local_ip_addrs = 0x5000001,remote_ip_addrs = 0x0,local rtp port = 16520, remote rtp port = 0*Mar 1 00:57:24.565:rtpspi_call_setup_request:spi_info copied for rtpspi_app_data_t.*Mar 1 00:57:24.565:rtpspi_call_setup_request:leaving*Mar 1 00:57:24.569:rtpspi_call_setup() entered*Mar 1 00:57:24.569:rtpspi_initialize_ccb:Entered*Mar 1 00:57:24.569:rtpspi_initialize_ccb:leaving*Mar 1 00:57:24.569:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=0, rem ip=0x0*Mar 1 00:57:24.569:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:57:24.569:rtpspi_call_setup:Leaving.*Mar 1 00:57:24.573:rtpspi_bridge:entered. conf id = 3, src i/f = 0x1859E88,dest i/f = 0x1964EEC, src call id = 9, dest call id = 8call info = 0x1919140, xmit fn = 0xDA7494, tag = 0*Mar 1 00:57:24.573:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:57:24.573:rtpspi_bridge:leaving.*Mar 1 00:57:24.573:rtpspi_caps_ind:Entered. vdb = 0x1859E88 call id = 9, srcCallId = 8*Mar 1 00:57:24.577:rtpspi_caps_ind:Returning success*Mar 1 00:57:24.577:rtpspi_caps_ack:Entered. call id = 9, srcCallId = 8*Mar 1 00:57:24.577:rtpspi_caps_ack:leaving.*Mar 1 00:57:24.818:rtpspi_call_modify:entered. call-id=9, nominator=0x7, params=0x18DD440*Mar 1 00:57:24.818:rtpspi_call_modify:leaving*Mar 1 00:57:24.818:rtpspi_do_call_modify:Entered. call-id = 9*Mar 1 00:57:24.818:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=16396, rem ip=0x6000001*Mar 1 00:57:24.822:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:57:24.822:rtpspi_do_call_modify:success. leaving*Mar 1 00:57:30.296:rtpspi_call_modify:entered. call-id=9, nominator=0x7, params=0x18DD440*Mar 1 00:57:30.296:rtpspi_call_modify:leaving*Mar 1 00:57:30.300:rtpspi_do_call_modify:Entered. call-id = 9*Mar 1 00:57:30.300:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3*Mar 1 00:57:30.300:rtpspi_do_call_modify:success. leaving*Mar 1 00:58:39.055:rtpspi_bridge_drop:entered. src call-id=9, dest call-id=8, tag=0*Mar 1 00:58:39.055:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3*Mar 1 00:58:39.055:rtpspi_bridge_drop:leaving*Mar 1 00:58:39.059:rtpspi_call_disconnect:entered. call-id=9, cause=16, tag=0*Mar 1 00:58:39.059:rtpspi_call_disconnect:leaving.*Mar 1 00:58:39.059:rtpspi_do_call_disconnect:Entered. call-id = 9*Mar 1 00:58:39.059:rtpspi_call_cleanup:entered. ccb = 0x1AF5400, call-id=9, rtp port = 16520*Mar 1 00:58:39.059:rtpspi_store_call_history_entry():Entered.*Mar 1 00:58:39.059:rtpspi_store_call_history_entry():Leaving.*Mar 1 00:58:39.059:rtpspi_free_rtcp_session:Entered.*Mar 1 00:58:39.059:rtpspi_free_rtcp_session:Success. Leaving*Mar 1 00:58:39.063:rtpspi_call_cleanup:leaving*Mar 1 00:58:39.063:rtpspi_do_call_disconnect:leavingRelated Commands
debug rtpspi send-nse
To trigger the Routing Table Protocol (RTP) security parameter index (SPI) software module to send a triple redundant NSE, use the debug rtpspi send-nse command in privileged EXEC mode. To disable this action, use the no form of the command.
debug rtpspi send-nse call-ID NSE-event-ID
no debug rtpspi send-nse call-ID NSE-event-ID
Syntax Description
call-ID
Specifies the call ID of the active call. The valid range is from 0 to 65535.
NSE-event-ID
Specifies the NSE Event ID. The valid range is from 0 to 255.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 device and Cisco 3600 series routers (except the Cisco 3620 router).
Examples
The following example shows the RTP SPI software module set to send an NSE:
Router# debug rtpspi send-nseRelated Commands
debug rtpspi session
To debug all Routing Table Protocol (RTP) security parameter index (SPI) sessions, use the debug rtpspi session command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug rtpspi session
no debug rtpspi session
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 device and Cisco 3600 series routers (except the Cisco 3620 router).
Examples
The following example shows a debug trace for RTP SPI sessions on a gateway:
Router# debug rtpspi session*Mar 1 01:01:51.593:rtpspi_allocate_rtp_port:allocated RTP port 16406*Mar 1 01:01:51.593:rtpspi_call_setup:rtp_session_mode = 0x2*Mar 1 01:01:51.593:rtpspi_call_setup:mode = CC_CALL_NORMAL.destianation number = 0.0.0.0*Mar 1 01:01:51.593:rtpspi_call_setup:Passed local_ip_addrs=0x5000001*Mar 1 01:01:51.593:rtpspi_call_setup:Passed local_rtp_port = 16406*Mar 1 01:01:51.593:rtpspi_call_setup:Saved RTCP Session = 0x1AFDFBC*Mar 1 01:01:51.593:rtpspi_call_setup:Passed remote rtp port = 0.*Mar 1 01:01:51.598:rtpspi_start_rtcp_session:Starting RTCP session.Local IP addr = 0x5000001, Remote IP addr = 0x0,Local RTP port = 16406, Remote RTP port = 0, mode = 0x2*Mar 1 01:01:51.598:rtpspi_start_rtcp_session:RTP Session creation Success.*Mar 1 01:01:51.598:rtpspi_call_setup:RTP Session creation Success.*Mar 1 01:01:51.598:rtpspi_call_setup:calling cc_api_call_connected()*Mar 1 01:01:51.598:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494,dstIF=0x1964EEC, dstCallID=10, voip_mode=0x2, rtp_mode=0x2, ssrc_status=0*Mar 1 01:01:51.598:rtpspi_bridge:Calling cc_api_bridge_done() for 11(0x1AF5400) and 10(0x0).*Mar 1 01:01:51.602:rtpspi_caps_ind:caps from VTSP:codec=0x83FB, codec_bytes=0x50,fax rate=0x7F, vad=0x3 modem=0x0*Mar 1 01:01:51.602:rtpspi_get_rtcp_session_parameters():CURRENT VALUES:dstIF=0x1964EEC, dstCallID=10, current_seq_num=0x0*Mar 1 01:01:51.602:rtpspi_get_rtcp_session_parameters():NEW VALUES:dstIF=0x1964EEC, dstCallID=10, current_seq_num=0xF1E*Mar 1 01:01:51.602:rtpspi_caps_ind:Caps Used:codec=0x1, codec bytes=80,fax rate=0x1, vad=0x1, modem=0x1, dtmf_relay=0x1, seq_num_start=0xF1F*Mar 1 01:01:51.602:rtpspi_caps_ind:calling cc_api_caps_ind().*Mar 1 01:01:51.822:rtpspi_do_call_modify:Remote RTP port changed. New port=16498*Mar 1 01:01:51.822:rtpspi_do_call_modify:Remote IP addrs changed. New IP addrs=0x6000001*Mar 1 01:01:51.822:rtpspi_do_call_modify:Starting new RTCP session.*Mar 1 01:01:51.822:rtpspi_start_rtcp_session:Removing old RTCP session.*Mar 1 01:01:51.822:rtpspi_start_rtcp_session:Starting RTCP session.Local IP addr = 0x5000001, Remote IP addr = 0x6000001,Local RTP port = 16406, Remote RTP port = 16498, mode = 0x2*Mar 1 01:01:51.822:rtpspi_start_rtcp_session:RTCP Timer creation Success. (5)*(5000)*Mar 1 01:01:51.826:rtpspi_start_rtcp_session:RTP Session creation Success.*Mar 1 01:01:51.826:rtpspi_do_call_modify:RTP Session creation Success.*Mar 1 01:01:51.826:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0*Mar 1 01:01:57.296:rtpspi_do_call_modify:Mode changed. new = 3, old = 2*Mar 1 01:01:57.296:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494,dstIF=0x1964EEC, dstCallID=10, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2*Mar 1 01:01:57.296:rtpspi_do_call_modify:RTCP Timer start.*Mar 1 01:01:57.296:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0*Mar 1 01:03:06.108:rtpspi_modify_rtcp_session_parameters():xmit fn=0x0,dstIF=0x0, dstCallID=0, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2*Mar 1 01:03:06.112:rtpspi_do_call_disconnect:calling rtpspi_call_cleanup(). call-id=11*Mar 1 01:03:06.112:rtpspi_call_cleanup:releasing ccb cache. RTP port=16406*Mar 1 01:03:06.112:rtpspi_call_cleanup:RTCP Timer Stop.*Mar 1 01:03:06.112:rtpspi_call_cleanup:deallocating RTP port 16406.*Mar 1 01:03:06.112::rtpspi_call_cleanup freeing ccb (0x1AF5400)Related Commands
debug rtsp all
To display all related information about the Real Time Streaming Protocol (RTSP) data, use the debug rtsp all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtsp all
no debug rtsp all
Syntax Description
This command has no arguments or keywords.
Defaults
Debug is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
We recommend that you log output from the debug rtsp all command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Examples
The following example shows debugging output for the debug rtsp all command. The show debug command shows which RTSP modules are traced.
Router# debug rtsp allAll RTSP client debugging is onRouter# show debugRTSP:RTSP client Protocol Error debugging is onRTSP client Protocol Message Handler debugging is onRTSP client API debugging is onRTSP client socket debugging is onRTSP client session debugging is onRouter#Router#!call initiatedRouter#*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_get_new_scb:*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_initialize_scb:*Mar 11 03:14:23.471: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5FE6C*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F0D4 context=0x6345042C*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_get_new_scb:*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_initialize_scb:*Mar 11 03:14:23.471: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5D874*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F204 context=0x6345046C*Mar 11 03:14:23.471: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A59FB8*Mar 11 03:14:23.471: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A59FB8*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A59FB8*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5A304*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A5A304*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5A304*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5A650*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A5A650*Mar 11 03:14:23.475: //166//RTSP:LP:RS45:/rtsp_api_handle_req_set_params:*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5A650*Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_request: msg=0x63A5A99C*Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_handle_req_set_params: msg=0x63A5A99C*Mar 11 03:14:23.475: //166//RTSP:LP:RS46:/rtsp_api_handle_req_set_params:*Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_free_msg_buffer: msg=0x63A5A99CRouter#Router#!call answeredRouter#Router#!digits dialedRouter#Router#!call terminatedRouter#*Mar 11 03:14:51.603: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5ACE8*Mar 11 03:14:51.603: //-1//RTSP:RS46:/rtsp_api_request: msg=0x63A5B034*Mar 11 03:14:51.607: //-1//RTSP:RS45:/rtsp_control_process_msg:*Mar 11 03:14:51.607: //166//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 0*Mar 11 03:14:51.607: //166//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY*Mar 11 03:14:51.607: //166//RTSP:/rtsp_session_cleanup:*Mar 11 03:14:51.607: //-1//RTSP:/rtsplib_free_svr_session:*Mar 11 03:14:51.607: //-1//RTSP:/rtsplib_stop_timer: timer(0x638D5DDC) stops*Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: scb=0x63A5FE6C, callID=0xA6*Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: No streams in session control block*Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5FE6C*Mar 11 03:14:51.611: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5ACE8*Mar 11 03:14:51.611: //-1//RTSP:RS46:/rtsp_control_process_msg:*Mar 11 03:14:51.611: //166//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 0*Mar 11 03:14:51.611: //166//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY*Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup:*Mar 11 03:14:51.611: //-1//RTSP:/rtsplib_free_svr_session:*Mar 11 03:14:51.611: //-1//RTSP:/rtsplib_stop_timer: timer(0x63A60110) stops*Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: scb=0x63A5D874, callID=0xA6*Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: No streams in session control block*Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5D874*Mar 11 03:14:51.611: //-1//RTSP:RS46:/rtsp_api_free_msg_buffer: msg=0x63A5B034Table 284 describes the significant fields shown in the display.
Related Commands
debug rtsp api
To display information about the Real Time Streaming Protocol (RTSP) application programming interface (API) messages passed down to the RTSP client, use the debug rtsp api command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtsp api
no debug rtsp api
Syntax Description
This command has no arguments or keywords.
Defaults
Debug is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
We recommend that you log output from the debug rtsp api command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Examples
The following example shows output from the debug rtsp api command:
Router# debug rtsp apiRTSP client API debugging is onRouter# !call initiated*Mar 11 03:04:41.699: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F0D4 context=0x6345088C*Mar 11 03:04:41.699: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F204 context=0x634508CC*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A59FB8*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A59FB8*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A59FB8*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5A304*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A5A304*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5A304*Mar 11 03:04:41.703: //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5A650*Mar 11 03:04:41.703: //-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A5A650*Mar 11 03:04:41.703: //146//RTSP:LP:RS35:/rtsp_api_handle_req_set_params:*Mar 11 03:04:41.703: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5A650*Mar 11 03:04:41.703: //-1//RTSP:RS36:/rtsp_api_request: msg=0x63A5A99C*Mar 11 03:04:41.703: //-1//RTSP:RS36:/rtsp_api_handle_req_set_params: msg=0x63A5A99C*Mar 11 03:04:41.703: //146//RTSP:LP:RS36:/rtsp_api_handle_req_set_params:*Mar 11 03:04:41.703: //-1//RTSP:RS36:/rtsp_api_free_msg_buffer: msg=0x63A5A99CRouter!call answeredRouter#!digits dialedRouter#!call terminated*Mar 11 03:05:15.367: //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5ACE8*Mar 11 03:05:15.367: //-1//RTSP:RS36:/rtsp_api_request: msg=0x63A5B034*Mar 11 03:05:15.367: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5ACE8*Mar 11 03:05:15.367: //-1//RTSP:RS36:/rtsp_api_free_msg_buffer: msg=0x63A5B034Table 285 describes the significant fields shown in the display.
Related Commands
debug rtsp client
Note
To display client information and stream information for the stream that is currently active for the Real Time Streaming Protocol (RTSP) client, use the debug rtsp client command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtsp client
no debug rtsp client
Syntax Description
This command has no arguments or keywords.
Defaults
Debug is not enabled.
Command Modes
Privileged EXEC
Command History
12.1(3)T
This command was introduced.
12.3(4)T
This command was replaced by the debug rtsp session command.
Usage Guidelines
We recommend that you log output from the debug rtsp client command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Related Commands
debug rtsp client session
Note
To display debug messages about the Real Time Streaming Protocol (RTSP) client or the current session, use the debug rtsp command. To disable debugging output, use the no form of this command.
debug rtsp [client | session]
no debug rtsp [client | session]
Syntax Description
Defaults
Debug is not enabled.
Command History
12.1(3)T
This command was introduced.
12.3(4)T
This command was replaced by the debug rtsp session command.
Examples
The following example displays the debug messages of the RTSP session:
Router# debug rtsp sessionRTSP client session debugging is onrouter#Jan 1 00:08:36.099:rtsp_get_new_scb:Jan 1 00:08:36.099:rtsp_initialize_scb:Jan 1 00:08:36.099:rtsp_control_process_msg:Jan 1 00:08:36.099:rtsp_control_process_msg:received MSG request of TYPE 0Jan 1 00:08:36.099:rtsp_set_event:Jan 1 00:08:36.099:rtsp_set_event:api_req_msg_type=RTSP_API_REQ_PLAYJan 1 00:08:36.103:rtsp_set_event:url:[rtsp://rtsp-cisco.cisco.com:554/en_welcome.au]Jan 1 00:08:36.103:rtsp_process_async_event:SCB=0x62128F08Jan 1 00:08:36.103:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_IDLErtsp_event = RTSP_EV_PLAY_OR_RECJan 1 00:08:36.103:act_idle_event_play_or_rec_req:Jan 1 00:08:36.103:rtsp_resolve_dns:Jan 1 00:08:36.103:rtsp_resolve_dns:IP Addr = 1.13.79.6:Jan 1 00:08:36.103:rtsp_connect_to_svr:Jan 1 00:08:36.103:rtsp_connect_to_svr:socket=0, connection_state = 2Jan 1 00:08:36.103:rtsp_start_timer:timer (0x62128FD0)starts - delay (10000)Jan 1 00:08:36.107:rtsp_control_main:SOCK= 0 Event=0x1Jan 1 00:08:36.107:rtsp_stop_timer:timer(0x62128FD0) stopsJan 1 00:08:36.107:rtsp_process_async_event:SCB=0x62128F08Jan 1 00:08:36.107:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_IDLErtsp_event = RTSP_EV_SVR_CONNECTEDJan 1 00:08:36.107:act_idle_event_svr_connected:Jan 1 00:08:36.107:rtsp_control_main:SOCK= 0 Event=0x1Jan 1 00:08:36.783:rtsp_control_main:SOCK= 0 Event=0x1Jan 1 00:08:36.783:rtsp_process_async_event:SCB=0x62128F08Jan 1 00:08:36.783:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_READYrtsp_event = RTSP_EV_SVR_DESC_OR_ANNOUNCE_RESPJan 1 00:08:36.783:act_ready_event_desc_or_announce_resp:Jan 1 00:08:36.783:act_ready_event_desc_or_announce_resp:RTSP_STATUS_DESC_OR_ANNOUNCE_RESP_OKJan 1 00:08:37.287:rtsp_control_main:SOCK= 0 Event=0x1Jan 1 00:08:37.287:rtsp_process_async_event:SCB=0x62128F08Jan 1 00:08:37.287:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_READYrtsp_event = RTSP_EV_SVR_SETUP_RESPJan 1 00:08:37.287:act_ready_event_setup_resp:Jan 1 00:08:37.287:act_ready_event_setup_resp:Remote RTP Port=13344Jan 1 00:08:37.287:rtsp_rtp_stream_setup:scb=0x62128F08, callID=0x7 record=0Jan 1 00:08:37.287:rtsp_rtp_stream_setup:Starting RTCP session.Local IP addr = 1.13.79.45, Remote IP addr = 1.13.79.6,Local RTP port = 18748, Remote RTP port = 13344 CallID=8Jan 1 00:08:37.291:xmit_func = 0x0 vdbptr = 0x61A0FC98Jan 1 00:08:37.291:rtsp_control_main:CCAPI Queue EventJan 1 00:08:37.291:rtsp_rtp_associate_done:ev=0x62070E08, callID=0x7Jan 1 00:08:37.291:rtsp_rtp_associate_done:scb=0x62128F08Jan 1 00:08:37.291:rtsp_rtp_associate_done:callID=0x7, pVdb=0x61F4FBC8,Jan 1 00:08:37.291: spi_context=0x6214145CJan 1 00:08:37.291: disposition=0, playFunc=0x60CA2238,Jan 1 00:08:37.291: codec=0x5, vad=0, mediaType=6,Jan 1 00:08:37.291: stream_assoc_id=1Jan 1 00:08:37.291:rtsp_rtp_modify_session:scb=0x62128F08, callID=0x7Jan 1 00:08:37.291:rtsp_process_async_event:SCB=0x62128F08Jan 1 00:08:37.291:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_READYrtsp_event = RTSP_EV_ASSOCIATE_DONEJan 1 00:08:37.291:act_ready_event_associate_done:Jan 1 00:08:37.291:rtsp_get_stream:Jan 1 00:08:37.783:rtsp_control_main:SOCK= 0 Event=0x1Jan 1 00:08:37.783:rtsp_process_async_event:SCB=0x62128F08Jan 1 00:08:37.783:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_READYrtsp_event = RTSP_EV_SVR_PLAY_OR_REC_RESPJan 1 00:08:37.783:act_ready_event_play_or_rec_resp:Jan 1 00:08:37.783:rtsp_start_timer:timer (0x62128FB0)starts - delay (4249)rtsp-5#Jan 1 00:08:42.035:rtsp_process_timer_events:Jan 1 00:08:42.035:rtsp_process_timer_events:PLAY OR RECORD completedJan 1 00:08:42.035:rtsp_process_async_event:SCB=0x62128F08Jan 1 00:08:42.035:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_PLAY_OR_RECrtsp_event = RTSP_EV_PLAY_OR_REC_TIMER_EXPIREDJan 1 00:08:42.035:act_play_event_play_done:Jan 1 00:08:42.035:act_play_event_play_done:elapsed play time = 4249 total play time = 4249Jan 1 00:08:42.035:rtsp_send_teardown_to_svr:Jan 1 00:08:42.487:rtsp_control_main:SOCK= 0 Event=0x1Jan 1 00:08:42.487:rtsp_process_async_event:SCB=0x62128F08Jan 1 00:08:42.487:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_PLAY_OR_RECrtsp_event = RTSP_EV_SVR_TEARDOWN_RESPJan 1 00:08:42.487:act_play_event_teardown_resp:Jan 1 00:08:42.487:rtsp_server_closed:Jan 1 00:08:42.487:rtsp_send_resp_to_api:Jan 1 00:08:42.487:rtsp_send_resp_to_api:sending RESP=RTSP_STATUS_PLAY_COMPLETEJan 1 00:08:42.491:rtsp_rtp_teardown_stream:scb=0x62128F08, callID=0x7Jan 1 00:08:42.491:rtsp_rtp_stream_cleanup:scb=0x62128F08, callID=0x7Jan 1 00:08:42.491:rtsp_update_stream_stats:scb=0x62128F08, stream=0x61A43350,Jan 1 00:08:42.491:call_info=0x6214C67C, callID=0x7Jan 1 00:08:42.491:rtsp_update_stream_stats:rx_bytes = 25992Jan 1 00:08:42.491:rtsp_update_stream_stats:rx_packetes = 82Jan 1 00:08:42.491:rtsp_reinitialize_scb:Jan 1 00:08:42.503:rtsp_control_process_msg:Jan 1 00:08:42.503:rtsp_control_process_msg:received MSG request of TYPE 0Jan 1 00:08:42.503:rtsp_set_event:Jan 1 00:08:42.503:rtsp_set_event:api_req_msg_type=RTSP_API_REQ_DESTROYJan 1 00:08:42.503:rtsp_session_cleanup:Jan 1 00:08:42.503:rtsp_create_session_history:scb=0x62128F08, callID=0x7Jan 1 00:08:42.503:rtsp_insert_session_history_record:current=0x6214BDC8, callID=0x7Jan 1 00:08:42.503:rtsp_insert_session_history_record:count = 3Jan 1 00:08:42.503:rtsp_insert_session_history_record:starting history record deletion_timer of10 minutesJan 1 00:08:42.503:rtsp_session_cleanup:deleting session:scb=0x62128F08Router#Related Commands
debug rtsp error
To display error information about the Real-Time Streaming Protocol (RTSP) client, use the debug rtsp error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtsp error
no debug rtsp error
Syntax Description
This command has no arguments or keywords.
Defaults
Debug is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
We recommend that you log output from the debug rtsp error command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Related Commands
debug rtsp pmh
To display debugging information about the Protocol Message Handler (PMH), use the debug rtsp pmh command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtsp pmh
no debug rtsp pmh
Syntax Description
This command has no arguments or keywords.
Defaults
Debug is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
We recommend that you log output from the debug rtsp pmh command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Related Commands
debug rtsp session
To display client information and stream information for the stream that is currently active for the Real Time Streaming Protocol (RTSP) client, use the debug rtsp session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtsp session
no debug rtsp session
Syntax Description
This command has no arguments or keywords.
Defaults
Debug is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
We recommend that you log output from the debug rtsp session command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Examples
The following example shows the display of the debugging messages of the RTSP session:
Router# debug rtsp sessionRTSP client session debugging is onRouter#Router#!call initiatedRouter#*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_get_new_scb:*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_initialize_scb:*Mar 11 03:09:58.123: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5FE6C*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_get_new_scb:*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_initialize_scb:*Mar 11 03:09:58.123: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5D874Router#Router#!call answeredRouter#Router#!digits dialedRouter#Router#!call terminatedRouter#*Mar 11 03:10:38.139: //-1//RTSP:RS41:/rtsp_control_process_msg:*Mar 11 03:10:38.139: //158//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 0*Mar 11 03:10:38.139: //158//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY*Mar 11 03:10:38.139: //158//RTSP:/rtsp_session_cleanup:*Mar 11 03:10:38.139: //-1//RTSP:/rtsplib_free_svr_session:*Mar 11 03:10:38.139: //-1//RTSP:/rtsplib_stop_timer: timer(0x638D5DDC) stops*Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: scb=0x63A5FE6C, callID=0x9E*Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: No streams in session control block*Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5FE6C*Mar 11 03:10:38.143: //-1//RTSP:RS42:/rtsp_control_process_msg:*Mar 11 03:10:38.143: //158//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 0*Mar 11 03:10:38.143: //158//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY*Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup:*Mar 11 03:10:38.143: //-1//RTSP:/rtsplib_free_svr_session:*Mar 11 03:10:38.143: //-1//RTSP:/rtsplib_stop_timer: timer(0x63A60110) stops*Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: scb=0x63A5D874, callID=0x9E*Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: No streams in session control block*Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5D874Table 286 describes the significant fields shown in the display.
Related Commands
debug rtsp socket
To display debugging messages about the packets received or sent on the TCP or User Datagram Protocol (UDP) sockets, use the debug rtsp socket command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rtsp socket
no debug rtsp socket
Syntax Description
This command has no arguments or keywords.
Defaults
Debug is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Each Real-Time Streaming Protocol (RTSP) session has a TCP port for control and a UDP (RTP) port for delivery of data. The control connection (TCP socket) is used to exchange a set of messages (request from the RTSP client and the response from the server) for displaying a prompt. The debug rtsp socket command enables the user to debug the message exchanges being done on the TCP control connection.
Note
Related Commands
debug rudpv1
For debug information for Reliable User Datagram Protocol (RUDP), use the debug rudpv1 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug rudpv1 {application | performance | retransmit | segment | signal | state | timer | transfer}
no debug rudpv1{application | performance | retransmit | segment | signal | state | timer | transfer}
Syntax Description
Defaults
Debugging for rudpv1 is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command only during times of low traffic.
Examples
The following is sample output from the debug rudpv1 application command:
Router# debug rudpv1 applicationRudpv1:Turning application debugging on*Jan 1 00:20:38.271:Send to appl (61F72B6C), seq 12*Jan 1 00:20:48.271:Send to appl (61F72B6C), seq 13*Jan 1 00:20:58.271:Send to appl (61F72B6C), seq 14*Jan 1 00:21:08.271:Send to appl (61F72B6C), seq 15*Jan 1 00:21:18.271:Send to appl (61F72B6C), seq 16*Jan 1 00:21:28.271:Send to appl (61F72B6C), seq 17*Jan 1 00:21:38.271:Send to appl (61F72B6C), seq 18*Jan 1 00:21:48.275:Send to appl (61F72B6C), seq 19*Jan 1 00:21:58.275:Send to appl (61F72B6C), seq 20*Jan 1 00:22:08.275:Send to appl (61F72B6C), seq 21*Jan 1 00:22:18.275:Send to appl (61F72B6C), seq 22*Jan 1 00:22:28.275:Send to appl (61F72B6C), seq 23*Jan 1 00:22:38.275:Send to appl (61F72B6C), seq 24*Jan 1 00:22:48.279:Send to appl (61F72B6C), seq 25*Jan 1 00:22:58.279:Send to appl (61F72B6C), seq 26*Jan 1 00:23:08.279:Send to appl (61F72B6C), seq 27*Jan 1 00:23:18.279:Send to appl (61F72B6C), seq 28*Jan 1 00:23:28.279:Send to appl (61F72B6C), seq 29The following is sample output from the debug rudpv1 performance command:
Router# debug rudpv1 performanceRudpv1:Turning performance debugging oncorsair-f#*Jan 1 00:44:27.299:*Jan 1 00:44:27.299:Rudpv1 Sent:Pkts 11, Data Bytes 236, Data Pkts 9*Jan 1 00:44:27.299:Rudpv1 Rcvd:Pkts 10, Data Bytes 237, Data Pkts 9*Jan 1 00:44:27.299:Rudpv1 Discarded:0, Retransmitted 0*Jan 1 00:44:27.299:*Jan 1 00:44:37.299:*Jan 1 00:44:37.299:Rudpv1 Sent:Pkts 11, Data Bytes 236, Data Pkts 9*Jan 1 00:44:37.299:Rudpv1 Rcvd:Pkts 10, Data Bytes 237, Data Pkts 9*Jan 1 00:44:37.299:Rudpv1 Discarded:0, Retransmitted 0*Jan 1 00:44:37.299:*Jan 1 00:44:47.299:*Jan 1 00:44:47.299:Rudpv1 Sent:Pkts 11, Data Bytes 236, Data Pkts 9*Jan 1 00:44:47.299:Rudpv1 Rcvd:Pkts 11, Data Bytes 236, Data Pkts 9*Jan 1 00:44:47.299:Rudpv1 Discarded:0, Retransmitted 0*Jan 1 00:44:47.299:The following is sample output from the debug rudpv1 retransmit command:
Router# debug rudpv1 retransmitRudpv1:Turning retransmit/softreset debugging on*Jan 1 00:52:59.799:Retrans timer, set to ack 199*Jan 1 00:52:59.903:Retrans timer, set to ack 200*Jan 1 00:53:00.003:Retrans timer, set to ack 201*Jan 1 00:53:00.103:Retrans timer, set to ack 202*Jan 1 00:53:00.203:Retrans timer, set to ack 203*Jan 1 00:53:00.419:Retrans timer, set to ack 97*Jan 1 00:53:00.503:Retrans handler fired, 203*Jan 1 00:53:00.503:Retrans:203:205:*Jan 1 00:53:00.503:*Jan 1 00:53:00.607:Retrans timer, set to ack 207*Jan 1 00:53:00.907:Retrans timer, set to ack 210*Jan 1 00:53:01.207:Retrans handler fired, 210*Jan 1 00:53:01.207:Retrans:210:211:212:*Jan 1 00:53:01.207:*Jan 1 00:53:01.207:Retrans timer, set to ack 213*Jan 1 00:53:01.311:Retrans timer, set to ack 214*Jan 1 00:53:01.419:Retrans timer, set to ack 98*Jan 1 00:53:01.611:Retrans timer, set to ack 215*Jan 1 00:53:01.711:Retrans timer, set to ack 218*Jan 1 00:53:01.811:Retrans timer, set to ack 219*Jan 1 00:53:01.911:Retrans timer, set to ack 220*Jan 1 00:53:02.011:Retrans timer, set to ack 221*Jan 1 00:53:02.311:Retrans handler fired, 221*Jan 1 00:53:02.311:Retrans:221:*Jan 1 00:53:02.311:*Jan 1 00:53:02.311:Retrans timer, set to ack 222*Jan 1 00:53:02.415:Retrans timer, set to ack 225The following is sample output from the debug rudpv1 segment command:
Router# debug rudpv1 segmentRudpv1:Turning segment debugging on*Jan 1 00:41:36.359:Rudpv1: (61F72DAC) Rcvd ACK 61..198 (32)*Jan 1 00:41:36.359:Rudpv1: (61F72DAC) Send ACK 199..61 (32)*Jan 1 00:41:36.459:Rudpv1: (61F72DAC) Rcvd ACK 62..199 (8)*Jan 1 00:41:36.459:Rudpv1: (61F72DAC) Rcvd ACK 62..199 (32)*Jan 1 00:41:36.459:Rudpv1: (61F72DAC) Send ACK 200..62 (32)*Jan 1 00:41:36.559:Rudpv1: (61F72DAC) Rcvd ACK 63..200 (32)*Jan 1 00:41:36.559:Rudpv1: (61F72DAC) Send ACK 201..63 (32)*Jan 1 00:41:36.659:Rudpv1: (61F72DAC) Rcvd ACK 64..201 (32)*Jan 1 00:41:36.659:Rudpv1: (61F72DAC) Send ACK 202..64 (32)*Jan 1 00:41:36.759:Rudpv1: (61F72DAC) Rcvd ACK 65..202 (32)*Jan 1 00:41:36.759:Rudpv1: (61F72DAC) Send ACK 203..65 (32)*Jan 1 00:41:36.859:Rudpv1: (61F72DAC) Rcvd ACK 66..202 (32)*Jan 1 00:41:36.859:Rudpv1: (61F72DAC) Send ACK 204..66 (32)*Jan 1 00:41:36.959:Rudpv1: (61F72DAC) Rcvd ACK 67..202 (32)*Jan 1 00:41:36.959:Rudpv1: (61F72DAC) Rcvd ACK EAK 68..202 (9)*Jan 1 00:41:36.959:Rudpv1: (61F72DAC) Send ACK 203..67 (32)*Jan 1 00:41:36.963:Rudpv1: (61F72DAC) Send ACK 205..67 (32)*Jan 1 00:41:36.963:Rudpv1: (61F72DAC) Rcvd ACK 68..204 (8)*Jan 1 00:41:37.051:Rudpv1: (61F72B6C) Send ACK NUL 118..96 (8)*Jan 1 00:41:37.051:Rudpv1: (61F72B6C) Rcvd ACK 97..118 (8)*Jan 1 00:41:37.059:Rudpv1: (61F72DAC) Rcvd ACK 68..205 (32)*Jan 1 00:41:37.063:Rudpv1: (61F72DAC) Send ACK 206..68 (32)*Jan 1 00:41:37.263:Rudpv1: (61F72DAC) Rcvd ACK 70..206 (32)*Jan 1 00:41:37.363:Rudpv1: (61F72DAC) Send ACK EAK 207..68 (9)*Jan 1 00:41:37.363:Rudpv1: (61F72DAC) Rcvd ACK 71..206 (32)*Jan 1 00:41:37.363:Rudpv1: (61F72DAC) Rcvd ACK 69..206 (32)*Jan 1 00:41:37.363:Rudpv1: (61F72DAC) Send ACK 207..71 (8)*Jan 1 00:41:37.363:Rudpv1: (61F72DAC) Send ACK 207..71 (32)*Jan 1 00:41:37.363:Rudpv1: (61F72DAC) Send ACK 208..71 (32)*Jan 1 00:41:37.363:Rudpv1: (61F72DAC) Send ACK 209..71 (32)*Jan 1 00:41:37.367:Rudpv1: (61F72DAC) Rcvd ACK 72..209 (8)*Jan 1 00:41:37.463:Rudpv1: (61F72DAC) Rcvd ACK 72..209 (32)*Jan 1 00:41:37.463:Rudpv1: (61F72DAC) Send ACK 210..72 (32)*Jan 1 00:41:37.563:Rudpv1: (61F72DAC) Rcvd ACK 73..210 (32)*Jan 1 00:41:37.563:Rudpv1: (61F72DAC) Send ACK 211..73 (32)The following is sample output from the debug rudpv1 signal command:
Router# debug rudpv1 signalRudpv1:Turning signal debugging on*Jan 1 00:39:59.551:Rudpv1:Sent CONN_FAILED to connID 61F72DAC, sess 33*Jan 1 00:39:59.551:*Jan 1 00:39:59.551:Rudpv1:Sent CONN_TRANS_STATE to connID 61F72B6C, sess 34*Jan 1 00:39:59.551:*Jan 1 00:39:59.551:Rudpv1:Sent CONN_TRANS_STATE to connID 61F72DAC, sess 33*Jan 1 00:39:59.551:*Jan 1 00:39:59.551:Rudpv1:Sent CONN_OPEN to connID 61F72B6C, sess 34*Jan 1 00:39:59.551:Rudpv1:Sent AUTO_RESET to connID 61F72DAC, sess 33*Jan 1 00:39:59.551:*Jan 1 00:40:00.739:%LINK-5-CHANGED:Interface FastEthernet0, changed stateto administratively down*Jan 1 00:40:01.739:%LINEPROTO-5-UPDOWN:Line protocol on InterfaceFastEthernet0, changed state to down*Jan 1 00:40:04.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33*Jan 1 00:40:04.551:*Jan 1 00:40:05.051:Rudpv1:Clearing conn rec values, index 2, connid61F72DAC*Jan 1 00:40:10.051:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33*Jan 1 00:40:10.051:*Jan 1 00:40:10.551:Rudpv1:Clearing conn rec values, index 2, connid61F72DAC*Jan 1 00:40:15.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33*Jan 1 00:40:15.551:*Jan 1 00:40:16.051:Rudpv1:Clearing conn rec values, index 2, connid61F72DAC*Jan 1 00:40:21.051:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33*Jan 1 00:40:21.051:*Jan 1 00:40:21.551:Rudpv1:Clearing conn rec values, index 2, connid61F72DAC*Jan 1 00:40:25.587:%LINK-3-UPDOWN:Interface FastEthernet0, changed stateto up*Jan 1 00:40:26.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33*Jan 1 00:40:26.551:*Jan 1 00:40:26.587:%LINEPROTO-5-UPDOWN:Line protocol on InterfaceFastEthernet0, changed state to up*Jan 1 00:40:27.051:Rudpv1:Clearing conn rec values, index 2, connid61F72DAC*Jan 1 00:40:28.051:Rudpv1:Sent CONN_OPEN to connID 61F72DAC, sess 33The following is sample output from the debug rudpv1 state command:
Router# debug rudpv1 stateRudpv1:Turning state debugging on*Jan 1 00:38:37.323:Rudpv1: (61F72DAC) State Change:OPEN -> CONN_FAILURE*Jan 1 00:38:37.323:Rudpv1: (61F72B6C) State Change:OPEN -> TRANS_STATE*Jan 1 00:38:37.323:Rudpv1: (61F72DAC) State Change:CONN_FAILURE ->TRANS_STATE*Jan 1 00:38:37.323:Rudpv1: (61F72B6C) State Change:TRANS_STATE -> OPEN*Jan 1 00:38:37.323:Rudpv1: (61F72DAC) State Change:TRANS_STATE -> SYN_SENT*Jan 1 00:38:37.455:%LINK-5-CHANGED:Interface FastEthernet0, changed stateto administratively down*Jan 1 00:38:38.451:%LINEPROTO-5-UPDOWN:Line protocol on InterfaceFastEthernet0, changed state to down*Jan 1 00:38:42.323:Rudpv1: (61F72DAC) State Change:SYN_SENT -> CLOSED*Jan 1 00:38:42.823:Rudpv1: (61F72DAC) State Change:INACTIVE -> SYN_SENT*Jan 1 00:38:47.823:Rudpv1: (61F72DAC) State Change:SYN_SENT -> CLOSED*Jan 1 00:38:48.323:Rudpv1: (61F72DAC) State Change:INACTIVE -> SYN_SENT*Jan 1 00:38:53.323:Rudpv1: (61F72DAC) State Change:SYN_SENT -> CLOSED*Jan 1 00:38:53.823:Rudpv1: (61F72DAC) State Change:INACTIVE -> SYN_SENT*Jan 1 00:38:56.411:%LINK-3-UPDOWN:Interface FastEthernet0, changed stateto up*Jan 1 00:38:57.411:%LINEPROTO-5-UPDOWN:Line protocol on InterfaceFastEthernet0, changed state to up*Jan 1 00:38:57.823:Rudpv1: (61F72DAC) State Change:SYN_SENT -> OPENThe following is sample output from the debug rudpv1 timer command:
Router# debug rudpv1 timerRudpv1:Turning timer debugging on*Jan 1 00:53:40.647:Starting Retrans timer for connP = 61F72B6C, delay = 300*Jan 1 00:53:40.647:Stopping SentList timer for connP = 61F72B6C*Jan 1 00:53:40.747:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:40.747:Stopping Retrans timer for connP = 61F72B6C*Jan 1 00:53:40.747:Starting Retrans timer for connP = 61F72B6C, delay = 300*Jan 1 00:53:40.747:Stopping SentList timer for connP = 61F72B6C*Jan 1 00:53:40.847:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:40.847:Stopping Retrans timer for connP = 61F72B6C*Jan 1 00:53:40.847:Starting Retrans timer for connP = 61F72B6C, delay = 300*Jan 1 00:53:40.847:Stopping SentList timer for connP = 61F72B6C*Jan 1 00:53:40.947:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:40.947:Stopping Retrans timer for connP = 61F72B6C*Jan 1 00:53:40.947:Starting Retrans timer for connP = 61F72B6C, delay = 300*Jan 1 00:53:40.947:Stopping SentList timer for connP = 61F72B6C*Jan 1 00:53:41.047:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:41.147:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:41.151:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:41.151:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:41.151:Stopping Retrans timer for connP = 61F72B6C*Jan 1 00:53:41.151:Starting SentList timer for connP = 61F72B6C, delay = 300*Jan 1 00:53:41.419:Timer Keepalive (NullSeg) triggered for conn = 61F72DAC*Jan 1 00:53:41.419:Starting Retrans timer for connP = 61F72DAC, delay = 300*Jan 1 00:53:41.419:Stopping SentList timer for connP = 61F72DAC*Jan 1 00:53:41.419:Starting NullSeg timer for connP = 61F72DAC, delay = 1000*Jan 1 00:53:41.419:Stopping Retrans timer for connP = 61F72DAC*Jan 1 00:53:41.451:Timer SentList triggered for conn = 61F72B6C*Jan 1 00:53:41.451:Starting SentList timer for connP = 61F72B6C, delay = 300*Jan 1 00:53:41.451:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:41.451:Stopping SentList timer for connP = 61F72B6C*Jan 1 00:53:41.551:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:41.551:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:41.551:Starting NullSeg timer for connP = 61F72B6C, delay = 1000*Jan 1 00:53:41.551:Starting NullSeg timer for connP = 61F72B6C, delay = 1000The following is sample output from the debug rudpv1 transfer command:
Router# debug rudpv1 transferRudpv1:Turning transfer debugging on*Jan 1 00:37:30.567:Rudpv1:Send TCS, connId 61F72B6C, old connId 61F72DAC*Jan 1 00:37:30.567:Rudpv1:Initiate transfer state, old conn 61F72DAC tonew conn 61F72B6C*Jan 1 00:37:30.567:Rudpv1:Old conn send window 51 .. 52*Jan 1 00:37:30.567:Rudpv1:New conn send window 255 .. 2*Jan 1 00:37:30.567:Rudpv1:Rcvd TCS 142, next seq 142*Jan 1 00:37:30.567:Rudpv1:Rcv'ing trans state, old conn 61F72DAC to newconn 61F72B6C*Jan 1 00:37:30.567:Rudpv1:Seq adjust factor 148*Jan 1 00:37:30.567:Rudpv1:New rcvCur 142*Jan 1 00:37:30.567:Rudpv1:Send transfer state, old conn 61F72DAC to newconn 61F72B6C*Jan 1 00:37:30.567:Rudpv1:Send TCS, connId 61F72B6C, old connId 61F72DAC,seq adjust 208, indication 0*Jan 1 00:37:30.567:Rudpv1:Transfer seg 51 to seg 3 on new conn*Jan 1 00:37:30.567:Rudpv1:Finishing transfer state, old conn 61F72DAC tonew conn 61F72B6C*Jan 1 00:37:30.567:Rudpv1:Send window 2 .. 4Related Commands
clear rudpv1 statistics
Clears RUDP statistics and failure counters.
show rudpv1
Displays RUDP failures, parameters, and statistics.
Posted: Mon Jul 2 06:44:43 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
