| Attachment | Size |
|---|---|
 mta-DHCP.txt | 9.16 KB |
Is anyone else having issues with the Pico MiniCMTS?
We are having all sorts of problems with MTA's. We use only Arris eMTA's. Currently on Pico's latest software (v3.85/v352) and the eMTA no longer gets an IP address. They received an IP once at 11pm Saturday night, yet that went away sometime Sunday morning. Pico's support has been virtually non-existant on this. We use Promptlink's IPS for provisioning. The Arris CM's get an IP just fine and the CPE's receive IP's just fine, it is just the eMTA's that do not get IP addresses. Below is the log from Promptlink showing the DHCP offer is sent and attached is the Arris MTA DHCP log showing nothing received.
2016-04-20 00:00:23,153 DEBUG [IPS.DhcpService] - ReserveLeaseResponse received for device: 00:1D:D5:60:12:09
2016-04-20 00:00:23,154 DEBUG [IPS.dhcp] - OFFER sent: 162.210.244.235 to 00:1D:D5:60:12:09 (00:1D:D5:60:12:08) DeviceType: PacketCable
2016-04-20 00:00:23,178 DEBUG [IPS.dhcp] - DISCOVER received: 00:1D:D5:60:12:09
2016-04-20 00:00:23,178 DEBUG [IPS.dhcp] - OFFER sent: 162.210.244.235 to 00:1D:D5:60:12:09 (00:1D:D5:60:12:08) DeviceType: PacketCable
2016-04-20 00:00:23,203 DEBUG [IPS.dhcp] - DISCOVER received: 00:1D:D5:60:12:09
2016-04-20 00:00:23,203 DEBUG [IPS.dhcp] - OFFER sent: 162.210.244.235 to 00:1D:D5:60:12:09 (00:1D:D5:60:12:08) DeviceType: PacketCable
2016-04-20 00:00:23,228 DEBUG [IPS.dhcp] - DISCOVER received: 00:1D:D5:60:12:09
2016-04-20 00:00:23,228 DEBUG [IPS.dhcp] - OFFER sent: 162.210.244.235 to 00:1D:D5:60:12:09 (00:1D:D5:60:12:08) DeviceType: PacketCable
2016-04-20 00:00:23,253 DEBUG [IPS.dhcp] - DISCOVER received: 00:1D:D5:60:12:09
2016-04-20 00:00:23,253 DEBUG [IPS.dhcp] - OFFER sent: 162.210.244.235 to 00:1D:D5:60:12:09 (00:1D:D5:60:12:08) DeviceType: PacketCable
the loopback addresses, can the promptlink ping the mta gateway?
is the pico configured for packet cable?
Carl
The Promptlink servers can ping the MTA gateway. Pico actually has no extra configuration for packet cable, it is supposed to work out of the box.
my other thought would be service classes with priority of 7 for the mta, call agent can ping mta gateway?
How many customer on this system?
That shouldn't have any effect on the IP address. This seems to be an issue with the CMTS. But the call agent can ping the MTA gateway.
i don't have familiarity with PICO cmts'es but what your describing sounds like a different issue.
Arris mtas will ignore dhcp offers that come from ips that are not listed in option 122.1 in the cable modem dhcp offer.
So what I would check is that the ip (or the ip that is resolved if using dns) that you have specified as provisioning server I think it is option 122.1 is the IP that the MTA is receiving the offer from. If they are not the same, the Arris mta will silently ignore dhcp offers. (unless you are looking at debug input)
You can check both of these using the advanced web page and the password of the day.
Hi,
Arris MTAs require several dhcp options:
CM:
- option 122.1
- log server
MTA:
- option 122.3
- option 122.6
- hostname
This values are mostly used with all vendors.
BR