Cisco AS5850 Universal Gateway Card Guide
Universal Port Cards

Table Of Contents

Universal Port Cards

324 Universal Port Card Overview

LED Indicators

Startup Sequence

SPE Firmware

Verifying and Troubleshooting the Installation

show spe command

Configuring the Ports

For More Information


Universal Port Cards


The Cisco AS5850 universal gateway is equipped with dedicated universal port (324 universal port) cards, dedicated trunk (24T1/E1) cards, and mixed-use trunk and port handling services (T3/216 universal port) cards. This chapter provides an overview of the 324 universal port card (UPC), which supports modem services, and includes steps for configuring your software and verifying and troubleshooting your UPC installation.

The universal port handling capabilities of the channelized T3 cards function identically to ports handled on the UPC, the only difference being the number of ports handled.

This chapter describes the functionality of the universal port card and includes steps for verifying and troubleshooting.

This chapter contains the following sections:

324 Universal Port Card Overview

Configuring the Ports

For More Information

324 Universal Port Card Overview

A universal port is a port that can carry the equivalent of one DS0 of network traffic. Network traffic can be a modem, voice, or fax connection. The core hardware components are service processing elements (SPEs), each of which support six universal ports. There are 54 SPEs per UPC, for a total of 324 ports per UPC. Each UPC also has a minimum of one 64-megabyte SDRAM card. Configuration, management, and troubleshooting of universal ports can be done at the UPC, SPE, and port level.

Currently the UPC supports data, voice, and fax traffic and is universal port capable, depending on the software and platform. Each UPC plugs directly into the server backplane and has no external connections. Each UPC has three LEDs that indicate card status.

Figure 5-1 shows the UPC components.

Figure 5-1 324 Universal Port Card Components

The UPC performs the following functions:

Converts pulse code modulation (PCM) bitstreams to digital packet data.

Forwards converted and packetized data to the server main processor, which examines the data and forwards it to the route switch controller. From the route switch controller, the data is routed to the external network.

Supports all modem standards (such as V.34 and V.42bis) and features, including dial-in and dial-out.

Supports online insertion and removal (OIR), a feature that allows you to remove and replace UPCs while the system is operating. UPCs can be removed without disrupting the operation of other cards and their associated calls. If a UPC is removed while the system is operating, connections or current calls on that card are dropped. Calls being handled by other cards, however, are not affected.

A UPC can be installed in slots numbered 0 through 5 or 8 through 13 on the server backplane.

LED Indicators

The UPC has three LEDs (see Figure 5-2) to indicate card status. The these LEDs can be green, yellow, or off.

Figure 5-2 324 Universal Port Card LEDs

During normal operation, all three LEDs light as described in Table 5-1.

Table 5-1 UPC LED Descriptions

LED
State
Description

CPU/POWER

Green

UPC passed diagnostics and the card CPU is operating properly.

Yellow

Goes on shortly after the card is powered on.1 Card CPU diagnostics start when the card starts receiving power, and the LED remains yellow while the diagnostics run.

OFF

UPC not receiving power, or portware failed to load. If the portware fails to load onto the card, the Cisco AS5850 attempts to reload the portware automatically. If a programmed number of attempts to reload the portware fails, the Cisco AS5850 powers off the UPC.

CALLS/MAINT

Green

The LED goes on when at least one active call is switched through the card.

Yellow

Indicates card OIR status. The LED is yellow when the card has been busied out and has no calls, and may be removed without interrupting service.

OFF

The CALLS/MAINT LED is not lit if there is no traffic on the card, and the card has not been busied out.

PORT STATUS

Green

Goes on when all SPE modules have passed diagnostics and are operating properly.

OFF

LED remains off until diagnostics are complete. If this LED stays off, one or more SPE modules are missing from the card or one or more SPEs failed diagnostics.

1 There is a slight delay from the time that power is applied to the card to the time that this LED goes on.


Startup Sequence

1. Power is applied to the UPC, either when the system starts or when the card is inserted into the backplane of a running server.

2. The CPU/POWER LED comes on yellow after a brief pause, indicating that CPU diagnostics are running.

3. The CPU/POWER LED comes on green if CPU passes diagnostics.

4. SPE diagnostics run. There is no LED indication that SPE diagnostics are currently running. If all SPEs pass, the PORT STATUS LED comes on. If one or more SPEs fail, the PORT STATUS LED remains off. Available SPEs still go into service.

5. The SPE firmware loads on available SPEs. There is no LED indication that SPE firmware is currently loading. If there are firmware load failures, a set number of repeat attempts are tried. If the repeat threshold is exceeded, the card is shut down.

6. If CPU diagnostics, SPE diagnostics, and SPE firmware loads are all successful, the card is ready to accept connections. CPU/POWER and PORT STATUS LEDs are green, and the CALLS/MAINT LED is off until a call comes through.

SPE Firmware

SPE firmware is automatically downloaded to a UPC from the server's Cisco IOS image when you boot the system for the first time or when you insert a UPC while the system is operating. When you insert a UPC while the system is operating, the Cisco IOS image recognizes the card and the server downloads the required portware to the cards.

The SPE firmware image (also known as portware) is bundled with the Cisco IOS UPC image. The SPE firmware image uses an auto-detect mechanism, which enables the UPC to service multiple call types. An SPE detects the call type and automatically configures itself for that operation. You can upgrade the firmware without upgrading Cisco IOS software, and different firmware versions can be configured to run on SPEs in the same UPC.

If a problem develops requiring a reload of SPE firmware to an SPE, busyout traffic on the SPE's active ports before reloading. Reloading firmware for an SPE affects all ports handled by the SPE, and any connections handled by a port on the SPE during a reload will be dropped.

The UPC supports the features listed in Table 5-2.

Table 5-2 UPC Supported Features 

Feature
Description

Carrier protocols

ITU V.23 at 75/1200 bps

Telcordia Technologies (formerly Bellcore) 103 at 300 bps

ITU V.21 at 300 bps

ITU V.22 at 1200 bps

Telcordia Technologies (formerly Bellcore) 212A at 1200 bps

ITU V.22bis at 2400 bps

ITU V.32 up to 9600 bps

ITU V.32bis up to 14,400 bps

V.32 turbo up to 19,200 bps

V.FC up to 28,800 bps

V.34 up to 28,800 bps

V.34+ up to 33.6 bps

TIA/ITU V.90

K56flex

Error-correcting link-access protocols

V.42 LAPM, MNP 2-4

Compression protocols

V.42bis (includes MNP 5)

Command interface

Superset of the AT command set

In-band signaling/tone generation and detection

Dual-tone Multi-frequency (DTMF) generation

DTMF detection

Multi-frequency (MF) generation

MF detection

Other

Point-to-point Protocol (PPP) and SLIP framing


Verifying and Troubleshooting the Installation

The UPC's LEDs do not function without the proper Cisco IOS image running on the server. If you need to upgrade your Cisco IOS image, refer to the Cisco AS5850 Operations, Administration, Maintenance, and Provisioning Guide, available online at: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/sw_conf/5850oamp/ index.htm

During normal operation, all three UPC LEDs come on when the UPC is powered on. When the UPC CPU software starts running, it shuts off all LEDs except the power LED. The LEDs then come on again as described in Table 5-1.

To complete the installation, verify that the UPC LEDs operate properly by observing the following LED states:

The CPU/POWER LED is on and is yellow or green.

If the CPU/POWER LED remains off, verify that the card is seated properly.


Note If the portware fails to load onto the SPEs, the Cisco AS5850 attempts to reload the portware automatically. If a programmed number of attempts to reload the portware fails, the Cisco AS5850 powers off the UPC.


If the CPU/POWER LED is yellow, diagnostics are still running on the UPC. If the CPU/POWER LED stays yellow, contact TAC. To contact the Cisco Technical Assistance Center (TAC) refer to the "Obtaining Documentation" section on page xvi.

If the power LED for other UPCs in the server comes on, try inserting the UPC in a different slot. If none of the power LEDs come on, check your server power connections, power entry modules, and AC-input power supplies (if present).

The CALLS/MAINT LED is on and is green or yellow.

If the CALLS/MAINT LED is off but the power LED is on, there is no traffic on the card.

Verify that the other cards in the server work properly. Verify that the card is seated properly. Try inserting the card in a different slot. Verify that you are using the correct portware by using the show spe version command.

The PORT STATUS LED is on and is green.

If the PORT STATUS LED is green, all SPEs present on the card passed diagnostics. You may also verify SPE operation by using the show spe command.

If the PORT STATUS LED is off, one or more SPEs present on the card failed diagnostics.

If troubleshooting reveals problems with the UPC, arrange to replace the UPC. To contact the Cisco Technical Assistance Center (TAC) refer to the "Obtaining Documentation" section on page xvi.

show spe command

To verify proper function of a UPC in a Cisco AS5850, you must use the show spe command and its variants described in the Cisco AS5850 Operations, Administration, Maintenance, and Provisioning Guide, available online at: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/sw_conf/5850oamp/ index.htm

For further installation troubleshooting information, refer to the Cisco AS5850 Universal Gateway Hardware Installation Guide.

Configuring the Ports

If you are replacing a server card with a new server card of the same type in the same slot, the system software recognizes the new server card interfaces and brings them up automatically. No additional configuration is needed.

You must insert the UPC in the desired slot as described in Chapter 1, "Replacing or Installing Server Cards."

Use the following commands to help you configure your UPC for basic dialup service.

 
Command
Description

Step 1 

Router> enable
Password: password
Router# 

Enter the enable command.

Enter your password.

You are in privileged EXEC mode when the prompt changes to Router#.

Step 2 

Router# configure terminal
Enter configuration commands, one per 
line. End with CNTL/Z.
Router(config)#

Enter global configuration mode by typing the configure command. The example uses the terminal configuration option.

You are in global configuration mode when the prompt changes to Router(config)#.

Step 3 

Router(config)# spe country 
country_name

Specify the country to set the universal port card parameters (including country code and encoding). The default is usa if the universal gateway is configured with T1 interfaces and e1-default if the universal gateway has E1 interfaces. Use the no form of this command to set the country code to the default of domestic.

All sessions on all modules in all slots must be IDLE for this command to run.

Step 4 

Router(config)# line slot/port 
slot/port

Configure lines slot/0 slot/xx as ports on the UPC. To identically configure all ports on a UPC in slot three, enter line 3/00 3/323. Ports are numbered starting with 0.

You are in line configuration mode when the prompt changes to Router(config-line)#.

Step 5 

Router(config-line)# modem inout

Enable incoming and outgoing calls.

Step 6 

Router(config-line)# transport 
preferred none

Set no preferred transport protocol for connecting to the Cisco AS5850 and using the Cisco IOS CLI.

Step 7 

Router(config-line)# transport input 
all

Allow all supported transport protocols to be used when connecting to the terminal server.

Step 8 

Router(config-line)# session-timeout 
minutes

Close connections when there is no input traffic for the specified number of minutes.

Step 9 

Router(config-line)# exec-timeout 
minutes seconds

Set the EXEC timeout for the specified number of minutes and seconds.

Step 10 

Router(config-line)# autoselect 
during-login

Configure ports to detect the connection protocol desired and start a session.

Step 11 

Router(config-line)# autoselect 
timeout seconds

Set wait timeout for initial autoselect byte (in seconds).

Step 12 

Router(config-line)# autoselect ppp

Set line to allow PPP autoselection. This allows remote IP users running a PPP application to dial in, bypass the exec facility, and automatically start PPP on the line.

Step 13 

Router(config-line)# absolute-timeout 
minutes

Set absolute timeout for line disconnection to minutes.

Step 14 

Router(config-line)# no modem status 
poll

Disable modem management status polling.

Step 15 

Router(config-line)# no modem log 
rs232

Disable EIA/TIA 232 event logging.

Step 16 

Router(config-line)# exit
Router(config)# 

[or]

Router(config-line)# Ctrl-Z 
Router#

Type the exit command to exit out of line configuration mode.

Press Return to verify your command registers, then press Ctrl-Z to return to privileged EXEC mode.

Step 17 

Router# copy running-config 
startup-config

Save your changes when ready.


Tip The cdp enable configuration command has changed. For the async and group async interfaces, the default is now disabled. Most other interfaces are enabled by default.


If you are installing a new UPC into the server, no additional configuration is needed. For additional system software configuration information, refer to the Cisco AS5850 Operations, Administration, Maintenance, and Provisioning Guide, available online at: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/sw_conf/5850oamp/ index.htm

For More Information

For further information useful in troubleshooting or managing the UPC, refer to the Cisco AS5850 Operations, Administration, Maintenance, and Provisioning Guide, available online at: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/sw_conf/5850oamp/ index.htm