2-6 Riverstone Networks RS 2100 Switch Router Getting Started Guide
Software Overview
RS 2100 Introduction
•
Layer-4 application flows
QoS mechanisms supported on the RS 2100 include the following:
•
Traffic control queuing
•
Weighted random early detection
•
Weighted fair queuing
•
Strict priority queuing
•
QoS traffic control queues
•
ToS octet rewrites
•
Multi-Protocol Label Switching (MPLS) and the creation of LSPs for traffic engineering
Note
Traffic control queuing is based on assigning traffic to one of four queues: control,
high, medium, and low. Control traffic (routing protocols, and so on) has the
highest priority, high the second highest, and so on. The default priority for all
traffic is low.
2.3.7
Statistics
The RS 2100 can provide extensive statistical data on demand. You can access the following types of statistics:
Layer-2 RMON and MIB II Statistics
– Port statistics for normal packets and for errors (packets in, packets out,
CRC errors, and so on)
Layer-3 RMON v2 Statistics
– Statistics for ICMP, IP, IP-interface, IP routing, IP multicast, VLAN
Layer-4 RMON v2 Statistics
– Statistics for TCP and UDP
LFAP
– Light-weight File Accounting Protocol
Open APIs
– Slate and FAS Lite.
2.3.8
Web Hosting Features
The RS 2100 provides features that support and improve performance for high-capacity web access:
Load balancing
– allows incoming HTTP requests to a company’s web site to be distributed across several physical
servers. If one server should fail, other servers can pick up the workload.
Web caching
– allows HTTP requests from internal users to Internet sites to be redirected to cached web objects on
local servers. Not only is response time faster, since requests can be handled locally, but overall WAN bandwidth usage
is reduced.
Session persistence
– In certain situations where load balancing is being used, it may be critical that all traffic for the
client be directed to the same physical server for the duration of the session; this is the concept of
session persistence
.
TCP persistence
–
a binding is determined by the matching the source IP/port address as well as the virtual
destination IP/port address.
