A government agency client can reach NX-API on a Nexus switch, yet a show command returns no show output because the request uses the configuration message type. What should the request use instead?
Select an answer to reveal the explanation.
Short Explanation
NX-API is a service window with two wickets, one for looking and one for changing. You walked up to the change wicket with a show command, so nothing useful came back. Send the same command as a show request and the window can return the display output.
Full Explanation
NX-API accepts structured requests, in JSON or XML, and the message type tells the switch whether the body is a show command or a configuration command. A show command submitted as a configuration message is not processed as a display request, so the client does not get the show output it expected. Resending it with the show message type matches the command to the right handler. A second configuration message still describes a configuration operation. It does not become a show response just because the text inside looks like a show command. EEM is an on-box event tool. NX-API does not wait for a syslog applet before it will accept a request, and the feature is independent of any applet. The scheduler runs CLI on a clock. It is not the transport that returns a show command to a remote NX-API client. Caveat: the nxapi feature has to be enabled and the client must be allowed to reach it, or fixing the message type still produces a connection failure. Operational check: send one known show command with the show message type, confirm the reply contains that output, and confirm a configuration message is reserved for configuration changes.