Nexus FAQ & Troubleshooting
Feel Free to add you questions as comment to this section! Please dont forget to refer to IKE Vasileios Bouloukos (Unlicensed) and you will get your answer the soonest possible!
1. How can I create a user for Indeni in order to get remote access via ssh? How can I verify that the Indeni user has been successfully created?
Answer
The next command configures a user with the username indeni to the local database of the switch with network-admin access rights.
dc-admin role instead of the network-admin role should be defined. This new role provides Read-and-write access limited to a VDC.
You can confirm that the new user has been created and review the privilege access level with the next command.
Special attention should be taken when a remote server such as Radius or TACACS is used for Authenication, Authorization and Accounting (AAA). In this case the new Indeni user should be created to the remote server e.g. Radius and should be assigned with admin-role,
Are you still looking for more info? Then have a look to the next nexus indeni conluence link:
Still not clear? Write a comment with your question! An IKE is here to help you 
2. How can I check if the indeni has been connected via ssh successfully with the nexus switch?
The next command lists the users which are connected to the Nexus switch.
The indeni server with the IP address 10.10.8.116 has established a ssh session toward the Nexus switch (check figure below)
Finally, the next command illustrates the TCP state (e.g. ESTABLISHED) for the ssh session between the Nexus switch and the Indeni server
3. How can I check the CPU/Memory utilization on a Nexus series switch? How can I check that the Indeni didnt sharply increase the CPU/ Memory utilization of the device?
Answer
It has been noticed that low end devices with low hardware capabilities (CPU / RAM ) may appear high CPU / Memory utilization when are discovered by the Indeni. Currently the Nexus 3k, which is the lowest end switch from the Nexus family series swithces, has been noticed a high cpu/memory utilization during the discovery. The issue is already under investigation by Indeni (ssh hang issue). Finally, it has also been noticed that the Indeni demands more CPU/Memory resources during the interrogation.
Let's move to the NX-OS command which provide info for the CPU/Memory utilization of the Nexus switch.
- Use the provied below NX-OS command in order to display the CPU usage for the last 60 seconds, 60 minutes, and 72 hours. Be sure to check the average CPU usage (#) and the spikes (*). The command output provides graphical views of how busy the CPU has been till last 72h. You can see if the CPU has been constantly busy or if utilization has been spiking. This command is very useful if you want see quickly how the CPU ulization pattern has been modified when the Nexus switch has been discovered by Indeni. The CPU usage graph for the last 60 seconds, 60 minutes could provide a useful and fast CPU utilization report for review epsecially during the Indeni discovery phase.
NOTE:CPU utilization spikes caused by a known network event or activity are not usually problems. Even a spike close to 90% might be acceptable, depending on the cause. For example, an acceptable spike could be caused by the network administrator entering a specific command such as the " show tech support" command on the CLI.
Use this command in order to show the CPU usage sorted (from higher to lower) and at the process level:
Use this command in order to get CPU and Memory utilization report
Note: The show system resources command displays the overall memory utilization and the show process memory command displays memory utilization per process per VDC (VDC is the technology supported by the N7k series switch which permits the virtualization of the switch to several virtual switches)
4. Everything is fine and the Indeni server has established successfully a ssh session with the Nexus Switch. I checked the CPU/Memory utilization and everything is normal. However, I notice that the Indeni server didnt get any infomration from the nexus switch How can I be sure that the NX-OS commands included at the ind scripts are executed at the Indeni device?
Answer
You can easily keep track of the commands executed to a Nexus switch either by configuring to log all the commands to a Syslog server or by just searching the output of the show accounting log all command.. The simplest and fastest method is the last one.
In Release 5.x and later you can enable logging of "all" commands run on the device (not just the config commands) when you configure "terminal log-all" . Most of the Nexus deployments should have at least Nexus 5.x release which supports this command, otherwise you work with a real old NX-OS version, take care
It is noticed that the indeni server with the IP address 10.10.8.116 (left circle) execute the relevant NX-OS commands as highlighted on the right circle.
As soon as you complete the troubleshooting, dont forget to remove the command logging!
For testing purposes the show ver command is executed.
The show accounting log all command provides detailed information regarding the date, the user and the IP address of the user connected to the Nexus and run the show ver command.
5. 'Under "Nexus Simulations", a lot of the use cases were designed for the Nexus 9K series. Most of our customers/prospects so far deploy 5K and 7K predominantly. I love the use cases that are not model specific (configuration unchanged, vlan mismatch across vpc, BGP timers are too high, etc). I would like some use cases (5-10) that are either relevant to the 5K and 7K series or are generic enough to be applicable to multiple deployments."
Answer
Please, review the next link. It includes several scenarios and case studies demonstrating how the indeni can be your best friend for your Network and all Cisco Nexus Family!