Stacking Cisco Switches

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 4

Stacking Cisco Switches

Related topics
“About stacked switches” on page 74
“Tasks for stacking switches” on page 74
“Checking the switch IOS” on page 75
“Modifying the stacked switch configuration files” on page 76
“Configuring switch priority in a stacked switch” on page 77
9.4.1 About stacked switches
A stacked switch configuration allows two or more switches to be clustered in a way that they function
and
appear as one switch on the network. A true stacked switch configuration is different from connecting
switches
through the uplink ports to provide additional ports. The 3750 (X) switches qualified by Honeywell are
truly
stackable switches and act as one logical unit when connected through the backplane with the special
cable. Up
to nine 3750 (X) switches can be stacked. The following figure shows two separate switch configurations,
each
of which is comprised of three stacked switches. The first, third and fifth switches comprise the yellow
switch
and the second, fourth and sixth switches comprise the green switch.
Figure 23: Stacked Switches
9.4.2 Tasks for stacking switches
Switches can be stacked either by connecting a new switch to an existing switch, or by connecting two
new
switches and adding the stacked switch to the network. Following are the tasks associated with stacking
switches in an FTE network.
1. Power up and connect to the first base switch. See “Connecting locally to the switch” on page 99.
2. Verify the switches have the IOS version qualified by Honeywell as listed in the SCN for your release. If
the
version is not the same as that listed in the SCN, contact Honeywell Network Services for the procedure
to
upgrade the IOS.
9 INSTALLING AND REPLACING SWITCHES
74 www.honeywell.com
CAUTION
The first switch in the stack must have the correct Internal Operating System (IOS) and the switches added to
the stack must not have an IOS newer than the qualified version.
3. Configure the base switch. See “Configuring switch interface options” on page 100.
4. Load the switch configuration file on the base switch. See “Loading the switch configuration file” on
page 107.
5. Power up the next switch to be added to the stack (do not connect it at this time) and verify whether it
has
the correct IOS version. See “Checking the switch IOS” on page 75.
6. Power down the switch and then connect it to the stack. See the 3750-12s User Manual for connection
procedures.
CAUTION
Ensure that you verify whether the switch is powered off before connecting it to the stack. Connecting a
switch that is powered on causes other switches to reload and change their configuration.
7. Add the switch to the stack by typing the following commands at the switch prompt, substituting the
switch
number in the stack for X.
Conf t
Switch X provision ws-3750-12
For example:
• C3750-G1#Conf t
• C3750-G1#Switch 3 provision ws-3750g-12
Attention
Switch provisioning allows you to configure each switch in the stack with a separate configuration.
8. Edit the v101_stack.txt switch configuration file for the switch being added. See “Modifying the stacked
switch configuration files” on page 90.
9. Load the new switch configuration file to the stacked switch. See “Loading the switch configuration file”
on
page 107.
10. Repeat tasks 5 through 9 until all switches in the stack are added, making sure each new switch is
fully
loaded before adding the next one.
11. When all switches in the stack are fully loaded and ready, issue a show switch command to the base
switch.
For example: C3750-G1#show switch
Current switch
state
Role MAC address Priority
* 1 Ready Master 0015.faa3.8800 3
2 Ready Member 0015.faa3.bf00 2
3 Ready Member 0017.94b2.6800 1
All switches in the stack must indicate Ready status.
12. Configure the switch priority to increase the chances the base switch remains the master switch. See
“Configuring switch priority in a stacked switch” on page 77.
9.4.3 Checking the switch IOS
Cisco’s IOS version checking software detects the IOS version of each switch in the stack and updates all
switches to the latest version available, which may not be the version qualified by Honeywell. Switches
with an
unqualified IOS have unpredictable performance. Use this procedure to check the IOS version.
9 INSTALLING AND REPLACING SWITCHES
75
1. Use the Switch Configuration Tool’s Serial or Telnet connection to verify the switch’s IOS version. You
can
also install the Tera Term application from the Experion PKS Installation media on an Experion PKS
computer.
2. Enable and log in to the switch.
3. Check the IOS version by typing the following command at the switch prompt.
show boot
For example:
C3750-G1#show boot
BOOT path-list : flash:c3750-ipbase-mz.122-25.SEE2/c3750-ipbase-mz.122-25.S
The IOS version in the above example is 122-25.SEE2
4. For more information, refer to the IOS version qualified by Honeywell as listed on the Honeywell
Process
Solutions website (http://www.honeywellprocess.com/library/support/software-
downloads/Customer/FTEQualified-
IOS-Firmware-for-Cisco-Switches.pdf.
Tip
The IOS upgrade image is available from Honeywell TAC or Cisco.
• The IOS upgrade image must be the IP base with web services support.
• You must use the IOS upgrade image file with a .tar extension. Using the .bin file results in the switch not
spreading the new IOS to the other switches in the stack.
• Cisco 3850 switches use the XE IOS version of software, which only uses a *.bin installation in packaged
mode. Please see www.cisco.com for more details.
9.4.4 Modifying the stacked switch configuration files
Honeywell provides a default stacked switch configuration file (V101_stack) that can be modified to
configure
additional switches and options. See Section 9.7 for procedures on using switch configuration files. Use
this
procedure to modify the stacked switch configuration file and reuse it.
1. Copy the v101_stack.txt file to a location where you can edit it.
2. Rename the file according to the switch order in the stack.
For example, use v101_stack3.txt for the third switch in the stack.
3. Identify the switch order in the interface range command.
interface range GigabitEthernet2/0/1 – 12
For example, change the 2 following Gigabit Ethernet to a 3 to identify the third switch in the stack.
interface range GigabitEthernet3/0/1 – 12
Attention
You can also edit the 1 – 12 to a different range of ports to be configured as Gigabit.
4. Identify the VLAN to be used in the switchport access command.
switchport access vlan 101
For example, change 101 to 102
switchport access vlan 102
5. Save the file to a location from which you can access it using Tera Term’s Xmodem file transfer utility.
9 INSTALLING AND REPLACING SWITCHES
76 www.honeywell.com
Tip
The IOS upgrade image is available from Honeywell TAC or Cisco.
• The IOS upgrade image must be the IP base with web services support.
• You must use the IOS upgrade image file with a .tar extension. Using the .bin file results in the switch not
spreading the new IOS to the other switches in the stack.
9.4.5 Configuring switch priority in a stacked switch
Configuring the switch priority increases the chances of the base switch to remain the master switch.
Perform
the following procedure to establish specific priority for each switch in the stack.
1. Serial connect or telnet to the switch.
2. Enable and log in to the switch.
3. Type the Conf t at the switch prompt.
4. Type Switch X priority XX at the switch prompt, substituting the switch number for X and the priority
order
for XX.
Attention
The higher the number used for XX, the higher the priority.
In the following example, Switch 1, which is configured as the base switch, has the highest priority.
C3750-G1#Conf t
C3750-G1#Switch 1 priority 15
C3750-G1#Conf t
C3750-G1#Switch 2 priority 14
C3750-G1#Conf t
C3750-G1#Switch 3 priority 13
For additional information
• See Table 9-4 for a comprehensive list of all Honeywell’s switch configuration files.
• See Section 11.4 for additional examples of stacked switch configuration files.
9 INSTALLING AND REPLACING SWITCHES
77

9.5 Honeywell control firewall


The Honeywell control firewall provides security and determinism for level 1 FTE nodes. These switches
connect to uplink ports and only support level 1 nodes. For further details on planning, installation and
configuration of the Honeywell Control Firewall, refer to the Honeywell Control Firewall User’s Guide.
Related topics
“Honeywell control firewall connection requirements” on page 78
“Honeywell control firewall guidelines” on page 78
“Benefits of Honeywell control firewalls” on page 79
9.5.1 Honeywell control firewall connection requirements
The following are the connection requirements for a Honeywell control firewall
• All FIM4s and C300s must connect to a Honeywell control firewall.
• Any FTEBs to which a C300 communicates, must connect to the same Honeywell control firewall as the
C300.
• C200/FTEB and FIM/FTEB may connect to level 1 configured switches according to the established
best
practices or to a Honeywell control firewall.
• The Honeywell control firewall uplink port must always connect to a Level 2 switch port.
• The Honeywell control firewall must not be stacked.
• The Honeywell control firewall must be connected to an interface configured for portfast.

You might also like