Downloads |
Table Of Contents
SPE and Firmware Download Enhancements
Related Features and Technologies
Configuring for the spe Command
spe Command Firmware Download for the Cisco AS5200 and AS5300
Microcom spe Command Firmware Download for the Cisco AS5200 and AS5300
SPE and Firmware Download Enhancements
This document contains the following sections:
Feature Overview
The spe configuration command enables you to download firmware into your modems. When the access server is booted, the spe command controls the location from where the firmware image is downloaded to the service processing element (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.
Benefits
The spe command provides the capability to download firmware into your modems. The current setting of the SPE firmware location value is visible through the normal running-config or startup-config.
Restrictions
This command is available in Cisco IOS Release 12.0(4)XI1 or later releases.
Related Features and Technologies
•
SPE Manager
Related Documents
•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5200/52swcfg2/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/53swcf2/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/58sw_icg/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12supdoc/dsqcg3/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/mod_info/53fw_pw/53micaa/rnv110bp.htm#xtocid214860•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/mod_info/53fw_pw/5356ka/mcv9_fw3.htmSupported Platforms
These platforms support the spe command in Network Access Server (NAS) stand-alone and group scenarios for Cisco IOS Release 12.0(5)T and later releases:
•
•
•
Supported MIBs and RFCs
MIBs
•
RFCs
•
Prerequisites
•
•
Router# dir system:/ucodeDirectory of system:/ucode/14 -r-- 516060 <no date> mica_board_firmware15 -r-- 381540 <no date> mica_port_firmware16 -r-- 388741 <no date> microcom_firmwareNo space information availableRouter# dir flash:Directory of flash:/1 -rw- 6988532 <no date> c5300-is-mz.120-6.5.T8388608 bytes total (1400012 bytes free)Router# dir bootflash:Directory of bootflash:/1 -rw- 1006128 <no date> c5300-boot-mz.112-9.XA18388608 bytes total (7382416 bytes free)•
Two pieces of information are needed to enter the SPE configuration mode:
•
•
The show spe version command will deliver both bits of information. If show spe version is not available, then use show modem mapping.
The following example shows the output from an AS5300 with a single SPE (1/0) when the show spe version command is used:
Router# show spe versionIOS-Bundled Default Firmware-Filename Version Firmware-Type===================================== ======= =============system:/ucode/mica_board_firmware 2.0.2.0 Mica Boardwaresystem:/ucode/mica_port_firmware 2.6.2.0 Mica Portwaresystem:/ucode/microcom_firmware 5.1.20 Microcom F/W and DSPOn-Flash Firmware-Filename Version Firmware-Type========================== ======= =============flash:pw2621.ios 2.6.2.1 Mica PortwareSPE-# SPE-Type SPE-Range Version Upgrade Firmware-Filename1/0 MICA-DMM 1/0 - 1/11 2.6.2.0 N/A system:/ucode/mica_port_firmwareFrom this output, you can determine that the SPE range (SPE-#) is 1/0 and the available MICA firmware files are system:/ucode/mica_port_firmware (2.6.2.0) and flash:pw2621.ios (2.6.2.1).
If you don't have show spe version as an available command option, then use show modem mapping to get the following output:
Router# show modem mappingSlot 1 has Mica Carrier card.Modem Firmware FirmwareModule Numbers Rev Filename0 1/0 - 1/11 2.6.2.0 IOS-DefaultFirmware-file Version Firmware-Type============= ======= =============system:/ucode/mica_board_firmware 2.0.2.0 Mica Boardwaresystem:/ucode/mica_port_firmware 2.6.2.0 Mica Portwaresystem:/ucode/microcom_firmware 5.1.20 Microcom F/W and DSPflash:pw2621.ios 2.6.2.1 Mica PortwareDetermine the SPE range from the slot and module information—Slot 1 is the MICA carrier and Module 0 in it is populated, so the SPE is 1/0. The files are listed above.
Configuration Tasks
Perform the following tasks to download the firmware.
•
Configuring for the spe Command
Note
spe Command Firmware Download for the Cisco AS5200 and AS5300
The copy {flash | system | tftp} modem command will no longer be available for MICA portware and 56K Microcom modem firmware download beginning with Cisco IOS Release 12.0(4)XI1 and later releases. An error message appears if you enter this command—the system displays a prompt for you to use the new spe command.
Step 1
The following output shows an SPE download for Slot 1 SPE 5 with firmware—mica_port_firmware—that was bundled with the IOS image.
Router# configure terminalRouter(config)# spe 1/5 1/5Router(config-spe)# firmware location system:/ucode/mica_port_firmwareRouter(config-spe)# ^ZStep 2
Router# copy running-config startup-configDownload occurs when the modems become available and according to the SPE firmware upgrade option defined (default: busyout). The spe command generates NVRAM modem download and configuration file entries as well.
Note
spe 1/0 2/23
firmware location feature_card_flashMicrocom spe Command Firmware Download for the Cisco AS5200 and AS5300
For 56K systems running Cisco IOS Release 12.0(4)XI1, 12.0(5)T, and later releases, the new spe command is available for firmware download.
Note
To download modem firmware by using the spe command, do the following steps:
Step 1
The following example shows an SPE download for Slot 1 (that is, all modems on the feature card). The modem code resides on the Flash memory, and the modem code filename is mcom-modem-code.5.2.30.bin.
Router# configure terminalRouter(config)# spe 1/0 1/23Router(config-spe)# firmware location flash:mcom-modem-code.5.2.30.binRouter(config-spe)# ^ZStep 2
Router# copy running-config startup-configDownload occurs when the modems become available and according to the SPE firmware upgrade option defined (default: busyout). The spe command generates NVRAM modem download and configuration file entries as well.
SPE Range Description
•
•
•
•
Note
•
•
•
•
•
•
Troubleshooting
To troubleshoot the SPE function, use the following information:
V.34 modems can only use the copy command and will not support the spe commands:
Router(config)# spe 2/12 2/14Router(config-spe)# firmware location flash:mcom-fw-dsp.5.1.9_47.22.binPlease use 'copy' command, firmware download not supported for this type of SPE 2/12Please use 'copy' command, firmware download not supported for this type of SPE 2/13Please use 'copy' command, firmware download not supported for this type of SPE 2/14The following two examples illustrate the copy command showing an error message:
Router# copy system:ucode/mica_port_firmware modem:Modem Numbers (<slot>/<port> | group <number> | all)? 1/0 1/5'Copy' command is no longer valid for this type of port hardware, please use SPE configuration commandRouter# copy flash modemSource filename [portware.2620.ios]? flash:mcom-fw-dsp.5.1.9_47.22.binModem Numbers (<slot>/<port> | group <number> | all)? 2/7'Copy' command is no longer valid for this type of port hardware, please use SPE configuration commandCommand Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
•
•
•
•
•
firmware location
Use the firmware location SPE configuration command to download firmware into the modems. The no form of the command reverts the router back to the system embedded image default.
firmware location {system | flash}: filename
no firmware location {system | flash}: filename
Syntax Description
Default
None.
Command Mode
SPE configuration
Command History
Usage Guidelines
Use the firmware location SPE configuration command to download firmware into your modems. The no form of the command reverts the router back to the system embedded default. When the access server is booted, the firmware location command displays the location for the firmware that is embedded in the IOS image. If the firmware location command was given to download a firmware image from flash and then the no version of the exact command is subsequently given, then the firmware location command will download the embedded firmware in the IOS.
The firmware location command was first supported in Cisco IOS Release 12.0(4)XI1 along with the Resource Pool Management feature (although it can be used independently). For earlier images, use the copy command. For the Cisco IOS Release 12.0(4)XI1 images, the copy {flash | system | tftp} modem command will be disabled for MICA modems and newer versions of Microcom modems (i.e., 56Kbps). Old V.34 Microcom modems still use the copy command for downloading in Cisco IOS Release 12.0(4)XI1 images.
Note
Note
Examples
Examples of firmware location SPE configuration commands:
The following examples show downloads of firmware that was not bundled with the IOS image:
spe 1/2 1/4firmware location flash:portware.2620.iosspe 2/2 2/8firmware location flash:mcom-fw-dsp.5.1.9_47.22.binspe 2/12 2/23firmware location feature_card_flashThe following examples show downloads of firmware that was bundled with the IOS image:
spe 2/9 2/9firmware location system:/ucode/microcom_firmwarespe 1/5 1/7firmware location system:/ucode/mica_port_firmwareRelated Commands
firmware upgrade
Use the firmware upgrade SPE configuration command to modify the way in which the SPE will be downloaded. The no form of the command reverts the SPE back to the default SPE firmware upgrade option: busyout.
firmware upgrade {busyout | recovery | reboot}
no firmware upgrade
Syntax Description
busyout
Starts firmware upgrade immediately. (Default)
reboot
Delays firmware upgrade until reboot.
recovery
Delays firmware upgrade until recovery maintenance time.
Default
busyout
Command Mode
SPE configuration
Command History
Usage Guidelines
This command is for SPEs that contain more than 1 modem.
The SPE firmware location command is designed to integrate all continuous SPE ranges containing the same firmware location. However, the firmware upgrade command will not affect the SPE ranges. As such, all SPEs within the SPE range must have the same firmware upgrade mode or the router will default the upgrade mode to busyout. As such, if you want to upgrade a single SPE within an existing SPE range with a different upgrade mode than is currently configured, you must first change the upgrade mode for the entire SPE range and then change the firmware location for the specific SPE being upgraded.
Furthermore, each time you merge SPE ranges due to configuration changes, verify that the configuration of the SPE firmware upgrade remains effective to what is desired.
Examples
If busyout upgrade is specified, or if no upgrade mode is specified, the SPE modems are set into a "pending download" state when you use the firmware location command on the specified SPE. The "pending download" state prevents any modem in that state to be allocated for new calls until the state is cleared. Modems with active calls remain active for their call durations, but enter the "pending download" state when they terminate. This "pending download" state can only be cleared when the SPE is finally downloaded. When all modems within the SPE are in the "pending download" and no active calls remain on the SPE, the SPE is reloaded. The busyout option is the fastest way to upgrade modems on an active router but can severely impact the router's capacity during the upgrade. This is the default option for the firmware upgrade process:
Router#Router(config-spe)# firmware upgrade busyoutIf reboot upgrade is specified, the SPE modems are not reloaded to the new firmware location until the router is rebooted. The reboot upgrade option is useful for routers which need to have their SPE upgraded and are also going to be rebooted for maintenance. The new firmware can be configured, but will not take affect until the reboot takes place:
Router#Router(config-spe)# firmware upgrade rebootIf recovery upgrade is specified, the SPE modem are reloaded based on the modem recovery algorithm. The SPE modems are all set into a "pending upgrade" state when you use the firmware location command on this SPE. The "pending upgrade" state continues to allow modems to be allocated to modems for as long as there are active calls on the SPE. Only when no active calls exist on the SPE will the firmware download take place. Furthermore, at the configured "modem recovery maintenance time" (3:00 am), the modem recovery maintenance process will, in a controller fashion, attempt to reload the modems by busying out the modems for a window duration of time to make the download take place. Consult the modem recovery documentation for further details. The recovery upgrade option is the least impacting way to upgrade modems on an active router. Capacity is kept at a maximum. However, this option may take a few days for all modems to be reloaded to the new firmware location:
Router#Router(config-spe)# firmware upgrade recoveryRelated Commands
show modem version
To display version information about the modem firmware, controller, and DSP code (for 56K modems only), and boot code, enter the show modem version EXEC command. There is no no version of this command.
show modem version
Syntax
There are no keywords or variables for this command.
Command Mode
EXEC
Default
This function is disabled as default.
Command History
Usage Guidelines
This command is useful for verifying the version of modem firmware running on the system before or after a modem firmware upgrade. If there is a "-/-" in the DSP REV field, you cannot use the spe configuration commands for firmware download on that modem.
Examples
The following example displays information for modem firmware, which includes modem firmware version, boot code version, controller and DSP code version (56K modem modules only), modem board hardware version, and carrier card information. This particular example displays information for Microcom 56K modem cards (modules 0/0, 2/0, and 2/1) and V.34 cards (module 0/1) installed in a Cisco AS5200.
If the version number is displayed as 0.0.0, verify that out-of-band status polling is functioning.
router# show modem versionModem module Firmware Boot DSPMdm Number Rev Rev Rev0/0 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)0/1 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)...0/11 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)0/12 1 2.2(8) 1.0(5)0/13 1 2.2(8) 1.0(5)...0/23 1 2.2(8) 1.0(5)2/0 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)2/1 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)2/2 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)...2/21 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)2/22 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)2/23 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)Modem board HW version info:Slot 0:Carrier card:hw version= 8, number_of_ports= 24, max_modules= 2, max_oob_ports= 2Modem Module 0:number_of_modems= 12, option_bits= 1,rev_num= 02.00, vendor_model_number= 02,vendor_banner= Microcom MNP10 K56 ModemModem Module 1:number_of_modems= 12, option_bits= 1,rev_num= 03.00, vendor_model_number= 01,vendor_banner= Microcom MNP10 V34 ModemSlot 2:Carrier card:hw version= 7, number_of_ports= 24, max_modules= 2, max_oob_ports= 2Modem Module 0:number_of_modems= 12, option_bits= 1,rev_num= 02.00, vendor_model_number= 02,vendor_banner= Microcom MNP10 K56 ModemModem Module 1:number_of_modems= 12, option_bits= 1,rev_num= 02.00, vendor_model_number= 02,vendor_banner= Microcom MNP10 K56 ModemThe following example displays modem version information for V.110 terminal adapter modules:
router# show modem versionModem module Firmware BootMdm Number Rev Rev0/0 0 Unmanaged Unmanaged0/1 0 Unmanaged Unmanaged0/2 0 Unmanaged Unmanaged...0/11 0 Unmanaged Unmanaged1/0 0 Unmanaged Unmanaged...1/11 0 Unmanaged Unmanaged1/12 1 Unmanaged Unmanaged...1/22 1 Unmanaged Unmanaged1/23 1 Unmanaged Unmanaged2/0 0 Unmanaged Unmanaged...2/11 0 Unmanaged Unmanaged2/12 1 Unmanaged Unmanaged...2/22 1 Unmanaged UnmanagedModem board HW version info:Slot 0:Carrier card:hw version= 3, number_of_ports= 12, max_modules= 1, max_oob_ports= 1Modem Module 0:number_of_modems= 12, option_bits= 1,rev_num= 03.01, vendor_model_number= 01,vendor_banner= V.110 Terminal AdaptorSlot 1:Carrier card:hw version= 8, number_of_ports= 24, max_modules= 2, max_oob_ports= 2Modem Module 0:number_of_modems= 12, option_bits= 1,rev_num= 03.01, vendor_model_number= 01,vendor_banner= V.110 Terminal AdaptorModem Module 1:number_of_modems= 12, option_bits= 1,rev_num= 03.01, vendor_model_number= 01,vendor_banner= V.110 Terminal AdaptorSlot 2:Carrier card:hw version= 8, number_of_ports= 24, max_modules= 2, max_oob_ports= 2Modem Module 0:number_of_modems= 12, option_bits= 1,rev_num= 03.00, vendor_model_number= 01,vendor_banner= V.110 Terminal AdaptorModem Module 1:number_of_modems= 12, option_bits= 1,rev_num= 03.00, vendor_model_number= 01,vendor_banner= V.110 Terminal AdaptorThe following example shows the display from an AS5300:
Note
Router# show modem versionModem module Firmware Boot DSPMdm Number Rev Rev Rev1/0 0 2.6.1.01/1 0 2.6.1.01/2 0 2.6.1.01/3 0 2.6.1.01/4 0 2.6.1.01/5 0 2.6.1.01/6 1 2.6.1.0...1/41 6 2.6.1.01/42 7 2.6.1.01/43 7 2.6.1.01/44 7 2.6.1.01/45 7 2.6.1.01/46 7 2.6.1.01/47 7 2.6.1.02/0 0 5.0(40) 3.0(4) 22.0/47.02/1 0 5.0(40) 3.0(4) 22.0/47.02/2 0 5.1(9) 3.0(4) 22.0/47.0...2/8 0 5.1(9) 3.0(4) 22.0/47.02/9 0 5.0(40) 3.0(4) 22.0/47.02/10 0 5.1(9) 3.0(4) 22.0/47.02/11 0 5.1(9) 3.0(4) 22.0/47.02/12 1 2.3(6) 1.0(5) -/-2/13 1 2.3(6) 1.0(5) -/-...Modem board HW version info:Slot 1:Carrier card:number_of_ports= 48, max_modules= 10Manufacture Cookie Info:EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x47,Board Hardware Version 1.0, Item Number 73-2393-3,Board Revision A0, Serial Number 09361116,PLD/ISP Version 5.9, Manufacture Date 20-Jun-1998.Modem Module 0Manufacture Cookie Info:EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,Board Hardware Version 1.0, Item Number 73-2522-2,Board Revision B48, Serial Number 06542204,PLD/ISP Version 255.255, Manufacture Date 23-Jun-1998.Modem Module 1Manufacture Cookie Info:EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,Board Hardware Version 1.0, Item Number 73-2522-2,Board Revision B48, Serial Number 06478113,PLD/ISP Version 255.255, Manufacture Date 23-Jun-1998....Modem Module 7Manufacture Cookie Info:EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,Board Hardware Version 1.0, Item Number 73-2522-2,Board Revision B48, Serial Number 06478929,PLD/ISP Version 255.255, Manufacture Date 23-Jun-1998.Modem Module 8Modem Module 9Slot 2:Carrier card:hw version= 2, pld= 0, number_of_ports= 24,max_modules= 2, max_oob_ports= 2Manufacture Cookie Info:EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x47,Board Hardware Version 1.0, Item Number 73-2522-2,Board Revision ^@2, Serial Number 05433763,PLD/ISP Version 255.255, Invalid Date code.Modem Module 0:number_of_modems= 12, option_bits= 1,rev_num= 03.30, vendor_model_number= 02,vendor_banner= Microcom MNP10 K56 ModemModem Module 1:number_of_modems= 12, option_bits= 1,rev_num= 03.00, vendor_model_number= 01,vendor_banner= Microcom MNP10 V34 ModemRouter#Router# wr tBuilding configuration...Current configuration:!version 12.0service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryptionservice internal!hostname Router!aaa new-modelaaa group server radius aaa-serverserver 1.2.3.4!spe 1/0 1/7firmware location system:/ucode/mica_port_firmwarespe 2/0 2/1firmware location system:/ucode/microcom_firmwarespe 2/2 2/8firmware location flash:mcom-fw-dsp.5.1.9_47.22.binspe 2/9 2/9firmware location system:/ucode/microcom_firmwarespe 2/10 2/11firmware location flash:mcom-fw-dsp.5.1.9_47.22.binspe 2/12 2/23firmware location feature_card_flash!Router# termination length 0describes the fields shown in the previous displays of the show modem version command.
Table 1
show modem version Field Descriptions
Related Commands
None
show spe version
Enter the show spe version global show command to display the SPE download information such as the version and filename. There is no no version of this command.
show spe version [x/y/z] [x/y/z]
Syntax Description
Default
none
Command Mode
global
Command History
Usage Guidelines
To view SPE download information such as version and file names, enter the show spe version global show command.
Examples
The following examples show various implementations of the show spe version command to display information about the available SPE sources and modem resources:
Router#Router# show spe versionIOS-Bundled Default Firmware-Filename Version Firmware-Type===================================== ======= =============system:/ucode/mica_board_firmware 2.0.2.0 Mica Boardwaresystem:/ucode/mica_port_firmware 2.6.2.0 Mica Portwaresystem:/ucode/microcom_firmware 5.1.20 Microcom F/W and DSPOn-Flash Firmware-Filename Version Firmware-Type========================== ======= =============flash:portware.2620.ios 2.6.2.0 Mica Portwareflash:mcom-modem-firmware.3.1.30.bin 3.1.30 Microcom Firmwareflash:mcom-fw-dsp.5.1.9_47.22.bin 5.1.9 Microcom F/W and DSPflash:R0620.ios 0.6.2.0 Mica Portwareflash:pw2710.ios 2.7.1.0 Mica Portwareflash:mica-modem-pw_2_7_1_0.bin 2.7.1.0 Mica PortwareSPE-# SPE-Type SPE-Range Version Upgrade Firmware-Filename1/0 MICA-HMM 1/0 - 1/5 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/1 MICA-HMM 1/6 - 1/11 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/2 MICA-HMM 1/12 - 1/17 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/3 MICA-HMM 1/18 - 1/23 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/5 MICA-HMM 1/30 - 1/35 2.7.1.0 N/A system:/ucode/mica_port_firmware1/6 MICA-HMM 1/36 - 1/41 2.7.1.0 N/A system:/ucode/mica_port_firmware1/7 MICA-HMM 1/42 - 1/47 2.7.1.0 N/A system:/ucode/mica_port_firmware1/9 MICA-HMM 1/54 - 1/59 2.7.1.0 N/A flash:/pw2710.ios2/0 MCOM-V90 2/0 5.1(20) N/A system:/ucode/microcom_firmware2/1 MCOM-V90 2/1 5.1(20) N/A system:/ucode/microcom_firmware2/2 MCOM-V90 2/2 5.1(20) N/A system:/ucode/microcom_firmware2/3 MCOM-V90 2/3 5.1(20) N/A system:/ucode/microcom_firmware2/4 MCOM-V90 2/4 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/5 MCOM-V90 2/5 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/6 MCOM-V90 2/6 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/7 MCOM-V90 2/7 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/8 MCOM-V90 2/8 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/9 MCOM-V90 2/9 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/10 MCOM-V90 2/10 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/11 MCOM-V90 2/11 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/12 MCOM-V34 2/12 2.3(6) N/A feature_card_flash2/13 MCOM-V34 2/13 2.3(6) N/A feature_card_flash2/14 MCOM-V34 2/14 2.3(6) N/A feature_card_flash2/15 MCOM-V34 2/15 2.3(6) N/A feature_card_flash2/16 MCOM-V34 2/16 2.3(6) N/A feature_card_flash2/17 MCOM-V34 2/17 2.3(6) N/A feature_card_flash2/18 MCOM-V34 2/18 2.3(6) N/A feature_card_flash2/19 MCOM-V34 2/19 2.3(6) N/A feature_card_flash2/20 MCOM-V34 2/20 2.3(6) N/A feature_card_flash2/21 MCOM-V34 2/21 2.3(6) N/A feature_card_flash2/22 MCOM-V34 2/22 2.3(6) N/A feature_card_flash2/23 MCOM-V34 2/23 2.3(6) N/A feature_card_flashRouter# show spe version 1SPE-# SPE-Type SPE-Range Version Upgrade Firmware-Filename1/0 MICA-HMM 1/0 - 1/5 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/1 MICA-HMM 1/6 - 1/11 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/2 MICA-HMM 1/12 - 1/17 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/3 MICA-HMM 1/18 - 1/23 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/5 MICA-HMM 1/30 - 1/35 2.7.1.0 N/A system:/ucode/mica_port_firmware1/6 MICA-HMM 1/36 - 1/41 2.7.1.0 N/A system:/ucode/mica_port_firmware1/7 MICA-HMM 1/42 - 1/47 2.7.1.0 N/A system:/ucode/mica_port_firmware1/9 MICA-HMM 1/54 - 1/59 2.7.1.0 N/A flash:/pw2710.iosRouter# show spe version 1/2SPE-# SPE-Type SPE-Range Version Upgrade Firmware-Filename1/2 MICA-HMM 1/12 - 1/17 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.binRouter# show spe version 1/2 2SPE-# SPE-Type SPE-Range Version Upgrade Firmware-Filename1/2 MICA-HMM 1/12 - 1/17 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/3 MICA-HMM 1/18 - 1/23 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/5 MICA-HMM 1/30 - 1/35 2.7.1.0 N/A system:/ucode/mica_port_firmware1/6 MICA-HMM 1/36 - 1/41 2.7.1.0 N/A system:/ucode/mica_port_firmware1/7 MICA-HMM 1/42 - 1/47 2.7.1.0 N/A system:/ucode/mica_port_firmware1/9 MICA-HMM 1/54 - 1/59 2.7.1.0 N/A flash:/pw2710.ios2/0 MCOM-V90 2/0 5.1(20) N/A system:/ucode/microcom_firmware2/1 MCOM-V90 2/1 5.1(20) N/A system:/ucode/microcom_firmware2/2 MCOM-V90 2/2 5.1(20) N/A system:/ucode/microcom_firmware2/3 MCOM-V90 2/3 5.1(20) N/A system:/ucode/microcom_firmware2/4 MCOM-V90 2/4 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/5 MCOM-V90 2/5 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/6 MCOM-V90 2/6 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/7 MCOM-V90 2/7 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/8 MCOM-V90 2/8 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/9 MCOM-V90 2/9 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/10 MCOM-V90 2/10 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/11 MCOM-V90 2/11 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/12 MCOM-V34 2/12 2.3(6) N/A feature_card_flash2/13 MCOM-V34 2/13 2.3(6) N/A feature_card_flash2/14 MCOM-V34 2/14 2.3(6) N/A feature_card_flash2/15 MCOM-V34 2/15 2.3(6) N/A feature_card_flash2/16 MCOM-V34 2/16 2.3(6) N/A feature_card_flash2/17 MCOM-V34 2/17 2.3(6) N/A feature_card_flash2/18 MCOM-V34 2/18 2.3(6) N/A feature_card_flash2/19 MCOM-V34 2/19 2.3(6) N/A feature_card_flash2/20 MCOM-V34 2/20 2.3(6) N/A feature_card_flash2/21 MCOM-V34 2/21 2.3(6) N/A feature_card_flash2/22 MCOM-V34 2/22 2.3(6) N/A feature_card_flash2/23 MCOM-V34 2/23 2.3(6) N/A feature_card_flashRouter# show spe version 1/2 2/6SPE-# SPE-Type SPE-Range Version Upgrade Firmware-Filename1/2 MICA-HMM 1/12 - 1/17 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/3 MICA-HMM 1/18 - 1/23 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/5 MICA-HMM 1/30 - 1/35 2.7.1.0 N/A system:/ucode/mica_port_firmware1/6 MICA-HMM 1/36 - 1/41 2.7.1.0 N/A system:/ucode/mica_port_firmware1/7 MICA-HMM 1/42 - 1/47 2.7.1.0 N/A system:/ucode/mica_port_firmware1/9 MICA-HMM 1/54 - 1/59 2.7.1.0 N/A flash:/pw2710.ios2/0 MCOM-V90 2/0 5.1(20) N/A system:/ucode/microcom_firmware2/1 MCOM-V90 2/1 5.1(20) N/A system:/ucode/microcom_firmware2/2 MCOM-V90 2/2 5.1(20) N/A system:/ucode/microcom_firmware2/3 MCOM-V90 2/3 5.1(20) N/A system:/ucode/microcom_firmware2/4 MCOM-V90 2/4 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/5 MCOM-V90 2/5 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin2/6 MCOM-V90 2/6 5.1(9) N/A flash:/mcom-fw-dsp.5.1.9_47.22.bin5300-1#show spe versionIOS-Bundled Default Firmware-Filename Version Firmware-Type===================================== ======= =============system:/ucode/mica_board_firmware 2.0.2.0 Mica Boardwaresystem:/ucode/mica_port_firmware 2.6.2.0 Mica Portwaresystem:/ucode/microcom_firmware 5.1.20 Microcom F/W and DSPOn-Flash Firmware-Filename Version Firmware-Type========================== ======= =============flash:portware.2620.ios 2.6.2.0 Mica Portwareflash:mcom-modem-firmware.3.1.30.bin 3.1.30 Microcom Firmwareflash:mcom-fw-dsp.5.1.9_47.22.bin 5.1.9 Microcom F/W and DSPflash:R0620.ios 0.6.2.0 Mica Portwareflash:pw2710.ios 2.7.1.0 Mica Portwareflash:mica-modem-pw_2_7_1_0.bin 2.7.1.0 Mica PortwareSPE-# SPE-Type SPE-Range Version Upgrade Firmware-Filename1/0 MICA-HMM 1/0 - 1/5 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/1 MICA-HMM 1/6 - 1/11 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/2 MICA-HMM 1/12 - 1/17 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.bin1/3 MICA-HMM 1/18 - 1/23 2.7.1.0 N/A flash:mica-modem-pw_2_7_1_0.binFor the Cisco AS5800, the show spe version command display will be different. Note that the SPE-Port-Range field indicates the shelf/slot/port of the SPE.
5800# show spe versionFirmware-Filename Version Firmware-Type================= ======= =============IOS-Bundled Default 2.6.2.0 Mica Portwareslot0:/pw2710.ios 2.7.1.0 Mica Portwareslot0:/pw3102.ios 3.1.0.2 Mica Portwareslot0:/pw3101.ios 3.1.0.1 Mica PortwareSPE-# SPE-Type SPE-Port-Range Version Upgrade Firmware-Filename3/0 MICA-DMM 1/3/00 - 1/3/11 2.7.1.0 N/A slot0:/pw2710.ios3/1 MICA-DMM 1/3/12 - 1/3/23 2.7.1.0 N/A slot0:/pw2710.ios3/2 MICA-DMM 1/3/24 - 1/3/35 2.7.1.0 N/A slot0:/pw2710.ios3/3 MICA-DMM 1/3/36 - 1/3/47 2.7.1.0 N/A slot0:/pw2710.ios3/4 MICA-DMM 1/3/48 - 1/3/59 2.7.1.0 N/A slot0:/pw2710.ios3/5 MICA-DMM 1/3/60 - 1/3/71 2.7.1.0 N/A slot0:/pw2710.ios3/6 MICA-DMM 1/3/72 - 1/3/83 2.7.1.0 N/A slot0:/pw2710.ios3/7 MICA-DMM 1/3/84 - 1/3/95 2.7.1.0 N/A slot0:/pw2710.ios3/8 MICA-DMM 1/3/96 - 1/3/107 2.7.1.0 N/A slot0:/pw2710.iosTable 2
show spe version Field Descriptions
Related Commands
show modem version
Displays version information about the modem firmware, controller, and DSP code (for 56K modems only), and boot code.
spe
Use the spe configuration command to access the SPE configuration mode and control the downloading of firmware into the modems. There is no no version of this command.
spe {shelf/slot/module} {shelf/slot/module}
Syntax Description
Default
None.
Command Mode
Global configuration
Command History
12.0(4)XI1
This command was introduced.
12.0(5)T
This document changed to reflect new information on the command.
Usage Guidelines
The spe global configuration command enables the SPE configuration mode. Configure your SPE by specifying a slot and an SPE associated with the slot; or, you can configure a range of SPEs by specifying the first and last SPE in the range. On AS5800 platforms, you must also specify the shelf associated with the slot and SPE.
When the access server is booted, the spe global configuration command specifies the location from where the firmware image is downloaded to the SPE. If the spe configuration command is used to download the firmware from flash memory and then subsequently the no version of the exact command is entered, then the spe command downloads the embedded firmware.
The spe command was first supported in Cisco IOS Release 12.0(4)XI1 along with the Resource Pool Management feature (although it can be used independently). For earlier images, use the copy command on the Cisco AS5200 and Cisco AS5300, and the modem-pool command on the Cisco AS5800. For the Cisco IOS Release 12.0(5)T images, the copy {flash | system | tftp} modem command will be disabled for firmware and newer version of Microcom modems (i.e., 56Kbps). Old V.34 Microcom modems still use the copy command for downloading in Cisco IOS Release 12.0(5)T images. For Cisco AS5800, downloading firmware through the modem-pool command is disabled.
Note
Note
Examples
The following example shows the spe command being used from global configuration mode to access the SPE configuration mode for the SPE range from 1/2 to 1/4:
Router#Router# configuration terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# spe 1/2 1/4Router(config-spe)#Related Commands
Glossary
NAS—Network access server, such as a Cisco AS5200, AS5300, or AS5800.
SPE—Service Processing Element.
Note
