Table Of Contents
Release Notes for the Catalyst 2900 Series LRE XL Switches for Cisco IOS Release 12.0(5)WC6
Browser and Java Plug-In Requirements
Cluster Requirements and Guidelines
Catalyst 2900 XL and Catalyst 3500 XL Switches
Catalyst 1900 and Catalyst 2820 Switches
Minimum Cisco IOS Release for Major Features
New Software Features in this Release
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
Catalyst 2950G-24-EI-DC Service Requirement
Installing the Required Plug-In
Displaying the CMS Access Page
Upgrading the Switch IOS Software
Guidelines for Upgrading Switch Software
Overview of the Switch Upgrade Process
Determining the Switch Software Version
Which Software Files to Download from Cisco.com
Downloading the New Software and TFTP Server Application to Your Management Station
Copying the Current Startup Configuration from the Switch to a PC or Server
Using CMS to Upgrade One or More Switches
Recovering from an Incomplete CMS Software Upgrade
Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch
Configuring for an LRE Upgrade
Global Configuration of LRE Upgrades
Controller Configuration of LRE Upgrades
Obtaining Technical Assistance
Release Notes for the Catalyst 2900 Series LRE XL Switches for Cisco IOS Release 12.0(5)WC6
November 2002
Cisco IOS Release 12.0(5)WC6 runs on the Catalyst 2900 series LRE XL switches with 8-MB CPU DRAM.
Note
This release is only for Long-Reach Ethernet (LRE) switches. Do not install this release on Catalyst 3500 XL switches or on Catalyst 2900 XL switches that are not LRE switches. For information about those switches, refer to Cisco IOS Release 12.0(5)WC5.
These release notes include important information about this release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:
•
If you are installing a new switch, refer to the IOS release label on the rear panel of your switch.
•
If your switch is on and running, use the show version user EXEC command. See the "Determining the Switch Software Version" section.
•
If you are upgrading to a new release, refer to the software upgrade filename for the IOS version. Before upgrading your switch to this release, read the "Upgrading the Switch IOS Software" section.
You can download the switch software from these sites:
•
http://www.cisco.com/public/sw-center/sw-lan.shtml
(for registered Cisco.com users with a login password)•
http://www.cisco.com/public/sw-center/sw-lan.shtml
(for nonregistered Cisco.com users)This release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Contents
This document has these sections:
•
"Hardware Requirements" section
•
"Software Requirements" section
•
"Cluster Requirements and Guidelines" section
•
"Minimum Cisco IOS Release for Major Features" section
•
"New Software Features in this Release" section
•
"Limitations and Restrictions" section
•
"Documentation Notes" section
•
"Initial Switch Configuration" section
•
"Upgrading the Switch IOS Software" section
•
"Upgrading LRE Firmware" section
•
"Related Documentation" section
•
"Obtaining Documentation" section
•
"Obtaining Technical Assistance" section
Hardware Requirements
Note
Catalyst 3500 XL switches and Catalyst 2900 XL switches that are not LRE switches do not support this release. These switches can only be upgraded to Release 12.(5)WC5.
Note
This release is not for the Catalyst 2900 XL 4-MB switches. The 4-MB models are WS-C2908-XL, WS-C2916M-XL, WS-C2924C-XL, and WS-C2924-XL. These switches can only be upgraded up to Release 11.2(8.10)SA6. To be cluster members, these switches must run Release 11.2(8.x)SA6 original edition software. To determine the switch DRAM size, enter the show version user EXEC command.
This software release only supports the 16-MB Catalyst 2900 LRE XL switches (see Table 1). This release also supports the Cisco 575 and 585 LRE CPE (customer premises equipment) devices.
Table 1 Catalyst 2900 LRE XL Switches with 16-MB CPU DRAM
Switch DescriptionCatalyst 2912 LRE XL
4 10/100 ports and 12 LRE ports
Catalyst 2924 LRE XL
4 10/100 ports and 24 LRE ports
Software Requirements
This section describes the requirements for the system and for the Cluster Management Suite (CMS) software.
System Requirements
These operating systems are supported for CMS management:
•
Microsoft Windows 95 (Service Pack 1 required)
•
Microsoft Windows 98, second edition
•
Microsoft Windows NT 4.0 (Service Pack 3 or higher required)
•
Microsoft Windows 2000
•
Solaris 2.5.1 or higher, with the Sun-recommended patch cluster for that operating system and Motif library patch 103461-24
The minimum PC requirement is a Pentium processor running at 233 MHz with 64 MB of DRAM. The minimum UNIX workstation requirement is a Sun Ultra 1 running at 143 MHz with 64 MB of DRAM. Table 2 lists the recommended platforms for using CMS.
Table 2 Recommended Minimum Platform Configuration for Web-Based Management
OS Processor Speed DRAM Number of Colors Resolution Font SizeWindows NT 4.01
Pentium 300 MHz
128 MB
65,536
1024 x 768
Small
Solaris 2.5.1
SPARC 333 MHz
128 MB
Most colors for applications
-
Small (3)
1 Service Pack 3 or higher required
Browser and Java Plug-In Requirements
When starting a CMS session, the switch verifies the browser version to ensure that the browser is supported. If the browser is not supported, an error message appears, and the session does not start. Table 3 lists the browsers supported by CMS.
CMS requires the Java plug-ins described in the "Installing the Required Plug-In" section.
Table 3 Browser Requirements
Operating System Netscape Communicator1 Microsoft Internet ExplorerWindows 95
4.61, 4.7
5.0, or 5.5
Windows 98
-2
5.0, or 5.5
Windows NT 4.0
4.61, 4.7
5.0, or 5.5
Windows 2000
4.61, 4.7
5.0, or 5.5
Solaris 2.5.1 or higher
4.61, 4.7
-3
1 Netscape Communicator version 4.60 and 6.0 are not supported. (CSCdx34982)
2 CMS is not supported on machines running Windows 98 and Netscape Navigator. The workaround is to use Microsoft Internet Explorer if your operating system is Windows 98. (CSCdx4997)
3 Microsoft Internet Explorer is not supported on Solaris 2.5.1 or higher.
Note
If you receive an Internet Explorer error message that the page might not display correctly because your security settings prohibit the ActiveX controls, your security settings are set too high. To lower security settings, go to Tools > Internet Options, and select the Security tab. Select the indicated Zone, and move the Security Level for this Zone slider from High to Medium (the default).
To access CMS, follow the procedures in the "Initial Switch Configuration" section.
Cluster Requirements and Guidelines
This section describes the hardware and software requirements for clustering Catalyst desktop switches.
Catalyst 2900 XL and Catalyst 3500 XL Switches
Some versions of switch software do not support clustering, and other versions do not support some of the features in this release. To ensure that all cluster switches are using the same software level, we recommend that you upgrade all cluster switches to the software release that supports the features that you want.
If you have a cluster with switches that are running different versions of switch software, changes on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)XU or later.
Table 4 describes the Catalyst 2900 XL and Catalyst 3500 XL switches supported by this release and shows which switches can be command switches. All switches can function as standalone devices.
All Catalyst 2900 XL and Catalyst 3500 XL switches running Release 12.0(5.3)WC(1) and later are cluster-capable. All Catalyst 2900 XL modules are supported in cluster configurations.
We recommend that either the command switch has the latest software version installed if there switches in the cluster with older software versions or that all switches in the same platform be upgraded to the latest software version.
Note
We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, and Catalyst 3500 XL switches, either the Catalyst 2900 XL or Catalyst 3500 XL should be the command switch.
Table 4 Catalyst 2900 XL and Catalyst 3500 XL Switches as Cluster Members
Switch Release 12.0(5.3)WC(1) or higher? Command Capable? Member Capable?Catalyst 2900 XL (4 MB of DRAM)1
No
No
Yes
Catalyst 2900 XL (8 MB of DRAM)
Yes
Yes
Yes
Catalyst 2900 LRE XL (16 MB of DRAM)
Yes
Yes
Yes
Catalyst 3500 XL
Yes
Yes
Yes
1 These switches can act as cluster members if they are running Release 11.2(8.x)SA6 original edition software. They can interoperate with this software release, but they cannot be upgraded to it.
Catalyst 3550 Switches
Catalyst 3550 switches running Release 12.0(4)EA1 or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 3550 switches.
Note
We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has a Catalyst 3550 switch, that switch should be the command switch.
Catalyst 2950 Switches
Catalyst 2950 switches running Release 12.0(5)WC(1) or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 2950 switches.
Note
We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has Catalyst 2900 XL, Catalyst 2950, and Catalyst 3500 XL switches, the Catalyst 2950 should be the command switch.
Catalyst 1900 and Catalyst 2820 Switches
Table 5 lists the Catalyst 1900 and Catalyst 2820 switches and the minimum software release that they require to be cluster members. All Catalyst 2820 modules are supported in cluster configurations. For more information, refer to the documentation for the Catalyst 1900 and Catalyst 2820 switches.
Note
We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, and Catalyst 3500 XL switches, either the Catalyst 2900 XL or Catalyst 3500 XL should be the command switch.
Table 5 Catalyst 1900 and Catalyst 2820 Switches as Cluster Members
Switch Release 9.00 (-EN) Member Capable? Command Capable?Catalyst 1900
Yes
Yes
No
Catalyst 2820
Yes
Yes
No
Minimum Cisco IOS Release for Major Features
Table 6 lists the minimum software release required to support the major features of the Catalyst 2900 XL and Catalyst 3500 XL switches.
Table 6 Catalyst 2900 XL (including 2900 LRE XL) and Catalyst 3500 XL Features and the Minimum Cisco IOS Release Required
Feature Minimum Release RequiredEnhanced web-based switch management (CMS)
Release 12.0(5)WC3
MAC address notification
Release 12.0(5)WC3
Internet Group Management Protocol (IGMP) filtering
Release 12.0(5)WC3
Support for the Cisco 585 LRE CPE device
Release 12.0(5)WC4
Enhanced web-based switch management (CMS)
Release 12.0(5)WC4
MAC Address Notification
Release 12.0(5)WC4
Internet Group Management Protocol (IGMP) Filtering
Release 12.0(5)WC4
Port security MAC address aging
Release 12.0(5)WC5
Bridge protocol data unit (BPDU) guard
Release 12.0(5)WC5
Remote Authentication Dial-In User Service (RADIUS)
Release 12.0(5)WC5
UniDirectional Link Detection (UDLD) recovery
Release 12.0(5)WC5
Support for the Cisco Coarse Wave Division Multiplexing (CWDM) Gigabit Interface Converter (GBIC) modules
Release 12.0(5)WC5
WS-C2912-LRE XL and WS-C2912-LRE XL switches with LRE ports and support for the Cisco 575 LRE CPE device
Release 12.0(5.1)WC(1)
Rate selection
Release 12.0(5)WC6
LRE switch firmware upgrade capability for the switch local LRE controllers or connected CPE devices
Release 12.0(5)WC6
Interoperability with Catalyst 2950ST-24-LRE and Catalyst 2950ST-8-LRE switches
Release 12.0(5)WC6
Extended cluster member compatibility with the Catalyst 2950 and Catalyst 3550 switches
Release 12.0(5)WC(1)
Multicast VLAN Registration (MVR)
Release 12.0(5)WC(1)
Cross-stack UplinkFast
Release 12.0(5)XW
Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration
Release 12.0(5)XW
Support for the single-port 1000BASE-T GBIC module (WS-G5482)
Release 12.0(5)XW
WS-C3524-PWR XL switch with 10/100 inline-power ports
Release 12.0(5)XU
WS-C2924M-XL-EN-DC switch with DC power connector
Release 12.0(5)XU
WS-X2932-XL Catalyst 2900 XL 1-port 1000BASE-T module
Release 12.0(5)XU
Hot Standby Router Protocol (HSRP) for clustering
Release 12.0(5)XU
Extended discovery of cluster candidates up to 7 hops from the command switch
Release 12.0(5)XU
Support for up to 16 switches in a cluster
Release 12.0(5)XU
VLAN Trunking Protocol (VTP) pruning
Release 12.0(5)XU
Change management virtual LAN (VLAN) for a cluster
Release 12.0(5)XU
Private VLAN edge support
Release 12.0(5)XU
UDLD for detecting unidirectional links
Release 12.0(5)XU
Extended cluster member functionality for Catalyst 1900 and 2820 switches
Release 12.0(5)XP
Remote monitoring (RMON) support through the command-line interface (CLI) or Simple Network Management Protocol (SNMP)
Release 12.0(5)XP
Change management VLAN
Release 12.0(5)XP
Quality of service (QoS) based on IEEE 802.1P class of service (CoS) values
Release 12.0(5)XP
WS-C3548-XL switch with 48 10/100 ports
Release 12.0(5)XP
WS-X2931-XL Catalyst GigaStack GBIC module
Release 12.0(5)XP
Catalyst 3500 series XL switches (except WS-C3548-XL)
Release 11.2(8)SA6
Cluster management
Release 11.2(8)SA6
Terminal Access Control Access System Plus (TACACS+)
Release 11.2(8)SA6 (Enterprise Edition Software)
Network Time Protocol (NTP)
Release 11.2(8)SA6
Spanning Tree Protocol (STP) UplinkFast
Release 11.2(8)SA6
(Enterprise Edition Software)250 VLANs (some models: see the "Limitations and Restrictions" section)
Release 11.2(8)SA6
Catalyst 2900 series XL 1000BASE-X modules
Release 11.2(8)SA5
Catalyst 2900 series XL asynchronous transmission mode (ATM) modules
Release 11.2(8)SA5
IEEE 802.1Q trunking
Release 11.2(8)SA5
(Enterprise Edition Software)Inter-Switch Link (ISL) trunking
Release 11.2(8)SA4
(Enterprise Edition Software)VLAN Membership Policy Server (VMPS)
Release 11.2(8)SA4 (Enterprise Edition Software)
8192 media access control (MAC) addresses on modular switches
Release 11.2(8)SA4
Switch Network View stack management
Release 11.2(8)SA3
Web-based switch management
Release 11.2(8)SA
Fast EtherChannel port groups
Release 11.2(8)SA
New Software Features in this Release
Cisco IOS Release 12.0(5)WC6 contains these new features or enhancements:
•
The config-lre-sequence global configuration command to create new sequences or to add or to delete profiles in a user-defined sequence.
•
The config-lre-controller global configuration command for all upgrade related commands.
•
CMS support for the rate selection and LRE upgrade features.
Limitations and Restrictions
You should review this section before you begin working with the switches. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
•
A configuration conflict occurs if a switch cluster has Catalyst 2900 LRE XL switches using both private and public profiles. If one LRE switch in a cluster is assigned a public profile, all LRE switches in that cluster must have that same public profile. Before you add an LRE switch to a cluster, make sure that you assign it the same public profile used by other LRE switches in the cluster.
•
Catalyst 2900 LRE XL switches support 250 VLANs and 64 spanning-tree instances.
•
If a port group is set up between the LRE port of a Catalyst 2900 LRE XL switch and the Fast EtherChannel (FEC) ports of another switch through the LRE CPE devices, and the LRE link on an LRE port drops, the LRE switch no longer uses the LRE port for data transmission. However, the other switch might continue sending data through the FEC port. The packets being sent to the LRE port of the LRE switch are lost.
Data transmission continues normally if the LRE link is restored. (CSCdt22573)
•
You cannot configure a connected Cisco 585 LRE CPE device. You cannot monitor a Cisco 585 LRE CPE device from the switch LEDs or from CMS. Use the cluster setup privileged EXEC command to monitor a Cisco 585 LRE CPE device. You can still monitor a Cisco 575 LRE CPE device from the switch LEDs, from the CLI, and from CMS.
•
When packets from multiple VLANS that have the same source MAC address are received on different Ethernet ports of a Cisco 585 LRE CPE device, the LRE CPE creates a single ingress port entry in the packets. The packets are not correctly switched back to the VLANs if the network was designed with the assumption that MAC address and ingress port entries are maintained for each specific VLAN.
There is no workaround. This is a limitation of the Cisco 585 LRE CPE. (CSCdx03708)
•
Incoming Inter-Switch Link (ISL) frames are discarded by Cisco LRE CPE devices. ISL frames are not supported on the Cisco LRE CPE devices.
There is no workaround. (CSCdx25940)
•
You can connect the switch to a PC by using the switch console port and the supplied rollover cable and the DB-9 adapter. You need to provide a RJ-45-to-DB-25 female DTE adapter if you want to connect the switch console port to a terminal. You can order a kit (part number ACS-DSBUASYN=) with this RJ-45-to-DB-25 female DTE adapter from Cisco.
•
Certain combinations of port features create configuration conflicts. Refer to the "Avoiding Configuration Conflicts" section in the "Troubleshooting" chapter of the switch software configuration guide for a table that defines these conflicts.
•
When you add a VTP client, follow this caution and procedure:
CautionBefore adding a VTP client to a VTP domain, always verify that its VTP configuration revision number is lower than the configuration revision number of the other switches in the VTP domain. If necessary, reset the switch configuration revision number to 0. Switches in a VTP domain always use the VLAN configuration of the switch with the highest VTP configuration revision number. If you add a switch that has a revision number higher than the revision number in the VTP domain, it can erase all VLAN information from the VTP server and VTP domain.
Beginning in user EXEC mode, follow these steps to verify and reset the VTP configuration revision number on a switch before adding it to a VTP domain.
After resetting the configuration revision number, add the switch to the VTP domain.
Note
You can use the vtp transparent vlan database command to disable VTP on the switch and then change its VLAN information without affecting the other switches in the VTP domain. For more information about using vtp transparent mode, refer to the switch software configuration guide.
•
Host names and Domain Name System (DNS) server names that contain commas on a cluster command switch, member switch, or candidate switch can cause CMS to behave unexpectedly. You can avoid this instability in the interface by not using commas in host names or DNS names. Do not use commas when also entering multiple DNS names in the Device Configuration tab (Administration > IP Addresses) in CMS.
•
The range of seconds for the span-tree max-age global configuration command is now 6 to 200 seconds. If you had used this command in Release 11.2(8)SA6 or earlier to set a value greater than this range and now upgrade your software to Release 11.2(8.1)SA6 or later, the switch sets this value to the default: 20 seconds for IEEE STP and 10 seconds for IBM STP.
•
When using the SPAN feature, the monitoring port receives copies of sent and received traffic for all monitored ports. If the monitoring port is 50 percent oversubscribed for a sustained period of time, it will probably become congested. One or more of the ports being monitored might also experience a slowdown.
•
When using the Software Image Management (SWIM) application in the Resource Manager Essentials (RME) suite of the CiscoWorks2000 product family to perform automated system software and boot loader upgrades, you should note the following:
–
Catalyst 2900 series XL switches require Release 11.2(8)SA4 or later and RME version 2.1 or 2.2.
–
Catalyst 3500 series XL switches require Release 11.2(8.1)SA6 or later and RME version 2.2.
Open Caveats
These are the open caveats in this release:
•
CSCdv01167
A high number of collisions can occur for FTP transfers when a large number of packets are sent in a burst from a high-speed interface (such as Fa0/1) to a low-speed interface (such as Lo0/2), which can cause lower than expected transmission speeds.
The workaround is to set the LRE interface to the LRE-10 or the LRE-10LL profile.
Note
Not all environments are able to support the LRE-10 profile.
•
CSCdx03708
VLAN-tagged packets from multiple VLANs with the same source MAC address received on different Cisco 585 LRE CPE Ethernet ports create a single MAC address (ingress port entry). Any network designed with the assumption that MAC addresses are maintained per VLAN does not work.
There is no workaround; the Ethernet switch on the Cisco 585 LRE CPE does not support VLANs. All the ports are assumed to be in the same VLAN.
•
CSCdx25940
Maximum-sized ISL frames (frames of between 1537 and 1544 bytes) are discarded by the CPE device on ingress. Some chips and switches on the CPE device support a maximum frame size of 1536 bytes, which causes any maximum-sized ISL frames coming into the CPE from an end device or from an LRE switch to be discarded.
There is no workaround. You must ensure that the network does not send ISL tagged frames of sizes between 1537 and 1544 bytes to an LRE switch.
•
CSCdy40452
With LRE link persistence enabled, if you enter a shutdown command followed by a no shutdown command on the interface and wait for the LRE link to come up, when the link drops (for example, if you unplug the cable) the LRE link persistence function does not wait for the set delay duration before the link is reported as down. This only occurs the first time after a switch comes up and after a no shutdown command is entered.
The workaround is to remove the cable from the switchport and reconnect it. You can also reset the LRE interface with the command lre reset local.
•
CSCdy82784
The running configuration includes lre cpe 5 speed 100 when your LRE switch is connected to a Cisco 585 LRE CPE, even though the Cisco 585 LRE CPE supports only four Ethernet ports.
There is no workaround.
•
CSCdz36516
You can lose Ethernet connectivity on a remote CPE Fast Ethernet port if you shutdown remote CPE Fast Ethernet port from LRE interface, and then reload or reboot the switch without saving the current configuration.
The workaround is to issue the shutdown followed by no shutdown interface configuration commands.
Important Notes
This section describes important information related to this release.
•
The cluster setup privileged EXEC command was removed in Release 12.0(5)WC5.
•
The e2rb.bin LRE firmware file is required for the LRE switch operation. This file is deleted and then replaced with the most current version when you upgrade the LRE switch software. Do not delete this file after upgrading your LRE switch.
•
The MVR threshold feature was removed in Release 12.0(5.3)WC(1). To limit rates, use the port multicast storm control feature instead of the MVR threshold feature.
Documentation Notes
You can access all Catalyst 2900 documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/index.htm
This section provides updates to the product documentation.
These changes will be included in the next version of the documentation.
General Documentation Notes
•
This information is now only in the release notes and is no longer in the manuals:
–
Hardware, software, and cluster requirements
–
Procedures for initial switch configuration: using the setup program, installing browser plug-ins, and accessing CMS
–
Procedures for upgrading the switch software
•
DHCP autoconfiguration does not occur as described in the "DHCP Client Request Process" section under the "Using DHCP-Based Autoconfiguration" section in the software configuration guide.
When you start the switch, the switch automatically requests configuration information from a DHCP server only if a configuration file is not present on the switch.
DHCP autoconfiguration does not occur under these conditions:
–
When a configuration file is present and the service config global configuration command is disabled on the switch.
–
When a configuration file is present and the service config global configuration command is enabled on the switch. In this case, the switch broadcasts TFTP requests for the configuration file.
•
The software configuration guide incorrectly states that flow control is supported on ports running at 100 Mbps in full-duplex mode. Flow control is supported only on installed, 1000-Mbps module ports.
•
The 2900XL/3500XL documentation does not specify that Enterprise edition (which requires 8 Megabyes of flash) is required to configure TACACS+.
•
In the Catalyst 2900 Series XL Hardware Installation Guide in the section "Technical Specifications," Table A-4 shows an incorrect figure for the power consumption. The actual power consumption is 70W rather than 150W.
•
In the Catalyst 2900 Series XL Hardware Installation Guide in the section "Technical Specifications," Table A-4 should also include this information:
–
2912 LRE XL and 2924 LRE XL KVA rating: 0.07 KVA
–
2950 ST LRE KVA rating - 0.030 KVA
Updated Translated Warnings
These warnings have been updated for this release.
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
Overtemperature Warning
Chassis Power Connection
Catalyst 2950G-24-EI-DC Service Requirement
Initial Switch Configuration
This section provides these procedures:
•
"Using the Setup Program" section
•
"Installing the Required Plug-In" section
•
"Displaying the CMS Access Page" section
This section assumes that you have already installed the switch and connected devices to it, as described in the switch hardware installation guide.
Using the Setup Program
You can use an automatic setup program to assign switch IP information, host and cluster names, and passwords and to create a default configuration for continued operation. Later, you can use CMS or the command-line interface (CLI) to customize your configuration. To run the setup program, access the switch from the PC terminal that you connected to the console port. For information about connecting a PC or terminal to the switch console port, refer to the switch hardware installation guide.
Note
If the switch will be a cluster member, you do not always need to assign IP information or a password, as the switch will be managed through the IP address of the command switch. If you are configuring a command switch or standalone switch, you need to assign IP information. Refer to the switch software configuration guide for more information.
The first time that you access the switch, it runs a setup program that prompts you for IP and other configuration information necessary for the switch to communicate with local routers and the Internet. This information is also required if you plan to use CMS to configure and manage the switch.
You will need the following information from your system administrator:
Use this procedure to create an initial configuration for the switch:
Note
Be sure that the rollover cable is connecting a PC serial port to the switch console port. The data characteristics are 9600 baud, 8 data bits, 1 stop bit, and no parity. Use the supplied rollover cable and DB-9 adapter to connect a PC to the switch console port. You need to provide a RJ-45-to-DB-25 female DTE adapter if you want to connect the switch console port to a terminal. You can order a kit (part number ACS-DSBUASYN=) containing that adapter from Cisco. For console port and adapter pinout information, refer to the "Cable and Connector Specifications" appendix in the switch hardware installation guide.
At any point you can enter a question mark for help. Use Ctrl-C to stop the configuration dialog at any prompt. The default settings are in square brackets.
Step 1
Enter Y at the first prompt.
Continue with configuration dialog? [yes/no]: yStep 2
Enter the switch IP address, and press Return:
Enter IP address: ip_addressStep 3
Enter the subnet mask, and press Return:
Enter IP netmask: ip_netmaskStep 4
Enter Y at the next prompt to specify a default gateway (router):
Would you like to enter a default gateway address? [yes]: yStep 5
Enter the IP address of the default gateway, and press Return.
IP address of the default gateway: ip_address
Note
Enter a host name for the switch, and press Return.
Note
On a command switch, the host name is limited to 28 characters; on a member switch to 31 characters. Do not use -n, where n is a number, as the last character in a host name for any switch.
Step 6
Enter a secret password, and press Return.
Note
The password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, allows spaces, but ignores leading spaces.
Enter enable secret: secret_passwordStep 7
Enter Y to enter a Telnet password:
Would you like to configure a Telnet password? [yes] y
Note
The password can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces.
Step 8
Enter the Telnet password, and press Return:
Enter Telnet password: telnet_passwordStep 9
Enter Y to configure the switch as the cluster command switch. Enter N to configure it as a member switch or as a standalone switch.
Note
If you enter N, the switch appears as a candidate switch in Cluster Builder. In this case, the message in Step 10 is not displayed.
Would you like to enable as a cluster command switch? yStep 10
Assign a name to the cluster, and press Return.
Enter cluster name: cls_name
Note
The cluster name can be 1 to 31 alphanumeric characters, dashes, or underscores.
Step 11
The initial configuration is displayed:
The following configuration command script was created: ip subnet-zero interface VLAN1 ip address 172.20.153.36 255.255.255.0 ip default-gateway 172.20.153.01 hostname host_name enable secret 5 $1$M3pS$cXtAlkyR3/6Cn8/ line vty 0 15 password telnet_password snmp community private rw snmp community public ro cluster enable cls_name endStep 12
Verify that the information is correct.
•
If the information is correct, enter Y at the prompt, and press Return.
•
If the information is not correct, enter N at the prompt, press Return, and begin again at Step 1.
Use this configuration? [yes/no]: yAfter you complete the setup program, the switch can use the created default configuration. If you want to change this configuration or want to perform other management tasks, use one of these tools:
•
CMS from your browser (See the "Installing the Required Plug-In" section and the "Displaying the CMS Access Page" section.)
•
Command-line interface (CLI) (Refer to the switch software configuration guide.)
The switch software configuration guide provides more information about how to set a password to protect the switch against unauthorized Telnet access and how to access the switch if you forget the password.
Installing the Required Plug-In
A Java plug-in is required for the browser to access CMS. Download and install the plug-in before you start CMS. Each platform, Windows and Solaris, supports three plug-in versions. For information on the supported plug-ins, see the "Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users" section and the "Solaris Platforms" section.
You can download the recommended plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
Uninstall older versions of Java plug-ins before installing the Java plug-in.
If the Java applet does not initialize after you have installed the plug-in, open the Java Plug-in Control Panel (Start > Programs > Java Plug-in Control Panel), and verify these settings:
In the Proxies tab, verify that the Use browser settings is checked and that no proxies are enabled.
Note
If you are running McAfee VirusScan on Windows 2000 and the plug-in takes a long time to load, you can speed up CMS operation by disabling the VirusScan Internet Filter option, the Download Scan option, or both.
From the Start menu, disable the options by selecting Start > Programs > Network Associates > Virus Scan Console > Configure.
or
From the taskbar, right-click the Virus Shield icon, and in the Quick Enable menu, disable the options by deselecting Internet Filter or Download Scan.
Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users
These Java plug-ins are supported on the Windows platform:
•
Java plug-in 1.3.1
•
Java plug-in 1.3.0
•
Java plug-in 1.2.2_05
You can download these plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
If you start CMS without having installed the required Java plug-in, the browser automatically detects this. If you are using a supported Internet Explorer browser, it automatically downloads and installs the Java plug-in 1.3.1 (default). If you are using a supported Netscape browser, the browser displays a Cisco.com page that contains the Java plug-in and installation instructions. If you are using Windows 2000, Netscape Communicator might not detect the missing Java plug-in.
Solaris Platforms
These Java plug-ins are supported on the Solaris platform:
Caution


















