Cisco Industrial Ethernet 5000 Series Release Notes

Hardware Supported

Switch Models Supported

SFP Modules Supported

The SFP modules are switch Ethernet SFP modules that provide connections to other devices. Depending on the switch model, these field-replaceable transceiver modules provide uplink or downlink interfaces. The modules have LC connectors for fiber-optic connections.

You can use any combination of the supported SFP modules.

Table 1 SFP Modules

Express Setup Requirements

Hardware

• 1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
• 1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
• 16 GB available hard disk space (32-bit) or 20 GB (64-bit)

Software

• PC with Windows 7, or Mac OS 10.6.x
• Web browser (Internet Explorer 9.0, 10.0, and 11.0; or Firefox minimum version 25, recommended version 32) with JavaScript enabled
• Straight-through or crossover Category 5 or 6 cable

Express Setup verifies the browser version when starting a session, and it does not require a plug-in.

Right-to-Use License

“Right to Use” (RTU) is a trust based licensing scheme designed to make life easier for customers. It is designed to give customers the flexibility to upgrade, downgrade, or move the license for RMA purpose by using simple EXEC CLI commands. As this is a “trust” based scheme, customer can pay for a certain number of licenses in advance, and then activate these flexibly across a full range of switches deployed provided the number of licenses does not exceed that number at any given time.

There are 2 main types of licenses used for the IE5000 - “Evaluation” and “Permanent RTU (PRTU)”. An “Evaluation” license allows the customer to evaluate an image for 60 days at no cost. A “Permanent RTU” license is a paid license with no expiration. A user is prompted to change to a permanent license before the evaluation license expires, with periodic reminders. This license is “in-built” in the image just like the current “Evaluation License” in the CISL model, so customers do not need to connect to Cisco servers to get a license. A PRTU license is not tied to a particular hardware. It can be deactivated from the old/swapped out hardware and activated on the replacement switch using the CLI.

Secure Boot

• With the Secure Boot mechanism, software must be digitally signed and verified for authenticity and integrity prior to load and execution. This protects customers from running tampered software and safeguards revenue through software counterfeit protection.
• The switch can be booted only with a timed key using valid IOS image.
• Every IOS release will have the timing keys embedded inside the IOS image.

Dying Gasp

• If there is a loss of power to the switch, it sends out “Dying Gasp” messages to the OAM center to notify about the situation.
• These messages inform the downstream nodes about the loss of the switch, which helps routing recovery.

Smart Install

Smart Install is a plug-and-play configuration and software upgrade feature that provides zero-touch deployment for new switches. You can ship a switch to a location, place it in the network, and power it on with no configuration required on the device. For more information, see Smart Install Configuration Guide here: http://www.cisco.com/c/en/us/td/docs/switches/lan/smart_install/configuration/guide/smart_install.html

Note IE 5000 can be a Smart Installation Director.

Cisco IOS Limitations

• IP
• RADIUS
• SPAN and RSPAN
• Spanning Tree Protocol
• VLAN

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)

RADIUS

• RADIUS change of authorization (COA) reauthorization is not supported on the critical auth VLAN.

There is no workaround. (CSCta05071)

SPAN and RSPAN

• When the RSPAN feature is configured on a switch, Cisco Discovery Protocol (CDP) packets received from the RSPAN source ports are tagged with the RSPAN VLAN ID and forwarded to trunk ports carrying the RSPAN VLAN. When this happens a switch that is more than one hop away incorrectly lists the switch that is connected to the RSPAN source port as a CDP neighbor.

This is a hardware limitation. The workaround is to disable CDP on all interfaces carrying the RSPAN VLAN on the device connected to the switch. (CSCeb32326)

• 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)

Spanning Tree Protocol

• CSCtl60247

When a switch running Multiple Spanning Tree (MST) is connected to a switch running Rapid Spanning Tree Protocol (RSTP), the MST switch acts as the root bridge and runs per-VLAN spanning tree (PVST) simulation mode on boundary ports connected to the RST switch. If the allowed VLAN on all trunk ports connecting these switches is changed to a VLAN other than VLAN 1 and the root port of the RSTP switch is shut down and then enabled, the boundary ports connected to the root port move immediately to the forward state without going through the PVST+ slow transition.

There is no workaround.

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)

Express Setup Notes

• This browser setting is recommended for speeding up the time required to display Express Setup 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 Express Setup. 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:

• Express Setup 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). 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:

Note If the Express Setup failed in the Web Browser, use the reset button to reset the switch to factor default

Open 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)

© 2015 Cisco Systems, Inc. All rights reserved.