Hello
I've been working on setting up VOIP using ncs (packetcable) mta modems. I've been using Arris TM502G and Motorola SB5121 modems. So far, I've gotten the motorola to download the MTA config file, but I am having problems getting the Arris to ever request its MTA config.
Wireshark is showing a DNS query for SRV _kerberos._udp.BASIC.1 for the arris modem, but has never done this for motorola. From my understanding of provisioning flow, when using BASIC 1, once the DHCP ACK has been received, the modem should immediately skip to the step where the MTA config file is downloaded via TFTP. The TFTP request is never being sent by the Arris modem.
The relevant parts of my dhcp config file:
allow bootp;
#begin option 122 mta settings
option space docsis-mta;
option docsis-mta.dhcp-server-1 code 1 = ip-address;
option docsis-mta.dhcp-server-2 code 2 = ip-address;
option docsis-mta.provision-server code 3 = { integer 8, string };
#option docsis-mta.provision-server code 3 = { integer 8, ip-address };
option docsis-mta.as-req-as-rep-1 code 4 = { integer 32, integer 32, integer 32 };
option docsis-mta.as-req-as-rep-2 code 5 = { integer 32, integer 32, integer 32 };
option docsis-mta.krb-realm-name code 6 = string;
option docsis-mta.tgs-util code 7 = integer 8;
option docsis-mta.timer code 8 = integer 8;
option docsis-mta.ticket-ctrl-mask code 9 = integer 16;
option docsis-mta-pkt code 122 = encapsulate docsis-mta;
option docsis-mta.dhcp-server-1 192.168.40.2;
option docsis-mta.provision-server 0 "\003mta\007domains\003net\000";
#option docsis-mta.provision-server 1 192.168.40.3;
option docsis-mta.krb-realm-name "\005BASIC\0011\000";
option tftp-server-name "192.168.40.3";
#MTA Class
class "MTA"{
match if (substring(option vendor-class-identifier,0,4)="pktc");
spawn with hardware;
default-lease-time 21600;
max-lease-time 21600;
min-lease-time 10800;
option domain-name "domains.net";
ddns-updates off;
option domain-name-servers 192.168.40.2;
option subnet-mask 255.255.255.0;
option routers 192.168.40.1;
option log-servers 192.168.40.2;
option time-servers 192.168.11.250;
option tftp-server-name "192.168.40.3";
next-server 192.168.40.3;
use-host-decl-names-on;
option host-name = host-decl-name;
option docsis-mta.provision-server 0 "\003mta\007domains\003net\000";
option docsis-mta.krb-realm-name "\005BASIC\0011\000";
}
Also, from my Arris DHCP page:
Firmware Name TS040559A_042706_MODEL_4_5
Software filename SB5101-2.6.2.0-SCM00-NOSH-NNDMN.p7
Provisioning Method Full PacketCable
CM DHCP PARAMETERS
CM IP Addr 192.168.40.52 DHCP - CM IP Time Remaining
CM IP SubnetMask 255.255.255.0 Lease: 7.0 days (604693 seconds)
CM IP Gateway 192.168.40.1 Rebind: 6.1 days (529093 seconds)
CM TFTP Server 192.168.40.3 Renew: 3.5 days (302293 seconds)
CM Time Server 192.168.11.250
CM Time Offset -18000
CM Boot file arris.cfg
CM PACKETCABLE OPTIONS:
SubOption 1 Service Provider's Primary DHCP 192.168.40.2
SubOption 2 Service Provider's Secondary DHCP 0.0.0.0
MTA DHCP PARAMETERS
MTA FQDN mta0015a4517f22.domains.net DHCP - MTA IP Time Remaining
MTA IP Addr 192.168.40.101 Lease: 0.2 days (21580 seconds)
MTA IP SubnetMask 255.255.255.0 Rebind: 0.2 days (18880 seconds)
MTA IP Gateway 192.168.40.1 Renew: 0.1 days (10780 seconds)
MTA Boot file
MTA DHCP OPTION 6:
Service Provider Network Primary DNS 192.168.40.2
Service Provider Network Secondary DNS 0.0.0.0
MTA PACKETCABLE OPTIONS:
SubOption Type 122
SubOption 3 Service Provider's SNMP Entity mta.domains.net
SubOption 6 Kerberos Realm Realm (FQDN) BASIC.1
SubOption 7 Authorization method (MTA should get TGT) FALSE
SubOption 8 Provisioning timer (minutes) 10
SubOption 9 Security Ticket Invalidation 0
Any suggestions or help would be greatly appreciated.
Thanks,
Brandon
If the mta is not requesting the file it means it did not accept the dhcp offer from the server, this is a common problem, if you post a packet capture of the offer the server is giving out, for both the CM and the MTA (using wireshark) I can probably help you out. I don't have the information handy, but if you search the forums there is a post by me with step by step for troubleshooting via the telnet prompt at the modem too.
looking at your config can almost guarantee you that the problem is: you need to give the mta a fqdn, Non-SIP arris modems require a fqdn or they will not accept the offer. this can be done with these two lines in your config, in the mta class.
# makes the FQDN mta001122334455.mta.domains.net where 001122334455 is the mac of the mta.
option domain-name "mta.domains.net";
option host-name = concat ("mta",suffix (concat ("0", binary-to-ascii (16, 8, "", substring (hardware, 1, 1))),2), "", suffix (concat ("0", binary-to-ascii (16, 8, "", substring (hardware, 2, 1))),2), "",
suffix (concat ("0", binary-to-ascii (16, 8, "", substring (hardware, 3, 1))),2), "", suffix (concat ("0", binary-to-ascii (16, 8, "", substring (hardware, 4, 1))),2), "", suffix (concat ("0", binary-to-ascii (16, 8, "", substring (hardw
are, 5, 1))),2), "", suffix (concat ("0", binary-to-ascii (16, 8, "", substring (hardware, 6, 1))),2));
also TS040559A_042706_MODEL_4_5 is a very old firmware version should definitely call Arris to get a newer version.
Well, from browsing to the modem, it shows an FQDN of mta0015a4517f22.domains.net
This is the dhcp offer to the cm:
No. Time Source Destination Protocol Info
397 29.931309 192.168.40.2 255.255.255.255 DHCP DHCP Offer - Transaction ID 0x5c76374
Frame 397 (411 bytes on wire, 411 bytes captured)
Ethernet II, Src: Micro-St_df:33:d1 (00:0c:76:df:33:d1), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 192.168.40.2 (192.168.40.2), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol
Message type: Boot Reply (2)
Hardware type: Ethernet
Hardware address length: 6
Hops: 0
Transaction ID: 0x05c76374
Seconds elapsed: 0
Bootp flags: 0x8000 (Broadcast)
Client IP address: 0.0.0.0 (0.0.0.0)
Your (client) IP address: 192.168.40.52 (192.168.40.52)
Next server IP address: 192.168.40.3 (192.168.40.3)
Relay agent IP address: 0.0.0.0 (0.0.0.0)
Client MAC address: ArrisInt_51:7f:21 (00:15:a4:51:7f:21)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name: arris_test3.cfg
Magic cookie: (OK)
Option: (t=53,l=1) DHCP Message Type = DHCP Offer
Option: (53) DHCP Message Type
Length: 1
Value: 02
Option: (t=54,l=4) DHCP Server Identifier = 192.168.40.2
Option: (54) DHCP Server Identifier
Length: 4
Value: C0A82802
Option: (t=51,l=4) IP Address Lease Time = 7 days
Option: (51) IP Address Lease Time
Length: 4
Value: 00093A80
Option: (t=66,l=12) TFTP Server Name = "192.168.40.3"
Option: (66) TFTP Server Name
Length: 12
Value: 3139322E3136382E34302E33
Option: (t=67,l=15) Bootfile name = "arris_test3.cfg"
Option: (67) Bootfile name
Length: 15
Value: 61727269735F74657374332E636667
Option: (t=1,l=4) Subnet Mask = 255.255.255.0
Option: (1) Subnet Mask
Length: 4
Value: FFFFFF00
Option: (t=3,l=4) Router = 192.168.40.1
Option: (3) Router
Length: 4
Value: C0A82801
Option: (t=2,l=4) Time Offset = -5 hours
Option: (2) Time Offset
Length: 4
Value: FFFFB9B0
Option: (t=4,l=4) Time Server = 192.168.11.250
Option: (4) Time Server
Length: 4
Value: C0A80BFA
Option: (t=7,l=4) Log Server = 192.168.40.2
Option: (7) Log Server
Length: 4
Value: C0A82802
Option: (t=15,l=11) Domain Name = "domains.net"
Option: (15) Domain Name
Length: 11
Value: 646F6D61696E732E6E6574
Option: (t=122,l=37) CableLabs Client Configuration [TODO]CableLabs Client Configuration (37 bytes)
Option: (122) CableLabs Client Configuration [TODO]
Length: 37
Value: 0104C0A82802031200036D746107646F6D61696E73036E65...
Suboption 1: TSP's Primary DHCP Server: 192.168.40.2 (4 bytes)
Suboption 3: TSP's Provisioning Server: mta.domains.net (17 bytes)
Suboption 6: TSP's Kerberos Realm Name: BASIC.1 (9 bytes)
End Option
And this is the offer to the mta:
No. Time Source Destination Protocol Info
844 42.930728 192.168.40.2 192.168.40.101 DHCP DHCP Offer - Transaction ID 0xd34bf65
Frame 844 (391 bytes on wire, 391 bytes captured)
Ethernet II, Src: Micro-St_df:33:d1 (00:0c:76:df:33:d1), Dst: ArrisInt_51:7f:22 (00:15:a4:51:7f:22)
Internet Protocol, Src: 192.168.40.2 (192.168.40.2), Dst: 192.168.40.101 (192.168.40.101)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol
Message type: Boot Reply (2)
Hardware type: Ethernet
Hardware address length: 6
Hops: 0
Transaction ID: 0x0d34bf65
Seconds elapsed: 0
Bootp flags: 0x0000 (Unicast)
Client IP address: 0.0.0.0 (0.0.0.0)
Your (client) IP address: 192.168.40.101 (192.168.40.101)
Next server IP address: 192.168.40.3 (192.168.40.3)
Relay agent IP address: 0.0.0.0 (0.0.0.0)
Client MAC address: ArrisInt_51:7f:22 (00:15:a4:51:7f:22)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name: test3_mta.bin
Magic cookie: (OK)
Option: (t=53,l=1) DHCP Message Type = DHCP Offer
Option: (53) DHCP Message Type
Length: 1
Value: 02
Option: (t=54,l=4) DHCP Server Identifier = 192.168.40.2
Option: (54) DHCP Server Identifier
Length: 4
Value: C0A82802
Option: (t=51,l=4) IP Address Lease Time = 6 hours
Option: (51) IP Address Lease Time
Length: 4
Value: 00005460
Option: (t=12,l=15) Host Name = "mta0015a4517f22"
Option: (12) Host Name
Length: 15
Value: 6D7461303031356134353137663232
Option: (t=15,l=11) Domain Name = "domains.net"
Option: (15) Domain Name
Length: 11
Value: 646F6D61696E732E6E6574
Option: (t=1,l=4) Subnet Mask = 255.255.255.0
Option: (1) Subnet Mask
Length: 4
Value: FFFFFF00
Option: (t=3,l=4) Router = 192.168.40.1
Option: (3) Router
Length: 4
Value: C0A82801
Option: (t=6,l=4) Domain Name Server = 192.168.40.2
Option: (6) Domain Name Server
Length: 4
Value: C0A82802
Option: (t=7,l=4) Log Server = 192.168.40.2
Option: (7) Log Server
Length: 4
Value: C0A82802
Option: (t=122,l=37) CableLabs Client Configuration [TODO]CableLabs Client Configuration (37 bytes)
Option: (122) CableLabs Client Configuration [TODO]
Length: 37
Value: 0104C0A82802031200036D746107646F6D61696E73036E65...
Suboption 1: TSP's Primary DHCP Server: 192.168.40.2 (4 bytes)
Suboption 3: TSP's Provisioning Server: mta.domains.net (17 bytes)
Suboption 6: TSP's Kerberos Realm Name: BASIC.1 (9 bytes)
End Option
What it looks like to me, is that some reason the modem isn't taking the BASIC provisioning path. It's trying to find the hostname of the kerberos realm.
Thanks again,
Brandon
the arris mtas are very picky, if they do not like the offer they ignore it.
comparing your dhcp offer with mine you need to add
option tftp-server-name "192.168.40.3";
option bootfile-name "test3_mta.bin";
to your mta class to match what mine is offering
try that and lets see what you have, also is there any info in the logs?
here is the troubleshooting info to get the modem to tell you what is wrong
first you will need the password of the day here is the next 7 days worth
Date : Password of the Day
-----------------------------
10/11/10: F7P6US1KFH
10/12/10: MCXRQN9YVM
10/13/10: 3UI2YWE3PV
10/14/10: 9463VB9ZC3
10/15/10: MT16Z6XJGL
10/16/10: 20EIOWLZL1
10/17/10: LAUIP4FUR0
10/18/10: S6YRKPNMSE
access the web page at http://ip-of-cable-modem/
click on advanced
use the password of the day to log in
now type http://ip-of-cable-modem/techsupport.htm
here you can temporarily or permanently enable telnet and wan access to the modem
temporarily enable telnet access
telnet to the modems ip using the same password for telnet access
I would reccommend copying the password to the clipbord gonna have to use it several times
when in the telnet interface type in each command followed by enter key
cm
co
replevel 29
exit
quit
Log in again
mta
replevel 2
resetMTA
when the modem resets you will get a ton of dhcp debugging information that should help you narrow down the issue
typing help at the mta prompt will give you some other troubleshooting options like provmethod
if you are still having trouble post the output of the dhcp transaction here and I will help you as best as I can.
Here is the debugging information that comes in:
[ 4] MTA> resetMTA
resetMTA
PCMG: -->prov SNMPv3 key mgmt failed
PK DHCP: reset(): Stopping DHCP client
PK DHCP: reset(): reset message sent
PK DHCP: msgQWait(): received reset event
PK DHCP: task(): resetFlag set, going idle
PK DHCP: userAlarm(): sending event 2
PK DHCP: stateIdle(): Entering IDLE state, prevstate=0
PK DHCP: configureIpParams(): MTA IP address set to 0.0.0.0
00:05:15.89 55 PCMG CM_DB: MTA mac_addr = 0.15.a4.51.7f.22
00:05:15.89 55 PCMG CM_DB: MTA mac_addr = 0.15.a4.51.7f.22
PCMG: -->root Provisioning being tried (6) time
PK DHCP: start(): Starting DHCP client
PK DHCP: task(): State transition 0-1
PK DHCP: stateInit(): Entering INIT state, prevstate=0
PK DHCP: task(): State transition 1-2
00:05:15.89 55 MTA CM_DB: MTA mac_addr = 0.15.a4.51.7f.22
PK DHCP: reset(): Stopping DHCP client
PK DHCP: reset(): reset message sent
PK DHCP: msgQWait(): received reset event
PK DHCP: Unexpected msg 0 received while waiting for timer
PK DHCP: task(): resetFlag set, going idle
PK DHCP: userAlarm(): sending event 2
PK DHCP: stateIdle(): Entering IDLE state, prevstate=0
Return SPK DHCP: configureIpParams(): MTA IP address set to 0.0.0.0
0tatus: 0:05:15.90 550 PCMG CM_DB: MTA mac_addr = 0.15.a4.51.7f.22
00:05:15.90[ 55 PCMG CM_DB: MTA mac_addr = 0.15.a4.51.7f.22
PCMG: -->root Provisioning being tried (7) time
5PK DHCP: start(): Starting DHCP client
] PK DHCP: task(): State transition 0-1
MTAPK DHCP: stateInit(): Entering INIT state, prevstate=0
> PK DHCP: task(): State transition 1-2
PK DHCP: waitResponseRetry(): Attempt 0, timeout 600
PK DHCP: waitResponse(): Received response, verifying...
PK DHCP: processReplyMsg(): Verify phase done, acc=0 (Perfect)
PK DHCP: handleResponseDiscover(): Offer from primary server, retry=0
PK DHCP: handleResponseDiscover(): Offer perfect, requesting now
PK DHCP: waitResponse(): handler returned success, breaking out
PK DHCP: waitResponse(): selected response, acceptance=0 (Perfect), nextState=3
PK DHCP: waitResponseRetry(): pk_dhcp_waitResponse() returned 3, returning
PK DHCP: stateSelecting(): dhcpServerIdentifier 192.168.40.2
PK DHCP: stateSelecting(): MTA IP address 192.168.40.101
PK DHCP: stateSelecting(): dhcpIPaddrLeaseTime 21600
PK DHCP: task(): State transition 2-3
PK DHCP: stateRequesting(): Entering REQUESTING state, prevstate=2
PK DHCP: waitResponseRetry(): Attempt 0, timeout 800
resolvSend()
PK DHCP: waitResponse(): Received response, verifying...
PK DHCP: processReplyMsg(): Verify phase done, acc=0 (Perfect)
PK DHCP: handleResponseRequest(): received ACK
PK DHCP: waitResponse(): handler returned success, breaking out
PK DHCP: waitResponse(): selected response, acceptance=0 (Perfect), nextState=4
PK DHCP: waitResponseRetry(): pk_dhcp_waitResponse() returned 4, returning
PK DHCP: processReplyMsg(): Verify phase done, acc=0 (Perfect)
00:05:19.93 39 PDHT pk_mdb_MtaDevFQDN_set: sent message to PP Maintenance.
PK DHCP: processReplyMsg(): Commit phase done, acc=0 (Perfect)
PK DHCP: stateRequesting(): dhcpServerIdentifier 192.168.40.2
PK DHCP: stateRequesting(): MTA IP address 192.168.40.101
PK DHCP: stateRequesting(): dhcpIPaddrLeaseTime 21600
PK DHCP: stateRequesting(): dhcpT1value -1
PK DHCP: stateRequesting(): dhcpT2value -1
PK DHCP: stateRequesting(): IP address lease=21600, renew=10800, rebind=18900
PK DHCP: task(): State transition 3-4
PK DHCP: stateBound(): Entering BOUND state, prevstate=3
PK DHCP: configureIpParams(): MTA IP address set to 192.168.40.101
PK DHCP: stateBound(): Renew in 10799 seconds, Rebind in 18899 seconds
PK DHCP: userAlarm(): sending event 1
00:05:19.93 53 tCALLP Callp: MTA IP address restored/aquired
00:05:19.93 53 Securi pk_mdb_MtaDevSnmpEntity_get: mta.domains.net
00:05:19.93 53 Securi pk_mdb_MtaDevSnmpEntity_get: mta.domains.net
PCMG: -->prov SNMPv3 key mgmt failed
PK DHCP: reset(): Stopping DHCP client
PK DHCP: reset(): reset message sent
PK DHCP: msgQWait(): received reset event
PK DHCP: task(): resetFlag set, going idle
PK DHCP: userAlarm(): sending event 2
PK DHCP: stateIdle(): Entering IDLE state, prevstate=0
PK DHCP: configureIpParams(): MTA IP address set to 0.0.0.0
00:07:53.91 55 PCMG CM_DB: MTA mac_addr = 0.15.a4.51.7f.22
00:07:53.91 55 PCMG CM_DB: MTA mac_addr = 0.15.a4.51.7f.22
PCMG: -->root Provisioning being tried (9) time
PK DHCP: start(): Starting DHCP client
So, it looks as though it is still not following the BASIC.1 provisioning.
Mta Device Provisioning Method Indicator = fullPacketCable (1)
Is provmethod the same thing as provisioning flow type?
ya you probably don't want fullpacketcable provisioning,
you need to set the following snmp oid in your MODEM config file
I would recommend Gupi (4) but packetCableMinusKDC(2) or basic1(6) may also work depending on who your provider is
.1.3.6.1.4.1.4115.1.3.3.1.2.3.6.0 to integer 4
here is the description of the oid
ArrisMtaDevProvMethod
Indicates the method used to provision the device. This object should only be
changed by the configuration file. The following provisioning methods are supported:
docsisOnly(0) - DOCSIS-only provisioning
fullPacketCable(1) - PacketCable 1.5 Flows. See
arrisMtaDevPacketcableProvisioningFlow for which
flow we are using.
packetCableMinusKDC(2) - same as 'fullPacketCable', except with IPSEC and
SNMPv3 disabled
cps(3) - compatible with CPS2000 (SNMPv2; IPSEC disabled)
gupi(4) - SNMPv2, with no SNMP Informs and IPSEC disabled
singleMAC(5) - single config file (SNMPv2, single IP address,
single MAC address, no SNMP Informs, IPSEC disabled
basic1(6) - Basic1 SNMPv2, without the SNMP Enrollment, Status Informs
or Hash
basic2(7) - ARRIS Basic2 SNMPv2, without the SNMP Enrollment Inform or
Hash
gupiEncryptedMtaConfig(8) - Same as gupi(4) above with the MTA config file encrypted
using an Arris proprietary method.
gupiMacMta(9) - gupi provisioning that uses MTA MAC address as the MTA config
file name. (ie- 1337c0ded00d.bin)
gupiEncryptedMacMta(10) - gupi encrypted mta config provisioning that uses MTA MAC address
as the MTA config file name. (ie- 1337c0ded00d.bin)
gupiTftpSvrOverride(11) - gupi provisioning where the FQDN of the MTA TFTP server is expected to
be present in the MIB arrisMtaDevTFTPServerAddrOverrideFQDN
That definitely fixed the problem I was having. Now I'm at least getting the mta config file downloaded to the modem.
You wouldn't happen to know where I can find a good list or description of the arris mibs?
Thanks again for the help.
Brandon
Call up Arris get a support account not sure if money is involved or not, we got ours through the NCTC .
Arris has the best docs out of Cisco/Motorola/Arris not even close, and you can get access to PacketAce which has all the mibs and descriptions and is the best config editor imo. They also have decent phone support as well, they have helped resolve all my problems every time I called.
The mibs come with the firmware documentation members only download they have 3 guides available too a troubleshooting manual, provisioning manual and a management manual.