Using the Administrator User Interface

This chapter describes the administration tasks performed from the Broadband Access Center (BAC) administrator user interface. These tasks mainly involve monitoring the actions of various BAC components and include:

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.
For details on server configurations, see Configuring Broadband Access Center, page 17-1.

User Management

Managing users involves adding, modifying, and deleting users who administer BAC. Depending on your user type, you can use this menu to add, modify, and delete users. This menu displays all users configured to use BAC and identifies their user types.

There are three types of BAC users: an Administrator, a Read/Write user, and a Read-Only user. Each has different levels of access, with unique permissions to ensure access control and the integrity of provisioning data.

The assigned user type appears near the top right corner of every screen on the administrator user interface.

Administrator

BAC recognizes only one administrator and allows this user to view, add, modify, delete device data, and create other users. As an Administrator, you can also change other users' permissions from Read/Write to Read Only, and vice-versa. In addition, you have the ability to change the passwords of any other user type.

Read/Write User

As a Read/Write user, you can perform the same functions as the administrator except creating other users, changing the user types of others, or changing their passwords. Read/Write users can change their own password.

Read-Only User

As a Read-Only user, you have basic access including the ability to change your password and to view, but not change, device data. You cannot perform any action that is considered disruptive. You cannot, for example, perform reset or regenerate instructions.

Note You can add and delete users only if you are 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. However, while creating a new user you do have to determine which type of user it will be: a Read/Write user or a Read-Only user. BAC comes with one Administrator user already created; you cannot create an Administrator as a new user.

Step 2

The Manage Users page appears. (See Figure 16-1.) Click Add to display the Add User page.

Step 4

Confirm the new user's password, and select whether the new user's role is to be read only or read/write. See User Management, for complete descriptions of each user type.

Tip

Use the description field to identify the user's job or position, something that identifies the unique aspects of the new user.

Note

The new user's password must be recorded and stored in a safe place. This helps prevent loss or theft of the password and possible unauthorized entry.

Modifying Users

Although any user type can modify their password and user description, only the administrator can modify any other user's information.

Step 2

The Manage User page appears. Click the correct user name to display the Modify User page for that user.

Step 3

Make the necessary changes to the password, user type (provided that you are logged in as the Administrator), and the user's description.

Deleting Users

Only the administrator can delete any other user that appears in the Manage Users page. You cannot delete the default user, called admin.

Step 2

The Manage User page appears. Click the Delete icon (

) corresponding to the user you want to delete.

Device Management

•

Search for a specific device or for a group of devices that share criteria that you specify. See Searching for Devices.

•

View device data, such as configuration, properties, discovered data, and faults. See Viewing Device Details.

•

Perform various operations, such as an IP Ping, and live data retrieval, on the device to gain more insight. See Performing Operations on Device.

Manage Devices Page

The Manage Devices page appears when you click Devices on the Main menu or the Primary Navigation bar. This page, shown in Figure 16-2, contains the fields and controls necessary to perform all device management functions.

Searching for Devices

By using BAC, you can search for device information in a number of different ways.

To select the search type, from the Manage Devices page, click the Search Type drop-down list. Subsequent search pages contain screen components that may be unique to the search type selected.

The Manage Device page utilizes two separate but related areas to generate search results that let you perform many device management functions. These areas are the Search Type drop-down list, which defines which search to perform, and search value field, which qualifies the search type. You can perform these searches:

•

Device Identifier Search—Searches by using the device ID. This search function supports wildcard searching at the end of the search string. You can also look up a single device by providing a complete device ID of a specific device.

•

FQDN Search—Searches by using the fully qualified domain name (FQDN) associated with the device.

•

Owner ID search—Searches by using the owner ID associated with the device. The owner ID may identify the service subscriber's account number, for example. This search function does not support wildcard searching.

•

Registered Class of Service Search—Searches by using the Class of Service that a device has been provisioned with.

•

Related Class of Service Search—Searches by using both the registered and selected Class of Service.

•

Selected Class of Service Search—Searches by using the Class of Service selected by the RDU for a device that, for one reason or another, cannot retain its registered Class of Service.

Some searches that you can perform allow the use of a wildcard character (*) to enhance the search function. BAC provides specific wildcards for each search, as described in Table 16-1.

Table 16-1 Searches Supported for Device Management
Menu Search	Search Type Options
Device Identifier Search	Full Device Identifier or partial Device Identifier followed by a wildcard asterisk () character at the end of the string. For example, to search for a device with the ID 0010BF-ZAA001A00001, you can try 0010BF-, but searching by using *-ZAA001A00001 does not yield results.
FQDN Search	Full FQDN or partial FQDN string beginning with an wildcard asterisk () character. For example, to search for a device with the FQDN IGW-1234.ACME.COM, you can try: •.acme.com •.com •
Group Search	Group Name (Group Type) •Drop-down list Full Device Identifier or partial Device Identifier followed by a wildcard asterisk (*) character at the end of the string.
Owner ID Search	Owner ID Wildcard searches are not supported. You must enter the complete owner ID.
Registered Class of Service Search	Class of Service (Type) •Drop-down box
Related Class of Service Search	Class of Service (Type) •Drop-down box
Selected Class of Service Search	Class of Service (Type) •Drop-down box

In addition, a Page Size drop-down lets you limit the number of search results displayed per page. You can select 25, 50, or 75 results for display. 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 controls let you scroll forward or backward one page at a time, or to select a specific page.

Note A maximum of 1,000 results are returned for any query, with a maximum of 75 results displayed per page. You can change the default maximum by modifying the /adminui/maxReturned property, in the BPR_HOME/rdu/conf/adminui.properties file, and then running the bprAgent restart tomcat command (located in the /etc/init.d/ directory) to restart the BAC Tomcat component.

Device Management Controls

These buttons are located directly below the search function fields and are generally used in conjunction with the search function. For example, you might search for devices belonging to a specific group of devices in order to perform some sort of management function. The following buttons are available, although each management function may not be available depending on the search type used.

The Add button lets you add a new device to the RDU database. See Adding Device Records, for the appropriate instructions.

The Delete button lets you delete any selected device(s) from the RDU database. See Deleting Device Records, for the appropriate instructions.

Use the Regenerate button to force immediate regeneration of instructions for selected device(s).

The Relate button lets you associate a device (by using its Device ID) with a specific group (referred to as Node in the API).

The Unrelate button cancels the relationship between a selected device and the group that the device is currently related to.

Searching for devices returns results under the following headings or links that appear on the page:

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.

Displays all available details for the selected device. See Viewing Device Details, for additional information.

Viewing Device Details

To view any device details, click the View Details icon (

) corresponding to the device you want to view, and the Device Details page appears. Figure 16-3 provides a sample Device Details page.

Table 16-2 Device Details Page
Field or Button		Description
Device Details
Device Type		Identifies the device type.
DeviceID		Identifies the device identifier.
FQDN		Identifies the fully qualified domain name for the selected device. For example, IGW-1234.ACME.COM is a fully qualified domain name.
Host Name		Identifies the host. For example, in the FQDN description above, IGW-1234 is the hostname.
Domain Name		Identifies the domain within which the host resides. For example, in the FQDN description above, ACME.COM is the domain name.
Provisioning Group		Identifies the provisioning group to which the device has been pre-assigned or assigned automatically.
Home Provisioning Group		Identifies the provisioning group to which the device should belong.
CPE Password		Identifies the password used to authenticate the device when establishing a connection to BAC. This password is used only for HTTP-based authentication of the customer premises equipment (CPE). For security purposes, it returns a string with asterisk (*) characters regardless of the actual value unless the password has not been set, in which case an empty value is displayed.
Connection Request User Name		Identifies the username used to authenticate a ConnectionRequest from BAC to the CPE.
Connection Request Password		Identifies the password used to authenticate a ConnectionRequest from BAC to the CPE. For security purposes, this parameter returns an empty string regardless of the actual value.
Device Properties		Identifies any properties, other than those that appear on this page, that can be set for this device. This field includes the display of custom properties.
Registered Class of Service		Identifies the Class of Service assigned to this device. If a different Class of Service has been selected for the device by extension, an additional field with Selected Class of Service appears.
Owner Identifier		Identifies the device. This may be a user ID, and account number, or may be blank.
CPE Configuration Revision		Identifies the configuration rules revision number, which is set for the device ParameterKey following a successful configuration synchronization.
CPE Firmware Rule Revision		Identifies the firmware rules revision for this CPE.
Related Group Name (Group Type)		Identifies the group(s) name and type to which this device is related. See Group Management, for additional information.
Troubleshooting		Identifies if CPE troubleshooting is enabled or disabled. Note If troubleshooting is enabled, a View Troubleshooting Log link appears on this page.
View Device History Details		Provides a link to the history of configuration changes on the CPE.
Discovered Parameters Note This section includes any parameters discovered from the device. This section does not appear unless discovered parameters are available for the device. For details on how to configure discovered parameters, see Discovering CPE Parameters.
Has Routable IP Address		Identifies if a device is generally reachable; that is, if the source IP address of the last request was the same as the WAN IP address reported by the CPE in the Inform message.
Inform.DeviceId.Manufacturer		Identifies the manufacturer of the CPE reported in the last Inform message.
Inform.DeviceId.ManufacturerOUI		Identifies the unique identifier of the manufacturer of the CPE reported in the last Inform message.
Inform.DeviceId.ProductClass		Identifier a manufacturer's product or class of product over which the SerialNumber parameter is unique. The device reports this parameter in the Inform message.
InternetGatewayDevice.DeviceInfo.HardwareVersion		Identifies the hardware version of the CPE.
InternetGatewayDevice.DeviceInfo.ModelName		Identifies the model name of the CPE.
InternetGatewayDevice.DeviceInfo. SoftwareVersion		Identifies the software version currently installed on the CPE. The software version is also known as firmware version.
InternetGatewayDevice. ManagementServer.ParameterKey		Specifies the value of the ParameterKey reported by the device in the last Inform message or last set by the DPE, whichever occurred last.
Faulty Device List Note This information is displayed only if faults occur at the devices. For more information, see Device Faults.
Last Fault Time		Specifies the date and time that a recurring fault occurred for this device.
Location		Specifies the server on which this fault occurred.
Fault Description		Provides a description of the recurring fault.

Managing Devices

The Devices menu lets you add devices to the RDU databases and update preprovisioned data. Device management includes:

•

Relating selected devices to management objects, such as Provisioning Group, Class of Service, Group, and so on.

•

Executing operations on devices. These operations are actually performed on the device and include:

This section describes how to perform the various device management functions on new or existing devices.

Adding Device Records

Step 2

The Add Device page appears. Choose the device type and Class of Service, and complete the other fields on the page.

Step 3

In addition to the fields described earlier in this section, you can optionally add new values for existing property name/value pairs.

•

Property Name—Identifies the name of the custom or built-in device property.

Step 4

Click Submit to add the device, or Reset to clear all fields.

Modifying Device Records

Step 1

From the Manage Devices page, click the Identifier link corresponding to the correct device.

Step 2

The Modify Device page appears. Enter the data in the correct field. You can modify any existing property name/value pairs by clicking Add, or delete any of them by clicking the Delete button.

Step 3

Click Submit to save the changes made to this device, or Reset to clear all fields.

Deleting Device Records

Deleting device records is a simple process, but one that you should use carefully. To undo the delete, you must restore a previously backed up database or re-add the device.

Note See Database Restore, for additional information if restoration of a backed-up database becomes necessary.

Step 1

From the Manage Devices page, locate the device that you want to delete. You can use one of the search types for this purpose.

Viewing Device History

Step 1

From the Manage Devices page, locate the device whose history you want to view. You can use one of the search types for this purpose.

Step 3

The Device Details page appears. Against View Device History Details, click the View Details icon.

Regenerating Device Instructions

The Regenerate button or API operation force immediate regeneration of instructions for the device. These instructions are sent to the DPEs in the device's provisioning group. Normally, the process of regenerating the instruction is automatically triggered following changes to device, Class of Service, or other such impacting changes. However, after a change to a Class of Service, the system takes time to regenerate instructions for all devices. This button can be used to expedite regeneration of instructions for a given device. This may be desirable during proactive troubleshooting.

•

The provisioning group object is changed via the administrator user interface or the API.

Some instructions cannot be automatically regenerated because the BAC system cannot determine if the change impacts device instructions. In such cases, you must manually regenerate instructions by using the generationConfiguration() method or the administrator user interface. Instructions that must be manually regenerated are those that become necessary whenever:

Note Regardless of how instructions are regenerated, they are not propagated to the devices until the device configuration is activated, that is, the device contacts the DPE either on schedule or as a result of a connection request initiated from the DPE.

Relating and Unrelating Devices

You can define any number of arbitrary groups. The Relate function lets you associate a device to a specific group, which is in turn associated with a specific group type.

Relating a Device to a Group

Note You can relate devices to group(s) only one by one via the administrator user interface.

Step 1

From the Manage Devices page, locate the device which you want to relate to a group. You can use one of the search types for this purpose.

Step 2

Check the check box corresponding to the device Identifier, and click the Relate button.

Step 3

The Relate Device to Group(s) page appears. Select the Group Type from the drop-down list and the Group(s) from the list of defined groups.

Note

To select multiple groups from the Group list, press Control or Shift.

Note

To verify if the device has been added to the group, click the View Details icon corresponding to the device. On the Device Details page that appears, check the status against Related Group Name (Group Type).

Unrelating a Device from a Group

Note You can relate devices to group(s) only one by one via the administrator user interface.

Step 1

From the Manage Devices page, locate the device which you want to unrelate from a group.

Step 2

Check the check box corresponding to the device Identifier, and click the Unrelate button.

Step 3

The Unrelate Device from Group page appears. From the list of defined Group(s), select the group(s) from which you want to unrelate the device.

Note

To select multiple groups from the Group list, press Control or Shift.

Searching Device(s) in a Group

Step 1

From the Manage Devices page, select the Group Search option from the drop-down list under Search Type.

Step 2

The Group Name (Group Type) and the Device Identifier options appear. From the Group Name (Group Type) drop-down list, select the Group Name of the device(s) which you want to search.

Step 3

Enter a device ID in the Device Identifier field, or use a wildcard (*).

Performing Operations on Device

•

Reboot—Enables you to reboot the device. This operation is primarily intended for diagnostic purposes.

•

Request Connection—Instructs the device to establish a CWMP session with BAC.

•

Factory Reset—Enables you to reset a preregistered device settings to its original factory settings.

You can choose the parameters that you want to view for this device operation by selecting from the options under the Parameter List File drop-down box. Each parameter list is an XML file that details the parameters each file will return; click the View Details icon to view the parameters.

You can also define the parameters that you want to be retrieved in parameter lists. BAC provides a sample list of live data templates which specify various parameters to be read during a view live data query.

•

Ping Diagnostic—Enables you to perform an IP ping diagnostics test from the device to any host.

Note For all of the above operations, if the device is not reachable, an error message appears.

•

Force Firmware Upgrade—Enables you to force a device to update its firmware on next contact regardless of the MaintenanceWindow restrictions set in the firmware rules.

•

Force Configuration Synchronization—Enables you to force an individual device to synchronize its configuration regardless of the current configuration version on the device.

Note The operations forcing a firmware upgrade or a configuration synchronization take effect on the next device contact with the autoconfiguration server (ACS).

Performing a Reboot

Step 1

From the Devices > Manage Devices page, locate the correct device.

Step 3

The Device Operations page appears. From the drop-down list under Device Operation, select Reboot.

Performing a Request Connection

Step 1

From the Devices > Manage Devices page, locate the correct device.

Step 3

The Device Operations page appears. From the drop-down list under Device Operation, select Request Connection.

Performing a Factory Reset

Step 1

From the Devices > Manage Devices page, locate the correct device.

Step 3

The Device Operations page appears. From the drop-down list under Device Operation, select Factory Reset.

Displaying Live Data

Step 1

From the Devices > Manage Devices page, locate the correct device.

Step 3

The Device Operations page appears. From the drop-down list under Device Operation, select Display Live Data.

Step 4

The Device Operations page appears. Enter a duration in seconds for the operation to time out. The default timeout is 90 seconds.

Step 5

From the Parameter List File drop-down list, select the file, each of which is an XML file that details the parameters that are returned. Click on the View Details icon to view the parameters.

Note

You can also view these sample templates under the Configuration > Files tabs. From the View Files page, select the Parameter List option under the File Type drop-down list. Click Search. A list of sample parameter list files appears.

Performing a Ping Diagnostic

Step 1

From the Devices > Manage Devices page, locate the correct device.

Step 3

The Device Operations page appears. From the drop-down list under Device Operation, select Ping Diagnostic.

Step 4

The Device Operations page appears. Enter values in the following fields:

•

Device operation timeout (in seconds)—Specifies the duration after which the Ping operation times out.

•

Name of the hostname to be pinged—Identifies the hostname of the CPE to be pinged.

•

Interface—Identifies the WAN interface from which the Ping should originate on the CPE.

•

Number of repetitions—Specifies the number of times the Ping operation should run.

Forcing a Firmware Upgrade

To force a firmware upgrade on a device on next contact and bypassing the MaintenanceWindow restrictions set in the firmware rules:

Step 1

From the Devices > Manage Devices page, locate the device whose configuration you want to synchronize.

Step 3

The Device Operations page appears. From the drop-down list under Perform Device Operation, select Force Firmware Upgrade.

Forcing a Configuration Synchronization

To force a device to synchronize its configuration on next contact with the DPE regardless of the current configuration version on the device:

Step 1

From the Devices > Manage Devices page, locate the device whose configuration you want to synchronize.

Step 3

The Device Operations page appears. From the drop-down list under Perform Device Operation, select Force Configuration Synchronization.

Setting Device Operations Timeout

You can set the duration within which an operation is to be executed on device. After that period, the operation times out.

Note In addition to the procedure described in this section, you can set the default timeout duration in the Device Operation Timeout field via Configuration > Defaults > CWMP Defaults.

Step 1

From the Devices > Manage Devices page, locate the correct device.

Step 3

The Device Operations page appears. From the drop-down list under Device Operation, select the operation you want to perform.

Step 4

Enter a value (in seconds) in the Device Operation Timeout field. The default value for a device operation to time out is 90 seconds.

Group Management

Group management allows the creation, modification, and deletion of groups and group types.

Managing Group Types

Access the Manage Groups page (shown in Figure 16-4) by selecting Groups from either the main menu or the primary menu bar. Group Type is the default setting when this page appears.

Adding a Group Type

Step 3

The Add Group Type page appears. Enter a name for the new group type.

Step 4

If you have defined custom properties, the Property Name and Property Name section appear. Optionally, select the Property Name from the drop-down list and enter the required Property Value. You can add as many properties as required.

The new group type is recorded in the RDU, and the new group type appears on the Manage Group Types page.

Modifying Group Types

Step 2

The Manage Groups page appears. Locate and click the correct group type.

Step 3

The Modify Group Type page appears. Make the necessary changes to the Property Name/Property Value pairs. If you need to delete a specific pair, click Delete next to the correct pair.

Deleting Group Types

Step 2

The Manage Groups page appears. Locate the correct group type and click the Delete icon (

) corresponding to it.

Step 3

In the Delete Group Type dialog box, click OK to delete the selected group type, or Cancel to return to the previous page.

Managing Groups

Adding a New Group

Step 1

Select Group from the drop-down list on the Manage Groups page. Click Add.

Step 2

The Add Group page appears. Enter the new group name and select the appropriate Group Type for this node.

If you have defined custom properties, the Property name and Property Value section appear. Optionally, select the appropriate Property Name from the drop-down list and enter the required Property Value.

Step 5

Click Add to increase the number of applicable Property Name/Property Value pairs.

The new group is recorded in the RDU, and the new group appears on the Manage Groups page.

Modifying a Group

Step 2

The Modify Group page appears. Make the necessary changes to the Property Name/Property Value pairs. If you need to delete a specific pair, click Delete next to the correct pair.

Deleting Groups

You can delete any group that appears in the Manage Groups page by checking the box corresponding to the correct group and clicking the Delete button.

Relating/Unrelating Groups to Groups

The relate and unrelate functions are used to establish a relationship between group objects. To either relate or unrelate this relationship:

Step 1

Click Relate or Unrelate, as desired, for the selected group. The Relate Group or the Unrelate Group page appears.

Step 2

Select the appropriate Group Type from the drop-down list and select the group to which the node will be related/unrelated.

Viewing Group Details

Step 1

From the Manage Groups page, select the Group option from the Search Type drop-down list.

Step 2

Select the correct Group Type and enter the Group or Group wildcard in the appropriate field.

Step 4

Click the link corresponding to the Group whose details you want to view.

Viewing Servers

Viewing Device Provisioning Engines

The Manage Device Provisioning Engines page lets you monitor the list of all DPEs currently registered with the BAC database. Each DPE name displayed on this page is a link to another page that shows the details for that DPE. Click this link to display the details page, which is similar to Figure 16-5.

Note The RDU determines the names of the DPEs by performing a reverse DNS lookup on the DPE interfaces through which the DPE contacts the RDU.

Table 16-3 View Device Provisioning Engine Details Page
Field or Button	Description
Device Provisioning Engine Details
Host Name	Identifies the DPE hostname.
Port	Identifies the DPE port number from which DPE established connection to the RDU.
IP Address	Identifies the IP address of the DPE.
Primary Provisioning Group(s)	Identifies the primary provisioning group that the selected DPE belongs to. This is an active link that, if clicked, displays the Provisioning Group Details page for that provisioning group.
Properties	Identifies which properties have been configured for this DPE.
Version	Identifies the version of DPE software currently in use.
UpTime	Specifies the total time that the DPE has been operational since its last start-up.
State	Identifies whether the DPE is ready for operations. These states include: •Registering •Initializing •Synchronizing •Populating •Ready •Offline For details on each state, see DPE-RDU Synchronization. Note If this field reads Offline, the options from the Uptime field onwards do not appear. The DPE is prepared to service client requests in any state except Offline.
Device with Faults	Displays number of devices with faults at this DPE. If number is greater than zero, features the View Details icon which if clicked, displays details of devices with faults.
Log Files
DPE Log File	Features the View Details icon that if clicked displays the View Log File Contents page, which provides details of dpe.log.
Files	Identifies the number of files, such as firmware images, that are cached at the DPE.
Number of Devices	Identifies the number of CWMP devices for which the DPE maintains instructions. In a fully synchronized DPE, this number should equal the number of CWMP devices in the DPE's provisioning group.
CWMP Statistics Note This section displays statistics from the last time the DPE was started.
Sessions succeeded	Identifies the number of successful CWMP sessions.
Sessions failed	Identifies the number of failed CWMP sessions.
File Requests Succeeded	Identifies the number of successful firmware file download requests.
File Requests Failed	Identifies the number of failed firmware file download requests.
Immediate Device Operations Succeeded	Identifies the number of immediate device operations that succeeded.
Immediate Device Operations failed	Identifies the number of immediate device operations that failed.

Viewing Provisioning Groups

The Manage Provisioning Groups page lets you monitor all current provisioning groups. Each provisioning group appearing in this list is a link to its own details page. Click this link to display the details page, which is similar to Figure 16-6.

Table 16-4 identifies the fields and buttons shown in Figure 16-6. The fields described in Table 16-4 may include active links that, if clicked, display the appropriate details page.

Table 16-4 View Provisioning Groups Details Page
Field or Button	Description
Provisioning Group Details
Name	Identifies the provisioning group name selected from the List Provisioning Groups page.
Primary Device Provisioning Engine(s)	Identifies the hostnames of the DPEs that are primary for this provisioning group.
Provisioning Group Properties
Discovered ACS URL	Identifies the DPE URL through which the provisioning group connects to the DPE. Discovered URL is based on DPE interface configured for provisioning operations via the DPE CLI. The parameters is based on registration information from the DPE which registered last with the RDU. This URL is used for operations such as redirection of CPE to a different provisioning group.
ACS URL (Overrides Discovered ACS URL)	Identifies the configured URL of the BAC server associated with each provisioning group. This URL is used by devices to contact the DPEs in a given provisioning group, and is used for operations such as redirection of CPE to a a different provisioning group.
Submit	Activates or implements the changes you have made.
Reset	Returns all settings to their previous settings.

Viewing Regional Distribution Unit Details

The RDU option, from the Servers menu, displays details of the RDU. Figure 16-7 illustrates a sample RDU details page.

Table 16-5 View RDU Details Page
Field or Button	Description
Regional Distribution Unit Details
Host Name	Identifies the host name of the system that is running the regional distribution unit.
Port	Identifies the RDU listening port number for connections from the DPEs. The default port number is 49187, but a different port can be selected during installation of the RDU.
IP Address	Identifies the IP address assigned to the RDU.
Properties	Identifies properties configured for the RDU.
Version	Specifies the version of RDU software currently in use.
UpTime	Specifies the total time that the RDU has been operational since its last period of downtime.
State	Identifies whether the RDU is ready to respond to requests. The only state that is featured via the administrator user interface is Ready.
PACE Statistics
Batches Processed	Identifies how many individual batches have been processed since the last RDU start-up.
Batches Succeeded	Identifies how many individual batches have been successfully processed since the last RDU start-up.
Batches Dropped	Identifies how many batches have been dropped since the last RDU start-up.
Batches Failed	Identifies how many batches have failed processing since the last RDU start-up.
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.
IGS This is the Instruction Generation Service.
State	Identifies the operational state of the instruction generation service. This could be: •Idle—Specifies that the IGS is not processing regeneration requests. •Regeneration—Specifies that the IGS is processing regeneration requests. •Waiting Regeneration—Specifies that the IGS is unable to regenerate instructions for a device. When the IGS is stuck in this state, consult the rdu.log for details.
Requests Processed	Identifies the number of instruction generation requests processed since last RDU start-up.
Elapsed Time	Identifies, in seconds, the time elapsed since the start of regeneration.
Devices Regenerated	Identifies the number of device instructions regenerated since the regeneration process started.
Regeneration rate	Identifies the cumulative rate of device instructions regenerated since the regeneration process started.
Requests pending	Identifies the number of regeneration requests in queue.
Log Files
RDU Log File	Features the View Details icon, that, if clicked, displays the View Log File Contents page, which provides details of the rdu.log file.
Audit Log File	Features the View Details icon, that, if clicked, displays the View Log File Contents page, which provides details of the audit.log file.
Device Statistics
Number of CWMP Devices	Identifies the number of devices in the RDU database.
Device Faults Statistics
Devices with Faults in Last 1 Hour(s)	Identifies the number of devices with faults over the last one hour, at both the RDU and the DPEs.
Devices with Faults in Last 3 Hour(s)	Identifies the number of devices with faults over the last three hours, at both the RDU and the DPEs.
Devices with Faults in Last 12 Hour(s)	Identifies the number of devices with faults over the last 12 hours, at both the RDU and the DPEs.
Devices with Faults in Last 72 Hour(s)	Identifies the number of devices with faults over the last 72 hours, at both the RDU and the DPEs.

Table Of Contents