3 Configuring Cloud Native Core Binding Support Function Using Cloud Native Core Console
This chapter describes how to configure different global and service parameters in Oracle Communications Cloud Native Core BSF using Oracle Communications Cloud Native Core Console.
Cloud Native Core Console Interface
This section provides an overview of the Oracle Communications Cloud Native Core (CNC) Console, which includes an interface to aid in creating global and service parameters in BSF.
You can use BSF integrated with CNC Console only after logging successfully into the CNC Console application. To login successfully into the CNC Console, you need to make the following updates to the hosts file available at the C:\Windows\System32\drivers\etc location.
In the Windows system, user needs to open the hosts file in the notepad as an Administrator and append the following set of lines at the end:
Example:
10.75.225.189
cncc-iam-ingress-gateway.cncc.svc.cluster.local
10.75.225.189
cncc-core-ingress-gateway.cncc.svc.cluster.local
Note:
The IP Address in the above lines may change when deployment cluster changes.Save and close the notepad.
Note:
Before logging into CNC Console, it is important to create a CNC user and password. Using this user details, you can login to the CNC Console application. For information on creating a CNC Console user and password, see Oracle Communications Cloud Native Core Console Installation Guide.- Open a web browser and enter the URL:
http://cncc-core-ingress-gateway.cncc.svc.cluster.local:port
number/ and press Enter.
The login page opens.
where, port number is cncc-iam-ingress-port number
. - Enter the Username and Password.
- Click Login. Following screen appears:
Figure 3-1 CNC Console Interface
This is the CNC Console Home Page from where you can navigate to different NF services. To use BSF services integrated with CNC Console, click BSF in the left navigation pane.
General Configurations
You can manage and view the General Configurations from this page.
- From the navigation menu, under
BSF, click General Configurations.
The General Configurations screen appears.
- Click Edit to edit the general configurations.
- Enter the following information:
- Enable Tracing- Specifies whether to enable/disable tracing. By default, this configuration is enabled.
- Enable Metrics- Specifies whether to enable/disable system metrics. By default, this configuration is enabled.
- Click Save.
Configuring BSF Management Service
- From the navigation menu, under BSF, click Service Configurations,
and then click Management
Service.
The Management Service screen appears.
- Click Edit to configure the BSF Management Service.
- Check the default configuration for
the fields available in respective groups and edit as necessary.
The following table describes the fields along with their valid input values under each group:
Field Name Description Root Log Level
Indicates the log level of BSF Management Service.
Default Value: Warn
Allowed Values: Debug, Information, Warn, Error, Trace, Always
Server Root URL Specifies the URL of the server root. Log Levels Logger Name Default Value:
Level Indicates the log level of BSF Management Service.
Default Value: Warn
Allowed Values: Debug, Information, Warn, Error, Trace, Always
- Click Save.
Diameter Configurations
You can manage and view the Diameter Configurations from this page.
Settings
- From the navigation menu, click
The Settings screen appears.
.
- Click Edit to edit the settings.
- Enter the following information:
Timer
- Reconnect Delay (sec)- Enter the time frame to delay before attempting to reconnect after a connection failure in seconds. The default is 3 seconds.
- Response Timeout (sec)- Enter the response timeout interval in seconds. The default is 5 seconds.
- Connection Timeout (sec)- Enter the connection timeout interval in seconds. The default is 3 seconds.
- WatchDog Interval (sec)- Enter the watchdog interval in seconds. The default is 6 seconds.
Transport
- Protocol - TCP/SCTP
- Click Save.
Peer Nodes
- From the navigation menu, click
The Peer Nodes screen appears.
.
- Click Add to create peer node. The Create Peer Node screen appears.
- Enter the following information:
- Name- Unique Name of the peer node.
- Type- Defines which type of diameter service it should take up. The value can be Application function (af), backend, diameter routing agent(dra), ocs, tdf, or udr.
- Reconnect Limit (sec) -
- Initiate Connection- Set it to true to initiate a connection for this peer node.
- Port- Enter the port number. Enter a number from 0 to 65535.
- Host- Enter the host name. Enter a FQDN, ipv4 or ipv6 address available for establishing diameter transport connections to the peer node .
- Realm- Enter the realm name, that is, FQDNs to all of that computers that transact diameter traffic.
- Identity- Enter a identity to define a node in a realm.
- Click Save.
Note:
You can import and export the Peer Node configurations by clicking on Import and Export on Peer Nodes Configurations screen.
Session Viewer
The Session Viewer displays detailed session information for a specific subscriber. Within the session viewer, you can enter query parameters to render session data for a specific subscriber. This section provides information about viewing the sessions.
To view the sessions:
- From the navigation menu, under BSF, click Session Viewer. The Session Viewer page appears.
-
- Enter the value of the following fields in the Address group:
- IPV4 Address- The list consists of IP addresses in IPv4 format.
- IPV6 Prefix- The IPv6 Address Prefix
- IP Domain- The IPv4 address domain identifier.
- MAC Address- MAC address is formatted as six groups of two hexadecimal digits separated by colons (:) or hyphens (-). For example, in the format hh:hh:hh:hh:hh:hh.
- Enter the value of the following fields in the User group:
- SUPI- Subscription Permanent Identifier
- GPSI- Generic Public Subscription Identifier
- Enter the value of the following fields in the Slice Information
group:
- DNN-
- S-NSSAI_SST-
- S-NSSAI_SD-
- Enter the value of the following fields in the Address group:
- Click Query. Information about
the subscriber session(s) is displayed.
Following screen capture is an example of Query result:
If session data is not available, the error is displayed along with No session found.