Re: Nexus 1010 CIMC interface and management 0: same or differen
The CIMC is the Cisco Integrated Management Controller. It is the GUI interface that allows you to upgrade the server itself, collect /view logs, check the status of components (CPU,memory,adapters & drives).
Here is a more detailed description I found. I hope this helps.
Cisco Integrated Management Controller (CIMC) is used for management/monitoring of C-Series Rack servers. CIMC provides options like WebGUI, CLI and IPMI for management/monitoring tasks. CIMC runs on a separate chip on the C-Series servers and thus is able to provide services in case of any major hardware failure or system crash. CIMC also does user management tasks and supports user access levels of Admin (Full access), User/Operator (can change host features but not CIMC) and Read Only (can only see information). CIMC uses IPMI to monitor thermal and voltage sensors in the servers. CIMC is useful for initial configuration of the server and troubleshooting any problems in server operation; however CIMC can not be used for tasks like deploying an OS, deploying software patches, install software applications and manage external storage on SAN or NAS.
Nexus 1010 CIMC interface and management 0: same or different
Regarding your point 1 and 2, they are correct
IP address of CIMC and management 0 are different. Hence in a HA pair, there would be three IP addresses in play
1. Primary CIMC IP address
2 Secondary CIMC IP address
3 Management0 IP address
Shared between Primary and Secondary, and held by whichever is Active
CIMC IP addresses are used to
1. Power on / off servers
2. Gain access to serial console of Nexus1010
(Usefull during installation, or when management connectivity is lost)
3. To handle split brain scenario
(Need to configure the CIMC IP address on the Nexus1010 using the following command
nexus1010-system remote-mgmt [primary/secondary] ip ipaddr username password )
Configuring CIMC IP address is not a must, but optional. Nexus1010 ships with accessories to connect the serial port to terminal server in the conventional way. If configured it has its usefullnes explained in above 3 bullets.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...