The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to set up remote management in your startup configuration for use in recovering an unreachable Cisco Nexus 1010, and includes the following sections:
•Information About Remote Management
•Configuring Remote Management
•Feature History for Remote Management
You can add remote management to your redundant Cisco Nexus 1010 startup configuration so that in the event one of the pair becomes unreachable, the other can automatically attempt to recover it.
If redundant Cisco Nexus 1010s cannot communicate with each other over the management and control interfaces, they can both become active simultaneously. This is known as a split-brain conflict. A Cisco Nexus 1010 cannot be rebooted from its peer switch using high availability.
If one of the Cisco Nexus 1010s becomes unreachable, its peer becomes active if it was standby. If you have configured remote management, the newly-active Cisco Nexus 1010 can attempt to power cycle its unreachable peer switch through the mgmt0 port of its CIMC interface if CIMC is reachable on the peer. The active Cisco Nexus 1010 starts the reboot code immediately when the standby is lost. The standby Cisco Nexus 1010 waits 60 seconds before starting the reboot code.
For more information about loss of communication between redundant Cisco Nexus 1010s, see the Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.0(4)SV1(3).
For more information about CIMC, see the "Cisco Integrated Management Controller" section on page 1-3.
You can use this procedure to set up remote management in the startup configuration to be used in recovering an unreachable Cisco Nexus 1010 peer switch through the mgmt0 port of its CIMC software.
Before beginning this procedure, you must know or do the following:
•You previously configured the Cisco Integrated Management Controller (CIMC) when installing the Cisco Nexus 1010. For more information, see the Cisco Nexus 1010 Virtual Services Appliance Hardware Installation Guide.
•You have the following information for the Cisco Nexus 1010:
–CIMC management port IP address
–CIMC administrator login and password
•This procedure has steps for setting up remote management for both the primary and secondary Cisco Nexus 1010.
•You are logged in to the active Cisco Nexus 1010 in EXEC mode.
1. config t
2. nexus1010-system remote-mgmt primary ip ipaddr username username password password
3. nexus1010-system remote-mgmt secondary ip ipaddr username username password password
4. show running-config
5. copy running-config startup-config
For additional information related to implementing system-level HA features, see the following sections:
•RFCs
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
|
|
---|---|
No RFCs are supported by this feature |
— |
This section provides the remote management release history.
|
|
|
---|---|---|
remote management |
4.0(4)SP1(1) |
This feature was introduced. |