Revision Notes for Router Software 8.11 rev 4
===========================================================================
SITE MANAGER COMPATIBILITY
===========================================================================
Router version is managed by Site Manager version
v8.11 2.11
8.11 fix 1, 2, 3, 4 2.11
======================== Version 8.11 fix 4 =============================
The image for FRE BN hardware is: 2617326 Sep 22 16:42 bn.exe
The image for FRE ASN hardware is: 2504629 Sep 22 16:42 asn.exe
The image for VME & AFN Floppy hardware is: 2401472 Sep 22 17:26 ace.out
The image for AN hardware is: 2347269 Sep 22 17:03 an.exe
The image for IN Flash hardware is: 2513949 Sep 22 19:03 in.exe
The image for AFN Flash hardware is: 2281948 Sep 22 19:03 afn.exe
The image for BNX BN hardware is: 1692141 Sep 22 18:00 bn.exe
The image for BNX ASN hardware is: 1569234 Sep 22 18:00 asn.exe
----------------------------------------------------------------------------
Revision fix/8.11/4 corrects the following problems:
=============================================================================
CR 13948: Protocol Prioritization.
Protocol Priority may not prioritize traffic properly in some
configurations.
CR 12828: FDDI.
The optical bypass switch is not brought into bypass mode before
the BCN's FDDI interface is brought down. As a result, the FDDI
ring may wrap.
CR 14853: MIB.
When a multiline circuit is configured between two routers, the
counters for ifInOctets and ifOutOctets are incorrect for the
added multiline circuits. This condition is evident when comparing
the "ifInOctets" or "ifOutOctets" to that of "wfSyncRxOctets" or
"wfSyncTxOctets".
CR 16490: IPX.
The IPX end station RIF cache upon encountering a slot
reset becomes corrupted, causing the router to send out traffic as
Single Route Broadcasts instead of Specifically Routed Frames.
This condition occurs repeatedly even after a station has been
cached correctly in the corresponding MIB table (wfBrSrEsRifEntry).
This causes the router to produce excessive amounts of unwanted
traffic, which can adversely affect network performance.
CR 14874: IP.
When the slot with proxy ARP interface resets, IP connectivity
between specific stations on that segment and stations
using a subnet address in other segments may be lost indefinitely.
CR 16922: IPX.
IPX may fail to install a locally-defined route to a network
as the next hop to that network if an equal cost learned route
exists when that interface first comes up.
CR 15324: ARP.
In a Spanning Tree environment with IP host-only mode, ARP sends and
receives packets only on interfaces on which a bridge port is
forwarding. As a result, you cannot ping across the router after
bouncing a circuit or upon booting the router.
CR 17018: TCP.
Watchdog timeouts occur when TCP receives a corrupted packet with
TCP option length of 0. TCP skips over any invalid
option lengths and processes any that remain. If the option length
is zero, the current option pointer does not increment, thereby
causing an infinite TCP loop to occur.
CR 16603: DLSw.
If there are two or more SNA sessions generating traffic over a DLS
Switch configuration and the DLS Base record is bounced, a bus error
occurs, causing temporary loss of connectivity.
CR 17602: IP.
When configuring IP over Frame Relay, the default Address
Resolution type, ARPINARP, does not work correctly over Direct
Mode Pvcs. Enabling a Frame Relay interface should generate
Inverse ARP, which allows the discovery of all nodes.
CR 17676: ARP.
Routers send out ARP over Frame Relay with inconsistent source
hardware addresses. This causes remote routers to flush the ARP
entry of the sending router, resulting in an ARP storm in large
fully-mesh Frame Relay networks.
CR 15761: IP.
Upon receipt of an IP ICMP time stamp request packet, the
router responds but does not fill in the receive timestamp field
or the transmit timestamp field. Instead, it places a zero value
in the timestamp fields.
CR 17764: ARP.
Router in host-only mode fails to re-Arp for hosts after an
interface is bounced.
CR 16976: OSPF.
The following OSPF debug message was incomplete:
"ospf_soloist_proc_bufs_rcvd_buffer with unknown ospf type %d"
The actual OSPF type should be substituted for %d.
CR 17505: OSPF.
The SPF counter increases at an excessive rate because it is
incremented multiple times for a single ASE update.
CR 17549: IP.
IP static route entry does not recover after a Frame Relay
line goes down and is brought back up again.
CR 18180: IPX.
The command "Show IPX routes" may hang in certain redundant IPX
topologies.
CR 17886: IPX.
When you boot a router with 8.11/1 or later using a configuration
that has an IPX static route, the route does not appear in the
routing table unless the IPX base is bounced. This condition
occurred with an IPX static route with the next hop being a Frame
Relay network with a direct mode PVC.
CR 13822: DLSw.
When configuring DLS in dynamic mode from Site Manager, a panic
occurs. This condition occurs after completion of the slot
configuration.
CR 16888: DLSw.
When a DLSw router is placed on an Ethernet, the router does not
create and delete local connections correctly. This behavior is
observed initially by having a large number of LlcLinkEntry
instances that do not correspond to the actual number of DLS
connections. As a result, the maximum number of 11c links is
reached, no additional connections can be created, and the
following message displays in the log:
# 105: 06/08/95 10:03:04.322 DEBUG SLOT 1 LLC Code: 11
Maximum Number of LLC connections already active
CR 18408: DLSw
A failure occurs when a client and server try to connect on an
Ethernet segment with a DLS router connected to it. The connection
between the client and server contains a XID frame. The
router responds to the XID frame with a test frame, which it sends
on the same interface on which the XID frame was received. This
confuses the client and server, thereby causing the connection
to terminate.
CR 18857: IPX.
IPX installs a RIP-learned route over a local route when the
interface tick cost is greater than the tick cost of the network
learned via a RIP advertisement from a different segment.
CR 9383: System.
When you reset a slot (reset ) while running a
Technician Interface session or a telnet session, the Fail LED on
the associated link module becomes active and remains active
indicating that a hardware failure has occurred. This is a false
indication.
CR 18606: Switched Services.
When running Dial Backup over ISDN where the WHOAMI negotiation
is skipped for Dial-on-Demand, the software fails to check
whether the line trying to come up is a Dial-on-Demand line or a
Dial Backup line. This causes a bus error.
CR 13359: Frame Relay Switch.
The wfFrSwCctXNetSent attribute is always set to 1.
CR 16622: FDDI/BNX Switch.
Multiple wfFDDIOverrunRx events occur on FDDI interfaces while
running ten switches on the same FDDI ring. Approximately 60-70%
of the traffic on the ring is being received by only one out of ten
switches. However, because the FDDI MAC chip operates in
promiscuous mode, all other switches are affected by this
traffic. Functionality is required to allow FDDI BNX Switch
to operate in non-promiscuous mode.
CR 13127: BNX Switch
Site Manager displays an incorrect circuit name for the MIB instance
wfFrSwCctEntry.
CR 13503: DLSw.
ACCEPT filter processing is working in Site Manager, but it fails
to work correctly in the router software.
CR 16810: PCAP.
Packet Capture, pktdump, and pktconv need to support SDLC protocol.
CR 14405: ARP.
An IP host entry will not be deleted if other stations continue to
send traffic through the router destined for that host. If traffic
has been sent to the host during the wfIpInterfaceHostCache time
period, the host entry keepalive will be updated and the host will
not be removed from the table. Thus, the hosts to which traffic
is frequently sent will never be deleted, even if the host has
disappeared.
CR 16119: BNX Switch.
BNX Switch software allows you to enter an illegal tuple;
that is, a tuple whose local or remote IP address is out of range
(contains field(s) greater then 255). When you try to correct a
tuple whose IP address is out of range, you may risk
deleting the entire tuple table inadvertently.
CR 15750: BNX Switch.
When you use the Technician Interface to add a DLCI and a
tuple without entering a commit in between, a panic occurs on all
slots.
CR 17164: PCAP.
When you use the packet capture scripts to configure PCAP, typing
in the line number displayed by the script leads to an error in
the script, unless you remove the leading zeros.
CR 15726: BNX Switch.
When you add blue (state 7) or yellow (state 6) alarm into the T1
line (McT1), the state of wfMcT1Entry changes to the Red Alarm
State (state 5), and wfMcT1Entry remains in this state
permanently.
CR 15436: BNX Switch.
BNX requires a new MIB entry to reflect the number of DLCIs and
tuples configured. The new MIB improves our ability to
monitor the capacity of the switch to prevent it from exceeding
the specified limits. The new MIB attributes are
wfFrSwUsageNumTuples and wfFrSwUsageNumDIccts. These MIB
attributes are located in wfFrSwUsage.
CR 17535: GAME.
A window exists in which the software watchdog is disabled on the
FRE. In this window, a gate will _not_ get a software watchdog.
Hardware watchdogs are acknowledged normally, which means that in
this window a gate could hang the system if it had an infinite loop.
This includes FRE, FRE-II and FRE-II/060.
CR 17692: SDLC.
XID¹s are not resent when contact timer expires.
CR 17303: SNMP.
An ASN stack with BRI faults upon receipt of a SNMP get-next
request. The HP-OV Demand Poll command is a example of such a
series of get-next requests.
CR 16192: DLSw.
The connection between LANDP/DOS and HOST fails over DLS.
LANDP/DOS (an IBM product) tries first to establish a connection
by using a XID format 8 (defined for external standards
organizations). If the connection request is forwarded in a
transparent way (source routing), the host returns a negative XID
response. In this case, LANDP/DOS establishes the connection
using XID format 0.
CR 17241: X.25.
The router generates an X.25 debug message that reports an
incorrect X.21 local and remote address. The router
displays only the left-most eight bytes of the address instead of
the eight right-most bytes, which are more significant in terms
of troubleshooting X.25 failures.
CR 17931: PCAP.
A bus error occurs if you use the Packet Capture command to
display SDLC packets from the Technician Interface.
CR 15473: X.25
Each time an X.25 PDN/DDN virtual circuit is cleared, 32 bytes
of local memory is lost.
CR 15506: X.25.
MTU is set to twice the sync MTU on an ASN interface when sync
protocol is LAPB. This causes IP to fragment packets at 3150 when
sync MTU is actually 1600. On the BLN router, the actual sync MTU
is sent to the upper layer applications, causing IP to fragment
packets at 1550 (1600 - some header information.)
CR 14716: TCP.
If you lose a TCP connection in a dual switch DLSw
configuration and the SNA device keeps sending test polls,
DLS eventually generates the following message:
"TCP connection nnnnnnnn congested, issuing RNR"
This message displays repeatedly, after which TCP logs the
following message to close the connection:
"TCP Closing xxx.xxx.xxx.xxx,2067 - xxx.xxx.xxx.xxx,2065 TCB:
0xnnnnnnnn".
A tag violation immediately follows this message.
CR 18204: VINES.
Running VINES in a redundant network with equal cost multiple
paths to servers can cause a redirect packet that contains incorrect
information to be sent to an end station. As a result, the end
station is unable to reach the server.
CR 16350: VINES.
In a redundant network, routes are not being removed from the VINES
routing table. Instead, they are are being passed from router to
router, thereby gradually increasing the metric and causing severe
performance degradation.
CR 17729: VINES.
It is possible for some routes to get incorrect sequence numbers,
rendering some networks unreachable.
CR 14860: MIB.
A MIB query for ipRouteEntry.ipRouteIfIndex may incorrectly
return a value of zero for learned OSPF routes.
CR 18266: GAME.
Added the Resource Statistics utility. This utility supplies
utilization values for buffers, CPU, and memory on a per-slot
per-subsystem basis. A subsystem is defined as the kernel and any
dynamically loadable module. Each subsystem's statistics are kept
on a per-slot basis.
CR 18027: Compression.
Two routers that are transmitting DLSw NetBIOS traffic across an
unnumbered IP Interface on a PPP link suddenly experience loss of
compression.
CR 17896: VINES.
VINES neighbors may end up with an incorrect metric, causing
VINES redirect (RDR) packets to be sent to networks that are
situated on the other side of the given neighbor.
CR 18468: Compression.
When you enable compression on a Dial Backup line, the backup link
might fail.
CR 16864: PPP.
If you configured PPP on a dial-up circuit and you enter the command
"show PPP CHAP local", an error occurs.
CR 18238: LLC.
When DLS registers for SAP 0, it ends up using the joined table
that llc had set up for its 0 registration rather than making
a new table for the dls range. This allows all addresses with
the null sap into the llc processing arena. If the source saps
of these packets are not dls registered, they will be responded
back via llc sap 255 processing.
CR 18115: Source Routing Bridge.
Source Routing Bridge transmits a SRF destined for any
group or functional address out the interface on which it was
received. This leads to connectivity issues when the router is
configured to cache RIF's, such as NetBIOS name and query caches.
CR 18642: IPX.
Multiple bus faults occurred when creating IPX encap gates.
CR 18654: XNS.
The router is picking up Packet Exchange Protocol (PEP) packets
that are being broadcast to it and broadcasting them back out on
to the same local network. This results in excessive overhead on
the router and on the network and causes problems with PEP packet
sequencing. It also causes XNS mail servers (which use PEP
packets) to fault.
CR 18479: Technician Interface.
A new enhancement request for the Technician Interface enables
you to create a greeting, notice, caution, or warning message that
displays before the Technician Interface login prompt. To create and
initialize use of this message on the router, proceed as follows:
1. Create an ASCII file named ti_notice.txt on your PC or UNIX
workstation.
2. Enter the text of the greeting or notice message that meets your
requirements.
Allow for spacing and return characters so that your new message
looks the way you want it.
3. Save ti_notice.txt on your workstation or PC.
4. Use TFTP to copy ti_msg.txt to the router¹s default file system¹s
volume.
Each time the login prompt displays, this message displays first.
CR 17891: AT.
When a router receives an invalid Rtmp frame request frame, an
orphaned buffer message occurs. The offending frame that causes
this failure will have an illegal source network address.
CR 18364: MakeTools
After you use the hconfig and dehconfig tools to convert a bnx4.2
configuration file to ASCII and then back to hexadecimal, Site
Manager displays the following message on a Sun workstation:
"Warning: Bogus Record Found"
Site Manager then displays the Select Switch Model window.
CR 18598: X.25.
A large window size (about 100+) prompts X.25 to send an RNR
packet each time the router transmits and receives a packet.
CR 10205: IP.
HP Probe is not properly bridging unicast Name Reply messages
that are destined for remote hosts.
CR 18762: Scripts.
When you enter the "show PPP CHAP local" command, the router does
not display all of the PPP CHAP lines that are configured.
CR 18779: IP.
RIP was incorrectly advertising OSPF external Type 1 routes with
a metric of cost plus 1 instead of 1.
CR 18513: DLSw.
After an LLCI/DLS circuit is established between two stations,
periodic acknowledged XID¹s cause the router to echo test frames
as response frames after the connection is timed out.
CR 18748: SNMP.
Multiple bus errors occur when the SNMP Trap Manager attempts to
handle a cold start trap request.
CR 18765: SYNC.
After you boot a BN router and it begins generating IPX traffic over
Frame Relay, an orphan buffer occurs.
CR 7266: IP.
IP packets originated by the router (that is, pings) may cause the
wfIpInterfaceForwDatagrams forwarding stat to decrement by one.
CR 16827: MCT1E1.
A router is unable to bring up circuits on Revision 6 Mct1 board
because there is no receive data on the MCT1 line entry with switch
software Version 4.1 and 4.2.
CR None: TCP.
A problem occurs when DLS receives a bad TCP packet during network
crossover.
CR None: IP.
Trace route was not working for the Ping MIB.
CR 18513: DLSw.
When stations connected via a DLSw cloud exchange frames, the
router might incorrectly interpret an incoming XID frame as an
outgoing test response from the same interface. The test
response causes the PC that received it to hang.
CR 18986: VINES.
VINES may fault when aging routes.
CR 16611: PROTPRI.
If you dynamically decrease the queue while it is clipping, a
bus error occurs.
======================== Version 8.11 fix 3 =============================
The image for FRE BN hardware is: 2606113 Aug 18 16:26 bn.exe
The image for FRE ASN hardware is: 2493500 Aug 18 16:26 asn.exe
The image for VME & AFN Floppy hardware is: 2391191 Aug 18 16:45 ace.out
The image for AN hardware is: 2333335 Aug 18 16:42 an.exe
The image for IN Flash hardware is: 2501935 Aug 18 16:29 in.exe
The image for AFN Flash hardware is: 2270316 Aug 18 16:29 afn.exe
The image for BNX BN hardware is: 1669834 Aug 18 16:57 bn.exe
The image for BNX ASN hardware is: 1546954 Aug 18 16:57 asn.exe
_____________________________________________________________________________
Revision fix/8.11/3 corrects the following problems:
CR 15631: OSPF.
The MIB for the OSPF interface stops recording packet statistics,
such as hellos / dd packets sent and received on the interface, when
an OSPF interface or the OSPF global record is bounced. This
condition occurs because the OSPF soloist may restart on a
different slot, causing the interface statistics to be recorded
by the new slot.
CR 17133: DLS.
When a DLS router is attached to an Ethernet segment and two devices
are attempting to communicate on this segment via SNA,
NetBIOS or APPN, the router duplicates some frames, causing
the host and the client to drop a connection.
CR 17516: IP.
If a router configured for RIP and OSPF learned about some networks
via OSPF ASE type 2 advertisements, and OSPF ASE metric support is
disabled, RIP would incorrectly advertise those networks with a
cost of 1.
CR 16682: IPX.
When NetBIOSAccept is enabled (the default), IPX NETBIOS Directed
Broadcast packets are dropped.
CR 15561: SRB.
Added support in the NETBIOS Query cache for caching NETBIOS
NAME QUERY requests. The user must enable the new MIB variable
wfBrSrBaseNbNameQueryCacheDisable in the Source Route Base Record.
CR 17507: PING_MIB.
Added new field attributes to the PING MIB to improve the
performance of various network management products.
CR 16611: PROTPRI.
If you dynamically decrease the queue while it is clipping, a
bus error occurs.
CR 16543: PING_MIB.
Changing the values in a single entry in the Ping Entry table and
restarting ping does not restart ping.
CR 16744: SRB.
When using FDDI within a Source Route Bridge environment, source
route bridge packets that contain an information field that is
close or equal to 4472 bytes received on a Token Ring
interface are dropped internally in the router. To correct this
condition, the user must set the new MIB variable
wfBrSrInterfaceMaxLffield to 2 on FDDI source route interfaces.
CR 16391: VINES.
If VINES is disabled, the neighbors report the death of a neighbor,
but a router may not remove the route from the neighbor
table or the route table. Instead, the route is kept alive and
advertised throughout the network.
CR 16887: VINES.
A router running VINES Non-Sequence RIP Mode experiences a
FAULT in tmo_wdog.c when aging out 1500 VINES routes.
CR 16469: OSPF.
Bay Networks and Cisco routers do not form an OSPF adjacency
within a stub area if the Bay Networks router is configured as
the ABR and the import summaries parameter is set to TRUE for the
stub area. The Bay Networks router originates type 4
advertisements into the stub area; the Cisco router complains
about the type 4 advertisements and continues to restart the OSPF
interface.
CR 16745: VINES.
When bouncing the VINES base record, the router occasionally
sends out its initial SRTP updates with a sequence number of 0.
Consequently, sequenced neighbors send re-inits to the bounced
router, resulting in convergence times of 7 to 14 minutes.
CR 16550: IP.
A RIP export filter or RIP announce policy can be written to cause
RIP to advertise the default route in place of the routes that
match the filter. This action should be independent of the RIP
default supply setting.
CR 16393: VINES.
When three routers are booted in Non-Sequenced RTP Mode in a
redundant network with a delta formation, only one router can
exchange VINES traffic with two of its neighboring routers. As a
result, the two routers that share the segments cannot exchange
VINES traffic over the segment because they have only one
neighbor. This results in a network configuration that resembles a
hub and a spoke.
CR 16957: IP.
Bouncing a circuitless IP address may cause a bus
error, which temporarily disconnects IP.
CR 17027: IPX.
IPX SAPs with non-printable characters are processed
incorrectly.
CR 14939: IPX.
When attempting to route an IPX packet to a host on a Frame Relay
cloud, an out of memory reset can occur. This condition takes
place only when the host for which the packet is destined does
not have RIP enabled or the local router does not have an IPX
adjacent host entry.
CR None: IPX.
Bus error on General Service Request occurs if IDP packet length
is two bytes shorter than it has to be.
CR 15423: ARP.
Within an IP host-only environment, if the host entry for the
next hop router for a statically-configured route is aged out,
the router will fail to re-arp later on, and will not release the
next hop routes.
CR 15398: IP.
In a host-only environment, a static route is removed from the
routing table when the one interface with which the route is
associated goes down.
CR 13063: IP.
Users are unable to ping the router if the router is configured
in IP host-only mode.
CR 16432: IP.
The directly-connected route may disappear in IP host mode if
one of the IP interfaces is disabled.
CR 13518: VINES.
VINES needs to support new 0x80C4 ISAP for FDDI.
CR 16785: OSPF.
With multiple Virtual Links configured and a LSDB of
approximately 500 nets, one of the virtual Virtual Links will not
be established if OSPF is bounced. One Virtual Link will become
full with its neighbor, while the other link is stuck in
exchange->exchange start.
CR 16838: LNM.
A RESYNC from an LNM Station may fail following a nearest
upstream neighbor (NAUN) change of a router's interface to the
ring to be RESYNC'd. The failure reported from the LNM station
generally indicates no response from the router's upstream
neighbor. However, the failure follows that station even if
another device becomes the nearest upstream neighbor of the
router.
======================== 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
===========================================================================
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
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 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.
Feedback | Service Search
| ERC
Copyright
© Bay Networks,Inc., 1997. All rights reserved.
|
/tr> |
