Format of array of ip-addresses

[Niall O'Reilly]

At Mon, 17 Nov 2014 17:30:36 +0000,
Verne Arase wrote:
> 
> I’m trying to provide our Cisco APs with controller addresses, and
> was attempting to send them data via
> 
>    option space LWAPP;
>    option LWAPP.controller code 241 = array of ip-addresses;
> 
>    class “LWAPP” {
>       match option vendor-class-identifier;
>       }
> 
> Then within subnets:
> 
>    subclass “LWAPP” “Cisco AP c3600” {
>       vendor-option-space LWAPP;
>       option LWAPP.controller 1.2.3.4, 5.6.7.8;
>       }
> 
> but this doesn’t seem to be working.

  A couple of things surprise me there.

  I would expect 'array of ip-address' without the final 'es';
  Placing a 'subclass' specification within a 'subnet' block is likely
  to lead to trouble.  Did you really mean, "within subnets"?

  Here below is what we did where I used to work until retiring at end
  August.  This is no longer live, as we migrated to a commercial DDI
  solution shortly before that, but did use to work!

    server-identifier bf-infra-2.ucd.ie;
    option space Cisco_LWAPP_AP;
    option Cisco_LWAPP_AP.server-address code 241 = array of ip-address;
    class "Cisco-CAPWAP-AP" {
      match option vendor-class-identifier;
      vendor-option-space Cisco_LWAPP_AP;
      option Cisco_LWAPP_AP.server-address 10.192.146.10;
      set cisco-capwap-ap-vci = "(not-available)"; }
    subclass "Cisco-CAPWAP-AP" "Cisco AP c1040" {set cisco-capwap-ap-vci = "Cisco AP c1040";}
    subclass "Cisco-CAPWAP-AP" "Cisco AP c1140" {set cisco-capwap-ap-vci = "Cisco AP c1140";}
    subclass "Cisco-CAPWAP-AP" "Cisco AP c1240" {set cisco-capwap-ap-vci = "Cisco AP c1240";}
    subclass "Cisco-CAPWAP-AP" "Cisco AP c1600" {set cisco-capwap-ap-vci = "Cisco AP c1600";}
    subclass "Cisco-CAPWAP-AP" "Cisco AP c2600" {set cisco-capwap-ap-vci = "Cisco AP c2600";}

  We actually had two servers in an active/passive configuration,
  sharing the single server-address mentioned.

  The actions specified in the 'subclass' specifications are not
  significant; they were intended for initial debugging, and were
  never removed.

> Anyone know what the binary format would be of the “option
> LWAPP.controller 1.2.3.4, 5.6.7.8;” ?

  I don't remember, but suspect that just using the binary format
  will not be sufficient to overcome the problem you're having.

  Best regards,
  Niall O'Reilly