================================================================ REVISION NOTES FOR BAYRS VERSION 14.20 REVISION 3 ================================================================ Site Manager compatibility: BayRS version is managed by Site Manager version 14.20 Rev. 3 -------> 14.20, 14.20 Revisions 1 and 2 14.20 Rev. 2 -------> 14.20, 14.20 Revisions 1 and 2 14.20 Rev. 1 -------> 14.20, 14.20 Revisions 1 and 2 14.20 -------> 14.20, 14.20 Revisions 1 and 2 ========================================================================= BayRS and BCC Version 14.20 Revision 3 corrects the following problems: ========================================================================= CR 127613-1: DLSw If you configure a DLSw Protocol Priority Peer Queue for a peer and then add a DLSw Protocol Priority traffic filter to that peer, the router will fault. CR 129601-2: Octal Sync If an octal sync port receives bursts of errored frames from the network, the port will eventually hang. CR 130221-1: ARN/FT1 Sending loopback codes to the FT1 interface on an ARN does not cause the FT1 interface to go into the loopback state. CR 142219-1: Passport 2430/FT1 Sending loopback codes to the FT1 interface on a Passport 2430 does not cause the FT1 interface to go into the loopback state. CR 130235-2: ARN/FT1 When PPP echo request is enabled on the FT1 interface on an ARN, the FT1 interface will not stay in the loopback state after receiving loopback codes. CR 142223-1: Passport 2430/FT1 When PPP echo request is enabled on the FT1 interface on a Passport 2430, the FT1 interface will not stay in the loopback state after receiving loopback codes. CR 142220-1: Passport 5430/FT1 Sending loopback codes to the FT1 interface on a Passport 5430 does not cause the FT1 interface to go into the loopback state. CR 142226-2: Passport 5430/FT1 When PPP echo request is enabled on the FT1 interface on a Passport 5430, the FT1 interface will not stay in the loopback state after receiving loopback codes. CR 145449-1: ARN/FT1 The FT1 interface on an ARN may not always react correctly to loopback and fdl loopback codes when they are received on the FT1 interface. CR 145450-1: Passport 5430/FT1 The FT1 interface on a Passport 5430 may not always react correctly to loopback and fdl loopback codes when they are received on the FT1 interface. CR 145751-1: NAT When NAT is enabled, the router does not process RIP 1 updates with a source address of 255.255.255.255. CR 146507-1: ARN/FT1 The ARN MIB variable wfDs1E1PortLoopbackState is not being reset back to 1 (no loop) when loopback mode is terminated on the FT1 interface. CR 146697-1: Dial-on-Demand The one-way authentication feature on a dial-on-demand ISDN circuit is not working correctly. CR 147266-1: IGMP A Passport 5430 router running IGMP relay faults when a DVMRP multicast router is downstream from that router. CR 147534-3: Frame Relay Setting the queue limit on one virtual circuit causes the queue limits on other virtual circuits that have had their queue limits modified to revert to the default settings. CR 148172-1: Frame Relay Using protocol priority and traffic shaping on low speed links over a high speed physical line results in low queue starvation. CR 149031-1: Passport 5430/FT1 If an FT1 module on a Passport 5430 is configured as a frame relay switch, and the physical connection is disconnected, the sync LED for the FT1 stays on and the state of upper level protocols, such as IP, remain up. If you reconnect the link and then disconnect it again, the router does not register the event in the log. CR 149111-1: Passport 5430/FT1 If an FT1 module on a Passport 5430 is configured with PPP, and the physical connection is disconnected from the FT1 module for an extended period of time and then reconnected, the log reports that an LCP request is being sent. However, the show sync stats does not show any increment in receive or transmit frames and the upper level protocols, such as IP, remain down.