Cisco Systems NME-16ES-1G manual Automatic Recovery of Cluster Configuration

Page 29

Cisco EtherSwitch Service Modules Feature Guide

Information About the Cisco EtherSwitch Service Modules

•Each standby-group member (Figure 7) must be connected to the cluster command switch through the same VLAN. In this example, the cluster command switch and standby cluster command switches are Cisco EtherSwitch service module cluster command switches. Each standby-group member must also be redundantly connected to each other through at least one VLAN in common with the switch cluster.

For more information about VLANs in switch clusters, see these sections:

–“Discovery of Candidates and Members Through Different VLANs” section on page 24

–“Discovery of Candidates and Members Through Different Management VLANs” section on page 24

Figure 7

 

 

VLAN Connectivity Between Standby-Group Members and Cluster Members

 

 

Command

Passive

 

Standby

 

 

 

device

command device

command device

 

 

 

 

VLANs 9,16

VLANs 9,16

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Management

VLAN 9

 

 

 

 

VLAN 16

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Management VLAN 9

VLAN 9

Management

 

VLAN 16

Member devices

VLAN 16

101326

Automatic Recovery of Cluster Configuration

The active cluster command switch continually forwards cluster configuration information (but not device configuration information) to the standby cluster command switch. This ensures that the standby cluster command switch can take over the cluster immediately after the active cluster command switch fails.

Automatic discovery has these limitations:

•This limitation applies only to clusters that have Cisco EtherSwitch service module command and standby cluster command switches: If the active cluster command switch and standby cluster command switch become disabled at the same time, the passive cluster command switch with the highest priority becomes the active cluster command switch. However, because it was a passive standby cluster command switch, the previous cluster command switch did not forward cluster configuration information to it. The active cluster command switch only forwards cluster configuration information to the standby cluster command switch. You must therefore rebuild the cluster.

•This limitation applies to all clusters: If the active cluster command switch fails and there are more than two switches in the cluster standby group, the new cluster command switch does not discover any Catalyst 1900, Catalyst 2820, and Catalyst 2916M XL cluster member switches. You must again add these cluster member switches to the cluster.

Cisco IOS Release 12.2(25)SEC

29

Page 28 Page 30
Image 29
Page 28 Page 30
Contents Release Modification GuideContents Hardware Overview Network Modules Hardware Installation GuideSoftware Features and Benefits Performance Features Ease-of-Use and Ease-of-Deployment FeaturesManagement Options Availability Features Manageability FeaturesVlan Features Security Features QoS and CoS Features Monitoring Features Power-over-Ethernet FeaturesCisco StackWise Concepts Overview of Switch StacksSwitch Stack Membership Stack Master Election and Re-Election Stack Member Numbers Switch Stack Bridge ID and Router MAC AddressStack Member Priority Values Stack Protocol Version Compatibility Switch Stack Software Compatibility RecommendationsSwitch Stack Configuration Files Switch Stack Management Connectivity Management Connectivity to Specific Stack Members Accessing the CLI of a Specific Stack MemberClustering Concepts Cluster Compatibility Command Device CharacteristicsStandby Command Device Characteristics Discovery of Candidates and Members Through CDP Hops Candidate and Member CharacteristicsAutomatic Discovery of Candidates and Members Vlan Discovery of Candidates and Members Through Different VLANs Discovery of Candidates and Members Through Routed Ports SwitchNew out-of-box Discovery of Newly Installed Switches in ClustersHsrp and Standby Cluster Command Switches Other Considerations for Cluster Standby Groups Virtual IP Addresses in ClustersAutomatic Recovery of Cluster Configuration Hostnames in Clusters IP Addresses in ClustersSwitch Clusters and Switch Stacks Passwords in ClustersSwitch Stack Switch Cluster Snmp Community Strings in ClustersSwitch Stack Switch Cluster TACACS+ and Radius in Clusters Availability of Switch-Specific Features in Switch ClustersCisco IOS Release 12.225SEC Using Interface Configuration Mode Boot flash image-name Command or Action PurposeExample Dir flashShow running configuration EnableConfigure terminal Service-module interface slot/port sessionOutput of the show service-module status command Show power inlineShow ip interface brief Control+shift+6Sample Output for the boot flash Command on the Router Sample Output for the dir flash Command on the RouterRouter boot flashc2800-adventerprisek9-mz ExamplesRouter# configure terminal Router# show running config interface gigabitethernet2/0Router# service-module gigabitethernet2/0 session Switch dir flashSwitch# ctrl+shift+6 Switch# show ip interface briefSwitch# show power inline Sample Output for Pressing Ctrl+Shift+6 Followed byDhcp Feature Default SettingSTP Prerequisites Clustering Concepts section on Return Sample Output for Assigning the IP Address and Subnet Mask Sample Output for Entering an Interface NameCommand or Action Purpose Sample Output for Saving the Configuration to NvramRouter# service-module gigabitethernet1/0 reload Router# service-module gigabitethernet1/0 shutdownRouter# service-module gigabitethernet1/0 reset Cisco IOS Release 12.225SEC Restrictions Default Switch Stack ConfigurationAssigning a Stack Member Number Sample Output for the reload slot Command Sample Output for the switch renumber CommandShow switch Switchconfig# switch 6 renumberSample Output for the show switch Command Setting the Stack Member Priority ValueSample Output for the switch priority Command Verifying Information About the Switch StackSwitchconfig# switch 2 priority Switch show switchSwitch# show platform stack-manager all Show switch stack-ports Switchconfig# show switch neighborsShow version Using the CLI to Manage Switch ClustersRcommand Sample Output for the show cluster members Command Sample Output for the rcommand and show version CommandsChoose View Refresh Choose Cluster Add to Cluster or Cluster member PasswordDetailed Steps from the CLI Creating a Cluster Standby GroupRouting-redundancy Cluster standby-group HSRP-group-nameNo switchport Sample Output for the ping tftpserver Command Sample Output for the copy tftp flash Command Sample Output for the show flash CommandSwitch# show flash Switch# copy tftp flashService-module interface slot/port password-reset Flashinit Recovering from a Corrupted Software Image Using XmodemPassword-reset Service-module interface slot/portFlashinit Control+6Router# copy flash xmodem TroubleshootingSample Output for the copy flash xmodem Command Router# copy tftp xmodem Sample Output for the copy tftp xmodem CommandRouter# service-module gigabitethernet2/0 password-reset Router# service-module gigabitethernet1/0 sessionRecovering from a Lost or Forgotten Password Optional loadhelper filesystem/file-url Enable secret password Boot -x -v deviceimagenameRename Copy flashReload Copy running-configuration startup-configurationOptional set Boot Service-module password-reset commandSet Sample Output for the set CommandExample Scenario Action Result Current-stack-member-number Renumber new-stack-member-number Network Configuration Examples Network Demands Suggested Design Methods Cost-Effective Wiring Closet Redundant Gigabit Backbone Cisco SoftPhone Software Gigabit servers POP Technical Assistance Related DocumentsRelated Topic Document Title Description Link
Top Page Image Contents