Table of Contents
Release Notes for the Cisco IE 2000U Series Switches, CGS 2520 Switch, and CG Ethernet Switch Module for Cisco IOS Release 15.0(2)EK1
These release notes include important information about Cisco IOS Release 15.0(2)EK1 and any limitations, restrictions, and caveats that apply to the release. Verify that these release notes are correct for your switch:
- If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
- If your switch is on, use the show version privileged EXEC command. See the “Finding the Software Version and Feature Set” section.
- If you are upgrading to a new release, see the software upgrade filename for the software version. See the “Deciding Which Files to Use” section.
For a complete list of Cisco IE 2000U, CGS 2520, and CG ESM switch documentation, see the “Related Documentation” section.
You can download the switch software from this site (registered Cisco.com users with a login password):
Table 1 lists the new features added in this release.
An IE 2000U operating with PRP has a Gigabit Ethernet or uplink Fast Ethernet port connection to each of the two LANs. The switch sends two packets simultaneously to each LAN through the two different ports to its destination node. When the destination node receives the first packet successfully, it discards the second packet if it also arrives successfully as well. Each packet sent includes an incremented sequence number that helps the destination node distinguish between duplicate packets.
For feature overview and configuration details, see the Parallel Redundancy Protocol Software Configuration Guide for IE 2000U Series Switches .
The CGS 2520 switch, CGR 2010 router, and the CG ESM all support SFP modules with DOM, beginning with the 15.0(2)EK1 Release. The DOM feature on an SFP gives the end user the ability to monitor real-time parameters of the SFP, such as optical output power, optical input power, temperature, laser bias current, and transceiver supply voltage.
See Table 5 for the supported SFPs, including SFPs with DOM support.
For information about SFP modules, see your SFP module documentation and the Cisco CGS 2520 Hardware Installation Guide , Cisco Connected Grid Routers 2010 Hardware Installation Guide , or Cisco Connected Grid Ethernet Switch Module Interface Card Getting Started Guide .
PTP is defined in IEEE-1588 as Precision Clock Synchronization for Networked Measurements and Control Systems, and was developed to synchronize the clocks in packet-based networks that include distributed device clocks of varying precision and stability. PTP is optimal for use in distributed systems because it requires minimal bandwidth and little overhead processing.
For feature overview and configuration details, see Precision Time Protocol Software Configuration Guide for IE 2000U and Connected Grid Switches .
- Support for IEEE 802.3af-compliant powered devices (up to 15.4 W PoE per port) and support for IEEE 802.3at-compliant powered devices (up to 30 W PoE+ per port).
- Support for prestandard Cisco powered devices.
- Configurable support for Cisco intelligent power management, including:
On the CGS 2520, each power supply module can support an equivalent PoE load of two PoE+ ports or four PoE ports. When both power supply modules are installed, the system has enough power to support four PoE+ ports, or eight PoE ports. If ports are designated as high priority and low priority PoE or PoE+ ports at the command line interface (CLI), and one power supply module fails or is removed, power to the high priority ports is maintained, and power to the low priority ports is dropped. When assigning priority to PoE or PoE+ ports, it is important to assign priorities on the basis of power supply capacity.
On the Connected Grid Ethernet Switch Module Interface Card GRWIC-D-ES-2S-8PC model (Copper model), the first four 10/100BASE-T ports (FE0/1, FE0/2, FE0/3, FE0/4) are PoE+ ports. A maximum of two PoE+ ports or four PoE ports can be supported at one time.
- “Power over Ethernet Ports” section in the “Configuring Interfaces” chapter of the CGS 2520 Switch Software Configuration Guide, 12.2(53)EX
- Cisco Connected Grid Ethernet Switch Module Interface Card Software Configuration Guide
- Cisco CGS 2520 Hardware Installation Guide
- Cisco Connected Grid Ethernet Switch Module Interface Card Getting Started Guide .
The CGS 2520 supports TrustSec 4.0, an intelligent access control solution that enables secure network access, shows who and what is connecting to the network, and mitigates risk by providing centralized controls over the resources that users and devices can access.
For more information, go to http://www.cisco.com/en/US/netsol/ns1051/index.html .
Table 5 summarizes the SFP modules supported on the IE 2000U, CGS 2520, CGR 2010, and the ESM.
Note The four PoE ports can operate as PoE, or as PoE+ ports with certain constraints.
- SFP-GE-L with DOM support
- SFP-GE-S with DOM support
- SFP-GE-Z with DOM support
- GLC-EX-SMD with DOM support1
Note For additional information about SFP modules, including installation procedures and cable specifications, see the Hardware Installation Guide for the applicable platform as listed in the “Related Documentation” section.
Table 6 lists the minimum software requirements for the Cisco Configuration Professional.
Table 7 lists the minimum hardware requirements for Express Setup. You can find its minimum software requirements summarized under the table.
- PC with Windows 2000, XP, Vista, or Windows Server 2003
- Finding the Software Version and Feature Set
- Deciding Which Files to Use
- Archiving Software Images
- Upgrading a Switch by Using the CLI
- Installation Notes
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 compact flash memory card.
You can also use the dir filesystem : privileged EXEC command to see the directory names of other software images stored in flash memory. For example, use the dir flash: command to display the images in the flash memory.
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Table 8 lists the filenames for this software release.
Note If you download the IP services image and plan to use Layer 3 functionality, you must use the Switch Database Management (SDM) routing template. To determine the currently active template, enter the show sdm prefer privileged EXEC command. If necessary, enter the sdm prefer global configuration command to change the SDM template to a specific template. For example, if the switch uses Layer 3 routing, change the SDM template from the default to the routing template.You must reload the switch for the new template to take effect.
Before upgrading your switch software, make sure that you archive copies of both your current
Cisco IOS release and the Cisco IOS release to which you are upgrading. Keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for information:
Note Although you can copy any file on the flash memory to the TFTP server, it is time consuming to copy all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and archive it on an internal host in your network.
This procedure is for copying the combined tar file to the 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.
Step 1 Use Table 8 to identify the file that you want to download.
Step 2 Download the software image file. If you have a SMARTNet support contract, go to this URL, and log in to download the appropriate files:
For example, to download the image for a IE 2000U switch, click Cisco IE 2000U software . To obtain authorization and to download the cryptographic software files, click IE 2000U 3DES Cryptographic Software .
For more information, see the “Assigning the Switch IP Address and Default Gateway” chapter in the applicable document listed in Table 9 .
For more information about assigning an IP address and default gateway to the switch, see Table 9 .If you are installing the same version of software that currently exists on the switch, overwrite the current image by entering 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.
You can assign IP information to your switch using the methods shown in Table 9 .
The HTTP server interface must be enabled to display the device manager. By default, the HTTP server is disabled on the switch. Use the show running-config privileged EXEC command to see if the HTTP server is enabled or disabled.
The device manager uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184, where 184 is the new HTTP port number). Be sure to write down the port number through which you are connected. Use care when changing the switch IP information.
Refer to the “Guidelines and Limitations” section of each chapter within the guides listed in the “Related Documentation” section as well as the highlighted Notes, Warnings, and Cautions.
When upgrading from a previous installed release, use the "tar" image (instead of the .bin image file alone) to perform the upgrade, to also upgrade the Backplane FPGA. The FPGA upgrade is required for the PRP feature.
This section addresses the open caveats in this release and provides information on how to use the
Bug Search Tool to find further details on those caveats. This section includes the following topics:
Workaround: Reload the ESM, or perform a shut down/no shut down of the interfaces connected to the Sifos simulator until the used power is zero. Wait for the power negotiation to stabilize every time you turn the interfaces on and off, then shut down all interfaces. The switch should return all power reserved.
Conditions: PRP is a redundancy protocol that allows the same PRP-tagged packet to be sent on two separate PRP-enabled Ethernet switch ports. Upon receiving these two packets, the switch will remove one of them. However, PRP does not allow more than one identical packet on each link. Identical packets (two or more) appearing on the same link will NOT be filtered out.
Workaround: In this PRP release, because of hardware limitations, PTP packets will not have redundancy (redundancy of PTP packets is not implemented according to the specification). However, because most of the uplink ports need to connect to the grand master clock in some of the network topology, PTP packets are allowed to tunnel through the PRP pair ports.
Symptom: Occasionally, when one of the two PRP LAN cables are disconnected (causing a LINK_DOWN condition) and then reconnected, a small number of packet drops and/or CRC errors may be observed on the PRP LAN link that did not go down. The number of packet drops may be in the 1-4 range, and the number of CRC errors may be in the 1-2 range.
You can use the Bug Search Tool to find information about caveats for this release, including a description of the problems and available workarounds. The Bug Search Tool lists both open and resolved caveats.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.