Upgrading Modem Firmware

Cisco regularly enhances modem DSP code to improve modem performance. To obtain the latest DSP code, upgrade the NAS modem firmware.

Figure 6-1 summarizes the firmware upgrade procedure.

Figure 6-1 Modem Firmware Download Operation Example

Figure 6-1 Modem Firmware Download Operation Example

Mica-modem-pw.x.x.x.x. (portware file)

[2 Map the portware to the modems.

Mica-modem-pw.x.x.x.x. (portware file)

Download the portware from CCO to a TFTP server or directly into the NAS.

[2 Map the portware to the modems.

Internal view of a NAS

Step 1 Read the latest modem release notes about modem and firmware information on CCO. Understand the latest enhancements and bug fixes before you download code. Refer to the following URL for the latest release notes:

http://www.cisco.com/univercd/cc/td/doc/product/access/fwpwinfo/index.htm

Step 2 Download the latest firmware from CCO to the NAS Flash or bootFlash memory. Depending on which Cisco IOS you are running, there are two ways you can get the latest firmware from CCO into the NAS Flash or bootFlash. Table 6-2 describes these two methods.

Table 6-2 Firmware Copy Commands

Cisco IOS

Command

Purpose

12.0T and later

copy ftp command

Copy a file directly from CCO into Flash,

without staging it at a local TFTP server.

11.3 and later

copy tftp: {flash: | bootflash:}

Copy from a TFTP server.

The following example uses the copy ftp command. The file mica-modem-pw.2.7.1.0.bin is copied from ftp.cisco.com to the bootFlash. Be sure to specify your own CCO username and password in the command line (as indicated in the example).

5300-NAS#ping ftp.cisco.com

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.31.7.171, timeout is 2 seconds:

Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms 53 0 0-NAS#

53 0 0-NAS#copy ftp://CCOUSERNAME:[email protected]/cisco/access/modems/mica/ mica-modem-pw.2.7.1.0.bin bootflash:

Destination filename [mica-modem-pw.2.7.1.0.bin]? <cr> Accessing ftp://

CCOUSERNAME:[email protected]ftp.cisco.com/cisco/access/modems/mica/mica-modem-pw.2.7.1.0.bin. ..Translating "ftp.cisco.com"...domain server (171.70.24.56) [OK]

Erase bootflash: before copying? [confirm] n

Loading cisco/access/modems/mica/mica-modem-pw.2.7.1.0.bin

[OK - 392241/1024 bytes] Verifying checksum... OK (0x6638)

392241 bytes copied in 5.940 secs (78448 bytes/sec) 53 0 0-NAS#

Step 3 Verify that the new firmware is in Flash or bootFlash. In this example, the unbundled firmware file is mica-modem-pw.2.7.1.0.bin.

5300-NAS#dir Directory of flash:

flash:/

4583276 4675992 392241

5947548 4339

<no date> c5300-js-mz.112-18.P.bin

<no date> c5300-is-mz.120-4.XI1

<no date> startup-config.12.0(4)XI1

16777216 bytes total (1173496 bytes free)

Step 4 (Optional) Enable the debug modem maintenance command to watch the modem mapping operation take place:

53 0 0-NAS#debug modem maintenance

Modem Maintenance debugging is on 53 0 0-NAS#show debug Modem Management:

Modem Maintenance debugging is on 53 0 0-NAS#terminal monitor

Step 5 Map the new firmware to the modems.

For MICA modems, firmware is mapped to entire modem modules (6 or 12 modem-module boundaries; not individual modems). For Microcom modems, firmware is mapped to one or more individual modems. The rule requiring that all modems in a MICA module run the same code is an architectural requirement.

Depending on which Cisco IOS Release is loaded in the NAS, there are two commands that you can use. Table 6-3 describes these two commands.

Table 6-3 Modem Mapping Commands

Cisco IOS

Command

Notes

12.0(5)T and later

spe

An SPE unit is defined as the smallest software downloadable unit. For Microcom, an SPE is an individual modem.

For MICA, an SPE is either 6 or 12 modems, depending on whether the MICA module is single or double density.

Before Release 12.0(5)T

copy source modem

Replace the source variable with either flash or bootflash.

The following MICA example uses the spe command. The numbers 1/0 1/7 refer to modem module numbers 0 through 7 in slot 1. These numbers do not refer to specific modem numbers (for example, slot/port for Microcom modems). In this example, 48 modems are upgraded (8 SPE x 6 modems per module = 48 modems).

53 0 0-NAS#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

5300-NAS(config)#spe 1/0 1/7

53 0 0-NAS(config-spe)#firmware location flash:mica-modem-pw.2.7.1.0.bin

5300-

NAS(config-

spe)#

*Jan

23

11

14

48

.702

%MODEM-

5

-DL_

START:

Modem

(1/0)

started firmware download

*Jan

23

11

14

48

.702

%MODEM-

5

-DL_

START:

Modem

(1/1)

started firmware download

*Jan

23

11

14

48

.702

%MODEM-

5

-DL_

START:

Modem

(1/2)

started firmware download

*Jan

23

11

14

48

.702

%MODEM-

5

-DL_

START:

Modem

(1/3)

started firmware download

*Jan

23

11

14

48

.702

%MODEM-

5

-DL_

START:

Modem

(1/4)

started firmware download

*Jan

23

11

14

48

.702

%MODEM-

5

-DL_

START:

Modem

(1/5)

started firmware download

*Jan

23

11

15

03

.042

%MODEM-

5

-DL_

GOOD:

Modem

(1/0)

completed firmware download:

*Jan

23

11

15

03

.042

%MODEM-

5

-DL_

GOOD:

Modem

(1/1)

completed firmware download:

*Jan

23

11

15

03

.042

%MODEM-

5

-DL_

GOOD:

Modem

(1/2)

completed firmware download:

*Jan

23

11

15

03

.042

%MODEM-

5

-DL_

GOOD:

Modem

(1/3)

completed firmware download:

*Jan

23

11

15

03

.042

%MODEM-

5

-DL_

GOOD:

Modem

(1/4)

completed firmware download:

*Jan

23

11

15

03

.042

%MODEM-

5

-DL_

GOOD:

Modem

(1/5)

completed firmware download:

*Jan

23

11

15

03

.046

%MODEM-

5

-DL_

START:

Modem

(1/6)

started firmware download

*Jan

23

11

15

03

.046

%MODEM-

5

-DL_

START:

Modem

(1/7)

started firmware download

*Jan

23

11

15

03

.046

%MODEM-

5

-DL_

START:

Modem

(1/8)

started firmware download

*Jan

23

11

15

03

.050

%MODEM-

5

-DL_

START:

Modem

(1/9)

started firmware download

*Jan

23

11

15

03

.050

%MODEM-

5

-DL_

START:

Modem

(1/10) started firmware download

*Jan

23

11

15

03

.050

%MODEM-

5

-DL_

START:

Modem

(1/11) started firmware download

*Jan

23

11

15

17

.394

%MODEM-

5

-DL_

GOOD:

Modem

(1/6)

completed firmware download:

*Jan

23

11

15

17

.394

%MODEM-

5

-DL_

GOOD:

Modem

(1/7)

completed firmware download:

*Jan

23

11

15

17

.394

%MODEM-

5

-DL_

GOOD:

Modem

(1/8)

completed firmware download:

*Jan

23

11

15

17

.394

%MODEM-

5

-DL_

GOOD:

Modem

(1/9)

completed firmware download:

*Jan

23

11

15

17

.394

%MODEM-

5

-DL_

GOOD:

Modem

(1/10)

completed firmware download

*Jan

23

11

15

17

.394

%MODEM-

5

-DL_

GOOD:

Modem

(1/11)

completed firmware download

*Jan

23

11

16

43

.482

%MODEM-

5

-DL_

GOOD:

Modem

(1/47)

completed firmware download

In this example, the specified SPE range gets updated with new firmware in batches of six modems at a time. If double density modems were installed, batches of 12 modems would be updated.

Note below that the SPE range 1/0 to 1/7 is mapped to firmware 2.7.1.0. However, SPE range 2/0 through 2/7 is still mapped to the firmware that is bundled with the Cisco IOS.

firmware location flash:mica-modem-pw.2.7.1.0.bin spe 2/0 2/7

firmware location system:/ucode/mica_port_firmware

The following MICA example is for the copy source modem command. Unlike the spe command, the numbers 1/0-1/5 refer to specific modem numbers (slot/port). The busyout keyword will gracefully busy out the modems if the modems are off hook.

cisco#copy bootflash modem

Source filename []? mica-modem-pw.2.6.2.0.bin

Modem Numbers (<slot>/<port> | group <number> | all)? 1/0-1/5 Type of service [busyout/reboot/recovery] busyout

Allow copy of "bootflash:mica-modem-pw.2.6.2.0.bin" to modems? [yes/no]yes

cisco#

2dO5h

%MODEM-

5

-DL_

START:

Modem

(1/O)

started firmware download

2dO5h

%MODEM-

5

-DL_

START:

Modem

(1/1)

started firmware download

2dO5h

%MODEM-

5

-DL_

START:

Modem

(1/2)

started firmware download

2dO5h

%MODEM-

5

-DL_

START:

Modem

(1/3)

started firmware download

2dO5h

%MODEM-

5

-DL_

START:

Modem

(1/4)

started firmware download

2dO5h

%MODEM-

5

-DL_

START:

Modem

(1/5)

started firmware download

2dO5h

%MODEM-

5

-DL_

GOOD:

Modem

(1/O)

completed firmware download

2dO5h

%MODEM-

5

-DL_

GOOD:

Modem

(1/1)

completed firmware download

2dO5h

%MODEM-

5

-DL_

GOOD:

Modem

(1/2)

completed firmware download

2dO5h

%MODEM-

5

-DL_

GOOD:

Modem

(1/3)

completed firmware download

2dO5h

%MODEM-

5

-DL_

GOOD:

Modem

(1/4)

completed firmware download

2dO5h

%MODEM-

5

-DL_

GOOD:

Modem

(1/5)

completed firmware download

Step 6 Verify that the new firmware was successfully mapped to the modems. In the following example:

• SPE 1/1 applies to modem 1/6 through 1/11, and so on.

• The MICA modules 0 through 7 in slot 1 are running version 2.7.1.0 (not 2.6.2.0).

• All the modems in slot 2 are still running version 2.6.2.0, which is bundled into the Cisco IOS image (see the field IOS-Default).

53 0 0-NAS#show modem map

Slot 1 has Mica Carrier card.

Modem

Firmware

Firmware

Module Numbers

Rev

Filename

O

1/O

- 1/5

2.

7.

1

.O

flash:

mica-

modem-

-pw.

2.

7.

1.

O.

bin

1

1/6

- 1/11

2.

7.

1

.O

flash:

mica-

modem-

-pw.

2.

7.

1.

O.

bin

2

1/12

- 1/17

2.

7.

1

.O

flash:

mica-

modem-

-pw.

2.

7.

1.

O.

bin

3

1/18

- 1/23

2.

7.

1

.O

flash:

mica-

modem-

-pw.

2.

7.

1.

O.

bin

4

1/24

- 1/29

2.

7.

1

.O

flash:

mica-

modem-

-pw.

2.

7.

1.

O.

bin

5

1/3O

- 1/35

2.

7.

1

.O

flash:

mica-

modem-

-pw.

2.

7.

1.

O.

bin

6

1/36

- 1/41

2.

7.

1

.O

flash:

mica-

modem-

-pw.

2.

7.

1.

O.

bin

7

1/42

- 1/47

2.

7.

1

.O

flash:

mica-

modem-

-pw.

2.

7.

1.

O.

bin

Slot

2 has

Mica Carrier card.

M Configuring Modems Using Modem Autoconfigure

Modem

Firmware

Firmware

idule Numbers

Rev

Filename

0

2/0 -

2/5

2.

6.

2.

0

IOS-Default

1

2/6 -

2/11

2.

6.

2.

0

IOS-Default

2

2/12 -

2/17

2.

6.

2.

0

IOS-Default

3

2/18 -

2/23

2.

6.

2.

0

IOS-Default

4

2/24 -

2/29

2.

6.

2.

0

IOS-Default

5

2/30 -

2/35

2.

6.

2.

0

IOS-Default

6

2/36 -

2/41

2.

6.

2.

0

IOS-Default

7

2/42 -

2/47

2.

6.

2.

0

IOS-Default

Firmware-file

Firmware-file system:/ucode/mica_board_firmware system:/ucode/mica_port_firmware system:/ucode/microcom_firmware bootflash:mica-modem-pw.2.6.2.0.bin flash:mica-modem-pw.2.7.1.0.bin

Version Firmware-Type

2.0.2.0 Mica Boardware

2.6.2.0 Mica Portware

5.1.20 Microcom F/W and DSP

2.6.2.0 Mica Portware

2.7.1.0 Mica Portware

Was this article helpful?

0 0

Post a comment