CMTS MOTOROLA BSR 64000 - Clock Problem | docsis.org

You are here

CMTS MOTOROLA BSR 64000 - Clock Problem

6 posts / 0 new
Last post
Endrit
CMTS MOTOROLA BSR 64000 - Clock Problem

Does anyone have a problem that CMTS loses time ?

Current Time: 05/25-07:18:40

Slot Type Sub Red State RM IO UpTime LastUpTime Success Failure
0 DRX RX48 - RUN x x 00:00:00 1 1
1 DRX RX48 - RUN x x 00:00:00 1 1
2 DRX RX48 - RUN x x 00:00:00 40w01d07h 2 2
3 DRX RX48 - RUN x x 00:00:00 1 1
4 DTX TXPlusE - RUN x x 00:00:00 1 1
5 DTX TXPlusE - RUN x x 00:00:00 1 1
6 - - - - 0 0
7 SRM 10G 8 RUN x x 00:00:00 0 0
8 SRM 10G - stby x x 00:00:00 1 1
9 DTX TXPlusE - RUN x x 00:00:00 1 1
10 DTX TXPlusE - RUN x x 00:00:00 1 1
11 DTX TXPlusE - RUN x x 00:00:00 1 1
12 DTX TXPlusE - RUN x x 00:00:00 1 1
13 DTX TXPlusE - RUN x x 00:00:00 1 1
14 DTX TXPlusE - RUN x x 00:00:00 1 1
15 - - - - 0 0

:7A#show clock
THU MAY 25 07:18:43 2000
Timezone UTC, 1 hr 0 min offset from UTC, Daylight Saving is of

Is this a bug or something ?

Endrit

cmcaldas
I believe yes

I've had 3 different systems loose clock early this month. 2 use remote ntp servers and another was just configured with the date and time internally. re-adding the internal clock resolved the issue. think of it a y2k double issue lol
as much as I've been working on these units, it's time to replace them. key issue I've found is they had been designed for multicast and regular internet traffic. now with everyone streaming and it being unicast traffic, the srm cpu can't keep up (depending on the number of customers on the chassis. example; 5k customers cpu is around 20% free. with 200 customers cpu is around 90% free). when the cpu drops below 20 all kind of issue can and do happen

Endrit
CMTS MOTOROLA BSR 64000 - Clock Problem

Hey cmcaldas

Thanks first of all for your time.

When you se re-adding the clock, do you mean manually ?
I use sntp on my systems.

Endrit

cmcaldas
yes

Hi Endrit
yes, I would recommend manually.
example: BSR2:7A#clock set 05:38:48 15 jan 2020
clock set 05:38:48 15 jan 2020

eniac
Hi,

Hi,

I have the same problem.
I set the time manually, and deleted the setting of snmp server with command:
#no sntp server

Now the time and date is OK:
BTbsr64000-1:7A#show clock
WED JAN 22 13:49:07 2020
Timezone CET, 1 hr 0 min offset from UTC, Daylight Saving is off

But the units' uptime remain the same:
#sho chassis status

Current Time: 01/22-13:49:39
Running archive: FLASH:6422.srm4

Slot Type Sub Red State RM IO UpTime LastUpTime Success Failure
0 DRX RX48 - RUN x x 00:00:00 1 1
1 DRX RX48 - RUN x x 00:00:00 1 1
2 DRX RX48 - RUN x x 00:00:00 1 1
3 DRX RX48 - RUN x x 00:00:00 1 1
4 - - - - 0 0
5 - - - - 0 0
6 - - - - 0 0
7 SRM4 8 RUN x x 00:00:00 0 0
8 SRM4 - stby x - 00:00:00 1 1
9 - - - - 0 0
10 - - - - 0 0
11 DTX TX32E - RUN x x 00:00:00 00:03:35 2 2
12 - - - - 0 0
13 DTX TX32E - RUN x x 00:00:00 1 1
14 - - - - 0 0
15 HSIM GE2/ETH8 - RUN x x 00:00:00 1 1

How can I solve to see the real uptime?

Thank You!

At.

cmcaldas
clock

that won't show until you do a reload unfortunately. you could try an srm failover first.
let us know how you make out