HP 4400 HP B-series Fabric OS 6.3.2d Release Notes (5697-1105, July 2011) - Page 44

Fixed in Fabric OS 6.3.2., session,

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 44 highlights

PLOGI ACC is dropped when there is back-to-back plogin to a well- known address such as msd, nsd, fabric controller, etc., before the switch route setup is completed. The PLOGIs are held in queue without being ACC'd until the route setup is completed, but the issue is that once the setup is done, only one of the PLOGIs is ACC'd and the rest are dropped. Applies to any switch running 6.x Fabric OS, but more likely in directors. This is an unlikely scenario, because most devices do not perform such back-to-back logins early during switch/fabric bring up. Fixed in Fabric OS 6.3.2. During a stress test where interface toggling was triggered while a login is pending, a kernel panic occurred on the 2408 FCoE switch or 10/24 Fixed in Fabric OS 6.3.2. FCoE blade. When F_Port trunking is activated and after the master trunk goes offline, the switch adds the new master trunk to the list of ports, which will send EFP/BF/DIA flood. The ports remain in this state until all N_Ports are taken offline and logged back into the fabric again. Build Fabric (BF) is sent to the AG. AG forwarding the BF to redundant fabric caused fabric disruption. Fixed in Fabric OS 6.3.2. iSCSI director blade iscsicfg -commit all hangs the switch Telnet Fixed in Fabric OS 6.3.2. session, and hafailover is needed to recover. Weblinker terminated while removing slot-based license. 1. Open the switch via http and get into the licenseadmin page, Switchadmin -> licenseadmin. 2. Remove the Advanced extension slot based license. Weblinker is terminated. The daemon is restarted without further functional impact. Fixed in Fabric OS 6.3.2. With VF disabled, aborts and timeouts were seen on traffic over FCIP of FID 128 when Port Based Route Policy (aptpolicy of 1) was not propagated from CP to DP properly. Fixed in Fabric OS 6.3.2. 44

  • 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
Fixed in Fabric OS 6.3.2.
PLOGI ACC is dropped when there is back-to-back
plogin
to a well-
known address such as msd, nsd, fabric controller, etc., before the
switch route setup is completed. The PLOGIs are held in queue without
being ACC'd until the route setup is completed, but the issue is that
once the setup is done, only one of the PLOGIs is ACC'd and the rest
are dropped. Applies to any switch running 6.x Fabric OS, but more
likely in directors. This is an unlikely scenario, because most devices
do not perform such back-to-back logins early during switch/fabric
bring up.
Fixed in Fabric OS 6.3.2.
During a stress test where interface toggling was triggered while a login
is pending, a kernel panic occurred on the 2408 FCoE switch or 10/24
FCoE blade.
Fixed in Fabric OS 6.3.2.
When F_Port trunking is activated and after the master trunk goes offline,
the switch adds the new master trunk to the list of ports, which will send
EFP/BF/DIA flood. The ports remain in this state until all N_Ports are
taken offline and logged back into the fabric again. Build Fabric (BF)
is sent to the AG. AG forwarding the BF to redundant fabric caused
fabric disruption.
Fixed in Fabric OS 6.3.2.
iSCSI director blade
iscsicfg -commit all
hangs the switch Telnet
session, and
hafailover
is needed to recover.
Fixed in Fabric OS 6.3.2.
Weblinker terminated while removing slot-based license.
1.
Open the switch via http and get into the licenseadmin page,
Switchadmin -> licenseadmin.
2.
Remove the Advanced extension slot based license.
Weblinker is terminated.
The daemon is restarted without further functional impact.
Fixed in Fabric OS 6.3.2.
With VF disabled, aborts and timeouts were seen on traffic over FCIP
of FID 128 when Port Based Route Policy (aptpolicy of 1) was not
propagated from CP to DP properly.
44