Cisco Model GS7000 4-Port Node 1 GHz with 42 54 Split Installation Guide
Chapter 2 Installation
24
4037424 Rev A
Downloading Module Firmware Using the CTLP-
DOWNLOAD-MIB
With firmware version 4.1.0 and greater, the transponder has the ability to download
firmware to Optical Amps and Optical Switches by using the CTLP-Download MIB
(OID 1.3.6.1.4.1.2082.5.10.1).
firmware to Optical Amps and Optical Switches by using the CTLP-Download MIB
(OID 1.3.6.1.4.1.2082.5.10.1).
Note: While downloading firmware to the Optical Amps and Optical Switches, there
will be no communication between the transponder and any Optical Amps or
Optical Switches in the Hub or Node during the entire firmware download process,
although they will continue to function correctly. The transponder will still be able
to monitor the Optical Transmitters and Receivers.
will be no communication between the transponder and any Optical Amps or
Optical Switches in the Hub or Node during the entire firmware download process,
although they will continue to function correctly. The transponder will still be able
to monitor the Optical Transmitters and Receivers.
A firmware download to the modules can be accomplished in one of two ways:
management style download or provisioning style download.
management style download or provisioning style download.
To start a management initiated download, set the downloadModuleType,
downloadServer, and downloadFilename to the correct values. Then set the
downloadAdminStatus to either startDownload(1) or forceDownload(2).
downloadServer, and downloadFilename to the correct values. Then set the
downloadAdminStatus to either startDownload(1) or forceDownload(2).
To set up a provisioning style download so that the transponder will use the
module download information supplied by the provisioning server during boot
up or reboot, in the CM config file set the downloadModuleType to 2,
downloadServer, and downloadFilename to the correct values, and the
downloadAdminStatus to startDownload(1).
module download information supplied by the provisioning server during boot
up or reboot, in the CM config file set the downloadModuleType to 2,
downloadServer, and downloadFilename to the correct values, and the
downloadAdminStatus to startDownload(1).
Note: When using the provisioning style download, we strongly recommend that
you set the downloadAdminStatus to startDownload(1) in the CM config file. If the
downloadAdminStatus is set to forceDownload(2) in the CM config file, the
transponder will download the firmware to all modules on every reboot, even if they
are at the current version.
you set the downloadAdminStatus to startDownload(1) in the CM config file. If the
downloadAdminStatus is set to forceDownload(2) in the CM config file, the
transponder will download the firmware to all modules on every reboot, even if they
are at the current version.
OIDs Used for Module Firmware Download
The following OIDs are used for the Module Download Feature.
downloadServer (OID 1.3.6.1.4.1.2082.5.10.1.1.1) – The IP address of the TFTP
server where the module firmware file is located. If the TFTP server is
unknown and the OID is read, the returned value will be 0.0.0.0.
server where the module firmware file is located. If the TFTP server is
unknown and the OID is read, the returned value will be 0.0.0.0.
downloadModuleType (OID 1.3.6.1.4.1.2082.5.10.1.1.2) – The type of
download to be executed. Must be set to other(2). Type cm(1) is used for
other integrations and is not applicable in this instance.
download to be executed. Must be set to other(2). Type cm(1) is used for
other integrations and is not applicable in this instance.
downloadFilename (OID 1.3.6.1.4.1.2082.5.10.1.1.3) – The file name of the
software image to be loaded into the device. If the file is unknown and the
OID is read, the returned value will be (unknown).
software image to be loaded into the device. If the file is unknown and the
OID is read, the returned value will be (unknown).