Table Of Contents
Release Notes for the Cisco IE 3000 Switch, Cisco IOS Release 15.0(2)EY2
Contents
System Requirements
Supported Hardware
Switches and Modules
SFP Modules
Device Manager System Requirements
Hardware
Software
Cluster Compatibility
CNA Compatibility
Upgrading the Switch Software
Finding the Software Version and Feature Set
Deciding Which Files to Use
Archiving Software Images
Upgrading a Switch by Using Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Installation Notes
Limitations and Restrictions
Cisco IOS Limitations
Configuration
Ethernet
IP
Multicasting
QoS
SPAN and RSPAN
Trunking
VLAN
Device Manager Limitations
Important Notes
Device Manager Notes
SDM Template Notes
Open Issues
Resolved Issues
Documentation Updates
Related Documentation
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco IE 3000 Switch, Cisco IOS Release 15.0(2)EY2
July 2013
Cisco IOS Release 15.0(2)EY2 runs on all Cisco IE 3000 switches.
These release notes include important information about Cisco IOS Release 15.0(2)EY2, and any limitations, restrictions, and caveats that apply to this 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.
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/software/navigator.html?a=ahttp://www.cisco.com/cisco/web/download/index.htmli=rpm
Contents
•System Requirements
•Upgrading the Switch Software
•Installation Notes
•Limitations and Restrictions
•Important Notes
•Open Issues
•Resolved Issues
•Documentation Updates
•Related Documentation
•Obtaining Documentation, Obtaining Support, and Security Guidelines
System Requirements
•Supported Hardware
•Device Manager System Requirements
•Cluster Compatibility
•CNA Compatibility
Supported Hardware
Switches and Modules
.
Table 1 Cisco IE 3000 Switches and Modules
|
Switch Model
|
Description
|
Supported by Minimum/Suggested Cisco IOS Release
|
Cisco IE-3000-4TC |
4 10/100BASE-T Ethernet ports and 2 dual-purpose ports, each with a 10/100/1000BASE-T copper port and an SFP (small form-factor pluggable) module slot |
Minimum: Cisco IOS Release 12.2(55)SE;
Suggested: Cisco IOS Release 15.0(2)EY2 for PoE and SFP expansion modules. |
Cisco IE-3000-8TC |
8 10/100BASE-T Ethernet ports and 2 dual-purpose ports |
Minimum: Cisco IOS Release 12.2(55)SE;
Suggested: Cisco IOS Release 15.0(2)EY2 for PoE and SFP expansion modules. |
Cisco IE-3000-4TC-E |
4 10/100BASE-T Ethernet ports and 2 dual-purpose ports (supports the IP services software feature set) |
Minimum: Cisco IOS Release 12.2(55)SE;
Suggested: Cisco IOS Release 15.0(2)EY2 for PoE and SFP expansion modules. |
Cisco IE-3000-8TC-E |
8 10/100BASE-T Ethernet ports and 2 dual-purpose ports (supports the IP services software feature set) |
Minimum: Cisco IOS Release 12.2(55)SE;
Suggested: Cisco IOS Release 15.0(2)EY2 for PoE and SFP expansion modules. |
Cisco IEM-3000-8TM |
Expansion module with 8 10/100BASE-T copper Ethernet ports
|
Minimum: Cisco IOS Release 12.2(55)SE2 |
Cisco IEM-3000-8FM |
Expansion module with 8 100BASE-FX fiber-optic Ethernet ports |
Minimum: Cisco IOS Release 12.2(55)SE2 |
Cisco IEM-3000-4SM |
Expansion module with 4 100BASE-FX fiber-optic Ethernet ports Note The base switch supports up to two expansion modules with various combinations including the IEM-3000-8FM, IEM-3000-8TM and the PoE/PoE+ modules IEM-3000-4PC and IEM-3000-4PC-4TC. An exception to the combination is that if you install an 8-port IEM-3000-8FM or IEM-3000-8SM right after the base switch, then you can install only one expansion module. |
Cisco IOS Release 15.0(2)EY2 |
Cisco IEM-3000-8SM |
Expansion module with 8 100BASE-FX fiber-optic Ethernet ports |
Cisco IOS Release 15.0(2)EY2 |
Cisco IEM-3000-4PC |
Expansion module with 4 PoE 10/100BASE-T Ethernet ports Note Each Power over Ethernet (PoE) or Power over Ethernet Plus (PoE+) module requires an external power supply besides the existing power supply used to power up the base unit. A 44-57 V DC power output is required to support PoE ports (15.4 W) and a 50-57 V DC power output is required to support PoE+ ports (30 W) to meet the IEEE 802.3at standard. Cisco power modules PWR-IE65W-PC-AC (for AC input) and PWR-IE65-PC-DC (for DC input) provide the 54 V DC/1.2 A output to the PoE/PoE+ ports. |
Cisco IOS Release 15.0(2)EY2 |
Cisco IEM-3000-4PC-4TC |
Expansion module with 4 PoE and 4 non-PoE 10/100BASE-T copper Ethernet ports |
Cisco IOS Release 15.0(2)EY2 |
SFP Modules
.
Table 2 SFP Transceivers Support for IE 3000 Series Switches
|
Type of SFP
|
SFP Models
|
Industrial Temperature 100-Megabit Transceivers |
GLC-FE-100FX-RGD 100BASE-FX, 2km1 /MMF
GLC-FE-100LX-RGD 100BASE-LX,10km/MMF |
Industrial Temperature Gigabit Uplink |
GLC-SX-MM-RGD 1000BASE-T, 220-550m/MMF
GLC-LX-SM-RGD 1000BASE-LX/LH 550m/MMF, 10km/SMF
GLC-ZX-SM-RGD 10000BASE-ZX 70-100km/SMF |
Commercial Temperature 100-Megabit Transceivers |
GLC-FE-100FX 100BASE-FX, 2km/MMF
GLC-FE-100LX 100BASE-LX, 10km/SMF
GLC-FE-100EX 100BASE, 40km/SMF
GLC-FE-100ZX 100BASE, 80km/SMF
GLC-FE-100BX-D 10km/SMF
GLC-FE-100BX-U 10km/SMF |
Commercial Temperature Gigabit Uplink |
GLC-SX-MM 1000BASE-SX, 220-500m/MMF
GLC-LH-SM 1000BASE-LH, 550m/MMF, 10km/SMF
GLC-SX-MMD 1000BASE-SX, 220-500m/MMF, DOM
GLC-LH-SMD 1000BASE-LH, 550m/MMF, 10km/SMF, DOM
GLC-EX-SMD 1000BASE-EX, 40km, DOM
GLC-ZX-SMD 1000BASE-ZX, 70-100km/SMF, DOM
GLC-BX-D 1000BASE-BX10 10km/SMF
GLC-BX-U 1000BASE-BX10 10km/SMF
CWDM SFP 100km/SMF |
Device Manager System Requirements
•Hardware
•Software
Hardware
Table 3 Minimum Hardware Requirements
|
Processor Speed
|
DRAM
|
Number of Colors
|
Resolution
|
Font Size
|
233 MHz minimum1 |
512 MB2 |
256 |
1024 x 768 |
Small |
Software
•Windows 2000, XP, Vista, and Windows Server 2003.
•Internet Explorer 6.0, 7.0, Firefox 1.5, 2.0 or later with JavaScript enabled.
Device Manager verifies the browser version when starting a session and does not require a plug-in.
Cluster Compatibility
You cannot create and manage switch clusters through Device Manager. To create and manage switch clusters, use the command-line interface (CLI) or the Network Assistant application.
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•When you create a switch cluster, we recommend configuring the highest-end switch in your cluster as the command switch.
•If you are managing the cluster through Network Assistant, the switch with the latest software should be the command switch.
•The standby command switch must be the same type as the command switch. For example, if the command switch is a Cisco IE 3000 switch, all standby command switches must be Cisco IE 3000 switches.
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, and the command reference.
CNA Compatibility
Cisco IOS Release 15.0(2)EY2 is compatible with Cisco Network Assistant (CNA) 5.4 and later.
Note CNA 5.4 and earlier do not support the cisco-ie-macros that were introduced in Cisco IOS Release 12.2(55)SE. Using the new Smartport role names will cause CNA errors.
Cisco recommends installing the latest version of CNA from this URL:
http://software.cisco.com/download/release.html?mdfid=280771500&softwareid=280775097&release=5.8.6&flowid=5128
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Software
•Finding the Software Version and Feature Set
•Deciding Which Files to Use
•Archiving Software Images
•Upgrading a Switch by Using Device Manager or Network Assistant
•Upgrading a Switch by Using the CLI
•Recovering from a Software Failure
Finding the Software Version and Feature Set
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 use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
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.
Deciding Which Files to Use
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 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 4 lists the filenames for this software release.
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 see which template is currently active template, enter the show sdm prefer privileged EXEC command. If necessary, change the SDM template to the routing template by entering the sdm prefer routing global configuration command. You will be prompted to reload the switch to activate the new template.
Note The switch must be running Cisco IOS Release 12.2(52)SE or later to configure the routing template.
Table 4 Cisco IOS Software Image Files
Filename |
Description
|
"ies-lanbasek9-mz.150-2.EY2.bin "ies-lanbasek9-tar.150-2.EY2.tar |
Cisco IE 3000 cryptographic image file and Device Manager files with Layer 2+, Kerberos, and SSH features. |
"ies-ipservicesk9-mz.150-2.EY2.bin "ies-ipservicesk9-tar.150-2.EY2.tar |
Cisco IE 3000 IP services cryptographic image and Device Manager files with Kerberos, SSH, Layer 2+, and full Layer 3 features. |
Archiving Software Images
As a best practice for any upgrade, you should first archive copies of the current Cisco IOS release and the new Cisco IOS release before you upgrade to new software. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have 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 more information:
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps6969/ps1835/prod_bulletin0900aecd80281c0e.html
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
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.
You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2:
http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_t1.html
Upgrading a Switch by Using Device Manager or Network Assistant
You can upgrade switch software by using Device Manager or Network Assistant. For detailed instructions, click Help.
Note When using Device Manager to upgrade your switch, do not use or close your browser session after the upgrade process begins. Wait until after the upgrade process completes.
Upgrading a Switch by Using the CLI
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.
Note Make sure that the compact flash card is inserted into the switch before downloading the software.
To download software, follow these steps:
Step 1 Use Table 4 to identify the file that you want to download.
Step 2 Download the software image file:
a. If you are a registered customer, go to this URL and log in.
http://software.cisco.com/download/navigator.html?mdfid=282082952&catid=268438038
b. Navigate to Switches > Industrial Ethernet Switches.
c. Navigate to your switch model.
d. Click IOS Software, then select the latest IOS release.
e. Download the image you identified in Step 1.
Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.
For more information, see the Cisco IE 3000 Switch Software Configuration Guide.
Step 4 Log into the switch through the console port or a Telnet session.
Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering this privileged EXEC command:
Switch# ping tftp-server-address
For more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
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 entering this privileged EXEC command:
Switch# archive download-sw /overwrite /reload
tftp:[[//location]/directory]/image-name.tar
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:
Switch# archive download-sw /overwrite tftp://198.30.20.19/image-name.tar
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.
Recovering from a Software Failure
For recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
Installation Notes
You can assign IP information to your switch by using these methods:
•The Express Setup program, as described in the switch getting started guide.
•The CLI-based setup program, as described in the switch hardware installation guide.
•The DHCP-based autoconfiguration, as described in the switch software configuration guide.
•Manually assigning an IP address, as described in the switch software configuration guide.
Limitations and Restrictions
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.
This section contains these limitations:
•Cisco IOS Limitations
•Device Manager Limitations
Cisco IOS Limitations
•Configuration
•Ethernet
•IP
•Multicasting
•QoS
•SPAN and RSPAN
•Trunking
•VLAN
Configuration
•A static IP address might be removed when the previously acquired DHCP IP address lease expires.
This problem occurs under these conditions:
–When the switch is booted up 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 and CSCdz11708)
•When connected to some third-party devices that send early preambles, a switch port operating at 100 Mb/s full duplex or 100 Mb/s half duplex might bounce the line protocol up and down. The problem is observed only when the switch is receiving frames.
The workaround is to configure the port for 10 Mb/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
•When port security is enabled on an interface in restricted mode and the switchport block unicast interface command has been entered on that interface, MAC addresses are incorrectly forwarded when they should be blocked
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•A traceback error occurs if a crypto key is generated after an SSL client session.
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
•The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module.
The workaround is to configure aggressive UDLD. (CSCsh70244)
•When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.
The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command. (CSCsk65142)
•On a switch running both Resilient Ethernet Protocol (REP) and Bidirectional Forwarding Detection (BFD), when the REP link status layer (LSL) age-out value is less than 1 second, the REP link flaps if the BFD interface is shut down and then brought back up.
The workaround is to use the rep lsl-age-out timer interface configuration command to configure the REP LSL age timer for more than 1000 milliseconds (1 second). (CSCsz40613)
Ethernet
•Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address. More than one traffic stream may map to same member ports based on hashing results calculated by the ASIC.
If this happens, uneven traffic distribution will happen on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem.
Use any of these workarounds to improve EtherChannel load balancing:
–for random source-ip and dest-ip traffic, configure load balance method as src-dst-ip
–for incrementing source-ip traffic, configure load balance method as src-ip
–for incrementing dest-ip traffic, configure load balance method as dst-ip
–Configure the number of ports in the EtherChannel so that the number is equal to a power of 2 (i.e., 2, 4, or 8)
For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal.(CSCeh81991)
IP
•When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time might be slow when you are using the console.
The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)
Multicasting
•If the number of multicast routes and Internet Group Management Protocol (IGMP) groups are more than the maximum number specified by the show sdm prefer global configuration command, the traffic received on unknown groups is flooded in the received VLAN even though the show ip igmp snooping multicast-table privileged EXEC command output shows otherwise.
The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. (CSCdy09008)
•IGMP filtering is applied to packets that are forwarded through hardware. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port.
There is no workaround. (CSCdy82818)
•If an IGMP report packet has two multicast group records, the switch removes or adds interfaces depending on the order of the records in the packet:
–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)
•When IGMP snooping is disabled and you enter the switchport block multicast interface configuration command, IP multicast traffic is not blocked.
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•Incomplete multicast traffic can be seen under either of these conditions:
–You disable IP multicast routing or re-enable it globally on an interface.
–A switch mroute table temporarily runs out of resources and recovers later.
The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)
•After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.
Use one of these workarounds:
–Cancel membership in the multicast group by using the no ip igmp join-group group-address interface configuration command on an SVI.
–Disable IGMP snooping on the VLAN interface by using the no ip igmp snooping vlan vlan-id global configuration command. (CSCeh90425)
QoS
•Some switch queues are disabled if the buffer size or threshold level is set too low with the mls qos queue-set output global configuration command. The ratio of buffer size to threshold level should be greater than 10 to avoid disabling the queue.
The workaround is to choose compatible buffer sizes and threshold levels. (CSCea76893)
•When auto-QoS is enabled on the switch, priority queuing is not enabled. Instead, the switch uses shaped round robin (SRR) as the queuing mechanism. The auto-QoS feature is designed on each platform based on the feature set and hardware limitations, and the queuing mechanism supported on each platform might be different.
There is no workaround. (CSCee22591)
•If you configure a large number of input interface VLANs in a class map, a traceback message similar to this might appear:
01:01:32: %BIT-4-OUTOFRANGE: bit 1321 is not in the expected range of 0 to 1024
There is no impact to switch functionality.
There is no workaround. (CSCtg32101)
SPAN and RSPAN
•Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP) packets received from a SPAN source are not sent to the destination interfaces of a local SPAN session.
The workaround is to use the monitor session session_number destination {interface interface-id encapsulation replicate} global configuration command for local SPAN. (CSCed24036)
Trunking
•The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link [ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber. This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the frame to an IEEE 802.1Q trunk interface.
There is no workaround. (CSCdz33708)
•IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the output interface for the multicast route entry assigned to the multicast group and an interface in VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y.
There is no workaround. (CSCdz42909).
•For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not counted on the interface statistics.
There is no workaround. (CSCec35100).
VLAN
•If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000, the switch can fail.
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
•When line rate traffic is passing through a dynamic port, and you enter the switchport access vlan dynamic interface configuration command for a range of ports, the VLANs might not be assigned correctly. One or more VLANs with a null ID appears in the MAC address table instead.
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port. (CSCsi26392)
•When many VLANs are configured on the switch, high CPU utilization occurs when many links are flapping at the same time.
The workaround is to remove unnecessary VLANs to reduce CPU utilization when many links are flapping. (CSCtl04815).
Device Manager Limitations
•When you are prompted to accept the security certificate and you click No, you only see a blank screen, and Device Manager does not launch.
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
•When you successfully upgrade an image by using Device Manager and click No when prompted to reload the image, Device Manager becomes unusable.
The workaround is to manually reload the switch. (CSCsj88169)
Important Notes
•Device Manager Notes
•SDM Template Notes
Device Manager Notes
•You cannot create and manage switch clusters through Device Manager. To create and manage switch clusters, use the CLI or Cisco Network Assistant.
•We recommend this browser setting to speed up the time needed to display Device Manager from Microsoft Internet Explorer.
From Microsoft Internet Explorer:
1. Choose Tools > Internet Options.
2. Click Settings in the "Temporary Internet files" area.
3. From the Settings window, choose Automatically.
4. Click OK.
5. Click OK to exit the Internet Options window.
•The HTTP server interface must be enabled to display Device Manager. By default, the HTTP server is enabled on the switch. Use the show running-config privileged EXEC command to see if the HTTP server is enabled or disabled.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
| |
Command
|
Purpose
|
Step 1 |
configure terminal |
Enter global configuration mode. |
Step 2 |
ip http authentication {aaa | enable | local} |
Configure the HTTP server interface for the type of authentication that you want to use. •aaa—Enable the authentication, authorization, and accounting feature. You must enter the aaa new-model interface configuration command for the aaa keyword to appear. •enable—Enable password, which is the default method of HTTP server user authentication, is used. •local—Local user database, as defined on the Cisco router or access server, is used. |
Step 3 |
end |
Return to privileged EXEC mode. |
Step 4 |
show running-config |
Verify your entries. |
•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). You should write down the port number through which you are connected. Use care when changing the switch IP information.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
| |
Command
|
Purpose
|
Step 1 |
configure terminal |
Enter global configuration mode. |
Step 2 |
ip http authentication {enable | local | tacacs} |
Configure the HTTP server interface for the type of authentication that you want to use. •enable—Enable password, which is the default method of HTTP server user authentication, is used. •local—Local user database, as defined on the Cisco router or access server, is used. •tacacs—TACACS server is used. |
Step 3 |
end |
Return to privileged EXEC mode. |
Step 4 |
show running-config |
Verify your entries. |
SDM Template Notes
Due to changes in the default image settings, IP routing is no longer enabled in the default SDM template. Systems that upgrade from an earlier Cisco IOS release to Release 15.0(2)EY2 must run a non-default SDM template to preserve the earlier IP routing configurations.
Open Issues
•CSCee32792
When using SNMP v3, the switch unexpectedly reloads when it encounters the snmp_free_variable_element.
There is no workaround.
•CSCth59458
If a redundant power supply (RSP) switchover occurs during a bulk configuration synchronization, some of the line configurations might disappear.
The workaround is to reapply the line configurations.
•CSCtl12389
The show ip dhcp pool command displays a large number of leased addresses.
The workaround is to turn off ip dhcp remember and reload the switch.
•CSCtq64716
The following warning messages might be displayed during the boot process even when a RADIUS or a TACACS server have been defined:
%RADIUS-4-NOSERVNAME:
or
%AAAA-4-NOSERVER: Warning: Server TACACS2 is not defined
There is no workaround.
•CSCtt00966
The maximum number of VPN routing and forwarding (VRF) instances that can be configured is 25 instead of 26.
There is no workaround.
•CSCtx35080
When an attempt is made to view the web pages of a switch, the initial request for a password by Device Manager is an unsecure connection. After the password is accepted, the next dialog box asks if a secure connection is desired.
There is no workaround.
•CSCtx35101
The password must be entered twice before it is accepted in Express Setup.
There is no workaround.
•CSCtx69656
After the switch boots up, a connected device does not receive Gratuitous ARP (GARP) packets from the switch.
The workaround is to perform one of the following actions:
–clear the ARP cache on the connected device
–use the switchport nonegotiate command on the port to which the device is connected
–ping from the switch to the connected device
•CSCty66669, CSCtz98066
When a master switch in a switch stack reloads or loses power and rejoins the stack as a member switch (Switch A), traffic from Switch A to the destination is lost.
The workaround is to ping the destination from Switch A.
•CSCua38239
When you attempt to reconfigure a flow monitor on an interface, errors occur.
The workaround is to use the no flow monitor command in interface configuration mode and then configure flow monitor on the interface again.
•CSCua54137, CSCtx69656
When the switch reverts from a floating static route to a static route, packets are lost.
The workaround is to set static ARP.
•CSCua58659
The global power inline consumption default 15400 command fails to restrict the power consumption of a PoE+ port 15.4 W.
The workaround is to use the power inline consumption default 15400 command in interface configuration mode.
•CSCua74302 (Switches running the LAN base image)
ACLs applied to outbound traffic on the switch virtual interface (SVI) do not work.
There is no workaround.
•CSCud21309
The Address Resolution Protocol (ARP) packets leak in the isolated ports of a private VLAN when dot1x is enabled.
There is no known workaround.
Resolved Issues
•CSCtx37061
Resolved an issue in which a value of -1 could not be assigned to the PortLogSyncInterval variable.
•CSCuh27934
Resolved an issue in which the SFP expansion module was not responsive when GLC-FE-100LX-RGD SFP connectors are inserted into more than four ports.
•CSCug50434
Resolved an issue in which a PoE module required 48V power on cold boot or would not provide PoE on the ports. If a PoE power source is connected while the switch is operating, and power will be provided through the ports.
Documentation Updates
The Hardware installation Guide was updated to include more details about the PoE status LED on the front panel of the IEM-3000-4PC and the IEM-3000-4PC-4TC PoE expansion modules. This information is provided below. (CSCug58080)
Table 1-5 PoE Status LED Colors and Meanings
|
Color
|
PoE Status
|
Off |
PoE is off. If the powered device is receiving power from an AC power source, the port LED is off even if the powered device is connected to the switch port. |
Green |
PoE is on. The port LED is green only when the switch port is providing power. |
Alternating green and amber |
PoE is denied because providing power to the powered device will exceed the power capacity of the expansion module. |
Flashing amber |
PoE is off due to a fault.
Caution
Noncompliant cabling or powered devices can cause a PoE port fault. Use only standard-compliant cabling to connect Cisco prestandard IP Phones and wireless access points or IEEE 802.3af-compliant devices. You must remove any cable or device that causes a PoE fault.
|
Amber |
PoE for the port is disabled. (PoE is enabled by default.) |
Related Documentation
Installation, Configuration, Maintenance, and Operation Guides
http://www.cisco.com/en/US/products/ps9703/tsd_products_support_series_home.html
•Cisco IE 3000 Switch Software Configuration Guide
•Cisco IE 3000 Switch Command Reference
•Cisco IE 3000 Switch System Message Guide
•Cisco IE 3000 Switch Hardware Installation Guide
•Cisco IE 3000 Switch Getting Started Guide—available in English, simplified Chinese, French, German, Italian, Japanese, Brazilian Portuguese and Spanish
Cisco MIB Locator
http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
For other information about related products, see these documents:
•Device Manager online help (available on the switch)
•Getting Started with Cisco Network Assistant
•Release Notes for Cisco Network Assistant
SFP Module Installation Notes
http://www.cisco.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list.html
•Cisco Small Form-Factor Pluggable Modules Installation Notes
•Cisco CWDM GBIC and CWDM SFP Installation Note
Compatibility Documents
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
•Cisco Small Form-Factor Pluggable Modules Compatibility Matrix
•Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
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)
© 2013 Cisco Systems, Inc. All rights reserved.
Feedback