Provisioning Server FQDN unknown to the DNS Server | docsis.org

You are here

Provisioning Server FQDN unknown to the DNS Server

12 posts / 0 new
Last post
tykee
Provisioning Server FQDN unknown to the DNS Server

I'm trying to connect new cablemodem ARRIS TM902S with telephony.

Internet works fine, but telephony stops at:
Telephony-DHCP Completed
Telephony-TFTP In Progress
Telephony-Reg with Call Server In Progress
Telephony-Reg Complete Line(s): Not Registered

in EVENT LOG shows:
eventid: 4000950203
description: Provisioning Server FQDN unknown to the DNS Server

I'm using the same config file, what i'm using it on ARRIS TM602B, TM601B, but they works great!

kwesibrunee
there are significant changes

there are significant changes between the Docsis 1.x and Docsis 3.0 Arris Phone modems, post your MTA config and I will see what I can do to help you, but your best bet is to read the docsis 3.0 manual or call Arris Tech Support.

mbowe
Sounds like something wrong

Sounds like something wrong in your option 122

Maybe have a look over these Arris MTA provisioning notes I wrote up a while ago :
http://www.docsis.org/comment/3063#comment-3063

windwaterwaves
FQDN

FQDN is fully qualified domain name. Probably the name you have configured in the modem for the provisioning server (server.cablecompany.com) is not resolving via the DNS (Domain Name Server) that is also being sent to the cable modem. Either server.cablecompany.com does not have an A record in the DSNS server, or it is not talking to the dns server. If you know the provisioning server name you are sending it to, and the dns server do this...

Provisioning Server name: server.cablecompany.com
DNS Server IP: 192.168.1.10

On the DNS server, start nslookup, set the server to query, and do a query, should return the correct address. There may also be a missing reverse record.
NSLookup
server 192.168.1.10
server.cablecompany.com
(should return an IP address)
Then take the IP address and type it in and it should return server.cablecompany.com

Hope that helps.

scramatte
same issue here

In my case the TM902S ask for FQDN domain for sub-option 122.3 but when I set it , the TM902 told me that string length is incorrect !

Gloochy
regarding FQDN:

2 things here:
1. FQDN must be a string not an IP (ie. alfa.test.org)
2. FQDN must be known and reachable from CMTS (I have used Linux's bind as DNS here)

I use above (regarding FQDN) and tm902s is working fine

hope it will help

regards
G.

MaXt0r
Hi Gloochy,

Hi Gloochy,

I have the same problem over here.

Provisioning Server FQDN unknown to the DNS server - mtab822.xxxx.com/10.42.0.10

Can you explain me how to fix it?

Br,

T

scramatte
We are running isc bind 9

We are running isc bind 9 and dhcp server 4.1, our CMTS is Arris C4-C
I've just made the change on the cmts to be able to resolve our domain from it. Tomorrow we will retry to provision tm902.

Gloochy, Are you using such kind on setup ? I mean external linux dns+dhcp ?

MaXt0r
Hi Scramatte,

Hi Scramatte,

My lab setup is:

Debian Squeeze + DHCP3 + TFTPD + BIND9
C4C + Arris TM722 & TM902

Im able to get SIP online with the TM722 modems.
TM902 HSD only. Sip doesn't work!

MTA log shows Provisioning Server FQDN unknown to the DNS Server

Can you tell me how to fix that?

BR,

Thomas

scramatte
We still have got the same

We still have got the same issue ... I can't help you yet :(

Gloochy
FQDN

Hi, sorry for delay but due to business trip I had no possibility to answer earlier.

My setup (Lab enviroment, provisioning based on Debian):
DNS: bind9,
DHCP server: isc dhcpd 4.1 (worked also with v.3.x),
Call Agent = asterisk 1.4 + NCS patch
CMTS = Arris C4

On C4 I have applied: configure ip name-server 10.10.10.200

where 10.10.10.200 is an IP address of my provisioning system, where I got: DHCP, DNS, TFTP, ToD & Call Agent

regarding opt-122 for MTA:
122.3 = beta.vlabs.org
122.6 = BASIC.1

beta.vlabs.org is translated by bind9 (DNS) to 10.10.10.200, so from CMTS I can ping both: 10.10.10.200 & beta.vlabs.org

Hope it will help
G.

scramatte
Hi, Sorry for delay replying

Hi, Sorry for delay replying ...

Can you post here your dhcpd.conf options ?
Do you have encoded your options 122.3 y 122.6 ? I mean something like "\005BASIC\0011\000" for 122.6 ...

Log in or register to post comments