HP BL680c HP Virtual Connect Enterprise Manager User Guide - Page 25

Mixed Virtual Connect firmware versions and firmware compatibility in a VC Domain Group

Get HP BL680c - ProLiant - G5 PDF manuals and user guides
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 25 highlights

• Native • Smart Link • Private network • Preferred Link Connection • Preferred Link Connection Speed • Maximum Link Connection • Maximum Link Connection Speed • For each Fibre Channel SAN Fabric: • Fabric name • If VC Domain has firmware 2.0x and later: • Configuration speed • Login distribution • Fabric port location • Number of Fibre Channel SAN Fabrics configured in the VC Domain To add an unconfigured VC Module to a VC Domain Group, the following items must be identical: • Interconnect bays location and model • Enclosure model • Uplinks of the network and Fibre Channel SAN Fabric • Power state of the VC Modules Mixed Virtual Connect firmware versions and firmware compatibility in a VC Domain Group VCEM enables firmware compatibility using current and future versions of Virtual Connect firmware. This feature provides these benefits: • A single VC Domain Group can contain VC Domains running different firmware versions. The following table shows the supported combinations of Virtual Connect firmware within a single VC Domain Group. VC Domain Group VC Domain firmware 2.3x VC Domain firmware 2.1x VC Domain firmware 2.0x VC firmware 2.3x Yes No No VC firmware 2.1x Yes Yes No VC firmware 2.0x Yes Yes Yes * Virtual Connect 2.3x features must be disabled for it to be in the same group as Virtual Connect 2.1x or 2.0x. * Virtual Connect 2.1x features must be disabled for it to be in the same group as Virtual Connect 2.0x. NOTE: If you have a VC Domain Group 2.0x or 2.1x and all the VC Domains have been upgraded to Virtual Connect 2.3x, the group will not automatically function as a VC Domain Group 2.3x. To enable Virtual Connect 2.3x functionality, see Upgrading VC Domain Group Firmware Mode. • VCEM 6.0 might be able to support future versions of Virtual Connect firmware in a compatibility mode. This compatibility mode enables a new Virtual Connect firmware version to be used immediately with a VCEM 6.0 installation. For example, if Virtual Connect released a 2.2x version of its firmware, a domain within a 2.1x VC Domain Group could be upgraded to the 2.2x version of the firmware while preserving the 2.1x level of functionality. The VC Domain Group will operate at the firmware version with which it was created. A subsequent VCEM release would support the new functionality. VC Domains 25

  • 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
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
•
Native
•
Smart Link
•
Private network
•
Preferred Link Connection
•
Preferred Link Connection Speed
•
Maximum Link Connection
•
Maximum Link Connection Speed
•
For each Fibre Channel SAN Fabric:
Fabric name
•
•
If VC Domain has firmware 2.0x and later:
•
Configuration speed
•
Login distribution
•
Fabric port location
•
Number of Fibre Channel SAN Fabrics configured in the VC Domain
To add an unconfigured VC Module to a VC Domain Group, the following items must be identical:
•
Interconnect bays location and model
•
Enclosure model
•
Uplinks of the network and Fibre Channel SAN Fabric
•
Power state of the VC Modules
Mixed Virtual Connect firmware versions and firmware compatibility in a VC Domain Group
VCEM enables firmware compatibility using current and future versions of Virtual Connect firmware. This
feature provides these benefits:
•
A single VC Domain Group can contain VC Domains running different firmware versions. The following
table shows the supported combinations of Virtual Connect firmware within a single VC Domain Group.
VC firmware 2.0x
VC firmware 2.1x
VC firmware 2.3x
VC Domain Group
Yes
Yes
Yes
VC Domain firmware 2.3x
Yes
Yes
No
VC Domain firmware 2.1x
Yes
No
No
VC Domain firmware 2.0x
* Virtual Connect 2.3x features must be disabled for it to be in the same group as Virtual Connect 2.1x
or 2.0x.
* Virtual Connect 2.1x features must be disabled for it to be in the same group as Virtual Connect
2.0x.
NOTE:
If you have a VC Domain Group 2.0x or 2.1x and all the VC Domains have been upgraded
to Virtual Connect 2.3x, the group will not automatically function as a VC Domain Group 2.3x.
To enable Virtual Connect 2.3x functionality, see
Upgrading VC Domain Group Firmware Mode
.
•
VCEM 6.0 might be able to support future versions of Virtual Connect firmware in a compatibility mode.
This compatibility mode enables a new Virtual Connect firmware version to be used immediately with a
VCEM 6.0 installation. For example, if Virtual Connect released a 2.2x version of its firmware, a domain
within a 2.1x VC Domain Group could be upgraded to the 2.2x version of the firmware while preserving
the 2.1x level of functionality. The VC Domain Group will operate at the firmware version with which it was
created. A subsequent VCEM release would support the new functionality.
VC Domains
25