Cisco AS5300 Module Installation Guide
Microcom Modem Cards
Table of Contents
Microcom Modem Cards
Cisco IOS Software Requirements
Installing Modem Modules
Upgrading Modem Code
Deciding on an Update StrategyConfiguring Modem Modules
Modem Code Scenarios
Using the Modem Code from an External File
Downloading Modem Code to a TFTP ServerUsing the Modem Code Bundled with Cisco IOS Software
Copying the Modem Code File from a Local TFTP Server to the Modems
Download Failure Reasons and Recommended Actions
Monitoring, Polling, and Troubleshooting Modems
This chapter describes the analog Microcom modem modules and cards used in the Cisco AS5300 universal access servers. This chapter includes the following sections:
You can install up to two Microcom cards (see Figure 4-1) in any two slots of the access server chassis. Each Microcom card includes two slots in which you can install any combination of 12-port modem modules, as described below.
Figure 4-1: Microcom Carrier Card
The modules connect through the Microcom card and the system backplane to a Quad or Octal T1/PRI or E1/PRI card installed in the access server chassis. Data is transmitted or received on T1 or E1 lines connected to the Quad or Octal T1/PRI or E1/PRI card and then routed to the modules installed in the Microcom card.
The access server supports any combination of the following 12-port modules:
Note The 12-port modem modules can also be used in the Cisco AS5200 universal access server. The modular design of the Cisco AS5300 universal access server allows you to use those cards you may have already purchased for use with the Cisco AS5200 universal access server.
The 12-port modem modules are not included unless specified in your order. You can order the modem modules separately.
You must install the 12-port modules in the Microcom carrier card. The 12-port modules cannot be used as standalone cards and they cannot be installed in MICA carrier cards.
Figure 4-2: V.34 12-Port Modem Module
Figure 4-3: 56K 12-Port Modem Module
The 56K modem module uses Rockwell's K56flex technology. The modem can send data at up to 56 kbps and receive data at up to 33.6 kbps. However, the actual speed that you can achieve with the modem depends on the condition of your local telephone network.
Note Actual speeds vary depending on line conditions. Due to FCC limitations, speeds in the U.S. are less than 56 kbps.
The following requirements apply to using the 56K 12-port modem module:
The modem modules require Cisco IOS Release 11.2 (9)XA, 11.2 (10)P, or higher.
Note To use the modems, you must first install the modem code file into the Cisco AS5300 system Flash memory.
To install the modem module, refer to Figure 4-5 and take these steps:
Step 1 Attach an ESD-preventive wrist strap.
Step 2 Power OFF the access server. If using a DC-powered unit, refer to Figure 4-4 and complete steps a to d.
Figure 4-4: DC Power Supply Connections
(a) Loosen the three locking screws for the negative, positive, and ground connectors on the DC power supply terminal block
(b) Remove the -48 VDC wire from the terminal block negative connector (-) .
(c) Remove the +48 VDC wire from the terminal block positive connector (+) .
(d) Remove the safety ground (green wire) from the terminal block ground connector.
Step 3 Remove all interface cables from the back panel of the access server.
Step 4 Remove the blank cover or modem module installed in the carrier card.
Note If the carrier card is already installed in the access server, you can install modem modules in the card without removing the carrier card from the access server chassis.
Step 5 Remove the modem module from the ESD-preventive shipping material.
Step 6 Slide the modem module into the card slot until it is seated completely.
Step 7 Tighten the two captive screws on the modem module to secure it to the card.
Figure 4-5: 56K 12-Port Modem Module Installation
Step 8 Reconnect the AC power cord. Or, if using DC power, refer to Figure 4-6, and then complete steps a to d.
Figure 4-6: DC Power Supply Connections
(a) Insert the safety ground (green wire) into the terminal block ground connector and tighten the locking screw. Ensure that no bare wire is exposed.
(b) Insert the +48 VDC wire into the terminal block positive connector (+) and tighten the locking screw. Ensure that no bare wire is exposed.
(c) Insert the -48 VDC wire into the terminal block negative connector (-) and tighten the locking screw. Ensure that no bare wire is exposed.
(d) Make sure the power supply cord is secured to the cable strain-relief clamps on the DC power supply with cable ties.
Step 9 Power ON the access server.
Step 10 Proceed to the following section, "Upgrading Modem Code."
The 12-port modem module uses the following modem code images in a single-file format:
Modem code also resides on the access server: one version is bundled with Cisco IOS software, and another version can exist in system Flash memory. This modem code residing in the access server is a single file comprised of the modem firmware image combined with the DSP software image.
After power on, Cisco IOS software uses its bundled modem code file or the existing modem code file in system Flash memory to automatically update the DSP software and modem firmware on a specific modem.
When you install a new 12-port module, Cisco IOS software examines the following versions of modem code:
Then, Cisco IOS software ensures that the system uses matching DSP software and modem firmwarewhich may include overriding the current firmware on the modem. In some circumstances you may decide to manually update the modem code after the automatic download process completes.
Because of the possibility of multiple versions of modem code and the way Cisco IOS software process these versions, Cisco suggests that you decide between the following two strategies:
To help with the decision, Figure 4-7 shows a hypothetical release process. We recommend that you use the modem code bundled with Cisco IOS software because it is the easier strategy and enables you to take advantage of new modem code whenever you upgrade your Cisco IOS software. You can also control the modem code by reverting to previous versions by using the copy command as discussed later.
Figure 4-7: Release Timeline for Cisco IOS Software and Modem Code
Table 4-1: Modem Code ScenariosHardware Installation
Table 4-2: Modem Code ScenariosCisco IOS Software or Modem Code Upgrades
Figure 4-8: Release Timeline for Cisco IOS Software and Modem Code
Table 4-3: Resulting Versions of Cisco IOS Software and Modem Code
Table 4-4 provides a list of terms and commands and a description of how they are used in the modem code update process.
Table 4-4: Modem Code Terminology
Use the procedures in this section to transfer modem code from Cisco Connection Online (CCO) to the integrated modems on the 12-port module. The procedure consists of the following tasks:
You can download the single file (mcom-modem-code-x.x.x.bin) to a TFTP server on your LAN two ways:
Download Modem Code to a TFTP ServerMethod 1, Use an Internet Browser
Log in to Cisco's Software Center at the following URL to download the modem code file:
You must log in as a Cisco registered user. (If you are not a registered user, note that Cisco provides modem code on a disk when are updates are necessary. This disk is shipped with the 12-port module.)
After downloading to your desktop computer, you must transfer it to a TFTP server on your network using an FTP application.
Alternatively, you can access Cisco at http://www.cisco.com, login, and take the following path to the file:
Download Modem Code to a TFTP Server Method 2, Use a Traditional FTP Application
Take the following steps to download the modem code file from Cisco's FTP server using an FTP client application. These steps assume that you want to download both the modem firmware and the DSP software.
Note The directory path leading to the 56K images on cco.cisco.com is subject to change without notice. If you cannot access the files using an FTP application, use Download Method 1 earlier in this section.
Step 1 Log in to Cisco System's CCO FTP server, which is called cco.cisco.com:
terminal> ftp cco.cisco.com Connected to cio-sys.cisco.com. 220- 220- Cisco Connection Online | | Cisco Systems, Inc. 220- Email: firstname.lastname@example.org ||| ||| 170 West Tasman Drive 220- Phone: +1.800.553.2447 .:|||||:..:|||||:. San Jose, CA 95134 220- 220- NOTE: As of February 1, 1997 ftp.cisco.com will now point to this 220- service. Please be advised. To use the former ftp.cisco.com after 220- February 1, connect to ftpeng.cisco.com 220- 220- You may login with: 220- + Your CCO username and password, or 220- + A special access code followed by your e-mail address, or 220- + "anonymous" followed by your e-mail address for guest access. 220- 220- 220 cio-sys FTP server (CIOESD #103 Sun Dec 15 14:43:43 PST 1996) ready.
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 with 230-# 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 (-) 230- as the first character of your password. This will turn off a feature 230- that may be confusing your ftp client program. 230- Please send any questions, comments, or problem reports about this 230- server to email@example.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 at 230- 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- 230- 230- Please read the file README 230- it was last modified on Sat Feb 1 12:49:31 1997 - 163 days ago 230- User harry logged in. Access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files.
Step 3 Specify the directory that holds the Modem Code file, which is /cisco/access/5300:
ftp> cd /cisco/access/5300 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 View the contents of the directory with the ls command:
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 Aug 23 18:11 . drwxr-sr-t 19 ftpadmin ftpcio 512 Jul 18 10:26 .. lrwxrwxrwx 1 root 3 10 Aug 9 1996 README -> README.txt -rw-rw-r-- 1 root ftpcio 2304 Nov 8:07 README.txt -r--r--r-- 1 ftpadmin ftpint 377112 Jul 10 18:08 mcom-modem-code.3.1.30.bin -r--r--r-- 1 ftpadmin ftpint 635 Jul 10 18:08 mcom-modem-code.3.1.30.readme 226 Transfer complete.
Step 5 Specify a binary image transfer:
ftp> binary 200 Type set to I.
Step 6 Copy the modem code file from the server to your local environment with the get command. The filename is mcom-modem-code-3.1.30.bin.
The following example downloads the modem code file:
ftp> get mcom-modem-code-3.1.30.bin PORT command successful. Opening BINARY mode data connection for mcom-modem-code-3.1.30.bin (377112 bytes). Transfer complete. local: mcom-modem-code-3.1.30.bin remote: mcom-modem-code-3.1.30.bin 385503 bytes received in 3.6 seconds (1e+02 Kbytes/s)
Step 7 Quit your terminal session:
ftp> quit Goodbye.
Step 8 Verify that you successfully transferred the modem code file to your local directory:
server% ls -al total 596 -r--r--r-- 1 377112 Jul 10 18:08 mcom-modem-code-3.1.30.bin server% pwd /auto/tftpboot
Step 9 If you have not already done so, transfer this file to a local TFTP server that your Cisco AS5300 can access.
Note In some cases, Cisco ships modem software on a disk. To use this software, first upload the software to your TFTP server, then download the software to the modem using the method described in the next section "Copying the Modem Code File from a Local TFTP Server to the Modems."
If you loaded Cisco IOS software from a feature pack CD using Router Software Loader (RSL), note that the CD contains a TFTP server program for PCs using Windows 95. Run the server program from the directory where you installed the RSL program. Remember to set the Root directory to the directory where the Cisco AS5300 modem code is located. RSL is also available on CCO in the software library in the Access Products section.
The procedure for copying the modem code file from your local TFTP server to the access server system Flash memory is a two-step process. First, transfer the code to the access server. Then, transfer the code to the modems.
These two steps are performed only once. After you copy the modem code file into system Flash memory for the first time and map that file to a specific modem using the copy flash modem command, you do not have to perform these steps again. Because the DSP software runs from modem RAM, the Cisco IOS software must automatically copy the DSP software to each modem each time the access server power cycles.
Note A list of download failure reasons and recommended actions is provided in Table 4-5.
Step 1 Copy the modem code file from your TFTP server to the access server's system Flash memory using the copy tftp flash command. Cisco IOS software prompts you with a sequence of questions such as name/address of the TFTP server and the filename to be copied. Answer all of the prompts according to your configuration. The following example shows a typical download.
5300# copy tftp flash System flash directory: File Length Name/status 1 37712 mcom-modem-code.3.1.30.bin [4195272 bytes used, 12581944 available, 16777216 total] Address or name of remote host [255.255.255.255]? modem_server Source file name? as5300/mcom-modem-code.3.1.30.bin Destination file name [as5300/mcom-modem-code.3.1.30.bin]? as5300/mcom-modem-code.3.1.30.bin Accessing file 'as5300/mcom-modem-code.3.1.30.bin' on modem_server... Loading as5300/mcom-modem-code.3.1.30.bin from 126.96.36.199 (via Ethernet0): ! [OK] Erase flash device before writing? [confirm] no Copy 'as5300/mcom-modem-code.3.1.30.bin' from server as 'mcom-modem-code.3.1.30.bin' into Flash WITHOUT erase? [yes/no] yes Loading as5300/mcom-modem-code.3.1.30.bin from 188.8.131.52 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 282106/557056 bytes] Verifying checksum... OK (0xB163) Flash device copy took 00:00:04 [hh:mm:ss]
Step 2 Copy the modem code file to the modems by entering the copy flash modem Privileged EXEC command.
5300# copy flash modem Modem Numbers (<slot>/<port> | group <number> | all)? 1/0 System flash directory: File Length Name/status 1 5424872 c5200-js-mz 2 377112 mcom-modem-code-3.1.30.bin [5801984 bytes used, 10975232 available, 16777216 total] Name of file to copy? mcom-modem-code-3.1.30.bin Copy 'mcom-modem-code-3.1.30.bin' from Flash to modems? [yes/no]yes [OK - 377112/278528 bytes] 5300# *Mar 1 20:21:55: %MODEM-5-DL_START: Modem (1/0) started firmware download *Mar 1 20:23:24: %MODEM-5-DL_GOOD: Modem (1/0) completed firmware download: MNPClass10K56flexModemRev3.1.30/85
Note On the display, notice that the command copies the concatenated modem code file, mcom-modem-code-3.1.30.bin. When the DSP software and modem firmware download is complete, the display reports the modem firmware component, MNPClass10K56flexModemRev3.1.30/85, was downloaded to the modems.
If you want to verify that the DSP software and modem firmware copied to the modems, use the show modem version command. In this example, modems 2/12 through 2/23 are loaded with the 56K modem controller firmware and DSP software:
5300# show modem version Modem module Firmware Boot DSP Mdm Number Rev Rev Rev 2/0 0 2.2(8) 1.0(5) 2/1 0 2.2(8) 1.0(5) 2/2 0 2.2(7) 1.0(5) 2/3 0 2.2(7) 1.0(5) 2/4 0 2.2(7) 1.0(5) 2/5 0 2.2(7) 1.0(5) 2/6 0 2.2(7) 1.0(5) 2/7 0 2.2(7) 1.0(5) 2/8 0 2.2(7) 1.0(5) 2/9 0 2.2(7) 1.0(5) 2/10 0 2.2(7) 1.0(5) 2/11 0 2.2(7) 1.0(5) 2/12 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/13 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/14 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/15 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/16 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/17 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/18 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/19 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/20 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/21 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/22 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) 2/23 1 3.1(30) 3.0(4) 1.1(0)/1.1(0) Modem board HW version info: Slot 2: Carrier card: hw version= 8, number_of_ports= 24, max_modules= 2, max_oob_ports= 2 Modem Module 0: number_of_modems= 12, option_bits= 1, rev_num= 03.00, vendor_model_number= 01, vendor_banner= Microcom MNP10 V34 Modem Modem Module 1: number_of_modems= 12, option_bits= 1, rev_num= 03.00, vendor_model_number= 02, vendor_banner= Microcom MNP10 K56 Modem
Now the modems are equipped with code. The modems are configured to transmit at speeds up to 56 kbps. Each time the access server is power cycled, Cisco IOS software automatically loads the modems with the modem code in system Flash memory. If you erase the modem code file from system Flash memory, the Cisco IOS default modem code (that is, the bundled modem code) will be automatically downloaded to the modem.
If you already have a version of modem code in the Flash memory on your access server, and you upgrade to a Cisco IOS release that includes newer modem firmware, only the modems that are mapped to the bundled Cisco IOS version are updated. In order to set the modem firmware mapping to the firmware version bundled with Cisco IOS software, enter the following command:
5300# copy system:/ucode/filename modem
Note For Cisco IOS releases earlier than 11.3AA or 12.0, use the copy ios-bundled modem command.
Note This 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).
As a result of the copy system:/ucode/filename modem command, future Cisco IOS upgrades will potentially result in the mapping 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.)
Note To determine the version of modem code bundled with your Cisco IOS software, refer to the Cisco IOS release notes shipped with the chassis.
Table 4-5: Download Failure Reasons and Recommended Actions
This section lists the procedures you need to complete the following configuration tasks to configure the modem modules:
1. Configure the asynchronous group interface
2. Configure the controller
3. Configure the modems
4. Configure the serial interface
See the Cisco AS5300 Universal Access Server Software Configuration Guide for details. You can find the most up-to-date version of this manual online from either CCO or the CD-ROM.
See the Cisco AS5300 Universal Access Server Software Configuration Guide publication for details.