Release Notes for the Catalyst 3750 Switch Cisco IOS Release 12.1(19)EA1
Finding the Software Version and Feature Set
Upgrading a Switch by Using CMS
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Cisco IOS Limitations and Restrictions
Cluster Limitations and Restrictions
CMS Limitations and Restrictions
Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(19)EA1
Cisco CMS Caveats Resolved in Cisco IOS Release 12.1(19)EA1
Correction for the Catalyst 3750 Switch Hardware Installation Guide
Corrections for the Catalyst 3750 Software Configuration Guide
Obtaining Technical Assistance
Obtaining Additional Publications and Information
The Cisco IOS Release 12.1(19)EA1 runs on all Catalyst 3750 switches. Catalyst 3750 switches support stacking through Cisco StackWise technology. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
These release notes include important information about this Cisco IOS release and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:
For the complete list of Catalyst 3750 switch documentation, see the “Related Documentation” section.
You can download the switch software from these sites:
(for registered Cisco.com users with a login password)
(for nonregistered Cisco.com users)
This software 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 software releases become available, they will be posted to Cisco.com (previously Cisco Connection Online [CCO]) in the Cisco IOS software area.
Note If you are upgrading a switch running Cisco IOS Release 12.1(11)AX that uses the 802.1X feature, you must re-enable 802.1X after upgrading the software. For more information, see the “Cisco IOS Notes” section.
This information is in the release notes:
The system requirements are described in these sections:
Table 1 lists the hardware supported by this software release.
For information about the recommended platforms for web-based management, operating systems, and browser support, refer to the “Getting Started with CMS” chapter of the software configuration guide.
This release uses a CMS plug-in (Windows only) that replaces the Java plug-in. You can download the plug-in from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/CMS-Plug-In-Win-1-0
Note You must download the CMS plug-in to run CMS for this release.
Java plug-in 1.4.1_02 is required to run CMS. You can download the Java plug-in and installation instructions from this URL:
http://www.cisco.com/public/sw-center/lan/java/1.4.1-02.html
When a cluster consists of a mixture of Catalyst switches, the Catalyst 3750 must be the command switch. The Catalyst 3750 switch can be part of a cluster as a standalone switch or as a switch stack. In a cluster, a switch stack is treated as a single entity.
When you create a switch cluster, we recommend configuring the highest-end switch in your cluster as the command switch. When the command switch is a Catalyst 3750 switch, all standby command switches must also be Catalyst 3750 switches. The Catalyst 3750 switch that has the latest software should be the command switch. If the command switch is a Catalyst 3750 Gigabit Ethernet switch and the standby command switch is a Catalyst 3750 Fast Ethernet switch, command switch port speeds are reduced if the standby command switch takes over.
Table 2 lists the cluster capabilities and software versions for the switches. The switches are listed from highest to lowest end. A lower-end switch cannot be the command switch of a switch listed above it in the table (for example, a Catalyst 2950 switch cannot be the command switch of a cluster that has Catalyst 2970 or Catalyst 3550 switches).
Member switch only1 |
||
Some versions of the Catalyst 2900 XL software do not support clustering, and if you have a cluster with switches that are running different versions of Cisco IOS software, software features added on the latest release might not be reflected on switches running the older versions. For example, if you start CMS on a Catalyst 2900 XL switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)WC(1) or later.
Note The CMS is not forward-compatible, which means that if a member switch is running a software version that is newer than the release running on the command switch, the new features are not available on the member switch. If the member switch is a new device supported by a software release that is later than the software release on the command switch, the command switch cannot recognize the member switch, and it is displayed as an unknown device in the Front Panel view. You cannot configure any parameters or generate a report through CMS for that member; instead, you must launch the Device Manager application to configure and to obtain reports for that member.
These are the procedures for downloading software:
Note Before downloading software, read this section for important information.
The Cisco IOS image is stored as a . bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board Flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line displays C3750-I5-M for the enhanced multilayer image (EMI) or C3750-I9-M for the standard multilayer software image (SMI).
Note Although the show version output always shows the software image running on the switch, the model name shown at the end of this display is the factory configuration (SMI or EMI) and does not change if you upgrade the software image.
You can also use the dir filesystem : privileged EXEC command to see the directory names of other software images that you might have stored in Flash memory.
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined.tar file. This file contains both the Cisco IOS image file and the files needed for the CMS. You must use the combined.tar file to upgrade the switch through the CMS. To upgrade the switch through the CLI, use the.tar file and the archive download-sw privileged EXEC command.
Table 3 lists the software filenames for this software release.
You can upgrade switch software by using CMS. From the feature bar, select Administration > Software Upgrade. For detailed instructions, click Help.
This procedure is for copying the combined.tar file to the Catalyst 3750 switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
To download software, and if necessary, the TFTP server application, follow these steps:
Step 1 Use Table 3 to identify the file that you want to download.
Step 2 Download the software image file.
http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml
http://www.cisco.com/public/sw-center/sw-lan.shtml
To download the SMI and EMI files, select Catalyst 3750 software.
To obtain authorization and to download the crypto software files, select Catalyst 3750 3DES Cryptographic Software.
Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure the TFTP server is properly configured.
For more information, refer to Appendix B in the software configuration guide for this release.
Step 4 Log into the switch through the console port or a Telnet session.
Step 5 Ensure that you have IP connectivity to the TFTP server by using this privileged EXEC command:
For more information about assigning an IP address and default gateway to the switch, refer to the Catalyst 3750 Switch Software Configuration Guide.
Step 6 Download the image file from the TFTP server to the switch. If you are installing the same version of software that is currently on the switch, overwrite the current image by using this privileged EXEC command:
The /overwrite option overwrites the software image in Flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For // location, specify the IP address of the TFTP server.
For / directory / image-name .tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
You can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.
You can assign IP information to your switch by using these methods:
Note If you are upgrading a switch running Cisco IOS Release 12.1(11)AX which uses the 802.1X feature, you must re-enable 802.1X after upgrading the software. For more information, see the “Cisco IOS Notes” section.
These sections describe the new supported hardware and the new software features provided in this release:
For a list of all supported hardware, see the “Hardware Supported” section.
Cisco IOS Release 12.1(19)EA1 contains these new features or enhancements:
Note In the software documentation, IP refers to IP version 4 (IPv4).
– The option to install CMS to your computer rather than to download it from the cluster every time you start a CMS session.
Note CMS is downloaded to your browser each time you launch CMS. You can increase the speed at which CMS loads by permanently installing CMS on your PC or workstation. Select CMS > Installation and Distributions, and click Install. CMS is installed locally and will load faster the next time that you launch it.
– A feature bar, which offers networking features to configure and reports, graphs, and statistics to display. These options were previously on the menu bar, which is now dedicated to CMS service options. You can choose features from menus on the Features tab or search for them on the Search tab.
– Device-specific online help. Help topics appear below labels that name the devices to which the information applies. Topics appear only for the networking features in the cluster.
– This release uses a CMS plug-in (Windows only) that replaces the Java plug-in.
Note You must download the CMS plug-in to run CMS for this release.
You can download the plug-in from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/CMS-Plug-In-Win-1-0
The CMS plug-in includes a console window that you can use for troubleshooting. For more information see the “Documentation Updates” section.
For more information about new CMS features, click Help > What’s New from the online help.
For a detailed list of key features for this software release, refer to the Catalyst 3750 Switch Software Configuration Guide.
You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
These sections describe the limitations and restrictions:
These limitations apply to Cisco IOS configuration:
This problem occurs under these conditions:
– When the switch is booted without a configuration (no config.text file in Flash memory).
– When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1).
– When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires.
The workaround is to reconfigure the static IP address. (CSCea71176)
The workaround is to not set an ARP timeout value lower than 120 seconds. (CSCea21674)
This error message indicates a temporary memory shortage that normally recovers by itself. You can verify that the switch stack has recovered by entering the show cef line user EXEC commend and verifying that the line card states are up
and sync
. No workaround is required because the problem is self-correcting. (CSCea71611)
Decreased egress SPAN rate
. In all cases, normal traffic is not affected; the degradation limits only how much of the original source stream can be egress spanned. If fallback bridging and multicast routing are disabled, egress SPAN is not degraded. There is no workaround. If possible, disable fallback bridging and multicast routing. If possible, use ingress SPAN to observe the same traffic. (CSCeb01216)– If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the switch removes the port from the group.
– If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the switch adds the port to the group.
There is no workaround. (CSCec20128)
These limitations apply to cluster configuration:
These limitations apply to CMS configuration:
– Netscape 4.75 and JRE 1.3.1 or 1.4.0
The workaround is to click once outside of the CMS Window. CMS then proceeds. (CSCdz72175)
These sections describe the important notes related to this software release:
These notes apply to switch stacks.
This note applies to Cisco IOS software:
These notes apply to CMS configuration:
Resize the browser window again when CMS is not busy.
– Catalyst 2900 XL or Catalyst 3500 XL member switches running Cisco IOS Release 12.0(5)WC2 or earlier
– Catalyst 2950 member switches running Cisco IOS Release 12.0(5)WC2 or earlier
– Catalyst 3550 member switches running Cisco IOS Release 12.1(6)EA1 or earlier
In the Front Panel view, if the switch is running one of the previously listed software releases, the device LEDs do not appear. In the Topology view, if the member is a Long-Reach Ethernet (LRE) switch, the customer premises equipment (CPE) connected to the switch does not appear. The Bandwidth and Link graphs also do not appear in these views.
To view switch information, you need to upgrade the member switch software. For information about upgrading switch software, see the “Downloading Software” section.
These sections describe the open caveats with possible unexpected activity in this software release:
These are the severity 3 Cisco IOS configuration caveats:
When multicast VLAN registration (MVR) groups are added or deleted, the receiver port that joined the groups after the addition still receives traffic even after the group is deleted. The correct behavior is that MVR data traffic to the group should stop flowing to the receiver port immediately after the no mvr group ip-address global configuration command is entered.
The workaround is to disable MVR by using the no mvr global configuration command and then to re-enable it by using the mvr command. Add and delete the groups that have problems by using the mvr group ip-address and the no mvr group ip-address global configuration commands.
If the stack master is reloaded immediately after adding multiple VLANs, the new stack master might fail.
The workaround is to wait a few minutes after adding VLANs before reloading the stack master.
While booting up a nine-member switch stack with a large number of SNMP traps enabled, some of the stack members might not come up fully and become operational. There are two possible scenarios:
– The stack member stays in the initializing state. Use the show switch user EXEC command to detect this condition. Normally a switch joining the switch stack transitions from Initializing
to Ready
within 1 minute.
– The stack member comes up in the ready state, but all ports on the stack member remain in the linkdown state even though link partners indicate a linkup state.
The workaround is to reboot the whole switch stack using one of these methods:
– Use the reload privileged EXEC command on the stack master.
– Power cycle the stack master.
Gigabit Ethernet ports might have FCS errors when operating at Gigabit speeds on the Catalyst 3750G-24T and Catalyst 3750G-24TS switches. The FCS error rate for this condition is very low.
The workaround is to restart the ports by using the shutdown and then no shutdown interface configuration commands.
Distance Vector Multicast Routing Protocol (DVMRP) does not forward packets correctly.
After booting up a switch stack that has more than 300 VLANs and the maximum number of static EtherChannel groups (12), all interfaces that are part of an EtherChannel might stay down. This occurs because the remote switch detects an EtherChannel misconfiguration and disables its ports. This problem can occur in either PVST+ or Rapid-PVST+ mode.
The workaround is to restart the EtherChannel ports or configure automatic recovery:
– Use the shutdown and no shutdown interface configuration commands on the remote switch to restart all err-disabled interfaces
– Use the errdisable recovery cause channel-misconfig global configuration command to enable automatic link recovery on the remote switch, and use the errdisable recovery interval global configuration command to configure a short recovery interval.
After switches are added to or removed from a switch stack, the reconfiguration processes can defer normal CPU processes, such as CLI command handling, and make them unresponsive. The duration of the reconfiguration process depends on the size and nature of the running configuration, but the delay is not significant until the switch configuration exceeds several thousand lines. After the update finishes, CLI responsiveness returns.
There is no workaround other than removing commands from the switch configuration.
On a voice VLAN port with both 802.1X and port security enabled, dynamic secure addresses might not get deleted when the port is changed from multihost mode to single-host mode. This means that addresses learned in the multihost mode are still allowed after changing to single-host mode. This problem occurs under the following conditions:
– The port is in authorized state.
– The port learns the MAC address of multiple hosts.
– VLAN assignment is not enabled for the authorized host.
The workaround is to disable and then re-enable port security on the port.
If a switch stack is running fallback bridging and the switches in the switch stack have routed ports in the bridge-group, fallback bridging might not work. This occurs when the TCAM is full and a switch is added or deleted from the switch stack.
The workaround is to stop traffic to free up space in TCAM and then to reload the whole switch stack. Then enable the traffic 1 minute after the switch stack comes back up.
If a Catalyst 3750 switch loaded with Cisco IOS Release 12.1(14)EA1 software is added to a switch stack running Cisco IOS Release 12.1(11)AX software, the stack member changes to version mismatch (as expected). If an SNMP application traverses the CISCO-FLASH-MIB, a stack member in version mismatch state can fail.
The workaround is to avoid traversing the CISCO-FLASH-MIB while the switch stack is being upgraded from Cisco IOS Release 12.1(11)AX to Cisco IOS Release 12.1(14)EA1.
A Catalyst 3750 switch does not work with the User Registration Tool (URT). The PC attempting to connect to the network can log in successfully, but is not allowed to pass traffic after the port is moved to the user VLAN. The MAC address for that device shows BLOCKED.
If an IP phone is connected to a port on the stack master, and 802.1X port security and voice VLAN are configured on the port, disabling port security causes the IP phone MAC address to be deleted from the MAC address table on all stack members. The MAC address table on the stack master retains the phone MAC address.
Although it is visible in the command-line help string, the source-only-learning keyword is not supported on the Catalyst 3750 switches. Also, the igmp snooping report-suppression feature does not work.
If an 802.1X port is configured for forced-unauthorized port control mode and voice VLAN, after you remove the voice VLAN and disable 802.1X on the port, the port no longer passes traffic.
The workaround is to restart the port by using the shutdown and then the no shutdown interface configuration commands.
When DHCP snooping is enabled, if the lease time given by the server to the client is infinite, tracebacks are generated.
When CDP is disabled on a stack member interface and that interface is converted to a routed port or switch port, CDP is re-enabled on the stack member interfaces. Having CDP enabled on a stack member but not on the stack master can cause the 802.1X voice VLAN and inline power features to fail on the stack member.
The workaround is to enable and then disable CDP on the interface.
When both the sharing and shaping weights are enabled on Catalyst 3750 switches, the receiving rates might not follow the shared bandwidth weight if the priority queue is enabled on the egress queue.
The workaround is to use lower values of the shaped and shared weights for queues other than the first queue when the egress priority queue is enabled and if shaping in other queues is required.
Executing remote commands on a Catalyst 3750-12S switch that is unpacking and copying a new software image to Flash memory can cause the software upgrade to fail.
The workaround is to reload the switch to re-enable Flash operations, and then repeat the software upgrade procedure.
If a stack of Catalyst 3750 switches has a running configuration file larger than 400 kilobytes, this error message might appear when you exit global configuration mode and every 30 seconds while you are in global configuration mode:
There is no workaround. This does not affect switch functionality.
When IP Protocol-Independent Multicast (PIM) is enabled on a tunnel interface, the switch incorrectly displays the Multicast is not supported on tunnel interfaces
error message. IP PIM is supported on tunnel interfaces.
For an interface, if the voice VLAN and the access VLAN are assigned to different VLANs and the access VLAN enters a suspended state, the IP phones do not work.
The workaround is to reset the access VLAN to the active state.
If the system jumbo frame size is configured by using the system mtu jumbo global configuration command, the switch does not consistently forward routed IP packets between 1518 and 2016 bytes. These packets might be forwarded or dropped.
When an ACL that denies packets is configured on an ingress or an egress interface, the CPU usage might be as high as 70% because these packets are forwarded to the CPU to determine if an ICMP-unreachable packet should be generated.
When a configured secure MAC address exists on an interface, you cannot change it to a sticky MAC address. Alternatively, if a sticky MAC address exists on an interface, you cannot change it to a secure MAC address.
The workaround is to remove the configured secure or sticky MAC address by using the no switchport port-security mac-address mac-address or the no switchport port-security mac-address sticky mac-address interface configuration command before reconfiguring the port.
When the CISCO-STP-EXTENSIONS-MIB is polled, unknown indexes could be returned for some MIB objects.
The workaround is to remove all port-channel configuration information.
When an 802.1X- enabled port is authenticated with a radius-assigned VLAN, the port is shut down or link is removed, and a traceback message appears.
After a link is up, a switch sends three EAP-Request/Identity messages to the client. There is a 30-second gap between messages. However, PCs that are running Windows XP or Windows 2000 drop the first message so that the second message that the client receives appears to be the first, which is at least 30 seconds after the link is up. Therefore, a user does not see a password window until at least 30 seconds after the link is up.
During the SNMP polling of the VlanTrunkPortTable table in the CISCO-VTP-MIB, Telnet and ping traffic might be disrupted.
The workaround is to not poll the CISCO-VTP-MIB.
If per-user access control lists (ACLs) are downloaded from a RADIUS server after successful 802.1X authentication, disabling 802.1X does not remove the attached per-user ACLS from the interface.
The workaround is to enter the shutdown and no shutdown interface configuration commands to remove the ACLs.
When a Catalyst 3750 port has port security enabled and the port is changed from a trunk port to an access port, the switch might crash.
The workaround is to disable port security before changing the trunk port to an access port.
If QoS is enabled and the trust state is not configured on an ingress interface, mapping the CoS or DSCP values to the ingress or egress queues does not take effect when you enter the mls qos srr-queue input { cos-map | dscp-map } or the mls qos srr-queue output { cos-map | dscp-map } command.
The workaround is to configure the trust state on the ingress interface by using the mls qos trust { cos | dscp } interface configuration command and then map the CoS or DSCP values to the ingress or egress queues.
If you change the input priority queue for queue 2 by using the mls qos srr-queue input priority-queue 2 bandwidth global configuration command, the configurations that are generated contain an extra input keyword such as mls qos srr-queue input priority-queue input 2 bandwidth. This extra keyword causes an error message if the command is saved and the switch is reloaded.
1. Copy the config.text file to a PC or terminal.
2. Edit the config.text file and remove the extra input keyword.
3. Copy the file back to your switch.
When there are many configured secure and sticky MAC addresses on a port, some addresses might be dropped and removed from the configuration when the switch restarts.
The Catalyst 3750 EMI cryptographic image has a higher priority than the Catalyst 3750 SMI image during the master switch election in a stack. When two or more switches in the stack use different software images, such as the SMI image for Cisco IOS Release 12.1(11)AX and the cryptographic EMI for Cisco IOS Release 12.(19)EA1 or later, the switch running the SMI is selected as the stack master. This occurs because the switch running the cryptographic EMI takes 10 seconds longer to start than the switch running the SMI does, which causes the switch running the EMI to be excluded from the master election process that lasts 10 seconds.
The workaround is to upgrade the switch running the SMI to a software release later than Cisco IOS Release 12.1(11)AX or to manually start the master switch and wait at least 8 seconds before starting the new member switch.
When you configure a unicast MAC address filter that matches a Windows XP 802.1X client MAC address, the switch sends an authentication succeed EAPOL packet to the client followed by an authentication failure EAPOL packet. The Windows XP 802.1X client continues to reauthenticate itself.
If you change the policy-based routing (PBR) configuration on a switch, the processor memory might leak. If amount of available processor memory becomes too low, the switch becomes unusable.
The workaround is to reload the switch.
If BPDU filtering is enabled on a trunk port and BPDUs are received on VLANs on which an STP instance is not running, the BPDUs are dropped.
These are the severity 3 CMS configuration caveats:
The Port Settings table displays meaningless information in the columns for interface description and duplex cells. This problem occurs for some of the Catalyst 2820 and Catalyst 1900 switches.
CMS does not validate configuration values for STP port priority before applying them to the switch. When invalid values are applied, the attempt fails silently without a warning message. This applies to all switches running Cisco IOS Release 12.1 or later.
There is no workaround. Make sure that configuration values are valid.
CMS does not validate configuration values for STP port path cost before applying them to the switch. When invalid values are applied, the attempt fails silently without a warning message. This applies to all switches running Cisco IOS Release 12.1 or later.
There is no workaround. Make sure that configuration values are valid for the switch type.
CMS does not validate configuration values for STP bridge parameters before applying them to the switch. When invalid values are applied, the attempt fails silently without a warning message. This applies to all switches running Cisco IOS Release 12.1 or later.
There is no workaround. Make sure that configuration values are valid.
When CMS is operating in read-only mode, an error is reported if help is launched from the QoS Graph dialog box.
CMS does not apply shaped bandwidth weights that are invalid. Shaped weights are invalid if the sum of their reciprocals is greater than 1 and the weight of a queue is 0.
The settings on the Catalyst 2950 LRE ports cannot be modified by using the Port Settings window in CMS.
You cannot attach an access control list (ACL) to or or remove one from an interface when you are in guide mode.
The workaround is to use expert mode to attach an ACL to or or remove one from an interface.
When you change the Spanning Tree Protocol (STP) port priority on a switch that is running
Cisco IOS Release 12.1(19)EA1 or later, the value must range from 0 to 240 and be in an increment of 16. If you enter a value that is not an increment of 16, the configuration fails, and no error message appears.
The workaround is to enter values from 0 to 240 that are in increments of 16.
If UplinkFast is enabled and you enter a value in the Path Cost field in the STP Modify Port Parameters window, 3000 is automatically added to the configured-STP cost value. For example, if the path cost is 10, the actual value is 3010. If you disable UplinkFast, the path-cost value changes to its originally configured value of 10.
CMS does not recognize the CWDM SFP module on the Catalyst 2940 switches, even though the CWDM SPF module is supported by the switches.
When you launch the IP Multicast wizard, multicast-enabled devices do not appear in the list of multicast-enabled devices.
There is no workaround. The wizard does not display multicast-enabled devices.
When you right-click on a Catalyst 3750 switch in the Front Panel view, these pop-up menu options do not appear:
– The delete-cluster menu option if the Catalyst 3750 switch is a commander switch.
– The remove-from cluster option if the Catalyst 3750 switch is a member switch.
The workarounds are to select these menu options from the feature bar:
– Select Cluster > Delete Cluster to delete a cluster from a command switch.
– Select Cluster > Remove from Cluster to remove a member switch.
When you click Highlight VLAN Port Membership Modes in the VLAN window of a switch whose front panel is not displayed in Front Panel view, CMS brings the Front Panel view to the foreground, but the Front Panel view of the switch is not displayed and you cannot see the highlighted ports.
– From the Front Panel view cluster tree, check the box beside the switch icon so that the switch's front panel is displayed in Front Panel view. Then click Highlight VLAN Port Membership Modes in VLAN window. The switch's front panel is displayed and you can see the highlighted ports.
– After you click Highlight VLAN Port Membership Modes in VLAN window, you should check the box beside the switch icon in the Front Panel view cluster tree. The switch's front panel is displayed and you can see the highlighted ports.
When you click Previous instead of Finish in the Save Configuration window, the configuration for the interfaces is not applied to the member devices.
The workaround is to click the Finish button to apply the configuration to member devices. If you need to modify the configuration, you need to launch the configuration wizard again.
The IGMP Report Window does not list all the entries in the table.
These are the caveats that have been resolved in this release.
These Cisco IOS caveats were resolved in Cisco IOS Release 12.1(19)EA1:
Local and Remote SPAN can now be configured at the same time.
Under the these conditions, the Catalyst 3750 switch no longer reports a false security violation after an 802.1X supplicant is authenticated and assigned a new VLAN by the RADIUS server:
– 802.1X, port security, and voice VLAN are configured on a stack member port.
– Maximum number of secure addresses have been learned on the port before it is authenticated.
– The VLAN assigned by the RADIUS server is different than the access VLAN configured on the port.
A Catalyst 3750 switch is now able to pass Vine (Advanced Research Projects Agency) ARPA frames over bridge groups.
If an interface on a Catalyst 3750 switch was mapped to queue-set 2 and you disable and then globally re-enable multilayer QoS, the interface is now mapped to the correct egress queue-set (queue-set 2).
This section provides updates to the product documentation. These changes will be included in the next revision of the documentation.
The CMS requirements as described in the “Managing the Switch by Using the Cluster Management Suite” chapter are no longer correct. Refer to the “Getting Started with CMS” chapter of the switch software configuration guide for the latest CMS requirements.
These are corrections for the “Getting Started with CMS” chapter:
When CMS is running, press F2 to display or to hide the CMS console. Press F3 to display or to hide the CLI commands that CMS is sending.
http://www.cisco.com/public/sw-center/lan/java/1.4.1-02.html
These documents provide complete information about the switch and are available at Cisco.com:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/index.htm
You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the “Obtaining Documentation” section.
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order annual or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
Click Subscriptions & Promotional Materials in the left navigation bar.
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can submit e-mail comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
The Cisco TAC website ( http://www.cisco.com/tac) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
Using the online TAC Case Open Tool ( http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer.
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete listing of Cisco TAC contacts, go to this URL:
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
http://www.cisco.com/go/iqmagazine
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html