|
|
Table Of Contents
PRI/Q.931 Signaling Backhaul for Call Agent Applications
Signaling Backhaul and Backhaul Session Manager
Supported Standards, MIBs, and RFCs
Configuring Backhaul Session Manager
Configuring ISDN Signaling Backhaul
Monitoring and Maintaining Signaling Backhaul
clear backhaul-session-manager group
show backhaul-session-manager group
show backhaul-session-manager session
show backhaul-session-manager set
debug backhaul-session-manager set
debug backhaul-session-manager session
PRI/Q.931 Signaling Backhaul for Call Agent Applications
Feature History
This feature module describes the PRI/Q.931 Signaling Backhaul feature. This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
•
Feature Overview
PRI/Q.931 signaling backhaul is the ability to reliably transport the signaling (Q.931 and above layers) from a PRI trunk that is physically connected to a media gateway (for example, a Cisco AS5350 or Cisco AS5400) to a media gateway controller (Cisco VSC3000) for processing. Additionally, the Cisco VSC3000 can respond through the same interface. For the purposes of this document, the media gateway controller will be referred to as the virtual switch controller (VSC).
Figure 1 PRI Signaling Backhaul
The backhaul takes place between a media gateway and a VSC. The gateways provide an interface between the Public Switched Telephone Network (PSTN) and the packet network world (IP or ATM). The VSC provides call processing and gateway control.
The general principle behind signaling backhaul is to reliably pass as many layers of a protocol stack as possible through a gateway directly to the VSC.
Generally, signaling backhaul would occur at a common boundary for all protocols. For ISDN, the signaling backhaul will take place at the layer 2 (Q.921) and layer 3 (Q.931) boundary. The lower layers of the protocol will be terminated and processed on the gateway, while the upper layers will be backhauled to the VSC. The upper layers of the protocol are backhauled, or transported, to the VSC using Reliable User Datagram Protocol, or RUDP over IP. RUDP provides autonomous notification of connected and failed sessions, and in-sequence, guaranteed delivery of signaling protocols across an IP network. Backhaul session manager is a software function on the VSC and gateway that manages RUDP sessions. It also groups sessions between endpoints and establishes a selection priority, and collects these groups together to form a set.
Signaling backhaul provides the additional advantage of distributed protocol processing. This permits greater expandability and scalability while offloading lower layer protocol processing from the VSC.
Signaling Backhaul and Backhaul Session Manager
The backhaul session manager enables signaling applications to backhaul signaling information to a remote or local VSC, and also provides redundancy and transparent management of transport paths. To configure the backhaul session manager, you must create a new session-set, add session-groups in that session-set, and then add sessions to the session-group.
A session is an RUDP connection between two endpoints. An endpoint is defined by the IP address and the UDP port.
A session-group is a logically ordered list of sessions based on priority of the sessions. All of the sessions in the session-group must be configured to connect the same physical machines and, for reliability, these sessions can be defined to take different paths through the network. The backhaul session manager always uses the highest priority session available in the session-group to transport all PRI signaling traffic, regardless of the number of sessions configured in the session-group (note that RUDP keepalive traffic would exist on all sessions).
If the session currently being used fails, or a higher priority session within that session group gets established, backhaul session manager and RUDP support a function in which messages waiting to be transmitted on the current session are transferred to another session automatically, while maintaining guaranteed, in-sequence delivery. This is sometimes referred to as session failover. Thus, a session-group enables network path redundancy between the gateway and the VSC. A session-group cannot be deleted unless the sessions associated with it are deleted first.
A session-set is a collection of session-groups. A session-set enables VSC redundancy and is used to implement VSC switchover. A session-set cannot be deleted unless the groups associated with it are deleted first.
In a fault-tolerant configuration, a session-set on the signaling gateway (Cisco AS5350 or Cisco AS5400) can have more than one session-group, each session-group connecting the gateway to a different VSC. In non-fault-tolerant configuration, a session-set on the signaling gateway can contain only one session-group, because there is only one VSC available.
Note that each session-set on the VSC will always have one session-group, regardless of the configuration being used.
Benefits
Call Control
Signaling backhaul integrates gateways into a virtual switch with the call control centralized in the Cisco VSC.
Signaling Protocols
This feature provides the infrastructure to support the backhaul of the ISDN signaling protocol in a non-fault tolerant manner.
Restrictions
This feature supports FAS and NFAS PRI D-Channel signaling only. No other signaling protocols are supported. NFAS with backup D-channel signaling is not supported.
Related Documents
•
•
•
•
•
•
•
•
•
Supported Platforms
•
•
•
•
Table 1 lists the hardware platforms that support this feature, and the releases in which this feature was first supported.
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Supported Standards, MIBs, and RFCs
Standards
There are no new or modified standards for this feature.
MIBs
There are no new or modified MIBs for this feature.
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
There are no new or modified RFCs for this feature.
Prerequisites
Voice and modem functions are provided by the Universal Port Dial Feature card. See the Cisco AS5400 Card Installation Guide for more information.
•
•
Configuration Tasks
Perform the following three tasks to configure PRI signaling backhaul.
•
•
Caution
Configuring Backhaul Session Manager
The backhaul session manager enables signaling applications to backhaul signaling information to a remote or local virtual switch controller (VSC), and also provides redundancy and transparent management of transport paths.
To configure the backhaul session manager, complete the following steps in the following order in global configuration mode:
•
•
•
Create a New Session-Set
Step 1
Router(config)# backhaul-session-manager
Enters backhaul session manager configuration mode.
Step 2
Router(config-bsm)# ?
default Set a command to its defaults
exit Leave BSM config mode
group Specify the Session-Group name
help Description of the interactive help system
no Negate a command or set its defaults
session Specify the Session info
set Specify the Session-Set name
Shows backhaul session manager choices.
Step 3
Router(config-bsm)#
set ?WORD set-name
Router(config-bsm)# set set-name
Adds the new Session-Set.
Step 4
Router(config-bsm)# set set-name client ?
ft Specify the Session-Set Mode to Fault-Tolerant
nft Specify the Session-Set Mode to Non-Fault-Tolerant
Router(config-bsm)# set set-name client ft
Sets the Session-Set to fault-tolerant. Fault tolerance is the level of ability within a system to operate properly even if a group in the set fails.
Note
Add Session-Groups in the Session-Set
Add Sessions to the Session-Group
Repeat the preceding steps to add a second group of sessions for fault-tolerant configuration.
Caution
Change Default Values of Session-Group Parameters (optional)
Configuring ISDN Signaling Backhaul
You must configure ISDN in order to backhaul Q.931 signaling to the VSC.
Configuring the VSC
The Cisco VSC3000 is the signaling controller software, which provides call control, installed on, for example, a Sun Netra 1800. Man Machine Language (MML) is the user interface into the signaling controller software. You use this interface to configure parameters of your signaling controller software and to display information about the current settings.
To configure the VSC to perform signaling backhaul, do the following steps:
Note
Step 1
mml> prov-add:extnode:name="va-5400-6",
desc="AS-5400-6-Spans"Defines the media gateway, or the external node.
Step 2
mml> prov-add:ipfaspath:name="bh6NI2",
extnode="va-5400-6",mdo="BELL_1268",
custgrpid="1111",side="network",desc="Backhaul
service to AS-5400-6"Defines the PRI backhaul service (ipfaspath), the ISDN variant (NI2), customer group ID, or which dial plan to use for this connection (1111), the PRI (network and not user), and optional description (Backhaul service to AS-5400-6).
Step 3
mml> prov-add:iplnk:name="iplink6N",if="enif1",
ipaddr="IP_Addr1",port=5555,pri=1,
peeraddr="172.18.72.198",peerport=5555,sigslot=0,
sigport=0,svc="bh6NI2",desc="IP link-backhaul svc
NAS 5400-6"Defines the IP network connection to the backhaul service, the ethernet interface name for the VSC ethernet card (enif1), "IP_Addr1" as defined in ../etc/XECfgParm.dat, the port number used by the VSC (7007), the IP link priority, (1) the media gateway's IP address (172.18.72.198), the media gateway's IP port (7007), the media gateway's PRI physical card slot (0), the media gateway's PRI port or the T1/E1 controller number (0), the ipfas service, which matches the name in Step 2, and an optional description (IP link-backhaul svc NAS 5400-6).
Note
Step 4
mml>prov-add:mgcppath:name="mgcp54006",
extnode="va-5400-6",desc="MGCP service
to AS-5400-6"Defines the MGCP signaling service. This maps to the same external node name as for IPFASPATH (Step 2).
Step 5
mml>prov-add:iplnk:name="clink6",if="enif1",
ipaddr="IP_Addr1",port=2427,peeraddr=
"172.18.72.198",peerport=2427,svc="mgcp54006",
pri=1,desc="MGCP link to AS-5400-6"Defines the IP network connection to the MGCP signaling service. Defines the ethernet interface name for the VSC ethernet card (enif1), "IP_Addr1" as defined in ../etc/XECfgParm.dat, the port used by the VSC (2427), the media gateway's IP address (172.18.72.198), the media gateway's IP port (2427), the name for MGCP signaling service (mgcp54006), the IP link priority (1), and the optional description (MGCP link to AS-5400-6).
Note
Verifying Configuration
Step 1
In the example below, notice that the Layer 2 protocol is Q.921, and the Layer 3 protocol is BACKHAUL. This verifies that it is configured to backhaul ISDN. Also, if you are connected to a live line, you should see Layer 1 status is active, and layer 2 state is MULTIPLE_FRAME_ESTABLISHED. This means that the ISDN line is up and active.
Router# show isdn status*00:03:34.423 UTC Sat Jan 1 2000Global ISDN Switchtype = primary-net5ISDN Serial1:23 interfacedsl 0, interface ISDN Switchtype = primary-net5L2 Protocol = Q.921 L3 Protocol(s) = BACKHAULLayer 1 Status:ACTIVELayer 2 Status:TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:NLCB:callid=0x0, callref=0x0, state=31, ces=0 event=0x0NLCB:callid=0x0, callref=0x0, state=0, ces=1 event=0x00 Active Layer 3 Call(s)Activated dsl 0 CCBs = 0Number of active calls = 0Number of available B-channels = 23Total Allocated ISDN CCBs = 0Router#Step 2
Router# show backhaul-session-manager set allSession-SetName :set1State :BSM_SET_OOSMode :Fault-Tolerant(FT)Option :Option-ClientGroups :1statisticsSuccessful switchovers:0Switchover Failures:0Set Down Count 0Group:grp1Possible states are:
SESS_SET_IDLE: A session-set has been created.
SESS_SET_OOS: A session(s) has been added to session-group(s). No ACTIVE notification has been received from VSC.
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(s).
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 in-service that has ACTIVE notification and at least one session-group in-service that has STANDBY notification.
SESS_SET_SWITCH_OVER: An ACTIVE notification is received on session-group in-service, which had received STANDBY notification.
Step 3
The Status will be either Group-OutOfService (no session in the group has been established) or Group-Inservice (at least one session in the group has been established).
The Status(use) will be either Group-Standby (the VSC connected to the other end of this group will go into standby mode), Group-Active (the VSC connected to the other end of this group will be the active VSC), or Group-None (the VSC has not declared its intent yet).
Router# show backhaul-session-manager group status allSession-GroupGroup Name :grp1Set Name :set1Status :Group-OutOfServiceStatus (use) :Group-NoneStep 4
The State will be OPEN (the connection is established), OPEN_WAIT (the connection is awaiting 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 session will move to OPEN_WAIT after waiting a fixed amount of time.
The Use-status field indicates whether PRI signaling traffic is currently being transported over this session. The field will be either OOS (this session is not being used to transport signaling traffic) or IS (this session is being used currently to transport all PRI signaling traffic). The User-status field indicates the connection status.
Router# show backhaul-session-manager session allSession information --Session-id:35Group:grp1Configuration:Local:10.1.2.15 , port:8303Remote:10.5.0.3 , port:8303Priority:2RUDP Option:Client, Conn Id:0x2State:Status:OPEN_WAIT, Use-status:OOSStatistics:# of resets:0# of auto_resets 0# of unexpected RUDP transitions (total) 0# of unexpected RUDP transitions (since last reset) 0Receive pkts - Total:0 , Since Last Reset:0Recieve failures - Total:0 ,Since Last Reset:0Transmit pkts - Total:0, Since Last Reset:0Transmit Failures (PDU Only)Due to Blocking (Not an Error) - Total:0, Since Last Reset:0Due to causes other than Blocking - Total:0, Since LastReset:0Transmit Failures (NON-PDU Only)Due to Blocking(Not an Error) - Total:0, Since Last Reset:0Due to causes other than Blocking - Total:0, Since LastReset:0RUDP statisticsOpen failures:0Not ready failures:0Conn Not Open failures:0Send window full failures:0Resource unavailble failures:0Enqueue failures:0
Monitoring and Maintaining Signaling Backhaul
Use the following commands to monitor and maintain this feature.
Configuration Examples
This section provides the following configuration examples:
Fast Ethernet
In the following example, the Fast Ethernet interface is configured to not have auto negotiation configured:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# int f0Router(config-if)# duplex ?auto Enable AUTO duplex configurationfull Force full duplex operationhalf Force half-duplex operationRouter(config-if)# duplex fullRouter(config-if)#Router(config-if)# speed ?10 Force 10 Mbps operation100 Force 100 Mbps operationauto Enable AUTO speed configurationRouter(config-if)# speed 10Router(config-if)# ^ZRouter#Command Reference
This section documents new commands associated with the signaling backhaul feature. All other commands used with this feature are documented in the Cisco IOS Release 12.1(1)T command references.
•
•
•
•
•
•
•
backhaul-session-manager
To enter backhaul session manager configuration mode, use the backhaul-session-manager command in global configuration mode.
backhaul-session-manager
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Global configuration mode
Command History
Examples
Enter backhaul-session-manager configuration mode using this example:
Router(config)# backhaul-session-managerRouter(config-bsm)#clear backhaul-session-manager group
To reset the statistics or traffic counters for a specified session-group, use the clear backhaul-session-manager group command in privileged EXEC mode.
clear backhaul-session-manager group stats {all | name group-name}
Syntax Description
Defaults
The statistical information accumulates.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A session is the connection between a client and a server, and a session-group is a collection of sessions in a group to implement switchover in case of a session failure. This command clears all statistics.
Examples
To clear all statistics for all available session-groups, see the following example:
Router# clear backhaul-session-manager group stats allRelated Commands
show backhaul-session-manager group
Displays status, statistics, or configuration of a specified or all session-groups.
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
Usage Guidelines
This command clears all statistics.
Examples
To clear all RUDP statistics for all available session-groups, see this example:
Router# clear rudpv1 statisticsRelated Commands
debug rudpv1
Displays debugging information for RUDP.
show rudpv1
Displays RUDP statistics.
group auto-reset
To configure the maximum auto-reset value, use the group auto-reset command in backhaul session manager configuration mode. To set the value to default, use the no form of this command.
group grp-name auto-reset count
no group grp-name auto-reset count
Caution
Syntax Description
Defaults
5
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To configure the maximum auto-reset value for the group named Group5 to 6, see the following example:
Router(config-bsm)# group group5 auto-reset 6Related Commands
group cumulative-ack
To configure maximum cumulative acknowledgments, use the group cumulative-ack command in backhaul session manager configuration mode. Maximum cumulative acknowledgments are the maximum number of segments that are received before an acknowledgment is sent. To set the value to default, use the no form of this command.
group grp-name cumulative ack count
no group grp-name cumulative ack count
Caution
Syntax Description
grp-name
Session-group name.
count
Maximum number of segments received before acknowledgment. Range is 0 through 255.
Defaults
3
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To set the cumulative acknowledgment maximum for Group5 to 4, see the following example:
Router(config-bsm)# group group5 cumulative-ack 4Related Commands
group out-of-sequence
To configure maximum out-of-sequence segments that are received before an EACK is sent, use the group out-of-sequence command in backhaul session manager configuration mode. To set the value to default, use the no form of this command.
group grp-name out-of-sequence count
no group grp-name out-of-sequence count
Caution
Syntax Description
grp-name
Session-group name.
count
Maximum number of out-of-sequence segments. Range is 0 through 255.
Defaults
3
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To set the out-of-sequence maximum for Group5 to 4, see the following example:
Router(config-bsm)# group group5 out-of-sequence 4Related Commands
group receive
To configure maximum receive segments, use the group receive command in backhaul session manager configuration mode. To set the value to default, use the no form of this command.
group grp-name receive count
no group grp-name receive count
Caution
Syntax Description
Defaults
32
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To set the receive maximum to 10 for Group5, see the following example:
Router(config-bsm)# group group5 receive 10Related Commands
group retransmit
To configure maximum retransmits, use the group retransmit command in backhaul session manager configuration mode. To set the value to default, use the no form of this command.
group grp-name retransmit count
no group grp-name retransmit count
Caution
Syntax Description
Defaults
2
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To set the retransmit maximum for Group5 to 3, see the following example:
Router(config-bsm)# group group5 retrans 3Related Commands
group
To create a session-group and associate it to 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 set set-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To associate the group named Group5 with the set named Set1, see the following example:
Router(config-bsm)# group group5 set set1Related Commands
group timer cumulative-ack
To configure cumulative acknowledgment timeout, use the group timer cumulative ack command in backhaul session manager configuration mode. Cumulative acknowledgment timeout is the maximum number of milliseconds RUDP will delay before sending an acknowledgment for a received segment. To set the value to default, use the no form of this command.
group group-name timer cumulative ack time
no group group-name timer cumulative ack time
Caution
Syntax Description
group-name
Session-group name.
time
Number of milliseconds RUDP will delay. Range is 100 through 65535.
Defaults
100
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To set the cumulative acknowledgment timer for Group5 to 325, see the following example:
Router(config-bsm)# group group5 timer cumulative-ack 325Related Commands
group timer keepalive
To configure keepalive (or null segment) timeout, use the group timer keepalive command in backhaul session manager configuration mode. Keepalive timeout is the number of milliseconds RUDP will wait before sending a keepalive segment. To set the value to default, use the no form of this command.
group grp-name timer keepalive time
no group grp-name timer keepalive time
Caution
Syntax Description
grp-name
Session-group name.
time
Number of milliseconds before RUDP sends a keepalive segment. Range is 100 through 65535.
Defaults
1000
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To configure the keepalive timer for Group5 to 2050 milliseconds, see the following example:
Router(config-bsm)# group group5 timer keepalive 2050Related Commands
group timer retransmit
To configure retransmission timeout, use the group timer retransmit command in backhaul session manager configuration mode. Retransmission timeout is the number of milliseconds RUDP will wait to receive an acknowledgment for a segment. To set the value to default, use the no form of this command.
group grp-name timer retransmit time
no group grp-name timer retransmit time
Caution
Syntax Description
grp-name
Session-group name.
time
Number of milliseconds RUDP will delay. Range is 100 through 65535.
Defaults
300
Command Modes
Backhaul session manager configuration mode
Command History
Usage Guidelines
The retransmit timer must be greater than the cumulative-ack timer.
Examples
To set the retransmit timer for Group5 to 650, see the following example:
Router(config-bsm)# group group5 timer retransmit 650Related Commands
group timer transfer
To configure state transfer timeout, use the group timer transfer command in backhaul session manager configuration mode. To set the value to default, use the no form of this command.
group grp-name timer transfer time
no group grp-name timer transfer time
Caution
Syntax Description
grp-name
Session-group name.
time
Maximum number of milliseconds RUDP will wait for a transfer request. The range is 0 to 65535 milliseconds.
Defaults
2000
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To set the state transfer timer for Group5 to 1800, see the following example:
Router(config-bsm)# group group5 timer transfer-state 1800Related Commands
isdn bind-l3
To configure the ISDN serial interface for backhaul, use the isdn bind-l3 command in interface configuration mode. To disable, use the no form of this command.
isdn bind-l3 set-name
no isdn bind-l3 set-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration mode
Command History
Examples
To configure the ISDN serial interface for backhaul for the set named Set1, see the following example:
Router(config-if)# isdn bind-l3 set1isdn protocol-emulate
To emulate the network side of an ISDN configuration for a Net5 switch type, use the isdn protocol-emulate interface configuration command in interface configuration mode. To disable, use the no form of this command.
isdn protocol-emulate {network | user}
no isdn protocol-emulate {network | user}
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration mode
Command History
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 in emulating the network side. This command enables the Cisco IOS software to replicate the public switched network interface to a PBX. This feature is only supported for the PRI Net5 switch type.
Examples
To configure the interface (configured for Net5) to emulate the network side ISDN, see the following example:
Router(config)# int s0:15Router(config-if)# isdn protocol-emulate networksession
Use the session command in backhaul session manager configuration mode to associate a transport session with a specified session-group. It is assumed that the server is located on a remote machine. To delete the session, 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 priority
Syntax Description
Command Types
No default behavior or values
Command Modes
Backhaul session manager configuration mode
Command History
Examples
To associate a transport session with the session-group Group5 and specify the parameters described above, see the following example:
Router(config-bsm)# session group group5 161.44.2.72 5555 172.18.72.198 5555 1set
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 the set, use the no form of this command.
set set-name {client | server} {ft | nft}
no set set-name{client | server} {ft | nft}
Syntax Description
Defaults
No default behavior or values
Command Modes
Backhaul session manager configuration mode
Command History
Usage Guidelines
There can be multiple groups associated with a session-set.
The session-set should only be configured for the client for backhaul (not the server).
A set cannot be deleted unless the groups associated with the set are deleted first.
Examples
To specify the client set named Set1 to fault-tolerant, see the following example:
Router(config-bsm)# set set1 client ftshow backhaul-session-manager group
To display status, statistics, or configuration for all available 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
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following displays statistics for all session-groups:
Router# show backhaul-session-manager group stats allSession-Group grp1 statisticsSuccessful Fail-Overs :0Un-Successful Fail-Over attempts:0Active Pkts receive count :0Standby Pkts receive count :0Total PDUs dispatch err :0The following displays the current configuration for all session-groups:
Router# show backhaul-session-manager group cfg allSession-GroupGroup Name :grp1Set Name :set1Sessions :3Dest:10.5.0.3 8304 Local:10.1.2.15 8304 Priority:0Dest:10.5.0.3 8300 Local:10.1.2.15 8300 Priority:2Dest:10.5.0.3 8303 Local:10.1.2.15 8303 Priority:2RUDP Optionstimer cumulative ack :100timer keepalive :1000timer retransmit :300timer transfer state :2000receive max :32cumulative ack max :3retrans max :2out-of-sequence max :3auto-reset max :5The following displays the current state of all session-groups. This group named grp1 belongs to the set named set1.
The Status will be either Group-OutOfService (no session in the group has been established) or Group-Inservice (at least one session in the group has been established).
The Status (use) will be either Group-Standby (the VSC connected to the other end of this group will go into standby mode), Group-Active (the VSC connected to the other end of this group will be the active VSC), or Group-None (the VSC has not declared its intent yet).
Router# show backhaul-session-manager group status allSession-GroupGroup Name :grp1Set Name :set1Status :Group-OutOfServiceStatus (use) :Group-NoneRelated Commands
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
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
To display information for all available sessions, see the following example.
The State will be OPEN (the connection is established), OPEN_WAIT (the connection is awaiting 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 session will move to OPEN_WAIT after waiting a fixed amount of time.
The Use-status field indicates whether PRI signaling traffic is currently being transported over this session. The field will be either OOS (this session is not being used to transport signaling traffic) or IS (this session is being used currently 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 allSession information --Session-id:35Group:grp1 /*this session belongs to the group named 'grp1' */Configuration:Local:10.1.2.15 , port:8303Remote:10.5.0.3 , port:8303Priority:2RUDP Option:Client, Conn Id:0x2State:Status:OPEN_WAIT, Use-status:OOS, /*see explanation below */Statistics:# of resets:0# of auto_resets 0# of unexpected RUDP transitions (total) 0# of unexpected RUDP transitions (since last reset) 0Receive pkts - Total:0 , Since Last Reset:0Recieve failures - Total:0 ,Since Last Reset:0Transmit pkts - Total:0, Since Last Reset:0Transmit Failures (PDU Only)Due to Blocking (Not an Error) - Total:0, Since Last Reset:0Due to causes other than Blocking - Total:0, Since LastReset:0Transmit Failures (NON-PDU Only)Due to Blocking(Not an Error) - Total:0, Since Last Reset:0Due to causes other than Blocking - Total:0, Since LastReset:0RUDP statisticsOpen failures:0Not ready failures:0Conn Not Open failures:0Send window full failures:0Resource unavailble failures:0Enqueue failures:0Related Commands
show backhaul-session-manager set
To display session-groups associated with a specified session-set or all session-sets, use the show backhaul-session-manager set command in privileged EXEC mode.
show backhaul-session-manager set {all | name session-set-name}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
To show session groups associated with all session-sets, see the following example:
Router# show backhaul-session-manager set allRelated Commands
show rudpv1
To display RUDP information, use the show rudpv1 command in privileged EXEC mode.
show rudpv1 {failures | parameters | statistics}
Syntax Description
failures
RUDP failure statistics.
parameters
RUDP connection parameters.
statistics
RUDP internal statistics.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example shows output for show rudpv1 failures:
Router# show rudpv1 failures**** RUDPV1 Failure Stats ****CreateBufHdrsFailure 0CreateConnRecsFailure 0CreateEventQueueFailure 0OsSpecificInitFailure 0NotReadyFailures 0OptionNotSupportedFailures 0InvalidOptionFailures 0OptionRequiredFailures 0GetConnRecFailures 0InvalidConnFailures 0EventUnavailFailures 0GetConnRecFailures 0FindConnRecFailures 0EmptyBufferSendFailures 0BufferTooLargeFailures 0ConnNotOpenFailures 0SendWindowFullFailures 0GetBufHdrSendFailures 0SendInProgressFailures 0GetDataBufFailures 0GetBufHdrFailures 0SendFailures 0SendEackFailures 0SendAckFailures 0SendSynFailures 0SendRstFailures 0SendTcsFailures 0SendNullFailures 0TimerFailures 0ApplQueueFailures 0FailedRetransmits 0IncomingPktsDropped 0CksumErrors 0UnknownRudpv1Events 0InvalidVersion 0InvalidNegotiation 0The following example shows output for show rudpv1 parameters:
Router# show rudpv1 parameters*** RUDPV1 Connection Parameters ***Next Connection Id:61F72B6C, Remote conn id 126000Conn State OPENConn Type ACTIVEAccept Negot params? YesReceive Window 32Send Window 32Receive Seg Size 384Send Seg Size 384Requested NegotiatedMax Auto Reset 5 5Max Cum Ack 3 3Max Retrans 2 2Max OutOfSeq 3 3Cum Ack Timeout 100 100Retrans Timeout 300 300Null Seg Timeout 1000 1000Trans State Timeout 2000 2000Cksum type Hdr HdrNext Connection Id:61F72DAC, Remote conn id 126218Conn State OPENConn Type ACTIVEAccept Negot params? YesReceive Window 32Send Window 32Receive Seg Size 384Send Seg Size 384Requested NegotiatedMax Auto Reset 5 5Max Cum Ack 3 3Max Retrans 2 2Max OutOfSeq 3 3Cum Ack Timeout 100 100Retrans Timeout 300 300Null Seg Timeout 1000 1000Trans State Timeout 2000 2000Cksum type Hdr HdrThe following example shows output for show rudpv1 statistics:
Router# show rudpv1 statistics*** RUDPV1 Internal Stats ****Connection ID:61F72B6C, Current State:OPENRcvdInSeq 647RcvdOutOfSeq 95AutoResets 0AutoResetsRcvd 0TotalPacketsSent 1011TotalPacketsReceived 958TotalDataBytesSent 17808TotalDataBytesReceived 17808TotalDataPacketsSent 742TotalDataPacketsReceived 742TotalPacketsRetrans 117TotalPacketsDiscarded 38Connection ID:61F72DAC, Current State:OPENRcvdInSeq 0RcvdOutOfSeq 0AutoResets 0AutoResetsRcvd 0TotalPacketsSent 75TotalPacketsReceived 75TotalDataBytesSent 0TotalDataBytesReceived 0TotalDataPacketsSent 0TotalDataPacketsReceived 0TotalPacketsRetrans 0TotalPacketsDiscarded 0Cumulative RudpV1 StatisticsNumCurConnections 2RcvdInSeq 652RcvdOutOfSeq 95AutoResets 0AutoResetsRcvd 0TotalPacketsSent 1102TotalPacketsReceived 1047TotalDataBytesSent 18048TotalDataBytesReceived 18048TotalDataPacketsSent 752TotalDataPacketsReceived 752TotalPacketsRetrans 122TotalPacketsDiscarded 38Related Commands
clear rudpv1
Clears the statistics and failure counters.
show rudpv1
Shows RUDP statistics.
Debug Commands
This section documents new debug commands for PRI signaling backhaul. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
•
•
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. 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 {all | name set-name}
Syntax Description
Defaults
Debugging for backhaul session-sets is not enabled.
Command History
Examples
The following is output for the debug backhaul-session-manager set all command:
Router# debug backhaul-session-manager set allRouter# debug_bsm_command:DEBUG_BSM_SET_ALLFunction set_proc_event() is calledSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_OOSActive-Grp :NONESession-Grp :g-11Old State :Group-NoneNew State :Group-NoneEvent rcvd :EVT_GRP_INSBSM:Event BSM_SET_UP is sent to userSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_ACTIVE_ISActive-Grp :g-11Session-Grp :g-11Old State :Group-NoneNew State :Group-ActiveEvent rcvd :BSM_ACTIVE_TYPEThe following is output for the debug backhaul-session-manager set all name test-set command:
Router# debug backhaul-session-manager set name set1Router# debug_bsm_command:DEBUG_BSM_SET_NAMERouter# Function set_proc_event() is calledSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_OOSActive-Grp :NONESession-Grp :g-11Old State :Group-NoneNew State :Group-NoneEvent rcvd :EVT_GRP_INSRouter#BSM:Event BSM_SET_UP is sent to userSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_ACTIVE_ISActive-Grp :g-11Session-Grp :g-11Old State :Group-NoneNew State :Group-ActiveEvent rcvd :BSM_ACTIVE_TYPERelated Commands
debug backhaul-session-manager session
Debugs all available sessions or a specified session.
debug backhaul-session-manager session
To debug all the available sessions or a specified session, use the debug backhaul-session-manager session command. To turn off debugging, use the no form of this command.
debug backhaul-session-manager session {state | xport} {all | session-id}
no debug backhaul-session-manager session {state | xport} {all | session-id}
Caution
Syntax Description
Defaults
Debugging for backhaul-session-manager session is not enabled.
Command History
Examples
The following is output for the debug backhaul-session-manager session all command.
Router# debug backhaul-session-manager session allRouter# debug_bsm_command:DEBUG_BSM_SESSION_ALL23: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:CLOSE23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23: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:CLOSE23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23: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:CLOSE23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23: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:CLOSE23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23: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:CLOSE23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23: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_WAITRouter# debug backhaul-session-manager session state allRouter# debug_bsm_command:DEBUG_BSM_SESSION_STATE_ALL23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOSRouter# debug backhaul-session-manager session xport allRouter# debug_bsm_command:DEBUG_BSM_SESSION_XPORT23: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
debug backhaul-session-manager set
Traces state changes and receives messages and events for all available session-sets or a specified session-set.
debug rudpv1
For debug information for RUDP, use the debug rudpv1 command. To turn off debugging, 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}
Caution
Syntax Description
Defaults
Debugging for rudpv1 is not enabled.
Command History
Examples
The following is output for 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 output for 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 output for 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 output for 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 output for 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 output for 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 output for 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 output for 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.
Glossary
Backhaul—A scheme where telephony signaling is reliably transported from a gateway to a Media Gateway Controller across a packet switched network.
Fault Tolerance—The level of ability within a system to operate properly even if errors occur.
Layer 1—This describes the Physical Layer of the OSI Reference Model defined in ITU X.200. It is responsible for the electric signal being sent and received. This can be viewed as a bit stream coming in, and going out, of the system. Scope must be considered when using this term. For example, Layer 1 on a T1 is 1.544 Mbps but Layer 1 on a DS-0 timeslot in the T1 is 64 kbps.
Layer 2—This describes the Datalink Layer of the OSI Reference Model defined in ITU X.200. It is responsible for point-to-point delivery of a PDU. Layer 2 protocols have two basic classes: reliable (meaning delivery is guaranteed or an error is reported) and unreliable (meaning delivery may not occur with no indication to the upper layers).
Layer 3—This describes the Network Layer of the OSI Reference Model defined in ITU X.200. It is responsible for the network routing and delivery of a message. Examples of Layer 3 protocols include X.25 Packet Layer Protocol and the Internet Protocol. Q.931 is not considered a Layer 3 protocol because it is not concerned with routing and delivery of a message but rather the message body itself.
MG—Media Gateway. A Media Gateway terminates facilities (trunks), packetizes the PCM stream into IP/ATM and/or forwards packets into the IP/ATM network. It performs these functions in reverse order for media streams flowing from the packet network to the PSTN.
MGC—Media Gateway Controller. A Media Gateway Controller provides call control capability to handle signaling traffic from a variety of sources. It also manages connections and resources of its Media Gateways. Can also be called a Call Agent.
MGC Switchover—The re-routing of signaling traffic by the signaling gateway as required (and requested by the MGCs) between related MGCs in the event of failure or unavailability of the currently used MGC. The traffic is re-routed from the primary MGC to the back-up MGC.
MGCP—Media Gateway Control Protocol.
NFAS—Non-Facility Associated Signaling - This is a classification of signaling protocols that provide the signaling channel in a separate physical line from the bearer channels.
PDU—Protocol Data Unit. OSI term for packet.
Q.931—Q Signaling. An inter-PBX signaling protocol for networking PBX supplementary services in a multi- or uni-vendor environment.
RUDP—Cisco Reliable UDP.
Session—A session is an RUDP connection between two endpoints. An endpoint is defined by the IPaddress and the UDP port.
Session-Group—A session-group is a logically ordered list of sessions based on priority of the sessions. All of the sessions in the session-group must be configured to connect the same physical machines.
Session-Manager—Manages all the sessions in a specific client.
Session-Set—A collection of session-groups.
SG—Signaling Gateway. A Signaling Gateway transmits and receives PSTN signaling at the edge of IP/ATM network. It backhauls the signaling to a Media Gateway Controller. The Signaling Gateway function may be co-resident with the Media Gateway function to process signaling associated with line or trunk terminations controlled by the Media Gateway.
SS7—Signaling System 7. SS7 defines the procedures for the set-up, ongoing management, and subsequent clearing of calls between telephone users. It performs these functions by exchanging telephone control messages between SS7 components that support the end-user's connection.
VoIP—Voice over IP. The ability to carry normal telephone-style voice over an IP-based internet with POTS-like functionality, reliability, and voice quality.
VSC—Virtual Switch Controller. The Cisco VSC3000 is an intelligent call agent with universal protocol support. Functioning as a "soft switch," the Cisco VSC3000 controls the packet telephony network by directing calls across broadband, multi-service packet infrastructures. As a primary component within the Cisco Open Packet Telephony architecture, it utilizes open and widely recognized industry-standard protocols and interfaces.
Posted: Thu Sep 6 04:17:23 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
