HP Virtual Connect: Common Myths, Misperceptions, and Objections, Second Edition

24
Table 6. Virtual Connect versus Traditional Ethernet or Fibre Channel Switches
Description
Virtual Connect Traditional Switches
Provides port level ACLs, and VLAN
ACLs


Provides port trunking (EtherChannel)
on server downlinks


Provides user configurable QoS
features for individual server NICs


No impact on data center Spanning
Tree config or VTP config


Allows blade enclosure to represent
itself as a single, large hypervisor
host to external network


Does not require configuration &
management of traditional switches
inside each blade enclosure


Maintains consistent UUID for OS
image after server hardware
changes/moves


Maintains consistent server serial
number for OS image after server
hardware changes/moves


Maintains consistent MAC addresses
after server hardware
changes/moves


Maintains consistent WWNs after
server hardware changes/moves


When server admin moves server
profile, a downlink’s VLAN
assignments automatically follows


When server admin moves server
profile, a downlink’s VLAN tagging
configuration automatically follows


When server admin moves server
profile, an HBA’s SAN fabric
assignment automatically follows


Maintains consistent PXE setting for
server NICs after server hardware
changes/moves


Maintains consistent
FC Boot
parameters after server hardware
changes/moves


Enables Server Admin to make server
network connectivity changes without
interruption of LAN and SAN admins


Enables Server Admin to adjust
bandwidth allocation to a NIC on the
fly, from 100Mbps to 10Gbps.

