Cable Modem and MTA Code 122

[Daniel Dias Gonçalves]

Frank Bulk escreveu:
> You likely need to configure your CM configuration file to 'activate' the
> eMTA.
>
> Let's take this off-line as this is not directly related to this DHCP
> listserv.  
>
> FYI, there's the isp-cable listserv
> (http://isp-lists.isp-planet.com/isp-cable/) and two forums
> (http://www.cable-modems.org/forum/ and http://www.docsis.org/forum/2) that
> I can recommend as resources, too.
>
> Regards,
>
> Frank
>
> -----Original Message-----
> From: Daniel Dias Gonçalves [mailto:daniel at dgnetwork.com.br] 
> Sent: Monday, October 29, 2007 10:50 AM
> To: dhcp-users at isc.org
> Cc: frnkblk at iname.com
> Subject: Re: Cable Modem and MTA Code 122
>
> Frank Bulk escreveu:
>   
>> Daniel:
>>
>> There's a lot more you need to add.  Here's my config:
>>
>> option space cable-labs;
>> option cable-labs.tsp-primary-dhcp-server code 1 = ip-address;
>> option cable-labs.tsp-secondary-dhcp-server code 2 = ip-address;
>> option cable-labs.tsp-provisioning-server code 3 = { integer 8, string };
>> option cable-labs.tsp-as-backoff-retry code 4 = { unsigned integer 32,
>> unsigned integer 32, unsigned integer 32 };
>> option cable-labs.tsp-ap-backoff-retry code 5 = { unsigned integer 32,
>> unsigned integer 32, unsigned integer 32 };
>> option cable-labs.tsp-kerberos-realm-name code 6 = string;
>> option cable-labs.tsp-ticket-granting-server-utilization code 7 = boolean;
>> option cable-labs.tsp-provisioning-timer code 8 = unsigned integer 8;
>> option cable-labs-encapsulation code 122 = encapsulate cable-labs;
>>
>> and in my subnet definition:
>>
>>         option cable-labs.tsp-primary-dhcp-server 199.a.b.c;
>>         option cable-labs.tsp-secondary-dhcp-server 199.a.b.c;
>>         option cable-labs.tsp-kerberos-realm-name
>> 05:42:41:53:49:43:01:31:00;
>>         option cable-labs.tsp-provisioning-server 0
>> "\007charlie\006mtcnet\003net\000";
>>
>> The realm name, just in case your super-secret cereal box decoder doesn't
>> work, its BASIC.1.  Here's a website that helps encode the regular text,
>>     
> you
>   
>> just have to use the proper encoding (decompose the realm by its levels,
>>     
> in
>   
>> this case, "BASIC" and "1", and then prefix that section with string
>>     
> length,
>   
>> which is why you see '5' and '1', and then close it with a '0'.  For
>> example, secure.acme.net would be 06 73 65 63 75 72 65 04 61 63 6D 65 03
>>     
> 6E
>   
>> 65 74 00
>>
>> Regards,
>>
>> Frank
>>
>> -----Original Message-----
>> From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On
>>     
> Behalf
>   
>> Of Daniel Dias Gonçalves
>> Sent: Wednesday, October 24, 2007 8:00 AM
>> To: dhcp-users at isc.org
>> Subject: Cable Modem and MTA Code 122
>>
>> I use the Scientific Atlanta DPC2203 Cable modem with MTA . I tried to
>> use the following configuration and it didn't solve:
>>
>> Under your global options
>>  option voip122 code 122 = string;
>>
>> under your subnet options
>>  option voip122 01:04:0a:00:00:02;
>>
>> Somebody can help me?
>>
>> Thanks
>>
>> Daniel
>>
>>
>>
>>
>>
>>
>>
>>
>>     
> Thanks, but not work.
> The MTA Scientific Atlanta DPC2203 does'nt send the DISCOVERY for the
> DHCP, already the MTA Arris sends the DISCOVERY, the DHCP answers with
> the OFFER, but the process does not continue:
> Oct 29 13:47:01 server dhcpd: DHCPDISCOVER from 00:15:a2:19:dd:7e via
> 10.10.255.254
> Oct 29 13:47:01 server dhcpd: DHCPOFFER on 10.8.0.20 to
> 00:15:a2:19:dd:7e via 10.10.255.254
>
> * Both Cable Modem receives the IP and get the archive in the TFTP, but
> the MTA not.
>
> What to make to solve ?
>
> Thanks
>
> Daniel
>
>
>
>
>   
You said to check the configuration of the CM, but with the DHCP Network 
Registrar (Windows) it work correctly.
Is necessary use Kerberos-realm code 6 ?

Thanks,

Daniel