Specifications

Clarifications and Known Behaviors
ExtremeWare 7.0 Release Notes 51
Traffic Crosses Layer 3 Boundary
If ingress and egress VLANs do not share a port, layer 3 traffic with a broadcast MAC and unicast IP
address is incorrectly forwarded to the default route across a layer 3 boundary (PD2-119375325).
Moving a sub-VLAN Client
When a client is moved from one sub-VLAN to another, the client may not be able to ping or
communicate through the super-VLAN until the client has cleared its IP ARP cache for the default
router or the switch has that IP ARP cache entry cleared (4977).
No Static ARP Entries
The use of Static ARP entries associated with superVLANs or sub-VLANs is not supported in this
release (5106).
VLAN Aggregation and ESRP
A sub-VLAN should not be configured to run ESRP. The system will allow you to enable ESRP on a
VLAN and then designate the VLAN as a sub-VLAN, but this is not a supported configuration (5193).
ARP Entry Age
The age of ARP entries changes to a large value when system time is changed (1-E7FIV).
Multinetting and Client Default Gateways
It is critical that clients attached to multinetted segments have their default gateways correspond to the
same subnet as their IP addresses and that subnet masks be configured correctly. Not doing so will
result in slow performance of the switch (4938).
Multinetting and the Show VLAN Stats Command
The show vlan stats <vlan_name> command is not supported on multinetted VLANs.
Multinetting and VRRP
Multinetting is not supported with VRRP.
RIP Routing
RIP V2 Authentication
The authentication feature of RIPv2 is not supported.
RIP in Conjunction with other Routing Protocols
It is recommended that RIP be enabled only on routers running with less than 10,000 routes from other
routing protocols, such as BGP or OSPF.