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 contains the following sections:
You can add remote management to your redundant Cisco Nexus Cloud Services Platform startup configuration so that if one pair becomes unreachable, the other can automatically attempt to recover it.
If redundant Cisco Nexus Cloud Services Platforms cannot communicate with each other over the management and control interfaces, they can both become active simultaneously. This process is known as a split-brain conflict. A Cisco Nexus Cloud Services Platform cannot be rebooted from its peer switch using high availability.
If one Cisco Nexus Cloud Services Platform becomes unreachable, its peer becomes active if it is the standby. If you have configured remote management, the new active Cisco Nexus Cloud Services Platform can attempt to power cycle its unreachable peer switch through the mgmt0 port of its Cisco Integrated Management Controller (CIMC) interface if CIMC is reachable on the peer. The active Cisco Nexus Cloud Services Platform starts the reboot code immediately when the standby is lost. The standby Cisco Nexus Cloud Services Platform waits 60 seconds before starting the reboot code.
For more information about losing communication between redundant Cisco Nexus Cloud Services Platforms, see the Cisco Nexus 1000V High Availability and Redundancy Configuration Guide.
For more information about CIMC, see Cisco Integrated Management Controller.
You can set up remote management in the startup configuration to recover an unreachable Cisco Nexus Cloud Services Platform peer switch through the mgmt0 port of its CIMC software.
Use the following procedure to set up remote management for the primary and secondary Cisco Nexus Cloud Services Platform.
You have previously configured the CIMC when installing the Cisco Nexus Cloud Services Platform. For more information, see the Cisco Nexus Cloud Services Platform Hardware Installation Guide.
switch# configure terminal switch(config)# nexus-system remote-mgmt primary ip 172.23.181.132 username admin password password Note: User must ensure the login and password matches CIMC login credentials. switch(config)# nexus-system remote-mgmt secondary ip 172.23.180.184 username admin password password Note: User must ensure the login and password matches CIMC login credentials. switch(config)# show run !Command: show running-config !Time: Wed May 21 10:03:22 2014 version 5.2(1)SP1(7.1) hostname switch feature telnet no feature http-server username admin password 5 $1$5Ugkc3a7$VhMJcRReBuu0/3/oHftbU. role network-admin username admin keypair rsa banner motd #Cisco VSA # ip domain-lookup ip host switch 172.23.180.107 errdisable recovery cause failed-port-state snmp-server user admin network-admin auth md5 0xb64ad6879970f0e57600c443287a79f0 priv 0xb64ad6879970f0e57600c443287a79f0 localizedkey rmon event 1 log trap public description FATAL(1) owner PMON@FATAL rmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICAL rmon event 3 log trap public description ERROR(3) owner PMON@ERROR rmon event 4 log trap public description WARNING(4) owner PMON@WARNING rmon event 5 log trap public description INFORMATION(5) owner PMON@INFO vrf context management ip route 0.0.0.0/0 172.23.180.1 vlan 1,180,366 port-channel load-balance ethernet source-mac port-profile default max-ports 32 port-profile default port-binding static port-profile type vethernet N1K_Cloud_Default_Trunk switchport mode trunk no shutdown guid fd7b724c-03f0-4fc0-90a4-02b482918b3a max-ports 64 description Port Profile created for Nexus 1000V internal usage. Do not use. state enabled system storage-loss log time 30 system inter-sup-heartbeat time 15 interface Ethernet1 channel-group 1 mode active interface Ethernet2 interface Ethernet3 channel-group 1 mode active interface Ethernet4 interface Ethernet5 interface Ethernet6 interface PortChannel1 svs-domain control uplink Ethernet2 management uplink Ethernet2 virtual-service-blade VSM virtual-service-blade-type name VSM-1.3 interface control vlan 366 interface control uplink Ethernet4 interface management vlan 180 interface management uplink Ethernet2 interface packet vlan 366 interface packet uplink PortChannel1 ramsize 3072 crypto-offload 10000 disksize 3 numcpu 1 cookie 1315634022 no shutdown primary no shutdown secondary interface VsbEthernet1/1 interface VsbEthernet1/2 interface VsbEthernet1/3 virtual-service-blade vxgw virtual-service-blade-type name vx-gw-1.5 interface gw-uplink1 uplink Ethernet5 interface gw-uplink1 mode passthrough interface management vlan 180 interface management uplink Ethernet2 interface gw-uplink2 vlan 366 interface gw-uplink2 uplink Ethernet2 ramsize 2048 disksize 3 numcpu 3 cookie 628175011 no shutdown primary interface VsbEthernet2/1 interface VsbEthernet2/2 interface VsbEthernet2/3 interface mgmt0 ip address 172.23.180.107/24 interface control0 line console line vty boot kickstart bootflash:/nexus-1010-kickstart.5.2.1.SP1.7.1.bin boot system bootflash:/nexus-1010.5.2.1.SP1.7.1.bin boot kickstart bootflash:/nexus-1010-kickstart.5.2.1.SP1.7.1.bin boot system bootflash:/nexus-1010.5.2.1.SP1.7.1.bin svs-domain domain id 638 control vlan 366 management vlan 180 svs mode L2 switch-guid 19147832-15eb-47ca-a797-f1bd3b34f8ea switch#
This section provides the remote management release history.
Feature Name |
Releases |
Feature Information |
---|---|---|
Remote Management |
4.0(4)SP1(1) |
This feature was introduced. |