HP Brocade 8/12c HP Fabric OS 6.2.2f Release Notes (5697-1756, February 2012) - Page 42
Fixed in Fabric OS 6.2.2, If Fabric Watch
View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 42 highlights
Table 11 Fabric OS 6.2.2 closed defects (continued) Closed defect summary Solution Link timeout occurs on switch port connected to any Access Gateway during Fixed in Fabric OS 6.2.2 hafailover/reboot of AG switch with rlsdisable=0, causing traffic Workaround prior to update: Disable RLS disruption. as follows:Configure→system services→disable RLS probing If Fabric Watch fwalarms is turned off and Errlog is turned on, fabric watch daemon can crash causing a switch panic. Fixed in Fabric OS 6.2.2 Workaround prior to update: Disable ErrLog and Port Fencing (using the fwconfigure command) in the threshold alarm matrix configuration for all port related thresholds. This prevents the problem-causing functions from being called. Evmd (Event Monitor Daemon) crash causes switch to assert/reboot several Fixed in Fabric OS 6.2.2 hours after lscfg --delete when running SMI proxy client or SMI-like interface, due to timer events being processed in the context of a deleted logical switch. A switch panic occurs due to third-party management application giving Fixed in Fabric OS 6.2.2 bad response or no response to FCP LUN request. SwNs table lists one fewer name server entry than the actual number of devices (first entry shown in nsallshow CLI command) Fixed in Fabric OS 6.2.2 The urouteshow command lags for several seconds while displaying the Fixed in Fabric OS 6.2.2 route information. The lag is longer on products with large port counts, such as directors The errorshow command log still shows the original chassis name after Fixed in Fabric OS 6.2.2 a chassis name change. The sequence of creating two TI zones, not saving the change, and then modifying the attributes with the zone --add command results in misconfigured attributes that will cause software verify on remote switches when changes are committed. This can lead to a switch reboot or panic. Fixed in Fabric OS 6.2.2 Workaround prior to update: Other methods of creating TI Zones and modifying the definitions work seamlessly. It is just this odd set of steps that produce the failing condition. When creating multiple TI zones, they should be saved before modifying the attributes. You can clean up problem by using zone --add to modify the attributes again after the save. You can also delete and re-create the TI zone. Configuring IP address of CP1 blade from CP0 on any director: after Fixed in Fabric OS 6.2.2 hafailover the hostname portion of the configuration is no longer there Workaround prior to update: Run the for CP1. Other IP configuration information remains intact. ipaddrset command again from CP1 to configure CP1 hostname. The switchstatusshow command output was not updated after the faulty Fixed in Fabric OS 6.2.2 blade (multiprotocol router blade, multiprotocol extension blade, or 10/24 FCoE blade) was brought back up, enabled, and online. FDMI: fdmid crashes when a Brocade HBA with virtual ports is connected Fixed in Fabric OS 6.2.2 to a 4/256 SAN Director. Workaround prior to update: Log out all the devices that have registered their HBA information and log them in after the fabric is stable. 42