Cisco Cisco Broadband Access Center Telco Wireless 3.8 Release Notes
2
Cisco Broadband Access Center 3.8 Release Notes
OL-27175-01
System Components
Cisco BAC
enables you to provision and manage CPE by using the Broadband Forum’s CPE WAN
Management Protocol (CWMP), a standard defined in the TR-069 specification. Cisco BAC integrates
the capabilities defined in TR-069 to increase operator efficiency and reduce network-management
problems.
the capabilities defined in TR-069 to increase operator efficiency and reduce network-management
problems.
Cisco BAC supports devices based on the TR-069, TR-098, TR-104, TR-106, and TR-196 standards.
These devices include Ethernet and ADSL gateway devices, wireless gateways, VoIP ATAs, DLC, and
other devices that are compliant with CWMP. For details about the features supported in Cisco BAC 3.8,
see
These devices include Ethernet and ADSL gateway devices, wireless gateways, VoIP ATAs, DLC, and
other devices that are compliant with CWMP. For details about the features supported in Cisco BAC 3.8,
see
section.
System Components
Cisco BAC comprises:
•
A Regional Distribution Unit (RDU) that is a software that you install on your server. The RDU is
the primary server in a Cisco BAC deployment. Through its extensible architecture, the RDU
supports the addition of new technologies and services.
the primary server in a Cisco BAC deployment. Through its extensible architecture, the RDU
supports the addition of new technologies and services.
•
The Device Provisioning Engine (DPE) that is a software that you install on your server. The DPE
server handles all device interactions for the RDU.
server handles all device interactions for the RDU.
•
An administrator user interface through which you can monitor and manage Cisco BAC.
•
A Java provisioning application programming interface (API).
You can use this to integrate
Cisco BAC into an existing operations support-system environment. You can use the provisioning
API to register devices in Cisco BAC, assign device configuration policies, run CWMP
API to register devices in Cisco BAC, assign device configuration policies, run CWMP
operations
on the device, and configure the entire Cisco BAC provisioning system.
•
Cisco Network Registrar extensions (CNR extensions), are the links between Cisco BAC and Cisco
Network Registrar. You should install this component on all Cisco Network Registrar servers in your
Cisco BAC environment. If you are deploying Cisco BAC in a failover environment, ensure that you
install the extensions on the failover servers, as well.
Network Registrar. You should install this component on all Cisco Network Registrar servers in your
Cisco BAC environment. If you are deploying Cisco BAC in a failover environment, ensure that you
install the extensions on the failover servers, as well.
•
A STUN server that supports a UDP based Connection Request mechanism defined in TR069 Annex
G to allow Cisco BAC to initiate a session with a CPE that is operating behind a NAT Gateway.
G to allow Cisco BAC to initiate a session with a CPE that is operating behind a NAT Gateway.
•
The Cisco Access Register (CAR) extensions are the links between Cisco BAC and Cisco Access
Registrar. You should install this component on all Cisco Access Registrar servers in your Cisco
BAC environment. If you are deploying Cisco BAC in a fail-over environment, ensure that you also
install the extensions on the fail-over servers.
Registrar. You should install this component on all Cisco Access Registrar servers in your Cisco
BAC environment. If you are deploying Cisco BAC in a fail-over environment, ensure that you also
install the extensions on the fail-over servers.
System Requirements
You must have the Solaris 10 or 11, or Linux 5.x or 6.1 operating system installed on your system to use
the Cisco BAC software. For information on installation, see the
the Cisco BAC software. For information on installation, see the