Hello,
I am trying to set up new part of Thomson modems with Arris 1500 station, but modems stuck at DISCOVER/OFFER loop infinitely, while Arris modems works perfectly. Moreover, Thomsons behave completly strangely: 4 of 20 new modems of new part work nice, without any problems, while 16 other stuck at dhcp discover/offer stage.
dhcpd.conf:
[code]subnet 10.3.0.0 netmask 255.255.252.0 {
option routers 10.3.0.3;
next-server 10.3.0.3;
host 10.3.0.81 {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 10.3.0.81;
filename "thomson6";
}
}[/code]
Any suggestions?
Need more data/logs etc. At first glance - Time of Day, do You have it provisioned? Generally not much options in Your dhcpd.conf. :) Use dhcpdump it can help you a lot.
Ok, I've installed TOD server, but problem for Thomson still exists :(
More verbose information and logs
10.3.0.1 -- my dhcp & time & tftp server
Now dhcpd.conf looks like:
subnet 10.3.0.0 netmask 255.255.252.0 {
option routers 10.3.0.3;
next-server 10.3.0.1;
option tftp-server-name "10.3.0.1";
option time-servers 10.3.0.1;
option time-offset 10800;
host 10.3.0.81 {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 10.3.0.81;
filename "thomson6";
}
TOD server:
# netstat -l | grep time
udp 0 0 *:time *:*
And it works for Arris modem (which reports correct datetime and status: "TOD retrived"):
14:08:14.482784 IP 10.3.0.136.1424 > 10.3.0.1.37: UDP, length 1
14:08:14.482806 IP 10.3.0.1.37 > 10.3.0.136.1424: UDP, length 4
dhcpd.log for Thomson:
Mar 26 14:06:35 world dhcpd: DHCPDISCOVER from 00:11:e3:8e:a0:4a via 10.3.0.2
Mar 26 14:06:35 world dhcpd: DHCPOFFER on 10.3.0.81 to 00:11:e3:8e:a0:4a via 10.3.0.2
Mar 26 14:06:38 world dhcpd: DHCPDISCOVER from 00:11:e3:8e:a0:4a via 10.3.0.2
Mar 26 14:06:38 world dhcpd: DHCPOFFER on 10.3.0.81 to 00:11:e3:8e:a0:4a via 10.3.0.2
Mar 26 14:06:41 world dhcpd: DHCPDISCOVER from 00:11:e3:8e:a0:4a via 10.3.0.2
Mar 26 14:06:41 world dhcpd: DHCPOFFER on 10.3.0.81 to 00:11:e3:8e:a0:4a via 10.3.0.2
...
Thomson does not request TOD according to tcpdump (as it had't received IP address, I guess)
Station config and state:
[CornerStone] admin# info
Parameter Value
--------- -----
...
sw-filename "CMTS_ALBUM_4.3.306"
...
bootp-relay-control relay-tagging-enabled
time-rfc868-addr 10.3.0.1
time-offset 10800 seconds
time-sntp-addr 0.0.0.0
...
And here is dhcpdump:
TIME: 2010-03-26 16:31:28.494
IP: 10.3.0.2 (0:e0:81:b1:b7:6d) > 10.3.0.1 (0:30:48:9a:e9:ca)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 2b752799
SECS: 12
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 10.3.0.2
CHADDR: 00:11:e3:8e:a0:4a:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 55 ( 8) Parameter Request List 1 (Subnet mask)
2 (Time offset)
3 (Routers)
4 (Time server)
7 (Log server)
6 (DNS server)
66 (TFTP server name)
67 (Bootfile name)
OPTION: 60 ( 86) Vendor class identifier docsis2.0:052401010102010203010104010105010106010107010f0801100901000a01010b01180c0101
OPTION: 43 ( 39) Vendor specific info 0803001095c80754 .......T
686f6d736f6ec906 homson..
54434d343230ca0a TCM420..
535435322e30322e ST52.02.
3033cb03342e30 03..4.0
OPTION: 61 ( 7) Client-identifier 01:00:11:e3:8e:a0:4a
OPTION: 57 ( 2) Maximum DHCP message size 1500
---------------------------------------------------------------------------
TIME: 2010-03-26 16:31:28.494
IP: 10.3.0.1 (0:30:48:9a:e9:ca) > 10.3.0.2 (0:e0:81:b1:b7:6d)
OP: 2 (BOOTPREPLY)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 2b752799
SECS: 12
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 10.3.0.81
SIADDR: 10.3.0.1
GIADDR: 10.3.0.2
CHADDR: 00:11:e3:8e:a0:4a:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: thomson6.
OPTION: 53 ( 1) DHCP message type 2 (DHCPOFFER)
OPTION: 54 ( 4) Server identifier 10.3.0.1
OPTION: 51 ( 4) IP address leasetime 28800 (8h)
OPTION: 1 ( 4) Subnet mask 255.255.252.0
OPTION: 2 ( 4) Time offset 7200 (2h)
OPTION: 3 ( 4) Routers 10.3.0.3
OPTION: 4 ( 4) Time server 10.3.0.1
OPTION: 7 ( 4) Log server 10.3.0.1
OPTION: 6 ( 4) DNS server 10.3.0.1
OPTION: 66 ( 14) TFTP server name 10.3.0.1
Well the first thing I noticed is that your dhcp reply does not contain all of the parameters the device requested
The Device Requested
2 (Time offset)
3 (Routers)
4 (Time server)
7 (Log server)
6 (DNS server)
66 (TFTP server name)
67 (Bootfile name)
You sent:
2 (Time offset)
3 (Routers)
4 (Time server)
7 (Log server)
6 (DNS server)
66 (TFTP server name)
I would add option 67 in addition to your other info
i.e.
host 10.3.0.81 {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 10.3.0.81;
filename "thomson6";
option bootfile-name "thompson6";
}
Some modems want it one way some another does not hurt to put it twice but won't work if a required one is missing
give that a shot and lets see where we are at.
Mar 26 14:06:35 world dhcpd: DHCPDISCOVER from 00:11:e3:8e:a0:4a via 10.3.0.2
Mar 26 14:06:35 world dhcpd: DHCPOFFER on 10.3.0.81 to 00:11:e3:8e:a0:4a via 10.3.0.2
===
Can You actually ping the modem from prov-server or cmts? Even for a while?
Looks like routing problem (however due to Your dhcpd.conf should be highly unlikely:) )
Does the file "thomson6" actually exist in /tftpboot , is 755(rights) set on /tftpboot? Check with ls -la.
===
bootp-relay-control relay-tagging-enabled
You have of course set address in bootp-list?
========
time-sntp-addr 0.0.0.0
Set it too - Arris needs it. Use ntpd on server side.
============
IP: 10.3.0.1 (0:30:48:9a:e9:ca) > 10.3.0.2 (0:e0:81:b1:b7:6d)
Looks odd - Arris uses 0000CA as oui, are You sure it is well? How is this all connected - via something or what?
My example with Arris 1500:
TIME: 15:46:18.665598
IP: 10.9.0.5.68 (00:00:ca:26:b0:bf) > 10.9.0.1.67 (00:0e:0c:68:ff:a2,)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 05c76374
SECS: 0
FLAGS: 7f80
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 10.9.0.5
CHADDR: 00:15:ce:2f:fc:15:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 3 (DHCPREQUEST)
OPTION: 57 ( 2) Maximum DHCP message size 984
OPTION: 54 ( 4) Server identifier 10.9.0.1
OPTION: 50 ( 4) Request IP address 10.9.2.14
OPTION: 51 ( 4) IP address leasetime 1209600 (2w)
OPTION: 60 ( 86) Vendor class identifier docsis1.1:052401010102010103010104010105010106010107010f0801100901000a01010b01080c0101
OPTION: 55 ( 7) Parameter Request List 66 (TFTP server name)
67 (Bootfile name)
1 (Subnet mask)
3 (Routers)
2 (Time offset)
4 (Time server)
7 (Log server)
---------------------------------------------------------------------------
TIME: 15:46:18.666329
IP: 10.9.0.1.67 (00:0e:0c:68:ff:a2) > 10.9.0.5.67 (00:00:ca:26:b0:bf,)
OP: 2 (BOOTPREPLY)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 05c76374
SECS: 0
FLAGS: 7f80
CIADDR: 0.0.0.0
YIADDR: 10.9.2.14
SIADDR: 10.9.0.1
GIADDR: 10.9.0.5
CHADDR: 00:15:ce:2f:fc:15:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: cmts1-u2-4000-k1.
OPTION: 53 ( 1) DHCP message type 5 (DHCPACK)
OPTION: 54 ( 4) Server identifier 10.9.0.1
OPTION: 51 ( 4) IP address leasetime 1209600 (2w)
OPTION: 1 ( 4) Subnet mask 255.255.0.0
OPTION: 3 ( 4) Routers 10.9.0.1
OPTION: 2 ( 4) Time offset 1 (1s)
OPTION: 4 ( 4) Time server 10.9.0.1
OPTION: 7 ( 4) Log server 10.9.0.1
See my point?
OK, more to come :)
>> Can You actually ping the modem from prov-server or cmts? Even for a while?
Yes, connectivity is not a problem. Actually, I've tried several configurations: exactly on the station, near cmts, and in office -- far away from cmts.
>> Does the file "thomson6" actually exist in /tftpboot , is 755(rights) set on /tftpboot? Check with ls -la.
Yes, it does, with correct rights. I can get it from console, using tftp> command line without any problems.
>> time-sntp-addr 0.0.0.0
>> Set it too - Arris needs it. Use ntpd on server side.
Okay, I've set it up too and now my station and modems are in sync.
>> Looks odd - Arris uses 0000CA as oui, are You sure it is well? How is this all connected - via something or what?
Actually it can be another modem, or modem via station, or, even, CPE. I mention that line to prove that time-of-day server on my machine works fine and any device can get time correctly.
>> You have of course set address in bootp-list?
[CornerStone] bootp-list# show
BOOTP relay table
Index Status IP Address Client Types Relay Count
----- ---------- --------------- ------------- -----------
1 active 10.3.0.1 any-cm-or-cpe 9507
...
According to your dump I've added to my config file log server option too.
Now its fully packed with any kind of servers!
update: breaking news! see last post for details :)
Ok, I've put this option in config, but modem does not request firmware for now -- it still stuck on requesting IP address.
And some more news about this issue, absolutely strange:
If I reboot cmts (reset command - Restarts the CMTS), any Thomson modem from new part will work perfectly and come online! Lets call this modem "modem A". Now, if I change it to another Thomson modem (also from this part, let call us "modem B") it wont come online but stuck on dhcp discover/offer stage. At this moment, again, if I reboot my cmts with "modem B" connected -- it will come online and "modem A" wont! Vise versa this trick will work with any pair of thomson modems in box of brand new modems :)
Any suggestions? Its a magic!
I think that I have seen somewhere on the internet that this combination of modems and CMTS cannot work if modem firmware is not updated to the last version. It has something to do with too short DHCP discovery timer in older Thomson firmwares. I will try to find this link and post it here. In the meantime, try to upgrade at least one of the modems to the last firmware and try again.