Last week I was giving my customer a presentation about Cisco UCS system and how it improves the Data center efficiency and management. That was part of a vBlock Presentation I was delivering to my customer.
So in a nutshell, Most of you know that we have 3 configuration options for UCS management :
- XML-API. (Acts as a process runs on top of the NXOS. This is the core component of UCS manager system so any CLI or GUI command will make XML API call to the UCSM subsystem)
In this post I will focus mainly on the different CLI shells and their use cases. So let us talk first about the hierarchy of UCSM CLI shells. It looks like this:
I will talk briefly now about each one of them.
- This is the default shell when you login to FI either Cluster IP, FI-A or FI-B.
- If you are an old fan of Cisco IOS so I am afraid to tell you that this shell is not IOS like
- It will help you to navigate through equipment with Up ,down, where and scope commands
- Commit changes also backup and import jobs
- Local and remote user authentication
- It will also help you create, modify or delete Service profile , templates and LAN or SAN policies
- More IOS like
- Allows you to reboot your FIs
- Erase FI full configuration.
- Copy files from any external source to FI volatile memory or workspace.
- Traceroue, Ping, ssh and telnet commands can be run from this shell.
- Used a lot for different show commands
- ntp configuration
- Ethanalyzer configuration.
- Worth mentioning that show running-configuration output will only return SAN and LAN configuration not the entire UCS/FI configuration
- Used mainly for troubleshooting issues related to CIMC
- View alarms, System event logs, Onboard failures and power controls.
- An alternative to IPMI protocol.
- Another alternative to IPMI.
- Richer command set.
- Server management, monitoring , set LED status and power control.
- Go deep to the level of mezzanine cards.
- For TAC use only!
- Debug at IOM/FEX level.
- For TAC use Only!
- There are some configuration commands available in this mode however, Cisco does not recommend running any of these commands in this mode.
For those of you who are using Cisco UCSP Emulator, Only 2 shells are available there. Local-mgmt and nxos shells. The other shells will return errors when trying to connect to them.
To connect to different shell options, You can type (connect ?) from Root shell to list all available options as shown below:
Let me If you have any questions. I will be more than happy to answer them.