HP StorageWorks 1606 HP StorageWorks Fabric OS 6.3.0 release notes (5697-0358, - Page 30

Virtual Fabrics, Licensing behavior

Page 30 highlights

a rename, per the logic described above, login group names can be the same for WWNs differing only in OUIs. The merge logic would drop one of the login groups to satisfy the requirement to keep the login group name unique in the fabric-wide configuration. • Ethernet switch services must be explicitly enabled using the command fosconfig -enable ethsw before powering on a DC SAN Director Switch 10/24 FCoE Blade. Failure to do so causes the blade to be faulted (fault 9). • To support nondisruptive firmware upgrades on the DC SAN Backbone Director/DC04 SAN Director, a new service, ethsw, is being introduced to enable Ethernet switching on the DC SAN Director Switch 10/24 FCoE Blade in Fabric OS 6.3. LAN switching is disabled by default in Fabric OS 6.3. The user must explicitly enable Ethernet switch service using the command fosconfig -enable ethsw to prevent FC traffic interruption. • Upgrading from Fabric OS 6.x to 6.3 is nondisruptive. You can enable ethsw after upgrading without interrupting FC traffic. Upgrading the 2408 FCoE Converged Network Switch from Fabric OS 6.1.2_cee1 to 6.3 will disrupt the FC traffic. A firmware download of FOS 6.3 to another version with HP StorageWorks DC SAN or DC04 SAN Directors with one or more DC SAN Director Switch 10/24 FCoE blades installed will disrupt traffic through the blade. HA Failover of CP blades in either of these directors will also result in disruption of traffic through the 10/24 FCoE blades. • Upgrades from Fabric OS 6.3 to future releases will be nondisruptive to data traffic and will have behavior similar to a CP failover; ethsw remains unchanged. • Downgrade from Fabric OS 6.3 to 6.1.2_cee1 is disruptive if ethsw is enabled on Fabric OS 6.3. • Downgrade from Fabric OS 6.3 to 6.1.2_cee1 is nondisruptive if ethsw has never been enabled with Fabric OS 6.3. • Connecting a 2408 FCoE Converged Network Switch to an FCR-capable switch with fcrbcast config enabled will cause a storm of broadcast traffic, resulting in termination of iswitchd. Virtual Fabrics • On VF-capable platforms, the VF feature (initially supported with Fabric OS 6.2.0a) must be enabled in order to utilize the related capabilities, including logical switches and logical fabrics. • When creating logical fabrics that include switches that are not VF-capable, it is possible to have two logical switches with different FIDs in the same fabric. Be sure to verify that the FIDs match for all switches in the same logical fabric. • In order to support nondisruptive HCL on an 8/40 SAN Switch with VF enabled, the total zoning DB size for the entire chassis should not exceed 1 MB. Otherwise, ports may be re-initialized, causing frame drops during an HCL if the switch has a zoning database that is 1 MB or larger. • A switch with VF enabled cannot participate in a fabric that uses IP filter or password database distribution or administrative domains. You must disable the VF feature before deploying it in a fabric that uses these features. • VF is not supported on the 1606 Extension SAN switch. • VF-dedicated ISLs are supported on the DC SAN Director Switch Multiprotocol Extension Blade. XISLs are not supported. Licensing behavior When operating a switch with Fabric OS 6.3.x, some licenses may be displayed as Unknown. This is due to changes in licensing requirements for some features that no longer require a license key and may still be installed on a switch. 30

  • 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

a rename, per the logic described above, login group names can be the same for WWNs differing
only in OUIs. The merge logic would drop one of the login groups to satisfy the requirement to
keep the login group name unique in the fabric-wide configuration.
Ethernet switch services must be explicitly enabled using the command
fosconfig –enable
ethsw
before powering on a DC SAN Director Switch 10/24 FCoE Blade. Failure to do so causes
the blade to be faulted (fault 9).
To support nondisruptive firmware upgrades on the DC SAN Backbone Director/DC04 SAN
Director, a new service,
ethsw
, is being introduced to enable Ethernet switching on the DC SAN
Director Switch 10/24 FCoE Blade in Fabric OS 6.3. LAN switching is disabled by default in
Fabric OS 6.3. The user must explicitly enable Ethernet switch service using the command
foscon-
fig –enable ethsw
to prevent FC traffic interruption.
Upgrading from Fabric OS 6.x to 6.3 is nondisruptive. You can enable
ethsw
after upgrading
without interrupting FC traffic. Upgrading the 2408 FCoE Converged Network Switch from Fabric
OS 6.1.2_cee1 to 6.3 will disrupt the FC traffic. A firmware download of FOS 6.3 to another
version with HP StorageWorks DC SAN or DC04 SAN Directors with one or more DC SAN Dir-
ector Switch 10/24 FCoE blades installed will disrupt traffic through the blade. HA Failover of
CP blades in either of these directors will also result in disruption of traffic through the 10/24
FCoE blades.
Upgrades from Fabric OS 6.3 to future releases will be nondisruptive to data traffic and will have
behavior similar to a CP failover;
ethsw
remains unchanged.
Downgrade from Fabric OS 6.3 to 6.1.2_cee1 is disruptive if
ethsw
is enabled on Fabric OS
6.3.
Downgrade from Fabric OS 6.3 to 6.1.2_cee1 is nondisruptive if
ethsw
has never been enabled
with Fabric OS 6.3.
Connecting a 2408 FCoE Converged Network Switch to an FCR-capable switch with
fcrbcast
config
enabled will cause a storm of broadcast traffic, resulting in termination of
iswitchd
.
Virtual Fabrics
On VF-capable platforms, the VF feature (initially supported with Fabric OS 6.2.0a) must be enabled
in order to utilize the related capabilities, including logical switches and logical fabrics.
When creating logical fabrics that include switches that are not VF-capable, it is possible to have
two logical switches with different FIDs in the same fabric. Be sure to verify that the FIDs match
for all switches in the same logical fabric.
In order to support nondisruptive HCL on an 8/40 SAN Switch with VF enabled, the total zoning
DB size for the entire chassis should not exceed 1 MB. Otherwise, ports may be re-initialized,
causing frame drops during an HCL if the switch has a zoning database that is 1 MB or larger.
A switch with VF enabled cannot participate in a fabric that uses IP filter or password database
distribution or administrative domains. You must disable the VF feature before deploying it in a
fabric that uses these features.
VF is not supported on the 1606 Extension SAN switch.
VF-dedicated ISLs are supported on the DC SAN Director Switch Multiprotocol Extension Blade.
XISLs are not supported.
Licensing behavior
When operating a switch with Fabric OS 6.3.x, some licenses may be displayed as
Unknown
. This
is due to changes in licensing requirements for some features that no longer require a license key and
may still be installed on a switch.
30