User guide

Closed issues from previous 4.2.2a release34
On a large fabric, when using a v4.x
switch as a proxy, an
ERR_LOGICAL_BUSY is always
returned when discovering one
particular switch (dev185) with the API.
Fixed.
If customer has an EE monitor defined
that incorporates the last 15 ports and
changes the PID format to "2", the
resulting EE monitor will change to an
out of range port number. E.g. 7f
changes to 8f.
Fixed.
SCALABILITY: Zone contents between
memory and flash show differences.
Switch will not join in the sec fabric after
fastboot.
Fixed.
API Applications that use
GetAllObjects, in a large Fabric with
a large number of devices, may
observe that this function takes a long
time to complete.
Fixed.
A single security violation error entry is
logged when multiple similar violations
originating from different IP addresses
are detected.
Fixed.
API Applications that use
GetAllObjects, in a large Fabric with a
large number of devices, may observe
that this function takes a long time to
complete.
Fixed.
Firmwaredownload failed on one of the
core chassis (Core Switch 2/64) when
there were 21 switches doing
firmwaredownload at the same time in
4x30 fabric
Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued)
Fabric OS 4.2.2a Issue Status