Filter
Top Products
6-2
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 6 Firmware Management
Firmware Management Mechanisms
This download can be initiated in various modes:
• Firmware-rule based, in which firmware rules may or may not allow the download of the file
requested by a device, or may download a different file. Firmware rules are executed whenever a
device connects to the DPE.
• The device may contact the DPE, based on periodic contact after a reboot or a specific action, such
as an user-initiated upgrade by clicking in the local user interface of the device. Regardless of how
the device contacts the DPE, the firmware rules, determine whether the upgrade is needed and is
allowed at the time of the particular interaction.
• Proxy, in which an external application invokes the API download operation for a specific device
and specifies the firmware image file location. The DPE then executes the Download RPC on the
device, causing the device to download the file from the specified location.
The download can occur in three ways:
–
Immediate, in which the DPE connects to the device and instructs the device to download the
firmware.
–
On-connect, in which the DPE instructs the device to download the firmware on next contact
with the device.
–
Asynchronous, in which the DPE instructs the device to download the firmware without
reserving the PACE thread at RDU. The operation result is sent to the API client in an
AyncOperationEvent.
The multiple instance object support is available in the firmware template, which facilitates discovering
the device parameters for multiple object instances. The parameter value associated with the discovered
object instances is matched with the parameter values specified in the template, and further firmware
rule is applied based on the match condition. For more information on multi-instance object support, see
Multi-Instance Object Support, page 4-5.
Firmware Management Mechanisms
This section describes CPE firmware-management mechanisms provided by Cisco BAC. These
comprise:
• Policy-based firmware management through firmware rules templates. See Firmware Rule
Templates, page 6-2, for detailed information.
• External firmware management through proxy operations. See Direct Firmware Management,
page 6-4, for detailed information.
Firmware Rule Templates
You use rule templates to set policy-based firmware management. The firmware rules templates are
XML documents written according to a published schema document. Each template must be stored in a
file and uploaded into Cisco BAC.
Each firmware rules template contains one or more rules which trigger firmware updates based on
specific conditions. Any number of such templates can be added to Cisco BAC, through the administrator
user interface or API. The template is associated with a Class of Service object using the
COS_CWMP_FIRMWARE_RULES_FILE property. Each device, in turn, is assigned to a Class of Service. (For
information on Cisco BAC object relationships, see Cisco BAC Device Object Model, page 4-2.)