Revision Notes for Router Software v8.10 rev 3
Date: 5/4/95
Subj: Revision Notes for 8.10 fix 3
===========================================================================
SITE MANAGER COMPATIBILITY
===========================================================================
Router version is managed by Site Manager version
v8.10 2.10
8.10 fix 1, 2, 3 2.10, 2.10 fix 1
Revision fix/8.10/3 corrects the following problems:
===========================================================================
CR 13413: MIB.
14256 When a slot resets, the wfIfEntry record becomes nil for all the
configured circuits except for the slot that reset. All the
circuits are up and all protocols configured on these circuits
are fully functional.
CR 14373: System.
The TI welcome banner displayed after logging in has been
enhanced to allow the display of user defined text. The network
administrator may now create an ascii file called ti_msg.txt
which will replace the default login banner with the text stored
in the ti_msg.txt file. When a console or telnet session to the
router is started, the router will search the file system for a
'ti_msg.txt' file. If the file exists, its contents will be
displayed instead of the default, "Welcome to the Backbone
Technician's Interface". If the file does not exist, the default
login banner will be displayed.
CR 13754: Frame Relay.
PVC's 16 through 36 do not show any transmit stats after a slot
resets, a router reboots, or if the frame relay switch stops
sending status messages. This problem only occurs on slot 8 and
higher. The status of all the PVCs shows active but transmit
stats only increment on PVC 37s and higher (the particular
config uses PVC 16-56).
CR 13469: OSPF.
OSPF SPF Metric Limited to 65,535 in Calculation. When OSPF
Dijkstra calculates the shortest path to each destination, it
compares the costs of possible paths to select the best path.
The cost of any path is the sum of the outbound costs of each
link along that path. Each link can have a value ranging from 0
to 65,535. Therefore the sum of multiple high cost links could
result in a sum that is greater than 65,535. The Bay Networks
implementation resets the sum any time it exceeds 65,535.
The new limit for the SPF metric has been increased to 16,777,215.
CR 13527: OSPF.
Added new OSPF event log message for NBMA when the neighbor's
priority does not match the neighbor's interface priority.
CR None: IPX.
IPX router may exhibit poor performance or packets drops with
hogs bufs notices in the system log in large changing redundant
network topologies.
CR 13802: SYNC.
The KG84A feature that provides resyncronization support for
encryption devices on a sync line is not functioning on the AN.
CR 15274: DLSw.
When DLSw is run over Ethernet and Test frames are received with
no RIF DLSw drops them.
CR 14479: Spanning Tree Bridge.
A router configured for IP host-only will become unreachable in a
redundant bridge network after a topology change and Spanning
Tree reconverges.
CR 14291: Telnet.
Typing the single character command of Control-O followed by
return on a telnet session to the router will cause a watchdog
slot reset.
CR 15161: SYNC.
Cannot configure INTERNAL/EXTERNAL CLOCK to COM port when doing
Quick-Start running install.bat.
CR 13928: IP.
If there is no IP on the box the ping command issued from ti
will not report an error. When there is no IP router configured
the ping command will now display the error "IP Service is not
running"
CR 14288: System.
Deleting 0 byte file from Floppy based system causes watchdog
slot reset.
CR 14996: Frame Relay.
'Error in map_rem.c at line 60' panics can occur when PVCs are
bouncing on a Frame Relay interface.
CR 12937: PPP.
PPP Warning Code 17 - received LQR with no change in PeerINLQRs
on circuit is logged repeatedly and excessively in the event log.
Network Management stations receiving traps from the routers are
severely impacted.
CR 14597: OSPF.
IP Routing Table corruption may occur when running OSPF in very
specific configurations if certain criteria are met. The
corruption will appear as routers installing a remote router's
OSPF Point to Point link IP address as the next hop for the
actual Host Route of the Point to Point Link and for any other
routes that are local to that remote router.
CR 14825: OSPF.
A router may experience a "Watchdog expired, service terminating"
(BN, AN, ASN, or VME w/ACE32) or a system "hang" (AFN or VME
w/ACE 25) under some configurations when running OSPF. This
problem has been seen most commonly when an OSPF Point To Point
Link has one end misconfigured as Broadcast.
CR 14930: VINES.
VINES clients using certain applications may disconnect when
searching for services from a serverless segment.
CR 13797: X.25.
The X25 PDN max idle timer is only initialized on incoming calls.
It should also be initialized on outgoing calls.
CR 13552: Token Ring.
Gradual loss of memory occurs when a token ring interface goes
down/up.
CR 14741: XNS.
XNS router learns a network then ages it out even though it
receives rip updates.
CR 14309: SNMP.
After changing the system date (forward), the router will
incorrectly report how long its SNMP agent has been active,
affecting network management applications which use this value.
CR 14507: IP.
Dynamically disabling IP for a network adddress on a multi-netted
interface causes an exception vector 2 bus error on a BCN.
CR 13602: ATM.
The disable circuit script does not function properly on an ATM
interface. The command: 'disable circuit a31' erroneously returns
the message:
Unknown driver name type: 110
Circuit Disable Command Help
----------------------------
disable circuit
Even when circuit a31 exists and is active.
CR 13320: System.
Source routed frames destined to be forwarded out a sync
interface can be sporadically dropped with no indication
as to where/why.
This problem was occurring during momentary period of low buffer
availability. The repair is to increment the
wfKernelAliasBuffsDropped stat for each buffer dropped.
CR 14323: X.25.
Bay Network's router doesn't interoperate with BT Tymenet Switch.
As we are not using any facilties the router is expecting the
Call Accept to be as follows : 10 14 0F. However the BT switch
sends the Call Accept as 10 14 0F 00. The extra byte states that
called/calling address length field is 0. Upon receiveing this
Call Accept pkt from a switch the router send CLEAR IND/REQUEST
packet.
CR 13488: Source Route Bridge.
Source Route Bridge AREs can be forwarded incorrectly (the
particular ARE had already been forwarded by this bridge).
CR 13422: IPX.
Ipx Routes may fail to age in redundant configurations where
multiple IPX networks span multiple slots between two routers.
CR 13587: IPX.
IPX/NETBIOS nonbroacast frames not forwarded, unless netbios
accept attribute is enabled.
CR 13595: FTP.
The router's FTP server does not accept commands in lowercase.
CR 13949: Config.
Running install.bat on model 1530 (DSDT) AFN on a Token Ring
interface will result in the following error:
*** ERROR *** Goto/Gosub label not found: :LINK_DUAL_TOKE
run: Error at line 1251 in file 2:install.bat.
CR 13487: Source Route Spanning Tree Bridge.
If a Source Route Spanning tree bridge receives a BPDU from a
Transparent Spanning Tree bridge the following debug mesage will
show up in the log. "SPT base record not available."
CR None: IPX.
The handling of inbound IPX RIP advertisement packets has been
improved to more sparingly utilize system resources. The typical
user visible effect of the problem were hogs bufs notices in the
system log upon receipt of large numbers of IPX RIPs.
CR 13168: OSPF.
When OSPF is disabled on a per interface basis an erroneous
default route is inserted into the routing table and the LSDB.
CR 13431: OSPF.
Area Border router generates a Summary ASB LSA (type 4) for a
router in the area(s) which the advertised router belongs to.
This does not create any routing problems in IP/OSPF, it just
increases the size of the LSDB with unnecessary Summary LSAs.
CR 13464: System.
wfSysUpTime is not keeping the same time as that of the wallclock.
CR 13927: IPX.
If large numbers (> 1000) of IPX networks are learned from an
interface and that interface is disabled the IPX router may reset
with bus errors.
CR 13425: IPX.
The IPX MIB variable 'wfIpxBase.wfIpxBaseNetCount' is Inaccurate.
CR 13428: IPX.
When running 8.01 Fix 4, if wfIpxBase.17.0 (triggered updates) is
set to 2 (disable) Bus Errors in IPX may occur. It also appears
that IPX does not recover after several of these bus errors occur
simultaneously.
CR 13529: OSI.
OSI router bus error panics when configured with an OSI External
(interdomain) interface going over a PPP line.
CR 13190: System.
Wyse Terminals, which require that RTS(pin 4) be on in order to
communicate with the router's console port, do not work.
CR 13608: Frame Relay.
On a Frame Relay interface consisting of PVCs configured with
Bridge in Hybrid mode, if VCs change from INACTIVE to ACTIVE
while receiving bridge traffic the circuit can experience
a Bus error in dp_1294_decaps_act.
CR 13664: Bridge.
If the primary sync line on the Master side bounces up and down,
before the dial backup line is established, the bridge will panic
in spanning tree (Error in sp_msg.c)
CR 13543: Config.
Install.bat does not have point-to-multipoint option for OSPF
interface type.
CR 12806: TCP.
TCP does not send a TCP_ABORT_MSG to its client when the
connection is closed by receiving a RESET from the peer TCP host.
This will leave the client unaware that the underlying conection
has already been closed.
CR 13557: FDDI.
Watchdog expiration slot resets can occur on an FDDI slot when a
W&G FDDI analyzer is on the ring running its RMON options.
CR 13427: Switched Services.
In a dial backup configuration with IP and Source Route Bridge
configured there is no transmission of specifically routed frames
over the backup line from the master of the backup to the slave
if the primary line goes down a second time. IP is still still
working. Explorer packets are still transmitted and also the
specifically routed frames from the slave of the backup to the
master.
======================== Version 8.10 fix 2 ==============================
The image for FRE BN hardware is: 2577512 May 3 16:03 bn.exe
The image for FRE ASN hardware is: 2467141 May 3 16:04 asn.exe
The image for VME & AFN Floppy hardware is: 2362938 May 3 16:03 ace.out
The image for AN hardware is: 2307242 May 3 16:01 an.exe
The image for IN Flash hardware is: 2476796 May 3 16:29 in.exe
The image for AFN Flash hardware is: 2246611 May 3 16:29 afn.exe
The image for BNX BN hardware is: 1646820 May 3 16:28 bn.exe
The image for BNX ASN hardware is: 1526055 May 3 16:29 asn.exe
___________________________________________________________________________
CR 13920: IP.
A Slot may reset because of an "out of memory" or "insufficient
memory to continue => GAME restarts" condition. The loss of memory
occurs in the Ip Routing Table Manager and can be triggered by an
unstable environment where Synchronous links are going down/up.
The leak may continue after the environment stabilizes possibly
leading to the above mentioned slot resets.
CR 13529: OSI.
OSI router bus error panics when configured with an OSI External
(interdomain) interface going over a PPP line.
CR 13517: DLSw.
In a DLSw network that has AN hubs, if end stations send out LLC
test frames with a data length larger than 2KB, the AN may
experience memory corruption and/or PANIC.
CR 13522: Bridge.
When the Learning Bridge forwarding table is full traffic from
end station moved from one interface to another is not bridged.
CR 13432: LLC.
Receipt of an SSP contact message for a session that is in the
LLC2 disconnect phase (ie N2 *T1 not expired) causes a Bus Error
in the receiving router.
CR 13534: PPP.
When using the SHOW PPP LQR STATS and SHOW PPP LQR config scripts
the circuit names are displayed incorrectly.
CR 13493: IP.
Ip router can reset with 'PANIC in ip_rtm_misc.c at line 220'
while IP router on another slot is resetting.
CR 13571: Bridge.
While bridging traffic over an ATM network occasionally the
bridge would erroneously detect that a station had moved onto (or
behind) the ATM network. As a result the bridge forwarding table
would be incorrect and bridge packets on the ATM interface would
start to be dropped (incrementing wfBrTpInterfaceInDiscards).
Any connections that had previously been established would be lost.
CR 13373: DLSw.
In a heavily redundant DLSw network, DLSw may cause a panic
in mib_ent.c when creating a MIB instance.
CR 13460: AppleTalk.
AppleTalk ARP sub-system does not always recover after period
of AppleTalk router instability.
CR 13480: TCP.
Watchdog expiration slot resets can occur upon receipt of TCP
packet having corrupted TCP option (0 length of unknown option).
CR 13443: IP.
AFN router can hang following receipt of ARP request for one of
the IP addresses defined on that multi-netted interface.
CR 13538: IP.
Invalid Arps are logged erroneously when configured for ip
multinetting.
CR 13368: IP.
IP router generates checksum of -0 (0xffff) instead of +0 (0x0000)
for received packets with checksum of 0xfeff.
CR 12184: Source Route Spanning Tree Bridge.
A slot may incorrectly consider it's Bridge ID to be Root.
CR None: SYNC.
The granularity of the LAPB T1 ack timer has been changed from
seconds to tenths of a second. Note that this change affects
existing config files such that what the network administrator
previously configured in seconds is now a value in tenths of
a second. The MIB variables effected are;
wfSyncEntry.wfSyncRetryTimer and wfLabpEntry.wfLapbT1AckTimer.
CR 12355: IPX.
IN particular circumstances (misconfiguration in an IPX network)
IPX Directed broadcast(rip/sap) gets routed out same interface
it was received on.
CR 13366: OSPF.
Networks are not installed after moving ospf pt-to-pt link to
another router. If you dynamically reconfigure two routers,
deleting an ospf pt-to-pt link on router_A, and adding (moving)
the ospf pt-to-pt link to router_B. The pt-to-pt networks will
not be installed in router_A's routing table. Router_B is
properly advertising the routes, other routers (router_C) in the
network learn of the pt-to-pt networks from router_B. It is only
the pt-to-pt networks which are not installed in router_A's
routing table, other networks residing on the remote router
(router_D) are installed in router_A's routing table.
CR 13198: X.25.
When configuring an X25 Closed User Group with a value of 0 the
router does not create a facility in the Call Request Packet for
the CUG. Any other value from 1 - 999 will create this facility.
Site Manager says that all values from 0 - 999 are valid.
CR 12647: IPX.
In IPX networks with large numbers of end stations with many
clients attempting to open connections to one server a system
task and its associated memory can be lost.
CR 6432: System.
Network packets normally routed (if configured) are momentarily
bridged while routing sub-system (IP, IPX, AppleTalk...) is being
restarted. The packets are bridged permanently if the routing
sub-system is configured but disabled. This behavior as designed
in the series 7 and 8 architecture has created some rather
pernicious traffic conditions in looped IPX topologies as an
example.
This enhancement changes the router's behavior as described in
the chart below which makes distinctions between a routing
sub-system that is operating, configured but disabled, and
deleted.
SITUATION ACTION WHY
1. Box up - protocol Drop protocol. The way 5 series
disabled. platform works.
2. Boot with protocol Drop protocol. The way 5 series
disabled. platform works.
3. Box up - protocol Drop protocol. Stop routing loops.
fails.
4. Box up - protocol Bridge protocol. Protocol no longer
deleted. registered should in a
dynamic system act as
if never there.
5. Box up - protocol added Drop protocol. Similar to #2.
but disabled.
6. Box up - protocol Route protocol. Expected.
enabled.
Prior to this enhancement #1 thru #5 would bridge the protocol.
CR 13363: OSI.
When a Ping is issued from TI for OSI the field only allows you
to enter 38 Hex digits for the value of the address. The problem
is that you should be able to enter the Selector field with the
address which would be a total of 40 Hex digits.
CR 13297: DLSw.
The receipt of a CANUREACH with different source and destination
SAP's where the destination SAP is one defined in the DLS SAP
table but the source one is not, will cause a BUS error. If both
SAP's are defined in the SAP table the problem doesn't happen.
There is also no problem if neither is defined in the SAP table.
CR 13119: IP.
Snap Encapsulated 802.3 ARP requests incorrectly have the Hardware
Type Field set to 1 (Ethernet). This field should be set to
6 (IEEE 802 Network). It seems that certain End-stations, IBM
RS6000s for one, will not respond to our SNAP Encapsulated ARP
Requests over Enet when the endstation is configured for an 802.3
Network Interface. They will only respond if this field is set to 6.
CR 13210: Switched Services.
Hold down timer for dial backup does not work. If it is configured
the primary line may never come up on boot.
CR 13200: Bridge.
Configuring Bridge Filters that filter on DST MAC address has
higher precedence than the filter rule#1 which should be
triggered first. This appeared when two filters were configured
on one circuit. The first filter is a FWD filter to circuit E22
with field of ETYPE 0x6004. The second Filter is a drop filter
with DST MAC of 0x000000000000-0xffffffffffff. The second filter
has lower precedence and should be applied after the first filter
but the packets with ETYPE 0x6004 were dropped.
CR 13299: MIB.
The Mib tree does not support the case of two instances of the
same object, when one instance is a prefix of the other one
(variable length instances) the Mib will insert both of them in
the tree, but the longer one is then inaccessible and if one
deletes the shorter instances then both instances will be deleted
(creating a memory leak).
CR None: System:
TI 'save config' command fails on large config files even though
free memory available on the slot running TI is more than twice
the size of the config file. When the save fails, although an
informative error is recorded in the system log, NO error is
displayed to the TI session.
Note: The configuration save module now requires much less memory to
save the file to flash but it is important to note that the
memory used comes from a single segment which must be smaller
then the value recorded in the slot's MIB attribute
wfKernelMemoryMaxSegFree.
If the config save does fail for lack of a single memory segment
large enough there will now be an error displayed to the TI
session like; 'Config. file retrieval error.'
CR 11692: System.
Slot resets infrequently occur with an 'out of GID' error in the log.
CR 13066: Bridge.
Unable to reach Host Only interfaces after disabling Bridge.
CR 13179: Vines.
Vines router tends to PANIC during momentary period of all packet
buffers on a slot being in use.
CR 12751: IPX.
With a looped environment and number of paths greater than 1,
IPX never loses routes that should be aged out.
CR 13000: Source Route Bridge.
Source Route Traffic Filter to Forward to Circuit Group only,
also forwards packets to IP Encaps subsystem.
CR 13057: IP.
Slot resets with Tag violations can occur on receipt of
re-ordered IP fragments when IP header of the first fragment
exceeds 20 bytes.
CR 12916: PPP.
Slots running IPX router can panic when changing IPX network
address on a PPP interface.
CR 12807: Bridge.
Bridge SNAP filters do not work over PPP or Frame Relay interfaces.
CR 13131: System.
When the operating system's mechanism for single threading access
to a shared resource is utilized and one process waits behind
another, a 32 byte memory block is lost. Over time, this memory
leak that does not show up in the wfKernelEntry stats other than
a lack of free memory, can cause 'out of memory' slot resets.
CR 11762: DLSw.
A particular Netbios SQL application fails when going through
WF DLSw because we only allow for one connection per data link.
This application needs the client and server to have 2 sessions
opened, for 2 different Netbios names, at the same time. The first
session is opened OK but when the second tries to come up the WF
routers will terminate the data link (DISC at both ends).
CR 10670: OSPF.
OSPF adjacencies do not form when using the dial backup line after
the primary line is disabled.
CR 12895: Vines.
The Vines client program SEND.EXE does not work on serverless
segments.
CR 13021: SNMP.
SNMP Get Request (45 Objects) from SunNet Mgr fails with
Error - Get Request Too Big. It used to work in 7.71 fix 8 and it
fails with 7.80 fix 5 and up.
CR 11433: Token Ring.
The ring data rate is incorrect in the 8502 frame sent from the
router to the IBM Lan Network Manager. Even though the ring is
configured for 4Mbps it still sends the ring data rate as 16Mbps.
CR 12836: OSPF.
When filtering OSPF events to keep only INFO and STATE with
SM/Sun 2.0, we still have OSPF TRACE messages in the log after
OSPF initializes.
CR 12555: LLC.
After having opened and closed around 270 LLC sessions through a
router, it is no longer possible to establish new sessions. The
typical error messages in the log are:
933: 01/20/95 12:12:40.271 DEBUG SLOT 2 LLC Code: 11
Context not found or unavailable.
934: 01/20/95 12:12:40.271 DEBUG SLOT 2 LLC Code: 11
LLC ERROR: No Context Available
CR 12532: DLSw.
When DLSw and LNM are both configured on the same slot either
may fail to operate.
CR 12830: IP.
IP Router responds to a UDP echo request with the same DST and
SRC ports as the requesting packet.
CR 13514: Bridge.
Changed Bridge 'Forwarding Table Full' message from debug to
warning.
CR 13483: OSPF.
Adding a second non-backbone area (with no 0.0.0.0) can cause
Tag Violation slot resets.
CR 13286: IP.
IP packets with bad headers (fails checksum) where the header's
total length field contains a large value (larger than the size
of a buffer), can cause Tag Violation slot resets.
CR 13407: IP.
Routing table missing IP routes when parallel rip networks are
configured between 2 routers. If new rip advertisements
containing info on the same route(s) appear simultaneously on
two interfaces which reside on different slots, the routing table
can become corrupted so that no slot owns the just-learned routes.
CR 13392: XMODEM.
XMODEM - YMODEM is padding files transferred from the Router.
This is not a problem. Both XMODEM and YMODEM send padded files
as they should because frame size in these protocols is
constant - 128 bytes (128,1024 for YMODEM). The issue raised
in this CR was caused by TI's help saying 'Use the -y option to
send binary files WITHOUT being padded', which is incorrect.
The repair for this CR is to change the TI's help to read:
' ... With XYmodem files are padded with Control-Z (0x1A) such
that the size is a multiple of the frame size (128 or 1024
bytes). Use the -y option to receive binary files WITHOUT being
padded.'
' ... The padding (0x1A) will be removed on a receive side. '
CR 13367: AppleTalk.
On receiving an NBP broadcast request from a node on a directly
connected network, NBP lookups with the multicast address
different than what is sent in ZIP GetNetInfo Reply is sent from
AppleTalk router. As a result of this we do not get any NBP
replies from the servers on the same zone on the different
networks.
CR 13204: IP.
IP All Subnet Broadcasts not forwarded when ASB is enabled on
outgoing interface when ASB is initiated from an end-station
more than one hop away.
CR 13277: OSPF.
OSPF can reset with 'Error in ospf_rtab.c at line 399' when WAN
link is disabled.
CR 13188: System.
The event log capacity for a VME based router has been increased
from 32 KB to 64 KB.
CR 13399: IP.
Version 8.01 doesn't handle IP Rip updates correctly from a
multinetted interface within the same class address with the
remote router having more subnets defined, and configured for
explicit broadcast.
CR 12776: DLSw.
Disabling LLc2 on a router can cause Panic Vector 2 Bus Errors
if Sap 0 is configured.
======================== Version 8.10 fix 1 ==============================
The image for FRE BN hardware is: 2563507 Mar 10 18:37 bn.exe
The image for FRE ASN hardware is: 2490217 Mar 10 18:37 asn.exe
The image for VME & AFN Floppy hardware is: 2363445 Mar 10 18:44 ace.out
The image for AN hardware is: 2306663 Mar 10 18:40 an.exe
The image for IN Flash hardware is: 2333448 Mar 10 18:42 in.exe
The image for AFN Flash hardware is: 2248720 Mar 10 18:42 afn.exe
The image for BNX BN hardware is: 1584296 Mar 10 18:39 bn.exe
The image for BNX ASN hardware is: 1488650 Mar 10 18:39 asn.exe
___________________________________________________________________________
CR 13253: ATM.
Disconnecting then reconnecting the fiber into the receive
interface on the OC3 SingleMode interface can place the receiver
into a reset state, not recovering until the driver has been
reinitialized.
CR 13228: ATM.
When running multiple PVCs over ATM, the router may display an
ERROR in atmalc_xmt.c. This seems to occur when traffic is
transmitted out all VCs simultaneously.
CR 13240: ATM.
An ATM interface has received the following message:
# 1372: 02/22/95 12:30:58.590 DEBUG SLOT 3 ATMINTF Code: 96
Port 1: coprocessor driver fault 23.
This occurred while running IPX Vines and IP over 80 group
mode VCs. This error is not easily reproducible and it has
only been seen twice.
CR 13177: ATM.
At random times, the ATM driver will log "coprocessor driver fault
26" or "coprocessor driver fault 27". In addition, the driver
will reset at atmalc_rcv.c at line 323 when this happens. This
anomaly occurs very infrequently and the driver recovers quickly.
CR 13220: IP.
DVMRP may cause IP on the slot to restart if a network with a
non-contiguous subnet mask is advertised to DVMRP by a neighbor.
Feedback | Service Search
| ERC
Copyright
© Bay Networks,Inc., 1997. All rights reserved.
|
/tr> |
