Would like to use the G0 mgmt interface of a ISR4000 series router to do PNP. Is there a way to define the vrf that pnp should use via option 43. Can set the vrf for PNP http server to Mgmt-intf on the cli. It would be great if this could be done via DHCP option 43 as well.
- That is something we are working on. In the meantime you can use a "bootstrap config" as a workaround.where 10.10.10.10 should be replaced by the IP address of your controller.
vrf forwarding Mgmt-vrf
ip address dhcp
ip http client source-interface GigabitEthernet0/0
pnp profile VRF-PROFILE
transport https ipv4 10.10.10.10 port 443 source GigabitEthernet0/0
Would like VRF support as well, since both the outside-facing interfaces will be in fvrfs. It looks like as soon as the router hits the 'vrf forwarding' command on the interface communication fails and the autoconfig is over
- you could also do the vrf configuration as a "Self-erasing EEM" script. This is a workaround for the moment. You would need to put that on the device out of band. You can use an iPhone PnP app (with console cable) or a USB stick. It is an initial piece of config that allow the device to talk to APIC. The EEM script is an alternative way of doing it inband.
==Now add EEM script commands to be executed /triggered after say 4 min ..==
event manager applet POST_PNP
event timer countdown time 240
action 1.0 cli command "enable"
action 1.1 cli command "config t"
action 1.2 cli command "interface GigabitEthernet1"
action 1.3 cli command "vrf fo mpls"
action 1.4 cli command "ip add x.x.x.x"
action 1.5 cli command "ip route vrf mpls 0 0 x.x.x.x"
action 1.7 cli command "exit"
action 1.8 cli command "no event manager applet POST_PNP"
action 1.9 cli command "end"
action 2.0 cli command "exit"
=== end of EEM script commands to set VRF forwarding on interface ==
"Bootstrap" is an alternative to option43/dns discovery. It is a small amount of config to bring up an interface, give it an IP address and config a route. You also include the IP address of the controller in this config. It contains no credentials or other sensitive information. Templates are deployed by the controller onto the device. they contain the full configuration for the device. There is a workflow where you can define a rule without a serial number.
An installer can use the smartphone PnP app, and get a list of "serial free" rules in a project. They can scan the serial number of the device they are installing, and use the PnP app (with a special serial cable) to download the bootstrap config onto the device. At the same time, the serial number is added to the rule on APIC-EM. The device can then be provisioned.
you can specify any address (corrected) interface as the source for the pnp profile.