- Device Manager Help
- Configuring Cisco DCNM-SAN Server
- Configuring Authentication in Cisco DCNM-SAN
- Configuring Cisco DCNM-SAN Client
- Device Manager
- Configuring Performance Manager
- Configuring High Availability
- Configuring Trunking
- Configuring PortChannels
- Configuring N Port Virtualization
- Configuring Interfaces
- Configuration of Fibre Channel Interfaces
- Using the CFS Infrastructure
- Configuring SNMP
- Configuring Domain Parameters
- Configuring and Managing Zones
- Configuring FCoE
- Configuring Dense Wavelength Division Multiplexing
- Configuring and Managing VSANs
- Discovering SCSI Targets
- Configuring SAN Device Virtualization
- Configuring Fibre Channel Routing Services and Protocols
- Managing FLOGI, Name Server, FDMI, and RSCN Databases
- Configuring FICON
- Creating Dynamic VSANs
- Distributing Device Alias Services
- Configuring Advanced Fabric Features
- Configuring Users and Common Role
- Configuring Security Features on an External AAA Server
- Configuring Certificate Authorities and Digital Certificates
- Configuring FC-SP and DHCHAP
- Configuring Cisco TrustSec Fibre Channel Link Encryption
- Configuring FIPS
- Configuring IPv4 and IPv6 Access Control Lists
- Configuring IPsec Network Security
- Configuring Port Security
- Configuring Fabric Binding
- Configuring FCIP
- Configuring the SAN Extension Tuner
- Configuring iSCSI
- Configuring IP Services
- Configuring IP Storage
- Configuring IPv4 for Gigabit Ethernet Interfaces
- Configuring IPv6 for Gigabit Ethernet Interfaces
- Configuring SCSI Flow Services
- Configuring SCSI Flow Statistics
- Configuring Fibre Channel Write Acceleration
- Monitoring the Network
- Monitoring Performance
- Configuring Call Home
- Configuring System Message Logging
- Scheduling Maintenance Jobs
- Configuring RMON
- Configuring Fabric Configuration Server
- Monitoring Network Traffic Using SPAN
- Monitoring System Processes and Logs
- Configuring QoS
- Configuring Port Tracking
- Configuring FlexAttach Virtual pWWN
- Configuring Interface Buffers
- Verifying Ethernet Interfaces
Configuring High Availability
This chapter describes how to configure high availability, and describes the switchover processes.
About High Availability
Process restartability provides the high availability functionality in Cisco MDS 9000 Family switches. This process ensures that process-level failures do not cause system-level failures. It also restarts the failed processes automatically. This process is able to restore its state prior to the failure and continues executing from the failure point going forward.
An HA switchover has the following characteristics:
- It is stateful (nondisruptive) because control traffic is not impacted.
- It does not disrupt data traffic because the switching modules are not impacted.
- Switching modules are not reset.
Note Switchover is not allowed if auto-copy is in progress.
Switchover Processes
Switchovers occur by one of the following two processes:
- The active supervisor module fails and the standby supervisor module automatically takes over.
- You manually initiate a switchover from an active supervisor module to a standby supervisor module.
Once a switchover process has started another switchover process cannot be started on the same switch until a stable standby supervisor module is available.
This section includes the following topics:
Synchronizing Supervisor Modules
The running image is automatically synchronized in the standby supervisor module by the active supervisor module. The boot variables are synchronized during this process.
The standby supervisor module automatically synchronizes its image with the running image on the active supervisor module.
Note The image a supervisor module is booted up from cannot be deleted from bootflash. This is to ensure that the new standby supervisor module ia able to synchronize during the process.
Manual Switchover Guidelines
Be aware of the following guidelines when performing a manual switchover:
Manually Initiating a Switchover
To manually initiate a switchover from an active supervisor module to a standby supervisor module, use the active supervisor module using Device Manager system switchover command. After you enter this command, another switchover process cannot be started on the same switch until a stable standby supervisor module is available.
To ensure that an HA switchover is possible, enter the show system redundancy status command or the show module command. If the command output displays the HA standby state for the standby supervisor module, then the switchover is possible. See "Verifying Switchover Possibilities" for more information.
To perform a switchover using Device Manager, follow these steps:
Step 1 Ensure that an HA switchover is possible by selecting Physical > Modules to verify the presence of multiple modules.
You see the screen shown in Figure 7-1.
Figure 7-1 Modules Screen Shows Current Supervisor
Step 2 In the main Device Manager screen, select Admin > Reset Switch .
Figure 7-2 Reset Switch Dialog Box
Step 3 Click Switch to Standby .
Verifying Switchover Possibilities
This section describes how to verify the status of the switch and the modules before a manual switchover.
- Use the s how system redundancy status command to ensure that the system is ready to accept a switchover.
- Use the show module command to verify the status (and presence) of a module at any time. A sample output of the show module command follows:
The Status column in the output should display an OK status for switching modules and an active or HA-standby status for supervisor modules. If the status is either OK or active, you can continue with your configuration.
Copying Boot Variable Images to the Standby Supervisor Module
You can copy the boot variable images that are in the active supervisor module (but not in the standby supervisor module) to the standby supervisor module. Only those KICKSTART and SYSTEM boot variables that are set for the standby supervisor module can be copied. For module (line card) images, all boot variables are copied to the corresponding standby locations (bootflash: or slot0:) if not already present.
Enabling Automatic Copying of Boot Variables
To enable or disable automatic copying of boot variables, follow these steps:
Verifying the Copied Boot Variables
Use the show boot auto-copy command to verify the current state of the copied boot variables. This example output shows that automatic copying is enabled:
This example output shows that automatic copying is disabled:
Use the show boot auto-copy list command to verify what files are being copied. This example output displays the image being copied to the standby supervisor module's bootflash. Once this is successful, the next file will be image2.bin.
Note This command only displays files on the active supervisor module.
This example output displays a typical message when the auto-copy option is disabled or if no files are copied:
Displaying HA Status Information
Use the show system redundancy status command to view the HA status of the system. Tables 7-1 to 7-3 explain the possible output values for the redundancy, supervisor, and internal states.
The following conditions identify when automatic synchronization is possible:
- If the internal state of one supervisor module is Active with HA standby and the other supervisor module is HA standby, the switch is operationally HA and can do automatic synchronization.
- If the internal state of one of the supervisor modules is none, the switch cannot do automatic synchronization.
Table 7-1 lists the possible values for the redundancy states.
Table 7-2 lists the possible values for the supervisor module states.
Table 7-3 lists the possible values for the internal redundancy states.
The HA switchover mechanism in the standby supervisor module is enabled (see the “Synchronizing Supervisor Modules” section). |
|
The active supervisor module in the switch is ready to be configured. The standby supervisor module is in the HA-standby state. |
|
The switch is in the process of changing over to the HA switchover mechanism. |
|
The switch is intentionally shut down for debugging purposes. |
|
The standby supervisor module is in the process of synchronizing its state with the active supervisor modules. |
|
The active supervisor module and the second supervisor module is present but is not functioning. |
|
The switch is in a transient state. If it persists, call TAC. |