| Attachment | Size |
|---|---|
 CMTS-1.PNG | 70.41 KB |
| CMTS-2.png | 15.64 KB |
Hi
When I check the online cable modems in the CMTS C100G-Casa Systems, I see that some have the # in the information of the DS or US channels, mainly it happens in the US Intf
CASA-C100G#show cable modem online
MAC Address IP Address US DS MAC Prim RxPwr Timing Num BPI
Intf Intf Status Sid (dB) Offset CPEs Enb
0023.bed9.38ac 10.8.192.184 12/12.3/0# 0/5/26* online(pt) 149 8.2 2904 1 yes
0023.bedb.5c27 10.8.197.187 11/10.3/0# 4/0/13* online(pt) 293 8.5 2350 1 yes
when I check one of these, for example:
CASA-C100G#show cable modem 0023.bed9.38ac bonding
Reason code: x/y/z(reason_code)
1 MDD timeout 2 FEC lock failure
3 Bad tcc 4 Bad rcc
5 Reg ack 6 DBC rsp
7 TR power bad 8 NCP profile failure
9 Impaired channel 10 Channel unreachable
11 Range timeout 12 Ranging failure
0 Unknown
MAC Address MAC US DS US DS US/DS CHAN EXCLUDED
id Intf Intf SET SET
0023.bed9.38ac 6 12/12.3/0 0/5/26 257 274(3*8) 12/12.0/0(5)
CASA-C100G#show cable modem 0023.bedb.5c27 bonding
Reason code: x/y/z(reason_code)
1 MDD timeout 2 FEC lock failure
3 Bad tcc 4 Bad rcc
5 Reg ack 6 DBC rsp
7 TR power bad 8 NCP profile failure
9 Impaired channel 10 Channel unreachable
11 Range timeout 12 Ranging failure
0 Unknown
MAC Address MAC US DS US DS US/DS CHAN EXCLUDED
id Intf Intf SET SET
0023.bedb.5c27 33 11/10.3/0 4/0/13 259 273(1*8) 11/10.3/0(11)
*** these modems have excluded channels. ***
Most of my cable modems are: (4 * 8), four bonded upstream channels along with eight bonded downstream channels
when i reboot the modem it shows again (4 * 8), example:
CASA-C100G#show cable modem 0023.bed9.38ac bonding
Reason code: x/y/z(reason_code)
1 MDD timeout 2 FEC lock failure
3 Bad tcc 4 Bad rcc
5 Reg ack 6 DBC rsp
7 TR power bad 8 NCP profile failure
9 Impaired channel 10 Channel unreachable
11 Range timeout 12 Ranging failure
0 Unknown
MAC Address MAC US DS US DS US/DS CHAN EXCLUDED
id Intf Intf SET SET
0023.bed9.38ac 6 12/12.2/0 0/5/8 257 267(4*8)
What configuration can I do so that the modem can automatically return to bonding (4 * 8) without having to reboot the modme ?
I share the result of the command:
CASA-C100G#show cable modem 0023.bee1.111c verbose
CASA-C100G#show cable modem 0023.bee1.111c verbose
MAC Address :0023.bee1.111c
IP Address :10.8.10.41
MAC Status :online(pt)
CM-ID :4255
Prim Sid :1593
MAC Domain :44
Service-Group :nodo38
Upstream Channel Set :12/5.0/0, 12/5.1/0
Downstream Channel Set :9/3/18, 9/3/9, 9/3/10, 9/3/11, 9/3/16, 9/3/17, 9/3/8, 9/3/19
CASA-C100G#show cable modem 0023.bee0.d98b verbose
MAC Address :0023.bee0.d98b
IP Address :10.8.192.133
MAC Status :online(pt)
CM-ID :1753
Prim Sid :402
MAC Domain :44
Service-Group :nodo38
Upstream Channel Set :12/5.0/0, 12/5.1/0, 12/5.3/0, 12/5.2/0
Downstream Channel Set :9/3/22, 9/3/1, 9/3/2, 9/3/3, 9/3/21, 9/3/0, 9/3/23, 9/3/24
where you can see that some have 4 channels of up and others only 2 in the item: Upstream Channel Set
attached screenshots
How can I fix this automatically?
This command attempts to recover the modems from partial service,
cable partial-service dbc-recovery 3600 retry unlimited
This attempts to use DBC to recover modems in partial service every hour and will retry unlimited times (each hour)
However, it is not magic, you still need to address why your modems are going into partial service to begin with. Rebooting them may recover them, because the issue is transient, but if you do not fix the underlying problem they will just enter partial service when RF conditions deteriorate again.
The CLI your showing shows a reason code of 5 and 11
MAC Address MAC US DS US DS US/DS CHAN EXCLUDED
id Intf Intf SET SET
0023.bed9.38ac 6 12/12.3/0 0/5/26 257 274(3*8) 12/12.0/0(5)
5 = Registration Ack
11 = Ranging Timeout
These can point to lots of different things, 5 could be a bandwidth shortage, your upstream channel could be so. full, that a modem can't get a timeslot to respond to a registration Request.
11 ranging timeout, could be a DS utilization problem, i.e. the downstream was too full it did not hear the ranging response.
you can use the show cable modem cm-status log, to get the modems side of the conversation assuming you have the appropriate cm-status' enabled, I would recommend turning them all on.
Hi
Thanks for your help
I have 1 cmts with an old firmware version that only allows this part of the command:
cable partial-service dbc-recovery 3600
(It should work)
On other CMTS if allowed to apply full command
cable partial-service dbc-recovery 3600 retry unlimited
I have a question:
when the cmts applies this command to recover the modems from partial servicen
the cable modem is rebooted or loses connection and the user would be affected ?
It uses a DBC (Dynamic Bonding Change) to tell the modem to change its bonded channels it is using. Typically in normal HFC conditions this is transparent to the customer. This is the same mechanism that is used to do load balancing. If you have RF problems however, depending on their severity it could affect customers.
For example: if the CMTS tells a modem to use a channel and it is severely impaired, the DBC operation will not even complete. However, if the channel is only slightly impaired, or intermittently, the DBC will succeed, but when larger amounts of data traverse the network it could cause issues that a customer would notice, until the problem got bad enough that the channel got put in partial service again.
show load-balance dynamic will show the DBC results:
show load-balance dynamic
Mac address Mac_id upstream-channel downstream-channel initial_tech cmd status type time
acdb.481d.481d 3->3 1,2,3,4,5->1,2,3,4 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,47->- direct dbc Success PSR 2023-03-31 17:14:06
acdb.481d.481d 3->3 1,2,3,4->1,2,3,4,5 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,47->- broadcast-ranging dbc Success PSR 2023-03-31 17:14:27
acdb.4820.8065 101->101 3,2,1,4,5->3,2,1,4 24,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,1,25,26,27,28,29,30,31,32,47->- direct dbc Success PSR 2023-04-06 12:54:15
acdb.4820.8065 101->101 3,2,1,4->3,2,1,4,5 24,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,1,25,26,27,28,29,30,31,32,47->- broadcast-ranging dbc PartialService PSR 2023-04-06 12:54:35
acdb.4820.8065 101->101 3,2,1,4,5->3,2,1,4 24,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,1,25,26,27,28,29,30,31,32,47->- direct dbc Success PSR 2023-04-06 13:54:45
acdb.4820.8065 101->101 3,2,1,4->3,2,1,4,5 24,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,1,25,26,27,28,29,30,31,32,47->- broadcast-ranging dbc PartialService PSR 2023-04-06 13:55:05
acdb.4820.8065 101->101 4,2,3,1,5->4,2,3,1 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,47->- direct dbc Success PSR 2023-04-06 16:20:41acdb.4820.8065 101->101 4,2,3,1->4,2,3,1,5 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,47->- broadcast-ranging dbc PartialService PSR 2023-04-06 16:21:02acdb.4820.8065 101->101 4,2,3,1,5->4,2,3,1 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,47->- direct dbc Success PSR 2023-04-06 17:21:11acdb.4820.8065 101->101 4,2,3,1->4,2,3,1,5 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,47->- broadcast-ranging dbc PartialService PSR 2023-04-06 17:21:32acdb.4820.8065 101->101 4,2,3,1,5->4,2,3,1 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,47->- direct dbc Success PSR 2023-04-06 18:21:41acdb.4820.8065 101->101 4,2,3,1->4,2,3,1,5 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,47->- broadcast-ranging dbc cmRejected PSR 2023-04-06 18:22:02
This is the result of 2 partial service recovery operations, the first 2 lines show a modem with mac address acdb.481d.481d on docsis-mac 3 recovering from partial service using the DBC method. Note the PSR in the BAL column for partial service recovery, and the status was successful in both attempts. The next several lines show a modem with mac-address acdb.4820.8065 on docsis-mac 101 unsuccessfully, it attempts several times then gives up the failed attempts result i a PartialService Status, and after several attempts the CM rejects the final attempt. with the command I gave you earlier, this is what would happen if your RF problem was not cleared. Once the modem rejected it, the CMTS will wait the 3600 seconds to attempt again.
One other common status you will see in the show load-balance dynamic output is: TXP standing for Transmit Power. Typically this would be paired with a cmRejected and means the Modem refused to make the DBC because it did not have sufficient Transmit power overhead to add another upstream channel into its bonding group. Or in other words the modem was at max transmit power already.
Hi
days ago apply the command: "cable partial-service dbc-recovery 3600 retry unlimited" on the CMTS
Checking in the CMTS I keep looking at many channel lines excluded from Upstream
For example port 4/8 has a total of 217 cable modems connected, 125 of these 217 when I look at the following command have channels excluded from Upstream
show cable modem partial-service upstream | include 4/8
MAC Address IP Address MAC US DS US DS US/DS CHAN EXCLUDED
0023.bef3.0e0a 10.10.185.146 13 4/8.1/0 1/4/24 256 298(3*8) 4/8.1/0(5)
145b.d1be.6f4f 10.10.186.1 13 4/8.1/0 1/4/24 256 291(3*8) 4/8.2/0(5)
1859.3340.6ef2 10.10.185.118 13 4/8.1/0 1/4/21 256 297(3*8) 4/8.2/0(5)
1859.3341.54ca 10.10.185.2 13 4/8.1/0 1/4/17 256 269(2*8) 4/8.1/0(5), 4/8.3/0(5)
1859.338c.78b6 10.10.185.173 13 4/8.3/0 1/4/29 256 293(3*8) 4/8.1/0(5)
1859.3398.3600 10.10.186.12 13 4/8.1/0 1/4/16 256 269(2*8) 4/8.0/0(5), 4/8.2/0(5)
1859.339e.303c 10.10.185.131 13 4/8.2/0 1/4/12 256 283(1*8) 4/8.1/0(5), 4/8.0/0(5), 4/8.3/0(5)
1859.33b3.5c0a 10.10.186.206 13 4/8.3/0 1/4/20 256 308(2*8) 4/8.1/0(5), 4/8.0/0(5)
1859.33b5.0148 10.10.185.201 13 4/8.2/0 1/4/29 256 281(3*8) 4/8.0/0(6)
1859.33f4.7280 10.10.183.32 13 4/8.1/0 1/4/25 256 300(2*8) 4/8.0/0(5), 4/8.2/0(5)
1c1b.689c.9baf 10.10.179.82 13 4/8.1/0 1/4/20 256 286(2*8) 4/8.0/0(5), 4/8.2/0(5)
1c1b.689c.dbc3 10.10.174.55 13 4/8.3/0 1/4/24 256 297(2*8) 4/8.1/0(5), 4/8.0/0(5)
1c1b.689d.1982 10.10.191.81 13 4/8.3/0 1/4/13 256 272(2*8) 4/8.1/0(5), 4/8.0/0(5)
1c1b.689d.8a23 10.10.185.154 13 4/8.3/0 1/4/25 256 285(2*8) 4/8.1/0(5), 4/8.2/0(5)
1c1b.689e.23c2 10.10.176.73 13 4/8.0/0 1/4/24 256 291(2*8) 4/8.1/0(5), 4/8.2/0(5)
1c1b.689e.28f9 10.10.186.29 13 4/8.0/0 1/4/14 256 274(3*8) 4/8.2/0(5)
1c1b.689e.7b67 10.10.176.93 13 4/8.3/0 1/4/0 256 258(3*8) 4/8.1/0(5)
I attach the complete result (125 cable modems have channels excluded)
I show the result of the command to diagnose what may be causing this
show upstream signal-quality | include 4/8
4/8.0/0 35.1
4/8.0/1 0.0
4/8.1/0 33.4
4/8.1/1 0.0
4/8.2/0 32.8
4/8.2/1 0.0
4/8.3/0 33.1
show docsis upstream channel utilization | include 4/8
4/8.0 (40000000 Hz) 10.2 37 27 180 Centenario - 1
4/8.1 (36800000 Hz) 15.4 6 86 122 Centenario - 1
4/8.2 (33600000 Hz) 10.2 33 51 156 Centenario - 1
4/8.3 (30400000 Hz) 10.2 7 47 155 Centenario - 1
show interface upstream port 4/8
interface upstream 4/8.0
description "Centenario - 1"
spectrum-rule 1
frequency 40000000
channel-width 3200000
power-level 5
no fast-carrier-offset
power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
ingress-cancellation
partial-service fec-threshold 1
partial-service snr-threshold 0
no small-signal-compensation
logical-channel 0 description "Centenario - 1"
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 channel-width 3200000
logical-channel 0 profile 64 secondary-profile 16
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 0 ranging-backoff 2 8
logical-channel 0 pre-equalization 1440
no logical-channel 0 post-equalization
logical-channel 0 power-offset 0
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no logical-channel 0 shutdown
logical-channel 1 prov-attr-mask 0x0
logical-channel 1 channel-width 3200000
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 data-backoff automatic
logical-channel 1 ranging-backoff 0 4
no logical-channel 1 pre-equalization
no logical-channel 1 post-equalization
logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
logical-channel 1 shutdown
no shutdown
the same is repeated for the other 3 channels of the port, in total I use 4 channels per port
attached the configuration of the channels of port 4/8
show modulation-profile
modulation-profile 16
request atdma qpsk off 64 0 16 338 0 16 fixed on 1 1536 qpsk0
initial atdma qpsk off 640 5 34 338 0 48 fixed on 1 1536 qpsk0
station atdma qpsk off 384 5 34 338 0 48 fixed on 1 1536 qpsk0
a-short atdma 16qam off 104 12 75 338 6 16 shortened on 1 1536 qpsk1
a-long atdma 16qam off 104 16 220 338 0 16 shortened on 1 1536 qpsk1
modulation-profile 64
request atdma qpsk off 64 0 16 338 0 16 fixed on 1 1536 qpsk0
initial atdma qpsk off 640 5 34 338 0 48 fixed on 1 1536 qpsk0
station atdma qpsk off 384 5 34 338 0 48 fixed on 1 1536 qpsk0
a-short atdma 64qam off 104 12 75 338 6 16 shortened on 1 1536 qpsk1
a-long atdma 64qam off 104 16 220 338 0 16 shortened on 1 1536 qpsk1
Laboratorio-CasaC40G#show load-balance dynamic | include 13->13
Mac address Mac_id upstream-channel downstream-channel initial_tech cmd status type time
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 06:53:58
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 06:54:23
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 06:54:50
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 06:55:17
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 06:55:43
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 06:56:10
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 06:56:37
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 06:57:03
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 06:57:30
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 06:57:57
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 06:58:23
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 06:58:50
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 06:59:16
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 06:59:43
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 07:00:10
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 07:00:36
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 07:01:02
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 07:01:30
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 07:01:55
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 07:02:22
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 07:02:50
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 07:03:15
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 07:03:42
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 07:04:10
attached file with the complete result of this command
attach file with levels of cable mode connected to port 4/8
Please help me indicating what change I can apply to help improve this or what other commands I can use to diagnose and help solve this
and not have a high number of upstream channels excluded
These lines show Partial Service Recovery failing because the modem rejected it, you would need to consult the modem's event log to find out why it rejected the PSR
6019.712a.afc2 13->13 3,2,1,4->3,2,4 12,2,3,4,5,6,7,8,9,10,11,1,13,14,15,16->- direct dbc cmRejected PSR 2023-04-30 07:03:42
6019.7118.3ab2 13->13 3,2,1,4->3,2,1 29,17,18,19,20,21,22,23,24,25,26,27,28,30,31,32->- direct dbc cmRejected PSR 2023-04-30 07:04:10
This line is a little more curious:
602a.d073.0e97 13->13 2,1,3,4->2,1,3,4 14,15,16,23,24,13,22,21->- direct dbc cmtsRejected PSR 2023-04-30 07:03:15
I have not seen cmtsRejected before, I suspect you have some uncommon load-balance settings that are affecting it.
What are your load-balance settings? Do you have manual load-balance groups defined?
The partial service recovery mechanism is working, as evidenced by the log, but either the modem or the CMTS is rejecting the recovery. To determine why the modem is rejecting the recovery you will need to consult the modem log. For the ones that are cmtsRejected, you can check show cable modem cm-status log which may give you an indication of why it is not recovering. If you can not determine from the cm-status log, you could enable debugging on a particular modem and track the responses during the partial service recovery.
Hi
load-balance, spectrum rule and interface docsis-mac settings
CasaC40G#show load-balance running-config
!
!
! load balance commands
!
load-balance enable
load-balance permit dbc-chg-prim-ds
load-balance execution-rule 1
method modem
method utilization dynamic
threshold load 10 enforce 15 minimum 50
interval 60
suspicious-channel retry interval 300
load-balance policy 1
rule execution 1
load-balance general-group default-settings
policy-id 1
initial-tech period-ranging
enable
-------------------
CasaC40G#show spectrum rule
cable spectrum hop-period 30
cable spectrum monitor-period 30
cable spectrum cm-mode-monitor-period 45
no cable spectrum back-hop-step
no cable spectrum trap
no cable spectrum syslog
no spectrum analysis full-spectrum
spectrum ranging-zone interval 30 snr-threshold 150
spectrum rule 1
action modulation
correctable-fec threshold 20
uncorrectable-fec threshold 3
profile 1 snr-threshold 20
profile 2 snr-threshold 26
profile 16 snr-threshold 250
profile 64 snr-threshold 270
-----
CasaC40G#show interface docsis-mac 13
interface docsis-mac 13
no shutdown
sync-interval 10
insertion-interval 20
ucd-interval 1000
no dhcp-authorization
invited-ranging-attempts 16
initial-tech broadcast-ranging
initial-tech ofdma broadcast-ranging
no energy management
no battery backup
ip-provisioning-mode ipv4-only
no early-authentication-encryption
no upstream extended-frequency-range
cm-status event report
no multicast-dsid-forward
downstream channel bonding
upstream channel bonding
no tftp-enforce
no tftp-enforce src-interface
no tftp-proxy
no cable privacy valid-period-check
no upstream drop classifier
no dhcp-giaddr-primary
no dhcpv6-link-address-primary
no dhcp-insert
mdd interval 2000
sid-cluster max-requests 0
sid-cluster max-outstanding-bytes 0
sid-cluster max-total-bytes 0
sid-cluster max-time 0
max sid-cluster per-service-flow 2
ip bundle 1
upstream 1 interface upstream 4/8.0/0
upstream 2 interface upstream 4/8.1/0
upstream 3 interface upstream 4/8.2/0
upstream 4 interface upstream 4/8.3/0
downstream 1 interface qam 1/4/0
downstream 2 interface qam 1/4/1
downstream 3 interface qam 1/4/2
downstream 4 interface qam 1/4/3
downstream 5 interface qam 1/4/4
downstream 6 interface qam 1/4/5
downstream 7 interface qam 1/4/6
downstream 8 interface qam 1/4/7
downstream 9 interface qam 1/4/8
downstream 10 interface qam 1/4/9
downstream 11 interface qam 1/4/10
downstream 12 interface qam 1/4/11
downstream 13 interface qam 1/4/12
downstream 14 interface qam 1/4/13
downstream 15 interface qam 1/4/14
downstream 16 interface qam 1/4/15
downstream 17 interface qam 1/4/16
downstream 18 interface qam 1/4/17
downstream 19 interface qam 1/4/18
downstream 20 interface qam 1/4/19
downstream 21 interface qam 1/4/20
downstream 22 interface qam 1/4/21
downstream 23 interface qam 1/4/22
downstream 24 interface qam 1/4/23
downstream 25 interface qam 1/4/24
downstream 26 interface qam 1/4/25
downstream 27 interface qam 1/4/26
downstream 28 interface qam 1/4/27
downstream 29 interface qam 1/4/28
downstream 30 interface qam 1/4/29
downstream 31 interface qam 1/4/30
downstream 32 interface qam 1/4/31
mgmd ipv4 query-interval 125
mgmd ipv4 version 3
mgmd ipv4 max-query-response-time 100
mgmd ipv4 proxy-interface gige 7/0
mgmd ipv4 robustness 2
mgmd ipv4 last-member-query-interval 10
mgmd ipv4 shutdown
mgmd ipv6 query-interval 125
mgmd ipv6 version 2
mgmd ipv6 max-query-response-time 100
mgmd ipv6 proxy-interface gige 7/0
mgmd ipv6 robustness 2
mgmd ipv6 last-member-query-interval 10
mgmd ipv6 shutdown
privacy kek life-time 604800
privacy tek life-time 43200
no cable cm-status report event-list 1,2,3,4,5,6,7,8,9,10,11,16,17,18,20,21,22,23,24,25,26,27
cable cm-status event 1 max-timer 2.00 max-number 8
cable cm-status event 2 max-timer 2.00 max-number 8
cable cm-status event 3 max-timer 2.00 max-number 8
cable cm-status event 4 max-timer 2.00 max-number 8
cable cm-status event 5 max-timer 2.00 max-number 8
cable cm-status event 6 max-timer 2.00 max-number 8
cable cm-status event 7 max-timer 2.00 max-number 8
cable cm-status event 8 max-timer 2.00 max-number 8
cable cm-status event 9 max-timer 2.00 max-number 8
cable cm-status event 10 max-timer 2.00 max-number 8
cable cm-status event 11 max-timer 2.00 max-number 8
cable cm-status event 12 max-timer 2.00 max-number 8
cable cm-status event 13 max-timer 2.00 max-number 8
cable cm-status event 14 max-timer 2.00 max-number 8
cable cm-status event 15 max-timer 2.00 max-number 8
cable cm-status event 16 max-timer 2.00 max-number 8
cable cm-status event 17 max-timer 2.00 max-number 8
cable cm-status event 18 max-timer 2.00 max-number 8
cable cm-status event 19 max-timer 2.00 max-number 8
cable cm-status event 20 max-timer 2.00 max-number 8
cable cm-status event 21 max-timer 2.00 max-number 8
cable cm-status event 22 max-timer 2.00 max-number 8
cable cm-status event 23 max-timer 2.00 max-number 8
cable cm-status event 24 max-timer 2.00 max-number 8
cable cm-status event 25 max-timer 2.00 max-number 8
cable cm-status event 26 max-timer 2.00 max-number 8
cable cm-status event 27 max-timer 2.00 max-number 8
no cm trap
cm trap interval 600
cable diplexer upstream-upper-band-edge 255
cable diplexer downstream-lower-band-edge 255
cable diplexer downstream-upper-band-edge 255
What can I add or modify?
load balance settings look ok
In your docsis-mac interface I would absolutely enable
cable cm-status report event-list 1,2,3,4,5,6,7,8,9,10,11,16,17,18,20,21,22,23,24,25,26,27
this allows you to monitor the cm-status log "show cable modem cm-status log" and monitor the events the cable modem detects from the CMTS side.
As to your original problem, what does your utilization (DS/US) look like on affected channels in that mac domain?
DBC's require a round trip from CMTS to modem and back, so if you have heavily utilized (>80%) utilization channels, there is a big likelihood that DBCs could be lost.
Still the most likely issue, is an intermittent signal problem, monitoring SNR per channel, and FEC counters per channel/modem can eliminate this possibility from the list.
Hi
CasaC40G#show docsis upstream channel utilization | include 4/8
4/8.0 (40000000 Hz) 10.2 38 84 132 Centenario - 1
4/8.1 (36800000 Hz) 15.4 30 45 169 Centenario - 1
4/8.2 (33600000 Hz) 15.4 35 49 164 Centenario - 1
4/8.3 (30400000 Hz) 10.2 33 41 168 Centenario - 1
CasaC40G#show upstream signal-quality | include 4/8
4/8.0/0 31.7
4/8.0/1 0.0
4/8.1/0 32.1
4/8.1/1 0.0
4/8.2/0 32.6
4/8.2/1 0.0
4/8.3/0 32.6
Laboratorio-CasaC40G#show docsis downstream channel utilization | include 1/4/
1/4/0 (345000000 Hz) 42.9 73 3 52
1/4/1 (351000000 Hz) 42.9 75 0 69
1/4/2 (357000000 Hz) 42.9 76 0 89
1/4/3 (363000000 Hz) 42.9 79 0 101
1/4/4 (369000000 Hz) 42.9 68 1 84
1/4/5 (375000000 Hz) 42.9 67 0 72
1/4/6 (381000000 Hz) 42.9 65 0 52
1/4/7 (387000000 Hz) 42.9 64 5 35
1/4/8 (393000000 Hz) 42.9 31 17 22
1/4/9 (399000000 Hz) 42.9 33 1 50
1/4/10 (405000000 Hz) 42.9 33 0 51
1/4/11 (411000000 Hz) 42.9 33 1 50
1/4/12 (417000000 Hz) 42.9 25 13 36
1/4/13 (423000000 Hz) 42.9 24 16 28
1/4/14 (429000000 Hz) 42.9 24 2 41
1/4/15 (435000000 Hz) 42.9 24 1 42
1/4/16 (441000000 Hz) 42.9 32 3 50
1/4/17 (447000000 Hz) 42.9 34 4 66
1/4/18 (453000000 Hz) 42.9 34 1 69
1/4/19 (459000000 Hz) 42.9 34 4 66
1/4/20 (465000000 Hz) 42.9 31 27 33
1/4/21 (471000000 Hz) 42.9 31 9 50
1/4/22 (477000000 Hz) 42.9 31 3 56
1/4/23 (483000000 Hz) 42.9 31 0 59
1/4/24 (489000000 Hz) 42.9 31 19 38
1/4/25 (495000000 Hz) 42.9 33 36 27
1/4/26 (501000000 Hz) 42.9 33 4 59
1/4/27 (507000000 Hz) 42.9 33 2 61
1/4/28 (513000000 Hz) 42.9 30 3 84
1/4/29 (519000000 Hz) 42.9 26 30 29
1/4/30 (525000000 Hz) 42.9 26 4 55
1/4/31 (531000000 Hz) 42.9 26 10 49
with which command can I see the amount of FEC of the channel and modem ?
Upstream Channel
show interface upstream13/0.0 stat
Interface upstream 2:0/0.0 statistics
Admin status: UP
Channel utilization interval: 30
Avg upstream channel utilization: 0
Avg percent contention slots: 99
Avg percent initial ranging slots: 1
Avg percent minislots lost on late MAPs: 0
Logical-channel 0
Received 7254 broadcasts, 610866 multicasts, 5888472 unicasts
0 discards, 0 errors, 0 unknown protocol
7317750 Unerroreds, 0 Correcteds, 0 Uncorrectables
Total Modems On This Upstream Channel: 1 ,1 active cm,3 secondary cm
Req Mslots 350745301, Used Req Mslots 5294539
Init Mtn Mslots 1610759437, Used Init Mtn Mslots 0
Total Mslots 2198392178, Ucast Granted Mslots 30478527
Admin status: UP
Last clearing of interface stat: never
Per modem FEC
show cable modem fec ! all modems
or
show cable modem [mac address] fec ! Single modem
scm fec
MAC Address US IF USSNR Unerrored Corrected Uncorrectable IUC4Uncorrectable
2c99.24d6.da15 2:0/1.0/0 42.1 264625 0 0 0
2c99.24d6.da15 2:0/1.1/0 42.1 264877 0 0 0
2c99.24d6.da15 2:0/1.2/0 42.1 241087 0 0 0
2c99.24d6.da15 2:0/1.3/0 42.1 240816 0 0 0
3468.95fa.0eac 2:0/1.0/0 42.1 570378 0 0 0
3468.95fa.0eac 2:0/1.1/0 42.1 566742 0 0 0
3468.95fa.0eac 2:0/1.2/0 42.1 398263 0 0 0
3468.95fa.0eac 2:0/1.3/0 42.1 400550 0 0 0
40b8.9ae6.c73d 2:0/0.0/0 42.1 399554 0 0 0
40b8.9ae6.c73d 2:0/0.1/0 26.3 233339 20517 62003 3753
the IUC4Uncorrectable counter is Ranging, so if your counter for ranging in incrementing it means your ranging responses are getting uncorrectable errors.
enable for testing only on the docsis-mac interface where the upstream port 4/8 is configured
cable cm-status report event-list 1,2,3,4,5,6,7,8,9,10,11,16,17,18,20,21,22,23,24,25,26,27
This is a part of the command output:
show cable modem cm-status log
Laboratorio-CasaC40G#show cable modem cm-status log
MAC Address Status_Event Msg Content Time
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:54:57
bcc8.1053.9794 QAM FEC FAIL DS: 3 2023-05-01 01:54:56
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:53:46
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:53:15
bcc8.1053.9794 QAM FEC FAIL DS: 3 2023-05-01 01:53:14
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:51:56
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:51:04
bcc8.1053.9794 QAM FEC FAIL DS: 3 2023-05-01 01:51:02
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:48:41
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:48:09
bcc8.1053.9794 QAM FEC FAIL DS: 3 2023-05-01 01:48:08
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:47:15
1c1b.689f.4170 SUCC T3 RETRY US: 1 2023-05-01 01:46:42
b816.19e8.e82e T4 TIME OUT US: 4 2023-05-01 01:46:42
6455.b1ff.e7c4 T4 TIME OUT US: 2 2023-05-01 01:46:42
b816.19e9.bb54 T4 TIME OUT US: 1,4 2023-05-01 01:46:42
6019.712a.afc2 QAM FEC RECOVERY DS: 14,8,9,12,16 2023-05-01 01:46:42
6019.712a.afc2 15,13,11,10
6019.712a.afc2 7,6,5,3,2,4
6019.712a.afc2 1
bcc8.100f.7a58 T4 TIME OUT US: 4 2023-05-01 01:46:42
7cb2.1bc3.717f T4 TIME OUT US: 4 2023-05-01 01:46:42
1c1b.689f.4170 T4 TIME OUT US: 1,2 2023-05-01 01:46:42
a47a.a465.72f3 T4 TIME OUT US: 2,3,4 2023-05-01 01:46:42
1c1b.689e.7b67 T4 TIME OUT US: 2 2023-05-01 01:46:42
602a.d06f.b8a5 T4 TIME OUT US: 4 2023-05-01 01:46:42
90b1.34fc.65be T4 TIME OUT US: 4 2023-05-01 01:46:42
6019.7127.0742 MDD RECOVERY DS: 27,26,25,24 2023-05-01 01:46:42
6019.7127.0742 23,22,28,29
bcc8.1053.9794 T4 TIME OUT US: 4 2023-05-01 01:46:42
a47a.a465.5e0e T4 TIME OUT US: 1,4 2023-05-01 01:46:42
1c1b.689e.f223 T4 TIME OUT US: 1,2,3,4 2023-05-01 01:46:42
b816.19ea.36ff T4 TIME OUT US: 1,2,3,4 2023-05-01 01:46:42
602a.d091.639c T4 TIME OUT US: 1,4 2023-05-01 01:46:42
1c1b.689c.9baf T4 TIME OUT US: 4 2023-05-01 01:46:42
bcc8.1053.9794 QAM FEC RECOVERY DS: 3 2023-05-01 01:46:42
20e5.645c.1b05 T4 TIME OUT US: 2,4 2023-05-01 01:46:42
6019.712a.afc2 T4 TIME OUT US: 1,4 2023-05-01 01:46:42
6019.71f9.9b32 QAM FEC RECOVERY DS: 20,28,27,19 2023-05-01 01:46:42
6019.71f9.9b32 29,18,22,24
6019.71f9.9b32 30,23,26,25
6019.71f9.9b32 31,17,21,32
e448.c786.60dc T4 TIME OUT US: 4 2023-05-01 01:46:42
3060.23d5.a11d T4 TIME OUT US: 1,2,4 2023-05-01 01:46:42
602a.d075.cfce T4 TIME OUT US: 1,2,4 2023-05-01 01:46:42
3060.23d5.6397 T4 TIME OUT US: 2,4 2023-05-01 01:46:42
1c1b.689c.fbb2 T4 TIME OUT US: 4 2023-05-01 01:46:42
6455.b1ff.e326 T4 TIME OUT US: 1 2023-05-01 01:46:42
7896.84bd.45d2 T4 TIME OUT US: 1,2 2023-05-01 01:46:42
b816.19e9.6d84 T4 TIME OUT US: 3,4 2023-05-01 01:46:42
5039.5545.6d48 T4 TIME OUT US: 1 2023-05-01 01:46:42
2476.7d45.e064 T4 TIME OUT US: 2,4 2023-05-01 01:46:42
1c1b.689f.fe46 T4 TIME OUT US: 1,4 2023-05-01 01:46:42
6019.7118.3ab2 T4 TIME OUT US: 4,2,1 2023-05-01 01:46:42
602a.d094.075a T4 TIME OUT US: 1,4 2023-05-01 01:46:42
7896.84be.955a T4 TIME OUT US: 2,3,4 2023-05-01 01:46:42
6019.712a.afc2 T3 RETRY EXECEED US: 1 2023-05-01 01:46:42
7896.84bf.c02b T4 TIME OUT US: 4 2023-05-01 01:46:42
3060.23d5.ad02 T4 TIME OUT US: 4 2023-05-01 01:46:42
bcc8.1000.2c10 T4 TIME OUT US: 4 2023-05-01 01:46:42
1c1b.689e.23c2 T4 TIME OUT US: 4 2023-05-01 01:46:42
6019.712f.68d2 QAM FEC RECOVERY DS: 24,17,30,21 2023-05-01 01:46:42
6019.712f.68d2 19,18,32,22
6019.712f.68d2 31,29,23
1c1b.689d.be28 T4 TIME OUT US: 4 2023-05-01 01:46:42
7896.845e.8e61 T4 TIME OUT US: 4 2023-05-01 01:46:42
a47a.a465.663c T4 TIME OUT US: 1,2,3,4 2023-05-01 01:46:42
b816.19e8.5705 T4 TIME OUT US: 2,4 2023-05-01 01:46:42
7896.84bd.3c33 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
1859.33b5.0148 T4 TIME OUT US: 4 2023-05-01 01:46:41
602a.d07c.eef3 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
3060.23d5.3931 T4 TIME OUT US: 1,2,4 2023-05-01 01:46:41
7896.84bd.7b6f T4 TIME OUT US: 4 2023-05-01 01:46:41
1c1b.689f.3a1a T4 TIME OUT US: 1,3,4 2023-05-01 01:46:41
a47a.a465.50d3 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
602a.d08e.2678 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
b816.19e9.0379 T4 TIME OUT US: 4 2023-05-01 01:46:41
b816.19ea.8f34 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
5465.de66.9082 QAM FEC RECOVERY DS: 19,30,26,32 2023-05-01 01:46:41
5465.de66.9082 27,29,22,17
5465.de66.9082 31,28,24,23
5465.de66.9082 21,20,18,25
7896.84bf.d351 T4 TIME OUT US: 2,4 2023-05-01 01:46:41
90b1.34fd.55fd T4 TIME OUT US: 2,3,4 2023-05-01 01:46:41
7896.84be.9c14 T4 TIME OUT US: 4 2023-05-01 01:46:41
c8fb.2655.6bc1 T4 TIME OUT US: 4 2023-05-01 01:46:41
1859.33b3.5c0a T4 TIME OUT US: 1,4 2023-05-01 01:46:41
bcc8.1015.d3b7 T4 TIME OUT US: 4 2023-05-01 01:46:41
7896.84be.0dd3 T4 TIME OUT US: 1,3,4 2023-05-01 01:46:41
3060.23d4.faa3 T4 TIME OUT US: 4 2023-05-01 01:46:41
6019.7127.0742 QAM FEC RECOVERY DS: 28,29,27,26 2023-05-01 01:46:41
6019.7127.0742 25,24,23,22
6019.7127.0742 21
1c1b.689f.baa2 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
6019.7116.1112 QAM FEC RECOVERY DS: 19,32,31,27 2023-05-01 01:46:41
6019.7116.1112 24,21,17,23
6019.7116.1112 22,30,29,28
6019.7116.1112 26,20,25,18
1859.3398.3600 T4 TIME OUT US: 1,3 2023-05-01 01:46:41
1c1b.689d.9eab T4 TIME OUT US: 4 2023-05-01 01:46:41
7cb2.1bd8.ace3 T4 TIME OUT US: 4 2023-05-01 01:46:41
1c1b.689d.c095 T4 TIME OUT US: 2,3,4 2023-05-01 01:46:41
2476.7d23.95f2 T4 TIME OUT US: 4 2023-05-01 01:46:41
90b1.34fc.6b25 T4 TIME OUT US: 4 2023-05-01 01:46:41
602a.d07b.4abc T4 TIME OUT US: 1,4 2023-05-01 01:46:41
3060.23d7.2cc9 T4 TIME OUT US: 4 2023-05-01 01:46:41
6019.7122.5932 T4 TIME OUT US: 2 2023-05-01 01:46:41
6455.b1ff.f72a T4 TIME OUT US: 4 2023-05-01 01:46:41
7cbf.b1ee.8d0a T4 TIME OUT US: 4 2023-05-01 01:46:41
90b1.34fb.c0a0 T4 TIME OUT US: 4 2023-05-01 01:46:41
3060.23d6.1d49 T4 TIME OUT US: 4 2023-05-01 01:46:41
6019.7118.3ab2 T3 RETRY EXECEED US: 4 2023-05-01 01:46:41
1c1b.689e.54ca T4 TIME OUT US: 4 2023-05-01 01:46:41
7896.84bf.aa8f T4 TIME OUT US: 1,4 2023-05-01 01:46:41
7896.84bf.24d0 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
c8fb.2646.3b51 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
7896.84bd.7b51 T4 TIME OUT US: 1 2023-05-01 01:46:41
7896.84bd.1008 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
7896.84bf.610f T4 TIME OUT US: 4 2023-05-01 01:46:41
7cb2.1b1f.3119 T4 TIME OUT US: 2,4 2023-05-01 01:46:41
b816.19e9.5290 T4 TIME OUT US: 1 2023-05-01 01:46:41
7896.84bf.8182 T4 TIME OUT US: 1 2023-05-01 01:46:41
602a.d083.d0f1 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
5465.de6c.94d2 SUCC T3 RETRY US: 1 2023-05-01 01:46:41
602a.d083.d0f1 QAM FEC RECOVERY DS: 19,20 2023-05-01 01:46:41
6019.711a.2422 QAM FEC RECOVERY DS: 21,17,25,30 2023-05-01 01:46:41
6019.711a.2422 29,26,28,19
6019.711a.2422 32,23,27,24
6019.711a.2422 20,18,22,31
1c1b.689c.b7f9 T4 TIME OUT US: 1,2,3,4 2023-05-01 01:46:41
602a.d083.d0f1 MDD RECOVERY DS: 1,2,3,4,17 2023-05-01 01:46:41
602a.d083.d0f1 19,20
6019.7129.c342 QAM FEC RECOVERY DS: 24 2023-05-01 01:46:41
1c1b.689f.ff8a T4 TIME OUT US: 2,4 2023-05-01 01:46:41
b816.19ea.2f28 T4 TIME OUT US: 4 2023-05-01 01:46:41
7896.84bd.7fa1 T4 TIME OUT US: 1,2,3,4 2023-05-01 01:46:41
90b1.34fb.f7c3 T4 TIME OUT US: 4 2023-05-01 01:46:41
602a.d075.1dd1 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
602a.d075.1dd1 QAM FEC RECOVERY DS: 7,24 2023-05-01 01:46:41
1859.33f4.7280 T4 TIME OUT US: 4 2023-05-01 01:46:41
7896.84bf.180a T4 TIME OUT US: 1,2,3,4 2023-05-01 01:46:41
602a.d075.1dd1 MDD RECOVERY DS: 24 2023-05-01 01:46:41
c8fb.2657.14f3 T4 TIME OUT US: 4 2023-05-01 01:46:41
5465.de6c.eab2 T4 TIME OUT US: 4,3 2023-05-01 01:46:41
bcc8.100a.ef4c T4 TIME OUT US: 4 2023-05-01 01:46:41
3060.23d5.2980 T4 TIME OUT US: 1,3,4 2023-05-01 01:46:41
bcc8.100a.ef4c QAM FEC RECOVERY DS: 3,22,23,24 2023-05-01 01:46:41
1c1b.689e.cd18 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
602a.d088.b3a5 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
bcc8.100a.ef4c MDD RECOVERY DS: 1,2,3,4,22 2023-05-01 01:46:41
bcc8.100a.ef4c 23,24
7cbf.b1ee.8e9c T4 TIME OUT US: 1 2023-05-01 01:46:41
3060.23d5.e260 T4 TIME OUT US: 1,3,4 2023-05-01 01:46:41
7cbf.b1ee.d822 T4 TIME OUT US: 2,4 2023-05-01 01:46:41
c8fb.2684.9a1d T4 TIME OUT US: 1,4 2023-05-01 01:46:41
6019.7119.22f2 QAM FEC RECOVERY DS: 23,30,17,24 2023-05-01 01:46:41
6019.7119.22f2 18,27,21,20
3060.23d6.fde6 T4 TIME OUT US: 4 2023-05-01 01:46:41
c8fb.265b.6a21 T4 TIME OUT US: 4 2023-05-01 01:46:41
5465.de6c.eab2 MDD RECOVERY DS: 24 2023-05-01 01:46:41
1c1b.689e.28f9 T4 TIME OUT US: 3 2023-05-01 01:46:41
1c1b.689c.be83 T4 TIME OUT US: 1,4 2023-05-01 01:46:41
b816.19ea.6a2f T4 TIME OUT US: 1,4 2023-05-01 01:46:41
7896.84be.1c31 T4 TIME OUT US: 1 2023-05-01 01:46:41
602a.d073.a76c T4 TIME OUT US: 1,4 2023-05-01 01:46:41
7896.845e.c689 T4 TIME OUT US: 3,4 2023-05-01 01:46:41
e448.c752.b552 T4 TIME OUT US: 4 2023-05-01 01:46:41
5039.555e.ceff T4 TIME OUT US: 4 2023-05-01 01:46:41
e86d.5204.bcd3 T4 TIME OUT US: 4 2023-05-01 01:46:41
602a.d07e.87ef T4 TIME OUT US: 1,4 2023-05-01 01:46:41
602a.d07e.87ef QAM FEC RECOVERY DS: 17,19,23 2023-05-01 01:46:41
602a.d07e.87ef MDD RECOVERY DS: 17,18,19,21 2023-05-01 01:46:41
602a.d07e.87ef 22,23,24
5465.de6c.eab2 QAM FEC RECOVERY DS: 26,27,23,20 2023-05-01 01:46:41
5465.de6c.eab2 28,17,32,29
5465.de6c.eab2 31,30,24,22
5465.de6c.eab2 21,19,18,25
7896.84bd.ef3a T4 TIME OUT US: 4 2023-05-01 01:46:40
1c1b.689c.dbc3 T4 TIME OUT US: 1 2023-05-01 01:46:40
7896.84be.d331 T4 TIME OUT US: 4 2023-05-01 01:46:40
1859.3341.54ca T4 TIME OUT US: 1,2,4 2023-05-01 01:46:40
c8fb.2645.8ec2 T4 TIME OUT US: 4 2023-05-01 01:46:40
2476.7d45.8946 T4 TIME OUT US: 1 2023-05-01 01:46:40
c8fb.2640.56fa T4 TIME OUT US: 1,2,4 2023-05-01 01:46:40
7896.84be.0d73 T4 TIME OUT US: 1,4 2023-05-01 01:46:40
c8fb.267d.5d34 T4 TIME OUT US: 1,2,3,4 2023-05-01 01:46:40
3060.23d4.fa97 T4 TIME OUT US: 4 2023-05-01 01:46:40
7896.84bd.571e T4 TIME OUT US: 2,4 2023-05-01 01:46:40
602a.d076.53b8 T4 TIME OUT US: 1,2 2023-05-01 01:46:40
1c1b.689f.8a33 T4 TIME OUT US: 4 2023-05-01 01:46:40
3060.23d7.a904 T4 TIME OUT US: 3 2023-05-01 01:46:40
7cb2.1b17.3315 T4 TIME OUT US: 2,3,4 2023-05-01 01:46:40
7cb2.1b29.d7e0 T4 TIME OUT US: 1,2,4 2023-05-01 01:46:40
Most of these messages are indicative of Downstream problems:
recovery of DS FEC (i.e. uncorrectables started / stopped at cable modem)
602a.d07e.87ef QAM FEC RECOVERY DS: 17,19,23 2023-05-01 01:46:41
Mac Domain Descriptor Recovery (this goes out every 2000 uSecs so if it loses this it means it lost DS for extended periods of time)
602a.d07e.87ef MDD RECOVERY DS: 17,18,19,21 2023-05-01 01:46:41
Although these errors are occurring on the upstream, the usual culprit, is data loss on the downstream, or capacity on the US which does not seem to be the problem, thoug h you should check US capacity when the T4s are occuring.
https://pickmymodem.com/cable-modem-t3-and-t4-timeouts-error-messages-an...
c8fb.2640.56fa T4 TIME OUT US: 1,2,4 2023-05-01 01:46:40
7896.84be.0d73 T4 TIME OUT US: 1,4 2023-05-01 01:46:40
I suspect you have a few issues:
DS - You have Downstream Signal quality issues (Uncorrectables on DS at Cable modem, i.e. plant problem ) You will have to pull FEC stats from the modems individually.
DS - Either the DS Signal Quality issues or Capacity issue on DS is preventing Ranging Opportunities from being delivered to Upstream causing individual upstreams to "go offline" showing up as US partial service, this is the bulk of your messages i.e. the T4 timeouts.
US - Potentially US FEC problems, waiting on scm fec output., in order to determine rate you need to data points, from CMTS run show clock, then scm fec successively, then wait some time, say 30-90 secs, and re-run show clock, scm fec, this will allow us to get a rate.
Hi
apply the command "cable partial-service dbc-recovery 3600 retry unlimited" on the CMTS
I look at the result of the command is not being useful because it does not have the expected result
Cable modems do not recover partial Upstream service
some cablemodems should recover, but I see that it does not work with any
Attached complete result of: "show load-balance dynamic"
also filtered by states: Success - cmRejected
most have the status: cmRejected
Please tell me if I need to add something in the cmts configuration or docsis file
I add a docsis file that I use to check if I need to add or change anything for this to work
Please help me with this to make the command work
Thank you very much for your valuable help
These error messages indicate that you have return power issues:
90b1.34fc.37ec 6->6 7,8->7,8,6,5 16,2,3,4,13,14,15,1->- broadcast-ranging dbc cmRejected TXP 2023-06-18 10:20:14
7896.84bd.1d5e 11->11 1->1,2,3,4 5,6,7,8,29,30,31,32->- broadcast-ranging dbc cmRejected TXP 2023-06-18 10:20:14
TXP = Transmit Power
The first modem was trying to move from 2 channels with ids 7,8 to 4 channels with ides 5,6,7,8 and the modem could not comply because it would have exceeded the Transmit power for 4 channels which is 49 dB.
The second modem is the same thing trying to move from single upstream to 4 channel bonded and the CM says no, that would make my Transmit power too hign.
for a single channel you can have Transmit power up to 58 dB, for two channels it can have up to 54 dB per-channel power, for 4 channel bonding the max transmit level is 49 dB per-channel. All of these have a total power of 58 dB, but when you double the channels you lose ~4 dB per-channel, so that when you add the combined power together you get 58 dB.
your first modem has a TX power > 49 dB per-channel and < 54 dB per channel, which is why it can bond to two channels, your second modem has a per-channel (single channel) of > 54 dB which is why it is rejecting the Partial Service recovery because bonding to 4 channels would exceed its max transmit power.
These all indicate RF plant problems, rather than CMTS issues, most likely levels not set in the field correctly or excessive splitters at customer premise.
On newer Casa software builds, the CMTS does not classify modems that running into TX Power issues as partial service, it has a second category called reduced, i.e. scm reduced that will show the modems that are running in a reduced channel set due to power levels, and partial service shows modems that have signal problems, SNR/ FEC etc. on channels they would otherwise be able to use.
I believe the reduced feature came in, at 8.6 release.
Hi
Our cmts have the version Rel 8.6.1, how can I see or enable the reduced category in the CMTS
show cable modem reduced
Hi
in the cmts it does not allow me that command
CASA-C100G#show cable modem r
registered-traditional-docsis show 3.0 cable modem but registered as 2.0
remote-node show cable modem remote-node
remote-query show cable modem remote information
rip router rip
rogue cable modems that have failed the dynamic shared-secret authentication checks