HP StorageWorks 2/32 HP StorageWorks Fabric OS 5.2.1b Release Notes (AA-RWEYC- - Page 15

Fabric OS 5.2.1 fixes, Table 3 Fabric OS 5.2.1 closed defects

Page 15 highlights

portcfgdefault command function change for the Brocade 4Gb SAN Switch for HP c-Class BladeSystem Update to Brocade 4Gb SAN Switch for HP c-Class BladeSystem instructions. Zoning considerations with FC4-48 blade With Fabric OS 5.2.1b, the portcfgdefault command now resets the configuration to HP factory default port settings. After connecting to the Brocade 4Gb SAN Switch via the Onboard Administrator (OA) connect command, you will be in the switch CLI prompt. To return to the OA serial prompt: • Type Exit to log out of the switch. • Press Shift-Ctrl-underscore (escape sequence) to return to the OA prompt. B-Series switches running pre-5.2.0 firmware do not accept zone databases with Domain, Port Index, references to ports higher than 255. Zoning in Fabric OS 5.2.0 and later, therefore, do not allow a Domain, Port Index entry for ports above 255 to be created unless all switches in the fabric are at Zoning considerations continued... Fabric OS 5.2.0 or later versions. Once such an entry has been put into the zone database, an attempt to connect a pre-Fabric OS 5.2.0 switch to the fabric results in that switch being segmented with a Zone Mismatch segmentation reason. Any zoning that is already in use can continue to be used. However, in Fabrics containing pre-Fabric OS 5.2.0 switches, if new devices are added on the upper 16 ports (ports 32-47) of the FC4-48 port blade, then WWN zoning has to be used for those devices. If there is an existing Domain Port Index zone that connects to ports 32-47, HP recommends that you transform just that zone to WWN zoning. This would minimize the likelihood of rebuilding the entire fabric. Fabrics containing only Fabric OS 5.2.0 and later switches have no zoning limitation. Fabric OS 5.2.1 fixes Table 3 lists defects closed in the Fabric OS 5.2.1 firmware release. Table 3 Fabric OS 5.2.1 closed defects Closed defect summary Solution 4/256 director running FICON with fsmode enabled panics after upgrade from FOS v5.0.x, to either v5.1.x or v5.2.0. Fixed per Fabric OS 5.2.1. After previous diag failure, 2/128 director LEDs may blink indicating a failure on subsequent diag command execution, even though slotshow command shows proper operation. Fixed per Fabric OS 5.2.1. FR4-18i router blade POST failed after slotpoweroff/on. Fixed per Fabric OS 5.2.1. Error messages may result after a lot of diagnostic tests run during warm recovery on standby. Fixed per Fabric OS 5.2.1. Switch panics in rare cases during HAfailover due to zoning daemon assertion. Fixed per Fabric OS 5.2.1. Panic observed on new active CP after HAfailover, running I/O through AD, mirrored port and FC4-48. Unlikely user scenario Fixed per Fabric OS 5.2.1. Fastboot on remote switch followed by HAfailover on 4/256 can cause multiple kernel panics & error messages. Unlikely user scenario Fixed per Fabric OS 5.2.1. When using continuous mode in Fabric Watch with timing interval of 1 second, too many e-mail alert messages can cause unexpected termination of other processes. Fixed per Fabric OS 5.2.1. HP StorageWorks Fabric OS 5.2.1b release notes 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20

portcfgdefault
command function change
for the Brocade 4Gb SAN
Switch for HP c-Class
BladeSystem
With Fabric OS 5.2.1b, the
portcfgdefault
command now resets the
con
guration to HP factory default port settings.
Update to Brocade 4Gb
SAN Switch for HP c-Class
BladeSystem instructions.
After connecting to the Brocade 4Gb SAN Switch via the Onboard
Administrator (OA)
connect
command, you will be in the switch CLI prompt.
To return to the OA serial prompt:
Type
Exit
to log out of the switch.
Press
Shift-Ctrl-underscore
(escape sequence) to return to the OA prompt.
Zoning considerations with
FC4–48 blade
B-Series switches running pre-5.2.0
rmware do not accept zone databases
with Domain, Port Index, references to ports higher than 255. Zoning in Fabric
OS 5.2.0 and later, therefore, do not allow a Domain, Port Index entry for
ports above 255 to be created unless all switches in the fabric are at
Zoning considerations continued...
Fabric OS 5.2.0 or later versions. Once such an entry has been put into
the zone database, an attempt to connect a pre-Fabric OS 5.2.0 switch to
the fabric results in that switch being segmented with a Zone Mismatch
segmentation reason.
Any zoning that is already in use can continue to be used. However, in
Fabrics containing pre-Fabric OS 5.2.0 switches, if new devices are added
on the upper 16 ports (ports 32-47) of the FC4-48 port blade, then WWN
zoning has to be used for those devices. If there is an existing Domain Port
Index zone that connects to ports 32–47, HP recommends that you transform
just that zone to WWN zoning. This would minimize the likelihood of
rebuilding the entire fabric.
Fabrics containing only Fabric OS 5.2.0 and later switches have no zoning
limitation.
Fabric OS 5.2.1
xes
Table 3
lists defects closed in the Fabric OS 5.2.1
rmware release.
Table 3 Fabric OS 5.2.1 closed defects
Closed defect summary
Solution
4/256 director running FICON with fsmode enabled panics after
upgrade from FOS v5.0.x, to either v5.1.x or v5.2.0.
Fixed per Fabric OS 5.2.1.
After previous diag failure, 2/128 director LEDs may blink indicating
a failure on subsequent
diag
command execution, even though
slotshow
command shows proper operation.
Fixed per Fabric OS 5.2.1.
FR4-18i router blade POST failed after
slotpoweroff
/
on
.
Fixed per Fabric OS 5.2.1.
Error messages may result after a lot of diagnostic tests run during
warm recovery on standby.
Fixed per Fabric OS 5.2.1.
Switch panics in rare cases during HAfailover due to zoning daemon
assertion.
Fixed per Fabric OS 5.2.1.
Panic observed on new active CP after
HAfailover
, running I/O
through AD, mirrored port and FC4-48.
Unlikely user scenario
Fixed per Fabric OS 5.2.1.
Fastboot on remote switch followed by HAfailover on 4/256 can
cause multiple kernel panics & error messages.
Unlikely user scenario
Fixed per Fabric OS 5.2.1.
When using continuous mode in Fabric Watch with timing interval of
1 second, too many e-mail alert messages can cause unexpected
termination of other processes.
Fixed per Fabric OS 5.2.1.
HP StorageWorks Fabric OS 5.2.1b release notes
15