APIC-EM and Meraki MX64

[aihassan1]

Hello,

I'm wondering if anyone has had any success using APIC-EM to configure say, a 3650 switch via a broadband modem and a Meraki MX64 appliance? Also, what is the correct syntax in creating a DHCP option 43 profile on the Meraki MX64 appliance dashboard?

Also, would I have any other roadblocks once I have the option 43 string entered correctly? I've gotten as far as running debugs and checking the 'show pnp trace' and noticing that option 43 cannot be detected. At this point, the switch tries to resolve to devicehelper.cisco.com.

I have APIC-EM working successfully on my other test beds but having issues when it comes to Meraki and broadband.

Appreciate the help on this.

[colo]

Are you using the APIC-EM user interface or the API? If you are working with the API, you may want to consider using the Dashboard API to directly talk to the Meraki Cloud. You can learn more at http://developers.meraki.com/api

[aihassan1]

We currently use the APIC-EM user interface. I'm interested in the API aspect and have reviewed the API documentation but looking to stand this up with using the Meraki dashboard. I've entered the DHCP option quite a few ways on the dashboard but unless I place a bootstrap configuration on the 3650, i'm unable to have the switch call out to APIC-EM and download its configuration.

option 43 ascii "5A1D;B2;K4;I11.224.x.x;J80"

From the 'show pnp trace' on the switch, i can see option 43 profile configured once the switch boots but then it reverts to http://devicehelper.cisco.com

[colo · Accepted solution]

For help on the option 43 syntax on the MX64, I would suggest contacting support@meraki.com. There could be some firmware update available or some syntax I don't know about. Also check the documentation website first:

https://documentation.meraki.com/MX-Z/DHCP/Setting_Custom_DHCP_Options

[aihassan1]

Appreciate the help on this.

We have successfully resolved this concern. I had a ticket open with Meraki but as always, tried to be proactive while waiting to hear back.

Tested a few steps in my lab and found that adding option 15 in tandem with option 43 now allows my switch/routers communicate with APIC-EM for true zero-touch capability via the MX64 appliance.

Option = Custom, code =15, type = Text, value = (enter site domain)

Option = Custom, code =43, type = Text, value = ascii=5A1D;B2;K4;I11.x.x.x.x;J80