14ENTERPRISE OS SOFTWARE VERSION 11.4 RELEASE NOTES
occur during, for example, TFTP file transfers using Large Blocksize Negotiation (RFC 1783).
Each fragmented packet contains an IP Identification (ID) number that is used for re-assembly. When the first fragment arrives, the ID is stored in the NAT session that has already been setup for the TFTP file transfer, so when subsequent fragment’s arrive with no UDP header, a search is made for the session by ID and the relevant IP address. After the session is found, the destination and source ports are known and NAT can translate.
BGP-4 & IPv6 added to Multiprotocol Packages for OfficeConnect
NETBuilder & SuperStack II NETBuilder SI & PathBuilder S400 devices
Previously, BGP-4 & IPv6 was available only on the NETBuilder II and PathBuilder S5xx devices. Starting with 11.4, BGP-4 and IPv6 are supported on the OfficeConnect NETBuilder and SuperStack II NETBuilder SI (Ethernet only) bridge/routers, as well as on the PathBuilder S400 WAN convergence switch. BGP-4 and IPv6 will be available only on the multiprotocol packages for these platforms.
RSVP & RSVP Proxy added to Software Packages for OfficeConnect
NETBuilder & SuperStack II NETBuilder SI & PathBuilder S400 devices
Previously, RSVP was available only on the NETBuilder II and PathBuilder S5xx devices. Starting with 11.4, RSVP and RSVP Proxy are supported on the OfficeConnect NETBuilder and SuperStack II NETBuilder SI (Ethernet only) bridge/routers, as well as on the PathBuilder S400 wAN convergence Switch.
Traffic Shaping & QoS Traffic shaping and Quality of Service (QoS) features include Bandwidth on Features Demand with Incoming Traffic, and IP Quality of Service (IPQoS).
Bandwidth on Demand with Incoming Traffic
Bandwidth on Demand is a facility that provides supplementary bandwidth above the normal bandwidth levels specified by the user whenever traffic congestion is detected. In previous releases, only the transmitted traffic load was used to control this feature; with the 11.4 release, incoming traffic is also monitored. The need to monitor incoming traffic for Bandwidth on Demand appears in such situations as when a router that is connected to an ISP downloads a web-page. The incoming traffic bandwidth consumption would be high; it would be desirable at this point to add more bandwidth to accommodate the desired burst in traffic.
IP Quality of Service (IPQoS)
With the enormous growth in network traffic, robust QoS is required to ensure mission-critical and real-time application traffic will get adequate network resources to traverse the network regardless of the competing demands for bandwidth by other applications.
Policy-based QoS management will enable network managers to control bandwidth allocation and service levels on IP traffic flows. Traffic flows can be metered and policed on a per policy base to ensure its bandwidth consumption does not exceed the defined rate limits. When multiple flows are aggregated into a service class, rate limiting protects conforming flows from the aggressive flows hogging network resources that may lead to a denial of service. Flows can also be policed to ensure correct marking of the IP/TOS-byte in the IP header as per policy.
