Which two components are required for successful MDS USB POAP (Choose two.)

For USB-based POAP the switch ROMMON looks only at USB slot 1. It starts POAP when it finds a user-supplied script named poapscript (.pl or .py) in the root of that drive. Other files (images, configuration) can be pulled later by the script, and no special license or NTFS formatting is accepted, so only the presence of the USB stick in port 1 and the correctly-named script are mandatory for the POAP process to launch successfully.

A. Cisco MDS supports FAT/FAT32 on USB; NTFS is not recognized, so POAP will not start.
D. POAP runs in loader mode and does not require any feature license, including ENTERPRISEPKG.
E. Images may reside on USB or be downloaded over the network; they are not required for POAP to begin.

1. Cisco MDS 9000 Series NX-OS Fundamentals Configuration Guide, Rel. 9.3(1), “USB-Based POAP”, bullet 2 & 3 (USB slot 1; script must be named poapscript.[pl|py]).

2. Cisco MDS 9000 Series Troubleshooting Guide, Rel. 8.4, “Guidelines for POAP”, para 2 (FAT32 only; images optional—script can fetch them remotely).

3. Cisco Nexus 9000 NX-OS System Management Guide, Rel. 7.x, “PowerOn Auto-Provisioning Using USB”, Step 1b (USB must be inserted in port 1).