cc/td/doc/product/access/sc/rel7
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring the Cisco Signaling Link Terminal

Configuring the Cisco Signaling Link Terminal

This chapter describes how to configure the Cisco Signaling Link Terminals (SLTs) in your solution. Cisco SLTs perform SS7 signal preprocessing for the Cisco MGC. Each Cisco SLT consists of a custom Cisco IOS image running on a Cisco 2611 router.

This chapter contains the following sections:

Note   Simplex configurations, PRI signaling configurations, and some high-availability signaling configurations do not use a Cisco SLT.
Note   The Cisco 2611 only has SS7 functionality when used as a Cisco SLT. All standard Cisco 2611 software features are disabled when running the Cisco SLT image.

Cisco SLT Overview

The Cisco SLT enables the reliable transport of Signaling System 7 (SS7) protocols across an IP network. The Cisco SLT uses the Cisco IOS SS7 Cisco SLT feature set, providing reliable interoperability with the Cisco MGCs in your solution.


Figure 4-1: Cisco SLT


The Cisco SLT handles incoming and outgoing SS7 messages from the Signal Transfer Points (STPs). In a continous-service system, both Cisco SLTs are active and carry traffic. Each supports as many as two SS7 links, and the links can sustain an aggregate of 0.8 erlangs of traffic.

The linksets are distributed across the Cisco SLTs to ensure availability and dependability. Each Cisco SLT in a pair can handle the entire signaling load in case of failure, with no impact on call processing.

The Session Manager software manages the communication sessions with multiple Cisco MGCs. When the Cisco SLT is used with a redundant pair of controllers, the Session Manager maintains separate communication sessions with each controller in the pair. The session between the Cisco SLT and the active controller transports the SS7 traffic, while the session between the Cisco SLT and the standby controller provides backup.

Note   For more information about the Cisco SLT, see the publication Cisco Signaling Link Terminal.

Generic Solution Components

Figure 4-2 illustrates the components used in a generic solution with a Cisco MGC and Cisco SLTs.


Figure 4-2: System Components


Features Supported

The Cisco SLT uses Cisco's Reliable User Datagram Protocol (RUDP) to backhaul, or transport, upper-layer SS7 protocols across an IP network, including:

The Cisco SLT supports the following Message Transfer Part level 1 (MTP 1) functions:

The Cisco SLT supports the following Message Transfer Part level 2 (MTP 2) functions:

The Cisco SLT supports the following Interface Cards:

Cisco SLT Configuration Examples

Interconnection with SS7 network elements is supported through use of the following SS7 physical interface standards: T1, E1, V.35, RS-449, and RS-530. Following are examples of possible continuous-service solution configurations that include the Cisco SLT.

A-Link Cisco SLT Configuration

Access links (A-links) connect Service Switching Points (SSPs) or Service Control Points (SCPs), and pass through a Signal Transfer Point (STP) (see Figure 4-3).


Figure 4-3: Sample A-Link Cisco SLT Configuration


F-Link Cisco SLT Configuration

Fully associated links (F-links) connect SCPs and SSPs directly, and do not pass through as STP (see Figure 4-4).


Figure 4-4: Sample F-Link Cisco SLT Configuration


F-Link Cisco SLT Configuration with Drop and Insert

T1/E1 interface cards support Drop and Insert (also called TDM Cross-Connect), which allows individual T1/E1 channels to pass transparently, and uncompressed, between T1/E1 ports. This feature enables direct termination of SS7 A-links or F-links in T1 or E1 carriers, while the remaining bearer channels are passed on to a gateway device for processing (see Figure 4-5).


Figure 4-5: Sample F-Link Cisco SLT Configuration with Drop and Insert


Related Documentation

For additional information on how to install and configure a Cisco SLT, see the documentation that ships with the product.

Note   When used as a Cisco Signal Link Terminal device integrated into Cisco Media Gateway Controller, the Cisco 2611 has SS7 functionality only, because all standard Cisco 2611 software features are disabled when running the Cisco SLT image. In that case, only the featurette and Cisco VSC3000 documentation is relevant. Most of the Cisco 2600 user documentation no longer applies.

Before Configuration

Before you can configure the Cisco SLTs in your solution, confirm that you have the necessary hardware and software.

Prerequisites

The Cisco SLT consists of a custom Cisco IOS release running on a Cisco 2611 router. Each standard Cisco SLT ships with the following items:

Optional items include:

Note   If you want to use an existing Cisco 2611, you can increase DRAM by ordering MEM2600-32D= in either a quantity of 1 or 2 to replace one or both existing DRAM DIMMs. You can increase Flash in an existing Cisco 2611 equipped with 4 or 8 MB of Flash by ordering Cisco part number MEM2600-16FS= as a replacement for the existing Flash SIMM.

In addition, the router must be equipped with at least one of the following interface cards:

Two Message Transfer Part Level 2 (MTP 2) links can be terminated using the Cisco SLT. The MTP 2 links can be terminated by using both ports of a 2-port wide-area network (WAN) interface card (WIC) or voice WAN interface card (VWIC), or two links can be terminated across two WIC or VWICs, with one port on each.

In addition to the WAN or dual-mode interface cards, the following minimum hardware is required:

Installing the Hardware

Install each Cisco SLT based on the instructions that accompany the product and configure it to support the physical connections illustrated in Figure 4-2. When you attach the cable to the device, note whether you are using data communications equipment (DCE) or data terminal equipment (DTE) cables. This information is useful when you configure the device. Figure 4-6 shows the WIC-2T card.


Figure 4-6: WIC-2T Dual-Port Serial WAN Interface Card


Installing the Software

The Cisco 2611 router must be running a special version of the Cisco IOS software to function as a Cisco SLT and terminate SS7 signaling links. The Cisco SLT is shipped with this Cisco IOS software, but if you have an existing Cisco 2611, you must install the correct version. For more information, see Release Notes for the Cisco Media Gateway Controller Software Release 7.

Configuring the Cisco SLT

This section contains the following procedures:

Configuring the Basic Parameters

Perform the following steps on each Cisco SLT in your solution.

Step 1   Power on the Cisco SLT.

Note   Do not press any keys until the system messages stop. Any keys pressed during this timeare interpreted as the first command, which might cause the Cisco SLT to power off and start over. It takes a few minutes for these messages to stop.

Step 2   When the following message appears, type y (yes) and press Enter to begin the initial configuration dialog:

Would you like to enter the initial configuration dialog? [yes/no]: y
Tips At any point you can type a question mark (?) for help. Use Ctrl-C to abort configuration dialog at any prompt. Default settings are in square brackets.

Step 3   At the following prompt, type y (yes) and press Enter to start basic management setup:

Would you like to enter basic management setup? [yes/no]: y
Configuring global parameters:
Note   Basic management setup provides only enough connectivity for management of the system. Extended setup asks you to configure each interface on the system.

Step 4   Type the host name for the Cisco SLT and press Enter:

Enter host name [Router]: router_name

Step 5   Type an enable_secret password. This password is encrypted for security and cannot be seen in the configuration. The enable_secret password is used to protect access to privileged EXEC and configuration modes. After you enter it, enable_secret is encrypted in the configuration.

Enter enable secret: enable_secret

Step 6   Type an enable_password that is different from the enable_secret password. This password is not encrypted and therefore less secure than the enable_secret password, and can be seen in the configuration. The enable_ password is used when you do not specify an enable_secret password, with some older software versions, and with some boot images.

Enter enable password: enable_password

Step 7   Type a virtual terminal password (vt_password) to prevent unauthenticated access to the Cisco SLT through ports other than the console port. The vt_password is used to protect access to the router over a network interface. 

Enter virtual terminal password: vt_password

Step 8   Type yes and press Enter to begin configuring SNMP parameters:

Configure SNMP Network Management? [yes]: yes
            Community string [public]:

Step 9   Type the interface name used to connect to the management network and press Enter:

Current interface summary
 
Controller Timeslots D-Channel Configurable modes Status
T1 0/2     24        23        pri/channelized    Administratively up
T1 0/3     24        23        pri/channelized    Administratively up
 
Any interface listed with OK? value "NO" does not have a valid configuration
 
Interface                  IP-Address      OK? Method Status Protocol
Ethernet0/0                unassigned      NO  unset  up up      
Serial0/0                  unassigned      NO  unset  down                  down    
Ethernet0/1                unassigned      NO  unset  up                    down    
Serial0/1                  unassigned      NO  unset  down                  down    
 
Enter interface name used to connect to the management network from the above interface summary: Ethernet0/0

Step 10   Type y and press Enter to begin configuring Ethernet interface parameters for the IP address and subnet mask:

Configuring interface Ethernet0/0:
Configure IP on this interface? [yes]: y

Step 11   Type the IP address and the subnet mask for the Ethernet interface:

IP address for this interface: 10.1.1.5     
Subnet mask for this interface [255.0.0.0]: 255.255.0.0
Class A network is 10.0.0.0, 16 subnet bits; mask is /16

Step 12   Save your configuration to NVRAM and exit the initial configuration mode. The following message text and prompt appears:

The following configuration command script was created:
 
hostname aladdin
enable secret 5 $1$0gLU$vLK1YHrMcianH5oVWFJNP/
enable password lablab
line vty 0 4
password lab
no snmp-server
!
no ip routing
!
interface Ethernet0/0
no shutdown
ip address 10.1.1.5 255.255.0.0
!
interface Serial0/0
shutdown
no ip address
!
interface Ethernet0/1
shutdown
no ip address
!
interface Serial0/1
shutdown
no ip address
!
end
 
[0] Go to the IOS command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration to nvram and exit.
Enter your selection [2]: 2
Building configuration...
Use the enabled mode 'configure' command to modify this configuration.
 
Press RETURN to get started!

Step 13   If you do not see a # prompt at the end of the text, press Enter.

Step 14   At the command prompt, type each of the following commands and press Enter to access global configuration mode:

enable password
config t

This completes the configuration of the basic parameters. Continue to the next section ("Configuring the Physical Interfaces") to configure the physical interfaces. If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.

Configuring the Physical Interfaces

This section contains the following procedures:

Configuring the T1/E1 Multiflex Trunk Interfaces

The T1/E1 multiflex trunk interface cards are dual-mode T1 or E1 interfaces in a VWIC (Voice/WAN Interface Card) form for voice, data, and integrated voice/data applications. They support the SS7
Cisco SLT function, as do serial WICs.

The T1/E1 VWIC supports the following T1/E1 functionality:

For additional information about the T1/E1 multiflex trunk interface cards and configuring other types of WICs, see Cisco WAN Interface Cards Hardware Installation Guide.

Note   For serial WICs, no particular configuration is required, except to ensure that the interfaces are not shut down.

To configure the T1/E1 multiflex trunk interfaces of the Cisco SLT, complete the following steps:

Step 1   To start global configuration mode, type the following command and press Enter:

Router# configure terminal

Step 2   To start controller configuration mode for the T1 controller at the specified slot/port location, type the following command and press Enter: 

Router(config)# controller {T1 | E1} 0/port

Where:

Note   For information about WAN interface slot and port numbering, see Cisco WAN Interface Cards Hardware Installation Guide.

Step 3   To set framing, type one of the following commands (for either T1 or E1) and press Enter:

T1 Interface

E1 Interface

Router(config-controller)# framing esf

Router(config-controller)# framing crc4

Step 4   To set line coding, type one of the following commands (for either T1 or E1) and press Enter:

T1 Interface

E1 Interface

Router(config-controller)# linecode b8zs

Router(config-controller)# linecode hdb3

Note   The settings above are the most common settings. Consult your service provider and Wide-Area Networking Configuration Guide for more information.

Step 5   The following command specifies the impedance (amount of wire resistance and reactivity to current) for the E1 termination. Impedance levels are maintained to avoid data corruption over long-distance links. To enter a line-termination value for an E1 link, type the following command and press Enter:

T1 Interface

E1 Interface

 This parameter is for E1 interfaces, only.


 Router(config-controller)# line-termination {75-ohm | 120-ohm}


  • Specify 120-ohm to match the balanced 120-ohm interface. This is the default.
    

  • Specify 75-ohm for an unbalanced BNC 75-ohm interface.

Step 6   To set the cable length, type one of the following commands and press Enter:

T1 Interface

E1 Interface

  • To set a cable length longer than 655 feet, type the following command and press Enter, using the appropriate parameters as shown below:
    



    Router(config-controller)# cablelength long {gain26 | gain36} {-15db | -22.5db | -7.5db | 0db}
 

      

    • gain26—Specifies the decibel pulse gain at 26. This is the default pulse gain.
      

      

    • gain36—Specifies the decibel pulse gain at 36.
      

      

    • -15db—Specifies the decibel pulse rate at
      -15 decibels.
      

      

    • -22.5db—Specifies the decibel pulse rate at
      -22.5 decibels.
      

      

    • -7.5db—Specifies the decibel pulse rate at
      -7.5 decibels.
      

      

    • 0db—Specifies the decibel pulse rate at 0 decibels. This is the default pulse rate.
      

  • To set a cable length 655 feet or shorter, type the following command and press Enter, using the appropriate parameters as shown below:
    



    Router(config-controller)# cablelength short 
    {133 | 266 | 399 | 533 | 655}    
 

      

    • 133—Specifies a cable length from 0 to 133 feet
      

      

    • 266—Specifies a cable length from 134 to 266 feet
      

      

    • 399—Specifies a cable length from 267 to 399 feet
      

      

    • 533—Specifies a cable length from 400 to 533 feet
      

      

    • 655—Specifies a cable length from 534 to 655 feet
      






NoteIf you do not set the cable length, the system defaults to a setting of cablelength long gain26 0db.




 


 This parameter is for T1 interfaces, only.

Step 7   Specify the channel group and time slots to be mapped. Channel group 0 or 1 can be configured. Generally, only one time slot is configured when you are using the Cisco SLT feature, as is shown in this example, where time slot 24 is used for a T1 interface and time slot 16 is used for an E1 interface. A channel group creates a virtual serial interface. It is designated slot/port:subinterface:

To specify the channel group and time slots to be mapped, type one of the following commands and press Enter:

T1 Interface

E1 Interface

Router(config-controller)# channel-group 0 timeslots 24

Router(config-controller)# channel-group 0 timeslots 16

Step 8   If necessary, repeat Step 2 through Step 7 to configure the remaining Cisco SLT interfaces.

Step 9   To exit controller configuration mode, type the following command and press Enter:

Router(config-controller)# exit

Configuring Drop and Insert

To configure Drop and Insert (the TDM cross-connect function), complete the following steps:

Step 1   To enter global configuration mode, type the following command and press Enter:

Router# configure terminal

Step 2   To enter controller configuration mode for the T1 controller at the specified slot/port location, type the following command and press Enter: 

Router(config)# controller {T1 | E1} 0/port

Where:

Note   For information about WAN interface slot and port numbering, see Cisco WAN Interface Cards Hardware Installation Guide.

Step 3   Enter the following command to create TDM channel groups for the Drop-and-Insert function with a two-port T1 or E1 multiflex trunk interface card. You must set up a TDM group for each interface that you wish to cross-connect. To create TDM channel groups, type the following command and press Enter:

Router(config-controller)# tdm-group tdm-group-no timeslots timeslot-list

Where:

Note   You must set up a TDM group for each interface that you wish to cross-connect.

Step 4   To activate the controller, type the following command and press Enter:

Router(config-controller)# no shutdown

Step 5   Repeat Step 3 and Step 4 for the second interface.

Step 6   To exit controller configuration mode, type the following command and press Enter:

Router(config-controller)# exit

Step 7   To establish the connection between two T1 or E1 TDM groups of time slots on the trunk interface, type the following command and press Enter:

Router(config)# connect id T1 slot/port tdm-group-no-1 T1 slot/port tdm-group-no-2

Where:

Step 8   To exit global configuration mode, type the following command and press Enter:

Router(config)# exit

Verifying T1/E1 Multiflex Trunk Interface Configuration

To verify the initial T1/E1 trunk interface configuration, complete the following steps:

Step 1   Enter the privileged EXEC show controllers t1 or show controllers e1 command; for example, show controllers e1 or show controllers t1.

Following is sample output from both commands. Important information appears in bold:









Router# show controllers e1
E1 0/2 is up.
  Applique type is Channelized E1 - balanced
  Cablelength is Unknown
  No alarms detected.
  Version info Firmware: 19990702, FPGA: 6
  Framing is CRC4, Line Code is HDB3, Clock Source is Line.
  Data in current interval (599 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Total 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 Secs
E1 0/3 is down.
  Applique type is Channelized E1 - balanced
  Cablelength is Unknown
  Far End Block Errors Detected
  Receiver has loss of signal.
  Version info Firmware: 19990702, FPGA: 6
  Framing is CRC4, Line Code is HDB3, Clock Source is Line.
  Data in current interval (602 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 602 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 603 Unavail Secs
  Total 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 Secs
 









Router# show controllers t1
T1 0/0 is up.
  Applique type is Channelized T1
  Cablelength is short 133
  No alarms detected.
  Version info Firmware: 19990702, FPGA: 6
  Framing is ESF, Line Code is B8ZS, Clock Source is Line.
  Data in current interval (608 seconds elapsed):
     136066 Line Code Violations, 778727 Path Code Violations
     567 Slip Secs, 0 Fr Loss Secs, 608 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 608 Unavail Secs
  Total Data (last 10 15 minute intervals):
     4286812 Line Code Violations, 11478885 Path Code Violations,
     7734 Slip Secs, 69 Fr Loss Secs, 8996 Line Err Secs, 0 Degraded Mins,
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 9000 Unavail Secs
 










Step 2	  To view channel groups configured as virtual serial interfaces, type the show interface serial slot/port:subinterface command and press Enter:


Router# show interface serial 0/0:0
 

 The following text appears:


Serial0/0:0 is reset, line protocol is down
  Hardware is PowerQUICC Serial
  MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec,
     reliability 253/255, txload 1/255, rxload 1/255
  Encapsulation SS7 MTP2, loopback not set
  Keepalive set (10 sec)
  Last input never, output 00:12:22, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0 (size/max/drops); Total output drops: 0
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/0/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     1437 input errors, 2 CRC, 31 frame, 0 overrun, 0 ignored, 1404 abort
     128055 packets output, 512220 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
  Timeslot(s) Used:1, Transmitter delay is 0 flags
 


Step 3	  To view information about the virtual serial interface, type the show controllers serial slot/port:subinterface command and press Enter:


Router# show controllers serial 0/2:0
 

 The following text appears:


Interface Serial0/2:0
Hardware is PowerQUICC MPC860idb at 0x81143590, driver data structure at 0x81145
474
SCC Registers:
General [GSMR]=0x2:0x00000033, Protocol-specific [PSMR]=0x8
Events [SCCE]=0x0200, Mask [SCCM]=0x001F, Status [SCCS]=0x02
Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E
Interrupt Registers:
Config [CICR]=0x00367F80, Pending [CIPR]=0x04000246
Mask   [CIMR]=0x60240000, In-srv  [CISR]=0x00000000
Command register [CR]=0xD40
Port A [PADIR]=0x00F0, [PAPAR]=0x25F0
       [PAODR]=0x0000, [PADAT]=0x5A4F
Port B [PBDIR]=0x0000F, [PBPAR]=0x0000E
       [PBODR]=0x00000, [PBDAT]=0x37FFD
Port C [PCDIR]=0x00C, [PCPAR]=0xA00
       [PCSO]=0x000,  [PCDAT]=0x5F2, [PCINT]=0xFFF
Receive Ring
        rmd(68012930): status 9000 length 6 address 2DA22E4
        rmd(68012938): status 9000 length 6 address 2DA3AA4
        rmd(68012940): status 9000 length 6 address 2DA1E24
        rmd(68012948): status 9000 length 6 address 2DA27A4
        rmd(68012950): status 9000 length 6 address 2DA5724
        rmd(68012958): status 9000 length 6 address 2DA14A4
        rmd(68012960): status 9000 length 6 address 2DA5264
        rmd(68012968): status 9000 length 6 address 2DA4684
        rmd(68012970): status 9000 length 6 address 2DA4424
        rmd(68012978): status 9000 length 6 address 2DA1964
        rmd(68012980): status 9000 length 6 address 2DA4B44
        rmd(68012988): status 9000 length 6 address 2DA60A4
        rmd(68012990): status 9000 length 6 address 2DA2544
        rmd(68012998): status 9000 length 6 address 2DA3124
        rmd(680129A0): status 9000 length 6 address 2DA0FE4
        rmd(680129A8): status B000 length 6 address 2DA3844
Transmit Ring
        tmd(680129B0): status DC00 length 4 address 2AD9EA8
        tmd(680129B8): status DC00 length 4 address 2AD7568
        tmd(680129C0): status DC00 length 4 address 2ADA428
        tmd(680129C8): status DC00 length 4 address 2ADA6E8
        tmd(680129D0): status DC00 length 4 address 2AD7DA8
        tmd(680129D8): status DC00 length 4 address 2AD5468
        tmd(680129E0): status DC00 length 4 address 2AD8328
        tmd(680129E8): status DC00 length 4 address 2AD85E8
        tmd(680129F0): status DC00 length 4 address 2AD5CA8
        tmd(680129F8): status CE00 length 4 address 2AD8B68
        tmd(68012A00): status DC00 length 4 address 2AD8E28
        tmd(68012A08): status DC00 length 4 address 2AD64E8
        tmd(68012A10): status DC00 length 4 address 2AD67A8
        tmd(68012A18): status DC00 length 4 address 2AD9668
        tmd(68012A20): status DC00 length 4 address 2AD9928
        tmd(68012A28): status FC00 length 4 address 2AD6FE8
SPI Mode [SPMODE]=0xF70, Events [SPIE]=0x0
    Mask [SPIM]=0x0, Command [SPCOM]=0x0
SI Mode [SIMODE]=0x80408040, Global [SIGMR]=0xE
   Cmnd [SICMR]=0x0, Stat [SISTR]=0x0
SI Clock Route [SICR]=0x00004040
 
SCC GENERAL PARAMETER RAM (at 0x68013D00)
Rx BD Base [RBASE]=0x2930, Fn Code [RFCR]=0x18
Tx BD Base [TBASE]=0x29B0, Fn Code [TFCR]=0x18
Max Rx Buff Len [MRBLR]=1548
Rx State [RSTATE]=0x0, BD Ptr [RBPTR]=0x2970
Tx State [TSTATE]=0x188920A3, BD Ptr [TBPTR]=0x2A08
 
SCC SS7 PARAMETER RAM (at 0x68013D38)
CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8
Error-free SUs [EFSUC] = 22927
Max frm len [MFLR] = 278
Erm [ERM] = 0x0,N [NOCTETS] = 16, N_cnt [NOCTETS_CNT] = 12, T [ERM_THRESH] = 64,
 D [ERM_EFSUS] = 256, D_cnt [ERM_EFSUS_CNT] = 97
SS7 options [SS7_OPT] = 0x10F
Filter masks [MASK1] = 0xFFFFFFFF, [MASK2] = 0xFF
 
buffer size 1524
PQUICC SCC specific errors:
0 input aborts on receiving flag sequence
0 throttles, 0 enables
0 overruns
0 transmitter underruns
0 transmitter CTS losts
 




 



 Configuring the Serial Interfaces


 To configure the 1T and 2T serial interfaces, complete the following steps:



Step 1	  To enter global configuration mode, type the following command and press Enter:


Router# configure terminal
 


Step 2	  To enter interface configuration mode for the serial interface, type the following command and press Enter:


Router(config)# interface serial 0/2
 


Step 3	  To activate the interface, type the following command and press Enter:


Router(config-if)# no shutdown
 


Step 4	  To exit serial interface configuration mode, type the following command and press Enter:


Router(config-if)# exit
 




 



 Configuring the Ethernet Interface


 The Cisco SLT uses the built-in Ethernet interface for connection to the IP network that backhauls SS7 signaling between the Cisco SLT and the Cisco MGC.


 To configure the Ethernet interface, complete the following steps:



Step 1	  To enter global configuration mode, type the following command and press Enter:


Router# configure terminal
 


Step 2	  To enter interface configuration mode for the built-in Ethernet interface, type the following command and press Enter: 


Router(config)# interface Ethernet 0/0
 


Step 3	  To assign an IP address and subnet mask to the interface, type the following command and press Enter:


Router(config-if)# ip address 10.10.11.1 255.255.255.0
 


Step 4	  To activate the interface, type the following command and press Enter:


Router(config-if)# no shutdown
 


Step 5	  To exit interface configuration mode, type the following command and press Enter:


Router(config-if)# exit
 




 



 Verifying the Ethernet Interface Configuration


 To verify the Ethernet interface configuration, type the show interface ethernet 0/0 privileged EXEC command at the Router # prompt and press Enter:


Router# show interface ethernet 0/0
 

 The following verification text appears:


Ethernet0/0 is up, line protocol is up
  Hardware is AmdP2, address is 0050.7337.5100 (bia 0050.7337.5100)
  Internet address is 255.251.111.6/24
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters 10:00:36
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue -196/75, 0 drops
  5 minute input rate 3000 bits/sec, 5 packets/sec
  5 minute output rate 2000 bits/sec, 4 packets/sec
     45891 packets input, 3234949 bytes, 0 no buffer
     Received 1593 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     61546 packets output, 3728838 bytes, 0 underruns(518/2091/0)
     0 output errors, 2609 collisions, 3 interface resets
     0 babbles, 0 late collision, 875 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
 

 This completes the physical interface configuration. Continue to the next section ("Configuring the Session Manager and Reliable User Datagram Protocol") to configure the Session Manager, RUDP, and the variant. If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.


 Configuring the Session Manager and Reliable User Datagram Protocol


 The Session Manager and the Reliable User Datagram Protocol (RUDP) are responsible for managing the communication sessions with the Cisco MGCs. Regardless of the number of SS7 links that the Cisco MGC activates on the Cisco SLT, the router maintains only one Session Manager session with each Cisco MGC.







Note   You must reboot the Cisco SLT after setting a new session configuration or after changing an existing session configuration. Do not change session timers unless instructed to do so by Cisco technical support. Changing timers might result in service interruption or outage.




 To configure the session for establishing communications with the Cisco MGC, complete the following steps:







Note   You can define either one or two sessions.




 



Step 1	  To enter global configuration mode, type the following command and press Enter:


Router# configure terminal
 


Step 2	  To set the switchover (failover) timer, type the following command and press Enter:


Router(config)# ss7 set failover-timer 5
 






Note   When an active session fails, the failover-timer value 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 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. The default setting is 
3 seconds, and values from 1 through 10 are valid.





Step 3	  To configure the address pairs and ports for the first Session Manager session, type the following command and press Enter:


Router(config)# ss7 session-0 address 10.0.0.1 7000 10.0.0.2 7000
 


Step 4	  Specify the remote four-part IP address and the remote port first, then the local IP address and UDP port, by typing in the following command and pressing Enter:


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

 where session number is either 1 or 0.







Note   There are two sessions: one for the active Cisco MGC and one for the standby Cisco MGC. The port numbers for the remote Cisco MGC must be different for the active and standby machines and must match the settings for *.stPort in the XECdfParm.dat file.





Step 5	  To configure the address pairs and ports for the second Session Manager session, type the following command and press Enter:


Router(config)# ss7 session-0 address 10.0.0.1 7000 10.0.0.2 7001
 


Step 6	  Specify the remote four-part IP address and the remote port first, then the local IP address and UDP port, by typing the following command and pressing Enter:


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

 


 where session number is either 1 or 0.







Note   You can specify any UDP port not used by another protocol defined in RFC 1700 or otherwise used within your network.





Step 7	  To exit interface configuration mode, type the following command and press Enter:


Router(config-if)# exit
 


Step 8	  To save the new configuration as the startup configuration, type the following command and press Enter:


Router# copy system:running-config nvram:startup-config
 


Step 9	  To reload the Cisco SLT, type the following command and press Enter:


Router# reload
 






Note   You must reload the Cisco SLT if you delete a session or modify any of the parameters of a session. For a complete list of SS7 parameters and Cisco SLT commands, see "Cisco Signaling Link Terminal Command Reference."







 



 Verifying the Session Manager and RUDP Configuration


 To verify the Session Manager and RUDP configuration, complete the following steps:



Step 1	  To view a session configuration, type the privileged EXEC show ss7 sm session command, with or without a session number of 0 or 1, and press Enter:


Router# show ss7 sm session
Session[0]: Remote Host 255.251.250.252:8060, Local Host 255.251.251.252: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.251.250.253:8060, Local Host 255.251.251.252:8061
      retrans_t = 600
      cumack_t  = 300
      kp_t      = 2000
      m_retrans = 2
      m_cumack  = 3
      m_outseq  = 3
      m_rcvnum  = 32
 


Step 2	  To verify the switchover (failover) timer setting, type the privileged EXEC show ss7 sm set command and press Enter:


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


Step 3	  To view Session Manager statistics, type the privileged EXEC show ss7 sm stats command and press Enter: 


Router# show ss7 sm stats






Note   You can specify a session number of 1 or 2.




 The following text appears:


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
 




 



 Configuring the MTP2 Variant


 SS7 MTP2 supports the following four variants: 



 Parameters in one variant have different meanings, purposes, and ranges in another variant. See "Cisco Signaling Link Terminal Command Reference," for more on MTP 2 variant commands and their parameters.


 Note the following:



 To configure the MTP2 variant, complete the following steps:



Step 1	  To enter global configuration mode, type the following command and press Enter:


Router# configure terminal
 


Step 2	  To set the amount of DRAM to be used for I/O memory to 40 percent, type the following command and press Enter:


Router(config)# mem iomem 40
 






Note   You must set the I/O memory to at least 40 percent in order to have enough memory for the SS7 MTP2 signaling.





Step 3	  To configure the MTP2 variant Telcordia (formerly Bellcore) for channel 2, type the following command and press Enter:


Router(config)# ss7 mtp2-variant Bellcore 2
 


Step 4	  To set the aligned timer to 30,000 milliseconds, type the following command and press Enter:


Router(config-Bellcore)# T3 30000
 


Step 5	  To set the maximum number of message signal units (MSUs) waiting for acknowledgment to 16, type the following command and press Enter:


Router(config-Bellcore)# unacked-MSUs 16
 


Step 6	  To set the excessive delay timer to 50,000 milliseconds, type the following command and press Enter:


Router(config-Bellcore)# T7 50000
 


Step 7	  To exit Bellcore variant configuration mode, type the following command and press Enter:


Router(config-Bellcore)# exit
 


Step 8	  To exit configuration mode, type the following command and press Enter:


Router(config-if)# end
 


Step 9	  To save the running configuration to startup configuration, type the following command and press Enter:


Router# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
 




 



 This completes the Session Manager and RUDP configuration. Continue to the next section ("Configuring the Cisco Media Gateway Controller") to configure the Cisco MGC. If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.


 Configuring the Cisco Media Gateway Controller

 
 After you configure the Cisco SLT, you must configure the point codes, linksets, SS7 signaling links, and associated MTP 2 parameters on the Cisco MGC. 


 The Cisco MGC provides call control. Each SS7 link defined on the Cisco MGC is considered a logical channel, and each logical channel corresponds to a physical interface on the Cisco SLT. You can define two SS7 links (logical channels) from the Cisco MGC to each Cisco SLT in your solution. The logical channels defined on the TCS correspond to the physical serial interfaces on the Cisco SLT, proceeding from right to left, as follows:








Note   See the following documents for detailed provisioning information:
Cisco Media Gateway Controller Software Release 7 Provisioning Guide




 Table 4-1 lists examples of different signal termination channels mapping to interface positions.


  

Table 4-1: Examples of Logical Channels and Physical Interfaces




Logical Channel
Cisco SLT Physical Interface




Two 2-Port WICs
1-Port WIC on Right, 2-Port WIC on Left
Two 2-Port WICs
2-Port WIC on Right, 1-Port WIC on Left



 0


 Not used: Serial 0/0


 Assigned to port in first (right) slot: Serial 0/0


 Not used: Serial 0/0


 Not used: Serial 0/0




 1


 Assigned to second port in first (right) slot: Serial 0/1


 


 Not used: Serial 0/1


 Assigned to second port in first (right) slot: Serial 0/1




 2


 Not used: Serial 0/2


 Assigned to first port in second (left) slot: Serial 0/1


 Assigned to first port in second (left) slot: 
Serial 0/2


 Assigned to first port in second (left) slot:
Serial 0/2




 3


 Assigned to second port in second (left) slot:
Serial 0/3


 Not used: Serial 0/2


 Assigned to second port in second (left) slot: 
Serial 0/3


 











 


 This completes the Cisco MGC configuration. Continue to the next section ("Maintaining the Cisco SLT") for a list of commands used to monitor and maintain the Cisco SLT. If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.


 Maintaining the Cisco SLT

 
 Table 4-2 lists the commands used to maintain the Cisco SLT. For more information on these commands, see "Cisco Signaling Link Terminal Command Reference."


  

Table 4-2: Cisco SLT Maintenance Commands




Command
Purpose



Router# clear rudpv0 statistics

 Clears the counters that track RUDP statistics




Router# clear ss7 sm stats

 Clear the counters that track Session Manager statistics




Router# show rudpv0 failures

 Shows RUDP failure statistics




Router# show rudpv0 statistics

 Shows RUDP performance statistics




Router# show ss7 mtp2 ccb

 Shows channel control block information




Router# show ss7 mtp2 state

 Shows MTP 2 state machine information




Router# show ss7 mtp2 stats

 Shows MTP 2 operational statistics




Router# show ss7 mtp2 timer

 Shows MTP 2 timer settings




Router# show ss7 mtp2 variant

 Shows MTP 2 Telcordia (formerly Bellcore) protocol variant information




Router# show ss7 sm session

 Shows session configuration for timers, addresses, and ports




Router# show ss7 sm set

 Shows the setting of the switchover timer




Router# show ss7 sm stats

 Shows Session Manager performance statistics














 Configuration Examples

 
 This section contains the following configuration examples:



 T1 Configuration


 Following is an example of a Cisco SLT configuration with a T1 interface card:


version 12.0
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec localtime
no service password-encryption
!
hostname Router_T1
!
logging buffered 4096 debugging
!
ip subnet-zero
!






Tips Below, Extended SuperFrame (ESF) framing and binary-8 zero substitution (B8ZS) are configured on the T1 0/0 controller. For these settings, the defaults are usually sufficient, and need to be changed only if the service provider requires it. Because this is a short-haul link, the cable length is specified as short.






controller T1 0/0
 framing esf
 linecode b8zs
 cablelength short 133






Tips The channel-group controller configuration command below creates a channel group (0 or 1) that occupies a single time slot.






channel-group 0 timeslots 24
!
controller T1 0/1
 framing esf
 tdm-group 2 timeslots 1-23
!
process-max-time 200
!
 






Tips Ethernet 0/0 provides the IP connection for backhauling SS7 information between the Cisco 2600 series router and the Cisco Media Gateway Controller.






interface Ethernet0/0
 ip address 255.1.1.6
 no ip directed-broadcast
 no ip mroute-cache
 no cdp enable
!






Tips The channel-group command creates a logical serial interface that corresponds to the slot and port location of the T1 interface and to the channel group number of 0 or 1.






interface Serial0/0:0
 no ip address
 no ip directed-broadcast
!
interface Ethernet0/1
 no ip address
 no ip directed-broadcast
 no ip mroute-cache
!
ip classless
no ip http server
!






Tips The SS7 commands below all use the default settings. This is especially important for the session timers, which should not be changed except at the instruction of Cisco technical assistance personnel. Two sessions are configured here.






ss7 set failover-timer 3
ss7 session-0 address 255.1.0.2 8060 255.1.1.6 8060
ss7 session-0 retrans_t 600
ss7 session-0 cumack_t 300
ss7 session-0 kp_t 2000
ss7 session-0 m_retrans 2
ss7 session-0 m_cumack 3
ss7 session-0 m_outseq 3
ss7 session-0 m_rcvnum 32
ss7 session-1 address 255.1.0.1 8061 255.1.1.6 8061
ss7 session-1 retrans_t 600
ss7 session-1 cumack_t 300
ss7 session-1 kp_t 2000
ss7 session-1 m_retrans 2
ss7 session-1 m_cumack 3
ss7 session-1 m_outseq 3
ss7 session-1 m_rcvnum 32
!
line con 0
 exec-timeout 0 0
 transport input none
line aux 0
line vty 0 4
 exec-timeout 0 0
 password lab
 login
!
end






Tips The ss7 mtp2-variant commands below determine the MTP 2 variant on each channel.






ss7 mtp2-variant Bellcore 2 
ss7 mtp2-variant Bellcore 3

 E1 Configuration with Drop and Insert


 Following is an example of a Cisco SLT configuration with an E1 voice/WAN interface card that has Drop-and-Insert capabilities:


version 12.0
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec localtime
no service password-encryption
!
hostname Router_E1
!
logging buffered 4096 debugging
!
ip subnet-zero
!
!






Tips The channel-group controller configuration commands below create channel group 0. Each command occupies a single time slot. The TDM groups use the rest of the slots.






controller E1 0/0
 channel-group 0 timeslots 16
 tdm-group 1 timeslots 1-15,17-31
!
controller E1 0/1
 clock source internal
 tdm-group 1 timeslots 1-15,17-31
!
controller E1 0/2
 channel-group 0 timeslots 16
!
controller E1 0/3
!
process-max-time 200
!






Tips Ethernet 0/0 provides the IP connection for backhauling SS7 information between the Cisco 2600 series router and the Cisco Media Gateway Controller.






interface Ethernet0/0
 ip address 10.1.1.6
 no ip directed-broadcast
 no ip mroute-cache
 no cdp enable
!






Tips The channel-group command creates a logical serial interface that corresponds to the slot and port location of the T1 interface and to the channel group number of 0 or 1.






interface Serial0/0:0
 no ip address
 no ip directed-broadcast
 no keepalive
!
interface Ethernet0/1
 no ip address
 no ip directed-broadcast
 no ip mroute-cache
!
interface Serial0/2:0
 no ip address
 no ip directed-broadcast
 no keepalive
!
ip classless
no ip http server
!






Tips The connect command below links the two VXIC ports for Drop and Insert.






connect my_connection E1 0/0 1 E1 0/1 1
 !






Tips The SS7 commands below all use the default settings. This is especially important for the session timers, which should not be changed except at the instruction of Cisco technical assistance personnel. Two sessions are configured here.






ss7 set failover-timer 3
ss7 session-0 address 10.1.0.2 8060 10.1.1.6 8060
ss7 session-0 retrans_t 600
ss7 session-0 cumack_t 300
ss7 session-0 kp_t 2000
ss7 session-0 m_retrans 2
ss7 session-0 m_cumack 3
ss7 session-0 m_outseq 3
ss7 session-0 m_rcvnum 32
ss7 session-1 address 10.1.0.1 8061 10.1.1.6 8061
ss7 session-1 retrans_t 600
ss7 session-1 cumack_t 300
ss7 session-1 kp_t 2000
ss7 session-1 m_retrans 2
ss7 session-1 m_cumack 3
ss7 session-1 m_outseq 3
ss7 session-1 m_rcvnum 32
!
line con 0
 exec-timeout 0 0
 transport input none
line aux 0
line vty 0 4
 exec-timeout 0 0
 password lab
 login
!
end






Tips The ss7 mtp2-variant commands below determine the MTP 2 variant on each channel.






ss7 mtp2-variant Bellcore 2
ss7 mtp2-variant Bellcore 3

 Two 56-Kbps A-Links in a T1


 For a T1 interface, the channel-group controller configuration commands create two channel groups (0 and 1), each of which occupies a single time slot. The TDM groups use the rest of the time slots:


controller t1 0/0
 channel-group 0 timeslots 1
 channel-group 1 timeslots 2
 tdm-group 2 timeslots 3-24
controller t1 0/1
 tdm-group 3 timeslots 3-24
connect cicset1 t1 0/0 2 t1 0/1 3

 Two 64-Kbps F-Links in an E1


 For an E1 interface, the channel-group controller configuration commands create two channel groups (0 and 1), each of which occupies a single time slot. The TDM groups use the rest of the time slots:


controller e1 0/0
 channel-group 0 timeslots 16
 channel-group 1 timeslots 31
 tdm-group 2 timeslots 1-15, 17-30
controller e1 0/1
 tdm-group 3 timeslots 1-15, 17-30
connect cicset1 t1 0/0 2 t1 0/1 3

 





hometocprevnextglossaryfeedbacksearchhelp


Posted: Fri Sep  1 16:39:51 PDT 2000

Copyright 1989-2000©Cisco Systems Inc.