TXT

ReleaseNotes

By Calvin Cook,2014-07-04 23:02
7 views 0
ReleaseNotes

    DAS-3216/3216DC/3224/3224DC/3248/3248DC rev. B1 f/w ver. 2.42_4M

Release notes:

1.Bug Fix

    1.1.Fix old ADSL ÑPE troubles (DSL module updated)

    1.2.Fix “DSL Interface is Locked Up� troubles (ÑP and DP updated).

2.New features:

    2.1.Add Global DSL Profiles. Up 10 profile support simultaneously. 2.2.CLI enhancements. Add simple CLI mode (usermode)

    2.3.Packet Filtering enhancements:

    Support for Range in the named list interface. This allows configuration of more number of entries in a named list than 8, which is possible using discrete values.

    Removed the need to specify dimensioning on a per subrule type basis. Now the total number of subrules to be supported can be specified instead.

    Support for expression per rule. The expression can used to define logical “AND� and “OR� between sub-rules.

    Support for ARP subrule.

    IP TOS field enhancements: support for filtering on TOS field in IP header added and also a new action added to modify the TOS field in IP subrule. Note that IP header checksum is recomputed in case of modification.

    Support for rule action that facilitates congestion control through Buffer Admission Control.

    Support for “trap� and “control flow ID� in send-to-control and copy-to-control actions. These features allow flow control and prioritization of packets going to control plane. Support for rule actions to modify VLAN ID.

    Support for VLAN stacking.

    Support for Service VLAN ID and Service Priority fields in Ethernet Subrule.

    Support for actions to modify Service VLAN ID and Service Priority. Support for VLAN trunking. Out of total rules attached on an interface, the user can configure a subset to be applied on VLAN trunked packets using Context Subrule. This facilitates faster processing of VLAN trunked packets.

    Support for all actions in egress rule except ratelimiter. Support for dynamic enable and disable of rule statistics. Packet Classifier interface has been deprecated. Corresponding MOs and

    CLI commands are not supported from this release onwards. 2.4.Rate Limiting Enhancements

    Support for Flow Based Rate Limiting by utilizing filter rules to identify a flow.

    Support for byte-level rate limiters.

    Support for TRTCM (Two Rate Three Color Marker) algorithm. Support for a number of actions that can be taken on packets. 2.5.Added support for ATUC and ATUR traps through the SNMP Agent. 2.6.Support for VLAN Stacking feature.

    2.7.VLAN Cross-Connect feature.

2.Total supported features

Basic Bridging

    2.1.Ethernet Bridging � Basic bridging including address learning, aging and forwarding.

    2.2.Ethernet Bridging � Broadcast, Flooding / Dropping. 2.3.VLAN Bridging � Static VLAN membership definition. Configuration using GVRP.

    Support for following modes of bridging � configurable on a per VLAN.

    Residential Bridging: All traffic originating from the CPE ports are sent towards the uplink paths � without any destination address MAC lookup.

    Restricted (Full) Bridging: Switching of traffic from one CPE to another CPE is prohibited. In case traffic coming from one CPE / downlink is meant for another CPE / downlink, it is dropped - effectively achieving VLAN isolation between CPEs / stacked DSLAMs.

    Unrestricted (Full) Bridging allowing traffic between any two devices in the same VLAN.

    Dynamic modification of the bridging modes (mentioned above). 2.4.Support for VLAN stacking.

    2.5.Support for VLAN cross-connect.

    2.6.Link Aggregation

    Ethernet Trunking (Static Bonding).

    Ethernet Trunking based on LACP.

    2.7.Multicast support � using both � Static group configuration and through IGMP Snooping �

    Independent VLAN multicast (IVM).

    Shared VLAN Multicast (SVM).

    2.8.Multicast support � Support for IGMP v1,v2,v3 2.9.Multicast VLAN registration (MVR) support

    2.10.Multicast profile support

2.11.Multiple leave processing modes supported

    fast leave processing

    normal leave processing.

    2.12.Rack and Stack support on the Ethernet WAN interfaces. 2.13.Configurable limits on the number of MAC addresses that can be learnt / configured � both on a per-bridge-port basis as well as overall within the system.

    2.14.Configurability of flooding and broadcast enable / disable on a per-VLAN basis.

    2.15.Support for default VLAN.

    2.16.Configurability of the action to be taken when learning cannot happen due to forwarding table limits being reached. It can be configured to either „drop� or „forward�.

    2.17.Unregistered VLAN feature for supporting traffic from rack and stack on VLANs that are not configured in the system.

    2.18.“Forwarding table traps� are supported, which can be used by user application to keep themselves in sync with the changes in the forwarding tables. These traps are supported by packet filter interface.

Security

2.19.Throttling control

    Flood Control: Support for throttling flooded packets.

    Support for throttling broadcast packets.

    Support for throttling unregistered multicast flows.

    2.20.“Sticky� Bridge Ports: Ability to configure certain ports

    to learn MAC addresses on a semi-permanent basis. These learnt entries would be treated similar to the static entries and they will not be subject to aging or overwriting (moving). These may be deleted explicitly by management or by making the bridge port non-sticky after which aging will happen normally.

    2.21.Support for FDB conflict traps: When configured globally, a trap is generated when any MAC address learnt on one port appears as the source MAC address on another port (i.e. MAC address flapping). 2.22.Support for MAC address tracking: DAS-3224/3248 can be configured to track a global list of MAC addresses. When these MAC addresses move from one port to another a trap is generated. Whether packets from a particular bridge port should be subject to this tracking � is configurable. (It is possible to enable / disable this tracking on a per bridge port basis). This may be used to prevent denial of service from certain MAC addresses.

    2.23.MAC Address Access Control List

Per bridge port MAC accept list.

    Global MAC address deny list � The application of the global MAC address deny list can be enabled / disabled on a per bridge port basis.

    2.24.IP Address Access Control List

    Per bridge port Accept OR Deny list.

    2.25.Multiple queues are supported towards the Control Plane � one per DSL port. This ensures that traffic towards the Control Plane from one port will not affect traffic from another port. This mitigates the impact of a denial-of-service attack from one of the CPE ports.

Packet Filtering

    2.26.Support for Rule based � multistage - Packet Filtering: Packet filtering can be used to implement filtering required of NetBeui, NetBios, DHCP, 802.1x and other protocols.

    2.27.Support for atomic modification of rule sequence. The user can replace a rule sequence of a stage on an interface by another sequence in one step.

    2.28.Support for “Copy to Control� feature is provided in generic filter. A copy of the packet is forwarded to control plane and no further rule of that stage is applied.

    2.29.Support for Egress filtering for Unicast, broadcast and multicast traffic.

    2.30.Support for short-circuiting from a stage. It allows a User to specify that if a particular condition is met, no further filtering should be applied.

    2.31.Support for L3 Header for non IP packets, Ethernet DSAP, SSAP fields for filtering LLC packets, Egress Generic Subrule and Ethernet subrule, and IP Option +.

    2.32.Support for Generic subrule for all header types except Ethernet at the egress.

    2.33.Support for Multiple actions per filter rule.

    2.34.Support in "Generic filter sequence table" to support interface as "Alleth" for aggregated Ethernet interfaces exists.

    2.35.Support for ranges in the named list interface.

    2.36.Support for a “single� table space accommodating sub-rules

    of different types.

    2.37.Support for expression per rule. The expression can used to define logical “AND� and ”OR� between sub-rules.

    2.38.Support for Range in the named list interface. This allows configuration of more number of entries in a named list than 8, which is possible using discrete values.

    2.39.Support for ARP subrule.

    2.40.IP TOS field enhancements: support for filtering on TOS field in IP header added and also a new action added to modify the TOS field in IP subrule. Note that IP header checksum is recomputed in case of modification.

    2.41.Support for rule action that facilitates congestion control through Buffer Admission Control.

    2.42.Support for rule actions to modify VLAN ID.

    2.43.Support for VLAN stacking.

    Support for Service VLAN ID and Service Priority fields in Ethernet Subrule.

    Support for actions to modify Service VLAN ID and Service Priority. 2.44.Support for VLAN trunking. Out of total rules attached on an interface, the user can configure a subset to be applied on VLAN trunked packets using D-Link Subrule. This facilitates faster processing of VLAN trunked packets.

    2.45.Support for all actions in egress rule except ratelimiter. 2.46.Support for dynamic enable and disable of rule statistics.

QoS

    2.47.Prioritized Bridging � Support for multiple queues per port Eight (8) queues supported per ATM port.

    Eight (8) queues supported per physical Ethernet port.

    2.48.Multiple per-queue scheduling mechanisms. In addition to strict priority scheduling � we also support

    Minimum and maximum bandwidth guarantees

    Weighted excess bandwidth distribution.

    2.49.Input Rate Limiting (IRL) on a per-AAL5 interface. 2.50.Buffer admission control triggered using IRL.

    2.51.Output Rate Limiting (ORL) on a per ATM-port basis. 2.52.Output Rate Limiting (ORL) on a per-Physical Ethernet Interface basis.

    2.53.Packet priority to traffic class mapping table supported on a per egress bridge port.

    2.54.Multiple mechanisms of prioritizing incoming traffic on a per-bridge port basis.

    Using Source Port configuration (for untagged packets). Using Packet Classifier actions.

    Using priority regeneration table (mapping ingress priority to egress priority).

    Combinations of the above.

    2.55.Multiple mechanisms of 802.1p re-tagging of outgoing traffic on a per ingress bridge port basis.

    Using Source Port configuration (for untagged packets).

Using Classifier actions.

    Using priority regeneration table (mapping ingress priority to egress priority).

    Combinations of the above.

    2.56.Ability to share the same profile across multiple (similar) ports. 2.57.Support for dynamic modification of ORL supported on ATM and Ethernet interfaces.

    2.58.Rate Limiting Enhancements

    Support for predefined flows at bridge level � broadcast, unknown unicast and unregistered multicast.

    Support for Flow Based Rate Limiting by utilizing filter rules to identify a flow.

    Support for byte-level and packet-level rate limiters.

    Support for SR2CM (Single Rate Two Color Marker) and TRTCM (Two Rate Three Color Marker) algorithms.

    Support for a number of actions that can be taken on packets.

PPPOA to PPPoE inter-working

    2.60.Support for PPPoE Client functionality towards the WAN side. 2.61.Support for PPPoA to PPPoE tunnels on VC Muxed and LLC muxed VCs. PPPoE session establishment, data forwarding and PPPoE session teardown are supported.

    2.62.Support for relaying PPP packets from CPE to WAN side and vice versa.

    2.63.Bridging shall happen normally on bridge ports created over the PPPoE interfaces.

    2.64.Support of configurability of whether a given VC carries EoA or PPPoA traffic.

    2.65.Support for configuring multiple Service-Name and AC-Name tags. 2.66.Support for configuring an association between a PPPoE interface and a Service-Name tag; and PPPoE interface and an AC-Name tag. 2.67.Management interface for configuring PPPoE session parameters and deleting an existing PPPoE session.

    2.68.Support for configurability of Inactive sessions to be torn down or not.

    2.69.Support for Generic Filtering rules on the PPPoA frames is provided for the support for IP / TCP / UDP / IGMP and generic sub-rules. Support is also provided for filtering PAP / CHAP packets.

    2.70.Support for PPPoE , ALLPPPOE and ALLCPE interface in generic filter.

    2.71.Support for transmit and receive of PPPoE (Ethernet type II and 802.3 formats) and PPP packets using Packet filter interfaces.

IPOA to IPOE Tunneling

    2.72.Support for RFC 2684 Routed encapsulated IPOA interface configuration.

    2.73.Support for IPoA to IPoE tunnels on VC muxed and LLC muxed VCs. 2.74.Conversion of IPoA frame into an IPoE frame and vice versa. 2.75.Source MAC address to be used for IPOE frames can be configured per port using profiles.

    2.76.Support for relaying IPoA packets from CPE to WAN side and vice versa.

    2.77.In the upstream frames from IPOA interface are forwarded on the basis of the default route. The packet is sent to the MAC address of Next hop of the default route.

    2.78.The packet in the above case would follow the bridging logic for selecting the port on which the packet has to finally go. 2.79.DAS-3224/3248 resolves the MAC address of the next hop IP address dynamically.

    2.80.The MAC address of the next hop IP Address can also be statically configured.

    2.81.IP host based lookup in the downstream direction to determine the IPOA interface on which the packet has to be forwarded.

    2.82.Proxy ARP support for ARP requests for IPOA interfaces coming from the ISP side.

    2.83.Extension of the Auto Sensing Framework to support detection of IPOA connections.

    2.84.Extension of Generic Filtering for IPOA to IPOE tunneled packets. 2.85.Support for ALLIPOE interface in the generic rules. 2.86.Support for transmit and receive of IPoA (Ethernet type II and 802.3 formats) and IPoE packets using Packet filter interfaces. 2.87.Support of no IP forwarding table lookup if the MAC address on a port is unique. This is controllable per IPOA interface.

     Relay features

    2.88.DHCP Relay Option 82 support

    2.89.PPPoE Intermediate Agent Support

ATM features

    2.90.Support for Raw AAL5 interface for remote CPE management. 2.91.Support for OAM - I.610 (F5) � end-to-end and segment loop back.

    2.92.Support Dual End Loop Test (DELT)

    2.93.RDI and AIS cell support in ATM OAM.

    2.94.Last seen unknown VPI / VCI on an ATM port is exported to the user.

2.95.Support for single-cell AAL5 frames.

    2.96.Support for 8 output queues per ATM port. This allows the configuration of up to eight different types of service classes.

Miscellaneous

    2.97.Support for Binary Fallback: Multiple versions of Control Plane and Data Plane software can reside on the FLASH. DAS-3224/3248 will automatically use the correct backup combination � should the primary combination fail to come up for some reason.

    2.98.Remote firmware upgrade support.

    2.99.Remote config update support ( over FD.cfg operations) 2.100.Add CLI command reboot config network in safe mode (support remote update configuration file after remote firmware upgrade) 2.101.Debugging feature: System crash and reboot information provides complete and detailed information of state of the system and cause of crash.

    2.102.Support for ACL Traps in SNMP.

    2.103.Support for high capacity counters � 64 bit counters provided for CPE side interfaces for ATM, ATM VC, EOA and PPPoE interface types.

    2.104.Support for Ethernet error counters based on RFC 3635 for dot3StatsTable.

Report this document

For any questions or suggestions please email
cust-service@docsford.com