HP Virtual Connect for the Cisco Network Administrator

HP Virtual Connect for Cisco Network Administrators (version 4.x)
Document Number: C01386629 Date: January 2014
page 35
Create a virtual Fibre Channel interface to carry the FCoE traffic through eth1/5:
 interface vfc 2005
 bind interface port-channel 200
 no shutdown
Assign the vfc interface and the Fibre Channel port to the FCoE VSAN:
 vsan database
 vsan 201
 vsan 201 interface fc 2/1
 vsan 201 interface vfc 2005
Configure the interface connected to the datacenter LAN:
 interface eth 1/17
 switchport mode trunk
 switchport trunk allowed vlan 1,10,20
Configuration of the zone:
Create zones:
 zone name fcoe-zone vsan 201
 member pwwn 20:53:00:02:ac:00:15:9d {This is the WWN of the second 3PAR controller port}
 member pwwn 50:06:0b:00:00:c3:1a:22 {This is the WWN of the Blade FlexFabric Adapter port 2}
Create zoneset:
 zoneset name zoneset1 vsan 201
 member fcoe-zone
Activate zoneset:
 zoneset activate name zoneset1 vsan 201
Comparing VC and VMware Networking Technology
One method of understanding how Virtual Connect operates on the LAN is to compare the Virtual
Connect networking components and their functionality to the networking components of a VMware
ESX server. Since the networking technology used in a VMware ESX server is commonly
understood and accepted by many customers, understanding the many similarities between VC and a
VMware ESX server will help an implementer have a better understanding of how Virtual Connect
looks to, and behaves on, the external network. Just to be clear, Virtual Connect and a VMware ESX
server are fundamentally different products and address completely different needs within the
datacenter. This comparison is strictly about understanding the similarities between the two products