Filter
Top Products
Patch 86251-08 For Rapier Series Switches 23
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
When changing from RSTP to STP mode, the STPCOMPATIBLE option for
the RSTPTYPE parameter incorrectly appeared in the dynamic
configuration. Also, when changing from RSTP to STP mode or vice versa,
disabled STP ports did not remain in the disabled state. These issues have
been resolved.
Previously, VJC supported 136 interfaces and PPPoE supported 256 PPP
interfaces, but the device software supported up to 512 PPP interfaces. This
discrepancy sometimes caused a fatal error and prevented PPPoE interfaces
with a PPP index greater than 255 from working correctly. This issue has
been resolved, so that VJC and PPPoE now fully support 512 PPP interfaces.
BGP routes that were added after a summary aggregate route had been
formed were not suppressed. This issue has been resolved: all routes added
after summary aggregate route creation are also now suppressed.
The SHOW BGP ROUTE command displayed unselected routes as the
"best" route, until they had been processed. This issue has been resolved.
When a single route was deleted from an aggregate route, the aggregate
route was deleted, even if it contained other routes. This issue has been
resolved.
A field has been added to the SHOW IP command output that displays
whether the IP ARP log is enabled or disabled.
When an oversize packet (PMTU) was received, an error message was not
returned, even when IPv6 flow was enabled. This issue has been resolved.
If a port went down, the port was deleted from the appropriate static IGMP
associations but was not added back again when it came back up. Similarly,
static IGMP associations were automatically deleted but not added back
when IP or IGMP was disabled. These issues have been resolved. You can
now create IGMP associations before enabling IGMP, and they will become
active when IGMP is enabled.
The maximum number of firewall sessions had decreased since software
release 86s-241. This issue has been resolved.
If a ping was active and the IP configuration was reset, subsequent pings
were sent out the wrong interface. This issue has been resolved.
Executing a ping to the IP address 0.0.0.0 did not return an
invalid
destination address
error message. Also, when the TRACE command
was executed for local addresses, it timed out after 90 seconds. These issues
have been resolved.
PCR: 03720 Module: STP Level: 2
PCR: 03722 Module: PPP, VJC Level: 3
PCR: 03723 Module: BGP Level: 2
PCR: 03728 Module: IPG Level: 4
PCR: 03733 Module: IPV6 Level: 3
PCR: 03738 Module: IPG Level: 2
PCR: 03741 Module: FIREWALL Level: 3
PCR: 03743 Module: IP Level: 3
PCR: 03744 Module: PING Level: 3