Segmented Management Instance Interface Types

The Management Instance supports the following interface types:

• Management Instance CLIP

  • You can assign a circuitless management IP (CLIP) address bound to a VRF.

  • The IP address is not bound to a physical network; it does not transmit nor receive IPv4 Address Resolution Protocol (ARP) or IPv6 Neighbor Discovery (ND) messages.

  • You do not need to configure a default or static route. This interface type uses all routing information learned by protocols attached to the VRF.

  • Packets can ingress on any port or VLAN in the VRF. You can configure accept policies to access the Management Instance CLIP from other VRF. Inter-VRF access is not permitted with traditional IP routing using OSPF, BGP, or RIP. Packets ingressing the switch from a VLAN belonging to a different VRF without a configured accept policy will not reach the Management Instance CLIP IP address.

  • You can use this interface type for CLIP management network routing in a Fabric network or Layer 3 routing network.

• Management Instance OOB

  • You can assign a management IP address bound to the Out-of-Band (OOB) interface.

  • The Dynamic Host Configuration Protocol (DHCP) Client can request an IPv4 address for the Management Instance OOB interface.

  • You must configure a default or static route to reach the next-hop gateway; no routing protocol information is used to access off-link networks.

  • You can use this interface type for OOB management network routing, as an alternative to in-band network routing management.

• Management Instance VLAN

  • You can assign a Management Instance IP address to an inband VLAN.

  • The DHCP Client can request an IPv4 address for the Management Instance VLAN interface.

  • The interface resides on the physical VLAN segment, behaving as a host for sending and receiving IPv4 ARP and IPv6 ND messages.

  • You must configure a default or static route to reach the next-hop gateway; no routing protocol information is used to access off-link (other subnets) networks.

  • No internal routing occurs between other non Management Instance VLANs. Packets must ingress on one of the ports in the VLAN.

  • You can use the Management Instance VLAN for management network routing, such as binding the Management Instance VLAN to an I-SID, which routes all management traffic to a single I-SID in a Fabric network. Also, other normal VLAN related operations such as VLAN port member changes are valid.

You can create only one of each interface type.