 |
|||
     |
|||
|
Revision Notes for Router Software 8.11 rev 2
Date: 7/25/95
Subj: Revision Notes for 8.11 fix 2
===========================================================================
SITE MANAGER COMPATIBILITY
===========================================================================
Router version is managed by Site Manager version
v8.11 2.11
8.11 fix 2 2.11
======================== Version 8.11 fix 2 =============================
The image for FRE BN hardware is: 2603251 Jul 21 15:33 bn.exe
The image for FRE ASN hardware is: 2490679 Jul 21 15:34 asn.exe
The image for VME & AFN Floppy hardware is: 2388828 Jul 21 16:18 ace.out
The image for AN hardware is: 2330169 Jul 21 15:41 an.exe
The image for IN Flash hardware is: 2499609 Jul 21 16:02 in.exe
The image for AFN Flash hardware is: 2268113 Jul 21 16:02 afn.exe
The image for BNX BN hardware is: 1671531 Jul 21 16:27 bn.exe
The image for BNX ASN hardware is: 1548863 Jul 21 16:27 asn.exe
- --------------------------------------------------------------------------
Revision fix/8.11/2 corrects the following problems:
===========================================================================
CR 14782: IP.
Outbound filters based on the UDP header of a SRB frame
encapsulated in IP can cause a fragmented portion of the
frame to be dropped.
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 display 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 14601: LLC.
An "Out of Memory" or "Insufficient Memory" crash may occur on a
slot running LNM/LLC if the IBM LNM station within the network
gets permanently hung in a "Data Loss" condition and is not reset
for a long period of time. LNM data to be forwarded by LLC gets
queued up indefinitely because the LNM Station will not
acknowledge any LNM frames sent by LLC.
CR 14728: VINES.
When upgrading a router from pre-8.10 (non-sequenced RTP) to
Version 8.10 (sequenced RTP), VINES will hog buffers. Eventually
the slot will run out of buffers, sometimes causing a fault that
will reset the slot. Other times, however, the free space will
remain at 0, and the slot is rendered useless.
CR 14948: Source Route Bridge.
While the router is logging the following message:
"sr_rte: ccb not found, dropping frame",
if SRB is disabled and then enabled, the SRB will
FAULT in sr_rte.c at line 150.
CR 13422: IPX.
IPX Routes may fail to age in redundant configurations where
multiple IPX networks span multiple slots between two routers.
CR 15257: DLSw.
NetBIOS broadcast type frames are being rebroadcasted out the
interface on which they were received.
CR 16055: 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 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 prevents SNA sessions between hosts on the local
Ethernet segment from working properly.
CR 15399: LAPB.
Bus error in g_brestore occurs after LAPB receives RNR during
periods of heavy traffic. All of X.25 SVCs are cleared by the bus
error.
CR 14838: OSPF.
Adjacency of misconfigured routers is formed when an intended
Point-to-Point link is configured as point-to-point on one end
and Broadcast on the other end. This adjacency corrupts the
routing table if other optimal paths do not exist. Any routes
that would normally point back out the intended Point-to-Point
interface end up with 255.255.255.255 as the next hop on the
router with Broadcast configured. The router with
Point-to-Point install no routes.
CR 14393: TCP.
DLS may fail to reestablish its TCP sessions after the interface
failure.
CR 15696: DLSw.
NetBIOS NQ storm can cause a crash.
CR 14537: RIF.
Translation Bridge presently updates the RIF to a source routing
end station each time it receives an explorer frame with that
station's source MAC address. If the station sends an all-routes
explorer and redundant paths are on different slots, XB will
receive multiple copies and update the RIF on its local slot, but
both paths will update Learning Bridge. This may result in a
less than optimal RIF since the last explorer received may have
traversed the slowest path.
CR 15389: BGP.
BGP4 Route Policies do not support AS_PATH Pattern Matching as
is required by Internet Provider market.
CR 15650: Multiline
If you multiline 4 E1 circuits using the Addressed Based
algorithm, the load is not shared evenly on the four lines when an
even distribution of addresses exists.
CR 13919: DLSw.
DLSw sends out NetBIOS NameRecognized frames on the same
interface from which they are being received. This causes a
connection failure between NetBIOS clients and servers.
CR 15562: LNM.
When there is 28 or more circuits (including LLC circuits) already
defined, a circuit will fail when you add LNM and LLC to it.
CR 7505: DLSw.
Bay Networks sends the data from Test frames in the CANUREACH,
but other vendors (IBM, Proteon) do not return the data in the
ICANREACH. This causes problems establishing sessions because
Test responses will contain inappropriate data.
CR 14797: LNM.
An LNM station will be unable to link with the router when the
router is booted with a DLSw sap entry of 0. If this DLSw sap
entry is added dynamically once the router is up, the LNM station
is able to link.
CR 15332: Frame Relay.
When a SYNC line on a BNX switch is running at a speed less than
the access line at the other end of the PVC, then the SYNC line
drops MGT frames and the PVC goes down when the higher speed end
of the PVC is transmitting to the lower speed end of the SYNC.
CR 15475: Frame Relay.
Buffering LMI, or a delay in responding to LMI from the router
causes switch sequences number mismatch ì event messages.
CR 15158: DLSw.
Bus Error occurs when using DLSw Wan Keepalive Timer and TCP
connection is not fully established.
CR 12402: ISDN.
While dynamically changing the ISDN Switch type with Site Manager,
you may see an error in the log. Everything appears to recover.
CR 15101: ISDN.
Bus error may occur and system restart when deleting a SBOD pool.
CR 15775: DLSw.
A router participates in a local negotiation which eventually
results in a connection failure.
CR 15275: LLC.
Unsolicited "Final" bit response was rejected according to
IEEE 802.2 standard. The finite state machine has been changed
to process the unsolicited "Final" bit response as if the
"Final" bit were set to 0 based on the IBM Token Ring Network
standard.
CR 15424: SDLC.
In a Multi-drop environment, if the remote controllers are
brought down by VTAM, and if one or more controllers is VARY'd on
at the same time, they will come up without a problem. If any of
the remaining controllers are left VARY'd off for approximately
5-10 minutes, then try to VARY On; they will never become active.
CR 15240: DLSw:SDLC.
In DLSw SDLC conversion, the Local Device Canureach Retries
default value should be changed from infinite to 5, to prevent
hung connections on the LLC side when SDLC goes up and down.
CR 14800: DLSw.
In a dual switch DLSw configuration, if the WAN link is disabled
the TCP connection is lost but left opened. An SNA device
continues to send Test Polls for 80+ connections and DLS starts
reporting the message: "TCP connection nnnnnnnn congested,
issuing RNR". After a few of these reports, the slot will
experience a bus error in dla_tcp_tx_op_act.
CR 12846: SWSERV.
After the bring up time is reached on a demand circuit, calls
will not be made until a minute later.
CR 13963: OSPF.
If the customer has IP/OSPF (Point-to-Point or Broadcast)
configured on a primary line (either PPP or WF standard) that
goes down, the backup line after it has been established will
lose IP connectivity.
CR 15246: IPX.
After rebooting, a router with an IPX dial-on-demand circuit
should establish a call, send its RIP and SAP data, and request
the RIP and SAP information from the called router. This works
with Version 7.80 and 8.01 routers, but not with Version 8.10
routers.
CR 16075 LNM.
When two or more LNM clients are connected to the router and
information is being disseminated to these clients, the
information is sent only to the client that was linked first.
CR 14944: Frame Relay.
If wfSyncEntry.wfSyncMediaType is set to the number 4, 5, or 6
when the frame relay circuit is coming up, the router panics when
the frame relay circuit is bounced.
CR 15333: DLSw.
When the origin router responds to the origin station with the
completed xid3, if there is more than 3 bytes of associated data
in the xid3 packet, it will be truncated at 3 bytes. This
situation occurs because the code was written with an 802.2 type
xid (3 bytes of data) in mind when the dest sap is null.
CR 15922: ARP.
PS2s running AIX do not respond to an ARP from the wf router
when end station support is configured. This is because the
router sends out an ARP as a STE, but with the largest frame bits
in the RIF set to 1¹s.
CR 16095: LNM.
When the router was the only station on the ring and the new
station experienced a problem attaching to the ring, the
established router would beacon and process its own beacons in LNM.
CR 16223: GAME.
The Free Running Clock (FRC) on the ACE platforms is supposed to
interrupt at one-second intervals. It actually interrupts at
about 1.02 second intervals.
CR 15355: LLC.
When DLSw is configured on a Token Ring interface, the interface
will experience a bus error upon receipt of a particular packet.
CR 16344: Packet Line Script.
An ASN module number cannot be configured due to an error in the
packet.bat script file. When starting the config packet line
command, the script will not ask for a module number even if
there is an ASN or ASN stack. The module number, therefore, is
always set to 1 for an ASN, and there is no chance to configure
the capture for modules 2, 3 or 4.
CR 16189: ICMP Message.
Router does not respond with ICMP Destination Unreachable when
pinging an IP address in the net of a disabled interface. This
interface either can be its own interface or one of the stations
connected via that specific interface.
CR 14317: IP Router Filters.
While converting router filters to policies, route RIP import and
export filters are not applied in the correct order after upgrade
from 7.80 to 8.01/8.10.
NO CR: FDDI.
Booting a BCN by configuring DLS on an Interface and TCP cloud on
a CSMA/CD interface results in a race condition between two
registrations of SAP 02.
CR 15929: NLSP.
A router may be unable to handle GNA from clients in a timely
fashion due to a high rate of incoming GSQ request in an
interface. Depending on the size of the required response
(number of packets) and the rate of GSQ's, the router may never
recover as GSQ and GNSs will in most cases originate retries,
thereby exacerbating the problem.
CR 16564: LNM.
When running LNM with the Ring Parameter Server enabled, a router
may fail to respond to Ring Initialization Requests from certain
stations when they attempt to enter a ring.
CR 15997: DLSw.
When configured for DLS, a peer router will log the following
message: "Connector MAU1 Bad frame length on transmit request:
SO=010a EO=0101". This message will occur upon arrival of a
NetBIOS test poll frame (dsap=00/ssap=f0) via TCP.
CR 16373: SRB.
Packets that are translated from LB to SRB that will be using an
ARE or STE will have invalid largest frame (lf) field in the RIF.
CR 15086: IP.
An IP interface configured for end station support on a Token
Ring will send an ARP using an STE (Single Route Broadcast). It
is desirable to have ARP use an ARE (All Route's Broadcast) in
certain situation's.
CR 13418: VINES.
Two BLN routers situated back to back connected via X.25 will
result in PPP and SMDS bus errors in VINES. In addition, no
traffic is being generated during this period.
CR 15397: PPP.
Dial-on-demand between Bay Networks¹ and NON-CHAP routers fails
with ISDN when non-CHAP routers initiate the call.
======================== Version 8.11 fix 1 =============================
The image for FRE BN hardware is: 2589945 Jun 21 14:46 bn.exe
The image for FRE ASN hardware is: 2477862 Jun 21 14:46 asn.exe
The image for VME & AFN Floppy hardware is: 2374448 Jun 21 15:00 ace.out
The image for AN hardware is: 2318086 Jun 21 14:57 an.exe
The image for IN Flash hardware is: 2484846 Jun 21 14:47 in.exe
The image for AFN Flash hardware is: 2253781 Jun 21 14:47 afn.exe
The image for BNX BN hardware is: 1658167 Jun 21 15:10 bn.exe
The image for BNX ASN hardware is: 1535915 Jun 21 15:10 asn.exe
__________________________________________________________________________
CR 14692: MCE1 Driver
MCE1 was known to shutdown logical lines due to excessive Rx
errors caused by noisy lines. Performance improvements have been
implemented in the 8.10 Munich driver that will enable it to
handle excessive Rx errors (queue overflows) without disabling
logical lines. During periods in which the 8.10 Munich driver
is experiencing excessive Rx errors, the driver will log an event
log message. This message will appear only when CPU-intensive
software is running at the same time logical lines are
experiencing excessive Rx errors. If the log message occurs
at a significant rate of more than a few minutes, then the user
should determine which logical lines are experiencing excessive
Rx errors and disable them. The software no longer disables
logical lines automatically.
CR 15302: IP
Static routes no longer set the address resolution type for
individual networks when submitting the routes to IP. Instead,
address resolution is set to DDN X25 type for the next hop at the
IP level, based on the Network Interface address resolution type.
CR 13259: Source Route Spanning Tree Bridge
12305
10305
12274
When configuring Source Route Spanning Tree Global parameters
in local configuration mode, users no longer need to enter a
bridge priority and MAC address. Rather, the router software
sets the bridge priority to its default value (128) automatically
and it learns the MAC address during boot up and assigns this
address to the router.
CR 15441: LNM
When a circuit with Source Route bridge and LNM is enabled
where the microcode is Fast Mac Plus and there is traffic on the
ring, the group address may not get loaded. As a result,
Specifically Routed Frames (SRF) are not received and source
routing will not work.
CR 15068: System.
The wall clock time on a FRE based router jumps ahead periodically.
If enough time has elapsed for the resync to occur, it will correct
itself. The jump will occur on all slots at the same time. This
problem could be noted by the output of a 'date' command.
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 14025: Source Route Bridge.
Source Routing over PPP, FR, or SMDS causes bus error when the
WAN interface goes down/up.
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
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
