background image

Patch SB251-10 For SwitchBlade 4000 Series Switches and AT-9800 Series Switches

9

Patch SB251-10 for Software Release 2.5.1
C613-10361-00 REV J

Support has been added, to the MIB-2 interface MIB, for the port interface. 
This means that port counters can now be shown.

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.

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.

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.

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.

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.

The ADD IPV6 ND command now has a PORT parameter which means that 
it can be associated with the VLAN parameter.

Changes have been made to the 

SysDescription

.

TCP source and TCP destination ports were swapped when viewed in the 
GUI.   This issue has been resolved.

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.

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.

PCR: 03060

Module: CORE, SWI

                                  Level: 3

PCR: 03066

Module: SWI

                                  Level: 2

PCR: 03071

Module: CORE

                                  Level: 2

PCR: 03079

Module: IPG, SWI

                                  Level: 1

PCR: 03088

Module: SWI

                                  Level: 2

PCR: 03105

Module: FIREWALL

                                  Level: 3

PCR: 03112

Module: IPV6

                                  Level: 3

PCR: 03118

Module: CORE

                                  Level: 4

PCR: 03119

Module: CLASSIFIER

                                  Level: 4

PCR: 03138

Module: SWI

                                 L evel: 2

PCR: 03141

Module: IPG

                                  Level: 3

Summary of Contents for SB251-10

Page 1: ...s Switches Document Number C613 10354 00 Rev D available on the Documentation and Tools CD ROM packaged with your switch or from www alliedtelesyn co nz documentation documentation html WARNING Using...

Page 2: ...ansition to the Forwarding state This issue has been resolved The DISABLE SWITCH PORT and ENABLE SWITCH PORT commands were not interacting correctly with trunk groups This issue has been resolved so t...

Page 3: ...st entry in the VLAN Tag table was being corrupted when a valid L2MC table entry was incorrectly written to CAM entry 0 The source of this VLAN Tag table corruption has been removed IPX routes that we...

Page 4: ...ed ports are not affected by the trunk group port deletion All IP routes were being added to all switch instances This caused issues on SwitchBlade line cards that did not have enough CAM to store the...

Page 5: ...k group goes link down If the Master port in a trunk group goes link down and a Non Master port is still link up then STP will go through the Listening Learning Forwarding reconfiguration on the new M...

Page 6: ...the switch ports Features in SB251 06 Patch file details are listed in Table 5 Patch SB251 06 includes all issues resolved and enhancements released in previous patches for Software Release 2 5 1 and...

Page 7: ...control card and an M5 control card were installed and the M3 control card was acting as the Master This could cause unexpected restarts This issue has been resolved On a 48 port line card or a 32F ca...

Page 8: ...hough it was the first instance For example if 2 26 was configured as the mirror port the GUI mirror object would return 2 2 The first chip instance was not affected This issue has been resolved TCP6...

Page 9: ...d This issue has been resolved 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 b...

Page 10: ...pback test The ports in the BIST loopback test now remain in loopback Features in SB251 02 Patch file details are listed in Table 9 Patch SB251 02 includes all issues resolved and enhancements release...

Page 11: ...OLICY command This is the value of the port bandwidth used when the default traffic class percentage bandwidth is set on a QoS Policy Adding a layer 2 filter on a SwitchBlade did not block traffic to...

Page 12: ...t a higher level This issue has been resolved DHCP RENEW request messages are now unicast as defined in the RFC not broadcast VLAN tagged multicast packets were incorrectly being sent over untagged VL...

Page 13: ...nd slot to act as a slave has been resolved Support has been added to allow for multicasting to any number of overlapping VLANs up to the maximum number of multicast forwarding entries An issue with p...

Page 14: ...14 Patch Release Note Patch SB251 10 for Software Release 2 5 1 C613 10361 00 REV J...

Reviews: