Revision Notes for Router Software v8.01 rev 7
Date: 6/2/95
Subj: Revision Notes for 8.01 fix 7
===========================================================================
SITE MANAGER COMPATIBILITY
===========================================================================
Router version is managed by Site Manager version
v8.01 2.00
8.01 fix 1, 2, 3, 4, 5, 6, 7 2.00, 2.00 fix 1, 2
======================== Version 8.01 fix 6 =============================
The image for FRE hardware is: 1782721 Jun 1 14:17 boot.exe
The image for VME & AFN Floppy hardware is: 1667602 Jun 1 14:58 ace.out
The image for AN hardware is: 1555349 Jun 1 14:27 boot.exe
The image for IN & AFN Flash hardware is: 1656282 Jun 1 14:42 boot.exe
__________________________________________________________________________
Revision fix/8.01/7 corrects the following problems:
===========================================================================
CR 15032: X.25.
IP Routes learned over a DDN X25 type interface unreachable
unless a Virtual Connection is already established to the next
hop host.
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 routers
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 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 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 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 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 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 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 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 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 14025: Source Route Bridge.
Source Routing over PPP, FR, or SMDS causes bus error when the
WAN interface goes down/up.
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 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.
======================== Version 8.01 fix 6 =============================
The image for FRE hardware is: 1780036 May 18 18:25 boot.exe
The image for VME & AFN Floppy hardware is: 1665435 May 18 19:00 ace.out
The image for AN hardware is: 1553014 May 18 18:34 boot.exe
The image for IN & AFN Flash hardware is: 1654006 May 18 18:48 boot.exe
__________________________________________________________________________
CR 13556: Protocol Priority.
13948 Protocol Priority may not prioritize traffic properly in some
configurations.
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 13527: OSPF.
Added new OSPF event log message for NBMA when the neighbor's
priority does not match the neighbor's interface priority.
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.
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 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 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 environement stablizes possibly
leading to the above mentioned slot resets.
CR 14015: TI.
TI command "more" set to "off" by default upon router bootup.
This problem was introduced in rev fix/8.01/5.
CR None: IPX.
IPX router bus errors upon receipt of directed broadcast packets
that were not destined for this router.
This problem was introduced as a side effect of the repair
documented below in fix/8.01/5 in CR 12355.
CR 13464: System.
wfSysUpTime is not keeping the same time as that of the wallclock.
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 13654: Frame Relay.
On a Frame Relay interface consisting of PVCs configured with
Bridge in Hybrid mode, when excessive brige traffic is flooded
out all VC's causing the LMI to timeout, the interface comes down
and DP reports DP_VC_LINDWN_MSG for each of the VC's followed by
a FAULT in map_rem.c at line 60.
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 13549: LLC.
A Bus Error may occur following a "Client Request Failure:
request = xx, failure = 1" as reported by LLC in the event log.
CR 13534: PPP.
When using the SHOW PPP LQR STATS and SHOW PPP LQR config scripts
the circuit names are displayed incorrectly.
CR 13529: OSI.
OSI router bus error panics when configured with an OSI External
(interdomain) interface going over a PPP line.
======================== Version 8.01 fix 5 =============================
The image for FRE hardware is: 1778437 Apr 18 09:42 boot.exe
The image for VME & AFN Floppy hardware is: 1662154 Apr 18 09:45 ace.out
The image for AN hardware is: 1549557 Apr 18 09:45 boot.exe
The image for IN & AFN Flash hardware is: 1652343 Apr 18 09:44 boot.exe
__________________________________________________________________________
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 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 13425: IPX.
The IPX MIB variable 'wfIpxBase.wfIpxBaseNetCount' is Inaccurate.
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 13443: IP.
AFN router can hang following receipt of ARP request for one of
the IP addresses defined on that multi-netted interface.
CR 13576: FDDI.
An orphan buffer error can appear in the log of an FDDI slot
running Learning Bridge.
CR 13460: AppleTalk.
AppleTalk ARP sub-system does not always recover after period
of AppleTalk router instability.
CR 13531: Switched Services.
If a Sync line is set up to be used for both dial backup and
demand dial, only demand dial will function.
CR 13373: DLSw.
In a heavily redundant DLSw network, DLSw may cause a panic
in mib_ent.c when creating a MIB instance.
CR 13538: IP.
Invalid Arps are logged erroneously when configured for ip
multinetting.
CR 13480: TCP.
Watchdog expiration slot resets can occur upon receipt of TCP
packet having corrupted TCP option (0 length of unknown option).
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 13368: IP.
IP router generates checksum of -0 (0xffff) instead of +0 (0x0000)
for received packets with checksum of 0xfeff.
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 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 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 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 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 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 12776: DLSw.
Disabling LLc2 on a router can cause Panic Vector 2 Bus Errors
if Sap 0 is configured.
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 13188: System.
The event log capacity for a VME based router has been increased
from 32 KB to 64 KB.
CR 13277: OSPF.
OSPF can reset with 'Error in ospf_rtab.c at line 399' when WAN
link is disabled.
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 12880: Telnet.
Need to type control-j to get the password to be accepted in 8.01.
The problem exists if you telnet outbound from 8.01 router. To
reproduce this set a password on an 8.01 router then try to telnet
to itself. The password won't be accepted unless you type a
control-j which is the equivalent of a LineFeed. The password is
the only part of the technicians interface that will not just
take a Carriage Return but requires both a CR and a LF.
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 12886: IPX.
Adding a SAP filter to PPP interface that is going down/up can
cause Tag Violation slot resets.
======================== Version 8.01 fix 4 =============================
The image for FRE hardware is: 1772850 Mar 13 16:33 boot.exe
The image for VME & AFN Floppy hardware is: 1657895 Mar 13 17:06 ace.out
The image for AN hardware is: 1545831 Mar 13 16:41 boot.exe
The image for IN & AFN Flash hardware is: 1649134 Mar 13 16:54 boot.exe
___________________________________________________________________________
CR 12872: IP.
Router forwards all traffic received on a given interface
to incorrect next hop despite normal appearance of IP route
and forward tables.
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 None: IPX.
IPX router intermittently stops forwarding traffic for a
particular connection. This most typically occurs in a source
routed environment with end-station support configured.
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 12184: Source Route Spanning Tree Bridge.
A slot may incorrectly consider it's Bridge ID to be Root.
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 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 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 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 13036: DLSw.
When an LLC token ring interface gets congested and starts sending
RNRs, the session gets stuck in 'enter busy' state and never gets
'exit busy'. The configuration is dual switch, two OS/2
workstations are used to establish an LU-LU connection.
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 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 13179: Vines.
Vines router tends to PANIC during momentary period of all packet
buffers on a slot being in use.
CR 13166: Vines.
Under particular circumstances servers that use a neighbor as a
gateway can become unreachable from behind a BNET router.
CR 13201: Switched Services.
Access Nodes may reset in the quicsync driver when receiving an
ISDN call.
CR 12916: PPP.
Slots running IPX router can panic when changing IPX network
address on a PPP interface.
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 12807: Bridge.
Bridge SNAP filters do not work over PPP or Frame Relay interfaces.
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 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 10946: IP.
An ip circuit configured dynamically on a demand circuit will not
transition to the UP state until the router is rebooted.
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 12830: IP.
IP Router responds to a UDP echo request with the same DST and
SRC ports as the requesting packet.
CR 12782: System.
Improved the debug information recorded in the system log on
occurrences of BB TAG violation slot resets.
CR 12855: SNMP.
Watchdog expiration slot resets can occur if router receives an
SNMP packet containing a zero len INTEGER_TAG.
======================== Version 8.01 fix 3 =============================
The image for FRE hardware is: 1767206 Feb 17 14:12 boot.exe
The image for VME & AFN Floppy hardware is: 1651627 Feb 17 14:41 ace.out
The image for AN hardware is: 1537464 Feb 17 14:20 boot.exe
The image for IN & AFN Flash hardware is: 1640529 Feb 17 14:31 boot.exe
__________________________________________________________________________
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.
========================= Version 8.01 fix 2 =============================
The image for FRE hardware is: 1767298 Feb 14 17:06 boot.exe
The image for VME & AFN Floppy hardware is: 1651470 Feb 14 17:29 ace.out
The image for AN hardware is: 1537418 Feb 14 17:12 boot.exe
The image for IN & AFN Flash hardware is: 1640873 Feb 14 17:21 boot.exe
___________________________________________________________________________
CR 12532: DLSw.
When DLSw and LNM are both configured on the same slot either
may fail to operate.
CR 9999: IPX.
Loss of connectivity for IPX hosts that use inter-slot routing
can occur. This usually happens after an IPX interface goes
down/up or End Station Support learns a new RIF for a given
IPX host.
This problem was introduced as a side effect of the repair
documented below in fix/8.01/1 in CR 9999.
CR 12895: Vines.
The Vines client program SEND.EXE does not work on serverless
segments.
CR 12687: LNM.
In the response to a Request Bridge Status in LNM the router
assigns the MAC address of the ring being queried to the Internal
LAN ID. The MAC address should be the pseudo MAC address assigned
by the user. This causes confusion on the management workstation
and reports the wrong ring speed for the ring that the
workstation is connected.
CR 12535: Config.
QSYNC interface will not come up after running install.bat.
CR 11623: LNM.
When the Token Ring MAC address and the LNM interface MAC address
have a zero in the last digit then we cannot link to the
Wellfleet from the IBM_LNM station.
CR 12908: LNM.
PANIC in mib_ent.c at line 1041 can occur after disabling LNM
Interface.
CR 11719: Source Route Bridge.
Running NetBIOS Caching may cause exception vector panic in
sr_nb_process_are as a result of RIF entries being aged while
the same RIF entries are being relearned.
CR 12583: E1.
E1 board configured with external clock uses the clock received
from port 1 as its clock source. If port 1 goes down then clock
source switches to port 2. After port 1 returns the clock source
remains with port 2 instead of returning to port 1.
CR 12735: Frame Relay.
In a Bridged Environment where a combination of FDDI, Ethernet
and Frame Relay exist, intermittent TAG VIOLATIONS may occur on
the Frame Relay slot.
CR 11250: IP.
Default Route IP Export Route Filtering Causes Bus Error. When
Export Route Filter is configured to filter out the default route
(0.0.0.0/255.255.255.255 IP_ADDR/IP_MASK) it would cause bus
errors on the slot.
CR 11058: Config.
7.80 Router log shows up as slots booting off different router
versions. With SM 1.80 connect to a 7.71 router, go to Config Mgr
in dynamic mode and save the file. Then reboot the router under
7.80, SM displays msgs showing what versions the slots are
booting off of. What will appear in the log, in an alternating
fashion, is the first slot will show "booting off 7.80", the
second slot will be "booting off 7.71", the third slot will be
"booting off 7.80" and the fourth will be "booting off
7.71", and so on.
CR 12434: IP.
Rip Import Route Filters do not apply mask correctly. RIP applies
the interface mask instead of the configured import route filter
mask.
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 12541: IPX.
After executing an incorrect ipx ping such as 'ping -IPX 0x1.0'
the slot running ti will either become disconnected but not show
anything in the log as in the case of VME hardware or reset with
a tag violation in the case of the BN or ASN hardware.
CR 12388: PPP.
When the PPP protocol determines that a sync line has gone down,
through either missing echoes or LQR, the LCP will cause the NCPs
to go into a starting state but the
wfPppCircuitEntry.wfPppCircuitState is still up.
CR 12589: PPP.
All bridge traffic is discarded on PPP link between Wellfleet
and Network Systems router/bridge.
CR 12334: OSPF.
If the router is configured to run OSPF NBMA and does not have
Static Neighbor configured it will not have Dynamic Neighbor in
the MIB even if adjacency with the neighbor can be established.
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 12575: Vines.
Zero hop count NetRPC search and search-all broadcasts are
forwarded even if ARP is not enabled on the interface. This can
result in broadcasts storms if a local Streettalk server goes down.
Note: There is a side effect of the repair for this problem. It was
determined that we should only forward Zero Hop Search (and
Search-all) packets when ARP is enabled on an interface. This
will cause problems using some applications in a network where
Remote Client Privilege is needed. When RC is needed, ARP should
be enabled on all Vines interfaces where there are no servers.
For example:
______ ______
| Vines| | ____ ____ | | |
|Client|-----| | |______ | | |----| Vines|
| | |____| R1 | /_______| R2 |----| |Server|
|______| | |____|^ |____| | |______|
^ | ^ ^
| | | |
Arp RC Arp RC
Here, Arp needs to be on the client side interfaces of both R1
and R2 to allow Zero Hop Search packets through to the server.
RC needs to be on the server side interfaces because the nearest
server is greater than 1 hop away from the client.
CR 12476: Packet Capture.
Unable to restart packet capture if the first PCAP file is too
large. To reproduce problem:
Calculate the maximum amount of memory allowed for Packet Capture
on a slot. You will be able to successfully run this capture
once, if you stop the capture when the trace is full, and attempt
to restart you get the following warning message for PCAP:
"wfPktCaptureBufSize for line xxx101 invalid"
The wfPktCaptureControl is set to 1 (start), but
wfPktCaptureCapture is set to 2 (stopped). It seems that the
memory resources are being checked but memory resources allocated
for the previous PCAP file are not being considered for the
PCAP file overwrite.
CR 12358: LNM.
Stations cannot insert onto a ring on which an ANts is the only
available Ring Parameter Server. Ring station sends out a Request
Initialization to the RPS functional address C00000000002, and
the frame is returned from the ring with the AR/FC bits set,
indicating an RPS is available. The AN does not return an answer
to this request (it sees them as illegally formatted), and after
3 retries the ring station exits from the ring.
CR 12423: IP.
IP router allows various types of invalid IP subnet masks. The
IP interface should not come up when an invalid IP subnet mask
is configured.
CR 12436: Vines.
Vines internal network table gets corrupted in a Vines network
with redundant links. This causes servers behind a router to
become unreachable even though the MIB has a valid metric for
the route.
CR 12409: OSPF.
OSPF problem when 2 wf routers are configured as follows:
------- Area A1 ------- Area A2
| R1 |-----------| R2 |--------------
------- Network N1 ------- Network N2
When both routers come up for the first time and establish a full
adjacency network N2 is advertised into A1 by R2 as a summary
link, installed as such in R1's lsdb and also appears in R1's
ip routing table.
At this point R1 is rebooted. When it comes up and establishes
a full adjacency with R2 it correctly installs N2 as a summary
link in the lsdb but N2 is now missing from R1's routing table.
CR 11031: Vines.
When Vines Fragmentation Protocol (FRP) is disabled on a WAN
interface, a bus error panic will occur when the sync interface
is disabled and enabled.
CR 12260: Netboot.
Netboot does not work when bofl is configured on a sync line.
CR 10597: Spanning Tree Bridge.
Non-root AN sync port detect topology change under no-load
conditions. Log messages stating "spanning tree topology change
detected, sending TCN out port %x" have been seen on the non-root
bridge of a two AN-ES test configuration. Port %x is the sync
port connecting the AN's. This behavior is causing increased
packet loss over the sync pipe.
CR 11376: LNM.
LNM can cause 'out of memory' slot resets when receiving excessive
non-isolating errors.
CR 11529: OSPF.
OSPF no longer advertises attached external interface after CSMACD
bounces. External interface is up and appears in the routing table
but is not found in the LSDB. This occurs after the CSMACD has
bounced (seen in the log). All external routes learned over that
external interface are no longer reachable from the OSPF network.
CR 11638: IP.
The propagation of a zero subnet over the same network/different
IP subnet will not get installed into the IP routing table. This
failure can be seen when the following scenario exists, standard
class b network is sub-netted with a class c mask and a zero subnet
exists within network.
CR 11877: OSPF.
ospf.bat script incorrectly displays two-word neighbor statuses.
CR 11829: IPX.
If the destination network of a SAP entry does not exist in the
routing table, IPX may panic while calculating the nearest server.
CR 11704: X.25
Querying the router for its MIB-II ifTable on an interface configured
for X.25 returns the value 6 for the ifType. The value 6 is
enumerated to ethernet-csmacd in MIB-II.
CR 11692: System.
Slot resets infrequently occur with an 'out of GID' error in the log.
CR 10388: XNS.
The show xns routes script displays the next hop host but NOT
the next hop network.
CR 12184: Spanning Tree Bridge.
A slot may incorrectly consider it's Bridge ID to be Root.
CR 11557: OSPF.
OSPF routes learned over a virtual link are not processed
properly on the backbone router that is receiving them in certain
(large routing table) topologies due to a non-recoverable
hogs bufs situation.
CR 12376: IP.
Arp Request is discarded if the source IP address is not in the
same subnet (12376).
CR 12373: SNMP.
Snmp packets containing a get request for 24 or more objects
causes various problems (usually ASN1parse errors).
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 11611: System.
Various unexplained RPC Timouts in mib_ent.c.
CR 11677: OSPF.
OSPF virtual link will cause OSPF resets at versions > 8.0.
CR 10842: System.
A VME router fails to boot properly with very large config files.
Some slots are unable to receive the config info.
CR 12086: Circuits.
Enabling Hardware Filters in ESAF 5531-2 Link Modules caused the
interface to hung in the initialization state if it was
configured via install.bat.
CR 11934: IP.
Under very heady loads, routing information may not be properly
maintained after IP on another slot resets.
CR 10520: Source Route Bridge.
A source route packet with length field bits set to 3 (4472)
that originates on a Token Ring segment will have the length
field decreased to 2 (2072) when it crosses an FDDI ring.
CR 12134: OSPF.
OSPF does not properly notify IP when an LSU is received with a
change of MASK.
CR 12127: Token Ring.
The Token Ring interface on an AN will continuously reset with a
timeout error on a network that is very busy. Some example log
messages are;
Connector MAU1 Cmd (0xa) time-out (s=008c)
(a=0000 0000 0000 0000).
Connector MAU1 stop... env->phy_addr = 04000000.
CR 10722: IP.
IP connectivity can be lost while aging hosts. This is due to the
routing table getting corrupted if no buffers are available while
Host aging is happening.
CR 12115: IP.
Receipt of a RIP broadcast sourced from another network results in
an Error: exception vector 2 - Bus error. Receipt of multiple
broadcasts back to back may result in IP restarting. A likely
configuration where this may occur is a multi-net'd environment
where the suspect router is only partially or non multi-net'd.
CR 11589: Source Route Bridge.
Source route bridge filter setup to drop all routes explorer frames
based on the RIF length do not drop the frames in 8.01. The same
filter works in tests on 7.80 fix 3 and 7.71 fix 4.
CR 12085: DECnet.
DECnet Level 2 router doesn't listen to the DECnet Level 2 router
multicast. This problem was previously reported by CR 8599 and
fixed in v7.80 (also version 7.71 fix 5).
CR 11814: PPP.
OSI over PPP may not be established; The OSI NCP remains in closed
state. This can happen to any NCP, not just OSI. The problem will
appear if the remote router sends a PPP Protocol Reject packet to
WF in response to WF sending a PPP Configuration Request packet.
RFC 1548 specifies that the NCP should remain in whatever state it
is in when it receives the Protocol Reject, and that the NCP should
stop sending out whatever is causing the peer router to send back
Protocol Rejects. Instead, WF router is generating a closed event
and transitioning to Closed state. This prevents us from
establishing a connection if/when the remote router ever does
send a Connection Request.
CR 11977: Vines.
Running Vines over Source Route Bridge using End Station support
may result in RIFs being changed too often causing Vines servers
to go into suppression.
CR 10870: IP.
IP router does not update ARP Cache according to RFC. RFC 826
suggests the desired algorithm for receipt of an ARP request is
for a receiver (even though he may not be the target) to update his
ARP Cache when a request is received containing a new source MAC
address for an entry that already exists. The IP router does not
update the ARP cache for existing entry upon receiving ARP request
containing new source MAC Address if the ARP destination is not for
the local interface.
CR 11857: System.
An orphan buffer error can appear in the log with the source gate
ID value in the 0x400 range (I.E. 0x401, 0x402, 0x403 etc).
CR 11370: OSPF.
Version 7.xx advertises default summary with stab metric of 0 into
a stub area. Version 5.78 does not have this problem. The metric
for the summary link advertisement is set to the (per-area)
configurable parameter Stub metric.
CR 11596: MIB.
The Mib stat if.ifOutErrors can be erroneously high on enet
circuits. It appears that the mib stat
wfCSMACDEntry.wfCSMACDDeferredTx is incorrectly being added in
the calculation of if.ifOutErrors.
======================== Version 8.01 fix 1 ==============================
The image for FRE hardware is: 1773483 Dec 20 12:40 boot.exe
The image for VME & AFN Floppy hardware is: 1651186 Dec 20 12:59 ace.out
The image for AN hardware is: 1544831 Dec 20 13:36 boot.exe
The image for IN & AFN Flash hardware is 1645144 Dec 20 14:07 boot.exe
----------------------------------------------------------------------------
CR 4270: Source Route Bridge.
In source routing environment Apple end stations issue test frame
with 0xAAAAF3 dsap_ssap_ctrl field to the router. The router doesn't
reply to this frame and Apple end station support doesn't come up
on the network.
CR 11754: IP.
When IP circuits are disabled/enabled, OSPF HELLO packets can be
sent to wrong subsystem causing unpredictable results (like
orphaned buffer log entries).
CR 11006: DLSw.
The loss of a number of segments in the IP cloud between 2 routers
running DLSw causes a high number (70+ %) of TCP retransmissions
for the rest of the life of the connection. Slots can also reset
with out of memory errors.
The out of memory resets were caused by the method of handling
broadcast frames which are not flow-controlled - if TCP was busy
DLS would try to save incoming broadcast traffic for as long as
there is memory on a slot. In some cases this would result in DLS
eventually using up all available local memory causing a slot to
reset. This problem has been resolved by the following improvements
to the configurability of DLS.
Three new MIB attributes were added to the wfDlsSlotEntry MIB object.
wfDlsCurrentMemory -- to reflect the amount of memory in kilobytes
currently used by DLS on a particular slot.
wfDlsMaxAllowedMemory -- this is a configurable parameter. It
reflects how much memory in kilobytes DLS
is allowed to use on a particular slot.
When this number is reached DLS would start
dropping incoming traffic. Thus preventing
a router from crashing. The default value
is -1, Which means infinity. (all available
memory).
wfDlsHiWaterMark -- to reflect the highest memory consumption
in kilobytes reached on a particular slot
by DLS since the last reboot.
The last attribute is intended to be used in the following way.
Since every customer environment is different and it is hard to
predict an average traffic load, the user should let a router run
with wfDlsMaxAllowedMemory set to the default value for sometime.
Assuming there were no unusual events during this period of time a
user should set wfDlsMaxAllowedMemory to wfDlsHiWaterMark or some
number close to it. For example: after booting wfDlsMaxAllowedMemory
is set to -1. wfDlsHiWaterMark is 0. wfDlsCurrentMemory is 0.
Looking at the above attributes after 3 days one sees
wfDlsMaxAllowedMemory is still set to -1. wfDlsCurrentMemory is 100
and wfDlsHiWaterMark is 300. Now if you set wfDlsMaxAllowedMemory
to 300, it would assure that in an emergency situation DLS would not
run a slot out of memory because of the unlimited consumption of
memory. The optimal amount of memory allowed to be taken by DLS
should be determined experimentally for the particular configuration.
Access to the above attributes is available from TI only for now.
The Site Manager support for this enhancement will be implemented
in a later release.
CR 10922: PPP.
AN is connected to a Network Systems router via sync port. Sync
port is configured for PPP with bridging and IP. IP comes up fine.
When the BNCP negotiation takes place the Network Systems router
sends the AN a BNCP configure reject for all mac types (FDDI
ETHERNET and TOKEN RING). When the AN receives the configure reject
a bus error Panic occurs.
CR 9839: Bridge.
Setting up Bridge Traffic Filters to drop IP broadcast traffic
while bridging and running IP 'Not Forwarding' mode does not
work. The Traffic Filters are not applied.
CR 9175: SMDS.
Router responds to SMDS heartbeat poll on logical link 0 instead
of logical link 1.
CR 10685: Source Route Bridge.
Running NetBIOS Caching may cause panic in sr_nb_process_are due
to RIF entries being aged while the same RIF entries are being
relearned.
CR 10684: Source Route Bridge.
Running NetBIOS Caching may cause a 'PANIC in mib_ent.c at line
710' due to RIF entries being aged while the same RIF entries
are being learned.
CR 10543: System.
Slot resets with 'System restart in tmo_wdog.c at line 51' when
XNS router learns many (500) routes after wan link goes down/up.
CR 10498: NML.
Slot running NML can bus error in tfind when bridging traffic .
CR 10412: Bridge.
When Learning bridge traffic is flooded over FDDI onto a Frame
Relay network the router at the remote side does not flood the
bridge traffic out its other interfaces which reside on the same
slot as the Frame Relay interface.
CR 10557: AppleTalk.
Slot routing AppleTalk can experience Tag Violation reset upon
receipt of illegal NBP tuples.
CR 9870: OSPF.
Dynamic disabling of an OSPF interface can cause a PANIC bus
error on non-backbone routers.
CR 9958: Vines.
Vines router does not respond to StreetTalk requests from clients
on serverless segments.
CR 10314: DECnet.
In particular configuration DECnet router sends incorrect level
2 routing message designating local area as 1 hop and some non
zero cost away.
CR 10790: System.
On an ASN the attribute 'HwModuleModRev' was 0 all the time
instead of displaying the true Net Module revision number.
CR 9690: OSPF.
The External Route Tag Field within an OSPF AS External Link
State Advertisement is inconsistent when the ASE is generated
from a 7 series router. The use of this field, although not
documented in the OSPF specification to this effect, in the 5
series is to list the IP address of the gateway from which an ASE
Type 2 was originally learned via RIP (or other protocol). The 5
series does this consistently and has proved to be an invaluable
troubleshooting tool when debugging a large OSPF network where
there are multiple routers advertising the same ASE Type 2s. The
7 series on the other hand, will use the field in the same way
initially, but seems to lose track of what data is actually being
plugged into the field if the ASE Type 2 is refreshed for any
reason. An example of when this might happen is if an ASE Type
2 is aged, flushed and then relearned and refreshed again. The
External Route Tag field may look fine in an advertisement prior
to and when it is actually flushed, but when a new instance is
generated, bogus data may appear in this field.
CR 10696: Bridge.
Learning bridge over token ring does not learn about station
moves as it should.
CR 10745: Switched Services.
Enhancement for Dial-on-Demand circuits to allow the configuration
of the inactivity timer to be in seconds instead of minutes. Note
that this change affects existing config files such that what the
network administrator previously configured in minutes is now a
value in seconds.
CR 9225: Bridge.
8743: Bridge traffic doesn't properly switch back to the primary line
from a dial backup one. The router may stop learning and taking
incoming traffic from the sync port. Also the router may loop
back broadcast packets in the sync port.
CR 10787: IPX.
IPX router does not age out rip entries received with a hop
count of 15.
CR 9999: IPX.
Slot can reset with 'Out of Memory' errors when IPX interface with
many (> 400) hosts entries goes down.
CR 10667: IPX.
IPX Routes May Fail to Age Properly. The Lost Route implementation
incorrectly forms the packet to be sent out in the case where that
route was learned to be dead (hop count of 16) from a different
interface than the one that the route was originally learned from.
CR 10819: XNS.
XNS can restart on the slot where one or both sync lines in a
multiline configuration go down/up.
CR 10746: IPX.
IPX router responds to Get Nearest Server request when sap
filters are configured on the same interface where both a
server and a client reside (10746).
CR 10859: IPX.
IPX router does not correctly forwarded IPX Netbios frames
(type 14h).
CR 10857: IPX.
IPX router doesn't update its SAP advertisement after socket
number changes.
CR 7221: IP.
IP and OSPF remain up when FDDI interface is disconnected.
CR 10616: IPX.
Accept option doesn't work properly for IPX Traffic Filters.
CR 10569: IP.
When deleting one IP address from a multinetted interface arp
will no longer function correctly. If an IP address gets deleted
from a multinetted interface all devices on remaining network
will be unreachable.
CR 10029: Filters.
When configuring outbound filters based on source or destination
MAC address, the MAX address must be entered in canonical format.
The problem then arises that when entering a MAC address range in
canonical format, the high address range could end up with a lower
value than the low range and Site Manager will give a message
'Minimum Value Greater Than Maximum Value'. Added a new MIB variable
'wfCctOptsEntry.wfCctOptsMacFilterFormat'. The default is 1,
which is canonical. Setting this to 2 will allow entering MAC
filters in token ring format. (Note: All filters on the interface
must be in token ring format!). Site Manager support for this option
will be implemented in a future release.
CR 10724: Switched Services.
If multiple packets are sent to a dial on demand circuit in quick
sequence bus error/panic will occur before the modem dials out.
The packets in this case were ip encapsulated source route
explorer packets.
CR 10563: Vines.
When running Vines over Frame Relay with Vines Fragmentation
Protocol (FRP) disabled, Vines traffic will not be forwarded.
CR 10702: IP.
Although a Wellfleet router running version 7.80 and 8.0 software
can transport DHCP requests/replies, there are still areas where
Wellfleet routers are not 100% RFC1532 compliant.
1) The BootP Relay agent should only care about UDP BootP Server
packets (port 67). The current code registers and processes for
both BootPC and BootPS ports. A relay agent MUST silently discard
any received UDP message whose UDP destination port number is
BootPC (68) in paragraph 4.1 of RFC1532.
2) Seconds field should apply to request packets only so one can set
the seconds field to a non-zero number and still let 0 second
replies through. Our implementation checks both request and
replies. The Microsoft implementation has a minor problem of
not setting it to 0 initially and not incrementing it
subsequently (see paragraph 3.2 in RFC1532).
3) The newly defined Broadcast flag is not checked in the current
code, the correct behavior is to broadcast only if 'ciaddr'
field is zero and the flag is set. (See paragraphs 3.1.1 and
5.3 in RFC1532).
CR 10582: Switched Services.
The dial backup link is not initiated in the following cases:
1. When the modem is set to loopback.
2. When Rx wire is being disconnected either on the master or on
the slave side.
This has been resolved by enhancing the sync drivers to check
for the BOFL packets and detect the loopback condition. The
loopback is detected by comparing the source MAC address in the
BOFL packets with the sync interface's MAC address. When the
loopback is detected the sync line driver is brought down. When
it is trying to come back up it goes into loopback state and stays
in it until it receives the BOFL from the remote side.
A new MIB attribute 'wfSyncRemoteLpbkDetection' has been added to
the wfSyncEntry. The above actions will take place only if this
attribute is set to ENABLED. This has been done intentionally since
most customers are using loopback for verifying that the link
functions properly. Site Manager support for this option will
be implemented in release 2.10.
CR None: System.
System reliability is now improved on ACE32 processors by the
addition of a watchdog process which will restart a slot if a
single task runs for more than 16 seconds.
CR 10793: IPX.
IPX ping over token ring fails intermittently.
CR 10814: DECnet.
DECnet router does not generate triggered update when adjacency
comes up.
CR 10966: DECnet.
DECnet router may experience a hogs bufs condition which could lead
to multiple PANICS when a topology change occurs. The specific
topology change would be in the form of a number of adjacencies
going unreachable at the same time and the presence of at least one
other router sharing a common segment. What can happen is that when
the adjacencies time-out, DECNET, which does not support
split-horizon, counts to infinity to age out the routes. During
this time of counting to infinity hogs bufs can occur. Also,
counting to infinity takes more CPU cycles than it should.
CR 11231: IPX.
Multiple instances of the same IPX route will appear in the MIB
if a router has multiple connections to another router, even
with multi-path turned off.
CR 10860: Vines.
A network that routes Vines and also has end station support and
servers that are redundantly linked to the bridged network,
may show servers as unreachable on the remote slots where Vines
is routed.
CR 10885: DLSw.
DLSw may cause a MIB panic when deleting instances after
failure of multiple DLSw sessions.
CR 11369: IP.
IP router loses track (has no ARP entry and doesn't send ARP
request for new one) of host entries after another slot resets.
CR none: IPX.
When IPX responds to Get Nearest Server, in the case of a tie in
the hop count to a number of different servers, IPX router should
respond with the one that is first in alphabetical order, which
is not the case starting with 7.71 fix 7. This problem was
introduced by the fix for CR 10746.
CR None: System.
The message 'gate 0x0c1fe being killed by 0x00049 @ 0x304a2c3e
is dead - ignored' frequently appears in the log. Although this
message can be generated from many subsystems, one particular
problem involving HostCache which produced those messages is
now resolved.
CR 8101: System.
Slot Resets with 'checksum error found in old system log'. The
entire system log for that slot is then lost. System log validation
has been improved to be more discriminating when making its decision
to eliminate a slot's damaged log.
CR 11095: DLSw.
DLS, when configured for an ethernet interface erroneously
responds with a Disconnect Mode packet to sna bind requests
which are destined to hosts on the same local ethernet segment.
This problem has the effect of preventing sna sessions between
hosts on the local ethernet segment from working.
CR 11366: IPX.
IPX is incorrectly processing SAP names followed by NULL chars and
ending with garbage characters. The problem shows up as large SAP
tables with many duplicated entries which are all the same server.
This causes the router to send out many SAP packets with what
appears to be the duplicate server entries.
CR 11168: OSI.
OSI router fails to accept packets with pad bytes before the
NLPID when received over PPP interface.
CR None: IPX.
The maximum number of IPX SAP filters per interface that can be
configured has been increased from 50 to 150.
The Site Manager support for this enhancement will be implemented
in versions 2.00 fix 1 and 2.1.

Feedback | Service Search
| ERC
Copyright
© Bay Networks,Inc., 1997. All rights reserved.
|
/tr> |