HP StorageWorks 2/64 HP StorageWorks Fabric OS 5.0.5d Release Notes (AA-RW1WF- - Page 10

Fabric OS 5.0.5c, Fabric OS 5.0.5d

Get HP StorageWorks 2/64 - Core Switch PDF manuals and user guides View all HP StorageWorks 2/64 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 10 highlights

Fabric OS 5.0.5c fixes Table 4 lists improvements included in Fabric OS 5.0.5c. Table 4 Fabric OS 5.0.5c closed defects Closed Defects Switch panic or CP failover when a kernel process is spawned by a non-root user. Switch panics due to a bad ipaddress in the syslog.conf file. This affects all platforms. After an upgrade to Fabric OS 5.0.5x. dual CP switches show excessive TRCK-1004 logs though there is no change to the configuration. Fabric OS 5.0.5d fixes Table 4 lists improvements included in Fabric OS 5.0.5d. Table 5 Fabric OS 5.0.5d closed defects Closed Defects Switch panic can occur if an unstable or faulty port generates an excessive number of interrupts. Switch panic occurs when the Remote Procedure Call Daemon (RPCD) attempts to retrieve a non-initialized variable. When an FCP probe failure occurs, the failing port results in an "In_Sync" state. As a result the device does not appear in Name server because of the traffic interruption through this port. API library can crash during the activation of a large zone set. Due to Performance Server Daemon (PSD) panic assertions, the standby CP on all Directors can result in a reboot loop. Zone changes cause the CALD (Common Access Layer Daemon) to return a SCN-1001 code from the standby CP. The zoneObjectRename command allows the creation of duplicate aliases causing zone database corruption. 10

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
Fabric OS 5.0.5c
fi
xes
Table 4
lists improvements included in Fabric OS 5.0.5c.
Table 4 Fabric OS 5.0.5c closed defects
Closed Defects
Switch panic or CP failover when a kernel process is spawned by a non-root user.
Switch panics due to a bad ipaddress in the syslog.conf
fi
le. This affects all platforms.
After an upgrade to Fabric OS 5.0.5x. dual CP switches show excessive TRCK-1004 logs though there is no
change to the con
fi
guration.
Fabric OS 5.0.5d
fi
xes
Table 4
lists improvements included in Fabric OS 5.0.5d.
Table 5 Fabric OS 5.0.5d closed defects
Closed Defects
Switch panic can occur if an unstable or faulty port generates an excessive number of interrupts.
Switch panic occurs when the Remote Procedure Call Daemon (RPCD) attempts to retrieve a non-initialized
variable.
When an FCP probe failure occurs, the failing port results in an "In_Sync" state. As a result the device does
not appear in Name server because of the traf
fi
c interruption through this port.
API library can crash during the activation of a large zone set.
Due to Performance Server Daemon (PSD) panic assertions, the standby CP on all Directors can result in a
reboot loop.
Zone changes cause the CALD (Common Access Layer Daemon) to return a
SCN-1001
code from the
standby CP.
The
zoneObjectRename
command allows the creation of duplicate aliases causing zone database
corruption.
10