HP Brocade 8/24c HP Virtual Connect: Common Myths, Misperceptions, and Objecti - Page 17

VC-FC does not support Cisco's VSAN or Brocades Virtual Fabric

Get HP Brocade 8/24c PDF manuals and user guides View all HP Brocade 8/24c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 17 highlights

Table 4. VC Comparison • • • • • • Virtual Connect • Doesn't: o Keeps the same SAN assignments with the server Does keep the server serial number the same after hardware replacement. o Prevents problems with application licensing if application uses server serial number as part of license data Does keep the server UUID the same after hardware replacement. Does keep the server MAC addresses the same after hardware replacement. o Prevents problems with application licensing if application uses server's MAC address as part of license data Does keep the server WWNs the same after hardware replacement. Does keep Fibre Channel boot parameters the same after hardware replacement Does allow for pre-provisioning o Since MAC addresses and WWNs are known BEFORE the server is received from HP, administrators can pre-provision the server o Knowing MAC addresses before receiving the server from HP means things like DHCP reservations can be completed BEFORE server is physically in hand o Knowing WWNs before receiving the server from HP means things like WWN zoning, Selective Storage Presentation/LUN mapping & presentation, etc. can be completed BEFORE server is physically in hand N/A - VC provides same result as DHCP Option 82 and provides additional features #30: VC-FC doesn't provide login distribution and failover on FC uplinks to the SAN Incorrect: FC login distribution and failover features are provided in VC firmware version 1.31 and above. With these features, server HBA fabric logins can be automatically distributed across all VCFC uplink ports on the same VC-FC module. Should a port fail or lose link, VC-FC automatically re-logs in the WWN into the fabric on another active VC-FC uplink port from the same VC-FC module. #31: All VC-FC uplinks have to be connected to the same SAN fabric Incorrect: Support for multiple fabrics per VC-FC module is provided in VC firmware version 1.31 and above. This feature allows the Storage administrator to assign any of the available VC-FC uplinks to a different SAN fabric and dynamically assign server HBAs to the desired SAN fabric. #32: VC-FC does not support Cisco's VSAN or Brocades Virtual Fabric features Incorrect: Virtual Connect can support both Cisco's VSAN and Brocades Virtual Fabric solutions. The Storage Administrator can create a VC SAN Fabric with the upstream FC switch ports configured for either Dynamic WWN-based or Port-based membership. 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
17
Table 4. VC Comparison
o
Keeps the same SAN assignments with the server
•
Does keep the server serial number the same after hardware
replacement.
o
Prevents problems with application licensing if application
uses server serial number as part of license data
•
Does keep the server UUID the same after hardware replacement.
•
Does keep the server MAC addresses the same after hardware
replacement.
o
Prevents problems with application licensing if application
uses server's MAC address as part of license data
•
Does keep the server WWNs the same after hardware replacement.
•
Does keep Fibre Channel boot parameters the same after hardware
replacement
•
Does allow for pre-provisioning
o
Since MAC addresses and WWNs are known BEFORE the
server is received from HP, administrators can pre-provision
the server
o
Knowing MAC addresses before receiving the server from
HP means things like DHCP reservations can be completed
BEFORE server is physically in hand
o
Knowing WWNs before receiving the server from HP means
things
like
WWN
zoning,
Selective
Storage
Presentation/LUN mapping & presentation, etc. can be
completed BEFORE server is physically in hand
Virtual Connect
Doesn’t:
•
N/A – VC provides same result as DHCP Option 82 and provides
additional features
#30: VC-FC doesn’t provide login distribution and failover on FC uplinks
to the SAN
Incorrect:
FC login distribution and failover features are provided in VC firmware version 1.31 and
above. With these features, server HBA fabric logins can be automatically distributed across all VCFC
uplink ports on the same VC-FC module.
Should a port fail or lose link, VC-FC automatically re-logs in
the WWN into the fabric on another active VC-FC uplink port from the same VC-FC module.
#31: All VC-FC uplinks have to be connected to the same SAN fabric
Incorrect:
Support for multiple fabrics per VC-FC module is provided in VC firmware version 1.31
and above. This feature allows the Storage administrator to assign any of the available VC-FC uplinks
to a different SAN fabric and dynamically assign server HBAs to the desired SAN fabric.
#32:
VC-FC does not support Cisco’s VSAN or Brocades Virtual Fabric
features
Incorrect:
Virtual Connect can support both Cisco’s VSAN and Brocades Virtual Fabric solutions.
The Storage Administrator can create a VC SAN Fabric with the upstream FC switch ports configured
for either Dynamic WWN-based or Port-based membership.