Poap Dynamic Breakout; Script Execution Phase; Post-Installation Reload Phase; Guidelines And Limitations For Poap - Cisco Nexus 9000 Series Configuration Manual

Using PowerOn Auto Provisioning

POAP Dynamic Breakout

Beginning with Cisco NX-OS Release 7.0(3)I4(1), POAP dynamically breaks out ports in an effort to detect
a DHCP server behind one of the broken-out ports. Previously, the DHCP server used for POAP had to be
directly connected to a normal cable because breakout cables were not supported.
POAP determines which breakout map (for example, 10gx4, 50gx2, 25gx4, or 10gx2) will bring up the link
connected to the DHCP server. If breakout is not supported on any of the ports, POAP skips the dynamic
breakout process. After the breakout loop completes, POAP proceeds with the DHCP discovery phase as
normal.
For more information on dynamic breakout, see the interfaces configuration guide for your device.
Note

Script Execution Phase

After the device bootstraps itself using the information in the DHCP acknowledgement, the script file is
downloaded from the TFTP server.
The switch runs the configuration script, which downloads and installs the software image and downloads a
switch-specific configuration file.
However, the configuration file is not applied to the switch at this point, because the software image that
currently runs on the switch might not support all of the commands in the configuration file. After the switch
reboots, it begins running the new software image, if an image was installed. At that point, the configuration
is applied to the switch.
Note If the switch loses connectivity, the script stops, and the switch reloads its original software images and
bootup variables.

Post-Installation Reload Phase

The switch restarts and applies (replays) the configuration on the upgraded software image. Afterward, the
switch copies the running configuration to the startup configuration.

Guidelines and Limitations for POAP

POAP configuration guidelines and limitations are as follows:
• The switch software image must support POAP for this feature to function.
• POAP does not support provisioning of the switch after it has been configured and is operational. Only
• If you use POAP to bootstrap a Cisco Nexus device that is a part of a virtual port channel (vPC) pair
auto-provisioning of a switch with no startup configuration is supported.
using static port channels on the vPC links, the Cisco Nexus device activates all of its links when POAP
starts up. The dually connected device at the end of the vPC links might start sending some or all of its
Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide, Release 7.x
Guidelines and Limitations for POAP
33