clear rudpv1 statistics
To clear the counters that track RUDP statistics for a specified session-group, use the clear rudpv1 statistics command in privileged EXEC mode.
- clear rudpv1 statistics
Syntax Description
This command has no arguments or keywords.
Defaults
The statistical information accumulates.
Command Modes
Privileged EXEC
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Usage Guidelines
This command clears all statistics.
Examples
The following example clears all RUDP statistics for all available session-groups:
Router#
clear rudpv1 statistics
Related Commands
Command |
Description |
debug rudpv1
|
Displays debugging information for RUDP.
|
show rudpv1
|
Displays RUDP statistics.
|
|
debug backhaul-session-manager session
To debug all the available sessions or a specified session, use the debug backhaul-session-manager session command in privileged EXEC mode. To turn off debugging, use the no form of this command.
- debug backhaul-session-manager session {state {all | session-id}} | {xport {all | session-id}} | all
- no debug backhaul-session-manager session
|
Caution Use caution when enabling this debug command in a live system. This command produces large amounts of output which could lead to a disruption of service. |
Syntax Description
state
|
Shows information about state transitions. Possible states are as follows:
SESS_SET_IDLE—A session-set has been created.
SESS_SET_OOS—A session has been added to a session-group. No ACTIVE notification has been received from the Cisco VSC3000.
SESS_SET_ACTIVE_IS—An ACTIVE notification has been received over one in-service session-group. STANDBY notification has not been received on any available session-group.
SESS_SET_STNDBY_IS—A STANDBY notification is received, but there is no in-service active session-group available.
SESS_SET_FULL_IS—A session-group is in-service that has ACTIVE notification and at least one session-group is in service that has STANDBY notification.
SESS_SET_SWITCH_OVER—An ACTIVE notification is received on an in-service session-group that had received STANDBY notification.
|
all
|
All available sessions.
|
session-id
|
A specified session.
|
xport
|
Provides traces for all PDUs (packets), application PDUs, and also session-manager messages.
Use caution while enabling this debug command in a live system.
|
|
Command Modes
Privileged EXEC
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example shows output for the debug backhaul-session-manager session all command.
Router#
debug backhaul-session-manager session all
Router# debug_bsm_command:DEBUG_BSM_SESSION_ALL
23:49:14:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)
23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE
23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT
23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:19:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)
23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE
23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT
23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:24:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)
23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE
23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT
23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:29:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)
23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE
23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT
23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:34:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)
23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE
23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT
23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:49:34:SESSION:XPORT:sig rcvd. session = 33, connid = 0x80BA14EC, sig = 1 (CONN-FAILED)
23:49:34:SESSION:STATE:(33) old-state:OPEN, new-state:CLOSE_WAIT
The following example shows output for the debug backhaul-session-manager session state all command.
Router#
debug backhaul-session-manager session state all
Router# debug_bsm_command:DEBUG_BSM_SESSION_STATE_ALL
23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE
23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT
23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS
The following example shows output for the debug backhaul-session-manager session xport all command.
Router#
debug backhaul-session-manager session xport all
Router# debug_bsm_command:DEBUG_BSM_SESSION_XPORT
23:51:39:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)
23:51:42:SESSION:XPORT:sig rcvd. session = 33, connid = 0x80BA14EC, sig = 5 (CONN-RESET)
23:51:44:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)
Related Commands
Command |
Description |
debug backhaul-session- manager set
|
Traces state changes and receives messages and events for all available session-sets or a specified session-set.
|
|
debug backhaul-session-manager set
To trace state changes and receive messages and events for all the available session-sets or a specified session-set, use the debug backhaul-session-manager set command in privileged EXEC mode. To turn off debugging, use the no form of this command.
- debug backhaul-session-manager set {all | name set-name}
- no debug backhaul-session-manager set
Syntax Description
all
|
All available session-sets.
|
name set-name
|
A specified session-set.
|
|
Command Modes
Privileged EXEC
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example shows output for the debug backhaul-session-manager set all command:
Router#
debug backhaul-session-manager set all
Router# debug_bsm_command:DEBUG_BSM_SET_ALL
Function set_proc_event() is called
BSM:Event BSM_SET_UP is sent to user
New State :BSM_SET_ACTIVE_IS
Event rcvd :BSM_ACTIVE_TYPE
The following example shows output for the debug backhaul-session-manager set command for the session-set named set1:
Router#
debug backhaul-session-manager set name set1
Router# debug_bsm_command:DEBUG_BSM_SET_NAME
Router# Function set_proc_event() is called
Router#BSM:Event BSM_SET_UP is sent to user
New State :BSM_SET_ACTIVE_IS
Event rcvd :BSM_ACTIVE_TYPE
Related Commands
Command |
Description |
debug backhaul-session- manager session
|
Debugs all available sessions or a specified session.
|
|
debug rudpv1
For debug information for RUDP, use the debug rudpv1 command in privileged EXEC mode. To turn off debugging, use the no form of this command.
- debug rudpv1 {application | performance | retransmit | segment | signal | state | timer | transfer}
- no debug rudpv1
|
Caution Use this command only during times of low traffic. |
Syntax Description
application
|
Application debugging.
|
performance
|
Performance debugging.
|
retransmit
|
Retransmit/soft reset debugging.
|
segment
|
Segment debugging.
|
signal
|
Signals sent to applications.
|
state
|
State transitions.
|
timer
|
Timer debugging.
|
transfer
|
Transfer state information.
|
|
Command Modes
Privileged EXEC
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example shows output for the debug rudpv1 application command:
Router#
debug rudpv1 application
Rudpv1: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 29
The following example shows output for the debug rudpv1 performance command:
Router#
debug rudpv1 performance
Rudpv1:Turning performance debugging on
*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: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: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
The following example shows output for the debug rudpv1 retransmit command:
Router#
debug rudpv1 retransmit
Rudpv1: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.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: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:Retrans timer, set to ack 222
*Jan 1 00:53:02.415:Retrans timer, set to ack 225
The following example shows output for the debug rudpv1 segment command:
Router#
debug rudpv1 segment
Rudpv1: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 example shows output for the debug rudpv1 signal command:
Router#
debug rudpv1 signal
Rudpv1: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:Rudpv1:Sent CONN_TRANS_STATE to connID 61F72B6C, sess 34
*Jan 1 00:39:59.551:Rudpv1:Sent CONN_TRANS_STATE to connID 61F72DAC, sess 33
*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:40:00.739:%LINK-5-CHANGED:Interface FastEthernet0, changed state
*Jan 1 00:40:01.739:%LINEPROTO-5-UPDOWN:Line protocol on Interface
FastEthernet0, changed state to down
*Jan 1 00:40:04.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33
*Jan 1 00:40:05.051:Rudpv1:Clearing conn rec values, index 2, connid
*Jan 1 00:40:10.051:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33
*Jan 1 00:40:10.551:Rudpv1:Clearing conn rec values, index 2, connid
*Jan 1 00:40:15.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33
*Jan 1 00:40:16.051:Rudpv1:Clearing conn rec values, index 2, connid
*Jan 1 00:40:21.051:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33
*Jan 1 00:40:21.551:Rudpv1:Clearing conn rec values, index 2, connid
*Jan 1 00:40:25.587:%LINK-3-UPDOWN:Interface FastEthernet0, changed state
*Jan 1 00:40:26.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33
*Jan 1 00:40:26.587:%LINEPROTO-5-UPDOWN:Line protocol on Interface
FastEthernet0, changed state to up
*Jan 1 00:40:27.051:Rudpv1:Clearing conn rec values, index 2, connid
*Jan 1 00:40:28.051:Rudpv1:Sent CONN_OPEN to connID 61F72DAC, sess 33
The following example shows output for the debug rudpv1 state command:
Router#
debug rudpv1 state
Rudpv1: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 ->
*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 state
*Jan 1 00:38:38.451:%LINEPROTO-5-UPDOWN:Line protocol on Interface
FastEthernet0, 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 state
*Jan 1 00:38:57.411:%LINEPROTO-5-UPDOWN:Line protocol on Interface
FastEthernet0, changed state to up
*Jan 1 00:38:57.823:Rudpv1: (61F72DAC) State Change:SYN_SENT -> OPEN
The following example shows output for the debug rudpv1 timer command:
Router#
debug rudpv1 timer
Rudpv1: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 = 1000
The following example shows output for the debug rudpv1 transfer command:
Router#
debug rudpv1 transfer
Rudpv1: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 to
*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 new
*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 new
*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 to
*Jan 1 00:37:30.567:Rudpv1:Send window 2 .. 4
Related Commands
Command |
Description |
clear rudpv1 statistics
|
Clears RUDP statistics and failure counters.
|
show rudpv1
|
Displays RUDP failures, parameters, and statistics.
|
|
group auto-reset
To specify the maximum number of auto-resets for a session group, use the group auto-reset command in backhaul session manager configuration mode. To restore the default number, use the no form of this command.
- group grp-name auto-reset count
- no group grp-name auto-reset
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
grp-name
|
Session-group name.
|
count
|
Maximum number of auto-resets before the connection is considered failed. The range is from 0 to 255. The default is 5.
|
|
Defaults
5 auto-resets
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example specifies a maximum of six auto-resets for session group 5:
Router(config-bsm)#
group group5 auto-reset 6
Related Commands
Command |
Description |
group cumulative-ack
|
Configures the maximum number of segments that are received in a session group before an acknowledgment is sent.
|
group out-of-sequence
|
Configures the maximum out-of-sequence segments that are received before an error acknowledgment (EACK) is sent.
|
group receive
|
Configures the maximum number of segments in the receive window of a session group.
|
group retransmit
|
Configures the maximum number of retransmits.
|
|
group cumulative-ack
To configure the maximum number of segments that are received in a session group before an acknowledgment is sent, use the group cumulative-ack command in backhaul session manager configuration mode. To restore the default number, use the no form of this command.
- group grp-name cumulative-ack count
- no group grp-name cumulative-ack
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
grp-name
|
Session-group name.
|
count
|
Maximum number of segments received before acknowledgment. The range is from 0 to 255. The default is 3.
|
|
Defaults
3 segments
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example configures session group 5 to send acknowledgment after four segments have been received:
Router(config-bsm)#
group group5 cumulative-ack 4
Related Commands
Command |
Description |
group auto-reset
|
Specifies the maximum number of auto-resets for a session group.
|
group out-of-sequence
|
Configures the maximum out-of-sequence segments that are received before an error acknowledgment (EACK) is sent.
|
group receive
|
Configures the maximum number of segments in the receive window of a session group.
|
group retransmit
|
Configures the maximum number of retransmits.
|
|
group out-of-sequence
To configure the maximum number of out-of-sequence segments that can be received in a session group before an acknowledgment (ACK) is sent, use the group out-of-sequence command in backhaul session manager configuration mode. To restore the default number, use the no form of this command.
- group grp-name out-of-sequence count
- no group grp-name out-of-sequence
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
grp-name
|
Session-group name.
|
count
|
Maximum number of out-of-sequence segments that can be received in a session-group before an ACK is sent. The range is from 0 to 255. The default is 3.
|
|
Defaults
3 segments
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example configures session group 5 to send acknowledgment after four out-of-sequence segments have been received:
Router(config-bsm)#
group group5 out-of-sequence 4
Related Commands
Command |
Description |
group auto-reset
|
Specifies the maximum number of auto-resets for a session group.
|
group cumulative-ack
|
Configures the maximum number of segments that are received in a session group before an acknowledgment is sent.
|
group receive
|
Configures the maximum number of segments in the receive window of a session group.
|
group retransmit
|
Configures the maximum number of retransmits.
|
|
group receive
To configure the maximum number of segments in the receive window of a session group, use the group receive command in backhaul session manager configuration mode. To restore the default number, use the no form of this command.
- group grp-name receive count
- no group grp-name receive
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
grp-name
|
Session-group name.
|
count
|
Maximum number of segments in the receive window of the media gateway. This is the maximum number of segments the media gateway is allowed to receive before it sends an ACK.
The range is from 1 to 64. The default is 32.
|
|
Defaults
32 segments
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example configures session group 5 to receive a maximum of 10 segments before the Cisco VSC3000 receives an acknowledgment:
Router(config-bsm)#
group group5 receive 10
Related Commands
Command |
Description |
group auto-reset
|
Specifies the maximum number of auto-resets for a session group.
|
group cumulative-ack
|
Configures the maximum number of segments that are received in a session group before an acknowledgment is sent.
|
group out-of-sequence
|
Configures the maximum number of out-of-sequence segments that are received before an ACK is sent.
|
group retransmit
|
Configures the maximum number of retransmits.
|
|
group retransmit
To configure the maximum number of retransmits in a session group, use the group retransmit command in backhaul session manager configuration mode. To restore the default number, use the no form of this command.
- group grp-name retransmit count
- no group grp-name retransmit
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
grp-name
|
Session-group name.
|
count
|
Maximum number of retransmits allowed in a session group. The range is from 0 to 255. The default is 2.
|
|
Defaults
2 retransmits
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example configures session group 5 to allow as many as 3 retransmits:
Router(config-bsm)#
group group5 retrans 3
Related Commands
Command |
Description |
group auto-reset
|
Specifies the maximum number of auto-resets for a session group.
|
group cumulative-ack
|
Configures the maximum number of segments that are received in a session group before an acknowledgment is sent.
|
group out-of-sequence
|
Configures the maximum number of out-of-sequence segments that are received before an ACK is sent.
|
group receive
|
Configures the maximum number of segments in the receive window of a session group.
|
|
group set
To create a session-group and associate it with a specified session-set, use the group command in backhaul session manager configuration mode. To delete the group, use the no form of this command.
- group grp-name set set-name
- no group grp-name
Syntax Description
grp-name
|
Session-group name.
|
set-name
|
Session-set name.
|
|
Defaults
No default behavior or values.
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example associates session-group group5 with session-set set1:
Router(config-bsm)#
group group5 set set1
Related Commands
Command |
Description |
group auto-reset
|
Specifies the maximum number of auto-resets for a session group.
|
group cumulative-ack
|
Configures the maximum number of segments that are received in a session group before an acknowledgment is sent.
|
group out-of-sequence
|
Configures the maximum out-of-sequence segments that are received before an error acknowledgment (EACK) is sent.
|
group receive
|
Configures the maximum number of segments in the receive window of a session group.
|
group retransmit
|
Configures the maximum number of retransmits.
|
group timer cumulative-ack
|
Configures cumulative acknowledgment timeout.
|
group timer keepalive
|
Configures keepalive (or null segment) timeout.
|
group timer retransmit
|
Configures retransmission timeout.
|
group timer transfer
|
Configures state transfer timeout.
|
group auto-reset
|
Specifies the maximum number of auto-resets for a session group.
|
|
group timer cumulative-ack
To configure the maximum number of milliseconds Reliable User Datagram Protocol (RUDP) delays before sending an acknowledgment for a received segment, use the group timer cumulative-ack command in backhaul session manager configuration mode. To restore the default value, use the no form of this command.
- group group-name timer cumulative-ack time
- no group group-name timer cumulative-ack
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
group-name
|
Session-group name.
|
time
|
Number of milliseconds that RUDP delays before sending an acknowledgment for a received segment. The range is from 100 to 65535. The default is 100.
|
|
Defaults
100 milliseconds
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example specifies 325 milliseconds as the maximum acknowledgment delay for session group 5:
Router(config-bsm)#
group group5 timer cumulative-ack 325
Related Commands
Command |
Description |
group timer keepalive
|
Configures keepalive (or null segment) timeout.
|
group timer retransmit
|
Configures retransmission timeout.
|
group timer transfer
|
Configures state transfer timeout.
|
|
group timer keepalive
To configure the number of milliseconds that Reliable User Datagram Protocol (RUDP) waits before sending a keepalive segment, use the group timer keepalive command in backhaul session manager configuration mode. To restore the default value, use the no form of this command.
- group grp-name timer keepalive time
- no group grp-name timer keepalive
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
grp-name
|
Session-group name.
|
time
|
Number of milliseconds before RUDP sends a keepalive segment when no RUDP packets are received or sent. The range is from 100 to 65535. The default is 1000.
|
|
Defaults
1000 milliseconds
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example configures RUDP to send keepalive segments if no RUDP packets are received or sent for 2.5 seconds (2500 milliseconds) in session group 5.
Router(config-bsm)#
group group5 timer keepalive 2500
Related Commands
Command |
Description |
group timer cumulative-ack
|
Configures cumulative acknowledgment timeout.
|
group timer retransmit
|
Configures retransmission timeout.
|
group timer transfer
|
Configures state transfer timeout.
|
|
group timer retransmit
To configure the number of milliseconds that Reliable User Datagram Protocol (RUDP) waits to receive an acknowledgment for a segment before retransmitting the segment, use the group timer retransmit command in backhaul session manager configuration mode. To restore the default value, use the no form of this command.
- group grp-name timer retransmit time
- no group grp-name timer retransmit
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
grp-name
|
Session-group name.
|
time
|
Number of milliseconds RUDP waits before retransmitting the segment. The range is from 100 to 65535. The default is 300.
|
|
Defaults
300 milliseconds
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Usage Guidelines
The retransmit timer must be greater than the cumulative-ack timer set using the group timer cumulative-ack command.
Examples
The following example sets a retransmit time of 650 milliseconds for session group 5:
Router(config-bsm)#
group group5 timer retransmit 650
Related Commands
Command |
Description |
group timer cumulative-ack
|
Configures cumulative acknowledgment timeout.
|
group timer keepalive
|
Configures keepalive (or null segment) timeout.
|
group timer transfer
|
Configures state transfer timeout.
|
|
group timer transfer
To configure the number of milliseconds Reliable User Datagram Protocol (RUDP) will wait for a transfer request, use the group timer transfer command in backhaul session manager configuration mode. To restore the default value, use the no form of this command.
- group grp-name timer transfer time
- no group grp-name timer transfer
|
Caution Do not change this parameter unless instructed to do so by Cisco technical support. There are relationships between group parameters that can cause sessions to fail if not set correctly. |
Syntax Description
grp-name
|
Session-group name.
|
time
|
The number of milliseconds RUDP waits to receive a selection of a new session from the application during a transfer state. The range is from 0 to 65535. The default is 600.
|
|
Defaults
600 milliseconds
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example sets a state transfer time of 1800 milliseconds for session group 5:
Router(config-bsm)#
group group5 timer transfer-state 1800
Related Commands
Command |
Description |
group timer cumulative-ack
|
Configures cumulative acknowledgment timeout.
|
group timer keepalive
|
Configures keepalive (or null segment) timeout.
|
group timer retransmit
|
Configures retransmission timeout.
|
|
isdn bind-L3
To configure an ISDN D-channel serial interface for signaling backhaul and associate it with a session-set, use the isdn bind-L3 interface configuration command. To disable signaling backhaul on an ISDN D-channel serial interface, use the no form of this command.
- isdn bind-L3 set-name
- no isdn bind-L3
|
Note In the command, the capital "L" is shown here for clarity. You can enter a lowercase "l".
|
Syntax Description
set-name
|
Specifies the session-set with which you are associating this D-channel interface.
|
|
Defaults
The ISDN D-channel is not configured for signaling backhaul and not associated with a session-set.
Command Modes
Interface configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example configures T1 signaling channel serial 0:23 for signaling backhaul and associates the D-channel with the session-set named Set1:
Router(config)#
interface s0:23
Router(config-if)#
isdn bind-L3 set1
The following example configures E1 signaling channel serial 0:15 for signaling backhaul and associates the D-channel with the session-set named Set3:
Router(config)#
interface s0:15
Router(config-if)#
isdn bind-L3 set3
isdn protocol-emulate
To configure an ISDN D-channel serial interface to emulate the network side or user side protocol of an ISDN configuration for a Net5 switch type, use the isdn protocol-emulate command in interface configuration mode. To restore the default emulation configuration, use the no form of this command.
- isdn protocol-emulate {network | user}
- no isdn protocol-emulate
Syntax Description
network
|
The network side of an ISDN configuration.
|
user
|
The user side of an ISDN configuration.
|
|
Defaults
ISDN D-channel serial interfaces emulate the user side protocol of an ISDN configuration for a Net5 switch type.
Command Modes
Interface configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Usage Guidelines
The current ISDN signaling stack can emulate the ISDN network side, but it does not conform to the specifications of the various switch types when emulating the network side. This command enables the Cisco IOS software to replicate the public switched network interface to a PBX. This feature is supported only for the PRI Net5 switch type.
Examples
The following example configures T1 signaling channel serial 0:23 (configured for Net5) to emulate the network-side ISDN:
Router(config)#
interface s0:23
Router(config-if)#
isdn protocol-emulate network
The following example configures E1 signaling channel serial 0:15 (configured for Net5) to emulate the network-side ISDN:
Router(config)#
interface s0:15
Router(config-if)#
isdn protocol-emulate network
session group
To add a transport session to a specified session-group, use the session group command in backhaul session manager configuration mode. To delete a transport session from a specified session-group, use the no form of this command.
- session group group-name remote_ip remote_port local_ip local_port priority
- no session group group-name remote_ip remote_port local_ip local_port
Syntax Description
group-name
|
Name of the session-group to which this session is added.
|
remote_ip
|
IP address of the Cisco VSC3000 server at the remote end of this backhaul link.
|
remote_port
|
UDP port number on the Cisco VSC3000 server at the remote end of this backhaul link. The range is from 1024 to 9999.
|
local_ip
|
IP address of the media gateway port used for signaling backhaul.
|
local_port
|
UDP port number of the media gateway port used for signaling backhaul. The range is from 1024 to 9999.
|
priority
|
Priority of this session within its session-group. The range is from 0 to 9999; 0 is the highest priority.
|
|
Command Types
No default behavior or values.
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Usage Guidelines
The Cisco VSC3000 server is assumed to be located on a remote machine.
Examples
The following example adds a transport session to session-group "group 5" and specifies the remote and local IP addresses and ports, and specifies a priority of 1 within the session group:
Router(config-bsm)#
session group group5 192.168.2.72 5555 172.18.72.198 5555 1
set
To create a fault-tolerant or non-fault-tolerant session-set with the client or server option, use the set command in backhaul session manager configuration mode. To delete a session-set, use the no form of this command.
- set set-name {client | server} {ft | nft}
- no set set-name
Syntax Description
set-name
|
Session-set name.
|
client
|
The session-set operates as a client. Select this option for signaling backhaul.
|
server
|
The session-set operates as a server.
|
ft
|
Fault-tolerant operation. Select fault-tolerant if this session-set can contain more than one session-group, with each session-group connecting the gateway to a different Cisco VSC3000. Fault-tolerance allows the system to operate properly if a session-group in the session-set fails.
|
nft
|
Non-fault-tolerant operation. Select non-fault-tolerant if this session-set contains only one session-group (which connects the gateway to a single Cisco VSC3000).
|
|
Defaults
No session-set is configured.
Command Modes
Backhaul session manager configuration
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Usage Guidelines
Multiple session-groups can be associated with a session-set.
For signaling backhaul, session-sets should be configured to operate as clients.
A session-set cannot be deleted unless all session-groups associated with the session-set are deleted first.
Examples
The following example creates a session-set named "Set1", operating as a client and fault-tolerant:
Router(config-bsm)#
set set1 client ft
show backhaul-session-manager group
To display status, statistics, or configuration for session-groups, use the show backhaul-session-manager group command in privileged EXEC mode.
- show backhaul-session-manager group {status | stats | cfg} {all | name group-name}
Syntax Description
status
|
Status.
|
stats
|
Statistics.
|
cfg
|
Configuration.
|
all
|
Displays output for all configured session-groups.
|
name
|
Displays output for the designated session-group only.
|
group-name
|
Name of a session-group.
|
|
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example displays statistics for all session-groups:
Router#
show backhaul-session-manager group stats all
Session-Group grp1 statistics
Un-Successful Fail-Over attempts:0
Active Pkts receive count :0
Standby Pkts receive count :0
Total PDUs dispatch err :0
The following example displays the current configuration for all session-groups:
Router#
show backhaul-session-manager group cfg all
Dest:10.5.0.3 8304 Local:10.1.2.15 8304 Priority:0
Dest:10.5.0.3 8300 Local:10.1.2.15 8300 Priority:2
Dest:10.5.0.3 8303 Local:10.1.2.15 8303 Priority:2
timer cumulative ack :100
timer transfer state :2000
The following example displays the current state of all session-groups. This group named "grp1" belongs to the set named "set1".
The Status is either Group-OutOfService (no session in the session-group has been established) or Group-InService (at least one session in the session-group has been established).
The Status (use) is either Group-Standby (the Cisco VSC3000 connected to the other end of this session-group goes into standby mode), Group-Active (the Cisco VSC3000 connected to the other end of this session-group is the active Cisco VSC3000), or Group-None (the Cisco VSC3000 has not declared its intent).
Router#
show backhaul-session-manager group status all
Status :Group-OutOfService
Related Commands
Command |
Description |
show backhaul- session- manager set
|
Displays session-groups associated with a specific or all session-sets.
|
show backhaul- session- manager session
|
Displays status, statistics, or configuration of sessions.
|
|
show backhaul-session-manager session
To display various information for about a session or sessions, use the show backhaul-session-manager session command in privileged EXEC mode.
- show backhaul-session-manager session {all | ip ip-address}
Syntax Description
all
|
Information is displayed about all available sessions.
|
ip
|
Information is displayed about the session associated with this IP address only.
|
ip-address
|
The IP address of the local or remote session.
|
|
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release |
Modification |
12.1(1)T
|
This command was introduced on the Cisco AS5300 access server.
|
12.2(4)T
|
This command was first supported on the Cisco 2600, Cisco 3600, and Cisco MC3810 series.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850 platform.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and implemented on the Cisco VG200.
|
12.2(11)ZC
|
This command was integrated in to the Cisco IOS Release 12.2(11)ZC and implemented on the Catalyst 6500 series and Cisco 7600 series CMM.
|
|
Examples
The following example displays information for all available sessions.
The State is OPEN (the connection is established), OPEN_WAIT (the connection is waiting for establishment), OPEN_XFER (session failover is in progress for this session, which is a transient state), or CLOSE (this session is down, also a transient state).
The Use-status field indicates whether PRI signaling traffic is being transported over this session. The field is either OOS (this session is not being used to transport signaling traffic) or IS (this session is being used to transport all PRI signaling traffic). OOS does not indicate if the connection is established and IS indicates that the connection is established.
Router#
show backhaul-session-manager session all
Group:grp1 /*this session belongs to the group named 'grp1' */
Local:10.1.2.15 , port:8303
Remote:10.5.0.3 , port:8303
RUDP Option:Client, Conn Id:0x2
Status:OPEN_WAIT, Use-status:OOS, /*see explanation below */
# of unexpected RUDP transitions (total) 0
# of unexpected RUDP transitions (since last reset) 0
Receive pkts - Total:0 , Since Last Reset:0
Recieve failures - Total:0 ,Since Last Reset:0
Transmit pkts - Total:0, Since Last Reset:0
Transmit Failures (PDU Only)
Due to Blocking (Not an Error) - Total:0, Since Last Reset:0
Due to causes other than Blocking - Total:0, Since Last
Transmit Failures (NON-PDU Only)
Due to Blocking(Not an Error) - Total:0, Since Last Reset:0
Due to causes other than Blocking - Total:0, Since Last
Send window full failures:0
Resource unavailble failures:0
Related Commands