Release Notes

Stratix 5700 family of Ethernet managed switches and ArmourStratix 5700 family of Ethernet managed switches for extreme environments
Version 15.021 (released 11/2013)

Catalog Number 1783-BMS (series A)

These release notes describe version information for 1783-BMS, version 15.021 (released 11/2013).

Corrected Anomalies in This Release

This release corrects the following anomalies.

Connectivity Issues on Ports Fa1/5 and Fa1/6
 
CORRECTED: Known Anomaly Identified as of Firmware Revision 3.001, IOS 15.0(2)EA1.fc2 

Firmware Revision 2.001, IOS Release 15.0(2)EB.fc2

Catalog Numbers 1783-BMS06TL, 1783-BMS06TA

Ports Fa1/5 and Fa1/6 can exhibit connectivity issues. The status indicators on the product and the monitoring tools (Device Manager, AOP, CLI) show a link connection, but the ports do not pass traffic.

You can use either of these workarounds:
If connecting Fa1/5 or Fa1/6 from one affected switch to another affected switch, the link shuts down. In this scenario, you can use either of these workarounds:
 
Corrected: Firmware Revision 3.001, IOS 15.0(2)EA1.fc2 
 
Connectivity Issues on Ports Fa1/9 and Fa1/10
Anomaly

Firmware Revision 2.001, IOS Release 15.0(2)EB.fc2

Catalog Numbers 1783-BMS10CL, 1783-BMS10CA



Ports Fa1/9 and Fa1/10 can exhibit connectivity issues. The status indicators on the product and the monitoring tools (Device Manager, AOP, CLI) show a link
connection, but the ports do not pass traffic.

As a workaround, you can manually configure the ports to use full-duplex and
restart the switch.

If REP segments are configured with another 1783-BMS10CL or 1783-BMS10CA switch, you must manually configure one side of each link to use full-duplex while the other side retains the default configuration of Auto.
 

Corrected: Firmware Revision 3.001, IOS Release 15.0(2)EA1.fc2

Auto-negotiation and Half-duplex

Anomaly

Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL,
1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL,
1783-BMS06TGA, 1783-BMS10CGN, 1783-BMS10CL, 1783-BMS10CA,
1783-BMS10CGL, 1783-BMS10CGA, 1783-BMS10CGP,
1783-BMS12T4E2CGL, 1783-BMS12T4E2CGP, 1783-BMS12T4E2CGNK, 1783-BMS20SGN, 1783-BMS20CL, 1783-BMS20CA, 1783-BMS20CGL,
1783-BMS20CGP, 1783-BMS20CGPK

When a device is connected to a copper combo port with auto-negotiation, the port’ s Duplex mode is set to half-duplex even though the upstream switch is set to full-duplex.

 

Corrected: Firmware Revision 3.001, IOS Release 15.0(2)EA1.fc2

Express Setup with SD Card

Anomaly

Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL,
1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL,
1783-BMS06TGA, 1783-BMS10CGN, 1783-BMS10CL, 1783-BMS10CA,
1783-BMS10CGL, 1783-BMS10CGA, 1783-BMS10CGP,
1783-BMS12T4E2CGL, 1783-BMS12T4E2CGP, 1783-BMS12T4E2CGNK, 1783-BMS20SGN, 1783-BMS20CL, 1783-BMS20CA, 1783-BMS20CGL,
1783-BMS20CGP, 1783-BMS20CGPK

Express Setup fails when starting a switch with a Secure Digital (SD) card inserted.

 

Corrected: Firmware Revision 3.001, IOS Release 15.0(2)EA1.fc2

Upgrade from SD Card

Anomaly

Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL,
1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL,
1783-BMS06TGA, 1783-BMS10CGN, 1783-BMS10CL, 1783-BMS10CA,
1783-BMS10CGL, 1783-BMS10CGA, 1783-BMS10CGP,
1783-BMS12T4E2CGL, 1783-BMS12T4E2CGP, 1783-BMS12T4E2CGNK, 1783-BMS20SGN, 1783-BMS20CL, 1783-BMS20CA, 1783-BMS20CGL,
1783-BMS20CGP, 1783-BMS20CGPK

Upgrades from 15.0(1)EY1 or 15.0(1)EY2 to a later release through the
Device Manager Web interface did not work when started from a Secure Digital (SD) card.

 

 

Known Anomalies in This Release

This release has the following known anomalies.

Layer 2 NAT Statistics

Anomaly

Firmware Revision 3.001, IOS Release 15.0(2)EA1.fc2

Catalog Numbers 1783-BMS10CGN, 1783-BMS20CGN,
1783-BMS12T4E2CGNK

Layer 2 NAT statistics can show a difference in the number of translated packets versus the number of total packets after several days of operation when all packets are intended to be translated.

There is no workaround.

 

PoE Static Mode

CORRECTED with Firmware Revision 4.001, IOS Release 15.2(1)EY1

Anomaly

Firmware Revision 3.001, IOS Release 15.0(2)EA1.fc2

Catalog Numbers 1783-BMS12T4E2CGL, 1783-BMS12T4E2CGP,
1783-BMS12T4E2CGNK,

When a PoE port is set to Static mode, the port can become disabled if sufficient power is not available.

Workaround: Verify the PoE power supply is sized properly for your application or use the default Auto mode.

 

Known Anomalies from Previous Releases

These anomalies are from previous releases but are still known in this release.

Boot Host Retry Timeout

CORRECTED with Firmware Revision 5.001, IOS Release 15.2(3)EA1.fc2

Known Anomaly First Identified as of:

Release 1.001, IOS Release 15.0(1)EY1

Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL, 1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL, 1783-BMS06TGA, 1783-BMS10CL, 1783-BMS10CA, 1783-BMS10CGL, 1783-BMS10CGA, 1783-BMS10CGP, 1783-BMS20CL, 1783-BMS20CA,1783-BMS20CGL, 1783-BMS20CGP, 1783-BMS20CGPK

Revision 2.001, IOS Release 12.2(46)EX1

Catalog Numbers 1783-MS06T, 1783-MS10T

Revision 4.001, IOS Release 12.2(52)SE

Catalog Numbers 1783-RMS06T, 1783-RMS10T
 

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. This 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 nonzero value for the timeout value when you enter the boot host retry timeout timeout-value command.

Refer to the Cisco Command Reference manual, available at http://www.Cisco.com, for more information.

 

Inconsistent Statistics

Known Anomaly Identified as of

Stratix® 5700 IOS Release 15.0(1)EY1, Firmware Revision 1.001

Stratix 8000 IOS Release 12.2(46)EX1, Firmware Revision 2.001

Stratix 8300 IOS Release 12.2(52)SE, Firmware Revision 4.001

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… 66 bytes are correctly forwarded even though the port status indicator flashes amber, and the frames are not counted ithe interface statistics.

Workaround: There is no workaround.

SDM Template Configuration Does Not Sync to SD Card (Lgx00138487)

Corrected with IOS Release 15.0(2)EB.fc2

Known Anomaly Identified as of IOS Release 15.0(2)EB.fc2, Firmware Revision 2.001

Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL,
1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL,
1783-BMS06TGA, 1783-BMS10CL, 1783-BMS10CA, 1783-BMS10CGL,
1783-BMS10CGA, 1783-BMS10CGP, 1783-BMS10CGN, 1783-BMS20CL,
1783-BMS20CA,1783-BMS20CGL, 1783-BMS20CGP, 1783-BMS20CGPK, 1783-BMS20CGN

The SDM template configuration does not synchronize to or restore from the Secure Digital (SD) card. As a workaround, you can change the SDM templates manually.

 

IP Traffic Leaks on Trunk Port

CORRECTED with IOS Release 15.2(1)EY1

Known Anomaly Identified as of

Stratix 5700™ IOS Release 15.0(1)EY1, Firmware Revision 1.001

Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL, 1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL, 1783-BMS06TGA, 1783-BMS10CL, 1783-BMS10CA, 1783-BMS10CGL, 1783-BMS10CGA, 1783-BMS10CGP, 1783-BMS20CL, 1783-BMS20CA,1783-BMS20CGL, 1783-BMS20CGP, 1783-BMS20CGPK

Stratix 8000™ IOS Release 12.2(46)EX1, Firmware Revision 2.001

Catalog Numbers 1783-MS06T, 1783-MS10T


Stratix 8300™ IOS Release 12.2(52)SE, Firmware Revision 4.001

Catalog Numbers 1783-RMS06T, 1783-RMS10T

 
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. This is because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y.

There is no workaround.
 

Link Does Not Forward

CORRECTED with Firmware Revision 4.001, IOS Release 15.2(1)EY1

Anomaly

Release 1.001, IOS Release 15.0(1)EY1


Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL, 1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL, 1783-BMS06TGA, 1783-BMS10CL, 1783-BMS10CA, 1783-BMS10CGL, 1783-BMS10CGA, 1783-BMS10CGP, 1783-BMS20CL, 1783-BMS20CA,1783-BMS20CGL, 1783-BMS20CGP, 1783-BMS20CGPK

When a link is not forwarding (for example, Spanning tree learning mode when you power up the switch), the alarm status indicator blinks red. The status indicator turns solid green again when link goes into Forwarding mode.

Do the following to disable this status indicator behavior.
1. From the CLI, access Configuration mode by entering this command: configure terminal.
2. Enter the AB alarm profile by entering this command: alarm profile ab-alarm.
3. Turn off the link not forwarding alarm by entering this command: relay-major.
4. Exit Configuration mode by entering this command: end.
5. Download the configuration to nonvolatile memory by entering this command: write.

Refer to the Cisco Command Reference manual, available at http://www.Cisco.com, for more information.

 

Notification for Synchronization Is Not Necessary

CORRECTED with IOS Release 15.2(4)EA3

Stratix 5700™ and ArmorStratix™ 5700 Firmware Revision 7.001


Known Anomaly Identified as of IOS Release 15.0(1)EY1

Stratix 5700™ and ArmorStratix™ 5700 Firmware Revision 1.001


When an SD card is present and the switch is managed with the Device Manager Web interface, a notification can appear. This notification reads ‘ Notification: Switch software has been updated. Synchronize the new software between SD Card and Onboard Flash?’ . This can appear when a sync is not necessary.

The workaround is to use the Sync status indicator on the SD Sync dialog box to determine if a sync is necessary.
 

Packets Received from a SPAN Source Are Not Sent

Known Anomaly Identified as of IOS Release 15.0(1)EY1

Stratix 5700™ Firmware Revision 1.001

Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL, 1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL, 1783-BMS06TGA, 1783-BMS10CL, 1783-BMS10CA, 1783-BMS10CGL, 1783-BMS10CGA, 1783-BMS10CGP, 1783-BMS20CL, 1783-BMS20CA,1783-BMS20CGL, 1783-BMS20CGP, 1783-BMS20CGPK
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. Refer to the Cisco Command Reference manual, available at http://www.Cisco.com, for more information.

Priority Queuing Is Not Enabled

Known Anomaly Identified as of

Stratix® 5700 IOS Release 15.0(1)EY1, Firmware Release 1.001

Stratix 8000 IOS Release 12.2(46)EX1, Firmware Revision 2.001

Stratix 8300 IOS Release 12.2(52)SE, Firmware Revision 4.001

When auto-QoS is enabled on the switch, priority queuing is not enabled. Instead, the switch uses shaped-round-robin (SRR) as the queuing method. The auto-QoS feature is designed on each platform based on the feature set and hardware limitations, and the queuing method supported on each platform might be different.

Workaround: There is no workaround.

Rate of Received DHCP Requests Exceeds 2000 ppm

Known Anomaly Identified as of

Stratix® 5700 IOS Release 15.0(1)EY1, Firmware Revision 1.001

Stratix 8000 IOS Release 12.2(46)EX1, Firmware Revision 2.001

Stratix 8300 IOS Release 12.2(52)SE, Firmware Revision 4.001

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.
Workaround: Use rate limiting on DHCP traffic to prevent a denial of service attack from occurring.

Switch Queues Disabled

Known Anomaly Identified as of

Stratix® 5700 IOS Release 15.0(1)EY1, Firmware Revision 1.001

Stratix 8000 IOS Release 12.2(46)EX1, Firmware Revision 2.001

Stratix 8300 IOS Release 12.2(52)SE, Firmware Revision 4.001

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 :1 to avoid disabling the queue.

Workaround: Choose compatible buffer sizes and threshold levels.

Traffic on EtherChannel Ports Not Balanced

Known Anomaly Identified as of

Stratix® 5700  IOS Release 15.0(1)EY1, Firmware Revision 1.001

Stratix 8000 IOS Release 12.2(46)EX1, Firmware Revision 2.001

Stratix 8300  IOS Release 12.2(52)SE, Firmware Revision 4.001

Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports is distributed to member ports on the load-balance configuration and traffic characteristics such as a MAC or IP address. More than one traffic stream might map to the same member ports based on hashing results calculated by the ASIC.

If this situation occurs, uneven traffic distribution occurs 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.

Refer to the Cisco Command Reference manual, available at http://www.Cisco.com, for more information.

VLANS Not Correctly Assigned

Known Anomaly Identified as of

Stratix® 5700 IOS Release 15.0(1)EY1, Firmware Revision 1.001

Stratix 8000 IOS Release 12.2(46)EX1, Firmware Revision 2.001

Stratix 8300 IOS Release 12.2(52)SE, Firmware Revision 4.001

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 correctly assigned. One or more VLANs with a null ID appear in the MAC address table instead.
Workaround: The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port. Refer to the Cisco Command Reference manual, available at http://www.Cisco.com, for more information.

Incorrect NAT Statistics

CORRECTED with Firmware Revision 5.001, IOS Release 15.2(3)EA1.fc2

Known Anomaly First Identified as of Firmware Revision 2.001, IOS Release 15.0(2)EB.fc2

 
Catalog Numbers 1783-BMS10CGN, 1783-BMS20CGN
 
The total number of translations reported on the NAT Statistics view of the
Device Manager Web interface is fewer than the total number of NAT translated packets.

There is no workaround.

Port Threshold Exceeded Alarm Does Not Reset (134499)

Anomaly

Firmware Revision 2.001, IOS Release 15.0(2)EB.fc2


Catalog Numbers 1783-BMS06SL, 1783-BMS06SA, 1783-BMS06TL,
1783-BMS06TA, 1783-BMS06SGL, 1783-BMS06SGA, 1783-BMS06TGL,
1783-BMS06TGA, 1783-BMS10CL, 1783-BMS10CA, 1783-BMS10CGL,
1783-BMS10CGA, 1783-BMS10CGP, 1783-BMS10CGN, 1783-BMS20CL,
1783-BMS20CA,1783-BMS20CGL, 1783-BMS20CGP, 1783-BMS20CGPK, 1783-BMS20CGN

If you enable port thresholds via Device Manager or the Logix Designer application and trigger a threshold alarm by sending more traffic than is allowed through the port, the EIP Mod status indicator blinks red indicating a minor alarm. This is expected behavior. However, there is no way to reset the status indicator when you disable or change the threshold other than restarting the switch.
 
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.

Copyright © 2026 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.