Datasheet

Alcatel-Lucent Page 78
OmniSwitch 9000
the same scope (the one for the primary interface)
With VRRP and Multinetting, you can still configure multiple instances to load balance the master role
among the sub-netted interfaces.
Routing In Multinetting Routing protocols (RIP, OSPF, and BGP) are supported in a multinetted environment. The routing
interfaces are now based on ip interfaces, instead of the VLANs. Therefore, routing protocols are
totally independent of VLANs and their data structures are maintained as part of an array indexed by ip
interface only. There is no difference between running a routing protocol on an interface part of a
multinetted vlan or a regular interface. Each subnet (interface) on the multinetted vlan can run its own
routing protocol.
Multicast Routing In Multinetting The multicast routing protocols will be supported on one interface per VLAN. One interface
designated the primary interface, will be used for the multicast routing protocols. The multicast routing
protocols will not allow configuration on any non-primary interfaces. By default the first interface is
the primary interface. DVMRP and PIM-SM will only allow configuration on the primary interface of
a VLAN. This is to ensure consistency between the multicast routing protocols (DVMRP, PIM-SM,
IPMRM), IPMS and IGMP.
Layer-3 Routing (IPX)
Routes 1K Routes
1K Host entries
IPX Routing 64 IPX interfaces
Static routing (256 routes)
RIP/SAP, 1K routes
5000 RIP and SAP entries each are supported.
IPX routing is limited to 8000 packets per second per NI.
Each NI can independently route up to 8000 p/s.
Policy/QoS
QoS / ACLs Features summary:
• 802.1p classification 4.1.8
• TOS/DSCP classification 4.1.9
• Ethertype classification
• IP protocol classification
• ICMP type and code classification
• TCP Flag classification and “established” for implicit “reflexive” tcp flows
• “qos apply” will not impact existing flows
• Port disable rules to shutdown a port when incoming packets matches a rule
• Rule logging
• Port redirect action to force a packet to be sent out on a given port
• User port profiles to filter and shutdown ports for BPDUs, IP spoofing and routing
protocols (RIP, OSPF, BGP)
• DropServices to drop tcp/udp ports
• IGMP ACLs
• L2/L3/L4 QoS fully supports IP multicast traffic (priority, bandwidth shaping..)
• 8 hardware queues per port
QoS Conditions & Actions supported The following types of conditions are available:
• L1 conditions: source port, destination port, source port group, destination port group
• L2 conditions: source Mac, source Mac group, destination Mac, destination Mac group,
802.1p, ethertype, and source vlan (Destination vlan is not supported).
• L3 conditions: ip protocol, source ip, source network group, destination ip, destination
network group, TOS, DSCP, ICMP type, ICMP code.
• L4 conditions: source TCP/UDP port, source TCP/UDP port range, destination TCP/UDP
port, destination TCP/UDP port range, service, service group, tcp flags
• IP multicast condition: An ip multicast condition is used for IGMP ACLs. The multicast ip
is actually the multicast group address used in the IGMP report packet.
IP multicast can be combined with destination port, destination vlan, destination Mac,
destination ip, that are the port/vlan/Mac/ip of the device that sent the IGMP report
The following actions are available:
• ACL (disposition drop/accept – default is accept)
• Priority
• 802.1p/TOS/DSCP Stamping
• 802.1p/TOS/DSCP Mapping
• Maximum bandwidth
• Redirect Port
Note: Condition combinations and Action combinations are also supported.
Priority Queues Eight hardware based queues per port
Traffic Prioritization Flow based QoS in hardware (L1-L4)
Internal & External (aka remarking) prioritization