APIC-EM - AP FlexConnectGroup 8.3 JSON Syntax

Trying to use the APIC-EM PNP feature to configure Access-points running 8.3 with the WLC-IP, Ap-MODE, AP-Group and FlexConnect-Group. can't find the JSON syntax for WLC 8.3 software (AP image 15.3(3)JD).

 The 8.2 syntax shows as follows:

 {"apGroup":"BldgA-local","primaryWlcIP":"10.10.80.5","primaryWlcName":"5508-1","secondaryWlcIP":"10.10.80.6","secondaryWlcName":"5508-2","tertiaryWlcIP":"10.10.10.7","tertiaryWlcName":"8500-1","apMode":" flexconnect"}

missing the FlexConnect Group setting added in 8.3.

 That would be apFlexGroupName

 Note: You also need to set the apMode as well.

 That should be all you need.

 And you need to remove the "apGroup" attribute.

{

     "primaryWlcIP":"10.10.80.5",

     "primaryWlcName":"BranchWLC-A",

     "secondaryWlcIP":"10.10.80.6",

     "secondaryWlcName":"BranchWLC-B",

     "tertiaryWlcIP":"10.10.10.7",

     "tertiaryWlcName":"BranchWLC-HA",

     "apMode":" flexconnect",

     "apGroup":"APGrp-BranchA",

     "apFlexGroupName":"FlexGrp-BranchA"

}

  You can have both.

• apGroup: sets RF characteristics (i.e. to cater for physical/environmental differences within a site)
• flexGroup is for having different security, DHCP, ACL and VLAN mappings for different sites that (for instance) all broadcast the same SSID.

• primary, secondary, tertiary WlcIP and WlcName
• apMode
• apGroup
• apFlexGroupName

 Are the ones that are documented.  There are 9 options in total.  You only need to specify a primate wlcIP and wlcName, no need to provide secondary and tertiary.

• Is this apFlexGroupName is accurate?  It does not appear to be taking that setting, but the other documented ones work.  Here is my sanitized config

 {

"primaryWlcIP": "1.1.1.1",

"primaryWlcName": "primary",

"secondaryWlcIP": "2.2.2.2",

"secondaryWlcName": "secondary",

"apMode": "flexconnect",

"apGroup": "APGroup",

"apFlexGroupName": "Flex-100"

}

This is what the AP's shipped with.  If 8.3 is the requirement then looks like I'm stuck setting the flexconnect groups manually after they join.  Also noticed that after the AP has been upgrade to 8.3 and the mode button is pressed to reset the config it ignores the PNP information because its not booted into a recovery image.  If you have an AP that has been previously upgrade to 8.3 without connecting to the console and manually booting to the AP using ap: boot flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-mx

how can you get the AP to accept the pnp config.  or is this the only way.

• There is a 8.3 recovery image on CCO.
•  ap3g2-rcvk9w8-tar.153-3.JD.tar
•  That is an 8.3 recovery image.

 Is there a way to automate the updating of the recovery image.  Needing the manually copy recovery image via console doesn't seem viable.

• just did this with a staging controller for 2802 APs, because they don't do PNP on their 8.2 code. DHCP option for staging controller, DNS for PNP. 

• first boot they join the staging controller, upgrade to 8.3, then I have a script run to clear config on the AP. Then they boot, PNP and get their real config.
• the flex group is harder, as the config clearing script would have to check that they were not in a flex group.  Totally doable.