A logistics company developer runs Python on a jump host, not on the switch, and needs to add a VLAN over the network. Which approach matches that off-box script?
Select an answer to reveal the explanation.
Short Explanation
The script lives on a jump host, so it has to phone the switch. You call NX-API over HTTPS from that off-box Python, which is the fit for a VLAN change from the logistics host. The on-box cli module is not installed on the jump host.
Full Explanation
Off-box Python drives the switch from outside. NX-API is the HTTPS interface that accepts JSON or XML requests, including configuration, from a script running on a jump host. That is the match for a VLAN change that is not executing on the switch. The cli module exists inside the on-box Python interpreter. Importing that name on a laptop does not give the laptop a module that can configure the switch, because the module is not part of the jump host. POAP is a boot process the switch runs when startup configuration is missing. Starting something on the jump host does not turn the developer's script into POAP, and a VLAN change does not require wiping startup configuration. A SPAN session copies frames for analysis. It does not accept a VLAN configuration encoded by the operator. Caveat: NX-API has to be enabled on the switch, and the request has to use the configuration message type, or the HTTPS call connects and still does not add the VLAN. Operational check: from the jump host, send the VLAN request to NX-API and confirm the VLAN exists in the running configuration.