View Full Version : What is a rescue CMTS?
Hi
Been having disconnects every 48 hours or so now for a couple of weeks - repowering the cm or a release/renew on the router brings it straight back - the cm modem log shows many references to "locked and synced to rescue cmts - all is well" this appears throughout the cm log all day - is all well if it needs that many rescues?
Thx
Guy
KingDaveRa
30-12-2009, 14:49
Mine's been doing it for the last few days, yet still working quite happily. My power level is a bit high, and my sync light is flashing constantly. I've got an engineer hopefully coming back this afternoon (one came this morning to poke it about) so hopefully get it sorted!
Sephiroth
30-12-2009, 17:46
It wouldn't half help if you posted your modem stats (upstreamj/downstream/Operational Config/Event Log) rather than picking two words out of the event log.
Tell us also where you are.
Ignitionnet
30-12-2009, 18:04
A rescue CMTS doesn't exist on the Virgin network it's just what the modem says when you reconnect after being disconnected. It's quite misleading.
Sephiroth
30-12-2009, 18:07
A rescue CMTS doesn't exist on the Virgin network it's just what the modem says when you reconnect after being disconnected. It's quite misleading.
All's well then! LOL.
Ignitionnet
30-12-2009, 18:20
All's well then! LOL.
Yep, I think the functionality was intended for high availability scenarios where you have a node connected to a primary and secondary CMTS with secondary detecting failure of primary and taking over its' function.
Hi
This is the modem details (ntl255)
Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 12
Downstream Frequency : 322750000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : -4.1 dBmV
Downstream SNR : 38.8 dB
Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 3
Upstream Frequency : 45800000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 55.5 dBmV
Upstream Mini-Slot Size : 2
First TimeLast TimePriorityDescription
Wed Dec 30 19:09:45 2009 Wed Dec 30 19:09:45 2009 Information (7)Downstream sync ok
Wed Dec 30 19:09:45 2009 Wed Dec 30 19:09:45 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 19:09:45 2009 Wed Dec 30 19:09:45 2009 Information (7)Downstream sync ok
Wed Dec 30 19:09:45 2009 Wed Dec 30 19:09:45 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 19:09:45 2009 Wed Dec 30 19:09:45 2009 Information (7)Downstream sync failed
Wed Dec 30 19:09:44 2009 Wed Dec 30 19:09:44 2009 Information (7)Downstream sync ok
Wed Dec 30 19:09:44 2009 Wed Dec 30 19:09:44 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 19:09:44 2009 Wed Dec 30 19:09:44 2009 Information (7)Downstream sync ok
Wed Dec 30 19:09:44 2009 Wed Dec 30 19:09:44 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 19:09:44 2009 Wed Dec 30 19:09:44 2009 Information (7)Downstream sync failed
Wed Dec 30 19:08:42 2009 Wed Dec 30 19:08:42 2009 Information (7)Downstream sync ok
Wed Dec 30 19:08:42 2009 Wed Dec 30 19:08:42 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 19:08:42 2009 Wed Dec 30 19:08:42 2009 Information (7)Downstream sync ok
Wed Dec 30 19:08:42 2009 Wed Dec 30 19:08:42 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 19:08:42 2009 Wed Dec 30 19:08:42 2009 Information (7)Downstream sync failed
Wed Dec 30 19:08:41 2009 Wed Dec 30 19:08:41 2009 Information (7)Downstream sync ok
Wed Dec 30 19:08:41 2009 Wed Dec 30 19:08:41 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 19:08:41 2009 Wed Dec 30 19:08:41 2009 Information (7)Downstream sync ok
Wed Dec 30 19:08:40 2009 Wed Dec 30 19:08:40 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 19:08:40 2009 Wed Dec 30 19:08:40 2009 Information (7)Downstream sync failed
Wed Dec 30 19:08:04 2009 Wed Dec 30 19:08:04 2009 Information (7)Downstream sync ok
Wed Dec 30 19:08:04 2009 Wed Dec 30 19:08:04 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 19:08:04 2009 Wed Dec 30 19:08:04 2009 Information (7)Downstream sync ok
Wed Dec 30 19:08:04 2009 Wed Dec 30 19:08:04 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 19:08:04 2009 Wed Dec 30 19:08:04 2009 Information (7)Downstream sync failed
Wed Dec 30 19:05:19 2009 Wed Dec 30 19:05:19 2009 Information (7)Downstream sync ok
Wed Dec 30 19:05:19 2009 Wed Dec 30 19:05:19 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 19:05:19 2009 Wed Dec 30 19:05:19 2009 Information (7)Downstream sync ok
I don't recall any references to rescue cmts previously, I have logged a call with faults and they have said the fault is either linked to a high number of T3 timeouts they can see on my modem or it is linked to a larger problem with software on the motorola kit that has just been installed which they are waiting motorola staff to attend and sort!
Area is Derby
Thx
Guy
---------- Post added at 19:21 ---------- Previous post was at 19:17 ----------
A rescue CMTS doesn't exist on the Virgin network it's just what the modem says when you reconnect after being disconnected. It's quite misleading.
If I repower the modem it seems to connect normally and then the rescue business starts 5 mins afterwards - see below from earlier today
Wed Dec 30 12:25:08 2009 Wed Dec 30 12:25:08 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 12:25:08 2009 Wed Dec 30 12:25:08 2009 Information (7)Downstream sync ok
Wed Dec 30 12:25:08 2009 Wed Dec 30 12:25:08 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 12:25:08 2009 Wed Dec 30 12:25:08 2009 Information (7)Downstream sync failed
Wed Dec 30 12:25:08 2009 Wed Dec 30 12:25:08 2009 Information (7)Downstream sync ok
Wed Dec 30 12:25:08 2009 Wed Dec 30 12:25:08 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 12:25:08 2009 Wed Dec 30 12:25:08 2009 Information (7)Downstream sync ok
Wed Dec 30 12:25:07 2009 Wed Dec 30 12:25:07 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 12:25:06 2009 Wed Dec 30 12:25:06 2009 Information (7)Downstream sync failed
Wed Dec 30 12:25:06 2009 Wed Dec 30 12:25:06 2009 Information (7)Downstream sync ok
Wed Dec 30 12:25:06 2009 Wed Dec 30 12:25:06 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 12:25:06 2009 Wed Dec 30 12:25:06 2009 Information (7)Downstream sync ok
Wed Dec 30 12:25:06 2009 Wed Dec 30 12:25:06 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 12:25:05 2009 Wed Dec 30 12:25:05 2009 Information (7)Downstream sync failed
Wed Dec 30 12:25:05 2009 Wed Dec 30 12:25:05 2009 Information (7)Downstream sync ok
Wed Dec 30 12:25:05 2009 Wed Dec 30 12:25:05 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 12:25:05 2009 Wed Dec 30 12:25:05 2009 Information (7)Downstream sync ok
Wed Dec 30 12:25:05 2009 Wed Dec 30 12:25:05 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 12:25:05 2009 Wed Dec 30 12:25:05 2009 Information (7)Downstream sync failed
Wed Dec 30 12:19:58 2009 Wed Dec 30 12:19:58 2009 Information (7)The s/w filename specified in the config file is the same as ...
Wed Dec 30 12:19:58 2009 Wed Dec 30 12:19:58 2009 Information (7)A software upgrade filename was specified in the config file.
Wed Dec 30 12:19:58 2009 Wed Dec 30 12:19:58 2009 Information (7)Authorized
Wed Dec 30 12:19:58 2009 Wed Dec 30 12:19:58 2009 Information (7)Registration complete!
Wed Dec 30 12:19:58 2009 Wed Dec 30 12:19:58 2009 Information (7)We registered with a DOCSIS 1.1 config file!
Wed Dec 30 12:19:58 2009 Wed Dec 30 12:19:58 2009 Information (7)Received a REG-RSP message from the CMTS...
Wed Dec 30 12:19:58 2009 Wed Dec 30 12:19:58 2009 Information (7)Sending a REG-REQ to the CMTS...
Wed Dec 30 12:19:58 2009 Wed Dec 30 12:19:58 2009 Information (7)CableModem SNMP configure complete
Wed Dec 30 12:19:57 2009 Wed Dec 30 12:19:57 2009 Information (7)IP init completed ok
Wed Dec 30 12:19:57 2009 Wed Dec 30 12:19:57 2009 Information (7)CableModem TFTP init ok
Sephiroth
30-12-2009, 20:45
It's the Motorola kit (if that's what your CMTS is) that sets the downstream power (which is rather low IMO). So this time I'd trust what the techie told you as to the instability.
It seems the real rescue of the CMTS is with Motorola bods right now; somebody needs to rescue VM from putting in duff kit. Shouldn't kit be staged and validated etc before being put into public use?
Ignitionnet
30-12-2009, 21:16
The downstream power is nothing to do with the Motorola BSR, it's to do with the several kilometres of amplified fibre and coax in between the BSR and the customer. The BSR just outputs a fixed value, if it were outputting low it would be noted by automated monitoring systems and would affect everyone.
The customer is probably right at the end of a cascade farthest away from the nearest amplifier or on the wrong tap. Upstream power is high for 16QAM so this might be part of the problem, could also be BSR software.
Sephiroth
30-12-2009, 22:05
The downstream power is nothing to do with the Motorola BSR, it's to do with the several kilometres of amplified fibre and coax in between the BSR and the customer. The BSR just outputs a fixed value, if it were outputting low it would be noted by automated monitoring systems and would affect everyone.
The customer is probably right at the end of a cascade farthest away from the nearest amplifier or on the wrong tap. Upstream power is high for 16QAM so this might be part of the problem, could also be BSR software.
I didn't express myself very well, obviously. The "which is rather low" remark that I made referred to what was at the CM end after all impedances had been accounted for. So there we agree.
Tell me if I'm wrong, but the BSR outputs at 50 dBmv, budgeted to arrive at the "ideally impeded" cable modem at 0 dBmv.
KingDaveRa
30-12-2009, 23:10
Mine's still doing it.
Downstream Lock : Locked
Downstream Channel Id : 19
Downstream Frequency : 314750000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 3.8 dBmV
Downstream SNR : 42.1 dB
First TimeLast TimePriorityDescription
Wed Dec 30 23:08:44 2009 Wed Dec 30 23:08:44 2009 Information (7)Downstream sync ok
Wed Dec 30 23:08:44 2009 Wed Dec 30 23:08:44 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 23:08:44 2009 Wed Dec 30 23:08:44 2009 Information (7)Downstream sync ok
Wed Dec 30 23:08:44 2009 Wed Dec 30 23:08:44 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 23:08:44 2009 Wed Dec 30 23:08:44 2009 Information (7)Downstream sync failed
Wed Dec 30 23:08:44 2009 Wed Dec 30 23:08:44 2009 Information (7)Downstream sync ok
Wed Dec 30 23:08:44 2009 Wed Dec 30 23:08:44 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 23:08:44 2009 Wed Dec 30 23:08:44 2009 Information (7)Downstream sync ok
Wed Dec 30 23:08:43 2009 Wed Dec 30 23:08:43 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 23:08:43 2009 Wed Dec 30 23:08:43 2009 Information (7)Downstream sync failed
Wed Dec 30 23:07:32 2009 Wed Dec 30 23:07:32 2009 Information (7)Downstream sync ok
Wed Dec 30 23:07:32 2009 Wed Dec 30 23:07:32 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 23:07:32 2009 Wed Dec 30 23:07:32 2009 Information (7)Downstream sync ok
Wed Dec 30 23:07:32 2009 Wed Dec 30 23:07:32 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 23:07:32 2009 Wed Dec 30 23:07:32 2009 Information (7)Downstream sync failed
Wed Dec 30 23:07:32 2009 Wed Dec 30 23:07:32 2009 Information (7)Downstream sync ok
Wed Dec 30 23:07:32 2009 Wed Dec 30 23:07:32 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 23:07:32 2009 Wed Dec 30 23:07:32 2009 Information (7)Downstream sync ok
Wed Dec 30 23:07:31 2009 Wed Dec 30 23:07:31 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 23:07:31 2009 Wed Dec 30 23:07:31 2009 Information (7)Downstream sync failed
Wed Dec 30 23:06:42 2009 Wed Dec 30 23:06:42 2009 Information (7)Downstream sync ok
Wed Dec 30 23:06:42 2009 Wed Dec 30 23:06:42 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 23:06:42 2009 Wed Dec 30 23:06:42 2009 Information (7)Downstream sync ok
Wed Dec 30 23:06:42 2009 Wed Dec 30 23:06:42 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 23:06:42 2009 Wed Dec 30 23:06:42 2009 Information (7)Downstream sync failed
Wed Dec 30 23:06:41 2009 Wed Dec 30 23:06:41 2009 Information (7)Downstream sync ok
Wed Dec 30 23:06:41 2009 Wed Dec 30 23:06:41 2009 Information (7)locked and synced to rescue CMTS...all is well!
Wed Dec 30 23:06:41 2009 Wed Dec 30 23:06:41 2009 Information (7)Downstream sync ok
Wed Dec 30 23:06:41 2009 Wed Dec 30 23:06:41 2009 Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Wed Dec 30 23:06:41 2009 Wed Dec 30 23:06:41 2009 Information (7)Downstream sync failed
Wed Dec 30 22:50:12 2009 Wed Dec 30 22:50:12 2009 Information (7)Downstream sync ok
Wed Dec 30 22:50:12 2009 Wed Dec 30 22:50:12 2009 Information (7)locked and synced to rescue CMTS...all is well!
Still got a winking sync light.
Ignitionnet
30-12-2009, 23:30
Tell me if I'm wrong, but the BSR outputs at 50 dBmv, budgeted to arrive at the "ideally impeded" cable modem at 0 dBmv.
Next to impossible to get the ideally impeded and amplified cable modem though. After a line extender on a single branch segment the modems on the closest tap will get considerably more power than those 150 feet away. My modem gets +16dBmV before attenuation but the people who are at the end of the branch are probably closer to 0dBmV. Nothing Virgin or any other cable company can do about things like this, some people are right next to their closest amplifier, some on the same rated taps are considerably further away.
Hi
Tech has now been and replaced modem with a black 256 and replaced the modem end cable connector. 2 hours later and no rescue cmts entries in the log and no loss of sync.
I notice from the modem config that the downstream modulation has changed from QAM256 to QAM64 and the upstream from QAM16 to QPSK
Thx
Welshchris
02-01-2010, 15:48
Hi
Tech has now been and replaced modem with a black 256 and replaced the modem end cable connector. 2 hours later and no rescue cmts entries in the log and no loss of sync.
I notice from the modem config that the downstream modulation has changed from QAM256 to QAM64 and the upstream from QAM16 to QPSK
Thx
u have proberbly been taken off the newer Motorolla BSR and put onto the older Cisco UBR kit thats why its changed.
almost all new modems are registered onto the older kit rather than the newer kit unless its a 50mb modem.
Ignitionnet
02-01-2010, 17:20
Modems are balanced between all platforms automatically, with only the parameters of the balance changed. There's not someone at Virgin deciding which platform a new modem goes onto when it is registered and he may find himself on the BSR shortly as and when load balancing decides it's required.
Where did you get the idea that 'almost all' new modems are going onto the legacy uBRs not the BSR / 10k?
Welshchris
02-01-2010, 17:51
i got the idea from Second line support and CEO office. They told me almost all new modems are put onto UBRs to start off with except 50mb and its not until network teams balence networks do any get changed around.
The reason they told me this is because when they told me they wanted to take me off the BSR and put back onto the UBR in Swansea they said it was quicker to just swap the modem than get the network teams to change platform as i had a spare modem that wasnt registered.
Ignitionnet
02-01-2010, 17:55
It's very much an area dependent thing. Some modems will move immediately, some will never move. I think at least some modems range to the uBRs first by default then get pushed to the overlay network via their config files and a downstream channel change. YMMV.
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.