Filter
Top Products
4-17
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 4 CPE Management Overview
Device Deployment in Cisco BAC
Cisco BAC provides two device deployment options, which can also be used in combination:
• Preregistered—The device record is added to the RDU before the device makes initial contact with
the DPE, also known as the ACS.
• Unregistered—The device makes contact with the DPE, before the device record is added to the
RDU.
Preregistered Devices
In this scenario, device data is preprovisioned into Cisco BAC, and the device is associated with a
specific Class of Service. The Class of Service can correspond to a service that the subscriber registered
for or a default configuration.
A preregistered device is preconfigured with certain parameters specific to the service provider. These
parameters are typically “burnt-in” as factory defaults.
Note If you reset the device to factory defaults, the settings on the device revert to the preburnt configuration,
and the device may go through the reconfiguration process.
Device data is preregistered in Cisco BAC. This is typically done through the API; alternatively, it can
be done using the administrator user interface.
Preconfiguration involves three important issues:
• The device must be able to establish network connectivity. For DSL devices, this typically involves
using auto-detection of ATM PVC and using PPP for authentication. The IP address is obtained
using PPP or using DHCP. Other devices typically use an existing internet connection and local
DHCP for address assignment.
• CPE must contact the configuration servers of the appropriate service provider; in other words, the
CPE must know the ACS URL. The ACS URL can be preburnt into the device (assigned) or
discovered using DHCP from the WAN side.
• The service provider must be able to associate the CPE with a specific subscriber. This process is
typically accomplished by the Operations Support Systems (OSS) application responsible for
subscriber registration. Cisco BAC is updated with appropriate data to provision device
configuration.
Unregistered Devices
In this scenario, no device data is prepopulated into Cisco BAC. Device data is added to Cisco BAC only
when the device first contacts a Cisco BAC server.
Cisco BAC allows unregistered devices (with no preconfigured parameters) to appear on a network and
gain default access. However, the lack of support for preregistering device data into Cisco BAC restricts
authentication options for unregistered devices, to using mechanisms based on certificates as opposed to
shared secrets.
The lack of preregistered data also means that Cisco BAC has to dynamically classify the devices and
determine the default configuration of a device.