Revision Notes for Router Software v8.12 rev 13
============================================================================
SITE MANAGER COMPATIBILITY
=============================================================================
Router Version is managed by Site Manager version
v8.12 through 8.12/8 ------------------> V2.12, V3.00, 3.00 Rev 1,
3.01 Rev 1
*8.12 fix 9, ------------------------------> V2.12 fix 1, 3.01 Rev 2
8.12 fix 10,
8.12 fix 11
8.12 fix 12
(* only necessary to enable you to configure
wfIpInterfaceTrEsArpType correctly. See CR 22267 for details)
NOTE: CR 23734 was incorrectly noted as being fixed in 8.12/11, but
actually has been fixed in 8.12/13.
=============================================================================
Revision fix 8.12/13 corrects the following problems:
=============================================================================
CR 22064: DLSw.
When an IBM host I9021 replies to an XID T2 poll by TEST Poll,
DLS transmits this TEST Poll through SSP but does not
send a Reach_Ack message to ICANREACH in response to the
the TEST Poll frame. As a result, the session is never
established.
CR 23734: DLSw.
DLSw does not forward XID-P if the entry in
wfDlsConnectionEntry is in a disconnected state. Instead, the
router drops the XID-P's.
CR 23306: GAME.
Booting an AN2 router occasionally will corrupt the Flash cards.
This condition occurs mostly at sites that experience some type
of console port problem, such as a misconfigured modem.
CR 23479: GAME.
An AN2 router corrupts Token Ring frames before transmitting
them to other hosts on the Token Ring network. This problem was
first detected in IPX frames that were being transmitted by the
AN2 router.
CR 24909: Flash.
An AFN router running 8.12/11 or above generates the following
message when a Maxell Flash card (part number: EF2MTBAA) is placed
in the router:
"Unsupported device found in memory card, writes disabled"
"Flash Card Detected; Unknown Device detected"
"Memory card media info; Mfg ID 0xFF, Device ID 0xFF, number chips 8"
"File System is in a corrupt state, re-format"
CR 22407: AN Token Ring.
A packet whose length is greater than the default MTU size
for a Token Ring network (4568) will cause a fault on an AN
or AN-2 router. The router drops packets up to 8K in size.
Packets whose size exceeds 8K cause a fault because of a
hardware limitation.
CR 18562: SMDS.
When you have configured SMDS as part of your DLS-TCP/IP cloud,
an orphan buffer occurs that temporarily breaks the TCP
connections. The TCP connections do recover, however.
CR 23480: GAME.
GAME debug log message Code: 113 contains incorrect destination
gate handle information.
CR 23559: PPP.
The Sync driver does not calculate SaveInOctets correctly. Only
the current LQR packet is being accounted for. SaveInOctets needs
to be accumulated for all packets received.
CR 16308: GAME.
GAME Debug Event Code: 115 messages appear repeatedly in event
logs, indicating that reliable messages between slots are being
lost or dropped. This is a normal operating condition, and the
message is no longer logged.
CR 20487: MIB.
When you configure a router to send generic SNMP traps and an
interface changes state (goes up or down), the router sends
a packet that contains an incorrect field OID string.
CR 22755: SDLC.
When dynamically configuring a synchronous port for SDLC using
Site Manager 3.00/rev1 and 9.01/1sqa3, the SDLC link will not
become active on the router.
CR 23433: NetBoot.
When trying to netboot an ASN router, the NOVRAM that holds
Netboot parameters becomes corrupted, causing the router to boot
continuously.
CR 23838: BOOTP.
After dynamically adding or deleting BOOTP on an interface,
a hogs bufs condition may occur in the MIB Manager.
CR 23754: DLSw.
After disconnecting an SNA session in a dual slot DLS Token Ring
environment, the session remains disconnected and fails to take
an alternate path.
CR 19376: SNMP.
Disabling SNMP while the lock is enabled and in use caused an
error to occur.
CR 22231: Frame Relay.
The router encapsulation of OSI over Frame Relay contains an
optional pad byte, which was eliminated in RFC 1490. The correct
encapsulation should be DLCI,DLCI,0x03, OSI NLPID.
CR 23938: Datapath.
Disabling a PPP line with DECnet configured disables DECnet on
the entire slot rather than the circuit. This problem occurs only
when you have a bridge configured on the circuit.
CR 22361: OSPF.
If you disable a virtual interface, OSPF's global MIB object will
change to the state of 2 (down).
CR 24005: DLSw.
Disabling and enabling the DLS base causes an SNA Ethernet
application to fail.
CR 24315: IPX.
A bug exists is 8.12/6 (+) that can lead to the age of a SAP
entry to show up as a negative value in the MIB. The Server is
usually learned from a router over a HSSI line. If you monitor
the age, you will see that it increments closer to zero but never
becomes positive. If you look at the adjacent router for this
same entry, it is positive. This does not cause any connectivity
problems, but is simply cosmetic.
CR 22775: Translation Bridge.
A circuit is configured for Source Route Bridge and Translation
Bridge and another circuit is configured for LB. When an ARE frame
arrives, the Translation Bridge translates it into an Ethernet
packet and calls the flood alias to flood all gates, including the
"Ethernet to Source Routing" gate. This gate then converts the
flooded Ethernet packet to a Source Route Bridge and sends it out
on the same circuit from which the ARE originated.
CR 24224: LNM.
Tag violations and bus errors generally occur when a local rings'
stations leave the ring and the router interface reverts to
single station state.
CR None: IPX.
Two routers connected by multiple redundant links contain routes
that fail to age over time.
CR 13189/
21168: GAME.
A slot may reset with "Error in msg_fwd.c" when attempting to send
reliable messages between processes.
CR 24346: Translation Bridge.
Disabling the Translation Bridge base results in bus errors when
transferring files back and forth to an end station on an
Ethernet segment from an end station on a Token Ring segment.
------------------------------------------------------------------------------
Revision fix 8.12/12 corrects the following problems:
=============================================================================
CR 24572: Tools.
In 8.12, fix 11, the VME-based router boot image,
ace.out, contains an executable file that was built with an
incorrect pathname. This causes problems when you attempt to open
and/or save the ace.out image file using the Image Builder in
PC and UNIX-based Site Manager. PC Site Manager will not allow
you to open the ace.out image using the Image Builder; UNIX Site
Manager will allow you to open ace.out in Image Builder but will
save the file with zero bytes.
-----------------------------------------------------------------------------
Revision fix 8.12/11 corrects the following problems:
=============================================================================
CR 23479: GAME.
An AN2 router corrupts Token Ring frames before transmitting
them to other hosts on the Token Ring network. This problem was
first detected in IPX frames that were being transmitted by the
AN2 router.
CR 22750: Telnet.
When the Telnet client fails to set the "Push Bit" correctly during
Terminal Type Negotiations, Telnet sessions do not get established.
CR 21767: OSI.
Router fails to respond to an OSI ping over PPP after the
synchronous line is bounced.
CR 19688: DLSw.
DLSw drops non-NameQuery/NameRegisterNetBios broadcast frames that
a router receives in a short interval because of the nature of its
caching system.
CR 21881: FDDI.
An attempt to enable or disable an FDDI connector failed because
the variable "ver" (version) is present in the FDDI.bat script file.
CR 22686: DLSw.
If a DLS connection gets reestablished through a different
interface on the same slot, the DLS Connection entry does not
get updated.
CR 20956: Compression.
Two routers configured with WCP that are connected back to back
produce a loop back situation that results in a bus error, causing
the PPP interface to bounce.
CR 21882: IPX.
If you disable IPX RIP supply on a router, the router will fail to
learn about any other IPX routes over that interface.
CR 22215: SYNC.
The Hold Down Timer that is used for Dial Backup fails to work
correctly if the platform OSYNC net modules, ASN and AN, are being
used on the Master Primary Line (calling side).
CR 20859: Switched Services.
When a router with multiple DOD pools receives a call, IPCP fails
to converge.
CR 21335: DECnet.
If a slot configured to run DECnet attempts to send an adjacent
message to another slot, and that slot unexpectedly
goes down, a fault on the transmitting slot
occurs, resulting in the following error message:
"Error in drs_cct_init.c at line 824".
CR 23076: DLSw.
When you boot a DLS network with multiple (>300) TCP peer
connections, the routine dls_tcp_rcv_establish exits with orphan
buffers, but the network remains operational.
CR 22977: DLSw.
The router faults when 400 TCP peer connections with 212
DLS connections are running on one slot.
CR 22522: TCP.
When you run an automated test script that disables and enables
TCP, an error occurs in tcp_mgr.c at line 1019.
CR 22549: Source Route Bridge.
The router drops Single Route Explorers if the number of
route descriptors in the frame exceed the maximum
number of RDs configured for that interface. According to the IBM
Source Routing specification, decreasing the number of hops from 7
(or the "Max numbers of RDs") should affect only ARE's, not
STEs or Source Route Frames (SRFs). Also, the router will drop
STEs if you set the new MIB parameter, wfBrSrAreHopCountlimit.
CR 22741: IP.
When you disable the RIP supply, the router should not respond
with a RIP supply to any RIP request from other routers or nodes,
except when the source port of the request is a port other than
the UDP 520 (the designated RIP port). In this case, the router
should respond even if the supply is turned off.
CR 21617: BGP.
Numerous TCP segment retransmissions may cause routers exchanging
30000 routes via BGP an excessive amount of time to complete.
CR 22415: IPX.
When you use the IPX maximum path setting to install multiple equal
cost paths to the router, the router may answer "get nearest
server" requests when there is a server local to that network.
CR 22398: Telnet.
When you disable and re-enable TCP, an error occurs in
tn_tcp_listen.c. This errors occurs because the router fails to
receive a successful tcp_open call return when attempting to
establish the listening well known telnet port.
CR 23263: IPX.
If the router bounces an IPX interface while it is processing
a general service query, a situation may occur in which the router
chooses to ignore subsequent general service queries.
CR 22783: Switched Services.
When a primary circuit fails, the master router selects a modem
from the pool and initiates the dial recovery process. However,
if the modem selected has the phone line disconnected, the router
attempts to dial three times and then terminates the process
without attempting to use the other operational modems in the
pool. Also, if the backup line is up and is disconnected from the
router, the backup process is terminated and no attempt is
made to establish a connection through one of the remaining
modems in the pool.
CR 23165: Translation Bridge.
A router configured with one or two translation bridge interfaces
on the same slot will experience multiple faults on that slot if
the interfaces receive several source route packets that require a
RIF packet to be cached.
CR 23290: TCP.
A problem exists in 9.00/rel through 9.01/1sqa4 in which breaking
down 225+ TCP sessions causes a router to run out of resources and
eventually fault.
CR 23289: IP.
When an IP interface removes the wfIpNetToMediaEntry for an
address and then receives an ARP request from that IP address--
either by the circuit bouncing or when host cache is enabled-- the
router may fail to respond to the ARP request.
CR 23665: DLSw.
If you configure DLS on two circuits on the same slot
(each circuit has a IBM host with same mac address) and
you disable and re-enable TCP, the existing DLS connection
disconnects and never recovers.
CR 22790: Translation Bridge.
Translation bridge caches a RIF incorrectly, sending a bad
source routing bridge packet whose destination MAC address is a
Wellfleet proprietary group address (C000A2FFFFF3).
CR 23669: VINES.
When you add a VINES client to the router's table, the router
inadvertently sends out full SRTP updates to client neighbors.
As a result, client neighbors whose routing server is not a
Bay Networks router are aged out every six minutes, and a full
update is sent out.
CR 23021: VINES.
A bus error occurs when a VINES server attached to different
physical media (Ethernet and Token Ring, for example) on the same
router on different slots learns a new neighbor that is on the
same segment as one of the dual attachments.
CR 22064: DLSw.
When an IBM host I9021 replies to an XID T2 poll by TEST Poll,
DLS transmits this TEST Poll through SSP but does not
send a Reach_Ack message to ICANREACH in response to the
the TEST Poll frame. As a result, the session is never
established.
CR 22806: DLSw.
Customer enhancement to ensure that Bay Networks implementation
of NetBIOS over DLS is compatible with Windows NT's
implementation of NetBIOS.
Specifically, Windows NT uses a second NAME_QUERY
to construct a matrix. The new implementation of NetBIOS over DLS
employs multiple NameQuery frames to construct two matrices.
The NBF issues the first NAME_QUERY with an LSN=0 to find the
remote device. When the remote device responds, the network
address is extracted and put into the matrix. Then a second
NAME_QUERY with a real LSN is sent directly to the remote
device. The Bay Networks implementation of the DLS state machine
drops the second NAME_QUERY frame. As a result, the matrix is
never completed, and NetBIOS does not work properly.
CR 23351: LNM.
When a Token Ring port that you have configured for LNM receives a
single LLC TEST FINAL frame, it passes it to LNM. But after LNM
processes the packet, it fails to free it, causing the packet to
loop back to itself.
CR 23858: Translation Bridge.
When you disable translation bridge in dynamic mode while RIFs are
present in the cache, bus error may occur.
CR 22434: TCP.
When you attempt to boot a router consisting of 500 plus TCP
connections, an error occurs in mib_ent.c at line 1115.
------------------------------------------------------------------------------
Revision fix 8.12/10 corrects the following problem:
=============================================================================
No CR: IPX
Bus error may occur in g_gate_status.
-----------------------------------------------------------------------------
Revision fix 8.12/9 corrects the following problems:
=============================================================================
CR 19177: VINES.
After a slot resets, VINES may stop forwarding packets to
some networks even though the network table in the MIB is correct.
CR 19507: DLS.
The DLSw Destination MAC address filters do not work properly.
As a result, the DLS Drop All Filter fails to
drop packets according to the filter precedence logic that
has been defined.
CR 19126: DLS.
DLSw destination MAC filters do not work properly. Users
operating PC's running SNA 3270 emulation software are allowed
to access the Destination MAC addresses 0x400000031723 and
0x400000000007, both of which are restricted.
CR 21998: IPX.
Dynamically adding, deleting, or modifying the IPX SAP server or
network filters using Site Manager will sometimes cause
a slot fault, which is generated in the form of a bus or watchdog
error.
CR 22085: FTP.
When you use the FTP software package QVNET to transfer a file to
a router, a tag violation error occurs.
CR 22397: TCP.
Disabling and enabling the DLS base causes an error when you have
approximately 400 TCP connections (state 3) on a router.
CR 21497: IP.
Dynamically configuring OSPF summaries may cause routers to
advertise OSPF summaries with incorrect masks, thereby preventing
access to routes summarized within those summaries.
CR 22188: Source Route Bridge.
Source Route Bridge (SRB) filters fail on HSSI and SYNC media.
The SRB traffic filters you enter in Site Manager in are in
non-bitswapped format for all media types. These traffic filters
fail on SYNC and HSSI media when the MAC addresses (entered in
Site Manager) are compared to a bitswapped MAC address that exists
when frames get bridged from Token Ring to HSSI/SYNC.
CR 19902: VINES.
Customer enhancement to provide Ethertype 0x80C4 on Ethernet to
enable native VINES support on FDDI and to support the
interoperability of bridging (FDDI to Ethernet) and routing
(Ethernet).
CR 22610: VINES.
A neighbor entry on the slot may cause an invalid next
hop pointer because of a timing error. As a result, that neighbor
and all of the servers it knows about become unreachable from the
router. The router will be able to ping its neighbor, but several
of the servers/routers behind the router that reside on other slots
will be unable to ping through this router.
CR 19627: Token Ring.
A fault may occur on an AN router upon receipt of a source route
frame that contains only the standard source route LLC header and
its associated RIF field.
CR 22267: MIB.
You cannot properly configure the 'TR End Station ARP Type'
parameter in Site Manager revisions 3.00 through 3.01/rev1
when interacting with 8-series router code versions up to
8.12/fix8. This problem is caused by an IP Interface MIB parameter
inconsistency between versions 8.12 and 9.00.
Support for 'TR End Station Arp Type' was implemented in 8.11/fix2
and 9.00/rel. The attribute wfIpInterfaceTrEsArpType was added to
both the 8.10 and 9.00 MIB revisions but at different offsets,
thus preventing 3.00/3.01 users to set this attribute dynamically
against an 8.12 router version.
To use this MIB attribute for 8.12/fix9, you MUST consider the
following:
o Update previous configurations and use the correct version of
Site Manager when implementing future configuration changes.
o Configuration files created by version 2.12/rel or earlier
will be upgraded automatically when booted on a router running
8.12/fix9 to correct the MIB inconsistency and preserve the
original attribute setting.
o Site Manager 2.12/fix1 and 3.01/rev2 users will now be able to
configure this attribute dynamically against 8.12/fix9. If you
are using Site Manager version 2.12/fix1 or version 3.00 or
higher, you MUST upgrade your router software to version
8.12/fix9 (minimally) to correctly manage this attribute.
CR 20863: DECnet.
If you bounce a DECnet circuit while it is learning adjacencies,
bus errors may occur.
CR 22628: OSI.
OSI routing may stop whenever a reset occurs on a slot that routes
OSI traffic. This failure condition occurs after you manually
reset a slot or after it encounters a software failure (fault,
resetting a slot).
CR 13463: IP.
When upgrading router software from 8.01/4 to 8.10, the
processing of multiple ARPs could result in a hogs bufs
condition.
CR 22814: IP.
Removed changes for CR 13523 (introduced in 8.12/8) pending
resolution of the problems identified in CR 22814.
CR 22502: Token Ring.
A fault in the tms380 driver may occur when a Token Ring card
(quad or dual) that is running DLS attempts to initialize
interfaces on a slot that supports over 100 TCP connections. The
failure occurs because the driver code fails to wait long
enough for the token diagnostics to complete on a busy system.
CR 23182: IP.
An OSPF Point-to-Point interface fails to receive Hello packets
from its neighbor, causing an established adjacency
to go down. This condition may occur in environments in which a
default route is used, thus affecting those interfaces that
receive packets destined for the default route.
CR 22020: LLC.
If you change the Source Route Bridge Ring ID dynamically, DLSw
fails, preventing connections established over DLSw (SNA and
NetBIOS) from functioning.
-----------------------------------------------------------------------------
Revision 8.12/8 corrects the following problems:
==============================================================================
CR 17620: Frame Relay.
Certain Protocol Prioritization/Outbound Bridge Filters over Frame
Relay cause ARP to erroneously drop ARP frames.
CR 20237: X.25.
X.25 PDN connections are off by 1 when accepting calls.
For example, when you set max_connections to
a value of 2, the service allows 3 calls. Likewise, when you set
max_connections to a value of 4, the service allows 5 calls.
CR 19805: MIB.
MIBII ifentry iftype 46 does not exist for HSSI interface.
Therefore, when attempting to run a WAN summary against the HSSI
port, the field displays all zeros (0000s), and never updates.
CR 21332: DLSw.
Dynamically deleting the DLS slot IP address disrupts the existing
TCP connections on other slots on a router.
CR 16192: DLSw.
When using DLS between LANDP/DOS and the host system, the XID
format 8 is dropped, preventing LANDP/DOS from receiving the
negative XID response. As a result, LANDP/DOS and the host are
unable to establish a connection.
CR 19600: DLSw.
DLS creates invalid wfDlsConnectionEntry entries on local switch,
causing a panic in dls_netbios.c, which in turn causes all NetBIOS
and SNA sessions to bounce.
CR 21331: TCP.
TCP peers fail to reconnect when you dynamically delete and later
add a DLS peer entry that has already established a TCP
connection.
CR 19502: SYNC.
When you enable the RTS/CTS option (used to provide sync line flow
control to some DCE equipment) on an AN or an ASN router,
the synchronous interface goes down, preventing it from
transmitting and receiving frames.
AN---------|Break Out Box|------------BLN
sync sync
The Break Out Box is configured to act as a modem eliminator.
CR 20131: PCAP.
Packet Capture receive filters on source or destination MAC
address and do not work on TOKEN or FDDI.
CR 13523: Source Routing Bridge.
A failure of IP Encapsulated source route traffic may occur under
certain circumstances immediately following the replacement of
router hardware. The problem occurs as a result of an unexpected
change to the Time of Day clock, which can be introduced by a
change in hardware. This is considered a problem because IP
Encapsulation runs on a UDP based application that uses time
stamped sequence numbering.
CR 20679: MIB.
The MIB entry wfIfEntry.wfIfOperStatus used to indicate that
an interface is disabled is not set correctly for
Token Ring, Ethernet and Synchronous interfaces. The current value
is set to 3 for TESTING. This value should be set to 2 for DOWN.
CR 21555: IP.
An IP error occurs continuously after booting a router, and IP
fails to recover. The problem occurs only when attempting to
process an invalid host adjacent host, whose nexthop
interface address does not exist.
CR 20955: PING_MIB.
When issuing a series of pings, the ping MIB may receive
echo replies out of sequence, therefore causing the ping MIB to
report invalid positive values for total and maximum delay.
CR 21639: X.25.
A panic in mib_ent.c occurs when you add or delete X.25 VCs.
VCs get added and deleted when sessions are being added or timed
out or when a router tries to start a session to a remote site but
the remote end is not operational.
CR 21269: DECnet
When you issue the SHOW DECNET CIRCUITS command under certain
circumstances, the link module type is displayed incorrectly. If
the link module that resides in the slot is an FDDI card, the
script shows it incorrectly as a Token Ring card
under the circuit type. The script reflects the link module type
correctly if the card is either a Token Ring or an Ethernet.
CR 21893: DLSw.
NetBIOS Name recognized frame is duplicated by DLS in a local
switch configuration with Source Routing Bridge enabled.
CR 19206: DLSw.
A fault can occur in tcp_prep_xbuf.c when establishing DLS
connections.
CR 21944: Source Routing Bridge.
A Source Route frame whose destination address is a Wellfleet
Group MAC Address does not get filtered by Source Routing Bridge
(SRB) traffic filters on a Token Ring interface when the SRB
traffic filters are configured for the real destination address
and not the Wellfleet group MAC address.
CR 21268: SCRIPTS.
If you have configured more than one SNMP Manager and issue the
the SHOW SNMP COMMUNITY command, the output format for the SNMP
Managers display incorrectly on your screen. Insert a carriage
return at the end of the first SNMP Manager to ensure that they
format correctly.
CR None: VINES.
A router may experience memory loss or corruption when numerous
VINES routes are aged simultaneously.
CR 21691: DLSw.
When you configure a DLSw filter with the action "Forward to
Peer", any matching packet is not forwarded. The log indicates
that the filter rule matched successfully, but shows an
invalid IP address.
CR 19711: Scripts.
The SHOW HARDWARE SLOT command generates too many columns on your
screen, causing Link Serial Number of 1346 wraps on an 80 column
display down to the next line. For example:
[1:1]$ show hardware slot
Hardware Information per Slot
-----------------------------
Slot Processor Processor Processor Link Link Link
Module Revision Serial No. Module Revision Serial No- -- --------------- --------- ---------- ------------ -------- ------
1 Access Node 129 00000542 module#1045 2147483777 134
6
CR 16330: SCRIPTS.
When you issue the script SHOW STATE ALL command with Frame Relay
or BGP configured, the state.bat script calls the fr.bat script
with invalid parameters. This causes the fr.bat script to display
its help information.
CR 21835: IP.
A router acting as a BOOTp gateway fails to forward BOOTp replies
back to the requester over a Frame Relay interface configured in
Group Mode.
CR 21553: DLSw.
When using SRB Encaps on a Token Ring interface,
wfDlsInterfaceEntry.7 & wfLlcInterfaceEntry.24, the XID is not
getting passed to the Token Ring. The RIF field has the explorer
bit still asserted.
CR 19724: IP.
The route tables for each slot are inconsistent. When a packet
destined for a network that is missing from a particular slot's
route table is forwarded, the packet is sent out the Default
Route. The default router receives the packet, does a lookup for
the destination, and the packet is sent back to the original
router on a different slot/interface. Because this slot
has a correct route table, the packet is forwarded out the correct
interface.
CR 22390: TCP.
TCP connections for an unconfigured peer may fail to reach a full
"ESTABLISHED" state, preventing DLSw connectivity between the
peers. This condition applies only to connections from Write to
Read port.
CR 22: TCP.
When you have approximately 400 TCP connections (state 3) on a
router and you disable and enable the DLS base
s wfDls.2.0 2;commit; s wfDls.2.0 1;commit, and error occurs.
CR 21673: DLSw.
SDLC sends RNRs and never exits in a half duplex mode.
-----------------------------------------------------------------------------
NOTE:
We have created a revised version of the 8.12/7 revision notes to reflect
a minor change in the build. CR 21960 has been removed from 8.12/7 and
incorporated into 8.12/6. The revised version shown below reflects this
change. Ignore the previous version of 8.12/7 that you received.
-----------------------------------------------------------------------------
Revision 8.12/7 corrects the following problems:
==============================================================================
CR 22021: VINES.
VINES ICP metric notifications are sending internal metrics
rather than Sequenced advertised metrics. As a result, significant
delay occurs when resending packets to clients.
CR 21587: VINES.
The Sequenced RTP bit in the compatibility byte should be set if all
neighbors on a segment support sequenced RTP packets.
CR 21590: VINES.
The Sequenced RTP bit in the RTP Machine type byte should be set
if the router supports sequenced RTP.
CR 19747: NVFS.
When you attempt to hot-swap a Flash card on an AN router, the
Technician Interface generates a message indicating that
the Flash card is corrupted. This is an invalid message. The Flash
card is not corrupted.
CR 21174: IP.
A Frame Relay interface whose address resolution type is set to
"INARP" experiences permanent buffer loss if you attempt to
establish a connection within the IP network of the
Frame Relay cloud and the end station does not have an entry in
the ARP table.
-----------------------------------------------------------------------------
Revision 8.12/6 corrects the following problems:
==============================================================================
CR 21960: IPX.
Hogsbufs may occur in ipx_rip_sap_request_act when receiving IPX
RIP requests.
CR 19338: PCAP.
Packet Capture displays Tx and Rx packets out of sequence on a
MCT1 circuit. Tx packet (A) displays after the Rx packet (B) in
the capture file, even though packet (A) is sent before
packet (B) is received.
CR 18964: IP.
A router configured on a Token Ring interface with end station
support enabled will flood the log with mapping messages at a rate
of 10 to 12 mapping messages per second, causing the log to wrap.
CR 19548: MCT1.
Excessive traffic across multiple logical lines on Port 1 of an
MCT1 link causes delayed response to LMI on Port 2 of the same
MCT1 link.
CR 15703: OSI.
OSI area address aliases are not being advertised in IS hello
messages; only the main NSAP is being advertised. As a result,
adjacencies cannot be established between the end-system and
the Bay Networks router.
CR 19249: Switch Services
An auto-terminated DoD circuit configured on an ISDN-B channel
will not be created if the B-channel is in use when the
auto-termination reset timer expires.
CR 19606: DVMRP.
When you delete the DVMRP protocol from a slot or multiple slots on
a router, the DVMRP.exe file continues to reside in the
router's memory address space. This can lead to inefficient
use of available memory addresses for other protocols attempting
to use that space.
CR 18928: FTP.
Issuing multiple commands during an FTP session and then
changing directories to a different slot can cause a slot to fault.
CR 18246: NVFS.
A file that contains an illegal filename cannot be deleted from
a Flash card.
CR 17553: DLSw.
If you remove the cable between the router and the controller,
the DLS/SDLC and SYNC do not display a message notifying you
that the cable has been removed.
CR 20165: GAME.
The wall clock timer that runs on FRE-060 boards is slower than the
timer running on the FRE-040 boards. As a result, log events get
printed out of sequence.
CR 18771/
CR 20101: BNX Switch.
When you set the date and time on a router by specifying the
"date" command (using the Technician Interface) with invalid
alphanumeric characters, the clock may reset hours/minutes to
00.00.
CR 18735: Technician Interface.
When you enter the "Diag" and "Reset" commands from the Technician
Interface without specifying a slot, the router performs
diagnostics on all slots and then reboots each slot. An
enhancement request has been issued to provide a confirmation
message that asks the user to decide whether or not to perform
diagnostics on each slot or reset all slots.
CR 19909: NVFS.
While attempting to hot-swap a Flash card, a file on the Flash
got corrupted when the first character in the filename changed
to an exclamation point ("!"). Attempts at deleting the file
failed, thus leaving no other option but to reformat the Flash
card.
CR 20410: FTP.
If you attempt to change to a non-existent directory/file system
on a router using FTP, a watchdog panic error occurs when you
attempt to change directories subsequently.
CR 18534: IP.
In most configurations, the MIB variable
wfIpBase.wfIpBaseHosts.0 does not accurately represent the total
number of hosts that the router knows about. While the total
number of hosts should match the number of instances in
wfIpNetToMediaEntry, the actual number seems to be larger.
CR 19486: Hardware-Diagnostics
When you hot-swap a link module from a BLN or a BCN router, the
FAIL LED remains on. Customer enhancement request to turn LED off.
To turn off the FAIL LED, enter the following command:
diag -1
This will not run diagnostics.
CR 19882: DLSw.
Whenever you run a single switch DLS, NetBIOS frames that are
being sent in and out on the same slot were going through DLS
instead of SRB.
CR 14876: PPP.
PPP authentication fails occasionally, producing the following
message in the log file:
"Received PAP message with incorrect identifier"
This message occurs if the packet ID's are different during the
period in which PAP authentication takes place.
CR 20687: ATM_DRVR.
The Tsunami framer device (NTC) is being programmed to set the C2
overhead byte for SDH to 1. According to the G.709 specification,
the C2 overhead byte should be set to 0x13.
CR 18862: OSPF.
An Area Border Router (ABR) may lose connectivity to routes within
an attached area if direct connectivity is lost to that area, even
though an alternate path exists via the Backbone.
CR 17778: DLSw.
If you disable/enable the DLS base, the router may fault.
CR 20418: ISDN.
4-MB is not enough memory to run ISDN on an AN router. You need
at least 8-MB of memory to run ISDN.
CR 20949: LLC.
The index value for the SAP to de-register in the case of SRB
and Frame Relay encapsulation is based on an index variable that
is unrelated to the actual SAP being deregistered.
CR 6081: LNM.
Using the IBM LAN Network Manager to test a LAN segment that the
LNM Servers is monitoring will fail. This failure occurs because
the 8304 Request Station Information arrives with a destination
address of C000000001 (the active monitor functional address), and
there is no code in the LNM to accept queries for this functional
address.
CR 20896: IP.
Updating the forwarding table for a network that has gone
down and come back up can remove valid entries from the table,
causing the number of entries in the table to fluctuate.
CR 19990: VINES.
When the router is configured for non-sequenced ARP and the
client is running Version 5.5x on a Token Ring serverless segment,
the client sends a sequenced ARP to the router. When the router
responds to the sequenced ARP, the client sends Sequenced RTP
client updates, which are not processed by the router, causing
the client's neighbor entry to age out.
CR 18144, 16310, 14598: VINES.
The above-mentioned CRs relate to a situation in which change
receive gates were used to send sequenced change updates. When the
soloist slot sent the packet on all interfaces, a problem occurred
when the interfaces bounced, leaving the orphaned
buffers as the soloist without a map to the change receive gates.
CR: 20284: VINES.
Large sequenced RTP packets transmitted over a WAN utilize a
slot's full memory capacity, forcing it to reset.
CR 19750: VINES.
Invalid entries are being inserted and removed from the redirect
pool over a WAN interface on which FRP (VINES Fragmentation
Protocol) is enabled.
CR 17058, 17826, 13384: VINES.
After removing n_dsp->mbuf_headsn, the pointers were not set to
NIL, preventing the allocation of new buffers. Instead, memory that
had been freed was being corrupted.
CR 19674: VINES.
The counter of VINES sequenced neighbor is not reset to 0 after
the VINES base record is enabled. Instead, the counter
is incremented by the number of active sequenced neighbor(s) from
the previous counter value.
CR 20064: VINES.
VINES neighbor table and network tables do not get updated
immediately (updates takes approximately 90 seconds) when
implementing a topology change.
CR 20753: VINES.
A neighbor VINES server is being added and removed from
the neighbor table continuously, causing the router to eventually
fault.
CR 20785: VINES.
Metrics bounce up when routes are removed over multipath.
CR 19983: VINES.
When running VINES in Group Mode, Frame Relay fails to send out
an RTP Request packet when the interface initializes, preventing
all routes from being relearned. This may result in connectivity
problems.
CR 14940: Frame Relay.
LMI timer drifts when the CPU is busy. As a result, updates are
not sent on time and connectivity is lost.
CR 19760: VINES.
Customer request to disable VINES Redirects on interfaces. A new
MIB parameter will be implemented to satisfy this request. This
parameter should be implemented in networks such as non-fully
meshed Group Mode Frame Relay (Hub and Spoke) running VINES where
a Redirect will cause connectivity loss between spokes. You need
to set the new MIB parameter to DISABLE to prevent Redirects from
being generated.
CR 21242: DLSw.
Faults occur when you disable TCP on a router while playing test
frames into a DLS interface.
CR 21258: DLSw.
NetBIOS status response frame is echoed back out the interface
frame on which it was received.
CR 20979: VINES.
Routers running in either Sequenced or Automode sometimes will
have sequence numbers stored in the VINES base record that do
not match those sequence numbers stored in the SRTP packets
being transmitted out.
CR 21654: VINES.
The current implementation of one forwarding table per
interface can significantly affect performance (and cause loss of
connectivity) at sites running Frame Relay with numerous
PVCs and VINES networks. Suggested implementation of one
forwarding table per slot. This causes
wfVinesIfEntry.wfVineslffwdTableEntries to be obsolete.
CR 21668: IP.
If there are entries in the forwarding table that are pointing to
the default route and the default route is disabled, only the first
entry will be deleted. The other entries will continue to forward
packets to the default route's next hop.
CR 20962: VINES.
Bogus network numbers can propagate throughout large VINES
networks.
CR 20555: VINES.
After setting the system time backwards and booting the router,
neighbor routers running VINES sequence RTP enter the
re-initialization mode, causing a three minute VINES outage.
CR 20772: SYNC.
wfSyncState remains a value of of8 when wfSyncRemoteLpbkDetection
is enabled.
CR 19177: VINES.
After a slot resets, VINES may stop forwarding packets to
some networks even though the network table in the MIB is correct.
CR 21950: VINES.
A router running in Automode or Sequenced mode sends
out SRTP Synchronization packets too frequently. The router
should send out SRTP Synchronization packets every 12 hours.
CR 21977: VINES.
In a router running in Automode, non-sequenced RTP change updates
contain all network changes rather than just the current changes.
==============================================================================
Revision 8.12/5 corrects the following problems:
==============================================================================
CR 20504: TCP.
A router may experience hogs bufs on all slots
configured for DLS when a single slot in a router is tearing down
numerous TCP connections. This may result in resource utilization
faults throughout the router, depending on the hardware
(memory/buffers) present.
CR 14263: DLSw.
Faults occur in the mapping function when you attempt to add DLSw
Peers dynamically.
CR 20870: DLSw.
A slot configured for DLS experiences memory loss each time a DLSw
Peer's TCP connections close and reopen. This eventually causes the
slot to run out of memory.
CR 20682: DLSw.
A stream of test polls sourced or destined and to or from at least
75 MAC addresses may cause a slot configured for DLSw to
experience a bus error, which in turn causes a slot to
deplete its available buffers permanently. As a result,
buffers on other slots throughout the affected router may
experience faults.
CR 18971: DLSw.
A bus fault occurs in DLSw when you attempt to send test polls
while TCP is disabled.
CR 18887: DLSw.
The router may fault when sending DLS frames into a TCP
connection that has not been fully established.
CR 20503: DLSw.
A slot configured for DLS may experience a "Watchdog expired,
service terminating - system restart" fault when TCP is tearing
down a large number of connections.
CR 18876: LLC.
The router experiences a bus fault and/or Watchdog timer expired
fault after Token Ring interface configured for LLC2 bounces.
CR 19211: DLSw.
The router may fault when sending DLS frames into a TCP
connection that has not been fully established.
CR 21277: DLSw.
A bus fault occurs in DLS when you attempt to transfer a large
NetBIOS file (35K) from an AN to an ASN router.
=============================================================================
Revision 8.12/4 corrects the following problems:
=============================================================================
No CR: IPX.
When the router boots, excessive IPX hogs bufs occur, causing
significant network performance degradation.
CR 21004: FDDI.
An FDDI frame with a size of 4094 bytes get dropped by the
receiving FDDI interface.
=============================================================================
Revision 8.12/3 corrects the following problems:
=============================================================================
CR 20540: Source Routing Bridge.
When you configure Source Routing Bridge (SRB) on an SMDS circuit
(using both proprietary encaps and standard encapsulation methods)
ring bridge pairs are incorrectly mapped to SMDS e.164
addresses, causing significant degradation in SRB performance.
------------------------------------------------------------------------------
Revision 8.12/2 corrects the following problems:
=============================================================================
CR 19543: Source Routing Bridge.
In a Group Mode configuration within Frame Relay, the Hub router
may transmit Specifically Routed Frames (SRFs) out the incorrect
DLCI intermittently. This condition occurs on a Hub router within a
non-fully meshed environment.
CR 18910: Switched Services.
A Dial-on-Demand connection that is brought up and down
repeatedly while operating with a specific modem type can cause
intermittent tag violations on a BLN router or cause an AN router to
hang.
CR 16861: Translation Bridge.
Translation Bridge (XB) will cause a hogs bufs condition when
caching 1000 RIFS.
CR 19664: Source Routing Bridge.
A race condition exists between circuits running XB on the same
slot. As a result, XB produces a bus error while flushing messages
after the router is booted.
CR None: X.25.
Site Manager would not build due to missing comments in X25.mdl
file.
CR 17873: Switched Services.
When you configure the primary line on the COM1 port with external
clocking on an ASN router, the COM1 port fails to initialize
successfully. This condition occurs because the primary line is
initialized before the ISDN/BRI, thereby causing the ISDN to
overwrite the pins for the external clock when it comes up.
CR 19745: DLSw.
In an environment where numerous DLS connections (40 plus) are
being established and TCP and LLC are in a congested state, a bus
error can occur, causing DLS to be reinitialized.
CR 19563: Source Routing Bridge.
Upgrading a router to Version 8.11 causes other routers on the
FDDI ring running Version 7.80 to panic on the FDDI slot
configured for Source Routing Bridge. As a result, the router
running Version 8.11 sees a message indicating bad frame
length on transmit request messages in the log for SRB Token Ring
interfaces.
CR 13373: DLSw.
When running DLSw in a heavily looped Source Routing Bridge
environment, DLSw may panic when creating a MIB instance.
CR 19998: LLC.
The T1 timer associated with LLC2 sessions is timing out
prematurely, causing frame rejects to be transmitted
incorrectly. This condition occurs in situations in which there
is heavy traffic and many PU's and LU's.
CR 19721: LB.
When attempting to connect to a NetWare server, the source and
destination MAC addresses in the IPX GNS response packet gets
corrupted through Ethernet-ATM-FDDI-Ethernet bridging.
CR 19997: LLC.
An LLC2 session that receives a TESTf after it has already been
established will cause the session to disconnect. This should
happen only for a TESTp frame, not for a TESTf frame.
CR 17792: Source Routing Bridge.
SRB traffic filters configured on the destination address in a
Source Route Frame are not working correctly. The actual
destination address is moved to the end of the frame, and
a group address is inserted in its place. As a result, the
actual destination address does not match the specified
destination address in the filter rules.
CR 18861: OSPF.
An Area Border Router(ABR) may fail to generate a new Router Links
Advertisement for the Backbone router if it loses connectivity to
an attached area.
CR 20343: MCT1.
It is possible for logical lines to go "deaf" on an MCT1 port
configured with multiple logical lines. In its attempt to recover,
logical lines will not see incoming frames.
CR 15954: Source Routing Bridge.
Frames configured to be dropped by Source Routing Bridge filter
instead are translated and forwarded by XB to the transparent
bridge side of the network. This condition occurs for both ARE's
and for SRF's.
CR 19947: IP.
A configuration parameter is required that will enable users to
select whether IP Broadcast messages are sent out as STE's or
ARE's when end station support is enabled.
CR 18684: IPX.
IPX traffic may stop being received intermittently over an ATM
link, causing a potential loss of connectivity.
CR 20054: VINES.
In a redundant VINES network when one of the routes becomes
unavailable, VINES fails to reconverge. This causes the existing
route to age out, preventing alternate routes from being learned.
CR 18859: OSPF.
In the OSPF MIB, the variable
wfOspfGeneralGroup.wfOspfAreaBdrRtrStatus does not accurately
reflect the true status of the router. The variable appears to
indicate that only a second AREA is configured and enabled, which
doesn't necessarily mean the router is actually an AREA Border
router at the time.
CR 19428: IP.
In an IP host-only and spanning tree environment, changes in the
spanning tree topology may cause some routers to lose IP
connectivity with other devices.
CR 19429: SPAN.
The router can change a Spanning Tree port state from blocking to
forwarding under specific circumstances, and yet not send a
topology change notification as required.
CR 20338: AT.
In a redundant topology under certain circumstances, AARP's are
not generated when NBP Forwarded Requests need to be sent to the
next hop router.
CR 20413: EGP.
If a router is configured for EGP on an interface and receives a
fragmented frame, the router produces an error.
CR 20056: OSPF.
Virtual adjacencies frequently get stuck is the exchange start
state when the backup soloist is enabled on an OSPF router. In
addition, when OSPF restarts, an orphaned buffer occurs during the
attempted formation of the virtual adjacency.
CR 19762: DLSw.
When upgrading to 8.11 or above on a router running DLSw on an
Ethernet Interface, A Tag Violation/Slot Reset may occur on the
Ethernet Slot if a pre-8.10/8.11 configuration file is used. A
typical example would be upgrading from 8.01 to 8.11
RELX and using the original 8.01 configuration file.
CR 13524: AN.
When you attempt to set the date for December 1999 on an AN
router, the system sets an incorrect date. For example:
> date 11/30/99 23:59:45
Nov 30, 1999 23:59:45 [GMT]
>
> date
Jan 131, 19100 0:00:11 [GMT]
CR 20697: IPX.
When you boot a BN router when IPX is initializing, a bus error
occurs.
CR 20637: Switched Services.
In a dial back up configuration with MCT-1 as the primary
interface, the router will log transmitter time out messages
continuously after the primary interface is bounced.
CR 20724: IP.
Request to enhance the table structures in the fast forwarding
table to reduce the processing time required by IP to update the
table.
CR 20761: DLSw.
DLs remains connected to the router after SNA client is
disconnected from the router.
------------------------------------------------------------------------------
Revision 8.12/1 corrects the following problems:
=============================================================================
CR 19846: AppleTalk.
A bus fault occurs when a slot receives a certain RTMP
packet on an interface configured with AppleTalk.
CR 18876: LLC.
When a Token Ring interface configured for LLC2 bounces, a bus
error and/or a watchdog timer expired fault occurs.
CR 19668: LLC.
When a slot receives a certain LLC packet on a Token Ring
interface configured for LNM, the slot experiences a bus error.

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