Cisco Broadband Access Center for Telco and Wireless

Broadband Access Center for Cable Release Notes for Release 2.6

  • Viewing Options

  • PDF (285.3 KB)
  • Feedback
Release Notes for Broadband Access Center for Cable Release 2.6

Table Of Contents

Release Notes for Broadband Access Center for Cable Release 2.6



Related Documentation

System Components

System Requirements

Hardware Considerations

Device Provisioning Engine 590

New Features


Component Installation of a Solaris Device Provisioning Engine

API Installation Component Removed

RDU Migration From Previous Releases


Known Software Problems

Obtaining Documentation

Documentation CD-ROM

Ordering Documentation

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information

Release Notes for Broadband Access Center for Cable Release 2.6

January 30, 2004

These release notes for release 2.6 of Cisco Broadband Access Center for Cable (BACC), introduce a Solaris based software Device Provisioning Engine (DPE) and support for the CableHome technology.



The Broadband Access Center for Cable (BACC) product is a high-speed provisioning application that is easy to install, configure, and maintain. It provides a simple and easy way to deploy high-speed data, voice technology, and home networking technology services.

This provisioning API allows easy integration into an existing operations support system (OSS) environment.

Related Documentation

This release of the BACC product is supported by these related guides:

Broadband Access Center for Cable Administrator's Guide (Release 2.6)

Broadband Access Center for Cable Installation Guide (Release 2.5)

Device Provisioning Engine Recovery CD-ROM Release Notes for Release 2.5

Cisco Content Engine 500 Series Hardware Installation Guide

Cisco Network Registrar User's Guide (Release 6.0)

Cisco Network Registrar CLI Reference (Release 6.0)

System Components

The BACC comprises these major components:

The regional distribution unit (RDU), which is software that you install on your server(s).

The DPE, which is available in two versions:

A software DPE that is installed on a Solaris Sparc computer.

Software that comes pre-installed on rack mountable hardware known as the DPE-590.

A key distribution center (KDC) server used to authenticate MTAs and grant security tickets to them

Cisco Network Registrar DHCP extension points.

An application program interface (API) with which you can integrate BACC with other OSS and billing systems.

An administrator's user interface from which you can monitor and manage BACC.

A sample user interface (SUI) with which you can demonstrate BACC's power and flexibility.

System Requirements

You must have either the Solaris 8 or Solaris 9 operating system and Network Registrar installed on your system to successfully use the BACC software.

Note The use of Network Registrar version 6.1 is required and, although the BACC product will support operation under the Solaris 8 operating system, the Solaris 9 operating system is strongly recommended.

Hardware Considerations

The minimum hardware requirements needed to support both a lab and a fully deployed network are completely described in the Cisco Broadband Access Center for Cable Installation Guide.

Note Processing capacity, disk storage, and memory requirements depend on the size of the network deployment and the amount of log information needed.

Device Provisioning Engine 590

All installation and connection issues are discussed in the 500 Series installation guide that accompanies this product.

New Features

These are the new features built into the BACC 2.6 release:

Solaris Device Provisioning Engine

This BACC release supports the deployment of a DPE on Solaris Sparc computers running Solaris 8 or Solaris 9.

Note The DPE component now requires licenses to be installed at the RDU. If you have not yet received your licenses, contact your Cisco Systems representative before proceeding.

DHCP Option 122 Support

This BACC release now supports DHCP option 122, as specified and approved by both CableLabs and the IETF, for PacketCable EMTA configuration. Option 122, as specified in RFC 3495, replaces the Cablelabs defined DHCP option 177.

CableHome Support

This BACC release supports the non-secure version of this home networking technology. The CableHome technology is herein after referred to as home networking technology.

PacketCable Optimizations

The performance of PacketCable voice technology has been enhanced with this BACC release.

KDC Support

Starting with this BACC release, the KDC is now supported on multiprocessor Solaris computers.

Creation of Configuration File Templates From Binary Files

This features simplifies the process of developing templates through the introduction of a command line interface (CLI) tool that converts binary configuration files (either DOCSIS or PacketCable) into a BACC template.


As with previous versions of this product, BACC 2.6 has two forms of installation: Lab and component installations. While the differences are clearly described in the Cisco Broadband Access Center for Cable Installation Guide for release 2.5, the introduction of the new Solaris DPE affects the installation process.

Component Installation of a Solaris Device Provisioning Engine

During a component installation, you are prompted to select the components you want to install. With this BACC release, you can now install a DPE component.

Within the Lab Installation process, there are no differences to the installation. In the component installation however, you must select the DPE.

If, during DPE installation, the installation program detects the presence of a TFTP server running on the same computer that the DPE being installed on, the installation is immediately terminated and an error message appears on screen.

During the DPE installation, you are prompted to provide the locations of these directories:

Home Directory

Data Directory

Once you enter this information, refer to chapter 5 of the Cisco Broadband Access Center for Cable Installation Guide and perform the Configuring a Device Provisioning Engine for Data procedure, starting with step 2.

Caution After Solaris DPE installation is complete, you must configure the DPE using the CLI. Refer to the Cisco Broadband Access Center for Cable Administrator's Guide for these configuration instructions. Do not attempt to start the DPE until after you have completed this configuration.

API Installation Component Removed

The installation programs for previous BACC releases provided for the installation of an API component. The installation of this component has been removed in the BACC 2.6 release although the API is still available as in previous releases.

RDU Migration From Previous Releases

This release does not support migration of the RDU database from prior BACC releases. If a previous BACC version is detected during installation, the installation program prompts you to uninstall that version and remove the RDU database.


For information on BACC bugs, see the BACC26_BugList.html file in the docs/ subdirectory of the BACC CD-ROM or electronic distribution.

Known Software Problems

Table 1 identifies software issues that are known to exist in this release of BACC.

Table 1 Broadband Access Center for Cable Known Software Problems  



Any changes you make to the Network Registrar properties at the RDU, are not dynamically propagated to the Network Registrar extension points.

To correct this problem, restart the Network Registrar server so that the extensions re-read the defaults from the RDU.


When using option-177 to provision MTA devices, a lab installation may fail to return a DHCP offer.

During a lab installation, the installation program populates two optional properties (/pktcbl/dhcp/secondary and /pktcbl/dns/secondary) with empty values in the file. When these optional properties are present, the BACC Network Registrar extensions use empty values in options, if the configuration commands generated by the RDU reference them.

This causes the Network Registrar DHCP server to drop the DHCP offer packet because these values are required to be an IP address.

To correct this, edit the file and enter valid IP addresses for these two properties.

It is generally safe, in a lab installation, to make the secondary properties identical to the primary properties.


The RDU logs messages containing a null.

Currently this issue has no resolution.


When a DPE is configured with provisioning enabled on both interfaces, all UDP responses from the DPE may be directed to an interface other than the incoming request. This causes the external requester to reject the response.

To avoid this problem, use only one provisioning interface on each DPE.


When performing a search using the CPE DHCP Criteria, the results displayed may not be usable.

This search type displays results that include all modems and custom CPEs associated with that CPE DHCP criteria. These modems and custom CPEs are related to the default CPE DHCP Criteria even if they are not in the promiscuous mode. This is not updated if the default CPE DHCP criteria changes.

Do not rely on the search results obtained from CPE DHCP criteria searches, in order to retrieve modems associated with a given CPE DHCP criteria.


After booting a DOCSIS modem, with a computer behind it, and enabling the promiscuous mode, the computer and the modem should both receive the correct DHCP criteria and class of service. The computer should receive the system default for provisioned promiscuous DHCP criteria.

After disabling the promiscuous mode on the modem, the computer continues to receive the default provisioned promiscuous DHCP criteria rather than the default computer DHCP criteria.

The computers configuration must be manually regenerated to force it to receive the correct service level.


The BACC API does not validate the value for the cpeDHCPCriteria property. If an invalid DHCP criteria value is entered, a large number of errors will be generated in the RDU logs.

Only enter valid DHCP criteria names as the value for the cpeDHCPCriteria property. Avoid the use of punctuation and space characters.


The DPE port is susceptible to random packets.

The UDP port that the DPE is configured to listen on should be protected from outside access. For performance reasons, the DPE expects to receive only well-structured messages on this port.


When PACEConnection objects are continually created and released in the BACC API client, the API client eventually runs out of memory.

When integrating with the BACC API client, open the required number of PACEConnections once, and re-use them. There is no need to release a PACEConnection.

Obtaining Documentation

Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

You can access the most current Cisco documentation on the World Wide Web at this URL:

You can access the Cisco website at this URL:

International Cisco websites can be accessed from this URL:

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

All users can order annual or quarterly subscriptions through the online Subscription Store:

Click Subscriptions & Promotional Materials in the left navigation bar.

Ordering Documentation

You can find instructions for ordering documentation at this URL:

You can order Cisco documentation in these ways:

Registered users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

Nonregistered users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

You can submit e-mail comments about technical documentation to

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC Website

The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:

Accessing all the tools on the Cisco TAC website requires a user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL: