Poap Configuration Script; Guidelines And Limitations For Poap Configuration; Using Poweron Auto Provisioning - Cisco MDS 9000 Series Configuration Manual

Hide thumbs Also See for MDS 9000 Series:
Table of Contents

Advertisement

About Power On Auto Provisioning
DHCP information is used during the POAP process only when POAP fails via USB because of the
Note
following reasons:
• USB is not present.
• Script is not present or script is present with incorrect names.
• Script execution fails.

POAP Configuration Script

The reference script supplied by Cisco supports the following functionalities:
• Retrieves switch-specific identifiers, for example, the serial number.
• Downloads the software images (system and kickstart images) if the files do not already exist on the
switch.
• Installs the software image on the switch, which is then used at the next reboot.
• Schedules the downloaded configuration to be applied at the next switch reboot.
• Stores the configuration as startup configuration.

Guidelines and Limitations for POAP Configuration

The POAP configuration guidelines and limitations are as follows:
• Only FAT32 USB is supported. (The file system on the USB should be FAT32). For both Cisco MDS
9700 and 9500 series switches, POAP is supported only on USB 1 Port.
• The software image for the Cisco MDS 9000 Series Switches, including the Cisco MDS 9396S Multilayer
Fabric Switch, must support POAP.
POAP via USB is supported from Cisco MDS NX-OS Release 7.3(0)D1(1).
• POAP can be initiated on any switch by erasing the startup configuration and reloading the switch.
• POAP does not support provisioning of the switch after it has been configured and is operational. Only
auto provisioning of a switch with no startup configuration is supported.
• Important POAP updates are logged in the syslog and are available from the serial console.
• Critical POAP errors are logged to the bootflash. The filename format is
date-time_poap_PID_[init,1,2].log, where date-time is in the YYYYMMDD_hhmmss format and PID
is the process ID.
• Script logs are saved in the bootflash directory. The filename format is date-time_poap_PID_script.log,
where date-time is in the YYYYMMDD_hhmmss format and PID is the process ID.
• You can configure the format of the script log file. These formats are specified in the script. The template
of the script log file has a default format. However, you can choose a different format for the script
execution log file.
Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide
28

Using PowerOn Auto Provisioning

OL-29291-02

Advertisement

Table of Contents
loading

Table of Contents