Control Center

Feature History

Feature Name

Release Information

Description

Access Control Center from cnAAA

2025.01.0

cnAAA allows access to the Control Center through a GUI using HTTPS in a web browser. Users can view, edit, import, and export Custom Reference Data (CRD) to maintain consistent data management across systems.

Overview

The Cloud Native Authentication, Authorization, and Accounting (cnAAA) enables secure access to the Control Center through a GUI using the HTTPS protocol on a web browser.

In the Control Center, administrators can manage Custom Reference Data (CRD) by viewing, editing, importing, and exporting data to maintain consistency across systems. This approach is essential for preventing discrepancies, errors, and data integrity issues that can occur when data is managed independently in multiple systems.

Functionalities

This section describes the functionalities of the Control Center.

  • Login to the Control Center.

  • Find Subscriber.

  • Create Subscriber.

  • Reference Data.

  • Find Subscriber Session.

Login to the Control Center

You can login to the Control Center GUI through the https protocol.

Procedure

Enter the credentials in the Username and Password fields, of the Control Center GUI and click Login.

Find Subscriber

You can find detailed information of a specific subscriber using their credentials or name.

Procedure

Step 1

Enter the subscriber's name or credentials in the Credentials or Name field.

Step 2

Click Search to initiate the search process.

Step 3

View the results displayed in a table format.

Note

 

Balance-Related Panels and Grids have been removed from the Subscriber Profile view.

Create Subscriber

You can create a subscriber from the control center GUI

Procedure

Step 1

In the Credential field, enter a unique identifier for the subscriber .This identifier is essential for tracking and managing subscriber accounts.

Step 2

In the Name field, enter the subscriber's full name or an alternative identifier to help with searching and managing records.

Click Reset to reset all the data.

Click Save to submit the information and complete creation of the subscriber.

Click Save & Continue to proceed to additional configuration screens, such as General, Credentials, Services, Notifications, and Subaccounts.

Once you click Save & Continue, sample data will be displayed on the Subscribers screen.

Reference Data

Step 3

Access Reference Data: Click Reference Data to view options for importing or exporting CRD data.

Step 4

Manage CRD Tables: Select the configured CRD tables to create, read, update, or delete records from the CRD tables.

Find Subscriber Session

The Find Subscriber Session allows you to search and retrieve session details for a specific subscriber based on their session data.

Before you begin

Follow these steps to configure the cnAAA Ops-Center to fetch specific subscriber session data under the Find Subscriber Session view.

  1. Login to cnAAA Ops-Center.

  2. Ensure the Ops-Center is fully shut down before proceeding with configuration changes.

  3. Configure this command in Ops-Center.

    
cdl datastore session find-by-nuk-prefixes 
USuMSubscriberIdKey 
cdl datastore session find-by-nuk-prefixes 
MacAddressKey 
cdl datastore session find-by-nuk-prefixes 
UserIdKey 
cdl datastore session find-by-nuk-prefixes 
FramedIpKey 
cdl datastore session find-by-nuk-prefixes 
FramedIPv6AddressKey

  4. Restart the cnAAA Ops-Center.

Procedure

Step 1

Select the Query Key from the drop-down list to choose the type of key for your search, such as User ID, Framed IP, or Framed IPv6 Prefix.

Step 2

In the Key Data field, enter the specific value associated with the selected Query Key.

Step 3

Execute the search to retrieve session details.

Review the results displayed in a structured table format, which includes the Primary Key, Type, and Subscriber Credential.

View session details by navigating to the session details section to access in-depth information about a selected session.

Delete Subscriber

You can delete a specific subscriber from Control Center GUI.

Procedure

Step 1

Navigate to Find subscriber and enter the subscriber's credentials or name in the Credentials or Name field.

Step 2

Click Search to initiate the search process.

View the results displayed in a table format.

Step 3

Place the cursor on a particular subscriber and click Delete.

A pop message is displayed stating "Are you sure want to delete this subscriber", click Yes.

You can see a Subscriber deletion successful message.

Delete Session

You can delete a specific subscriber session from Control Center GUI:

Procedure

Step 1

Click Find Subscriber Session.

Step 2

Choose the Query Key from the drop-down list to choose the type of key for your search, such as User ID, Framed IP, Framed IPv6 Prefix.

Step 3

In the Key Data field, enter the specific value associated with the selected Query Key.

Step 4

Execute the search to retrieve session details and click Open from table where session details are present.

Step 5

Under the session details section, click Remove Session.

A pop message is displayed stating "Are you sure want to remove this session", click Yes.

You can see a Session deletion successful message

Service wise user level bifurcation

The subscriber bifurcation report provides visibility into subscriber provisioning and distribution trends within the Control Center. This feature centralizes reporting, which eliminates manual database queries and reduces operational overhead. Administrators can generate, view, and export reports using filters such as circle code, service type, and daily creation counts. The system provides these reports in Comma-Separated Values (CSV) format to support business intelligence, regulatory compliance, and the analysis of baseline service assignments, such as Plan0, for new subscribers.

Software upgrade and deployment

Before you configure or use this feature, verify that the software is correctly deployed:

  • Qualify the software upgrade: Refer to Chapter 6: Software Upgrade Qualification for prerequisites and system health checks.

  • Monitor and verify the upgrade: Refer to Chapter 6: Monitor the cnAAA Upgrade and Verify the Helm Status to ensure the deployment is successful.

  • Verify post-deployment: Refer to Chapter 6: Post deployment verification steps to confirm that the Subscriber Bifurcation link is visible in the Control Center.

Configure the subscriber bifurcation report

Use this procedure to configure the subscriber bifurcation report settings in the Ops-Center. These settings allow you to manage service codes, user interface (UI) display limits, and export capabilities.

This table summarizes the configurable engine properties.

Table 1. Configuration parameters
Parameter Engine property Default value

Plan0 service code

 com.broadhop.subscriber.bifurcation.serviceCode Plan0

UI result limit

 com.broadhop.service.bifurcation.maxResult 1,000

Export result limit

 com.broadhop.export.service.bifurcation.maxResult 100,000

Feature toggle

 com.broadhop.subscriber.bifurcation.enable true

Configure report settings

Procedure

Complete these steps to configure the report settings:

Property: com.broadhop.subscriber.bifurcation.serviceCode

Complete these steps to configure the report settings: Property: com.broadhop.subscriber.bifurcation.serviceCode

Step 1

Log in to the Ops-Center CLI and enter config mode.

Step 2

Navigate to your engine group: engine <engine-group-name>.

Step 3

Configure the Plan0 service code.

properties com.broadhop.subscriber.bifurcation.serviceCode value
        <service-name>

Step 4

Configure the UI result limit.

properties com.broadhop.service.bifurcation.maxResult value <number-of-results>

If you set this value to 0 or less, the system uses a default value of 1,000, while values greater than 100,000 are capped at 100,000. This total limit applies to all Subscriber Profile Repository (SPR) MongoDB instances combined. We recommend setting the value to 20,000 to achieve optimal UI performance.

Step 5

Configure the CSV export limit.

CSV exports cannot exceed 100,000 records. If you configure a higher value, the system adjusts it to 100,000.

properties com.broadhop.export.service.bifurcation.maxResult value <number-of-records>

Step 6

Configure query timeouts.

To prevent performance degradation during large data scans, configure query timeouts. The valid range is 1 to 60 seconds, with a default value of 20 seconds. 

properties spr.subscriber.bifurcation.aggregate.max.time.seconds value <timeout-in-seconds>
properties spr.avp.aggregate.max.time.seconds value <timeout-in-seconds>

Step 7

commit the changes.

Workflow

Once the Subscriber Bifurcation is integrated and configured, you can generate reports by following this workflow:

  1. Navigate to the Subscribers section in the Control Center and click Subscriber Bifurcation.

  2. Select the Subscriber Type: Static (all provisioned subscribers) or Plan0 (subscribers with the Plan0 service).

  3. Apply filters by selecting the Filter Type (All, Provisioned, Circle Code, Service Type, or Service Code).

  4. Specify the Start Date and End Date.


    Note

    The range is limited to the previous 90 days from the current date.

  5. Click Search to view the results in the UI.

  6. Click Export to download the data as a CSV file.

Data interpretation and limitations

Observe these operational constraints when you use the subscriber bifurcation report:

  • Historical data constraint: The UI is limited to a 90-day window to ensure database performance. For data older than 90 days, administrators must perform a manual database dump via the backend.

  • Time zone synchronization: The system processes data in UTC. If your regulatory requirements mandate Indian Standard Time (IST), ensure your data team applies the necessary offset (+5:30) during external post-processing of the exported CSV.

  • Result set caps: If the report exceeds the configured maxResult (default 1000), the UI truncates the display. Narrow the date range or apply more specific filters if this occurs.

  • Subscriber identification: The report displays Network or Credential IDs. If the subscriber's full name is required, cross-reference the exported IDs using the Find Subscriber module.

  • Credential duplication: If a subscriber has multiple credential IDs, the report displays them as separate rows. This ensures all active credentials are accounted for in the bifurcation.