REVISION NOTES FOR BAYRS VERSION 13.01 REVISION 1



Site Manager compatibility:
BayRS version is managed by Site Manager version
13.01 Revision 1 --------------------> 7.01 and 7.01 Revision 1

13.01 Revision 1 is Year 2000 Compliance Certified by Bay Networks. It has successfully passed Bay Networks Test Procedure which tests conformance to Bay Networks Year 2000 compliance definition, both of which can be found at Bay Networks Year 2000 Web site at http://www.baynetworks.com/year2000/.


13.01 Revision 1 corrects the following problems:



CR 26899: IPX
Triggered updates can only be enabled/disabled per interface. Added Option 3 to wfIpxRipCircImmedUpdate and wfIpxSapCircImmedUpdate, which by default uses the new global parameter. The new global parameter is wfIpxAdvSysGlobalTrigUpdate, which is enabled as default.

CR 27734: GAME
The ASN2 router reports that a redundant power supply failed when one does not
exist. A new MIB parameter (wfRASNRPSUPresent) was added to disable the
logging of the message.

CR 29731: TI
The configuration file size is set to 0 bytes when there is insufficient space to save it.

CR 29756: OSPF
An OSPF router might unicast link-state updates unnecessarily to its
neighbors.

CR 30166: BISYNC
Bisynchronous transmission does not work on an octal sync card interface when configured for ASCII Character mode.

CR 30999: FTP
Using FTP to transfer large files (3+ MB) from an ARN to a PC running Windows 95 over frame relay dial-on-demand can cause the ARN router to fault.

CR 31900: IP Traffic Filters
When an IP traffic filter is enabled on an ATM interface, the number of hops in the TTL (time-to-live) counter decreases by 2 on packets that are forwarded by the router.

CR 32388: Scripts
The Technician Interface command "show hardware slots" does not display net module position 4 in the ASN router platform.

CR 33256: X.25
If you reboot the remote router or a link failure occurs, PVCs on the local router do not recover. The problem does not occur when both routers are rebooted at the same time.

CR 34296: BGP
Allow BGP to identify two additional AS segment types (AS_CONFED_SET and AS_CONFED_SEQUENCE) as specified in RFC 1965, "BGP Autonomous Confederations for BGP." BGP will recognize an update containing these segment types, drop the update, log a warning message that an update with a Confederation segment type was received, and continue to maintain the peer session.

CR 35523: ISDN
When configured for a server one charge call ID and the router (callback server) is going to set up the call, the router experiences a bus error.

CR 71111: MIB-2
When you boot the router it creates MIB-2 ifEntry instances for logical circuits only. RFC 1213 requires that ifEntry instances be created for logical circuits (such as, IP), the associated PVC, and the underlying physical interface.

The following MIB attributes all remain at zero: ifMtu, ifSpeed, ifPhysAddress, ifInErrors, ifOutErrors, and ifOutQlen. The following are the only MIB attributes that display valid data: ifIndex, ifAdminStatus, ifOperStatus, ifLastChange, ifInOctets, ifOutOctets, ifInDiscards, and ifOutDiscards.

CR 72834: BCC - IP
The BCC "show ip" command truncates circuit names exceeding eight characters in length. The truncation prevents you from distinquishing between multiple circuit names for which the first eight characters match.

CR 73560: BGP
The router faults in an ATM PVC environment while continuously
disabling and enabling ATM and IP interfaces.

CR 74044: IPv6
IPv6 over PPP faults when the PPP interface is disabled.

CR 74330: BGP
A bus error may occur when BGP is recalculating nexthop addresses after one becomes unreachable.

CR 75574: NAT
When deleting the last IP interface on a slot on which you have configured NAT configured, a fault may occur.

CR 75667: ATM
A LEC mistakenly sends out an LE_ARP message for a multicast address. According to LANE VI specification, a LEC should not generate an LE_ARP message for a multicast address.

CR 75844: SRB
If you use an SRB filter based on the NetBios name, faults can occur.

CR 78301: IP
In ISP mode, router does not pass ASB (all subnet broadcast) traffic.

CR 78787: X.25
The IPEX gateway doesn’t respond to the Reset Request Cause=0 and Diag=0 settings.

CR 79117: BCC - ATM
A tag violation may occur on the ARE processor when running the BCC "show atm line phy config" command.

CR 79357: BGP
Dynamically changing the BGP peer addresses causes a fault.

CR 79587: IPEX
When you disconnect a network cable from the router, not all TCP sessions are disconnected.

CR 79799: X.25
When you attempt to establish TCP sessions between clients and servers using the IPEX protocol, not all sessions create TCP connections.

CR 79893: DLSw
A Unix server PU 2.1 fails to connect to an SDLC PU 4 (3745) through DLSw routers whenever PU 2.1 is activated before PU 4. When this condition occurs, the Unix server continuously sends XID Fmt 3 frames while receiving nothing. Also, PU 4 does not forward XID Fmt 3 frames to the peer router by the secondary SDLC router.

CR 79932: RIP
RIP does not broadcast routing updates on to a LAN segment that is subnetted. Also, RIP does not generate a default route if you enable the default route generate option.

CR 80274: IP
The router experiences a bus error when you restart an IP interface.

CR 80388: DLSw
When you disable IP on a router using DLSw Version 2.0, the router experiences an error.

CR 80719: BCC - IPX
If you exit and then reenter the BCC, the watchdog-spoofing command does not display the correct value in the configuration output.

CR 80901: ATM
A router configured with NLPID PVCs in an ATM service record sends only one to three INARPs out each PVC before it stops operating.

CR 81185: OSPF
The fact that an area is a stub is not taken into account in path selection for AS externals; this can lead to routing loops.

CR 81723: X.25 Gateway
You cannot configure the number of times the X.25 Gateway function retries a TCP connection for a permanent virtual circuit. To fix this problem, a new MIB variable (wfIpexMappingTcpMaxRetry) was added which allows you to set how many times the PVC-TCP Router will retry the TCP connection to the remote end.

CR 82060: SNMP
Deleting SNMP globally using the BCC causes a router fault.

CR 82294: BootP
Configuring the Schedule Boot parameter causes the router to fault. This does not occur when you configure the Boot parameter using the Technician Interface.

CR 82369: X.25 Gateway
The IPEX Gateway (PVC-TCP) discontinues the TCP Retry even if some of the IPEX session gates are still in the TCP Retry State.

CR 82556: X.25
If an X.25 call clear request times out, the ARN router may experience a tag violation or bus error.

CR 83110: ATM
The "show atm interface" command fails if you have not configured signalling on the interface.

CR 83167: OSPF
When the router table manager fails to delete an entry from the routing net pool, a fault occurs. This can happen when a network interface in a non-backbone area, which learned an OSPF route that is in the range of an OSPF Summary Range defined in the backbone area, goes down.

CR 83316: BGP
Fault when changing BGP4 accept policy to add Route Flap Dampening.

CR 83491: SYNC
Entering the "dis syn cir <circuit name>" command disables all sync interfaces configured on the router.

CR 83691: Flash Handler.
The flash driver code is unable to recognize SanDisk ATA flash cards used in crash dumps. The driver cannot identify the following flash cards:

- 40MB PCMCIA PC CARD ATA (Product No. SDP3B-40-101-00)
- 85MB PCMCIA PC CARD ATA (Product No. SDP3B-85-101-00)

CR 83951: IP
When a router receives a bridged LAT change node packet, the router simultaneously generates an ICMP packet and sends the packet via the default route. The LAT change node packet also gets bridged.

CR 84074: X.25
A router may experience bus errors and then restart while terminating X.25 virtual circuits.

CR 84263: ARN
Crash dump support has been added for the ARN platform.

CR 84320: SNMP Agent
Can’t load RAESA agent (raesa.exe) on a VNR.

CR 84379: ARP
A tag violation might occur in ARP when a circuit goes down.

CR 84446: IPX
IPX route filters fail if more than 40 filters are configured.

CR 84803: X.25
If a router receives a call accept packet for a virtual circuit when there is no call request pending, bus errors may occur.

CR 84956: SDLC
During XID negotiation of an SDLC attached 2.1 device, the router changes the format of the XID packet from Pre-Negotiation exchange to Negotiation proceeding. This change prevents the 2.1 device from ever establishing a connection with a host.

CR 85111: IP
A memory leak occurs when using the IP-FORWARD_TO_FIRST_UP_NEXT_HOP filter.

CR 85269: SMDS
The default value for the MIB IFTF variable is idles (FF). Instead, the default should be flags (7E) and selectable.

CR 85271: IPX
When a router receives a RIP update for an existing network with a maximum hop value of 16, it experiences an IPX memory leak, eventually causing the router to restart with an out-of-memory fault.

CR 85312: QLLC
On a router using QLLC, sessions might not reestablish after deactivating then activating a PU device. As a result, the QLLC device does not clear the call or initiate a new session.

CR 85314: X.25
A bus error occurs on a router configured using the X.25 protocol if a call is both requested and cleared at approximately the same time.

CR 85393: TR LANE
When configuring IP and a token ring LANE (LAN emulation) client on a router, the router sometimes sets LE_ARP for a MAC address rather than the route descriptor. As a result, traffic traverses the bus causing connectivity problems.

CR 85597: ECMP
IP does not remove an external type 1 entry from the routing table after OSPF max ages it when configured for ECMP.

CR 85612: VINES
If the router receives a VIP (VINES IP) packet destined for a client at the network layer, sourced from a station on the same LAN, and if the client’s routing server is not in the routing table, but the client is in the router’s neighbor table, this causes a fault and VINES resets on the router.

CR 85713: ISDN
On an ASN router with a PRI card, when receiving from the ISDN switch a clear indication (cause 31 or 32) or a disconnect request (cause 44), a bus error occurs.

CR 85908: PCAP
When PCAP is enabled on an ATM circuit, the router may fault.

CR 85967: DLSw
If DLSw is disabled and there is a TP/LB traffic filter configured for 802.2 source SAPs, a bus error can occur. If the bus fault does not occur, the LB will stop receiving data packets on the Ethernet interface when DLSw is re-enabled.

CR 86204: X.25
The default value for the MIB attribute wfIpexMappingTcpMaxRetry is 1,000. The value should be changed to 0 to indicate that there is no limit to the number of retries the router attempts.

CR 86447: Syslog
When deleting a Syslog object in a second Telnet session, faults may occur.

CR 86519: IPEX
Out of sequence packets can cause a failure in an IPEX session.

CR 86550: SRB
In a configuration that uses source route bridging, the IP encapsulation incorrectly uses the new protocol UDP (User Datagram Protocol) port 12289, inhibiting its ability to establish connections.

CR 86586: OSI
OSI does not build a second ‘Code 2’ section in non-pseudonode LSP after the first ‘Code 2’ section has filled up.

CR 86617: SRB
IP encapsulation uses the new protocol UDP port for all IP explorer entries even though it is configured for one port only.

CR 87036: IPEX
A bus error may occur when IPEX tries to transmit a buffer to TCP while clearing a call.

CR 87182: BCC
Faults generated when deleting log-host objects using the BCC.

CR 87362: PPP
IP circuits fail to go up after a line recovers from going down.

CR 87580: IP
The router experiences a bus error when accepting full Internet routes from two BGP peers and OSPF is bounced globally.

CR 87612: BCC
For most slot range configurations, the BCC "filter slot-lower-bound,slot-upper-bound" commands for a log-host object are not functional.

CR 87670: FTP
When using the "*.*" wildcard syntax in MS-DOS to transfer an entire directory’s contents to a flash memory card, if you answer "y" to the send file "." or "..", this causes an orphaned buffer fault.

CR 88040: DLSw
In a DLSw configuration where the backup peer is not configured for the DLSw multicast IP group address, CANUREACH frames may be sent to OSPF (or other protocols) instead of the backup peer causing a fault in that protocol.

CR 88262: X.25
An error may occur on the router when you pass traffic between client and server applications and one of the applications is disconnected.

CR 88297: ECMP
When ECMP is enabled on the router, the IP routes are not added to the IP
routing table.

CR 88322: SNMP
If you issue the "get" command to certain SNMP variables, the router fails to return valid responses.

CR 88483: X.25
When LAPB entries are started between a client and server PC, the client
faults with the message "Error in buf_float.c at line 113".

CR 88637: ATM
The router does not send a connect acknowledgment message when in receipt of a LAN emulation client connection request.

CR 88762: DVMRP
In some DVMRP configurations a prune message from a neighbor router can stop
the flow of multicast for a group, when there are still other active neighbors
relying on the stream and/or a directly attached IGMP client registered for
the group.

CR 88765: ISDN
ARN 56/64K CSU/DSU boards experience damage by voltage surges, even with surge protector.

CR 88776: Scripts
Enabling and disabling sync circuits causes a bus error.

CR 88978: ATM
ILMI (Interim Local management Interface) timers are not changeable.

CR 89097: ATM
Address registration fails between the BayRS Release 13.01 and the FORE switch running Version 5.3. A workaround is to delete and add the ATM port on the FORE switch.

CR 89309: DLSw
Multislot broadcast does not work correctly on SDLC secondary interfaces.

CR 89355: X.25
Rebooting an ARN router with the ISDB module can cause loss of TCP connectivity and bus errors.

CR 89356: IP
A failure may occur on the router when an IP circuit transitions between primary and backup.

CR 89551: IP
Using Site Manager to modify IP traffic filters with fragment instances
deactivates the filters.

CR 89605: IP
Configured circuitless IP state is down; upon boot, router cannot make peer connections with circuitless IP devices.

CR 89696: NTP
When the Network Time Protocol Peer Preference option is set to "no," the local time changes with the remote peer server, so the timing of scheduled reboots is thrown off.

CR 89704: NTP
The Peer Filter option used during the configuration of Network Time Protocol doesn’t function properly. When an NTP access filter is set for a particular peer server, the local time does not update even if the filter type is set to Prefer. The router must be rebooted for the filter to take effect.

CR 90114: SWSERV
When the Demand-cct-group option is configured on the central site for receiving incoming calls, incoming demand calls fail.

CR 90210: DLSw
If you change the XID values while a link station is in session, the current DLS session is not reset dynamically.

CR 90220: IP
When configuring a router for Bridge IP host mode and you add a static route, the route gets removed from the routing table after a reboot.

CR 90310: ISDN
ARN and AN router ISDN BRI S/T adapter modules fail due to an improperly programmed ISAC internal register.

CR 90431: OSI
After adjacencies go up and down due to loss of hellos under heavy load, connectivity is sometimes lost.

CR 90638: IPX
A VBM error may occur in IPX when another slot goes down.

CR 90899: ATM
During initialization, an ARE virtual network router experiences a VBM fault.

CR 91071: DLSw
If you disable DLS, the DLS peers configured and TCP connections up, the TCP connections to the peers are closed, but wfDlsPeerEntry.wfDlsPeerStates reflects a connected state.

CR 91169: IP
The IP forwarding table becomes corrupt with a range of addresses marked as unreachable after a change in the topology occurs with variable length subnets and overlapping routes.

CR 91723: DVMRP
When setting the full update interval on a router interface running DVMRP to its minimum value of 10 seconds, the router experiences a game fault (zero divide) error.

CR 91759: IP
When inbound IP traffic filters are applied to router interfaces with actions of FOWARD_TO_NEXT_HOP_INTERFACE and FORWARD_TO_FIRST_UP_NEXT_HOP_INTERFACE, tag violation faults can occur.

CR 92886: ATM
If the address-resolution type for the IP interface is set to ATMARP on an ATM PVC, the ATM call control process repeatedly panics.