Patch | 9 |
PCR: 03060 | Module: CORE, SWI | Level: 3 |
Support has been added, to the
This means that port counters can now be shown.
PCR: 03066 | Module: SWI | Level: 2 |
If a hardware filter was added to the switch, with a source VLAN and a destination port of 1, then a host connected to the switch could not PING a host on a different port. This issue has been resolved.
PCR: 03071 Module: CORE | Level: 2 |
An unexpected restart that occurred when upgrading a SwitchBlade from
Release 2.4.4 to Release 2.5.1 was caused by NVS generating an SNMP trap.
This issue has been resolved.
PCR: 03079 | Module: IPG, SWI | Level: 1 |
Static routes were occasionally not added to all hardware tables across all instances. This would affect connectivity if an instance had a default route added to its table that pointed out one of its ports. This issue has been resolved.
PCR: 03088 | Module: SWI | Level: 2 |
Ports could not be added to the default VLAN after a hotswap, if the default VLAN was Protocol, Subnet, MAC address, or Limited protocol based. This issue has been resolved.
PCR: 03105 | Module: FIREWALL | Level: 3 |
Incorrect handling of TCP sessions, and poor load balancing performance could be caused by TCP virtual balancers not selecting a new resource if required. This issue has been resolved.
PCR: 03112 | Module: IPV6 | Level: 3 |
The ADD IPV6 ND command now has a PORT parameter which means that it can be associated with the VLAN parameter.
PCR: 03118 | Module: CORE | Level: 4 |
Changes have been made to the SysDescription.
PCR: 03119 | Module: CLASSIFIER | Level: 4 |
TCP source and TCP destination ports were swapped when viewed in the
GUI. This issue has been resolved.
PCR: 03138 | Module: SWI | L evel: 2 |
Packets that were sent out a default route could have an incorrect source IP address, if the interface route to the destination IP address existed but was down. This issue has been resolved.
PCR: 03141 | Module: IPG | Level: 3 |
Packets could be sent with an incorrect source address if a route was added to a VLAN and another VLAN had an IP interface configured that was in the same subnet as the route. This issue has been resolved.
Patch