|
|
This document describes Managing Port Services on the Cisco AS5400 Universal Access Server. It includes the overview, the maintenance and troubleshooting tasks, and the Cisco IOS software commands required for port service management.
This document includes the following sections:
The Managing Port Services on the Cisco AS5400 Universal Access Server feature implements the port service management for the Cisco AS5400 using the NextPort dial feature card (DFC). The NextPort DFC is a hardware card that processes digital service port technology for the Cisco AS5400. A port is defined as an endpoint on a DFC card through which multiservice tones and data flow. The ports on the NextPort DFC support both modem and digital services. Ports can be aggregated at the slot level of the NextPort module, the Service Processing Element (SPE) level within the NextPort module, and the individual port level.
Instead of the traditional line/modem one-to-one correspondence, lines are mapped to an SPE that resides on the Cisco AS5400 NextPort DFC. Each SPE provides modem services for six ports. Busyout and shutdown can be configured at the SPE or port level. The NextPort DFC introduces the slot and SPE software hierarchy. On the Cisco AS5400, the hierarchy designation is slot/spe. The NextPort DFC slot is defined as a value between 1 and 7. Slot 0 is reserved for the motherboard. Each NextPort DFC provides 18 SPEs. The SPE value ranges from 0 to 17. Since each SPE has six ports, the NextPort DFC has a total of 108 ports. The port value ranges from 0 to 107.
The NextPort DFC performs the following functions:
SPE firmware is automatically downloaded to a NextPort DFC from the Cisco AS5400 when you boot the system for the first time, or when you insert a NextPort DFC while the system is operating. When you insert DFCs while the system is operating, the Cisco IOS image recognizes the cards and downloads the required firmware to the cards.
The SPE firmware image is bundled with the access server Cisco IOS image. The SPE firmware image uses an auto detect mechanism, which enables the NextPort DFC to service multiple call types. An SPE detects the call type and automatically configures itself for that operation. For further information on upgrading SPE firmware from the Cisco IOS image, see the "Configuring SPEs to Use an Upgraded Firmware File" section.
The firmware is upgradable independent of Cisco IOS upgrades, and different firmware versions can be configured to run on SPEs in the same NextPort DFC. You can download firmware from the Cisco Systems Cisco Connection Online (CCO) File Transfer Protocol (FTP) server. For further information on upgrading SPE firmware from the Cisco CCO FTP server, see the "Upgrading SPE Firmware from the Cisco CCO FTP Server" section.
Upgrading SPE firmware from the Cisco CCO FTP server can be done in two steps:
 |
Note You must be a registered Cisco user to log in to the Cisco Software Center. |
You can download software from the Cisco Systems CCO FTP server using an Internet browser or using an FTP application. Both procedures are described.
Step 2 Bring up the Cisco Software Center home page at the following URL (this is subject to change without notice):
http://www.cisco.com/kobayashi/sw-center/
Step 3 Click Access Products (under Cisco Software Products) to open the Access Products window.
Step 4 Click Cisco AS5400 Series Software.
Step 5 Click the SPE firmware you want and download it to your workstation or PC. For example, to download SPE firmware for the universal access server, click Download Universal Images.
Step 6 Click the SPE firmware file you want to download, and then follow the remaining download instructions. If you are downloading the SPE firmware file to a PC, make sure that you download the file to the c:/tftpboot directory; otherwise, the download process does not work.
Step 7 When the SPE firmware is downloaded to your workstation, transfer the file to a Trivial File Transfer Protocol (TFTP) server in your LAN using a terminal emulation software application.
Step 8 When the SPE firmware is downloaded to your workstation, transfer the file to a TFTP server somewhere in your LAN using a terminal emulation software application.
|
Note The directory path leading to the SPE firmware files on cco.cisco.com is subject to change without notice. If you cannot access the files using an FTP application, try the Cisco Systems URL http://www.cisco.com/cgi-bin/ibld/all.pl?i=support&c=3. |
terminal> ftp cco.cisco.com
Connected to cio-sys.cisco.com.
Step 2 Enter your CCO registered username and password (for example, harry and letmein):
Name (cco.cisco.com:harry): <harry>
331 Password required for harry.
Password: <letmein>
230-#############################################################
230-# Welcome to the Cisco Systems CCO FTP server.
230-# This server has a number of restrictions. If you are not familiar
230-# with these, please first get and read the /README or /README.TXT file.
230-# http://www.cisco.com/acs/info/cioesd.html for more info.
230-#############################################################
230-
Step 3 Specify the directory path that holds the SPE firmware you want to download. For example, the directory path for the Cisco AS5400 SPE firmware is /cisco/access/5400:
ftp> cd /cisco/access/5400
250-Please read the file README
250- it was last modified on Tue May 27 10:07:38 1997 - 48 days ago
250-Please read the file README.txt
250- it was last modified on Tue May 27 10:07:38 1997 - 48 days ago
250 CWD command successful.
Step 4 Enter the ls command to view the contents of the directory:
ftp> ls
227 Entering Passive Mode (192,31,7,130,218,128)
150 Opening ASCII mode data connection for /bin/ls.
total 2688
drwxr-s--T 2 ftpadmin ftpcio 512 Jun 30 18:11 .
drwxr-sr-t 19 ftpadmin ftpcio 512 Jun 23 10:26 ..
lrwxrwxrwx 1 root 3 10 Aug 6 1996 README ->README.txt
-rw-rw-r-- 1 root ftpcio 2304 May 27 10:07 README.txt
-r--r--r-- 1 ftpadmin ftpint 377112 Jul 10 18:08 np-spe-upw-1.0.1.2.bin
-r--r--r-- 1 ftpadmin ftpint 635 Jul 10 18:08 SPE-firmware.3.1.30.readme
Step 5 Specify a binary image transfer:
ftp> binary
200 Type set to I.
Step 6 Copy the SPE firmware files from the access server to your local environment with the get command.
Step 7 Quit your terminal session:
ftp> quit
Goodbye.
Step 8 Enter the ls -al command to verify that you successfully transferred the files to your local directory:
server% ls -al
total 596
-r--r--r-- 1 280208 Jul 10 18:08 np-spe-upw-1.0.1.2.bin
server% pwd
/auto/tftpboot
Step 9 Transfer these files to a local TFTP or remote copy protocol (RCP) server that your access server or router can access.
The procedure for copying the SPE firmware file from your local TFTP server to the NextPort DFC is a two-step process. First, transfer the SPE firmware to the access server's Flash memory. Then, configure the SPEs to use the upgrade firmware. The upgrade occurs automatically, either as you leave configuration mode, or as specified in the configuration.
These two steps are performed only once. After you copy the SPE firmware file into Flash memory for the first time, you should not have to perform these steps again.
|
Note Because the SPE firmware is configurable for individual SPEs or ranges of SPEs, the Cisco IOS software automatically copies the SPE firmware to each SPE each time the access server restarts. |
To transfer SPE Firmware to Flash memory, follow these steps to download the Universal SPE firmware to Flash memory:
Router# show flash System flash directory: File Length Name/status 1 4530624 c5400-js-mx [498776 bytes used, 16278440 available, 16777216 total] 16384K bytes of processor board System flash (Read/Write)
Step 2 Enter the copy tftp flash command to download the code file from the TFTP server into the access server Flash memory. You are prompted for the download destination and the remote host name.
Router# copy tftp flash
Step 3 Enter the show flash command to verify that the file has been copied into the access server Flash memory:
Router# show flash
The NextPort DFC port is not supported on other Cisco access servers.
For further information about managing port services with NextPort DFC, see the following documents that ship with your Cisco AS5400. These documents are also available online and on the
documentation CD.
For further information about dial technology, see the following documents:
|
Note The SPE support is also available on the Cisco AS5800 universal port card. |
Standards
Carrier protocols
Error-correcting link-access protocols
Compression protocols
MIBs
The following MIBs are supported on the Cisco AS5400:
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None.
See the following sections for configuration tasks for the NextPort port service management feature. Configuring Country Code is a required step; all the other steps are optional:
To set the NextPort DFC to be operational for call set up, you must specify the country name. To specify the country name, perform the following task in global configuration mode:
| Command | Purpose | ||
|---|---|---|---|
| Specifies the country to set the DFC parameters (including country code and encoding). If you do not specify a country, the interface uses the default. If the access server is configured with T1 interfaces, the default is usa. If the access server is configured with E1 interfaces, the default is e1-default. Use the no form of this command to set the country code to the default of the domestic country.
|
To configure the SPEs to use the upgraded firmware file, use the following steps beginning in EXEC mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Router#show spe version | Displays SPE firmware versions to obtain the On-Flash firmware filename. |
Step 2 | Router#config terminal | Enters global configuration mode. |
Step 3 | Router(config)#spe slot/spe or Router(config)#spe slot/spe slot/spe | Enters the SPE configuration mode. You can choose to configure a single SPE or range of SPEs by specifying the first and last SPE in the range. |
Step 4 | Router(config-spe)#firmware upgrade {busyout | download-maintenance | reboot} | Specifies the upgrade method. Three methods of upgrade are available. The busyout keyword waits until all calls are terminated on an SPE before upgrading the SPE to the designated firmware. The download-maintenance keyword upgrades the firmware during the download maintenance time. The reboot keyword requests the access server to upgrade firmware at the next reboot. |
Step 5 | Router(config-spe)#firmware location filename | Specifies the SPE firmware file in Flash memory to use for the selected SPEs. Allows you to upgrade firmware for SPEs after the new SPE firmware image is copied to your Flash memory. Enter the no firmware location command to revert back to the default Cisco IOS bundled SPE firmware. |
Step 6 | Router(config-spe)#exit | Exits SPE configuration mode. |
Step 7 | Router#exit | Exits global configuration mode. |
Step 8 | Router#copy running-config startup-config | Saves your changes. |
|
Note The copy ios-bundled command is not necessary with NextPort DFCs. By default, the version of SPE firmware bundled with the Cisco IOS software release transfers to all SPEs not specifically configured for a different SPE firmware file. |
To disable specific SPEs in the NextPort DFC, complete the following steps starting in global configuration mode:
| Command | Purpose |
|---|---|
or | Enters SPE configuration mode. You can also configure SPEs specifying the first and last SPE in the range. |
| Gracefully disables an SPE by waiting for all the active services on the specified SPE to terminate. You can perform auto-diagnostic tests and firmware upgrades when you put the SPEs in the Busiedout state. Active ports on the specified SPE will change the state of the specified range of SPEs to the BusyoutPending state. The state changes from BusyoutPending to Busiedout when all calls end. Use the show spe command to see the state of the range of SPEs. Use the no form of this command to re-enable the SPEs. |
| Clears active calls on all ports on the SPE. Calls can no longer be placed on the SPE because the SPE state is changed to Busiedout. Use the no form of this command to re-enable the ports on the SPE. |
To reboot specified SPEs, perform the following task in privileged EXEC mode:
| Command | Purpose | ||
|---|---|---|---|
Router#clear spe slot/spe | Allows manual recovery of a port that is frozen in a suspended state. Reboots SPEs that are in suspended or Bad state. Downloads configured firmware to the specified SPE or range of SPEs and power-on self test (POST) is executed.
This command can be executed regardless of the state of SPEs. All active ports running on the SPE are prematurely terminated, and messages are logged into the appropriate log. |
To configure the lines and ports to dial in to your network, complete the following steps beginning in global configuration mode:
To verify your SPE line configuration, perform the following steps:
Router# show spe
Step 2 Enter the show line command to display a summary for a single line:
Router# show line 1
|
Note If you are having trouble, make sure that you have turned on the protocols for connecting to the lines (transport input all) and that your access server is configured for incoming and outgoing calls (modem inout). |
This section describes how to configure NextPort DFC ports. You need to be in port configuration mode to configure the NextPort ports. The port configuration mode allows you to shut down or put individual ports or ranges of ports in busyout mode. To configure NextPort ports, perform the following steps beginning in global configuration mode:
| Command | Purpose | |||
|---|---|---|---|---|
Step 1 | Router(config)#port slot/port | Enters port configuration mode. Configures a single port. | ||
Step 2 | Router(config-port)#port slot/port slot/port | Configures a range of ports. | ||
Step 3 | Router(config-port)#busyout | (Optional) Gracefully disables a port by waiting for the active services on the specified port to terminate. Use the no form of this command to re-enable the ports. Maintenance activities, such as testing, can still be performed while the port is in busyout mode.
| ||
Step 4 | Router(config-port)#shutdown | (Optional) Clears active calls on the port. No more calls can be placed on the port in the shutdown mode. Use the no form of this command to re-enable the ports.
| ||
Step 5 | Router(config-port)#exit | Exits the port configuration mode. |
The following privileged EXEC mode commands allow you to clear ports on an SPE:
| Command | Purpose |
|---|---|
Router# Router# clear port 4/1 Router# This will clear port 4/01 [confirm] yes | Clears port 1 on slot 4 of the NextPort port on the Cisco AS5400. |
Router# clear port 4 Router# This will clear port 4/00 - 4/107 [confirm] yes | Clears all active ports on slot 4 of the NextPort port on the Cisco AS5400. |
Depending on the configuration, call record is displayed on the console, or the syslog, or on both. The log contains raw data in binary form, which must be viewed using the show commands listed in the "Monitoring SPE Performance Statistics" section. You can configure some aspects of history events by using the following commands in global configuration mode:
| Command | Purpose |
|---|---|
Router(config)#spe call-record modem max-userid | Requests the access server to generate a modem call record after a call is terminated. To disable this function, use the no form of this command. |
Router(config)#spe log-event-size number | Sets the maximum size of the history event queue log entry for each port. The default is 50 events per port. |
The following privileged EXEC mode commands allow you to clear some or all of the log events relating to the SPEs:
| Command | Purpose |
|---|---|
Router#clear spe log | Clears all event entries in the slot history event log. |
Router#clear spe counters | Clears statistical counters for all types of services for the specified SPE, a specified range of SPEs, or all SPEs. If you do not specify the range of SPEs or an SPE, the statistics for all SPEs are cleared. |
Router#clear port log | Clears all event entries in the port level history event log. You cannot remove individual service events from the port log. |
This section provides troubleshooting information for your SPEs regardless of service type mode.
|
Note SPE ports that pass the diagnostic test are marked as Pass, Fail, and Unkn. Ports that fail the diagnostic test are marked as Bad. These ports cannot be used for call connections. Depending on how many ports are installed, the diagnostic tests may take from 5 to 10 minutes to complete. |
When an SPE port is tested as Bad, you may perform additional testing by conducting a series of internal back-to-back connections and data transfers between two SPE ports. All port test connections occur inside the access server. For example, if mobile users cannot dial into port 2/5 (which is the sixth port on the NextPort DFC in the second chassis slot), attempt a back-to-back test with port 2/5 and a known-functioning port such as port 2/6.
|
Note You might need to enable this command on several different combinations of ports to determine which one is not functioning properly. A pair of operable ports successfully connects and completes transmitting data in both directions. An operable port and an inoperable port do not successfully connect with each other. |
Router# test port modem back-to-back 2/10 3/20 Repetitions (of 10-byte packets) [1]: *Mar 02 12:13:51.743:%PM_MODEM_MAINT-5-B2BCONNECT:Modems (2/10) and (3/20) connected in back-to-back test:CONNECT33600/V34/LAP *Mar 02 12:13:52.783:%PM_MODEM_MAINT-5-B2BMODEMS:Modems (3/20) and (2/10) completed back-to-back test:success/packets = 2/2
 |
Tips You may reboot the port that has problems using the clear spe command. |
|
Tips You may also schedule recovery using the spe download maintenance command. |
This section documents various SPE performance statistics for the NextPort DFC:
To view SPE events and firmware statistics for the NextPort DFCs, enter one or more of the following commands in privileged EXEC mode:
| Command | Purpose | ||
|---|---|---|---|
Router#show spe slot/spe | Displays the SPE status for the specified range of SPEs. | ||
Router#show spe log [reverse | slot] | Displays the SPE system log. | ||
Router#show spe version | Lists all SPEs and the SPE firmware files used.
|
| Command | Purpose |
|---|---|
Router#show port config {slot | slot/port} | Displays the configuration information for specified ports or the specified port range. The port should have an active session associated at the time the command is executed. |
Router#show port digital log [reverse slot/port] [slot | slot/port] | Displays the digital data event log. |
Router#show port modem log [reverse slot/port] [slot | slot/port] | Displays the port history event log. |
Router#show port modem test [slot | slot/port] | Displays the test log for the specified SPE port range or all the SPE ports. |
Router#show port operational-status [slot | slot/port] | Displays the operational status of the specified ports or the specified port range. The port should have an active session associated at the time the command is executed. |
To view digital SPE statistics for the NextPort DFCs, enter one or more of the following commands in privileged EXEC mode:
| Command | Purpose |
|---|---|
Router#show spe digital [slot | slot/spe] | Displays history statistics of all digital SPEs. |
Router#show spe digital active [slot | slot/spe] | Displays active digital statistics of a specified SPE, the specified range of SPEs, or all the SPEs. |
Router#show spe digital csr [summary | slot | slot/spe] | Displays the digital call success rate statistics for a specific SPE, a range of SPEs, or all the SPEs. |
Router#show spe digital disconnect-reason [summary | slot | slot/spe] | Displays the digital disconnect reasons for the specified SPE or range of SPEs. The disconnect reasons are displayed with Class boundaries. |
Router#show spe digital summary [slot | slot/spe] | Displays digital history statistics of all SPEs, a specified SPE, or the specified range of SPEs for all service types. |
| Command | Purpose |
|---|---|
Router#show spe modem active {slot | slot/spe} | Displays the active statistics of a specified SPE, a specified range of SPEs, or all the SPEs serving modem traffic. |
Router#show spe modem csr {summary | slot | slot/spe} | Displays the call success rate statistics for a specific SPE, range of SPEs, or all the SPEs. |
Router#show spe modem disconnect-reason {summary | slot | slot/spe} | Displays the disconnect reasons for the specified SPE or range of SPEs. The disconnect reasons are displayed with Class boundaries. |
Router#show spe modem high speed {summary | slot | slot/spe} | Shows the connect-speeds negotiated within each high speed modulation or codecs for a specific range of SPEs or all the SPEs. |
Router#show spe modem low speed {summary | slot | slot/spe} | Shows the connect-speeds negotiated within each low speed modulation or codecs for a specific range of SPEs or all the SPEs. |
Router#show spe modem high standard {summary | slot | slot/spe} | Displays the total number of connections within each low modulation or codec for a specific range of SPEs. |
Router#show spe modem low standard {summary | slot | slot/spe} | Displays the total number of connections within each high modulation or codec for a specific range of SPEs. |
Router#show spe modem summary {slot | slot/spe} | Displays the history statistics of all SPEs, specified SPE or the specified range of SPEs. |
The NextPort dial feature card (DFC) provides port service management for the Cisco AS5400.
For further information on configuration examples for the Cisco AS5400, see the Cisco AS5400 Universal Access Server Software Configuration Guide.
Posted: Wed Sep 27 13:58:06 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.