Hi,
I was able to get Arris eMTAa working on a test machine, but now I have some trouble when I am trying to get it to work on a production server. In the DHCPd log files I see that MTA sends DHCPDISCOVER and then DHCP server sends the DHCPOFFER back, but it never accepts it. I assume that there is something wrong with the sent data to the MTA, however it is strange that when I log in into Advanced menu and look at the MTA-DHCP logs, I see only BOOTREQUEST message type entries and no replies, but DHCP server sends out replies as I can see it. Is normal that such DHCP server's responses are ignored also in the MTA DHCP log if they don't contain enough information (option 122 etc.)?
The information is send out is as following:
CM host entry:
host nh1 {
hardware ethernet xx:xx:xx:xx:xx:xx;
vendor-option-space docsis-mta;
option host-name "cm1";
option docsis-mta.provision-server 0 "\003mta\007domains\003net\000";
option docsis-mta.krb-realm-name "\005BASIC\0011\000";
option domain-name "mta.domains.net";
ddns-updates off;
option subnet-mask subnetmask;
option docsis-mta.dhcp-server-1 ip;
filename "file.cfg";
option bootfile-name "file.cfg";
}
MTA host entry:
host nh2 {
hardware ethernet xx:xx:xx:xx:xx:xx;
option domain-name "mta.domains.net";
option host-name "cm1";
option docsis-mta.dhcp-server-1 IP;
option subnet-mask subnetmask;
option docsis-mta.provision-server 0 "\003mta\007domains\003net\000";
option docsis-mta.krb-realm-name "\005BASIC\0011\000";
filename "voip.cfg";
option bootfile-name "voip.cfg";
}
I am already setting the following data in the pool:
- for CM:
option routers IP;
max-lease-time 86400;
default-lease-time 86400;
option time-offset 3600;
server-identifier IP;
option tftp-server-name "IP";
next-server IP;
option time-servers IP;
option log-servers IP;
- for MTA:
option routers IP;
option subnet-mask subnetmask;
max-lease-time 86400;
default-lease-time 86400;
option time-offset 3600;
server-identifier IP;
option tftp-server-name "IP";
next-server IP;
option time-servers IP;
option log-servers IP;
option docsis-mta.provision-server 0 "\003mta\007domains\003net\000";
option docsis-mta.krb-realm-name "\005BASIC\0011\000";
option docsis-mta.dhcp-server-1 IP;
So the CM configuration file is successfully downloaded, but for the MTA part, not even the IP address is accepted.
TIA for any help possible, this is driving me nuts.
Update ...
I have just gone through the Wireshark log and I have all of the following options (and more) sent to both CM and MTA.
CM
DHCP 12 = Host
DHCP 15 = Domain
DHCP 1 = Subnet Mask
DHCP 3 = Router
DHCP 2 = time-offset
DHCP 6 = domain name server
DHCP 7 = Log server
DHCP 122 – suboptions 1 = Primary DHCP Server
DHCP 66 = TFTP Server
DHCP 67 = Bootfile
MTA
DHCP 12 = Host
DHCP 15 = Domain
DHCP 1 = Subnet Mask
DHCP 3 = Router
DHCP 2 = time-offset
DHCP 6 = domain name server
DHCP 7 = Log server
DHCP 122 – suboptions 3, 6
I have no more ideas what to do.
TIA
If the MTA ignores a request because it is missing required options it still logs it on the Advanced->DHCP->MTA DHCP LOGS page if DHCP Logging is turned on. (There is a disable/enable button next to the link for MTA-DHCP)
so, if logging is turned on, and no replies are showing up then the MTA is not receiving any replies. This usually indicates a communication problem between dhcpd and the cmts or dhcpd and/or the MTA. Possible reasons could be access-lists denying traffic for subnets MTA(s) are on, wrong subnet/gateway in dhcpd conf, or a true routing problem between CMTS ->Dhcpd server and/or MTA -> DHCPD server.
Thank you very much. This information was very much needed to know in which way to look for a solution.
One more question: I can successfully connect to the CM's web interface and to CMTS via telnet - both from the DHCP server. It doesn't work also if I put the MTA in the same pool as CM (and CM successully downloads the configuration file). Could this information be of any help when resolving the issue?
TIA
Without knowing your network topography hard to say, I would look at things like access-lists, iptables on the dhcpd server SELinux settings on DHCPd server, as well as making sure your subnet/network settings are right.
IF you are still having trouble, call up Arris, there is a CLI troubleshooting method to diagnose dhcp problems, and it will tell you if the response is malformed/ missing parameters etc.. very useful, but it is not something I could tell you how to do. you have to turn on specific registers? in the cli to enable the functionality. This is documented in the 560 page Troubleshooting guide in their downloads too, though I have not sat down and read it cover to cover.