background image

Patch 86253-07 For Rapier Series Switches

SHOW IGMPSNOOPING ROUTERADDRESS

13

Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E

The port counters were not incremented: 

ifInDiscards

ifinErrors

ifOutDiscards

ifOutErrors

This issue has been resolved.

The following SNMP MIB objects could not be set: 

Dot1dStpPriority

Dot1dStpBridgeMaxAge

Dot1dStpBridgeHelloTime

Dot1dStpBridgeForwardDelay

This issue has been resolved.

DHCP was incorrectly using the directly connected network interface 
source IP address as the source IP address of packets it generates. This issue 
has been resolved. DHCP now uses the local IP address as the source 
address for the packets it generates when a local IP interface address is set. 
If a local IP interface address is not set, then it uses the IP address of the 
interface where packets are sent from as the source address.

When the device rebooted with PIM or PIM6 enabled, it sometimes did not 
send a 

Hello

 packet quickly enough. This issue has been resolved.

When a DHCP client was in the renewing state, and it sent a DHCP

 Request

the device did not add the ARP entry to the ARP table. Instead, the device 
generated an ARP

 Request

 in order to transmit the DHCP

 Ack

. This caused 

a broadcast storm in the network when the client kept sending DHCP 

Request

s. This issue occurred because the 

ciaddr

 field, not the 

giaddr

 field, 

was checked in the 

Request

 packet when the device determined whether to 

add the ARP entry. This issue has been resolved.

The current implementation of RSTP conforms to the IEEE standard 
802.1w-2001. However, several minor deviations from the standard are 
possible without having a functional impact on the behaviour of RSTP. 
These changes are useful for debugging RSTP, and tidy up aspects of RSTP 
that sometimes have no purpose. The following three variations have been 
implemented: 

The 

Learning

 and 

Forwarding

 flags are set in BPDUs to indicate the state 

of the Port State Transition state machine. 

The 

Agreement

 flag is set in BPDUs only when a Root Port is explicitly 

agreeing to a proposal from a designated port. Do not set the 

Agreement

 

flag in BPDUs transmitted by Designated Ports. 

PCR: 31145

Module: SWI

                                  Level: 3

PCR: 31146

Module: SWI

                                  Level: 3

PCR: 31147

Module: DHCP

                                  Level: 3

PCR: 31148

Module: PIM, PIM6

                                  Level: 2

PCR: 31152

Module: DHCP

                                  Level: 2

PCR: 31154

Module: STP

                                  Level: 4

Summary of Contents for 86253-07

Page 1: ...on and Tools CD ROM packaged with your switch or from www alliedtelesyn co nz documentation documentation html WARNING Using a patch for a different model or software release may cause unpredictable r...

Page 2: ...was no default policy route This issue has been resolved Now a route whose policy exactly matches the policy of the packet is selected If an exact match does not exist a route with the default policy...

Page 3: ...layed when they should not have been The log messages were Vrrp 1 Vlan vlan2 10 Port Failed decrementing priority by 20 Vrrp 1 Vlan vlan2 1 Port up incrementing priority by 2 This issue has been resol...

Page 4: ...ssue has been resolved If DHCP clients do not respond to echo requests the DHCP server can not detect an addressing conflict so may offer inuse addresses to clients This issue has been resolved This P...

Page 5: ...in NTP Client mode the SHOW TIME command sometimes displayed the incorrect time This issue has been resolved The device sometimes rebooted when OSPF on demand was enabled for PPP This issue has been r...

Page 6: ...selecting blocks and scrolling up This issue has been resolved When RIP demand mode was enabled and one interface changed to a reachable state the triggered Request packet was not sent from that inte...

Page 7: ...utes were forwarded even if there was no default policy route This issue has been resolved Now a route whose policy exactly matches the policy of the packet is selected If an exact match does not exis...

Page 8: ...to the ADD FIREWALL POLICY RULE and SET FIREWALL POLICY RULE commands An IP address range for the IP parameter is now only accepted when enhanced NAT is configured An IP address range for GBLREMOTE pa...

Page 9: ...length could not be transferred using TFTP This limit has now been raised to 1000 characters to match the maximum command line length The SHOW FILE command caused an error when the displayed file had...

Page 10: ...g message was generated each time a directed broadcast packet was deleted This issue has been resolved Log messages are now rate limited to a maximum of one log message every 10 seconds for a directed...

Page 11: ...d multicast addresses i e 2240 0 1 to 224 0 0 255 are treated as router multicast addresses If DEFAULT is specified the following addresses are treated as router multicast addresses IGMP Query 224 0 0...

Page 12: ...ed BPDUs at the rate specified by the local helloTime value when they were not the root bridge This is the behaviour specified in 802 1w 2001 This behaviour can cause instability in the spanning tree...

Page 13: ...quest the device did not add the ARP entry to the ARP table Instead the device generated an ARP Request in order to transmit the DHCP Ack This caused a broadcast storm in the network when the client k...

Page 14: ...ng ICMP packets even when enhanced fragment handling was enabled on the firewall If a long packet is passed to the firewall for processing the firewall chains the fragmented packets The firewall can p...

Page 15: ...h 86253 04 includes all issues resolved and enhancements released in previous patches for Software Release 2 5 3 and the following enhancements MLD snooping is now supported on AT 9800 Series Switches...

Page 16: ...L NETUNREACH HOSTUNREACH REDIRECT SHOW IP ICMPREPLY For details see Enable and Disable ICMP Messages on page 28 Interoperating with other vendors implementations of ISAKMP was occasionally causing err...

Page 17: ...te was deleted even if it contained other routes This issue has been resolved The time recorded when a user logged in was overwritten when the same user logged in a second time while the original conn...

Page 18: ..._SUBNET RFC 2407 4 6 2 7 ISAKMP was using the ID_IPV6_ADDR RFC 2407 4 6 2 6 option instead This issue has been resolved MLD and MLD Snooping accepted MLD Query packets with a hop limit greater than 1...

Page 19: ...resolved PIM SM did not establish a BSR candidate between two AR720 routers with PPP over SYN This issue has been resolved When INGRESSLIMIT parameter in the SET SWITCH PORT command was set to 64kbps...

Page 20: ...was executed when a trace was already in progress This issue has been resolved The layer 3 filter was matching a layer 3 packet incorrectly when the egress port was specified by the filter This issue...

Page 21: ...rface s actual IP address If this situation occurred traffic was redirected back out the public interface This issue has been resolved Software emulation of layer 3 hardware filtering was not operatin...

Page 22: ...XCHANGE command This issue has been resolved DHEXPONENTLENGTH parameter in the CREATE ISAKMP POLICY command was not accepted when creating ISAKMP policies that used IPv6 This issue has been resolved W...

Page 23: ...op This issue has been resolved When executing the SET DHCP POLICY DELETE DHCP POLICY and DESTROY DHCP POLICY commands memory was not de allocated correctly This issue has been resolved If ports were...

Page 24: ...olved Features in 86253 03 Patch file details are listed in Table 4 Patch 86253 03 includes all issues resolved and enhancements released in previous patches for Software Release 2 5 3 and the followi...

Page 25: ...he source of a mirror port did not disable the mirror port This issue has been resolved A fatal error occurred if the number of DVMRP interfaces being added exceeded the limit This issue has been reso...

Page 26: ...abled 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 s...

Page 27: ...FC 2460 s requirement to align packet sizes to 8 octets The DHCP server did not send a DHCPNAK message when a previously statically assigned IP DHCP entry was again requested by a client This issue ha...

Page 28: ...ork Unreachable This message indicates that the switch does not know how to reach the destination network Host Unreachable This message indicates that the switch does not know how to reach the host IC...

Page 29: ...ALL NETUNREACH HOSTUNREACH REDIRECT Description This command enables ICMP reply messages If ALL is specified all configurable ICMP message replies are enabled If NETUNREACH is specified all network un...

Page 30: ...MLD snooping is independent of the MLD and Layer 3 configuration so an IPv6 interface does not have to be attached to the VLAN and MLD does not have to be enabled or configured MLD snooping is enabled...

Page 31: ...prevent specified ports from acting as IGMP all group ports and specify which ports are allowed to behave as all group entry ports by using the ENABLE IP IGMP ALLGROUP command For example consider a...

Page 32: ...rmation about IGMP use the command SHOW IP IGMP See Also ENABLE IP IGMP ALLGROUP DISABLE IP IGMP ALLGROUP IGMP Protocol Status Enabled Default Query Interval 125 secs Default Timeout Interval 270 secs...

Page 33: ...rts If ALL is specified all ports are able to behave as all group entry ports The default is ALL Examples To enable ports 1 5 and 7 to behave as all group entry ports use the command ENABLE IP IGMP AL...

Page 34: ...07 for Software Release 2 5 3 C613 10382 00 REV E Availability Patches can be downloaded from the Software Updates area of the Allied Telesyn web site at www alliedtelesyn co nz support updates patche...

Reviews: