The POAP process starts by assigning a temporary IP address to the switch via the DHCP protocol. Additional DHCP scope options are also provided to facilitate the configuration script download.

• Option 66 or Option 150: References the Script Server. IEEE Option 66 allows a single IP address or Server name. Cisco's Option 150 allows provision of a list of IP addresses for accessing the TFTP-Server
• Option 67: References the Configuration Script or Bootfile Name.

The Open NX-OS switch, acting as a DHCP client, will use this information to contact the TFTP server to obtain the configuration script file.

The configuration script (for example, poap.py) will be executed. The logic of the configuration script will download the software image, switch configuration, agent information and any other additional requirements from the network. POAP provides multiple mechanisms to flexibly identify switches, based on their serial number or system MAC address or their location in the network, as determined by its directly connected neighbors. The downloaded image and configuration is 'scheduled' to be applied after a reboot.

Below is a flowchart representing the POAP process:

POAP Process Flow Chart