|
|
The AS5300 access servers support MICA or Microcom modem carrier cards. For details on the carrier cards, refer to the Cisco AS5300 Universal Access Server Hardware Installation Guide. For new IOS modem commands, refer to the New and Changed Cisco IOS Commands for the Cisco AS5300 publication, which ships with your access server.
Most of the modem management functions, such as monitoring, managing, polling, and upgrading firmware for modems 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 chapter includes the following sections:
This section describes how to send AT commands to MICA and Microcom (V.34 and 56K) modems.
For a list and description of AT commands, refer to the AT Command Set and Register Summary for MICA Six-Port Modules or to the AT Command Set and Register Summary for V.34 and 56K 12-Port Modules publications. For new IOS modem commands, refer to "New and Changed Cisco IOS Commands for the Cisco AS5300," which ships with your access server.
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.
| Step | Command | Purpose |
|---|---|---|
| 1 | 5300> enable
| Enter privileged EXEC (enable) mode.
Enter the password. You have entered privileged EXEC mode when the |
| 2 | 5300# config term
| Enter global configuration mode.You have entered global configuration mode when the 5300(config)# prompt appears.
|
| 3 | 5300(config)# line 1
| Enter line configuration mode. In this example, line 1 is specified. You have entered line configuration mode when the 5300(config-line)# prompt appears.
|
| 4 | 5300(config-line)# modem at-mode-permit
| Configure a Microcom modem to permit a direct-connect session. |
| 5 | 5300 (config-if)# end
| Return to privileged EXEC mode.
This message is normal and does not indicate an error. |
| 6 | 5300# modem at-mode 1/1
You are now entering AT | 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. |
| 7 | Ctrl-C
5300# | When you are finished entering AT commands, press Ctrl-C to exit AT command mode and return to privileged EXEC mode. |
To send AT commands to a MICA modem involves a reverse Telnet procedure. Table A-2 shows how to enter AT command mode from EXEC mode using reverse Telnet.
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 EXEC mode:
To view additional performance statistics for MICA modems only, enter one or more of the following commands in EXEC mode:
This section describes how to manage modems by removing inoperable modems from service, disable a modem from dial-up service, and set modem recovery times and event buffers. For details on disabling a modem from dial-up services, see the section, Troubleshooting Modems , later in this chapter.
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:
This section applies to Microcom modems only. To set the maximum time of time the call-switching module waits for a local modem to respond to a request before it is considered locked in a suspended state, enter the following command in global configuration mode:
The default is five minutes. After the call-switching module resets a suspended modem, the module recovers to a default call-switching module state.
To remove modems from service and indicate them as suspected or proven to be inoperable, enter the following command in line configuration mode:
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.
This section describes polling modems for statistics, including setting the time interval between polls and the maximum number of 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:
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.
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:
To poll for a modem's status and statistics through its out-of-band port, enter the following command in line configuration mode:
The no modem status-poll command disables status polling through the out-of-band port for a specified modem.
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.
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 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.
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 EXEC mode 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.
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:
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.
To disable modems from dialing or answering calls, enter one of the following commands in line configuration mode:
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:
To debug a modem or group of modems, enter the following commands in EXEC mode:
Cisco Systems posts new versions of modem firmware to its TFTP server. The new firmware versions contain bug fixes or new modem features, which improve your system's overall modem performance. You must be a Cisco Connection Online (CCO) registered user to access the files.
To download firmware, use a PC or UNIX work station to access Cisco's CCO TFTP server and download the new firmware to your desktop. Then, transfer the firmware to a TFTP server on your LAN. (You might be able to set up your workstation as a TFTP server.) Next, log on to the access server or router to which you want to upgrade modem firmware and enter the Cisco IOS copy command to transfer a copy of the file to the modems.
Perform these two steps to download modem firmware from Cisco System's CCO TFTP server to your integrated modems:
Step 1--Download the Modem Firmware from CCO to Your Workstation
Step 2--Copy Modem Firmware from a Local TFTP Server to an Access Server
Choose one of these methods to download firmware files:
You must be a registered Cisco user to log into Cisco's Software Center.
Step 1 Launch an Internet browser.
Step 2 Bring up Cisco System's Software Center home page at following URL (this is subject to change without notice):
Step 3 Click Access Products to open the Access Products window.
Step 4 Find the firmware you want and download it to your local workstation. For example, to download firmware for the Cisco AS5300, click Cisco AS5300 Series Software.
Step 5 Click Download Microcom Modem Firmware or Download MICA Modem Firmware.
Step 6 Select the version of firmware you want to download.
Step 7 Follow the remaining download instructions.
Step 8 When the firmware is downloaded to your workstation, transfer the file to a TFTP server somewhere in your LAN using a terminal emulation software application.
Take the following steps to download firmware files from Cisco's TFTP server using an FTP client application:
Step 1 Log in to Cisco System's CCO FTP server called cco.cisco.com:
ftp cco.cisco.com
Step 2 Enter your CCO registered username and password (for example, harry and letmein):
harry
letmein
Step 3 Specify the directory path that holds the modem firmware you want to download. For example, the directory path for the Cisco AS5300 56-kpbs modem firmware is /cisco/access/5300/56k:
cd /cisco/access/5300/56k
Step 4 View the contents of the directory with the ls command:
ls
Step 5 Specify a binary image transfer:
binary
Step 6 Copy the modem firmware files from the server to your local environment with the get command.
The following example downloads the modem firmware file:
get mcom-modem-firmware.2.2.8.binStep 7 Quit your terminal session:
quit
Step 8 Verify you successfully transferred the files to your local directory:
ls -al
pwd
Step 9 Transfer these files to a local TFTP or rcp server that your access server or router can access.
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:
Downloading firmware to 56K and MICA modems is a two-step process:
Step 1 Download the firmware to the access server Flash memory by entering the copy tftp flash command in EXEC mode. After you enter the command, you are prompted for the download destination and the remote host name as requested by the system software.
The following example downloads firmware to the access server Flash memory for both 56K and MICA modems:
Step 2 Copy the firmware from the flash memory to the modems by entering the copy flash modem command.
The following example downloads new firmware from the Cisco AS5300's Flash memory to MICA modems:
The following example downloads new firmware from the Cisco AS5300's Flash memory to a 56K Microcom modem:
If you already have a version of modem firmware in the Flash memory on your access server, when you upgrade a Cisco IOS version that includes new modem firmware, only the Cisco IOS version is updated. The current version of modem firmware in the Flash memory is kept and not overwritten by the new version of modem firmware.
You can fix this in one of two ways:
5300# copy ios-bundled modem
Step 1 Use the copy tftp modem command to copy the firmware file from your TFTP server to all the modems on your access server.
The following example copies the modem firmware file from your TFTP server Modem_Server to all the V.34 modems installed in the Cisco AS5300 access server:
copy tftp modem
Modem Firmware Download Modem Numbers? all
Modem_Server
as5300/elem/mcom-modem-firmware.2.2.8.bin
mcom-modem-firmware.2.2.8.bin on Modem_Server...
mcom-modem-firmware.2.2.8.bin .from 223.255.254.254 (via Ethernet0): ! [OK]
mcom-modem-firmware.2.2.8.bin from 223.255.254.254 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|