Downloads |
Table Of Contents
Integrated Signaling Link Terminal
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Provisioning and Enabling SS7 Digital Links
Provisioning and Enabling SS7 Serial Links
Provisioning CT3 Digital SS7 Links
Verifying CT3 Digital SS7 Links
Disabling CT3 Digital SS7 Links
Provisioning Remaining Timeslots for PRI
Digital SS7 Link Configuration Example
Serial SS7 Link Configuration Example
Provisioning Remaining Timeslots for Voice or Data Example
Verifying Provisioned Links Example
Integrated Signaling Link Terminal
Feature History
12.2(11)T
This feature was introduced on the Cisco AS5350 and the Cisco AS5400.
This feature module describes the Integrated Signaling Link Terminal feature in
Cisco IOS Release 12.2(11)T and includes the following sections:•
Supported Standards, MIBs, and RFCs
Feature Overview
The Integrated Signaling Link Terminal (SLT) feature pulls existing Cisco distributed Message Transfer Part (MTP) SS7 signaling architecture functionality—previously available only on Cisco 26xx-based SLTs—directly onto a single Cisco AS5350 or Cisco AS5400 gateway. Like the Cisco 26xx-based SLT, the Integrated SLT on a Cisco AS5350 or Cisco AS5400 backhauls upper-layer Signaling System 7 (SS7) protocols across an IP network using Cisco Reliable User Datagram Protocol (RUDP), terminating the MTP1 and MTP2 layers of the SS7 protocol stack at the Media Gateway Controller (MGC).
Using the 2-, 4-, or 8-PRI dial feature card (DFC) or the CT3 (28-PRI) DFC card, this feature is designed for small points of presence (POPs) that require only one or two network access servers (NASs) or Voice-Over-IP (VoIP) gateways as part of a dial or VoIP solution. This feature eliminates the use of the Cisco 26xx-based SLT in the product configuration.
When the Integrated SLT feature is implemented, a Cisco AS5350 or Cisco AS5400 functions as an SS7 signaling data link terminal and as a NAS, voice gateway, or both when universal ports are used.
The Integrated SLT feature supports the following:
•
•
•
•
•
•
•
•
•
•
Figure 1, Figure 2, and Figure 3 show variations of the SLT architecture.
Figure 1 Integrated SLT Architecture
Figure 2 Multiple SS7 Terminations over Multiple NAS Gateways
Figure 3 Standalone NAS Gateway
Benefits
Four SS7 Link Support
The Integrated SLT feature supports up to four SS7 signaling links per Cisco AS5350 or Cisco AS5400, with each link running at a maximum of 0.4 erlangs. Any combination of serial and digital links is also supported. It is possible to have all digital links on the same trunk.
Note
No Hardware Changes
This feature is designed to run on the existing Cisco AS5350 or Cisco AS5400 platforms. No new hardware changes are required. The 1T Serial Line Interface on Cisco AS5350 and Cisco AS5400 trunk DFC cards can be used to terminate SS7 A-link traffic. The DS1 and DS3 interfaces on the Cisco AS5350 and Cisco AS5400 8-PRI and CT3 trunk DFCs are used to support SS7 A-link or F-link digital link interface. Fast Ethernet interfaces on the Cisco AS5350 and Cisco AS5400 motherboard are used to backhaul SS7 message signaling units (MSUs) to MGCs.
Reduced Rack Space and Power Requirements
Having NAS and Cisco SLT functionality coexist on a single Cisco AS5350 or Cisco AS5400 reduces the rack space and power requirements necessary for small POP offices and permits bearer hairpinning without external cabling and connectivity.
Remote Functionality
Cisco SLT functionality in a NAS platform functions remotely from the MGC.
T1/E1 Time Slots Function as SS7 Signaling Links
This feature supports the use of any time slot on any T1/E1 as an SS7 signaling link, especially time slots 16 for E1 and 24 for T1, to meet the demand for replacement of old D channels.
Restrictions
The following currently available Cisco 26xx SLT features are not available in the Integrated SLT on the Cisco AS5350 and Cisco AS5400 platforms:
•
•
•
•
Note
Related Features and Technologies
For information about the Cisco MGC and SS7, see the following documentation:
•
•
Related Documents
•
•
•
•
•
•
•
•
•
•
•
•
Supported Platforms
•
•
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
No new or modified RFCs are supported by this feature.
Configuration Tasks
See the following sections for specific configuration tasks for the Integrated SLT feature using new or changed command-line interface (CLI). Configuration tasks for the Integrated SLT feature are similar to those used to configure the Cisco 26xx-based Cisco SLT with changes to the CLI for use on the Cisco AS5350 and Cisco AS5400 platforms. Refer to the instructions in the "Configuration Tasks" section of the Cisco Signaling Link Terminal feature module. Each task in the list is identified as either required or optional.
•
•
•
•
•
•
•
•
•
•
Provisioning and Enabling SS7 Digital Links
Use the information in this section if your system uses digital SS7 digital links. If your system uses serial links, use the configuration tasks in the "Provisioning and Enabling SS7 Serial Links" section.
On Cisco 26xx-based SLTs, the encapsulation for interface serial objects is forced to SS7. For NAS platforms, however, the encapsulation for channel-group serial interface objects defaults to HDLC, thus, the Integrated SLT encapsulation type must be explicitly set to SS7 to override this default.
The explicit use of the ss7 encapsulation command is new to the Integrated SLT feature and is only available and is visible on interface serial objects created by the channel-group command (refer to the "Configuring the T1/E1 Multiflex Trunk Interfaces" section of the Cisco Signaling Link Terminal Upgrade Procedures document for more information about this command). Once encapsulation is set to SS7, the encapsulation command for that object is no longer available and cannot be changed back to HDLC. As with Cisco 26xx-based SLTs, there is no need to specify whether the SS7 link is to be used as an A-link or an F-link.
The first set of steps in this section create the interface serial object that will later be configured as an SS7 digital link.
The next set of steps convert the interface serial object created above into an SS7 digital link.
Verifying SS7 Digital Links
To display information for a given session channel ID, enter the show ss7 mtp1 channel-id command in privileged EXEC mode. If no channel ID number is selected, information for all assigned channel IDs is displayed. This command is useful for determining which channel IDs have already been allocated.
Router# show ss7 mtp1 channel-idSS7 MTP1 Session-channel [all]:channel assigned interface------- ------------------0 7/3:0 (digital)1 7/3:1 (digital)To display information for each provisioned SS7 link, including the name of the serial interface for the link, the assigned MGC port, whether the link is serial (12-in-1 port) or digital (E1/T1 trunk DS0), the assigned channel ID, and whether the link is stopped or started, enter the show ss7 mtp1 links command in privileged EXEC mode:
Router# show ss7 mtp1 linksSS7 MTP1 Links [num = 2, platform max = 4]:sessioninterface type MGC state channel--------- -------- --- ------------ -------7/3:0 digital 7/3 STARTED 07/3:1 digital 7/2 STARTED 1To verify the initial T1 digital interface, enter the show controllers t1 command in privileged EXEC mode:
Router# show controllers t1T1 7/3 is up.Applique type is Channelized T1Cablelength is short 133No alarms detected.alarm-trigger is not setVersion info of slot 7: HW: 768, PLD Rev: 1Framer Version: 0x8Manufacture Cookie Info:EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x02,Board Hardware Version 3.0, Item Number 73-3996-03,Board Revision A0, Serial Number JAB04390AV2,PLD/ISP Version <unset>, Manufacture Date 13-Oct-2000.Framing is ESF, Line Code is B8ZS, Clock Source is Line.Data in current interval (788 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsTotal Data (last 12 15 minute intervals):66437 Line Code Violations, 5685 Path Code Violations,8 Slip Secs, 136 Fr Loss Secs, 8 Line Err Secs, 0 Degraded Mins,0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 152 Unavail SecsTo verify the initial E1 digital interface enter the show controllers e1 command in privileged EXEC mode:
Router# show controllers e1E1 0/2 is up.Applique type is Channelized E1 - balancedCablelength is UnknownNo alarms detected.Version info Firmware: 19990702, FPGA: 6Framing is CRC4, Line Code is HDB3, Clock Source is Line.Data in current interval (599 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsTotal Data (last 10 15 minute intervals):435334 Line Code Violations, 1 Path Code Violations,8 Slip Secs, 69 Fr Loss Secs, 9 Line Err Secs, 0 Degraded Mins,8 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 69 Unavail SecsE1 0/3 is down.Applique type is Channelized E1 - balancedCablelength is UnknownFar End Block Errors DetectedReceiver has loss of signal.Version info Firmware: 19990702, FPGA: 6Framing is CRC4, Line Code is HDB3, Clock Source is Line.Data in current interval (602 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 602 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 603 Unavail SecsTotal Data (last 10 15 minute intervals):0 Line Code Violations, 0 Path Code Violations,0 Slip Secs, 9000 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 9000 Unavail SecsTo learn more about the virtual serial interface, enter the show interfaces serial slot/trunk:channel-group command in privileged EXEC mode, as in the following example:
Router# show interfaces serial 7/3:1Serial7/3:1 is up, line protocol is downHardware is PowerQUICC SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,reliability 255/255, txload 4/255, rxload 1/255Encapsulation SS7 MTP2, loopback not setKeepalive set (10 sec)Last input never, output 00:00:00, output hang neverLast clearing of "show interface" counters 03:53:40Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 26000 bits/sec, 836 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort11580159 packets output, 46320636 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 output buffer failures, 0 output buffers swapped out2 carrier transitionsDCD=up DSR=down DTR=down RTS=down CTS=downTo learn more about the low-level hardware-related resources associated with this interface serial object, enter the show controllers serial slot/trunk:channel-group command in privileged EXEC mode, as in the following example:
Router# show controllers serial 7/3:1Interface Serial7/3:1Hardware is PowerQUICC SCCSCC port[0-3]: 2Session-channel-id [0-3]: 1SS7 Link-type : digitalSS7 Link-state: STARTEDIDB-state : IDBS_UPTDM: Trunk/DS0 Local-Side Backplane Local-Side SCC7/00:2 -> 0:STi0/8 -> 0:STio00/1 -> 1:STo3/2 -> SCC27/00:2 <- 0:STo0/8 <- 1:STio08/1 <- 1:STi3/2 <- SCC2PowerQUICC SS7 Serial StatisticsHost sizeof Linestate = 2344Host Addr Linestate = 0x2C30BF64Trunk sizeof Linestate = 2344Port State (Admin): STARTEDLine (Operational): UPOne Sec Count 149186RX SCC Interrupts: 14924563RX SCC->Host BD Copies: 0RX Host Doorbell Interrupts: 0RX Host->SCC BD Copies: 0TX Host Doorbell Interrupts: 14924563TX Host->SCC BD Copies: 12458365TX SCC Interrupts: 14924563TX SCC Start Interrupts 14924563TX SCC->Host BD Copies: 12458349TX Underrun Errors: 0TX CTS Lost Errors: 0TX Clock Glitch Errors: 0RX CP/SDMA Overrun Errors: 0RX BD Overrun Errors: 0RX CD Lost Errors: 0RX Abort Sequence Errors: 0RX Non-Octet Align Errors: 0RX CRC Errors: 0RX Clock Glitch Errors: 0MPC860 SCC RegistersPSMR = 0x8, GSMR_HI = 0x2, GSMR_LO = 0x33, DSR = 0x7E7ERBASE = 0x2900, TBASE = 0x2A00, RFCR = 0x18, TFCR = 0x18RSTATE = 0x0, TSTATE = 0x188020A9RBPTR = 0x2900, TBPTR = 0x2A08MRBLR = 0x1F4C_MASK = 0xF0B8, C_PRES = 0xFFFF, EFSUC = 0x0, MFLR = 0x116ERM = 0x0, NOCTETS = 0x10, NOCTETS_CNT = 0x7ERM_THRESH = 0x40, ERM_EFSUS = 0x100, ERM_EFSUS_CNT = 0x100SS7_OPTIONS = 0xB, MASK1 = 0xFFFFFFFF, MASK2 = 0xFFInterrupt Registers:Config [CICR]=0x0, Pending [CIPR]=0x8000Mask [CIMR]=0x3804E46, In-srv [CISR]=0x0SCC Mask [SCCM]=0x1FPort A [PADIR]=0x4030, [PAPAR]=0xA333[PAODR]=0x0, [PADAT]=0xACFFPort B [PBDIR]=0x3FE08, [PBPAR]=0xC0[PBODR]=0x0, [PBDAT]=0x3FDFFPort C [PCDIR]=0x0, [PCPAR]=0x1[PCSO]=0x30, [PCDAT]=0xFCE, [PCINT]=0xFCCPort D [PDDIR]=0xFF0, [PDPAR]=0xC, [PDDAT]=0x17D3MPC860 TX BD RingTX Head = 0x1TX Tail = 0x1TX Tx_prev_rexmit = 0x10tmd(62E57F34): status 9C00 length 4 buf_ptr 4126AE00tmd(62E57F3C): status 9C00 length 4 buf_ptr 412684FCtmd(62E57F44): status 9C00 length 4 buf_ptr 412687B8tmd(62E57F4C): status 9C00 length 4 buf_ptr 41268A74tmd(62E57F54): status 9C00 length 4 buf_ptr 41268D30tmd(62E57F5C): status 9C00 length 4 buf_ptr 41268FECtmd(62E57F64): status 9C00 length 4 buf_ptr 412692A8tmd(62E57F6C): status 9C00 length 4 buf_ptr 41269564tmd(62E57F74): status 9C00 length 4 buf_ptr 41269820tmd(62E57F7C): status 9C00 length 4 buf_ptr 41269ADCtmd(62E57F84): status 9C00 length 4 buf_ptr 41269D98tmd(62E57F8C): status 9C00 length 4 buf_ptr 4126A054tmd(62E57F94): status 9C00 length 4 buf_ptr 4126A310tmd(62E57F9C): status 9C00 length 4 buf_ptr 4126A5CCtmd(62E57FA4): status 9C00 length 4 buf_ptr 4126A888tmd(62E57FAC): status BC00 length 4 buf_ptr 4126AB44MPC860 RX BD RingRX Head = 0x0RX Tail = 0x0rmd(62E57EAC): status 9000 length 0 buf_ptr 40BA6FD0rmd(62E57EB4): status 9000 length 0 buf_ptr 40BA6D10rmd(62E57EBC): status 9000 length 0 buf_ptr 40BA6A60rmd(62E57EC4): status 9000 length 0 buf_ptr 40BA67A0rmd(62E57ECC): status 9000 length 0 buf_ptr 40BA64E0rmd(62E57ED4): status 9000 length 0 buf_ptr 40BA6220rmd(62E57EDC): status 9000 length 0 buf_ptr 40BA5F70rmd(62E57EE4): status 9000 length 0 buf_ptr 40BA5CB0rmd(62E57EEC): status 9000 length 0 buf_ptr 40BA59F0rmd(62E57EF4): status 9000 length 0 buf_ptr 40BA5730rmd(62E57EFC): status 9000 length 0 buf_ptr 40BA5480rmd(62E57F04): status 9000 length 0 buf_ptr 40BA51C0rmd(62E57F0C): status 9000 length 0 buf_ptr 40BA4F00rmd(62E57F14): status 9000 length 0 buf_ptr 40BA4C40rmd(62E57F1C): status 9000 length 0 buf_ptr 40BA4990rmd(62E57F24): status B000 length 0 buf_ptr 40BA46D0PowerQUICC SCC specific errors:0 input aborts on receiving flag sequence0 throttles, 0 enables0 overruns0 transmitter underrunsDisabling SS7 Digital Links
The following steps remove SS7 digital links. Begin these steps in global configuration mode.
Provisioning and Enabling SS7 Serial Links
Use the information in this section if your system uses serial SS7 links. If your system uses digital links, use the configuration tasks in the "Provisioning and Enabling SS7 Digital Links" section.
An SS7 serial link is automatically created for interface 0 whenever an 8-PRI or CT3 DFC board is inserted. SS7 links need to have a session-channel ID assigned to them using the channel-id command in interface configuration mode. This value is carried in backhaul messages to and from the MGC. For messages received from the MGC, the channel-link ID field tells the software to which SS7 link the message is to be forwarded. On existing SLT platforms, this value is implicitly assigned by software based on the slot and interface number. An extra provisioning step has been added with the Integrated SLT feature to explicitly assign these session-channel IDs to each SS7 link.
To provision and enable the link, use the following commands beginning in global configuration mode. For the serial SS7 link, the interface serial object already exists and is named "interface serial slot/0."
Verifying SS7 Serial Links
To display information for a given session-channel ID, enter the show ss7 mtp1 channel-id command in privileged EXEC mode. If no channel ID number is selected, information for all assigned channel IDs is displayed. This command is useful for determining which channel IDs have already been allocated.
Router# show ss7 mtp1 channel-idSS7 MTP1 Session-channel [all]:channel assigned interface------- ------------------1 7/0 (serial)To display information for each provisioned SS7 link, including the name of the serial interface for the link, the assigned MGC port, whether the link is serial (12-in-1 port) or digital (E1/T1 trunk DS0), assigned channel ID, and whether the link is stopped or started, enter the show ss7 mtp1 links command in privileged EXEC mode:
Router# show ss7 mtp1 linksSS7 MTP1 Links [num = 4, platform max = 4]:sessioninterface type SCC state channel--------- -------- --- ------------ -------7/0 serial 7/0 STARTED 3To learn more about the virtual serial interfaces, enter the show interfaces serial slot/0 command in privileged EXEC mode, as shown in the following output:
Router# show interfaces serial 7/0Serial7/0 is up, line protocol is downHardware is PowerQUICC SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,reliability 255/255, txload 4/255, rxload 1/255Encapsulation SS7 MTP2, loopback not setKeepalive set (10 sec)Last input never, output 00:00:00, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 30000 bits/sec, 955 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort10599771 packets output, 42399084 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDCD=up DSR=up DTR=up RTS=down CTS=upTo learn more about the low-level hardware-related resources associated with this interface serial object, enter the show controllers serial slot/0 command in privileged EXEC mode, as in the following example:
Router# show controllers serial 7/0Interface Serial7/0Hardware is PowerQUICC SCCSCC port[0-3]: 0Session-channel-id [0-3]: 3SS7 Link-type : serialSS7 Link-state: STARTEDIDB-state : IDBS_UPDTE V.35 TX and RX clocks detected.PowerQUICC SS7 Serial StatisticsHost sizeof Linestate = 2344Host Addr Linestate = 0x2C30AD14Trunk sizeof Linestate = 2344Port State (Admin): STARTEDLine (Operational): UPOne Sec Count 117226RX SCC Interrupts: 11727361RX SCC->Host BD Copies: 0RX Host Doorbell Interrupts: 0RX Host->SCC BD Copies: 0TX Host Doorbell Interrupts: 11727361TX Host->SCC BD Copies: 11184548TX SCC Interrupts: 11727361TX SCC Start Interrupts 11727361TX SCC->Host BD Copies: 11184532TX Underrun Errors: 0TX CTS Lost Errors: 0TX Clock Glitch Errors: 0RX CP/SDMA Overrun Errors: 0RX BD Overrun Errors: 0RX CD Lost Errors: 0RX Abort Sequence Errors: 0RX Non-Octet Align Errors: 0RX CRC Errors: 0RX Clock Glitch Errors: 0MPC860 SCC RegistersPSMR = 0x8, GSMR_HI = 0x2, GSMR_LO = 0x33, DSR = 0x7E7ERBASE = 0x2400, TBASE = 0x2500, RFCR = 0x18, TFCR = 0x18RSTATE = 0x0, TSTATE = 0x188920A3RBPTR = 0x2400, TBPTR = 0x2520MRBLR = 0x1F4C_MASK = 0xF0B8, C_PRES = 0xFFFF, EFSUC = 0x0, MFLR = 0x116ERM = 0x0, NOCTETS = 0x10, NOCTETS_CNT = 0x2ERM_THRESH = 0x40, ERM_EFSUS = 0x100, ERM_EFSUS_CNT = 0x100SS7_OPTIONS = 0xB, MASK1 = 0xFFFFFFFF, MASK2 = 0xFFInterrupt Registers:Config [CICR]=0x0, Pending [CIPR]=0x70008000Mask [CIMR]=0x3804E46, In-srv [CISR]=0x0SCC Mask [SCCM]=0x1FPort A [PADIR]=0x4030, [PAPAR]=0xA333[PAODR]=0x0, [PADAT]=0xACFFPort B [PBDIR]=0x3FE08, [PBPAR]=0xC0[PBODR]=0x0, [PBDAT]=0x3FDFFPort C [PCDIR]=0x0, [PCPAR]=0x1[PCSO]=0x30, [PCDAT]=0xFCE, [PCINT]=0xFCCPort D [PDDIR]=0xFF0, [PDPAR]=0xC, [PDDAT]=0x17D3MPC860 TX BD RingTX Head = 0xETX Tail = 0xETX Tx_prev_rexmit = 0x10tmd(62E57F34): status 9C00 length 4 buf_ptr 41427360tmd(62E57F3C): status 9C00 length 4 buf_ptr 4142761Ctmd(62E57F44): status 9C00 length 4 buf_ptr 414278D8tmd(62E57F4C): status 9C00 length 4 buf_ptr 41427B94tmd(62E57F54): status 9C00 length 4 buf_ptr 41427E50tmd(62E57F5C): status 9C00 length 4 buf_ptr 4142810Ctmd(62E57F64): status 9C00 length 4 buf_ptr 414283C8tmd(62E57F6C): status 9C00 length 4 buf_ptr 41428684tmd(62E57F74): status 9C00 length 4 buf_ptr 41428940tmd(62E57F7C): status 9C00 length 4 buf_ptr 41428BFCtmd(62E57F84): status 9C00 length 4 buf_ptr 41428EB8tmd(62E57F8C): status 9C00 length 4 buf_ptr 41429174tmd(62E57F94): status 9C00 length 4 buf_ptr 41429430tmd(62E57F9C): status 9C00 length 4 buf_ptr 414296ECtmd(62E57FA4): status 1C00 length 4 buf_ptr 41426DE8tmd(62E57FAC): status BC00 length 4 buf_ptr 414270A4MPC860 RX BD RingRX Head = 0x0RX Tail = 0x0rmd(62E57EAC): status 9000 length 0 buf_ptr 40B1E450rmd(62E57EB4): status 9000 length 0 buf_ptr 40B1E190rmd(62E57EBC): status 9000 length 0 buf_ptr 40B1DEE0rmd(62E57EC4): status 9000 length 0 buf_ptr 40B1DC20rmd(62E57ECC): status 9000 length 0 buf_ptr 40B1D960rmd(62E57ED4): status 9000 length 0 buf_ptr 40B1D6A0rmd(62E57EDC): status 9000 length 0 buf_ptr 40B1D3F0rmd(62E57EE4): status 9000 length 0 buf_ptr 40B1D130rmd(62E57EEC): status 9000 length 0 buf_ptr 40B1CE70rmd(62E57EF4): status 9000 length 0 buf_ptr 40B1CBB0rmd(62E57EFC): status 9000 length 0 buf_ptr 40B1C900rmd(62E57F04): status 9000 length 0 buf_ptr 40B1C640rmd(62E57F0C): status 9000 length 0 buf_ptr 40B1C380rmd(62E57F14): status 9000 length 0 buf_ptr 40B1C0C0rmd(62E57F1C): status 9000 length 0 buf_ptr 40B1BE10rmd(62E57F24): status B000 length 0 buf_ptr 40B1BB50PowerQUICC SCC specific errors:0 input aborts on receiving flag sequence0 throttles, 0 enables0 overruns0 transmitter underrunsDisabling SS7 Serial Links
The following steps remove SS7 serial links. Begin these steps in global configuration mode.
Provisioning CT3 Digital SS7 Links
The following steps create the interface serial object that will later be configured as a CT3 SS7 digital link. Enter these commands beginning in global configuration mode:
The following steps convert the interface serial object created above into a CT3 SS7 digital link.
Verifying CT3 Digital SS7 Links
To verify the interface, enter the show ss7 mtp1 link command in privileged EXEC mode:
Router# show ss7 mtp1 linkSS7 MTP1 Links [num = 3, platform max = 4]:sessioninterface type SCC state channel--------- -------- --- ------------ -------7/0:0 digital 7/3 STARTED 06/0:8:23 digital 6/3 STARTED 17/6:23 digital 7/1 STARTED 2To display information for all 28 T1 lines within each T3 port adapter in the router, enter the
show controllers t3 command in privileged EXEC mode:Router# show controllers t3T3 6/0 is down.Applique type is Channelized T3Transmitter is sending remote alarm.Receiver has loss of signal.MDL transmission is disabledFEAC code received: No code is being receivedFraming is C-BIT Parity, Line Code is B3ZS, Clock Source is InternalData in current interval (740 seconds elapsed):0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsTotal Data (last 74 15 minute intervals):4849590 Line Code Violations, 4849590 P-bit Coding Violation,4 C-bit Coding Violation, 0 P-bit Err Secs,0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,66600 Unavailable Secs, 0 Line Errored Secs,0 C-bit Errored Secs, 0 C-bit Severely Errored SecsTo display information about the newly configured interfaces, enter the show interfaces serial slot-number/0 command in privileged EXEC mode. The following example uses slot 6:
Router# show interfaces serial 6/0Serial6/0 is initializing, line protocol is downHardware is PowerQUICC SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation SS7 MTP2, loopback not setKeepalive set (10 sec)Last input never, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDCD=down DSR=down DTR=down RTS=down CTS=downDisabling CT3 Digital SS7 Links
The following steps remove CT3 digital SS7 links. Begin these steps in global configuration mode.
Provisioning Remaining Timeslots for PRI
The following sections describe how to provision time slots for voice or data calls on PRI interfaces (trunks) for which one or more time slots have already been configured as SS7 links. The provisioning of the links themselves is the same as previous examples, but the following processes provision remaining timeslots for voice or data. (The SS7 link is called an F-link after this process is done.)
There are two instances for using this configuration:
•
•
The following example configuration assumes that you want to use timeslot 3 on trunk 7 of slot 4 as an SS7 link using a T1 card. You can use the remaining timeslots on that trunk for voice traffic.
The following steps convert the interface serial object created above into an SS7 digital link.
The following example configuration shows how you might use the ISDN D-channel as an SS7 link assuming you want to use timeslot 24 on trunk 7 of slot 4 as the SS7 link using a T1 card. You can use the remaining timeslots on that trunk for voice traffic.
The following steps convert the interface serial object created above into an SS7 digital link.
The following optional steps allow a D-channel to be used as a B-channel for voice or data.
The following optional steps convert the interface serial object created above into an SS7 digital link.
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
Digital SS7 Link Configuration Example
The following example shows configured SS7 links on timeslots 12 and 24 of trunk 3 of 8PRI card in slot 7:
Router# configure terminalRouter(config)# !Router(config)# !Router(config)# controller t1 7/3Router(config-controller)# channel-group 11 timeslots 12Router(config-controller)# channel-group 23 timeslots 24Router(config-controller)# exitRouter(config)# !Router(config)# !Router(config)# interface serial 7/3:11Router(config-if)# encapsulation ss7Router(config-if)# channel-id 3Router(config-if)# no shutdownRouter(config-if)# exitRouter(config)# !Router(config)# !Router(config)# interface serial 7/3:23Router(config-if)# encapsulation ss7Router(config-if)# channel-id 2Router(config-if)# no shutdownRouter(config-if)# exitRouter(config)# endSerial SS7 Link Configuration Example
The following example shows a configured SS7 link on the 1T serial port of the 8PRI card in slot 7:
Router# configure terminal
Router(config)# !
Router(config)# !
Router(config)# interface serial 7/0
Router(config-if)# channel-id 1
Router(config-if)# no shutdown
Router(config-if)# exit
Router(config)# endProvisioning Remaining Timeslots for Voice or Data Example
The following example shows how to convert remaining timeslots on trunk 3 of an 8-PRI card in slot 7 into B-channels for voice or data using the pri-group command. Because the default D-channel (timeslot 24) is now reserved as an SS7 link, you must move the D-channel to another timeslot not already used as an SS7 link that is within the selected range of timeslots in the pri-group command. This is done by using the new (hidden) rlm-timeslot option. You can choose to make this new timeslot usable as a B-channel for voice or data by using the isdn rlm-group command.
Router# configure terminal
Router(config)# !
Router(config)# !
Router(config)# !
Router(config)# controller t1 7/3
Router(config-controller)# pri-group timeslots 1-11,13-23 nfas_d primary nfas_int 0
nfas_group 0 rlm-timeslot 3
Router(config-controller)# exit
Router(config)# !
RRouter(config)# interface serial 7/3:2
Router(config-if)# isdn rlm-group 0
Router(config-if)# exit
Router(config)# end
Router#
Verifying Provisioned Links Example
The following example shows how configured SS7 links are verified:
Router# show ss7 mtp1 linksSS7 MTP1 Links [num = 4, platform max = 4]:sessioninterface type SCC state channel--------- -------- --- ------------ -------7/3:11 digital 7/3 STARTED 37/3:23 digital 7/2 STARTED 27/0 serial 7/0 STARTED 1Troubleshooting Tips
Use the following debug commands to troubleshoot your configuration:
•
•
•
Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
Note
New Command
Modified Commands
channel-id
To assign a session channel ID to a Signaling System 7 (SS7) serial link, use the channel-id command in interface configuration mode. To disable, use the no form of this command.
channel-id channel-id
no channel-id
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
The channel-id command is visible only if the object's encapsulation type is changed to SS7.
Before an SS7 serial link can be enabled using the no shutdown command, you must enter the channel-id command in interface configuration mode to assign a session channel ID to the SS7 serial link. This ID is unique to the Cisco AS5350 and Cisco AS5400, and the command is visible only for provisioned objects whose encapsulation type is the new SS7 value.
The channel identifier is reserved when you explicitly assign an ID using the channel-id command for the associated serial interface object. This fails if the selected channel identifier is currently assigned to another link or if all channel identifiers are already assigned.
A channel identifier is released when the no channel-id command is entered. The link must first be shut down to do this.
Examples
The following example shows a unique session channel ID zero being assigned to the Cisco AS5350 or Cisco AS5400:
Router(config-if)# channel-id 0
Related Commands
channel-group
To direct high-level data link control (HDLC) traffic from the T1/E1 interface to the digital signaling processor (DSP) card, use the channel-group command in controller configuration mode. To unassign a channel group, use the no form of this command.
Cisco 2600 Series, Cisco 3660, Cisco 3725, and Cisco 3745
channel-group channel-group-number timeslots range [speed bit-rate]
no channel-group channel-group-number
Cisco 2611 (Cisco Signaling Link Terminal or SLT)
channel-group channel-number
no channel-group channel-number
Cisco AS5350 and Cisco AS5400 Series
channel-group channel-group-number
no channel-group channel-group-number
Cisco MC3810
channel-group channel-number timeslots range [speed bit-rate}]
no channel-group [channel-number timeslots range]
Syntax Description
Defaults
The T1/E1 line is connected to the Motorola MPC-860x processor serial communication controller (SCC) or network module with two voice or wide area network (WAN) interface card (WIC/VIC) slots and 0/1/2 FastEthernet ports DSCC4 by default on Cisco 2600 series, Cisco 2600XM, Cisco 3660, Cisco 3725, and Cisco 3745 routers.
There is no default behavior or values on the Cisco SLT (Cisco 2611).
The serial interface object encapsulation is set to HDLC on a NAS (Cisco AS5350 and Cisco AS5400 series).
The default line speed when configuring a T1 controller is 56 kbps on the Cisco 2600 series, Cisco 2600XM, Cisco 3660, Cisco 3725, Cisco 3745, and the Cisco MC3810.
The default line speed when configuring an E1 controller is 64 kbps on the Cisco 2600 series, Cisco 2600XM, Cisco 3660, Cisco 3725, Cisco 3745, and the Cisco MC3810.
Command Modes
Controller configuration mode
Command History
Usage Guidelines
By default, the channel-group command on a NAS sets the serial interface object encapsulation to HDLC. You must override the default by entering the encapsulation ss7 command for that serial interface object. Once this is done, encapsulation cannot be changed again for that object. The SS7 encapsulation option is new to the Integrated Signaling Link Terminal feature and is only available for interface serial objects created by the channel-group command. The Integrated Signaling Link Terminal feature added SLT functionality on Cisco AS5350 and Cisco AS5400 platforms.
A digital SS7 link can be deleted by entering the no channel-group channel-group-number command on the associated T1/E1 controller. The link must first be stopped using the no shutdown command. It is not necessary to remove the channel ID association first.
Use the channel-group command in configurations where the router or access server must communicate with a T1 or E1 fractional data line. The channel group number may be arbitrarily assigned and must be unique for the controller. The time slot range must match the time slots assigned to the channel group. The service provider defines the time slots that comprise a channel group.
Note
Valid values for the bit-rate argument have changed. If you specify 56 kbps, the channel group is limited to 14 channels on the Cisco MC3810 MultiFlex Trunk (MFT). Because the 56 keyword is the default, specify the 64 keyword when you need more than 14 channels.
The channel group number can be 0 or 1 on the Cisco SLT (Cisco 2611).
The channel-group command also applies to Voice over Frame Relay, Voice over ATM, and Voice over HDLC on the Cisco MC3810.
Examples
The following example shows how to explicitly set the encapsulation type to SS7 to override the HDLC default. This example uses an 8PRI DFC card inserted into slot 7, and DS0-timeslot 3 on trunk 5 of that card is used as an SS7 link:
Router# configure terminalRouter(config)# controller t1 7/5Router(config-controller)# channel-group 2 timeslots 3Router(config-controller)# exitRouter(config)# interface serial 7/5:2Router(config-if)# encapsulation ss7Router(config-if)# channel-id 0Router(config-if)# no shutdownRouter(config-if)# endRouter#The following example defines three channel groups. Channel-group 0 consists of a single time slot, channel-group 8 consists of 7 time slots and runs at a speed of 64 kbps per time slot, and channel-group 12 consists of a single time slot.
channel-group 0 timeslots 1channel-group 8 timeslots 5,7,12-15,20 speed 64channel-group 12 timeslots 2The following example configures a channel group on controller T1 0 on a Cisco MC3810:
controller T1 0channel-group 10 timeslots10 64
Note
Related Commands
Displays information for a given session channel ID.
Sets the encapsulation type to SS7.
debug ss7 mtp1
Note
To initiate SS7 MTP1 debugging, enter the debug ss7 mtp1 command in global configuration mode during a low-traffic period. The no form of this command disables debugging output.
debug ss7 mtp1 [ipc | link-state | oir | rx | scc-regs | siram | tdm-info | tx]
no debug ss7 mtp1
Syntax Description
Command Modes
Global configuration
Defaults
Debug is disabled
Command History
12.2(11)T
This command was introduced on the Cisco AS5350 and Cisco AS5400 Signaling Link Terminal (SLT).
Usage Guidelines
The following debug commands are not used in this release:
•
•
•
•
Examples
To turn on message tracing between the host processor and the trunk firmware for each trunk card inserted, use the debug ss7 mtp1 ipc command.
For example, there is a digital link in slot 7, trunk 0, channel-group 0 (therefore, timeslot 1). When you enter show ss7 mtp1 links, the following output is displayed:
Router# show ss7 mtp1 linksSS7 MTP1 Links [num = 1, platform max = 4]:sessioninterface type SCC state channel--------- -------- --- ------------ -------7/0:0 digital 7/3 STOPPED 0Notice that the link is stopped in this example. Enter the following commands:
Router# debug ss7 mtp1 ipcRouter# configure terminalRouter(config)# interface serial 7/0:0Router(config-if)# no shutdownRouter(config-if)# endYou would see trace output similar to the following:
00:01:27:from Trunk(7):TRUNK_SERIAL_STOP(3), link_type=200:01:27:from Trunk(7):TRUNK_SERIAL_START(3), link_type=2In this case, the output means that for the SS7 link that is using SCC3 on the trunk card in slot 7 (link 7/0:0), the host processor has told the board firmware to STOP then START.
To show low-level (MTP1) state changes for the internal state-machine implemented for each SS7 link, use the debug ss7 mtp1 link-state command. The following output shows the different MTP1 states link Serial 7/0:0 goes through during shutdown, no shutdown, and debug.
For example, if you stopped the SS7 link 7/0:0 (shutdown), then restarted it (no shutdown), you could see MTP1 state changes by enabling debugging, as follows:
Router# debug ss7 mtp1 link-stateRouter# configure terminalRouter(config)# interface serial 7/0:0Router(config-if)# shutdown01:02:20:%TRUNK_SERIAL-3-STATE_GENERIC:At ../src-7k-as5400/as5400_ss7_link.c:511 [Serial7/0:0]:STOP:STARTED -> STOP_PENDINGss7_link_ll_stop 7/0:0:Tx shadow ring has0 unsent buffers01:02:20:%TRUNK_SERIAL-3-STATE_GENERIC:At ../src-7k-as5400/as5400_ss7_link.c:1010 [Serial7/0:0]: FW_STOPPED:STOP_PENDING -> STOPPEDNow restart the link:
Router(config-if)# no shutdown01:02:26:ss7_link_start:slot=7/SCCport=3 current state is STOPPED01:02:26:%TRUNK_SERIAL-3-STATE_GENERIC:At ../src-7k-as5400/as5400_ss7_link.c:1417 [Serial7/0:0]: START:STOPPED -> START_PENDING01:02:26:%TRUNK_SERIAL-3-STATE_GENERIC:At ../src-7k-as5400/as5400_ss7_link.c:1164 [Serial7/0:0]: STOP_START:START_PENDING -> STOP_START_PENDINGss7_link_ll_stop 7/0:0:Tx shadow ring has 0 unsent buffers01:02:26:%TRUNK_SERIAL-3-STATE_GENERIC:At ../src-7k-as5400/as5400_ss7_link.c:1010 [Serial7/0:0]: FW_STOPPED:STOP_START_PENDING -> START_PENDING01:02:26:%TRUNK_SERIAL-3-STATE_GENERIC:At ../src-7k-as5400/as5400_ss7_link.c:1234 [Serial7/0:0]: FW_STARTED:START_PENDING -> STARTEDTo show detailed information about how TDM timeslots on the DFC trunk card on the host backplane are allocated and deallocated based on link configuration activity, use the debug ss7 mtp1 tdm-info command.
For example, if you wanted to create a digital SS7 link on timeslot 1 of trunk 0 for an 8PRI board in slot 7, and you would like to see traces of the TDM resources allocated, you would enable TDM debugging using the debug ss7 mtp1 tdm-info command then create the new SS7 link as described above, as in the following example:
Router# debug ss7 mtp1 tdm-infoRouter# configure terminalRouter(config)# controller t1 7/0Router(config-controller)# channel-group 0 timeslots 1Router(config-controller)# exitRouter(config)# interface serial 7/0:0Router(config-if)# encapsulation ss7Due to the debug flag, the following information is displayed:
05:26:55: ss7_link_flink_tdm_setup:card type for slot 7 is T1 8PRI05:26:55: ds0-side BEFORE call to tdm_allocate_bp_ts()slot = 7unit = 0 (trunk)channel = 4stream = 0group = 005:26:55: scc-side BEFORE call to tdm_allocate_bp_ts()slot = 7unit = 29channel = 3 (SCC-port)stream = 3group = 005:26:55:05:26:55:TDM(PRI:0x28002000):Close PRI framer st0 ch405:26:55:<<< tdm_allocate_bp_ts(ss7_ch) SUCCEEDED >>>05:26:55:scc-side AFTER call to tdm_allocate_bp_ts()bp_channel = 4bp_stream = 0bp_ts->bp_stream = 0bp_ts->bp_channel = 4bp_ts->vdev_slot = 7bp_ts->vdev_channel = 3bp_ts->vdev_slot = 7 should be the same as the CLI slot, and bp_ts->vdev_channel = 3 should be *->channel.
When you later remove the SS7 link, other information is displayed showing how resources are cleaned up.
Related Commands
debug ss7 mtp2
To trace backhaul SS7 MTP 2 message signaling units (MSUs), enter the debug ss7 mtp2 command in global configuration mode during a low-traffic period. The no form of this command disables debugging output.
debug ss7 mtp2 [aerm | backhaul | cong | iac | lsc | lssu | msu | packet [all] | rcv | seurm | timer | txc][channel]
no debug ss7 mtp2
Syntax Description
Command Modes
Global configuration
Defaults
Debug is disabled.
Command History
Usage Guidelines
If you do not specify a channel number with each keyword, the command displays information for channel 0.
Examples
The following is an example of debug ss7 mtp2 aerm command output. See the MTP 2 specification tables for details:
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_MONITORINGThe 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=0x0The following is an example of debug ss7 mtp2 cong command output. See the MTP 2 specification tables for details:
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=0MTP2CONGESTION_ACTIVE*Mar 8 09:11:01.143:itu2CongestionAbatement chnl=0 MTP2CONGESTION_IDLEThe following is an example of debug ss7 mtp2 iac command output. See the MTP 2 specification tables for details:
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_PROVINGThe following is an example of debug ss7 mtp2 lsc command output. See the MTP 2 specification tables for details:
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=0MTP2LSC_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=0MTP2LSC_INITIAL_ALIGNMENTThe following is an example of debug ss7 mtp2 msu command output for channel 2. The output for this command can slow traffic under busy conditions, so enter it when there is low traffic. See the MTP 2 specification tables for details about the command output:
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=252Warning
The 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 0x00008000protocol_type 0x0001msg_ID 0x0001msg_type 0x0044channel_ID 0x0000bearer_ID 0x0000length 0x0004data 0x00000001*Mar 1 00:53:07.224: ---- Outgoing Rudp msg (132 bytes) ----SM_msg_type 0x00008000protocol_type 0x0001msg_ID 0x0001msg_type 0x0045channel_ID 0x0000bearer_ID 0x0000length 0x0074data 0x0000001E 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x000000000x00000002 0x00000000 0x00008317 0x000000000x00000002 0x00000000 0x00000008 0x009B5C970x00000000 0x0032A2A7 0x0000061C 0x000000BF0x00000000 0x00000000 0x00000006 0x000000000x000000ED*Mar 1 00:53:11.343: ---- Outgoing Rudp msg (41 bytes) ----SM_msg_type 0x00008000protocol_type 0x0001msg_ID 0x0000msg_type 0x0011channel_ID 0x0000bearer_ID 0x0000length 0x0019data 0x8201190A 0x03190A00 0x11F01122 0x334455660x778899AA 0xBBCCDDEE*Mar 1 00:53:11.351: ---- Incoming Rudp msg (41 bytes) ----SM_msg_type 0x00008000protocol_type 0x0001msg_ID 0x0001msg_type 0x0010channel_ID 0x0000bearer_ID 0x0000length 0x0019data 0xB203190A 0x01190A00 0x21F01122 0x334455660x778899AA 0xBBCCDDEE*Mar 1 00:53:13.739: ---- Incoming Rudp msg (27 bytes) ----SM_msg_type 0x00008000protocol_type 0x0001msg_ID 0x0001msg_type 0x0010channel_ID 0x0000bearer_ID 0x0000length 0x000Bdata 0x9503190A 0x01190A00The following is an example of debug ss7 mtp2 rcv command output. See the MTP 2 specification tables for details:
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 windowbsnr=2 bibr=0x80 fsnr=66 fibr=0x80 fsnf=0 fsnl=127 fsnx=0fsnt=127*Mar 8 09:22:52.569:BSNR not in windowbsnr=2 bibr=0x80 fsnr=66 fibr=0x80 fsnf=0 fsnl=127 fsnx=0fsnt=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_IDLEThe following is an example of debug ss7 mtp2 suerm command output. See the MTP 2 specification tables for details:
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_IDLEWarning
The 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=0Warning
The following is an example of debug ss7 mtp2 txc command output for channel 2. The transmission control is functioning and updating Backward Sequence Numbers (BSNs). See the MTP 2 specification for details:
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*Mar 1 01:10:43.908: itu2TXC_PDU2xmit chnl=2 MTP2TXC_INSERVICE*Mar 1 01:10:43.928: itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE*Mar 1 01:10:43.932: itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICThe following MTP2 specification tables explain codes that appear in the command output.
0x0
Cause unknown - default
0x1
Management initiated
0x2
Abnormal BSN (Backward Sequence Number)
0x3
Abnormal FIB (Forward Indicator Bit)
0x4
Congestion discard
Related Commands
debug ss7 sm
To display debug messages for the a Signaling System 7 (SS7) Session Manager, use the debug ss7 sm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ss7 sm [session 0-3 | set | timer]
no debug ss7 sm session
Syntax Description
0-3
Specifies a session ID number 0 to 3.
session
Sets Session Manager session debug.
set
Sets Session Manager debug.
timer
Sets Session Manager timer debug.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to watch the Session Manager and Reliable User Data Protocol (RUDP) sessions. The Session Manager is responsible for establishing the RUDP connectivity to the Virtual Switch Controller (VSC).
Support for up to four Session Manager sessions was added. Session Manager sessions are now numbered 0 through 3. This feature changes the CLI syntax, and adds sessions 2 and 3.
Examples
The following is an example of debug ss7 sm command output using the session keyword. The Session Manager has established the connection (RUDP_CONN_OPEN_SIG) for session 3.
Router# debug ss7 sm session 3*Mar 8 09:37:52.119:SM:rudp signal RUDP_SOFT_RESET_SIG, session = 3*Mar 8 09:37:58.129:SM:rudp signal RUDP_CONN_RESET_SIG, session = 3*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 = 3The 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 = 0Related Commands
encapsulation ss7
To explicitly set the encapsulation type to SS7 and override the serial interface objects high-level data link control (HDLC) default, use the encapsulation ss7 command in interface configuration mode.
encapsulation ss7
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
The SS7 encapsulation command is new with the Integrated SLT feature and is available only for interface serial objects created by the channel-group command. For network access server (NAS) platforms, the encapsulation for channel group serial interface objects defaults to HDLC. You must explicitly set the encapsulation type to SS7 to override this default.
When encapsulation is set to SS7, the encapsulation command for that object is no longer available. A serial SS7 link is deleted only when its associated dial feature card (DFC) card is removed. As with existing Cisco 26xx-based SLTs, you do not need to specify whether the SS7 link is to be used as an
A-link or an F-link.By itself this command does not select the correct encapsulation type. Therefore, once created, you must set the encapsulation type to the new SS7 value, as well as assign a session channel ID to the link at the serial interface command level.
The configuration on a digital SS7 link can be saved (no shutdown) only when its encapsulation is successfully set to SS7 and it has been assigned a channel identifier.
Examples
To learn more about the virtual serial interface and check SS7 encapsulation, enter the show interfaces serial slot/trunk:channel-group command in privileged EXEC mode, as in the following example:
Router# show interfaces serial 7/3:1Serial7/3:1 is up, line protocol is downHardware is PowerQUICC SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,reliability 255/255, txload 4/255, rxload 1/255Encapsulation SS7 MTP2, loopback not setKeepalive set (10 sec)Last input never, output 00:00:00, output hang neverLast clearing of "show interface" counters 03:53:40Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 26000 bits/sec, 836 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort11580159 packets output, 46320636 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 output buffer failures, 0 output buffers swapped out2 carrier transitionsDCD=up DSR=down DTR=down RTS=down CTS=downRelated Commands
pri-group (pri-slt)
To specify an ISDN PRI on a channelized T1 or E1 controller, use the pri-group (pri-slt) command in controller configuration mode. To remove the ISDN PRI configuration, use the no form of this command.
pri-group [timeslots timeslot-range [nfas_d [backup | none | primary [nfas_int number]] [nfas-group number [iua as-name]]]
no pri-group
Syntax Description
Defaults
No ISDN-PRI group is configured.
Command Modes
Controller configuration
Command History
Usage Guidelines
The pri-group (pri-slt) command provides another way to bind a D channel to a specific IUA AS. This option allows the RLM group to be configured at the pri-group level instead of in the D channel configuration. For example, a typical configuration would look like the following:
controller t1 1/0/0pri-group timeslots 1-24 nfas_d pri nfas_int 0 nfas_group 1 iua asnameBefore you enter the pri-group command, you must specify an ISDN-PRI switch type and an E1 or T1 controller.
When configuring NFAS, you use an extended version of the pri-group command to specify the following values for the associated channelized T1 controllers configured for ISDN:
•
•
•
The iua keyword is used to bind an NFAS group to the IUA AS.
When binding the D channel to an IUA AS, the as-name must match the name of an AS set up during IUA configuration.
Before you can modify a PRI group on a Media Gateway Controller (MGC), you must first shut down the D channel.
The following shows how to shut down the D channel:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Dchannel3/0:1Router(config-if)# shutdownExamples
The following example configures the NFAS primary D channel on one channelized T1 controller, and binds the D channel to an IUA AS. This example uses the Cisco AS5400 and applies to T1, which has 24 timeslots and is used mainly in North America and Japan:
Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as5400-4-1The following example applies to E1, which has 32 timeslots and is used by the rest of the world:
Router(config-controller)# pri-group timeslots 1-31 nfas-d primary nfas-int 0 nfas-group 1 iua as5400-4-1The following example configures ISDN-PRI on all time slots of controller E1 on a Cisco 2600 series router:
Router(config)# controller E1 4/1Router(config-controller)# pri-group timeslots 1-7,16In the following example, the rlm-timeslot keyword automatically creates interface serial 4/7:11 (4/7:0:11 if you are using the CT3 card) for the D channel object on a Cisco AS5350. You can choose any timeslot other than 24 to be the virtual container for the D channel parameters for ISDN.
Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 0 rlm-timeslot 3Related Commands
isdn switch-type
Configures the Cisco 2600 series router PRI interface to support QSIG signaling.
show controllers serial
To display serial interface information including the Cisco Media Gateway Controller (MGC) port, channel ID, link type (serial or digital), TDM mappings if digital, link state, Tx and Rx statistics, MGC register values, and Tx and Rx BD ring information, enter the
show controllers serial command in privileged EXEC mode.show controllers serial [slot/port]
Cisco 7500 Series and Cisco 7000 Series with the RSP7000 and RSP7000CI
show controllers serial [slot/port-adapter/port]
Cisco 5350 and Cisco 5400 Series
show controllers serial {slot/port:subinterface}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The information displayed is generally useful for diagnostic tasks performed by technical support personnel only. For the PA-E3 or PA-T3 port adapters, the show controllers serial command also displays configuration information such as the framing, clock source, bandwidth limit, whether scrambling is enabled, the national bit, the international bits, and DSU mode configured on the interface. Also displayed is the performance statistics for the current interval and last 15-minute interval and whether any alarms exist.
Examples
The following is a typical example of the show controllers serial command:
Router# show controllers serial 0/2:0Interface Serial0/2:0Hardware is PowerQUICC MPC860idb at 0x81143590, driver data structure at 0x81145474SCC Registers:General [GSMR]=0x2:0x00000033, Protocol-specific [PSMR]=0x8Events [SCCE]=0x0200, Mask [SCCM]=0x001F, Status [SCCS]=0x02Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7EInterrupt Registers:Config [CICR]=0x00367F80, Pending [CIPR]=0x04000246Mask [CIMR]=0x60240000, In-srv [CISR]=0x00000000Command register [CR]=0xD40Port A [PADIR]=0x00F0, [PAPAR]=0x25F0[PAODR]=0x0000, [PADAT]=0x5A4FPort B [PBDIR]=0x0000F, [PBPAR]=0x0000E[PBODR]=0x00000, [PBDAT]=0x37FFDPort C [PCDIR]=0x00C, [PCPAR]=0xA00[PCSO]=0x000, [PCDAT]=0x5F2, [PCINT]=0xFFFReceive Ringrmd(68012930): status 9000 length 6 address 2DA22E4rmd(68012938): status 9000 length 6 address 2DA3AA4rmd(68012940): status 9000 length 6 address 2DA1E24rmd(68012948): status 9000 length 6 address 2DA27A4rmd(68012950): status 9000 length 6 address 2DA5724rmd(68012958): status 9000 length 6 address 2DA14A4rmd(68012960): status 9000 length 6 address 2DA5264rmd(68012968): status 9000 length 6 address 2DA4684rmd(68012970): status 9000 length 6 address 2DA4424rmd(68012978): status 9000 length 6 address 2DA1964rmd(68012980): status 9000 length 6 address 2DA4B44rmd(68012988): status 9000 length 6 address 2DA60A4rmd(68012990): status 9000 length 6 address 2DA2544rmd(68012998): status 9000 length 6 address 2DA3124rmd(680129A0): status 9000 length 6 address 2DA0FE4rmd(680129A8): status B000 length 6 address 2DA3844Transmit Ringtmd(680129B0): status DC00 length 4 address 2AD9EA8tmd(680129B8): status DC00 length 4 address 2AD7568tmd(680129C0): status DC00 length 4 address 2ADA428tmd(680129C8): status DC00 length 4 address 2ADA6E8tmd(680129D0): status DC00 length 4 address 2AD7DA8tmd(680129D8): status DC00 length 4 address 2AD5468tmd(680129E0): status DC00 length 4 address 2AD8328tmd(680129E8): status DC00 length 4 address 2AD85E8tmd(680129F0): status DC00 length 4 address 2AD5CA8tmd(680129F8): status CE00 length 4 address 2AD8B68tmd(68012A00): status DC00 length 4 address 2AD8E28tmd(68012A08): status DC00 length 4 address 2AD64E8tmd(68012A10): status DC00 length 4 address 2AD67A8tmd(68012A18): status DC00 length 4 address 2AD9668tmd(68012A20): status DC00 length 4 address 2AD9928tmd(68012A28): status FC00 length 4 address 2AD6FE8SPI Mode [SPMODE]=0xF70, Events [SPIE]=0x0Mask [SPIM]=0x0, Command [SPCOM]=0x0SI Mode [SIMODE]=0x80408040, Global [SIGMR]=0xECmnd [SICMR]=0x0, Stat [SISTR]=0x0SI Clock Route [SICR]=0x00004040SCC GENERAL PARAMETER RAM (at 0x68013D00)Rx BD Base [RBASE]=0x2930, Fn Code [RFCR]=0x18Tx BD Base [TBASE]=0x29B0, Fn Code [TFCR]=0x18Max Rx Buff Len [MRBLR]=1548Rx State [RSTATE]=0x0, BD Ptr [RBPTR]=0x2970Tx State [TSTATE]=0x188920A3, BD Ptr [TBPTR]=0x2A08SCC SS7 PARAMETER RAM (at 0x68013D38)CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8Error-free SUs [EFSUC] = 22927Max frm len [MFLR] = 278Erm [ERM] = 0x0,N [NOCTETS] = 16, N_cnt [NOCTETS_CNT] = 12, T [ERM_THRESH] = 64,D [ERM_EFSUS] = 256, D_cnt [ERM_EFSUS_CNT] = 97SS7 options [SS7_OPT] = 0x10FFilter masks [MASK1] = 0xFFFFFFFF, [MASK2] = 0xFFbuffer size 1524PQUICC SCC specific errors:0 input aborts on receiving flag sequence0 throttles, 0 enables0 overruns0 transmitter underruns0 transmitter CTS losts
Related Commands
show interfaces serial
To find out about channel groups configured as virtual serial interfaces, verify that the router has high-level data link control (HDLC) encapsulation on the interface, and verify that the interface sees the loopback, use the show interfaces serial command in privileged EXEC mode.
Cisco 5350 and Cisco 5400 Series
show interfaces serial interface serial number
Cisco 7200 Series
show interfaces serial [slot/port] [accounting]
Cisco 7000 and Cisco 7500 Series with the RSP7000, RSP7000CI, or Ports on VIPs
show interfaces serial [slot/port-adapter/port]
Cisco 7500 Series
show interfaces serial [slot/port [:channel-group]] [accounting]
Cisco 7500 Series with a CT3IP
show interfaces serial [type slot/port-adapter/port] [:t1-channel] [accounting | crb]
Syntax Description
Command Modes
Privileged EXEC
EXEC when using Frame Relay encapsulation
Command History
Examples
The following example checks HDLC encapsulation on interface serial 0:
Router# show interfaces serial 0Serial0 is up, line protocol is up (looped)Hardware is HD64570Internet address is 10.1.1.1, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation HDLC, loopback set, keepalive set (10 sec)Table 2 describes significant fields shown in the display.
Related Commands
show ss7 mtp1 channel-id
To display information for a given session channel ID, use the show ss7 mtp1 channel-id command in privileged EXEC mode.
show ss7 mtp1 channel-id [channel]
Syntax Description
Defaults
Information for all channels is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no channel ID number is selected, information for all assigned channel IDs is displayed. This command is useful for determining which channel IDs have already been allocated.
Examples
The following sample output displays the name of the serial interface for the link, the assigned media gateway controller (MGC) port, whether the link is serial (12-in-1 port) or digital (E1/T1 trunk DS0), the assigned channel ID, and whether the link is stopped or started:
Router# show ss7 mtp1 channel-idSS7 MTP1 Session-channel [all]:channel assigned interface------- ------------------0 7/0:0 (digital)1 7/0 (serial)3 7/0:1 (digital)Table 3 describes significant fields shown in this output.
The following sample output concerns a specified channel-ID parameter:
Router# show ss7 mtp1 channel-id 1serial interface: 7/0:1 (digital)SCC port: 2link state: STARTEDIDB state: IDBS_UPrcv-pool:pool-name: Rcv07:02congested: FALSEin-use buffers: 16free buffers: 384tx-pool:pool-name: SS7txB01in-use buffers: 64free buffers: 1236Table 4 describes significant fields shown in this output.
Related Commands
show ss7 mtp1 links
To display information for each provisioned Signaling System 7 (SS7) link, use the show ss7 mtp1 links command in privileged EXEC mode.
show ss7 mtp1 links
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display the name of the serial interface for the link, the assigned media gateway controller (MGC) port, whether the link is serial (12-in-1 port) or digital (E1/T1 trunk DS0), the assigned channel ID, and whether the link is stopped or started. This command is useful for quickly letting you know what links have been assigned and what channel IDs are in use.
Examples
The following sample output shows that there are four SS7 links (out of a platform maximum of four).
Note
Router# show ss7 mtp1 linksSS7 MTP1 Links [num = 4, platform max = 4]:sessioninterface type SCC state channel--------- -------- --- ------- -------7/0:0 digital 7/3 STARTED 07/0:1 digital 7/2 STARTED 17/1:0 digital 7/1 STARTED 27/1:1 digital 7/0 STARTED 3
Related Commands
show ss7 mtp2 variant
To display information about the Signaling System 7 (SS7) Message Transfer Part level 2 (MTP2) protocol variant, use the show ss7 mtp2 variant command in privileged EXEC mode.
show ss7 mtp2 variant [channel]
Syntax Description
Defaults
Information for all channels is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command can take an optional channel ID at the end (for example, show ss7 mtp2 variant 0). If the optional channel ID is omitted, the command displays the SS7 variant for all configured SS7 links.
Each country specifies its own variant of SS7, and the Cisco SLT supports several variants of the MTP2 protocol. The selected variant can affect the MTP2 statistics displayed by various commands. The Cisco SLT support the following variants:
•
•
•
•
Each channel can be configured to any one of the protocol variants. When you change from one variant to another, for example from Bellcore to NTT, the MTP2 parameters default to those specified by NTT. You can then change the defaults as required.
Examples
The following is sample output from this command showing protocol-variant information for channel 1:
Router# show ss7 mtp2 variant 1Protocol version for channel 1 is Bellcore GR-246-Core Issue 2, Dec 1997The following is sample output showing the SS7 variant for the SS7 link whose channel ID is 2:
Router# show ss7 mtp2 variant 2Protocol version for channel 2 is Bellcore GR-246-Core Issue 2, Dec 1997The following is sample output showing the SS7 variant for all configured links:
Router# show ss7 mtp2 variantProtocol version for channel 0 is Bellcore GR-246-Core Issue 2, Dec 1997Protocol version for channel 1 is Bellcore GR-246-Core Issue 2, Dec 1997Protocol version for channel 2 is Bellcore GR-246-Core Issue 2, Dec 1997Protocol version for channel 3 is Bellcore GR-246-Core Issue 2, Dec 1997In each case, all SS7 links are clearly provisioned to use the Bellcore variant (refer to the ss7 mtp2 variant bellcore command).
Command output shows that the MTP2 variant is being used for each of the SS7 links and that the Bellcore version is implemented; it also shows where the links are identified by their assigned channel IDs.
Related Commands
Glossary
AERM—SS7 MTP 2 function that provides monitoring of link alignment errors.
CAS—channel associated signaling. The transmission of signaling information within the voice channel. CAS signaling often is referred to as robbed-bit signaling because user bandwidth is being robbed by the network for other purposes.
CLI —command-line interface. An interface that allows the user to interact with the operating system by entering commands and optional arguments.
CSU/DSU—channel service unit. Digital interface device that connects end-user equipment to the local digital telephone loop. Often referred to together with DSU, as CSU/DSU. Data service unit (DSU) is a device used in digital transmission that adapts the physical interface on a DTE device to a transmission facility, such as T1 or E1. The DSU also is responsible for such functions as signal timing.
DFC—dial feature card.
DS0—digital service zero (0). Single timeslot on a DS1 (also known as T1) digital interface—that is, a 64-kbps, synchronous, full-duplex data channel, typically used for a single voice connection on a PBX.
DSPWare—Firmware running on the DSP coprocessor.
EIM—Errored Interval Monitor.
HDLC—high-level data link control. Bit-oriented synchronous data link layer protocol developed by ISO. Derived from SDLC, HDLC specifies a data encapsulation method on synchronous serial links using frame characters and checksums.
MGC—Cisco Media Gateway Controller. The emerging industry standard generic term for the VSC.
MSU—message signaling units. SS7 message that carries call control, database traffic, network management, and network maintenance data in the signaling information field (SIF).
MTP—Message Transfer Part. Layers 1 (physical), 2 (data), and 3 (network) of the SS7 signaling protocol.
MTP1—Layer 1 of MTP, corresponding to layer 1 of the OSI model.
MTP2—Layer 2 of MTP, corresponding to layer 2 of the OSI model.
NAS—network access server. Cisco platform (or collection of platforms, such as an AccessPath system) that interfaces between the packet world (for example, the Internet) and the circuit world (for example, the PSTN).
NFAS—Non-Facility Associated Signaling. A classification of signaling protocols that provide the signaling channel in a separate physical line from the bearer channels.
NTT—SS7 protocol.
OAM—Operation, Administration, and Maintenance. ATM Forum specification for cells used to monitor virtual circuits. OAM cells provide a virtual circuit-level loopback in which a router responds to the cells, demonstrating that the circuit is up and the router is operational.
OSI—Open System Interconnection. International standardization program created by ISO and ITU-T to develop standards for data networking that facilitate multivendor equipment interoperability.
PCR—Preventative Cyclic Retransmission.
PDU—protocol data unit. OSI term for packet.
POP—point of presence. In OSS, a physical location where an interexchange carrier installed equipment to interconnect with a local exchange carrier (LEC).
RUDP—Reliable User Data Protocol.
SUERM—Signal Unit Error Rate Monitor.
SLT—Signaling Link Terminal.
SS7—Signaling System 7.
TTC—Japan telecom.
WIC—WAN interface card.
