Hi,
I have a CMTS 1000. Or maybe it's a 1100 or 1500. How do I tell? Anyway, I had it to the point where the modem would get an IP, but not a config file. This is all just in a test environment. I use Debian Linux and DHCP. I've statically assigned my config file (cm1.md5) to the modem. I know the config file is good because I use it in other working environments. The bad part is that I've reset the CMTS to factory defaults and now I can't even get the moedm to get and IP address. Can anyone help me out?
Thanks,
emkowale
post your cmts config, dhcp config and tftp config file. also, post your dhcpd lgo file and xinetd log file. without these data it's hard to help you.
Hello,
Thanks for the help. Here is the dhcpd.conf file:
option domain-name-servers 192.168.0.12;
option routers 192.168.0.12;
ddns-update-style interim;
authoritative;
max-lease-time 21600;
ignore client-updates;
default-lease-time 21600;
option ntp-servers 192.168.0.12;
option log-servers 192.168.0.12;
shared-network "autobot"
{
subnet 192.168.0.0 netmask 255.255.255.0 {
authoritative;
default-lease-time 21600;
option subnet-mask 255.255.255.0;
option routers 192.168.0.12;
option broadcast-address 255.255.255.255;
pool {
range dynamic-bootp 192.168.0.100 192.168.0.254;
}
}
}
# CM
host CM {
next-server 192.168.0.12;
filename "cm1.md5";
hardware ethernet 00:16:cf:4a:99:ce;
fixed-address 192.168.0.7;
}
Here is the tftp config file:
Main
{
NetworkAccess 1;
ClassOfService
{
ClassID 1;
MaxRateDown 3000000;
MaxRateUp 250000;
PriorityUp 1;
PrivacyEnable 0;
}
MaxCPE 1;
/* CmMic 9293513f89c3d8bb5cb920c8cadf3b83; */
/* CmtsMic 5d8e227485621dc8c84cda25d0aefc27; */
/*EndOfDataMkr*/
/* Pad */
}
Here is the dhcpd log file:
Nov 8 12:21:57 omega dhcpd: DHCPDISCOVER from 00:16:cf:4a:99:ce via eth0
Nov 8 12:21:57 omega dhcpd: DHCPOFFER on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:21:59 omega dhcpd: DHCPREQUEST for 192.168.0.7 (192.168.0.12) from 00:16:cf:4a:99:ce via eth0
Nov 8 12:21:59 omega dhcpd: DHCPACK on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:22:40 omega dhcpd: DHCPDISCOVER from 00:16:cf:4a:99:ce via eth0
Nov 8 12:22:40 omega dhcpd: DHCPOFFER on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:22:42 omega dhcpd: DHCPREQUEST for 192.168.0.7 (192.168.0.12) from 00:16:cf:4a:99:ce via eth0
Nov 8 12:22:42 omega dhcpd: DHCPACK on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:23:21 omega dhcpd: DHCPDISCOVER from 00:16:cf:4a:99:ce via eth0
Nov 8 12:23:21 omega dhcpd: DHCPOFFER on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:23:23 omega dhcpd: DHCPREQUEST for 192.168.0.7 (192.168.0.12) from 00:16:cf:4a:99:ce via eth0
Nov 8 12:23:23 omega dhcpd: DHCPACK on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:24:05 omega dhcpd: DHCPDISCOVER from 00:16:cf:4a:99:ce via eth0
Nov 8 12:24:05 omega dhcpd: DHCPOFFER on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:24:07 omega dhcpd: DHCPREQUEST for 192.168.0.7 (192.168.0.12) from 00:16:cf:4a:99:ce via eth0
Nov 8 12:24:07 omega dhcpd: DHCPACK on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:24:46 omega dhcpd: DHCPDISCOVER from 00:16:cf:4a:99:ce via eth0
Nov 8 12:24:46 omega dhcpd: DHCPOFFER on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Nov 8 12:24:48 omega dhcpd: DHCPREQUEST for 192.168.0.7 (192.168.0.12) from 00:16:cf:4a:99:ce via eth0
Nov 8 12:24:48 omega dhcpd: DHCPACK on 192.168.0.7 to 00:16:cf:4a:99:ce via eth0
Here is the xinetd log file: Actually, I have no xinetd file, but the tftp stuff from the main log is:
Nov 8 12:20:36 omega tftpd[25652]: tftpd: trying to get file: cm1.md5
Nov 8 12:20:36 omega tftpd[25652]: tftpd: serving file from /tftpboot
Nov 8 12:20:51 omega tftpd[25655]: tftpd: trying to get file: test
Nov 8 12:20:51 omega tftpd[25655]: tftpd: serving file from /tftpboot
Nov 8 12:21:20 omega tftpd[25658]: tftpd: trying to get file: cm1.md5
Nov 8 12:21:20 omega tftpd[25658]: tftpd: serving file from /tftpboot
Nov 8 12:22:00 omega tftpd[25665]: tftpd: trying to get file: cm1.md5
Nov 8 12:22:00 omega tftpd[25665]: tftpd: serving file from /tftpboot
Nov 8 12:22:43 omega tftpd[25669]: tftpd: trying to get file: cm1.md5
Nov 8 12:22:43 omega tftpd[25669]: tftpd: serving file from /tftpboot
Nov 8 12:23:24 omega tftpd[25673]: tftpd: trying to get file: cm1.md5
Nov 8 12:23:24 omega tftpd[25673]: tftpd: serving file from /tftpboot
Nov 8 12:24:08 omega tftpd[25677]: tftpd: trying to get file: cm1.md5
Nov 8 12:24:08 omega tftpd[25677]: tftpd: serving file from /tftpboot
Nov 8 12:24:49 omega tftpd[25681]: tftpd: trying to get file: cm1.md5
Nov 8 12:24:49 omega tftpd[25681]: tftpd: serving file from /tftpboot
Nov 8 12:25:31 omega tftpd[25720]: tftpd: trying to get file: cm1.md5
Nov 8 12:25:31 omega tftpd[25720]: tftpd: serving file from /tftpboot
Nov 8 12:26:14 omega tftpd[25740]: tftpd: trying to get file: cm1.md5
Nov 8 12:26:14 omega tftpd[25740]: tftpd: serving file from /tftpboot
Finally, I'm not sure how to get the cmts config. When I try to use `putcfg 192.168.0.12 cmts.config` I get:
SnmpMib start
1.3.6.1.2.1.1.4.0 OctetString "Eric Kowalewski" // syscontact.0
1.3.6.1.2.1.1.5.0 OctetString "TEST CMTS" // sysname.0
1.3.6.1.2.1.1.6.0 OctetString "Eric's Office" // syslocation.0
1.3.6.1.2.1.69.1.3.3.0 Integer 3 // docsdevswadminstatus.0
1.3.6.1.4.1.482.60.5.1.1.0 Integer 4 // lcprovisioningcontrol.0
1.3.6.1.4.1.482.60.5.1.2.0 IpAddress 192.168.0.100 // lcconfigipaddress.0
1.3.6.1.4.1.482.60.5.1.3.0 IpAddress 255.255.255.0 // lcconfigipsubnet.0
1.3.6.1.4.1.482.60.5.1.4.0 IpAddress 19
When I try to use `putmng 192.168.0.12 cmts.config2` I get:
Configuration data transfer initiated, wait...
Unexpected timeout waiting for tftp packet (2)!
Unexpected timeout on mib get!
Error in configuration data transfer!
[TEST CMTS] console> mib object lcconfigipgateway.0 192.168.0.12
[TEST CMTS] console>
Thanks,
emkowale
Hello,
Now I get the following from a `modem activity * all`:
[TEST CMTS] console> 11/08/07 17:36:38 00:16:cf:4a:99:ce DHCP REQUEST:
DA=ff:ff:ff:ff:ff:ff SA=00:16:cf:4a:99:ce
SRC IP=0.0.0.0 DST IP=255.255.255.255
yiaddr=0.0.0.0
11/08/07 17:36:38 00:16:cf:4a:99:ce DHCP ACK:
DA=00:16:cf:4a:99:ce SA=00:e0:29:9e:d0:02
SRC IP=192.168.0.12 DST IP=192.168.0.7
yiaddr=192.168.0.7
11/08/07 17:36:39 00:16:cf:4a:99:ce SID:2461, TFTP Read Request
11/08/07 17:36:39 00:16:cf:4a:99:ce Rcvd Reg Req; SID 2461
11/08/07 17:36:39 00:16:cf:4a:99:ce Reg Req
11/08/07 17:36:39 00:16:cf:4a:99:ce Authorizing..11/08/07 17:36:39 00:16:cf:4a:99:ce Invalid TLV Data!!; SID 2461
11/08/07 17:36:42 00:16:cf:4a:99:ce Rcvd Reg Req; SID 2461
11/08/07 17:36:42 00:16:cf:4a:99:ce Reg Req
11/08/07 17:36:42 00:16:cf:4a:99:ce Authorizing..11/08/07 17:36:42 00:16:cf:4a:99:ce Invalid TLV Data!!; SID 2461
11/08/07 17:36:44 00:16:cf:4a:99:ce Rcvd Rng Req-> Adj: nothing.
11/08/07 17:36:44 00:16:cf:4a:99:ce Sent Rng Resp: Success, SID 2461
11/08/07 17:36:45 00:16:cf:4a:99:ce Rcvd Reg Req; SID 2461
11/08/07 17:36:45 00:16:cf:4a:99:ce Reg Req
11/08/07 17:36:45 00:16:cf:4a:99:ce Authorizing..11/08/07 17:36:45 00:16:cf:4a:99:ce Invalid TLV Data!!; SID 2461
11/08/07 17:36:48 00:16:cf:4a:99:ce Rcvd Reg Req; SID 2461
11/08/07 17:36:48 00:16:cf:4a:99:ce Reg Req
11/08/07 17:36:48 00:16:cf:4a:99:ce Authorizing..11/08/07 17:36:48 00:16:cf:4a:99:ce Invalid TLV Data!!; SID 2461
11/08/07 17:36:51 00:16:cf:4a:99:ce Rcvd Reg Req; SID 2461
11/08/07 17:36:51 00:16:cf:4a:99:ce Reg Req
11/08/07 17:36:51 00:16:cf:4a:99:ce Authorizing..11/08/07 17:36:51 00:16:cf:4a:99:ce Invalid TLV Data!!; SID 2461
Thanks,
emkowale
if you have auth string in cable modem config file then you have to put same auth string in cmts config. here is a link for docs: http://rapidshare.com/files/68338526/1000.rar
Hello,
I understand the auth string stuff. Any ideas about the:
11/08/07 18:34:05 00:16:cf:4a:99:ce Authorizing..11/08/07 18:34:05 00:16:cf:4a:99:ce Invalid TLV Data!!; SID 1086
?
Thanks,
emkowale
sorry i don't know what that message could be. if you don't solve your problem i can send you by mail succesfully tested configuration of cmts, dhcpd and tftpd.
TLV is a type/length/value that's encoded in UCD messages. I recall seeing invalid TLV messages when docsis 2.0 capable modems would register on a CMTS running 1.1 code. The modems would register fine, but the CMTS always complained because it didn't recognize the 2.0 TLVs. It shouldn't be harmful.
first thing, i don't see auth string (mic) definition on your cmts. second, i believe it's easier to configure cmts via cli. i have some docs about arris 1000 so i can send them to you.
Hello,
I noticed that when I logged in it says:
Cornerstone CMTS 1500
Copyright 1997-2000 Arris Interactive
If you have docs on that it would be great! Also, do I really need an authentication string in a test environment? I do realize that it is a security thing in a production environment. I agree about the CLI configuring.
Thanks,
emkowale
I have a Cornerstone CMTS 1100, running 4.0.4 software. I have it partially configured, but I am having trouble with assigning IP scopes. The ip-level gives the commands for adding, but I keep getting an error. Here is the error:
[Reggiez_CMTS] ip-level# ?
Parameters settable at this level (use 'info' to display):
config-ip-address
config-ip-subnet
config-ip-gateway
default-ttl
dns-control
dns-domain-name
There is 'show' data available at this level
Next levels of tree available [show,info]:
[s ] route-list
[s,i] route-modify/
[s ] icmp
[s ] udp-stats
[s ] udp-entry-list
[s ] tcp-stats
[s ] tcp-connection-list
[s ] arp-list
[ i] arp-modify/ethernet/
[ i] arp-modify/cable/
[s,i] igmp-modify/ethernet
[s,i] igmp-modify/cable
[s ] multicast-list
[s,i] multicast-modify//ethernet
[s,i] multicast-modify//cable
[s ] scope-list
[ i] scope-modify/ethernet//
[ i] scope-modify/cable//
[s ] dns-list
[ i] dns-modify/
Type 'help' for command information
[Reggiez_CMTS] ip-level# scope-modify/cable/10.10.10.1/255.255.255.0
SNMP Error: Bad Value
[Reggiez_CMTS] scope-modify/cable/10.10.10.1/255.255.255.0# admin-state
Parameter Value
--------- -----
SNMP Error: No Such Name
[Reggiez_CMTS] scope-modify/cable/10.10.10.1/255.255.255.0#
any help would be appreciated on figuring out what I need to do to get this working. Thanks in advance.