Cisco MGX 8850 PXM45 Release Notes page 61

Table 23
DDTs Issue
CSCdy70541
CSCdy71636
CSCdy72444
CSCdy73577
CSCdy73583
CSCdy73683
OL-2914-01 Rev D0, July 3, 2003
Severity 2 Open Caveats in MGX 8830 3.0.10 Software (continued)
Description
Hardware: pxm1e
Symptom: Primary clock status is lockable but still the active clock is internal clock...
Conditions: The primary clock was configured from trunk 7:2.2:22 and it was active.
The secondary clock was configured from trunk 7:2.11:11 and was in bad state
because of no clock signal. To clear this problem from secondary clock the "cnfclksrc
secondary 7:2.9:29" command was executed. The trunk 7:2.9:29 was an active trunk
with PNNI-link established both ways. After executing this command the active clock
status became from "internal clock" even though the primary clock is still in locked
state. Also, the secondary clock is still shown as 7:2.11:11 instead of 7:2.9:29.
Moreover, the status of secondary clock has became "UNKNOWN"
Workaround: Port 2.11:11 is oper down. Bring it up active (either by loopback or
physical cable) delclksrc secondary configure new clock source.
Hardware: pxm1e
Symptom: The customer sees traffic stop in one direction spontaneously.
Conditions: It happens spontaneously on an FRSM 8T1E1 card on a POP1 shelf.
POP1 shelf is a feeder to an MGX 2 shelf.
Workaround: Using CWM reconfigure the CIR of the connection or delete and re add
the PVC.
Hardware: pxm1e
Symptom: Statistical alarm does not clear after 24 hours
Conditions: Line 2.3 went into statistical alarm. the line 2.3 went into major alarm
and never cleared out of it. cnfalm -ds3 2.3 -dsev (major) was set. After 24 hours
alarm should have cleared.
Workaround: Unknown.
Hardware: pxm1e
Symptom: Oam_conn_upoamerr: failed reading ATLAS for connection status.
Conditions: After multiple switchcc.
Workaround:
Hardware: pxm1e
Symptom: 1. The clock has failed and is stuck in "clock set Nak" state. The clock
frequency samples detected by the PXM1E are compliant and good.
Conditions: Do a switchcc from 7->8, then do a switchredcd from 30->28.
Workaround: Unknown.
Hardware: pxm1e
Symptom: New connection across MPG stay in failed state.
Conditions: Added few new connections across MPG. The connection stayed in failed
state for 15+ minutes. The connections were in CTRLR-ABIT alarm but eventually
came up OK. PXM1E node is acting as a PGL for the network. Last fail cause does
not specify the error.
Workaround: Unknown.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
Caveats
61