3 Messages
Started Unicast Maintenance Ranging - No Response received - T3 time-out
I have Xfinity Maintenance coming over but, after looking through this forum, it appears I might have an issue the tech can't diagnose. I believe I've included the necessary logs for diagnosis along with redacting MAC Addresses. I've been working on intermittent service since Tuesday and changing out the modem/router for a new one (same model) didn't help. I've also talked to Support Multiple times so I've gone through the checklists... cycling power, checking connections, etc... multiple times. Although my wife works from home I believe our data use is fairly normal (I see that Xfinity have asked others posters if they're gamers). Any help would be appreciated.
My Modem/Router is a Netgear AC 19000 C7000V2
| Startup Procedure | ||||||||
| Procedure | Status | Comment | ||||||
| Acquire Downstream Channel | 615000000 Hz | Locked | ||||||
| Connectivity State | OK | Operational | ||||||
| Boot State | OK | Operational | ||||||
| Security | Enabled | BPI+ | ||||||
| IP Provisioning Mode | Honor MDD | honorMdd(4) | ||||||
| Downstream Bonded Channels | ||||||||
| Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR | Correctables | Uncorrectables |
| 1 | Locked | QAM256 | 34 | 615000000 Hz | 1.5 dBmV | 40.1 dB | 0 | 0 |
| 2 | Locked | QAM256 | 17 | 519000000 Hz | 1.8 dBmV | 40.3 dB | 0 | 0 |
| 3 | Locked | QAM256 | 18 | 525000000 Hz | 1.6 dBmV | 40.1 dB | 0 | 0 |
| 4 | Locked | QAM256 | 19 | 531000000 Hz | 1.6 dBmV | 40.2 dB | 0 | 0 |
| 5 | Locked | QAM256 | 20 | 537000000 Hz | 1.9 dBmV | 40.1 dB | 0 | 0 |
| 6 | Locked | QAM256 | 21 | 543000000 Hz | 2 dBmV | 40.3 dB | 0 | 0 |
| 7 | Locked | QAM256 | 22 | 549000000 Hz | 2 dBmV | 40.2 dB | 0 | 0 |
| 8 | Locked | QAM256 | 23 | 555000000 Hz | 1.9 dBmV | 40.2 dB | 0 | 0 |
| 9 | Locked | QAM256 | 24 | 561000000 Hz | 1.9 dBmV | 39.5 dB | 0 | 0 |
| 10 | Locked | QAM256 | 25 | 567000000 Hz | 2 dBmV | 40.3 dB | 0 | 0 |
| 11 | Locked | QAM256 | 26 | 573000000 Hz | 2.1 dBmV | 40.3 dB | 0 | 0 |
| 12 | Locked | QAM256 | 27 | 579000000 Hz | 2.1 dBmV | 40.3 dB | 0 | 0 |
| 13 | Locked | QAM256 | 28 | 585000000 Hz | 1.9 dBmV | 40.2 dB | 0 | 0 |
| 14 | Locked | QAM256 | 29 | 591000000 Hz | 1.8 dBmV | 40.1 dB | 0 | 0 |
| 15 | Locked | QAM256 | 30 | 597000000 Hz | 1.7 dBmV | 40.1 dB | 0 | 0 |
| 16 | Locked | QAM256 | 31 | 603000000 Hz | 1.6 dBmV | 40 dB | 0 | 0 |
| 17 | Locked | QAM256 | 33 | 609000000 Hz | 1.2 dBmV | 40.8 dB | 0 | 0 |
| 18 | Locked | QAM256 | 35 | 621000000 Hz | 1.1 dBmV | 39.9 dB | 0 | 0 |
| 19 | Locked | QAM256 | 36 | 627000000 Hz | 1.5 dBmV | 40.6 dB | 0 | 0 |
| 20 | Locked | QAM256 | 37 | 633000000 Hz | 1.5 dBmV | 40 dB | 0 | 0 |
| 21 | Locked | QAM256 | 38 | 639000000 Hz | 1.4 dBmV | 40.6 dB | 0 | 0 |
| 22 | Locked | QAM256 | 39 | 645000000 Hz | 2 dBmV | 41.4 dB | 0 | 0 |
| 23 | Locked | QAM256 | 40 | 651000000 Hz | 1.9 dBmV | 41.4 dB | 0 | 0 |
| 24 | Locked | QAM256 | 41 | 657000000 Hz | 1.8 dBmV | 41.4 dB | 0 | 0 |
|
||||||||
| Upstream Bonded Channels | ||||||||
| Channel | Lock Status | US Channel Type | Channel ID | Symbol Rate | Frequency | Power | ||
| 1 | Locked | ATDMA | 4 | 5120 Ksym/sec | 29200000 Hz | 46.2 dBmV | ||
| 2 | Locked | ATDMA | 2 | 5120 Ksym/sec | 16300000 Hz | 45.8 dBmV | ||
| 3 | Locked | ATDMA | 3 | 5120 Ksym/sec | 22800000 Hz | 45.5 dBmV | ||
| 4 | Locked | ATDMA | 9 | 5120 Ksym/sec | 35600000 Hz | 46.3 dBmV | ||
| 5 | Locked | ATDMA | 10 | 2560 Ksym/sec | 40400000 Hz | 47.8 dBmV | ||
| 6 | Not Locked | Unknown | 0 | 0 Ksym/sec | 0 Hz | 0.0 dBmV | ||
| 7 | Not Locked | Unknown | 0 | 0 Ksym/sec | 0 Hz | 0.0 dBmV | ||
| 8 | Not Locked | Unknown | 0 | 0 Ksym/sec | 0 Hz | 0.0 dBmV | ||
| Time | Priority | Description | ||||||
| 2024-5-24, 09:06:02 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 09:06:02 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 09:03:24 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 09:03:24 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:58:58 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 08:58:57 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:55:34 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 | ||||||
| 2024-5-24, 08:55:18 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;Redacted | ||||||
| 2024-5-24, 08:55:18 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:52:53 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 08:52:52 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:50:51 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 | ||||||
| 2024-5-24, 08:50:35 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;Redacted | ||||||
| 2024-5-24, 08:46:15 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 08:42:03 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:39:28 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 | ||||||
| 2024-5-24, 08:39:13 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;Redacted | ||||||
| 2024-5-24, 08:34:53 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 08:34:53 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:23:49 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 08:23:49 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:20:37 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 08:20:37 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:19:25 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 08:14:46 | Warning (5) | MDD message timeout;Redacted | ||||||
| 2024-5-24, 08:13:14 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-24, 08:11:36 | Warning (5) | MDD message timeout;Redacted | ||||||
| 1970-1-1, 00:00:45 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 | ||||||
| 1970-1-1, 00:00:39 | Notice (6) | WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:N/A) - Reason:INIT | ||||||
| 1970-1-1, 00:00:39 | Notice (6) | WiFi Interface [wl0] set to Channel 3 (Side-Band Channel:N/A) - Reason:INIT | ||||||
| 1970-1-1, 00:00:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;Redacted | ||||||
| 2024-5-24, 08:00:21 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;Redacted | ||||||
| 2024-5-24, 07:56:01 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-23, 22:05:20 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-23, 22:02:39 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-23, 22:00:22 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-23, 21:53:59 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;Redacted | ||||||
| 2024-5-23, 21:43:42 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
| 2024-5-23, 21:34:24 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;Redacted | ||||||
| 2024-5-23, 21:30:04 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;Redacted | ||||||
XfinityKrista
Official Employee
•
968 Messages
1 month ago
Hello @claytor1999, thank you for taking the time to reach out on social media. I understand your concern with the internet connection, and I'd like the opportunity to check into that for you.
To access your account, will you please send us a direct message with your full name and complete service address.
To do so, click on the chat icon located at the top right of this forums page.
Here's the detailed steps to direct message us:
3
EG
Expert
•
104.3K Messages
1 month ago
@claytor1999 @XfinityKrista
Please circle back here and post any possible solutions for the issue here in these open forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.
1