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