fwUpdateImageUri

This is a URI string specifies the protocol and various location parameters to be
used by the switch to perform a get operation using any of the supported
protocols TFTP, FTP, sFTP. SFTP and FTP are mandatory and TFTP is
recommended to support various user update tools. The IOM must report the
protocols supported for the level of executing firmware in the IOM capabilities
field of the VPD EEPROM. In this context the CMM (or remote host) acts as the
server and the IOM acts as the client. The format of this string is as follows:
<protocol>://<username>:<password>@<IP address or hostname:<port>/<path>/<filename>
          
An example of a URI for the firmware packet file would be:
ftp://USERID:PASSW0RD@192.168.0.2:30045/tmp/1308 application.img1
						or
ftp://USERID:PASSW0RD@[fe80::290:27ff:fe29:6019]:30045/tmp/application.img
						or
sftp://USERID:PASSW0RD@192.168.0.2:30045/tmp/application.img
						or
sftp://USERID:PASSW0RD@[fe80::290:27ff:fe29:6019]:30045/tmp/application.img
          
where the FTP or sFTP protocol will be used for transferring the packet file,
username is USERID, password is PASSW0RD, host IP address is either
fe80::290:27ff:fe29:6019 or 192.168.0.2, port number is 30045, and /tmp is the
full pathname to the packet file application.img. Note: The URI may or may not
have a port number. If the port number is not included the default port number for
that protocol will be used.
          
Some protocols do not need the username, password, and the port number, so
the minimum requirement for a fully qualified address would be:
<protocol>://<IP address or hostname>/<path</<filename>
          
An example of a fully qualified address for the firmware packet file can be:
tftp://192.168.0.2:2022/tmp/application.img.
          
ote: (1) the MM will set the URI to the IOM. This URI may point to a server that
is internal to the chassis with an IP address/hostname or if the server is external
to the chassis then a public IP address/ hostname. Therefore the IP address of
the server may or may not be the MMs IP address. In addition when a public IP
address/hostname is used the filename in the URI may point to the top level
directory that contains many files that make up the firmware image and the IOM
is responsible to accept or reject this operation and indicate this by utilizing the
status OID.
          
Notes on sftp file transfers:
(3) Summary: CMM will provide to the IOM the fingerprint of the CMM sftp
server's public key as part of the other parameters in the URI for the file
transfer.
(4) CMM 'sets' to the IOM the URI which will contain the fingerprint (128bit MD5
fingerprint). For example assume the 128bit MD5 fingerprint of the 1024-bit
RSA key is '00:6d:75:9e:f3:38:2b:6b:2e:e7:a8:87:9f:ea:26:03'. CMM issues
a 'set' of the URI to the IOM of form:
<protocol>://<username>:<password>;<fingerprint>@<IP
address>:<port>/<path>/<filename.
Then the URI would be: sftp://USERID:PASSW0RD;
00:6d:75:9e:f3:38:2b:6b:2e:e7:a8:87:9f:ea:26:03@
[fe80::290:27ff:fe29:6019]:30045/tmp/application.img
(5) The fingerprint character string then will be used by IOM to create the
CMM's sftp servers public key and add to the IOM's known host key file.
(6) IOM sftp client then connects to the CMM sftp server. Since IOM has the
CMM sftp servers public key fingerprint the IOM sftp client will look into it's
known host key file.
(7) IOM begins the sftp transfer of application.img using the user credentials
(for example USERID, PASSW0RD) and CMM's sftp server key.
Note - As of 5/1/2013 this specification assumes that the fingerprint in the URI
will be for a RSA key only. Therefore all IOM sftp client's when connecting to the
sftp server will respond to the sftp server and indicate in the
'server_host_key_algorithms list that a RSA key is the preferred key by listing
this first in the 'server_host_key_algorithms' parameter 'name-list'. The sftp
client and server then will be required to use a RSA key for the file transfer. In
the future the URI syntax will be changed to allow the user to specify which type
of key (RSA or DSA) the fingerprint is for.

MIB

IBM-BCCUSTOM-MIB

OID

.1.3.6.1.4.1.2.6.215.3.1.2.7

Type

scalar

Access

readwrite

Status

current

Parent

firmwareCmd

Siblings

7