
5-18
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
OL-12247-04
Chapter 5 Managing Switch Stacks
Understanding Switch Stacks
•
“IP Routing and Switch Stacks” section on page 38-3
•
“IPv6 and Switch Stacks” section on page 39-9
•
“HSRP and Switch Stacks” section on page 40-5
•
“Multicast Routing and Switch Stacks” section on page 44-9
•
“Fallback Bridging and Switch Stacks” section on page 46-3
Switch Stack Management Connectivity
You manage the switch stack and the stack member interfaces through the stack master. You can use the
CLI, SNMP, Network Assistant, and CiscoWorks network management applications. You cannot manage
stack members on an individual switch basis.
These sections provide switch stack connectivity information:
•
Connectivity to the Switch Stack Through an IP Address, page 5-18
•
Connectivity to the Switch Stack Through an SSH Session, page 5-18
•
Connectivity to the Switch Stack Through Console Ports or Ethernet Management Ports, page 5-19
•
Connectivity to Specific Stack Members, page 5-19
Connectivity to the Switch Stack Through an IP Address
The switch stack is managed through a single IP address. The IP address is a system-level setting and is
not specific to the stack master or to any other stack member. You can still manage the stack through the
same IP address even if you remove the stack master or any other stack member from the stack, provided
there is IP connectivity.
Note
Stack members retain their IP addresses when you remove them from a switch stack. To avoid a conflict
by having two devices with the same IP address in your network, change the IP addresses of any switches
that you remove from the switch stack.
For related information about switch stack configurations, see the
“Switch Stack Configuration Files”
Connectivity to the Switch Stack Through an SSH Session
The Secure Shell (SSH) connectivity to the switch stack can be lost if a stack master running the
cryptographic software image and the IP base or IP services feature set fails and is replaced by a switch
that is running the noncryptographic image and the same feature set. We recommend that a switch
running the cryptographic software image and the IP base or IP services feature set be the stack master.
Encryption features are unavailable if the stack master is running the noncryptographic software image.