Cisco MGX 8850 PXM45 Release Notes page 79

Table 28
DDTs Issue
CSCdy52131
CSCdy53083
CSCdy53476
CSCdy54351
CSCdy55759
CSCdy56415
OL-2914-01 Rev D0, July 3, 2003
Severity 2 Open Caveats for MGX 8850 3.0.10 Software (continued)
Description
Hardware: pxm1e
Symptom: FI: reset/failure on PXM1E is reported incorrectly in error log and reset
type & error is not logged.
Conditions: When we insert the QE0 reset (test 4a) fault. The log does not show reset
type and error reason. FI card is in slot 8. When we insert reset QE1 (test 4b) fault on
PXM1E. The failure and reset reason is not reported in the log correctly. The FI card
is in slot 8
Workaround: Unknown.
Hardware: axsm1b_oc12
Symptom: Core dump on slot #14, AXSM OC12
Conditions: Following a switchcc script running for about 3 days.
Workaround: None.
Hardware: pxm45b
Symptom: All service modules and standby PXM in the node reset/boot continuously.
Conditions: Unknown failure of the standby PXM.
Workaround: Remove the standby PXM and reset the active PXM.
Hardware: pxm45b
Symptom: Slave end persistent SPVC mismatch on frame_discard field between ram
and disk; i.e., disk shows for this connection frame_discard is OFF, but ram shows it
is ON.
Conditions: A routed persistent SPVC, where master end has frame_discard turned
on. Then slave end persistent SPVC will have frame_discard field mismatch between
ram and disk.
Workaround: There are 2 ways to workaround: 1) From line card CLI, do
upcon/dncon, or cnfcon for the given connection. 2) Switchcc from controller card.
This will only fix the first 10 mismatched SPVC connections.
Hardware: pxm45b
Symptom: Executed command "memshow ?" on PXM45 sw revision 2.1(80.0) and
console stopped responding to commands.
Conditions: Command "memshow ?" on active PXM45 sw rev 2.2(80.0) caused the
console to hang.
Workaround: No workaround at this time. Do not execute the command.
Hardware: pxm1e
Symptom: dspdiagerr doesn't update failure message
Conditions: When online diag running on active & standby PXMs and if the test fail
on active PXM then the PXM switchover and dspdiagerr record the message and test
will continue on the new standby PXM. But after the another test failed on the newly
standby PXM, dspdiagerr removed the previous message and did not update with new
failure message.
Workaround: Unknown.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
Caveats
79