HP 1606 HP B-series Fabric OS 6.4.1b Release Notes (5697-0886, March 2011-incl - Page 67
Table 13 Fabric OS 6.4.1 closed defects, EX_Port or a VEx_Port near an F/E port
View all HP 1606 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 67 highlights
Table 13 Fabric OS 6.4.1 closed defects (continued) Closed defect summary Solution When 8Gb switches and directors have an 8Gb blade in slot 1, frame drops Fixed in Fabric OS 6.4.1. occur in the fabric when Ex/VEx ports are configured. Hosts cannot see Workaround prior to upgrade: targets if there is an Ex/VEx port configured in the same ASIC chip as an User can verify that a fabric has this F/E port with EGID 0. Customer may observe poor performance in the fabric when this condition occurs. 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. After upgrading an HP StorageWorks 4/256 SAN Director with FC4-48 Fixed in Fabric OS 6.4.1. blades installed, the HP StorageWorks 4/256 SAN Director 4/48 blade faults and traffic through the blade is disrupted. External RASLOG messages EM-1051 are seen reporting that a slot inconsistency was detected. The Login database gets corrupted after several switch enable/disable Fixed in Fabric OS 6.4.1. transitions. This happens when misbehaving devices bouncing offline/online do not participate in LIP to acquire a valid AL_PA and then later try to login with an invalid AL_PA. Fabric OS 6.4.1 fixes 67