Filter
Top Products
6-11
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 6 Firmware Management
Authoring Firmware Rules Templates
• FileSize—Specifies the size of the file. This is mandatory when the location is File System. The
FileSize can also be set to 0.
Examples
<InternalFirmwareFile>
<FileName>sample-firmware-image1.bin</FileName>
<DeliveryTransport>service http 1</DeliveryTransport>
<FileType>X CISCO_COM DLCImage</FileType>
<Location>File System</Location>
<FileSize>1234</FileSize>
</InternalFirmwareFile>
ExternalFirmwareFile
The ExternalFirmwareFile element describes the name of a firmware image file located at a remote
server. It comprises:
• FileURL—Specifies the URL for a firmware image file located at remote location.
• FileSize—Specifies the size of the firmware image file to be downloaded. The FileSize can also be
set to 0.
• AuthenticationCredentials—Specifies the username and password to use if HTTP authentication is
enforced by the file server. The username and password are transmitted using the Download RPC to
the device.
• FileType—Specifies the vendor specific download FileType element. This element is optional. The
default value is 1 Firmware Upgrade Image. The template version must be set to 2.0 to enable this
feature.
Note Ensure that you use SSL/TLS for CWMP to avoid transferring passwords in clear text.
You can use substitutable parameters to make the template-processing engine derive a
device-specific username and password from the device record when processing firmware
rules at the RDU.
Examples
<ExternalFirmwareFile>
<FileURL>http://imageserver.isp.com/sample-firmware-image.bin</FileURL>
<FileSize>3449</FileSize>
<AuthenticationCredentials>
<HttpUserName>test</HttpUserName>
<HttpPassword>changeme</HttpPassword>
</AuthenticationCredentials>
<FileType>X CISCO_COM DLCImage</FileType>
</ExternalFirmwareFile>
Sample Firmware Rules Template
The following is an example of a firmware template that supports the new feature like multi-instance
object support and features supported in earlier versions of firmware template.
<FirmwateTemplate templateVersion="3.0">
<Prerequisites>