CLIP Management Instance

You can associate only one VRF ID with a CLIP Management Instance IP address.

You must configure a new loopback interface isis ip-source address if you migrate the current ISIS IP address to the CLIP Management Instance when the IP address is the same as a previously configured IP shortcut.

Advertisement of the IPv4 or IPv6 address in the GRT for the CLIP Management Instance to ISIS occurs automatically. Advertisement of the IPv4 or IPv6 address in the VRF Layer 3 VSN bound to the CLIP Management Instance occurs automatically. You must configure route redistribution to advertise the CLIP Management Instance to different protocols.

You must configure accept policies or configure inter-VRF route redistribution to access the CLIP Management Instance from a different VRF.

Packets sent to the CLIP Management Instance IP address must ingress the switch from a VLAN associated with the VRF associated with the CLIP Management Instance.

UDP server applications such as TFTP or RADIUS dynamic server or SMMP can have limitations when multiple Segmented Management Instances are configured with overlappping or asymmetrical routing:

Note

The limiations listed do not apply to TCP applications or if a single Management Instance is configured.

Client communication to the CLIP Management Instance IP address is from the same subnet as the VLAN Management Instance.
Client communication to the CLIP Management Instance IP address when specific static routes or default route with higher preference back to the client network exist on OOB Management Instance or VLAN Management Instance.
Client communication to the OOB Management Instance IP address or VLAN Management Instance IP address that relies on a default route with a lower preference than the internal default route used by the CLIP Management Instance.
Client communication to the CLIP Management Instance IP address is from the same subnet as the OOB Management Instance (even if the OOB port is down).

Asymmetrical routing can occur in any of these three scenarios. For the first two scenarios you can use the OOB or VLAN Management Instance IP address instead of the CLIP Management Instance IP address. Also, use FTP or SCP file transfer as an alternative since those protocols are TCP based.

The third scenario, you can configure more specific static routes for networks originating UDP client communication to the OOB or VLAN Management Instance IP address if the CLIP Management Instance is also configured.