D3.0 CMS Can´t go online (solved) | docsis.org

You are here

D3.0 CMS Can´t go online (solved)

13 posts / 0 new
Last post
Rchakiras
D3.0 CMS Can´t go online (solved)
AttachmentSize
Image icon cisco.jpg38.98 KB
Image icon CASA.jpg27.73 KB

Hi im new at this. I have two cmts in operation (CISCO 10K AND CASA 3200). I operate with CNR, im workin with docsis 1.x ,1.0 and have no problem but with the cms 3.0 cant go online all set in

Cisco init(io)
Casa init(d)

I think may have touble with the CNR but im not sure.

Can anybody help me?

Jaime Rios
dhcp offer:

Hi, checking one of the images you sent, init(io) "(init(io)—The Cisco CMTS has seen DHCPOFFER)" that indicates the Cisco Cmts saw an offer being sent to the cable modem, so, chances are the information sent from CNR is not enough for that cable modem, so, definitely a troubleshoot has to be done on CNR side.
Try to run a capture on CNR to check what the modem is asking for, and what CNR is responding.
Regards.-

Rchakiras
Hi Jaime how can i do that?

Hi Jaime how can i do that?

mbowe
on the cisco cmts :

on the cisco cmts :

debug cable mac-address xxxx.xxxx.xxxx
debug cable dhcp
term mon

also on the cnr server, you could use wireshark :
tcpdump port bootps -s 1500 -v

Rchakiras
Here is the term mon

Here is the term mon

File attachments: 
mbowe
Sep 15 23:58:32.010:

Your debug says :

Sep 15 23:58:32.010: DHCP Option 2 - Time Offset: 4294945696

Above looks bogus.
Should be offset in seconds (eg 36000 for GMT+10).

Unless that's how things look for GMT-XX? Dont know for sure, never tried.
Just try setting to 0 if need be to identify if this option is the one preventing modems from booting.

kwesibrunee
Besides the wonky time offset

Besides the wonky time offset, you are missing a tftp server or next server in you dhcp offer, the modem does not know where to go to download its config....

So if your using ISC add a next-server xxx.xxx.xxx.xxx; statement, or whatever works for your dhcp server.

DocsisAdmin
c3200 debug

On the c3200,
show log
(see if there's anything interesting there, such as the IP addresses offered not being in the ip bundle scope).

debug cable mac xxxx.xxxx.xxxx
debug cable dhcp
debug cable cfg
debug cable verbose
logging debug

Clear the cable modem, watch it boot.

Afterward-
no logging debug

Rchakiras
CASA

DEBUG

File attachments: 
DocsisAdmin
Missing TFTP info

I see the config file name in the offer, but not the TFTP server or next server field options. Those need to be configured in CNR.

Rchakiras
TFTP

I have configured the TFTP, and i recently change the time offset, but still CMS 3.0 can´t go online, cms doc 2.0 can

File attachments: 
DocsisAdmin
No next-server?

I still don't see the next-server field. It should point to the tftp server. I don't think it's an extended options field, it should be part of the main scope configuration. It's been years since I've played with DHCP but I'm pretty sure it's a requirement for docsis 3.0.

Here's a snippet from another config posted here:

next-server 10.1.1.1;
option broadcast-address 10.255.255.255;
option time-offset -18000;
option domain-name "somedomain.net";
option routers 10.1.1.1;
option time-servers 10.1.1.1;
option ntp-servers 10.1.1.1;
option domain-name-servers 10.1.1.1;

Rchakiras
Next- server

Thanks a lot.

Thats was the answer.

Log in or register to post comments