VLAN Management Instance

Note

VLAN Management Instance is not supported on VSP 8600 Series.

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

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.

For the VLAN Management Instance to take route priority when used in conjunction with the CLIP Management Instance, you must configure a default route for the VLAN Management Instance with a value lower than 100, or configure static routes for direct communication over the VLAN Management Instance and management networks.

Packets sent to the VLAN Management Instance IP address must ingress the switch from a VLAN port (or contain the VLAN ID) associated with the VLAN Management Instance. The system does not route packets between the VOSS routing VLAN and the VLAN Management Instance.

If you configure the same VLAN ID for VOSS routing and for the VLAN Management Instance, the VOSS routing stack transmits and receives all ARP, ND, and ICMP packets. In this scenario, the packets are only counted and shown in the VOSS routing KHI port statistics. The management statistics and KHI management statistics do not count or show the packets.

IPv4 and IPv6 address co-existence for both VOSS routing VLAN and VLAN Management Instance is supported, however you must manually match both IP address configurations between the VLANs. For example, the following configuration is not supported:

VLAN Management Instance with both IPv4 and IPv6 address routing but only the IPv4 or IPv6 address configured for VOSS routing VLAN.

If you configure the VLAN Management Instance with a manual IPv4 address and a DHCP IPv4 address first, you cannot add a IPv4 address to a VOSS routing VLAN.

If you configure the VLAN Management Instance with an IPv6 address first, you can only add one IPv6 global address to a VOSS routing VLAN.