to results for ""
Below is a cache of http://www.ruggedcom.com/pdfs/soft_history/ros_history/ros-cf52_main_v3-4-6.pdf. It's a snapshot of the page taken as our search engine crawled the Web.
The web site itself may have changed. You can check the current page or check for previous versions at the Internet Archive. Yahoo! is not affiliated with the authors of this page or responsible for its content.
Rugged Operating System v3.4.6 Release Notes May 1, 2008

ROS
TM
3.4.6 Release Notes
Rugged Operating System v3.4.6 Release Notes
May 1, 2008
Copyright © 2008 RuggedCom Inc.
Overview
ROS
TM
v3.4.6 provides a single bug fix.

This firmware release supports all RuggedSwitch and RuggedServer product series.

Build date: Apr 28 2008 12:53

File Size: 1851442



User Guides
All user Guides are available from the RuggedCom Web site at
www.RuggedCom.com
.

ROS
TM
3.4.6 Release Notes
Changes In v3.4.6 (1405)
Fixed false positive Port Guard activation
Type:
Minor
Products:
All except RMC30
ID:

1400
A similar issue was addressed in v3.4.5. However, it was learned that even when tolerating
continuous port bouncing-link conditions for 3 seconds, there are still occurrences of false positive
Port Guard activation resulting in shutting down ports for some end devices. It was recognized that
responding to a sustained bouncing link condition on a port by disabling the port may be too
aggressive as it is causing interruption to a customer network.
The instantaneous CPU response to a port bouncing-link condition is now mitigated by modulation
(i.e. varying the On/Off time duty cycle) of the port (PHY) interrupt response referred to in ROS as
the Fast-Link-Detection (FDL) facility. In addition the final (steady state) response to a prolonged
bouncing-link condition will be filtered by significantly lengthening the tolerance-window (to greater
than 2 minutes) before a decision will be reached to raise an Alarm to indicate that Port Guard has
latched FDL in a disabled state. Unless this alarm has been raised, the Port Guard will continuously
recover from intermittent bouncing-link conditions, without network interruption or manual
intervention.

Fixed Relay Agent Operation
Type:
Critical
Products:
All
ID:

1389
If switch was acting as Relay Agent, the DHCP frames received from client were corrupted during
frame type determination. Corrupted frames were not recognized as DHCP frames, but instead were
sent to IP stack for processing, which could cause system to crash. This is fixed.


ROS
TM
3.4.6 Release Notes
Changes In v3.4.5 (1353)
Fixed false positive Port Guard activation
Type:
Minor
Products:
All except RMC30, RS8000 and RS1600
ID:

1343

The Port Guard feature was implemented to protect the device CPU from being overloaded by
processing frequent Ethernet link state changes (i.e. bouncing link) caused by a faulty end device or
invalid cable connection (e.g. 10Base-FL to 100Base-FX connection). However, link bouncing for a
short period of time (less than a second) is apparently normal for some end devices. Such an event
could trigger an undesirable Port Guard activation. To prevent such a false positive event, Port
Guard is only activated if the link is bouncing for a minimum of 3 seconds.



ROS
TM
3.4.6 Release Notes
Changes In v3.4.4 (1323)
Command enhanced to add developer level information for Debugging
Purposes
Type:
Enhancement
Products:
All
ID:

1262

The last ROS release (v3.4.3) introduced some significant new OS hardening technologies (See
ID # 1312). The intended set of diagnostics and recovery enhancements were incomplete however,
due to release deadline obligations, and so the implementation has been continued (and validated)
with this release.

Specifically, an enhancement to a (factory mode) system command (klog) was originally planned
(for the previous release) to facilitate capturing data which is useful for developer debugging and
diagnostics purposes, from the running C stack of suspended tasks. Although originally planned to
be included in the previous release, the command was NOT fully operational until now.


ROS
TM
3.4.6 Release Notes
Changes In v3.4.3 (1297)
Fixed operation under heavy multicast traffic with more than 256 multicast
streams
Type:
Major
Products:
All except RS400 and RMC30
ID:

1289
Received multicast packets should be forwarded to the device CPU, so that ROS
TM
would be able to
perform multicast filtering (IGMP Snooping). Even if a multicast packet shouldnt be filtered by IGMP
Snooping, ROS
TM
still applies internal multicast filters to protect the device CPU from being
overloaded by processing continuously received multicast frames (streams). The number of such
multicast filters was limited to 256, so any additional multicast streams kept being forwarded to the
CPU and those streams could overload the CPU, thus blocking different ROS
TM
applications. To
prevent such scenario, forwarding multicast frames to the CPU is disabled, as long as IGMP
Snooping is disabled. NOTE: In some products (i.e. RS8000 and RS1600 series), disabling of
forwarding multicast frames to the CPU may not be possible due to hardware constraints, so the
problem is solved by significantly increasing the number of multicast filters created by the software
upon detection of multicast streams.
Fixed processing IP broadcasts received on non-management VLAN on DHCP
Relay Agent access ports
Type:
Minor
Products:
All except RMC30
ID:

1299
ARP packets (broadcasts) received on non-management VLANs on a switch DHCP Relay Agent
access port, were ignored. As a result, devices on corresponding VLAN interfaces would be
unreachable for IP communication. This is fixed.
Improved ROS
TM
System Diagnostics and Recovery Capability
Type:
Enhancement
Products:
All
ID:

1312

ROS
TM
implements continuous system monitoring which is able to detect and report system
anomalies (e.g. insufficient memory resources etc.). ROS
TM
also takes some actions to recover from
detected anomalies.
Those monitoring and recovery mechanisms are now significantly improved:
1. Assigning memory resources to device critical applications (such as RSTP) is prioritized.
2. Detection of and recovery from accidental system lockup (potentially caused by network
anomalies, such as DoS attack or traffic bursts) is improved.
3. Better system diagnostic information is available in case of system anomalies detection or/and
recovery activation.



ROS
TM
3.4.6 Release Notes
Changes In v3.4.2 (1211)
Added support for RS920L Serial Device Server
Type:
New Feature
Products:
RS920 series
ID:

1129
The RuggedVDSL RS920L is an industrially hardened serial device server and managed Ethernet
switch supporting Ethernet over VDSL (EoVDSL). The RS920L can be configured with up to 2
EoVDSL interfaces and 2 serial ports (RS485/RS422/RS232).
Added support for Long-Reach Ethernet-over-VDSL (EoVDSL) Interface
Type:
Enhancement
Products:
RS900L, RS930L, RS910L, RS920L
ID:

1108
As opposed to the previously supported 2.5Km distance EoVDSL interface, the Long-Reach EoVDSL
interface offers communication over a 5Km distance.
RS940G now supports 1000Base-T option for ports 7 and 8
Type:
Enhancement
Products:
RS940G
ID:

1232
Previously, RS940G was only available with 1000Base-X port type for ports 7 and 8. Now
1000Bsase-T option is also available.
Fixed problem when frequent link bouncing causes device blocking
Type:
Critical
Products:
All products except RMC30
ID:

694

Port Guard feature is implemented to protect against faulty end devices or mis-matched fiber ports
causing the system to detect a large number of link state change events in a short period of time (link
bouncing) causing network failure and device to become unresponsive since most of the system
resources are used to process these events. Device would not be able to keep even essential
network application properly running (such as RSTP).
If the Port Guard feature is enabled, it can detect abnormal number of link changes. Once problem is
detected, the port in question will be disabled to release other device resources to keep network
alive.



ROS
TM
3.4.6 Release Notes
Fixed unexpectedly closing TCP connections
Type:
Minor
Products:
All products
ID:

1120
Sometimes a just opened TCP connection (either incoming or outgoing) was unexpectedly closed by
ROS
TM
after about 5 seconds. This is fixed.
Fixed loading factory default configuration
Type:
Minor
Products:
All products
ID:

1127
Very rarely, running the Load Factory Default Configuration command could cause the ROS
TM

management session to hang and any IP connectivity with the device to be lost until the device
reboot. This is fixed.
F