Specifications

45Fabric OS 4.4.0f release notes
Issue: Both CPs reboot at same time
after blade replacement.
Symptom: During initialization on a
Core Switch 2/64, a blade is faulted
and sysctrl tries to shut down the
blade. During this shutdown process,
the object used to reference this
blade has not been initialized
causing the CP to ASSERT due to an
invalid object
Fixed
Issue: Without Fabric Watch license,
snmpd panic during mib walk.
Symptom:
run: snmpwalk -v3 -u snmpadmin1
10.64.148.56
.1.3.6.1.4.1.1588.2.1.1.1.10.1;
There will be 19000 no fabric watch
license printed, then snmpd panics.
Fixed
Issue: Memory corruption when
management software sends fabric
slot information request through
msd, which causes a switch panic.
Symptom: kSWD kill of msd,
portlogdump has following entry
earlier: msd msRemQ 255 f004
00fffc7b,00fffc2c,10000060,69805
fe1 <-- GSLOTD
Fixed
Issue: When there is a faulted blade
in a chassis based switch, Fabric
Manager shows the switch to be
unreachable.
Symptom: A switch is seen as
"Unknown" in FM. Unable to fully
manage switch through Fabric
Manager.
Fixed
Table 9 Fabric OS 4.4.0e closed issues summary
Closed defect Status