Dell Force10 Z9000 Configuration Manual page 922

• All system management protocols are supported on VLT ports, including SNMP, RMON, AAA,
ACL, DNS, FTP, SSH, Syslog, NTP, RADIUS, SCP, TACACS+, Telnet, and LLDP.
• Layer 3 VLAN connectivity VLT peers is enabled by configuring a VLAN network interface for
the same VLAN on both switches.
• IGMP snooping is supported over VLT ports. The multicast forwarding state is synchronized on
both VLT peer switches. The IGMP snooping process on a VLT peer shares the learned group
information with the other VLT peer over the chassis interconnect trunk.
• Software features supported on VLT physical ports:
• In a VLT domain, the following software features are supported on VLT physical ports: 802.1p,
LLDP, flow control, port monitoring, jumbo frames.
• Software features not supported with VLT:
• In a VLT domain, the following software features are supported on non-VLT ports: 802.1x, ingress
and egress ACLs, BGP, DHCP relay, DHCP Snooping, FRRP, IS-IS, IPv6 dynamic routing, OSPF,
Active-Active PIM-SM, PIM-SSM, ingress and egress QOS, sFlow, and all protocols currently
supported in FTOS.
• VLT and VRRP interoperability:
• In a VLT domain, VRRP inter-operates with virtual link trunks that carry traffic to and from access
devices (see
and backup roles. Each peer actively forwards L3 traffic, reducing the traffic flow over the VLT
interconnect.
• VRRP elects the router with the highest priority as the master in the VRRP group. To ensure
VRRP operation in a VLT domain, you must configure VRRP group priority on each VLT peer so
that a peer is either the master or backup for all VRRP groups configured on its interfaces. See
VRRP Group (Virtual Router) Priority
• To verify that a VLT peer is consistently configured for either the master or backup role in all
VRRP groups, enter the
• You must also configure the same L3 routing (static and dynamic) on each peer so that L3
reachability and routing tables are identical on both VLT peers. Both the VRRP master and backup
peers should be able to locally forward L3 traffic in the same way.
• In a VLT domain, although both VLT peers actively participate in L3 forwarding as the VRRP
master or backup router, the
peer as backup.
• Failure scenarios:
• On a link failover, when a VLT port channel fails, the traffic destined for that VLT port channel is
re-directed to the VLTi to avoid flooding.
• When a VLT switch determines that a VLT member port has failed (and that no other local
member ports are available), the peer with the failed member port notifies the remote peer that it
no longer has an active member port for a link. The remote peer then enables data forwarding
across the VLT interconnect for packets that would otherwise have been forwarded over the failed
member port. This mechanism ensures reachability and provides loop management.
• If all ports in the chassis interconnect trunk fail, or if the messaging infrastructure fails to
communicate across the interconnect trunk, the VLT management system uses the backup link
interface to determine whether the failure is a link-level failure or whether in fact the remote peer
has failed entirely. If the remote peer is still alive (heartbeat messages are still being received), the
VLT secondary switch disables its VLT port channels. If keepalive messages from the peer are not
being received, the peer continues to forward traffic, assuming that it is the last device available in
| Virtual Link Trunking (VLT)
922
Figure 48-1). The VLT peers belong to the same VRRP group and are assigned master
command on each peer.
show vrrp
show vrrp
for more information.
command output displays one peer as master and the other
Set