Patch | 5 |
4)Not all routes were removed from the BGP route table when a peer was disabled.
These issues have all been resolved.
PCR: 40419 | Module: OSPF, IPG | Level: 2 |
If OSPF was configured using the command set ospf dyninterface=stub, to advertise dynamic interfaces such as PPPoE interfaces as stub links, the links were not being advertised as expected. This issue has been resolved.
PCR: 40420 | Module: BGP, IGP | Level: 2 |
In some circumstances, when a BGP peer became physically disconnected, subsequent deletion of routes could cause a switch reboot to occur.
PCR: 40419 | Module: OSPF, IPG | Level: 2 |
If OSPF was configured using the command set ospf dyninterface=stub, to advertise dynamic interfaces such as PPPoE interfaces as stub links, the links were not being advertised as expected. This issue has been resolved.
PCR: 40420 | Module: BGP, IGP | Level: 2 |
In some circumstances, when a BGP peer became physically disconnected, subsequent deletion of routes could cause a switch reboot to occur.
PCR: 40457 | Module: STP | Level: 2 |
If an STP disabled port was moved from one VLAN to another, it caused
STP to reconverge. This issue has been resolved.
PCR: 40460 Module: SWMX | Level: 2 |
Incorrect behaviour would occur if the switch was configured with a hardware filter that used a classifier matching on a VLAN, plus some additional IP Layer 3 or Layer 4 information (e.g. UDPDPort); and another filter using a classifier matching on just a VLAN. The result would be that only
PCR: 40465 | Module: PIM6, PIM4 | Level: 2 |
The switch could reboot when a user changed the Rendezvous Point
Candidate (RPC) priority in the PIM6 module. This issue has been resolved.
PCR: 40470 | Module: BGP | Level: 2 |
When BGP redistributed routes, locally imported routes were selected rather than peer learnt routes. This issue has been resolved.
Patch
