|
|
This chapter provides information for uploading and downloading software and firmware, including where to obtain it, along with required preparations and procedures. This chapter also describes uploading and downloading software and firmware to a Cisco WAN switch. You can initiate an upload or download of software or firmware in three ways:
The TFTP protocol is used to download software and firmware images from the CWM workstation to WAN switches.
 |
Note A CWM workstation is not required to download the software images. You can download the software images using any machine that can run a TFTP client/server process. |
Cisco Connection Online (CCO) provides a web page, WAN Switching Upgrade Planner, that provides information about the latest Cisco software product. If you have a Cisco Connection Online account, you can order or download software directly to your system. The URL for CCO software and firmware is:
http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml
The WAN Switching Upgrade Planner web page provides links to the following:
Before downloading software and firmware to a switch, use the Switch CLI (Command Line Interface) to execute the following commands. This is required regardless of how the software image transfer will be initiated.
When you select the switch node from the CWM Network Topology window and then select the Node menu's Node Admin option, the CWM software telnets to the switch. A new terminal window is displayed for your use.
Step 2 Enable the switch to allow downloading. From the Switch CLI, execute the following command:
cnffunc
Step 3 Use the Index column's value for the Download From Remote StrataView entry in the following command:
cnffunc <index> e
In the example, <index> would be set to 6. The "e" parameter specifies to enable the function. Once this command is executed, the switch allows downloading from a CWM workstation, provided the latter is connected to another switch in the same network.
Step 4 Invoke the following command when a redundant processor card is not installed.
cnfnodeparm
shows sample output from the cnfnodeparm command. When a redundant processor card (BCC, NPM, or NPC) is not installed, you should set the parameter indicating the presence of a redundant processor to No. In the command output, look for the number corresponding to the CC Redundancy Cnfged entry.
Step 5 Invoke the following command:
cnfnodeparm <number> N
When you have a redundant processor card and the value for the parameter CC Redundancy Cnfged is Yes, you are requesting an image download into both processors (active and redundant).
|
Note If CC Redundancy Cnfged is Yes and no redundant processor card is present, the download is suspended. |
Step 6 Configure the switch to receive software or firmware images from the CWM workstation by invoking the cnffwswinit command:
cnffwswinit <IP_addr_CWM_workstation>
|
Note The step above is required if you are using a CWM workstation to send the download request to the switch. |
This section provides a procedure for uploading switch software from a CWM workstation. Before initiating the upload operation, you must load the software/firmware revisions in the CWM workstation's /usr/users/svplus/images/ipxbpx directory.
The procedure for uploading switch software to another switch is as follows:
The Network Topology window is displayed.
Step 2 Click on the IGX 8400 series or BPX 8600 series node icon in the Network Topology window, to which you want to upload the switch software/firmware, then select the SW/FW Images option from the Software Mgmt menu.
The Image Uploader window is displayed. This window displays a list of the IGX 8400 series or BPX 8600 series software that is loaded on the CWM workstation (in the /usr/users/svplus/images/ipxbpx directory) for the type of node selected.
Step 3 In the Image Download window, select the image to upload, and then start the image upload by clicking on the Upload button.
Step 4 Invoke the dsprevs command on the switch CLI from the telnet window.
When the upload is complete, the dsprevs command shows the status of the upload in the secondary column on the right hand side of the display. For a non-graceful upgrade (no CC Redundancy configured), the secondary status upon completion should be Loaded. For a graceful upgrade (CC Redundancy is configured), the secondary status upon completion should be Upgraded.
If you are uploading firmware, invoke the dspfwrev to monitor the status of the upload operation. The status upon completion should be Complete.
When you are finished uploading software, you must invoke the runrev command in order to run the uploaded software. When you uploaded firmware, you must invoke the burnfwrev command in order to burn the firmware onto the card. For details about the runrev and burnfwrev commands, refer to the Switch software manuals.
To upload images to an MGX, complete the following steps:
Step 2 Launch CWM as a user with All access privileges for Topology.
Step 3 Click on Topology in the CWM Desktop window.
The Network Topology window is displayed.
Step 4 Click on the node icon in the Network Topology window, upon which you want to upload the switch software/firmware, then select the Software Mgmt menu's SW/FW Images option.
The Image Uploader window is displayed. This window displays a list of the software that is loaded on the CWM workstation (in the /usr/users/svplus/images/mgx directory) for the type of node selected.
Step 5 Select the image you wish to upload, then Select Upload.
When the upload has completed, you must reset the MGX switch.
Step 6 Log into the MGX shelf controller card and issue the resetsys command.
Upon completion of the resetsys command, the MGX or node switches over to the new software.
The following naming convention is used for software images:
IGX and BPX software images have the following format (where Release is 9.2.0):
<Release>.img <9.2.0>.img <9.2.0>.000 ... <9.2.0>.022
IGX and BPX firmware images have the following format:
<FW Release>.img <A.A.02>.img
The following naming convention is used for software images:
<cardtype>_<A>_<B> [<C>_<D>].fw
where <cardtype> is a name of the card. <A>, <B>, <C>, and <D> can be a string containing any combination of numerals and characters. <A>_<B> <C>_<D> indicates the firmware version number of a given image file. <C> and <D> are optional. The .fw extension indicates the file is a firmware image.
Software and firmware can be downloaded via Switch CLI or TFTP.
|
Note Bootcode is not available for download; only software and firmware downloads are available. |
Before a loadrev or getfwrev command is issued for a routing node, some other routing node closer (in hop count distance) to this node, may already have the software or firmware.
|
Note The loadrev and getfwrev commands attempt to retrieve the software or firmware from a CWM workstation or from another routing node in the network (the latter only in the case the node to be downloaded is itself a routing node). The selected node or workstation is always one of the closest sites (in terms of hop count). A routing switch can be downloaded using another routing switch. A feeder switch needs the image to be on a managing CWM workstation. |
To download software and firmware images, complete the following steps:
To view the list of images residing in this directory, use the Images menu from the Network Topology window, which is available from the CWM Desktop window.
Step 2 Select the Images menu's SW/FW option. A list of images is displayed in the Downloader Images window.
You can initiate a download session between a switch and the CWM workstation managing the network by using Switch CLI. When the switch is a routing node, the command can be initiated from any routing node in the same network. When the switch is an IGX feeder, you must initiate the loadrev command from that particular switch. You can initiate downloads for all routing nodes in a network by supplying a "*" (asterisk) rather than the actual switch name to the command.
To download firmware, use the getfwrev command from the switch CLI. This requires a CWM workstation to be attached to the node and for the firmware files to be in the /usr/users/svplus/images/ipxbpx directory on the CWM workstation.
The following example of uses the getwrev command to download firmware of a new card, BXM, with revision number AA04. From the command line on the switch (named node1) type:
getfwrev BXM A.A.01 node1
The firmware's filename is obtained by concatenating the Cardname and Revision number. The /usr/users/svplus/images/ipxbpx directory should contain the files BXMAA01.img, BXMAA01.000, BXMAA01.001, and so on.
The commands dsprev (software) and dspfwrev (firmware) display existing software (or firmware) revisions on a routing network, as well as the revisions currently being downloaded. When these commands are issued at a feeder, revisions on that feeder alone appear on the screen.
You can use the dsprev or dspfwrev commands to see when downloading of the software or firmware is complete.
When you have a workstation with CWM loaded, you can use the CWM GUI to download the firmware. When you do not want to use the CWM GUI or the getfwrev command, follow these steps.
The following is the format of the dnld.fw file:
IP: <IP address of the Workstation containing the firmware files>
PathName: <Path of the directory where the firmware files are present>
Cardname: <Name of the card>
RevNum: <Revision number of the firmware revision>
filename: <Name of the firmware files in the Workstation>
Step 2 The following example shows a download of the firmware revision (for an FRP card with revision number FHA) onto a switch named node2 from the CWM workstation whose IP address is 192.9.201.2. From the command line on the node2 switch, type:
cnffwswinit 192.9.201.2
This allows you to do a tftp put on the switch from the workstation with IP address 192.9.201.2.
Ensure the firmware is in the /usr/users/svplus/images/ipxbpx directory on the CWM workstation and name them fha.img, fha.000, fha.001 and so on.
Step 3 Create the following dnld.fw file on the CWM workstation.
tftp_request
IP: 192.9.201.2
PathName: /usr/users/svplus/images/ipxbpx
Cardname: FRP
RevNum: FHA
filename: fha
Step 4 From the CWM workstation type:
host% tftp
Step 5 Invoke the tftp put command:
host% tftp node2
tftp> bin
tftp> put dnld.fw
tftp> quit
The above step should start the firmware download on node2, which tries to get the firmware files from the 192.9.201.2 CWM workstation.
Step 6 From the command line on the switch, type:
dspdnld
The output of the download is as follows:
node2 TN StrataCom IPX 15 9.1.0A May 21 1998 23:05 GMT
dl_dest: Active CC dl_source: SV 192.9.201.2
dl_type: None dl_image: Firmware
pathname: /usr/users/svplus/images/ipxbpx
filename: fha
BFC20000 BFC30000 BFC40000 BFC50000 BFC60000
Last Command: dspdnld
Next Command:
To download the firmware from a Sun workstation which is not running CWM, it is likely the TFTP (Trivial File Transfer Protocol) server is not configured to run on the Sun. To perform a manual configuration, follow these steps:
The usual output is as follows:
#tftp dgram udp wait root usr/etc/in.tftpd in.tftpd -s /tftpboot
On the Sun workstation, the firmware files are located in the /user/myname/images/ipxbpx directory.
Step 2 Replace the above line in the /etc/inetd.conf with the following line:
tftp dgram udp wait root /usr/etc/in.tftpd in.tftpd -s /user/myname/images/ipxbpx
|
Note Removing the "#"at the beginning of the entry un-comments the line and configures the TFTP server on the Sun workstation. |
Step 3 Have the inetd daemon on the Sun use the new inetd.conf file. You must kill the inetd daemon. Get the process id of the inetd daemon as follows:
host% ps -ef | grep inetd
Following is sample output:
root 120 0.0 0.0 48 0? IW May 10 0:00 inetd
In this example, 120 is the process id of the inetd daemon.
Step 4 Kill the inetd daemon.
host% kill -9 120
Step 5 Restart the inetd daemon to use the new inetd.conf file:
host% inetd
You have now configured your node to support a TFTP server.
|
Note The default TFTP server for the Sun workstation does not accept an absolute pathname unlike the TFTP servers on a CWM workstation. |
Step 6 Place the firmware files in the default directory the TFTP server uses. This is specified by an entry in the file inetd.conf. For the above example, /user/myname/images/ipxbpx was the specified directory.
Proceed exactly as in the previous example. The only difference is the pathname in the dnld.fw, which you specify as "." This ensures the node downloads the firmware files from the default TFTP directory on the TFTP server. The dnld.fw file now appears as follows:
tftp_request
IP: <IP address of the Sun workstation>
PathName: .
Cardname: FRP
RevNum: FHA
filename: fha
Posted: Fri Sep 29 10:24:35 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.