Filter
Top Products
6-6
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 6 Firmware Management
Authoring Firmware Rules Templates
Authoring Firmware Rules Templates
Firmware rule templates in Cisco BAC are based on an XML schema file located at
<BPR_HOME>/rdu/templates/cwmp/schema/FirmwareTemplateSchema.xsd.
Firmware rules execute after processing an Inform from the device. They are also triggered after the
device issues a RequestDownload RPC.
A firmware rules template comprises:
• FirmwareTemplate—The root element, which can contain a Prerequisites tag, and one or more
named FirmwareRule elements.
Firmware rules are processed in order and, once a firmware rule matches, further rules are not
processed.
–
TemplateVersion—A TemplateVersion attribute has been introduced to support the different
firmware file types and the download of large firmware files. In the FirmwareTemplate
configuration file, the template version must be set to 3.0 to enable multi-instance object
support feature. If the template version is not provided or is set to 1.0, the new features will not
work as expected.
• Prerequisites—Contains conditions which must be met before the rules listed in the firmware rule
template are processed. Prerequisites may contain zero or one MaintenanceWindow, and zero or
more Expressions.
You can enable Expressions and MaintenanceWindow for firmware templates just as it is done for
configuration templates.
–
MaintenanceWindow—Describes the time range within which the firmware rule template is
valid for processing. For detailed information, see Prerequisites, page 5-9.
Replace contents and/or modify file
attributes/properties
You can replace an existing firmware image file
even if the file is associated to a firmware file
template using the API. The administrator user
interface, however, notifies of existing
associations before replacing a firmware image
file.
When a firmware image file’s contents are
replaced, IGS regenerates firmware rules for each
affected device and IGS distributes them to the
DPEs in the device’s provisioning group.
Subsequently, when the device contacts the DPE,
new rules are executed.
Replace file contents, modify file attributes and
properties, or both
Search by name, suffix, regex or file type -
- View templates in tabular form from the
administrator user interface
Templates appear in tabular form only if they do
not include conditionals.
Table 6-2 Firmware File Management Operations (continued)
Firmware Image File Firmware Rules Template