HP 4400 HP StorageWorks Fabric OS 6.4.1 Release Notes (5697-0760, November 201 - Page 75

Fabric OS 6.4.1 fixes, lists defects closed in the Fabric OS 6.4.1 firmware release.

Get HP 4400 PDF manuals and user guides View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 75 highlights

Fabric OS 6.4.1 fixes Table 13 lists defects closed in the Fabric OS 6.4.1 firmware release. Table 13 Fabric OS 6.4.1 closed defects Closed defect summary Solution In a dual Inter-fabric Link (IFL) FCR fabric with LSAN Matrix configured Fixed in Fabric OS 6.4.1. and LSAN binding enabled, disabling the EX_Port for one of the IFLs causes all FCR devices to be removed from the name server database. The Tape REC command fails in an FCR environment because the ori- Fixed in Fabric OS 6.4.1. ginator source ID in the header and in the body of the TAPE REC command frame do not match, resulting in data corruption on the tape. One or more fans go into a faulted state on the HP StorageWorks DC SAN Backbone Director Switch even though the fans are operating properly. Functional fans are improperly flagged as bad with error code [PLAT-5042], FAN I2C reset messages in the Raslog. Fixed in Fabric OS 6.4.1. When 8Gb switches and directors have an 8Gb blade in slot 1, frame drops occur in the fabric when Ex/VEx ports are configured. Hosts cannot see targets if there is an Ex/VEx port configured in the same ASIC chip as an F/E port with EGID 0. Customer may observe poor performance in the fabric when this condition occurs. Fixed in Fabric OS 6.4.1. Workaround prior to upgrade: User can verify that a fabric has this problem by running sloterrshow 1 on directors or sloterrshow on switches; the type6_miss counter should be seen continuously incrementing during traffic load on backend port/E_Port. Avoid configuring an EX_Port or a VEx_Port near an F/E port with an EGID of 0. To identify a port with an EGID of 0, login in as root and run bladeportmap [1]. The first port where Upt is not -1 uses EGID 0. Once the problem occurs, the user must make the F/E port into an EX_Port and then configure it back to an F/E port to fix the problem port. Execute the following instructions: 1. Disable the F/E port. 2. Configure the F/E port as an EX_Port for a valid FID. 3. Connect a link between the FID and the EX port (IFL). 4. Enable the port. 5. Verify that the link is online. Then disable the port. 6. Disable the EX_Port configuration. 7. Connect the host/ISL back to the F/E port. 8. Enable the port. HP StorageWorks Fabric OS 6.4.1 Release Notes 75

  • 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
Fabric OS 6.4.1 fixes
Table 13
lists defects closed in the Fabric OS 6.4.1 firmware release.
Table 13 Fabric OS 6.4.1 closed defects
Solution
Closed defect summary
Fixed in Fabric OS 6.4.1.
In a dual Inter-fabric Link (IFL) FCR fabric with LSAN Matrix configured
and LSAN binding enabled, disabling the EX_Port for one of the IFLs
causes all FCR devices to be removed from the name server database.
Fixed in Fabric OS 6.4.1.
The Tape REC command fails in an FCR environment because the ori-
ginator source ID in the header and in the body of the TAPE REC com-
mand frame do not match, resulting in data corruption on the tape.
Fixed in Fabric OS 6.4.1.
One or more fans go into a faulted state on the HP StorageWorks DC
SAN Backbone Director Switch even though the fans are operating
properly. Functional fans are improperly flagged as bad with error code
[PLAT-5042], FAN I2C
reset messages in the Raslog.
Fixed in Fabric OS 6.4.1.
Workaround prior to upgrade:
User can verify that a fabric has this
problem by running
sloterrshow
1
on directors or
sloterrshow
on
switches; the
type6_miss
counter
should be seen continuously
incrementing during traffic load on
backend port/E_Port. Avoid
configuring an EX_Port or a VEx_Port
near an F/E port with an EGID of 0.
To identify a port with an EGID of 0,
login in as root and run
bladeportmap [1]
. The first port
where
Upt
is not -1 uses EGID 0.
Once the problem occurs, the user
must make the F/E port into an
EX_Port and then configure it back
to an F/E port to fix the problem
port. Execute the following
instructions:
1.
Disable the F/E port.
2.
Configure the F/E port as an
EX_Port for a valid FID.
3.
Connect a link between the FID
and the EX port (IFL).
4.
Enable the port.
5.
Verify that the link is online.
Then disable the port.
6.
Disable the EX_Port configura-
tion.
7.
Connect the host/ISL back to the
F/E port.
8.
Enable the port.
When 8Gb switches and directors have an 8Gb blade in slot 1, frame
drops occur in the fabric when Ex/VEx ports are configured. Hosts
cannot see targets if there is an Ex/VEx port configured in the same
ASIC chip as an F/E port with EGID 0. Customer may observe poor
performance in the fabric when this condition occurs.
HP StorageWorks Fabric OS 6.4.1 Release Notes
75