Filter
Top Products
RuggedSwitch™ User Guide
flows burst continuously to 100% of the line bandwidth, STP can be disrupted.
Restrict the traffic flows to below 100%.
Problem Six
• After I bring up a new port the root moves on to that port, and I
don’t want it to.
• The port that I want to become root won’t do so.
Is it possible that the port cost is incorrectly programmed or that autonegotiation
derives an undesired value? Inspect the port and path costs with each port active
as root.
Problem Seven
• My IED/Controller doesn’t work with your switch.
Certain low CPU bandwidth controllers have been found to behave less than
perfectly when they receive unexpected traffic. Try disabling STP for the port.
If the controller fails around the time of a link outage then there is the remote
possibility that frame misordering or duplication may be the cause of the problem.
Try setting the root port of the failing controllers bridge to STP.
Problem Eight
• My network runs fine with your switch but I occasionally lose
polls to my devices.
Inspect network statistics to determine if the root bridge is receiving TCNs around
the time of frame loss. It may be possible that you have problems with
intermittent links in your network.
Problem Nine
• I’m getting lots of TCNs at the root, where are they coming from?
Examine the RSTP port statistics to determine the port from which the TCNs are
arriving. Sign-on to the switch at the other end of the link attached to that port.
Repeat this step until the switch generating the TCNs is found (i.e. the switch that
is itself not receiving a large number of TCNs). Determine the problem at that
switch.
RuggedCom