Filter
Top Products
4-2
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 4 CPE Management Overview
Cisco BAC Device Object Model
Cisco BAC Device Object Model
The Cisco BAC device object model is crucial in controlling the configuration and firmware rules that
are generated as instructions for the DPE to manage devices. This process occurs at the RDU, and is
controlled through named attributes and relationships.
The main objects in the device object model are:
• IPDevice—Represents a network entity that requires provisioning.
• Owner ID—Represents an external identifier for a subscriber.
• Device Type—Represents the type of the device.
• ProvGroup—Represents a logical grouping of devices serviced by a specific set of DPEs.
• Class of Service—Represents the configuration profile to be assigned to a device.
• File—Serves as a container for files used in provisioning that include templates and firmware
images.
• Group—Is a customer-specific mechanism for grouping devices.
Common among the various objects in the Cisco BAC device data model are:
• Name. For example, Gold Class of Service
• Attributes. For example, Device ID and a fully qualified domain name (FQDN)
• Relationships. For example, the relationship of a device to a Class of Service
• Properties. For example, a property which specifies that a device must be in a provisioning group.
See Figure 4-1 for a description of the interaction between the various objects in the device data model.
Figure 4-1 Device Object Model
In the Cisco BAC device object model, the IPDevice is related to the Class of Service, the Provisioning
Group, and the Device Type. The Class of Service is then related to the Configuration Template and the
Firmware Rules Template. Files can be related to one another, such as the firmware rules template being
related to the firmware image.
158269
Prov Group Class of Service
0..*
0..*
0..*
0..*
File
Device Type Owner ID
0..*
0..*
0..* 0..2
1..1
Group
0..* 0..n
1..1
1..1
0..*
1..*
0..1
Group Type
0..n
1..1
IPDevice