-
Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide
-
Preface
-
Chap 1: Understanding Basic Hardware Architecture and Cisco IOS Software
-
Chap 2: Verifying Basic Setup
-
Chap 3: Basic Configuration Using the Command-Line Interface
-
Chap 4: Continuing Configuration Using the Command-Line Interface
-
Chap 5: Managing and Troubleshooting the Universal Port Card
-
Chap 6: Configuring Voice over IP
-
Appendix A: Using the Setup Script
-
Appendix B: ROM Monitor
-
Appendix C: Comprehensive Configuration Examples
-
Feedback
Table Of Contents
Managing and Troubleshooting the Universal Port Card
Managing SPE Performance Statistics
Viewing SPE Performance Statistics
Port Configuration Mode Commands
SPE Configuration Mode Commands
Configure SPE Diagnostic Tests
Displaying SPE Firmware Versions
Upgrading SPE Firmware from the Cisco.com FTP Server
Download SPE Firmware from the Cisco.com FTP Server to a Local TFTP Server
Copy the SPE Firmware File from Local TFTP Server to the SPEs
Using SPE Firmware Bundled with Cisco IOS Software
Managing and Troubleshooting the Universal Port Card
Note
The information herein applies to the Cisco AS5350, Cisco AS5400, and Cisco AS5400HPX universal gateways. Note that the latter requires use of Cisco IOS release 12.2(2)XB or later.
Note
A universal port card is a hardware card that processes digital signals for the Cisco AS5350 and Cisco AS5400 universal gateways. Ports on the universal port card support multiple types of services such as modem, fax, digital data, and voice. You can manage your port connections at the universal-port-card slot level, service-processing-element (SPE) level, or port level using monitoring and troubleshooting commands. A port is defined as an endpoint on a trunk card through which multiservice tones, voice, and data flow. There are multiple ports per SPE.
Tip
•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/index.htm
or
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5400/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/software/. Select your Cisco IOS release and search for this title.•
http://www.cisco.com/warp/public/76/nextport_compare.htmlThe universal port card introduces slot and SPE software hierarchies. On the Cisco AS5350 and Cisco AS5400, the hierarchy designation is slot/spe and slot/port:
•
•
•
For example, universal-port-card port 2/5 is the sixth port in the second chassis slot on the gateway. Slot 0 is reserved for the motherboard.
You can perform the following functions on an SPE:
•
•
•
•
This chapter includes the following sections:
•
Managing SPE Performance Statistics
Configuration
By default, an event log is enabled and based on one event queue per SPE port. The log contains raw data in binary form, which must be viewed using the show commands listed in the "Viewing SPE Performance Statistics" section. You may configure some aspects of how the record is kept using the following global configuration mode commands (at the AS5350(config)# or AS5400(config)# prompt):
•
•
•
The following privileged EXEC mode commands allow you to clear some or all of the log events relating to the SPEs (at the AS5350# or AS5400# prompt):
•
•
•
Viewing SPE Performance Statistics
You can view SPE statistics using the Cisco IOS software with the gateway. To view performance statistics for the universal port cards, enter one or more of the following commands in privileged EXEC mode (at the AS5350# or AS5400# prompt):
show spe voice Commands
•
•
show spe digital Commands
•
•
•
•
show spe modem Commands
•
•
•
•
•
show spe Commands
•
•
•
•
show port Commands
•
•
•
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121limit/121x/
121xh/121xh_2/dt_cltrk.htm)•
•
Managing Ports
This section describes how to manage universal ports. You can clear ports, remove ports from service, and disable ports from dial-up service by using port configuration mode. For details on disabling a port from dial-up service, see the "Troubleshooting" section.
Clear Ports
To clear a port means to deactivate calls on a port or to clear the Bad state on a port and reset it. Ports need to be cleared if communication attempts with the port have failed or if the port is to be removed from operation.
Use the show spe slot/spe command to view the active ports on an SPE. To clear ports on an SPE, enter the following command in privileged EXEC mode. You can clear all ports on the gateway, all ports on a slot, or a port. This replaces the clear modem command.
•
AS5400# clear port 4/1AS5400# This will clear port 4/01 [confirm] yesAS5400#•
AS5400# clear port 4AS5400# This will clear port 4/00 - 4/107 [confirm] yesAS5400#If slot/port is specified, the port on that SPE is cleared. If slot is specified, all active ports on that particular slot are cleared. If no argument is specified, all ports are cleared.
Additionally, this command clears the Bad state on a port and resets it. However, the port is not cleared if the SPE was previously in a Bad state due to an SPE firmware download.
Port Configuration Mode
Port configuration mode allows you to enter a mode similar to line configuration mode. This mode allows individual ports or ranges of ports to be shut down or put in busyout mode. Port configuration mode commands replace the modem range, modem busyout, and modem shutdown commands used with MICA modems.
•
AS5400# configure terminalEnter configuration commands, one per line. End with CNTL/Z.AS5400(config)# port 3/1AS5400(config-port)#•
AS5400# configure terminalEnter configuration commands, one per line. End with CNTL/Z.AS5400(config)# port 3/1 3/18AS5400(config-port)#Port Configuration Mode Commands
The following commands are available in port configuration mode:
•
Note
•
Note
Managing SPEs
This section describes how to manage SPEs by setting the SPE country code, entering SPE configuration mode, upgrading the SPE firmware, performing busyout on SPEs, and clearing active calls on the SPEs.
SPE Country
On the Cisco AS5350 and Cisco AS5400, DS-0 companding law selection is configured for the entire system rather than on individual voice ports.
To configure companding on your CT1/CE1/CT3 controller lines, you must use the spe country command in global configuration mode. (This command replaces the modem country command. If you do not specify a country, your controller line uses the default.
For T1 interfaces, the default is t1-default (Mu-Law); for E1 interfaces, the default is e1-default (A-Law). Use the no form of this command to set the country code to the default.
Supported countries include, but are not limited to, those shown in Table 5-1:
Note
•
AS5400(config)# spe country usaAS5400(config)#•
AS5400# show speSPE settings:==============Country code configuration usaPolling interval: 12 secs.History log events: 50(per port)Port legends:============Port state: (s)shutdown (t)test (r)recovery (d)download(b)busiedout (p)busyout pending, (B)bad (a)active callCall type: (m)modem (d)digital (v)voice (_)not in useSPE SPE SPE SPE Port CallSPE# Port # State Busyout Shut Crash State Type4/00 0000-0005 ACTIVE 0 0 0 ______ ______4/01 0006-0011 ACTIVE 0 0 0 ______ ______4/02 0012-0017 ACTIVE 0 0 0 ______ ______4/03 0018-0023 ACTIVE 0 0 0 ______ ______4/04 0024-0029 ACTIVE 0 0 0 ______ ______4/05 0030-0035 ACTIVE 0 0 0 ______ ______4/06 0036-0041 ACTIVE 0 0 0 ______ ______4/07 0042-0047 ACTIVE 0 0 0 ______ ______4/08 0048-0053 ACTIVE 0 0 0 ______ ______4/09 0054-0059 ACTIVE 0 0 0 ______ ______4/10 0060-0065 ACTIVE 0 0 0 ______ ______4/11 0066-0071 ACTIVE 0 0 0 ______ ______4/12 0072-0077 ACTIVE 0 0 0 ______ ______4/13 0078-0083 ACTIVE 0 0 0 ______ ______4/14 0084-0089 ACTIVE 0 0 0 ______ ______4/15 0090-0095 ACTIVE 0 0 0 ______ ______4/16 0096-0101 ACTIVE 0 0 0 ______ ______4/17 0102-0107 ACTIVE 0 0 0 ______ ______SPE Configuration Mode
SPE configuration mode allows you to enter SPE configuration mode, which is similar to line configuration mode. You can configure an SPE by specifying a slot and an SPE associated with the slot or, you can choose to configure a range of SPEs by specifying the first and last SPE in the range.
The following example demonstrates how to enter SPE configuration mode.
AS5400# config tEnter configuration commands, one per line. End with CNTL/Z.AS5400(config)# spe 1/1 1/17AS5400(config-SPE)#SPE Configuration Mode Commands
The following commands are available in SPE configuration mode:
•
•
–
–
–
•
•
Troubleshooting
This section provides troubleshooting information that apply to your modems regardless of service type mode. You learn how to perform diagnostic tests on installed ports or SPEs, configure automatic recovery of ports on an SPE, and configure a scheduled recovery of SPEs.
Configure SPE Diagnostic Tests
You can perform three types of diagnostic tests on your SPE modem:
SPE Startup Test
To perform diagnostic testing on all your installed SPE ports during the system's initial startup or rebooting process, in global configuration mode with the prompt displayed as AS5350# or AS5400#, enter the following command:
port modem startup-test—Perform diagnostic testing for all modems.
The results of the SPE port startup test are displayed in the show port modem test command output. SPE ports that pass the diagnostic test are 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, this diagnostic test may take from 5 to 10 minutes to complete. Perform additional testing on an inoperative SPE port by executing the test port modem back-to-back command. The no port modem startup-test command disables startup testing.
SPE Auto-Test
To perform diagnostic testing on all the installed SPE ports during the system's initial startup or rebooting process, or during service, in global configuration mode with the prompt displayed as AS5350(config)# or AS5400(config)#, enter the following command:
port modem autotest—Perform diagnostic testing for all ports.
The results of the SPE port auto-test are displayed in the show port modem test command's output. Ports that pass the diagnostic test are marked as Idle, Busy, Downloading, and Reset, and are put into service. Ports that fail the diagnostic test are marked as Bad, and are not put into service or tested again until they are no longer marked as Bad. If all the ports of an SPE are bad, the corresponding SPE is also marked bad. These ports cannot be used for call connections. Depending on how many ports are present and not marked Bad, this diagnostic test may take from 5 to 10 minutes to complete. You may perform additional testing on an inoperative port by executing the test port modem back-to-back command. The no port modem autotest command disables testing.
You may additionally configure the following options:
•
•
•
A sample diagnostic autotest setting the time at 12:45 and at 8 hour intervals looks like the following:
AS5400(config)# port modem autotest time 12:45 8AS5400(config)#SPE Back-to-Back Test
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 gateway. For example, if mobile users cannot dial into port 2/5 (the sixth port on the universal port card 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.
Enter the following command in privileged EXEC mode (the prompt is displayed as AS5350# or AS5400#) to perform internal back-to-back port tests between two ports:
test port modem back-to-back slot/port slot/port [num-packets]—Perform internal back-to-back port tests between two ports, sending test packets of the specified size.
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 connect and complete transmitting data in both directions. An operable port and an inoperable port do not successfully connect with each other.
A sample back-to-back test might look like the following:
AS5400# test port modem back-to-back 2/10 3/20Repetitions (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/2A port that has been confirmed to have problems can often be fixed using the clear spe command. For more information, see the "Clear an SPE" section.
The results of the test port modem back-to-back command are displayed in the show port modem test command's output:
AS5400# show port modem testDate Time Modem Test Reason State Result3/02 12:00:57 PM 2/01 Back-To-Back :STARTUP TEST Idle PASS3/02 12:00:57 PM 2/00 Back-To-Back :STARTUP TEST Idle PASS3/02 12:00:58 PM 2/02 Back-To-Back :STARTUP TEST Idle PASS3/02 12:00:58 PM 2/03 Back-To-Back :STARTUP TEST Idle PASS3/02 12:00:58 PM 2/04 Back-To-Back :STARTUP TEST Idle PASS3/02 12:00:58 PM 2/05 Back-To-Back :STARTUP TEST Idle PASS...3/02 12:01:14 PM 3/95 Back-To-Back :STARTUP TEST Idle PASS3/02 12:01:14 PM 3/94 Back-To-Back :STARTUP TEST Idle PASS3/02 12:01:15 PM 3/75 Back-To-Back :STARTUP TEST Idle PASS3/02 12:01:15 PM 3/74 Back-To-Back :STARTUP TEST Idle PASS3/02 12:13:52 PM 3/20 Back-To-Back :USER INITIATED Idle PASS3/02 12:13:52 PM 2/10 Back-To-Back :USER INITIATED Idle PASS...3/02 12:44:00 PM 3/102 No Test (Time) :MIN IDLE MODEMS Idle NOTST3/02 12:44:00 PM 3/103 No Test (Time) :MIN IDLE MODEMS Idle NOTST3/02 12:44:00 PM 3/104 No Test (Time) :MIN IDLE MODEMS Idle NOTST3/02 12:44:00 PM 3/105 No Test (Time) :MIN IDLE MODEMS Idle NOTST3/02 12:44:00 PM 3/106 No Test (Time) :MIN IDLE MODEMS Idle NOTST3/02 12:44:00 PM 3/107 No Test (Time) :MIN IDLE MODEMS Idle NOTST3/02 12:44:21 PM 2/73 Back-To-Back :TIME INTERVAL Idle PASS3/02 12:44:21 PM 2/72 Back-To-Back :TIME INTERVAL Idle PASS3/02 12:44:21 PM 2/33 Back-To-Back :TIME INTERVAL Idle PASS3/02 12:44:21 PM 2/32 Back-To-Back :TIME INTERVAL Idle PASS3/02 12:44:21 PM 3/37 Back-To-Back :TIME INTERVAL Idle PASS
Note
SPE Recovery
You may configure automatic recovery (removal from service and reloading of SPE firmware) of ports on an SPE at any available time from global configuration mode (the prompt is AS5350(config)# or AS5400(config)#) as shown:
spe recovery {port-action {disable | recover | none} | port-threshold num-failures}
When an SPE port fails to connect for a certain number of consecutive times, a problem exists in a specific part or the whole of SPE/firmware. Such SPEs have to be recovered by downloading firmware. Any port failing to connect num-failures times is moved to a state based on port-action, where you can choose to disable (mark the port as Bad) or recover the port when the SPE is in IDLE and has no active calls. The default for num-failures is 30.
You may also schedule recovery using the spe download maintenance configuration command.
SPE Download Maintenance
You may configure a scheduled recovery of SPEs from global configuration mode (the prompt is AS5350(config)# or AS5400(config)#) as shown:
spe download maintenance time hh:mm | stop-time hh:mm | max-spes num-of-spes | window time-period | expired-window {drop-call | reschedule}
Download maintenance starts at time, steps through all the SPEs that need recovery and SPEs that need a firmware upgrade, and starts maintenance on max-spes at a time. It waits for the window delay time for all the ports on the SPE to become inactive before moving the SPE to the idle state. It downloads firmware immediately after the SPE moves to idle. If the ports are still in use by the end of (window), depending on the expired-window setting, connections on the SPE ports are shut down and the firmware is downloaded by choosing the drop-call option, or the firmware download is rescheduled to the next download maintenance time by choosing the reschedule option. This process continues until the number of SPEs under maintenance are below max-spes, or until stop-time (if set), or until all SPEs marked for recovery or upgrade have had their firmware reloaded. The default download-maintenance time is 03:00.
Clear an SPE
The clear spe privileged EXEC mode command allows you to manually recover a port that is frozen in a suspended state. This command causes the firmware configured for that SPE to be downloaded to the specified SPE or the range of SPEs and Power On Self Test (POST) to be executed. This command can be executed regardless of the state of the SPEs. All active ports running on the SPE are prematurely terminated and messages are logged into the appropriate log. This replaces the clear modem command.
The following example shows a coldstart on SPE 1 on slot 1:
AS5400# clear spe 1/1AS5400# Are you sure you want to clear SPE 1/1(Y/N)? YUpgrading SPE Firmware
With new systems, Cisco loads a Cisco IOS software-compatible version of SPE firmware into each installed SPE. A map of the version(s) of SPE firmware copied to RAM for each SPE is stored in nonvolatile random-access memory (NVRAM) so that it is retained over power cycles.
Note
You can acquire new SPE firmware from the Cisco Software Center in one of two ways:
•
•
When you have the new firmware, you can configure different firmware versions onto individual SPEs or ranges of SPEs on a universal port card. You can also configure different upgrade methods by using the firmware upgrade command.
This section provides instructions for the following:
•
•
•
Important Upgrade Commands
There are several commands you use to upgrade SPE firmware. For examples on using the commands, see the "Upgrading SPE Firmware from the Cisco.com FTP Server" section and the "Using SPE Firmware Bundled with Cisco IOS Software" section.
•
•
•
–
–
–
Note
Displaying SPE Firmware Versions
Use the show spe version command to list the versions of SPE firmware running on the SPEs, residing in system Flash memory, and bundled with Cisco IOS software. This helps you decide if you need to change the version running on the modems.
Note
AS5400# show spe versionIOS-Bundled Default Firmware-Filename Version Firmware-Type===================================== ======= =============system:/ucode/np_spe_firmware1 0.0.6.75 SPE firmwareOn-Flash Firmware-Filename Version Firmware-Type========================== ======= =============flash:np.spe 0.6.4.5 SPE firmwareflash:np_6_77.spe 0.0.6.77 SPE firmwareflash:np_6_79.spe 0.0.6.79 SPE firmwareSPE-# SPE-Type SPE-Port-Range Version UPG Firmware-Filename2/00 CSMV6 0000-0005 0.0.6.75 N/A ios-bundled default2/01 CSMV6 0006-0011 0.0.6.75 N/A ios-bundled default2/02 CSMV6 0012-0017 0.0.6.75 N/A ios-bundled default2/03 CSMV6 0018-0023 0.0.6.75 N/A ios-bundled default2/04 CSMV6 0024-0029 0.0.6.75 N/A ios-bundled default2/05 CSMV6 0030-0035 0.0.6.75 N/A ios-bundled default2/06 CSMV6 0036-0041 0.0.6.77 N/A np_6_77.spe2/07 CSMV6 0042-0047 0.0.6.77 N/A np_6_77.spe2/08 CSMV6 0048-0053 0.0.6.77 N/A np_6_77.spe2/09 CSMV6 0054-0059 0.0.6.77 N/A np_6_77.spe2/10 CSMV6 0060-0065 0.0.6.77 N/A np_6_77.spe2/11 CSMV6 0066-0071 0.0.6.77 N/A np_6_77.spe2/12 CSMV6 0072-0077 0.0.6.79 N/A np_6_79.spe2/13 CSMV6 0078-0083 0.0.6.79 N/A np_6_79.spe2/14 CSMV6 0084-0089 0.0.6.79 N/A np_6_79.spe2/15 CSMV6 0090-0095 0.0.6.79 N/A np_6_79.spe2/16 CSMV6 0096-0101 0.0.6.79 N/A np_6_79.spe2/17 CSMV6 0102-0107 0.0.6.79 N/A np_6_79.speUpgrading SPE Firmware from the Cisco.com FTP Server
Upgrading SPE firmware from the Cisco.com FTP server is a three-step process:
•
•
•
Download SPE Firmware from the Cisco.com FTP Server to a Local TFTP Server
Note
You can download software from the Cisco.com FTP server using an Internet browser or using an FTP application. Both procedures are described.
Using an Internet Browser
Step 1
Step 2
http://www.cisco.com/public/sw-center/Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Using an FTP Application
Note
http://www.cisco.com/pcgi-bin/ibld/all.pl?i=support&c=3
Step 1
terminal> ftp cco.cisco.comConnected to cio-sys.cisco.com.220-220- Cisco Connection Online | | Cisco Systems, Inc.220- Email: cco-team@cisco.com ||| ||| 170 West Tasman Drive220- Phone: +1.800.553.2447 .:|||||:..:|||||:. San Jose, CA 95134220-220- NOTE: As of February 1,1997 ftp.cisco.com will now point to this220- service. Please be advised. To use the former ftp.cisco.com after220- February 1, connect to ftpeng.cisco.com220-220- You may login with:220- + Your CCO username and password, or220- + A special access code followed by your e-mail address, or220- + "anonymous" followed by your e-mail address for guest access.220-220 cio-sys FTP server (CIOESD #103 Sun Dec 15 14:43:43 PST 1996) ready.Step 2
Name (cco.cisco.com:harry): harry331 Password required for harry.Password: letmein230-##############################################################230-# Welcome to the Cisco Systems CCO FTP server.230-# This server has a number of restrictions. If you are not familiar230-# 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-230- ***** NOTE: As of February 1, 1997, "cco.cisco.com", *****230- ***** "www.cisco.com" and "ftp.cisco.com" are now all *****230- ***** logical names for the same machine. *****230- ***** *****230- ***** The old "ftp.cisco.com" is an entirely *****230- ***** different machine, which is now known as *****230- ***** "ftpeng.cisco.com" or "ftp-eng.cisco.com". *****230- ***** *****230- ***** In general, "ftpeng.cisco.com" is used only for *****230- ***** distribution of Cisco Engineering-controlled *****230- ***** projects, such as beta programs, early field *****230- ***** trials, developing standards documents, etc. *****230- ***** *****230- ***** Be sure to confirm you have connected to *****230- ***** the machine you need to interact with. *****230-230- If you have any odd problems, try logging in with a minus sign (-) as230- the first character of your password. This will turn off a feature230- that may be confusing your ftp client program.230- Please send any questions, comments, or problem reports about this230- server to cco-team@cisco.com.230-230- NOTE:230- o To download files from CCO, you must be running a *passive-mode*230- capable FTP client.230- o To drop files on this system, you must cd to the /drop directory.230- o Mirrors of this server can be found at230-230- + ftp://www-europe.cisco.com European (Amsterdam)230- + ftp://www-fr.cisco.com France (Paris)230- + ftp://www-au.cisco.com Australia (Sydney)230- + ftp://www-jp.cisco.com Japan (Tokyo)230- + ftp://www-kr.cisco.com Korea (Seoul)230-230- Please read the file README230- it was last modified on Sat Feb 1 12:49:31 1997 - 163 days ago230 User harry logged in. Access restrictions apply.Remote system type is UNIX.Using binary mode to transfer files.Step 3
ftp> cd /cisco/access/5350250-Please read the file README250- it was last modified on Tue May 27 10:07:38 1997 - 48 days ago250-Please read the file README.txt250- it was last modified on Tue May 27 10:07:38 1997 - 48 days ago250 CWD command successful.Step 4
ftp> ls227 Entering Passive Mode (192,31,7,130,218,128)150 Opening ASCII mode data connection for /bin/ls.total 2688drwxr-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.readme226 Transfer complete.Step 5
ftp> binary200 Type set to I.Step 6
Step 7
ftp> quitGoodbye.Step 8
server% ls -altotal 596-r--r--r-- 1 280208 Jul 10 18:08 np-spe-upw-1.0.1.2.binserver% pwd/auto/tftpbootStep 9
Copy the SPE Firmware File from Local TFTP Server to the SPEs
The procedure for copying the SPE firmware file from your local TFTP server to a universal port card is a two-step process:
1.
2.
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. 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 gateway restarts.
Transfer SPE Firmware to Flash Memory
Follow these steps to download the universal SPE firmware to Flash memory:
Step 1
AS5400# show flashSystem flash directory:File Length Name/status1 4530624 c5350-js-mx[498776 bytes used, 16278440 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)Step 2
Note
If you do not have available space to copy the SPE firmware, during the copy operation the system displays a message telling you to delete the current file and squeeze the Flash memory to make room for the new image. Enter the delete flash:version command, followed by the squeeze flash command, to perform this delete-and-squeeze operation. Then proceed with the copy operation.AS5400# copy tftp flashAddress or name of remote host [192.168.19.91]?Source filename [c5350-js-mz.xm.Feb16]?Destination filename [c5350-js-mz.xm.Feb16]?Accessing tftp://192.168.19.91/c5350-js-mz.xm.Feb16...Loading c5350-js-mz.xm.Feb16 from 192.168.19.91 (via FastEthernet0/0):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 10573848/21147648 bytes]10573848 bytes copied in 77.356 secs (137322 bytes/sec)Step 3
AS5400# show flash-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name1 .. unknown 12375B0E 92704 6 337539 Feb 21 2001 22:46:51 np.spe2 .. image 1A58C7EA AA7F9C 20 10573848 Feb 21 2001 23:11:59 c5350-js-mz.xm.Feb165079140 bytes available (10911644 bytes used)
Configure SPEs to Use an Upgraded Firmware File
Follow these steps to configure the SPEs to use the upgraded firmware:
Step 1
AS5400> enableStep 2
Password: passwordAS5400#You are in privileged EXEC mode when the prompt changes to AS5350# or AS5400#.
Step 3
Note
AS5400# show spe versionIOS-Bundled Default Firmware-Filename Version Firmware-Type===================================== ======= =============system:/ucode/np_spe_firmware1 0.0.6.75 SPE firmwareOn-Flash Firmware-Filename Version Firmware-Type========================== ======= =============flash:np.spe 0.6.4.5 SPE firmwareflash:np_6_77.spe 0.0.6.77 SPE firmwareflash:np_6_79.spe 0.0.6.79 SPE firmwareflash:np-spe-upw-1.0.1.2.bin 1.0.1.2 SPE firmwareSPE-# SPE-Type SPE-Port-Range Version UPG Firmware-Filename2/00 CSMV6 0000-0005 0.0.6.75 N/A ios-bundled default2/01 CSMV6 0006-0011 0.0.6.75 N/A ios-bundled default2/02 CSMV6 0012-0017 0.0.6.75 N/A ios-bundled default2/03 CSMV6 0018-0023 0.0.6.75 N/A ios-bundled default2/04 CSMV6 0024-0029 0.0.6.75 N/A ios-bundled default2/05 CSMV6 0030-0035 0.0.6.75 N/A ios-bundled default2/06 CSMV6 0036-0041 0.0.6.77 N/A np_6_77.spe2/07 CSMV6 0042-0047 0.0.6.77 N/A np_6_77.spe2/08 CSMV6 0048-0053 0.0.6.77 N/A np_6_77.spe2/09 CSMV6 0054-0059 0.0.6.77 N/A np_6_77.spe2/10 CSMV6 0060-0065 0.0.6.77 N/A np_6_77.spe2/11 CSMV6 0066-0071 0.0.6.77 N/A np_6_77.spe2/12 CSMV6 0072-0077 0.0.6.79 N/A np_6_79.spe2/13 CSMV6 0078-0083 0.0.6.79 N/A np_6_79.spe2/14 CSMV6 0084-0089 0.0.6.79 N/A np_6_79.spe2/15 CSMV6 0090-0095 0.0.6.79 N/A np_6_79.spe2/16 CSMV6 0096-0101 0.0.6.79 N/A np_6_79.spe2/17 CSMV6 0102-0107 0.0.6.79 N/A np_6_79.speStep 4
AS5400# configure terminalEnter configuration commands, one per line. End with CNTL/Z.AS5400(config)#You are in global configuration mode when the prompt changes to AS5350(config)# or AS5400(config)#.
Step 5
AS5400(config)# spe slot/speorAS5400(config)# spe slot/spe slot/speYou are in SPE configuration mode when the prompt changes to AS5350(config-SPE)# or AS5400(config-SPE)#.
Step 6
AS5400(config-SPE)# firmware location np-spe-upw-1.0.1.2.binStep 7
AS5400(config-SPE)# firmware upgrade busyout | download-maintenance | rebootStep 8
AS5400(config-SPE)# exitAS5400(config)#Step 9
AS5400(config)# Ctrl-ZAS5400#Step 10
AS5400# copy running-config startup-config
Using SPE Firmware Bundled with Cisco IOS Software
Use this procedure to update SPE firmware on the SPEs in your gateway if you decide to use the version of SPE firmware bundled with Cisco IOS software instead of the version already mapped to your ports.
To set the SPE firmware mapping to the SPE firmware version bundled with Cisco IOS software, enter the following commands:
Step 1
AS5400> enableStep 2
Password: passwordAS5400#You are in privileged EXEC mode when the prompt changes to AS5350# or AS5400#.
Step 3
AS5400# configure terminalEnter configuration commands, one per line. End with CNTL/Z.AS5400(config)#You are in global configuration mode when the prompt changes to AS5350(config)# or AS5400(config)#.
Step 4
AS5400(config)# spe slot/speorAS5400(config)# spe slot/spe slot/speYou are in SPE configuration mode when the prompt changes to AS5350(config-SPE)# or AS5400(config-SPE)#.
Step 5
AS5400(config-SPE)# no firmware locationStep 6
AS5400(config-SPE)# exitAS5400(config)#Step 7
AS5400(config)# Ctrl-ZAS5400#Step 8
AS5400# copy running-config startup-configThis process does not delete any existing SPE firmware that resides in system Flash memory in case you later want to revert to it. If you decide to delete the code from system Flash memory, remember that all files in system Flash memory are deleted; therefore save and restore any important files (for example, the Cisco IOS software image).
Note
Health Monitor
The Health Monitor allows you to see the status of different components of the AS5400:
The show health-monitor summary command shows the status of the following components:
•
•
•
The show health-monitor summary command provides high level component status.
The show health-monitor command shows more details such as the status of sub components.
The following example shows the display output of the show health-monitor command:
AS5400#show health-monitorChassis:Power Supply FailureRedundant Power System is present.PS Input Voltage status: failurePS Output Voltage status: failurePS Fan status: normalPS Thermal status: normalPS OverVoltage status: normalTemperature OKFans OKMemory:Free Memory processor OKMemory Fragmentation Processor OKFree Memory I/O OKMemory Fragmentation I/O OKDetailed summary:Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 62EC07E0 219412512 67221920 152190592 142181548 139874020I/O 40000000 67110380 46387964 20722416 20722416 20706928DFC's:Slot 1 (NP108 DFC) OKSlot 2 (NP108 DFC) OKSlot 3 (NP108 DFC) OKSlot 4 (NP60 DFC) OKSlot 5 (NP108 DFC) OK, 1 SPE's BADSlot 7 (CT3 DFC) OKAS5400#AS5400#AS5400#AS5400#AS5400#show health-monitor summAS5400#show health-monitor summary ?| Output modifiers<cr>The following example shows the display output of the show health-monitor summary command:
AS5400#show health-monitor summaryChassis:Power Supply FailureTemperature OKFans OKMemory:Free Memory processor OKMemory Fragmentation Processor OKFree Memory I/O OKMemory Fragmentation I/O OKDFC's:Slot 1 (NP108 DFC) OKSlot 2 (NP108 DFC) OKSlot 3 (NP108 DFC) OKSlot 4 (NP60 DFC) OKSlot 5 (NP108 DFC) OKSlot 7 (CT3 DFC) OKInterface Queue Wedge Monitor
The Interface Queue Wedge Monitor displays information about interface queue wedges and the times that they occur. An interface queue is wedged when the packet count that is being transmitted (output queue) or received (input queue) is equal to or greater than the maximum packet count size of the queue, and consequently, no more packets are being transmitted or received.
The Interface Queue Wedge Monitor is enabled or disabled using following commands.
•
•
The Interface Queue Wedge Monitor is disabled by default.
When the Interface Queue Wedge Monitor is enabled, it monitors all the input and output queue wedge interfaces. The show wedged-interfaces [output/input] command displays the queue wedged interfaces.
The show wedged-interfaces output command displays the output queue wedge interfaces and their respective time-since-wedges.
The show wedged-interfaces input command displays the input queue wedge interfaces and their respective time-since-wedges.
Interface Queue Wedge Output Procedure
When the Interface Queue Wedge Monitor is enabled, and an interface (such as a FastEthernet0/0 output queue is already wedged, the following message is displayed on the console, syslog, and buffer:
Eg: 00:39:15: %HHM-3-INTFWEDGE: FastEthernet0/0 Output Queue WedgedThe following procedure shows an example of how to enable, disable, and show the results of a wedged interface output:
Step 1
AS5400##conf tEnter configuration commands, one per line. End with CNTL/Z.AS5400#(config)#interface-monitor enableAS5400#(config)#^ZAS5400##Step 2
AS5400##sh wedged-interfaces outputInterface Name Time Since WedgeAsync4/00 00:23:33Async4/01 00:23:26Async4/02 00:23:21Async4/03 00:23:15FastEthernet0/0 00:24:35FastEthernet0/1 00:24:50Virtual-Access2 00:38:19Virtual-Access3 00:38:19AS5400##Step 3
AS5400##show proc cpu | i Intf39 0 341 0 0.00% 0.00% 0.00% 0 Intf Wedge MonitAS5400##Step 4
AS5400##conf tEnter configuration commands, one per line. End with CNTL/Z.AS5400#(config)#no interface-monitor enableAS5400#(config)#^ZAS5400##AS5400##Step 5
AS5400##show proc cpu | i IntfAS5400##Step 6
AS5400##show wedged-interfaces outputInterface Name Time Since WedgeAS5400##AS5400##Step 7
AS5400##conf tEnter configuration commands, one per line. End with CNTL/Z.AS5400#(config)#interface-monitor enableAS5400#(config)#^ZAS5400##00:39:03: %HHM-3-INTFWEDGE: Async4/00 Output Queue Wedged00:39:04: %SYS-5-CONFIG_I: Configured from console by console00:39:06: %HHM-3-INTFWEDGE: Async4/01 Output Queue Wedged00:39:09: %HHM-3-INTFWEDGE: Async4/02 Output Queue Wedged00:39:12: %HHM-3-INTFWEDGE: Async4/03 Output Queue Wedged00:39:15: %HHM-3-INTFWEDGE: FastEthernet0/0 Output Queue Wedged00:39:18: %HHM-3-INTFWEDGE: FastEthernet0/1 Output Queue Wedged00:39:39: %HHM-3-INTFWEDGE: Virtual-Access2 Output Queue Wedged00:39:42: %HHM-3-INTFWEDGE: Virtual-Access3 Output Queue WedgedAS5400##AS5400##AS5400##Step 8
AS5400##sh wedge outInterface Name Time Since WedgeAsync4/00 00:25:26Async4/01 00:25:20Async4/02 00:25:15Async4/03 00:25:08FastEthernet0/0 00:26:29FastEthernet0/1 00:26:44Virtual-Access2 00:40:12Virtual-Access3 00:40:12AS5400##Step 9
AS5400##show proc cpu | i Intf39 0 25 0 0.00% 0.00% 0.00% 0 Intf Wedge MonitWedge Interface Input Procedure
The following procedure shows an example of how to enable, disable, and show the results of wedged interface input:
Step 1
AS5400##sh wedged-interfaces inputInterface Time Since WedgeAsync4/00 00:21:58Async4/01 00:21:51Async4/02 00:21:26Async4/03 00:21:21FastEthernet0/0 11:58:28FastEthernet0/1 11:58:46Virtual-Access2 00:08:46Virtual-Access3 00:08:46AS5400##AS5400##Step 2
AS5400##sh proc cpu | i Intf39 0 21 0 0.00% 0.00% 0.00% 0 Intf Wedge MonitAS5400##AS5400##AS5400##Step 3
AS5400##conf tEnter configuration commands, one per line. End with CNTL/Z.AS5400#(config)#no interface-monitor enableAS5400#(config)#^ZAS5400##AS5400##AS5400##Step 4
AS5400##sh proc cpu | i IntfAS5400##AS5400##Step 5
AS5400##show wedged-interfaces outputInterface Time Since WedgeAS5400##AS5400##Step 6
AS5400##conf tEnter configuration commands, one per line. End with CNTL/Z.AS5400#(config)#interface-monitor enableAS5400#(config)#^ZAS5400##AS5400##AS5400##12:00:50: %HHM-3-INTFWEDGE: Async4/00 Input Queue Wedge12:00:53: %HHM-3-INTFWEDGE: Async4/01 Input Queue Wedge12:00:56: %HHM-3-INTFWEDGE: Async4/02 Input Queue Wedge12:00:59: %HHM-3-INTFWEDGE: Async4/03 Input Queue Wedge12:01:02: %HHM-3-INTFWEDGE: FastEthernet0/0 Input Queue Wedge12:01:05: %HHM-3-INTFWEDGE: FastEthernet0/1 Input Queue Wedge12:01:26: %HHM-3-INTFWEDGE: Virtual-Access2 Input Queue Wedge12:01:29: %HHM-3-INTFWEDGE: Virtual-Access3 Input Queue WedgeAS5400##AS5400##Step 7
AS5400##sh proc cpu | i Intf39 8 110 72 0.00% 0.00% 0.00% 0 Intf Wedge MonitAS5400##Step 8
Here is the o/p again---------------------AS5400##sh wedged-interfaces inputInterface Time Since WedgeAsync4/00 00:24:14Async4/01 00:24:06Async4/02 00:23:42Async4/03 00:23:37FastEthernet0/0 12:00:44FastEthernet0/1 12:01:01Virtual-Access2 00:11:02Virtual-Access3 00:11:02Where to Go Next
At this point you can go to:
•
•
•
http://www.cisco.com/univercd/cc/td/doc/product/software/.
Select your Cisco IOS release and search for this title.
Tip
•
http://www.cisco.com/warp/public/76/nextport_compare.html•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/alxnxpt.htm•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/nextport/index.htm.
Tip
•
