Revision Notes for Router Software 8.12 rev 7
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.
============================================================================
SITE MANAGER COMPATIBILITY
=============================================================================
Router Version is managed by Site Manager version
v8.12 V2.12, V3.00, 3.00 Rev 1
8.12 fix 7
-----------------------------------------------------------------------------
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 fix 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 fix 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 fix 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 fix 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 fix 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> |
