Release Notes for Cisco Broadband Access Center 3.5.3

Table Of Contents

Release Notes for Cisco Broadband Access Center 3.5.3

Contents

Introduction

System Requirements

System Hardening

Installing Cisco BAC 3.5.3

Upgrading from Cisco BAC 3.5.2 or 3.5.2.1

Upgrading the RDU

Upgrading the DPE

Caveats

Resolved Issues

Known Issues

Abbreviations and Definitions

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco Broadband Access Center 3.5.3

---

Revised: June 1, 2012, OL-24214-01

Cisco Broadband Access Center (Cisco BAC) 3.5.3 resolves some of the open defects in Cisco BAC 3.5, 3.5.1 and 3.5.2.

This document provides information on upgrade procedures from earlier versions to 3.5.3 and the bug fixes being addressed in this release.

See the Cisco BAC 3.5 documentation for complete information about the product. You can access the Cisco BAC 3.5 product documentation at:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps529/tsd_products_support_series_home.html

Contents

This document includes the following sections:

•Introduction

•System Requirements

•System Hardening

•Installing Cisco BAC 3.5.3

•Upgrading from Cisco BAC 3.5.2 or 3.5.2.1

•Caveats

•Abbreviations and Definitions

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

Introduction

Cisco Broadband Access Center, referred to as Cisco BAC through out this document, automates the tasks of provisioning and managing customer premises equipment (CPE) in a broadband service provider network. The product provides a simple and easy way to deploy high-speed data, voice technology, and home networking devices.

With the high-performance capabilities of Cisco BAC, you can scale the product to suit networks of virtually any size, even those with millions of CPE. It also offers high availability, made possible by the product's distributed architecture and centralized management.

Cisco BAC supports provisioning and managing of 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.

Cisco BAC supports devices based on the TR-069, TR-098, TR-104, and TR-106 standards. These devices include Ethernet and ADSL gateway devices, wireless gateways, VoIP ATAs, and other devices compliant with CWMP.

This release supports provisioning of IOS routers. For the Cisco BAC Architecture and system components, see Cisco Broadband Access Center Administrator's Guide, Release 3.5.

System Requirements

For information on installation and operating system requirements, see Installation Guide for Cisco Broadband Access Center, Release 3.5.

System Hardening

This Cisco BAC release has undergone comprehensive security testing. The objective of this security testing was to identify and eliminate any security vulnerabilities pertaining to Cisco BAC and its supporting software and hardware. This release was also tested for protocol robustness to define application stamina when exposed to Denial of Service attacks and protocol irregularities.

For information on the System Hardening, see Cisco Broadband Access Center Hardening Guidelines, Release 3.5.

Installing Cisco BAC 3.5.3

For installation information, see Installation Guide for Cisco Broadband Access Center 3.5.

Upgrading from Cisco BAC 3.5.2 or 3.5.2.1

You must apply the Cisco BAC 3.5.3 upgrade on your existing Cisco BAC 3.5.2 or 3.5.2.1 RDU and Cisco BAC 3.5.2 or 3.5.2.1 DPE. The Cisco BAC 3.5.3 installation instructions in this section are based on the assumption that you have Cisco BAC release 3.5.2 or 3.5.2.1 already installed.

Upgrading the RDU

To apply this release on your Cisco BAC RDU server:

---

Step 1 Untar the file, 353Upgrade.tar.

Step 2 Go to the /upgrade353 directory.

Step 3 Go to the /bin directory.

Step 4 Run the ./353-upgrade-rdu.sh script.

The Cisco BAC watchdog is stopped by the script.

The following message appears confirming the upgrade for Cisco BAC 3.5.3:

RDU Upgrade for BAC 3.5.3 Completed Successfully

Step 5 Start the Cisco BAC watchdog agent. To do this, run the following command:

/etc/init.d/bprAgent start

---

Upgrading the DPE

To apply this release on your Cisco BAC DPE server:

---

Step 1 Untar the file, 353Upgrade.tar.

Step 2 Go to the /upgrade353 directory.

Step 3 Go to the /bin directory.

Step 4 Run the ./353-upgrade-dpe.sh script.

The Cisco BAC watchdog is stopped by the script.

The following message appears confirming the upgrade for Cisco BAC 3.5.3:

DPE Upgrade for BAC 3.5.3 Completed Successfully

Step 5 Start the Cisco BAC watchdog agent. To do this, run the following command:

/etc/init.d/bprAgent start

---

Note For details on how to configure Cisco BAC 3.5.3, see the document Cisco_Broadband_Access_Center_353_CPEaaS_Extension_Configuration.pdf available in the BAC_3.5.3_DPE_Extensions_SolarisK9/Documentation directory of the software bundle.

---

Caveats

This section lists the defects that were either fixed in Cisco BAC 3.5.3 or are still open.

Resolved Issues

Table 1 lists the bugs resolved in this Cisco BAC3.5.3 release.

Table 1 Resolved Issues

Bug ID	Summary
CSCtq86110	ACS (DPE) does not handle INFORM session with empty event in header.
CSCtr85572	BAC should handle INFORM without event code.
CSCts54726	BAC should allow to configure Error Option in set configuration file.
CSCtu09461	Defect in IOS config command splitting that exceeds 3000 character limit.

Known Issues

Table 2 identifies known issues in this Cisco BAC 3.5.3 release.

Table 2 Known Issues

Bug ID	Summary
CSCtk64957	Stack trace Exception on admin UI on device page.
CSCts69128	Length for Error option and target options not validated

Abbreviations and Definitions

Table 3 Abbreviations and Definitions

Term	Description
AC	Access Controller, also known as FGW
ACE	Application Control Engine — A Cisco load-balancing and SSL acceleration device, which is available as a blade for Cisco routers as well as stand-alone appliance.
BAC	Broadband Access Center — A mass-scale CPE provisioning and management product, which also implements TR-069 (auto configuration server - ACS - functions).
CLI	Command Line Interface such as the one exposed by the Cisco BAC DPE.
CPE	Customer Premises Equipment — A device such as an FAP, which is deployed at customer's premises.
DPE	Device Provisioning Engine — Distributed server in Cisco BAC architecture, which interfaces with CPE.
FAP	Femtocell Access Point — A device that functions as a mini 3G cell tower in customer home and backhauls cellular calls via customer's internet connection through the FGW.
FCAPS	Fault, Configuration, Accounting, Performance, and Security.
FGW	Femtocell Gateway, also known as AC. Each Femtocell Gateway (FGW) supports a large set of Femtocell Access Points (FAP). Each FAP is configured to associate with a specific FGW, and each FGW must be specifically provisioned to authorize and service each FAP.
FPG	Femto Provisioning Gateway — An application developed by SA, which provides Femto provisioning workflow glue between AT&T systems and Cisco BAC NB API.
GPS	Global Positioning Satellite — It is used to verify the location of the FAP.
IMSI	International Mobile Subscriber Identifier. This is the SIM card ID.
Network Listen	A radio network test performed by the FAP. A measure of received code power from the neighborhood cells, used to pick the code with the least interference as well as to assist in the location verification.
Polygon	A Polygon is a geo-political county which is significant for provisioning differentiation. A device is determined to be in a given Polygon based on its location.
RDU	Regional Distribution Unit. Central server in Cisco BAC architecture, which exposes NB API.
SA	Scientific Atlanta is a division of Cisco. SA is the systems integrator for AT&T Femtocell solution.
SSL	Secure Socket Layer. Authentication and encryption protocol originally defined by Netscape. This specification has been superseded by IETF standard for TLS protocol, which is based on SSL 3.0 and is compatible with SSL 3.0.The term SSL is used to refer to both SSL 3.0 and TLS 1.0 since they are compatible and both are typically implemented.
White list	Access control list that specifies which cell phones can register with FAP.

Related Documentation

This release of the Cisco BAC product is supported by the following documents:

•Installation Guide for Cisco Broadband Access Center, Release 3.5

•Cisco Broadband Access Center Administrator's Guide, Release 3.5

•Integration Developer's Guide for Cisco Broadband Access Center, Release 3.5

•Cisco Broadband Access Center DPE CLI Reference, Release 3.5

•Cisco Broadband Access Center 3.5 Third Party and Open Source Copyrights

•Release Notes for Cisco Broadband Access Center, 3.5

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

---

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2012 Cisco Systems, Inc. All rights reserved.