Manage Network Functions and Devices
As of Oracle Communications Session Element Manager Release 9.0, the previous device nodes (used in OCSEM 7.x) that maintained the standalone or HA pair devices were replaced with the concept of a Network Function (NF). NFs are a network architecture concept used to describe entire classes of network node functions into building blocks that may connect, or chain together, to create communication services as defined by the GS NFV-MAN 001 - ETSI. In this context, a NF can be composed of one-to-many Edge devices. For example, a SBCbased NF can be composed of two SBC instances running as a HA pair.
Oracle Enterprise Edge and Core Plug-in Product Category and Network Function Types
As of Oracle Communications Session Element Manager Release 8.0, the previous device nodes (used in OCSEM 7.x) that maintained the standalone or HA pair devices were replaced with the concept of a Network Function (NF). NFs are a network architecture concept used to describe entire classes of network node functions into building blocks that may connect, or chain together, to create communication services as defined by the GS NFV-MAN 001 - ETSI. In this context, a NF can be composed of one-to-many Edge devices. For example, a SBC-based NF can be composed of two SBC instances running as a HA pair.
The following table describes the product category and Network Function (NF) types that you can select for your Oracle Enterprise Edge and Core Plug-in.
| Product Category | NF Type | Component Devices |
|---|---|---|
| Enterprise Edge & Core | ESBC | Standalone Oracle Enterprise Session Border Controller (ESBC) device |
| ECB | Standalone Oracle Enterprise Communications Broker (ECB) device | |
| Device Cluster | High-Availability (HA) device pair of the component devices listed above. |
Connectivity with 2FA-Enabled SBC Device
Two-factor authentication (2FA) is an additional layer of security on a device. When you select 2FA for a device, you must provide a key and a passphrase (to decrypt the keyfile), both are stored. SBC and ESBC devices support Multi-factor Authenication (MFA).
Note:
The 2FA feature is supported for SBC and ESBC devices; however, an ECB device does not support 2FA configuration. Hence, you cannot enable 2FA while adding ECB devices.Session Delivery Manager Release 9.0.4 supports 2 Factor Authentication (2FA) for connectivity with SBC devices. The 2FA Authentication extends beyond username and password-based authentication to additionally support a key with passphrase.
After a combination of username, password and uploaded KeyFile is configured, all future connections with the device is authenticated only when the KeyFile is validated. For more information on how to configure 2FA, see the section Add a Network Function with Devices.
Note:
- Configuration of 2FA is optional. The existing users will have no problems to log in to Session Delivery Manager or when connecting to SBC devices after upgrading to Release 9.0.4.
- If you have upgraded to Session Delivery Manager Release 9.0.4. and you want to enable 2FA on an existing device, then you must remove the device and add it again.
- For a fresh installation of Session Delivery Manager Release 9.0.4, devices with 2FA enabled at the device end must be added to SDM with the 2FA Status set to Enabled. Similarly, devices with 2FA disabled at the device end must be added to SDM with the 2FA Status set to Disabled.
You can avail pre generated certificates to access the GUI as a first factor authentication, and then you can log in to the SDM User Interface.