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.
Cisco NX-OS is a resilient operating system that is specifically designed for high availability at the network, system, and process level. For more information about high availability (HA) concepts and features for Cisco NX-OS devices, see the Cisco Nexus 7000 Series NX-OS High Availability and Redundancy Guide.
This chapter describes the Cisco Nexus 7000 Series NX-OS high availability commands.
To delete the boot variable log, use the clear bootvar log command.
|
|
This example shows how to delete the boot variable log:
switch#
clear bootvar log
|
|
---|---|
To delete core dump files of a virtual device context (VDC) from the logflash, use the clear cores command.
clear cores archive file file-name
Specifies all core dump files for a VDC from the logflash on the module. |
|
Specifies the file on the logflash that needs to be deleted. |
|
|
This example shows how to delete core dump files of a VDC from the logflash:
switch(
config)#
clear cores archive
switch(
config)#
|
|
---|---|
To delete the crossbar-related information, use the clear x-bar driver command.
clear xbar-driver [ xbar xbar-number | local xbar counter]
(Optional) Specifies the crossbar number. The range is from 1 to 5. |
|
(Optional) Specifies the crossbar slot number. The range is from 1 to 4. |
|
|
This example shows how to delete the crossbar-related information:
switch#
clear xbar-driver xbar 2 inst 1 counters port_num 1 all
switch#
|
|
---|---|
To enable internal CRC detection and isolation functionality, use the hardware fabric crc command in configuration mode. To disable this functionality, use the no form of the command.
hardware fabric crc [threshold threshold-count ]
Specifies the threshold count, taken over a 24-hour period, consecutively. The range is 1 to 100. |
|
|
The following example shows how to enable internal CRC error detection and isolation:
switch#
config terminal
switch(config)#
hardware fabric crc threshold 100
The following example shows how to disable internal CRC error detection and isolation:
switch#
config terminal
switch(config)#
no hardware fabric crc
|
|
---|---|
To power off a supervisor module in the Cisco NX-OS software, use the out-of-service command.
out-of-service module module-number
|
|
---|---|
This command is not supported on line card modules. For line card modules, use the poweroff command.
You can use the out-of-service command only in the default virtual device context (VDC).
Use this command to safely remove a module from service in the software. Before bringing a module back into service, you must remove the physical hardware module from the chassis and reinsert it.
This example shows how to take a supervisor module out of service:
|
|
---|---|
Shuts down a supervisor of a line card module in the Cisco NX-OS software. |
|
To power off a supervisor of a line card module in the Cisco NX-OS software, use the poweroff command.
poweroff { module module-number | xbar xbar-number }
|
|
---|---|
This example shows how to take a supervisor module out of service:
|
|
---|---|
To configure the power supply redundancy mode, use the power redundancy-mode command. To disable the power redundancy mode, use the no form of this command.
power redundancy-mode { combined | insrc-redundant | ps-redundant | redundant }
no power redundancy-mode { combined | insrc-redundant | ps-redundant | redundant }
|
|
---|---|
You can use the power redundancy-mode command only in the default virtual device context (VDC).
You can configure the power supplies with the following modes:
This example shows how to configure the power supply redundancy mode:
This example shows how to disable the power supply redundancy mode:
|
|
---|---|
To reload a module in the device, use the reload module command.
reload module slot [ force-dnld ]
|
|
---|---|
You can use the reload module command only in the default virtual device context (VDC).
To display information about the hardware on your device, use the show hardware command.
This example shows how to reload a module:
|
|
---|---|
Displays the fabric modules in the Cisco Nexus 7000 Series switch. |
To display the boot variables in the startup configuration, use the show boot command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
This example shows how to display the boot variables in the startup configuration:
switch#
show boot
Current Boot Variables:
sup-1
kickstart variable = bootflash:/n7000-s1-kickstart.4.1.5.gbin.S1
system variable = bootflash:/n7000-s1-dk9.4.1.5.gbin.S1
sup-2
kickstart variable = bootflash:/n7000-s1-kickstart.4.1.5.gbin.S1
system variable = bootflash:/n7000-s1-dk9.4.1.5.gbin.S1
No module boot variable set
Boot Variables on next reload:
sup-1
kickstart variable = bootflash:/n7000-s1-kickstart.4.1.5.gbin.S1
system variable = bootflash:/n7000-s1-dk9.4.1.5.gbin.S1
sup-2
kickstart variable = bootflash:/n7000-s1-kickstart.4.1.5.gbin.S1
system variable = bootflash:/n7000-s1-dk9.4.1.5.gbin.S1
No module boot variable set
switch(#
|
|
---|---|
Configures the boot variable for the Cisco NX-OS software kickstart image. |
|
Configures the boot variable for the Cisco NX-OS software system image. |
To display the system core dump files, use the show cores command.
Specifies all core dumps for a virtual device context (VDC). |
|
|
|
---|---|
This example shows how to display the recent system core dump file:
|
|
---|---|
To display the core filename, use the show system cores command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
To configure the system core filename, use the show system cores command.
This example shows how to display the core filename:
switch#
show system cores
Cores are transferred to slot0:
switch#
|
|
---|---|
To display the system redundancy status, use the show system redundancy command.
show system redundancy [ ha ] status
(Optional) Displays the virtual device context (VDC) redundancy (high availability) status. |
network-admin
network-operator
vdc-admin
vdc-operator
|
|
---|---|
This example shows how to display the system redundancy status:
This example shows how to display the VDC redundancy status:
|
|
---|---|
To display the status of the system standby manual boot feature, use the show system standby manual-boot command.
show system standby manual-boot
network-admin
network-operator
vdc-admin
vdc-operator
|
|
This example shows how to display the status of the system standby manual boot feature:
switch(config)#
show system standby manual-boot
system standby manual-boot option is disabled
switch(config)#
|
|
---|---|
To configure the destination for the core dumps on your system, use the system cores command. To revert to the default, use the no form of this command.
system cores {slot1:[path] | tftp:/server//[path/]}filename
no system cores {slot1:[path] | tftp:/server//[path/]}filename
network-admin
network-operator
vdc-admin
vdc-operator
|
|
This example shows how to configure the destination for the system core:
switch#
config t
switch(config)#
system cores slot1:core_file
switch(config)#
This example shows how to disable system core logging:
|
|
---|---|
To enable the Supervisor Reset High Availability (HA) policy, use the system hap-reset command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
You configure switchover and high availability (HA) policies for a virtual device context (VDC) when you create the VDC.
This example shows how to enable the Supervisor Reset HA policy:
switch(config)#
system hap-reset
switch(config)#
|
|
---|---|
Disables the heartbeat checks and reverts to the factory default. |
To enable heartbeat checks (default) and revert to the factory default, use the system heartbeat command. To disable heartbeat checks, use the no form of this command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
This example shows how to enable the heartbeat checks (default) and revert to the factory default:
This example shows how to disable the heartbeat checks:
|
|
---|---|
Disables the heartbeat checks (default) and reverts to the factory default. |
To disable the Supervisor Reset High Availability (HA) policy, use the system no hap-reset command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
You configure switchover and high availability (HA) policies for a VDC when you create the VDC.
This example shows how to disable the Supervisor Reset HA policy:
switch#
system no hap-reset
switch#
|
|
---|---|
To enable the system standby manual boot, use the system standby manual-boot command. To disable the system standby manual-boot option, use the no form of this command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
This example shows how to enable the system standby manual boot:
switch#
system standby manual-boot
system standby manual-boot option is enabled
switch#
|
|
---|---|
To switch over to the standby supervisor, use the system switchover command.
|
|
---|---|
This example shows how to switch over to the standby supervisor:
|
|
---|---|
To enable the watchdog feature, use the system no watchdog command. To disable the watchdog feature, use the no form of this command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
This example shows how to enable the watchdog feature:
This example shows how to disable the watchdog feature:
|
|
---|---|
Prevents the system from entering the Linux KGDB debugger on a watchdog failure. |