Specifications

47Fabric OS 4.4.0f release notes
Closed issues from Fabric OS 4.4.0f
Table 10 lists issues resolved with the release of Fabric OS version 4.4.0f.
Table 10 Fabric OS 4.4.0f closed issues summary
Closed defect Status
Issue: When "Long Distance Fabric"
parameter is configured on 1 Gb
StorageWorks 8 and 16 switches to
include a SAN Switch 4/32 in the
fabric, ISL ports on the older switches
get link timeouts.
1 Gb StorageWorks 8 and 16
switches running FOS 2.x must set the
Long Distance Fabric parameter ON
when connected to a SAN Switch
4/32. This results in a Continuous
Link Timeout.
Workaround: Do not use Long
Distance Fabric parameter. Use
portcfglongdistance to set
Long distance link on individual
port.
Issue: DCC policy is not enforced
properly after
failover/reboot/fastboot.
Symptom: DCC_POLICY is not
enforced if only 1 CP is rebooted or
fastbooted during either cold or
warm recovery. Rebooting or
fastbooting both CPs does not show
any error.
Workaround: Issue a subsequent
secpolicyactivate after the
reboot/fastboot completes to
reestablish the DCC policy.
Issue: When a disk drive on a loop is
replaced, the Nameserver still shows
the WWN of the old drive.
Symptom: During JBOD drive
replacement testing, the new drive
WWN information is not listed in the
switch name server table. The
portloginshow command
displays the correct WWN of the
drive, but the old wwn shows up in
the name server table.
Workaround: After swapping the
device, portdisable and
portenable will correct the
portwwn in the NS database.
Issue: Switch does not pass traffic in
interopmode with Window host if
there is a zone change performed
without a switch reboot.
Symptom: FC trace showed FOS 4.4
switch rejecting a GPN_ID with the
error port ID not in register.
Workaround: Switch reboot.