Specifications

52 ExtremeWare 7.0 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
OSPF
Default Route Entries in the IP FDB
After a link transition, entries created by the OSPF originated default route are still in the IP FDB
(PD2-109830730, PD2-109830723).
Disable OSPF Before Adding or Removing External Area Filters
If you configure an OSPF area external filter on an ABR, and the filter is set to exclude routes that have
already been learned, an OSPF failure occurs. A workaround is to disable OSPF before adding or
removing OSPF external area filters (PD2-105170634).
BGP
Multi Exist Descriminator Not Compared
If a route is received from the same AS via EBGP and the IBGP peer, the switch does not compare the
multi exist descriminator. To avoid this, use the
enable bgp always-compare-med command
(PD2-126767407).
Route Dropped if Switch’s AS is First AS in Path
If the switch receives a route from an IBGP peer and the first AS number in the AS path sequence is the
switch’s own AS number, the route is dropped as a loop. To avoid this, do not prepend the switch’s AS
number to the AS path (PD2-126767401).
BGP Set Community Inadvertantly Advertised
The BGP Set Community NO_EXPORT_SUBCONFED is inadvertantly advertised to EBGP peers
(PD2-120403214).
Do Not Use configure access-profile Command to Set Community
Do not use the configure access-profile add command to set the BGP community , as the
command does not correctly set the value. Use the
configure route-map add command instead
(PD2-129638011).
Best Routes
If a new best route comes from an I-BGP peer, an older best route that comes from E-BGP won't be
withdrawn (PD2-108750310).
BGP Loops
If a switch detects a BGP route loop, it tears down the link to the neighbor that forwarded the route. To
avoid this, disable and re-enable BGP (PD2-99209507).