SPA1x2 enhancement CDETS# CSCub70600 DHCP option 159 and 160

[sven]

Hello,

in one of the discussions here a Cisco rep says this "have opened enhancement CDETS# CSCub70600 to have 159 and 160 added to the SPA1xx ATA devices"

so my questión is simple, how can I track that? I want to know if 1.3.0 will have this?

thanks
Sven

[umbrualbert]

Hi Sven

Have you been able to track this issue, I'm still experiencing this in 1.3.1 and dont see the fix as part of the software release notes.

Is there any workaround or way we can track the existing enhancement that has been opened.

I'm also referencing this thread

https://supportforums.cisco.com/thread/2165731

Thanks

Albert

[sven]

HI Albert,

no, I'm afraid I am still at the same point.... initial spa122.cfg file I have to load with tftp and option 66... then there I put the line:

http://whatever-address/spa-$MA.cfg

to change to http.... but the initial cfg still by tftp which is giving me a headache as it doesn't work with NAT in between....

and I also didn't find a way to track this...

BR,

Sven

[Patrick Born]

Hi Sven & Community,

The enhancement CDETS#CSCub70600 was addressed and applied to firmware version 1.3.1(003) which is available on Cisco.com. Refer to the reference doc in my signature for a link to the firmware.

I've just downloaded 1.3.1(003) from Cisco.com and tested in my lab:

I configured my Open DHCP Server to offer OPTION 159 as follows:159="http://192.168.1.19"

[I don't run DNS in my lab, but if I set the OFFER to: 159="http://myProvisioningServer.fqdn" then the ATA performs a DNS lookup for the FQDN, once that's resolved, it'll send a TCP SYN to the provisioning server in an attempt to initiate the communications to request it's configuration file]

I factory reset my SPA122 and this is its DHCP REQUEST which includes 159 and 160 [click image for high quality version]:

Here's the resulting HTTP GET:

I use Wireshark to follow the TCP stream and here's the config file download:

Regards,

Patrick---

Use this reference document to locate SPA ATA resources

[sven]

Hi Patrick,

that's great news. I will give it a try soon.

now only we'll have to get the units from factory with 1.3.1 preinstalled ... becuase the one that we are getting from the wholesaler are still coming with 1.0.1 !

Do you know which version newly manufactered units get coming out of factory today?

thanks

Sven

[Dan Lukes]

Verified with option 160 and HTTPS provisioning server requiring client certificate from device.

Of course, it doesn't mean that TFTP server can be removed from our networks. As long as new devices will be delivered with an old firmware, the TFTP server is still required for initial provisioning.

Note that option 66 (TFTP) take precedence over options 159/160 so if the DHCP reply contain both, then TFTP configuration will be used.

[Patrick Born]

Dan,

Good point about the precedence. The factory default is: DHCP OPTION: 66,160,159,150 [click for larger image]

Regards,

Patrick---

[Dan Lukes]

I consider "generic option is prefered over vendor's specific option if both present" to be suboptimal decision for default configuration. Despite of it, I'm not calling for change. SPA1x2 class devices should have same behavior as SPA50x class devices as much as possible.

In advance, I can push our ISC-DHCP server not to send option 66 if (and only if) option 160 is requested by client. It's tricky way, somewhat. See configuration fragment bellow, if interested.

Thank you for your cooperation

Dan

1. option cisco-https-name code 160 = text;
2. ...
3. if option vendor-class-identifier ~= "CISCO SPA1[12]2" {
4.    option cisco-https-name "https://.../Cisco/Provisioning.php";
6.    if concat( ",", binary-to-ascii (10, 8, ",", option dhcp-parameter-request-list),",") ~= ",160," {
7.       supersede tftp-server-name "";
8.    } else {
9.       supersede tftp-server-name "tftp.???.cz";
10.    }
11. }

Notes:

[1] - definition of proprietary vendor's option 160;

[3] - condition true for DHCP requests received from SPA112 and SPA122 devices only

[4] - statement ignored by ISC-DHCP unless DHCP client asked for option 160 (e.g. pre-1.3.1 devices)

[5] - condition true if DHCP client asked for option 160 (e.g. 1.3.1 devices and newer)

[7] - such statement delete option tftp-server-name from DHCP reply

Message was edited by: Dan Lukes (ISC-DHCP configuration fragment added)

[Patrick Born]

Hi Sven,

Initially ATAs shipped with 1.0.x firmware. ATAs now ship with 1.2.x. I don't know how many 1.0.x ATAs are still in the channel.

I'm investigating when ATAs will start shipping with 1.3.x

Regards,

Patrick---