Behavior Change
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.