cc/td/doc/product/wanbu/9_1/nms
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Downloading Software and Firmware From Switch CLI or by TFTP

Downloading Software and Firmware From Switch CLI or by TFTP

Initiating Software and Firmware Download From Switch

To download software and firmware images, follow these steps:

Step 1 Copy the software and firmware images onto the Cisco StrataView Plus (SV+) workstation in the /usr/users/svplus/images/ipxbpx directory.

To view the list of images residing in this directory, use the Images menu from the Network Topology window, which is available from the Cisco SV+ Desktop window.

Step 2 Select the Images menu's SW/FW option. A list of images is displayed in the Downloader Images window, as shown in Figure C-1.


Figure C-1: Downloader Images Window


Initiating a Software Download from a Switch

You can initiate a download session between a switch and the Cisco SV+ 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 a feeder (IPX or IGX feeder), it is necessary to initiate the command from that particular switch. It is also possible to initiate downloads for all routing nodes in a network by supplying a "*" (asterisk) rather than the actual switch name to the command.

Following are some helpful tips:

loadrev <software revision> <node name>
getfwrev <card-type> <image name> <node name>

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 Cisco SV+ 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/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 Cisco SV+ workstation.

Initiating a Firmware Download from a Switch

To download firmware, use the getfwrev command from the switch CLI. This requires a Cisco SV+ workstation to be attached to the node and for the firmware files to be in the /usr/users/svplus/images/ipxbpx directory on the Cisco SV+ 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.

Monitoring a Download Session

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.

Figure C-2 shows the sample output of a dsprev command, in which a software download to the switch (revision 9.1.0A) is in progress.


Figure C-2: dsprev---Command Sample Output Screen


You can use the dsprev or dspfwrev commands to see when downloading of the software or firmware is complete.

Using TFTP to Load Firmware From a Cisco StrataView Plus Workstation

When you have a workstation with Cisco SV+ loaded, you can use the Cisco SV+ GUI to download the firmware. When you do not want to use the Cisco SV+ GUI or the getfwrev command, follow these steps.

Step 1 Use the TFTP's (Trivial File Transfer Protocol) tftp put command for the dnld.fw file, with the required download information, to start the firmware download.

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 Cisco SV+ 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 Cisco SV+ workstation and name them fha.img, fha.000, fha.001 and so on.

Step 3 Create the following dnld.fw file on the Cisco SV+ workstation.

tftp_request

IP: 192.9.201.2
PathName: /usr/users/svplus/images/ipxbpx
Cardname: FRP
RevNum: FHA
filename: fha

Step 4 From the Cisco SV+ 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 Cisco SV+ 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:

Using TFTP to Load Firmware From Sun Workstations Not Running StrataView Plus

To download the firmware from a Sun workstation which is not running Cisco SV+, 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:

Step 1 Grep on the /etc/inetd.conf file searching for the tftp string:
host% grep tftp /etc/inetd.conf

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 Cisco SV+ 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


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Oct 4 19:45:55 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.