-
Cisco AS5300 Software Configuration Guide
-
About This Guide
-
Chap 1: First-Time Configuration
-
Chap 2: Using Cisco IOS Software
-
Chap 3: Basic Configuration
-
Chap 4: Access Service Security
-
App A: Managing Modems
-
App B: ROM Monitor
-
App C: Using Setup on Cisco IOS Releases 11.2 or 11.3(2)T
-
App D: Upgrade VoIP Software
-
Update to AS5300 Installation and Software Configuration Guides
-
Feedback
Table Of Contents
Configuring Microcom Modems for Monitoring
Configuring MICA Modems for Monitoring
Modem Performance Statistics Commands
Remove Inoperable Modems from Service
Set Time Interval between Polls
Disable a Modem from Dial-Up Services
Important Modem Upgrade Commands
Displaying Modem Code Versions
Upgrading Modem Code from the Cisco CCO TFTP Server
Download Modem Code from the Cisco CCO TFTP Server to a Local TFTP Server
Copy the Modem Code File from Local TFTP Server to Modems
Upgrading Modem Code from Diskettes
Copy the Modem Code to Your PC Hard Disk
Copy the Modem Code from Your PC to the Modems
Using the Modem Code Bundled with Cisco IOS Software
Managing Modems
The Cisco AS5300 universal access servers support MICA or Microcom modem carrier cards. For details on the carrier cards, refer to the Cisco AS5300 Universal Access Server Chassis Installation Guide and Cisco AS5300 Universal Access Server Module Installation Guide, available online at
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/hw_inst/index.htmYou can manage your modems using monitoring, polling, and troubleshooting commands. For both Microcom and MICA modems, most of the modem management functions are identical. This appendix discusses procedures and commands common to both types of modems and procedures and commands that apply to only one type of modem. Sections or commands that apply to only one type of modem are clearly indicated.
This appendix includes the following sections:
Monitoring Modems
This section describes how to send AT commands to MICA and Microcom modems.
For a list and description of AT commands, refer to the following:
•
AT Command Set and Register Summary for MICA Six-Port Modules or AT Command Set, available online at
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/sw_ports/at_set/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/sw_ports/at_set/atcmnds1.htmConfiguring Microcom Modems for Monitoring
To monitor Microcom (V.34 and 56K) modems you must perform two main configuration tasks:
•
•
Table A-1 describes all the steps necessary to enter AT command mode on the access server.
Table A-1 Entering AT Command Mode for Microcom Modems
5300> enable
Password: <password>
5300#
Enter enable mode (also called privileged EXEC mode).
Enter the password.
You have entered enable mode when the 5300# prompt appears.
5300# configure terminal
Enter configuration commands, one per line. End
with CNTL/Z.
5300(config)#
Enter global configuration mode.You have entered global configuration mode when the 5300(config)# prompt appears.
5300(config)# line 1
5300(config-line)#
Enter line configuration mode. In this example, line 1 is specified. You have entered line configuration mode when the 5300(config-line)# prompt appears.
5300(config-line)# modem at-mode-permit
Configure a Microcom modem to permit a direct-connect session.
5300(config-if)# end
5300#
%SYS-5-CONFIG_I: Configured from console by consoleReturn to enable mode.
This message is normal and does not indicate an error.5300# modem at-mode 1/1
You are now entering AT
command mode on modem (slot 1 / port 1).
Please type CTRL-C to exit AT command mode.Enter a direct-connect session with a TA1 . In this example, a direct connect session is established with the TA in
slot 1, port 1. Enter the TA slot number first, followed by the TA port number.Now you are in AT command mode and can enter the AT commands described in this document.
Ctrl-C
5300#
When done entering AT commands, press Ctrl-C to return to enable mode.
1 TA = Terminal Adapter.
Configuring MICA Modems for Monitoring
To send AT commands to a MICA modem involves a reverse Telnet procedure. Table A-2 shows how to enter AT command mode from enable mode (also called privileged EXEC) using reverse Telnet.
Note
Modem Performance Statistics Commands
You can view modem statistics and configure modem events using the Cisco IOS software with the Cisco AS5300 access server. To view performance statistics for the Microcom and MICA modems, enter one or more of the following commands in enable mode (the prompt is displayed as 5300#):
•
•
•
•
•
•
•
•
•
•
•
•
•
To view additional performance statistics for MICA modems only, enter one or more of the following commands in EXEC mode:
•
•
•
•
Note
Managing Modems
This section describes how to manage modems by checking the type of modem connected to the access server, removing inoperable modems from service, and disabling a modem from dial-up service. For details on disabling a modem from dial-up services, see the section, "Troubleshooting Modems," later in this appendix.
Check Modem Type
To check the type of modem connected to the access server and to configure the modem automatically, enter the following command in global configuration mode [the prompt is displayed as 5300(config)#]:
•
The modem is identified each time the line is reset. If a modem cannot be detected, the line continues retrying for 10 seconds. When the modem type is determined, this information remains stored until the modem is recycled or disconnected. Discovery mode is much slower than configuring a line directly.
Each time the modem is reset (every time a chat reset script is executed), a string of commands is sent to the modem, the first one being "return to factory-defaults."
Set Modem Event Buffer
This section applies to Microcom modems only. To configure the size of the history event queue buffer for manageable modems in the access server, enter the following command in global configuration mode [the prompt is displayed as 5300(config)#]:
•
Note
Remove Inoperable Modems from Service
To remove modems from service and indicate them as suspected or proven to be inoperable, enter the following command in line configuration mode [the prompt is displayed as 5300(config-line)#]:
•
If you mark a single modem as inoperable using this command, it appears as Bad—without the asterisk (*)—in the Status column of the show modem command's output for that particular modem. A modem marked inoperable by the modem startup-test command appears as Bad* in the show modem command output for that particular modem. Use the no modem bad command to unmark a modem as Bad* or Bad and restore it for dial-up connection services.
Polling Modems
This section describes polling modems for statistics, including setting the time interval between polls and the maximum number of polling attempts.
Set Polling Attempts
To set the maximum number of polling attempts used to retrieve a local modem's status or statistics, enter the following command in global configuration mode [the prompt is displayed as 5300(config)#]:
•
If the number of attempts to retrieve modem status or statistics exceeds the number you define, the out-of-band port is removed from operation. In this case, you must reset the modem hardware using the clear modem command.
Set Time Interval between Polls
To set the time interval between the polls that are sent to the local modems for reporting modem status and statistics, enter the following command in global configuration mode [the prompt is displayed as 5300(config)#]:
•
Poll for Modem Statistics
To poll for a modem's status and statistics through its out-of-band port, enter the following command in line configuration mode [the prompt is displayed as 5300(config-line)#]:
•
The no modem status-poll command disables status polling through the out-of-band port for a specified modem.
Troubleshooting Modems
This section describes how to perform diagnostic testing on installed modems, test two modems back-to-back, disable modems from service, reset a modem, and debug a modem.
Perform a Modem Startup Test
To perform diagnostic testing on all the installed modems during the system's initial startup or rebooting process, enter the following command in global configuration mode [the prompt is displayed as 5300(config)#]:
•
The results of the modem startup test are displayed in the Status column of the show modem command's output. Modems that pass the diagnostic test are marked as Idle, Busy, Downloading, and Reset. Modems that fail the diagnostic test are marked as Bad*. These modems cannot be used for call connections. Depending on how many modems are installed, this diagnostic test may take from 5 to 15 minutes to complete. Perform additional testing on an inoperative modem by executing the test modem back-to-back command. The no modem startup-test command disables startup testing.
Test Two Modems Back-to-Back
Perform additional testing on a modem suspected of being inoperable by conducting a series of internal back-to-back connections and data transfers between two modems. All modem test connections occur inside the access server. For example, if mobile users cannot dial into modem 2/5 (which is the sixth modem port on the modem board in the second chassis slot), attempt a back-to-back test with modem 2/5 and a known-functioning modem such as modem 2/6.
Enter the following command in enable mode (the prompt is displayed as 5300#) to perform internal back-to-back modem tests between two modems:
•
You might need to enable this command on several different combinations of modems to determine which one is not functioning properly. A pair of operable modems successfully connect and complete transmitting data in both directions. An operable modem and an inoperable modem do not successfully connect with each other.
Hold and Reset a Modem
This section applies to Microcom modems only. To reset and isolate the modem hardware for extensive troubleshooting, enter the following command in line configuration mode [the prompt is displayed as 5300(config-line)#]:
•
Use this command if you are experiencing extreme modem behavior (for example, if the modem is uncontrollably dialing into the network). This command prevents the modem from establishing software relationships such as those created by the test back-to-back modem command and the modem startup-test command. The modem is unusable while the modem hold-reset command is configured.
This command is also used to reset a modem that is frozen in a suspended state. Disable the suspended modem with the modem hold-reset command, and then restart hardware initialization with the no modem hold-reset command. A modem decommissioned by the modem hold-reset command does not accept modem firmware upgrades using the copy modem command.
Disable a Modem from Dial-Up Services
To disable modems from dialing or answering calls, enter one of the following commands in line configuration mode [the prompt is displayed as 5300(config-line)#]:
•
•
The modem busyout command is not executed until the active modem is idle. No active connections are interrupted when you use this command. In contrast, the modem shutdown command immediately terminates all active connections on the specified modem. The resulting modem status for both these commands is the same. Enable the no form of these commands to restore a modem for dial-up services.
You can still configure the following commands on a disabled modem:
•
•
•
•
Debug a Modem
To debug a modem or group of modems, enter the following commands in enable mode (the prompt is displayed as 5300#):
•
•
•
Upgrading Modem Code
Modem code is a generic term applied to a modem code file, which is also called modem code for MICA modems and firmware for Microcom modems.
With new systems, Cisco loads a Cisco IOS software-compatible version of modem code and copies the version to the installed modem modules. A map of the version(s) of modem code copied to the modem RAM for each modem module is stored in nonvolatile random-access memory (NVRAM) so that it is retained over power cycles.
Note
You can acquire new modem code in several ways:
•
•
•
This section describes how to upgrade modem code on your access server modems by:
1
2
3
4
CautionCisco ships the access server with the latest version of modem code installed in the system Flash memory and mapped to the modems. If you choose to use the modem code bundled with your installed Cisco IOS software, you could be reverting to a previous version of modem code. Also note that once you map the bundled modem code (using the copy system:/ucode/filename modem command or, for Cisco IOS releases earlier than 11.3A or 12.0, the copy ios-bundled modem command) to your modems, each time you upgrade the Cisco IOS software, the new bundled modem code is automatically mapped to your modems. See "Displaying Modem Code Versions," later in this appendix, for details on displaying modem code versions mapped to modems, installed in system Flash memory, and bundled with the Cisco IOS software on your access server.
How to Obtain Modem Code
You can obtain modem code in one of two ways:
•
•
Note
Important Modem Upgrade Commands
There are several commands you use to upgrade modem code. For examples on using the commands, see "Upgrading Modem Code from the Cisco CCO TFTP Server," "Upgrading Modem Code from Diskettes," and "Using the Modem Code Bundled with Cisco IOS Software," later in this appendix for details.
•
•
•
Choosing an Update Strategy
Because of multiple versions of modem code and the way Cisco IOS software processes these versions, Cisco suggests that you choose one of the following two strategies:
•
•
CautionCisco ships the access server with the latest version of modem code installed in the system Flash memory and mapped to the modems. If you choose to use the modem code bundled with your installed Cisco IOS software, you could be reverting to a previous version of modem code. Also note that once you map the bundled modem code (using the copy system:/ucode command or, for releases earlier than Cisco IOS release 11.3AA or 12.0, the copy ios-bundled modem command) to your modems, each time you upgrade the Cisco IOS software, the new bundled modem code is automatically mapped to your modems. See "Displaying Modem Code Versions," later in this appendix, for details on displaying modem code versions mapped to modems, installed in system Flash memory, and bundled with the Cisco IOS software on your access server.
To help with the decision, shows a hypothetical release process. Using the modem code bundled with Cisco IOS software is the easier strategy and enables you to take advantage of new modem code whenever you upgrade your Cisco IOS software. You can control the modem code by using the copy command as discussed later.
Figure A-1 Release Timeline for Cisco IOS Software and Modem Code
Modem Code Scenarios
provides scenarios that can occur when you upgrade Cisco IOS software or modem code.
Table A-3 Modem Code Scenarios—Cisco IOS Software or Modem Code Upgrades
1
You receive a new access server from the Cisco factory.
•
2
You update Cisco IOS software, and you decide to use the version of modem code selected by Cisco IOS software.
•
•
3
You update Cisco IOS software, and you decide not to use the modem code selected by Cisco IOS software.
•
•
4
The modems are running a version of modem code from system Flash memory that is different than the version bundled with Cisco IOS software. You decide to revert to the bundled version.
•
5
Cisco releases new modem code, which is a later version than the version currently running on the modems. You decide to use Cisco's newest modem code.3
•
1 To find out the version of modem in your system, use the show modem mapping command. This command displays the versions bundled with Cisco IOS software (copied into Flash memory) and running on the modems.
2 In part, Cisco IOS software bases this decision on the last copy command issued. For more details about mapping, see .
3 Cisco might ship this modem code on a diskette packed with the spare carrier card.
shows a location on the release timeline where updates might take place, and explains the resulting versions of Cisco IOS software and modem code.
Figure A-2 Release Timeline for Cisco IOS Software and Modem Code
Table A-4 Resulting Versions of Cisco IOS Software and Modem Code
EventTime
Cisco IOS Software
and Modem Code1
You upgrade Cisco IOS software to Release B.
•
•
•
•
•
Modem Code Version 2•
Modem Code Version 2•
Modem Code Version 2•
Modem Code Version 12
You upgrade Cisco IOS software to Release C. (Cisco IOS software uses mapping from last copy command at Time 1).1
Cisco IOS Release C
Modem Code Version 1You enter the copy system:/ucode/filename modem command (or, for Cisco IOS releases earlier than 11.3AA or 12.0, the copy ios-bundled modem command).
Cisco IOS Release C
Modem Code Version 33
New Modem Code Version 4 is released, you copy the file to system Flash memory, enter copy flash modem, and specify Modem Code Version 4.
Cisco IOS Release C
Modem Code Version 44
You upgrade Cisco IOS software to Release D.
Cisco IOS Release D
Modem Code Version 4You enter the copy system:/ucode/filename modem command (or, for Cisco IOS releases earlier than 11.3AA or 12.0, the copy ios-bundled modem command).
Cisco IOS Release D
Modem Code Version 3
1 This example assumes the last copy command was copy flash modem, and Modem Code Version 1 was specified.
provides a list of terms and commands and a description of how they are used in the modem code update process.
Table A-5 Modem Code Terminology
Modem code
Modem code on the MICA modems resides in and runs out of modem RAM. Cisco IOS software transfers a version of modem code to modem RAM on each reboot and reload.
System Flash memory can contain several versions of modem code: a version bundled with Cisco IOS software and multiple versions that resulted from previous copy tftp flash commands.
copy system:/ucode/filename command
(or, for Cisco IOS releases earlier than 11.3AA or 12.0, the copy ios-bundled modem command)This command transfers the version of modem code bundled with Cisco IOS software to the modem RAM and maps that version to the modem modules specified by the modem range.
To view a list of microcode filenames, use the command dir system:/ucode.
This command does not affect any existing versions of modem code that reside in system Flash memory.
After one copy system:/ucode/filename modem command, future Cisco IOS upgrades will potentially result in the downloading of new Cisco IOS bundled firmware to the modems. (If the new Cisco IOS image contains the same modem code as the old one, no new code will be downloaded to the modems.)
copy tftp flash filename command
Places a copy of the modem code in system Flash memory.
copy flash modem command
This command transfers the version of modem code in system Flash memory to the modem RAM and maps that version to the modem modules specified by the modem range.
Mapping commands
The copy commands map a specific version of modem code to a group of modem slots/ports. The copy system:/ucode/filename modem command (or, for Cisco IOS releases earlier than 11.3AA or 12.0, the copy ios-bundled modem command) maps the slots/ports to the bundled version, and the copy flash modem command maps the slots/ports to the system Flash version.
Cisco IOS software uses the mapping to determine which version of modem code should be downloaded to the modems. If Cisco IOS software finds no mapping or invalid mapping, it downloads the bundled version.
Although modem ranges are specified on as slot/port, the modem code is downloaded on a per module basis.
The show modem mapping command lists all versions of modem code running on the modem modules, residing in system Flash, and bundled with Cisco IOS software. This will help you decide if you need to update your modem code files.1
1 This command is supported in Cisco IOS Releases 11.2(11)P, 11.3(2)T, and later.
Displaying Modem Code Versions
Use the show modem mapping command to list the versions of modem code running on the modem modules, residing in system Flash memory, and bundled with Cisco IOS software. This will help you decide if you need to change the version running on the modems.
5300# show modem mappingSlot 1 has Mica Carrier card.Modem Firmware FirmwareModule Numbers Rev Filename0 1/0 - 1/5 2.2.3.0 flash:mica-modem-portware.2.2.3.0.bin1 1/6 - 1/11 2.2.3.0 mica-modem-portware.2.2.3.0.bin2 1/12 - 1/17 2.2.3.0 mica-modem-portware.2.2.3.0.bin3 1/18 - 1/23 2.2.3.0 mica-modem-portware.2.2.3.0.bin4 1/24 - 1/29 2.2.3.0 mica-modem-portware.2.2.3.0.binSlot 2 has Mica Carrier card.Modem Firmware FirmwareModule Numbers Rev Filename0 2/0 - 2/5 2.2.3.0 flash:1:mica-modem-portware.2.2.3.0.bin1 2/6 - 2/11 2.2.3.0 mica-modem-portware.2.2.3.0.bin2 2/12 - 2/17 2.2.3.0 mica-modem-portware.2.2.3.0.bin4 2/24 - 2/29 2.2.3.0 mica-modem-portware.2.2.3.0.binIOS Bundled Firmware Information:Mica Boardware Version : 1.0.0.0Mica Portware Version : 2.0.1.7Microcom Firmware Version : 3.1.30Microcom DSP Software Version : 1.01Firmware files on System Flash:Firmware-file Version Firmware-Type============= ======= =============flash:1:mica-modem-portware.2.2.3.0.bin 2.3.0 Mica Portwareflash:2:mcom-modem-firmware.3.1.30.bin 3.1.30 Microcom FirmwareUpgrading Modem Code from the Cisco CCO TFTP Server
Upgrading modem code from the Cisco CCO TFTP server is a two-step process:
•
•
Note
Download Modem Code from the Cisco CCO TFTP Server to a Local TFTP Server
Note
You can download software from the Cisco Systems CCO TFTP server using an Internet browser or using an FTP application. Both procedures are described.
Note
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
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/5300250-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 mcom-modem-code.x.x.x.bin-r--r--r-- 1 ftpadmin ftpint 635 Jul 10 18:08 mcom-modem-code.3.1.30.readme226 Transfer complete.Step 5
ftp> binary200 Type set to I.Step 6
The following example downloads a Microcom modem firmware file:
ftp> get mcom-modem-code.x.x.x.binPORT command successful.Opening BINARY mode data connection for mcom-modem-code.x.x.x.bin (280208 bytes).Transfer complete.local: mcom-modem-code.x.x.x.binremote: mcom-modem-code.x.x.x.bin385503 bytes received in 3.6 seconds (1e+02 Kbytes/s)Step 7
ftp> quitGoodbye.Step 8
server% ls -altotal 596-r--r--r-- 1 280208 Jul 10 18:08 mcom-modem-code.x.x.x.binserver% pwd/auto/tftpbootStep 9
Copy the Modem Code File from Local TFTP Server to Modems
The procedure for copying the modem code file from your local TFTP server to the modems is a two-step process. First, transfer the modem code to the access server's Flash memory. Then, transfer the modem code to the modems.
These two steps are performed only once. After you copy the modem code file into Flash memory for the first time, you should not have to perform these steps again. Because the modem code runs from the modems themselves, the Cisco IOS software automatically copies the modem code to each modem each time the access server power cycles.
Depending on the type of modems that you have installed in your system, the download instructions will vary. Refer to the instructions that best describe your scenario:
•
Upgrading MICA Modem Code
Downloading modem code to MICA modems is a six-step process:
Step 1
Step 2
5300> enablePassword: <password>5300#Step 3
5300# show flashSystem flash directory:File Length Name/status1 4530624 c5300-js-mx[498776 bytes used, 16278440 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)Step 4
5300# copy tftp flashSystem flash directory:File Length Name/status1 4530624 c5300-js-mx[498776 bytes used, 16278440 available, 16777216 total]Address or name of remote host [255.255.255.255]?Source file name? mica-modem-portware.x.x.x.x.binDestination file name [mica-modem-portware.x.x.x.x.bin]?Accessing file 'mica-modem-portware.x.x.x.x.bin' on 255.255.255.255...Loading mica-modem-portware.x.x.x.x.bin from 2.2.0.1 (via Ethernet0): ! [OK]Erase flash device before writing? [confirm] noCopy 'mica-modem-portware.x.x.x.x.bin' from serveras 'mica-modem-portware.x.x.x.x.bin' into Flash WITHOUT erase? [yes/no]yLoading mica-modem-portware.x.x.x.x.bin from 2.2.0.1 (via Ethernet0):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 249108/16278440 bytes]Verifying checksum... OK (0xE009)Flash device copy took 00:00:02 [hh:mm:ss]Step 5
5300# show flashSystem flash directory:File Length Name/status1 4530624 c5300-js-mz2 210104 mica-modem-portware.x.x.x.x.bin[747948 bytes used, 16029268 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)Step 6
5300# copy flash modemModem Numbers (<slot>/<port> | group <number> | all)? allSystem flash directory:File Length Name/status1 4530624 c5300-js-mz2 210104 mica-modem-portware.x.x.x.x.bin[747948 bytes used, 16029268 available, 16777216 total]Name of file to copy? mica-modem-portware.x.x.x.x.binType of service [busyout/reboot] busyoutCopy 'flash:mica-modem-portware.x.x.x.x.bin' from Flash to modems? [yes/no] yes*Nov 30 21:17:43.574: %MODEM-5-DL_START: Modem (2/0) started firmware download*Nov 30 21:17:43.578: %MODEM-5-DL_START: Modem (2/1) started firmware download*Nov 30 21:17:43.578: %MODEM-5-DL_START: Modem (2/2) started firmware download*Nov 30 21:17:43.578: %MODEM-5-DL_START: Modem (2/3) started firmware download...*Nov 30 21:17:53.170: %MODEM-5-DL_GOOD: Modem (2/11) completed firmware download:*Nov 30 21:17:53.598: %MODEM-5-DL_GOOD: Modem (2/12) completed firmware download:*Nov 30 21:17:53.598: %MODEM-5-DL_GOOD: Modem (2/13) completed firmware download:*Nov 30 21:17:53.598: %MODEM-5-DL_GOOD: Modem (2/14) completed firmware download:
Note
For additional information about downloading modem code to modems, refer to the following publications:
•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/hw_inst/spares/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/hw_inst/spares/index.htmUpgrading Microcom Modem Code
Downloading modem code to 56K Microcom modems is a five-step process:
Step 1
5300> enablePassword: <password>5300#Step 2
5300# show flashSystem flash directory:File Length Name/status1 5826036 c5300-js-mz[5826100 bytes used, 10951116 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)5300#Step 3
5300# copy tftp flashSystem flash directory:File Length Name/status1 5826036 c5300-js-mz[5826100 bytes used, 10951116 available, 16777216 total]Address or name of remote host [jurai]? juraiSource file name? mcom-modem-code-3.1.30.binDestination file name [mcom-modem-code-3.1.30.bin]? mcom-modem-code-3.1.30.binAccessing file 'mcom-modem-code-3.1.30.bin' on tftp_server...Loading mcom-modem-code-3.1.30.bin from 223.255.254.254 (via Ethernet0): ! [OK]Erase flash device before writing? [confirm] no%Warning: File not a valid executable for this systemCopy file? [confirm]Copy 'mcom-modem-code-3.1.30.bin' from serveras 'mcom-modem-code-3.1.30.bin' into Flash WITHOUT erase? [yes/no] yesLoading mcom-modem-code-3.1.30.bin from 223.255.254.254 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 377112/10951116 bytes]Verifying checksum... OK (0xB163)Flash device copy took 00:00:10 [hh:mm:ss]Step 4
5300# show flashSystem flash directory:File Length Name/status1 5826036 c5300-js-mz2 377112 mcom-modem-code-3.1.30.bin[6203276 bytes used, 10573940 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)Step 5
5300# copy flash modemModem Numbers (<slot>/<port> | group <number> | all)? allSystem flash directory:File Length Name/status1 5826036 c5300-js-mz2 377112 mcom-modem-code-3.1.30.bin[6203276 bytes used, 10573940 available, 16777216 total]Name of file to copy? mcom-modem-code-3.1.30.binCopy 'mcom-modem-code-3.1.30.bin' from Flash to modems? [yes/no] yes[OK - 377112/278528 bytes]5300#*Mar 3 03:51:17.147: %MODEM-5-DL_START: Modem (1/15) started firmware download*Mar 3 03:52:47.519: %MODEM-5-DL_GOOD: Modem (1/15) completed firmware download: MNPClass10K56flexModemRev3.1.30/85Upgrading Modem Code from Diskettes
This section describes how to copy modem code from diskettes to your hard disk in a PC environment, and then upload the modem code to the modems. The steps are similar if you are using a Macintosh or UNIX workstation.
Note
Copy the Modem Code to Your PC Hard Disk
This section describes how to copy the modem code file to your hard disk in a PC environment. The steps are similar if you are using a Macintosh or a UNIX workstation.
Step 1
Step 2
Step 3
Copy the Modem Code from Your PC to the Modems
If you are using a PC running Microsoft Windows 95, upgrading modem code from a hard drive onto a Cisco AS5300 involves installing a TFTP application on your PC, connecting your PC and the access server, establishing a HyperTerminal session on your PC, pinging the PC and access server to make sure they are talking to each other, and finally, copying the modem code from the PC to the access server. See the following sections for details.
Note
Set Up a TFTP Application on the PC
Step 1
Note
Step 2
Step 3
•
•
•
CautionIf you do not select the c:\tftpboot directory as your TFTP server directory, you will not be able to perform the copy procedure. This also applies if you are using RCP on your system.
Connect your PC and the Access Server
Step 1
Figure A-3 Connecting a PC and an Access Server
Note
Step 2
Step 3
Establish a HyperTerminal Session
Use the steps in this section to establish a HyperTerminal session from your local PC to the Cisco AS5300. You will use the HyperTerminal session to talk to the access server.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
•
•
•
•
•
Step 7
Step 8
Note
Ping the PC and Access Server
Ping the access server and the PC to make sure they are talking to each other and there are no configuration problems on your access server.
Step 1
(a)
(b)
(c)
(d)
Note
Step 2
5300> enablePassword: <password>5300#Step 3
5300# ping 172.16.1.1The access server displays five exclamation points (!) if everything is working and it displays five dots (.) if there is a problem. In the latter case, check the cabling between the router and the PC and check the access server configuration.
Upload Modem Code to the Access Server
The procedure for copying the modem code file from your PC set up as a local TFTP server to the access server system Flash memory is a two-step process:
•
•
Perform these two steps only once. After you copy the modem code file into system Flash memory for the first time, you should not have to perform these steps again. Because the code runs from modem RAM, the Cisco IOS software must automatically copy the modem code to each modem each time the access server power cycles.
The following code examples show a download to MICA modems. Use the same steps to download to Microcom modems.
Step 1
5300# show flashSystem flash directory:File Length Name/status1 4530624 c5300-js-mx[498776 bytes used, 16278440 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)Step 2
5300# copy tftp flashSystem flash directory:File Length Name/status1 4530624 images/c5300-js-mx[498776 bytes used, 16278440 available, 16777216 total]Address or name of remote host [255.255.255.255]? juraiSource file name? mica-modem-portware.x.x.x.x.binDestination file name [mica-modem-portware.x.x.x.x.bin]?Accessing file 'mica-modem-portware.x.x.x.x.bin' on 255.255.255.255...Loading mica-modem-portware.x.x.x.x.bin from 2.2.0.1 (via Ethernet0): ! [OK]Erase flash device before writing? [confirm] noCopy 'mica-modem-portware.x.x.x.x.bin' from serveras 'mica-modem-portware.x.x.x.x.bin' into Flash WITHOUT erase? [yes/no] yesLoading images/mica-modem-portware.x.x.x.x.bin from 2.2.0.1 (via Ethernet0):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 249108/16278440 bytes]Verifying checksum... OK (0xE009)Flash device copy took 00:00:02 [hh:mm:ss]Step 3
5300# show flashSystem flash directory:File Length Name/status1 4530624 c5300-js-mz2 210104 mica-modem-portware.x.x.x.x.bin[747948 bytes used, 16029268 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)Step 4
5300# copy flash modemModem Numbers (<slot>/<port> | group <number> | all)? allSystem flash directory:File Length Name/status1 4530624 c5300-js-mz2 210104 mica-modem-portware.x.x.x.x.bin[747948 bytes used, 16029268 available, 16777216 total]Name of file to copy? mica-modem-portware.x.x.x.x.binType of service [busyout/reboot] busyoutCopy 'flash:mica-modem-portware.x.x.x.x.bin' from Flash to modems? [yes/no] yes*Feb 27 21:17:43.574: %MODEM-5-DL_START: Modem (2/0) started portware download...*Feb 27 21:17:43.598: %MODEM-5-DL_START: Modem (2/13) started portware download*Feb 27 21:17:53.598: %MODEM-5-DL_GOOD: Modem (2/14) completed portware download:
Note
Using the Modem Code Bundled with Cisco IOS Software
Use this procedure to update modem code on the modems in your access server if you decide to use the version of modem code bundled with Cisco IOS software instead of the version already mapped to your modems.
CautionCisco ships the access server with the latest version of modem code installed in the system Flash memory and mapped to the modems. If you choose to use the modem code bundled with your installed Cisco IOS software, you could be reverting to a previous version of modem code. Also note that once you map the bundled modem code (using the copy system:/ucode/filename modem command—or, for Cisco IOS releases earlier than 11.3AA or 12.0, the copy ios-bundled modem command) to your modems, each time you upgrade the Cisco IOS software, the new bundled modem code is automatically mapped to your modems. See "Displaying Modem Code Versions," later in this appendix, for details on displaying modem code versions mapped to modems, installed in system Flash memory, and bundled with the Cisco IOS software on your access server.
To set the modem code mapping to the modem code version bundled with Cisco IOS software, enter the following command:
Step 1
5300> enablePassword: <password>5300#Step 2
5300# copy system:/ucode/microcom_firmware modemModem Numbers (<slot>/<port> | group <number> | all)? 0/0Copy "system:/ucode/microcom_firmware" to modems? [yes/no]yes5300#Mar 11 22:55:38.734: %MODEM-5-DL_START: Modem (0/0) started firmware downloadMar 11 22:57:08.699: %MODEM-5-DL_GOOD: Modem (0/0) completed firmware download:MNPClass10V.90ModemRev5.0.40/85This command does not affect any existing modem code 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 will be deleted, therefore save and restore any important files (for example, the Cisco IOS software image).
Note
