how to get NX-OS style CLI in ACI 1.3

[Bojan Zivancevic]

I just have set up ACI 1.3 system (APIC 1.3g and nexus 11.3 ACI software). It works fine, just a basic setup. I am totally new to ACI so please bare with me. I am trying to find my way through complicated maze of documents and I am constantly finding suggestions to use "NX-OS style configuration method" for certain tasks.

Now, when I connect to APIC/switches through ssh I am getting good old linux shell. Nothing similar to NX-OS.

Can someone explain to me how to get this? It's important for one other reason. I am using, and still want to use basic mode. Certain things cannot be configured in basic mode gui, only advanced mode is supported. This means I have to use CLI - and I don't see how.

Thanks a lot.

[dpita · Accepted solution]

Hello

Thanks for using supportForums. 

The NXOS style CLI is automatically available on the APICs only when you SSH as you said. While it may seem like linux, the default prompt is now [APIC-NAME]# and you can type config t and configure the switches and tenants in something similar to traditional NXOS

The switches do not run the NXOS-style CLI but something similar known as iNXOS which is linux based as you mentioned. Also, for your information, no configuration is done on the switches individually. 

As soon as you log into the APIC via SSH, the "?" should be available to take a look at the available commands. you should also be able to run something like "fabric <leaf-id> show lldp neighbors" that command will use the APIC to poll/interrogate the leaf for the desired command. There is also "config t" as i mentioned earlier to enter the actual configuration mode. In this mode everything available in the GUI can be done via a CLI command. 

hope that helps! what other questions do you have?

[Bojan Zivancevic]

Wow, what a mix. As soon as I typed "uname" and got the response, I stopped thinking about NX-OS. Never thought of that.

Yes it all works like you suggested, thanks. I feel a lot more comfortable now that I can check some things in CLI. :)

[Robert Burns]

When you SSH to the APIC you actually land in a shell where the NXOS CLI commands function.  It does look like a linux shell (and it is), but certain NXOS like commands have been added to help bridge the gap between our NXOS CLI interface and the ACI CLI interfaces.  You can find info on the NXOS CLI on APIC here:  http://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/1-x/cli/nx/cfg/b_APIC_NXOS_CLI_User_Guide/b_APIC_NXOS_CLI_User_Guide_chapter_010.html

Per the Basic UI, I'd personally suggest you try to become familiar with the Advanced (standard) UI if possible.  There are many more options to familiarize yourself with, but once you understand the policy model and the relationship between objects, it will all start to make sense as you create policies.  By using the Basic UI, the system hides some of the complexity by creating these "hidden" policies under the covers.  The problem with this is some of these basic-UI created policies can't be modified in the Advanced UI and can lead to complications/confusion down the road. 

Robert

[Bojan Zivancevic]

Thanks for the link and the explanation. As for the mode, I am aware of the problem you have mentioned - things created inside one mode cannot be edited in the other, and advanced mode is matched fully to the object model as well. But the problem lies in "there are many more options..." It is too much right now. Basic mode at least makes it possible for me to start using ACI, passing traffic through and all.

At least for me it is hard to grasp the model and the whole concept. I come from a networking world and this is totally different. For a simple NTP connection I have to make lots of clicks regarding policies and that sort of thing. I need a slow start. :)

Thanks.