SLX MCT client remote state stays in Undep (Undeployed)
Allthough all interfaces on both MCT peers are Up, the client info in show cluster keeps showing Undep for the remote. Client Info: ============ Name Id ESI Interface Local/Remote State ---- -- --- --------- ------------------ client1 0:0:7:3:4:6:0:0:0:0 Port-channel 10 Up / Undep
This can be caused by using a BGP neighbor IP that is not it's router-id. MCT requires:
Explicit “ip router-id” to be configured on both MCT peers
peer-ip configuration for the cluster must match the MCT peer node’s router-ID (loopback IP)
Use the loopback router-id as bgp neighbor IP. Use static routes or OSPF to make the loopback IP reachable from the peer.