Contributor
•
168 Messages
CM Event Type Codes
@EG , @BruceW - Could you please be so kind and double check these CM Event Type Codes below for accuracy.
CM-STATUS Event Type Code |
Event Condition |
Event Trigger |
0 |
Reserved |
|
1 |
Secondary Channel MDD timeout |
Lost MDD Timer expiry of a secondary channel advertised as active in the primary channel MDD. |
2 |
QAM/FEC lock failure |
Loss of QAM or FEC lock on one of the downstream channels advertised as active in the primary channel MDD. |
3 |
Sequence out-of-range |
Receipt of a packet with an out-of-range sequence number for a particular DSID. |
4 |
Secondary Channel MDD Recovery |
Receipt of an MDD on a Secondary channel advertised as active in the most recent primary channel MDD. |
5 |
QAM/FEC Lock Recovery |
Successful QAM/FEC lock on a channel advertised as active in the most recent primary channel MDD. |
6 |
T4 timeout |
Expiration of the T4 timeout on the CM. |
7 |
T3 retries exceeded |
The number of T3 retries as specified in Annex B is exceeded. |
8 |
Successful ranging after T3 retries exceeded |
Successful ranging on a channel for which T3 retries exceeded event had been reported. |
9 |
CM operating on battery backup |
CM detects loss of A/C Power for more than 5 seconds and the CM is operating on battery backup. |
10 |
CM returned to A/C power |
CM detects the presence of A/C Power for more than 5 seconds and has returned from backup battery to operating on A/C power. |
11 |
MAC Removal Event |
The CM has determined that one or more MAC addresses need to be removed due to a specific CMCI port transition. (ifOperStatus transitions from 'UP' to 'DOWN') |
12-15 |
Reserved for future use |
|
16 |
DS OFDM profile failure |
FEC errors were over limit on one of the assigned downstream OFDM profiles of a channel |
17 |
Primary Downstream Change |
Loss of Primary Downstream followed by successful acquisition of a backup primary downstream channel as the new primary downstream channel |
18 |
DPD Mismatch |
The CM detect the mismatch between the LSB of DPD change count and NCP odd/even bit |
19 |
Deprecated |
|
20 |
NCP profile failure |
FEC errors were over limit on NCP |
21 |
PLC failure |
FEC errors were over limit on PLC |
22 |
NCP profile recovery |
FEC recovery on NCP profile |
23 |
PLC recovery |
FEC recovery on PLC channel |
24 |
OFDM profile recovery |
FEC recovery on OFDM profile |
25 |
OFDMA Profile failure |
CM not able to support certain profile because the profile is out of modem capability when it gets a UCD containing profile definition changes. |
26 |
MAP Storage overflow indicator |
The MAPs received by the CM contain more information elements than the CM can support. |
27 |
MAP Storage almost full indicator |
The CM's internal MAP storage capacity is filling up. |
28-255 |
Reserved for future use |
|
BruceW
Gold Problem Solver
•
26.3K Messages
1 year ago
Sadly, my understanding of CM Event Type Codes leaves much to be desired. I'm especially impressed by #18, DPD Mismatch: "The CM detect the mismatch between the LSB of DPD change count and NCP odd/even bit".
LSB? "DPD change count"? "NCP odd/even bit"? Huh??? 🤔
My guess is that it would take much more than a few minutes to acquire even a crude understand of those TLAs, and a deep dive into DOCSIS to begin to develop anything like a real understanding of them. So I stick with what is no doubt a grossly oversimplified rule-of-thumb for these Event Type Codes: "few messages = good, many messages = bad".
But I applaud your contribution to making this stuff a bit less mysterious, and thank you for your efforts!
Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.
(edited)
0