Using the Broadband Access Center for Cable Administrator User Interface
This chapter describes the administration activities performed using the Broadband Access Center (BAC) administrator user interface. These activities mainly involve monitoring the actions of various BAC components including:
Note The procedures described in this chapter are presented in a tutorial manner. Wherever possible, examples
are included to illustrate the possible results of each procedure.
Managing Users
Managing users involves adding, modifying, and deleting users who administer BAC. The following procedures include illustrated examples to demonstrate these functions. For example purposes, let us assume that:
Note The adding and deleting of user functions can only be performed by a user who is logged in as the
Administrator.
Adding a New User
Adding a new user is a simple process of entering the user's name and creating a password. To add a new user:
Step 1 Click Users, from either the Main Menu or the Primary Navigation bar, and the Manage Users page appears. (See Figure 4-1.)
Figure 4-1 Example Manage Users Page
Step 2 Click Add and the Add User page appears. (See Figure 4-2.)
Figure 4-2 Add User Page
Step 3 Enter the new user's username and a password. In this example, the username is user_1.
Step 4 Confirm the new user's password and enter a description of the new user.
Tip Use the description field to identify the user's job or position; something that identifies the unique aspects of the new user.
Step 5 Click Submit when complete. Once the new user is added to the administrative database, the User Successfully Added page appears.
Step 6 Click the link indicated on this page and the Manage Users page appears with the new user added. (See Figure 4-3.)
Figure 4-3 Manage Users Page With a New User Added
After completing this procedure you will see that a new user has been added. It should be noted however, that the new user's password must be recorded and stored in a safe place. This helps to prevent the loss or theft of the password and possible unauthorized entry.
Modifying Users
You can modify both the password and description of any user entered into the administrative database. Changes to the password and description are the only modifications allowed.
Note Any nonadministrative user that is created in this application cannot be used to modify or delete the
admin user. (See Figure 4-3.)
To modify user properties:
Step 1 From either the Main Menu or the Primary Navigation bar, click Users and a Manage User page, similar to that shown in Figure 4-4, appears.
Figure 4-4 Example Manage Users Page
Step 2 Click the desired user name and the Modify User page appears. (See Figure 4-5.)
Figure 4-5 Modify User Page
Step 3 Make the necessary changes to the password and, if required, the user's description.
Step 4 Click Submit. The User properties have been modified page appears.
Step 5 Click the link indicated on this page and the Manage Users page appears with the appropriately modified user description. (See Figure 4-6.)
Note In the example shown in Figure 4-6, the
description of user_1 has changed from Assistant Administrator to System Admin. Regardless of the
change you want to make to the description, you must enter (and confirm) a password.
Figure 4-6 Manage Users Page With a Modified User Added
Deleting Users
You can delete any user, except an administrator, that appears in the Manager Users page. To delete a user:
Step 1 From either the Main menu or the Primary Navigation bar, click Users and a Manage User page, similar to that shown in Figure 4-7, appears.
Figure 4-7 Example Manage Users Page
Note The default user called admin cannot be deleted.
Step 2 Click the Delete icon corresponding to the user you want to delete and the delete user dialog box appears. In this example, you would click the Delete icon corresponding to Ace_Duffy.
Step 3 Click OK to delete the selected user, or click Cancel to return to the previous page. The User successfully deleted page appears.
Step 4 Click the link indicated on this page and the Manage Users page appears without the deleted user. (See Figure 4-8.)
Figure 4-8 Manage Users Page Showing a Deleted User
After completing this procedure, you will see that the user has been deleted.
Managing Devices
This section describes how to manage devices, including adding and deleting devices using BAC.
Device management is performed from the Manage Devices page (Figure 4-9). To access this page, click the Devices link on the Main Menu, or click Devices in the Primary Navigation bar.
Figure 4-9 Example Manage Devices Page
Table 4-1 identifies the fields and buttons appearing in the Manage Devices page, as shown in Figure 4-9.
Table 4-1 Manage Devices Page
Field or Button
Description
Search Type
Displays a drop down list that identifies all available search types. The available search criteria includes:
Class of service
DHCP criteria
Fully qualified domain name (FQDN)
IP address
MAC address
Owner ID
MAC Address or MAC Address wildcard
Although this field is initially identified as the MAC Address or MAC Address wildcard, this is only the default indication. The title of this field changes depending on the Search Type selected. See the "Search Types" section for supported search criteria and the instructions for their use.
Page Size
Specifies the maximum number of search results that will be displayed in the page's content area, after each search.
Click this button to regenerate the configurations of all devices having the specified search criteria. See the "Regenerating Device Configurations" section for additional information.
Note This button only appears when you choose either the DHCP or class of service search type.
Reset
Click this button to reboot the device.
Identifier
Identifies the MAC address of each device.
Device Type
Identifies the device type. This can include:
ATA186
ATA188
DOCSIS modems
Computers
PacketCable MTAs
Status
Identifies whether or not the device is provisioned. A provisioned device is one that has been registered using the API, or the administrative user interface, and has restarted on the network.
Step 1 From the Manage Devices page, click Add. The Add device page appears as shown in Figure 4-10.
Figure 4-10 Adding a Device Page
Step 2 Choose the device type and class of service, and complete the other fields on the page.
Step 3 Click Submit to add the device, or Reset to clear all fields.
Table 4-7 identifies the Add Device page fields and buttons shown in Figure 4-10.
Table 4-2 Adding a Device Page Fields and Buttons
Field or Button
Description
Device Type
Displays a drop down list that identifies the available device types you can create within BAC. Available selections include:
ATA 186
ATA 188
Computers
DOCSIS modems
PacketCable MTAs
MAC Address
This is the MAC address of the device being added.
Enter the MAC address of the device being added in this field. When doing this, you must ensure that you enter the commas and colons in the appropriate positions. For example:
1,6,00:00:00:00:00:AE
Host Name
Identifies the device's host. For example, from an FQDN of node.cisco.com, node is the host name.
Domain Name
Identifies the domain within which the host resides. For example, from an FQDN of node.cisco.com, cisco.com is the domain name.
Owner Identifier
Identifies the device using something other than the host name. This may be a user ID, an account number, or may be left blank.
Class of Service
Specifies the class of service that the device is to be provisioned with.
DHCP Criteria
Specifies the DHCP criteria that the device is to be provisioned with.
Property Name
Identifies the name of the custom or built-in device property.
Property Value
Identifies the value of the property.
Note To specify a CPE DHCP criteria for a DOCSIS modem, for use with
promiscuous computers, you must specify the property /provisioning/cpeDhcpCriteria. The value must
be a valid DHCP criteria.
Deleting Devices
Deleting devices is a simple process, but one that you should use carefully as the only way to undo the delete, is to restore a previously backed up database or by re-adding the device.
Step 1 From the Devices page, locate the device that you want to delete. You can use one of the search types for this purpose.
Step 2 Click the check box to the left of the desired device.
Step 3 Click Delete. The device record stored in the RDU database is removed.
Regenerating Device Configurations
It is sometimes necessary to change many different class of service or DHCP criteria parameters. When this happens, existing device configurations become stale and require regeneration of the configuration. To eliminate the need to manually regenerate each configuration, and reduce the potential for introducing errors, BAC provides a configuration regeneration service (CRS) that you can use to automatically regenerate all device configurations.
Device configurations are automatically regenerated whenever:
A class of service property is changed.
A DHCP criteria property changes.
An external file is replaced. This applies to files that are dynamic DOCSIS templates and are directly associated with a class of service.
New default classes of service or DHCP criteria are designated.
In addition, some configurations cannot be automatically regenerated, but must rely on manual regeneration using either the generationConfiguration() method or the administrator's user interface. Configurations that must be manually regenerated are those that become necessary whenever:
A technology default is changed.
The system defaults are changed.
A file that is included within another DOCSIS template is changed.
Note Regardless of how configurations are regenerated, they are not propagated to the devices until the device
is rebooted.
Searching For and Viewing Device Information
You can search for device information a number of different ways using BAC. Each search result that you generate also carries with it a View Details function. The details that are displayed are identical no matter which search method you use.
To search for a device type, from the Manage Devices page, click the Search Type button and a drop-down list, similar to that shown in Figure 4-11, appears. Subsequent search pages contain screen components that may be unique to the search type selected.
When the number of search results is greater than the selected page size, paging controls appear in the lower-left corner of the page. These let you scroll forward or backward one page at a time, or to select a specific page. Refer to the "Scrolling Backward and Forward" section for additional information.
Figure 4-11 Sample Manage Devices Search Types
Note A maximum of 1000 results are returned for any query with a maximum of 75
results displayed per screen. You can change the default maximum by modifying the
/adminui/maxReturned property, in <BPR_HOME>/rdu/conf/adminui.properties file, and then running
the bprAgent restart jrun command (located in the /etc/init.d/ directory) to restart the BAC JRun
component.
Search Types
You can search for specific devices using these functions:
This search method lets you identify devices that belong to any selected class of service. Figure 4-12 illustrates the results of a class of service search.
Figure 4-12 Class of Service Search Results Page
Table 4-3 identifies the fields shown in Figure 4-12. Refer to Table 4-1 for definitions of the function buttons on this page.
Table 4-3 Class of Service Search Page
Field or Button
Description
Class of Service (Type)
Select the desired class of service from this drop down list.
Page Size
Specifies the maximum number of search results displayed in the page's content area, after each search.
Note This function is also available on all other search criteria pages.
Search
Click this button to begin searching. When the search criteria is broad enough, or the database is large enough, there may be multiple pages showing the results of the search. The number of pages of search results are identified at the lower left corner of the page.
Note This function is also available on all other search criteria pages.
Identifier
Identifies all devices matching the search criteria. Each of the identifiers displayed has a link to another page from which you can modify the device.
Device Type
Identifies the device type. This can include:
ATA186
ATA188
DOCSIS modems
Computers
PacketCable MTAs
Status
Identifies whether or not the device is provisioned. A provisioned device is one that has been registered using the application programming interface (API), or the administrative user interface, and has booted on the network.
The DHCP criteria search lets you identify devices that belong to certain DHCP criteria. Figure 4-13 illustrates the DHCP criteria search page.
Figure 4-13 DHCP Criteria Search Page
Table 4-4 identifies the fields and buttons shown in Figure 4-13. Refer to Table 4-1 for definitions of the function buttons on this page.
Table 4-4 DHCP Criteria Search Page
Field or Button
Description
DHCP Criteria (Type)
Select the desired DHCP criteria from this drop down list.
Identifier
Identifies all of the devices meeting the DHCP criteria entered above. Each of the identifiers displayed has a link to another page from which you can modify the device.
Device Type
Identifies the device type. This can include:
ATA186
ATA188
DOCSIS modems
Computers
PacketCable MTAs
Status
Identifies whether or not the device is provisioned. A provisioned device is one that has been registered using the API, or the administrative user interface, and has booted on the network.
The fully qualified domain name (FQDN) search is useful when searching for devices that are identified through the FQDN assigned by the DNS Server, especially when the device MAC address is unknown.
Example:
The web site www.cisco.com is a fully qualified domain name. In this domain name, www is the host, cisco is the second level domain, and .com is the third level domain. Figure 4-14 illustrates the FQDN Search page.
Figure 4-14 FQDN Search Page
Table 4-5 identifies the fields and buttons shown in Figure 4-14. Refer to Table 4-1 for definitions of the function buttons on this page.
Table 4-5 FQDN Search Page
Field or Button
Description
FQDN or FQDN Wildcard
Enter all or part of a FQDN in this field. You can use an asterisk (*) as a wildcard character when searching for several IP addresses. Use these formats when using wildcard characters to search:
modem10.cisco.com
*.cisco.com
*.com
*
Note Cisco does not recommend using the last wildcard search (*) in systems that support hundreds of thousands, or more, devices.
Displays the FQDN that corresponds to the search criteria you entered in the FQDN field. Each identifier displays a link to another page, from which you can modify the device.
Device Type
Identifies the device type. This can include:
ATA186
ATA188
DOCSIS modems
Computers
PacketCable MTAs
Status
Identifies whether or not the device is provisioned. A provisioned device is one that has been registered using the API, or the administrative user interface, and has booted on the network.
The IP Address Search returns all devices on the network that currently have the specified DHCP leased IP address. Figure 4-15 illustrates the IP Address Search page.
Figure 4-15 IP Address Search Page
Table 4-6 identifies the fields and buttons shown in Figure 4-15. Refer to Table 4-1 for definitions of the function buttons on this page.
Identifies all of the devices meeting the IP address search criteria entered above. Each of the identifiers displayed has a link to another page from which you can modify the device.
Device Type
Identifies the device type. This can include:
ATA186
ATA188
DOCSIS modems
Computers
PacketCable MTAs
Status
Identifies whether or not the device is provisioned. A provisioned device is one that has been registered using the API, or the administrative user interface, and has booted on the network.
The MAC address search function is best used when you know the precise MAC address for a specific modem or when all devices with a specific vendor-prefix unambiguously identify the equipment vendor. Therefore, if you perform a MAC address search, you can identify, by the MAC address, the manufacturer and type of device. Figure 4-16 illustrates the MAC Address Search page.
Note The vendor-prefix is the first 3 octets of the MAC address. For example, for
MAC address 1,6,aa:bb:cc:dd:ee:ff, the vendor-prefix is "aa:bb:cc".
Figure 4-16 MAC Address Search Page
Table 4-7 identifies the MAC Address Search page fields and buttons shown in Figure 4-16.
Table 4-7 MAC Address Search Page
Field or Button
Description
MAC Address or MAC Address wildcard
Enter the MAC address in this field using any of these formats:
The full MAC address for any given device. For example:
1,6,00:00:00:00:00:AE
Only the vendor-prefix portion of MAC address. For example:
1,6,00:00:00:*
Note The asterisk wildcard character can be used in place of any MAC address octet.
An asterisk (*) to search for all devices. If you use this input option, a limited number of search results are returned to you. For example:
1,6,*
Note Cisco does not recommend using the last wildcard search ( 1,6,*) in systems that support hundreds of thousands, or more, devices.
Identifies all of the devices meeting the MAC address search criteria entered above. Each of the MAC addresses displayed has a link to another page from which you can modify the device.
Device Type
Identifies the device type. This can include:
ATA186
ATA188
DOCSIS modems
Computers
PacketCable MTAs
Status
Identifies whether or not the device is provisioned. A provisioned device is one that has been registered using the API, or the administrative user interface, and has booted on the network.
The owner ID can identify a device, it could identify the service subscriber's account number, or anything else that uniquely identifies that device. Figure 4-17 illustrates the results of an Owner ID Search.
Note Wildcard searches are not supported in the Owner ID search function.
Figure 4-17 Devices by Owner ID Search Results Page
Table 4-8 identifies the fields shown in Figure 4-17. Refer to Table 4-1 for definitions of the function buttons on this page.
Table 4-8 Owner ID Search Page
Field or Button
Description
Owner ID
Enter the assigned owner ID in this field before clicking the Search button.
Identifier
Identifies all devices matching the search criteria. Each of the identifiers displayed has a link to another page from which you can modify the device.
Device Type
Identifies the device type. This can include:
ATA186
ATA188
DOCSIS modems
Computers
PacketCable MTAs
Status
Identifies whether or not the device is provisioned. A provisioned device is one that has been registered using the API, or the administrative user interface, and has booted on the network.
You can view the details of any device identified in the search results. To view any device details:
Step 1 Perform whichever search activity you require to locate the device that you want details of.
Step 2 Click the Details icon ( ) corresponding to the device you want to view and a View Device Details page, similar to the one shown in Figure 4-18, appears.
Figure 4-18 Search Results Device Details Page
Note The information contained in the page shown in
Figure 4-18 is largely dependent on the
type of device you choose.
Specifies the type of device found by the search. Available types include:
ATA186
ATA188
Computer
DOCSIS modems
PacketCable MTAs
MAC Address
Identifies the devices MAC address.
FQDN
Identifies the fully qualified domain name for the selected device. For example, ACME.COM is a fully qualified domain name.
Host Name
Identifies the host. For example, from the FQDN description above, ACME is the host name.
Domain Name
Identifies the domain within which the host resides. For example, from the FQDN description above, .COM is the domain name.
Behind Device
Identifies the device that this device is behind.
Provisioning Group
Identifies the provisioning group to which the device is assigned.
DHCP Criteria
Identifies the DHCP criteria used. This is an active link that, if clicked, displays the appropriate Modify DHCP Criteria page.
CPE DHCP Criteria
Identifies the DHCP criteria used for customer premises equipment, when in the Promiscuous mode.
Device Properties
Identifies any properties, other than those displayed on this page, that can be set for this device. These are custom properties.
Device Provisioned State
Identifies whether the device is provisioned or not. A device is provisioned only when it is registered and has booted on the network.
Device Registered State
Identifies whether the device is registered or not.
Relay Agent Circuit Identifier
Identifies the relay agent circuit identifier of the device. This is equivalent to DHCP option 82, sub option 1.
Relay Agent Remote Identifier
Identifies the relay agent remote identifier of the device. This is the equivalent to the DHCP option 82, sub option 2.
Client Identifier
Identifies the client identification used by the device in its DHCP messages.
Client Request Host Name
Identifies the host name that the client requested in its DHCP messages.
Class of Service
Identifies the class of service assigned to this device.
Owner Identifier
Identifies the device. This may be a user ID, and account number, or may be blank.
DHCP Information
DHCP Inform Dictionary
Identifies additional information that the Network Registrar extensions send to the RDU when requesting the generation of a configuration. This is for internal BAC use only.
DHCP Request Dictionary
Identifies the DHCPDISCOVER or DHCPREQUEST packet details that were sent from the Network Registrar extensions to the RDU when requesting the generation of a configuration.
DHCP Response Dictionary
This field is for internal BAC use only; it should always be empty.
DHCP Environment Dictionary
This field is for internal BAC use only; it should always be empty.
Lease Information
IP Address
Identifies a device's IP address.
DHCP Lease Properties
Identifies the lease properties, this should always be empty.
Technology Specific Information
Note The technology specific information only identifies data that is germane to the technologies you are licensed to use.
XGCP Ports
Identifies the ports on which the gateway control protocol is active.
DOCSIS Version
Identifies the DOCSIS version currently in use.
Viewing Servers
This section describes the BAC administrator view server pages:
Identifies all DPEs registered with the BAC database. Each of the DPEs displayed in this screen is a link to another page that shows the details for that DPE. Click this link and the details screen appears.
Viewing Device Provisioning Engine Details
Figure 4-20 illustrates a sample View Device Provisioning Engine Details page. This page displays the current status for the selected DPE server, and includes information, such as the number of requests being handled and any error state flags.
Complete this procedure to view all BAC details:
Step 1 ChooseServers on the Primary Navigation bar.
Step 2 Choose DPEs from the Secondary Navigation bar. All connected DPEs appear in the List DPEs page similar to that shown in Figure 4-19.
Step 3 Locate the desired DPE, if more than one is displayed. You might have to use the scroll buttons, in the lower-left of the page, to find the required DPE.
Step 4 Click the link for the appropriate DPE and the details page, similar to that shown in Figure 4-20, appears.
Identifies the primary provisioning groups that the selected DPE belongs to. This is an active link that, if clicked, displays the Provisioning Group Details page for that provisioning group.
Secondary Provisioning Group(s)
Identifies the secondary provisioning group (provided that this DPE belongs to a secondary provisioning group) that the selected DPE belongs to.
PacketCable Enabled
Identifies whether or not the PacketCable voice technology is enabled on this DPE.
Properties
Identifies which properties have been assigned to this DPE.
Version
Identifies the version of DPE software currently in use.
Up Time (in seconds)
Specifies the total amount of time that the DPE has been operational since its last period of down time.
State
Identifies whether or not the DPE is ready for operations.
Note If this field reads Offline, the version, up time and all fields below, are not displayed.
Cache Details
Hits
Identifies the number of cache hits that have occurred since the last time the DPE was started.
Misses
Identifies the number of cache misses that have occurred since the last time the DPE was started.
Files
Identifies the number of cache files that are currently stored in the DPE.
Configurations
Identifies how many device configuration files are saved in cache.
TFTP Statistics
Packets Received
Identifies the number of TFTP packets that have been received by the selected DPE.
Packets Dropped
Identifies the number of TFTP packets that have been dropped due to the DPE being overloaded.
Packets Successful
Identifies the number of TFTP packets that have been transmitted successfully.
Packets Failed
Identifies the number of TFTP packets that have failed during transmission.
Time of Day Statistics
Packets Received
Identifies the number of Time of Day packets that have been received by the selected DPE.
Packets Successful
Identifies the number of Time of Day packets that have been transmitted successfully.
Packets Failed
Identifies the number of Time of Day packets that have failed during transmission.
PacketCable SNMP Statistics
SNMP Informs Successful
Identifies the number of inform requests that have been successfully sent.
SNMP Sets Successful
Identifies the number of successful SNMP sets.
Configuration Informs Successful
Identifies the number of SNMP informs received from PacketCable MTAs indicating that they were successfully provisioned.
Configuration Informs Failed
Identifies the number of SNMP informs received from PacketCable MTAs indicating that they failed to be provisioned.
Listing Network Registrar Extension Points
To list the Network Registrar extension points, from the Servers tab, click NRs. The List Network Registrar Extension Points page, similar to that shown in Figure 4-21, appears. This page lists the extension points for all Network Registrar servers that have been registered with the RDU, and are configured for use with BAC. Network Registrar servers automatically register with the RDU when those servers are started.
Figure 4-21 List Cisco Network Registrar Extension Points Page
Table 4-12 List Cisco Network Registrar Extension Points Page
Field or Button
Description
Network Registrar Extension Point
Identifies the Network Registrar extension points. Each of the extension points displayed has a link to another page that shows the details for that point.
Viewing Network Registrar Extension Point Details
Complete this procedure to view the extension point details of any selected Network Registrar server:
Step 1 Choose Servers on the Primary Navigation bar.
Step 2 Choose NRs from the Secondary Navigation bar. All connected Network Registrar servers appear in the List Cisco Network Registrar page similar to that shown in Figure 4-21.
Step 3 Locate the desired Network Registrar server if more than one is displayed. You might have to use the scroll buttons, in the lower-left of the page, to find the required server.
Step 4 Click the link to the desired extension point and the details page, similar to that shown in Figure 4-22, appears.
Table 4-13 View Network Registrar Extension Point Details Page
Field or Button
Description
Network Registrar Extension Point Details
Host Name
Displays the host name of the system running Network Registrar.
IP Address
Identifies the IP address of the Network Registrar.
Provisioning Group
Identifies the provisioning group for this Network Registrar servers. This is an active link that, if clicked, displays the Provisioning Group Details page for that provisioning group.
PacketCable Enabled
Identifies whether or not the PacketCable voice technology is enabled.
Properties
Identifies the properties that are applied to the selected Network Registrar.
Version
Identifies the extension point version currently in use.
Up Time
Identifies how long the Network Registrar extension point has been operational. This is indicated in hours, minutes, and seconds.
State
Identifies whether or not the extension point is operational.
Note If the state indicated is Offline, the Up Time, version, and extension point statistics are not displayed.
Network Registrar Extension Point Statistics
Packets Received
Identifies the number of packets that have been received.
Packets Ignored
Identifies the number of packets that were ignored.
Packets Dropped
Identifies the number of packets that were dropped.
Packets Successful
Identifies the number of packets that transferred successfully.
Packets Failed
Identifies the number of packets that failed to be transferred.
Device Provisioning Engine(s) Details
DPE
Identifies the IP address of the device provisioning engine.
Port
Identifies the DPE port number.
Type
Identifies whether this DPE is a primary or secondary DPE.
Status
Identifies whether or not the DPE is operational.
Listing Provisioning Groups
To list provisioning groups, click the Server tab, then click Provisioning Groups. The List Provisioning Groups page, similar to that shown in Figure 4-23, appears. This list identifies all of the provisioning groups within the system.
Identifies all provisioning groups. Each provisioning group displayed has a link to another page that shows the details for that group.
Viewing Provisioning Group Details
Complete this procedure to view all BAC provisioning group details:
Step 1 Choose Servers on the Primary Navigation bar.
Step 2 Choose Provisioning Groups from the Secondary Navigation bar. All configured provisioning groups appear in the Provisioning Groups page similar to that shown in Figure 4-23.
Step 3 Locate the desired provisioning group if more than one is displayed. You might have to use the scroll buttons, in the lower-left of the page, to find the required group.
Step 4 Click the provisioning group link and the details page, similar to that shown in Figure 4-24, appears.
Figure 4-24 View Provisioning Group Details Page
Table 4-15 identifies the fields and buttons shown in Figure 4-24. The fields described in Table 4-15 may include active links that, if clicked, will display the appropriate details page.
Table 4-15 View Provisioning Groups Details Page
Field or Button
Description
Name
Identifies the provisioning group name selected from the List Provisioning Groups page.
Primary Device Provisioning Engine(s)
Identifies the host names of the DPEs that are primary for this provisioning group.
Secondary Device Provisioning Engine(s)
Identifies the host names of the DPEs that are secondary for this provisioning group.
Network Registrar Extension Points
Identifies the host name of the Network Registrar server assigned to this provisioning group.
Viewing Regional Distribution Unit Details
The Regional Distribution Unit page lets you view the pertinent details of that RDU. To view the BAC RDU details:
Step 1 Choose Servers on the Primary Navigation bar.
Step 2 Choose RDU from the Secondary Navigation bar. The RDU details appear in the View Regional Distribution Unit page similar to that shown in Figure 4-25.
Figure 4-25 View Regional Distribution Unit Details Page
Identifies the host name of the system that is running the regional distribution unit.
Port
Identifies the RDU listening port number. While the default port number is 49187, the port number displayed in this field is the same as that entered as the Regional Distribution Unit Host/Port screen during installation.
IP Address
Identifies the IP address assigned to the RDU.
Properties
Identifies the RDU properties that are used for server configuration and control.
Version
Specifies the version of RDU software currently in use.
Up Time
Specifies the total amount of time that the RDU has been operational since its last period of down time.
State
Identifies whether or not the RDU is ready to respond to requests.
PACE Statistics
Batches Processed
Identifies how many individual batches have been processed while the PACE engine has been operating.
Batches Succeeded
Identifies how many individual batches have been successfully processed while the PACE engine has been operating.
Batches Dropped
Identifies how many batches have been dropped while the PACE engine has been operating.
Batches Failed
Identifies how many batches have failed processing while the PACE engine has been operating.
Average Processing Time
Identifies the average time, in milliseconds, that it takes to process the batch excluding the time it spends in the queue if RDU is too busy.
Average Batch Processing Time
Identifies the average time, in milliseconds, that it takes to process the batch including the time it spends in the queue if RDU is too busy.
Configuration Regeneration Statistics
State
Identifies whether or not the configuration regeneration service is ready to respond to requests.
Requests Processed
Identifies how many configuration regeneration requests have been processed.
Device Statistics
DOCSIS Modems
Identifies the number of DOCSIS modems are currently identified in the RDU.
Computers
Identifies the number of computers are currently identified in the RDU.
ATA 186/ATA 188
Identifies the number and type of ATA devices are currently identified in the RDU.
Packet Cable MTA
Identifies the number of MTAs are currently identified in the RDU.