RCM supports the following timers:

• Init Wait Timer—The Init Wait timer defers the registration of Init state UPs and registers the active UPs first. This timer starts only when RCM controller starts or when RCM moves to HA MASTER state.

  When RCM controller starts or moves to HA MASTER state, the RCM controller has no state and learns the UP state from the UPs itself. The Init state UPFs should not be assigned HostIDs that are already allocated to Active UPs.

• Mass UPF Failure Timer—The Mass UPF Failure timer starts when all UPs lose BFD connectivity with RCM. Depending on the network deployment, there could be network connectivity issue between RCM and UPs. If RCM cannot establish BFD connectivity to any UPF within the timeout period, then RCM HA switchover is performed.

Previous Behavior:

• The Init Wait timer starts only with the first UPF registration.

• The Init Wait Timer was not configurable and fixed to 300 seconds.

• The Mass UPF Failure timer was not configurable and fixed to 3 minutes.

New Behavior:

• The Init Wait timer starts only when the RCM controller starts or when RCM moves to HA MASTER state.

• The Init Wait timer is configurable using the k8 smf profile rcm-config-ep init-wait-timeout init_wait_timeout command.

• The Mass UPF Failure timer is configurable using the k8 smf profile rcm-config-ep mass-upf-failure-timeout upf_failure_timeout command.

Customer Impact:

• Reduced wait times for UPF registration.

• No change in behavior if the timer CLI commands are not used.

• The timer CLI commands can be used to change or disable the Init Wait timeout and Mass UPF Failure timeout.

For more information, refer to the UCC 5G RCM Configuration and Administration Guide.

RCM supports CLI commands to configure track interface and IPv4 virtual routes for the Keepalived pod.

When VIP gets attached to the service interface (when RCM moves to MASTER state), addition of IPv4 routes is required for non-host networking Bfdmgr.

Previous Behavior: RCM did not support CLI commands to configure track interface and IPv4 virtual routes for the Keepalived pod.

New Behavior: RCM supports Ops Center CLI commands to configure additional tracking interfaces and IPv4 virtual routes for the Keepalived pod.

Customer Impact: There is no impact if the CLI commands are not used. The CLI commands are backward compatible

Command Changes

Use the following RCM Ops Center CLI commands to configure the track interface and IPv4 virtual routes in the Keepalived pod:

k8 smf profile rcm-keepalived-ep vrrp-config group group_name 
   ipv4-route route_serial_number 
      destination host_network_ipv4 mask ipv4_mask gateway host_ipv4 device interface_name 
   track-interface track_interface 
   exit 

NOTES:

• ipv4-route route_serial_number : Configures the Keepalived IPv4 virtual routes.

• track-interface track_interface : Configures the Keepalived track interface.

For more information, refer to the UCC 5G RCM Configuration and Administration Guide.

The RCM host configuration includes a new service type "NNRF". In the string-based approach, RCM acts as a configurator and pushes the configuration of all services including the NNRF service.

In the Yang-based approach, NSO acts as a configurator and allows configuration of only the service names in RCM. NSO pushes the whole configuration including the NNRF service.

Important

The script support does exist currently for NNRF service type. So, you must manually configure this service type.

Previous Behavior: The NNRF service type was not supported.

New Behavior: The RCM host configuration includes the NNRF service type.

Customer Impact: You can use the NNRF commands in RCM.

For more information, refer to the UCC 5G RCM Configuration and Administration Guide.

As part of security enhancement, RCM supports the following functionality:

• Partition Usage in RCM VM—In RCM VM, the /tmp and /var/tmp directories are mounted as separate partitions to prevent privilege escalation attacks.

• RCM provides flexibility to configure the host-networking mode for SNMP trapper pod. The k8 smf profile rcm-snmp-trapper-ep snmp-trapper host-networking { false | true } CLI command configures the SNMP trapper pod in host networking mode and non-host networking mode.

• RCM supports the conversion of host networking pods to non-host networking mode for restricting pod access to host network namespace. The CLI commands k8 smf profile rcm-bfd-ep host-networking { true | false } and k8 smf profile rcm-bfd-ep node-port-enabled { true | false } can be configured to run BFDmgr in non-host networking mode.

• RCM supports the tracking interface and IPv4 virtual-routes configuration for the Keepalived pod. The IPv4 virtual-routes configuration installs routes when RCM moves to MASTER state.

For more information, refer to the UCC 5G RCM Configuration and Administration Guide.

Use the following RCM Ops Center CLI commands to configure the following functionality:

• To configure the SNMP trapper pod in host networking mode and non-host networking mode:

  k8 smf profile rcm-snmp-trapper-ep snmp-trapper host-networking { false | true } 

• To configure host networking mode and non-host networking mod in BFDmgr:

  k8 smf profile rcm-bfd-ep host-networking { true | false } 
  

  Default value: true

• To configure node port:

  k8 smf profile rcm-bfd-ep node-port-enabled { true | false } 

  Default value: false

  The node port must be set to true when host networking is set to false .

• To configure tracking interfaces in Keepalived pod:

  k8 smf profile rcm-keepalived-ep vrrp-config group vrrp_group_name 
     track-interface interface_name 
     exit 

• To configure IPv4 virtual routes in Keepalived pod:

  k8 smf profile rcm-keepalived-ep vrrp-config group vrrp_group_name 
     ipv4-route route_serial_number 
        destination host_network_ipv4 mask ipv4_mask gateway host_ipv4 device interface-name 
        exit 
     exit 

The rcm show-snmp-trap history CLI command displays the history of SNMP event traps.

Previous Behavior: RCM did not support any command to display the SNMP trap history.

New Behavior: RCM supports the rcm show-snmp-trap history CLI command to display the SNMP trap history. This command displays details for the latest 5000 SNMP traps.

Customer Impact: This command eases debugging with the detailed history of SNMP traps.

For more information, refer to the UCC 5G RCM Configuration and Administration Guide.

During upgrade or downgrade, it is recommended to use the compatible configuration files to avoid lockout. The configuration files saved from a new trusted build will not work on older builds (trusted or regular) and new regular builds.

Customer Impact: Possible impact during upgrade or downgrade activities.

Previous Behavior: The SNMP trap for status change update failure was not supported by the keepalived pod.

New Behavior: The keepalived pod generates and raises the RCMControllerStateUpdateFailure SNMP trap when RCM status change request through HTTP POST from RCM keepalived to RCM controller fails.

Customer Impact: The new SNMP trap eases diagnosis of issues in the keepalived pod.

For more information, refer to the UCC 5G RCM Configuration and Administration Guide.

Previous Behavior: The SNMP trapper pod worked only in host networking mode.

New Behavior: The SNMP trapper pod can be configured in host networking mode and non-host networking mode using the k8 smf profile rcm-snmp-trapper-ep snmp-trapper host-networking [ false | true ] command.

Customer Impact: You can use the command to configure non-host networking mode for the SNMP trapper pod.

For more information, refer to the UCC 5G RCM Configuration and Administration Guide.

The Virtual Routing and Forwarding (VRF) feaure allows multiple instances of a routing table to coexist within the same router at the same time. In UPF, VRF enables association of IP address pools with VRF.

In this release, UPF supports up to 129 VRFs for private APN/DNN.

For more information, refer to the UCC 5G UPF Configuration and Administration Guide > Virtual Routing and Forwarding chapter.