 |
|||
     |
|||
|
Revision Notes for Router v10.01 rev3
============================================================================
SITE MANAGER COMPATIBILITY
=============================================================================
Router Version is managed by Site Manager version
v10.01 revision 1 --------------------------> V4.01, 4.00 rev 2
v10.01 revision 2 --------------------------> V4.01, 4.00 rev 2
v10.01 revision 3 --------------------------> V4.01, 4.00 rev 2
------------------------------------------------------------------------------
Revision 10.01/3 corrects the following problems:
=============================================================================
CR 24365: DLSw.
A new DLSw feature has been introduced that will allow you to
enable or disable NetBIOS session alive frame transmissions.
Previously, a NetBIOS session would always transmit session alive
frames over DLSw every 30 seconds. These session alive frames
could cause lines to remain active unnecessarily, possibly
increasing the usage cost of the line.
Use the Technician Interface to enable or disable NetBIOS session
alive frame transmissions. To enable the NetBIOS session alive
filter, stopping session alive frame transmissions, issue the
following Technician Interface command:
set wfDlsNetbiosSessionAliveFilter.1
To disable the NetBIOS session alive filter, allowing session
alive frame transmissions, issue the following Technician
Interface command:
set wfDlsNetbiosSessionAliveFilter.2
CR 24662: LAN Bridge and Source Route Bridge.
If a router encounters a slot disconnect, all bridge traffic
generated between the affected slots will terminate.
CR 25986: TCP.
When a client issues a Telnet session to a network address of
which the router is a subnet, the router attempts to establish a
Telnet session, but the local memory allocated to this process is
never returned when the session ends. The log clearly indicates
the Telnet/TCP session initializing, but does not indicate that
the session has ended. As a result, a memory leak occurs.
CR 25956: IPX.
The initiation of IPX RIP and SAP updates are staggered so that
SAP updates start after a time delay of half the RIP update
period. If you fail to configure RIP, then the value used to
initiate the SAP updates may be incorrect, thereby preventing SAPs
from being sent.
CR 21151: DVMRP.
In a route loop topology, the non-dominant router rejected routes
on the wrong interface.
CR 23779: DVMRP.
In a route loop topology, the non-dominant router accepted the
multicast data from its dominant router and deleted the cache
entry on the correct VIF, thereby causing DVMRP to fail.
CR 24985: DVMRP.
A nexthop address of 0.0.0.0 sometimes appears in the DVMRP
routing table, thereby causing DVMRP to fault.
CR None: LLC.
The presence of the g_timer_get_read() variable caused the timer
to expire prematurely which led to the transmission of multiple
SABMEŐs. This condition caused sessions to disconnect.
CR 23215: MIB II.
A problem in the router code causes indexing errors to occur
in Frame Relay direct mode PVC's. This problem affects network
management stations in particular, which are unable to correlate
IP addresses to their corresponding Frame Relay direct mode PVC's
in network management maps.
CR 26404: Switched Services.
An incorrect line in the router code causes a flag to be set
that erroneously indicates that the modem is down when it is
in fact operational.
CR 26441: BNX SWITCH.
A T1 port can be suspended in a loopback state. The only way to
disable this state is to bounce the port.
CR 26296: DLSw.
A router configured on a Token Ring network receives a test frame,
which it sends as a CANUREACH to the routerŐs DLS peer.
The peer sends an LLC test poll explorer frame as a single-route
broadcast (STE) only. A MIB variable has been created that allows
you to send STEŐs or AREŐs (all-routes explorer frames) to each
interface.
CR 26487: DVMRP.
The router will accept route updates from an unknown neighbor
provided the source IP address of the update resides on the
correct network. DVMRP should not send route updates
before sending probe packets, and DVMRP should not accept route
updates from an unlearned neighbor.
CR 23695: DLSw.
When you deactivate the line from the host, and then reactivate
it, the DLSw connection to the controller does not come up. The
log shows the disconnect message transmitted out to the AN router,
but fails to show the routerŐs response. To activate the line, you
must bounce DLSw on the remote AN.
CR 26222: SDLC.
Bus error in sdlc_disconnect_send_msg on slot 8 during scaling
testing where there were 12 primary SDLC devices per port on all
ports. This bus error would repeat every 3 to 20 minutes.
CR 26791: DVMRP.
The non-dominant router sends a graft upon receipt of a IGMP host
join message. This results in duplicate packets being forwarded
to the LAN.
CR 26825: DVMRP.
Bay Networks routers do not accept route updates from unknown
neighbors. Because Cisco routers do not send DVMRP probe messages
over a tunnel, Bay Networks routers will drop all route updates
and multicast traffic transmitted from the Cisco routers. A switch
must be added to allow accepting route updates from unknown
neighbors.
CR 26853: DLS.
A recovery problem occurred after disconnecting/reconnecting the
SDLC lines to the PU or the host on an SDLC-to-SDLC connection.
CR 26842: MCT1.
MCT1 module faults with multiple bus errors and fails to recover
when attempting to boot LN routers.
CR 23288: IGMP.
A fault occurs in igmp.misc.c when attempting to create a new
IGMP interface.
CR 24875: Source Route Bridge.
When the router switches to the backup line and then later
switches back to the primary line, source route frames get
dropped.
CR 26885: IP.
After OSPF goes down one slot and comes back on another slot,
some IP routes may be missing on one slot (the old OSPF soloist
slot), and all other slots are pointing to the old OSPF slot as
the author of that route.
CR None: Frame Relay.
Frame Relay-ATM network interworking required support allowing many
DLCIŐs to map to the same VCID.
CR 25885: DLSw.
CR 25929 A bus error occurs when attempting to establish a DLS/SDLC
connection to one particular link station. This condition can be
attributed to the configuration of a duplicate local device.
CR 26593: DLSw.
PUs can fail to activate in a manner that results in
NCP status code PAPU2 after you execute a prescribed sequence
of actions. This sequence of actions can be cleared only by
a NetView operator.
CR 25849: SDLC.
The primary FRAD inexplicably fails to issue DISCs to all
configured remote devices. For example, when you configure 3 PUs
with link station addresses 01, 02, and 03, the FRAD initially
sends DISCs for all three, but after all three failed to respond,
FRAD stops sending DISCs. Then when 03 eventually responded, the
FRAD still failed to send a DISC for it. Resetting the slot caused
the FRAD to begin sending DISCs for PU 03, but not for 01 and 02.
CR 26919: SDLC.
In the below network, PC3270 sessions fail to recover
after disabling and enabling the wfSyncEntry instance for the
Frame Relay port on a router configured with Primary SDLC
ports. This problem occurs because the remote/primary SDLC router
does not send out the XID null frames onto the Frame Relay line and
the host/secondary SDLC router does not send out a DISC request
to the host after the frame relay port on the host router notices
that the primary router stops polling the host router.
host remote
host -- sdlc -- router --- FR 1490 --- router -- sdlc -- PCs
CR None: SNMP.
When setting multiple VARs in one PDU that includes display
strings, the SNMP agent sets the value of the strings to the
correct length, but truncates the last three to four bytes.
CR 26192: MIB.
The configuration file for the ASN router (ti_asn.cfg) supplied
with all versions of 10.00 (rel through 10.00 rev4) has a 9.00 MIB
version.
CR 26364: APPN.
You cannot enter a host name consisting of 17 characters
when issuing an APPN ping at the Technician Interface prompt.
You should be able to enter up to 17 characters for an APPN
host name.
CR 25123
CR 23427: DLSw.
A bus error occurred in dls_flow_tcp_busy after disabling DLS
on a remote router. The remote router is a BCN. The BCN's SDLC
lines are configured as Primary. This error occurs if there is no
configured slot IP address in DLS.
CR 27063: DLSw.
The router generates the following log message too frequently:
"received an SSP command in TCP local"
CR 27087: IPX.
An ARE router constantly resets when IPX is configured within any
ATM Service Record. The problem has been seen in both a PVC and
LANE configuration where IPX is configured on the ARE and at least
one other slot on a BLN or BCN router.
CR 26440: DataPath.
Successive attempts to disable and re-enable Learning Bridge
causes the router to eventually fault because of insufficient
memory. This problem stems from a memory leak in the routine
dp_cc_op_act.
CR 26924: DLSw.
The router code corrupts DLSw data packets during periods in which
the buffer depletes its memory. The packets become corrupted when
the 16-byte DLSw data frames get inserted between the end of the
TCP header and the start of the DLSw data. This condition causes
the receiving routers to experience tag violations.
CR 27140: IP.
A problem occurred when routers running OSPF learned the same
external network with two different masks (the more specific mask
learned by RIP being injected into the OSPF cloud; the less
specific mask via a static route). Then when the RIP network is
disabled, the more specific route gets flushed out of the
OSPF lsdb, and IP points to a disabled interface as the next valid
hop.
CR 26129: MIB.
Problem occurred when attempting to open an 8.12 config file
(with a MIB stamp of 8.10) with SM 4.01/rel in local mode. Problem
exists on both PC/Windows and UNIX SM platform.
Added support for the following IPX MIB attributes to ensure
backward-compatibility for the Site Manager IPX MIB.
wfIpxBaseNetSizeBoundEn
Allows you to enable or disable the maximum allowable size of the
network table.
wfIpxBaseMaxNetTblSize
Allows you to specify an integer that determines the maximum
allowable size of the network table.
wfIpxBaseNetTblFillNotify
Allows you to specify an integer from 1 through 100 that
notifies you when (configured) percentage is reached.
CR 20940: Redundancy.
A router experienced a bus error when Router Redundancy received
corrupted frames and attempted to process the frames as multiple
Router Redundancy PDU fragments along with SNMP frames.
CR 26268: BNX Switch.
Congestion control was not setting FECN and BECN on trunks
correctly.
------------------------------------------------------------------------------
Revision 10.01/2 corrects the following problems:
==============================================================================
CR 26969: DLSw.
Test polls generated by running a TCL script in a dual switch
DLS network causes the router to fault with tag violations.
-----------------------------------------------------------------------------
Revision 10.01/1 corrects the following problems:
==============================================================================
NOTE: Revision 10.01/1 incorrectly referenced CR 25249. The correct CR
number is 24249, as documented in the 10.01/1 revision notes.
-----------------------------------------------------------------------------
CR 23065: IP.
Attempting to boot an ASN router configured for IP host-only may
cause a tag violation to occur.
CR 25483: Switched Services.
The router fails to redial if the first connection attempt times
out before the DCE asserts DSR, but after receiving a connection
indication (CNX) from the DCE.
CR 26247: APPN.
APPN attempts to connect to a link station 10 times (its fixed
limit) before it times out. This problem occurs with APPN over
SDLC when SDLC tries to bring up the link station 10 times before
timing out and alerting APPN. If APPN reaches its limit of 10
retries, it deletes the link station.
CR 26452: GAME.
A g_fwd may fail before the slot has discovered that the remote
slot has gone down. This results in a panic as the sending slot
thinks the remote slot should have received the buffer because
it is still in its slot mask.
CR 25591: Translation Bridge.
RIF entries on a Token Ring segment may fail to age properly.
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 while
multiple SRFŐs are being received simultaneously.
CR 18837: BOOTP.
In a multinetting environment, the router chooses the last address
added to the multinetted interface as the BOOTP gateway. If you
disable BOOTP for that address, the router continues to use this
address as the BOOTP gateway instead of selecting the next
address in the network configuration as the new BOOTP gateway.
CR 25126: MCT1E1.
The Munich driver mail may fail to transmit all frames, except
interrupt queue frames on the priority queue. This problem occurs
only on logical lines with high error rates.
CR 24714: OSPF.
When you configure two AN routers across a synchronous interface
with a MTU size of 4608, OSPF adjacencies can take up to 20
minutes to form. The AN router receiving the Data Base Description
packets remains in the loading state while the router sending this
information will be in the full state.
CR 19711: Scripts.
The SHOW HARDWARE SLOT command generates too many columns on a
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 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 22792: IP.
Within IP traffic filters, for any rule that has a log action,
the router logs an entry. Only the rule with the highest
procedure should be performed.
CR 23340: LLC.
The router may fault with the following error during a test poll
storm:
"Error in Buffer.c at line 157"
CR 24142: IP.
The router faults after receiving corrupted ICMP packets that have
an IP length that exceeds 65,000 bytes.
CR 25569: DLSw.
A Windows NT/NetBIOS session may randomly fail to establish through
DLSw whenever the server and the client pick up the same local
session ID for the session they are attempting to establish.
CR 25656: GAME.
The first day of each month the clock on the AN router shifts by
one extra day. As a result, the Frame Relay circuit on the router
disconnects, preventing the router from sending LMIs to the
switch. This condition also has caused the clock to stop
temporarily.
CR 24249: FRE-2.
If you plug an incorrect console cable/connector into the SRML
module of a running BN router, the LED's located in the front of
the FRE's suddenly stop blinking, indicating that the router is
inoperable. The lights resume normal operation when you remove
the console connector.
CR 25844: DLSw.
Playing a test poll storm in a dual switch configuration
causes a watchdog to occur on the adjacent router.
CR 24048: LNM.
An IBM LAN Network Manager station intermittently fails to
establish a link to a Token Ring interface. This situation occurs
only when the Token Ring interface was previously linked and then
unlinked from another LNM station.
CR 24049: LNM.
When unlinking an IBM LNM Manager from a Token Ring interface,
the router generates incorrect LNM link status for the MIB variable
wfLnmInterfaceEntry. When you unlink the LNM station,
the LNM link status should reflect a "nil" value, rather than
retain the previous MAC address of the IBM LNM Manager station.
CR 25418: DLSw.
When you issue a "get wfDlsSlotEntry.*.5" command from the
Technician Interface, the router generates invalid information
for the MIB variables .wfDlsCurrentMemory and .wfDlsHiWaterMark.
CR 25805: NVFS.
Compacting Series 2 Flash cards (especially Epson Seiko Flash
cards) can occasionally corrupt file systems.
CR 25956: IPX.
IPX may stop sending IPX SAPs if you have not configured IPX RIP.
CR 24311: IPX.
If IPX tries to send IPX update messages to busy slots, it may
fault because of a g_fwd failure.
CR 25867: DLSw.
A router running with hundreds of DLS connections may fault with
the following error because a buffer is being freed erroneously:
"Error in Buf.float.c at line 114"
CR 24821: X.25.
When X.25 processes a connect indicate and you have not enabled the
flow control negotiation parameter, X.25 rejects all facility
code. The flow control negotiation parameter is limited to
packet and window size only.
CR 26107: Frame Relay Switch.
Excess burst is not being calculated correctly, causing frames
that exceed excess burst to be dropped at the ingress; the
data does not exceed excess burst. Excess burst
uses the large default that should never be exceeded.
CR 26139/
25737: Frame Relay Switch.
When one Navtel is configured to send packets at 256 bytes, and the
second Navtel has a packet size of 32 or lower, the traffic
stops. Traffic resumes when the packet size is increased to a
value of 64 or higher.
CR 26118: Frame Relay Switch.
When creating multiple mappings for the MIB attribute
wfCctOptsCngcEntry, the first map fired and deleted all the
structures and the second map tried to use invalid memory. This
caused a tag violation to occur.
CR 25846: OSPF.
After OSPFŐs Dykstra algorithm runs for 65,535 tries, OSPF faults
with the following message: "LSA in UNEXPECTED STATE".
CR 26163: MCT1E1.
When selecting an unused QMCT1 or DMCT1 interface in Site Manager,
the Link Module Fail LED lights up. When you reboot the router,
the fail LED's on both the QMCT1 and Dual MCT1 link modules turn
off.
CR 25900: MCT1E1.
On a router configured with IP over PPP, with 64-byte packets
using one slot with 48 logical lines, the QMCT1 is unable to
utilize 85 percent of the 128K line.
CR 26230: DLSw.
If SDLC secondary disconnects, and the router reaches a
CANUREACH state during this period, DLS never reestablishes.
CR 25351: DLSw.
When a DLS MAC entry is cached (for example, when a test poll was
received from that MAC address), creating an instance of
wfDlsDefaultMacEntry for that MAC address may cause the router to
fault.
CR 20516: LLC.
Disabling a DLS interface on a Token Ring network while it is
transmitting and receiving DLS traffic causes a watchdog timeout
to occur in llc.
CR 21715/
22160: DLSw.
A watchdog timeout occurs in DLS after disabling the DLS base
record. If you have multiple SAPs configured (for example, all 127
possible SAPs), DP takes too long to deregister SAPs when DLS
shuts down.
CR 23591: DLSw.
Establishing a DLS over SDLC connection may take a long time
because of a delay in the transmission of CANUREACH.
CR 24959: MCT1E1.
When listing the instances of the MIB variable
wfDs1E1BertStatsEntry, the listing succeeds intermittently for
port 1 but fails to succeed for subsequent ports.
CR 25119: MCT1E1.
When a primary clock is lost on a QMCT1, the router fails to
initiate the secondary clock on port 3.
CR 25255: Hardware Compression.
The driver faults when it mistakenly determines the state of the
rings as hung when the rings are functioning properly.
CR 25096: MCT1E1.
The QMCT1 port 1 primary clock was changed to an external clock.
However, there is no external clock connected. Therefore,
port 1 clocking should revert to the secondary clock but does not.
CR 24161/
CR 25120: Bisynchronous.
The Bisync/BOT code does not handle a DLE-DLE combination
correctly within transparent text.
CR 23255: DataPath.
When running a bridge storm (bridging loops without Spanning Tree),
a slot may reset with an "out of memory" error or a watchdog timer
error.
CR 25443: FDDI.
A hardware problem can occur when the state of a protocol is
"down", but the state of the interface is "up". If you monitor the
FDDIEntry, the Tx stats continue to grow while the Rx no longer
increments. If you perform a packet capture on Rx on this
interface, the trace will show that packets are being received,
but unacknowledged. This condition can be caused by hardware
corrupting information in the Ring Descriptors, which causes the
interface to hang and never recover.
CR 25473: DLSw.
Link stations do not recover when a Frame Relay cable is
disconnected and connected again.
CR 24918: GAME.
A new Autosave log feature has been implemented on LN routers
that allows users to automatically save the log to the Flash card
or floppy drive when the log is about to wrap. This new feature
prevents the log information from being lost.
You can enable the Log Autosave feature from the Technician
Interface only.
The Log Autosave feature requires that you set two new attributes
in wfSerialPortEntry object: wfSerialPortAutoSaveNumFiles and
wfSerialPortAutoSaveVolume. The wfSerialPortAutoSaveNumFiles
attribute allows you to specify a value that determines the number
of times a log will be saved when it wraps. Specifying a value of
0 disables the feature; 0 is the default.
The wfSerialPortAutoSaveVolume attribute allows you to specify
a volume number ("2:"), or a volume name ("a:"), which determines
where you want logs to be saved. Specifying a colon after the
volume or volume name is optional.
On a BN platform, there is only one instance of the
wfSerialPortEntry object. Therefore, you will need to specify the
attributes described above for this instance.
On an ASN platform, there are 4 instances of wfSerialPortEntry,
each corresponding to a possible slot. You can configure the
feature on only one of the instances corresponding to an existing
slot.
On an LN platform, there are also 4 instances of wfSerialPortEntry.
Enable the feature on the first instance, which should correspond
to the console port (wfSerialPortEntry.wfSerialPortName.1 =
"CONSOLE").
The log gets saved in a file named "auto
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
