A government agency NX-API client receives JSON replies for show commands, but configuration commands sent the same way do not change the switch. Those requests use the show message type. What must a configuration request use?
Select an answer to reveal the explanation.
Short Explanation
You keep handing the clerk a form that only asks for information and then wondering why nothing gets built. You send the change with the NX-API configuration message type, on the API that is already answering show commands. Renaming a field on the show request does not turn a lookup into a configuration.
Full Explanation
NX-API is enabled on this switch, which is why the agency already receives JSON show output. The message type tells the switch whether the payload is a show command or a configuration change. A show message type returns command output and does not enter configuration, so the VLAN or other change in that request is ignored. The configuration message type is what the same API expects when the payload should modify the switch. Wrapping the show message type in a different JSON field name leaves it a show request. The API will not treat that as configuration just because the command string inside looks like config. An EEM applet can run CLI when an event fires, and it is not a substitute for the configuration message type. NX-API is not limited to show commands. SPAN copies frames. It does not parse an API payload or apply configuration to the switch. Caveat: the account in the API call still needs a role that is allowed to configure, or the right message type can be rejected for authorization. Operational check: resend one small configuration with the configuration message type, confirm the JSON response reports success, and confirm the running configuration actually contains the change.