Cisco Signaling Link Terminal Command Reference

This section contains the following new or modified commands (modified commands are marked by an asterisk). All other commands used with the Cisco SLT are documented in the Cisco IOS Release 12.0 command references and feature modules.

In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.

To use this functionality, enter a show or more command followed by the pipe character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:

command | {begin | include | exclude} regular-expression

Following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears.

show atm vc | begin PeakRate

For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module CLI String Search.

clear rudpv0 statistics

To clear the counters that track RUDP statistics, type the privileged EXEC clear rudpv0 statistics command and press Enter:

Syntax Description	Default	Command Mode
This command has no arguments or keywords.	The statistical information accumulates.

clear rudpv0 statisticssm

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

The statistical information accumulates.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example clears RUDP statistics on a Cisco SLT:

Router# clear rudpv0 statistics

Related Commands

Command

Description

show rudpv0 failures

Displays RUDP information about failed connections and the reasons for them. clear rudpv0 statistics resets the counters for these statistics to 0.

show rudpv0 statistics

Displays RUDP information about number of packets sent, received, and so on. clear rudpv0 statistics resets the counters for these statistics to 0.

clear ss7 sm stats

To clear the counters that track Session Manager statistics, type the privileged EXEC clear ss7 sm stats command and press Enter:

Syntax Description	Default	Command Mode
This command has no arguments or keywords.	The statistical information accumulates.

clear ss7 sm

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

The statistical information accumulates.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example clears Session Manager statistics on a Cisco SLT:

Router # clear ss7 sm stats

Related Command

Command

Description

show ss7 sm stats

Displays Session Manager information about number of packets queued, received, and so on. The clear ss7 sm stats command resets the counters for these statistics to 0.

forward-alarms

To turn on alarm forwarding so that alarms arriving on one T1/E1 port are sent to the other port on dual-mode multiflex trunk interface cards, use the forward-alarms controller configuration command on one port.

forward-alarms

Use the no form of this command to restore the default value so that no alarms are forwarded:

no forward-alarms

When you enter this command, physical-layer alarms on the configured port are forwarded to the other port on dual-port cards, simulating a one-way repeater operation. The system forwards RAIs (remote alarm indications, Yellow Alarms), alarm indication signals (AIS, or Blue Alarms), losses of frame (LOF alarms or Red Alarms), and losses of signaling (LOS alarms or Red Alarms).

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

Alarm forwarding is disabled.

Controller configuration

Syntax Description	Default	Command Mode
This command has no arguments or keywords.	Alarm forwarding is disabled.	Controller configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example turns on alarm forwarding on controller E1 0/0 of a Cisco SLT:

Router(config)# controller e1 0/0
Router(config-controller)# forward-alarms

line-termination

Note This command applies to E1 controllers only.

To set the line termination on an E1 controller, type the line-termination controller configuration command and press Enter:

line-termination { 75-ohm | 120-ohm }

Use the no form of this command to restore the default value:

Syntax Description	Default	Command Mode
120-ohm—Matches the unbalanced twisted-pair 120-ohm interface. 75-ohm—Matches the balanced BNC 75-ohm interface.	120-ohm	Controller configuration

no line-termination sm

Syntax Description
Default
Command Mode

120-ohm—Matches the unbalanced twisted-pair 120-ohm interface.

75-ohm—Matches the balanced BNC 75-ohm interface.

120-ohm

Controller configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets controller E1 0/0 to a line-termination of 75-ohm:

Router(config)# controller e1 0/0
Router(config-controller)# line-termination 75-ohm

loopback (E1 controller)

To set the loopback method for testing the E1 interface, type the loopback controller configuration command and press Enter:

loopback {diag | local {line | payload} }

Use the no form of this command to restore the default value:

no loopback

You can use a loopback test on lines to detect and distinguish equipment malfunctions caused either by line and Channel Service Unit/Digital Service Unit (CSU/DSU) or by the interface. If correct data transmission is not possible when an interface is in loopback mode, the interface is the source of the problem.

Syntax Description
Default
Command Mode

diag—Places the interface into local diagnostic loopback mode.

local—Places the interface into local loopback mode.

line—Places the interface into external loopback mode at the line level.

payload—Places the interface into external loopback mode at the payload level.

No loopback is configured.

Controller configuration

Syntax Description	Default	Command Mode
diag—Places the interface into local diagnostic loopback mode. local—Places the interface into local loopback mode. line—Places the interface into external loopback mode at the line level. payload—Places the interface into external loopback mode at the payload level.	No loopback is configured.	Controller configuration

Command History


Release	Modification
11.3 MA	This command was introduced as a controller configuration command for the Cisco MC3810.
12.0(5)T and 12.0(7)XR	The command was introduced as an ATM interface configuration command for the Cisco 2600 and 3600 series.
12.0(5)XE	The command was introduced as an ATM interface configuration command for the Cisco 7200 and 7500 series.
12.1(1)T	The command was modified as a controller configuration command for the Cisco SLT.

Example

The following example sets the payload loopback method on controller E1 0/0:

Router(config)# controller e1 0/0
Router(config-controller)# loopback local payload

loopback (T1 controller)

To set the loopback method for testing the T1 interface, type the loopback controller configuration command and press Enter:

loopback {diagnostic | local {payload | line} | remote {iboc | esf {payload | line}}

Use the no form of this command to restore the default value:

no loopback

You can use a loopback test on lines to detect and distinguish equipment malfunctions caused either by line and Channel Service Unit/Digital Service Unit (CSU/DSU) or by the interface. If correct data transmission is not possible when an interface is in loopback mode, the interface is the source of the problem.

Syntax Description
Default
Command Mode

diagnostic—Loops the outgoing transmit signal back to the receive signal.

line—Places the interface into external loopback mode at the line level.

local—Places the interface into local loopback mode.

payload—Places the interface into external loopback mode at the payload level.

remote—Keeps the local end of the connection in remote loopback mode.

iboc—Sends an in-band bit-oriented code to the far-end to cause it to go into line loopback.

esf—Specifies extended super frame as the T1 or E1 frame type.

No loopback is configured.

Controller configuration

Syntax Description	Default	Command Mode
diagnostic—Loops the outgoing transmit signal back to the receive signal. line—Places the interface into external loopback mode at the line level. local—Places the interface into local loopback mode. payload—Places the interface into external loopback mode at the payload level. remote—Keeps the local end of the connection in remote loopback mode. iboc—Sends an in-band bit-oriented code to the far-end to cause it to go into line loopback. esf—Specifies extended super frame as the T1 or E1 frame type.	No loopback is configured.	Controller configuration

Command History


Release	Modification
11.3 MA	This command was introduced as a controller configuration command for the Cisco MC3810.
12.0(5)T and 12.0(7)XR	The command was introduced as an ATM interface configuration command for the Cisco 2600 and Cisco 3600 series.
12.0(5)XE	The command was introduced as an ATM interface configuration command for the Cisco 7200 and Cisco 7500 series.
12.1(1)T	The command was introduced as a controller configuration command for the Cisco SLT.

Example

The following example sets the diagnostic loopback method on controller T1 0/0:

Router(config)# controller t1 0/0
Router(config-controller)# loopback diagnostic

show rudpv0 failures

To show SS7 Reliable User Datagram Protocol (RUDP) failure statistics, type the show rudpv0 failures privileged EXEC command and press Enter:

Syntax Description	Default	Command Mode
This command has no arguments or keywords.	This command has no default values or behaviors.

show rudpv0 failures

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example display of RUDP failures:

Router# show rudpv0 failures
 
**** RUDP Failure Stats ****
 
CreateBufHdrsFailure       0
CreateConnRecsFailure      0
CreateEventsFailure        0
 
NotReadyFailures           0
OptionNotSupportedFailures 0
OptionRequiredFailures     0
GetConnRecFailures         0
InvalidConnFailures        0
EventUnavailFailures       0
 
EmptyBufferSendFailures    0
BufferTooLargeFailures     0
ConnNotOpenFailures        0
SendWindowFullFailures     0
GetBufHdrSendFailures      0
 
GetDataBufFailures         0
GetBufHdrFailures          0
 
SendEackFailures           0
SendAckFailures            0
SendSynFailures            0
SendRstFailures            0
SendNullFailures           0
 
TimerNullFailures          0
FailedRetransmits          0
IncomingPktsDropped        0
UnknownRudpEvents          0

Related Commands

Command

Description

clear rudpv0 statistics

Resets the counters for the statistics generated by show rudpv0 failures to 0.

show rudpv0 statistics

Displays RUDP information about number of packets sent, received, and so forth. clear rudpv0 statistics resets the counters for these statistics to 0.

show rudpv0 statistics

To show SS7 Reliable User Datagram Protocol (RUDP) internal statistics, type the show rudpv0 statistics privileged EXEC command and press Enter:

show rudpv0 statistics

Because the statistics counters are continually updated, the cumulative total may not be exactly equal to individual connection counters. Once a connection is reset, previous statistics are lost, so the current connection statistics reflect only this instance of the RUDP connection—since the last reset.

Cumulative statistics reflect counts since the router was rebooted or since the last time the clear rudpv0 statistics command was issued.

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

Alarm forwarding is disabled.

Syntax Description	Default	Command Mode
This command has no arguments or keywords.	Alarm forwarding is disabled.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example display of RUDP statistics and states for two connections:

Router# show rudpv0 statistics
 
*** RUDP Internal Stats ****
 
Connection ID: 811641AC,   Current State: OPEN
 
RcvdInSeq                  1
RcvdOutOfSeq               0
 
SoftResets                 0
SoftResetsRcvd             0
 
TotalPacketsSent           4828
TotalPacketsReceived       4826
TotalDataBytesSent         0
TotalDataBytesReceived     4
TotalDataPacketsSent       0
TotalDataPacketsReceived   1
TotalPacketsRetrans        0
TotalPacketsDiscarded      0
 
Connection ID: 81163FD4,   Current State: OPEN
 
RcvdInSeq                  2265
RcvdOutOfSeq               0
 
SoftResets                 0
SoftResetsRcvd             0
 
TotalPacketsSent           7863
TotalPacketsReceived       6755
TotalDataBytesSent         173690
TotalDataBytesReceived     56121
TotalDataPacketsSent       2695
TotalDataPacketsReceived   2265
TotalPacketsRetrans        0
TotalPacketsDiscarded      0
 
Cumulative RudpV0 Statistics
 
RcvdInSeq                  2266
RcvdOutOfSeq               0
 
SoftResets                 0
SoftResetsRcvd             0
 
TotalPacketsSent           12691
TotalPacketsReceived       11581
TotalDataBytesSent         173690
TotalDataBytesReceived     56125
TotalDataPacketsSent       2695
TotalDataPacketsReceived   2266
TotalPacketsRetrans        0
TotalPacketsDiscarded      0

Related Commands

Command

Description

clear rudpv0 statistics

Resets the counters for the statistics generated by show rudpv0 statistics to 0.

show rudpv0 failures

Displays RUDP information about failed connections and the reasons for them. clear rudpv0 statistics resets the counters for these statistics to 0.

show ss7 mtp2 ccb

To display SS7 MTP 2 Channel Control Block (CCB) information, type the show ss7 mtp2 ccb privileged EXEC command and press Enter:

show ss7 mtp2 ccb channel

The application and meaning of the output is dependent on the MTP 2 variant; for example, TTC only supports emergency alignment.

Syntax Description
Default
Command Mode

channel—Specifies a channel from 0 through 3.

The default is set when you first configure the MTP 2 variant. The link must be out of service in order to change the MTP 2 variant.

If you do not specify a channel, the command shows Channel Control Block information for channel 0.

Syntax Description	Default	Command Mode
channel—Specifies a channel from 0 through 3.	The default is set when you first configure the MTP 2 variant. The link must be out of service in order to change the MTP 2 variant. If you do not specify a channel, the command shows Channel Control Block information for channel 0.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example display of MTP 2 CCB information:

Router# show ss7 mtp2 ccb 0
SS7 MTP2 Internal Channel Control Block Info for channel 0
Protocol version for channel 0 is xxxxx xxxxx xxxxx Version x
ModuloSeqNumber             = 128   (0x80  )
MaxSeqNumber                = 127   (0x7F  )
Unacked-MSUs (MaxInRTB)     = 40    (0x28  )
MaxProvingAttempts          = 5     (0x5   )
error_control               = Basic 
LSSU_Len                    = 1     (0x1   )
MSU_Len                     = 272   (0x110 )
 
SUERM-threshold             = 64    (0x40  )
SUERM-number-octets         = 16    (0x10  )
SUERM-number-SUs            = 256   (0x100 )
 
Tie-AERM-Emergency          = 1     (0x1   )
Tin-AERM-Normal             = 1     (0x1   )
 
MSU_FISU_Accepted_flag      = FALSE 
LSSU_available              = TRUE 
AbnormalBSN_flag            = FALSE 
AbnormalBSN_flag            = FALSE 
UnreasonableBSN             = FALSE 
UnreasonableFSN             = FALSE 
Abnormal_FIBR_flag          = FALSE 
congestionDiscard           = TRUE

show ss7 mtp2 state

To display internal SS7 Message Transfer Part level 2 (MTP 2) state machine information, type the show ss7 mtp2 state privileged EXEC command and press Enter:

Syntax Description	Default	Command Mode
channel—Specifies a channel from 0 through 3.	If you do not specify a channel, the command shows state machine information for channel 0.

show ss7 mtp2 state [channel]

Syntax Description
Default
Command Mode

channel—Specifies a channel from 0 through 3.

If you do not specify a channel, the command shows state machine information for channel 0.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following are example displays of MTP 2 state machine information for two different channels:

Note Table A-1 defines the fields.

Router# show ss7 mtp2 state 0
SS7 MTP2 states for channel 0
Protocol version for channel 0 is xxxxx xxxxx xxxxx Version x 
  MTP2LSC_OOS             MTP2IAC_IDLE           
  MTP2TXC_INSERVICE       MTP2RC_IDLE            
  MTP2SUERM_IDLE          MTP2AERM_IDLE          
  MTP2CONGESTION_IDLE    
    Congestion Backhaul  = Abate 
Remote Processor Outage  = FALSE 
 
Router# show ss7 mtp2 state 1
SS7 MTP2 states for channel 1
Protocol version for channel 1 is xxxxx xxxxx xxxxx Version x 
  MTP2LSC_OOS             MTP2IAC_IDLE           
  MTP2TXC_INSERVICE       MTP2RC_IDLE            
  MTP2SUERM_IDLE          MTP2AERM_IDLE          
  MTP2CONGESTION_IDLE    
    Congestion Backhaul  = Abate 
Remote Processor Outage  = FALSE

show ss7 mtp2 stats

To display SS7 MTP 2 operational statistics, type the show ss7 mtp2 stats privileged EXEC command and press Enter:

show ss7 mtp2 stats [channel]

Syntax Description
Default
Command Mode

channel—Specifies a channel from 0 through 3.

If you do not specify a channel, the command shows state machine information for channel 0.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of operations and maintenance (OM) statistics for MTP 2 channel 0:

Note Table A-1 defines some of the fields.

Router# show ss7 mtp2 stats 0
SS7 MTP2 Statistics for channel 0
Protocol version for channel 0 is xxxxx xxxxx xxxxx Version x 
OMIACAlignAttemptCount  = 0        
OMIACAlignFailCount     = 0        
OMIACAlignCompleteCount = 0        
 
OMMSU_TO_XMIT_Count     = 0        
OMMSU_XMIT_Count        = 0        
OMMSU_RE_XMIT_Count     = 0        
OMMSU_RCV_Count         = 0        
OMMSU_Posted_Count      = 0        
OMMSU_too_long          = 0        
 
OMFISU_XMIT_Count       = 0        
OMFISU_RCV_Count        = 0        
 
OMLSSU_XMIT_Count       = 17       
OMLSSU_XMIT_SINCount    = 0        
OMLSSU_XMIT_SIECount    = 0        
OMLSSU_XMIT_SIOCount    = 0        
OMLSSU_XMIT_SIOSCount   = 17       
OMLSSU_XMIT_SIPOCount   = 0        
OMLSSU_XMIT_SIBCount    = 0 
 
OMLSSU_RCV_Count        = 0        
OMLSSU_RCV_SINCount     = 0        
OMLSSU_RCV_SIECount     = 0        
OMLSSU_RCV_SIOCount     = 0        
OMLSSU_RCV_SIOSCount    = 0        
OMLSSU_RCV_SIPOCount    = 0        
OMLSSU_RCV_SIBCount     = 0        
OMLSSU_RCV_InvalidCount = 0        
 
OMRemote_PO_Count       = 0        
OMRemote_Congestion_Cnt = 0        
 
OMtimeINSV (secs)       = 0        
OMtimeNotINSV (secs)    = 9550     
OMMSUBytesTransmitted   = 0        
OMMSUBytesReceived      = 0        
 
OMTransmitReqCount      = 33       
OMPDU_notAcceptedCount  = 0        
OMPDU_NACK_Count        = 0        
OMunreasonableFSN_rcvd  = 0        
OMunreasonableBSN_rcvd  = 0        
 
OMT1_TMO_Count          = 0        
OMT2_TMO_Count          = 0        
OMT3_TMO_Count          = 0        
OMT4_TMO_Count          = 0        
OMT5_TMO_Count          = 0        
OMT6_TMO_Count          = 0        
OMT7_TMO_Count          = 0        
OMT8_TMO_Count          = 0        
OMTA_TMO_Count          = 0        
OMTF_TMO_Count          = 0        
OMTO_TMO_Count          = 0        
OMTS_TMO_Count          = 477218   
OMLostTimerCount        = 0        
 
OMOMLostBackHaulMsgs    = 0        
 
OMAERMCount             = 0        
OMAERMFailCount         = 0        
OMSUERMCount            = 0        
OMSUERMFailCount        = 0        
OMCongestionCount       = 0        
OMCongestionBackhaulCnt = 0 
 
 

Table A-2: SS7 OM Information Fields


Field
Description

 OMIACAlignAttemptCount
 OMIACAlignFailCount
 OMIACAlignCompleteCount 
 Counts for Initial Alignment Control (IAC) attempts.

 OMMSU_TO_XMIT-_Count
 Related to the results of the show ss7 sm stats command PDU_pkts_receive_count statistic. The number shown in OMMSU_TO_XMIT_Count is less than the PDU_pkts_receive_count because OMMSU_TO_XMIT_Count shows the number of PDUs going out on the link, while the PDU_pkts_receive_count includes PDUs that are internal to MTP2. 

 OMMSU_RCV_Count
 Related to the results of the show ss7 sm stats command packets_send_count.

 OMLSSU_XMIT_Count 
 OMLSSU_XMIT_SINCount
 OMLSSU_XMIT_SIECount
 OMLSSU_XMIT_SIOCount 
 OMLSSU_XMIT_SIOSCount
 OMLSSU_XMIT_SIPOCount
 OMLSSU_XMIT_SIBCount
 Represent the number of times that MTP 2 has posted the specific Link Status Signal Unit (LSSU) to MTP 1. They do not show the number of LSSUs actually sent over the link.

 OMLSSU_RCV_Count
 OMLSSU_RCV_SINCount
 OMLSSU_RCV_SIECount
 OMLSSU_RCV_SIOCount
 OMLSSU_RCV_SIOSCount
 OMLSSU_RCV_SIPOCount
 OMLSSU_RCV_SIBCount
 OMLSSU_RCV_InvalidCount
 Represent the number of LSSUs received by MTP 2 from MTP 1. Due to MTP 1 filtering, this is not the same as the actual LSSUs sent over the link.

 OMT1_TMO_Count
 OMT2_TMO_Count
 OMT3_TMO_Count
 OMT4_TMO_Count
 OMT5_TMO_Count
 OMT6_TMO_Count
 OMT7_TMO_Count
 OMT8_TMO_Count
 OMTA_TMO_Count
 OMTF_TMO_Count
 OMTO_TMO_Count
 OMTA_TMO_Count
 OMLostTimerCount
 Contain information about timers in use.

 OMLostBackhaulMsgs
 Related to the results of the show ss7 sm stats command PDU_pkts_recieve_count statistic. The counter indicates how many messages received from the Cisco MGC have been lost due to a lack of resources in the Cisco SLT. For example, if the Cisco MGC sends 100 MSUs and the Cisco SLT only has 65 free buffers, 35 MSUs might be lost.

show ss7 mtp2 timer

MTP 2 uses eight different timers on each link. Throughout the link state transitions, multiple timers are active. An in-service MTP 2 link requires timers that are constantly started, stopped, and restarted. Use this command to display the configured timer durations.

To display durations of the SS7 MTP 2 state machine timers, type the show ss7 mtp2 timer privileged EXEC command and press Enter:

show ss7 mtp2 timer [channel]

The show ss7 mtp2 timer command displays the status of the eight timers that you set on the Cisco MGC using MML commands. Then, you download the timers from the Cisco MGC to the Cisco SLT.

Note You set all MTP 2 configuration parameters at the Cisco SLT command line interface. The Cisco MGC parameter data files are no longer used to configure the Cisco SLT.

Syntax Description
Default
Command Mode

channel—Specifies a channel from 0 through 3.

If you do not specify a channel, the command shows state machine information for channel 0.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example displays timer information for channel 0:

Router# show ss7 mtp2 timer 0
SS7 MTP2 Timers for channel 0 in milliseconds
Protocol version for channel 0 is xxxxx xxxxx xxxxx Version x 
    T1 aligned/ready = 15000 
      T2 not aligned = 5000  
          T3 aligned = 3000  
T4 Emergency Proving = 3000 
   T4 Normal Proving = 3000 
      T5 sending SIB = 200   
      T6 remote cong = 3000  
 T7 excess ack delay = 2000  
  T8 errored int mon = 0     
TA SIE timer = 20    
       TF FISU timer = 20    
        TO SIO timer = 20    
       TS SIOS timer = 20

show ss7 sm session

To display information about SS7 Session Manager session, type the show ss7 sm session privileged EXEC command and press Enter:

show ss7 sm session [session]

If no sessions are configured, the message "No Session is configured" appears.

Syntax Description
Default
Command Mode

session—Specifies a session, 0 or 1.

If you do not specify a session, the command shows information for both sessions.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example shows displays session information for both sessions:

Router# show ss7 sm session
Session[0]: Remote Host 255.255.251.254:8060, Local Host 255.255.255.254:8060
      retrans_t = 600
      cumack_t  = 300
      kp_t      = 2000
      m_retrans = 2
      m_cumack  = 3
      m_outseq  = 3
      m_rcvnum  = 32
Session[1]: Remote Host 255.255.251.255:8061, Local Host 255.255.255.254:8061
      retrans_t = 600
      cumack_t  = 300
      kp_t      = 2000
      m_retrans = 2
      m_cumack  = 3
      m_outseq  = 3
      m_rcvnum  = 32

Field
Description

Remote Host, Local Host

IP address and port number for the session.

retrans_t

Retransmission timer value.

cumack_t

Cumulative acknowledgment timer value.

m_cumack

Maximum number of segments that can be received before the RUDP sends an acknowledgment.

m_outseq

Maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.

m_rcvnum

Maximum number of segments that the remote end can send before receiving an acknowledgment.

Related Commands

Note Use the default settings for the timer commands listed below. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers may result in service interruption or outage.


Command	Description
ss7 session retrans_t	Sets the retransmission timer.
ss7 session m_rcvnum	Sets the maximum number of segments that the remote end can send before receiving an acknowledgment.
ss7 session m_outseq	Sets the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
ss7 session m_cumack	Sets the maximum number of segments that can be received before the RUDP sends an acknowledgment.
ss7 session cumack_t	Sets the cumulative acknowledgment timer.
ss7 session	Establishes a session.

show ss7 sm set

To display information about the SS7 switchover timer, type the show ss7 sm set privileged EXEC command and press Enter:

show ss7 sm set

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example displays switchover (failover) timer information:

Note The switchover timer is set to the default of 3 seconds.

Router# show ss7 sm set
Session Manager Set
      failover timer = 3 seconds

Related Command

Command

Description

ss7 set failover timer

Specifies the amount of time that the Session Manager waits for the session to recover before declaring the session inactive.

ss7 session

Establishes a session.

show ss7 sm stats

To display SS7 Session Manager session statistics, type the show ss7 sm stats privileged EXEC command and press Enter:

show ss7 sm stats

If no sessions are configured, the message "No Session is configured" appears.

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

The command shows information for both sessions.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example displays SS7 Session Manager statistics, including information about the session state, protocol data units (PDUs) packets sent and received, and SS7 Reliable User Datagram Protocol (RUDP) performance:

Router# show ss7 sm stats
 
-------------------- Session Manager  --------------------
 
Session Manager state             = SESSION SET STATE-ACTIVE
Session Manager Up count          = 1
Session Manager Down count        = 0
   lost control packet count      = 0
              lost PDU count      = 0
 failover timer expire count      = 0
 invalid_connection_id_count      = 0
 
Session[0] statistics  SM SESSION STATE-STANDBY:
Session Down count               = 0
   Open Retry count              = 0
 
   Total Pkts receive count      = 1
   Active Pkts receive count     = 0
   Standby Pkts receive count    = 1
   PDU Pkts receive count        = 0
   Unknown Pkts receive count    = 0
 
   Pkts send count               = 0
   Pkts requeue count            = 0
    -Pkts window full count      = 0
    -Pkts resource unavail count = 0
    -Pkts enqueue fail count     = 0
   PDUs dropped (Large)          = 0
   PDUs dropped (Empty)          = 0
 
   RUDP Not Ready Errs           = 0
   RUDP Connection Not Open      = 0
   RUDP Invalid Conn Handle      = 0
   RUDP Unknown Errors           = 0
   RUDP Unknown Signal           = 0
   NonActive Receive count       = 0
 
Session[1] statistics  SM SESSION STATE-ACTIVE:
Session Down count               = 0
   Open Retry count              = 0
 
   Total Pkts receive count      = 2440
   Active Pkts receive count     = 1
   Standby Pkts receive count    = 0
   PDU Pkts receive count        = 2439
   Unknown Pkts receive count    = 0
 
   Pkts send count               = 2905
   Pkts requeue count            = 0
    -Pkts window full count      = 0
    -Pkts resource unavail count = 0
    -Pkts enqueue fail count     = 0
   PDUs dropped (Large)          = 0
   PDUs dropped (Empty)          = 0
 
RUDP Not Ready Errs           = 0
   RUDP Connection Not Open      = 0
   RUDP Invalid Conn Handle      = 0
   RUDP Unknown Errors           = 0
   RUDP Unknown Signal           = 0
   NonActive Receive count       = 0

Related Commands


Command	Description
clear ss7 sm-stats	Clears the counters that track Session Manager statistics for the show ss7 sm stats command.
ss7 session	Establishes a session.

show ss7 mtp2 variant

To display information about the SS7 MTP 2 protocol variant, type the show ss7 mtp2 variant privileged EXEC command and press Enter:

show ss7 mtp2 variant [channel]

Each country specifies its own variant of SS7, and the Cisco SLT supports several variants of the MTP 2 protocol. The variant you select can affect the MTP 2 statistics displayed by various commands. The Cisco SLT support the following variants:

Telcordia (formerly Bellcore)
ITU
TTC (Japan Telecom)

You can configure each channel to any one of the protocol variants. When you change from one variant to another, for example from Bellcore to TTC, the MTP2 parameters default to those specified by TTC. You can then change the defaults as required.

Syntax Description
Default
Command Mode

channel—Specifies a channel from 0 through 3.

If you do not specify a channel, the command shows state machine information for channel 0.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example displays protocol variant information for channel 1:

Router# show ss7 mtp2 variant 1
Protocol version for channel 1 is Bellcore GR-246-Core Issue 2, Dec 1997

Related Commands


Command	Description
ss7 mtp2-variant bellcore	Specifies the mtp2-variant as Bellcore.
ss7 mtp2-variant itu	Specifies the mtp2-variant as ITU.
ss7 mtp2-variant ttc	Specifies the mtp2-variant as TTC.

ss7 mtp2-variant bellcore

To configure the device for Telcordia (formerly Bellcore) standards, type the ss7 mtp2-variant bellcore global configuration command and press Enter:

ss7 mtp-variant bellcore [channel] [parameters]

The no or default form of the command restores the default value:

{no|default} ss7 mtp-variant bellcore [channel]

This MTP2 variant has configurable timers and parameters. See Table A-3 for a list of these values.

Table A-3: Bellcore Parameters and Values

Parameter Description Default Range

T1

Aligned/ready Timer Duration (Milliseconds)

13000

1000 through 65535

T2

Not Aligned Timer (Milliseconds)

11500

1000 through 65535

T3

Aligned Timer (Milliseconds)

11500

1000 through 65535

T4-Emergency-Proving

Emergency Proving Timer (Milliseconds)

600

1000 through 65535

T4-Normal-Proving

Normal Proving Period (Milliseconds)

2300

1000 through 65535

T5

Sending Sib Timer (Milliseconds)

100

80 through 65535

T6

Remote Congestion Timer (Milliseconds)

6000

1000 through 65535

T7

Excessive Delay Timer (Milliseconds)

1000

500 through 65535

lssu-len

1 Or 2 Byte Lssu Format

1

1 through 2

unacked-MSUs

Maximum number of MSUs waiting ACK

127

16 through 127

proving-attempts

Maximum number of attempts to prove alignment

5

3 through 8

SUERM-threshold

SUERM error rate threshold

64

32 through 128

SUERM-number-octets

SUERM octet counting mode

16

8 through 32

SUERM-number-signal-units

Signal units (good or bad) needed to dec ERM

256

128 through 512

Tie-AERM-Emergency

AERM emergency error rate threshold

1

1 through 8

Tie-AERM-Normal

AERM normal error rate threshold

4

1 through 8

Note Timer durations are converted to 10 millisecond units. For example, a T1 value of 1005 is converted to 100, which results in a actual timeout duration of 1000 milliseconds. This is true for all timers and all variants.

Syntax Description
Default
Command Mode

channel—Specifies the channel, 0-3.

parameters—See Table A-3 for timer descriptions, defaults, and ranges.

Bellcore is the default variant if no other is configured.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets the aligned/ready timer duration on channel 0 to 30,000 milliseconds:

Router(config)# ss7 mtp2-variant Bellcore 0
Router(config-Bellcore)# T1 30000

The following example restores the aligned/ready timer default value of 13,000 milliseconds:

Router(config)# ss7 mtp2-variant Bellcore 0
Router(config-Bellcore)# no T1

Related Commands


Command	Description
ss7 mtp2-variant itu	Specifies the mtp2-variant as ITU.
ss7 mtp2-variant ttc	Specifies the mtp2-variant as TTC.

ss7 mtp2-variant itu

To configure the device for ITU (International Telecom United) standards, type the ss7 mtp2-variant itu global configuration command and press Enter:

ss7 mtp-variant itu [channel] [parameters]

The no or default form of the command restores the default value:

{no|default} ss7 mtp-variant itu [channel]

The ITU MTP2 variant has configurable timers and parameters. See Table A-4 for a list of these values.

Table A-4: ITU (White) Parameters and Values

Parameter Description Default Range

T1

Aligned/ready Timer Duration (milliseconds)

40000

1000 through through 65535

T2

Not Aligned Timer (milliseconds)

5000

1000 through 65535

T3

Aligned Timer (milliseconds)

1000

1000 through 65535

T4-Emergency-Proving

Emergency Proving Timer (milliseconds)

500

1000 through 65535

T4-Normal-Proving

Normal Proving Timer (milliseconds)

8200

1000 through 65535

T5

Sending Sib Timer (milliseconds)

100

80 through 65535

T6

Remote Congestion Timer (milliseconds)

6000

1000 through 65535

T7

Excessive Delay Timer (milliseconds)

1000

1000 through 65535

lssu-len

1 or 2 byte LSSU format

1

1 through 2

msu-len

1 or 2 byte MSSU format

1

1 through 2

unacked-MSUs

Maximum number of MSUs waiting ACK

127

16 through 127

proving-attempts

Maximum number of attempts to prove alignment

5

3 through 8

SUERM-threshold

SUERM error rate threshold

64

32 through 128

SUERM-number-octets

SUERM octet counting mode

16

8 through 32

SUERM-number-signal-units

Signal units (good or bad) needed to SUERM

256

128 through 512

Tie-AERM-Emergency

AERM emergency error rate threshold

1

1 through 8

Tin-AERM-Normal

AERM normal error rate threshold

4

1 through 8

Syntax Description
Default
Command Mode

channel—Specifies the channel, 0 through 3.

parameters—See Table A-4 for timer descriptions, defaults, and ranges.

Bellcore is the default variant if no other is configured.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets the emergency proving period on channel 1 to 10,000 milliseconds:

Router(config)# ss7 mtp2-variant itu 1
Router(config-itu)# t4-Emergency-Proving 10000

The following example restores the emergency proving period default value of 5,000 milliseconds:

Router(config)# ss7 mtp2-variant itu 1
Router(config-itu)# default t4-Emergency-Proving

Related Commands


Command	Description
ss7 mtp2-variant bellcore	Specifies the mtp2-variant as Bellcore.
ss7 mtp2-variant ttc	Specifies the mtp2-variant as TTC.

ss7 mtp2-variant ttc

To configure the device for TTC (Japan Telecom) standards, type the ss7 mtp2-variant ttc global configuration command and press Enter:

ss7 mtp-variant ttc [channel] [parameters]

The no or default form of the command restores the default value:

{no|default} ss7 mtp-variant ttc [channel]

The TTC MTP2 variant has configurable timers and parameters. See Table A-5 for a list of values.

Table A-5: TTC Parameters and Values

Parameter Description Default Range

T1

Aligned/ready Timer Duration (Milliseconds)

15000

1000 through 65535

T2

Not Aligned Timer (Milliseconds)

5000

1000 through 65535

T3

Aligned Timer (Milliseconds)

3000

1000 through 65535

T4-Emergency-Proving

Emergency Proving Timer (Milliseconds)

3000

1000 through 65535

T5

Sending Sib Timer (Milliseconds)

200

80 through 65535

T6

Remote Congestion Timer (Milliseconds)

2000

1000 through 65535

T7

Excessive Delay Timer (Milliseconds)

3000

1000 through 65535

TA

SIE interval timer (milliseconds)

20

10 through 500

TF

FISU interval timer (milliseconds)

20

10 through 500

TO

SIO interval timer (milliseconds)

20

10 through 500

TS

SIOS interval timer (milliseconds)

20

10 through 500

unacked-MSUs

Maximum number of MSUs waiting ACK

40

16 through 40

proving-attempts

Maximum number of attempts to prove alignment

5

3 through 8

SUERM-threshold

SUERM error rate threshold

64

32 through 128

SUERM-number-octets

SUERM octet counting mode

16

8 through 32

SUERM-number-signal-units

Signal units (good or bad) needed to dec ERM

256

128 through 512

Tie-AERM-Emergency

AERM emergency error rate threshold

1

1 through 8

Syntax Description
Default
Command Mode

channel—Specifies the channel, 0 through 3.

parameters—See Table A-5 for timer descriptions, defaults, and ranges.

Bellcore is the default variant if none other is configured.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets the maximum number of proving attempts for channel 3 to 3:

Router(config)# ss7 mtp2-variant ttc 3
Router(config-ttc)# proving-attempts 3

The following example restores the maximum number of proving attempts to the default value:

Router(config)# ss7 mtp2-variant ttc 3
Router(config-ttc)# default proving-attempts

Related Commands


Command	Description
ss7 mtp2-variant bellcore	Specifies the mtp2-variant as Bellcore.
ss7 mtp2-variant itu	Specifies the mtp2-variant as ITU.

ss7 session

To create a Reliable User Datagram Protocol (RUDP) session, type the ss7 session global configuration command and press Enter:

ss7 session-session number {address remote-address remote-port local-address local-port}

The no form of the command deletes the session:

no ss7session-session number address

Note the following:

You can configure a maximum of two sessions, one for each signaling link. In a redundant Cisco MGC configuration, session-0 is configured to one Cisco MGC and session-1 is configured to the other.
The Cisco MGC must be configured to send messages to the local port, and it must be configured to listen on the remote port.
You must reload the Cisco SLT whenever you remove a session or change the parameters of a session.

Syntax Description
Default
Command Mode

session-number—SS7 session number. Valid values are 0 and 1. You must enter the hyphen, with no space following it, after the session keyword.

remote-address—The remote IP address of the Cisco MGC in four-part dotted-decimal format.

remote-port—The number of the remote UDP port on which the Cisco MGC is configured to listen. This UDP port cannot be used by another protocol as defined in RFC 1700 and cannot be otherwise used in the network.

local-address—The local IP address of the router in four-part dotted-decimal format.

NoteThe local IP address for both sessions, 0 and 1, must be the same.

local-port—The number of the local UDP port on which the router expects to receive messages from the Cisco MGC. Specify any UDP port that is not used by another protocol as defined in RFC 1700 and that is not otherwise used in your network.

NoteThe local UDP port must be different for session-0 and session-1.

No session is configured.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets up two sessions on a Cisco SLT:

ss7 session-0 address 255.251.255.255 7000 255.255.255.254 7000
ss7 session-1 address 255.255.255.252 7002 255.255.255.254 7001

Note The local IP addresses in session-0 and session-1 must be the same.

Related Commands


Command	Description
ss7 session retrans_t	Sets the retransmission timer.
ss7 session m_retrans	Sets the maximum number of times that the RUDP attempts to resend a segment before declaring the connection invalid.
ss7 session m_rcvnum	Sets the maximum number of segments that the remote end can send before receiving an acknowledgment.
ss7 session m_outseq	Sets the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
ss7 session m_cumack	Sets the maximum number of segments that can be received before the RUDP sends an acknowledgment.
ss7 session k_pt	Sets the null segment (keepalive) timer.
ss7 session cumack_t	Sets the cumulative acknowledgment timer.

ss7 session cumack_t

To set the Reliable User Datagram Protocol (RUDP) cumulative acknowledgment timer for a specific SS7 signaling link session, type the ss7 session cumack_t global configuration command and press Enter:

ss7 session-session number cumack_t milliseconds

The no form of the command restores the default value:

no ss7 session-session number cumack_t

The cumulative acknowledgment timer determines when the receiver sends an acknowledgment. If the timer is not already running, it is initialized when a valid data, null, or reset segment is received. When the cumulative acknowledgment timer expires, the last in-sequence segment is acknowledged. The RUDP typically tries to "piggyback" acknowledgments on data segments being sent. If no data segment is sent in this period of time, however, it sends a standalone acknowledgment.

Warning Use the default setting. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers may result in service interruption or outage.

Syntax Description
Default
Command Mode

session-number—SS7 session number. Valid values are 0 and 1. You must enter the hyphen, with no space following it, after the session keyword.

milliseconds—Use this parameter to specify the amount of time (in milliseconds) that the RUDP waits before sending an acknowledgment after receiving a segment.

Valid values are from 100 through 65535. This value should be less than the value configured for the retransmission timer (using the ss7 session-session number retrans_t command).

The default value is 300 milliseconds.

Global configuration

Example

The following example sets up two sessions and sets the cumulative acknowledgment timer to 320 milliseconds for each one:

ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7000
ss7 session-0 cumack_t 320
ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7001
ss7 session-1 cumack_t 320

Related Commands


Command	Description
ss7 session retrans_t	Sets the retransmission timer.
ss7 session m_retrans	Sets the maximum number of times that the RUDP attempts to resend a segment before declaring the connection invalid.
ss7 session m_rcvnum	Sets the maximum number of segments that the remote end can send before receiving an acknowledgment.
ss7 session m_outseq	Sets the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
ss7 session m_cumack	Sets the maximum number of segments that can be received before the RUDP sends an acknowledgment.
ss7 session k_pt	Sets the null segment (keepalive) timer.
show ss7	Displays the SS7 configuration.

ss7 session kp_t

To set the null segment (keepalive) timer for a specific SS7 signaling link session, type the ss7 session kp_t global configuration command and press Enter:

ss7 session-session number kp_t milliseconds

The no form of the command restores the default value:

no ss7 session-session number kp_t

The null segment timer determines when a null segment (keepalive) is sent by the client Cisco SLT. On the client, the timer starts when the connection is established and is reset each time a data segment is sent. If the null segment timer expires, the client sends a keepalive to the server to verify that the connection is still functional. On the server, the timer restarts each time a data or null segment is received from the client.

The value of the server's null segment timer is twice the value configured for the client. If no segments are received by the server in this period of time, the connection is no longer valid.

Warning Use the default setting. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers may result in service interruption or outage.

Syntax Description
Default
Command Mode

session-number—SS7 session number. Valid values are 0 and 1. You must enter the hyphen, with no space following it, after the session keyword.

milliseconds—Use this parameter to specify the amount of time (in milliseconds) that the RUDP waits before sending a keepalive to verify that the connection is still alive.

Valid values are from 100 through 65535.

The default value is 2000 milliseconds.

To disable keepalive, set milliseconds to 0.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets up two sessions and sets a keepalive of 1,800 milliseconds for each one:

ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7000
ss7 session-0 kp_t 1800
ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7001
ss7 session-1 kp_t 1800

Related Commands


Command	Description
ss7 session retrans_t	Sets the retransmission timer.
ss7 session m_retrans	Sets the maximum number of times that the RUDP attempts to resend a segment before declaring the connection invalid.
ss7 session m_rcvnum	Sets the maximum number of segments that the remote end can send before receiving an acknowledgment.
ss7 session m_outseq	Sets the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
ss7 session m_cumack	Sets the maximum number of segments that can be received before the RUDP sends an acknowledgment.
ss7 session cumack_t	Sets the cumulative acknowledgment timer.
show ss7	Displays the SS7 configuration.

ss7 session m_cumack

To set the maximum number of segments that can be received before the Reliable User Datagram Protocol (RUDP) sends an acknowledgment in a specific SS7 signaling link session, enter the ss7 session m_cumack global configuration command:

ss7 session-session number m_cumack segments

The no form of the command restores the default value:

no ss7 session-session number m_cumack

The cumulative acknowledgment counter records the number of unacknowledged, in-sequence data, null, or reset segments received without a data, null, or reset segment being sent to the transmitter. If this counter reaches the configured maximum, the receiver sends a standalone acknowledgment (a segment that contains only acknowledgment information). The standalone acknowledgment contains the sequence number of the last data, null, or reset segment received.

Warning Use the default setting. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers may result in service interruption or outage.

Syntax Description
Default
Command Mode

session-number—SS7 session number. Valid values are 0 and 1. You must enter the hyphen, with no space following it, after the session keyword.

segments—Use this parameter to specify maximum number of segments that can be received before the Reliable User Datagram Protocol (RUDP) sends an acknowledgment.

Valid values are from 0 through 255.

The default value for segments is 3.

If you set segments to 0, an acknowledgment is sent upon receipt of a data, null, or reset segment.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets up two sessions and in each session sets a maximum of two segments for receipt before acknowledgment:

ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001
ss7 session-0 m_cumack 2
ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000
ss7 session-1 m_cumack 2

Related Commands


Command	Description
ss7 session retrans_t	Sets the retransmission timer.
ss7 session m_retrans	Sets the maximum number of times that the RUDP attempts to resend a segment before declaring the connection invalid.
ss7 session m_rcvnum	Sets the maximum number of segments that the remote end can send before receiving an acknowledgment.
ss7 session m_outseq	Sets the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
ss7 session k_pt	Sets the null segment (keepalive) timer.
ss7 session cumack_t	Sets the cumulative acknowledgment timer.
show ss7	Displays the SS7 configuration.

ss7 session m_outseq

To set the maximum number of out-of-sequence segments that can be received before the Reliable User Datagram Protocol (RUDP) sends an extended acknowledgment in a specific SS7 signaling link session, enter the ss7 session m_outseq global configuration command:

ss7 session-session number m_outseq segments

The no form of the command restores the default value:

no ss7 session-session number m_outseq

The out-of-sequence acknowledgment counter records the number of data segments that have arrived out of sequence. If this counter reaches the configured maximum, the receiver sends an extended acknowledgment segment that contains the sequence numbers of the out-of-sequence data, null, and reset segments received. When the transmitter receives the extended acknowledgment segment, it retransmits the missing data segments.

Warning Use the default setting. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers may result in service interruption or outage.

Syntax Description
Default
Command Mode

session-number—SS7 session number. Valid values are 0 and 1. You must enter the hyphen, with no space following it, after the session keyword.

segments—Use this parameter to specify the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment. If the specified number of segments are received out of sequence, an Extended Acknowledgment segment is sent to inform the sender which segments are missing.

Valid values are from 0 through 255.

The default value is 3 segments.

If you set segments to 0, an acknowledgment is sent immediately after an out-of-sequence segment is received.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets up two sessions and sets a maximum number of four out-of-sequence segments for each session:

ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001
ss7 session-0 m_outseq 4
ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000
ss7 session-1 m_outseq 4

Related Commands


Command	Description
ss7 session retrans_t	Sets the retransmission timer.
ss7 session m_retrans	Sets the maximum number of times that the RUDP attempts to resend a segment before declaring the connection invalid.
ss7 session m_rcvnum	Sets the maximum number of segments that the remote end can send before receiving an acknowledgment.
ss7 session m_cumack	Sets the maximum number of segments that can be received before the RUDP sends an acknowledgment.
ss7 session k_pt	Sets the null segment (keepalive) timer.
ss7 session cumack_t	Sets the cumulative acknowledgment timer.
show ss7	Displays the SS7 configuration.

ss7 session m_rcvnum

To set the maximum number of segments that the remote end can send before receiving an acknowledgment in a specific SS7 signaling link session, enter the ss7 session m_rcvnum global configuration command:

ss7 session-session number m_rcvnum segments

The no form of the command restores the default value:

no ss7 session-session number m_rcvnum

The outstanding segments counter is the maximum number of segments that the Cisco IOS end of the connection can send without getting an acknowledgment from the receiver. The receiver uses the counter for flow control.

Warning Use the default setting. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers may result in service interruption or outage.

Syntax Description
Default
Command Mode

session-number—SS7 session number. Valid values are 0 and 1. You must enter the hyphen, with no space following it, after the session keyword.

segments—Use this parameter to specify the maximum number of segments that the remote (Cisco IOS) end can send before receiving an acknowledgment.

Valid values are from 1 through 64.

The default value is 32 segments.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets up two sessions and for each session sets a maximum of 36 segments for receipt before an acknowledgment:

ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001
ss7 session-0 m_rcvnum 36
ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000
ss7 session-1 m_rcvnum 36

Related Commands


Command	Description
ss7 session retrans_t	Sets the retransmission timer.
ss7 session m_retrans	Sets the maximum number of times that the RUDP attempts to resend a segment before declaring the connection invalid.
ss7 session m_outseq	Sets the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
ss7 session m_cumack	Sets the maximum number of segments that can be received before the RUDP sends an acknowledgment.
ss7 session k_pt	Sets the null segment (keepalive) timer.
ss7 session cumack_t	Sets the cumulative acknowledgment timer.
show ss7	Displays the SS7 configuration.

ss7 session m_retrans

To set the maximum number of times that the RUDP attempts to resend a segment before declaring the connection invalid in a specific SS7 signaling link session, enter the ss7 session m_retrans global configuration command:

ss7 session-session number m_retrans number

The no form of the command restores the default value:

no ss7 session-session number m_retrans

The retransmission counter is the number of times a segment has been retransmitted. If this counter reaches the configured maximum, the transmitter resets the connection and informs the upper-layer protocol.

Warning Use the default setting. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers may result in service interruption or outage.

Syntax Description
Default
Command Mode

session-number—SS7 session number. Valid values are 0 and 1. You must enter the hyphen, with no space following it, after the session keyword.

segments—Use this parameter to specify the maximum number of times that the RUDP attempts to resend a segment before declaring the connection broken.

Valid values are from 0 through 255.

The default value for segments is 2 times.

If you set segments to 0, the RUDP attempts to resend the segment continuously.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets up two sessions and for each session sets a maximum number of three times to resend before a session becomes invalid:

ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001
ss7 session-0 m_retrans 3
ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000
ss7 session-1 m_retrans 3

Related Commands


Command	Description
ss7 session retrans_t	Sets the retransmission timer.
ss7 session m_rcvnum	Sets the maximum number of segments that the remote end can send before receiving an acknowledgment.
ss7 session m_outseq	Sets the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
ss7 session m_cumack	Sets the maximum number of segments that can be received before the RUDP sends an acknowledgment.
ss7 session k_pt	Sets the null segment (keepalive) timer.
ss7 session cumack_t	Sets the cumulative acknowledgment timer.
show ss7	Displays the SS7 configuration.

ss7 session retrans_t

To set the amount of time that the RUDP waits to receive an acknowledgment for a segment in a specific SS7 signaling link session, enter the ss7 session retrans_t global configuration command:

ss7 session-session number retrans_t milliseconds

The no form of the command restores the default value:

no ss7 session-session number retrans_t

The retransmission timer is used to determine whether a packet must be retransmitted and is initialized each time a data, null, or reset segment is sent. If an acknowledgment for the segment is not received by the time the retransmission timer expires, all segments that have been transmitted—but not acknowledged—are retransmitted.

Warning Use the default setting. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers may result in service interruption or outage.

Syntax Description
Default
Command Mode

session-number—SS7 session number. Valid values are 0 and 1. You must enter the hyphen, with no space following it, after the session keyword.

segments—Use this parameter to specify the amount of time that the RUDP waits to receive an acknowledgment for a segment.

Valid values are from 100 through 65535.

If you set this parameter to 0, the RUDP attempts to resend the segment continuously.

NoteThis value should be greater than the value configured for the cumulative acknowledgment timer (using the ss7 session cumack_t command).

The default value is 600 milliseconds.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets up two sessions and specifies 550 milliseconds as the time to wait for an acknowledgment for each session:

ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001
ss7 session-0 retrans_t 550
ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000
ss7 session-1 retrans_t 550

Related Commands


Command	Description
ss7 session m_retrans	Sets the maximum number of times that the RUDP attempts to resend a segment before declaring the connection invalid.
ss7 session m_rcvnum	Sets the maximum number of segments that the remote end can send before receiving an acknowledgment.
ss7 session m_outseq	Sets the maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
ss7 session m_cumack	Sets the maximum number of segments that can be received before the RUDP sends an acknowledgment.
ss7 session k_pt	Sets the null segment (keepalive) timer.
ss7 session cumack_t	Sets the cumulative acknowledgment timer.
show ss7	Displays the SS7 configuration.

ss7 set failover-timer

To specify the amount of time that the SS7 Session Manager waits for the active session to recover or for the standby Cisco MGC to indicate that the Cisco SLT should switch traffic to the standby session, enter the ss7 set failover-timer global configuration command:

ss7 set failover-timer [seconds]

The no form of the command restores the default value:

no ss7 set failover-timer

This command specifies the number of seconds that the Session Manager waits for the active session to recover or for the standby Cisco MGC to indicate that the Cisco SLT should switch traffic to the standby session and to make that session the active session. If the timer expires without a recovery of the original session or an active message from the standby Cisco MGC, the signaling links are taken out of service.

Syntax Description
Default
Command Mode

seconds—Time in seconds that the Session Manager waits for a session to recover.

Values from 1 through 10 are valid.

The default value is 3 seconds.

Global configuration

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

The following example sets the switchover timer to four seconds:

ss7 set failover-timer 4

Related Commands


Command	Description
show ss7 sm set	Displays the current switchover timer setting.
ss7 session	Establishes a session.

Debug Commands

This section documents the following new or modified debug commands:

debug rudpv0 application

To enable SS7 Reliable User Datagram Protocol (RUDP) application debugging, enter the debug rudpv0 application privileged EXEC command:

debug rudpv0 application

The no form of the command disables debugging output:

no debug rudpv0 application

The command output shows the sequence numbers of segments as they are being passed to the upper-layer protocol.

Warning Use this command only for testing problems in a controlled environment. This command can generate large amounts of output. If there is any significant amount of traffic flow when you issue the command, the processor may slow down so much that RUDP connections fail. This command is recommended for field support personnel only, and is not recommended for use without prior recommendation from Cisco.

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug rudpv0 application command output:

*Mar  1 00:41:09.387: Turning application debugging on
*Mar  1 00:41:09.395: Send to appl, seq 204
*Mar  1 00:41:13.722: Send to appl, seq 205
*Mar  1 00:41:23.631: Send to appl, seq 206
*Mar  1 00:41:37.225: Send to appl, seq 207
*Mar  1 00:41:37.225: Send to appl, seq 208
*Mar  1 00:41:37.225: Send to appl, seq 209
*Mar  1 00:41:39.404: Send to appl, seq 210
*Mar  1 00:41:39.444: Send to appl, seq 211
*Mar  1 00:41:48.632: Send to appl, seq 212

debug rudpv0 performance

To view information about sent and received SS7 RUDP packets, enter the debug rudpv0 performance privileged EXEC command:

debug rudpv0 performance

The no form of this command disables debugging output:

no debug rudpv0 performance

The command output shows the average number of segments sent and received per second for all RUDP connections combined. The "Sent" and "Rcvd" counts report the total number of segments (both internal RUDP segments and data segments) averaged over the time since the last issue of the clear rudpv0 statistics command or the last reboot.

The "Data Bytes" and packet counts are averaged only over the number of segments when there is actual data traffic flowing. For example, sent keepalive segments do not affect these counts.

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug rudpv0 performance command output.

Router# debug rudpv0 performance
*Mar  1 01:12:34.065: Turning performance debugging on
*Mar  1 01:12:41.817:
*Mar  1 01:12:41.817: Sent: Pkts 1,  Data Bytes 118,  Data Pkts 1
*Mar  1 01:12:41.817: Rcvd: Pkts 1,  Data Bytes 47,  Data Pkts 1
*Mar  1 01:12:41.817: Discarded: 0,  Retransmitted 0
*Mar  1 01:12:41.817:
*Mar  1 01:12:51.846:
*Mar  1 01:12:51.846: Sent: Pkts 1,  Data Bytes 118,  Data Pkts 1
*Mar  1 01:12:51.846: Rcvd: Pkts 1,  Data Bytes 47,  Data Pkts 1
*Mar  1 01:12:51.846: Discarded: 0,  Retransmitted 0
*Mar  1 01:12:51.846:
*Mar  1 01:13:11.907:
*Mar  1 01:13:11.907: Sent: Pkts 1,  Data Bytes 118,  Data Pkts 1
*Mar  1 01:13:11.907: Rcvd: Pkts 1,  Data Bytes 47,  Data Pkts 1
*Mar  1 01:13:11.907: Discarded: 0,  Retransmitted 0
*Mar  1 01:13:11.907:
*Mar  1 01:13:21.931:
*Mar  1 01:13:21.931: Sent: Pkts 1,  Data Bytes 118,  Data Pkts 1
*Mar  1 01:13:21.931: Rcvd: Pkts 1,  Data Bytes 47,  Data Pkts 1

debug rudpv0 retransmit

To show information about SS7 RUDP retransmit timer performance, enter the debug rudpv0 retransmit privileged EXEC command:

debug rudpv0 retransmit

The no form of this command disables debugging output:

no debug rudpv0 retransmit

The command output shows internal RUDP events involved in retransmitting segments.

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug rudpv0 retransmit command output:

Router# debug rudpv0 retransmit
*Mar  1 01:14:21.405: Turning retransmit/softreset debugging on
*Mar  1 01:14:21.633: Retrans timer, set to ack 67
*Mar  1 01:14:22.647: Retrans timer, set to ack 45
*Mar  1 01:14:23.636: Retrans timer, set to ack 46
*Mar  1 01:14:23.636: Retrans timer, set to ack 68
*Mar  1 01:14:25.640: Retrans timer, set to ack 47
*Mar  1 01:14:25.644: Retrans timer, set to ack 69
*Mar  1 01:14:27.639: Retrans timer, set to ack 48
*Mar  1 01:14:27.643: Retrans timer, set to ack 70
*Mar  1 01:14:29.642: Retrans timer, set to ack 49
*Mar  1 01:14:29.646: Retrans timer, set to ack 71
*Mar  1 01:14:31.645: Retrans timer, set to ack 50
*Mar  1 01:14:31.649: Retrans timer, set to ack 72
*Mar  1 01:14:33.649: Retrans timer, set to ack 51
*Mar  1 01:14:33.653: Retrans timer, set to ack 73
*Mar  1 01:14:35.648: Retrans timer, set to ack 52
*Mar  1 01:14:35.652: Retrans timer, set to ack 74

debug rudpv0 segment

To show information about segments being sent and received by the SS7 RUDP, type the debug rudpv0 segment privileged EXEC command and press Enter:

debug rudpv0 segment

The no form of this command disables debugging output:

no debug rudpv0 segment

The command output shows segments that are being sent and received by the RUDP and the control bits that are set in those segments. The number in parentheses is the length of the segment.

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug rudpv0 segment command output:

*Mar  1 01:16:57.981: Turning segment debugging on
*Mar  1 01:16:58.005: RUDP:  Rcvd ACK 30..145 (4),
*Mar  1 01:16:58.642: RUDP:  Send NUL ACK 143..155 (4),
*Mar  1 01:16:58.895: RUDP:  Rcvd ACK 156..143 (4),
*Mar  1 01:16:59.808: RUDP:  Send NUL ACK 146..29 (4),
*Mar  1 01:17:00.105: RUDP:  Rcvd ACK 30..146 (4),
*Mar  1 01:17:00.646: RUDP:  Send NUL ACK 144..155 (4),
*Mar  1 01:17:00.898: RUDP:  Rcvd ACK 156..144 (4),
*Mar  1 01:17:01.812: RUDP:  Send NUL ACK 147..29 (4),
*Mar  1 01:17:02.108: RUDP:  Rcvd ACK 30..147 (4),
*Mar  1 01:17:02.645: RUDP:  Send NUL ACK 145..155 (4),
*Mar  1 01:17:02.897: RUDP:  Rcvd ACK 156..145 (4),
*Mar  1 01:17:03.811: RUDP:  Send NUL ACK 148..29 (4),
*Mar  1 01:17:04.107: RUDP:  Rcvd ACK 30..148 (4),
*Mar  1 01:17:04.648: RUDP:  Send NUL ACK 146..155 (4),
*Mar  1 01:17:04.897: RUDP:  Rcvd ACK 156..146 (4),
*Mar  1 01:17:05.814: RUDP:  Send NUL ACK 149..29 (4),
*Mar  1 01:17:06.107: RUDP:  Rcvd ACK 30..149 (4),

debug rudpv0 signal

To enable SS7 RUDP signaling debugging, enter the debug rudpv0 signal privileged EXEC command:

debug rudpv0 signal

The no form of this command disables debugging output:

no debug rudpv0 signal

The command output shows the signals the RUDP is sending to the upper-layer protocol.

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug rudpv0 signal command output:

Router# debug rudpv0 signal
*Mar  1 00:00:35.093:Turning signal debugging on
*Mar  1 00:02:29.060:Sent CONN_RESET_SIG to connID 811BE94C
*Mar  1 00:02:30.061:Sent CONN_OPEN_SIG to connID 811BE94C
*Mar  1 00:04:11.195:Sent CONN_RESET_SIG to connID 811BEB24
*Mar  1 00:04:15.202:Sent CONN_OPEN_SIG to connID 811BEB24

debug rudpv0 timer

To see SS7 RUDP timer delay setting and start and stops, enter the debug rudpv0 timer privileged EXEC command:

debug rudpv0 timer

The no form of this command disables debugging output:

no debug rudpv0 timer

The command output shows the timers that RUDP starts and stops, as well as those that expire.

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug rudpv0 timer command output that shows the configured delays for active timers used in the specified connections (connection ID 81164054 and so on):

Router# debug rudpv0 timer
*Mar  1 01:19:46.842: Turning timer debugging on
*Mar  1 01:19:47.479: Timer Keepalive (NullSeg) triggered for conn = 81164054
*Mar  1 01:19:47.479: Starting Retrans timer for connP = 81164054, delay = 600
*Mar  1 01:19:47.479: Stopping SentList timer for connP = 81164054
*Mar  1 01:19:47.479: Starting NullSeg timer for connP = 81164054, delay = 2000
*Mar  1 01:19:47.700: Stopping Retrans timer for connP = 81164054
*Mar  1 01:19:47.992: Timer Keepalive (NullSeg) triggered for conn = 8116422C
*Mar  1 01:19:47.992: Starting Retrans timer for connP = 8116422C, delay = 600
*Mar  1 01:19:47.992: Stopping SentList timer for connP = 8116422C
*Mar  1 01:19:47.992: Starting NullSeg timer for connP = 8116422C, delay = 2000
*Mar  1 01:19:48.196: Stopping Retrans timer for connP = 8116422C
*Mar  1 01:19:48.629: Starting Retrans timer for connP = 81164054, delay = 600
*Mar  1 01:19:48.629: Stopping SentList timer for connP = 81164054

debug ss7 mtp2 aerm

To display SS7 MTP 2 Alignment Error Rate Monitor (AERM) events and state transitions, enter the debug ss7 mtp2 aerm privileged EXEC command:

debug ss7 mtp2 aerm [channel]

The no form of this command disables debugging output:

no debug ss7 mtp2 aerm

Syntax Description
Default
Command Mode

channel—Enter a logical channel number. Valid values are from 0 through 3.

If you do not specify a channel number, the command displays information for channel 0.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 aerm command output:

Router# debug ss7 mtp2 aerm 0
*Mar  8 08:59:30.991:itu2AERM_Start  chnl=0  MTP2AERM_IDLE
*Mar  8 08:59:35.070:itu2AERM_Stop  chnl=0  MTP2AERM_MONITORING

Note See the MTP 2 specification for more details.

debug ss7 mtp2 backhaul

To display SS7 MTP 2 events and messages received from and sent to the Cisco MGC, enter the debug ss7 mtp2 backhaul privileged EXEC command:

debug ss7 mtp2 backhaul [channel]

The no form of this command disables debugging output:

no debug ss7 mtp2 backhaul

This command helps debug communications between the Cisco MGC and the Cisco SLT.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 backhaul command output for channel 0:

Router# debug ss7 mtp2 backhaul 0
*Mar  1 03:08:04.433: MTP2: send Disc Ind  ch=0  reason=0x14-T2 expired waiting for SIO
*Mar  1 03:08:04.433: MTP2: send LSC Ind  ch=0  event=0x8-lost link alignment cause=0x0
*Mar  1 03:08:08.721: MTP2: rcvd Conn Req - Normal  ch=0
*Mar  1 03:08:10.311: MTP2: rcvd Statistics Req-Send&Reset   ch=0
*Mar  1 03:08:10.311: MTP2: send Stats Cfm  ch=0
*Mar  1 03:08:20.440: MTP2: send Disc Ind  ch=0  reason=0x14-T2 expired waiting for SIO
*Mar  1 03:08:20.444: MTP2: send LSC Ind  ch=0  event=0x8-lost link alignment cause=0x0
*Mar  1 03:08:24.719: MTP2: rcvd Conn Req - Normal  ch=0
*Mar  1 03:08:36.438: MTP2: send Disc Ind  ch=0  reason=0x14-T2 expired waiting for SIO
*Mar  1 03:08:36.438: MTP2: send LSC Ind  ch=0  event=0x8-lost link alignment cause=0x0
*Mar  1 03:08:40.312: MTP2: rcvd Statistics Req-Send&Reset   ch=0
*Mar  1 03:08:40.312: MTP2: send Stats Cfm  ch=0
*Mar  1 03:08:40.721: MTP2: rcvd Conn Req - Normal  ch=0
*Mar  1 03:08:52.444: MTP2: send Disc Ind  ch=0  reason=0x14-T2 expired waiting for SIO
*Mar  1 03:08:52.444: MTP2: send LSC Ind  ch=0  event=0x8-lost link alignment cause=0x0
*Mar  1 03:08:56.719: MTP2: rcvd Conn Req - Normal  ch=0
*Mar  1 03:09:08.438: MTP2: send Disc Ind  ch=0  reason=0x14-T2 expired waiting for SIO
*Mar  1 03:09:08.438: MTP2: send LSC Ind  ch=0  event=0x8-lost link alignment cause=0x0

Note Table A-6, Table A-7, and Table A-8 define the codes that appear in the command output.

Table A-6: Backhaul Debug Event Codes

Event Code Explanation

0x0

Local processor outage

0x1

Local processor outage recovered

0x2

Entered a congested state

0x3

Exited a congested state

0x4

Physical layer up

0x5

Physical layer down

0x7

Protocol error (see cause code)

0x8

Link alignment lost

0x9

Retransmit buffer full

0xa

Retransmit buffer no longer full

0xb

Negative acknowledgment received from far end

0xc

Remote entered congestion

0xd

Remote exited congestion

0xe

Remote entered processor outage

0xf

Remote exited processor outage

Table A-7: Backhaul Debug Cause Codes

Cause Code Explanation

0x0

Cause unknown - default

0x1

Management initiated

0x2

Abnormal BSN (Backward Sequence Number)

0x3

Abnormal FIB (Forward Indicator Bit)

0x4

Congestion discard

Table A-8: Backhaul Debug Reason Codes

Cause Code Explanation

0x0

Layer management request

0x1

SUERM (Signal Unit Error Monitor) failure

0x2

Excessively long alignment period

0x3

T7 timer expired

0x4

Physical interface failure

0x5

Two or three invalid BSNs

0x6

Two or three invalid FIBs

0x7

LSSU (Link Status Signal Unit) condition

0x8

Excessive MTP 2 congestion

0x13

SIOs (Service Information Octets) received in Link State Control (LSC)

0x14

Timer T2 expired waiting for SIO

0x15

Timer T3 expired waiting for SIE/SIN

0x16

SIO received in initial alignment control (IAC)

0x17

Proving period failure

0x18

Timer T1 expired waiting for FISU (Fill-In Signal Unit)

0x19

SIN received in in-service state

0x20

CTS lost

0x25

No resources

debug ss7 mtp2 cong

To display information about SS7 MTP 2 congestion state machine events and transitions, enter the debug mtp2 cong privileged EXEC command:

debug ss7 mtp2 cong [channel]

The no form of this command disables debugging output.

no debug mtp2 cong

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 cong command output:

Router# debug ss7 mtp2 cong 0
*Mar  8 09:10:56.219:itu2CongestionOnset  chnl=0  MTP2CONGESTION_IDLE
*Mar  8 09:10:59.332:itu2CongestionAbatement chnl=0
MTP2CONGESTION_ACTIVE
*Mar  8 09:11:01.143:itu2CongestionAbatement chnl=0  MTP2CONGESTION_IDLE

Note See the MTP 2 specification for details.

debug ss7 mtp2 iac

To display information about SS7 MTP 2 initial alignment control (IAC) events and transitions, enter the debug ss7 mtp2 iac privileged EXEC command:

debug ss7 mtp2 iac [channel]

The no form of this command disables debugging output.

no debug mtp2 iac

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 iac command output:

Router# debug ss7 mtp2 iac 0
*Mar  8 09:17:58.367:itu2IAC_Start  chnl=0  MTP2IAC_IDLE
*Mar  8 09:17:58.739:itu2IAC_Rcvd_SIO  chnl=0  MTP2IAC_NOT_ALIGNED
*Mar  8 09:17:58.739:itu2IAC_Rcvd_SIN  chnl=0  MTP2IAC_ALIGNED
*Mar  8 09:17:58.739:itu2IAC_Rcvd_SIN  chnl=0  MTP2IAC_PROVING
*Mar  8 09:18:02.814:itu2IAC_T4_TMO   chnl=0  MTP2IAC_PROVING

Note See the MTP 2 specification for details.

debug ss7 mtp2 lsc

To display information about SS7 MTP 2 Link State Control (LSC) events and transitions, enter the debug ss7 mtp2 lsc privileged EXEC command:

debug ss7 mtp2 lsc [channel]

The no form of this command disables debugging output:

no debug mtp2 lsc

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 lsc command output:

Router# debug ss7 mtp2 lsc 0
*Mar  8 09:20:21.105:itu2LSC_Rcvd_SIOS  chnl=0  MTP2LSC_INSERVICE
*Mar  8 09:20:21.121:itu2LSC_Retrieve_BSNT  chnl=0  MTP2LSC_OOS
*Mar  8 09:20:22.058:itu2LSC_SetEmergency  chnl=0  MTP2LSC_OOS
*Mar  8 09:20:22.058:itu2LSC_Start  chnl=0  MTP2LSC_OOS
*Mar  8 09:20:33.785:itu2LSC_AlignmentNotPossible  chnl=0
MTP2LSC_INITIAL_ALIGNMENT
*Mar  8 09:20:38.758:itu2LSC_SetEmergency  chnl=0  MTP2LSC_OOS
*Mar  8 09:20:38.758:itu2LSC_Start  chnl=0  MTP2LSC_OOS
*Mar  8 09:20:44.315:itu2LSC_Rcvd_SIO  chnl=0  MTP2LSC_INITIAL_ALIGNMENT
*Mar  8 09:20:44.315:itu2LSC_Rcvd_SIO  chnl=0  MTP2LSC_INITIAL_ALIGNMENT
*Mar  8 09:20:44.319:itu2LSC_Rcvd_SIE  chnl=0  MTP2LSC_INITIAL_ALIGNMENT
*Mar  8 09:20:44.319:itu2LSC_Rcvd_SIE  chnl=0  MTP2LSC_INITIAL_ALIGNMENT
*Mar  8 09:20:48.397:itu2LSC_AlignmentComplete  chnl=0
MTP2LSC_INITIAL_ALIGNMENT

Note See the MTP 2 specification for details.

debug ss7 mtp2 msu

To trace backhaul SS7 MTP 2 Message Signaling Units (MSUs), enter the debug ss7 mtp2 msu command during a low-traffic period. The no form of this command disables debugging output.

debug ss7 mtp2 msu [channel]

The no form of this command disables debugging output:

no debug mtp2 msu

MSUs carry addressed signaling information for call setup and tear down and SS7 network management.

The command output can slow traffic under busy conditions, so enter it when there is low traffic.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 msu command output for channel 2:

Router# debug ss7 mtp2 msu 2
*Mar  1 01:01:12.447: MTP2: send MSU Ind  ch=2  len=25
*Mar  1 01:01:12.455: MTP2: rcvd MSU Req  ch=2  len=252

debug ss7 mtp2 packet

To display debug messages for SS7 MTP 2 packets, enter the debug ss7 mtp2 packet privileged EXEC privileged EXEC command:

debug ss7 mtp2 packet [channel] [all]

The no form of this command disables debugging output:

no debug ss7 mtp2 packet

Syntax Description
Default
Command Mode

channel—Enter a logical channel number. Valid values are from 0 through 3.

all—Enter a logical channel number. Valid values are from 0 through 3.

If you do not specify a channel number or the all keyword, the command displays information for channel 0.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 packet command output for channel 0:

Router# debug ss7 mtp2 packet 0
*Mar  1 00:53:00.052: MTP2 incoming trace enabled on channel 0.
*Mar  1 00:53:00.052: MTP2 outgoing trace enabled on channel 0.
*Mar  1 00:53:07.220: ---- Incoming Rudp msg (20 bytes) ----
SM_msg_type    0x00008000
protocol_type  0x0001
msg_ID         0x0001
msg_type       0x0044
channel_ID     0x0000
bearer_ID      0x0000
length         0x0004
data           0x00000001
 
*Mar  1 00:53:07.224: ---- Outgoing Rudp msg (132 bytes) ----
SM_msg_type    0x00008000
protocol_type  0x0001
msg_ID         0x0001
msg_type       0x0045
channel_ID     0x0000
bearer_ID      0x0000
length         0x0074
data           0x0000001E 0x00000000 0x00000000 0x00000000
               0x00000000 0x00000000 0x00000000 0x00000000
               0x00000000 0x00000000 0x00000000 0x00000000
               0x00000002 0x00000000 0x00008317 0x00000000
               0x00000002 0x00000000 0x00000008 0x009B5C97
               0x00000000 0x0032A2A7 0x0000061C 0x000000BF
               0x00000000 0x00000000 0x00000006 0x00000000
               0x000000ED
 
*Mar  1 00:53:11.343: ---- Outgoing Rudp msg (41 bytes) ----
SM_msg_type    0x00008000
protocol_type  0x0001
msg_ID         0x0000
msg_type       0x0011
channel_ID     0x0000
bearer_ID      0x0000
length         0x0019
data           0x8201190A 0x03190A00 0x11F01122 0x33445566
               0x778899AA 0xBBCCDDEE
 
*Mar  1 00:53:11.351: ---- Incoming Rudp msg (41 bytes) ----
SM_msg_type    0x00008000
protocol_type  0x0001
msg_ID         0x0001
msg_type       0x0010
channel_ID     0x0000
bearer_ID      0x0000
length         0x0019
data           0xB203190A 0x01190A00 0x21F01122 0x33445566
               0x778899AA 0xBBCCDDEE
 
*Mar  1 00:53:13.739: ---- Incoming Rudp msg (27 bytes) ----
SM_msg_type    0x00008000
protocol_type  0x0001
msg_ID         0x0001
msg_type       0x0010
channel_ID     0x0000
bearer_ID      0x0000
length         0x000B
data           0x9503190A 0x01190A00

debug ss7 mtp2 rcv

To display information about SS7 MTP 2 receiver state machine events and transitions, enter the debug ss7 mtp2 rcv privileged EXEC command:

debug ss7 mtp2 rcv [channel]

The no form of this command disables debugging output:

no debug ss7 mtp2 rcv

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 rcv command output:

Router# debug ss7 mtp2 rcv 0
*Mar  8 09:22:35.160:itu2RC_Stop  chnl=0  MTP2RC_INSERVICE
*Mar  8 09:22:35.164:itu2RC_Start  chnl=0  MTP2RC_IDLE
*Mar  8 09:22:52.565:BSNR not in window
        bsnr=2  bibr=0x80    fsnr=66  fibr=0x80  fsnf=0  fsnl=127  fsnx=0
fsnt=127
 
*Mar  8 09:22:52.569:BSNR not in window
        bsnr=2  bibr=0x80    fsnr=66  fibr=0x80  fsnf=0  fsnl=127  fsnx=0
fsnt=127
 
*Mar  8 09:22:52.569:AbnormalBSN_flag == TRUE
*Mar  8 09:22:52.569:itu2RC_Stop  chnl=0  MTP2RC_INSERVICE
*Mar  8 09:22:57.561:itu2RC_Start  chnl=0  MTP2RC_IDLE

Note See the MTP 2 specification for details.

debug ss7 mtp2 suerm

To display information about SS7 MTP 2 Signal Unit Error Rate Monitor (SUERM) state machine events and transitions, enter the debug ss7 mtp2 suerm privileged EXEC command:

debug ss7 mtp2 suerm [channel]

The no form of this command disables debugging output:

no debug mtp2 suerm

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 suerm command output:

Router# debug ss7 mtp2 suerm 0
*Mar  8 09:33:51.108:itu2SUERM_Stop  chnl=0  MTP2SUERM_MONITORING
*Mar  8 09:34:00.155:itu2SUERM_Start  chnl=0  MTP2SUERM_IDLE

Note See the MTP 2 specification for details.

debug ss7 mtp2 timer

To display information about SS7 Message Transfer Part level 2 (MTP 2) timer starts and stops, enter the debug ss7 mtp2 timer privileged EXEC command:

debug ss7 mtp2 timer [channel]

The no form of this command disables debugging output:

no debug mtp2 timer

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 mtp2 timer command output for channel 0:

Router# debug ss7 mtp2 timer 0
*Mar  1 01:08:13.738: Timer T7 (ex delay) Start    chnl=0
*Mar  1 01:08:13.762: Timer T7 (ex delay) Stop     chnl=0
*Mar  1 01:08:13.786: Timer T7 (ex delay) Start    chnl=0
*Mar  1 01:08:13.810: Timer T7 (ex delay) Stop     chnl=0
*Mar  1 01:08:43.819: Timer T7 (ex delay) Start    chnl=0
*Mar  1 01:08:43.843: Timer T7 (ex delay) Stop     chnl=0
*Mar  1 01:08:48.603: Timer T7 (ex delay) Start    chnl=0
*Mar  1 01:08:48.627: Timer T7 (ex delay) Stop     chnl=0
*Mar  1 01:09:13.784: Timer T7 (ex delay) Start    chnl=0
*Mar  1 01:09:13.808: Timer T7 (ex delay) Stop     chnl=0
*Mar  1 01:09:13.885: Timer T7 (ex delay) Start    chnl=0
*Mar  1 01:09:13.909: Timer T7 (ex delay) Stop     chnl=0

debug ss7 mtp2 txc

To display information about SS7 MTP 2 transmit state machine events and transitions, enter the debug ss7 mtp2 txc privileged EXEC command:

debug ss7 mtp2 txc [channel]

The no form of this command disables debugging output:

no debug mtp2 txc

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

In the following example of debug ss7 mtp2 txc command output for channel 2, the transmission control is functioning and updating Backward Sequence Numbers (BSNs):

Router# debug ss7 mtp2 txc 2
*Mar  1 01:10:13.831: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:13.831: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:13.831: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:13.839: itu2TXC_PDU2xmit  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:13.863: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:13.863: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:23.603: itu2TXC_PDU2xmit  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:23.627: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:23.627: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:23.631: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:23.631: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:23.635: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:43.900: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:43.900: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE
*Mar  1 01:10:43.900: itu2TXC_bsn_update  chnl=2  MTP2TXC_INSERVICE

Note See the MTP 2 specification for details.

debug ss7 sm session

Use this command to watch the Session Manager and RUDP sessions. The Session Manager is responsible for establishing the RUDP connectivity to the Cisco MGC.

To display debugging information for an SS7 Session Manager session, enter the debug ss7 sm session privileged EXEC command:

debug ss7 sm session [session]

The no form of this command disables debugging output:

no debug ss7 sm session

Syntax Description
Default
Command Mode

session—Specifies a session, 0 or 1.

If you do not specify a session, the command shows information for both sessions.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 sm session command output for session 0. The Session Manager has established the connection (RUDP_CONN_OPEN_SIG):

Router# debug ss7 sm session-0
*Mar  8 09:37:52.119:SM:rudp signal RUDP_SOFT_RESET_SIG, session = 0
*Mar  8 09:37:58.129:SM:rudp signal RUDP_CONN_RESET_SIG, session = 0
*Mar  8 09:37:58.129:SM:Opening session[0] to 10.5.0.4:8060
*Mar  8 09:37:58.137:SM:rudp signal RUDP_CONN_OPEN_SIG, session = 0

debug ss7 sm set

Use this command to watch Session Manager progression for the set, which is the aggregation of the two RUDP sessions.

To display debugging information for the SS7 Session Manager switchover timer, enter the debug ss7 sm set privileged EXEC privileged EXEC command:

Note The no form of this command disables debugging output.

debug ss7 sm set

The no form of this command disables debugging output:

no debug ss7 sm set

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 sm set command output. The Session Manager connection is up (SM_UP):

Router# debug ss7 sm set
*Mar  6 12:37:10.176:SESSION SET STATE-INACTIVE   Active session = 1
*Mar  6 12:37:10.176:Session[0]:SM SESSION STATE-OPENING  |  Session[1]:
SM SESSION STATE-STANDBY
*Mar  6 12:37:10.176:Event:0x02-SM EVENT-ACTIVE on Session 1
*Mar  6 12:37:10.176:SM:SM_UP sent to MTP2

debug ss7 sm timer

Use this command to watch Session Manager timer progressions.

To enable SS7 Session Manager timer debugging, enter the debug rudp timer privileged EXEC privileged EXEC command:

debug ss7 sm timer

The no form of this command disables debugging output:

no ss7 sm timer

Syntax Description
Default
Command Mode

This command has no arguments or keywords.

This command has no default values or behaviors.

Command History


Release	Modification
12.0(7)XR and 12.1(1)T	This command was introduced.

Example

Following is an example of debug ss7 sm timer command output:

Router# debug ss7 sm timer
*Mar  6 12:38:30.483:SM:Open Timer is stopped for Session=0
*Mar  6 12:38:30.483:SM:Open Timer is started for Session=0
*Mar  6 12:41:56.141:SM:Fail-Over Timer is stopped

State	Description	Possible Values
MTP2LSC	Indicates the overall status of the link.	OOS—The link is out of service. INITIAL_ALIGNMENT—The link is in a transitional link alignment state. ALIGNED_READY—The link is in a transitional link alignment state. ALIGNED_NOT_READY—The link is in a transitional link alignment state. INSERVICE—The link is in service. PROCESSOR_OUTAGE—There is an outage in the local processor. This state implies that the link has been aligned. POWER_OFF—It is possible you do not have the I/O memory set to at least 40 percent. There may not be enough memory for the SS7 MTP2 signaling.
MTP2IAC	Indicates the status of the initial alignment control state machine.	IDLE—The state machine is idle. It is not aligning the link. NOT_ALIGNED—The state machine has begun the alignment process. ALIGNED—The link has exchanged the alignment handshake with the remote device. PROVING—The link alignment is being proven. This is a waiting period before the LSC state changes to INSERVICE.
MTP2TXC	Indicates the status of the transmission control state machine.	IDLE—The state machine is inactive. INSERVICE—The state machine is the active transmitter.
MTP2RC	Indicates the status of the receive control state machine.	IDLE—The state machine is inactive. INSERVICE—The state machine is the active receiver.
MTP2SUERM	Indicates the status of the signal unit error monitor (SUERM).	IDLE—The state machine is inactive. MONITORING—The SUERM is active. SUERM uses a leaky-bucket algorithm to track link errors while the link is in service. If the number of link errors reaches the threshold, the link is taken out of service.
MTP2AERM	Indicates the status of the alignment error rate monitor state machine (AERM).	IDLE—The state machine is inactive. MONITORING—Alignment error monitor is active. This is part of the alignment process.
MTP2CONGESTION	Indicates the status of the congestion control state machine.	IDLE—The state machine is inactive. No congestion is detected; normal traffic flow. ACTIVE—Congestion has been declared. The Cisco SLT is sending SIBs every T5, which indicates that the remote end should stop sending new MSUs until the local Cisco SLT can catch up.
Congestion Backhaul	Indicates congestion status of the backhaul link between the Cisco SLT and the Cisco MGC.	Abate—The link between the Cisco SLT and the Cisco MGC is not under congestion. Onset—The link between the Cisco SLT and the Cisco MGC is under congestion and the Cisco MGC should stop sending new MSUs until the local Cisco SLT can catch up.
Remote Processor Outage	Indicates the processor outage status of the remote.	TRUE indicates that the remote is in processor outage. FALSE indicates that the remote has not declared processor outage.

Field	Description
OMIACAlignAttemptCount OMIACAlignFailCount OMIACAlignCompleteCount	Counts for Initial Alignment Control (IAC) attempts.
OMMSU_TO_XMIT-_Count	Related to the results of the show ss7 sm stats command PDU_pkts_receive_count statistic. The number shown in OMMSU_TO_XMIT_Count is less than the PDU_pkts_receive_count because OMMSU_TO_XMIT_Count shows the number of PDUs going out on the link, while the PDU_pkts_receive_count includes PDUs that are internal to MTP2.
OMMSU_RCV_Count	Related to the results of the show ss7 sm stats command packets_send_count.
OMLSSU_XMIT_Count OMLSSU_XMIT_SINCount OMLSSU_XMIT_SIECount OMLSSU_XMIT_SIOCount OMLSSU_XMIT_SIOSCount OMLSSU_XMIT_SIPOCount OMLSSU_XMIT_SIBCount	Represent the number of times that MTP 2 has posted the specific Link Status Signal Unit (LSSU) to MTP 1. They do not show the number of LSSUs actually sent over the link.
OMLSSU_RCV_Count OMLSSU_RCV_SINCount OMLSSU_RCV_SIECount OMLSSU_RCV_SIOCount OMLSSU_RCV_SIOSCount OMLSSU_RCV_SIPOCount OMLSSU_RCV_SIBCount OMLSSU_RCV_InvalidCount	Represent the number of LSSUs received by MTP 2 from MTP 1. Due to MTP 1 filtering, this is not the same as the actual LSSUs sent over the link.
OMT1_TMO_Count OMT2_TMO_Count OMT3_TMO_Count OMT4_TMO_Count OMT5_TMO_Count OMT6_TMO_Count OMT7_TMO_Count OMT8_TMO_Count OMTA_TMO_Count OMTF_TMO_Count OMTO_TMO_Count OMTA_TMO_Count OMLostTimerCount	Contain information about timers in use.
OMLostBackhaulMsgs	Related to the results of the show ss7 sm stats command PDU_pkts_recieve_count statistic. The counter indicates how many messages received from the Cisco MGC have been lost due to a lack of resources in the Cisco SLT. For example, if the Cisco MGC sends 100 MSUs and the Cisco SLT only has 65 free buffers, 35 MSUs might be lost.

Field	Description
Remote Host, Local Host	IP address and port number for the session.
retrans_t	Retransmission timer value.
cumack_t	Cumulative acknowledgment timer value.
m_cumack	Maximum number of segments that can be received before the RUDP sends an acknowledgment.
m_outseq	Maximum number of out-of-sequence segments that can be received before the RUDP sends an extended acknowledgment.
m_rcvnum	Maximum number of segments that the remote end can send before receiving an acknowledgment.

Parameter	Description	Default	Range
T1	Aligned/ready Timer Duration (Milliseconds)	13000	1000 through 65535
T2	Not Aligned Timer (Milliseconds)	11500	1000 through 65535
T3	Aligned Timer (Milliseconds)	11500	1000 through 65535
T4-Emergency-Proving	Emergency Proving Timer (Milliseconds)	600	1000 through 65535
T4-Normal-Proving	Normal Proving Period (Milliseconds)	2300	1000 through 65535
T5	Sending Sib Timer (Milliseconds)	100	80 through 65535
T6	Remote Congestion Timer (Milliseconds)	6000	1000 through 65535
T7	Excessive Delay Timer (Milliseconds)	1000	500 through 65535
lssu-len	1 Or 2 Byte Lssu Format	1	1 through 2
unacked-MSUs	Maximum number of MSUs waiting ACK	127	16 through 127
proving-attempts	Maximum number of attempts to prove alignment	5	3 through 8
SUERM-threshold	SUERM error rate threshold	64	32 through 128
SUERM-number-octets	SUERM octet counting mode	16	8 through 32
SUERM-number-signal-units	Signal units (good or bad) needed to dec ERM	256	128 through 512
Tie-AERM-Emergency	AERM emergency error rate threshold	1	1 through 8
Tie-AERM-Normal	AERM normal error rate threshold	4	1 through 8

Parameter	Description	Default	Range
T1	Aligned/ready Timer Duration (milliseconds)	40000	1000 through through 65535
T2	Not Aligned Timer (milliseconds)	5000	1000 through 65535
T3	Aligned Timer (milliseconds)	1000	1000 through 65535
T4-Emergency-Proving	Emergency Proving Timer (milliseconds)	500	1000 through 65535
T4-Normal-Proving	Normal Proving Timer (milliseconds)	8200	1000 through 65535
T5	Sending Sib Timer (milliseconds)	100	80 through 65535
T6	Remote Congestion Timer (milliseconds)	6000	1000 through 65535
T7	Excessive Delay Timer (milliseconds)	1000	1000 through 65535
lssu-len	1 or 2 byte LSSU format	1	1 through 2
msu-len	1 or 2 byte MSSU format	1	1 through 2
unacked-MSUs	Maximum number of MSUs waiting ACK	127	16 through 127
proving-attempts	Maximum number of attempts to prove alignment	5	3 through 8
SUERM-threshold	SUERM error rate threshold	64	32 through 128
SUERM-number-octets	SUERM octet counting mode	16	8 through 32
SUERM-number-signal-units	Signal units (good or bad) needed to SUERM	256	128 through 512
Tie-AERM-Emergency	AERM emergency error rate threshold	1	1 through 8
Tin-AERM-Normal	AERM normal error rate threshold	4	1 through 8

Parameter	Description	Default	Range
T1	Aligned/ready Timer Duration (Milliseconds)	15000	1000 through 65535
T2	Not Aligned Timer (Milliseconds)	5000	1000 through 65535
T3	Aligned Timer (Milliseconds)	3000	1000 through 65535
T4-Emergency-Proving	Emergency Proving Timer (Milliseconds)	3000	1000 through 65535
T5	Sending Sib Timer (Milliseconds)	200	80 through 65535
T6	Remote Congestion Timer (Milliseconds)	2000	1000 through 65535
T7	Excessive Delay Timer (Milliseconds)	3000	1000 through 65535
TA	SIE interval timer (milliseconds)	20	10 through 500
TF	FISU interval timer (milliseconds)	20	10 through 500
TO	SIO interval timer (milliseconds)	20	10 through 500
TS	SIOS interval timer (milliseconds)	20	10 through 500
unacked-MSUs	Maximum number of MSUs waiting ACK	40	16 through 40
proving-attempts	Maximum number of attempts to prove alignment	5	3 through 8
SUERM-threshold	SUERM error rate threshold	64	32 through 128
SUERM-number-octets	SUERM octet counting mode	16	8 through 32
SUERM-number-signal-units	Signal units (good or bad) needed to dec ERM	256	128 through 512
Tie-AERM-Emergency	AERM emergency error rate threshold	1	1 through 8

Event Code	Explanation
0x0	Local processor outage
0x1	Local processor outage recovered
0x2	Entered a congested state
0x3	Exited a congested state
0x4	Physical layer up
0x5	Physical layer down
0x7	Protocol error (see cause code)
0x8	Link alignment lost
0x9	Retransmit buffer full
0xa	Retransmit buffer no longer full
0xb	Negative acknowledgment received from far end
0xc	Remote entered congestion
0xd	Remote exited congestion
0xe	Remote entered processor outage
0xf	Remote exited processor outage

Cause Code	Explanation
0x0	Cause unknown - default
0x1	Management initiated
0x2	Abnormal BSN (Backward Sequence Number)
0x3	Abnormal FIB (Forward Indicator Bit)
0x4	Congestion discard

Cause Code	Explanation
0x0	Layer management request
0x1	SUERM (Signal Unit Error Monitor) failure
0x2	Excessively long alignment period
0x3	T7 timer expired
0x4	Physical interface failure
0x5	Two or three invalid BSNs
0x6	Two or three invalid FIBs
0x7	LSSU (Link Status Signal Unit) condition
0x8	Excessive MTP 2 congestion
0x13	SIOs (Service Information Octets) received in Link State Control (LSC)
0x14	Timer T2 expired waiting for SIO
0x15	Timer T3 expired waiting for SIE/SIN
0x16	SIO received in initial alignment control (IAC)
0x17	Proving period failure
0x18	Timer T1 expired waiting for FISU (Fill-In Signal Unit)
0x19	SIN received in in-service state
0x20	CTS lost
0x25	No resources

Table of Contents

Cisco Signaling Link Terminal Command Reference