ITP Operations Guide

ITP Operations Manual
May 1, 2002
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Customer Order Number:

Text Part Number:
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public
domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Copyright 2002, Cisco Systems, Inc.
All rights reserved.
C ON T E N T S
Site Survey
1-1
Cisco 7513 Overview 1-1

Cisco 7513 Dual CyBus Backplane
Cisco 7513 System Specifications
1-3
1-4
Physical Hardware Installation & Cabling
2-1
Slot Locations on the Cisco 7507 and Cisco 7513

Cisco 7507 Router Slot Numbering 2-3
Cisco 7513 Router Slot Numbering 2-4
SS7 Port Adapter Overview
2-3
2-5
PA-A3-8E1IMA and PA-A3-8T1IMA Port Adapter Overview

VIP4 Overview
2-7
2-8
FEIP-DSW Overview
2-9
Safety Guidelines 2-11

Safety Warnings 2-11
Electrical Equipment Guidelines 2-12
Telephone Wiring Guidelines 2-13
Preventing Electrostatic Discharge Damage
FCC Class A Compliance
2-13
2-14
Required Tools and Equipment
2-14
Software and Hardware Requirements 2-15

Checking Hardware and Software Compatibility
2-15
Ensuring Network Operation During Removal of VIP and Port Adapters

Understanding Online Insertion and Removal (OIR) 2-16
Taking Active Links Out of Service 2-16
Removing the VIP4
2-16
Removing and Installing Port Adapters from the VIP4 2-18

Safe and Proper Handling of Port Adapters 2-18
Illustrated Procedure for Removing and Installing Port Adapters
Reinstalling the VIP4
2-16
2-20
2-22
Connecting the Port Adapter Cables 2-24

Connecting the SS7 Port Adapter Interface Cables
Connecting PA A3-IMA Cables 2-26
Connecting a 75-120 Ohm Adapter Cable 2-27
2-24
iii
Contents
Connecting the 75120-Ohm Adapter Cable
2-28
Verifying the VIP4 and Port Adapter Installation
2-30
FEIP2-DSW Installation 2-32

IEEE 802.3u 100BASE-T Specifications 2-32
Removing an Interface Processor or Interface Processor Filler
Removing an FEIP2-DSW 2-34
Installing an FEIP2-DSW 2-36
Attaching Cables to FEIP2-DSW 2-37
Using LEDs to Check FEIP2-DSW Status 2-40
FEIP2-DSW LEDs 2-41
FEIP2-DSW Receptacles, Cables, and Pinouts 2-41
System Quick Start
3-1
Install the Hardware 3-3

Packing List 3-4
Prepare to Install the Router 3-4
Install the Router on a Bench or Tabletop 3-5
Rack-Mount the Router (Recommended) 3-7
Mount Brackets to the Rack Posts 3-9
Secure the Spacers 3-11
Attach the Chassis Ears 3-12
Mount the Chassis in the Rack 3-13
lnstall Interface Processors, Fillers, VIPs, or RSPs
Attach the Cable-Management Bracket 3-16
Install Power Supplies in the Router 3-17
Connect AC-Input Power Supply 3-18
Connect DC-Input Power Supply 3-19
Connect the RSP 3-20
Connect the Console Port 3-21
Connect the Auxiliary Port 3-21
Connect the Console and the Auxiliary Y-Cables
Start and Configure the System 3-22
Start a Basic Configuration 3-23
Configure Using AutoInstall 3-24
Perform a Basic Configuration Using Setup
Configure an Ethernet Interface 3-26
Install Field Replaceable Units (FRUs) 3-27
Flash Memory Cards 3-27
Format a Flash Memory Card 3-28
iv
3-24
3-14
3-21
2-34
Contents
Copy Files to Flash Memory 3-29

Make a Flash Memory Card Image Bootable 3-29
Enable Booting from Flash Memory 3-30
Prepare to Remove and Install an RSP 3-30
Remove and Install an Interface Processor, Filler, VIP, or RSP
Check the RSP Installation 3-32
Check the Interface Processor or VIP Installation 3-33
Copy the Configuration File for an RSP 3-34
Retrieve the Configuration File for RSPs 3-36
Remove and Install Port Adapters 3-38
Remove and Replace the Power Supply 3-39
3-31
Installing or Replacing the Power Supply 4-1

Install Power Supplies in the Router 4-1
Connect AC-Input Power Supply 4-2
Connect DC-Input Power Supply 4-3
Remove and Replace the Power Supply 4-4
Software Verification of Hardware
5-1
Verify That the System Has Detected the HSL Hardware

Examine All ATM Port Adapters Installed in Each Slot
5-2
5-3
Verify that the IOS Has Provided the Initial Default Configuration for Each of the ATM Interfaces
Verify the State of Each Interface
5-5
Additional Commands to Obtain Details about the Hardware

Verifying Installation of the SS7 Port Adapter
5-6
5-9
Examine All SS7 Port Adapters Installed in Each Slot
5-10
Verify that the IOS has Provided the Initial Default Configuration for Each of the SS7 Controllers
Additional Commands to Obtain Details of the Hardware
Configure and Maintain RSP Redundancy - RPR+
Restrictions
5-11
5-12
6-1
6-1
Supported Platforms
Prerequisites
5-4
6-2
6-2
Configuration Tasks 6-2

Copying an Image onto an RSP 6-3
Setting the Config-Register Boot Variable
Configuring RPR+ 6-5
Verifying RPR+ 6-7
Troubleshooting Tips 6-7
6-4
Contents
Configuration Examples 6-7

Configuring RPR+ Example
Configure IP Addressing
6-8
7-1
Identifying Interface Numbers and Addresses

Configuring FE Interfaces
7-1
7-2
Checking the Configuration 7-4

Using show Commands to Verify FEIP2-DSW Status 7-4
Using show Commands to Display Interface Information 7-5
Using the ping Command to Verify Network Connectivity 7-7
ITP Global Configuration
8-1
Specifying the SS7 Variant
8-1
Specifying National Options and Network Indicator
8-1
Specifying the Point Code 8-2

Specifying the Point Code Representation 8-2
Specifying the Primary Local Point Code 8-3
Specifying a Secondary Point Code 8-3
Specifying the Capability Point Code 8-3
Putting a Low Speed Link (LSL) in Service
9-1
Creating a Basic Controller Configuration for the SS7 Port Adapter

Performing a Basic Data Interface Configuration
Configuring Cyclic Redundancy Checks
Configuring Linksets
9-1
9-4
9-5
9-5
Assigning Links to Linksets 9-6

Traditional SS7 Links 9-6
Putting a High Speed Link (HSL) in Service
Enabling an ATM Interface
10-1
Configuring a Permanent Virtual Circuit (PVC)

Configuring SSCF
Configuring SSCOP
10-1
10-4
10-4
10-5

Using show Commands to Verify the New Interface Status
Using loopback Commands 10-7
Checking Bit Errors Using a Bit Error Rate Test 10-8
Using the debug ATM Commands 10-8
vi
10-9
10-6
Contents
Assigning Links to Linksets
10-9
Taking an SS7 PA Out of Service
11-1
Identifying Links Associated with an SS7 PA
11-1
Disabling Links Associated with an SS7 PA

Identifying and Disabling the Controller
Taking an HSL PA Out of Service
11-3
11-4
12-1
Identifying Links Associated with an HSL PA
12-1
Disabling Links Associated with an HSL PA

Identifying and Disabling the Interface
Taking an SS7 Link Out of Service
12-2
12-3
13-1
13-1
Disabling a Link Associated with an SS7 PA
13-3
Taking an HSL Out of Service
14-1
14-1
Disabling a Link Associated with an HSL PA
14-2
Taking a Linkset Out of Service
15-1
Identifying and Disabling Linksets
15-1
MTP3 Routes 16-1

Specifying the Cisco ITP Route Table
16-1
Global Title Translation (GTT) 17-1

Overview of GTT 17-1
Storing and Loading GTT Configuration Data
Configuring GTT 17-10
Configuring Global Title Address Conversion
Verifying Global Title Translations 17-26
ITP GTT Configuration Example 17-28
Saving Route and GTT Tables
17-4
17-24
18-1
Saving and Loading a Route Table 18-1

Specifying the Default Route Table 18-1
Loading the Route Table Contents 18-2
Adding Routes to the Route Table 18-2
Saving the Route Table 18-2
Saving and Loading a GTT Table 18-3
Loading a GTT Table from a Remote File Server or Flash (No existing GTT Data)
18-3
vii
Contents
Loading a GTT Table from a Remote File Server or Flash (Existing GTT Data)
Bulk Loading/Replacing Entire GTT Database 18-4
Replacing a Failed SS7 LSL or HSL Port Adapter
Port Adapters on the VIP4 19-1
Online Insertion and Removal (OIR)
19-1
19-2
Taking Port Adapters Out of Service 19-3

Taking an SS7 PA Out of Service 19-3
Taking an HSL PA Out of Service 19-4
Removing the VIP4
19-6
Replacing Port Adapters
19-6
Reinstalling the VIP4 and Connecting the Port Adapter Cables 19-9
Reinstalling the VIP4 19-9
Connecting the SS7 Port Adapter Interface Cables 19-10
Connecting PA A3-IMA Cables 19-11
Verifying the VIP4 and SS7 Port Adapter Installation
19-12
Reactivating the Links Associated with the Port Adapter 19-17

Reactivating Disabled SS7 Low Speed Links 19-17
Reactivating Disabled High Speed Links 19-18
Installing or Replacing a FastEthernet Port Adapter
20-1
Port Adapter Overview 20-1

LEDs 20-2
Receptacles, Cables, and Pinouts 20-2
Identifying Interface Addresses 20-4
Removing the VIP4 20-6
Online Insertion and Removal (OIR) 20-6
Shutting Down an Interface 20-6
Procedure for Removing the VIP4 20-8
20-9
Reinstalling the VIP4 and Connecting the Port Adapter Cables

Reinstalling the VIP4 20-12
Connecting a PA-2FE RJ-45 or SC Cable 20-13
Configuring the PA-2FA 20-15
Using the EXEC Command Interpreter
Configuring the Interfaces 20-15
20-15

Observing the LEDs 20-21
viii
20-12
20-18
18-4
Contents
Replacing a Failed VIP
21-1
VIP4 Overview 21-1

21-2
Taking Port Adapters Out of Service 21-3

Taking an SS7 PA Out of Service 21-3
Taking an HSL PA Out of Service 21-4
Removing the VIP4
21-6
21-7

21-10
21-12
Reactivating the Links Associated with the Port Adapter 21-17

Reactivating Disabled SS7 Low Speed Links 21-18
Reactivating Disabled High Speed Links 21-18
Replacing a Failed RSP
22-1
Replacing a Failed RSP in a Non-Redundant Configuration

Removing the RSP8 22-2
Inserting the RSP8 22-3
Restarting the System 22-6
Troubleshooting the Installation 22-8
Replacing a Failed RSP8 in an RPR+ Configuration
Removing the RSP8 22-13
Inserting the RSP8 22-15
Adding New Port Adapters
Software Upgrade
22-1
22-13
23-1
24-1
Ongoing Monitoring 25-1

Monitoring the Cisco ITP
25-1
ix
Contents
C H A P T E R
Site Survey
Cisco 7513 Overview
The Cisco 7513 router supports multiprotocol, multimedia routing and bridging with a wide
variety of protocols and any combination of available electrical interfaces and media.
Network interfaces reside on interface processors that provide a direct connection between
the two CyBuses in the Cisco 7513 and your external networks. The Cisco 7513 has 13
slots: interface processor slots 0 through 5, Route Switch Processor RSP8 slots 6 and 7, and
interface processor slots 8 through 12.
There are bays for up to two AC-input or DC-input power supplies. The chassis will operate
with one power supply. Although a second power supply is not required, it allows load
sharing and increased system availability. The Cisco 7513 is shown in . The three
front-panel LEDs indicate system and power supply status, and LEDs on the RSP, interface
processors, and power supplies indicate status.
Caution Because of agency compliance and safety issues, mixing AC-input and DC-input
power supplies in the same Cisco 7513 is not a supported configuration and should not be
attempted. Doing so might cause damage.
1-1
Chapter 1
Cisco 7513 Overview
Figure 1-1
POWER
A
POWER
B
NORMAL
H3074
Front-panel
LEDs
Cisco 7513 (Front View)
1-2
Site Survey
Chapter 1
Site Survey
Cisco 7513 Overview
Figure 1-2 shows details on the rear, interface-processor end of the Cisco 7513.
Figure 1-2
Cisco 7513 (Rear View)
Blower module
Cable-management
bracket
NO
RM
AL
EN
EJE
AB
LE
AB
LE
CT
SLO SLO
T0 T1
SLA MA
S
V E TE
R
Card cage and

processor modules
SLA
VE
/M
CP
RE
AU
NS
TE
HA
LT
EN
X.
ROUTE SWITCH PROCESSOR 2
CO
AS
SE
OLE
Air intake vent

AC
OK
FAN
OK
OUTPUT
FAIL
AC
OK
OUTPUT
FAIL
POWER
POWER
Chassis grounding
receptacles
H5268
Power supplies
FAN
OK
I
I
0
0
Cisco 7513 Dual CyBus Backplane

The dual CyBus backplane, located at the rear of the Cisco 7513 removable card cage, provides the
physical connections for the RSPs and interface processors, and transfers information at up to
2.134 Gbps (1.067 Gbps per CyBus).
The dual CyBus has 13 slots: interface processor slots 0 through 5 (CyBus 0); two RSP slots (slots
6 and 7); interface processor slots 8 through 12 (CyBus 1), as shown in Figure 1-3Figure 1-3.
1-3
Chapter 1
Site Survey
Cisco 7513 Overview
Dual CyBus Backplane in the Cisco 7513
H3163
Figure 1-3
CyBus 0 (slots 0 through 5)
RSP RSP
10
11
12
CyBus 1 (slots 8 through 12)
An RSP8 in either slot 6 or slot 7 controls both CyBus 0 and CyBus 1. The dual CyBus backplane in the
Cisco 7513 has an aggregate bandwidth of 2.134 Gbps. Interface processors connected to one CyBus are
unaffected by the traffic generated by the interface processors connected to the other CyBus. The two
CyBuses are independent of one another.
The backplane slots are keyed so that the processor modules can be installed only in the slots designated
for them. Keys on the backplane fit into two key guides on each module. Although the RSP uses unique
keys, all eleven interface processor slots use the same key, so you can install an interface processor in
any interface processor slot, but not in the RSP slot.
Cisco 7513 System Specifications

Table 1-1 lists the specifications for the Cisco 7513 system.
Table 1-1
Description
Backplane
Specification
Two 1.0677-Gbps CyBuses, 11 interface processor slots, 2 RSP slots
Dimensions
(H x W x D)
33.75 x 17.5 x 22 in. (85.73 x 44.45 x 55.88 cm)

Chassis width including rack-mount flanges is 18.93 in. (48.1 cm)
Chassis depth including power cables and cable-management bracket is 24 in. (60.96 cm)
1-4
Specifications for the Cisco 7513
Chapter 1
Site Survey
Cisco 7513 Overview
Description
Weight
Power dissipation
Specification
Chassis with blower module: 75 lb (34.02 kg)
Chassis with blower module and 1 power supply: 100 lb (45.36 kg)
Chassis with blower module and 2 power supplies: 125 lb (56.7 kg)
Chassis with blower module, 2 power supplies, and all slots filled: ~160 lb (72.58 kg),
each processor module weighs ~2.5 lb (1.13 kg)
1600W with a maximum configuration and 1 AC-input power supply
1600W with a maximum configuration and 1 DC-input power supply
1700W nominal with a maximum configuration and either 2 AC-input or 2 DC-input power
supplies
Heat dissipation
AC-input voltage
1600W (5461 Btu/hr)

100 to 240 VAC
Frequency
AC-input cable1
AC-input voltage
and current
50/60 Hz
12 AWG, with 3 leads, an IEC-320 plug on the router end, and a country-dependent plug on
the power source end
100 VAC at 16 amps (A) maximum, wide input with power factor correction (PFC)
240 VAC at 7A maximum
DC-input voltage
and current
48 VDC nominal, at 35A in North America

(60 VDC at 35A in the European Union)
DC-input cable
8 AWG (recommended minimum), with 3 leads and rated for at least 194F (90C) (you
supply the cable)
Power distribution
Airflow/noise level
+5.2 VDC @ 75A, +12 VDC @ 15A, 12 VDC @ 3A, +24 VDC @ 5A
Bottom to top through chassis by variable-speed blower (62 to 70 dBA)
Temperature
Relative humidity
32 to 104F (0 to 40C), operating; 4 to 149F (20 to 65C), nonoperating

10 to 90%, noncondensing
Software requirement
Cisco IOS Release 12.0(7)S or a later release of 12.0 S for the RSP8 in the Cisco 7513
Agency approvals
Safety: UL 1950, CSA 22.2-950, EN60950, EN41003, TS001, AS/NZS 3260

EMI: FCC Class A, EN60555-2, EN55022 Class B, VDE 0878 Part 3, 30 Class B
Immunity: EN55101/2 (ESD), EN55101/3 (RFI), EN55101/4 (Burst), EN55101/5 (Surge),
EN55101/6 (Conducted), IEC77B (AC Disturbance)
1.The Cisco 7513 requires a minimum of 20A service with a 20A receptacle at the power source. The power cable supplied with the
Cisco 7513 uses a 20A male plug.
Terms and Acronyms

Following is a list of acronyms, initializations, and terms that identify the Cisco 7500 series system
components and features:
BackplaneSingle or dual system bus to which Cisco interface processors and system processors
attach within a Cisco 7500 series router.
Card cageAssembly in which the backplane is mounted.
CxBusCisco Extended Bus, the 533-megabit-per-second (Mbps) data bus in the Cisco 7000 series
routers.
CyBusCisco Extended Bus, the 1.067-gigabit-per-second (Gbps) data bus in the Cisco 7500 series
routers; the Cisco 7505 has one CyBus; the Cisco 7507,
Cisco 7507-MX, Cisco 7513, and the Cisco 7513-MX have two CyBuses (called the dual CyBus)
for an aggregate bandwidth of 2.134 Gbps. The Cisco 7576 has two dual CyBuses on a single split
backplane creating two independent routers. Each Cisco 7576 independent router has an aggregate
bandwidth of 2.134 Gbps. (Interface processors designed for the CxBus work with the CyBus.)
dBusDiagnostic bus for Route Switch Processor diagnostic and control access, system discovery
and control, microcode download, and fault diagnosis for all processors connected to the CyBus.
1-5
Chapter 1
Site Survey
Cisco 7513 Overview
DIMMDual in-line memory module.
DRAMdynamic random-access memory.
FEIPFast Ethernet Interface Processor.
FRUField-replaceable unit, defined as any spare part that requires replacement by a

Cisco-certified service provider.
GbpsGigabits per second.
HSAHigh System Availability.
Interface processorPrinted circuit card attached to a metal carrier that provides the electrical
interfaces used by the Cisco 7500 series routers.
MbpsMegabits per second.
NVRAMNonvolatile random-access memory.
Processor modulesAll interface processors and main system processors used in the Cisco 7500
series routers.
RSPRoute Switch Processor; the main system processor. In this publication, the term RSP
includes all RSP models (differences between RSP models are clearly noted).
RSP8Specific main system RSP for the Cisco 7507-MX and Cisco 7513-MX.
SIMMSingle in-line memory module.
SparesSpare parts that do not require replacement by a Cisco-certified service provider.
SRAMStatic random-access memory.
TDM busConnectors on the backplane of the Cisco 7507-MX, Cisco 7513-MX, and Cisco 7576
that are designed for future time-division multiplexing hardware as it becomes available.
1-6
C H A P T E R

This chapter describes how to remove the VIP4-80, how to remove a port adapter from the VIP4-80, and how
to install a new or replacement port adapter. This chapter describes the physical installation, removal, and
cabling of interface processors and port adapters. It does not describe software configuration tasks that
might be associated with installation or removal of hardware. Related software tasks are described in
other chapters of this manual and references to the relevant chapters are provided as appropriate.
VIP AND PORT ADAPTER OVERVIEWS

For information about the platforms, interface processors and port adapters supported on the ITP, refer to the
following INFORMATION sections:
Slot Locations on the Cisco 7507 and Cisco 7513, page 3
SS7 Port Adapter Overview, page 5
PA-A3-8E1IMA and PA-A3-8T1IMA Port Adapter Overview, page 7
VIP4 Overview, page 8
FEIP-DSW Overview, page 9
IMPORTANT PRE-INSTALLATION INFORMATION

For safety guidelines and required tools and equipment, refer to the following PRE-INSTALLATION
sections:
Safety Guidelines, page 11
FCC Class A Compliance, page 14
Required Tools and Equipment, page 14
Software and Hardware Requirements, page 15
TASKS
For instructions on how to remove, install, and verify the interface processors and port adapters supported
on the ITP, refer to the following TASK sections:
VIP, SS7 Port Adapter, ATM Port Adapter Installation and Removal
Ensuring Network Operation During Removal of VIP and Port Adapters, page 16
Removing the VIP4, page 16
Removing and Installing Port Adapters from the VIP4, page 18
2-1
Chapter 2
Reinstalling the VIP4, page 22
Connecting the Port Adapter Cables, page 24
Verifying the VIP4 and Port Adapter Installation, page 30
FEIP-DSW Installation and Removal
FEIP2-DSW Installation, page 32
IEEE 802.3u 100BASE-T Specifications, page 32
Removing an Interface Processor or Interface Processor Filler, page 34
Removing an FEIP2-DSW, page 34
Installing an FEIP2-DSW, page 36
Attaching Cables to FEIP2-DSW, page 37
Using LEDs to Check FEIP2-DSW Status, page 40
FEIP2-DSW LEDs, page 41
FEIP2-DSW Receptacles, Cables, and Pinouts, page 41
2-2
Chapter 2


This section describes slot locations on the Cisco 7507 and Cisco 7513 platforms and summarize the slot
location conventions on those platforms.
Cisco 7507 Router Slot Numbering

Figure 2-1 shows a Cisco 7507 with an SS7 port adapter installed on the VIP4-80 in slot 5.
Figure 2-1
Cisco 7507
DC
FA
IL
AC
PO
WE
R
NO
RM
PA-MC-8TE1-SS7
6
7
Captive
installation screw
AL
Upper
power supply
EJ
EC
T
2
Chassis
grounding
receptacles
SL SLO
OT T
0 1
SL MA
AV ST
E ER
AV
Captive
installation screw
E/M
CP
RE
AS
TE
HA
SE
AL
SL
EN
LT
EN
AB
LE
65855
DC
FA
IL
AC
PO
WE
R
Lower
power supply
AU
NS
OL
CO
X.
Slot 0
RSP slots
2-3
Chapter 2
Cisco 7513 Router Slot Numbering

Figure 2-2 shows a Cisco 7513 with an SS7 port adapter installed on the VIP4-80 in slot 11.
Figure 2-2
Cisco 7513
Blower module
Cable-management
bracket
RM
AL
PA-MC-8TE1-SS7
6
7
NO
CT
EJE
SLO SLO
T0 T1
/M
CP
RE
AU
NS
TE
HA
SE
LT
EN
AB
LE
X.
CO
AS
AL
VE
EN
SLA
SLA MA
S
V E TE
R
Card cage and

processor modules
OLE
Air intake vent

AC
OK
FAN
OK
OUTPUT
FAIL
AC
OK
OUTPUT
FAIL
POWER
POWER
Chassis grounding
receptacles
2-4
I
I
0
0
65856
Power supplies
FAN
OK
Chapter 2


The SS7 Port Adapter is a single-width, eight-port T1/E1 port adapter with a custom hardware-assist
engine to support SS7 signaling. The SS7 Port Adapter features full channelization of up to 127
HDLC-encoded SS7 (or DS0) channels at 56 Kbps or 64 Kbps. Performance monitoring, Drop and
Insert, BERT functionality, external clocking (with multiple backups), internal clocking, and standard
alarm integration are also supported. The hardware-assist engine provides a 30% MSU per second
performance improvement on the Versatile Interface Processor (VIP) under typical conditions.
The SS7 port adapter supports MTP2, Cisco HDLC, Frame Relay, PPP, and Switched Multimegabit Data
Service (SMDS) Data Exchange Interface (DXI) encapsulations over each T1 or E1 link. For SMDS
only, DXI is sent on the T1 or E1 line, so it needs to connect to an SMDS switch that has direct DXI
input.
The SS7 Port Adapter provides the following features:
Singlewide port adapter with 8 T1 or E1 RJ48c ports
Runs on Cisco 7500 Versatile Interface Processor (VIP4-80)
Integrated CSU/DSU
Software configurable for E1/T1
Software configurable for 56/64 kbps timeslots in E1 and T1 modes
Common external clock source with multiple backups or internal clock
MTP2 FISU/LSSU generation and filtering
Drop and Insert for non-SS7 timeslots
ANSI, ITU, and China SS7 variant support
Figure 2-3 shows a faceplate view of the SS7 Port Adapter.

Figure 2-3
SS7 Port AdapterFaceplate View
AL
PA-MCX-8TE1-M
6
7
65853
EN
When you are running channelized data, each DS1 interface can provide up to 24 T1 channel groups if
your SS7 Port Adapter is configured for T1, or 31 E1 channel groups if your SS7 Port Adapter is
configured for E1. The T1 channel groups are numbered from 0 to 23 and the E1 channel groups are
numbered from 0 to 30. Each T1 channel group provides up to twenty-four 56k or 64-kbps time slots,
which are numbered 1 to 24. Each E1 channel group provides up to thirty-one 64-kbps time slots, which
are numbered 1 to 31. Multiple time slots can be mapped to a single channel group. Each channel group
is presented to the system as a serial interface that can be configured individually. Usable bandwidth for
each channel group is calculated as n x 56 kbps or n x 64 kbps, where n is the number of T1 time slots
(1 to 24) or E1 channels (1 to 31).
Each of the channels on the SS7 Port Adapter uses a portion of the bandwidth (fractional T1 or E1) or
the entire bandwidth for data transmission. Usable bandwidth for each channel is n x 56 kbps or n x 64
kbps, where n is a number from 1 to 24 for T1 and 1 to 31 for E1. When you are not running at full T1
and E1 speeds, the unused portion of the bandwidth cannot be used and is filled with idle channel data.
2-5
Chapter 2
Note
Time slots on the SS7 Port Adapter are numbered 1 to 24 for T1 and 1 to 31 for E1, instead of the
zero-based scheme (0 to 23 or 0 to 30) used with other Cisco products. This numbering scheme is to
ensure consistency with telco numbering schemes for T1 and E1 channels within channelized
equipment.
The SS7 Port Adapter supports Facility Data Link (FDL) in Extended Superframe (ESF) framing on T1
networks, as well as network and payload loopbacks. Bit error rate testing (BERT) is supported on each
of the T1 or E1 links. BERT can be run only on one port at a time.
Note
On a SS7 Port Adapter configured for T1, BERT is done only over a framed T1 signal.
The SS7 Port AdapterSS7 Port Adapter does not support the aggregation of multiple T1s or E1s (called
inverse muxing or bonding) for higher bandwidth data rates.
2-6
Chapter 2


The 8 port IMA port adapters allow you to connect up to eight SS7 High Speed Links to the ITP, as
described in ITU standard Q.2100 and ANSI Telcordia specification GR-2878-CORE. All ports allow
for 1.55 Mbps (T1) or 2.048 MBps (E1) bandwidth utilization on a singe T1 or E1.
BN
EN
BN
18000
E1 IMA
AB
PA-A3-8E1 IMAFaceplate View
LE ALR
D M
Figure 2-5
18001
T1 IMA
EN
PA-A3-8T1 IMAFaceplate View
AB A
LE LR
D M
Figure 2-4
The PA-A3-IMA supports the following features for broadband SS7 support:
Eight standard T1/E1 (1.544/2.048 Mbps) interfaces with two intergated quad RJ-45 connectors.
Binary 8-zero substituation (B8ZS) line encoding for T1 and High-Density Bipolar (HDB3) line
encoding for E1 in accordance with ATM UNI standards; alternate mask inversion (AMI) encoding
for both T1 and E1.
Super Frame (SF) and Extended Super Frame (ESF) framing for T1, Basic Frame, Clear E1 and
CCS-CRC framing for E1.
Header Error Control (HEC) based cell delineation for ATM framing.
Facility Data Link (FDL) processing for T1.
Selectable Tx clock sources for each T1/E1 line.
AAL5, SSCOP, SSCF-NNI and MTP3b.
2-7
Chapter 2
VIP4 Overview
VIP4 Overview
The VIP4, a single motherboard, supports up to two single-width port adapters, or one dual-width port
adapter. Figure 2-6 shows a VIP4 with two installed single-width port adapters. A dual-width
port adapter occupies both port adapter slots (not shown).
Note
To ensure proper airflow in the router and compliance with EMI prevention standards, a
VIP4 with one single-width port adapter must have a blank port adapter installed in the
empty port adapter slot location.
Note
A VIP4 without at least one installed port adapter is not supported.

Figure 2-6
VIP4 with Two Single-Width Port AdaptersHorizontal Orientation Shown
Bus connector
Packet
memory
DIMM U5
CPU memory
DIMM U1
Port adapter
in slot 1
26561
Port adapter
in slot 0
CPU
2-8
Chapter 2

FEIP-DSW Overview
FEIP-DSW Overview
The FEIP2-DSW is a dual-port, fixed configuration interface processor that provides two, 100-Mbps,
IEEE 802.3u Fast Ethernet (FE) interface interfaces and the capability for Distributed Services (DS) and
Distributed Switching (DSW). The dynamic random access memory (DRAM) configuration for the
FEIP2-DSW is 32 megabytes (MB), and the standard static random access memory (SRAM)
configuration is 2 MB.
You can upgrade the DRAM to 64 MB.

The FEIP2-DSW is available in the following fixed configurations:
FEIP2-DSW-2TX(=)FEIP2-DSW with two, 100BASE-TX FE interfaces (See .)

Each 100BASE-TX interface on the FEIP2-DSW-2TX has an RJ-45 connector to attach to
Category 5 unshielded twisted-pair (UTP) for 100BASE-TX, and an MII connector that permits
connection through external transceivers to 62.5/125-micron multimode optical fiber for
100BASE-FX, or to Category 3, 4, and 5 UTP or shielded twisted-pair (STP) for 100BASE-T4
physical media.
Figure 7
Fast Ethernet Interface Processor (FEIP2-DSW-2TX)

Bus connector
CPU
Boot ROM
U6
U4
DRAM
SIMMs
U2
FAST ETHERNET
RJ
45
LI
NK
MI
I
FAST ETHERNET
H9782
SRAM
DIMM U5
EN
AB
LE
D
Note
FEIP2-DSW-2FX(=)FEIP2-DSW with two, 100BASE-FX FE interfaces (See .)

Each 100BASE-FX interface on the FEIP2-DSW-2FX has an SC-type fiber-optic connector for
100BASE-FX, and an MII connector that permits connection through external transceivers to
62.5/125-micron multimode optical fiber for 100BASE-FX, or to Category 3, 4, and 5 UTP or
shielded twisted-pair (STP) for 100BASE-T4 physical media.
2-9
Chapter 2
FEIP-DSW Overview
Figure 8
Fast Ethernet Interface Processor (FEIP2-DSW-2FX)

Bus connector
CPU
Boot ROM
U6
H9783
ER
K
II
M
FAST ETHERNET
FI
BE
R
LI
NK
MI
I
FIB
ER
FIB
II
FAST ETHERNET
LIN
U4
LIN
SRAM
DIMM U5
DRAM
SIMMs
U2
Each FE interface on an FEIP2-DSW can be configured at 100 Mbps, half duplex, for a maximum
aggregate bandwidth of 200 Mbps per pair. Each FE interface on an FEIP2-DSW can also be configured
at 200 Mbps, full duplex, for a maximum aggregate bandwidth of 400 Mbps per pair. Further, one FE
interface can be configured at 100 Mbps, half duplex, while the other FE interface can be configured at
200 Mbps, full duplex, for a maximum aggregate bandwidth of 300 Mbps per pair.
2-10
Chapter 2

Safety Guidelines
Safety Guidelines
This section provides safety guidelines that you should follow when working with any equipment that
connects to electrical power or telephone wiring.
Safety Warnings
Safety warnings appear throughout this publication in procedures that, if performed incorrectly, might
harm you. A warning symbol precedes each warning statement.
Warning
This warning symbol means danger. You are in a situation that could cause bodily injury. Before
you work on any equipment, be aware of the hazards involved with electrical circuitry and be
familiar with standard practices for preventing accidents. To see translations of the warnings
that appear in this publication, refer to the Regulatory Compliance and Safety Information
document that accompanied this device.
Waarschuwing
Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel
kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van
de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard
maatregelen om ongelukken te voorkomen. Voor vertalingen van de waarschuwingen die in
deze publicatie verschijnen, kunt u het document Regulatory Compliance and Safety Information
(Informatie over naleving van veiligheids- en andere voorschriften) raadplegen dat bij dit
toestel is ingesloten.
Varoitus
Tm varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan.

Ennen kuin tyskentelet minkn laitteiston parissa, ota selv shkkytkentihin liittyvist
vaaroista ja tavanomaisista onnettomuuksien ehkisykeinoista. Tss julkaisussa esiintyvien
varoitusten knnkset lydt laitteen mukana olevasta Regulatory Compliance and Safety
Information -kirjasesta (mrysten noudattaminen ja tietoa turvallisuudesta).
Attention
Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant
causer des blessures ou des dommages corporels. Avant de travailler sur un quipement, soyez
conscient des dangers poss par les circuits lectriques et familiarisez-vous avec les
procdures couramment utilises pour viter les accidents. Pour prendre connaissance des
traductions davertissements figurant dans cette publication, consultez le document Regulatory
Compliance and Safety Information (Conformit aux rglements et consignes de scurit) qui
accompagne cet appareil.
Warnung
Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer
Krperverletzung fhren knnte. Bevor Sie mit der Arbeit an irgendeinem Gert beginnen, seien
Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken
zur Vermeidung von Unfllen bewut. bersetzungen der in dieser Verffentlichung enthaltenen
Warnhinweise finden Sie im Dokument Regulatory Compliance and Safety Information
(Informationen zu behrdlichen Vorschriften und Sicherheit), das zusammen mit diesem Gert
geliefert wurde.
2-11
Chapter 2
Safety Guidelines
Avvertenza
Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle
persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi
ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti.
La traduzione delle avvertenze riportate in questa pubblicazione si trova nel documento
Regulatory Compliance and Safety Information (Conformit alle norme e informazioni sulla
sicurezza) che accompagna questo dispositivo.
Advarsel
Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan fre til personskade. Fr
du utfrer arbeid p utstyr, m du vare oppmerksom p de faremomentene som elektriske kretser
innebrer, samt gjre deg kjent med vanlig praksis nr det gjelder unng ulykker. Hvis du vil
se oversettelser av de advarslene som finnes i denne publikasjonen, kan du se i dokumentet
Regulatory Compliance and Safety Information (Overholdelse av forskrifter og
sikkerhetsinformasjon) som ble levert med denne enheten.
Aviso
Este smbolo de aviso indica perigo. Encontra-se numa situao que lhe poder causar danos
fsicos. Antes de comear a trabalhar com qualquer equipamento, familiarize-se com os perigos
relacionados com circuitos elctricos, e com quaisquer prticas comuns que possam prevenir
possveis acidentes. Para ver as tradues dos avisos que constam desta publicao, consulte
o documento Regulatory Compliance and Safety Information (Informao de Segurana e
Disposies Reguladoras) que acompanha este dispositivo.
Advertencia!
Varning!
Este smbolo de aviso significa peligro. Existe riesgo para su integridad fsica. Antes de
manipular cualquier equipo, considerar los riesgos que entraa la corriente elctrica y
familiarizarse con los procedimientos estndar de prevencin de accidentes. Para ver una
traduccin de las advertencias que aparecen en esta publicacin, consultar el documento
titulado Regulatory Compliance and Safety Information (Informacin sobre seguridad y
conformidad con las disposiciones reglamentarias) que se acompaa con este dispositivo.
Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till
personskada. Innan du utfr arbete p ngon utrustning mste du vara medveten om farorna med
elkretsar och knna till vanligt frfarande fr att frebygga skador. Se frklaringar av de
varningar som frkommer i denna publikation i dokumentet Regulatory Compliance and Safety
Information (Efterrttelse av freskrifter och skerhetsinformation), vilket medfljer denna
anordning.
Electrical Equipment Guidelines

Follow these basic guidelines when working with any electrical equipment:
Before beginning any procedures requiring access to the chassis interior, locate the emergency
power-off switch for the room in which you are working.
Disconnect all power and external cables before moving a chassis.
Do not work alone when potentially hazardous conditions exist.
Never assume that power has been disconnected from a circuit; always check.
Do not perform any action that creates a potential hazard to people or makes the equipment unsafe;
carefully examine your work area for possible hazards such as moist floors, ungrounded power
extension cables, and missing safety grounds.
2-12
Chapter 2

Safety Guidelines
Telephone Wiring Guidelines

Use the following guidelines when working with any equipment that is connected to telephone wiring or
to other network cabling:
Never install telephone wiring during a lightning storm.
Never install telephone jacks in wet locations unless the jack is specifically designed for wet
locations.
Never touch uninsulated telephone wires or terminals unless the telephone line has been
disconnected at the network interface.
Use caution when installing or modifying telephone lines.
Preventing Electrostatic Discharge Damage

Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are
improperly handled, results in complete or intermittent failures. Port adapters and processor modules
comprise printed circuit boards that are fixed in metal carriers. Electromagnetic interference (EMI)
shielding and connectors are integral components of the carrier. Although the metal carrier helps to
protect the board from ESD, use a preventive antistatic strap during handling.
Following are guidelines for preventing ESD damage:
Caution
Always use an ESD wrist or ankle strap and ensure that it makes good skin contact.
Connect the equipment end of the strap to an unfinished chassis surface.
When installing a component, use any available ejector levers or captive installation screws to
properly seat the bus connectors in the backplane or midplane. These devices prevent accidental
removal, provide proper grounding for the system, and help to ensure that bus connectors are
properly seated.
When removing a component, use any available ejector levers or captive installation screws to
release the bus connectors from the backplane or midplane.
Handle carriers by available handles or edges only; avoid touching the printed circuit boards or
connectors.
Place a removed board component-side-up on an antistatic surface or in a static shielding container.

If you plan to return the component to the factory, immediately place it in a static shielding
container.
Avoid contact between the printed circuit boards and clothing. The wrist strap only protects
components from ESD voltages on the body; ESD voltages on clothing can still cause damage.
Never attempt to remove the printed circuit board from the metal carrier.
For safety, periodically check the resistance value of the antistatic strap. The measurement should be
between 1 and 10 megohms (Mohms).
2-13
Chapter 2

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant
to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates,
uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference, in which case users will be
required to correct the interference at their own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference
stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment
causes interference to radio or television reception, try to correct the interference by using one or more
of the following measures:
Note
Turn the television or radio antenna until the interference stops.
Move the equipment to one side or the other of the television or radio.
Move the equipment farther away from the television or radio.
Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is,
make certain the equipment and the television or radio are on circuits controlled by different circuit
breakers or fuses.)
The SS7 Port Adapter has been designed to meet these requirements. Modifications to this product
that are not authorized by Cisco Systems, Inc., could void the various approvals and negate your
authority to operate the product.
Required Tools and Equipment

You need the following tools and parts to install a port adapter, VIP, or interface processor. If you need
additional equipment, contact a service representative for ordering information.
Number 1 and Number 2 Phillips and a 3/16-inch, flat-blade screwdriver
PA-MCX-8TE1-M(=) port adapter, hereafter referred to as the SS7 Port Adapter
PA-A3-8E1IMA port adapter, hereafter referred to as the ATM Adapter.
VIP4-80, hereafter referred to as the VIP4
FEIP2-DSW-2TX= or FEIP2-DSW-2FX=, and at least one available interface processor slot in your
Cisco 7500 series router
Cables appropriate for the FE interfaces on your FEIP2-DSW; Cisco Systems does not supply
Category 5 UTP RJ-45 cables, MII cables, or SC-type, 62.5/125-micron optical-fiber cables; these
cables are available commercially.
Shielded cables (FTP [foil twisted-pair]) with 120-ohm impedance
Your own electrostatic discharge (ESD)-prevention equipment or the disposable grounding wrist
strap included with all upgrade kits, field-replaceable units (FRUs), and spares
Antistatic mat
Antistatic container
2-14
Chapter 2

Software and Hardware Requirements
Caution
Before you attach an MII transceiver to an MII receptacle on your FEIP2-DSW, ensure that your MII
transceiver responds to physical sublayer (PHY) address 0 per section 22.2.4.4. PHY Address of the
IEEE 802.3u specification; otherwise, interface problems might result. Confirm that this capability is
available on your MII transceiver with the transceiver's vendor or in the transceiver's documentation. If
a selection for Isolation Mode is available, we recommend you use this setting (if no mention is made
of PHY addressing).
Caution
To prevent system problems, do not simultaneously connect cables to the RJ-45 (or SC) and MII
receptacles on a single FEIP2-DSW, FE interface. Each FE interface (100BASE-FX or 100BASE-TX)
can have either an MII attachment or an RJ-45 (or SC) attachment, but not both. The MII and RJ-45 (or
SC) receptacles represent two physical connection options for one FE interface.
Software and Hardware Requirements

Cisco IOS Release 12.2(4)MB3 or a later release of Cisco IOS Release 12.2
Checking Hardware and Software Compatibility

To check the minimum software requirements of Cisco IOS software with the hardware installed on your
router, Cisco maintains a hardware and software compatibility matrix on Cisco.com. This tool does not
verify whether modules within a system are compatible, but it does provide the minimum IOS
requirements for individual hardware modules or components.
Note
Access to this tool is limited to users with Cisco.com login accounts.

To access the matrix, click Login at Cisco.com and go to Service & Support: Technical Support
HelpCisco TAC: Tool Index: HW-SW Compatibility Matrix. You can also access the matrix by
pointing your browser directly to
http://www.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi.
Choose a product family or enter a product number to search for the minimum supported software release
needed for your hardware.
Warning
This equipment will be inoperable when main power fails.
2-15
Chapter 2
Ensuring Network Operation During Removal of VIP and Port Adapters
Ensuring Network Operation During Removal of VIP and Port

Adapters
Before you remove the VIP from the router chassis, review the following important information:
Understanding Online Insertion and Removal (OIR), page 16
Taking Active Links Out of Service, page 16
Understanding Online Insertion and Removal (OIR)

Online board installation and removal (OIR) refers to the capability to remove and install specific
interface processors while the system is in operation, without risking system crash or error. VIPs
connected to the CxBus support OIR. A VIP can be removed from the system with no disassembly other
than external interface cabling.
To perform OIR properly, always wait 30 seconds between removal and reinsertion of the VIP.
Note
Adding additional hardware such as port adapters or a VIP4-80 to the ITP is different than replacing
faulty hardware and requires a 60-second downtime. Such an operation should be planned for and
performed during a maintenance schedule.
Taking Active Links Out of Service

Within the well-designed SS7 network, alternate linksets on the ITP are configured so that, in the event
of a network, hardware, or maintenance condition, a path is always available for signaling traffic flow
across the linkset on the redundant VIP. If removal of the affected VIP is to be performed while links
within a linkset are active, you should first gracefully disable the links associated with the port adapters
installed on the VIP.
We recommend that you inhibit and shutdown all the in-service links associated with the port adapter
before you remove the VIP. This will allow traffic to be rerouted to the alternate linkset.
If the active links have already been disabled, proceed to the Removing the VIP4 section on
page 16.
If the active links have not been disabled and you wish to disable them, follow the procedure in the
chapter that pertains to your port adapter type, then proceed with this procedure:
Chapter 11, Taking an SS7 PA Out of Service
Chapter 12, Taking an HSL PA Out of Service
Removing the VIP4

Note
To help prevent dust and contaminants from entering the chassis, do not leave the interface
processor slot open. If you do not plan to reinstall the VIP immediately, insert an interface
processor filler in the empty slot
2-16
Chapter 2

Removing the VIP4
Step 1
Attach an ESD-preventive wrist strap between you and an unpainted chassis surface.
Step 2
Remove the standby RSP8.
Step 3
Wait 20 to 30 seconds. This time will vary depending on the number of interfaces installed in your
system.
Step 4
Disconnect all cables from the VIP4 interface ports.
Step 5
Use a screwdriver to loosen the captive installation screws at both ends of the board.
Caution
Step 6
Always use the ejector levers to remove a VIP4 or interface processor. Failure to do so can
cause erroneous system error messages indicating a board failure.
Place your thumbs on the ejector levers and simultaneously pull both of the ejector levers outward to
release the board from the backplane connector.
Use the boards handle to carefully pull it straight out of the slot, keeping your other hand under the
carrier to guide it.
If you removed a VIP4 or interface processor and the interface processor slot is to remain empty,
install an interface processor filler (Product Number MAS7K-BLANK=) to keep dust out of the
router, maintain proper airflow inside the router, and ensure compliance with EMI approvals by
providing a tight EMI-preventive seal. Do not leave the interface processor slot open.
Step 7
Place the removed board on an antistatic mat or foam pad, or place it in an antistatic container if you
plan to return it to the factory.
Step 8
system.
Step 9
Reinsert the standby RSP8.
This completes the procedure for removing a VIP4 from your Cisco 7500 series router. You are now
ready to remove or install the SS7 Port Adapter. Proceed to the Removing and Installing Port Adapters
from the VIP4 section on page 18.
2-17
Chapter 2
Removing and Installing Port Adapters from the VIP4

This section describes safe and proper handling of a port adapter and provides an illustrated procedure
for removing and installing port adapters.
Note
Removing and installing port adapters always requires removing the VIP from the ITP.
Safe and Proper Handling of Port Adapters

The SS7 Port Adapter and the ATM Port Adapter are single-width port adapters that occupy either of the
two port adapter slots on a VIP4. When a single-width port adapter slot is not in use, a blank port adapter
must fill the empty slot to allow the router to conform to electromagnetic interference (EMI) emissions
requirements and to allow proper airflow through the router. If you plan to install a new single-width
port adapter in a port adapter slot that is not in use, you must first remove the blank port adapter.
Caution
Always handle the port adapter by the carrier edges and handle; never touch the port adapter
components or connector pins. (See Figure 2-9.)
Figure 2-9
Handling a Port Adapter

Metal carrier
H6420
Printed circuit board
Caution
To prevent system problems, do not remove port adapters from the VIP4 motherboard or
attempt to install other port adapters on the VIP4 motherboard while the system is
operating. To install or replace port adapters, first remove the VIP4.
Caution
To prevent a disruption to system operation, you should replace a port adapter with the
same type of port adapter you removed, but this is not a requirement.
Warning
When performing the following procedures, wear a grounding wrist strap to avoid ESD
damage to the card. Some platforms have an ESD connector for attaching the wrist strap.
Do not directly touch the backplane with your hand or any metal tool, or you could shock
yourself.
2-18
Chapter 2

After you have reviewed the preceding safety precautions, you are ready to remove or install the SS7
Port Adapter on the VIP4-80. Proceed to the Illustrated Procedure for Removing and Installing Port
Adapters section on page 20.
2-19
Chapter 2
Illustrated Procedure for Removing and Installing Port Adapters

Note
When you reach Step 6 of this procedure, refer to the more detailed information at the beginning of
the Reinstalling the VIP4 section on page 22.
Figure 2-10 describes removing and installing a single-width port adapter such as the SS7 Port Adapter
or the ATM Port Adapter.
Figure 2-10 Removing and Installing a Single-Width Port Adapter
Note: You must first remove the

VIP4 from the chassis before
removing a port adapter from the
VIP4.
Step 1
To remove the port adapter,
remove
the screw that secures the port
adapter (or blank port adapter).
(See A.)
Step 2
With the screw removed, grasp
the handle on the front of the port
adapter (or blank port adapter)
and carefully pull it out of its slot,
away from the edge connector at
the rear of the slot. (See A.)
Screw
Step 3
To insert the port adapter,
carefully align the port adapter
carrier between the upper and
the lower edges of the port
adapter slot. (See B.)
Carrier
Upper edge
Lower edge
Step 4
Install the screw in the rear of the
port adapter slot. Do not overtighten
the screw. (See A.)
C
NO
RM
AL
Captive
installation
screw
PA-MC-8TE1-SS7
7
6
IL
PO
WE
EC
T
5
EJ
SL SLO
OT T
0 1
SL MAS
AV TE
E
R
AV
E/
MAS
CPU
RES
TE
HAL
T
1
SL
ET
Step 5
Carefully slide the new port adapter
into the port adapter slot until the
connector on the port adapter is
completely seated in the connector
at the rear of the port adapter slot.
(See B.)
FA
DC
AC
FA
IL
PO
WE
EN
AC
AL
DC
EN
AB
LE
2-20
AU
CO
X.
NSO
LE
29327
Step 6
Reinstall the VIP4 motherboard in the
chassis, and tighten the captive
installation screw on each end of the
VIP4 faceplate. (See C.)
Chapter 2

After you have installed the SS7 Port Adapter or the ATM Port Adapter on the VIP4 motherboard (Step
5), you are ready to reinstall the VIP in the router chassis and connect the SS7 Port Adapter cables.
Proceed to the Reinstalling the VIP4 section on page 22.
2-21
Chapter 2

Note
Reinstalling the VIP in the router chassis is illustrated in the final step (Step 6) of the Illustrated
Procedure for Removing and Installing Port Adapters section on page 20. If you have already
reinstalled the VIP in the router chassis, proceed to the Connecting the Port Adapter Cables section
on page 24.
After you have installed the SS7 Port Adapter and/or ATM Port Adapter on the VIP4-80, you must
reinstall the VIP into the same slot from which it was removed. The VIP4 slides into an open interface
processor slot and connects directly to the backplane. The interface processors are keyed to guide pins
on the backplane, so the VIP4 can be installed only in an interface processor slot.
Note
To ensure compliance with EMI approvals by providing a tight EMI seal for the Cisco 7500
and the Cisco 7000 routers, we recommend that you first install interface processors in the
interface processor slots closest to the RSP slots, and then work out to the
interface processor slots furthest from the RSP slots. For more information on interface
processor slots on your router, refer to the Cisco 7500 Series Installation and Configuration
Guide or the appropriate Quick Start Guide for the Cisco 7500 series routers, or refer to
Cisco 7000 Hardware Installation and Maintenance manual for the Cisco 7000 series
routers.
Caution
Remove or insert only one interface processor at a time. Allow the system to complete its
discovery and initialization of the interfaces before removing or inserting another
interface processor. Disrupting the sequence before the system has completed verification
can cause the system to detect spurious hardware failures.
Use the following procedure to install a VIP4:
Step 1
Step 2
Ensure that a console terminal is connected to the console port (on the RSP or RSP7000) and that your
console is turned on, or that you have a reliable Telnet connection to the system.
Step 3
Hold the VIP4 handle with one hand and place your other hand under the carrier to support the VIP4
and guide it into the slot. Avoid touching the card or any connector pins.
Caution
To prevent ESD damage, handle interface processors by the handles and carrier edges only.
Step 4
Place the back of the VIP4 in the slot and align the notch on the carrier with the groove in the slot.
Step 5
While keeping the VIP4 parallel to the backplane, carefully slide it into the slot until the back of the
faceplate makes contact with the ejector levers, and then stop.
Caution
Always use the ejector levers when installing or removing interface processors. An
interface processor that is partially seated in the backplane might cause the system to hang
and subsequently crash, and shoving or slamming the interface processor into the slot can
damage the backplane pins and board.
2-22
Chapter 2

Step 6
Using your thumbs, simultaneously push both ejector levers inward until the VIP4 is pushed entirely
into its slot.
Step 7
Tighten both of the captive installation screws.
Caution
To ensure proper EMI isolation for the router, be sure to tighten the captive installation
screws on each VIP4 immediately after you install it and before proceeding with the
installation of each remaining VIP4 or other interface processor.
2-23
Chapter 2
Connecting the Port Adapter Cables

Depending on the port adapters you have installed, perform either or both of the following tasks:
Connecting the SS7 Port Adapter Interface Cables, page 24
Connecting PA A3-IMA Cables, page 26
Connecting a 75-120 Ohm Adapter Cable, page 27

The SS7 Port Adapter uses shielded twisted-pair cables with RJ-48C connectors to connect to a PBX or
to the Public Switched Telephone Network (PSTN).
Each connection supports T1 (100-ohm) or E1 (120-ohm) interfaces that meet T1.403 and ACCUNET
TR62411 standards. The RJ-48C connector does not require an external transceiver. The DS1 ports are
T1 interfaces that use foil twisted-pair (FTP) cables.
Figure 2-11 shows the SS7 Port Adapter interface cable connector
87654321
RJ-48C connector
24939
Figure 2-11 SS7 Port Adapter Interface Cable Connector
Table 2-1 lists the signal pinouts and descriptions for the RJ-48C connector.
Table 2-1
Note
Pin
Signal
RX tip
RX ring
No connection
TX tip
TX ring
No connection
No connection
No connection
Shielded cables (FTP [foil twisted-pair]) with 120-ohm impedance are required to comply with CE
marking requirements. These shielded cables are not available from Cisco Systems; they are
available from outside commercial cable vendors.
2-24
RJ-48C Connector Pinouts

To connect FTP cables with RJ-48C connectors to the SS7 Port Adapter, proceed as follows:
Step 1
Attach the cable directly to one of the RJ-48C ports on the SS7 Port Adapter.
Step 2
Attach the network end of the cable to your external equipment.
Step 3
Repeat Step 1 and Step 2 for the other SS7 Port Adapter ports.
Figure 2-12 Connecting the SS7 Port Adapter Twisted-Pair Cable with RJ-48C Connector
AL
PA-MCX-8TE1-M
6
7
EN
65854
Chapter 2
Twisted-pair cable
with RJ-48C connector
To PBX or PSTN
After you properly connect a port to a line, it takes approximately 30 seconds for Cisco IOS to report
that the line is up.
2-25
Chapter 2
Connecting PA A3-IMA Cables

The eight DS1/E1 interface receptacles on the PA-A3-IMA are RJ-45 connectors for T1 (100 ohm) or
E1 (120 ohm). All eight may be used simultaneously as ATM interfaces, or they may be used to create
IMA groups.
Note
After you properly connect a port to a line, it takes approximately 30 seconds for Cisco IOS software to
report that the line is up.
TR62411 standards. The RJ-45 connection does not require an external transceiver. The DS1 ports are
Note
To meet VCCI Class II EMI requirements, you must use FTP cables.
Figure 2-13 shows the PA-A3-IMA interface cable connector.
H2936
Figure 2-13 PA-A3-IMA Interface Connector
87654321
RJ-45 connector
RJ-48C Connector PinoutsTable 2-1 lists the signal pinouts and descriptions for the RJ-45 connector.
IMA Interface Cable RJ-45 Connector Pinouts
Pin
Signal
Signal
To
J1-1
RX ring
TX ring
J2-4
J1-2
RX tip
TX tip
J2-5
J1-3
RX shield
TX shield
NC
J1-4
TX ring
RX ring
J2-1
J1-5
TX tip
RX tip
J2-2
J1-6
TX shield
RX shield
NC
J1-7
NC
NC
J1-8
NC
NC
2-26
Chapter 2

Connecting a 75-120 Ohm Adapter Cable

The 75120-ohm adapter cable connects Cisco 120-ohm E1 port adapters to 75-ohm unbalanced G.703
E1 lines. The adapter has an eight-pin RJ-48C connector on the 120-ohm side and dual BNC coaxial
connectors (transmit and receive) on the 75-ohm side. Two switches on the 120-ohm side allow the outer
conductor of the cable (the input port of the E1 port adapter) to be either isolated from or connected to
a protected earth ground (see Figure 2-14). The 120-ohm E1 ports of your port adapter connect to the
75120-ohm adapter cable using RJ-48C connectors and Category 3 or Category 5 shielded foil
twisted-pair (FTP) cable with 120-ohm impedance (see Figure 15 and Figure 16).Table 2-1
Early versions of this cable do not have the ground switches.

Figure 2-14 75120-Ohm Adapter Cable
XMI
T SH
IEL
CON 1 D TO G
NEC 2 ND 1
T XM
2
IT S
HIEL
D TO
GND
12
DISCONNECT XMIT SHIELD TO GND 1 2

XMIT
DISC
ONN
ECT
CONNECT XMIT SHIELD TO GND 1 2
RCV
RJ-48c
Figure 15
E1 Multichannel Port Adapter Interface Cable and RJ-48C Connector
87654321
RJ-48c connector
Table 2Table 2-1 shows the pinouts of the RJ-48C connector on the 75120-ohm adapter cable.
Table 2
Pin
Signal
Rx ring 1
Rx tip
NC2
Tx ring3
Tx tip
2-27
45561
1 2
H10253
Note
Chapter 2
Table 2
Pin
Signal
NC
NC
NC
1. Rx = receive.
2. NC = no connection.
3. Tx = transmit.

Connect the 75120-ohm adapter cable between the port adapter and the 75-ohm unbalanced G.703 E1
line using the following procedure:
Step 1
Note
Step 2
Note
Set the two ground switches to the desired position.
To ground the outer conductor of the cable, both switches must be in the down position. To
isolate the outer conductor of the cable from ground, both switches must be in the up
position (see Figure 2-14).
Attach the Category 3 or Category 5 FTP cable directly to the RJ-48C port on the E1 multichannel port
adapter.
To comply with CE marking requirements, use shielded foil twisted-pair (FTP) cable with
120-ohm impedance.
Step 3
Attach the network end of your Category 3 or Category 5 cable to your 75120-ohm adapter cable.
Step 4
Attach the BNC connector of the 75120-ohm adapter cable marked receive to the network device
connector marked transmit.
Step 5
Attach the BNC connector of the 75120-ohm adapter cable marked transmit to the network device
connector marked receive.
2-28

Figure 16
Connecting a 75120-Ohm Adapter Cable to a Multichannel E1 Port Adapter
7
6
24067
1
0
K
L IN
AB
LE
MULTICHANNEL E1/PRI
EN
Chapter 2
Category 3 or Category 5
shielded foil twisted-pair (FTP) cable
TX
RX
2-29
Chapter 2

This section describes the procedures you can use to verify your VIP4 and port adapter
installation.Observing LED
Note
The VIP4 has no LEDs that are visible or usable when the VIP4 is installed. The
port adapters you install on the VIP4 have status and interface LEDs.
After you install the VIP4 and connect the SS7 Port Adapter cables, you can verify the installation by
observing the port adapter LED states and the system messages displayed on your console terminal.
When the system has reinitialized all interfaces, the enabled LED on the VIP4 port adapters and on all
interface processors should go on, depending on your connections and configuration. The console screen
also displays a message as the system discovers each interface during its reinitialization.
SS7 Port Adapter LEDs

The SS7 Port Adapter has a green enabled LED, a bicolor alarm LED, and a bicolor port status LED,
one for each port on the port adapter (see Figure 2-17).
Figure 2-17 LEDs on the SS7 Port Adapter
AL
PA-MCX-8TE1-M
6
7
65853
EN
After system initialization, the enabled LED goes on to indicate that the port adapter has been enabled
for operation.
The following conditions must be met before the SS7 Port Adapter is enabled:
The SS7 Port Adapter is correctly connected and is receiving power.
A valid system software image for the port adapter has been downloaded successfully.
The system recognizes the SS7 Port Adapter.
If any of the above conditions are not met, or if the initialization fails for other reasons, the enabled LED
does not go on.
Table 2-3 lists the functions of the LEDs.
Table 2-3
LED Label
Color
State
Function
EN
Green
On
Indicates the SS7 Port Adapter is powered up.
Off
Indicates the SS7 Port Adapter is not ready or is

disabled.
Amber
On
Indicates an alarm condition exists on the remote

end of one of the T1/E1 ports.
Red
On
Indicates an alarm condition exists locally on one

of the T1/E1 ports.
AL
2-30
Chapter 2

Table 2-3
LED Label
SS7 Port Adapter LEDs (continued)
Color
0 through 7 Green
Yellow
State
Function
Off
Indicates no alarms detected on any port.
On
Indicates the port is enabled and in frame.
On
Indicates the port is in loopback.
Off
Indicates that the port is not enabled, the received

signal is bad, or an alarm condition exists.
PA-A3-IMA LEDs
The PA-A3-IMA has ten LEDs: one bicolor alarm LED, one green enabled LED, and eight bicolor port
status LEDs (see Figure 2-18).
E1 IMA
BN
18002
RM
AL
ED
BL
NA
Figure 2-18 LEDs on the PA-A3-IMA
for operation.
The following conditions must be met before the PA-A3-IMA is enabled:
The PA-A3-IMA is correctly connected and is receiving power.
The system recognizes the PA-A3-IMA or a VIP2 with a PA-A3-IMA or a VIP4 with a PA-A3-IMA.
does not go on.
Table 2-4 lists LED colors and indications.
Table 2-4
PA-A3-IMA LEDs
LED Label
Color
State
Function
ALRM
Yellow
On
Indicates a minor alarm on one of the T1/E1 ports
Red
On
Indicates a major alarm on one of the T1/E1 ports
ENABLED
Green
On
Indicates IMA port adapter is enabled for

operation
Port 07
Green
On
Indicates port is enabled and in frame
Green/Yellow
Off
Indicates port is not initialized or is in alarm

condition
Yellow
On
Indicates port is in loopback
2-31
Chapter 2
FEIP2-DSW Installation
The FEIP2-DSW operates in all Cisco 7500 series routers, and in Cisco 7000 series routers using the
7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI). The
FEIP2-DSW is capable of providing Distributed Services (DS) and Distributed Switching (DSW).
Note
Software licenses are required to use DSW and DS and are included with the FEIP2-DSW.
IEEE 802.3u is well suited to applications where a local communication medium must carry sporadic,
occasionally heavy traffic at high peak data rates. Stations on a CSMA/CD LAN can access the network
at any time. Before sending data, the station listens to the network to see if it is already in use. If it is,
the station waits until the network is not in use, then transmits; this is half-duplex operation.
A collision occurs when two stations listen for network traffic, hear none, and transmit very close to
simultaneously. When this happens, both transmissions are damaged, and the stations must retransmit.
The stations detect the collision and use backoff algorithms to determine when they should retransmit.
Both Ethernet and IEEE 802.3u are broadcast networks, which means that all stations see all
transmissions. Each station must examine received frames to determine if it is the intended destination
and, if it is, to pass the frame to a higher protocol layer for processing.
IEEE 802.3u specifies the following different physical layers for 100BASE-T:
100BASE-TX100BASE-T, half and full duplex over Category 5 unshielded twisted-pair (UTP),
Electronics Industry Association/Telecommunications Industry Association
[EIA/TIA]568-compliant cable
100BASE-FX100BASE-T, half and full duplex over optical fiber
100BASE-T4100BASE-T, half and full duplex over Category 3, 4, or 5 UTP or shielded

twisted-pair (STP) cabling with four pairs; also called 4T+ or T2, which is 2-pair UTP over Category
3 cable.
Each physical layer protocol has a name that summarizes its characteristics in the format speed/signaling
method/segment length, where speed is the LAN speed in megabits per second (Mbps), signaling method
is the signaling method used (either baseband or broadband), and segment length is typically the
maximum length between stations in hundreds of meters. Therefore, 100BASE-T specifies a 100-Mbps,
baseband LAN with maximum network segments of 100 meters (or 400 meters for 100BASE-FX).
IEEE 802.3u 100BASE-T Specifications

Table 5 lists the cabling specifications for 100-Mbps Fast Ethernet transmission over UTP, STP, and
fiber-optic cables. Table 6 summarizes IEEE 802.3u 100BASE-T physical characteristics for
100BASE-TX and 100BASE-FX.
Table 5
Parameter
RJ-45
Specifications and Connection Limits for 100-Mbps Transmission
MII
1
SC-Type
Cable specification
Category 5 UTP , 22 to 24
AWG3
Category 3, 4, or 5, 150-ohm UTP or 62.5/125 multimode

STP, or multimode optical fiber
optical fiber
Maximum cable length
1.64 ft (0.5 m) (MII-to-MII cable4)
2-32
Chapter 2

Parameter
RJ-45
MII
SC-Type
Maximum segment
length
328 ft (100 m) for

100BASE-TX
3.28 ft (1 m)5 or 1,312 ft (400 m) for 328 ft (100 m)

100BASE-FX
Maximum network
length
656 ft (200 m)5 (with 1

repeater)
656 ft (200 m)5 (with 1

repeater)
1. EIA/TIA-568 or EIA-TIA-568 TSB-36 compliant.

2. Cisco Systems does not supply Category 5 UTP RJ-45 or 150-ohm STP MII cables. Both are available commercially.
3. AWG = American Wire Gauge. This gauge is specified by the EIA/TIA-568 standard.
4. This is the cable between the MII port on the FE interface and the appropriate transceiver.
5. This length is specifically between any two stations on a repeated segment.
Table 6
IEEE 802.3u Physical Characteristics
Parameter
100BASE-FX
100BASE-TX
Data rate (Mbps)
100
100
Signaling method
Baseband
Baseband
Maximum segment length

(meters)
100 m between repeaters
100 m between DTE1 and

repeaters
Media
SC-type: dual simplex or single duplex for Rx

and Tx
RJ-45MII
Topology
Star/hub
Star/hub
1. DTE = data terminal equipment.
For interface port and cable pinouts, refer to the FEIP2-DSW Receptacles, Cables, and Pinouts section
on page 41. You can install FEIP2-DSW in any available interface processor slot.
Note
Each FEIP2-DSW model is a fixed configuration; therefore, individual FE interfaces are not available as
spare parts, do not have handles, and are not field replaceable or removable. You must treat the entire
FEIP2-DSW assembly as a field-replaceable unit (FRU).
Caution
To prevent system problems, we recommend that you not attempt to remove an FEIP2-DSW FE interface
and replace it with another type of interface, nor attempt to mix 100BASE-TX and 100BASE-FX FE
interfaces on the same FEIP2-DSW.
Note
Each of the FEIP2-DSW-2FXs two 100BASE-FX interfaces uses the MII connector like the
FEIP2-DSW-2TX, but the FEIP2-DSW-2FX has an SC-type fiber-optic connector in place of the RJ-45
connector. Either the MII LED or the RJ-45 (or FIBER) LED should be on at any one time; never both.
Caution
receptacles on a single FEIP2-DSW FE interface. Each FE interface (100BASE-FX or 100BASE-TX)
2-33
Chapter 2
The online insertion and removal function allows you to install and remove an FEIP2-DSW without first
shutting down the system; however, you must follow the instructions carefully. Failure to insert the
FEIP2-DSW properly can cause system error messages indicating a board failure.
Each unused interface processor slot must contain an interface processor filler (which is an interface
processor carrier without an interface board) to keep dust out of the chassis and to maintain proper air
flow through the interface processor compartment. If you are installing a new FEIP2-DSW that is not a
replacement, you must first remove the interface processor filler from an unused slot; to do so proceed
to theRemoving an Interface Processor or Interface Processor Filler section on page 34. If you are
replacing an FEIP2-DSW, proceed to the Removing an FEIP2-DSW section on page 34.
Note
To ensure compliance with EMI approvals by providing a tight EMI-preventive seal for the Cisco 7507
and Cisco 7513 routers, we recommend that you first install interface processors in the interface
processor slots closest to the RSP slots, whenever possible, then work out to the interface processor slots
furthest from the RSP slots.
Removing an Interface Processor or Interface Processor Filler

If you plan to replace a currently installed interface processor with an FEIP2-DSW, attach an
ESD-preventive wrist strap between you and any unpainted chassis surface; interface processor fillers
do not require protection from ESD. Select an interface processor slot for the new FEIP2-DSW and
remove the interface processor or interface processor filler as follows:
Step 1
Use a screwdriver to loosen the captive installation screws on the interface processor or interface
processor filler.
Step 2
Place your thumbs on both ejector levers and simultaneously pull them both outward to release the
filler from the backplane connector.
Step 3
Grasp the handle with one hand and pull the card straight out of the slot, keeping your other hand under
the carrier to guide it. (See .) Keep the carrier parallel to the backplane.
Step 4
Store the interface processor or interface processor filler for future use.
To help prevent dust and contaminants from entering the chassis, do not leave the interface processor
slot open. Immediately proceed to the Reinstalling the VIP4 section on page 22.
Removing an FEIP2-DSW
You need not shut down the interface or the system power when removing an FEIP2-DSW or interface
processor.
Note
In Cisco 7507 or Cisco 7513 systems, online insertion and removal of any interface processor in either
CyBus might cause the slave RSP8 to reboot with a bus error or a processor memory parity error. The
master RSP will recover from this event and issue a cBus Complex Restart message. Cisco 7507 and
Cisco 7513 systems that are configured with an RSP8 as the system slave are not affected and will not
experience this problem.
If you have a Cisco 7507 or a Cisco 7513 with an RSP8 configured as the system slave, we strongly
recommend that you use the following procedure to remove and replace an interface processor:
2-34

Step 1
Remove the slave RSP8.
Step 2
Wait 15 seconds.
Step 3
Remove and replace the interface processor using the procedures in this publication.
Step 4
Wait 15 seconds.
Step 5
Reinsert the slave RSP8.

If you are replacing a failed FEIP2-DSW, remove the existing board first, then install the new
FEIP2-DSW in the same slot. If you are replacing a currently installed interface processor with an
FEIP2-DSW, remove the existing board first, then install the new FEIP2-DSW in the same slot.
shows proper handling of an interface processor during installation.
Figure 19
Handling Processor Modules for Installation and Removal

(Horizontal Orientation Shown)
H4714
Chapter 2
Captive installation
screws
To remove an FEIP2-DSW or interface processor, follow these steps:

Step 1
Attach an ESD-preventive wrist strap between you and any unpainted chassis surface.
Step 2
If you are replacing a failed FEIP2-DSW, disconnect all cables from the FEIP2-DSW ports; however, if
you are only moving an FEIP2-DSW to another slot, this step is not necessary.
Step 3
Caution
Always use the ejector levers to remove or install the FEIP2-DSW. Failure to do so can cause erroneous
system error messages indicating a board failure.
Step 4
Place your thumbs on the ejector levers and simultaneously pull both of the ejectors outward to release
the FEIP2-DSW from the backplane connector.
2-35
Chapter 2
Step 5
carrier to guide it. (See .) Keep the board parallel to the backplane.
Step 6
Step 7
If the interface processor slot is to remain empty, install a filler (MAS7K-BLANK) to keep dust out of
the chassis and to maintain proper air flow inside the chassis. Do not leave the interface processor slot
open. Immediately proceed to the Reinstalling the VIP4.
Installing an FEIP2-DSW
The FEIP2-DSW slides into the same slot from which the faulty card was removed and connects directly
to the backplane. The interface processors are keyed to guide pins on the backplane, so the FEIP2-DSW
can be installed only in an interface processor slot.
Note
To ensure compliance with EMI approvals, by providing a tight EMI seal for the Cisco 7507 and Cisco
7513 routers, we recommend that you first install interface processors in the interface processor slots
closest to the RSP slots, whenever possible, then work out to the interface processor slots furthest from
the RSP slots.
Caution
Remove or insert only one interface processor at a time. Allow at least 15 seconds for the system to
complete its discovery and initialization before removing or inserting another interface processor.
Disrupting the sequence before the system has completed verification can cause the system to interpret
hardware failures.
Follow these steps to install an FEIP2-DSW:
Step 1
console is turned ON.
Step 2
Hold the FEIP2-DSW handle with one hand and place your other hand under the carrier to support the
FEIP2-DSW and guide it into the slot. (See .) Avoid touching the card or any connector pins.
Caution
Note
The processor modules are oriented horizontally in the Cisco 7010 and Cisco 7505 and vertically in the
Cisco 7000, Cisco 7507, and the Cisco 7513.
Step 3
Place the back of the FEIP2-DSW in the slot and align the notch on the carrier with the groove in the
slot.
Step 4
While keeping the FEIP2-DSW parallel to the backplane, carefully slide it into the slot until the back of
the faceplate makes contact with the ejector levers, then stop.
2-36
Chapter 2

Caution
Always use the ejector levers when installing or removing processor modules. A module that is partially
seated in the backplane might cause the system to hang and subsequently crash, and shoving or slamming
the interface processor into the slot can damage the backplane pins and board.
Step 5
Using your thumbs, simultaneously push both ejector levers inward until the FEIP2-DSW is pushed
entirely into its slot.
Step 6
Caution
To ensure proper electromagnetic interference (EMI) isolation for the chassis, make certain to tighten
the captive installation screws on each FEIP2-DSW immediately after you install it and before
proceeding with the installation of each remaining FEIP2-DSW or other interface processor.
Attaching Cables to FEIP2-DSW

The MII and RJ-45 (or SC) receptacles represent two physical connection options for one FE interface.
Each FEIP2-DSW has two FE interfaces. On a single FE interface, you can use either the RJ-45 (or SC
for FEIP2-DSW-2FX) connection or the MII connection. You can use the RJ-45 (or SC for
FEIP2-DSW-2FX) connection on one FE interface and the MII connection on the other.
Note
RJ-45, SC, and MII cables are not available from Cisco Systems; they are available from outside
commercial cable vendors.
Connect RJ-45, SC (FEIP2-DSW-2FX), or MII cables as follows:
Step 1
If you have MII connections, attach an MII cable directly to the MII port on the FEIP2-DSW or attach
a 100BASE-T transceiver, with the media appropriate to your application, to the MII port on the
FEIP2-DSW. (See for FEIP2-DSW-2TX or for FEIP2-DSW-2FX.)
Caution
Before you attach an MII transceiver to an MII receptacle on your FEIP2-DSW, ensure that your MII
transceiver responds to physical sublayer (PHY) address 0 per section 22.2.4.4. PHY Address of the
IEEE 802.3u specification; otherwise, interface problems might result. Confirm that this capability is
available on your MII transceiver with the transceiver's vendor or in the transceiver's documentation. If
a selection for Isolation Mode is available, we recommend you use this setting (if no mention is made
of PHY addressing).
If you have RJ-45 connections, attach the Category 5 UTP cable directly to one of the RJ-45 ports on the
FEIP2-DSW. (See for FEIP2-DSW-2TX or for FEIP2-DSW-2FX.) The FEIP2-DSW is an end station
device and not a repeater. You must connect the FE interface to a repeater or hub.
If you have an SC connection (FEIP2-DSW-2FX), attach a cable directly to the SC port on one of the
FEIP2-DSW-2FXs interfaces. (See .) Use either one duplex SC connector, or two simplex SC
connectors, and observe the correct relationship between the receive (RX) and transmit (TX) ports on
the FEIP2-DSW-2FX and your repeater.
2-37
Chapter 2
Connecting MII or RJ-45 Cables (FEIP2-DSW-2TX Shown, Horizontal Orientation)
FAST ETHERNET
MII cable
To transceiver,
repeater, or DTE
Note
or
RJ-45 cable
To repeater
or DTE
Each Fast Ethernet interface (100BASE-FX or 100BASE-TX) can have either an MII attachment or an
RJ-45 (or SC) attachment, but not both. The MII and RJ-45 (or SC) receptacles represent two physical
connection options for one FE interface.
Warning
Because invisible radiation may be emitted from the aperture of the port when no fiber cable is
connected, avoid exposure to radiation and do not stare into open apertures.
Warning
Class 1 LED product.
2-38
FAST ETHERNET
H9784
Figure 20

MII cable
ER
H9785
K
II
LIN
FAST ETHERNET
FIB
FAST ETHERNET
K
II
LIN
ER
Connecting MII or SC Cables (FEIP2-DSW-2FX Shown, Horizontal Orientation)
FIB
Figure 21
or
Simplex (2)
To repeater
To transceiver,
repeater, or DTE
Step 2
Caution
Duplex (1)
To repeater
For the 100BASE-TX RJ-45 connections, attach the ferrite bead to the RJ-45 cable (at either end), as
shown in .
The ferrite bead prevents electromagnetic interference (EMI) from affecting the 100BASE-TX-equipped
system and is a required component for proper system operation.
Figure 22
Attaching the Ferrite Bead around the RJ-45 Cable
Ferrite bead
Caution
RJ-45 cable
with ferrite bead
H4202
Chapter 2
To prevent problems on your FEIP2-DSW and network, do not simultaneously connect RJ-45 (or SC)
and MII cables to one FE interface. On a single FE interface, only one network connection can be used
at one time. Only connect cables that comply with EIA/TIA-568 standards. (Refer to Table 5 and
Table 6, on page 33, for cable recommendations and specifications.)
Step 3
Attach the network end of your RJ-45 (or SC) or MII cable to your 100BASE-T transceiver, switch,
hub, repeater, DTE, or other external 100BASE-T equipment.
Step 4
Repeat Steps 1 through 3 for the second FE interface as required.

This completes the FEIP2-DSW cable installation.
2-39
Chapter 2
Using LEDs to Check FEIP2-DSW Status

The FEIP2-DSW has four status LEDs on its faceplate that indicate status on each FE port. (See .)
LEDs (Partial Faceplate View of FEIP2-DSW-2TX)
H2941
Figure 23
After you connect cables, observe the LED states and the console display as the router initializes. When
the system has reinitialized all interfaces, the enabled LED on the FEIP2-DSW should go on. (For
complete descriptions of the FEIP2-DSW LEDs, refer to the FEIP2-DSW LEDs section on page 41.)
The console screen will also display a message as the system discovers each interface during its
reinitialization. After system initialization, the enabled LED goes on to indicate that the FEIP2-DSW is
enabled for operation.
The following conditions must be met before the FEIP2-DSW is enabled:
The interface processor is correctly connected to the backplane and receiving power.
The system bus recognizes the interface processor.
A valid version of microcode is loaded and running.
If any of these conditions is not met, the enabled LED does not go on.
Verify that the FEIP2-DSW is connected correctly as follows:
Step 1
While the system reinitializes each interface, observe the console display messages and verify that the
system discovers the FEIP2-DSW. The system should recognize the FEIP2-DSW interfaces but leaves
them configured as down.
Step 2
When the reinitialization is complete, verify that the enabled LED on each FEIP2-DSW FE interface is
on and remains on. If the LED does stay on, proceed to Step 5. If the enabled LED does not stay on,
proceed to the next step.
Step 3
If an enabled LED fails to go on, suspect the that the FEIP2-DSW board connector is not fully seated in
the backplane. Loosen the captive installation screws, then firmly push the top ejector down while
pushing the bottom ejector up until both are parallel to the FEIP2-DSW faceplate. Tighten the captive
installation screws. After the system reinitializes the interfaces, the enabled LED on the FEIP2-DSW
should go on. If the enabled LED goes on, proceed to Step 5. If the enabled LED does not go on,
proceed to the next step.
Step 4
If an enabled LED still fails to go on, remove the FEIP2-DSW and try installing it in another available
interface processor slot.
If the enabled LED goes on when the FEIP2-DSW is installed in the new slot, suspect a failed backplane
port in the original interface processor slot.
If the enabled LED still fails to go on, but other LEDs on the FEIP2-DSW go on to indicate activity,
proceed to Step 5 to resume the installation checkout and suspect that the enabled LED on the
FEIP2-DSW has failed.
2-40
Chapter 2

If no LEDs on the FEIP2-DSW go on, suspect that the FEIP2-DSW is faulty.

If the enabled LED still does not go on, do not proceed with the installation. Contact a service
representative to report the faulty equipment and obtain further instructions.
Step 5
Use the show interfaces or show controllers cbus command to verify the status of the FEIP2-DSW
interfaces. (If the interfaces are not configured, you must configure them.
If an error message displays on the console terminal, refer to the appropriate reference publication for
error message definitions. If you experience other problems that you are unable to solve, contact a
service representative for assistance.
FEIP2-DSW LEDs
The FEIP2-DSW contains the enabled LED and a bank of three status LEDs for each of the two FE
interfaces (located between the two receptacles on each FE interfacesee ). After system initialization,
the enabled LED goes on to indicate that the FEIP2-DSW has been enabled for operation.
LEDs on a Fast Ethernet Interface
(Partial Horizontal Faceplate View of FEIP2-DSW-2TX)
H2941
Figure 24
The following conditions must be met before the enabled LED goes on:
The FEIP2-DSW is correctly connected and receiving power
The FEIP2-DSW card contains a valid microcode version that has been downloaded successfully
The bus recognizes the FEIP2-DSW.
If any of these conditions is not met, or if the initialization fails for other reasons, the enabled LED does
not go on.
Following are the three status LEDs and an explanation of what each indicates:
MIIOn when the MII port is selected as the active port by the controller.
LinkWhen the RJ-45 or SC port is active, this LED is on when the FE interface is receiving a
carrier signal from the network. When the MII port is active, this LED is an indication of network
activity, and it flickers on and off proportionally to this activity.
RJ45 (or FIBER on FEIP2-DSW-2FX)On when the RJ-45 (or FIBER) port is selected as the active
port by the controller.
FEIP2-DSW Receptacles, Cables, and Pinouts

The two interface receptacles on each Fast Ethernet interface are a single MII, 40-pin, D-shell type
receptacle, and a single RJ-45 receptacle (or SC-type for FEIP2-DSW-2FX optical-fiber connections).
(See the FEIP2-DSW-2TX in and the FEIP2-DSW-2FX in .)
2-41
Chapter 2
You can use either one receptacle or the other; only one receptacle can be used at one time. Each
connection supports IEEE 802.3u interfaces compliant with the 100BASE-X and 100BASE-T standards.
The RJ-45 connection does not require an external transceiver. The MII connection requires an external
physical sublayer (PHY) and an external transceiver. Cisco Systems does not supply Category 5 UTP
RJ-45 cables; these cables are available commercially.
Caution
receptacles on a single FEIP2-DSW, FE interface. Each FE interface (100BASE-FX or 100BASE-TX)
Single FEIP2-DSW-2TX Fast Ethernet Interface (Horizontal Faceplate View)
FAST ETHERNET
45
H4495
RJ
NK
MI
LI
EN
AB
LE
Figure 25
Single FEIP2-DSW-2FX Fast Ethernet Interface (Horizontal Faceplate View)
TX
RX
H6014
NK
BE
FI
LI
FAST ETHERNET
MI
EN
AB
LE
Figure 26
The RJ-45 connection does not require an external transceiver. The MII connection requires an external
physical sublayer (PHY) and an external transceiver. shows the RJ-45 cable connectors. RJ-45 cables
are not available from Cisco Systems, but are available from commercial cable vendors. Table 7 lists the
pinouts and signals for the RJ-45 connectors.
RJ-45 Connections, Plug and Receptacle (FEIP2-DSW-2TX)
87654321
RJ-45 connector
Warning
H2936
Figure 27
The ports labeled Ethernet, 10BaseT, Token Ring, Console, and AUX are safety extra-low
voltage (SELV) circuits. SELV circuits should only be connected to other SELV circuits. Because the
BRI circuits are treated like telephone-network voltage, avoid connecting the SELV circuit to the
telephone network voltage (TNV) circuits.
Table 7 lists the pinouts and signals for the FEIP2-DSW-2TXs RJ-45 connectors.
2-42

Table 7
Pin
Description
Receive Data + (RxD+)
RxD
Transmit Data + (TxD+)
TxD
Referring to the RJ-45 pinout in Table 7, proper common-mode line terminations should be used for the
unused Category 5, UTP cable pairs 4/5 and 7/8. Common-mode termination reduces the contributions
to electromagnetic interference (EMI) and susceptibility to common-mode sources. Wire pairs 4/5 and
7/8 are actively terminated in the RJ-45, 100BASE-TX port circuitry in the FEIP2-DSW-2TX.
Figure 28
Straight-Through Cable Pinout, RJ-45 Connection to a Hub or Repeater (FEIP2-DSW-2TX)
FEIP
Hub or repeater
5 TxD+
5 RxD+
6 TxD
6 RxD
3 RxD+
3 TxD+
4 RxD
4 TxD
Figure 29
H3137
Note
RJ-45 Connector Pinout (FEIP2-DSW-2TX)
Crossover Cable Pinout, RJ-45 Connections Between Hubs and Repeaters

(FEIP2-DSW-2TX)
ub or LAN switch
Hub or LAN switch
3 TxD+
3 TxD+
6 TxD
6 TxD
1 RxD+
1 RxD+
2 RxD
2 RxD
H3138
Chapter 2
2-43
Chapter 2
2-44
C H A P T E R
System Quick Start

This chapter provides illustrated text to help you quickly perform the following tasks:
Install the Hardware, page 3-3
Connect the RSP, page 3-20
Start and Configure the System, page 3-22
Install Field Replaceable Units (FRUs), page 3-27
3-1
Chapter 3
Figure 3-1
ADD FIGURE CALLOUT HERE
POWER
A
POWER
B
74547
NORMAL
3-2
System Quick Start
Chapter 3
System Quick Start

Install the Hardware

Figure 3-2
Blower module
Cable-management
bracket
NO
RM
NO
AL
RM
AL
EN
EJE
Card cage and

processor
modules
EJE
CT
SLO SLO
T0 T1
VE
CP
RE
AU
NS
HA
SE
/M
CP
LT
RE
AU
X.
OLE
VE
CO
NS
AS
TE
HA
SE
AB
LE
LT
EN
X.
OLE
CO
TE
Interface
processor slot
numbering
scheme
AS
CT
SLA MA
S
VE TE
R
SLA
/M
LE
SLO SLO
T0 T1
SLA MAS
VE TE
R
SLA
AB
Air intake vent

AC
OK
FAN
OK
OUTPUT
FAIL
AC
OK
Power supplies
FAN
OK
OUTPUT
FAIL
POWER
POWER
B
I
I
0
0
74555
Chassis
grounding
receptacles
The Cisco 7513 has 13 slots: interface processor slots 0 through 5, Route Switch Processor slots 6 and
7, and interface processor slots 8 through 12.
The Cisco 7576 router is two Cisco 7500 series routers configured on a single split backplane, with 13
slots. Router A uses interface processor slots 0 through 5 with a Route Switch Processor in slot 6. Router
B uses interface processor slots 8 through 12 with a Route Switch Processor in slot 7.
The Cisco 7513 and Cisco 7576 routers have bays for up to two AC-input or DC-input power supplies.
Each chassis will operate with one power supply, but a second power supply allows load sharing and
increased system availability.
Note
The Cisco 7576 does not support the high system availability (HSA) feature. The RSP in slot 6 is
automatically the system master for router A and the RSP in slot 7 is automatically the system master
for router B.
3-3
Chapter 3
System Quick Start
Note
If you are only configuring one of the two Cisco 7576 internal routers, configure router A instead of
router B. Install an RSP in slot 6, and interface processors in slots 0 through 5.
Packing List
1 Cisco 7513 or 7576 router
1 Route Switch Processor (RSP)
Y-adapter cables, 1 auxiliary and 1 console
1 AC power supply
1 AC power supply cable
1 Power cord
1 Anti-static wrist strap and documentation
Prepare to Install the Router

Note
Warning
For detailed hardware installation instructions and safety guidelines, refer to the Cisco 7500 Series
Router Installation and Configuration Guide, Site Preparation and Safety Guide, and the Cisco 7500
Regulatory Compliance and Safety Guide.
Only trained and qualified personnel should install, replace, or service this equipment.
Step 1
Lift the router safely out of the packing container.
Step 2
Ensure the power service at the site is suitable for the router you are installing.
Step 3
Check the packing slip to ensure that all the proper components are present.
Step 4
Confirm that you have the required tools and parts:

For rack-mounting (optional):
Number 1 and Number 2 Phillips screwdrivers
1/4-inch and 3/16-inch flat-blade screwdrivers
Tape measure
Level (optional)
Two mounting brackets (identical), each with an attached spanner bar
Two chassis ears with captive grommets (identical)
Four M4 x 10-mm Phillips flat-head screws to secure the ears to the chassis
Twelve 10-32 x 5/8-inch LG Phillips pan-head screws with integral square cone washers
3-4
Chapter 3
System Quick Start

For cable-management brackets:
Number 1 Phillips screwdriver
Two cable-management brackets
Six M3 x 8-mm Phillips pan-head screws
For interface modules:
Number 1 Phillips or 3/16-inch flat-blade screwdriver
For DC-Input Power Supply:
Twin-lead, 10-AWG cable terminal block connection
Single 8-AWG wire for the ground connection
3/16-inch flat-blade screwdriver
8-mm nut driver
Install the Router on a Bench or Tabletop

POWER
POWER
74562
Figure 3-3
3-5
Chapter 3
System Quick Start
Note
Caution
To rack-mount the router, refer to the Rack-Mount the Router (Recommended) section on page 3-7.
Two people are required to perform this step. Avoid sudden twists or moves to prevent injury.
Step 1
With a person positioned at either side of the chassis, grasp the bottom edge of the chassis with one hand
near the front and the other near the back. Slowly lift the chassis in unison. Place the chassis on a bench
or tabletop where the air intake vent on the front of the chassis is not drawing in exhaust air from other
equipment.
Warning
When lifting the router, do not lift by grasping the handle of the blower module, nor should you grasp
the air intake grill
Step 2
Ensure that you have at least 2 or 3 feet (0.6 to .09 m) of clearance around the rear of the chassis to install
power supplies and perform maintenance on the chassis.
Step 3
Proceed to the lnstall Interface Processors, Fillers, VIPs, or RSPs section on page 3-14.
3-6
Chapter 3
System Quick Start

Rack-Mount the Router (Recommended)

Figure 3-4
Chassis ear (cutaway of frame post

to enable view of chassis ear)
M4 x 10-mm long
Phillips flat-head
screws (to attach
ears to chassis)
10-32 x 5/8 in. long

Phillips pan-head screws
with integral square cone
washers (for mounting
brackets and chassis
ears to rack posts)
Bracket (2)
POWER
A
POWER
74546
3-7
Chapter 3
System Quick Start
To rack-mount the Cisco 7513 or Cisco 7576 router, you will perform the following steps:
Step 1
Mount the brackets to the rack posts.
Step 2
Secure the spanner bars.
Step 3
Attach the chassis ears.
Step 4
Mount the chassis.
3-8
Chapter 3
System Quick Start

Mount Brackets to the Rack Posts

Figure 3-5
Rack post
Flange
id
ds
74554
lde
ie
Sh
3-9
Chapter 3
System Quick Start
Note
The distance between the inner edges of the left and right rack-mounting posts must be at least 17.72
inches (45.088 cm), and the distance between the holes in the mounting posts must be 18.31 inches (46.5
cm) (+ .063 inches or .16 cm).
Step 1
Place the bracket on the inner side of the rack post, with the flanged front edge of the bracket in front of
the rack post.
Step 2
Align the mounting holes in the bracket with those in the rack post.
Step 3
Support the bracket with one hand, and use the other hand to insert a 10-32 x 5/8-inch LG Phillips
pan-head screw through the bottom mounting hole on the front of the bracket and into the rack post.
Step 4
Secure the top of the bracket to the rack with two pan-head screws. Finger-tighten the screws.
Step 5
Push the brackets as far apart as possible before using a Number 2 Phillips screwdriver to tighten the
screws.
Step 6
Adjust the brackets if the distance between them is less than 17.5 inches (45.45 cm).
Step 7
Repeat Step 3 through Step 6 for the remaining bracket. Use a level or tape measure to ensure that the
two brackets are level in the rack.
3-10
Chapter 3
System Quick Start

Secure the Spacers

Figure 3-6
A
C
74556
Step 1
Loosen the 10-32 x 5/8-inch LG Phillips pan-head screw at the end of the ledge of the right-side bracket.
This screw is the anchor for the spanner bar.
Step 2
Remove the tape that secures the spanner bar on the left bracket, and swing the bar down (see A) over
the anchor screw on the opposite bracket (see B).
Step 3
If the spanner bar does not reach the opposite bracket, loosen the pan-head screws to allow more play
between the brackets, and adjust brackets as needed.
Step 4
Repeat Step 1 through Step 3 to fasten the remaining spanner bar to its anchor screw. (See C.)
Step 5
Push the brackets as far apart as possible before tightening the screws.
Step 6
Use a Number 2 Phillips screwdriver to tighten the six pan-head screws that secure the brackets to the
rack-mounting posts, and the two anchor screws that secure the spanner bars.
Step 7
Adjust the brackets if the distance between them is less than 17.5 inches (44.45 cm).
3-11
Chapter 3
System Quick Start
Attach the Chassis Ears

Figure 3-7
Center-mount position
Flush-mount position
POWER
A
POWER
74545
Step 1
Step 2
Position the ears on the chassis as follows:
To flush-mount the chassis, place each ear so that the mounting strips are flush with the end of the
chassis, and align the mounting holes in the ear with those in the chassis.
To center-mount the chassis, place each ear with the mounting strips away from the end of the
chassis, and align the mounting holes in the ear with those in the chassis.
Use two M4 x 10-mm LG Phillips flat-head screws to secure each ear to the chassis.
3-12
Chapter 3
System Quick Start

Mount the Chassis in the Rack

POWER
POWER
74549
Figure 3-8
Caution
Two people are required to perform this step.
Step 1
With a person positioned at either side of the chassis, grasp the bottom edge of the chassis with one hand
near the front and the other near the back.
Step 2
Slowly lift the chassis in unison. Avoid sudden twists or moves to prevent injury.
Step 3
With the chassis positioned so the front is closest to the rack, insert the front of the chassis into the rack
between the brackets, and then slowly lower the chassis until it rests on the two bracket ledges.
3-13
Chapter 3
System Quick Start
Step 4
Slide the chassis back into the rack along the ledges until the ears meet the front mounting posts on both
sides of the rack.
Step 5
Secure each ear to the rack-mounting post with two 10-32 x 5/8-inch LG Phillips pan-head screws.
lnstall Interface Processors, Fillers, VIPs, or RSPs

Figure 3-9
Bottom ejector lever
Captive
installation
screw
Card
carrier
guide
Card
slot
STOP!
on contact
3-14
74552
Chapter 3
System Quick Start

The Route Switch Processor (RSP) comes uninstalled with your Cisco 7513 or 7576 router, but is a
required system component. Install the RSP2, RSP4, or RSP8 in either slot 6 or slot 7, and install
interface processors (optional) in any of the eleven interface processor slots, which are numbered 0
through 5, and 8 through 12, from left to right when viewing the chassis from the rear.
Step 1
Hold the interface processor, filler, VIP, or RSP with one hand, and place your other hand under the
carrier to support the card and guide it into the slot. Avoid touching the card.
Step 2
Place the interface processor, filler, VIP, or RSP in the slot and align the guide on the carrier with the
groove in the slot.
Step 3
Carefully slide the interface processor, filler, VIP, or RSP into the slot until the faceplate makes contact
with the ejector levers.
Step 4
Use the thumb and forefinger of each hand to push the ejector lever flat against the interface processor,
filler, VIP, or RSP.
Step 5
Use a screwdriver to tighten the captive installation screws.
Step 6
Repeat Step 1 through Step 5 to install any additional interface processors, fillers, VIPs, or RSPs.
Step 7
To check an RSP installation, refer to the Check the RSP Installation section on page 3-32, and refer
to the Check the Interface Processor or VIP Installation section on page 3-33 to check the interface
processor or VIP installation.
3-15
Chapter 3
Attach the Cable-Management Bracket

Figure 3-10 ADD FIGURE CALLOUT HERE
Blower
module
Loosen
screws (2)
Bracket
74563
Card cage
3-16
System Quick Start
Chapter 3
System Quick Start

Step 1
Locate the two slotted screws between the blower module and the card cage opening at the interface
processor end of the router.
Step 2
Use a flat-blade screwdriver to loosen the screws.
Step 3
Place the bracket over the screws.
Step 4
Tighten the screws.
Step 5
Route the cables to and through the cable-management bracket.
Note
If you are using very thin cables that slip through the bracket, insert cable ties through the holes in the
bracket and wrap them around the cables to secure them.
It may be necessary to bundle longer cables to avoid tangling them. Do not block the power supply or
chassis intake air vents with cables. Cables should not interfere with the removal and installation of the
blower module.
Install Power Supplies in the Router

Figure 3-11 Power Supply
B
DC
FAN OUTPUT
OK
OK
FAIL
AC
OK
FAN OUTPUT
OK
AC
FAIL
OK
FAN OUTPUT
OK
FAIL
POWER
A
POWER
74557
Captive screws
Note
The Cisco 7513 and the Cisco 7576 routers are shipped with the power supplies removed. Each chassis
comes with one power supply as standard equipment; a second power supply is optional equipment. The
power supplies rest on the floor of the chassis under the card cage assembly.
This procedure applies to AC-input and DC-input power supplies, with differences clearly noted. Do not
mix AC-input and DC-input power supplies in the same chassis. Install the first power supply in the
lower power supply bay and the second, if any, in the upper bay. In systems with dual power supplies
and separate available power sources, connect each power supply to separate input linesthe second
power source will likely be available during a failure.
3-17
Chapter 3
System Quick Start
For AC-input power supplies, confirm that the power on the power supply is off.
Step 1
For DC-input power supplies, turn off the circuit breaker to which you will connect power, and tape the
breaker switch to the off position.
Hold the power supply by the handle and place your other hand underneath it.
Step 2
Use two hands to remove and install power supplies.
Caution
Step 3
Place the power supply inside the bay, and align it to go straight into the bay.
Step 4
Push the power supply back into the bay until its front panel is flush with the chassis rear panel.
Step 5
Use a screwdriver to tighten the captive installation screw on the top of the power supply.
For AC-input power supplies, proceed to the Connect AC-Input Power Supply section on page 3-18.
For DC-input power supplies, proceed to the Connect DC-Input Power Supply section on page 3-19.
Connect AC-Input Power Supply

Cable-retention clip
AC
OK
FAN
OK
OUTPUT
FAIL
AC
OK
FAN
OK
OUTPUT
FAIL
POWER
B
I
I
74550
Captive screws
Warning
The system power switch on the power supply should be off.
3-18
Chapter 3
System Quick Start

Step 1
For AC-input power supplies, push the cable retention clip away from the power receptacle and plug in
the power cable.
Step 2
Push the cable retention clip until it snaps into place around the cable connector.
Step 3
Reconnect the power cable at the power source, remove the tape on the breaker switch. Do not turn on
the breaker or power to the power supply.
A power supply blank must remain in any empty power supply bay.
Note
Repeat Step 1 through Step 3 for the second power supply, if present.
Step 4
Do not mix AC-input and DC-input power supplies in the same chassis.
Note
Connect DC-Input Power Supply

DC-input power supply

Remove
DC
FAN OUTPUT
OK
OK
Terminal
block
cover
FAIL

with the terminal block
cover removed
DC-input
cable (8-AWG)
Power leads
attached to
terminal block
(+) Positive
() Negative
( ) Ground
DC
FAN OUTPUT
OK
OK
FAIL
Conduit
bracket
Remove
I
Warning
74551
Captive
installation
screw
Step 1
Use a screwdriver to loosen and remove the terminal block cover screws.
Step 2
Lift and remove the terminal block cover.
Step 3
Route the DC-input power cable from the power source through the conduit bracket on the power supply.
Allow sufficient slack in the cable.
3-19
Chapter 3
System Quick Start
Connect the RSP
Step 4
Attach and tighten the conduit to the conduit bracket.
Note
The proper wiring sequence is ground to ground, positive to positive (line to L), negative to
negative (neutral to N). The ground wire should always be connected first and disconnected last.
Step 5
Attach the ground wire to the ground terminals using the 8-mm nut driver.
Step 6
Check the power supplys wiring and color code to verify that it matches the wiring and color code at
the DC source.
Warning
Incorrect wiring could create a dangerous shock hazard and could damage the power supply, power
source, and chassis components.
Step 7
Replace the terminal block cover.
Step 8
Reconnect the power cable at the power source.
Step 9
Repeat Step 1 through Step 8 for a second power supply, if present.
Connect the RSP

DB-25 female
Modem
Auxiliary
port
Console
port
DB-25 male
RSP
3-20
74544
Console terminal
Chapter 3
System Quick Start

Connect the RSP
Connect the Console Port

The system console port on the RSP is a DB-25 receptacle DCE port for connecting a data terminal,
which allows you to configure and manage the system. The console port is labeled Console.
Step 1
Connect the console cable from the terminal to the console port on the RSP.
Step 2
Check your terminals documentation to determine the baud rate of the terminal you will be using.
Note
Step 3
The baud rate of the terminal you are using must match the default baud rate (9600 baud).
Set up the terminal as follows: 9600 baud, 8 data bits, no parity, and 2 stop bits (9600, 8N2).
Connect the Auxiliary Port

The auxiliary port on the RSP is an ETA/TIA DTE DB-25 plug to which you can attach external
equipment in order to access the router from the network. The port is located next to the console port on
the RSP and is labeled AUX.
Step 1
Connect the cable from the auxiliary device to the auxiliary port on the RSP.
Step 2
Check your terminals documentation to determine the baud rate of the terminal.
Note
Step 3
The baud rate of the terminal must match the default baud rate (9600 baud).
Set up the terminal as follows: 9600 baud, 8 data bits, no parity, and 2 stop bits (9600, 8N2).
Connect the Console and the Auxiliary Y-Cables

CONSOLE
DB-25 male
Console connectors
to console ports on two
RSPs in RSP slots
To console terminal
CONSOLE
DB-25 male
74543
DB-25 female
3-21
Chapter 3
System Quick Start
Start and Configure the System
The console and auxiliary Y-cables allow you to simultaneously connect the console or auxiliary ports
on two RSP2s, RSP4s, or RSP8s to a single console terminal or external auxiliary device. These are
configured as system master and slave in RSP slots 6 and 7 in the Cisco 7513.
Step 1
Connect the DB-25 female end of the Y-cable to the console terminal device.
Step 2
Connect one DB-25 male end of the Y-cable to an RSP or other external auxiliary device.
Step 3
Repeat Step 2 for the other RSP or other external device.
AUXILIARY
DB-25 female
Auxiliary connectors
to auxiliary ports on two
RSPs in RSP slots
To external
auxiliary equipment
AUXILIARY
DB-25 female
74542
DB-25 male
Step 1
Connect the DB-25 male end of the Y-cable to the external auxiliary equipment.
Step 2
Connect one DB-25 female end of the Y-cable to auxiliary ports on an RSP in an RSP slot.
Step 3
Repeat Step 2 for the auxiliary ports on a second RSP in an RSP slot.
Step 4
Connect the interface processors or VIPs to the external network. Refer to the appropriate processor
module manual, such as the Route Switch Processor (RSP4/4+) Installation and Configuration Guide.

Step 1
Step 2
Check the following components to make sure they are secure:
Each interface processor is inserted all the way into its slot, and captive installation screws are
tightened.
All interface cable connections are secured, and any Flash memory cards are secured in their PC
slots.
The system power cable is connected.
Check the console terminal to make sure it is connected to the console port and turned on.
Turn the system power switch to the on (|) position. The green AC (or DC) OK and fan OK LEDs on
each power supply should go on. After a few seconds, the red output fail LED will turn OFF.
3-22
Chapter 3
System Quick Start

Step 3
Listen for the system blower; you should immediately hear it operating.
Step 4
Observe the normal LED indicator on the RSP. If this indicator is not on after system initialization, an
error has occurred. If necessary, refer to Appendix A in the Cisco 7500 Series Installation and
Configuration Guide.
Step 5
Wait until the system boot is complete before attempting to verify the status of interface processor
indicators. During the boot process, the LED indicators on most of the interfaces go on and off in
irregular sequence.
Step 6
Observe the LED indicators on the interface processors in your system. When the system boot is
complete (a few seconds), the RSP begins to initialize the interface processors. During this initialization,
the indicators on each interface processor behave differently (most flash on and off).
The enabled LED on each interface processor goes on when initialization has been completed, and the
console screen displays a script and system banner similar to the following:
GS Software (RSP-K ), Version 11.1(8)CA
Copyright (c) 1986-1995 by Cisco Systems, Inc.
This RSP2 is system master
Other RSP2 is not plugged in
Compiled Wed 10-May-95 11:06
Step 7
Observe the system startup banner. When you start up the router for the first time, the system
automatically enters the setup command facility, which determines which interfaces are installed and
prompts you for configuration information for each one. On the console terminal, after the system
displays the system banner and hardware configuration, you will see the following System Configuration
Dialog prompt:
--- System Configuration Dialog --At any point you may enter a questions mark `?' for help.
Refer to the `Getting Started' Guide for additional help.
Default settings are in square brackets `[]'. continue with
configuration dialog? [yes]:
Start a Basic Configuration

Many privileged-level EXEC commands are used to set operating parameters. To enter the
privileged-level:
Step 1
Enter the enable command at the EXEC prompt (>), and then enter a privileged-level password, as
follows:
Router> enable
Password:
Router#
Step 2
Enter the configure terminal command to enter configuration mode:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Step 3
Enter the config-register value configuration command, where value is a hexadecimal number preceded
by 0x, as in the following example:
Router(config)# config-register 0x010F
3-23
Chapter 3
System Quick Start
Step 4
Press Ctrl-Z to exit configuration mode.
Step 5
Save the new settings to NVRAM. Enter the copy running-config startup-config command.
Note
Step 6
The new settings do not take effect until the system software is reloaded by rebooting the router.
Enter the show version command to view the configuration register value currently in effect. The value
is displayed on the last line of the screen display:
Configuration register is 0x141 (will be 0x101 at next reload)
Step 7
Reboot the router, and then perform a basic configuration using:
AutoInstall (proceed to Step 1)
Setup facility (proceed to the Perform a Basic Configuration Using Setup section on page 3-24)
Note
Configuration register changes take effect only when the system reloads, such as when you issue
a reload command from the console.
Configure Using AutoInstall

Step 1
Connect to the network using a serial (WAN) cable to the channel service unit/data service unit
(CSU/DSU).
Step 2
Contact your system administrator to verify that the TCP/IP host on your network is preconfigured.
Step 3
Step 4
At the # prompt, enter the copy running-config startup-config command to save the configuration to
NVRAM as follows:
Hostname# copy running-config startup-config
This completes the procedure for performing a basic configuration using AutoInstall.
Perform a Basic Configuration Using Setup

Note
The routers serial (WAN) cable should not be connected to the CSU/DSU unless you are planning to
use AutoInstall. If you are using the console Y-cable that shipped with your router, use either of the two
DB-25 male plug ends of the Y-cable.
3-24
Chapter 3
System Quick Start

Step 1
Select the protocols supported on your interfaces. For Internet Protocol (IP)-only installations, accept
the default values. A typical minimal configuration using IP, IPX, and AppleTalk follows:
Configuring global parameters:
Enter host name [Router]: Router
Step 2
Enter the enable secret password and the enable password when the following is displayed:
The enable secret is a one-way cryptographic secret used instead of the enable password
when it exists.
Enter enable secret: barney
The enable password is used when there is no enable secret and when using older software
and some boot images.
Enter enable password: betty
Step 3
Enter yes or no to accept or refuse SNMP management:

Configure SNMP Network Management? [yes]: yes
Community string [public]:
Step 4
Enter no to refuse to enable CLNS:

Configure CLNS? [no]: no
Step 5
Enter no to refuse to enable routing on AppleTalk and IPX:

Configure AppleTalk? [no]: no
Multizone networks? [no]: no
Configure IPX? [no]: no
Step 6
Enter no to refuse to enable Vines, XNS, DECnet, or bridging:

Configure
Configure
Configure
Configure
Step 7
Vines? [no]: no
XNS? [no]: no
DECnet? [no]: no
bridging? [no]: no
Enter yes or press Return to configure IP, and then select an interior routing protocol for IP, if you are
using IP routing:
Configure IP? [yes]: yes
Configure IGRP routing? [yes]: yes
Your IGRP autonomous system number [1]: 15
Step 8
NVRAM as follows:
Note
Consult your network administrator to obtain network addresses and subnet mask information.
3-25
Chapter 3
System Quick Start
Configure an Ethernet Interface

Step 1
To configure your system for an Ethernet LAN, respond to the prompts as follows, using your own IP
address and subnet mask information:
Configuring interface parameters:
Configuring interface Ethernet0/0:
Is this interface in use? [no]: yes
Configure IP on this interface? [no]: yes
IP address for this interface: 1.1.1.10
Number of bits in subnet field [0]:
Class A network is 1.0.0.0, 0 subnet bits; mask is 255.0.0.0
Step 2
Enter no to refuse to enable IPX on this interface, using the IPX network number:
Configure IPX on this interface? [no]: no
Step 3
Enter no to refuse to enable AppleTalk on this interface:

Configure AppleTalk on this interface? [no]: no
Step 4
Step 5
NVRAM as follows:
Your Cisco 7507/7513 router is now minimally configured and ready to use. If you want to modify the
parameters after the initial configuration, use the setup command. To perform more complex
configurations, use the configure command. For more information on additional interface configuration
and information on more specific system configurations, refer to the Cisco 7500 Series Installation and
3-26
Chapter 3
System Quick Start

Install Field Replaceable Units (FRUs)

Flash Memory Cards
NO
RM
AL
SL SL
OT OT
0 1
S L MA
AV S T
ER
E
NO
RM
AL
SL S L
OT OT
0
SL
NO
M
AV AST
ER
E
RM
AL
SL SL
OT OT
0 1
M
AV AST
E
E
SL
3-27
Chapter 3
System Quick Start
A Flash memory card that ships with your Cisco 7513 or Cisco 7576 contains the Cisco IOS software
image to boot your router. You do not need to format it.
The RSP has two PC Card slotsslot 0 and slot 1into which you can install a Flash memory card. In
the RSP2, RSP4, and RSP8, the orientation is vertical. PC Card slot 0 is on the left and slot 1 is on the
right (as shown).
Note
A Flash memory card can be inserted and removed with the system power on. Both PC Card slots can
be used at the same time.
Step 1
To eject the card, press the appropriate eject button until the card is free of the connector at the back of
the slot (see C).
Step 2
Remove the card from the slot and place it in an antistatic bag to protect it.
Step 3
Face the front panel of the RSP, and hold the Flash memory card with the connector end of the card
toward the slot (see A).
Step 4
The label should face right.
Note
Step 5
The Flash memory card is keyed and cannot be seated the wrong way. The eject button will not
pop out if the card is not properly inserted.
Insert the card into the appropriate slot until the card completely seats in the connector at the back of the
slot and the eject button pops out toward you (see B).
Note
The card does not insert all the way inside the RSP; a portion of the card remains outside of the
slot. Do not attempt to force the card past this point.
Format a Flash Memory Card

Flash memory cards shipped as spare parts must be formatted. Use only Intel Series 2+ Flash memory
cards.
Step 1
Enter format slot0: (or format slot1:) to format the Flash memory card, as follows:
Router# format slot0:
Step 2
At the erase all sectors prompt, press Enter to proceed.

All sectors will be erased, proceed? [confirm]
Step 3
At the volume ID prompt, enter the ID name:

Enter volume id (up to 30 characters): MyNewCard
Formatting sector 1
Format device slot0 completed
Router#
3-28
Chapter 3
System Quick Start

Copy Files to Flash Memory

To upgrade to a new Cisco IOS image, copy the image file to Flash memory. Upgrade images one at a
time; do not delete all known good images at one time. You cannot copy an image while the system is
running from Flash memory.
Use the command copy tftp:filename [bootflash | slot0 | slot1]: filename for the copy procedure, where
tftp:filename is the source of the file and [bootflash | slot0 | slot1]: filename is the destination in
bootflash memory or on either of the Flash memory cards.
An example of the copy tftp:filename command follows for a file in the Flash memory card in PC Card
slot 0:
Router# copy tftp:myfile1 slot0:myfile1
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet1/0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#
Make a Flash Memory Card Image Bootable

Note
Step 1
In this example, the filename is new.image, and the Flash memory card is located in slot 0.
Enter the configure terminal command at the enable prompt, as follows:

Step 2
Enter the no boot system command, as follows.

Router(config)# no boot system
Step 3
Enter the boot system flash slot0:new.image command, as follows:

Router(config)# boot system flash slot0:new.image
Step 4
Enter the config-register 0x2102 command to enable loading an image from Flash memory:
Router(config)# config-register 0x2102
Step 5
Step 6
Enter the copy running-config startup-config command to save the configuration to NVRAM as
follows:
Step 7
Enter the reload command. When the system reloads, it will boot the image new.image from the Flash
memory card in slot 0.
Router# reload
3-29
Chapter 3
System Quick Start
Enable Booting from Flash Memory

To enable booting from Flash memory, set configuration register bits 3, 2, 1, and 0 to a value between 2
and 15 in conjunction with the boot system flash device:filename configuration command, where device
is bootflash:, slot0:, or slot1:, and filename is the name of the file from which you want to boot the
system. In the following example, the Flash memory card is in slot 0.
Step 1
Enter the configure terminal command at the enable prompt, as follows:

Step 2
At the prompt, enter configuration commands, one per line.

Enter configuration commands, one per line.
Step 3
Press Ctrl-Z to exit configuration.
Step 4
Enter the boot system flash bootflash:slot0: filename command, as follows:

Router(config)# boot system flash blootflash:slot0:filename
Step 5
Enter the config-register command with the value shown in the following example:
Router(config)# config-reg 0x0102
Ctrl-Z
Router#
Press Ctrl-Z to exit enable booting mode.
Prepare to Remove and Install an RSP

To remove and install an RSP, you will perform the following steps:
Copy the configuration file using a Trivial File Transfer Protocol (TFTP) server
Remove the RSP
Install the RSP
Connect to the RSP
Turn the system power back on, if it has been turned off
Retrieve the configuration file
3-30
Chapter 3
System Quick Start

Remove and Install an Interface Processor, Filler, VIP, or RSP

Captive
installation
screw
Card
carrier
guide
Card
slot
STOP!
on contact
74552
3-31
Chapter 3
System Quick Start
Note
Do not shut down the system power when removing an interface processor, VIP, or an RSP in a system
configured for HA. If you are removing an RSP and have only one RSP, shut down the system, but first
copy the configuration file to a TFTP server. See the Copy the Configuration File for an RSP section
on page 3-34. If you have a system using high system availability (HSA), shut down the system to
remove the master RSP, but leave power on if you remove only the slave RSP.
Step 1
Attach an ESD-preventive wrist strap between you and any unpainted chassis surface.
Step 2
If you have a VIP4 and are using HSA with an RSP2 as the slave processor, remove the RSP2 and wait
20-30 seconds.
Step 3
Disconnect all cables from the interface processor, VIP, or RSP port adapters; unless you are only
moving a carrier, then skip this step.
Step 4
Use a screwdriver to loosen the captive installation screws, as shown in A.
Step 5
Place your thumbs on both ejector levers and simultaneously pull them both outward, as shown in B.
Step 6
Grasp the interface processor, filler, VIP, or RSP handle with one hand and pull the carrier straight out
of the slot, keeping your other hand under the carrier to guide it.
Step 7
Store the interface processor, VIP, or RSP in an antistatic bag.
Step 8
If you have a VIP4 and are using HSA with an RSP2 as the slave processor, wait 20-30 seconds, and then
reinsert the RSP2.
Step 9
Repeat Step 2 through Step 8 to remove any additional interface processors, fillers, VIPs, or RSPs.
Step 10
Perform the steps in the lnstall Interface Processors, Fillers, VIPs, or RSPs section on page 3-14 to
install an interface processor, filler, VIP, or RSP.
Check the RSP Installation

Step 1
Check the RSP connections to make sure they are secure:
The RSP is inserted all the way into its slot, and both the captive installation screws are tightened.
The console terminal is turned on and is connected to the console port.
Step 2
Observe the RSP LEDs. While the system initializes, the CPU halt LED on the RSP stays on. It goes off
when the boot process is complete. As the RSP initializes each interface processor, the status LEDs on
each interface processor go on and off in irregular sequence.
Step 3
Verify that the console terminal displays the system banner and startup screen as the system restarts.
Note
Boot time is approximately 1 minute for systems with one RSP and approximately 1.5 minutes
for systems with two RSPs.
3-32
Chapter 3
System Quick Start

Step 4
Verify that all the enabled LEDs (on the interface processors) are on.
Step 5
In systems with a second RSP installed (and HSA or HA configured), use the show version command
to verify that the slave (or standby) RSP is recognized by the system.
Step 6
When you have verified all the conditions in Step 1 through Step 4 (or Step 5 if you have a second RSP
installed and want to use the HSA or HA features), the installation is complete.
If you replaced the RSP and saved your configuration file to a remote server before doing so, proceed to
the Retrieve the Configuration File for RSPs section on page 3-36.
An error condition exists if no LEDs go on at power up or after initialization, or if the boot error or CPU
halt LEDs go on and remain on. If this happens, see Appendix A in the Cisco 7500 Series Installation
and Configuration Guide.
Check the Interface Processor or VIP Installation

Note
Step 1
Step 2
When a new VIP is inserted or when a VIP is moved to a new slot, the system recognizes the new
interfaces, but leaves them in the shutdown state until you configure them. After the system reinitializes
all interfaces, the enabled LED on the port adapters and on all interface processors, VIPs, and RSPs
should go on, depending on your connections and configuration.
Observe the console display messages when the system reinitializes each interface as follows:
For a new interface processor or VIP, the system should recognize all new interfaces, but leave them
configured as down.
For a replaced interface processor or VIP, the system should recognize each interface and place it in
the same state (up or down) each was in when you removed the interface processor or VIP.
Verify that the enabled LED on each port adapter goes on and remains on.
If the enabled LED on a port adapter fails to go on, the interface processor or VIP may not be fully seated
in the backplane. Refer to Appendix A in the Cisco 7500 Series Installation and Configuration Guide.
Step 3
If the VIP is new, configure the new interfaces.
follows:
Router> enable
Password:
Router#
Use the configure command to configure the interface processor or VIP.
Refer to the appropriate configuration section of your port adapter documentation to configure the
port adapter.
3-33
Chapter 3
System Quick Start
Step 4
If the VIP is a replacement, use the show interfaces type slot/port adapter/port or show controllers
cbus command to verify the status of the interfaces.
If you replaced a VIP with a new VIP with a greater number of ports (for example, if you replaced a
single-port adapter VIP with a dual-port adapter VIP), the system will recognize the interfaces on the
previously configured port adapter, but will not recognize the additional port adapter interfaces. The new
interfaces will remain in the shutdown state until you configure them.
Step 5
When the interfaces are up, check the activity of each interface by observing the status LEDs, which are
described in the LED section of your port adapter documentation.
Copy the Configuration File for an RSP

Refer to the appropriate Cisco IOS software documentation for the configuration options available, and
for specific configuration instructions, as needed.
Before you copy (save) the running configuration to a TFTP file server, ensure the following:
Step 1
You have a connection to the router either with a console terminal connected to the RSP console port
or remotely through a Telnet session.
The router is connected to a network supporting a file server (remote host).
The remote host supports the TFTP application.
You have the interface processor address or name of the remote host available.
follows:
Router> enable
Password:
Router#
Step 2
Enter the ping command followed by the name or IP address of the remote server, and then press Return
to check the connection between the router and the remote host.
Step 3
Enter the show running-config command to display the currently running configuration on the terminal
and ensure that the configuration information is complete and correct. If it is not, use the configure
command to add or modify the existing configuration.
Step 4
Create a file on the TFTP server.
Note
Before you can save a file to a TFTP server, a file must first exist on the TFTP server. Create this
file. Ensure that the filename matches the filename you will copy from the router. Also, ensure
that the server permissions are set so the router can copy to this file.
3-34
Chapter 3
System Quick Start

Step 5
Enter the copy startup-config tftp command. The EXEC command interpreter prompts you for the
name or interface processor address of the remote host that is to receive the configuration file. (The
prompt might include the name or address of a default file server.)
Router# copy startup-config tftp
Remote host []?
Step 6
Enter the name or IP address of the remote host. In the following example, the name of the remote server
is servername:
Router# copy startup-config tftp
Remote host []? servername
Translating "servername"...domain server (1.1.1.1) [OK]
Step 7
Enter the name of the configuration file. The default is to use the name of the router with the suffix
-confg. Press Return to accept the default filename, or enter a different name for the file, then press
Return. In the following example, the default is accepted:
Name of configuration file to write [Router-confg]?
Write file Router-confg on host 1.1.1.1? [confirm]
Writing Router-confg .....
Step 8
The system displays the instructions you entered for confirmation. If the instructions are not correct,
enter n (no), and then press Return to cancel the process. To accept the instructions, press Return, or
press y and then press Return. In the following example, the default is accepted:
Write file Router-confg on host 1.1.1.1? [confirm]
Writing Router-confg: !!!! [ok]
The system displays a series of exclamation points

(! ! !) or periods (. . .) during the copy process. The !!!! and [ok] indicate that the operation was
successful. A series of periods (...) and [timed out] or [failed] indicates a failure of the process.
If the display indicates that the process was successful, the copy process is complete. The configuration
is stored on the remote file server.
If the display indicates that the process failed, the configuration was not saved (see the following
example):
Writing Router-confg .....
Repeat the preceding steps, or select a different remote file server and repeat the preceding steps.
After you upload the configuration file, continue with the Remove and Install an Interface Processor,
Filler, VIP, or RSP section on page 3-31 to install the RSP. If you are unable to copy the configuration
to a remote host successfully, contact your network administrator or contact Cisco technical assistance.
3-35
Chapter 3
System Quick Start
Retrieve the Configuration File for RSPs

Retrieve the saved configuration and copy it to NVRAM by accessing the router through a console
terminal, or from a remote terminal.
Step 1
follows:
Router> enable
Password:
Router#
Note
The router runs from the default configuration in NVRAM until the previous configuration is
retrieved. Passwords configured on the previous system are not valid until they are retrieved.
Step 2
Enter the ping command followed by the name or IP address of the remote server, and then press Return
to check the connection between the router and the remote host.
Step 3
Enter the copy tftp startup-config command and press Return to enter the configuration mode and
specify that you will configure the system from a network device (instead of from the console terminal,
which is the default).
Router# copy tftp startup-config
Step 4
Enter the IP address or name of the remote host (the remote TFTP server to which you originally saved
the configuration file).
Address of remote host [255.255.255.255]? 10.1.1.1
Step 5
Enter the name of the configuration file. The default is to use the name of the router with the suffix -confg
(Router-confg in the following example). If you specified a different filename when you copied the
configuration, enter the filename; otherwise, press Return to accept the default.
Name of configuration file [Router-confg]?
Step 6
Before the system reloads the new configuration file in NVRAM, it displays the instructions you entered
for confirmation. If the instructions are not correct, enter n (no), and then press Return to cancel the
process. To accept the instructions, press Return, or press y and then press Return. Output similar to
the following appears:
Configure using Router-confg from 10.1.1.1? [confirm]
Loading Router-confg from 10.1.1.1: ! ! [OK - 1186/126927 bytes]
Warning: distilled config is not generated
[OK]
%SYS-5-CONFIG_NV: Non-volatile store configured from Router-confg by console tftp from
10.1.1.1
The console display indicates whether or not the operation was successful. A series of exclamation
points (!!!!) and [OK] (as shown in the preceding example) indicates that the operation was successful.
A series of periods (. . .) and [timed out] or [failed] indicates a failure due to a network fault or an
incorrect server name, address, or filename. The following is an example of a failed attempt to boot from
a remote server:
Booting Router-confg ..... [timed out]
If the display indicates that the process was successful, as shown in Step 6, proceed to the next step.
If the display indicates that the process failed, verify the name or IP address of the remote server and the
filename, and repeat the preceding steps. If the process fails again, contact your network administrator.
3-36
Chapter 3
System Quick Start

Step 7
Enter the show startup-config command to confirm that the configuration file was retrieved correctly.
Look at the first line for the configuration file size. Compare it with the file you retrieved from the TFTP
server to confirm that it is correct. Following is an example:
Router# show startup-config
Using 1186 out of 126968 bytes
!
version 12.0(9)S
hostname Router
!
Router#
Step 8
To ensure that the startup configuration file stored in NVRAM is the default running configuration file
used by the system, enter the copy system:running-config nvram:startup-config command:
Router# copy system:running-config nvram:startup-config
Router#
%SYS-5-CONFIG_I: Configured from memory by console
Router#
This completes the process for retrieving the configuration file for the RSP.
3-37
Chapter 3
Remove and Install Port Adapters

Screw
Carrier
Upper edge
Lower edge
Captive
installation
screw
3-38
OLE
X.
NS
CO
AU
HA
U
RE
CP
EJE
SE
74553
SLO SLO
T0 T1
NO
RM
AL
CT
LT
ROUTE SWITCH PROCESSOR
System Quick Start
Chapter 3
System Quick Start

Note
First remove the VIP from the chassis before removing the port adapter from the VIP. See the Remove
and Install an Interface Processor, Filler, VIP, or RSP section on page 3-31 for instructions.
Step 1
Remove the screw that secures the port adapter (or blank port adapter), as shown in A.
Step 2
Grasp the handle and carefully pull it out of its slot, away from the edge connector at the rear of the slot.
(See A.)
Step 3
To insert the port adapter, align the carrier between the upper and the lower edges of the port adapter
slot. (See B.)
Step 4
Carefully slide the port adapter into the slot until the connector is completely seated in the connector at
the rear of the port adapter slot, as shown in B.
Step 5
Install the screw in the rear of the port adapter slot on the VIP. Do not overtighten the screw. (See A.)
Step 6
Carefully slide the VIP motherboard into the interface processor slot until the connectors at the rear of
the VIP are completely seated in the connectors at the rear of the interface processor slot. Use the ejector
levers to seat the VIP in the interface processor slot. Tighten the captive installation screws on the VIP.
(See C.)
Remove and Replace the Power Supply

Redundant power supplies support online insertion and removal (OIR); if you remove one power supply,
the second power supply immediately ramps up to maintain uninterrupted operation. In this case,
proceed to Step 2. If you have only one power supply, you must turn off power before removing and
replacing it. In this case, proceed to Step 1.
Step 1
Turn off the power source.
Step 2
Turn off the switch on the power supply.
Step 3
Disconnect the power cable from the power source.
Step 4
Disconnect the power cable from the power supply.

For the AC-input power supply: Lift up the cable retention clip and remove the power cable from the AC
receptacle.
3-39
Chapter 3
System Quick Start

Captive
installation screw
DC
ER
R
WE
IL
FA PO
DC AC
IL
FA POW
AC
LEDs
Power supply
front panel
AC power
receptacle
On/off switch
Locking device
74560
For the DC-input power supply: Use a screwdriver to loosen the captive installation screws on the
terminal block cover, lift the cover, use the wire cutters to cut the nylon strain-relief ties, and then remove
the three power leads (remove the ground lead last) from the terminal block.
3-40
System Quick Start


DO NOT SHIP WITH POWER SUPPLY
INSTALLED
FASTENER TO BE FULLY ENGAGED

BEFORE OPERATING POWER SUPPLY
screw
OU
T
INP FAIL
UT
PO
WE
Power leads attached

to terminal block
( ) negative
( ) positive
( ) ground
Nylon ties on cable

and metal bracket
INPUT VOLTAGE : 40-72 V=

INPUT CURRENT : 24-13A
74561
Chapter 3
Step 5
Use a screwdriver to loosen and remove the captive installation screw on the top of the power supply.
Step 6
Grasp the power supply handle with one hand and place your other hand underneath to support the
bottom of the power supply.
Warning
Keep hands and fingers out of the power supply bays. High voltage is present on the power backplane
when the system is operating.
Step 7
Pull the power supply out of the bay and put it aside.
Step 8
If the power supply bay is to remain empty, install a power-supply filler plate over the opening and secure
it with a mounting screw.
Step 9
Refer to the Install Power Supplies in the Router section on page 3-17 to replace the power supply.
3-41
Chapter 3
3-42
System Quick Start
C H A P T E R
Installing or Replacing the Power Supply

This chapter provides illustrated text to help you Install the power supply in the router.
Install Power Supplies in the Router

Figure 4-1
Power Supply
B
DC
FAN OUTPUT
OK
OK
FAIL
AC
OK
FAN OUTPUT
OK
AC
FAIL
OK
FAN OUTPUT
OK
FAIL
POWER
A
POWER
74557
Captive screws
Note
The Cisco 7513 and the Cisco 7576 routers are shipped with the power supplies removed. Each chassis
comes with one power supply as standard equipment; a second power supply is optional equipment. The
power supplies rest on the floor of the chassis under the card cage assembly.
This procedure applies to AC-input and DC-input power supplies, with differences clearly noted. Do not
mix AC-input and DC-input power supplies in the same chassis. Install the first power supply in the
lower power supply bay and the second, if any, in the upper bay. In systems with dual power supplies
and separate available power sources, connect each power supply to separate input linesthe second
power source will likely be available during a failure.
4-1
Chapter 4
For AC-input power supplies, confirm that the power on the power supply is off.
Step 1
For DC-input power supplies, turn off the circuit breaker to which you will connect power, and tape the
breaker switch to the off position.
Hold the power supply by the handle and place your other hand underneath it.
Step 2
Use two hands to remove and install power supplies.
Caution
Step 3
Place the power supply inside the bay, and align it to go straight into the bay.
Step 4
Push the power supply back into the bay until its front panel is flush with the chassis rear panel.
Step 5
Use a screwdriver to tighten the captive installation screw on the top of the power supply.
For AC-input power supplies, proceed to the Connect AC-Input Power Supply section on page 4-2.
For DC-input power supplies, proceed to the Connect DC-Input Power Supply section on page 4-3.
Connect AC-Input Power Supply

Figure 4-2
Cable-retention clip
AC
OK
FAN
OK
OUTPUT
FAIL
AC
OK
FAN
OK
OUTPUT
FAIL
POWER
B
I
I
74550
Captive screws
Warning
4-2
Chapter 4
Step 1
For AC-input power supplies, push the cable retention clip away from the power receptacle and plug in
the power cable.
Step 2
Push the cable retention clip until it snaps into place around the cable connector.
Step 3
Reconnect the power cable at the power source, remove the tape on the breaker switch. Do not turn on
the breaker or power to the power supply.
A power supply blank must remain in any empty power supply bay.
Note
Repeat Step 1 through Step 3 for the second power supply, if present.
Step 4
Do not mix AC-input and DC-input power supplies in the same chassis.
Note
Connect DC-Input Power Supply


Remove
DC
FAN OUTPUT
OK
OK
Terminal
block
cover
FAIL

with the terminal block
cover removed
DC-input
cable (8-AWG)
Power leads
attached to
terminal block
(+) Positive
() Negative
( ) Ground
DC
FAN OUTPUT
OK
OK
FAIL
Conduit
bracket
Remove
I
Captive
installation
screw
Warning
74551
Figure 4-3
Step 1
Use a screwdriver to loosen and remove the terminal block cover screws.
Step 2
Lift and remove the terminal block cover.
Step 3
Route the DC-input power cable from the power source through the conduit bracket on the power supply.
Allow sufficient slack in the cable.
4-3
Chapter 4
Step 4
Attach and tighten the conduit to the conduit bracket.
Note
The proper wiring sequence is ground to ground, positive to positive (line to L), negative to
negative (neutral to N). The ground wire should always be connected first and disconnected last.
Step 5
Attach the ground wire to the ground terminals using the 8-mm nut driver.
Step 6
Check the power supplys wiring and color code to verify that it matches the wiring and color code at
the DC source.
Warning
Incorrect wiring could create a dangerous shock hazard and could damage the power supply, power
source, and chassis components.
Step 7
Replace the terminal block cover.
Step 8
Reconnect the power cable at the power source.
Step 9
Repeat Step 1 through Step 8 for a second power supply, if present.
Remove and Replace the Power Supply

Redundant power supplies support online insertion and removal (OIR); if you remove one power supply,
the second power supply immediately ramps up to maintain uninterrupted operation. In this case,
proceed to Step 2. If you have only one power supply, you must turn off power before removing and
replacing it. In this case, proceed to Step 1.
Step 1
Turn off the power source.
Step 2
Turn off the switch on the power supply.
Step 3
Disconnect the power cable from the power source.
Step 4
Disconnect the power cable from the power supply.

For the AC-input power supply: Lift up the cable retention clip and remove the power cable from the AC
receptacle.
4-4
Figure 4-4

Captive
installation screw
DC
ER
R
WE
IL
FA PO
DC AC
IL
FA POW
AC
LEDs
Power supply
front panel
AC power
receptacle
On/off switch
Locking device
74560
Chapter 4
For the DC-input power supply: Use a screwdriver to loosen the captive installation screws on the
terminal block cover, lift the cover, use the wire cutters to cut the nylon strain-relief ties, and then remove
the three power leads (remove the ground lead last) from the terminal block.
4-5
Chapter 4
Figure 4-5
DO NOT SHIP WITH POWER SUPPLY

INSTALLED
FASTENER TO BE FULLY ENGAGED

BEFORE OPERATING POWER SUPPLY
screw
OU
T
INP FAIL
UT
PO
WE
Power leads attached

to terminal block
( ) negative
( ) positive
( ) ground
INPUT VOLTAGE : 40-72 V=

INPUT CURRENT : 24-13A
Step 5
Use a screwdriver to loosen and remove the captive installation screw on the top of the power supply.
Step 6
Grasp the power supply handle with one hand and place your other hand underneath to support the
bottom of the power supply.
Warning
Keep hands and fingers out of the power supply bays. High voltage is present on the power backplane
when the system is operating.
Step 7
Pull the power supply out of the bay and put it aside.
Step 8
If the power supply bay is to remain empty, install a power-supply filler plate over the opening and secure
it with a mounting screw.
Step 9
Refer to the Install Power Supplies in the Router section on page 4-1 to replace the power supply.
4-6
74561
Nylon ties on cable

and metal bracket
C H A P T E R

This chapter describes how to perform the following tasks:
Verify That the System Has Detected the HSL Hardware, page 2
Examine All ATM Port Adapters Installed in Each Slot, page 3
Verify that the IOS Has Provided the Initial Default Configuration for Each of the ATM Interfaces,
page 4
Verify the State of Each Interface, page 5
Additional Commands to Obtain Details about the Hardware, page 6
Verifying Installation of the SS7 Port Adapter, page 9
Examine All SS7 Port Adapters Installed in Each Slot, page 10
Verify that the IOS has Provided the Initial Default Configuration for Each of the SS7 Controllers,
page 11
Additional Commands to Obtain Details of the Hardware, page 12
5-1
Chapter 5

Issue the show version command in user EXEC mode to list all the hardware controllers and network
interfaces detected by the system.
The following sample output shows that the system has detected one Ethernet controller and one ATM
controller with 8 interfaces:
1 EIP controller (6 Ethernet)
1 VIP4-80 RM7000 controller (8 ATM)
8 ATM network interface(s)
Router> show version

Cisco Internetwork Operating System Software
IOS (tm) RSP Software (RSP-ITPV-M), Version 12.2(4)MB4, EARLY DEPLOYMENT RELEASE
SOFTWARE (fc1)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Wed 03-Apr-02 12:36 by yiyan
Image text-base: 0x60010C10, data-base: 0x6123A000
ROM: System Bootstrap, Version 12.0(10r)S1, RELEASE SOFTWARE (fc1)

BOOTLDR: RSP Software (RSP-ITPV-M), Version 12.2(4)MB4, EARLY DEPLOYMENT RELEASE
SOFTWARE (fc1)
ITP-1 uptime is 1 day, 19 hours, 1 minute

System returned to ROM by reload at 15:57:11 UTC Mon Apr 15 2002
System image file is "disk0:rsp-itpv-mz.122-4.MB4.bin"
cisco RSP8 (R7000) processor with 262144K/8216K bytes of memory.
R7000 CPU at 250Mhz, Implementation 39, Rev 2.1, 256KB L2, 2048KB L3 Cache
Last reset from power-on
G.703/E1 software, Version 1.0.
G.703/JT2 software, Version 1.0.
X.25 software, Version 3.0.0.
Bridging software.
Primary Rate ISDN software, Version 1.1.
Channelized E1, Version 1.0.
Chassis Interface.
4 VIP4-80 RM7000 controllers (2 FastEthernet)(32 E1)(24 ATM).
2 FastEthernet/IEEE 802.3 interface(s)
113 Serial network interface(s)
24 ATM network interface(s)
2043K bytes of non-volatile configuration memory.
125440K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
16384K bytes of Flash internal SIMM (Sector size 256K).
Slave in slot 7 is running Cisco Internetwork Operating System Software
SOFTWARE (fc1)
TAC Support: http://www.cisco.com/tac
Compiled Wed 03-Apr-02 12:36 by yiyan
Slave: Loaded from system
Slave: cisco RSP8 (R7000) processor with 262144K bytes of memory.
Configuration register is 0x102
5-2
Chapter 5


Issue the show diagbus command in privileged EXEC mode to display a high level view of all the port
adapters installed and their locations. The command also displays the hardware serial number and part
numbers.
The following sample output shows an 8 port E1 port adapter (PA) installed in bay 1 of slot 5.
Router# show diagbus
Slot 5:
Physical slot 5, ~physical slot 0xA, logical slot 5, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: None
EEPROM format version 1
VIP4-80 RM7000 controller, HW rev 2.01, board revision A0
Serial number: 18560245 Part number: 73-3143-03
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 22 02 01 01 1B 34 F5 49 0C 47 03 00 00 00 00
0x30: 50 16 A8 00 00 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0x312C (00:05:09 ago)
Controller Memory Size: 128 MBytes DRAM, 65536 KBytes SRAM
PA Bay 1 Information:
IMA E1 PA, 8 ports
HW rev 1.00, Board revision A0
5-3
Chapter 5
Verify that the IOS Has Provided the Initial Default Configuration for Each of the ATM Interfaces
Verify that the IOS Has Provided the Initial Default Configuration
for Each of the ATM Interfaces
The IOS provides a initial default configuration for each hardware interface.
Issue the show running-config command in privileged EXEC mode to display the initial configuration
for each of the ATM interfaces.
The following sample output shows 8 ATM interfaces detected in Slot 5, Bay 1 and their default
configuration:
Router# show running-config
interface ATM5/1/0
no ip address
shutdown
no ima-group
no atm ilmi-keepalive
!
interface ATM5/1/1
no ip address
shutdown
no ima-group
!
interface ATM5/1/2
no ip address
shutdown
no ima-group
!
interface ATM5/1/3
no ip address
shutdown
no ima-group
!
interface ATM5/1/4
no ip address
shutdown
no ima-group
!
interface ATM5/1/5
no ip address
shutdown
no ima-group
!
interface ATM5/1/6
no ip address
shutdown
no ima-group
!
interface ATM5/1/7
no ip address
shutdown
no ima-group
5-4
Chapter 5


Issue the show interface privileged EXEC command to verify the state of an interface.
The following sample output shows that the ATM interface number 0 in the port adapter in Bay 1 of Slot
5 is down and so is the line protocol. This is because the interface has been configured as shutdown in
the initial configuration.
Router# show interface ATM5/1/0
ATM5/1/0 is administratively down, line protocol is down
Hardware is cyBus IMA PA
MTU 4470 bytes, sub MTU 4470, BW 1920 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5
511 maximum active VCs, 0 current VCCs
VC idle disconnect time: 300 seconds
0 carrier transitions
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); 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)
Available Bandwidth 1440 kilobits/sec
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
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
5-5
Chapter 5

To obtain additional details about the hardware controllers, issue the following privileged EXEC
commands:
show controllers command
show controller cbus command
Sample output from both commands follows.

Router# show controllers ATM 5/1/0
ATM5/1/0: Port adaptor specific information
Hardware is E1 (2000Kbps) port adaptor
Framer is PMC PM7344, SAR is LSI ATMIZER II
Default Maximum Queue Length: 0
Scrambling is Disabled
linecode is HDB3
E1 Framing Mode: pcm30 ADM format
LBO (Cablelength) is long gain43 120db
Facility Alarms:
No Alarm
Counters:
hcs
- # uncorrectable HEC errors
chece
- # rx Correctable HEC errors
uicell
- # unassigned/idle cells dropped
oocd
- # rx out of cell deliniation
rx_fovr
- # rx FIFO over run
tx_fovr
- # tx FIFO over run
coca
- # tx Change of cell allignment
pcv
- # path code violations
lcv
- # line code violations
es
- # errored Seconds
ses
- # severely errored secs
sefs
- # severely errored framing secs
uas
- # unavailable seconds
css
- # controlled slip seconds
les
- # line errored seconds
bes
- # bursty errored seconds
dm
- # degraded minutes
ss
- # stuffed seconds
hcs:0, chece:0, uicell:0, oocd:0,
rx_fovr:0, tx_fovr:0, coca:0, pcv:0, lcv:0, es:0, ses:0,
sefs:0, uas:0, css:0, les:0, bes:0, dm:0, ss:0
Bert Information:
state
: OFF, pattern
: invalid
interval
: 0,
result
: OUT_OF_SYNC
sync count : 0,
bit errors : 0
kbit count : 0
bit errors since last sync
: 0
kbit count since last sync
: 0
rx_cfg
- receive configuration
tx_cfg
- transmit configuration
rxint_cfg
- interface configuration. receive
txint_cfg
- interface configuration. transmit
txtiming
- Tx timing options
tran_diagr - Diags and FIFO parity control
5-6
Chapter 5

cdrc_cfg
- CDRC configuration
refclk_div1 - DJAT ref clock divisor N1
refclk_div2 - DJAT ref clock divisor N2
t1frmr_cfgr - T1-FRMR configuration
e1frmr_align- E1-FRMR frame alignment
t1tran_cfgr - T1-TRAN configuration
e1tran_cfgr - E1-TRAN configuration
txcp_ctrl
- TXCP control
rxcp_ctrl
- RXCP control
rxcp_frmctrl- RXCP framing control
t1frmr_isr - T1_FRMR interrupt status
e1frmr_isr - E1_FRMR interrupt status
e1frmr_statr- E1-FRMR framing status
rx_cfg =0x5, tx_cfg =0x5, rxint_cfg =0x5, txint_cfg =0xA,
txtiming =0xA, tran_diagr =0x8, cdrc_cfg =0xF8, refclk_div1 =0x2F,
refclk_div2 =0x2F, t1frmr_cfgr=0x0, e1frmr_align = 0x4, t1tran_cfgr= 0x0,
e1tran_cfgr = 0xE4, txcp_ctrl = 0xA0, rxcp_ctrl = 0x28, rxcp_frmctrl=0x80,
e1frmr_isr =0x34, t1frmr_isr = 0x0, e1frmr_statr = 0x0
active HSRP group:

VIP reported active HSRP group:

Router# show controller cbus
slot5: VIP4-80 RM7000, hw 2.01, sw 22.20, ccb 5800FF70, cmdq 480000A8, vps 8192
software loaded from system
IOS (tm) VIP Software (SVIP-ITPDW-M), Experimental Version 12.2(20010919:072403)
[ppearce-topsail_n
ROM Monitor version 103.0
ATM5/1/0, applique is E1 (2000Kbps)
gfreeq 48000158, lfreeq 480001C8 (4544 bytes)
rxlo 4, rxhi 129, rxcurr 0, maxrxcurr 0
txq 48001A00, txacc 48001A02 (value 6), txlimit 6
gfreeq 48000158, lfreeq 480001D0 (4544 bytes)
txq 48001A08, txacc 48001A0A (value 0), txlimit 6
gfreeq 48000158, lfreeq 480001D8 (4544 bytes)
gfreeq 48000158, lfreeq 480001E0 (4544 bytes)
gfreeq 48000158, lfreeq 480001E8 (4544 bytes)
gfreeq 48000158, lfreeq 480001F0 (4544 bytes)
gfreeq 48000158, lfreeq 480001F8 (4544 bytes)
5-7
Chapter 5

gfreeq 48000158, lfreeq 48000200 (4544 bytes)
Router#
5-8
Chapter 5


In order to cause the system to automatically detect the interfaces on SS7 Port adapter, you must
configure the slot and bay in which it is installed, and specify whether it is a T1 or E1 adapter.
You modify the configuration of your router through the software command interpreter called the EXEC
(also called enable mode). You must enter the privileged level of the EXEC command interpreter with
the enable command before you can use the configure command to configure a new interface or change
the existing configuration of an interface. The system prompts you for a password if one has been set.
The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>).
At the console terminal, use the following procedure to enter the privileged level:
Step 1
At the user-level EXEC prompt, enter the enable command. The EXEC prompts you for a
privileged-level password as follows:
Router> enable
Password:
Step 2
Enter the password (the password is case sensitive). For security purposes, the password is not displayed.
When you enter the correct password, the system displays the privileged-level system prompt (#):
Router#
Note
Step 3
This process will take about 30 seconds and is disruptive to ITP operation. Therefore, a maintenance
window should be shceduled to perform this process. The process needs to be entered only once for
each SS7 port adapter at initial installation.
Specify whether the card is to be used as T1 or E1 by using the card type command in configuration
mode.
The following example sets the card in slot 4 Bay 0 to T1:

Router(config) # card type t1 4 0
The following example sets the card in slot 4 Bay 0 to E1:

Router(config)# card type e1 4 0
After you have issued the card type command, the system will display the following messages. In the
following example the system has detected a T1 SS7 port adapter in Bay 0 of Slot 4:
"The system will restart, please wait..."
"%RSP-3-RESTART: cbus complex"
"%CONTROLLER-5-UPDOWN: Controller T1 4/0/0, changed state to up"
"%CONTROLLER-5-UPDOWN: Controller T1 4/0/1, changed s linecode b8zs"
5-9
Chapter 5

Issue the show diagbus privileged EXEC command to display a high level view of all the port adapters
installed and their locations. The command also displays the hardware serial number and part numbers.
The following sample output shows that an 8 port T1/E1 port adapter (PA) is installed in Bay 0 of Slot 4.
Router# show diagbus
Slot 4:
Physical slot 4, ~physical slot 0xB, logical slot 4, CBus 0
Board is analyzed
VIP4-80 RM7000 controller, HW rev 2.01, board revision A0
Test history: 0x00
RMA number: 00-00-00

0x20: 01 22 02 01 01 1B 04 E0 49 0C 47 03 00 00 00 00
0x30: 50 05 35 00 00 00 00 00 00 00 00 00 00 00 00 00

Flags: 0x4
Insertion time: 0x352C (00:22:56 ago)

MCX-SS7 Hangten 8T1/E1 PA, 8ports
HW rev 1.00, Board revision 02
Serial number: MIC05320007 Part number: 73-7263-01
5-10
Chapter 5

Verify that the IOS has Provided the Initial Default Configuration for Each of the SS7 Controllers
Verify that the IOS has Provided the Initial Default Configuration
for Each of the SS7 Controllers
The IOS provides a initial default configuration for each hardware interface.
Issue the show running-config command in privileged EXEC mode to display the initial configuration
for each of the SS7 interfaces.
The following sample output shows the 8 T1 SS7 interface controllers detected in Slot 4, Bay 0 and their
default configuration.
controller T1 4/0/0
framing esf
linecode b8zs
!
controller T1 4/0/1
framing esf
linecode b8zs
!
controller T1 4/0/2
framing esf
linecode b8zs
!
controller T1 4/0/3
framing esf
linecode b8zs
!
controller T1 4/0/4
framing esf
linecode b8zs
!
controller T1 4/0/5
framing esf
linecode b8zs
!
controller T1 4/0/6
framing esf
linecode b8zs
!
controller T1 4/0/7
framing esf
linecode b8zs
5-11
Chapter 5

To obtain additional details about the hardware controllers, issue the following privileged EXEC
commands:
Sample output from both commands follows.

Router# show controllers T1 4/0/0
T1 4/0/0 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
Data in current interval (320 seconds elapsed):
0 Line Code Violations, 2 Path Code Violations
1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
2 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 12 Unavail Secs
The following sample output shows information about the SS7 interface controllers in Slot 4 Bay0:
Router# show controller cbus
T1 4/0/0, applique
gfreeq 48000150,
rxlo 4, rxhi 79,
T1 4/0/1, applique
gfreeq 48000150,
rxlo 4, rxhi 79,
T1 4/0/2, applique
gfreeq 48000150,
rxlo 4, rxhi 79,
T1 4/0/3, applique
gfreeq 48000150,
rxlo 4, rxhi 79,
T1 4/0/4, applique
gfreeq 48000150,
rxlo 4, rxhi 79,
T1 4/0/5, applique
gfreeq 48000150,
rxlo 4, rxhi 79,
T1 4/0/6, applique
gfreeq 48000150,
rxlo 4, rxhi 79,
T1 4/0/7, applique
gfreeq 48000150,
rxlo 4, rxhi 79,
5-12
is Channelized T1
lfreeq 48000180 (1536
rxcurr 0, maxrxcurr 0
is Channelized T1
lfreeq 48000188 (1536
is Channelized T1
lfreeq 48000190 (1536
is Channelized T1
lfreeq 48000198 (1536
is Channelized T1
lfreeq 480001A0 (1536
is Channelized T1
lfreeq 480001A8 (1536
is Channelized T1
lfreeq 480001B0 (1536
is Channelized T1
lfreeq 480001B8 (1536
bytes)
bytes)
bytes)
bytes)
bytes)
bytes)
bytes)
bytes)
C H A P T E R
Configure and Maintain RSP

Redundancy - RPR+
This chapter describes Route Processor Redundancy Plus (RPR+) on Cisco 7500 series routers.This
document includes the following sections:
Supported Platforms, page 2
Prerequisites, page 2
Configuration Tasks, page 2
Configuration Examples, page 7
The RPR+ feature is an enhancement of the RPR feature on Cisco 7500 series routers. RPR+ keeps the
Virtual Interface Processors (VIPs) from being reset and reloaded when a switchover occurs between the
active and standby route switch processors (RSPs). Because VIPs are not reset and microcode is not
reloaded on the VIPs, and the time needed to parse the configuration is eliminated, switchover time is
reduced to 10 to 30 seconds.
Feature
Switchover Time
Notes
High System Availability (HSA) 8 to 10 minutes
System default.
RPR
4 to 5 minutes
VIPs and legacy interface processors

supported.
RPR+
10 to 30 seconds
VIPs supported.1
1. Legacy Interface Processors default to RPR. A message similar to the following is displayed during switchover:
%HA-2-NO_Quiesce: Slot 11 did not quiesce, it will be disabled and then reloaded.
RPR+ reduces the amount of unplanned downtime of a Cisco 7500 series router by enabling a faster
switchover time to the standby RSP.
RPR+ is an enhancement of RPR. Switchover time with RPR+ is reduced to 10 to 30 seconds.
Restrictions
RPR+ operates only in a system with VIPs as the line cards. Systems with legacy Interface
Processors default to RPR.
In RPR+ mode, configuration changes done through SNMP may not be automatically configured on
the standby RP after a switchover occurs.
6-1
Chapter 6
Supported Platforms
RPR+ does not work on routers configured with MPLS.
Supported Platforms
Cisco 7507
Cisco 7513
Determining Platform Support Through Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated
information regarding platform support for this feature, access Feature Navigator. Feature Navigator
dynamically updates the list of supported platforms as new platform support is added for the feature.
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.
To access Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your
account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify
that your e-mail address is registered with Cisco.com. If the check is successful, account details with a
new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com
by following the directions at http://www.cisco.com/register.
Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases
occur. For the most current information, go to the Feature Navigator home page at the following URL:
http://www.cisco.com/go/fn
Prerequisites
RPR+ requires a Cisco 7500 series router loaded with two RSP8s.
Configuration Tasks
See the following sections for the configuration tasks required to run RPR+:
Copying an Image onto an RSP, page 3 (required)
Setting the Config-Register Boot Variable, page 4 (optional)
Configuring RPR+, page 5 (required)
Verifying RPR+, page 7 (optional)
6-2
Chapter 6

Configuration Tasks
Copying an Image onto an RSP

Use TFTP to copy a high availability Cisco IOS image onto the active and standby RSPs:
Step 1
Command
Purpose
Router# copy tftp slotslot-number:
Uses TFTP to copy a high availability Cisco IOS

image onto the Flash memory card of the active
RSP.1
Address or name of remote host []? ip-address
slotslot-numberSpecifies the Flash memory

card of the active RSP.
The router prompts you for the IP address of the

TFTP server.
Name of file to copy []? imagename<Return>
writing
filename!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ip-addressSpecifies the IP address of the

TFTP server that contains the new image.
The router prompts you for the name of the image

file you are copying to the Flash memory card.
Destination file name? [imagename1] <Return>
Accessing file 'imagename' on ip-address.. found !
Loading imagename from ip-address (via
Ethernet1/0/0): !
The router prompts you to enter the name under

which you want the file to appear at the destination.
Step 2
Router# copy tftp slaveslotslot-number:
imagename1Indicates the name of the image

as it appears at the destination.

image onto the Flash memory card of the standby
RSP.

writing
filename!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
imagenameIndicates the name of the image to

be loaded onto the Flash memory card.
slaveslotslot-numberSpecifies the Flash

memory card of the standby RSP.

TFTP server.



Loading imagename from ip-address (via Ethernet1/0):
!



1. Before you copy a file to Flash memory, be sure there is ample space available in Flash memory. Compare the size of the file you are copying to the
amount of available Flash memory shown. If the space available is less than the space required by the file you will copy, the copy process will not
continue and an error message similar to the following will be displayed;
%Error copying tftp://image@server/tftpboot/filelocation/imagename (Not enough space on device).
6-3
Chapter 6
Configuration Tasks
Setting the Config-Register Boot Variable

Though it is not required, we recommend that you modify the software configuration register boot field
so that the system boots the same image that the hw-module slotslot-number image file-spec command
specified in the Configuring RPR+ section.
Command
Purpose
Step 1
Router# show version
Obtains the current configuration register setting.
Step 2
Enters configuration mode, selecting the terminal

option.
Step 3
Router(config)# boot system flash

slotslot-number:[imagename]
Specifies the filename of an image stored in Flash

memory.
Step 4
Router(config)# config-register 0x2102
imagenameIt is recommended that you set

the boot variable so that the system boots the
same image specified by the hw-module slot
slot-number image file-spec command. See
Step 2 of the Configuring RPR+ section on
page 5.
slot-numberSpecifies the active RSP slot

where the Flash memory card is located. Valid
numbers are slot 2 or slot 3 for a Cisco 7507
router and slot 6 or slot 7 for a Cisco 7513
router.
Modifies the existing configuration register setting

to reflect the way in which you want to load a
system image.
value range0x0 to 0xFFFFFFFF
Step 5
Router# Ctrl-Z
Exits configuration mode.
Step 6
Router# reload
Reboots the router to make your changes take

effect.
6-4
Chapter 6

Configuration Tasks
Configuring RPR+
Note
RPR+ should be configured on the ITP before any global SS7 configuration is done. This will allow
Cisco IOS to save all configuration including route and GTT tables on both RSP cards.
If a second RSP is added and configured for RPR+ then is is necessary to perform the following steps
after RPR+ is enabled:
Command
Purpose
Step 1
Router# copy running-config startup-config
Populate and save the current configuration on both

primary and secondary RSP.
Step 2
Router# copy slot0:mtp3-routes slaveslot0:mtp3-routes
Copy the MTP3 routing table (saved as

slot0:mtp3-routes) to the flash card on the secondary
RSP. This step can be ommitted if no routing table
has been saved. slot0: will have to be replaced
with disk0: if a 128 MByte ATA pcmcia disk is
used.
Step 3
Router# copy slot0:gtt-table slaveslot0:gtt-table
Copy the GTT table (saved as slot0:gtt-table) to the

flash card on the secondary RSP. This step can be
ommitted if no GTT is configured. slot0: should
be replaced with disk0:if a 128 MByte ATA
pcmcia disk is used.
Step 4
Router# hw-module sec-cpu reset
This step is mandatory if one of the two previous

copy commands was entered. It will restart the
secondary RSP and ensure that in the unlikely event
of a switchover, corrrect tables are available.
6-5
Chapter 6
Configuration Tasks
To configure RPR+, enter the commands as shown below:

Command
Purpose
Step 1
Enters configuration mode.
Step 2
Router(config)# hw-module slotslot-number image

file-spec
Verifies that the specified image is compatible with

RPR+ and exists on the standby RSP. If a high
availability image is found, the running
configuration is updated.
slot-numberSpecifies the standby RSP slot

router or slot 6 or slot 7 for a Cisco 7513 router.
file-specIndicates the Flash device and the

name of the image on the standby RSP.
Note
Step 3

file-spec
The image indicated by the file-spec

attribute must be available on the local
Flash device. Remote protocols such a
Trivial File Transfer Protocol (TFTP) and
remote copy protocol (RCP) are not
available.

RPR+ and exists on the active RSP. If a high


name of the image on the active RSP.
Note

available.
Step 4
Router(config)# redundancy
Enters redundancy mode.
Step 5
Router(config-r)# mode rpr-plus

Operating mode is RPR, configured mode is rpr-plus.
Sets the redundancy mode to RPR+ on both the

active and standby RSPs. HSA is the default
redundancy mode.
Note
6-6
If the active and standby RSPs are running

different IOS images and have Fast
Software Upgrade configured, the default
redundancy mode is RPR.
Chapter 6

Configuration Examples
Command
Purpose
Step 6
Router(config-r)# end
Step 7
Resets and reloads the standby RSP with the

specified Cisco IOS image and executes the image.
Note
If you do not specify a Cisco IOS image in

Step 2, this command loads and executes
the bundled default IOS standby image.
The system then operates in HSA mode.
Verifying RPR+
Use the show redundancy command to verify that RPR+ is enabled:
Router# show redundancy
Operating mode is rpr-plus
redundancy mode rpr-plus
hw-module slot 2 image disk0:rsp-pv-mz
hw-module slot 3 image disk0:rsp-pv-mz
The system
The system
The system
Reason for
total uptime since last reboot is 5 days, 19 hours 36 minutes.

has experienced 27 switchovers.
has been active (become master) for 5 days, 15 hours 14 minutes.
last switchover:User forced.
Troubleshooting Tips
Use the commands in the table below to troubleshoot the RPR+ feature on the Cisco 7500 series routers:
Command
Purpose
Router# show diag
Use this command to display hardware information

for the router.
Use this command to display the redundancy mode

of the RSP. This command also displays
information about the number of switchovers,
system uptime, RSP uptime, and reasons for any
switchovers.
Use this command to display image information for

each RSP.
This section provides the following configuration example:
Configuring RPR+ Example, page 8
6-7
Chapter 6
Configuring RPR+ Example

In the following example, the active RSP is in slot 2 and the standby RSP is installed in slot 3 of a
Cisco 7507 router.
Router# copy tftp slot0:rsp-pv-mz
Router# copy tftp slaveslot0:rsp-pv-mz
Router(config)# hw-module slot 2 image slot0:rsp-pv-mz
Router(config)# hw-module slot 3 image slot0:rsp-pv-mz
Router(config)# redundancy
Router(config-r)# mode rpr-plus
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service single-slot-reload-enable
!
hostname Router1
!
boot system rcp://path/to/image/rsp-boot-mz
boot system tftp://path/to/image/rsp-boot-mz
boot bootldr bootflash:rsp-boot-mz
enable password password
!
redundancy
mode rpr-plus !--indicates Redundancy mode has been configured for RPR+
!
hw-module slot 2 image slot0:rsp-pv-mz
hw-module slot 3 image slot0:rsp-pv-mz
ip subnet-zero
ip rcmd remote-username router1
ip cef distributed
ip host iphost 192.168.0.1
mpls traffic-eng auto-bw timers
!
!
controller T3 6/0/0
clock source line
!
!
interface Ethernet0/0/0
ip address 10.0.0.1 255.255.0.0
no ip directed-broadcast
ip route-cache distributed
no keepalive
.
.
.
exec-timeout 0 0
history size 40
transport preferred none
transport input none
line aux 0
line vty 0 4
login
!end
6-8
C H A P T E R
This chapter describes the tasks to configure IP addressing on the FEIP-DSW. It contains the following
sections:
Identifying Interface Numbers and Addresses, page 1
Configuring FE Interfaces, page 2
Checking the Configuration, page 4
After you verify that the FEIP2-DSW is installed correctly (the enabled LED goes on), you can configure
IP addressing on the new interfaces. The configure command requires privileged-level access to the
EXEC command interpreter, which usually requires a password. Contact your system administrator if
necessary to obtain EXEC-level access.
Note
Identifying Interface Numbers and Addresses

This section explains interface processor slot, FE interface, and interface port numbering.
Note
Although the interface processor slots in the Cisco 7000, Cisco 7507, and Cisco 7513 are vertically
oriented and those in the Cisco 7010 and Cisco 7505 are horizontally oriented, all models use the same
method for slot and port numbering.
In the router, physical port addresses specify the actual physical location of each interface port on the
router interface processor end. This address is composed of a three-part number in the format interface
processor slot number/adapter number/interface port number.
The first number identifies the interface processor slot in which the FEIP2-DSW is installed.
The second number identifies the physical FE interface on the FEIP2-DSW and is slot 0 (on the left)
and slot 1 (on the right).
The third number identifies the FE interface port, which is always numbered as interface 0.
7-1
Chapter 7
Interface ports on the FEIP2-DSW maintain the same address regardless of whether other interface
processors are installed or removed. However, when you move an FEIP2-DSW to a different slot, the
first number in the address changes to reflect the new interface processor slot number.
On the FEIP2-DSW-2TX, the first FE interface number is 0 and the second is 1. For example, on a
FEIP2-DSW in interface processor slot 3, the address of the first FE interface is 3/0/0 (interface
processor slot 3, FE interface 0, and interface port 0). The address of the second FE interface is 3/1/0
(interface processor slot 3, FE interface 1, and interface port 0).
Note
If you remove the FEIP2-DSW-2TX from interface processor slot 3 and install it in interface processor
slot 2, the addresses of these FE interfaces become 2/0/0 and 2/1/0, respectively.
You can also identify interface ports by physically checking the slot/adapter/interface port location on
the back of the router or by using software commands to display information about a specific interface
or all interfaces in the router.
This section describes a basic configuration. Press the Return key after each step unless otherwise
noted. At any time you can exit the privileged level and return to the user level by entering disable at the
prompt as follows:
Router# disable
Router>
Following is a basic configuration procedure:

Step 1
At the privileged-level prompt, enter configuration mode and specify that the console terminal is the
source of the configuration subcommands, as follows:
Router(config)#
Step 2
End with CNTL/Z.
At the prompt, specify the first interface to configure by entering the subcommand interface, followed
by the type (fastethernet) and slot/port (interface processor slot number/0). The example that follows
is for the interface port of the first FE interface port, on an FEIP2-DSW in interface processor slot 1:
Router(config)# interface fa 1/0/0
Step 3
If IP routing is enabled on the system, you can assign an IP address and subnet mask to the interface
with the ip address configuration subcommand, as in the following example:
Router(config-int)# ip address 1.1.1.10 255.255.255.0
Step 4
Add any additional configuration subcommands required to enable routing protocols and set the
interface characteristics.
Step 5
Change the shutdown state to up and enable the interface as follows:

Router(config-int)# no shutdown
Step 6
Configure additional FE interfaces as required.
Step 7
When you have included all of the configuration subcommands to complete the configuration, press
Ctrl-Z to exit configuration mode.
7-2
Chapter 7
Step 8
Write the new configuration to nonvolatile memory as follows:

[OK]
Router#
Following are descriptions and examples of the commands for configuring FE interface 3/0/0.
Descriptions are limited to fields that are relevant for establishing and verifying the configuration. After
configuring the new FE interface, use show commands to display the status of the new interface or all
interfaces, or to verify changes you have made.
FE half-duplex operation is the default. To change to full-duplex operation, use the following series of
commands:
Router(config)#
End with CNTL/Z.
Router(config)# interface fastethernet 3/0/0

Router(config-if)# full-duplex
Ctrl-z
Router#
Note
Using the show interfaces fastethernet command, you can see that the 3/0/0 FE interface is now
configured for full-duplex operation:
Router# sh int fa 3/0/0
FastEthernet 3/0/0 is administratively up, line protocol is up
(display text omitted)
Encapsulation ARPA, loopback not set, keepalive not set, fdx, 100BaseTX
To return the interface to half-duplex operation, use the no full-duplex configuration command, as
follows:
Router# config t
Router(config)# int fa 3/0/0
Router(config-if)# no full-duplex
Ctrl-z
Router#
End with CNTL/Z.
Using the show interfaces fastethernet command, you can see that the 3/0/0 FE interface is now
configured for half-duplex operation:
FastEthernet3/0/0 is administratively up, line protocol is up
Encapsulation ARPA, loopback not set, keepalive not set, hdx, 100BaseTX
7-3
Chapter 7
Checking the Configuration
The RJ-45 connection is the default for FEIP2-DSW-2TX (or SC for FEIP2-DSW-2FX). To change to
an MII connection and then verify it, use the following series of commands, including the media-type
configuration command:
Router# config t
Router(config)# int fa 3/0/0
Router(config-if)# media-type mii
Ctrl-z
End with CNTL/Z.

FastEthernet3/0/0 is administratively up, line protocol is up
Encapsulation ARPA, loopback not set, keepalive not set, hdx, MII
Use the media-type 100 configuration command to return the interface to its default state for RJ-45 or
SC (fiber-optic) connections.

After configuring the new interface, use the show commands to display the status of the new interface
or all interfaces and the ping command to check connectivity.
Using show Commands to Verify FEIP2-DSW Status

The following steps use show commands to verify that the new interfaces are configured and operating
correctly.
Step 1
Use the show version command to display the system hardware configuration. Ensure that the list
includes the new interfaces.
Step 2
Display all the current interface processors and their interfaces with the show controllers cbus
command. Verify that the new FEIP2-DSW appears in the correct slot.
Step 3
Specify one of the new interfaces with the show interfaces type slot/adapter/interface command and
verify that the first line of the display specifies the interface with the correct slot number. Also verify
that the interface and line protocol are in the correct state: up or down.
Step 4
Display the protocols configured for the entire system and specific interfaces with the show protocols
command. If necessary, return to configuration mode to add or remove protocol routing on the system
or specific interfaces.
Step 5
Display the running configuration file with the show running-config command. Display the
configuration stored in NVRAM using the show startup-config command. Verify that the
configuration is accurate for the system and each interface.
If the interface is down and you configured it as up, or if the displays indicate that the hardware is not
functioning properly, ensure that the network interface is properly connected and terminated. If you still
have problems bringing the interface up, contact a service representative for assistance.
7-4
Chapter 7
Using show Commands to Display Interface Information

To display information about a specific interface, use the show interfaces command with the interface
type and port address in the format show interfaces [type slot/adapter/port].
Following is a partial-display example of how the show interfaces command displays status information
(including the physical slot and port address) for the interface you specify. In this example, most of the
status information for each interface is omitted, and an FE interface in interface processor slot 3 is
shown:
Router# sh int fastethernet 2/0/0
FastEthernet2/0/0 is administratively down, line protocol is down
Hardware is cyBus FastEthernet Interface, address is 0000.0ca5.2380 (bia 0000)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec), hdx, 100BaseTX
(additional displayed text omitted from this example)
With the show interfaces [type slot/adapter/port] command, use arguments such as the interface type
(fastethernet, and so forth) and the port number (slot/port) to display information about a specific
interface only, as in the following example of the show interfaces fastethernet command, which shows
information specific to the first FE interface on an FEIP2-DSW in interface processor slot 2:
Router# show interfaces fastethernet 2/0/0
FastEthernet2/0/0 is administratively down, line protocol is down
Hardware is cyBus FastEthernet Interface, address is 0000.0ca5.2380 (bia 0000)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec), hdx, 100BaseTX
ARP type: ARPA, ARP Timeout 4:00:00
Last input 3:08:43, output 3:08:42, output hang never
Last clearing of show interface counters 2:58:36
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Received 0 broadcasts, 0 runts, 0 giants
0 watchdog, 0 multicast
0 input packets with dribble condition detected
0 output errors, 0 collisions, 0 interface resets, 0 restarts
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
The show controllers cbus command displays information about all of the interface processors in your
router, including the FEIP2-DSW. Following is an example of the show controllers cbus command used
with a Cisco 7500 series system:
Router# show controllers cbus
MEMD at 40000000, 2097152 bytes (unused 8256, recarves 1, lost 0)
RawQ 48000100, ReturnQ 48000108, EventQ 48000110
BufhdrQ 48000128 (2357 items), LovltrQ 48000148 (6 items, 1632 bytes)
IpcbufQ 48000158 (16 items, 4096 bytes)
IpcbufQ_classic 48000150 (8 items, 4096 bytes)
3570 buffer headers (48002000 - 4800FF10)
pool0: 11 buffers, 256 bytes, queue 48000130
7-5
Chapter 7

slot2: FEIP2, hw 2.4, sw 21.40, ccb 5800FF40, cmdq 48000090, vps 8192
software loaded from system
IOS (tm) VIP Software (SVIP-DW-M), Released Version 11.1(10)CA [biff 138]
ROM Monitor version 17.0
FastEthernet2/0/0, addr 0003.0b33.f540 (bia 0003.0b33.f540)
gfreeq 48000138, lfreeq 480001C0 (1536 bytes), throttled 0
FastEthernet2/1/0, addr 0003.0b33.f548 (bia 0003.0b33.f548)
gfreeq 48000138, lfreeq 480001C8 (1536 bytes), throttled 0
The show version (or show hardware) command displays the configuration of the system hardware (the
number of each interface processor type installed), the software version, the names and sources of
configuration files, and the boot images.
Following is an example of the show version command used with a Cisco 7500 series system:
IOS (tm) GS Software (RSP-JV-M), Released Version 11.1(10)CA [biff 135]
Compiled Sun 10-May-98 06:02 by biff
Image text-base: 0x600108A0, data-base: 0x60982000
ROM: System Bootstrap, Version 11.1(2) [biff 2], RELEASE SOFTWARE (fc1)
ROM: GS Bootstrap Software (RSP-BOOT-M), Version 10.3(8), RELEASE SOFTWARE (fc2)
Router uptime is 23 minutes
System restarted by reload
System image file is biff/rsp-jv-mz, booted via tftp from 223.255.254.254
cisco RSP8 (R4600) processor with 32768K bytes of memory.
R4700 processor, Implementation 33, Revision 1.0
SuperLAT software copyright 1990 by Meridian Technology Corp).
Bridging software.
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
TN3270 Emulation software (copyright 1994 by TGV Inc).
Chassis Interface.
1 FEIP2 controller (2 FastEthernet).
2 FastEthernet/IEEE 802.3 interfaces.
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
No slave installed in slot 7.
7-6
Chapter 7
To determine which type of interfaces are installed on an FEIP2-DSW in your system, use the
show diag slot command. Specific interface information is displayed, as shown in the following
example of an FEIP2-DSW in interface processor slot 2:
Router# show diag 2
Slot 2:
Physical slot 2, ~physical slot 0xD, logical slot 2, CBus 0
Board is analyzed
FEIP2 controller, HW rev 2.4, board revision D0
Test history: 0x00
RMA number: 00-00-00
0x20: 01 20 02 04 00 38 78 0A 49 06 94 03 00 00 00 00
0x30: 68 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00
Flags: 0x4
Insertion time: 0x9B8 (00:17:10 ago)
Fast-Ethernet PA, 1 ports, 100BaseTX-ISL
EEPROM format version 1\
Fast-Ethernet PA, 1 ports, 100BaseTX-ISL
In the preceding example, the two FE interfaces on the FEIP2-DSW are clearly marked 100BaseTX.
Using the ping Command to Verify Network Connectivity

The packet internet groper (ping) command allows you to verify that an interface port is functioning
properly and to check the path between a specific port and connected devices at various locations on the
network. This section provides brief descriptions of the ping command. After you verify that the system
and FEIP2-DSW have booted successfully and are operational, you can use this command to verify the
status of interface ports.
The ping command sends an echo request out to a remote device at an IP address that you specify. After
sending a series of signals, the command waits a specified time for the remote device to echo the signals.
Each returned signal is displayed as an exclamation point (!) on the console terminal; each signal that is
not returned before the specified time-out is displayed as a period (.). A series of exclamation points
(!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed]
indicate that the connection failed.
Following is an example of a successful ping command to a remote server with the address 1.1.1.10:
Router# ping 1.1.1.10 <Return>
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echoes to 1.1.1.10, timeout is 2 seconds:
7-7
Chapter 7
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms
Router#
If the connection fails, verify that you have the correct IP address for the server and
that the server is active (powered on), and repeat the ping command.
7-8
C H A P T E R

This chapter describes how to configure attributes that pertain to the ITP at the global level. These tasks
include:
Specifying the SS7 Variant, page 1
Specifying National Options and Network Indicator, page 1
Specifying the Point Code, page 2
Specifying the SS7 Variant

The SS7 variant specifies which variation of SS7 the router is running. The variant configured on the
ITP must match the variant of the connected SS7 network. To specify one of these variants, use the
following command in global configuration mode:
Command
Purpose
Router(config)# cs7 variant {ansi | itu | china}
Specifies which SS7 variant the router is running.
Note
If you must change the variant after you have completed ITP configuration, you must
first remove all linksets and the local point-code. After reconfiguring the variant, you must
first reconfigure the point code and then the linkset.
Specifying National Options and Network Indicator

To specify the ITU national options, use the following command in global configuration mode:
Command
Purpose
Router(config)# cs7 national-options {TFR |

multiple-congestion}
Specifies ITU national options.
8-1
Chapter 8
Specifying the Point Code
The network indicator on the ITP must match the network indicator in use in the rest of the SS7 network.
ITP supports one concurrent network indicator. To specify the network indicator, use the following
command in global configuration mode:
Command
Purpose
Router(config)# cs7 network-indicator {international |

national | reserved | spare}
Specifies this network indicator.

Each signaling point (also called an SS7 node) in the SS7 network is identified with a unique address
called a point code (PC). PCs are carried in signaling messages exchanged between signaling points to
identify the source and destination of each message. Operators can assign their own PCs in private SS7
networks.
Specifying the Point Code Representation

The format of the point code can be represented according to either the ANSI, ITU, or China standard.
The ANSI and China standard for point code representation is 24 bits partitioned into 3 components that
specify network.cluster.member, with a default representation of 8.8.8. The ITU standard for point code
representation is 14 bits partitioned into 3 components that specify zone.region.signaling point (sp), with
a default point code representation of 3.8.3. The delimiter that will appear between each segment (when
you show output of the configuration) can be either a dot or a dash. You can modify the default point
code bit format and the default delimiter at any time during configuration, without prior removal of links
and linksets.
You can change the partitioning of the bits to any configuration of 1, 2, or 3 components that total the
24-bit ANSI and China standard or 14-bit ITU standard. To modify the ANSI or ITU point code format,
or to return to either standards default format, use one of the following commands in global
configuration mode:
Command
Purpose
Router(config)# cs7 point-code format 1-24 [1-23 [1-22]]

description string
Specifies the point code representation.
Router(config)# cs7 point-code format default
Resets the point-code format to the default 8.8.8

(ANSI and China) or 3.8.3 (ITU).
The default delimiter between components of the point code is a dot. To change the delimiter to a dash,
or to return to the default delimiter (dot), use one of the following commands in global configuration
mode:
Command
Purpose
Router(config)# cs7 point-code delimiter [dot | dash]
Specifies the delimiter between bits as either dots

or dashes.
Router(config)# cs7 point-code delimiter default
Resets the delimiter to dots.
8-2
Chapter 8

Specifying the Primary Local Point Code

Note
You must specify the SS7 variant before you can specify the local point code.
Each Cisco ITP must have a unique local point code that is used to send management messages to
adjacent signaling points. To specify the point code, use the following command in global configuration
mode:
Command
Purpose
Router(config)# cs7 point-code point-code
Specifies the primary point code for the ITP.
Specifying a Secondary Point Code

If you intend to configure a second linkset between the ITP and an adjacent node, you must specify a
secondary local point code. To specify the secondary point code, use the following command in global
configuration mode:
Command
Purpose
Router(config)# cs7 secondary-pc point-code
Specifies a secondary point code for the ITP.
Specifying the Capability Point Code

The ITP supports configuration of a capability point-code (CPC). Its configuration is optional, but
recommended for certain networks. The prime example for use of a CPC is when a mated pair of ITP
nodes shares the same GTT database for redundancy purposes. In this configuration, all SCCP messages
are directed to a single capable point-code; either ITP can handle the SCCP processing. The figure
below shows a mated pair of ITPs with identical capability point-codes and a common GTT database for
selecting the appropriate HLR.
Figure 1
Mated Pair of ITPs With the Same Capability Point Codes
HLR1
MSC2
HLR2
ITP
ITP
ITPA
PC=5.100.2
CPC=5.100.12
ITPB
PC=5.100.5
CPC=5.100.12
59360
MSC1
8-3
Chapter 8
In Figure 1, each of the MSCs have two routes to the mated pair of ITPs. The MSCs can either load-share
all GTT messages between the mated pair of ITPs, or use one ITP as a backup should the primary fail.
All messages requiring GTT can be routed to the same destination point-code. In this case the DPC is
the CPC, which is 5.100.12. The benefit of CPC usage in this case is that if a single ITP is unreachable,
the MSCs are unaware of this event.
To specify the capability point code, use the following command in global configuration mode:
Command
Purpose
Router(config)# cs7 capability-pc point-code
Specifies the capability point code for the ITP.
Note
The previously defined point code format must be used to enter the capability point-code.
8-4
C H A P T E R
Putting a Low Speed Link (LSL) in

Service
This chapter discusses the following tasks:
Creating a Basic Controller Configuration for the SS7 Port Adapter, page 1
Performing a Basic Data Interface Configuration, page 4
Configuring Cyclic Redundancy Checks, page 5
Configuring Linksets, page 5
Assigning Links to Linksets, page 6
Creating a Basic Controller Configuration for the SS7 Port

Adapter
Perform the following steps to create a basic controller configuration for the SS7 Port Adapter:
Step 1
Determine whether the card type (E1 or T1) has already been configured, by entering the show
controller command:
Router# show controller {e1 | t1} slot/bay/port
Step 2
Note
If the card type has not been configured, proceed to Step 2.
If the card type has been configured, skip Step 2 and proceed to Step 3.
Enable global configuration mode and configure the card type as either T1 or E1.
This process will take about 30 seconds and is disruptive to ITP operation. Therefore, a maintenance
window should be shceduled to perform this process. The process needs to be entered only once for
each SS7 port adapter at initial installation.
Router(config)# card type {e1 | t1} slot/bay
The following example specifies card type T1 for the card in slot 1 bay 0:
9-1
Chapter 9
Router(config)# card type t1 1 0
The following example specifies card type E1 for the card in slot 1 bay 0:
Router(config)# card type e1 1 0
Note
Step 3
To change the card type of the SS7 Port Adapter after the card type command has been
entered, you must remove the card from the router, save the running configuration to
NVRAM, and reboot the router. When the router has finished rebooting, reinsert the card and
repeat Step 2.
If you have not already done so, enable global configuration mode by entering the configure terminal
command:
Router(config)#
Step 4
Configure a controller on an interface and enable controller configuration mode by entering the
controller t1 or controller e1 command with the slot/bay/port interface address.
Router(config)# controller {e1 | t1} slot/bay/port
The following example specifies controller T1 for slot 6 bay 0 port 1:

Router(config)# controller t1 6/0/0
Router(config-controller)#
The following example specifies controller E1 for slot 6 bay 1 port 1:

Router(config)# controller e1 6/1/1
Router(config-controller)#
Step 5
Set the T1 framing format to either Extended Super Frame or Super Frame by entering the framing
command with either the esf or sf keyword:
Router(config-controller)# framing {esf | sf}
The following example specifies Extended Super Frame as the T1 framing format. (ESF is the
default.):
Router(config-controller)# framing esf
The following example specifies Super Frame as the T1 framing format:

Router(config-controller)# framing sf
Set the E1 framing format to either CRC4 or No CRC4 by entering the framing command with either
the crc4 or no-crc4 keyword:
Router(config-controller)# framing {crc4 | no-crc4}
The following example specifies CRC4 as the E1 framing format. (CRC4 is the default.):
Router(config-controller)# framing crc4
The following example specifies CRC4 as the E1 framing format:

Router(config-controller)# framing no-crc4
Step 6
Set the T1 line coding to either Alternate Mark Inversion (AMI) or B8ZS by entering the linecode
command with either the ami or b8zs keyword:
9-2
Chapter 9

Router(config-controller)# linecode {ami | b8zs}
The following example specifies AMI line coding for T1 (AMI is the default.):
Router(config-controller)# linecode ami
The following example specifies b8zs line coding for T1:

Router(config-controller)# linecode b8zs
Set the E1 line coding to either AMI or HDB3by entering the linecode command with either the ami or
hdb3 keyword:
Router(config-controller)# linecode {ami | hdb3}
The following example specifies AMI line coding for E1:

Router(config-controller)# linecode ami
The following example specifies HDB3 line coding for E1 (HDB3 is the default):
Router(config-controller)# linecode hdb3
Step 7
Set the clock source by enter the clock source command according to one of the following 3 variations
of the command:
Router(config-controller)# clock source internal
Router(config-controller)# clock source line primary
Router(config-controller)# clock source line secondary priority
Use the no form of this command to restore the default, which is line.
Step 8
Define the time slots that belong to each T1 or E1 circuit by entering the channel-group command:
channel-group number timeslots value {speed [56 | 64]}
The following example sets channel group 0 timeslot 12 with a speed of 64 kbps:
Router(config-controller)# channel-group 0 timeslots 12 speed 64
Note
Step 9
For T1 the channel-group number can be from 0 to 23 and the time slot value can be from 1
to 24.
For E1 the channel-group number can be from 0 to 30 and the time slot value can be from 1
to 31. The maximum number of channel groups per each eight-port SS7 Port Adapter is 127.
All channelized interfaces configured on the SS7 Port Adapter must use the same speed.
Provide a description of the controller by entering the description command with up to 80 characters,
as in the following example:
Router(config-controller)# description Arizona 3 Router; location: building 2
Step 10
Specify the cable length to increase the pulse of a signal at the receiver and decrease the pulse from the
transmitter (modify the pulse equalization and line build-out values) by entering the cablelength long
command with decibel gain and decibel loss values:
Router(config-controller)# cablelength long [gain26 | gain36] [0db | -7.5db
| -15db | -22.5db]
The following example specifies a pulse gain of 26 decibels and a decibel pulse rate of -15 decibels:
Router(config-controller)# cablelength long [gain26 | gain36] [0db | -7.5db
| -15db | -22.5db]
9-3
Chapter 9
Enter the no form of this command to restore the default, which is gain36, 0dB.
Step 11
For T1, set the Facility Data Link (FDL) exchange standard to either AT&T technical reference 54016
or ANSI T1.403 by entering the fdl command:
Router(config-controller)# fdl {ansi | att}
Use the no form of this command to disable FDL.
Note
Step 12
The fdl configuration command is not allowed in Super Frame mode.
Enter the shutdown configuration command to shut down the controller, as in the following example:
Router(config-controller)# shutdown
To exit controller configuration mode and return to global configuration mode, enter the exit command.
To exit configuration mode and return to privileged EXEC mode, use the end command or press Ctrl-Z.

This section describes how to create an SS7 interface configuration: enabling the interface and
specifying MTP2 encapsulation. You might also need to enter other configuration command, depending
on the requirements for your system configuration and the protocols you plan to route on the interface.
For complete descriptions of configuration commands and the configuration options available for serial
interfaces, refer to the appropriate software documentation.
In the following procedure, press the RETURN key after each step unless otherwise noted. At any time
you can exit the privileged level and return to the user level by entering disable at the prompt as follows:
Router# disable
Router>
Step 1
Enter configuration mode and specify that the console terminal is the source of the configuration
commands, as follows:
Router(config)#
Step 2
Configure an interface and enable interface configuration mode by entering the interface serial
command, with the slot/bay/port:channel-group address.
Router(config)# interface serial5/0/0:0
Router(config-if)#
Step 3
Configure the serial interface to use MTP2 encapsulation, as in the following example:
Router(config-if)# encapsulation mtp2
Step 4
Add any other interface commands required to enable routing protocols and adjust the interface
characteristics.
Step 5
After including all of the configuration commands to complete your configuration, press Ctrl-Zhold
down the Control key while you press Zor enter end or exit to exit configuration mode and return to
the EXEC command interpreter prompt.
9-4
Chapter 9

Step 6
Write the new configuration to NVRAM as follows:

[OK]
Router#

CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted
data. All interfaces use a 16-bit CRC (CRC-CITT) by default but also support a 32-bit CRC. The sender
of a data frame calculates the frame check sequence (FCS). Before it sends a frame, the sender appends
the FCS value to the message. The receiver recalculates the FCS and compares its calculation to the FCS
from the sender. If there is a difference between the two calculations, the receiver assumes that a
transmission error occurred and sends a request to the sender to resend the frame.
Enable interface configuration mode and configure CRC on a serial interface.
The following example enables 32-bit CRC on a serial interface:
Router(config)# interface serial 3/0:0
Router(config-if)# crc 32
The following example disables 32-bit CRC on a serial interface and returns to the default 16-bit CRC:
Router(config)# interface serial 3/0:0
Router(config-if)# no crc 32
When you have finished, press Ctrl-Zhold down the Control key while you press Zor enter end or
exit to exit configuration mode and return to the EXEC command interpreter prompt. Then write the new
configuration to NVRAM using the copy running-config startup-config command.
Note
You must specify the SS7 variant and the point code before you can configure linksets.
A link is either a serial or ATM interface or a peer (virtual link) to a remote Cisco ITP node. Multiple
links are grouped in a linkset. Each link must be assigned to one linkset and multiple links can be
assigned to the linkset. Links within the same linkset must be parallel between the same nodes.
To configure a linkset you must name the linkset and specify the point code of the adjacent signaling
point. To specify a linkset, use the following command in global configuration mode:
Command
Purpose
Router(config)# cs7 linkset ls-name adjacent-point-code
Specifies a linkset to an adjacent node and enters

linkset configuration mode.
9-5
Chapter 9

After specifying linksets, you can assign links to the linkset. You will assign links to adjacent legacy SS7
devices as well as links to adjacent Cisco ITP peer nodes.
Traditional SS7 Links

You must configure a link to the legacy SS7 devices. To configure an SS7 link within a linkset, make
sure that the interface encapsulation is MTP2, then use the following command in linkset configuration
mode:
Command
Purpose
Router(config-cs7-ls)# link slc serial number
Configures an SS7 link within a linkset and enters

CS7 link configuration mode.
9-6
C H A P T E R
10
Putting a High Speed Link (HSL) in

Service
Note
HSL allows full bandwidth utilization of a 1.55Mbps T1 or a 2.048 Mbps E1 for a single SS7 link.
ITP HSL is compliant with both ANSI per Telcordia GR-2878-CORE and ITU per Q.2100 and
includes the following protocol stack components: AAL5, SSCOP, SSCF-NNI and MTP3b.
ATM HSL is supported on the Cisco 7500 router.
ATM is supported on the Loki 8 port T1/E1 port adapter with IMA support (PA-A3-8T1IMA).
ITP ATM HSL capability provides broadband SS7 support. HSL capability can be used to replace the
traditional MTP1 and MTP2 layers of the SS7 protocol stack with SAAL, to provide ATM at DS1 rates.
The following sections describe the required and optional tasks for configuring an ITP for ATM HSL
support:
Enabling an ATM Interface, page 1 (Required)
Configuring a Permanent Virtual Circuit (PVC), page 4 (Required)
Configuring SSCF, page 4 (Optional)
Configuring SSCOP, page 5 (Optional)
Configuring Linksets, page 9 (Required)
Assigning Links to Linksets, page 9 (Required)

Following are instructions for a basic configuration. You might also need to enter other configuration
subcommands, depending on the requirements for your system configuration and the protocols you plan
to route on the interface. For complete descriptions of configuration subcommands and the configuration
options available for ATM interfaces, refer to the appropriate software documentation.
Step 1
subcommands, as follows:
Router(config)#
10-1
Chapter 10
Step 2
Specify the first interface to configure by entering the interface atm subcommand, followed by the
interface address of the interface you plan to configure:
Router(config)# interface atm slot/bay/port
The following example specifies an ATM interface in slot 1 bay 1 port 0 and enables interface
configuration mode:
Router(config)# interface atm 1/1/0
Router(config-if)#
Note
Step 3
When the PA-A3-IMA port adapter comes up for the first time, all ports come up in ATM UNI
mode.
Set the type of framing used by the port to either Extended Super Frame (ESF) or Super Frame (SF) by
entering the framing command with either the esf or sf keyword.
Router(config-controller)# framing {esf | sf}
The following example specifies Extended Super Frame as the T1 framing format. (ESF is the
default.):
Router(config-controller)# framing esf
The following example specifies Super Frame as the T1 framing format:

Router(config-controller)# framing sf
Set the E1 framing format to either CRC4 or No CRC4 by entering the framing command with either
the crc4 or no-crc4 keyword:
Router(config-controller)# framing {crc4 | no-crc4}
The following example specifies CRC4 as the E1 framing format. (CRC4 is the default.):
Router(config-controller)# framing crc4
The following example specifies CRC4 as the E1 framing format:

Router(config-controller)# framing no-crc4
Step 4
Configure transmit attenuation and cable length for applicable T1 links using the lbo configuration
command.
Router(config-if)# lbo {long {gain26 | gain36} {-15db | -22.5db | -7.5db | 0db} | short
{133 | 266 | 399 | 533 | 655}}
The following example sets the cable length to long and the gain to 26 dB, with a 15 dB pulse:
Router(config-if)# lbo long gain26 -15db
Note
Each T1 port can operate in long-haul or short-haul mode. In long-haul mode, the user must
specify the gain and the line build-out. The default value is long-haul with gain 26 dB and 0 dB
line build-out. In short-haul mode, the user must specify the cable length in feet. The range is
from 0 to 655 feet. The actual mapping is shown in Table 10-1 below.
10-2
Chapter 10

Table 10-1 Mapping of Cable Length Values to Range
Step 5
Cable Length Range
Value
0 to 133 ft. (0 to 39.9 m)
133
133 to 266 ft. (39.9 to 79.8 m)
266
266 to 399 ft. (79.8 to 119.7 m)
399
399 to 533 ft. (119.7 to 159.9 m)
533
533 to 655 ft. (159.9 to 196.5 m)
655
Set the clock source by enter the clock source command according to one of the following 3 variations
of the command:
Router(config-controller)# clock source internal
Router(config-controller)# clock source line primary
The following example sets the clock source to internal:

Router(config-if)# clock source internal
Use the no form of this command to restore the default, which is line.
Step 6
Set the line code of the port using the linecode command. The example below sets the line code of a T1
port to alternate mark inversion (AMI):
Router(config-if)# linecode ami
The default values are b8zs for T1 and hdb3 for E1.
Step 7
On T1 ports with ESF framing, use the fdl command to enable Facility Data Link (FDL) performance
reporting. The default value is no fdl. The example below selects ANSI T1.403 for Facility Data Link
support.
Router(config-if)# fdl ansi
Step 8
On E1 ports, set the national and international reserve bits using the national reserve command as in
the example below:
Router(config-if)# national reserve 0 1 1 1 1 0
The default values are 1 1 1 1 1 1 1.

Step 9
To enable cell payload scrambling, use the scrambling command. The default value is no scrambling.
Router(config-if)# scrambling cell-payload
Step 10
Set the maximum transmission unit (MTU) size. The range is 64 through 9188 bytes. The default is 4470
bytes. Use the mtu command in interface configuration mode to change the maximum MTU packet size,
as shown in the following example:
Router(config-if)# mtu 5260
Step 11
Change the shutdown state to up and enable the interface:

Router(config-int)# no shutdown
Step 12
Repeat Step 2 through Step 10 to configure additional interfaces as required.
10-3
Chapter 10
Note
You do not have to perform Step 3 through Step 10 for each port if the default values are
acceptable.
Step 13
When you have included all of the configuration subcommands to complete the configuration, press
Ctrl-Z to exit configuration mode.
Step 14
Write the new configuration to NAVRAM:

[OK]
Router#
For more information about ATM commands, see the ATM Commands section of the Cisco IOS
Wide-Area Networking Command Reference, Release 12.2 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fwan_r/atmcmds/index.htm

You must configure one permanent virtual circuit (PVC) on the ATM interface before you can define the
interface as a link. To configure the PVC, use the following commands, beginning in interface
configuration mode:
Command
Purpose
Step 1
Router(config-if)# pvc name {vpi | vci} qsaal
Specifies the PVC. (The default/recommended PVC number

is 0/5.)
Step 2
Router(config-if)# atm nni
Selects Service Specific Coordination Function for Network

Node Interface.
Configuring SSCF
The SSCF NNI provides mapping of the services provided by SSCOP and of the SAAL to the ULP, in
this case MTP3. To vary the operating parameters of SSCF NNI, use the following commands in
interface configuration mode:
Command
Purpose
Router(config-if)# sscf-nni n1 number
Sets the number of PDUs sent during proving.
Router(config-if)# sscf-nni T1-timer seconds
Sets the link re-establishment time.
Router(config-if)# sscf-nni T2-timer seconds
Sets the alignment time-out.
Router(config-if)# sscf-nni T3-timer milli-seconds
Sets the proving PDU interval timer.
Router(config-if)# sscf-nni no-credit seconds
Sets SSCOP no-credit timer value.
10-4
Chapter 10

Configuring SSCOP
Command
Purpose
Router(config-if)# sscf-nni nrp number
Sets the maximum number of retransmissions allowed during

proving.
Router(config-if)# sscf-nni sscop-recovery minutes
Sets the SSCOP recovery timer.
Configuring SSCOP
The Service-Specific connection -Oriented Protocol (SSCOP) resides in the service-specific
convergence sublayer (SSCS) of the ATM adaptation layer (AAL). SSCOP is used to transfer
variable-length service data units (SDUs) between users of SSCOP. SSCOP provides for the recovery of
lost or corrupted SDUs.
To configure SSCOP parameters use the following commands in interface configuration mode:
Command
Purpose
Router(config-if)# sscop poll-timer milli-seconds
Sets the poll timer.
Router(config-if)# sscop keepalive-timer

milli-seconds
Sets the keepalive timer.
Router(config-if)# sscop idle-timer milli-seconds
Sets the idle timer
Router(config-if)# sscop noResponse-timer

milli-seconds
Sets the No Response timer.
Router(config-if)# sscop cc-timer milli-seconds
Sets the Connection Control timer.
Router(config-if)# sscop max-cc retries
Changes the retry count of the Connection Control timer

default value of ten.
Router(config-if)# sscop send-window packets
Changes the transmitter window default of 30.
Router(config-if)# sscop receive-window packets
Changes the receiver window default of 30.

After configuring the new interface, use the show commands to display the status of the new interface
or all interfaces, and use the ping and loopback commands to check connectivity. This section includes
the following subsections:
Using show Commands to Verify the New Interface Status, page 6
Using loopback Commands, page 7
Checking Bit Errors Using a Bit Error Rate Test, page 8
Using the debug ATM Commands, page 8
10-5
Chapter 10

Table 10-2 demonstrates how you can use the show commands to verify that new interfaces are
configured and operating correctly and that the PA-A3-IMA appears in them correctly. Sample displays
of the output of selected show commands appear in the sections that follow. Table 10-3 demonstrates
how you can use the ATM show commands to verify the current state of the ATM network and connected
virtual circuits.
Table 10-2 Using show Commands
Command
Function
Example
show diag slot
Displays types of port adapters

installed in your system and
information about a specific port
adapter slot, interface processor slot,
or chassis slot
Router# show diag 2
show interfaces atm

interface-processor-slot-number/port-adapterslot-number/interface-port-number
Displays status information about an

ATM interface on a VIP2 or VIP 4 in
a Cisco 7500 series router
Router# show interfaces atm

3/1/0
show running-config
Displays the running configuration

file
show startup-config
Displays the configuration stored in

NVRAM
Command
Function
Example
show atm traffic
Displays information about global

traffic to and from all ATM networks
connected to the router. Displays a
list of counters of all ATM traffic on
this router.
Router# show atm traffic
show sscop atm
Displays Service Specific

Connection-Oriented Protocol
(SSCOP) details for an ATM
interface.
Router# show sscop atm 1/ima1
show atm interface atm slot/ima

group-number
Displays port adapter-specific error

statistics, such as CRC errors, giants
received, no buffers available,
framing errors, application or
physical layer errors, and packet
timeout errors on receive.
Router# show interfaces atm

1/ima1
Table 10-3 Using ATM show Commands
If an interface is shut down and you configured it as up, or if the displays indicate that the hardware is
not functioning properly, ensure that the interface is properly connected and terminated. If you still have
problems bringing up the interface, contact a service representative for assistance. This section includes
the following subsections:
Using the show diag Command, page 7
10-6
Chapter 10

Using the show diag Command

Display the types of port adapters installed in your system (and specific information about each) using
the show diag slot command, where slot is the interface processor slot in a Cisco 7500 series router with
a VIP4.
Note
The outputs that appear in this document may not match the output you receive when running these
commands. The outputs in this document are examples only.
VIP4 in Cisco 7500 Series Routers

Following is an example of the show diag slot command that shows a PA-A3-IMA in port adapter
slot 0 on a VIP2 in interface processor slot 4:
Router# show diag 4
Slot 4:
Physical slot 4, ~physical slot 0xB, logical slot 4, CBus 0
Board is analyzed
Pending I/O Status:None
VIP2 controller, HW rev 2.11, board revision C0
Serial number:11208804 Part number:73-1684-04
Test history:0x00
RMA number:00-00-00
Flags:cisco 7000 board; 7500 compatible
Using loopback Commands

With the loopback test, you can detect and isolate equipment malfunctions by testing the connection
between the PA-A3-IMA interface and a remote device such as a modem or a CSU/DSU. The loopback
command places an interface in loopback mode, which enables test packets that are generated from the
ping command to loop through a remote device. If the packets complete the loop, the connection is good.
If not, you can isolate a fault to the remote device in the path of the loopback test.
The PA-A3-IMA supports three basic variations of loopback: diagnostic, local, and remote. The
diagnostic variation loops the outgoing transmit signal back to incoming receive, and local loopback
loops the incoming receive signal back out the transmitter. Remote loopback attempts to set the far end
of the T1 interface into loopback mode.
Note
E1 does not support remote loopback.

Depending on the mode of the port, issuing the loopback command checks the following path:
When no compact serial cable is attached to the PA-A3-IMA interface port, or if a DCE cable is
attached to a port that is configured as line protocol up, the loopback command tests the path
between the network processing engine and the interface port only (without leaving the network
processing engine and port adapter.)
When a DTE cable is attached to the port, the loopback command tests the path between the network
processing engine and the near (network processing engine) side of the DSU or modem to test the
PA-A3-IMA interface and compact serial cable.
10-7
Chapter 10
Checking Bit Errors Using a Bit Error Rate Test

To check bit errors using a bit error rate test (BERT), use the following command:
interface atm1/0 bert pattern
{2^11 | 2^15 | 2^20 O.153 | 2^20 QRSS | 2^23 | 0s | 1s | alt-0-1} interval minutes
Here 2^11 is an exponential number that represents a pseudorandom repeating pattern that is 2048 bits
long, 2^15 is an exponential number that represents a pseudorandom repeating pattern that is 32,767 bits
long, 2^20 is a pseudorandom repeating pattern that is 1,048,575 bits long, 2^23 is a pseudorandom
repeating pattern that is 8,388,607 bits long, 0s is a pattern of all zeros (00000000...), 1s is a pattern of
all 1s (111111...), and minutes is a value 114,400, which designate the time the BERT will run. To stop
the BERT, use the optional no form of the command.
In the following example, the pseudorandom pattern 2^20 is sent and repeats for 60 minutes:
Router# bert pattern 2^20 interval 60
The following is an example of running the BERT and displaying the results from a Cisco 7200 series
router:
Router(config)# interface atm 1/0
Router(config-if)# bert pattern 2^20 interval 1
Router(config-if)# end
Router# show controller atm 1/0
Interface ATM1/0 is up
Hardware is IMA PA - E1 (2Mbps)
Lane client mac address is 0090.b1f8.e454
Framer is PMC PM7344, SAR is LSI ATMIZER II
Firmware rev:DG01, ATMIZER II rev:3
idb=0x61C03C58, ds=0x61C0B480, vc=0x61C2C860, pa=0x61BF9880
slot 3, unit 1, subunit 0, fci_type 0x00BB, ticks 658
400 rx buffers:size=512, encap=64, trailer=28, magic=4
linecode is HDB3
E1 Framing Mode: crc.4 adM format
LBO (Cablelength) is long gain43 120db
Facility Alarms:
No Alarm
Bert Information:
state
interval
sync count
kbit count
bit errors
kbit count
:OFF, pattern
:0,
result
:1,
bit errors
:122871
since last sync
since last sync
:2^20
:IN_SYNC
:0
:0
:122871
Some display text omitted.
Using the debug ATM Commands

The following debug commands are available to aid in solving ATM network problems.
To create a dump of all protocol packets, use the debug atm packet command. The command displays
the contents of the Subnetwork Access Protocol/Network Layer Protocol Identifier/Switched
Multimegabit Data Service (SNAP/NLPID/SMDS) header followed by the first 40 bytes of a packet in
hexadecimal format.
10-8
Chapter 10

To display ATM errors, use the debug atm errors command. The command displays information from
all detected ATM errors. This includes such errors as encapsulation failures and errors during ATM
configuration.
To display ATM events, use the debug atm events command. The command displays event changes to
the IMA port adapter. The command also shows reset, VC configurations, and PA-A3-IMA
configurations.
To display information about OAM cells, use the debug atm oam command. The command displays the
contents of OAM cells as they arrive from the network.
After using a debug command, turn off debugging with the no debug command.
Note
You must specify the SS7 variant and the point code before you can configure linksets.
A link is either a serial or ATM interface or a peer (virtual link) to a remote Cisco ITP node. Multiple
links are grouped in a linkset. Each link must be assigned to one linkset and multiple links can be
assigned to the linkset. Links within the same linkset must be parallel between the same nodes.
To configure a linkset you must name the linkset and specify the point code of the adjacent signaling
point. To specify a linkset, use the following command in global configuration mode:
Command
Purpose
Router(config)# cs7 linkset ls-name adjacent-point-code
Specifies a linkset to an adjacent node and enters

linkset configuration mode.

After specifying linksets, you can assign links to the linkset. You will assign links to adjacent legacy SS7
devices as well as links to adjacent Cisco ITP peer nodes.
High-Speed Signaling Links

You must configure a link to HSL devices. To configure an HSL link within a linkset, make sure that the
ATM interface has NNI selected and a QSAAL PVC defined, then use the following command in linkset
configuration mode:
Command
Purpose
Router(config-cs7-ls)# link slc atm number
Configures a link to an HSL device and enters CS7

link configuration mode.
10-9
Chapter 10
10-10
C H A P T E R
11

Before you disable and remove an SS7 Port Adapter (SS7 PA) from an ITP, you must identify and take
out of service (inhibit and shut down) all the links using that port adapters interfaces. This procedure
describes the steps to inhibit and shut down the links and controllers of an SS7 PA before you can
physically remove the VIP from the ITP.
Note
This procedure requires a fully redundant ITP deployment where all linksets have at least two links
and those links are connected on at least two different VIP cards. If there is a single link in a linkset
or if all links in a linkset are connected to the same VIP, it is not possible to inhibit all links. Inhibiting
all links before disabling them (with shutdown) is a safeguard that allows the ITP to ensure that no
destinations become inaccessible while the port adapters is out of service. Inhibiting a link will fail
for either of the following reasons:
- A destination point code becomes inaccessible due to a missing or unavailable backup route.
- A destination point code becomes unavailable but a different link to the same destination is already
inhibited. In this case the other link is automatically uninhibited and put back into service.
One workaround to this situation is to first inhibit all A-links, then inhibit as many C/D links as
possible then, last, shut down the C-links.

You can display information about all links (and the linksets and interfaces with which they are
associated) by using the show cs7 linkset privileged EXEC command. This section first shows how to
display the information and then describes how to use the output to identify the interfaces, linksets, and
links associated with the SS7 PA you intend to disable.
Step 1
Display information about all linksets on an ITP by issuing the show cs7 linkset command in privileged
EXEC mode:
Command
Purpose
Router# show cs7 linkset
Displays the status of all interfaces with linksets

and links.
11-1
Chapter 11
The output of the show cs7 linkset command is a display of information about all linksets in the ITP
configuration. The information is organized by linkset name. You can identify the links associated with
a specific SS7 PA (the links that must be disabled before you remove the SS7 PA from the ITP) by
examining 3 fields of the display: Interface, Signaling Link Code (SLC), and linkset name (lsn).
An example of show cs7 linkset output is provided below. For the purposes of this example, assume that
the SS7 PA to be removed is located in slot 0 bay 1 of the ITP.
Note
Step 2
A typical configuration would include many linksets and the output of the show cs7 linkset command
typically would be much longer than the excerpt shown in the following example. This example
excerpts only partial output to represent in a short space how information for a number of linksets is
displayed.
Router#show cs7 linkset
lsn=sctp-10
apc=2.10.2
SLC Interface
00
172.18.58.78 21030 21030
01
172.18.58.78 21010 21010
02
172.18.58.78 21020 21020
04
172.18.58.78 21040 21040
state=avail
available/links=4/4
Service
PeerState
Inhib
avail
InService
----avail
InService
----avail
InService
----avail
InService
-----
lsn=ss7-1
apc=1.1.1
SLC Interface
00
Serial0/1/0:0
01
Serial0/1/0:1
02
Serial0/1/1:2
03
Serial0/1/1:3
04
Serial0/1/2:4
05
Serial0/1/2:5
06
Serial0/1/3:6
07
Serial0/1/3:7
08
Serial0/1/4:8
09
Serial0/1/4:9
10
Serial0/1/5:10
11
Serial0/1/5:11
12
Serial0/1/6:12
13
Serial0/1/6:13
14
Serial0/1/7:14
15
Serial0/1/7:15
state=avail
available/links=16/16
Service
PeerState
Inhib
avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
-------------
lsn=ss7-2
apc=1.2.1
SLC Interface
00
Serial2/1/0:0
01
Serial2/1/0:1
02
Serial2/1/0:2
03
Serial2/1/0:3
state=avail
Service
PeerState
Inhib
avail
------------avail
------------avail
------------avail
-------------
To identify the links associated with a specific SS7 PA, search the Interface field under each lsn until
you find the serial interfaces that match the physical slot and bay where the SS7 PA is located. (In our
example scenario the SS7 PA is located in slot 0 bay 1.) When you locate the interfaces, note the lsn
under which they are listed, and note the list of Signaling Link Codes (SLCs). You will need this
information to disable the links.
Some review of SS7 PA configuration and ITP configuration might be needed to understand the
relationship between the physical location of the SS7 PA and the serial interfaces. If so, read the
following paragraph. If not, proceed to the Disabling Links Associated with an SS7 PA section on
page 3
11-2
Chapter 11

In our example scenario we said that the SS7 PA to be removed is located in slot 0 of the ITP, in
bay1 of the VIP. When the SS7 PA was configured, the controller command was configured for each
of the 8 interface ports (0 - 7) on the SS7 PA. Configuring the controller for an SS7 PA interface port
specifies T1 or E1 and automatically creates 16 serial interfaces (0 - 15) for the port. So, in our
example there are 16 serial interfaces for each port, Serial0/1/0:{0-15} through Serial0/1/7:{0-15},
for a maximum of 128 serial interfaces. Some of these serial interfaces were associated with
signaling link codes (SLC) as links within linksets that point to nodes at adjacent point codes. The
sample output shows a set of serial interfaces listed under lsn ss7-1 that match the range of serial
interfaces for the SS7 PA in slot 0 bay 1.

The previous section described how to display and identify the links associated with the SS7 PA that you
intend to take out of service. This section describes how to disable the links.
Step 1
To ensure that backup routes are available before taking links out of service, inhibit all links by using
the cs7 inhibit command in privileged EXEC mode:
Command
Purpose
Router# cs7 inhibit lsn slc
Makes or keeps a signaling link unavailable to

user-generated signaling traffic.
Step 2
Enter global configuration mode by issuing the configure terminal command in privileged EXEC mode:
Command
Purpose
Enters global configuration mode.
Step 3
In the previous section of this chapter, Identifying Links Associated with an SS7 PA, you used the
show cs7 linkset command to display all linksets (and their associated links and interfaces). You
identified and noted the linkset name (lsn) and all the Signaling Link Codes (SLCs) associated with the
SS7 PA that you intend to take out of service. Specify the linkset that contains the links you intend to
shut down by issuing the cs7 linkset command in global configuration mode.
Command
Purpose
Router(config)# cs7 linkset lsn
Specifies a linkset and enables linkset

configuration mode.
Step 4
Beginning in linkset configuration mode, disable all links associated with the SS7 PA that you intend to
take out of service by repeating the following commands for each link:
Command
Purpose
Router(config-ls)# link slc
Specifies the link that you intend to take out of

service. Enables link configuration mode.
11-3
Chapter 11
Command
Purpose
Router(config-ls-link)# shutdown
Disables the link.
Router(config-ls-link)# exit
Exits link configuration mode and enables linkset

configuration mode.
Note
Repeat the above steps until all the links have been disabled, then use the exit command until you
return to global configuration mode.

After you have disabled all the links associated with the SS7 PA that you intend to take out of service,
you can disable the controller. Disabling the controller will shut down all interfaces using that controller.
To disable the controller, use the following commands, beginning in global configuration mode.
Command
Purpose
Step 1
Router(config)# controller {t1 | e1} slot/bay/port
Enable controller configuration mode.
Step 2
Shuts down all interfaces using that controller.
The SS7 PA can now be removed.
11-4
C H A P T E R
12

Before you disable and remove a High Speed Link Port Adapter (HSL PA) from an ITP, you must
identify and take out of service (inhibit and shut down) all the links using that port adapters interfaces.
This chapter describes the steps to inhibit and shut down the links and interfaces of an HSL PA before
you physically remove the HSL PA.

display the information and then describes how to use the output to identify the interfaces, linksets, and
links associated with the HSL PA you intend to disable.
Step 1
EXEC mode:
Command
Purpose

and links.
a specific HSL PA (the links that must be disabled before you remove the HSL PA from the ITP) by
examining 3 fields of the display: Interface, Signaling Link Code (SLC), and linkset name (lsn).
the HSL PA to be removed is located in slot 9 bay 0 of the ITP.
Note
displayed.
12-1
Chapter 12

lsn=stp2
apc=229.202.0
SLC Interface
00
ATM9/0/2
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
-------------
lsn=itp2
apc=229.205.0
SLC Interface
00
141.204.148.222 4096 4096
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
InService
-----
lsn=stp1
SLC Interface
00
ATM9/0/1
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
-------------
apc=229.201.0
lsn=wosgw
apc=229.55.110
SLC Interface
00
Serial8/1/1:1
01
Serial8/1/1:0
itp1#
Step 2
state=avail
available/links=2/2
Service
PeerState
Inhib
avail
------------avail
-------------
To identify the links associated with a specific HSL PA, search the Interface field under each lsn until
you find the atm interfaces that match the physical slot and bay where the HSL PA is located. When you
locate the interfaces, note the lsn under which they are listed, and note the list of Signaling Link Codes
(SLCs). You will need this information to disable the links.
In our example scenario the HSL PA is located in slot 9 bay 0. The show output for the example shows
two linksets (stp2 and stp1) with links associated with the ATM adapter in slot 9 bay 0. In our example
scenario we would note that link 0 in linkset stp2 and link 0 in stp2 must be disabled.

The previous section described how to display and identify the links associated with the HSL PA that
you intend to take out of service. This section describes how to disable the links.
Step 1
Command
Purpose

Step 2
Enter global configuration mode by issuing the configure terminal in privileged EXEC mode:
Command
Purpose
12-2
Chapter 12

Step 3
In the previous section of this chapter, Identifying Links Associated with an HSL PA, you used the
show cs7 linkset command to display all linksets (and their associated links and interfaces). You
identified and noted the linkset name (lsn) and all the Signaling Link Codes (SLCs) associated with the
HSL PA that you intend to take out of service. Specify the linkset that contains the links you intend to
shut down by issuing the cs7 linkset command in global configuration mode.
Command
Purpose

configuration mode.
Step 4
Beginning in linkset configuration mode, disable all links associated with the HSL PA that you intend to
take out of service by repeating the following commands for each link:
Command
Purpose

Disables the link.
Router(config-ls-link)# exit
Exits link configuration mode and enables linkset

configuration mode.
Note
Repeat the above steps until all the links have been disabled, then use the exit command until you
return to global configuration mode.

To disable the ATM interface, use the following commands, beginning in global configuration mode.
Command
Purpose
Step 1
Router(config)# interface atm number
Specifies the interface that you intend to take out

of service and enables interface configuration
mode.
Step 2
Router(config-if)# shutdown
Shut down the interface.
12-3
Chapter 12
12-4
C H A P T E R
13

This chapter describes the steps to shut down a link associated with an SS7 PA.
If you already know the Signaling Link Code (SLC) of the link you intend to shut down, the name
of the linkset that contains the link, and the interface, skip to the Disabling a Link Associated with
an SS7 PA section on page 3.
If you need instructions on how to identify the SLC of the link you intend to shut down or the name
of the linkset that contains the link, continue reading the following sections.

display the information and then describes how to use the output to identify the SLC of the link you
intend to disable.
Step 1
EXEC mode:
Command
Purpose

and links.
a specific SS7 PA by examining 3 fields of the display: Interface, Signaling Link Code (SLC), and
linkset name (lsn).
the link you intend to remove is associated with the SS7 PA located in slot 0 bay 1 of the ITP.
Note
displayed.
13-1
Chapter 13
Step 2

lsn=sctp-10
apc=2.10.2
SLC Interface
00
172.18.58.78 21030 21030
01
172.18.58.78 21010 21010
02
172.18.58.78 21020 21020
04
172.18.58.78 21040 21040
state=avail
available/links=4/4
Service
PeerState
Inhib
avail
InService
----avail
InService
----avail
InService
----avail
InService
-----
lsn=ss7-1
apc=1.1.1
SLC Interface
00
Serial0/1/0:0
01
Serial0/1/0:1
02
Serial0/1/1:2
03
Serial0/1/1:3
04
Serial0/1/2:4
05
Serial0/1/2:5
06
Serial0/1/3:6
07
Serial0/1/3:7
08
Serial0/1/4:8
09
Serial0/1/4:9
10
Serial0/1/5:10
11
Serial0/1/5:11
12
Serial0/1/6:12
13
Serial0/1/6:13
14
Serial0/1/7:14
15
Serial0/1/7:15
state=avail
Service
PeerState
Inhib
avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
------------avail
-------------
lsn=ss7-2
apc=1.2.1
SLC Interface
00
Serial2/1/0:0
01
Serial2/1/0:1
02
Serial2/1/0:2
03
Serial2/1/0:3
state=avail
Service
PeerState
Inhib
avail
------------avail
------------avail
------------avail
-------------
To identify the links associated with a specific SS7 PA, search the Interface field under each lsn until
you find the serial interfaces that match the physical slot and bay where the SS7 PA is located. (In our
example scenario the SS7 PA is located in slot 0 bay 1.) When you locate the interfaces, note the lsn
under which they are listed, and note the list of Signaling Link Codes (SLCs). You will need this
information to disable the links.
Some review of SS7 PA configuration and ITP configuration might be needed to understand the
relationship between the physical location of the SS7 PA and the serial interfaces. If so, read the
following paragraph. If not, proceed to the Disabling a Link Associated with an SS7 PA section on
page 3
In our example scenario we said that the SS7 PA to be removed is located in slot 0 of the ITP, in
bay1 of the VIP. When the SS7 PA was configured, the controller command was configured for each
of the 8 interface ports (0 - 7) on the SS7 PA. Configuring the controller for an SS7 PA interface port
specifies T1 or E1 and automatically creates 16 serial interfaces (0 - 15) for the port. So, in our
example there are 16 serial interfaces for each port, Serial0/1/0:{0-15} through Serial0/1/7:{0-15},
for a maximum of 128 serial interfaces. Some of these serial interfaces were associated with
signaling link codes (SLC) as links within linksets that point to nodes at adjacent point codes. The
sample output shows a set of serial interfaces listed under lsn ss7-1 that match the range of serial
interfaces for the SS7 PA in slot 0 bay 1.
13-2
Chapter 13


The previous section described how to display and identify the SLC of the link that you intend to shut
down. This section describes how to disable the link.
Step 1
Command
Purpose

Note
Step 2
You can not inhibit the last link (or the only link) in a linkset; you will receive an error message
indicating that the inhibit was denied. However, you can shut down the link. If you choose to shut
down the link, continue this procedure at Step 2.
Command
Purpose
Step 3
Specify the linkset that contains the link you intend to shut down by issuing the cs7 linkset command in
global configuration mode.
Command
Purpose

configuration mode.
Step 4
Disable the link by issuing the following commands, beginning in linkset configuration mode:
Command
Purpose

Disables the link.
If you intend to shut down more than one link in the linkset, issue the exit command from link
configuration mode to return to linkset configuration mode, then repeat the above two commands.
Note
A link can be brought back into the active state with the no shutdown command only if its
parent linkset is in the active state.
13-3
Chapter 13
13-4
C H A P T E R
14

This chapter describes the steps to shut down a high speed link (HSL) associated with an HSL PA.
If you already know the Signaling Link Code (SLC) of the link you intend to shut down, the name
of the linkset that contains the link, and the interface, skip to the Disabling a Link Associated with
an HSL PA section on page 2.
If you need instructions on how to identify the SLC of the link you intend to shut down or the name
of the linkset that contains the link, continue reading the following sections.

display the information and then describes how to use the output to identify the SLC of the link you
intend to disable.
Step 1
EXEC mode:
Command
Purpose

and links.
a specific HSL PA by examining 3 fields of the display: Interface, Signaling Link Code (SLC), and
linkset name (lsn).
the link you intend to shut down is associated with the HSL PA located in slot 9 bay 0 of the ITP.
Note
displayed.
14-1
Chapter 14

lsn=stp2
apc=229.202.0
SLC Interface
00
ATM9/0/2
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
-------------
lsn=itp2
apc=229.205.0
SLC Interface
00
141.204.148.222 4096 4096
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
InService
-----
lsn=stp1
SLC Interface
00
ATM9/0/1
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
-------------
apc=229.201.0
lsn=wosgw
apc=229.55.110
SLC Interface
00
Serial8/1/1:1
01
Serial8/1/1:0
itp1#
Step 2
state=avail
available/links=2/2
Service
PeerState
Inhib
avail
------------avail
-------------
To identify the links associated with a specific HSL PA, search the Interface field under each lsn until
you find the atm interfaces that match the physical slot and bay where the HSL PA is located. When you
locate the interfaces, note the lsn under which they are listed, and note the of Signaling Link Codes
(SLC) of the link you intend to shut down. You will need this information to disable the links

The previous section described how to display and identify the SLC of the link you intend to take out of
service. This section describes how to disable the link.
Step 1
Command
Purpose

Note
Step 2
You can not inhibit the last link (or the only link) in a linkset; you will receive an error message
indicating that the inhibit was denied. However, you can shut down the link. If you choose to shut
down the link, continue this procedure at Step 2.
Command
Purpose
14-2
Chapter 14

Step 3
Specify the linkset that contains the links you intend to shut down by issuing the cs7 linkset command
in global configuration mode.
Command
Purpose

configuration mode.
Step 4
Disable the link by issuing the following commands, beginning in linkset configuration mode:
Command
Purpose
Router(config-ls)# link

Disables the link.
If you intend to shut down more than one link in the linkset, issue the exit command from link
configuration mode, then repeat the above two commands.
Note
A link can be brought back into the active state with the no shutdown command only if its
parent linkset is in the active state.
14-3
Chapter 14
14-4
C H A P T E R
15

This chapter describes the procedure to shut down a linkset.
If you already know the linkset name (lsn) of the linkset you intend to take out of service, skip to
Step 2 of the procedure.
If you need instructions on how to identify the lsn of the linkset you intend to shut down, continue
reading from here.

You can display information about all linksets by using the show cs7 linkset privileged EXEC command.
This section first shows how to display the information and then describes how to use the output to
identify the linkset you intend to disable.
Step 1
EXEC mode:
Command
Purpose

and links.
configuration. The information is organized by linkset name. An example of show cs7 linkset output is
provided below.
Note
displayed.
lsn=stp2
apc=229.202.0
SLC Interface
00
ATM9/0/2
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
-------------
15-1
Chapter 15
lsn=itp2
apc=229.205.0
SLC Interface
00
141.204.148.222 4096 4096
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
InService
-----
lsn=stp1
SLC Interface
00
ATM9/0/1
state=avail
available/links=1/1
Service
PeerState
Inhib
avail
-------------
apc=229.201.0
lsn=wosgw
apc=229.55.110
SLC Interface
00
Serial8/1/1:1
01
Serial8/1/1:0
itp1#
state=avail
available/links=2/2
Service
PeerState
Inhib
avail
------------avail
-------------
Make a note of the lsn of the linkset you intend to disable. You will need this information to shut down
the linkset.
Step 2
To disable a linkset, use the following commands, beginning in privileged EXEC mode:
Command
Purpose
Specifies the linkset that you intend to take out of

service and enables linkset configuration mode.
Router(config-ls)# shutdown
Disables the linkset.
15-2
C H A P T E R
16
MTP3 Routes
This chapter describes the following tasks:
Specifying the Cisco ITP Route Table, page 1
Specifying the Default Route Table, page 1
Loading the Route Table Contents, page 1
Adding Routes to the Route Table, page 2
Saving the Route Table, page 2
Specifying the Cisco ITP Route Table

The Cisco ITP uses a route table to select the appropriate signaling path for each message, or signal unit,
that it must forward. The route table maps the destination point code (DPC) of the message to an output
linkset name that is used to forward the packet.
Specifying the Default Route Table

On the Cisco ITP router, a route table named system is configured by default. The system route table
keeps a record of routes to all adjacent signaling points. To specify the Cisco ITP route table, use the
Command
Purpose
Router(config)# cs7 route-table rt-name
Specifies the name of the route table and enters

route table mode.
Note
You must specify system as the route table name (rt-name).
Loading the Route Table Contents

Route table contents can be loaded from a URL that locates a binary version of the route table. To add
route table contents, use the following command in route table configuration mode:
16-1
Chapter 16
Command
Purpose
Router(config-cs7-rt)# load {flash | ftp | rcp | tftp} URL
Loads the contents of the route table.
MTP3 Routes
Adding Routes to the Route Table

Additional routes can be added to the system route table.
To update a Cisco ITP route table use the update route command in Cisco CS7 route table configuration
mode:
Command
Purpose
Router(config-cs7-rt)# update route point-code [mask | length]

linkset ls-name [priority priority-value1] [qos-class class]
Add a route to the route table.
1. The smaller the number, the higher the priority. See the update route ITP Command Set entry for an example.
Saving the Route Table

You can save an active route table into a file. The newly created file can be used with the load route-table
sub-command to populate the route table upon ITP startup. Note that all update route or remove route
route-table sub-commands are removed from the system configuration after the save is completed. This
is done because those commands have been applied to the actual route-table before the save and,
therefore, are included in the saved file.
We recommend that you save the router configuration to non-volatile memory after generating a new
route-table file because the configuration has changed (update/remove route commands may have been
removed from the configuration).
To save an active route table to a file, use the following command in privileged EXEC mode:
Command
Purpose
Router# cs7 save route-table name url
Save the route table to a file.
16-2
C H A P T E R
17
Global Title Translation (GTT)

This section includes the following information and procedures:
Note
Overview of GTT, page 1
Storing and Loading GTT Configuration Data, page 4
Configuring GTT, page 10
Configuring Global Title Address Conversion, page 24
Verifying Global Title Translations, page 26
ITP GTT Configuration Example, page 28
The GTT provisioning syntax and structure is based on GR-82 STP Generic Requirements
- Telcordia Technologies, Issue 3 December 1999.
Overview of GTT
A global title is an application address, such as an 800 number, calling card number, or mobile subscriber
identification number. Global Title Translation (GTT) is the process by which the SCCP translates a
global title into the point code and subsystem number of the destination SSP where the higher-layer
protocol processing occurs.
The two forms of GTT are described in detail in the Configuring GTT section on page 10:
Intermediate GTT -- A subsequent global title is required by another node, thus the routing indicator
is set to zero, indicating route by global title (gt).
Final GTT -- No subsequent global title is required by another node, thus the routing indicator is set
to 1, indicating route by point code and ssn (pcssn).
The main components of GTT are described in the following sections:
GTT Selectors, page 2
GTT Global Title Address Entries, page 2
GTT Application Groups, page 3
GTT Mated Application Entries, page 3
17-1
Chapter 17
GTT Selectors
A GTT Selector defines the parameters that select the translation table used to perform the translation
of an SCCP message to its next or final destination. A GTT selector comprises a mandatory name,
Translation Type (TT), and Global Title Indicator (GTI - only mandatory for ITU). In addition, an
optional Numbering Plan (NP), Nature of Address Indicator (NAI), and Quality of Service (QOS) may
be specified in certain cases.
GTT Selectors have 2 configuration modes:
The global configuration mode allows configuration of new selectors or is used to enter the submode
for modifying/updating an existing selector.
The gtt selector configuration submode is used to modify certain attributes of the selector or used to
update GTAs in the referenced selector.
Rules for Creating GTT Selectors
The following rules apply when configuring a GTT Selector:
NP and NAI can not be specified if the variant is ANSI.
GTI can be specified only if the variant is ITU.
NP and NAI must be specified if GTI=4.
The selector name must be unique and from 1 to 12 characters long.
Rules for Modifying GTT Selectors
A selectors TT, GTI, NP and NAI cannot be modified once they have been added. A selector must
be completely deleted to change these values.
If a QoS class is entered for a selector, it must have been defined prior to being used by the selector.
If a new name is given for the selector, it must be unique and no longer than 12 characters.
Rules for Deleting GTT Selectors
The selector name must exist.
A selector cannot be deleted if it contains Global Title Address (GTA) entries.
GTT Global Title Address Entries

A GTA (Global Title Address) entry defines the result of a translation for a particular address mask. GTA
entries are configured from the gtt selector configuration submode. The result of a translation consists of:
A new MTP3 Destination Point Code
A new SCCP CDPA Routing Indicator (RI)
A new SCCP CDPA Subsystem Number (SSN)
A new SCCP CDPA Translation Type (TT) (mutually exclusive with SSN)
A GTT Application Group (mutually exclusive with all of the above)
A QoS Class
Rules for Adding GTA Entries
A solitary GTT Mated Application (MAP) entry is automatically created when the routing indicator
keyword is pcssn and a subsystem number (ssn) is specified.
17-2
Chapter 17
There must be room to add the MAP entry if required, since there is a maximum of 10 subsystems
per point code in the GTT Mated Application table. (See GTT Mated Application Entries, page 3.)
The routing indicator keyword must be gt if a new translation type (ntt) is specified.
A TT and SSN cannot both be specified.
The PC can not be equal to the nodes self PC, capability point code, or secondary PC.
1 to 15 digits may be specified for the GTA. (Valid range is 0 through F hexadecimal.)
The GTA digits must be unique for the GTA Table.
If a GTT Application group name is specified, it must already exist in the GTT Application Group
table.
If the routing indicator is pcssn, indicating final GTT, but no SSN is specified, then at least one GTT
MAP entry must exist for the specified PC.
GTT Application Groups

A GTT Application group is an alternative result for the explicit PC and SSN in a GTA entry. A GTT
application group should be used instead of the PC/SSN result in the following cases:
When more then 1 backup is required for a destination
When load sharing across more than 2 destinations is required
When load sharing for intermediate GTT destinations is required
When a different backup is required for the same primary destination dependent on the GTA
When a different RI value is desired dependent on the destination selected from the application
group
GTT Application groups have 2 configuration modes.
The top-mode allows configuration of new group names or is used to enter the submode for
modifying/updating an group or group item.
The submode is used to modify certain attributes of the group or used to update entries in the group.
GTT Mated Application Entries

A GTT Mated Application (MAP) entry has two main purposes. It is used internally by the SCCP
application to track point code and SSN states such as congestion and availability. In addition it is used
to define backups or alternates for a particular PC/SSN combination. An entry in the GTA table that
contains a PC and SSN will have a corresponding entry in the MAP table. The entry in the MAP table
may be modified to work in 1 of 3 modes:
Solitary - no alternate if PC and/or SSN is not available
Shared - load share equally across the primary PC/SSN and backup PC/SSN
Dominant - always translate to primary PC/SSN if available, and only translate to backup if primary
is unavailable.
Rules for Configuring GTT MAP Entries
The following rules apply:
A backup point-code and subsystem must be specified if mode (multiplicity) is shared or dominant.
A backup point-code and subsystem cannot be specified if mode (multiplicity) is solitary.
17-3
Chapter 17
A PC/SSN entry cannot be deleted if it is being used as a backup by another PC/SSN entry.
A PC/SSN entry cannot be deleted if it is referenced by an entry in the GTA table.
The primary and backup point-code cannot be identical.
There is a maximum of 10 subsystems per point-code allowed.
The PC can not be equal to the nodes self PC, capability PC, or secondary PC.
Storing and Loading GTT Configuration Data

GTT configuration data is stored and loaded differently than traditional router configuration data. GTT
configuration commands are not stored in non-volatile RAM (NVRAM), so commands such as
write memory and show running config have no effect. Figure 1 shows the GTT data relationships on
an ITP. This section describes:
Loading a GTT Table from a Remote File Server or Flash (No existing GTT Data), page 4
Loading a GTT Table from a Remote File Server or Flash (Existing GTT Data), page 5
Bulk Loading/Replacing Entire GTT database, page 6
Figure 1
GTT Table Loading
Non-volatile memory
(flash:)
ITP
Remote
server
Flash
NVRAM
tftp://64.102.16.25
cs7 gtt load <url>

Save running GTT config to flash using copy command
(copy cs7:gtt-tables/gtt_default flash:filename)
GTT data in volatile RAM

(cs7:gtt-tables/gtt_default)
GTT Load CLI command to specify

where GTT data is copied from.
Can be flash: or remote server.
59361
Save running GTT config to remote server using copy command

(copy cs7:gtt-tables/gtt_default tftp://64.102.16.25/filename)
In order to preserve a GTT configuration across ITP reloads, you must use the GTT Table Loading
feature.
Warning
All GTT data will be lost during a router reboot if you do not use the GTT Table Loading
procedure.
The steps for loading a GTT table when the ITP has no existing GTT data are as follows:
17-4
Chapter 17
Step 1
Determine the desired default location for the GTT file to be loaded during ITP reloads. The default
location can be either Flash or a remote server. For example, if the GTT file is to be loaded from Flash,
the URL would be similar to the following:
flash:gttdata.txt.
If the GTT file is to be loaded from a remote server, the URL would be similar to the following:
tftp://64.102.16.25/gttdata.txt
Step 2
Specify that the GTT file is to be loaded into RAM during subsequent ITP reloads:
Command
Purpose
Router(config)# cs7 gtt load URL
Specify the URL location from which, upon ITP

reload, the GTT database will be loaded.
For example, using the default location and filename flash:gttdata.txt, the command would be:
cs7 gtt load flash:gttdata.txt
Step 3
Save the cs7 gtt load definition to NVRAM with a write memory command.
Step 4
Configure all desired GTT data using the CLI.
Step 5
Save the GTT data to the file specified in step 2 using the copy command or the cs7 save gtt-table
privileged EXEC command as in the following example:
copy cs7:gtt-tables/gtt_default flash:gttdata.txt
- OR cs7 save gtt-table flash:gttdata.txt
Note
The file cs7:gtt-tables/gtt_default is a machine generated file. Its format is not meant for
hand editing. It is recommended the CLI or an externally provided GUI product be used to
configure GTT data, rather then editing the gtt_default file.
Steps 4 and 5 can be repeated for subsequent updates of GTT data.
For an existing system with GTT data, to execute the load command immediately use the following
Command
Purpose
Router(config)# cs7 gtt load URL [execute]
Specify the URL location of the GTT database

and, optionally, load it now.
17-5
Chapter 17
Bulk Loading/Replacing Entire GTT database

It may be desirable to replace the entire contents of a GTT database with a new database without
rebooting the ITP. The cs7 gtt load command discussed above does not support this capability. To
perform a bulk load of the entire GTT database without the need to reboot an ITP, use the following
command in privileged EXEC mode:
Command
Purpose
Router# cs7 gtt replace-db URL

Warning:This action will take the SCCP subsystem offline while
replacing the entire GTT database. SCCP messages
requiring Global Title Translation may be dropped.
Are you sure?
[confirm]
Replace the entire contents of a GTT database

with a new database without rebooting the ITP.
GTT table:URL, loaded successfully.
Note
It is recommended that this command only be executed during a time when SCCP
processing has been re-routed to the mate ITP, since this command takes the SCCP database
offline during the time it is executing. The performance of this command differs from
platform to platform and is also dependant on the database size. The entire processing time
should never exceed 5 minutes and in most cases completes in less than one minute during
low traffic periods.
Command Syntax for Creating GTT Download File

This section describes the format of the text file used to store and load GTT information on the ITP. Since
GTT data is not preserved in NVRAM, and the expected size of GTT data can be up to 500,000 entries,
a separate compressed format (comma separated) is provided to represent GTT data configured on the
ITP. The text file is generated by the ITP when GTT data is saved to a file. Users who require the ability
to generate GTT tables offline must use these guidelines to create a syntactically and semantically
correct file that may be loaded to the ITP.
Command identifiers
The following table shows the command identifiers supported by the GTT table download format. Each
line in the text file is identified with a one-character string. All command identifiers may be prefixed
with a d to indicate a delete action. Otherwise the action is assumed to be an add action. A modify
action occurs only when the item already exists and one or more attributes have changed. The table
shows the command identifier and the action it specifies.
Command Identifier Action

s
Add or modify GTT Selector
ds
Delete Selector
Add or modify GTT GTA
dg
Delete GTT GTA
Add or modify GTT Application Groups or items in

the group
17-6
Chapter 17
da
Delete GTT Application Groups or items in the

group
Add or modify GTT MAP
dm
Delete a GTT MAP
Add or modify a Concerned Point Code List
dc
Delete a Concerned Point Code List or item in the

list
Syntax Rules:
All lines must be terminated with a '\n' (unix eol).
All tokens are comma separated.
Each line is parsed for syntax checks and then checked for semantics.
If a line is parsed and fails either syntax or semantic checks the download process is aborted at the
point of failure.
Commands and Examples
To add, modify, or delete a GTT Selector:

[d]sselectorname,tt,gti,[np],[nai],[qos]
Examples:
stest,0,4,7,4,1
stestsel,0,2, , ,
sa12345672,100,4,15,127,
To add, modify, or delete a GTT GTA:

[d]gselectorname,gta,pc,ri,[ssn],[ntt],[app-grp],[qos]
Examples:
gtest,349,1012,gt,100, , ,
gtest,828,1012,gt, ,100, ,
gtest,828258,1012,pcssn,129, , ,
gtest,8282588595,1012,pcssn,100, ,1,
gtest,919, , , , ,test,
gtest,920, , , , ,test,
gtest,980,859,pcssn,10, , ,
To add, modify, or delete a GTT Application Group:

[d]a group-name,[mult],cost,pc,ri,[ssn]
Examples:
atest,sha,1,861,gt,
atest,sha,2,859,pcssn,
atest,sha,3,1012,pcssn,10
To add, modify or delete a GTT MAP:

[d]mppc,pssn,mult,[bpc],[bssn],[concern pc list name],[rrc],[adj]
Examples:
17-7
Chapter 17
m809,10,sol,,,,0,0
m859,10,sol,,,,0,0
m861,10,sol,,,,0,0
m1012,10,sol,,,,0,0
m859,20,sha,861,20,,0,1
m859,25,dom,861,25,,1,0
To add, modify, or delete a Concerned PC List

[d]cconcern pc list name,pc
Examples:
clist1,809
clist1,859
clist3,1012
17-8
Chapter 17
The following table lists the valid values for each parameter of the GTT commands.
Parameter
Valid Values
selector name
Name of Selector - alphanumeric string maximum of 12 chars
tt
Translation Type - integer {0-255}
gti
Global Title Indicator- integer {2,4}
np
Numbering Plan - integer {0-15}
nai
Nature of Address Indicator - integer {0-127
qos
Quality of service Class identifier {1-7}
gta
Global Title Address Digits - numeric/hex sting 1 to 15 digits
pc
destination point code in hex
ri
routing indicator {gt, pcssn}
ssn
Subsystem Number - integer {2-255}
ntt
New Translation Type - integer {0-255}
app-grp
Application Group name - alphanumeric string maximum of 12 chars
group-name
Application Group name - alphanumeric string maximum of 12 chars
mult
Multiplicity {sol, dom, sha, cos}
cost
cost or priority of destination {1-8}
ppc
Primary point code in hex
pssn
Primary Subsystem Number - integer {2-255}
bpc
Backup point code in hex
bssn
Backup Subsystem Number - integer {2-255}
concern pc list name
Concerned Point Code List Name - alphanumeric string maximum of 12

chars
rrc
Boolean Re-Route if Congested - integer {0,1}
adj
Boolean Adjacency indicator {0,1}
Predefined ANSI Selector Names

A list of predefined ANSI selector names will appear on an ANSI ITP that has never had GTT data
provisioned on it. You may add/delete/or change any of the predefined selectors and then save the GTT
configuration using the copy or save command in conjunction with the cs7 gtt load command. Any
subsequent reloads will restore the saved configuration, not the original pre-defined selectors.
Selector Name
------------IDCARDS
CELLNWROAM
GTEQUALPC
CGNAMEDLY
MSGWAITNG
SCPACPAPP
PCSROAM
PCSCALLDLY
INTWKNPQR
MINSMS
TT
--1
3
4
5
7
8
9
10
11
12
GTI
--2
2
2
2
2
2
2
2
2
2
NP
---
NAI
---
DFLTQOS
-------
#GTAs
----0
0
0
0
0
0
0
0
0
0
17-9
Chapter 17
IMSISMS
WSIBYNP
CGCARDP10D
CGNAMEDP10D
CGMGMTP10D
MSGWAITP10D
13
14
28
29
30
31
2
2
2
2
2
2
0
0
0
0
0
0
Displaying Current GTT Configuration

Since the GTT data on an ITP is not stored in NVRAM, commands such as show run will not display
the current configuration. To display the current running configuration regarding GTT use the following
Command
Purpose
Router# show cs7 gtt config
Display the current running configuration of GTT.
Configuring GTT
The following sections describe how to configure GTT data on the ITP for different scenarios applicable
to real customer networks. The scenarios include:
Configuring Intermediate GTT To Route MSUs to a Single Point Code, page 11
Configuring Intermediate GTT To Load Balance MSUs Across Two Or More Point Codes, page 13
Configuring Final GTT To Route MSUs to a Solitary Point Code, page 16
Configuring Final GTT To Route MSUs to a Primary and Backup Point Code and SSN (Dominant
Mode), page 19
Configuring Final GTT To Load Balance MSUs Across a Group of Point Codes and Subsystems,
page 22
Rules For Removing GTT Configurations:
To delete a selector you must first delete any GTAs that reference it, using the no gta command.
After deleting the GTAs, you can remove the selector, using the no selector command.
To delete a mated application (GTT MAP), you must first delete any application groups and GTAs
that reference it (using the no cs7 gtt application-group command and no gta command). You can
then delete the mated application configuration using the no cs7 gtt map command.
To delete a map entry that references another map entry as a backup, change all entries that reference
it to solitary then delete the map entry with the no cs7 gtt map command.
To delete an application group that is referenced by a GTA, you must first delete the GTA using the
no gta command. After deleting the GTA, you can remove the application group with the
no cs7 gtt app-grp command.
17-10
Chapter 17
Configuring Intermediate GTT To Route MSUs to a Single Point Code

This configuration describes the scenario shown in Figure 2.
Figure 2
Intermediate GTT With One Destination
PC=158
Cisco ITP
performing
intermediate
GTT
External STP
performing
final GTT
PC=245
HLR
GTT data
59362
Incoming
SCCP MSUs
The ITP on the left side of Figure 2 is required to perform intermediate GTT for a set of digits (GTAs).
There is only 1 choice for the next destination regardless of its availability. All SCCP traffic that requires
GTT and that matches the configured digits is to be GTT routed to the destination PC=158.
Provisioning the ITP

To provision the ITP, perform the following steps:
Step 1
Determine the criteria needed to select the appropriate translation table. For ITU the most common
Global Title Indicator is 4. This means a TT, NP and NAI identify the translation table. For ANSI, only
the TT is required. For this example we will use TT=0, NP=1, NAI=3.
Note
Step 2
The choices of TT, NP, and NAI are application specific. Refer to the SS7 network
administrator to determine the appropriate combination of TT, NP, and NAI. ITU-T
Q.714 Specifications of Signaling System No. 7- Signaling Connection Control
Part defines many of the well-known applications.
Determine if a GTT Selector matching the criteria stated above already exists:
Command
Purpose
Router# show cs7 gtt selector
Display GTT selector information.
If a matching GTT selector exists, it can be referenced by its text name. If not, a new selector must be
created. For this example assume it does not exist and the name c7gsp will be used.
Step 3
Determine the range of digits from the called party address (CDPA) that need to be routed to PC=158.
In this example assume that any digits matching the prefix 3330810 need to be GTT routed to PC=158.
All GTA digits entered on the ITP are prefix matched against the actual digits arriving in the MSU
requiring GTT. When 3330810 is provisioned on the ITP it really means 3330810xxxxx... where x is any
digit. The ITP currently supports prefix matching from 1 to 15 digits (1 - 9 and hex characters A - F).
17-11
Chapter 17
Configuring the ITP GTT Database

Once the above criteria are determined, follow these steps to configure the ITP GTT database:
Step 1
Configure the selector:
Command
Purpose
Router(config)# cs7 gtt selector selector tt tt gti gti np np

nai nai
Names and configures the GTT selector and enters

GTT selector configuration submode.
Using the details of the example, the command would be:

cs7 gtt selector c7gsp tt 0 gti 4 np 1 nai 3
In this simple case only one translation needs to be added within the selector.
Step 2
Configure the GTA within the selector:
Command
Purpose
Router(config-cs7-gtt-selector)# gta gta result-type pc

routing-indicator
Names and configures the GTA.
The result type is used to specify whether the GTA will be routed to a specific point code and optional
SSN (pcssn) or to an application group (app-grp). In this case the result type is pcssn which allows the
operator to specify a specific point code (pc=158). An SSN is not used in this example:
gta 3330810 pcssn 158 gt
The above command can be referred to as a GTA rule. The rule states that the CDPA digits matching
3330810 will be routed to a point-code and optional subsystem number (pcssn). The point-code is 158,
the subsystem number in this example is not defined and the routing indicator is set to 'gt' indicating
intermediate GTT. Omitting a new SSN in the rule causes the original SSN to be preserved during the
translation.
Step 3
Exit the submode and verify the data entered:
Command
Purpose
Router(config-cs7-gtt-selector)# exit
Exits GTT Selector configuration submode.
Router(config)# exit
Exits global configuration mode.
Router# show cs7 gtt gta selector-name [digits]
Displays details about the given GTA.
For the example, the command and the output would be:
Router# show cs7 gtt gta c7gsp
Selector Name
------------c7gsp
GTA
--------------3330810
TT
--0
GTI
--4
NP
--1
PC
----------158
NAI
--3
RI
----gt
DFLTQOS
-------
SSN
---
#GTAs
----1
TT
---
App-Grp
QOS
------------ ---
To delete a GTT configuration, follow the rules in the Rules For Removing GTT Configurations:
section on page 10.
17-12
Chapter 17
Configuring Intermediate GTT To Load Balance MSUs Across Two Or More Point Codes
Figure 3
Intermediate GTT Shared Across 2 Destinations
PC=158
Incoming
SCCP MSUs
Cisco ITP
performing
intermediate
GTT
External STP
performing
final GTT
PC=245
HLR
External STP
performing
final GTT
PC=166
59363
GTT data
This example is similar to the previous example except that instead of only 1 destination point-code a
group of point-codes shall be used. For this example the mode (multiplicity) used to pick which
point-code to choose from the group is shared. This means that all SCCP messages that matched the
translation will be equally shared across the available destinations in the group in a round-robin fashion.
The MTP3 destination status is used to determine if the point code is available.
In Figure 3 the ITP on the left side of the illustration is required to act as an intermediate translation
point to the mated pair of STPs, which handle all final translations to a HLR. In this case the ITP is
required to share all GTT routed traffic for a range of digits between a mated pair of STPs (PC=158 and
PC=166).

Step 1
Determine the criteria needed to select the appropriate translation table. For this example assume GTT
selector criteria GTI-4, TT=0, NP=1, NAI=3. Also assume the appropriate selector already exists in the
ITP GTT database.
Step 2
Define a GTT application group representing the mated pair of STPs (PC=158, PC=166) in the
intermediate/shared mode.
Step 3
Determine the range of digits from the called party address (CDPA) that need to be routed to the
application group containing PC=158 and PC=166. In this example assume that any digits matching the
prefix 328 needs to be GTT routed to the application group.
17-13
Chapter 17

Once the above criteria are determined the following steps may be followed to configure the ITP GTT
database:
Step 1
Define a GTT application group representing the mated pair of STPs in the intermediate/shared mode:
Command
Purpose
Router(config)# cs7 gtt application-group group-name
Assigns an application group name and enters the

GTT application-group configuration submode for
adding items to the group.

Router(config)# cs7 gtt application-group intergroup1
Step 2
Add the point-codes into the application group then exit application group submode:
Command
Purpose
Router(config-cs7-gtt-app-grp)# pc point-code cost

routing-indicator
Adds a point code, cost, and routing indicator to

the application group.
Router(config-cs7-gtt-app-grp)# exit
Exits GTT application-group configuration

submode.
Using the details of the example, the commands would be:

Router(config-cs7-gtt-app-grp)# pc 158 1 gt
Router(config-cs7-gtt-app-grp)# pc 166 2 gt
The default mode for the group is share, which does not have to be changed for this example. In the
shared mode, all items in an application group must be given a unique cost (1-8). In the shared mode
the cost can be thought of as an item number. Should the mode be changed to a cost mode, the method
for choosing the next destination would switch from a round-robin scheme to a least cost available
algorithm. (The cost is ignored when the group is share, and share is the default.) An example of using
the cost mode is not shown, but can be thought of as follows:
Instead of sharing all traffic between the items in the group, pick the least cost item (1 being the least)
and choose it always if available. If the least cost item is not available, choose the next least cost
available item and route to it. If no items are available, drop message and initiate error and measurement
procedures.
Step 3
Enter the submode configuration for the existing selector:
Command
Purpose
Router(config)# cs7 gtt selector selector
Enters the GTT selector submode for the given

selector.

Router(config)# cs7 gtt selector c7gsp
After performing the above step, the CLI enters selector submode for configuring translations options
within the selector. In this simple case only one translation needs to be added within the selector.
17-14
Chapter 17
Step 4
Command
Purpose
Router(config-cs7-gtt-selector)# gta gta result-type

<group-name>
Names and configures the GTA for the given

selector.

Router(config-cs7-gtt-selector)# gta 328 app-grp intergroup1
Note
The application group intergroup1 may be used by as many GTT rules as

needed. Avoid creating application groups with the same items in them.
The above command can be referred to as a GTA rule. The rule states that the CDPA digits matching 328
will be routed to the application group intergroup1. Using an application group allows destinations to
be modified, added, or deleted without impacting the GTA table.
Step 5
Command
Purpose
Router# show cs7 gtt gta <selector name> [digits]
Using the details of the example, the command and output would be:
Router# show cs7 gtt application-group
Application Group Name: intergroup1
Multiplicity
: share
Ref Count
: 1
Application Identifier
---------------------PC=158
PC=166
RI
----gt
gt
Cost
---1
2

Selector Name
------------c7gsp
GTA
--------------3330810
328
TT
--0
GTI
--4
NP
--1
PC
----------158
NAI
--3
RI
----gt
DFLTQOS
-------
SSN
---
#GTAs
----2
TT
---
App-Grp
QOS
------------ --intergroup1
section on page 10.
17-15
Chapter 17
Configuring Final GTT To Route MSUs to a Solitary Point Code

Figure 4
ITP performing Final GTT to a Solitary Point Code
PC=158
Cisco ITP
performing
final GTT
GTT data
PC=245
HLR
SSN=250
59364
Incoming
SCCP MSUs
This example is similar to the previous example in that a solitary point-code is used. However, this
example involves final GTT rather then intermediate GTT from the previous 2 examples. The main
difference in intermediate vs. final GTT is the resultant routing indicator of the outgoing/translated
message. The ITP also makes use of the Subsystem status when choosing the destination.
In Figure 4 the ITP (PC=158) is required to perform final GTT to a HLR (PC=245/ SSN=250) for a
specific range of digits from the CDPA. In this case the ITP is required to route all GTT traffic for the
range of digits to an end node such as the HLR in this example.

Step 1
ITP GTT database.
Step 2
Determine the range of digits from the called party address (CDPA) that need to be routed to the HLR.
In this example assume that any digits matching the prefix 3335114 needs to be GTT routed to the HLR.
Step 3
Determine if the ITP should replace the SSN in the called party with SSN=250 or the ITP should rely on
the proper SSN already being set in the CDPA. In this example the ITP will implicitly replace SSN=250
in the called party regardless of any existing SSN.

Once the above criteria are determined the following steps may be followed to configure the ITP GTT
database.
Step 1
Command
Purpose
Router(config)# cs7 gtt selector selector
Specifies the selector name and enters selector

submode for configuring translations options
within the selector.
17-16
Chapter 17

After performing the above step, the CLI enters selector submode for configuring translations options
within the selector. In this simple case only one translation needs to be added within the selector.
Step 2
Command
Purpose
Router(config-cs7-gtt-selector)# gta gta result-type pc

routing-indicator ssn ssn
Names and configures the GTA for the given

selector.

Router(config-cs7-gtt-selector)# gta 3335114 pcssn 245 pcssn ssn 250
The above command can be referred to as a GTA rule. The rule states that the CDPA digits matching
3335114 will be routed to a point-code and subsystem. The point-code is 245 and the SSN=250. The
resultant routing indicator shall be set to pcssn, indicating final GTT (route on point code and
subsystem). Since the SSN was specified as 250, it will override any SSN that previously existed in the
called party. Conversely if the SSN was not specified in this rule, the ITP would try to route to whatever
subsystem existed in the CDPA.
Step 3
Exit the submode and use the show cs7 gtt commands to verify the data entered:
Command
Purpose
Router# show cs7 gtt gta gta
Router# show cs7 gtt map
Displays details about the GTT MAP entries.
Using the details of the example, the show command and output would be:
Selector Name
------------c7gsp
TT
--0
GTA
--------------3330810
3335114
328
GTI
--4
NP
--1
PC
----------158
245

PPC
PSSN
MULT
245
250
sol
NAI
--3
DFLTQOS
-------
RI
----gt
pcssn
SSN
---
#GTAs
----3
TT
---
App-Grp
QOS
------------ ---
250
intergroup1
BPC
-----------
BSSN
---
ConPCLst
RRC ADJ
off no
Ref
1
Table 1 describes the fields in the show cs7 gtt map display.
17-17
Chapter 17
Table 1
Note
show cs7 gtt map Field Descriptions
Field
Description
PCC
Primary Point Code
PSSN
Primary Subsystem Number
Mult
Multiplicity (load share mode)
BPC
Backup Point Code for Primary Point Code
BSSN
Backup Subsystem Number for Primary Subsystem Number
ConPCLst
Concerned point-code list name. Concerned point-code lists are

created using the cs7 gtt concern-pclist command. All destinations
in the list are notified when a subsystem status change occurs.
Concerned point-code lists are optional for all GTT MAP entries.
RRC
Reroute to backup if primary is congested Used to tell SCCP routing

if the backup should be used when the primary is congested. Default
is OFF.
ADJ
Adjacency flag. Used to signify if a PC/SSN should be considered

adjacent to local node in regards to SCCP management. Default is
NO.
Ref
Reference Count. Indicates how many times a MAP entry is

referenced by GTA or application group entries. A referenced MAP
can not be removed.
Whenever final GTT is provisioned with an explicit subsystem from a GTA entry such as
the one for GTA=3335114, a GTT MAP (Mated Application) entry is required. The ITP
will automatically create a solitary MAP as needed when the GTA entry is created. The
GTT MAP entry is used internally by the ITP to manage the status of a subsystem. The
operator could have pre-provisioned this MAP entry prior to configuring the GTT using the
cs7 gtt map command. For an example where the MAP is provisioned prior to the GTA
see the Configuring Final GTT To Route MSUs to a Primary and Backup Point Code and
SSN (Dominant Mode) section on page 19. The MAP can also be used to define a mate
point-code for the primary point-code. This is an alternative to using application-groups,
which take up more memory.
section on page 10.
17-18
Chapter 17
Configuring Final GTT To Route MSUs to a Primary and Backup Point Code and SSN (Dominant
Mode)
This configuration describes the scenario shown in Figure 5
Figure 5
Final GTT routed to a primary and backup PC/SSN
PC=245
PC=158
Incoming
SCCP MSUs
Cisco ITP
performing
final GTT
HLR
SSN=250
PC=1003
HLR
SSN=250
59365
GTT data
This example is similar to the previous example in that final GTT is being performed. However, this
example involves final GTT using a customized GTT MAP entry where a backup PC and SSN are also
utilized.
In Figure 5 the ITP (PC=158) is required to perform final GTT to a HLR (PC=245/ SSN=250) for a
specific range of digits from the CDPA. Also suppose the HLR (PC=245) has a backup (PC=1003) in
case of a failure. In this case the ITP is required to route all GTT traffic for a range of digits to the
primary HLR if it is available. If the primary HLR becomes unavailable, the ITP is required to use the
backup instead. This method of choosing the primary and backup subsystems is typically referred to as
operating in the dominant mode.

Step 1
ITP GTT database.
Step 2
In this example assume that any digits matching the prefix 339 needs to be GTT routed to the primary
HLR (PC=245) if available or the backup HLR (PC=1003) if the primary is not available.
Step 3
Step 4
Determine if a GTT MAP entry having the appropriate mode and backup criteria exists. For this example
assume the GTT MAP entry does not exist and create it.
17-19
Chapter 17

Step 1
Enter the GTT MAP entry:
Command
Purpose
Router(config)#
[bssn]
cs7 gtt map ppc pssn [flags] mode [bpc]
Enters the GTT MAP definition.

Router(config)# cs7 gtt map 245 250 rrc dom 1003 250
The above command can be referred to as a GTT MAP definition. The definition dictates that PC=245
and SSN=250 is a primary application backed up in the dominant mode by PC=1003 and SSN=250. The
rrc flag specifies that if the primary PC/SSN becomes congested we will re-route to the standby PC/SSN.
Step 2
Command
Purpose
Router(config)#
cs7 gtt selector selector
Enters selector submode for configuring

translations options within the selector.

Step 3
Command
Purpose
Router(config-cs7-gtt-selector)# gta gta result-type

point-code routing-indicator ssn ssn
Configure the GTA for the given selector.

Router(config-cs7-gtt-selector)# gta 339 pcssn 245 pcssn ssn 250
will be routed to a point-code and subsystem. The point-code is 245 and the SSN=250. The resultant
routing indicator shall be set to 'pcssn' indicating final GTT (route on point code and subsystem). Since
the SSN was specifically specified as 250, it will override any SSN that previously existed in the called
party. Conversely if the SSN was not specified in this rule, the ITP would try to route to whatever
subsystem existed in the CDPA. Since a GTT MAP entry was pre-defined and the PC=245 / SSN=250
exists in the GTT Mated Application entity set, a backup PC/SSN shall be used in the dominant mode
with the rrc flag indicating re-route to backup if primary is congested.
Step 4
Command
Purpose
17-20
Chapter 17
Command
Purpose
Displays details about the GTT MAP entries.
Using the details of the example, the show command and output would be:
Selector Name
TT GTI
NP NAI DFLTQOS #GTAs
------------- --- --- --- --- ------- ----c7gsp
0
4
1
3
4
GTA
--------------3330810
3335114
328
339
PC
----------158
245
RI
----gt
pcssn
SSN
---
245
pcssn
250
App-Grp
QOS
------------ ---
250
intergroup1

PPC
PSSN
MULT
245
250
dom
Note
TT
---
BPC
1003
BSSN
250
ConPCLst
RRC ADJ
on no
Ref
2
You can not delete any map entry that references another MAP entry. You must first change all entries
that reference it to sol before you can delete the entry with the no cs7 gtt map command. To modify
a MAP entry you must replace the entire command, including all keywords and arguments.
section on page 10.
17-21
Chapter 17
Configuring Final GTT To Load Balance MSUs Across a Group of Point Codes and Subsystems
Figure 6
Final GTT Load Balanced Across Multiple PC/SSN Nodes
PC=1810
PC=158
Incoming
SCCP MSUs
Cisco ITP
performing
final GTT
HLR
SSN=250
PC=558
GTT data
HLR
SSN=250
HLR
SSN=250
59366
PC=678
This example is similar to the example show in Figure 3 in that an application group name is being used
rather than an explicit point-code or PC/SSN. However, this example involves final GTT instead of
intermediate GTT.
In Figure 6 the ITP (PC=158) is required to perform final GTT to an application existing on multiple end
nodes to reduce the CPU load at any given single node. In this case the ITP is required to share all GTT
traffic for a range of digits between multiple end nodes (in this case 3 shall be used - maximum of 8
destinations possible).

Step 1
Define a GTT application group representing the 3 HLRs.
Step 2
ITP GTT database.
Step 3
In this example assume that any digits matching the prefix 900 needs to be GTT routed to the application
group containing the 3 HLRs.
Step 4
Step 5
Determine if GTT MAP entries for the 3 end nodes exist. For this example assume the 3 MAP entries
already exist. Note: When final GTT is being performed with the use of application groups, the MAP
entry is required for each PC/SSN, but the fields in the MAP entry such as the load share mode, bpc,
bssn, and optional flags are ignored.
17-22
Chapter 17
Configuring the ITP GTT

Step 1
Define a GTT application group representing the 3 HLRs in the final/shared mode.
Command
Purpose
Router(config)#
Defines the GTT application group and enters

GTT application-group configuration submode.
cs7 gtt application-group group-name

Router(config)# cs7 gtt application-group finalgroup1
Step 2
Add the point codes into the application group then exit the configuration submode for the application
group:
Command
Purpose
Router(config-cs7-gtt-app-grp)# pc point-code ssn ssn cost

routing-indicator
Adds the point codes to the application group.

Exits submode configuration for the application
group.

Router(config-cs-gtt-app-grp)#
Step 3
pc 1810 ssn 250 1 pcssn

exit
Command
Purpose
Router(config)#
cs7 gtt selector selector
Enters selector submode for configuring

translations options within the selector.

Step 4
Command
Purpose
Router(config-cs7-gtt-selector)#
group-name
gta gta result-type
Configures the GTA for the given selector.

Router(config-cs7-gtt-selector)# gta 900 app-grp finalgroup1
will be routed to the application group finalgroup1.
17-23
Chapter 17
Step 5
Command
Purpose
Exits GTT selector configuration submode.
Displays details about the GTT application

groups.
Using the details of the example, the show commands and their output would be:
Application Group Name: finalgroup1
Multiplicity
: share
Ref Count
: 1
Application Identifier
---------------------PC=1810 SSN=250
PC=558 SSN=250
PC=678 SSN=250
RI
----pcssn
pcssn
pcssn
Cost
---1
2
3

Selector Name
------------c7gsp
TT
--0
GTA
--------------3330810
3335114
328
339
900
GTI
--4
NP
--1
NAI
--3
DFLTQOS
-------
PC
----------158
245
RI
----gt
pcssn
SSN
---
245
pcssn
250
#GTAs
----5
TT
---
App-Grp
QOS
------------ ---
250
intergroup1
finalgroup1
section on page 10.
Configuring Global Title Address Conversion

Global Title Address conversion tables are used to specify mappings such as E.212 to E.214 address
conversion and E.212 to E.164 address conversion in ITU networks. Global Title Address conversion
includes the following capabilities and functions:
The address conversion process is applied to digits in the Called Party address, and is invoked when
RI=GT.
The address conversion process is separately configurable, allowing for variable length address and
resultant digit string (up to a maximum of 15 digits).
For ITU networks, the numbering plan and nature of address indicator values in the GTA may be
changed.
17-24
Chapter 17
Global Title Address conversion tables can be stored on local or network hard media, just as the GTT
entries are.
Global Title Address conversion table updates are allowed during router operation.
Global Title Address conversion can occur before and/or after GTT.
Initially, conversion rules perform a best match on the defined input addresses. Upon a successful
match, the input address is replaced with the resultant, or output, address. The addresses are stored
in a radix tree with the input address as the key.
To define a address conversion table and enter GTT address conversion submode, use the following
Command
Purpose
Router(config)# cs7 gtt address-conversion tablename
Defines a GTT address conversion table.
To define an input address and an output address, use the following commands in CS7GTT address
conversion submode:
Command
Purpose
Router(config-cs7-gtt-conv-tbl)# update in-address

input-address {out-address output-address np newnp nai newnai}
Defines input and output address entries.
To define a new numbering plan for the entire table, use the following command in CS7 GTT address
conversion submode:
Command
Purpose
Router(config-cs7-gtt-conv-tbl)# np newnp
Defines the new numbering plan value for the

entire table. Only valid for ITU networks.
To define a new nature of address for the entire table (in ITU networks only), use the following command
in CS7 GTT address conversion submode:
Command
Purpose
Router (config-cs7-gtt-conv-tbl)# nai newnai
Defines the new nature of address value for the

entire table. Only valid for ITU networks.
17-25
Chapter 17
After you have defined a GTA address conversion table, you can apply the table on a GTT selector basis.
To specify the global title address conversion table to apply either prior to or after performing local
global title translation, use either of the following commands in CS7 GTT selector submode:
Command
Purpose
Router(config-cs7-gtt-selector)# pre-gtt-address-conversion
tablename
Specifies the global title address conversion table

to apply prior to performing local global title
translation.
Router(config-cs7-gtt-selector)# post-gtt-address-conversion
tablename
Specifies the global title address conversion table

to apply after performing local global title
translation.
Verifying Global Title Translations

After the ITP is configured with GTT data and the links come into service, you can determine if the GTT
and routing are working properly. This section describes three methods for verifying GTT:
GTT Measurements, page 26
SCCP Accounting, page 27
Subsystem Status, page 27
GTT Measurements
You can display CS7 GTT measurements kept on a MAP, selector or system-wide basis.
To display a report for each PC/SSN combination, including the number of times it was used by a
successful translation, use the following command in privileged EXEC mode:
Command
Router#
Purpose
show cs7 gtt measurements map
Displays a report for each PC/SSN combination.
To display measurements kept on a Selector basis, use the following command in privileged EXEC
mode:
Command
Router#
Purpose
show cs7 gtt measurements selector [selector]
Displays a report for each selector.
To display measurements for the system, use the following command in privileged EXEC mode:
Command
Router#
Purpose
show cs7 gtt measurements map
Displays a system report.
To reset all GTT measurements to 0, use the following command in privileged EXEC mode:
Command
Router#
Purpose
clear cs7 gtt -meas
17-26
Resets all GTT measurements to 0.
Chapter 17
SCCP Accounting
In addition to the GTT measurements that are kept on a system wide scale, Cisco ITP provides optionally
configurable per linkset GTT accounting. In its current implementation, GTT accounting provides a
mapping between the linkset that packets come in on, the selector that they match, the GTA within that
selector, and final translated point codes. This accounting is performed for successful GTT.
To display GTT accounting, use the following command in privileged EXEC mode:
Command
Router#
Purpose
show cs7 accounting gtt-active
Subsystem Status
The ITP SCCP application must process SCCP management messages to track the status of remote
subsystems. A GTT MAP entry should be created for all remote subsystems the ITP will be routing to
via GTT. The ITP provides a method for displaying the real time status for any remote subsystem entered
in its database. To display the status of a remote subsystem use the keyword stat in conjunction with the
show cs7 gtt map privileged EXEC command:
Command
Router#
Purpose
show cs7 accounting gtt-active
Displays the real time status of each entry in the

GTT MAP table.
The following sample output of the show cs7 accounting gtt-active command shows the real-time status
of each entry in the GTT MAP table:
Router# show cs7 gtt map stat
PC
SSN
PCST
SST
CONGESTED
668
250 UNAVL avail
--------1003
250
avail avail --------1008
250
avail UNAVL --------2020
250
avail avail level 2
17-27
Chapter 17
ITP GTT Configuration Example

This configuration example includes the Global Title Translation (GTT) feature described in the chapter
Configuring ITP Optional Features. Four Cisco ITPs are configured. The network configuration is
illustrated in Figure 7.
In this example, Intermediate GTT is performed on ITPB. All GTAs matching 339 are sent to the
capability point code shared by ITPC and ITPD, where Final GTT is performed.
The arrow symbol indicates the configuration statements most relevant to the GTT configuration on each
ITP.
Assumptions:
All routers have redundant ethernet connectivity and therefore all SCTP associations use two IP
addresses (multi-homing).
Point codes and IP addresses for ITP routers:
ITPA 5.100.2 172.18.44.242 117.117.117.2
ITPB 5.100.5 172.18.44.243 117.117.117.3
ITPC 5.100.4 172.18.45.1 117.117.119.4
ITPD 5.100.3 172.18.46.1 117.117.118.4
Point codes for SS7 SSPs:

SMSC 5.100.1
VMI4 5.100.6
VT02 5.100.7
VRM2 5.100.8
HLR3 5.100.9
HLR4 5.100.13
ITP GTT Configuration for ITPA

no service pad
!
hostname ITPA
!
enable secret 5 $1$iBmo$AFlH6u2CVGDRM5BMeuGmx/
enable password lab
!
!
no ip cef
no ip finger
no ip domain-lookup
!
cs7 variant itu
cs7 point-code 5.100.2
cs7 capability-pc 5.100.12
!
controller E1 1/0/0
17-28
Chapter 17
channel-group 0 timeslots 1
!
controller E1 1/0/1
!
controller E1 2/0/0
!
!
interface FastEthernet0/0/0
ip address 172.18.44.242 255.255.255.128
no ip route-cache distributed
no ip route-cache
no ip mroute-cache
!
ip address 117.117.117.2 255.255.255.0
no ip route-cache
no ip mroute-cache
!
interface Serial1/0/0:0
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
cs7 local-peer 7000
local-ip 172.18.44.242
local-ip 117.117.117.2
!
!
! Routes using linksets to ITPC and ITPD have a default
! priority of 5. Routes to adjacent node SMS-C and VMI4
! are inserted by the systems with priority 5 and when
! the linkset is configured. They don't have to be defined
! here. Backup-routes to SMS-C and VMI4 are inserted with
! priority 9 using the "C-Link".
!
cs7 route-table system
update route 5.100.7 7.255.7 linkset ITPc
update route 5.100.8 7.255.7 linkset ITPd
update route 5.100.1 7.255.7 linkset ITPb priority 9
update route 5.100.6 7.255.7 linkset ITPb priority 9
!
cs7 linkset ITPc 5.100.4
accounting
link 0 sctp 172.18.45.1 117.117.119.4 7000 7000
route all table system
17-29
Chapter 17
!
cs7 linkset ITPd 5.100.3
accounting
link 0 sctp 172.18.46.1 117.117.118.4 7000 7000
!
cs7 linkset smsc 5.100.1
accounting
link 0 Serial1/0/0:0
!
cs7 linkset vmi4 5.100.6
accounting
!
cs7 linkset ITPb 5.100.5
accounting
link 0 sctp 172.18.44.243 117.117.117.3 7000 7000
!
ip classless
no ip http server
!
!
!
line con 0
line aux 0
line vty 0 4
password lab
login
!
end
17-30
Chapter 17
ITP GTT Configuration for ITPB
In the following configuration example, ITPB is configured to perform ITP QoS SCCP packet
classification. QoS class 1 is assigned to the GTT selector table named c7gsp. QoS class 2 is assigned
to GTA 339. According to QoS rules of precedence, if a QoS class is assigned to a selector table and to
a GTA within that selector table, the QoS class assigned to the GTA entry has precedence over the QoS
class assigned to the selector table.
version 12.1
no service pad
!
hostname ITPB
!
enable password lab
!
!
!
!
!
no ip cef
no ip finger
no ip domain-lookup
!
cs7 variant itu
!
controller E1 1/0/0
!
controller E1 1/0/1
!
controller E1 2/0/0
!
!
ip address 172.18.44.243 255.255.255.128
no ip route-cache
no ip mroute-cache
!
ip address 117.117.117.3 255.255.255.0
no ip route-cache
no ip mroute-cache
!
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
no ip address
encapsulation mtp2
17-31
Chapter 17
no ip route-cache
load-interval 30
!
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
cs7 local-peer 7000
local-ip 172.18.44.243
local-ip 117.117.117.3
!
cs7 local-peer 8000
local-ip 172.18.44.243
local-ip 117.117.117.3
!
cs7 local-peer 9000
local-ip 172.18.44.243
local-ip 117.117.117.3
!
cs7 qos class 1
qos-ip-precedence 4
!
cs7 qos class 2
qos-ip-precedence 3
! Routes using linksets to ITPC and ITPD have a default
! priority of 5. Routes to adjacent node SMS-C and VMI4
! are inserted by the systems with priority 5 and when
! the linkset is configured. They don't have to be defined
! here. Backup-routes to SMS-C and VMI4 are inserted with
! priority 9 using the "C-Link".
!
update route 5.100.1 7.255.7 linkset ITPa priority 9
update route 5.100.6 7.255.7 linkset ITPa priority 9
!
cs7 gtt selector c7gsp tt 0 gti 4 np 3 nai 4
qos-class 1
gta 339 qos-class 2 pcssn 5.100.14 gt
cs7 linkset ITPc 5.100.4
accounting
link 0 sctp 172.18.45.1
qos-class 1
link 1 sctp 172.18.45.1
qos-class 2
link 2 sctp 172.18.45.1
!
accounting
link 0 sctp 172.18.46.1
!
cs7 linkset smsc 5.100.1
accounting
17-32
117.117.119.4 7000 7000

117.117.119.4 8000 8000
117.117.119.4 9000 9000
117.117.118.4 7000 7000
Chapter 17
!
cs7 linkset vmi4 5.100.6
accounting
!
cs7 linkset ITPa 5.100.2
accounting
link 0 sctp 172.18.44.242 117.117.117.2 7000 7000
!
ip classless
no ip http server
!
!
!
line con 0
line aux 0
line vty 0 4
password lab
login
!
end
!
17-33
Chapter 17
ITP GTT Configuration for ITPC

version 12.1
no service pad
!
hostname ITPC
!
enable password lab
!
!
!
!
!
no ip cef
no ip finger
no ip domain-lookup
!
cs7 variant itu
!
controller E1 1/0/0
!
controller E1 2/0/0
!
!
ip address 172.18.45.1 255.255.255.128
no ip route-cache
no ip mroute-cache
!
ip address 117.117.119.4 255.255.255.0
no ip route-cache
no ip mroute-cache
!
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
cs7 local-peer 7000
local-ip 172.18.45.1
local-ip 117.117.119.4
!
!
! Routes to SMS-C and VMI4 use a combined linkset.
17-34
Chapter 17
! This is defined by inserting two routes with

! identical priority (5 is default).
!
update route 5.100.1 7.255.7 linkset ITPa
update route 5.100.1 7.255.7 linkset ITPb
!
accounting
link 0 sctp 172.18.44.242 117.117.117.2 7000 7000
!
accounting
link 0 sctp 172.18.44.243 117.117.117.3 7000 7000
!
accounting
link 0 sctp 172.18.46.1 117.117.118.4 7000 7000
!
cs7 linkset vt02 5.100.7
accounting
!
ip classless
no ip http server
!
!
!
line con 0
line aux 0
line vty 0 4
password lab
login
!
end
17-35
Chapter 17
ITP GTT Configuration for ITPD

version 12.1
no service pad
!
hostname ITPD
!
enable password lab
!
!
!
!
!
no ip cef
no ip finger
no ip domain-lookup
!
cs7 variant itu
!
controller E1 1/0/0
!
controller E1 2/0/0
!
!
ip address 172.18.46.1 255.255.255.128
no ip route-cache
no ip mroute-cache
!
ip address 117.117.118.4 255.255.255.0
no ip route-cache
no ip mroute-cache
!
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
no ip address
encapsulation mtp2
no ip route-cache
load-interval 30
!
cs7 local-peer 7000
local-ip 172.18.46.1
local-ip 117.117.118.4
!
!
! Routes to SMS-C and VMI4 use a combined linkset.
17-36
Chapter 17
! This is defined by inserting two routes with

! identical priority (5 is default).
!
!
accounting
link 0 sctp 172.18.44.242 117.117.117.2 7000 7000
!
accounting
link 0 sctp 172.18.44.243 117.117.117.3 7000 7000
!
cs7 gtt map 5.100.9 100 share 5.100.13 100
cs7 gtt selector cnam tt 0 gti 4 np 3 nai 4
gta 339 pcssn 5.100.9 pcssn ssn 100
!
accounting
link 0 sctp 172.18.45.1 117.117.119.4 7000 7000
!
cs7 linkset vrm2 5.100.8
accounting
!
ip classless
no ip http server
!
!
!
line con 0
line aux 0
line vty 0 4
password lab
login
!
end
17-37
Chapter 17
Figure 7
ITPs as STPs in a SS7oIP Topology
5.100.1
SL
SL
SL
5.100.6
MSC/VLR
VM14
SMSC
SL
SL
SL
HLR1
HLR2
ITPA
5.100.2
ITP
ITP
ITPB
5.100.5
SL = Signalling link (64 Kbit/s)

= Link E1 (2 Mbit/s)
= Ethernet
ITPC
5.100.4
SL
5.100.7
17-38
MSC/VLR
VT02
ITP
SL
HLR3
5.100.9
HLR4
5.100.13
ITP
ITPD
5.100.3
SL
SL
MSC/VLR
VRM2
5.100.8
59016
IP network
C H A P T E R
18

This chapter describes the procedures for backing up (saving) a route table and a Global Title Translation
(GTT) table. The chapter has two main sections that include subsections:
Saving and Loading a Route Table, page 1
Saving and Loading a GTT Table, page 3
Saving and Loading a Route Table

The Cisco ITP uses a route table to select the appropriate signaling path for each message, or signal unit,
that it must forward. The route table maps the destination point code (DPC) of the message to an output
linkset name that is used to forward the packet.
This section includes the following procedures:
Specifying the Default Route Table, page 1
Loading the Route Table Contents, page 2
Adding Routes to the Route Table, page 2
Saving the Route Table, page 2
Specifying the Default Route Table

On the Cisco ITP router, a route table named system is configured by default. The system route table
keeps a record of routes to all adjacent signaling points. To specify the Cisco ITP route table, use the
Command
Purpose
Router(config)# cs7 route-table rt-name
Specifies the name of the route table and enters

route table mode.
Note
You must specify system as the route table name (rt-name).
18-1
Chapter 18
Saving and Loading a Route Table
Loading the Route Table Contents

Route table contents can be loaded from a URL that locates a binary version of the route table. To add
route table contents, use the following command in route table configuration mode:
Command
Purpose
Router(config-cs7-rt)# load {flash | ftp | rcp | tftp} URL
Loads the contents of the route table.
Adding Routes to the Route Table

Additional routes can be added to the system route table.
To update a Cisco ITP route table use the update route command in Cisco CS7 route table configuration
mode:
Command
Purpose
Router(config-cs7-rt)# update route point-code [mask | length]

linkset ls-name [priority priority-value1] [qos-class class]
Add a route to the route table.
1. The smaller the number, the higher the priority. See the update route ITP Command Set entry for an example.
Saving the Route Table

You can save an active route table into a file. The newly created file can be used with the load route-table
sub-command to populate the route table upon ITP startup. Note that all update route or remove route
route-table sub-commands are removed from the non-volatile (NV) RAM configuration after the save is
completed. This is done because those commands have been applied to the actual route-table before the
save and, therefore, are included in the saved file.
We recommend that you save the router configuration to non-volatile memory after generating a new
route-table file because the configuration has changed (update/remove route commands may have been
removed from the configuration).
To save an active route table to a file, use the following command in privileged EXEC mode:
Command
Purpose
Router# cs7 save route-table name url
Save the route table to a file.
The following example saves the route table to a route table file named system in flash:
Router# save route-table system flash:system
18-2
Chapter 18

Saving and Loading a GTT Table

GTT configuration data is stored and loaded differently than traditional router configuration data. GTT
configuration commands are not stored in non-volatile RAM (NVRAM), so commands such as
write memory and show running config have no effect. Figure 1 shows the GTT data relationships on
an ITP. This section describes:
Loading a GTT Table from a Remote File Server or Flash (No existing GTT Data), page 3
Loading a GTT Table from a Remote File Server or Flash (Existing GTT Data), page 4
Bulk Loading/Replacing Entire GTT Database, page 4
Figure 1
GTT Table Loading
Non-volatile memory
(flash:)
ITP
Remote
server
Flash
NVRAM
tftp://64.102.16.25
cs7 gtt load <url>

Save running GTT config to flash using copy command
(copy cs7:gtt-tables/gtt_default flash:filename)
Save running GTT config to remote server using copy command
(copy cs7:gtt-tables/gtt_default tftp://64.102.16.25/filename)
GTT Load CLI command to specify

where GTT data is copied from.
Can be flash: or remote server.
59361
GTT data in volatile RAM

(cs7:gtt-tables/gtt_default)
In order to preserve a GTT configuration across ITP reloads, you must use the GTT Table Loading
feature.
Warning
All GTT data will be lost during a router reboot if you do not use the GTT Table Loading
procedure.
The steps for loading a GTT table when the ITP has no existing GTT data are as follows:
Step 1
Determine the desired default location for the GTT file to be loaded during ITP reloads. The default
location can be either Flash or a remote server. For example, if the GTT file is to be loaded from Flash,
the URL would be similar to the following:
flash:gttdata.txt.
18-3
Chapter 18
If the GTT file is to be loaded from a remote server, the URL would be similar to the following:
tftp://64.102.16.25/gttdata.txt
Step 2
Specify that the GTT file is to be loaded into RAM during subsequent ITP reloads:
Command
Purpose
Router(config)# cs7 gtt load URL
Specify the URL location from which, upon ITP

reload, the GTT database will be loaded.
For example, using the default location and filename flash:gttdata.txt, the command would be:
cs7 gtt load flash:gttdata.txt
Step 3
Save the cs7 gtt load definition to NVRAM with a write memory command.
Step 4
Configure all desired GTT data using the CLI.
Step 5
Save the GTT data to the file specified in step 2 using the cs7 save gtt-table privileged EXEC command
as in the following example:
cs7 save gtt-table flash:gttdata.txt
Note
The file cs7:gtt-tables/gtt_default is a machine generated file. Its format is not meant for
hand editing. It is recommended the CLI or an externally provided GUI product be used to
configure GTT data, rather then editing the gtt_default file.
Steps 4 and 5 can be repeated for subsequent updates of GTT data.
For an existing system with GTT data, to execute the load command immediately use the following
Command
Purpose
Router(config)# cs7 gtt load URL [execute]
Specify the URL location of the GTT database

and, optionally, load it now.
Bulk Loading/Replacing Entire GTT Database

It may be desirable to replace the entire contents of a GTT database with a new database without
rebooting the ITP. The cs7 gtt load command discussed above does not support this capability. To
perform a bulk load of the entire GTT database without the need to reboot an ITP, use the following
Command
Purpose
Router# cs7 gtt replace-db URL

Warning:This action will take the SCCP subsystem offline while
replacing the entire GTT database. SCCP messages
requiring Global Title Translation may be dropped.
Are you sure?
[confirm]
Replace the entire contents of a GTT database

with a new database without rebooting the ITP.
GTT table:URL, loaded successfully.
18-4
Chapter 18

Note
It is recommended that this command only be executed during a time when SCCP
processing has been re-routed to the mate ITP, since this command takes the SCCP database
offline during the time it is executing. The performance of this command differs from
platform to platform and is also dependant on the database size. The entire processing time
should never exceed 5 minutes and in most cases completes in less than one minute during
low traffic periods.
18-5
Chapter 18
18-6
C H A P T E R
19
Replacing a Failed SS7 LSL or HSL

Port Adapter
This chapter describes procedures that are required when you replace a failed SS7 low speed link (LSL)
or high speed link (HSL) port adapter. The main sections and procedures are:
Port Adapters on the VIP4, page 1
Taking Port Adapters Out of Service, page 3
Replacing Port Adapters, page 6
Reinstalling the VIP4 and Connecting the Port Adapter Cables, page 9
Verifying the VIP4 and SS7 Port Adapter Installation, page 12
Reactivating the Links Associated with the Port Adapter, page 17
Port Adapters on the VIP4

The VIP4 is a motherboard that supports up to two single-width port adapters, or one dual-width port
adapter. Figure 19-1 shows a VIP4 with two installed single-width port adapters.
The ITP provides low speed links (LSL) and high speed links through 2 single-width port adapters that
are installed on a VIP4 in the ITP.
Note
Note
19-1
Chapter 19
Port Adapters on the VIP4
Figure 19-1 VIP4 with Two Single-Width Port AdaptersHorizontal Orientation Shown
Bus connector
Packet
memory
DIMM U5
CPU memory
DIMM U1
Port adapter
in slot 1
26561
Port adapter
in slot 0
CPU

Online board installation and removal (OIR) refers to the capability to remove and replace specific
interface processors while the system is in operation. SS7 Low speed port adapters, high speed port
adapters, and Ethernet port adapters support OIR without causing system disruption. These boards are
designed to be removed from the system with no disassembly other than external interface cabling.
We recommend that each linkset have links on at least 2 VIPs so that a single VIP/PA failure does not
take the linkset out of service.
Removing a VIP with a port adapter is typically done either because of a failed port or a problem directly
with the VIP itself. The port adapter itself cannot be removed without removing the VIP. If the VIP with
the port adapter is to be removed for replacement, we recommend that you inhibit and shut down any in
service links before you remove the VIP. This will allow the traffic to be rerouted to the alternate links
or linkset. If removal of the affected VIP is performed while links within a linkset are active, rerouting
of traffic will also occur to the alternate linkset on the redundant VIP. It is required that the 7500 system
console messages report that the remaining active links and linkset become unavailable before inserting
the replacement VIP.
To perform OIR properly, wait 30 seconds between removal and reinsertion of the VIP.
Note
19-2
Chapter 19

Taking Port Adapters Out of Service

Before you physically remove a failed port adapter, you must administratively remove the port adapter
from service.
This section describes the procedures for administratively taking the port adapters out of service.
If you intend to replace a failed SS7 PA, follow the instructions in Taking an SS7 PA Out of Service,
page 3
If you intend to replace a failed HSL PA, follow the instruction in Taking an HSL PA Out of Service,
page 4

Identifying and Disabling SS7 Links
Before you disable an SS7 Port Adapter you must identify, inhibit and shutdown all the links using that
port adapter.
Note
all links before disabling (shutdown) them is a safeguard that allows the ITP to ensure that no
if a destination becomes inaccessible or a different (already inhibited) link may be out back in
service. If this situation occurs, one workaround could be to first inhibit all A-links, then inhibit as
many C/D-links as possible and last shut down the C-links.
Use the following commands, beginning in privileged EXEC mode:
Command
Purpose
Step 1
Identifies all links that are using an interface.
Step 2

Step 3
Enters global configuration mode, so you can

access a linkset.
Step 4
Router(config)# cs7 linkset ls-name
Specifies the linkset that contains the links you

intend to take out of service. Enables linkset
configuration mode.
Step 5
Router(config-ls)# link slc serial number

service. Enters link configuration mode.
Step 6
Disables the link.
19-3
Chapter 19
Note
Repeat the above steps until all the links are inhibited and shut down. If you need to exit from one
mode to a previous mode, issue the exit command until you return to the appropriate mode for the
command you need to issue.

Shut down the controller before you take the port adapter out of service. To disable the controller, use
the following commands, beginning in global configuration mode.
Command
Purpose
Step 1
Router(config)# controller type slot/bay/port
Identify the controller and enable controller

configuration mode.
Step 2

Identifying and Disabling High Speed Links
Before you disable an HSL Port Adapter you must identify, inhibit, and shutdown all the links using that
port adapter. Use the following commands, beginning in privileged EXEC mode:
Step 1
Command
Purpose

Look for the ATM interface to identify the links
that you will need to shutdown. Note the linkset
name.
Step 2

Step 3

access a linkset.
Step 4

configuration mode.
Step 5
Router(config-ls)# link slc atm number

Step 6
Disables the link.
Note
19-4
Chapter 19


Command
Purpose
Step 1
Specify the interface.
Step 2
19-5
Chapter 19
Removing the VIP4
Removing the VIP4

You must remove the VIP4-80 in order to replace the failed port adapter. This section describes the
procedure for removing a VIP4-80 from the ITP.
Note
Procedure for Removing the VIP4

Step 1
Step 2
Step 3
system.
Step 4
Step 5
Caution
Step 6
Step 7
Step 8
system.
Step 9

This section describes the procedures for physically removing a failed port adapter from the VIP and
installing the replacement port adapters on the VIP
19-6

When a single-width port adapter slot is not in use, a blank port adapter must fill the empty slot to allow
the router to conform to electromagnetic interference (EMI) emissions requirements and to allow proper
airflow through the router. If you plan to install a new single-width port adapter in a port adapter slot
that is not in use, you must first remove the blank port adapter.
Caution
Figure 19-2 Handling a Port Adapter
Metal carrier

H6420
Chapter 19
Caution
19-7
Chapter 19
Illustrated Procedure for Removing and Installing the SS7 Port Adapter
Note
Figure 19-3 describes removing and installing a single-width port adapter.

VIP4.
Step 1
remove
(See A.)
Step 2
Screw
Step 3
Carrier
Upper edge
Lower edge
Step 4
the screw. (See A.)
C
NO
RM
AL
Captive
installation
screw
PA-MC-8TE1-SS7
7
6
IL
PO
WE
EC
T
5
EJ
SL SLO
OT T
0 1
SL MAS
AV TE
E
R
AV
E/
MAS
CPU
RES
TE
HAL
T
1
SL
ET
Step 5
(See B.)
FA
DC
AC
FA
IL
PO
WE
EN
AC
AL
DC
EN
AB
LE
19-8
AU
CO
X.
NSO
LE
29327
Step 6
Chapter 19


This section describes the following tasks:

Note
Procedure for Removing and Installing the SS7 Port Adapter section on page 8. If you have already
reinstalled the VIP in the router chassis, proceed to the Connecting the SS7 Port Adapter Interface
Cables section on page 10.
After you have installed the SS7 Port Adapter on the VIP, you must reinstall the VIP. The VIP slides into
an open interface processor slot and connects directly to the backplane. The interface processors are
keyed to guide pins on the backplane, so the VIP can be installed only in an interface processor slot.
Note
routers.
Caution
19-9
Chapter 19
Use the following procedure to install a new VIP4:

Step 1
Step 2
Step 3
Caution
Step 4
Step 5
Caution
Step 6
into its slot.
Step 7
Caution

Note
Step 1
Step 2
19-10
Chapter 19

Step 3
AL
PA-MCX-8TE1-M
6
7
65854
EN
Twisted-pair cable
To PBX or PSTN
Connecting PA A3-IMA Cables

The eight DS1/E1 interface receptacles on the PA-A3-IMA are RJ-45 connectors for T1 (100 ohm) or
E1 (120 ohm). All eight may be used simultaneously as ATM interfaces, or they may be used to create
IMA groups.
Note
After you properly connect a port to a line, it takes approximately 30 seconds for Cisco IOS software to
report that the line is up.
TR62411 standards. The RJ-45 connection does not require an external transceiver. The DS1 ports are
To meet VCCI Class II EMI requirements, you must use FTP cables.
Figure 19-5 shows the PA-A3-IMA interface cable connector.
Figure 19-5 PA-A3-IMA Interface Connector
87654321
RJ-45 connector
H2936
Note
19-11
Chapter 19
lists the signal pinouts and descriptions for the RJ-45 connector.
IMA Interface Cable RJ-45 Connector Pinouts
Pin
Signal
Signal
To
J1-1
RX ring
TX ring
J2-4
J1-2
RX tip
TX tip
J2-5
J1-3
RX shield
TX shield
NC
J1-4
TX ring
RX ring
J2-1
J1-5
TX tip
RX tip
J2-2
J1-6
TX shield
RX shield
NC
J1-7
NC
NC
J1-8
NC
NC

This section describes the procedures you can use to verify your VIP4 and Port Adapter installation. It
includes information on the following topics:
Observing LEDs and System Messages, page 12
Using show Commands to Verify the VIP4 Status, page 15
Using show Commands to Display Interface Information, page 16
Observing LEDs and System Messages

After you install the VIP4 and connect the port adapter cables, you can verify the installation by
Note
19-12
Chapter 19


AL
PA-MCX-8TE1-M
6
7
65853
EN
for operation.
does not go on.
Table 19-1
LED Label
Color
State
Function
EN
Green
On
Off

disabled.
Amber
On

Red
On

of the T1/E1 ports.
Off
On
On
Off

AL
0 through 7 Green
Yellow
System Messages
When you remove and replace interface processors, the system provides status messages on the console
screen. The messages are for information only.
The following sample display shows the events logged by the system when a VIP4 with an SS7 Port
Adapter is removed from interface processor slot 4. The system reinitializes the remaining interface
processors and marks as down the SS7 Port Adapter interface on the VIP4 that was removed from slot 4:
Router#
00:51:01: %OIR-6-REMCARD: Card removed from slot 4, interfaces disabled
%LINK-5-CHANGED: Interface serial 4/0/0, changed state to administratively down
19-13
Chapter 19
The following sample display shows the events logged by the system when a VIP4 with a SS7 Port
Adapter is reinserted into interface processor slot 4. The the system automatically brings up the
interfaces that were up when the VIP4 was removed:
Router#
00:52:30: %OIR-6-INSCARD: Card inserted in slot 4, interfaces administratively shut down
00:52:35: %LINK-3-UPDOWN: Interface Serial4/0/0:1, changed state to up
When a new VIP4 is inserted or when a VIP4 is moved to a new slot, the system recognizes the new
interfaces but leaves them in the shutdown state until you configure them and change their state to up.
The following sample display shows the events logged by the system as you insert a new VIP4 in
interface processor slot 6:
Router#
To verify that the VIP4 is installed correctly, observe the LEDs and system messages as described in the
following steps. If you experience other problems that you are unable to solve, contact a service
representative for assistance.
Step 1
system discovers the VIP4 as follows:
If you installed a new VIP4, the system should recognize all new interfaces but leave them
configured as down. (You must configure new interfaces to make them available.)
If you replaced a VIP4, the system should recognize each interface and place it in the same state (up
or down) each was in when you removed the VIP4.
Step 2
When the reinitialization is complete, verify that the enabled LED on each port adapter goes on and
remains on. If it does, proceed to Step 5. If it does not, proceed to the next step.
Step 3
If the enabled LED on a port adapter fails to go on, suspect that the VIP4 board connector is not fully
seated in the backplane. Loosen the captive installation screws, and then firmly push both ejector levers
into place until they are approximately in the same orientation as the VIP4 faceplate. Tighten the
captive installation screws. After the system reinitializes the interfaces, the enabled LED on the port
adapter should go on. If it does, proceed to Step 5. If it does not, proceed to Step 4.
Step 4
If the enabled LED still fails to go on, remove the VIP4 and try installing it in another available
Step 5
If the enabled LED goes on when the VIP4 is installed in the new interface processor slot, suspect
a failed backplane port in the original interface processor slot.
If the enabled LED still fails to go on, but other LEDs go on to indicate activity, proceed to Step 5
to resume the installation checkout; suspect that the enabled LED on the port adapter has failed.
Contact a service representative to report the problem and obtain further instructions.
If no LEDs go on, suspect that the VIP4 is faulty. Contact a service representative to report the
problem and obtain further instructions.
If just the enabled LED still fails to go on, remove the VIP4 and ensure the port adapters are firmly
installed in their port adapter slots. Remove and reinstall them accordingly.
If the VIP4 is new and not a replacement, you must configure all new interfaces to make them available.
(This does not have to be done immediately, but new interfaces are not be available until you configure
them.)
19-14
Chapter 19

Step 6
If the VIP4 is a replacement, use the show interfaces type interface-processor-slotnumber/port-adapter-slot-number/interface-port-number command or the show controllers command
to verify the status of the interfaces. (See the following section, Using show Commands to Verify the
VIP4 Status.)
If you replaced a VIP4 with a new VIP4 with a greater number of interfaces (for example, if you replaced
a VIP4 with a single port adapter with a VIP4 with two port adapters), the system recognizes the
interfaces on the previously configured port adapter but does not recognize the additional port adapter
interfaces. The new interfaces remain in the shutdown state until you configure them.
Step 7
described in the appropriate LED section of your port adapter installation and configuration notes.
Step 8
In general, if an interface LED fails to go on and a cable is connected to the interface port, check the
cable connection and make certain it is properly seated in the connector.
Using show Commands to Verify the VIP4 Status

correctly.
Step 1
Step 2
Display all the current interface processors and their interfaces with the show controllers command.
Verify that the new VIP4 appears in the correct interface processor slot.
Step 3
Specify one of the new interfaces with the show interfaces type interface-processor-slotnumber/port-adapter-slot-number/interface-port-number command and verify that the first line of the
display specifies the interface with the correct slot number. Also verify that the interface and line
protocol are in the correct state: up or down.
Step 4
Step 5
configuration stored in the RSP NVRAM using the show startup-config command. Verify that the
Note
The outputs that appear in this document may not match the output you receive when
running these commands. The outputs in this document are examples only.
19-15
Chapter 19

To display information about a specific interface, use the show interfaces command in the format
show interface type interface-processor-slot-number/port-adapter-slot-number/interface-port-number
:channel-group-number.
The following is an example of the show interface serial command:
Router#show interface serial 4/0/0:0
Serial4/0/0:0 is up, line protocol is up
Hardware is cxBus T1
MTU 290 bytes, BW 56 Kbit, DLY 20000 usec,
Encapsulation SS7 MTP2, crc 16, loopback not set
Keepalive set (10 sec)
Last clearing of "show interface" counters 00:32:16
Queueing strategy: fifo
0 carrier transitions no alarm present
Timeslot(s) Used:1, subrate: 56Kb/s, transmit delay is 0 flags
Transmit queue length 109
Router#
To display hardware information about all of the interface processors in your router, including the VIP4,
use the show controller command.
Following is an example of the show controller command used with a Cisco 7500 series router:
Router#show controller t1 4/0/0
T1 4/0/0 is up.
No alarms detected.
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
Router#
To display the configuration of the system hardware (the number of each interface processor type
installed), the software version, the names and sources of configuration files, and the boot images, use
the show version (or show hardware) command.
To determine specific hardware configuration information about a VIP4 installed in your system
(including the amount of installed CPU and packet memory), use the show diag slot command.
Following example of a VIP4-80 with an SS7 Port Adapter; the VIP4-80 is installed in interface
processor slot 2:
Following is an example of the show diag slot command that shows an SS7 Port Adapter in interface
processor slot 2 of a Cisco 7513 router:
Router# show diag 2
19-16
Chapter 19

Reactivating the Links Associated with the Port Adapter
Slot 2:
PA-MCX-8TE1-M Port adapter, 8 ports
Port adapter is analyzed
Port adapter insertion time 00:52:22 ago
EEPROM contents at hardware discovery:
Hardware Revision
: 1.0
PCB Serial Number
: SIC04412B7S
Part Number
: 115-22681-01
Board Revision
: 02
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Deviation Number
: 0-0
IDPROM FIELD FORMAT ERROR, index 0x29
0x00: 04 FF 40 03 52 41 01 00 C1 8B 53
0x10: 31 32 42 37 53 82 73 58 99 01 42
0x20: 00 00 00 00 04 00 80 00 00 00 00
0x30: 00 00 00 00 00 00 00 00 00 00 00
0x40: 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00
49
30
CB
00
00
00
00
00
43
32
00
00
00
00
00
00
30
03
00
00
00
00
00
00
34
00
00
00
00
00
00
00
34
81
00
00
00
00
00
00

After you have replaced the LSL or HSL port adapter, you must reactivate any links that you took out of
service. Follow the procedure that pertains to your port adapter type:
Reactivating Disabled SS7 Low Speed Links, page 17
Reactivating Disabled High Speed Links, page 18
Reactivating Disabled SS7 Low Speed Links

To reactivate the SS7 low speed links that you previously took out of service, enter the following
commands, beginning in privileged EXEC mode:
Command
Purpose
Step 1
Router# controller type slot/bay/port
Specifies the controller (that you disabled earlier

in this procedure) and enables controller
configuration mode.
Step 2
Router(config-controller)# no shutdown
Enables the previously disabled controller.
Step 3
Router(config-controller)# exit
Exits controller configuration mode.
Step 4

access a linkset.
Step 5

previously shut down. Enables linkset
configuration mode.
Step 6
Specifies the link that you previously shut down.

Enters link configuration mode.
19-17
Chapter 19
Command
Purpose
Step 7
Router(config-ls-link)#
no shutdown
Enables the link you previously shut down.
Step 8
exit
Exits CS7 link submode.
Step 9
Router(config-ls)#
Step 10
Router(config)#
Step 11
Router# cs7 uninhibit lsn slc
Note
Exits CS7 linkset submode.
exit
exit
Uninhibits the previously inhibited links. (Repeat

this step for every previously inhibited link.)
Repeat the above steps until all the links that you previously shut down are enabled. If you need to
exit to a previous mode, issue the exit command until you return to the appropriate mode for the
Reactivating Disabled High Speed Links

To reactivate the high speed links that you previously took out of service, enter the following commands,
beginning in global configuration mode:
Command
Purpose
Step 1
Specify the interface and enable interface

configuration mode.
Step 2
Router(config-if)# no shutdown
Reactivate the interface.
Step 3
Router(config-if)# exit
Exit interface configuration mode.
Step 4

configuration mode.
Step 5

Step 6
Router(config-ls-link)# no shutdown
Step 7
Step 8
Router(config-ls)#
Step 9
Router(config)#
Step 1
Note
exit
exit

19-18
exit
C H A P T E R
20
Installing or Replacing a FastEthernet

Port Adapter
This chapter describes procedures to replace a failed FastEthernet port adapter. The main sections and
procedures are:
Port Adapter Overview, page 1
Configuring the PA-2FA, page 15
Port Adapter Overview

The PA-2FE provides two 10/100-Mbps, 10/100BaseT Fast Ethernet/Inter-Switch Link (ISL) interfaces
and supports both full-duplex and half-duplex operation.
This section includes the following information:
LEDs, page 2
Receptacles, Cables, and Pinouts, page 2
Identifying Interface Addresses, page 4
Both models of the PA-2FE (PA-2FE-TX and PA-2FE-FX) are shown in Figure 20-1 and Figure 20-2.
Figure 20-1 PA-2FE-TXFaceplate View
PA-2FE-TX
0
TX
1
RX
0
RX
1
TX
K1
LIN
46453
K0
LIN
D
LE
AB
EN
20-1
Chapter 20
Figure 20-2 PA-2FE-FXFaceplate View
0
RX
RX
TX
RX
TX
1
RX
1
TX
K1
LIN
46454
0
TX
K0
LIN
CL
A
PR SS
PR OD 1 LE
U
DE OD KT D P
U
CL IT MIT RO
AS AV K DU
SE EC LA C T
PR
S
1 VO SE
O
DU
YA 1
N T LE
CT
O
DE D
LE
L
D
DE
CL
AS
E
1
PA-2FE-FX
D
LE
AB
EN
LEDs
The PA-2FE contains seven LEDS; an enabled LED, which is standard on all port adapters, a link LED,
and a transmit LED and receive LED for each of the ports. The LEDs are shown in Figure 20-3.
Figure 20-3 LEDs on the PA-2FEFaceplate View of PA-2FE-TX
PA-2FE-TX
K0
LIN
0
TX
1
RX
0
RX
1
TX
K1
LIN
46453
D
LE
AB
EN
Receptacles, Cables, and Pinouts

The two interface receptacles on the PA-2FE are a single RJ-45 connection (on the PA-2FE-TX) or an
SC-type optical-fiber connection (on the PA-2FE-FX). Each connection supports IEEE 802.3u interfaces
compliant with the 100BaseX and 10/100BaseT standards. The RJ-45 connection does not require an
external transceiver.
Figure 20-4 shows the RJ-45 cable connectors. Cisco does not supply Category 5 UTP RJ-45 cables;
these cables are available commercially. Table 20-1 lists the pinouts and signals for the PA-2FE-TX
RJ-45 connectors.
87654321
RJ-45 connector
20-2
H2936
Figure 20-4 PA-2FE-TX RJ-45 ConnectionsPlug and Receptacle

Table 20-1 FE-TX RJ-45 Connector Pinouts
Description
Receive Data + (RxD+)
RxD
Transmit Data + (TxD+)
TxD
Referring to the RJ-45 pinout in Table 20-1, proper common-mode line terminations should be used for
the unused Category 5, unshielded twisted-pair (UTP) cable pairs 4/5 and 7/8. Common-mode line
termination reduces the contributions to electromagnetic interference (EMI) and susceptibility to
common-mode sources. Wire pairs 4/5 and 7/8 are passively terminated in the RJ-45, 100BaseTX port
circuitry in the PA-2FE-TX.
Depending on your RJ-45 interface cabling requirements, use the pinouts in Figure 20-5 and
Figure 20-6.
Figure 20-5 Straight-Through Cable PinoutPA-2FE-TX RJ-45 Connection to a Hub or Repeater
PA-2FE-TX
Hub or repeater
3 TxD+
3 RxD+
6 TxD
6 RxD
1 RxD+
1 TxD+
2 RxD
2 TxD
Figure 20-6 Crossover Cable PinoutPA-2FE-TX RJ-45 Connections Between Hubs and Repeaters
Hub or LAN switch Hub or LAN switch

3 TxD+
3 TxD+
6 TxD
6 TxD
1 RxD+
1 RxD+
2 RxD
2 RxD
49773
Note
Pin
49772
Chapter 20
Figure 20-7 shows the duplex SC connector (one required for both transmit and receive), and
Figure 20-8 shows the simplex SC connector (two required, one for each transmit and receive) used for
PA-2FE-FX optical-fiber connections. These multimode optical-fiber cables are commercially available,
and are not available from Cisco.
20-3
Chapter 20
H2214
Figure 20-7 PA-2FE-FX Duplex SC Connector
H2399
Figure 20-8 PA-2FE-FX Simplex SC Connector
Identifying Interface Addresses

Interfaces on a PA-2FE installed in a VIP maintain the same address regardless of whether other interface
processors are installed or removed. However, when you move a VIP to a different slot, the interface
processor slot number changes to reflect the new interface processor slot.
The interface address format in the VIP2 or VIP4 in Cisco 7500 series routers is:
Interface Address Format
Numbers
Syntax
Interface-processor-slot-number/port-adapter-slotnumber/interface-port-number
Interface processor slot0 through

12 (depends on the number of slots in
the router)
3/1/0
Port adapter slotalways 0 or 1

Interface port0 or 1
Note
Note
20-4

Bus connector
Packet
memory
DIMM U5
Port adapter
in slot 0
CPU
CPU memory
DIMM U1
Port adapter
in slot 1
26561
Chapter 20
20-5
Chapter 20
Removing the VIP4
Removing the VIP4

You must remove the VIP4-80 in order to replace the PA-2FE. This section describes the procedure for
removing a VIP4-80 from the router.
Note
Online Insertion and Removal (OIR), page 6
Shutting Down an Interface, page 6
Procedure for Removing the VIP4, page 8

port adapter is to be removed for replacement, we recommend that you inhibit and shut down any
in-service links before you remove the VIP. This will allow traffic to be rerouted to the alternate links or
linkset. If removal of the affected VIP is performed while links within a linkset are active, rerouting of
traffic will also occur to the alternate linkset on the redundant VIP. It is required that the 7500 system
Note
Shutting Down an Interface

Before you remove an interface that you will not replace, or replace port adapters, use the shutdown
command to shut down (disable) the interfaces to prevent anomalies when you reinstall the new or
reconfigured port adapter. When you shut down an interface, it is designated administratively down in
the show command displays.
Follow these steps to shut down an interface:
Step 1
Enter the privileged level of the EXEC command interpreter (also called enable mode). (See the Using
the EXEC Command Interpreter section on page 15 for instructions.)
20-6
Chapter 20

Removing the VIP4
Step 2
At the privileged-level prompt, enter configuration mode and specify that the console terminal is the
source of the configuration subcommands, as follows:
Router(config)#
Step 3
Shut down interfaces by entering the interface fastethernet subcommand (followed by the interface
address of the interface), and then enter the shutdown command. When you have finished, press
Ctrl-Zhold down the Control key while you press Zor enter end or exit to exit configuration mode
and return to the EXEC command interpreter.
Command
Example
interface, followed by the type (fastethernet) and

slot/port adapter/port
(interface-processor-slot-number/
port-adapter-slot-number/
interface-port-number)
The example is for interface 1 and interface 0 on

a port adapter in port adapter slot 1 of a VIP
installed
in interface processor slot 1.
Note
Step 4
Router(config-if)#
1/1/1
Router(config-if)#
Router(config-if)#
1/1/0
Router(config-if)#
Ctrl-Z
Router#
interface fastethernet
shutdown
interface fastethernet
shutdown
If you need to shut down additional interfaces, enter the interface fastethernet command
(followed by the interface address of the interface) for each of the interfaces on your
port adapter. Use the no shutdown command to enable the interface.

[OK]
Router#
The system displays an OK message when the configuration has been stored in NVRAM.
Step 5
Verify that new interfaces are now in the correct state (shut down) using the
show interfaces command.
20-7
Chapter 20
Removing the VIP4
Command
Example
show interfaces fastethernet, followed by

slot/port adapter/port
(interface-processor-slot-number/
port-adapter-slot-number/
The example is for interface 0 on a port adapter

in port adapter slot 1 of a VIP in interface
processor slot 1.
fastethernet 1/1/0 is administratively
down, line protocol is down
[Additional display text omitted from this
example]
Step 6
Reenable interfaces by doing the following:

a.
Repeat Step 3 to reenable an interface. Substitute the no shutdown command for the shutdown
command.
b.
Repeat Step 4 to write the new configuration to NVRAM. Use the

copy running-config startup-config command.
c.
Repeat Step 5 to verify that the interfaces are in the correct state. Use the
show interfaces command followed by the interface type and interface address of the interface.

Step 1
Step 2
Step 3
system.
Step 4
Step 5
Caution
Step 6
Step 7
20-8
Chapter 20

Step 8
system.
Step 9
ready to remove or install the Fast Ethernet Port Adapter. Proceed to the Replacing Port Adapters
section on page 9.

This section describes the procedures for removing port adapters from the failed VIP and installing the
port adapters on the replacement VIP
for removing and installing a port adapter.
The single-width port adapters that occupy either or both of the two port adapter slots on a VIP4. When
a single-width port adapter slot is not in use, a blank port adapter must fill the empty slot to allow the
router to conform to electromagnetic interference (EMI) emissions requirements and to allow proper
Caution
Metal carrier
H6420
Caution
Caution
To prevent interface reconfiguration requirements, you should replace a port adapter with
the same type of port adapter you removed, but this is not a requirement.
20-9
Chapter 20
Warning
yourself.
After you have reviewed the preceding safety precautions, you are ready to remove or install PA-2FE on
the VIP4-80. Proceed to the Illustrated Procedure for Removing and Installing the PA-2FE section on
page 11.
20-10

Illustrated Procedure for Removing and Installing the PA-2FE
Figure 20-11 describes removing and installing a single-width port adapter such as the Fast Ethernet Port
Adapter.

VIP4.
Step 1
remove
(See A.)
Step 2
Screw
Step 3
Carrier
Upper edge
Lower edge
Step 4
the screw. (See A.)
C
NO
RM
AL
Captive
installation
screw
PA-MC-8TE1-SS7
7
6
IL
PO
WE
EC
T
5
EJ
SL SLO
OT T
0 1
SL MAS
AV TE
E
R
3
O
SL
AV
E/
MAS
CPU
RES
TE
HAL
Step 5
(See B.)
FA
T
1
AC
ET
DC
DC
AC
FA
IL
PO
WE
EN
EN
AB
LE
AU
CO
X.
NSO
LE
Step 6
29327
Note
AL
Chapter 20
20-11
Chapter 20
After you have removed the port adapters from the failed VIP and reinstalled them on the replacement
VIP, you are ready to reinstall the VIP in the router chassis and connect the port adapter cables. Proceed
to the Reinstalling the VIP4 and Connecting the Port Adapter Cables section on page 12.

Connecting a PA-2FE RJ-45 or SC Cable, page 13

Note
Procedure for Removing and Installing the PA-2FE section on page 11. If you have already
reinstalled the VIP in the router chassis, proceed to the Connecting a PA-2FE RJ-45 or SC Cable
section on page 13.
After you have installed the Fast Ethernet Port Adapter on the VIP4-80, you must reinstall the VIP. The
VIP4 slides into an open interface processor slot and connects directly to the backplane. The interface
processors are keyed to guide pins on the backplane, so the VIP4 can be installed only in an interface
processor slot.
Note
routers.
Caution
20-12
Chapter 20


Step 1
Step 2
Step 3
Caution
Step 4
Step 5
Caution
Step 6
into its slot.
Step 7
Caution
Connecting a PA-2FE RJ-45 or SC Cable

To continue your PA-2FE port adapter installation, you must install the port adapters interface cables.
The following instructions apply to all supported platforms.
RJ-45 and SC-type fiber-optic cables are not available from Cisco; they are available from commercial
cable vendors.
Use the following procedure to connect RJ-45 or SC cables:
Step 1
If you have RJ-45 connections (PA-2FE-TX), attach the Category 5 unshielded twisted-pair (UTP) cable
directly to an RJ-45 port on the PA-2FE-TX. (See Figure 20-12.) The PA-2FE is an end station device
and not a repeater. You must connect the PA-2FE to a repeater, hub, or back-to-back to another
10/100-Mbps Fast Ethernet adapter.
If you have SC connections (PA-2FE-FX), attach the cable directly to an SC port on the PA-2FE-FX.
20-13
Chapter 20
(See Figure 20-13.) Use either one duplex SC connector or two simplex SC connectors, and observe the
correct relationship between the receive (RX) and transmit (TX) ports on the PA-2FE-FX and your
repeater.
Note
Port adapters have a handle attached, but this handle is not shown to allow a full detailed view
of each port adapters faceplate.
Figure 20-12 Connecting a PA-2FE-TX RJ-45 CableHorizontal Orientation (Shown Without Handles)
PA-2FE-TX
D
0
LI
NK
TX
RX
TX
RX
1
LI
NK
46455
LE
AB
EN
RJ-45 cable
RJ-45 cable
To repeater
or DTE
To repeater
or DTE
Figure 20-13 Connecting PA-2FE-FX SC CablesHorizontal Orientation (Shown Without Handles)
RX
TX
D L
1
E
LE E
S
1 TD
T
LA
C E N
C
U S
E
D S YA
0
D
O LA O
D
R K V
P IT EC
LE
1
D M
AVSE
TO
LE T
C
1 K IT S
U
S U U LA
D
S ODOD C
O
R
LA R R E
P
C P P D
RX
0
RX
TX
1
RX
TX
1
LI
NK
Simplex (2)
To repeater
Duplex (1)
To repeater
20-14
46456
PA-2FE-FX
D
LE
0
AB
0
NK
EN
LI
TX
Chapter 20

Configuring the PA-2FA
Caution
Only connect cables that comply with EIA/TIA-568 standards. (See Receptacles, Cables, and Pinouts
section on page 5 for cable recommendations and specifications.)
Step 2
Attach the network end of your RJ-45 or SC-type cable to your 10/100BaseT transceiver, switch, hub,
repeater, DTE, or other external 10/100BaseT equipment.

To continue your PA-2FE port adapter installation, you must configure the Fast Ethernet interfaces.
This section includes the following information:
Using the EXEC Command Interpreter, page 15
Configuring the Interfaces, page 15
Using the EXEC Command Interpreter

You modify the configuration of your router through the software command interpreter called the EXEC
(also called enable mode). You must enter the privileged level of the EXEC command interpreter with
the enable command before you can use the configure command to configure a new interface or change
the existing configuration of an interface. The system prompts you for a password if one has been set.
The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>).
At the console terminal, use the following procedure to enter the privileged level:
Step 1
At the user-level EXEC prompt, enter the enable command. The EXEC prompts you for a
privileged-level password as follows:
Router> enable
Password:
Step 2
Enter the password (the password is case sensitive). For security purposes, the password is not displayed.
When you enter the correct password, the system displays the privileged-level system prompt (#):
Router#
To configure the new interfaces, proceed to the Configuring the Interfaces section on page 15.
Configuring the Interfaces

After you verify that the new PA-2FE is installed correctly (the enabled LED goes on), use the
privileged-level configure command to configure the new interfaces. Have the following information
available:
Protocols you plan to route on each new interface
IP addresses, if you plan to configure the interfaces for IP routing
20-15
Chapter 20
Bridging protocols you plan to use
If you installed a new PA-2FE or if you want to change the configuration of an existing interface, you
must enter configuration mode to configure the new interfaces. If you replaced a PA-2FE that was
previously configured, the system recognizes the new interfaces and brings each of them up in their
existing configuration.
You can configure each of the interfaces on a PA-2FE at:
100 Mbps, half duplex, for a maximum aggregate bandwidth of 200 Mbps per pair. Half-duplex
operation is the default.
You can also configure one PA-2FE interface at 100 Mbps, half duplex, and the second PA-2FE interface
at 200 Mbps, full duplex, for a maximum aggregate bandwidth of 300 Mbps per pair.
You execute configuration commands from the privileged level of the EXEC command interpreter, which
usually requires password access. Contact your system administrator, if necessary, to obtain password
access. (See the Using the EXEC Command Interpreter section on page 15 for an explanation of the
privileged level of the EXEC.)
Performing a Basic Configuration

Following are instructions for a basic configuration: enabling an interface, and specifying IP routing.
You might also need to enter other configuration subcommands, depending on the requirements for your
system configuration and the protocols you plan to route on the interface. For complete descriptions of
configuration subcommands and the configuration options available for Fast Ethernet interfaces, refer to
the appropriate software documentation.
In the following procedure, press the Return key after each step unless otherwise noted. At any time you
can exit the privileged level and return to the user level by entering disable at the prompt as follows:
Router# disable
Router>
Step 1
subcommands, as follows:
Router(config)#
Step 2
Step 3
Specify the first interface to configure by entering the interface fastethernet subcommand, followed by
the interface address of the interface you plan to configure.
Command
Example
interface, followed by type (fastethernet) and

slot/port-adapter/port (interfaceprocessor-slot-number/port-adapterslot-number/interface-port-number).
The example is for the first interface of the first

port adapter on a VIP in interface processor
slot 1.
the interface address of the interface you plan to configure. Table 20-2 gives examples.
20-16
Router (config)# interface fastethernet

1/0/0
Chapter 20

Table 20-2 Examples of the interface fastethernet Subcommand
Platform
Command
Example
Cisco 7120 series routers
interface, followed by type

(fastethernet) and slot/interface
(port-adapter-slot-number/
The example is for the first interface of a

port adapter in port adapter slot 3.
Cisco 7401ASR routers
VIP2 and VIP4 in


(fastethernet) and
slot/port-adapter/port (interfaceprocessor-slot-number/port-adapterslot-number/interface-port-number).
Router(config)# interface fastethernet 3/0

Router(config-if)#

Router(config-if)#
The example is for the first interface of the port

adapter in slot 4.
Router (config)# interface fastethernet 4/0

Router(config-if)#
The example is for the first interface of the first port

adapter on a VIP in interface processor slot 1.
Router (config)# interface fastethernet
1/0/0
Note
The PA-2FE is automatically configured with 100-Mbps interfaces. If Cisco IOS software detects that
the PA-2FE is connected to a 10-Mbps interface, the PA-2FE will automatically be configured to run at
10-Mbps. Use the speed [10 | 100 | auto] command to manually set the Fast Ethernet speed.
Step 4
Assign an IP address and subnet mask to the interface (if IP routing is enabled on the system) by using
the ip address subcommand, as in the following example:
Router(config-if)# ip address 10.0.0.0 10.255.255.255
Step 5
Add any additional configuration subcommands required to enable routing protocols and set the
interface characteristics.
Step 6
Reenable the interfaces using the no shutdown command. (See the Shutting Down an Interface section
on page 6.)
Step 7
Configure all additional port adapter interfaces as required.
Step 8
After including all of the configuration subcommands to complete your configuration, press
Ctrl-Zhold down the Control key while you press Zor enter end or exit to exit configuration mode
and return to the EXEC command interpreter prompt.
Step 9

[OK]
Router#
20-17
Chapter 20
This completes the procedure for creating a basic configuration. To check the interface configuration
using show commands, proceed to the following section, Checking the Configuration.

This section describes 2 methods for verifying proper installation and configuration:
Using show Commands to Verify the New Interface Status, page 18
Observing the LEDs, page 21

Table 20-3 demonstrates how you can use the show commands to verify that new interfaces are
configured and operating correctly and that the PA-2FE appears in them correctly. Sample displays of
the output of selected show commands appear in the sections that follow.
Note
Table 20-3 Using show Commands
Command
Function
Example
show version or
show hardware
Displays system hardware

configuration, the number of
each interface type installed,
Cisco IOS software version,
names and sources of
configuration files, and boot
images
show controllers
Displays all the current interface

processors and their interfaces
Router# show controllers
show diag slot
Displays types of port adapters

installed in your system and
information about a specific
port adapter slot, interface
processor slot, or chassis slot
Router# show diag 2
show interfaces type

interface-processorslot-number/port-adapter-slot-number/
interface-port-number
Displays status information

about a specific type of interface
(for example, fastethernet) on a
VIP in a Cisco 7500 series router
show protocols
Displays protocols configured

for the entire system and for
specific interfaces
Router# show protocols
20-18
Chapter 20

Table 20-3 Using show Commands (continued)
Command
Function
Example
show running-config
Displays the running

configuration file
show startup-config
Displays the configuration

stored in NVRAM
If an interface is shut down and you configured it as up, or if the displays indicate that the hardware is
not functioning properly, ensure that the interface is properly connected and terminated. If you still have
problems bringing up the interface, contact a service representative for assistance.
Using the show version or show hardware Commands

Display the configuration of the system hardware, the number of each interface type installed, the Cisco
IOS software version, the names and sources of configuration files, and the boot images, using the show
version (or show hardware) command.
Note
VIP2 and VIP4 in Cisco 7500 Series Routers

Use the show version (or show hardware) command to display the configuration of the system
hardware (the number of each interface processor type installed), the software version, the names and
sources of configuration files, and the boot images. The following is an example of the show version
command from a Cisco 7500 series router with the PA-2FE:
IOS (tm) RSP Software (RSP-JSV-M), Version 12.1(20000701:015939) [485]
Compiled Wed 06-Sep-00 11:19 by pcl
Image text-base:0x60010970, data-base:0x616E2000
ROM:System Bootstrap, Version 11.1(8)CA1, RELEASE SOFTWARE (fc1)
BOOTFLASH:RSP Software (RSP-BOOT-M), Version 12.0(5), RELEASE SOFTWARE (fc1)
Router uptime is 5 minutes
System returned to ROM by reload
System image file is "tftp://172.168.0.0"
R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache
G.703/JT2 software, Version 1.0.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
Bridging software.
TN3270 Emulation software.
Chassis Interface.
1 EIP controller (6 Ethernet).
1 VIP2 controller (2 FastEthernet).
1 VIP2 R5K controller (2 FastEthernet).
20-19
Chapter 20
6 Ethernet/IEEE 802.3 interface(s)

4 FastEthernet/IEEE 802.3 interface(s)
No slave installed in slot 7.
Using the show diag Command

Display the types of port adapters installed in your system (and specific information about each) using
the show diag slot command.

Use the show diag slot command to determine which type of port adapter is installed on a VIP in your
system. Specific port adapter information is displayed, as shown in the following example of a
PA-2FE-TX in port adapter bay 0 and a PA-2FE-FX in port adapter bay 1 of a VIP2 installed in interface
processor slot 3:
Router# show diag 3
Slot 3:
Physical slot 3, ~physical slot 0xC, logical slot 3, CBus 0
Board is analyzed
Pending I/O Status:None
VIP2 R5K controller, HW rev 2.02, board revision C0
Serial number:13968891 Part number:73-2167-05
Test history:0x00
RMA number:00-00-00
Flags:cisco 7000 board; 7500 compatible
0x20:01 1E 02 02 00 D5 25 FB 49 08 77 05 00 00 00 00
0x30:60 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00
Flags:0x4
Insertion time:0x2750 (00:06:45 ago)
Controller Memory Size:128 MBytes DRAM, 8192 KBytes SRAM
Dual Port Fast Ethernet (RJ45), 2 ports
HW rev 1.00, Board revision UNKNOWN
Serial number:MIC04291ZUY Part number:73-5419-01
Dual Port Fast Ethernet (MMF), 2 ports
HW rev 1.00, Board revision UNKNOWN
Serial number:MIC04291ZUY Part number:73-5419-01
20-20
Chapter 20

Using the show interfaces Command

The show interfaces command displays status information (including the physical slot and interface
address) for the interfaces you specify. All of the examples that follow specify Fast Ethernet interfaces.

Use the show interfaces type slot/port-adapter/port command, with arguments such as the interface type
(for example, fastethernet) and the port number (slot/port), to display information about a specific
interface. The following example of the show interfaces fastethernet command shows information
specific to a Fast Ethernet interface on the PA-2FE in slot 3:
FastEthernet3/0/0 is up, line protocol is up
Hardware is cyBus FastEthernet Interface, address is 0030.f233.a900 (bia 0030.f233.a900)
Internet address is 7.7.7.7/24
Encapsulation ARPA, loopback not set
Half-duplex, 100Mb/s, 100BaseTX/FX
ARP type:ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:05, output hang never
Queueing strategy:fifo
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
Observing the LEDs

The PA-2FE contains seven LEDS; an enabled LED, which is standard on all port adapters, a link LED,
and a transmit LED and receive LED for each of the ports. The LEDs are shown in Figure 20-3.
Figure 20-14 LEDs on the PA-2FEFaceplate View of PA-2FE-TX
PA-2FE-TX
K0
LIN
0
TX
1
RX
0
RX
1
TX
K1
LIN
46453
D
LE
AB
EN
After system initialization, the enabled LED goes on to indicate that the PA-2FE has been enabled for
operation. The following conditions must be met before the enabled LED goes on:
The PA-2FE is correctly connected and receiving power.
20-21
Chapter 20
A PA-2FE-equipped card or chassis contains a valid microcode version that has been successfully
downloaded.
The bus recognizes the PA-2FE or PA-2FE-equipped VIP.
If any of these conditions are not met, or if the initialization fails for other reasons, the enabled LED
does not go on. Table 20-4 lists port LED colors and indications.
Table 20-4 PA-2FE LEDs
LED Label
Color
State
Function
ENABLED
Green
On
Port adapter is enabled for operation.
LINK0
Green
On
Port 0 is receiving a carrier signal from the network.1
TX0
Green
On
Port 0 is transmitting data.
RX0
Green
On
Port 0 is receiving data.
RX1
Green
On
Port 1 is receiving data.
TX1
Green
On
Port 1 is transmitting data.
LINK1
Green
On
Port 1 is receiving a carrier signal from the network.
1. When an RJ-45 or SC port is active.
20-22
C H A P T E R
21

This chapter describes procedures that are required when you replace a failed VIP. The main sections
and procedures are:
VIP4 Overview, page 1
Online Insertion and Removal (OIR), page 2
Taking Port Adapters Out of Service, page 3
Verifying the VIP4 and SS7 Port Adapter Installation, page 12
Reactivating the Links Associated with the Port Adapter, page 17
VIP4 Overview
Note
Note
21-1
Chapter 21
VIP4 Overview
Bus connector
Packet
memory
DIMM U5
CPU memory
DIMM U1
Port adapter
in slot 1
26561
Port adapter
in slot 0
CPU

port adapter is to be removed for replacement, we recommend that you inhibit and shut down any in
service links before you remove the VIP. This will allow traffic to be rerouted to the alternate links or
linkset. If removal of the affected VIP is performed while links within a linkset are active, rerouting of
traffic will also occur to the alternate linkset on the redundant VIP. It is required that the 7500 system
Note
21-2
Chapter 21


The VIP that you are replacing has either an SS7 low-speed link (LSL) adapter or an ATM HSL two port
adapter or both. You must administratively remove the port adapters from service before you physically
remove the failed VIP on which the port adapters are installed.
This section describes the procedures for administratively taking the port adapters out of service.
Taking an SS7 PA Out of Service, page 3
Taking an HSL PA Out of Service, page 4

Identifying and Disabling SS7 Links
Before you disable and remove an SS7 Port Adapter (SS7 PA) from an ITP, you must identify and take
out of service (inhibit and shut down) all the links using that port adapters interfaces. This procedure
describes the steps to inhibit and shut down the links and controllers of an SS7 PA before you can
physically remove the VIP from the ITP.
Note
all links before disabling (shutdown) them is a safeguard that allows the ITP to ensure that no
if a destination becomes inaccessible or a different (already inhibited) link may be out back in
service. If this situation occurs, one workaround could be to first inhibit all A-links, then inhibit as
many C/D-links as possible and last shut down the C-links.
Use the following commands, beginning in privileged EXEC mode:
Command
Purpose
Step 1
Step 2

Step 3

access a linkset.
Step 4

configuration mode.
Step 5
Router(config-ls)# link slc serial number

Step 6
Disables the link.
21-3
Chapter 21
Note

To disable the controller, use the following commands, beginning in global configuration mode.
Command
Purpose
Step 1
Router(config)# controller type slot/bay/port
Identify the controller and enable controller

configuration mode.
Step 2

Identifying and Disabling Links
Before you disable an HSL Port Adapter you must identify and disable all the links using that port
adapter. Use the following commands, beginning in privileged EXEC mode:
Note
Step 1
To ensure that backup routes are available before taking links out of service, inhibit the links. You
can not inhibit the last link (or the only link) in a linkset; you will receive an error message indicating
that the inhibit was denied. However, you can still choose to shut down the link.
Command
Purpose

Look for the ATM interface to identify the links
that you will need to shutdown. Note the linkset
name.
Step 2

Step 3

access a linkset.
Step 4

configuration mode.
Step 5
Router(config-ls)# link slc atm number

Step 6
Disables the link.
21-4
Chapter 21

Note

Command
Step 1
Step 2
Purpose
21-5
Chapter 21
Removing the VIP4
Removing the VIP4

You must remove the VIP4-80 in order to replace the SS7 Port Adapter. This section describes the
procedure for removing a VIP4-80 from the router.
Note
Caution
In Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX routers with the high
system availability (HSA) or high availability (HA) feature enabled, online insertion and
removal of any interface processor in either CyBus might cause the standby RSP2 to reboot
with a bus error or a processor memory parity error. The active RSP recovers from this
event and issues a cBus Complex Restart message. Systems that are configured with an
RSP4 or an RSP8 as the system standby are not affected and do not experience this
problem. For more information on HSA or HA, refer to your RSP Installation and

If your router does not have the HSA or HA feature enabled, perform only Step 4 through Step 7 in the
following procedure. If the router has the HSA or HA feature enabled with an RSP2 configured as the
system standby, we recommend that you perform all the steps in the following procedure:
Step 1
Step 2
Step 3
system.
Step 4
Step 5
Caution
Step 6
Step 7
21-6
Chapter 21

Note
If you do not have a Cisco 7507 or Cisco 7513 with the HSA or HA features
enabled and an RSP2 configured as the system standby, proceed to the section
Replacing Port Adapters; otherwise, proceed to Step 8.
Step 8
system.
Step 9
ready to remove or install the SS7 Port Adapter. Proceed to the Replacing Port Adapters section on
page 7.

This section describes the procedures for removing port adapters from the failed VIP and installing the
port adapters on the replacement VIP
for removing and installing a port adapter.
The single-width port adapters that occupy either or both of the two port adapter slots on a VIP4. When
a single-width port adapter slot is not in use, a blank port adapter must fill the empty slot to allow the
router to conform to electromagnetic interference (EMI) emissions requirements and to allow proper
Metal carrier

H6420
Caution
21-7
Chapter 21
Caution
Caution
To prevent interface reconfiguration requirements, you should replace a port adapter with
the same type of port adapter you removed, but this is not a requirement.
Warning
yourself.
After you have reviewed the preceding safety precautions, you are ready to remove or install the SS7
Port Adapter on the VIP4-80. Proceed to the Illustrated Procedure for Removing and Installing the SS7
Port Adapter section on page 9.
21-8

Illustrated Procedure for Removing and Installing the SS7 Port Adapter
Figure 21-3 describes removing and installing a single-width port adapter such as the SS7 Port Adapter.

VIP4.
Step 1
remove
(See A.)
Step 2
Screw
Step 3
Carrier
Upper edge
Lower edge
Step 4
the screw. (See A.)
C
NO
RM
AL
Captive
installation
screw
PA-MC-8TE1-SS7
7
6
IL
PO
WE
EC
T
5
EJ
SL SLO
OT T
0 1
SL MAS
AV TE
E
R
3
O
SL
AV
E/
MAS
CPU
RES
TE
HAL
Step 5
(See B.)
FA
T
1
AC
ET
DC
DC
AC
FA
IL
PO
WE
EN
EN
AB
LE
AU
CO
X.
NSO
LE
Step 6
29327
Note
AL
Chapter 21
21-9
Chapter 21
After you have removed the port adapters from the failed VIP and reinstalled them on the replacement
VIP, you are ready to reinstall the VIP in the router chassis and connect the port adapter cables. Proceed
to the Reinstalling the VIP4 and Connecting the Port Adapter Cables section on page 10.


Note
Procedure for Removing and Installing the SS7 Port Adapter section on page 9. If you have already
reinstalled the VIP in the router chassis, proceed to the Connecting the SS7 Port Adapter Interface
Cables section on page 11.
After you have installed the SS7 Port Adapter on the VIP4-80, you must reinstall the VIP. The VIP4
slides into an open interface processor slot and connects directly to the backplane. The interface
processors are keyed to guide pins on the backplane, so the VIP4 can be installed only in an interface
processor slot.
Note
routers.
Caution
21-10
Chapter 21


Step 1
Step 2
Step 3
Caution
Step 4
Step 5
Caution
Step 6
into its slot.
Step 7
Caution

Note
Step 1
Step 2
21-11
Chapter 21
Step 3
AL
PA-MCX-8TE1-M
6
7
65854
EN
Twisted-pair cable
To PBX or PSTN
Note
Port adapters have a handle attached, but this handle is not shown in Figure 21-4 to allow a full view
of the detail on each port adapters faceplate.
Warning
To reduce the risk of fire, use only 26 AWG or larger telecommunication line cord.
Warning
Do not work on the system or connect or disconnect cables during periods of lightning activity.
Warning
To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to
telephone-network voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports
contain TNV circuits. Some LAN and WAN ports both use RJ-48C connectors. Use caution when
connecting cables.
This completes the VIP4 and SS7 Port Adapter installation. You can now verify the installation. Proceed
to the Verifying the VIP4 and SS7 Port Adapter Installation section on page 12.

This section describes the procedures you can use to verify your VIP4 and SS7 Port Adapter installation.
It includes information on the following topics:
Observing LEDs and System Messages, page 13
Using show Commands to Verify the VIP4 Status, page 15
Using show Commands to Display Interface Information, page 16
21-12
Chapter 21

Observing LEDs and System Messages

After you install the VIP4 and connect the SS7 Port Adapter cables, you can verify the installation by
AL
PA-MCX-8TE1-M
6
7
EN
65853
Note
for operation.
does not go on.
Table 21-1
LED Label
Color
State
Function
EN
Green
On
Off

disabled.
Amber
On

Red
On

of the T1/E1 ports.
Off
On
AL
0 through 7 Green
21-13
Chapter 21
Table 21-1
LED Label
SS7 Port Adapter LEDs (continued)
Color
State
Function
Yellow
On
Off

System Messages
When you remove and replace interface processors, the system provides status messages on the console
screen. The messages are for information only.
The following sample display shows the events logged by the system when a VIP4 with an SS7 Port
Adapter is removed from interface processor slot 4. The system reinitializes the remaining interface
processors and marks as down the SS7 Port Adapter interface on the VIP4 that was removed from slot 4:
Router#
00:51:01: %OIR-6-REMCARD: Card removed from slot 4, interfaces disabled
%LINK-5-CHANGED: Interface serial 4/0/0, changed state to administratively down
The following sample display shows the events logged by the system when a VIP4 with a SS7 Port
Adapter is reinserted into interface processor slot 4. The the system automatically brings up the
interfaces that were up when the VIP4 was removed:
Router#
00:52:35: %LINK-3-UPDOWN: Interface Serial4/0/0:1, changed state to up
When a new VIP4 is inserted or when a VIP4 is moved to a new slot, the system recognizes the new
interfaces but leaves them in the shutdown state until you configure them and change their state to up.
The following sample display shows the events logged by the system as you insert a new VIP4 in
interface processor slot 6:
Router#
To verify that the VIP4 is installed correctly, observe the LEDs and system messages as described in the
following steps. If you experience other problems that you are unable to solve, contact a service
representative for assistance.
Step 1
system discovers the VIP4 as follows:
If you installed a new VIP4, the system should recognize all new interfaces but leave them
configured as down. (You must configure new interfaces to make them available.)
If you replaced a VIP4, the system should recognize each interface and place it in the same state (up
or down) each was in when you removed the VIP4.
Step 2
When the reinitialization is complete, verify that the enabled LED on each port adapter goes on and
remains on. If it does, proceed to Step 5. If it does not, proceed to the next step.
Step 3
If the enabled LED on a port adapter fails to go on, suspect that the VIP4 board connector is not fully
seated in the backplane. Loosen the captive installation screws, and then firmly push both ejector levers
into place until they are approximately in the same orientation as the VIP4 faceplate. Tighten the
captive installation screws. After the system reinitializes the interfaces, the enabled LED on the port
adapter should go on. If it does, proceed to Step 5. If it does not, proceed to Step 4.
21-14
Chapter 21

Step 4
If the enabled LED still fails to go on, remove the VIP4 and try installing it in another available
If the enabled LED goes on when the VIP4 is installed in the new interface processor slot, suspect
a failed backplane port in the original interface processor slot.
If the enabled LED still fails to go on, but other LEDs go on to indicate activity, proceed to Step 5
to resume the installation checkout; suspect that the enabled LED on the port adapter has failed.
Contact a service representative to report the problem and obtain further instructions.
If no LEDs go on, suspect that the VIP4 is faulty. Contact a service representative to report the
problem and obtain further instructions.
If just the enabled LED still fails to go on, remove the VIP4 and ensure the port adapters are firmly
installed in their port adapter slots. Remove and reinstall them accordingly.
Step 5
If the VIP4 is new and not a replacement, you must configure all new interfaces to make them available.
(This does not have to be done immediately, but new interfaces are not be available until you configure
them.)
Step 6
If the VIP4 is a replacement, use the show interfaces type interface-processor-slotnumber/port-adapter-slot-number/interface-port-number command or the show controllers command
to verify the status of the interfaces. (See the following section, Using show Commands to Verify the
VIP4 Status.)
If you replaced a VIP4 with a new VIP4 with a greater number of interfaces (for example, if you replaced
a VIP4 with a single port adapter with a VIP4 with two port adapters), the system recognizes the
interfaces on the previously configured port adapter but does not recognize the additional port adapter
interfaces. The new interfaces remain in the shutdown state until you configure them.
Step 7
described in the appropriate LED section of your port adapter installation and configuration notes.
Step 8
In general, if an interface LED fails to go on and a cable is connected to the interface port, check the
cable connection and make certain it is properly seated in the connector.
Using show Commands to Verify the VIP4 Status

correctly.
Step 1
Step 2
Display all the current interface processors and their interfaces with the show controllers command.
Verify that the new VIP4 appears in the correct interface processor slot.
Step 3
Specify one of the new interfaces with the show interfaces type interface-processor-slotnumber/port-adapter-slot-number/interface-port-number command and verify that the first line of the
display specifies the interface with the correct slot number. Also verify that the interface and line
protocol are in the correct state: up or down.
Step 4
21-15
Chapter 21
Step 5
configuration stored in the RSP NVRAM using the show startup-config command. Verify that the
Note
The outputs that appear in this document may not match the output you receive when
running these commands. The outputs in this document are examples only.

To display information about a specific interface, use the show interfaces command in the format
show interface type interface-processor-slot-number/port-adapter-slot-number/interface-port-number
:channel-group-number.
The following is an example of the show interface serial command:
Router#show interface serial 4/0/0:0
Hardware is cxBus T1
Encapsulation SS7 MTP2, crc 16, loopback not set
Queueing strategy: fifo
Timeslot(s) Used:1, subrate: 56Kb/s, transmit delay is 0 flags
Router#
To display hardware information about all of the interface processors in your router, including the VIP4,
use the show controller command.
21-16
Chapter 21

Following is an example of the show controller command used with a Cisco 7500 series router:
Router#show controller t1 4/0/0
T1 4/0/0 is up.
No alarms detected.
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
Router#
To display the configuration of the system hardware (the number of each interface processor type
installed), the software version, the names and sources of configuration files, and the boot images, use
the show version (or show hardware) command.
To determine specific hardware configuration information about a VIP4 installed in your system
(including the amount of installed CPU and packet memory), use the show diag slot command.
Following example of a VIP4-80 with an SS7 Port Adapter; the VIP4-80 is installed in interface
processor slot 2:
Following is an example of the show diag slot command that shows an SS7 Port Adapter in interface
processor slot 2 of a Cisco 7513 router:
Router# show diag 2
Slot 2:
PA-MCX-8TE1-M Port adapter, 8 ports
Port adapter is analyzed
Port adapter insertion time 00:52:22 ago
EEPROM contents at hardware discovery:
Hardware Revision
: 1.0
PCB Serial Number
: SIC04412B7S
Part Number
: 115-22681-01
Board Revision
: 02
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Deviation Number
: 0-0
IDPROM FIELD FORMAT ERROR, index 0x29
0x00: 04 FF 40 03 52 41 01 00 C1 8B 53
0x10: 31 32 42 37 53 82 73 58 99 01 42
0x20: 00 00 00 00 04 00 80 00 00 00 00
0x30: 00 00 00 00 00 00 00 00 00 00 00
0x40: 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00
49
30
CB
00
00
00
00
00
43
32
00
00
00
00
00
00
30
03
00
00
00
00
00
00
34
00
00
00
00
00
00
00
34
81
00
00
00
00
00
00

After you have replaced the LSL or HSL port adapter, you must reactivate any links that you took out of
service. Follow the procedure that pertains to your port adapter type:
Reactivating Disabled SS7 Low Speed Links, page 18
Reactivating Disabled High Speed Links, page 18
21-17
Chapter 21
Reactivating Disabled SS7 Low Speed Links

To reactivate the SS7 low speed links that you previously took out of service, enter the following
commands, beginning in privileged EXEC mode:
Command
Purpose
Step 1
Router# controller type slot/bay/port
Specifies the controller (that you disabled earlier

in this procedure) and enables controller
configuration mode.
Step 2
Router(config-controller)# no shutdown
Enables the previously disabled controller.
Step 3
Router(config-controller)# exit
Exits controller configuration mode.
Step 4

access a linkset.
Step 5

configuration mode.
Step 6

Step 7
no shutdown
Step 8
exit
Step 9
Router(config-ls)#
Step 10
Router(config)#
Step 11
Note
exit
exit

Reactivating Disabled High Speed Links

To reactivate the high speed links that you previously took out of service, enter the following commands,
beginning in privileged EXEC mode:
Command
Purpose
Step 1
Specify the interface and enable interface

configuration mode.
Step 2
Router(config-if)# no shutdown
Reactivate the interface.
Step 3
Router(config-if)# exit
Exit interface configuration mode.
Step 4

configuration mode.
21-18
Chapter 21

Command
Purpose
Step 5

Step 6
Router(config-ls-link)# no shutdown
Step 7
Step 8
Router(config-ls)#
Step 9
Router(config)#
Step 1
Note
exit
exit
exit

21-19
Chapter 21
21-20
C H A P T E R
22

This chapter describes the following tasks:
Replacing a Failed RSP in a Non-Redundant Configuration, page 1
Replacing a Failed RSP8 in an RPR+ Configuration, page 13

The following sections describe the procedures for replacing a failed RSP in a non-redundant
(non-RPR+) configuration
For the procedure to replace a failed RSP8 in an RPR+ configuration, refer to .
Removing the RSP8, page 2
Inserting the RSP8, page 3
Restarting the System, page 6
Troubleshooting the Installation, page 8
Caution
Removing the only installed RSP8 from a system while the system is operating will cause
the system to cease operation. Consider this before removing an RSP8 while the system is
operating. To ensure that the standby RSP8 operates properly with the full system
configuration should the active RSP8 ever fail, RPR+ must be properly configured. See
Chapter 6, Configure and Maintain RSP Redundancy - RPR+.
Note
The carriers on processor modules have electromagnetic interference (EMI) fences for EMI
shielding; therefore, they fit very tightly in the chassis slots. To ensure that you can
properly remove or install an RSP8 on a 7513 in slot 7, we recommend that you proceed as
follows: first remove an interface processor installed in slot 8, remove or install the RSP8
in RSP slot 7 (and fasten its captive installation screws as appropriate), and then reinstall
the interface processor in slot 8.
22-1
Chapter 22
Removing the RSP8

When you remove or install the RSP8, be sure to use the ejector levers, which help to ensure that the
RSP8 is fully inserted in the backplane or fully dislodged from it. An RSP8 that is only partially
connected to the backplane can halt the system unless a second RSP8 is installed.
Figure 1 shows a detail of the ejector lever mechanism that is appropriate for the router. When you
simultaneously push the ejector levers inward (toward the carrier handle), the levers push the RSP8 into
the slot and ensure that the board connectors are fully seated in the backplane. Follow these steps to
remove the RSP8:
Step 1
Attach an antistatic strap to yourself and then connect the equipment end of the strap to a captive
installation screw on an installed interface processor, or to any unfinished chassis surface.
Step 2
If you are replacing the RSP8, disconnect any devices that are attached to the console or auxiliary ports.
If you are removing the RSP8 for maintenance and will reinstall the same one, you can leave the
devices attached provided that doing so will not strain the cables.
Step 3
Use a screwdriver to loosen the two captive installation screws. (See Figure 1.)
Step 4
Place your thumbs on the ends of each of the ejectors and simultaneously pull them both outward, away
from the carrier handle (in the opposite direction from that shown in c of Figure 1) to release the carrier
from the slot and to dislodge the RSP8 from the backplane.
Step 5
Grasp the handle of the RSP8 with one hand and pull the RSP8 straight out of the slot, keeping your
other hand under the carrier to guide it. (See Figure 2.) Keep the carrier parallel to the backplane. Avoid
touching the board or any connector pins.
22-2
Chapter 22

Figure 1
Ejector Levers and Captive Installation Screw

Processor module
slot
Processor
module
carrier guide
Captive
installation
screw
c
H1482a
Stop
immediately
on contact
Step 6
Place the removed RSP8 on an antistatic mat or foam. If you plan to return the RSP8 to the factory,
immediately place it in an antistatic bag to prevent ESD damage.
Step 7
Attach the equipment end of the ESD-preventive strap to the RSP8 before performing any maintenance
on the RSP8 that might create an ESD hazard.
Inserting the RSP8

The RSP8 is keyed for installation only in an RSP slot. By default, the system active is the RSP that
occupies the first RSP slot in the router: slot 2 in the Cisco 7507 and Cisco 7507-MX, and slot 6 in the
Cisco 7513 and Cisco 7513-MX. Follow these steps to install an RSP8:
22-3
Chapter 22
Step 1
Grasp the RSP8 handle with one hand and place your other hand under the carrier to support and guide
it into the slot. (See Figure 2.) Avoid touching the board or any connectors.
Step 2
Place the back of the RSP8 in the appropriate RSP slot and align the notches along the edge of the
carrier with the grooves in the slot. (See a in Figure 1.)
Handling the RSP8 During Removal and Installation
H1355a
Figure 2
Caution
To prevent damage to the backplane, you must install the RSP8 in one of the two RSP slots
on the router. The slots are keyed for correct installation. Forcing the RSP8 into a different
slot can damage the backplane and the RSP8.
Step 3
While keeping the RSP8 parallel to the backplane, carefully slide the carrier into the slot until the RSP8
faceplate makes contact with the ejector levers, and then stop. (See b in Figure 1.)
Step 4
Using the thumb and forefinger of each hand to pinch each ejector lever, simultaneously push both
ejector levers inward (toward the handle) until they are parallel to the faceplate. (See c in Figure 1.)
Step 5
Use a screwdriver to tighten the captive installation screws on the ends of the RSP8. (See a in Figure 1.)
Step 6
Use a screwdriver to tighten the two captive installation screws on the RSP8 faceplate to prevent the
RSP8 from becoming partially dislodged from the backplane and to ensure proper EMI shielding.
(These screws must be tightened to meet EMI specifications.)
Step 7
If you disconnected the console terminal to remove the RSP8, or if you are installing a new RSP8,
connect the console terminal to the console port. (See the Connecting a Console Terminal section on
page 5.)
Step 8
Ensure that a console terminal is connected (see the Connecting a Console Terminal section on
page 5) and that it is turned on.
22-4
Chapter 22

Step 9
Turn the system power back on, and proceed to the Restarting the System section on page 6 to check
the installation.
Connecting a Console Terminal

The system console port on the RSP8 is a DB-25 receptacle DCE port for connecting a data terminal,
which you need to configure in order to communicate with your system. The console port is located on
the RSP8 just below the auxiliary port, as shown in Figure 3, and is labeled Console.
Before connecting the console port, check the documentation for your terminal to determine the baud
rate of the terminal you are using. The baud rate of the terminal must match the default baud rate (9600
baud). Set up the terminal as follows: 9600 baud, 8 data bits, no parity, and 2 stop bits (9600,8N2). Use
the console cable provided to connect the terminal to the console port on the RSP8, and then follow the
steps in the Restarting the System section on page 6.
Figure 3
Console and Auxiliary Port Connections

DB-25 female
Modem
Auxiliary
port
Console
port
DB-25 male
RSP
Note
H3538
Console terminal
The console and auxiliary ports are asynchronous serial ports; any devices connected to
these ports must be capable of asynchronous transmission. (Asynchronous is the most
common type of serial device; for example, most modems are asynchronous devices.)
Connecting to the Auxiliary Port

The auxiliary port on the RSP8 is a DB-25 plug DTE port for connecting a modem or other DCE device
(such as a channel service unit [CSU], data service unit [DSU], or other router) to the router. The port is
located next to the console port on the RSP8 and is labeled AUX. An example of a modem connection is
shown in Figure 3.
22-5
Chapter 22
Using the Y-Cables for Console and Auxiliary Connections

For systems with two RSP8s installed (one as active and one as standby in RSP slots 2 and 3 in the
Cisco 7507 and Cisco 7507-MX, and slots 6 and 7 in the Cisco 7513 and Cisco 7513-MX, using the HSA
feature), you can simultaneously connect to both console or auxiliary ports using a special, optional
Y-cable. If only one RSP8 is installed, it is the system active by default.
Note
The Y-cables are not required for the RSP8s in your Cisco 7507, Cisco 7507-MX,
Cisco 7513, or Cisco 7513-MX; two individual console cables and two individual auxiliary
cables can be used instead.
Figure 4 shows the console Y-cable and Figure 5 shows the auxiliary Y-cable.
Console Y-Cable (CAB-RSP8CON=)
CONSOLE
DB-25 female
Console connectors
to console ports on two
RSP8s in RSP slots
CONSOLE
DB-25 male
27128
To console terminal
Figure 5
DB-25 male
Auxiliary Y-Cable (CAB-RSP8AUX=)
AUXILIARY
DB-25 male
DB-25 female
Auxiliary connectors
to auxiliary ports on two
RSP8s in RSP slots
To external
auxiliary equipment
AUXILIARY
DB-25 female
27129
Figure 4
Restarting the System

When you turn the system power back on, verify that the system boots and resumes normal operation. If
you are restarting the system after upgrading the DRAM, expect that it will take the system longer to
complete the memory initialization portion of the boot sequence with more DRAM. (See the Verifying
System Startup Sequence section on page 10.)
Follow these steps to verify that the RSP8 is installed and functioning properly:
22-6
Chapter 22

Step 1
Check the RSP8 connections to make sure they are secure:
The RSP8 is inserted all the way into its slot, and both captive installation screws are tightened.
The console terminal is turned on and is connected to the console port.
Step 2
Observe the RSP8 LEDs. While the system initializes, the CPU halt LED on the RSP8 stays on. It goes
off when the boot process is complete. As the RSP8 initializes each interface processor, the status
LEDs on each interface processor go on and off in irregular sequence.
Step 3
For a Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX with HSA configured, verify that
the console terminal displays the system banner and startup screen as the system restarts.
The active console display should look similar to the following for a Cisco 7513 and Cisco 7513-MX
(note the RSP slots indicated):
System Bootstrap, Version 12.0(9)S, RELEASED SOFTWARE

SLOT 6 RSP8 is system master
SLOT 7 RSP8 is system slave
RSP8 processor with 128 Mbytes of main memory
[additional displayed text omitted from this example]
IOS (tm) RSP Software (RSP-JSV-M), Version 12.0(9)S [biff 51096]
Compiled Mon 22-Sep-99 21:15 by biff
Image text-base: 0x600108A0, data-base: 0x607B8000
R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
Slave in slot 7 is halted.
The active console display should look similar to the following for a Cisco 7507 and Cisco 7507-MX
(note the RSP slots indicated):

Slave in slot 3 is halted.
Step 4
With a single RSP8 (non-HSA), verify that the console terminal displays the system banner and startup
screen as the system restarts. The display should look similar to the following:
22-7
Chapter 22
Step 5
Note
After the system boots the software and initializes the interface processors, verify that the RSP8 LEDs
are in the following states:
RSP8 normal LED is on (for each RSP8 installed).
CPU halt LED is off (for each RSP8 installed).
Master RSP8 active LED is on.
Slave RSP8 standby LED is on (if HSA is configured).
Boot time is approximately 1 minute for systems with one RSP8 and approximately
1.5 minutes for systems with two RSP8s. These times vary with system configuration and
with the source location of the image being booted.
Step 6
Verify that all the enabled LEDs (on the interface processors) are on.
Step 7
In systems with a second RSP8 installed (and HSA configured), use the show version command to
verify that the standby RSP8 is recognized by the system. Following is a sample from a Cisco 7513:
Router> show version
IOS (tm) RSP Software (RSP-JSV-M), Version 12.0(9)S [biff 51096]
Compiled Mon 22-Sep-99 21:15 by biff
Image text-base: 0x600108A0, data-base: 0x607B8000
Slave in slot 7 is running Cisco Internetwork Operating System Software
(Note that this could also be slot 6 depending on which RSP is configured as the standby or the recent
crash history of your router.)
An error condition exists if no LEDs go on at power up or after initialization, or if the boot error or CPU
halt LEDs go on and remain on. If this happens, proceed to the Troubleshooting the Installation section
on page 8 to try to isolate the problem.
Troubleshooting the Installation

This section contains procedures to follow if your system does not restart and boot up as expected.
Review the descriptions that follow so you can anticipate the expected system startup sequence. Then
restart the system and try to isolate the problem by observing the LEDs as the system attempts to boot
the software and initialize the RSP8s and each interface processor.
Verifying LEDs
Following are functional descriptions of the LEDs on the power supplies and processor modules, and the
behavior you should observe at system startup.
System Power LEDs

On the router, the AC (or DC) OK LED is located on each power supply. If this LED does not go on and
stay on, there is most likely a problem with the input power or one of the internal DC lines.
22-8
Chapter 22

The AC (or DC) OK LED will not go on or will go off if the power supply reaches an out-of-tolerance
temperature or voltage condition. It is unlikely that the power supply will shut down during startup
because of an over-temperature condition; however, it can shut down if it detects an over- or
undervoltage condition during startup. For descriptions of environmental monitoring functions, refer to
the Cisco 7500 Series Installation and Configuration Guide, which is available on the Documentation
CD-ROM or in print.
RSP8 LEDs
Figure 6 shows the LEDs on the RSP8 faceplate. The LEDs on the RSP8 indicate the system and RSP8
status and which PC Card slot is active. The CPU halt LED, which goes on only if the system detects a
processor hardware failure, should remain off. A successful boot is indicated when the normal LED goes
on; however, this does not necessarily mean that the system has reached normal operation. During
normal operation, the CPU halt LED should be off, and the normal LED should be on, indicating that
the RSP8 is receiving +5V. The slot 0 and slot 1 LEDs indicate which PC Card slot is in use, and each
LED blinks when the card is accessed by the system. The active and the standby LEDs provide a visual
indication of whether the RSP8 is designated an active or a standby device.
RSP8 LEDs, Active/Standby Switch, and Reset Switch (Vertical Partial Front-Panel View)
NO
RM
AL
SL
SL
OT
Standby
OT
MA
SL
AV
Active
ST
ER
ST
AN
DB
Y/A
CT
IVE
CP
UH
AL
RE
SE
H7187
Figure 6
22-9
Chapter 22
Caution
The reset switch (see Figure 6) resets the RSP8 and the entire system. To prevent system
errors and problems, use it only at the direction of your Cisco-certified service
representative.
Interface Processor LEDs

Each interface processor contains an enabled LED. The enabled LED goes on to indicate that the
interface processor is operational and that it is powered up. It does not necessarily mean that the interface
ports on the interface processors are functional or enabled. When the boot sequence is complete, all the
enabled LEDs should go on.
If any do not, one of the following errors is indicated:
The interface processor is not installed correctly (it is not fully seated in the backplane connector).
The microcode and software that are loading at startup are not compatible.
The interface processor has failed.
Verifying System Startup Sequence

By checking the state of the LEDs, you can determine when and where the system failed in the startup
sequence. Because you turn on the system power with the on/off switches on each power supply, it is
easiest to observe the startup behavior from the rear of the router. Use the following descriptions of the
normal startup sequence to isolate the problem, and then use the troubleshooting procedures wherever
the system fails to operate as expected. If you are able to isolate the problem to a faulty hardware
component, or if you are unable to successfully restart the system, see the end of this document for
instructions on contacting a service representative.
Note
The time required for the system to initialize (boot) might vary with different router
configurations and the amount of memory that must be initialized. During the system
startup sequence, the time required to initialize the memory (not necessarily the entire boot
sequence) in a system that contains 256 MB of DRAM might be longer than in a system
that contains less DRAM.
During the boot sequence, the system banner display pauses while it initializes the memory. Because
your RSP8 has more than 32 MB of DRAM, you might notice an increase in the amount of time required
to initialize the memory. The pause in the banner display occurs after the copyright line and before the
system displays the list of installed hardware, as shown in the following display:
%SYS-5-RELOAD: Reload requested
System Bootstrap, Version 12.0(9)S
[System initializes memory at this point in the display]
Note
The procedures in this section are based on the assumption that your system was operating
correctly until you removed (or replaced) the RSP8. If the following sequence uncovers a
new problem with the power subsystem or one of the interface processors, refer to the Cisco
7500 Series Installation and Configuration Guide for system startup troubleshooting
procedures.
Use the following startup sequences and troubleshooting procedures to isolate system problems:
22-10
Chapter 22

Step 1
When you restart the system, the system power and AC (DC) OK LEDs should go on.
If the system power LED remains off, the RSP8 is probably not fully inserted and connected to the
backplane. Loosen the captive installation screws on the RSP8, and then use the ejector levers to
release the RSP8 and reseat it in the backplane. (For a description and illustration of the ejector
levers, see the Inserting the RSP8 section on page 3.) Tighten both captive installation screws.
If the system power LED still fails to go on as expected, a power supply or input power failure could
be the problem. Before contacting a service representative, refer to the Cisco 7500 Series
Installation and Configuration Guide for power subsystem troubleshooting procedures.
If the system power LED goes on, the power source is good, and the power supply is functional.
When the system power LED indicates normal operation, proceed to the next step.
Step 2
Listen for the system blower and observe the fan OK LED. You should hear the system blower start
operating immediately after you turn on the system power. If you determine that the power supply is
functioning normally and that an internal fan (or the system blower) is faulty, contact a service
representative. If the blower or a power supply fan does not function properly at initial startup, you
cannot make any installation adjustments.
Step 3
When you have verified that the power supply is functioning properly, observe the LEDs on the RSP8.
The CPU halt LED on the RSP8 should always remain off. If it goes on during the startup sequence, the
system has encountered a processor hardware error.
Use the show version command to check the current configuration register settings.
If the CPU halt LED goes on during a second startup attempt, suspect a processor hardware error
and contact a service representative.
Step 4
During the boot process, the LEDs on most of the interfaces light in irregular sequence; this does not
indicate either correct system startup or failure.
Step 5
When the system boot is complete, the RSP8 begins to initialize the interface processors. During this
initialization, the LEDs on each interface processor behave differently (most flash on and off). The
enabled LED on each interface processor goes on when initialization has been completed.
If the enabled LEDs on the interface processors go on, the system has booted successfully and is
now functional.
If the RSP8 LEDs previously indicated a successful system boot, but none of the enabled LEDs on
the interface processors go on, suspect that one of the interface processors has shifted out of its
backplane connector and halted the system. Use the ejector levers to release the interface processor
and reseat it in the backplane. (For an illustration of the ejector levers, see Figure 1.) Tighten both
captive installation screws.
If the enabled LED on a single interface processor remains off, suspect that the interface processor
has shifted out of its slot. Use the ejector levers to release the interface processor and reseat it in the
backplane. (For an illustration of the ejector levers, see Figure 1.) Tighten both captive installation
screws. After the system reinitializes the interfaces, the enabled LED on the interface processor
should go on.
If an enabled LED still fails to go on after you perform these steps, suspect that the specific interface
processor has failed.
22-11
Chapter 22
Step 6
When the system boot is complete and all interface processors have been initialized, the active RSP8s
console screen displays a script and a system banner similar to the following:
SLOT 6 RSP8 is system master (SLOT 2 for a Cisco 7507)
SLOT 7 RSP8 is system slave (SLOT 3 for a Cisco 7507, if installed)
ROM: System Bootstrap, Version 12.0(9)S [biff 2], RELEASE SOFTWARE (fc1)
ROM: GS Bootstrap Software (RSP-BOOT-M), Version 10.3(7), RELEASE SOFTWARE
Warning: monitor nvram area is corrupt... using default values
If all the previous conditions are met and this banner is displayed, the system startup was successful
and your installation is complete.
If an error message is displayed on the terminal, refer to the appropriate software publication for
error message definitions.
If the console screen is blank, check the terminal to ensure that it is turned on and that the console
cable is correctly connected between the terminal and the console port on the RSP8.
Check the terminal settings to ensure that the terminal is set for 9600 baud, 8 data bits, no parity,
and 2 stop bits.
If the terminal is set correctly and still fails to operate, suspect that the terminal is faulty. Connect a
different terminal and restart the system.
If the system still fails to start up or operate properly, or if you isolate the cause of the problem to a failed
component, contact a service representative for further assistance.
This completes the procedure for verifying system startup.
Troubleshooting a Failed RSP8

When a new active RSP8 takes over ownership of the router, it automatically reboots the failed RSP8 as
the standby RSP. You can access the state of the failed RSP8 in the form of a stack trace from the active
console using the show stacks command.
You can also manually reload a failed or inactive standby RSP8 from the active console. To do so, enter
the following command task from global configuration mode:
Router(config)# slave reload
Displaying Information about the Active and the Standby RSP8s

You can also display information about the active and the standby RSP8s. To do so, perform any of the
following tasks from EXEC mode:
22-12
Chapter 22

Table 1
Displaying Information on the Active and Standby RSP8s
Task
Command
Display the environment variable settings and

show boot var
configuration register settings for the active and the
standby RSP8 cards.
Show a list of Flash devices currently supported on show flash all
the router.
Display the software version running on the active
and the standby RSP8 cards.
show version
Display the stack trace and version information of

the active and the standby RSP8 cards.
show stacks 1
1. This command is documented in the System Management Commands chapter of the

Configuration Fundamentals Command Reference publication.

To replace a failed RSP8 in a reduncant (RPR+ configuration, first verify the active RSP card by using
the show version command. You will see output similar to the following:
125440K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
>>Slave in slot 7 is running Cisco Internetwork Operating System Software
SOFTWARE (fc1)
You can replace only an RSP card that runs in secondary (slave mode).
Removing the RSP8

When you remove or install the RSP8, be sure to use the ejector levers, which help to ensure that the
RSP8 is fully inserted in the backplane or fully dislodged from it. An RSP8 that is only partially
connected to the backplane can halt the system unless a second RSP8 is installed.
Figure 1 shows a detail of the ejector lever mechanism that is appropriate for the router. When you
simultaneously push the ejector levers inward (toward the carrier handle), the levers push the RSP8 into
the slot and ensure that the board connectors are fully seated in the backplane. Follow these steps to
remove the RSP8:
Step 1
Attach an antistatic strap to yourself and then connect the equipment end of the strap to a captive
installation screw on an installed interface processor, or to any unfinished chassis surface.
Step 2
If you are replacing the RSP8, disconnect any devices that are attached to the console or auxiliary ports.
If you are removing the RSP8 for maintenance and will reinstall the same one, you can leave the
devices attached provided that doing so will not strain the cables.
Step 3
Use a screwdriver to loosen the two captive installation screws. (See Figure 1.)
22-13
Chapter 22
Step 4
Place your thumbs on the ends of each of the ejectors and simultaneously pull them both outward, away
from the carrier handle (in the opposite direction from that shown in c of Figure 1) to release the carrier
from the slot and to dislodge the RSP8 from the backplane.
Step 5
Grasp the handle of the RSP8 with one hand and pull the RSP8 straight out of the slot, keeping your
other hand under the carrier to guide it. (See Figure 2.) Keep the carrier parallel to the backplane. Avoid
touching the board or any connector pins.
Figure 7
Ejector Levers and Captive Installation Screw

Processor module
slot
Processor
module
carrier guide
Captive
installation
screw
c
H1482a
Stop
immediately
on contact
Step 6
Place the removed RSP8 on an antistatic mat or foam. If you plan to return the RSP8 to the factory,
immediately place it in an antistatic bag to prevent ESD damage.
Step 7
Attach the equipment end of the ESD-preventive strap to the RSP8 before performing any maintenance
on the RSP8 that might create an ESD hazard.
22-14
Chapter 22

Inserting the RSP8

Note
Before re-inserting a new RSP8, remove any pcmcia flash card form the failed RSP and insert them
into the new RSP card.
The RSP8 is keyed for installation only in an RSP slot. By default, the system active is the RSP that
occupies the first RSP slot in the router: slot 2 in the Cisco 7507 and Cisco 7507-MX, and slot 6 in the
Cisco 7513 and Cisco 7513-MX. Follow these steps to install an RSP8:
Step 1
Grasp the RSP8 handle with one hand and place your other hand under the carrier to support and guide
it into the slot. (See Figure 2.) Avoid touching the board or any connectors.
Step 2
Place the back of the RSP8 in the appropriate RSP slot and align the notches along the edge of the
carrier with the grooves in the slot. (See a in Figure 1.)
Handling the RSP8 During Removal and Installation
H1355a
Figure 8
Caution
To prevent damage to the backplane, you must install the RSP8 in one of the two RSP slots
on the router. The slots are keyed for correct installation. Forcing the RSP8 into a different
slot can damage the backplane and the RSP8.
Step 3
While keeping the RSP8 parallel to the backplane, carefully slide the carrier into the slot until the RSP8
faceplate makes contact with the ejector levers, and then stop. (See b in Figure 1.)
Step 4
Using the thumb and forefinger of each hand to pinch each ejector lever, simultaneously push both
ejector levers inward (toward the handle) until they are parallel to the faceplate. (See c in Figure 1.)
Step 5
Use a screwdriver to tighten the captive installation screws on the ends of the RSP8. (See a in Figure 1.)
22-15
Chapter 22
Step 6
Use a screwdriver to tighten the two captive installation screws on the RSP8 faceplate to prevent the
RSP8 from becoming partially dislodged from the backplane and to ensure proper EMI shielding.
(These screws must be tightened to meet EMI specifications.)
Step 7
If you disconnected the console terminal to remove the RSP8, or if you are installing a new RSP8,
connect the console terminal to the console port. (See the Connecting a Console Terminal section on
page 5.)
Step 8
Ensure that a console terminal is connected (see the Connecting a Console Terminal section on
page 5) and that it is turned on.
Once inserted, the new RSP will boot up in secondary mode. To populate the startup configuration to the
new card issue the command copy running-config startup-config.
22-16
C H A P T E R
23

Adding new port adapters, whether inserted in an existing VIP or inserted in a new VIP, is disruptive to
normal ITP operation and requires therefore a maintenance window.
Any new hardware in the ITP requires Cisco ITP IOS to recalculate available memory buffers and
eventually reassign those resources to all (including the new) interfaces and ports.
A new VIP card can be inserted while the ITP is operational and powered on. However, once it is
inserted, IOS will cease normal operation until the new hardware is analyzed and an optimal buffer
assignment has been calculated. This process can take up to 60 seconds.
To insert a new VIP, perform the steps as described in the chapter Replacing a Failed VIP, in the
Reinstalling the VIP4 and Connecting the Port Adapter Cables section on page 10.
Once inserted, wait for all configured links and linkset to become available. This is the indication that
the ITP resumed normal operation.
To put the new port adapter into service, follow the steps as described in Chapter 9, Putting a Low Speed
Link (LSL) in Serviceand Chapter 10, Putting a High Speed Link (HSL) in Service.
23-1
Chapter 23
23-2
C H A P T E R
24
Software Upgrade
Note
Upgrading Cisco ITP IOS 12.2(4)MB4 to a later version is disruptive and requires a scheduled
maintenance downtime of about 90 seconds. Later IOS versions will be upgradable without
downtime unless stated otherwise in software relase notes.
Perform following steps for this procedure:
Step 1
Copy the new image onto the RSP(s)
Step 2
Define which software should run on the RSP(s)
Step 3
Reset the standby RSP to load the new IOS image
Step 4
Force a switchover to activate the new IOS version running on the standby RSP.
Step 1: copy tftp slot0:
Step 1
Command
Purpose
Router# copy tftp slotslot-number:

image onto the Flash memory card of the active
RSP.1
slotslot-numberSpecifies the Flash memory

card of the active RSP.

TFTP server.
writing
filename!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Loading imagename from ip-address (via
Ethernet1/0/0): !



24-1
Chapter 24
Step 2
Router# copy tftp slaveslotslot-number:

image onto the Flash memory card of the standby
RSP.

writing
filename!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Software Upgrade
slaveslotslot-numberSpecifies the Flash

memory card of the standby RSP.

TFTP server.



Loading imagename from ip-address (via Ethernet1/0):
!



Step 3
Step 4

file-spec



Note
24-2

attribute must be available on the local Flash
device. Remote protocols such a Trivial File
Transfer Protocol (TFTP) and remote copy
protocol (RCP) are not available.
Chapter 24
Step 5
Software Upgrade

file-spec



Note

attribute must be available on the local Flash
device. Remote protocols such a Trivial File
Transfer Protocol (TFTP) and remote copy
protocol (RCP) are not available.
Step 6
Step 7
1. Before you copy a file to Flash memory, be sure there is ample space available in Flash memory. Compare the size of the file you are copying to the
amount of available Flash memory shown. If the space available is less than the space required by the file you will copy, the copy process will not
continue and an error message similar to the following will be displayed;
%Error copying tftp://image@server/tftpboot/filelocation/imagename (Not enough space on device).
Command
Purpose
Step 1
Step 2

file-spec



Note

available.
24-3
Chapter 24
Step 3
Command
Purpose

file-spec



Note
Step 4
Software Upgrade

available.
Step 7: hw-module sec-cpu reset (** copy from page 5-6, step 7)
Step 5
Command
Purpose
Resets and reloads the standby RSP with the

specified Cisco IOS image and executes the image.
Note
If you do not specify a Cisco IOS image in

Step 2, this command loads and executes
the bundled default IOS standby image.
The system then operates in HSA mode.
Step 8: verify the standby RSP is booted by typing 'show redundancy':

Operating mode is rpr
redundancy mode is rpr-plus
hw-module slot 6 image disk0:rsp-itpv-mz.122-4.MB5
hw-module slot 7 image disk0:rsp-itpv-mz.122-4.MB5
The ITP operates in rpr (not rpr-plus) mode due to the different
24-4
Chapter 24
Software Upgrade
IOS image.
Step 8: force a switchover to activate the new IOS image:
Router# redundancy force-switchover
The standby RSP will became active, reload all VIP cards with new software and restart the de-activated
active RSP in five minutes. After a sucessfull switchover the standby RSP will be the active one and the
former active RSP will become standby RSP. Once the (new) standby RSP is booted after five minutes
the ITP operates again in RPR+ redundancy mode.
24-5
Chapter 24
24-6
Software Upgrade
C H A P T E R
25
Ongoing Monitoring
Monitoring the Cisco ITP
This section includes information about the following tasks:
Monitoring CPU/Memory, page 1
Monitoring Linksets and Links, page 2
Monitoring MTP2 Links/Interfaces, page 4
Monitoring M2PA Links/Interfaces, page 9
Monitoring Routes, page 12
Monitoring Gateway Screening Violations, page 13
Monitoring System Messages, page 13
Monitoring Accounting, page 14
Monitoring CPU/Memory
Why is this task important?
A healthy SS7oIP router needs to be running at less than 50% CPU during non fail-over conditions and
must have 50% available memory to handle route table changes due to network conditions. If an SS7oIP
router has a CPU and/or memory shortage, network availability is at risk. CPU and memory should be
monitored via system error messages or SNMP traps alerts
Under what circumstances should this task be performed?
System health monitoring is an ongoing process and should be automated. CiscoWorks network
management application can be used to automate this task.
What incidents or system messages should prompt the user to monitor the CPU/memory?
When Cisco ITP attempts to allocate memory for an event for which no memory is available, the
following IOS message is displayed:
25-1
Chapter 25
Ongoing Monitoring
%SYS-2-MALLOCFAIL:Memory allocation of [dec] bytes failed from [hex], pool

[chars], alignment [dec]
Explanation The requested memory allocation is not available from the specified memory pool. The
current system configuration, network environment, or possibly a software error might have
exhausted or fragmented the router memory.
Action Copy the error message exactly as it appears on the console or in the system log, call your
Cisco technical support representative, and provide the representative with the gathered information.
Should this task be part of a regular maintenance process that the user should do at regular intervals? If so, how
frequently?
Ongoing.
What commands does the user issue?
The show proc cpu command will display output such as the following:
CPU utilization for five seconds:0%/0%; one minute:0%; five
PID Runtime(ms) Invoked uSecs
5Sec
1Min
5Min TTY
27
0
1
0
0.00% 0.00% 0.00%
0
28
30238
70601
428
0.00% 0.01% 0.00%
0
53
56
353673
0
0.00% 0.00% 0.00%
0
minutes:0%
Process
MTP3 Input
MTP3 Mgmt
CS7 MTP2 timer
The show proc mem command will display output such as the following:
Total:26494208, Used:4829456, Free:21664752
PID TTY Allocated
Freed
Holding
27
0
192
0
13036
28
0
267888
276
274456
53
0
20948
340
27452
Getbufs
0
0
0
Retbufs
0
0
0
Process
MTP3 Input
MTP3 Mgmt
CS7 MTP2 timer
The show mem command will display output such as the following:
Processor
I/O
Head
80DBBB00
2700000
Total(b)
26494208
26214400
Used(b)
4829308
2227876
Free(b)
21664900
23986524
Lowest(b)
21615220
23979088
Largest(b)
21640172
23979036
Monitoring Linksets and Links

Links and linksets can change states from available to unavailable while the system is running. It is
important to monitor when a linkset has become unavailable since it can indicate total or partial loss of
a route to a destination node. When a link becomes unavailable, it can have a negative impact on the
throughput, since there will be fewer links to carry the traffic.
Link and linkset availability should be monitored at all times when there is traffic flowing over it.
What incidents or system messages should prompt the user to monitor Linksets and Links?
The user should monitor the links and linkset whenever a route or destination becomes unavailable.
25-2
Chapter 25
Ongoing Monitoring
frequently?
Whenever a link or linkset becomes unavailable, error messages are displayed on the console and an
SNMP trap is sent to the network management node.
To monitor all linksets, issue the show cs7 linkset brief command, which displays output such as the
following:
lsn=to_2651_1
lsn=to_helium
lsn=to_mgts_15
apc=0.3.3
apc=0.2.2
apc=1.1.1
state=UNAVAIL
state=avail
state=UNAVAIL
The following explanations are based on the preceding output of the show cs7 linkset brief command.
In the display above, the linkset to_helium is available and for traffic. A linkset is in available state when
it has at least one available link in it. The detailed display below indicates that the linkset has several
links that are available.
Linkset to_2651_1 is unavailable because it does not have any available links. Link 0 has been shutdown
via configuration.
In linkset to_helium, link 5 has been locally inhibited and as such is unavailable to carry traffic.
Link 6 has been remotely inhibited and is also unavailable to carry traffic. (If a link has been locally
inhibited via the cs7 inhibit command, the Inhibit column will display loc to indicate that the link was
locally inhibited. If a link is inhibited from the adjacent node, the show output will display rem to
indicate that it was remotely inhibited.
Linkset to_mgts_15 is also not available to carry traffic because it does not have any available links.
Link 0 has failed.
The possible states of a linkset are:
UNAVAIL Indicates the linkset does not have any available links and cannot transport traffic.
shutdown
Indicates the linkset has been shutdown in the configuration.
avail
Indicates the linkset has at least one available link and can carry traffic.
The possible states of a link are:
UNAVAIL
Indicates the link is not available to carry traffic. This can occur if the link is
remotely or locally inhibited by a user. It can also be unavailable if MTP2/M2PA has not been able
to successfully activate the link connection or the link test messages sent by MTP3 are not being
acknowledged.
shutdown Indicates the link has been shutdown in the configuration. A link is shutdown when it
is shutdown at the MTP3 layer.
avail
FAILED
A link is FAILED when the link is not shutdown but is unavailable at layer2 for some
reason. It is FAILED when the link is unavailable because the link has been inhibited or it is
blocked.
Indicates the link is active and able to transport traffic.
25-3
Chapter 25
Ongoing Monitoring
To monitor all linksets and all links in the linksets, issue the show cs7 linkset command. Refer to the
Command Reference section of this document for descriptions of the show commands.
lsn=to_2651_1
apc=0.3.3
SLC Interface
*00
10.10.10.5 5000 5000
state=UNAVAIL
Service
PeerState
shutdown OutOfService
Inhib
-----
lsn=to_helium
apc=0.2.2
SLC Interface
00
Serial4/0/0
01
Serial4/0/1
02
Serial4/0/2
03
Serial4/0/3
04
Serial4/0/4
*05
Serial4/0/5
*06
Serial4/0/6
07
Serial4/0/7
08
Serial4/1/0:0
09
Serial4/1/1:0
10
Serial4/1/2:0
11
Serial4/1/3:0
12
Serial4/1/4:0
13
Serial4/1/5:0
14
Serial4/1/6:0
15
Serial4/1/7:0
state=avail
Service
PeerState
avail
--------avail
--------avail
--------avail
--------avail
--------UNAVAIL
--------UNAVAIL
--------avail
--------avail
--------avail
--------avail
--------avail
--------avail
--------avail
--------avail
--------avail
---------
Inhib
--------------------loc
rem
-------------------------------------
lsn=to_mgts_15
apc=1.1.1
SLC Interface
*00
Serial1/1/0
state=UNAVAIL
Service
PeerState
FAILED
---------
Inhib
-----.
Monitoring MTP2 Links/Interfaces

Monitoring interfaces is useful for determining the status of MTP2/SCTP links, for providing statistical
information about the performance of the interface.
If an MTP2 link goes down.

If performance on an MTP2 link is degraded.
What incidents or system messages should prompt the user to monitor interfaces?
frequently?
Regular monitoring is not necessary for link failure problems because system messages will indicate link
failure conditions. Regular monitoring to find performance problems may be necessary.
show
show
show
show
interface serial
cs7 mtp2 state serial
cs7 mtp2 congestion serial
cs7 mtp2 statistics serial
25-4
Chapter 25
Ongoing Monitoring
The output of the show interface serial command can reveal possible Link Down problems. The fields
to examine are indicated with arrows in the sample output below:
Router# show int ser 5/0/0:0
Hardware is Multichannel T1
Encapsulation SS7 MTP2, crc 16, CRC 16, Data non-inverted
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
Timeslot(s) Used:1, subrate:64Kb/s, transmit delay is 0 flags
The field line protocol should display line protocol is up rather than down.
The field Encapsulation should display SS7 MTP2 rather than (for example) HDLC.
The output of the show cs7 mtp2 state serial command indicates the status of the MTP2 state machine.
The fields to examine are indicated with arrows in the sample output below:
Router# show cs7 mtp2 state ser 5/0/0:0
CS7 MTP2 states for interface Serial5/0/0:0
Protocol version for interface Serial5/0/0:0 is ITU-T Q.703 (1996) (White Book)
Link State Control (LSC)
Initial Alignment Control (IAC)
Transmission Control (TXC)
Reception Control (RC)
Signal Unit Error Rate Monitor (SUERM)
Alignment Unit Error Rate Monitor (AERM)
Congestion (CONG)
=
=
=
=
=
=
=
In Service
Idle
In Service
In Service
Monitoring
Idle
Idle
Layer3 link status

Layer3 congestion status
= Started
= Abate
The field Link State Control (LSC) should display In Service.

The field Transmission Control (TXC) should display In Service.
The field Reception Control (RC) should display In Service.
The field Layer3 link status should display Started.
25-5
Chapter 25
Ongoing Monitoring
The output of the show interface serial command can reveal possible performance problems. The fields
to examine are indicated with arrows in the sample output below:
Router# show int ser 5/0/0:0
Hardware is Multichannel T1
Encapsulation SS7 MTP2, crc 16, CRC 16, Data non-inverted
Timeslot(s) Used:1, subrate:64Kb/s, transmit delay is 0 flags
The field line protocol should display line protocol is up.

The field reliability displays a fraction in the range 255/255 to x/255 which indicates the percentage
of reliability. The fraction should represent 100%.
The field txload displays a fraction in the range 1/255 to x/255 which indicates the percentage of
transmit load on the link.
Under 40% txload is optimal.
40%-80% txload indicates a heavily loaded link.
Over 80%txload indicates a heavily congested link.
The field rxload displays a fraction in the range 1/255 to x/255 which indicates the percentage of
receive load on the link.
Under 40% rxload is optimal.
40%-80% rxload indicates a heavily loaded link.
Over 80% rxload indicates a heavily congested link.
In the field Output queue 0/40, 0 drops; input queue 0/75, 0 drops:
Output drops indicate local txCongestion or rxCongestion at remote.
Input drops indicate local rxCongestion or txCongestion at remote.
The field <number> no buffer indicates packet drops because of buffer shortage. The number should
be 0.
The field <number> input errors, <number> CRC, <number> frame, <number> overrun, <number>
ignored, <number> abort indicates problems with interface receive. The numbers should be 0.
In the field <number> output errors, <number> collisions, <number> interface resets all numbers
should be 0.
The field number output buffer failures, number output buffers swapped out indicates problems with
interface transmit.
25-6
Chapter 25
Ongoing Monitoring
The output of the show cs7 mtp2 congestion serial command indicates congestion levels. The fields to
examine are indicated with arrows in the sample output below:
Router# show cs7 mtp2 congestion ser 5/0/0:0
CS7 MTP2 congestion status for interface Serial5/0/0:0
Layer3 congestion status
= Abate
CongestionRxInd
CongestionTxInd
= Abate
= Abate (Level0)
CongestionTxOnset
CongestionTxOnset
CongestionTxOnset
CongestionTxOnset
Level1
Level2
Level3
Level4
=
=
=
=
XmitQ depth (max-used)

XmitQ depth (max-allowed)
250
350
450
500
( 50%
( 70%
( 90%
(100%
of
of
of
of
xmitQ
xmitQ
xmitQ
xmitQ
maxDepth)
maxDepth)
maxDepth)
maxDepth)
= 15
= 500
The field Layer3 congestion status should display Abate (MTP3 not congested) rather than Onset
(MTP3 congested).
The fields CongestionRxInd and CongestionTxInd indicate current congestion levels.
The field XmitQ depth (max-used) indicates the maximum number of packets ever waiting on the
queue and indicate how congested router might have been.
The output of the show cs7 mtp2 statistics serial command indicate congestion levels. The fields to
examine are indicated with arrows in the sample output below:
Router# show cs7 mtp2 statistics ser 5/0/0:0
CS7 MTP2 Statistics for interface Serial5/0/0:0
OMtimeINSV (secs)
OMtimeNotINSV (secs)
= 756
= 49
OMIACAlignAttemptCount = 10
OMIACAlignFailCount
= 4
OMIACAlignCompleteCount = 2
OMMSU_L3_XMIT_Count
OMMSU_XMIT_Count
OMMSUBytesTransmitted
OMMSU_RE_XMIT_Count
OMMSUBytesRetransmitted
=
=
=
=
=
137
137
1429
0
0
OMMSU_RCV_Count
OMMSUBytesReceived
= 157
= 1625
OMFISU_XMIT_Count
OMFISU_RCV_Count
= 159
= 307
OMLSSU_XMIT_Count
OMLSSU_XMIT_SINCount
OMLSSU_XMIT_SIECount
OMLSSU_XMIT_SIOCount
OMLSSU_XMIT_SIOSCount
OMLSSU_XMIT_SIPOCount
OMLSSU_XMIT_SIBCount
=
=
=
=
=
=
=
OMLSSU_RCV_Count
= 8
24
0
2
10
12
0
0
25-7
Chapter 25
OMLSSU_RCV_SINCount
OMLSSU_RCV_SIECount
OMLSSU_RCV_SIOCount
OMLSSU_RCV_SIOSCount
OMLSSU_RCV_SIPOCount
OMLSSU_RCV_SIBCount
=
=
=
=
=
=
0
4
4
0
0
0
OMT1_TMO_Count
OMT2_TMO_Count
OMT3_TMO_Count
OMT4_TMO_Count
OMT5_TMO_Count
OMT6_TMO_Count
OMT7_TMO_Count
OMAERMCount
OMAERMFailCount
OMSUERMCount
OMSUERMFailCount
=
=
=
=
=
=
=
=
=
=
=
0
4
0
2
0
0
0
2
0
2
0
Ongoing Monitoring
OMCongestionRxCount
= 0
OMCongestionTxCount
= 0
OMRemote_Congestion_Cnt = 0
OMxmitQ_maxcount
= 15
OMNACK_XMIT_Count
OMNACK_RCV _Count
= 0
= 0
OMunreasonableFSN_rcvd
OMunreasonableBSN_rcvd
OMabnormalBSN_rcvd
OMabnormalFIB_rcvd
=
=
=
=
0
0
0
0
(error)
(error)
(error)
(error)
OMFISU_notAccepted
OMMSU_notAccepted
OMFISU_congestionDrops
OMMSU_congestionDrops
OMMSU_too_long
OMMSU_unexpectedFSN
OMMSU_discarded
=
=
=
=
=
=
=
4
0
0
0
0
0
0
(packets
(packets
(packets
(packets
(packets
(packets
(packets
dropped)
dropped)
dropped)
dropped)
dropped)
dropped)
dropped)
The fields OMMSU_RE_XMIT_Count and OMMSUBytesRetransmitted indicate retransmission

on the link. Retransmission is an indication of probable congestion.
The fields OMCongestionRxCount, OMCongestionTxCount, OMRemote_Congestion_C indicate
congestion counts on the local or remote device.
The fields OMunreasonableFSN_rcvd, OMunreasonableBSN_rcvd, OMabnormalBSN_rcvd and
OMabnormalFIB_rcvd indicate protocol errors.
The field OMMSU_congestionDrops indicates the number of MSU packets dropped due to
rxCongestion.
The field OMMSU_unexpectedFSN indicates packets dropped due to unexpected FSN received.
The field OMMSU_discarded indicates total MSU packets dropped, probably due to congestion.
25-8
Chapter 25
Ongoing Monitoring
Monitoring M2PA Links/Interfaces

Note
M2PA/SCTP links run over any interface that supports IP (serial, ethernet, fast ethernet,
token ring, etc. The example used in this section is for fast ethernet.
Monitoring interfaces is useful for determining the status of M2PA/SCTP links and for providing
statistical information about the performance of the interface.
If the M2PA/SCTP links fail or if the M2PA/SCTP link performance is degraded.

What incidents or system messages should prompt the user to issue the monitor M2PA Links/Interfaces?
Should this task be part of a regular monitoring process that the user should do at regular intervals? If so, how
frequently?
Regular monitoring is not necessary for link failure problems because system messages will indicate link
failure conditions. Regular monitoring to identify performance problems may be necessary.
show interface interface-type
show cs7 m2pa state
The following output of the show interface ethernet command reveals possible link down problems:
Router# show int faste0/1
FastEthernet0/1 is up, line protocol is up
Hardware is AmdFE, address is 0003.e348.5f41 (bia 0003.e348.5f41)
Full-duplex, 100Mb/s, 100BaseTX/FX
75799 packets input, 11049547 bytes
0 watchdog
155409 packets output, 15498764 bytes, 0 underruns(0/0/0)
25-9
Chapter 25
Ongoing Monitoring
The field Internet address should display a valid IP address.

CS7 M2PA states for Peer (50.50.50.2 :9000)
M2PA Peer State
= InService
SCTP Peer State
=SCTP_ESTABLISHED
T1 aligned/ready
T6 remote cong
= 5000 ms
= 3000 ms
Local Processor Outage

Remote Processor Outage
InService LSSU Recv'd
Transport Handle
=
=
=
=
FALSE
FALSE
TRUE
0
The field M2PA Peer State should display InService.

The field SCTP Peer State should display SCTP_ESTABLISHED.
The following output of the show interface ethernet command reveals possible performance problems:
Router# show int faste0/1
FastEthernet0/1 is up, line protocol is up
Hardware is AmdFE, address is 0003.e348.5f41 (bia 0003.e348.5f41)
Full-duplex, 100Mb/s, 100BaseTX/FX
75895 packets input, 11064304 bytes
0 watchdog
155709 packets output, 15529225 bytes, 0 underruns(0/0/0)

The field Internet address should display a valid IP address.
The field reliability displays a fraction in the range 255/255 to x/255 which indicates the percentage
of reliability. The fraction should represent 100%.
The field txload displays a fraction in the range 1/255 to x/255 which indicates the percentage of
transmit load on the link.
Under 40% txload is optimal.
40%-80% txload indicates a heavily loaded link.
Over 80%txload indicates a heavily congested link.
The field rxload displays a fraction in the range 1/255 to x/255 which indicates the percentage of
receive load on the link.
25-10
Chapter 25
Ongoing Monitoring
Under 40% rxload is optimal.
40%-80% rxload indicates a heavily loaded link.
Over 80% rxload indicates a heavily congested link.
In the field Output queue 0/40, 0 drops; input queue 0/75, 0 drops:
Output drops indicate local txCongestion or rxCongestion at remote.
Input drops indicate local rxCongestion or txCongestion at remote.
The field <number> no buffer indicates packet drops because of buffer shortage. The number should
be 0.
The field <number> input errors, <number> CRC, <number> frame, <number> overrun, <number>
ignored, <number> abort indicates problems with interface receive. The numbers should be 0.
In the field <number> output errors, <number> collisions, <number> interface resets all numbers
should be 0.
The field number output buffer failures, number output buffers swapped out indicates problems with
interface transmit.
Router# show cs7 m2pa stats to_duck
CS7 M2PA Peer Statistics for (50.50.50.2 :9000)
M2PA Peer State
= InService
SCTP Peer State
= SCTP_ESTABLISHED
MSU_XMIT_Count
= 98658
MSU_RCV_Count
= 98913
MSU_XMIT_Fail_Count
= 0
MSU_XMIT_Drop_Count
= 0
LSSU_XMIT_Count
= 2
LSSU_XMIT_Fail_Count
= 0
LSSU_XMIT_SIISCount
= 2
LSSU_XMIT_SIPOCount
= 0
LSSU_XMIT_SIPOECount
= 0
LSSU_XMIT_SIBCount
= 0
LSSU_XMIT_SIBECount
= 0
LSSU_RCV_Count
= 2
LSSU_RCV_SIISCount
= 2
LSSU_RCV_SIPOCount
= 0
LSSU_RCV_SIPOECount
= 0
LSSU_RCV_SIBCount
= 0
LSSU_RCV_SIBECount
= 0
LSSU_RCV_InvalidCount
= 0
BytesTransmitted
= 3337163
BytesReceived
= 3340840
Remote_PO_Count
= 0
Remote_Congestion_Count
= 0
CongestionCount
= 0
Level 1 CongestionCount
= 1
= 0
= 0
= 0
T1_TMO_Count
= 0
T6_TMO_Count
= 0
The field Level x CongestionCount displays the number of times congestion level x has occurred.
Router# show ip sctp stat
** SCTP Overall Statistics **
Total Chunks Sent:
Total Chunks Rcvd:
Received Ordered Data Chunks:
50141
47738
10877
25-11
Chapter 25
Ongoing Monitoring
Received UnOrdered Data Chunks:0

Total Data Chunks Sent:
10877
Total Data Chunks Rcvd:
10877
Total Data Bytes Sent:
184924
Total Data Bytes Rcvd:
184924
Total Data Chunks Discarded:
0
Total Data Chunks Retrans:
0
Total
Total
Total
Total
Total
SCTP Datagrams Sent:

SCTP Datagrams Rcvd:
ULP Datagrams Sent:
ULP Datagrams Ready:
ULP Datagrams Rcvd:
41099
41099
10877
10877
10877
The field Total Data Chunks Retrans displays the number of retransmissions that have occurred.
The field Total Chunks Discarded displays the number of packets that have been discarded due to
duplicates.
Monitoring Routes
Monitoring routes is important because it reveals the status of all the routes in the network, and thus the
ability of the network to transport messages efficiently.
Under what circumstances should routes be monitored?
The status of routes should be monitored whenever the performance of the network is noticeably
degraded. This may reveal congestion on specific routes, for example, which may indicate a need to
deploy more links. In conjunction with other system messages it may reveal failures in various network
components.
What incidents or system messages should prompt the user to issue the show cs7 route command?
Whenever a destination accessibility status change message such as the following appears on the
console:
00:05:51:%CS7MTP3-5-DESTSTATUS:Destination 10.5.1 is inaccessible
Whenever a destination is reported to be inaccessible or restricted, the show cs7 route detailed
command will reveal what caused the destination to enter that state.
frequently?
Normally this should be performed to verify the configuration of new routes or deletion/modification of
existing routes. A regular monitoring is not needed because system generated messages (such as in the
example shown above) will inform the user of any abnormal operating conditions.
25-12
Chapter 25
Ongoing Monitoring
The show cs7 route command displays information such as the following:
router# show cs7 route
Routing table = system
Destination
Prio
-------------------- ---1.5.1/14
acces
5
5
7
1.5.3/14
acces
5
1.5.5/14
acces
5
1.5.6/14
acces
3
5
7
Linkset Name
------------------pollux
polaris
sirius
pollux
sirius
pollux
polaris
sirius
Route Status
-----------avail
avail
avail
avail
avail
avail
avail
avail
Refer to the Command Reference section of this document for detailed descriptions of the show
commands.
Monitoring Gateway Screening Violations

When screening is configured you can view screening activity.

When screening is configured.

What incidents or system messages should prompt the user to monitor gateway screening violations?
None. Violations do not appear as system messages because of the volume of messages this might
generate.
frequently?
At users discretion.
show cs7 access-lists
show cs7 accounting access-violations
[checkpoint]
commands.
Monitoring System Messages

System messages are part of the ITP alert infrastructure.

Monitoring should be automated via an external syslog server.
25-13
Chapter 25
Ongoing Monitoring
What incidents or system messages should prompt the user to monitor system messages?
Refer to the Cisco IOS Software System Error Messages documentation at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121sup/index.htm
frequently?
Yes, this process should be ongoing and automated.

show log
Monitoring Accounting
Monitoring accounting provides information about user-specific usage.

At users discretion.
What incidents or system messages should prompt the user to monitor system messages?
Traffic degradation, debugging of problems.

frequently?
At users discretion. This task can be part of ongoing statistics collection to be used for network capacity
planning or traffic profiling.
accounting
show cs7 accounting [checkpoint]
show cs7 linkset statistics
commands.
Summary of Commands used to Monitor Cisco ITP

Use the following commands in EXEC mode, to monitor various functions of Cisco ITP:
Command
Purpose
Router# show cs7 access-lists
Displays Cisco ITP access lists.
Router# show cs7 accounting [access-violations] [checkpoint]
Displays accounting details.
Router# show cs7 linkset [brief | detailed | ls-name | routes

| statistics]
Displays Cisco ITP linkset information.
Router# show cs7 m2pa {[local-peer port-num] | [peer ls-name

[slc]] | [state ls-name [slc]] |[stats ls-name [slc]]}
Displays Cisco ITP M2PA statistics.
25-14
Chapter 25
Ongoing Monitoring
Command
Purpose
Router# show cs7 mtp2 [congestion | state | statistics |

timers | variant] interface
Displays Cisco ITP MTP2 statistics.
Router# show cs7 mtp3 timers
Displays output from MTP3 timers.
Router# show cs7 ping point-code
Displays output from a Cisco ITP ping test.
25-15
Chapter 25
25-16
Ongoing Monitoring

ITP Operations Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ITP Operations Guide

Caricato da

Copyright:

Formati disponibili

ITP Operations Manual

Customer Order Number:

ITP Operations Manual

Cisco 7513 Overview 1-1

Physical Hardware Installation & Cabling

Slot Locations on the Cisco 7507 and Cisco 7513

PA-A3-8E1IMA and PA-A3-8T1IMA Port Adapter Overview

Safety Guidelines 2-11

Required Tools and Equipment

Software and Hardware Requirements 2-15

Ensuring Network Operation During Removal of VIP and Port Adapters

Removing and Installing Port Adapters from the VIP4 2-18

Connecting the Port Adapter Cables 2-24

ITP Operations Manual

Connecting the 75120-Ohm Adapter Cable

Verifying the VIP4 and Port Adapter Installation

FEIP2-DSW Installation 2-32

Install the Hardware 3-3

ITP Operations Manual

Copy Files to Flash Memory 3-29

Installing or Replacing the Power Supply 4-1

Verify That the System Has Detected the HSL Hardware

Additional Commands to Obtain Details about the Hardware

Examine All SS7 Port Adapters Installed in Each Slot

Configuration Tasks 6-2

ITP Operations Manual

Configuration Examples 6-7

Identifying Interface Numbers and Addresses

Checking the Configuration 7-4

Specifying the SS7 Variant

Specifying National Options and Network Indicator

Specifying the Point Code 8-2

Creating a Basic Controller Configuration for the SS7 Port Adapter

Assigning Links to Linksets 9-6

Configuring a Permanent Virtual Circuit (PVC)

Checking the Configuration 10-5

ITP Operations Manual

Assigning Links to Linksets

Taking an SS7 PA Out of Service

Identifying Links Associated with an SS7 PA

Disabling Links Associated with an SS7 PA

Identifying Links Associated with an HSL PA

Disabling Links Associated with an HSL PA

Identifying Links Associated with an SS7 PA

Disabling a Link Associated with an SS7 PA

Taking an HSL Out of Service

Identifying Links Associated with an HSL PA

Disabling a Link Associated with an HSL PA

Taking a Linkset Out of Service

Identifying and Disabling Linksets

MTP3 Routes 16-1

Global Title Translation (GTT) 17-1

Saving and Loading a Route Table 18-1

ITP Operations Manual

Taking Port Adapters Out of Service 19-3

Replacing Port Adapters

Reactivating the Links Associated with the Port Adapter 19-17

Port Adapter Overview 20-1

Reinstalling the VIP4 and Connecting the Port Adapter Cables

Checking the Configuration 20-18

Replacing a Failed VIP

VIP4 Overview 21-1

Taking Port Adapters Out of Service 21-3

Replacing Port Adapters