dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1124

owlyn
MVM
join:2004-06-05
Newtown, PA
Netgear CM2050V
Netgear RBRE960
Netgear RBSE960

owlyn

MVM

[Equip] Ubee Modem Lights

I've had a leased Ubee DVM3203B modem for a few months now. It works great- no problems to report (actually better signal levels than on the Arris 722G I had), but I have a question. The US and DS lights are blue and blinking (in unison). The blinking just started recently. All of my channels are bonded (8 x 3, which is normal for me), and my Blast! speeds are fine (around 120/12 on IPv4 and IPv6, which is the way things were before they started blinking). So, what does the blinking (or solid) mean? The Ubee site just mentions color, not blinking/non-blinking. Blue means bonded, green means not bonded.

cHarley
join:2013-07-10
Boynton Beach, FL

cHarley

Member

[Equip] Re: Ubee Modem Lights

You need to post a copy of the modem status page that shows the signal levels and SNR. I suspect the the problem will be shown there.

owlyn
MVM
join:2004-06-05
Newtown, PA
Netgear CM2050V
Netgear RBRE960
Netgear RBSE960

owlyn

MVM

All of that is perfect, but here you go. I know my US levels are on the high side, but they were still okay over the summer, so that's not a problem.

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 6 681 MHz -4.8 dBmV 39.5 dB 144 223
2 Locked QAM256 1 651 MHz -4.5 dBmV 39.9 dB 9 27
3 Locked QAM256 2 657 MHz -4.7 dBmV 39.5 dB 28 31
4 Locked QAM256 3 663 MHz -4.5 dBmV 39.0 dB 34 0
5 Locked QAM256 4 669 MHz -4.5 dBmV 39.4 dB 39 28
6 Locked QAM256 5 675 MHz -4.8 dBmV 39.1 dB 113 0
7 Locked QAM256 7 687 MHz -4.9 dBmV 39.8 dB 134 160
8 Locked QAM256 8 693 MHz -5.0 dBmV 38.9 dB 120 116

Correctables Uncorrectables
144 223

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 7 5120 Ksym/sec 36 MHz 47.8 dBmV
2 Locked ATDMA 8 5120 Ksym/sec 30 MHz 47.2 dBmV
3 Locked ATDMA 9 5120 Ksym/sec 23 MHz 47.2 dBmV
4 Not Locked Unknown 0 Ksym/sec 0 MHz 0.0 dBmV

Status
System uptime 1 days 14h:54m:23s
Computers Detected: 1
CM Status: Operational
WAN Isolation: OFF
Time and Date: Sat Oct 04 08:53:19 2014

Interfaces
Interface Name Provisioned State Speed MAC Address
Ethernet CPE Interface Enabled Up 1000.000
RF MAC Interface Enabled Up 0.000
RF Downstream Interface 1 Enabled Up 42.884 n/a
RF Upstream Interface 1 Enabled Up 30.720 n/a
Software Loopback Enabled Up 0.000 n/a
PacketCable Embedded Interface Enabled Up 0.000
RF Downstream Interface 2 Enabled Up 42.884 n/a
RF Downstream Interface 3 Enabled Up 42.884 n/a
RF Downstream Interface 4 Enabled Up 42.884 n/a
RF Downstream Interface 5 Enabled Up 42.884 n/a
RF Downstream Interface 6 Enabled Up 42.884 n/a
RF Downstream Interface 7 Enabled Up 42.884 n/a
RF Downstream Interface 8 Enabled Up 42.884 n/a
RF Upstream Interface 2 Enabled Up 30.720 n/a
RF Upstream Interface 3 Enabled Up 30.720 n/a
RF Upstream Interface 4 Enabled Up 0.000 n/a

And while I'm here, here's the event log:

CM Event Log
Date/Time Event Level Event ID Description
10/03/2014 10:25 Critical (3) R5.0 Started Unicast Maintenance Ranging - No Response received - T3
10/03/2014 10:13 Warning (5) T203.0 MDD message timeout******
10/03/2014 10:13 Critical (3) R4.0 Received Response to Broadcast Maintenance Request, But no Unica
10/03/2014 10:13 Warning (5) T203.0 MDD message timeout******
10/03/2014 09:20 Critical (3) T4.0 SYNC Timing Synchronization failure - Failed to receive MAC SYNC
10/03/2014 09:20 Warning (5) T203.0 MDD message timeout******
10/02/2014 17:59 Notice (6) I401.0 TLV-11 - unrecognized OID******
Time Not Established Warning (5) D3.0 DHCP WARNING - Non-critical field invalid in response ******
Time Not Established Notice (6) Overriding MDD IP initialization parameters; IP provisioning mod
10/01/2014 22:38 Notice (6) I401.0 TLV-11 - unrecognized OID******
10/01/2014 22:38 Warning (5) D3.0 DHCP WARNING - Non-critical field invalid in response ******
10/01/2014 22:38 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mod
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK
10/01/2014 22:38 Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC fram
10/01/2014 22:38 Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK

EG
The wings of love
Premium Member
join:2006-11-18
Union, NJ

EG

Premium Member

The signals at that moment were o/k. And you are indeed bonding multiple channels on the down and up. Both the US and the DS blinking together typically means a firmware update is in progess but I really don't see any indication of that in the error log entries. Perhaps it's stuck somehow. Have you tried powercycling it / resetting it if it has a reset button on the rear ?

owlyn
MVM
join:2004-06-05
Newtown, PA

owlyn

MVM

Recycled/reset it, and now the lights are not blinking. BTW, the levels "at that moment" are my typical levels. Firmware was not updated.

andyross
MVM
join:2003-05-04
Aurora, IL

andyross to owlyn

MVM

to owlyn

Re: [Equip] Ubee Modem Lights

From the log, you appear to have had an outage on October 1, then a few glitches on the 2nd and 3rd. Maybe something about that caused the modem to start blinking the lights.

The Zoom 5341J has had a similar issue where the upstream light will sometimes start blinking.

cHarley
join:2013-07-10
Boynton Beach, FL
Motorola MB8600
(Software) pfSense

cHarley

Member

said by andyross:

The Zoom 5341J has had a similar issue where the upstream light will sometimes start blinking.

That's usually a sign that the upstream power level is too high, typically >51 dBmV

owlyn
MVM
join:2004-06-05
Newtown, PA

owlyn to andyross

MVM

to andyross
Yes, we had 3 power outages and 2 "poco dug up the comcast line" incidents 12 hours.