NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
katPHish
Oct 24, 2016Aspirant
CM500 and sporadic issues on Comcast\Xfinity
Things seems sluggish of late. Need some help before contactng Comcast again as they as me to check with Netgear first. Info from this morning:
Upstream Bonded Channels | ||||||
| Channel | Lock Status | US Channel Type | Channel ID | Symbol Rate | Frequency | Power |
| 1 | Locked | ATDMA | 13 | 5120 Ksym/sec | 34800000 Hz | 37.3 dBmV |
| 2 | Locked | ATDMA | 14 | 5120 Ksym/sec | 27900000 Hz | 37.3 dBmV |
| 3 | Locked | ATDMA | 15 | 5120 Ksym/sec | 21000000 Hz | 36 dBmV |
| 4 | Locked | ATDMA | 16 | 2560 Ksym/sec | 14100000 Hz | 35 dBmV |
Downstream Bonded Channels | ||||||||
| Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR | Correctables | Uncorrectables |
| 1 | Locked | QAM256 | 1 | 609000000 Hz | 1.8 dBmV | 39.5 dB | 22 | 79 |
| 2 | Locked | QAM256 | 2 | 615000000 Hz | 1.7 dBmV | 39.4 dB | 33 | 31 |
| 3 | Locked | QAM256 | 3 | 621000000 Hz | 1.8 dBmV | 39.5 dB | 42 | 70 |
| 4 | Locked | QAM256 | 4 | 627000000 Hz | 1.9 dBmV | 39.4 dB | 35 | 65 |
| 5 | Locked | QAM256 | 5 | 633000000 Hz | 1.9 dBmV | 39.4 dB | 59 | 35 |
| 6 | Locked | QAM256 | 6 | 639000000 Hz | 1.8 dBmV | 39.2 dB | 40 | 24 |
| 7 | Locked | QAM256 | 7 | 645000000 Hz | 2.2 dBmV | 39.4 dB | 18 | 59 |
| 8 | Locked | QAM256 | 8 | 651000000 Hz | 1.9 dBmV | 39.2 dB | 50 | 38 |
| 9 | Locked | QAM256 | 9 | 657000000 Hz | 1.8 dBmV | 39.2 dB | 56 | 27 |
| 10 | Locked | QAM256 | 11 | 669000000 Hz | 1.8 dBmV | 39.1 dB | 23 | 61 |
| 11 | Locked | QAM256 | 12 | 675000000 Hz | 1.6 dBmV | 38.4 dB | 36 | 94 |
| 12 | Locked | QAM256 | 13 | 681000000 Hz | 1.7 dBmV | 39 dB | 27 | 41 |
| 13 | Locked | QAM256 | 14 | 687000000 Hz | 1.6 dBmV | 38.9 dB | 41 | 126 |
| 14 | Locked | QAM256 | 17 | 705000000 Hz | 1.8 dBmV | 39 dB | 225 | 26 |
| 15 | Locked | QAM256 | 21 | 729000000 Hz | 1.1 dBmV | 38.7 dB | 47 | 9 |
| 16 | Locked | QAM256 | 24 | 747000000 Hz | 0.6 dBmV | 38.4 dB | 24 | 19 |
Startup Procedure | ||
| Procedure | Status | Comment |
| Acquire Downstream Channel | 609000000 Hz | Locked |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Configuration File | ||
| Security | Enabled | BPI+ |
| IP Provisioning Mode | Honor MDD | honorMdd(4) |
Alot of these in log:
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=X;CMTS-MAC=X;CM-QOS=1.1;CM-VER=3.0;
SYNC Timing Synchronization failure - Failed to acquire FEC framing;
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
SYNC Timing Synchronization failure - Failed to acquire FEC framing;
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Dynamic Range Window violation
A lot more of these:
No Ranging Response received - T3 time-out
Have a few entries with a date time of:
1970-1-1, 00:00:XX
2 Replies
- DarrenMSr. NETGEAR Moderator
Hello KatPhish
If you are getting alot of T3 timeouts that is a sign of line issues that the ISP needs to come check out. Here is a link describing the timeouts.
http://volpefirm.com/docsis_timout_descriptions/
DarrenM
- katPHishAspirant
Logs has had no new entries since the 21st... THings seem better now. Go figure.