Hey everyone,
Im just about gone nuts, bugeyed and drive to smoke twice as much over Arris TM402 eMTA modems.
We have approximately 150 of these units which we're purchased refurbs, GREAT cable modme, no issues, the eMTA = STRAIGHT from Hell.
Got Packet Ace and Password of the Day util, our configuration is a BlonderTounge CMTS in the plant where these modems will sit, its working great with eMta enabled, we've tried posting config files (bin), assign via dhcpd.conf file on the OSS, EVERYTHING including from other posts on here modifying the dhcpd.conf with ranges for the eMta, etc., and had no luck, always says it emta Down, and it couldnt get the file. Naturally we have moved the bin files created and mta files (tried that format also) to the tftp directory, and no luck.
Can anyone PLEASE tell me how we can go about the following:
A) Configure the MTA for SIP
B) WHERE do we put the config files and what format exactly?
C) What modifications should I make to our DHCP Servers?
ANY Help is appreciated greatly appreciated!
First off these are questions best asked of Arris themselves, they have decent tech support and it is not often I can say that.
A) You need the SIP firmware you can get it by getting a hold of Arris
B)You need to add the following SNMP Mib setting to your cable modems config file
.1.3.6.1.4.1.4115.1.3.3.1.2.3.6.0 (aka arrisMtaDevProvMethod)
set it to 9 (aka gupiMacMta) which uses the mac address of the device as the MTA config file name i.e. 001122334455.bin
Then it will be set to download from your tftp server.
C) see the post about ten down for an example dhcpd.conf file too.
For works as the MTA download it config file :
PCMG: -->prov TFTP error in config file
PCMG: -->prov handling ACTION PK_MSM_TFTP_FAILED
PCMG: tftp failed
PK SNMP: pk_mdb_ifMtaOperStatus_set(2)
PKTC SNMP: pk_mdb_ifOperStatus_set(index=1,status=2)
PKTC SNMP INFORM : DNS Not supported. Can not query: [0.0.0.0].
----
PK TFTP: Downloaded 0013117b50bf.bin successfully. 628 bytes read
pk_tftp_varbind_parse(): 1.3.6.1.4.1.7432.1.1.1.6.0 --> 1
pk_tftp_content_parser_varbind(): TLV 11/64 must contain only PacketCable MIBs, not 1.3.6.1.4.1.7432.1.1.1.6.0
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.10.1.24.0 --> 7
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.7.0 --> 4.64.128.0
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.10.1.20.0 --> 16672
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.10.1.14.0 --> 11
Fitting param CfgMtaCountryTemplate, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.3.0 --> 55.55.46.55.51.46.52.48.46.49.54
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.4.0 --> 0
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.5.0 --> 55.55.46.55.51.46.52.48.46.49.54
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.6.0 --> 0
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.8.0 --> 80.67.77.65.59.80.67.77.85.59.71.55.50.57.59.116.101.108.10
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.9.0 --> 20
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.1.1.2.1 --> 50.48.51
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.1.1.3.1 --> 50.48.51
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.1.1.4.1 --> 50.48.51
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.1.1.5.1 --> 122.101.110
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.7432.2.1.2.1.1.18.9 --> 10
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.2.1.2.2.1.7.9 --> 1
Fitting param ifAdminStatus, group PerEndpointConfig
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.1.3.3.1.2.3.12.3.0 --> 4294967294
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.11.1.2.1 --> 71
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.11.1.3.1 --> 52.51.44.42.52.51
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.11.1.4.1 --> 1
Fitting param MIB-OBJECT, group Optional
pk_tftp_varbind_parse(): 1.3.6.1.4.1.4115.11.1.11.1.5.1 --> 0.0.0.3
Fitting param MIB-OBJECT, group Optional
pk_tftp_download(): pk_tftp_content_parser() returned 4
pk_tftp_download(): pk_tftp_registry_check() returned 3
pk_tftp_download(): error return 3 from pk_tftp_registry_check()
pk_tftp_download(): returning failure, code=3
PK TFTP: Set register cleared
PCMG: -->prov TFTP error in config file
PCMG: -->prov handling ACTION PK_MSM_TFTP_FAILED
PCMG: tftp failed
PK SNMP: pk_mdb_ifMtaOperStatus_set(2)
PKTC SNMP: pk_mdb_ifOperStatus_set(index=1,status=2)
PKTC SNMP INFORM : DNS Not supported. Can not query: [0.0.0.0].
TOD:getTimeFromServer using port: 1124
TOD: Time Servers list exhausted
Any ideas ?
Hi,
Thanks for your reply,
The problem here is, even though we have several other Arris pieces of hardware, they wont support these modems (500 purchased let me add in total) because they we're not bought direct or through a VAR they reconize. We bought the modems refurbished/used.
Our problems is we have access to nothing from Arris, even in packet cable mode I was unable to get these modems to configure or the MTA to even query a DHCP server, any other suggestions how this can be done, or any sources for the SIP firmware for these? (other than Arris)
The Oid I posted is how the Modem "turns on" the emta, I don't think it is unique to the SIP firmware. However it must be in the CABLE MODEMs config.
The Arris eMTAs are also extremely picky on fqdns each mta must have a fqdn or it will not work.
As far as getting support from ARRIS I would suggest buying a small quantity of legit modems from a recognized VAR to get the support, sure it will cost you a little bit of dough but the time it will save will be immense. I would suggest if you're in the US, use the cable COOP if your a member. We had only bought one box of modems (6) I think when we started working with them.
The eMTA setup is not simple and varies with different backends and equipment, without Arris's help I think you will have an extremely hard time. When we setup our first one it took the better part of a month to get things working appropriately.
Would you have sample files (bin, mta, conf) which ever is necessary to get the emtas enabled / programmed that I could trouble you for as a starting point?
Thank you again.
I will not be able to answer your questions below without knowing
the following:
- What type of provisioning server is being used?
- Does it support packetcable dhcp option 122?
- What DHCP options is currently setup for the CM & MTA?
- What version of software is on the MTA?
- Are the sip values in the CM config file to enable SIP?
- Are there separate IP scopes setup for CM & MTA?
The above questions are a good starting point.
Let me know,
Carlos
Hi Carlos,
Thank you for your reply.
Our provisioning server is a Fedora DHCP server (dhcpd.conf is main file) with a custom OSS software. Our TOD/SYSLOG/TFTP are also from Linux sources.
Apparently we're told we can use Option 122, though Ive used a sample dhcpd.conf file off this board and it did nothing for us.
We have no files in place as of now for the MTAs, though we used a template file found in another discussion. Including isolating a server and using the exact file in a mirrored server / cmts and did nothing.
The MTAs are using: 4.5.69C software.
Im not certain how to insert the values within the CM file to enable SIP, I knew this had to be done, but was unsure how to, is this done in packet ace?
Yes, the Cable Modems have 1 range of IPs, and the MTAs would have another range, though we would prefer to have them share a common group of IPs.
Thanks again for your reply.
It looks like the right questions are being asked.
Sniff all the traffic between the CM/eMTA and your network. That often yields very helpful information. You can't sniff just IPs, but also the DHCP requests (use the bootp.hw_addr filter in Wireshark to narrow it down to just the one CM/eMTA).
Frank
CableGuy613
You will need the ARRIS SIP software version on the device.
Looks like you have the factory default SW. Also the following
DHCP options are mandatory for the 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
Feel free to email me directly if you want to continue chatting.
carlos@ibbs.com