 |
|||
     |
|||
|
Revision Notes for Router 10.0 rev 2
=============================================================================
SITE MANAGER COMPATIBILITY
=============================================================================
Router Version is managed by Site Manager version
v10.0 revision 2 --------------------------> V4.00, 4.00 rev 2
-----------------------------------------------------------------------------
Revision 10.0/2 corrects the following problems:
=============================================================================
CR 17058: VINES.
After removing a local memory segment, the pointers were not set
correctly, preventing the allocation of new buffers. Instead,
memory that had been freed was being corrupted.
CR None: VINES.
A router may experience memory loss or corruption when numerous
VINES routes are aged simultaneously.
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 22166: IP.
When you attempt to restart BGP on a router with a large IP routing
table that contains more than 1700 cached networks entries, a
watchdog timer expires, causing the router to fault.
CR 22611: DVMRP.
Routers configured for DVMRP/IGMP will not send out prune messages
after the DVMRP/IGMP interface bounces, causing the
transmission of unnecessary multicast packets onto the networks.
CR 22789: ATM.
A periodic virtual buffer memory error may occur in routers
containing 10 or more LAN emulation clients running both IP and IPX.
This error may result in IP failing to restart on the LEC interfaces
or the LEC interfaces failing to restart altogether.
CR 21767: OSI.
Router fails to respond to an OSI ping over PPP after the
synchronous line is bounced.
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 22348: Technician Interface.
The ATM install script, install.bat, resets the ATM address User
Part to zero when you do not use autogeneration and when you enter
the optional network prefix.
CR 22750: Telnet.
When the Telnet Client fails to set the "Push Bit" correctly during
Terminal Type Negotiations, Telnet sessions may not get established.
CR 20863: DECnet.
If you bounce a DECnet circuit while it is learning adjacencies,
bus errors may occur.
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 22681: Frame Relay Switch.
The Stats File has the same start time for each record it creates.
The start time stamp in the Stats file header should be
based on the last time stamp the stats file was written, not on the
beginning of the STATS initialization time.
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 22517: Frame Relay Switch.
When you compact an SRAM, throughput on an Frame Relay Access line
drops from 94% to 12%, which is unacceptable.
CR 21743: IP.
The "Show IP Arp" script produces invalid values for the second two
bytes of the physical address when using Frame Relay (and probably
ATM and SMDS).
CR 22824: Frame Relay Switch.
The Loop Back LEDs go out on all ports on the QMCT1
when you configure the first port. The Loop Back LEDS on ports
2-4 should remain on until you configure them. Also, the red LED
when in Red Alarm state remains on when you disable the port.
CR 22266: MCT1E1
The Show ds1e1 Stat screen indicates that there are twice as many
circuit entries in the table (8) than what actually displays in
the table (4). The screen should indicate only four circuit
entries.
CR 22527: MCT1E1:
The following MIB attributes always should be set to zero:
wfDs1E1ModuleEntry.wfDs1E1ModuleTxBufferUseCredits.1.3 = 0
wfDs1E1ModuleEntry.wfDs1E1ModuleRxBufferUseCredits.1.3 = 0
CR 22714: 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 22822: IPX.
The router fails to acknowledge RIP and SAP requests when you
disable the "Listen" option on an IPX interface.
CR 22209: IP.
When a slot disconnects and then reconnects, a race condition
exists in the interslot communication, causing IP routing table
inconsistencies across slots.
CR 22984: Frame Relay Switch.
When you attempt to change the value of the FDDI bit mask for Stats
Data Collection using Site Manager, the router always returns a
NIL value.
CR 22113: SDLC.
If you configure a router for local switch DLSw or for a DLS
cloud using SDLC secondary, the local device will not recognize
unequal SAPs.
CR 23070: IP.
When the cache contains more than 500 entries and the default
route is flushed from the cache, the cache's RTBL is reset.
After the cache has been reset, and the cache is completely filled,
deleting an entry from the cache may result in a bus error.
CR 22943: MCT1E1.
The router will fault if remote connections go down during
periods of heavy traffic.
CR 23015: MCT1E1.
When a QMCT1 is configured with a FRE1 CPU Module, the QMCT1
download fails. However, there is no message indicating that the
QMCT1 is no longer supported by the FRE1.
CR 22602: OSPF.
Designated Router (DR) election does not work correctly on a
Frame Relay interface. OSPF initializes on a Frame Relay
Interface, causing the ATTEMPT state to start before the
DLCI becomes active. By the time the DLCI becomes active, the
Inactivity Timer for the neighbors has nearly expired or has
already expired. This interface now declares itself as the
DR.
CR 22754: IPX.
IPX routers running Version 8.12 respond to queries faster than
IPX routers running router software version 9.00 or greater. For
example, two routers are configured on an Ethernet segment, with
one router running Version 8.12 software and the other router
running router software version 9.00 or greater. If a host on the
same Ethernet segment sends an IPX RIP query, the
8.12 router responds to the query about five times faster than the
router running 9.00 or greater. Therefore, the 8.12 router always
will be the preferred router.
CR 22785: OSPF.
After you dynamically disable the
wfOspfGeneralGroup.wfOspfGeneralDisable.0 instance, it faults, and
subsequent attempts to enable it will not take effect.
CR 22982/
23036: Frame Relay Switch.
Customer requests event messages 143-147 should be changed from
INFO to WARNING for trapping purposes. Also, wffrSwCCtEntry must
be changed to wfFrSwVcEntry for events 122 and 128 because they
were the wrong attribute.
CR 22386: MIB.
Report Generator does not recognize the 128 context hardware
compression daughterboard
CR 22917: IP.
When booting a configuration file prior to Version 9.00 using a
9.xx image file, the RIP MIB object, wfRipInterfaceEntry, does
not initialize the wfRipIntfEnable attribute with the value found
in the configuration. By default, this attribute is enabled,
therefore, if the configuration file has the RIP interface
disabled after booting with an 9.xx image, the RIP interface
was being set to enabled.
CR 21298: IP.
If the Technician Interface is running on a slot on
which IP is not configured and you enter the IP Cache command to
examine a remote interface cache, the router may fault.
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 22729: ISDN.
ISDN failed in some tests of Australia ASN PRI test and
French Delta test.
CR 22085: FTP.
When you use the FTP software package QVNET to transfer a file to
a router, a tag violation error occurs.
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 21893: DLSw.
NetBIOS Name recognized frame is duplicated by DLS in a local
switch configuration with Source Routing Bridge enabled.
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 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 20955: PING_MIB.
When issuing a series of pings, the ping MIB may receive
echo replies out of sequence, thus causing the ping MIB to
report invalid positive values for total and maximum delay.
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 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 22020: LLC.
If you change the Source Route Bridge Ring ID dynamically, DLSw
fails, preventing connections established over DLSw (SNA and
NetBIOS) from functioning.
CR 21944: Source Routing Bridge.
A Specifically Routed Frame (SRF) 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 actual
destination address and not the Wellfleet group MAC address.
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 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 22977: DLSw.
The router faults when 400 TCP peer connections with 212
DLS connections are running on one slot where DLS is bounced.
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 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 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 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 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 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 22267: MIB.
You cannot properly configure the 'TR End Station ARP Type'
parameter in Site Manager revisions 3.00 through 4.00
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/4.00 users to set this attribute dynamically
against an 8.12 router version.
To manage this MIB attribute correctly, you MUST consider the
following:
o Update pre-8.12/9 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/9 and 10.0/2 to correct the MIB inconsistency and to
preserve the original attribute setting.
o Site Manager users running revision 2.12/fix1 and revision 3.00
or higher 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 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 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 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 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 22434: TCP.
When you attempt to boot a router consisting of 500 plus TCP
connections on a slot, an error occurs in mib_ent.c at line 1115.
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 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 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 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 19502: SYNC.
When you enable the RTS/CTS option on an AN or an ASN router,
the synchronous interface goes down, preventing it from
transmitting and receiving frames.
CR 19206: DLSw.
A fault can occur in tcp_prep_xbuf.c when establishing multiple DLS
connections.
CR 23669: VINES.
When a VINES client is added to the router's neighbor 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 when it is added back into the table.
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 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 23734: DLSw.
DLSw does not forward XID-P if the entry in
wfDlsConnectoinEntry is in a disconnected state. Instead, the
router drops the XID-P's.
CR 13463: IP.
When upgrading router software from 8.01/4 to 8.10 or higher, the
processing of multiple ARPs could result in a hogs bufs
condition.
CR 22287: Frame Relay Switch.
The QMCT1 has a hardware loopback, which the user needs to be able
to change using Site Manager.
CR 21565: MCT1E1.
Each interface SYNC LED remains lit on QMCT1 link module while the
router is under the following conditions:
1. The router is powered up and the link module is inserted into
the router.
2. The router is power cycled with the board in it.
3. While executing the 'diags' prompt from the Technician
Interface.
CR 21926: BNX.
BNX scaling rack found slots taking an inordinate amount of time
(approximately 25 minutes) to restart after you hot-swap or
reset the slot manually.
CR 17874: FTP.
When issuing an "mput" operation to a router that does not have
enough available space, the session terminates, providing no
indication that a problem exists. However, if you issue a single
"put" operation, the router software indicates that a problem has
occurred.
CR 22506: Technician Interface.
Technician Interface accepts only the default ELAN if you fail to
set the name ATM ELAN correctly in the file install.bat for ATM.
Alternatively, you can enter the name of an ELAN that you
configured previously.
CR 23296: Switched Services.
If a slot on the router is connected to an AT&T 4ESS switch, the
router can establish only a single outgoing connection on an ISDN
PRI line. All additional outgoing connection attempts will fail.
The router can, however, successfully receive multiple incoming
connection requests on the ISDN PRI line.
CR 21491
20126: OSPF.
Router failed to find the nexthop neighbor during SPF calculation,
causing OSPF to fault.
CR 22795: ISDN.
The ISDN BRI router sends a "Connect" message with a channel
identification information element that is rejected by NTT's
(NTT: Japan telecommunication telephone company) ISDN switch. As a
result, the call is never completed.
CR 23043: Hardware Compression.
An OSYNC cable configured with 8 PPP lines at 1024K clock speed,
running hardware compression on each line will eventually stop
forwarding data as the hardware compression or decompression
engine will fault.
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 23344: ATMARP.
Classical IP over PVCs not properly removing and resolving aged
entries.
CR 23268: ATM_DRVR.
Added a new MIB attribute in the wfAtmizerDrvCfgEntry,
wfAtmizerDrvCfgIwfCCt, which will provide a method to find the
circuit number associated with a Frame Relay/ATM Internetworking
service record.
CR 22672: Technician Interface.
The "Show Proc Mem" and "Show Proc CPU" commands sometime display
negative numbers.
CR 23292: X.25.
Bus error occurs sometimes when no valid service record that
matches an incoming X.25 call can be found.
CR: Frame Relay Switch.
Dynamically creating an ISDN PRI port causes the switch to
fault.
CR 22538: DVMRP.
Graft packets were not sent upstream when new members joined the
existing group if there was no previous range for the group in
the remote cache table.
CR 23195: IGMP.
The state of IGMP on an interface as reported in the MIB is
inaccurate. For instance, when you disable IGMP globally, each
IGMP interface entry remains in an up state (state of 1).
However, if you disable IGMP globally and reenable it on the
interface, the state of the IGMP interface remains in a state of 3.
CR 23222: IPX.
A route with a hop count of 15 does not get installed into the
IPX routing table.
CR 23377: DVMRP.
If a circuit receives multicast traffic on a circuit
before all other DVMRP circuits come up, the forward alias
will not include the circuit that is disabled. When the circuit
is enabled, the forward alias is not updated. The cache will not
reflect the new circuit until after the forwarded alias times out
and a new alias is created.
CR 23311: Frame Relay Switch.
A customer request to increment the FRAME RELAY RX counters on
PVC's that reside on the ATM interface. Incrementing these
counters will facilitate the process of tracing packets throughout
the network.
CR 22482: ATM.
When two ATM end stations simultaneously attempt to establish Data
Direct VCs to each other, the resulting ATM address comparison
incorrectly drops the incoming VC with the lower ATM address.
The comparison should result in using the lower address.
CR 22705: IP.
The "ip ospf_lsdb" command causes buffer corruption of the AN
router platform.
CR 23346: IP.
IP was causing an memory leak when the IP filter
"Forward to First Up Nexthop" is being used, and the next hop
being used goes down.
CR 20095: Frame Relay Switch.
When Frame Relay VC goes down and comes back up, the router
generates a message indicating that IP refused DLCMI
registration. This does not happen when the switch is rebooted.
CR None: Frame Relay Switch.
A new feature that allows a Frame Relay switch PVC to be terminated
either at the ingress or egress switch port and transmitted to
a router Frame Relay DTE port rather than across the Frame Relay
network (ingress) or to a driver (egress).
CR 23486: Frame Relay Switch.
The size of the wfCircuitLineList MIB attribute has increased
to the point where it exceeds the string limitations allocated
for the Hconfig file to handle strings in a configuration file.
Hconfig needs to be modified to handle the increased size of this
MIB attribute.
CR 24407: Token Ring.
A packet whose size exceeds the configured size of the MTU on an
AN or AN-2 Token Ring network may cause a fault.
CR 23257: IP.
Setting the Host Cache to 120 seconds on a Frame Relay interface
causes the slot on which the interface resides to log the same
debug messages continuously. In addition, the router is getting hog
buffer in "earp_operational_act+0x0", causing the slot to be
disconnected continuously.
CR 22963: IP.
IP replies (with a valid ICMP echo reply) to an ICMP echo request
to a disabled PPP IP interface when the TTL in the request is set to
1.
CR None: Frame Relay Switch.
Customer requested enhancements to the existing Frame Relay Control
feature.
1. Enhanced Control Logging Facility enables you to control the
frequency at which messages related to congestion control
are logged.
2. Enhanced Congestion Monitoring Facility enables you to view the
congestion level of any circuit at any instance of time.
CR 23556: GAME.
Issuing a "g wfKernelEntry" command may cause the ANS router
to drop packets.
CR 23178: OSPF.
An Area Border router fails to generate ASB summary links,
causing a loss of connectivity to AS external routes. This
condition can occur when a virtual link that exists between two
routers gives both routers a connection to the BACKBONE and to the
TRANSIT Area. After the ASB router on the BACKBONE has been
rebooted, the routers in the TRANSIT Area lose
connectivity to the AS Externals.
CR 22107: MCT1E1.
When you enable an MCE1 circuit on an ASN router, the router
generates the following warning message in the log file:
# 1: 02/06/96 13:08:58.824 WARNING SLOT 1
DS1E1 Code: 11
Connector COM21 enabled.
This should not be a warning message but rather an informational
message.
CR 23172: IPX.
A router accepts IPX RIP packets and forwards them out the wrong
interface after you boot the router. For example, after booting a
BCN router with 30 interfaces, the router sends out IPX RIP
packets with a source and destination address that is
equal to one of the other interfaces in the router.
CR 23533: DataPath.
When you configure multiple circuits with Source Route
Bridge, Source Route Bridge Spanning Tree, and traffic filters on
the same slot on a Token Ring network, the slot may fault when you
reboot the router.
CR 22961: OSPF.
Certain routers configured on the ATM PVC backbone report OSPF
packets with bad checksums in the log, causing a bus error to occur.
CR 23670: Frame Relay Switch.
When you attempt to dynamically change the Management Type in
the wfFrSwDlcmiEntry MIB, an error occurs in map_rem.c at line 60.
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 23439: IP.
The filter precedence appears to be working in reverse order
on ARE platforms so that a "drop all IP source filter" must be
made the highest precedence filter (rule #1) to avoid blocking
configured accept filters .
CR 23477: IP.
A slot running an ATM ARE might experience a fault if
a configured IP traffic filter is left in a disabled state
on the ATM interface.
CR 20443: ATM.
The ATM driver received too many release messages, causing it
to log the following debug messages:
"ATMizer command ring full"
"vpi/vci flow controlled"
CR 23748: Frame Relay Switch.
A situation exists in which the lowest priority traffic can
suddenly stop flowing while a constant stream of traffic
is transmitting out an interface configured with traffic
prioritization enabled.
CR 23559: PPP.
The Sync driver does not calculate SaveInOctets correctly.
SaveInOctets need to be accumulated for all packets received.
The current LQR packet is the only packet being
accounted for.
CR 19376: SNMP.
Disabling SNMP while the lock is enabled and in use can cause
the router to fault.
CR 18946: DLSw.
Bouncing the DLS base several times in succession after
establishing TCP connections causes the router to experience
an error in mib_ent.c at line 724.
CR 23668: DLSw.
DLSw session occasionally fails to recover when disabling and
re-enabling TCP.
CR 23398: DVMRP.
The forwarding cache does not age out after it receives a graft
packet.
CR 23449: DVMRP.
Graft packets may be accepted and acknowledged from a non-neighbor
router.
CR 22534: OSPF.
An NBMA within priority of zero (0) does not display the DR or
BDR in the MIB interface object.
CR 20810: OSPF.
Adjacencies may be trapped in exchanged state when a second
virtual link is configured.
CR 23909: FTP.
FTP buffer initialization was incorrect for messaging between
data server and control gates. This condition caused the router
to fault.
CR 23971: Frame Relay Switch.
Six events added to FRSW.edl were out of order. This caused an
inconsistency with events from earlier revisions of code.
CR 23696: Frame Relay Switch.
The wfFrSwVcXnetErrors counter will reset to zero when
the cross net status changes from active to inactive. The counter
appears to increment correctly when the status changes.
When the counter resets to zero and does not increment, you
can be misled into believing that there are no cross net errors,
and thus no problem with the cross net polling. A request has
been issued to allow the counter continue to increment as long
as the interface is down, and then set it to zero when the
interface returns to an active state.
CR 23459: MCE1.
An ASN router faults when you delete PRI Demand when Demand line
is active.
CR 23479: GAME.
An AN2 router may corrupt Token Ring frames before transmitting
them to other hosts on the Token Ring network.
CR 21992: OSPF.
OSPF may incur a watchdog timer error while rebuilding a Link State
Advertisement.
CR 20351: Switched Services.
Traffic being bridged from an Ethernet line to a synchronous line
does not bring up a ISDN dial line. However, IP and IPX
protocols are routed normally.
CR 20508: DLSw.
Disabling and enabling DLSw interfaces cause SNA DLS connections
to remain closed. You might have to reboot the router to
establish connections. NetBIOS and SDLC traffic remains
unaffected.
CR 23964: Hardware Compression.
The hardware compression driver could trigger on a false fatal
error from the compression or decompression engine, causing
hardware compression to restart on a slot.
CR 23702: BNX.
BNX OSPF Code 78 should be a warning message.
CR 24103: Frame Relay Switch.
DS1E1 Logical Lines can stop transmitting for no apparent reason.
LogicalLine, wfFrSwDlcmi, and wfFrSwVc states all show active,
but will not transmit.
CR 24192: MCT1E1.
The QMCT1 mistakenly detects a loopback code when you pull out
the T1 cable or replace it.
CR 23698: Frame Relay Switch.
Whenever the PRI D-channel is restarted, approximately 70 log
messages appear. Nearly one third of these messages are Switched
Services code 110 messages, which is excessive.
CR None: FRE.
A problem related to the FRE-II BB chips occurs when the PLL for
BBTX goes off frequently or stops entirely. This condition
potentially can disable all slots when the bad board flow controls
all BB rails.
CR 24250: MCT1E1.
When the T1 Cable is disconnected at the remote end, the QMCT1 may
not detect a carrier loss because the synchronous LED remains on
and the Red LED, which indicates a Red Alarm state, remains off.
CR 24304: Technician Interface.
The Technician Interface does not display Help command
descriptions after the "permit" command.
CR 24377: Frame Relay Switch.
PVC stays in active state even though Driver, DLCMI, IP are all
inactive.
CR 24047: DSLw.
A router within a DLSw environment where SNA clients are
configured to use SNA XID Format 3 instead of Format 0
may experience a DLSw slot reset due to a "Watchdog expired,
service terminating" fault.
CR 24418: DLSw.
An enhancement request to give customers the ability to enable
DLS interslot broadcast reduction. This is required for central
node routers.
CR 24224: LNM.
A router running source route bridging and LNM could generate a
tag violation in map_keep_rx.
CR 23532: Frame Relay Switch.
PVC redirect needs new action type,
such that it would switch to backup on demand but would
stay in back up until you issue manual redirect.
CR 23605: Frame Relay Switch.
IP goes down because a fault occurred in frsw_cngc on SLOT 5.
CR 23446: Frame Relay Switch.
Crossnet A-bit inactive updates can be sent by setting a mask
of the wfFrSwBase.wfFrSwBaseShutDown or by adding a shutdown
flag to the boot, reset, or restart commands using the Technician
Interface.
CR 24091: Frame Relay Switch.
Data throughput is degraded in 6.00 REL when compared
to 4.21/rev5.
CR 23872: DVMRP.
Issuing the "show DVMRP NEI" command allows the DVMRP routers
to identify each other on the network, but router information
between the routers is never exchanged.
CR 21873: OSPF.
ospf_ase_fill_in_cost faults when best_route is not available.
-----------------------------------------------------------------------------
Revision 10.0/1 corrects the following problems:
==============================================================================
CR 23609: Switched Services.
If you disconnect the BRI cable and then attempt to reconnect it
after dynamically deleting one of the local phone numbers that
are configured for an ISDN port on a BRI card, a bus error
can occur.
CR None: Switched Services.
This customer enhancement allows a demand circuit to be
associated with a point-to-point circuit so that if
the point-to-point circuit dies, the demand circuit gets
established immediately without having to wait for the routing
level to determine that the point-to-point route is unavailable.
After the demand connection is established, it remains operational
until you manually terminate the connection using force
takedown. This allows you to control whether the data switches
back to the point-to-point circuit. When the point-to-point
circuit becomes active, its router has a lower priority, and
the data will continue to flow over the demand connection.
Using Site Manager, create the point-to-point circuit, but do not
change the circuit type to Primary. Create the demand circuit to
be used as a backup. From the Technician Interface, get
the wfSwservOptsEntry attribute for the demand circuit. Set the
wfSwserv0ptsBackupCct attribute to the circuit number of the
point-to-point circuit number. It is also required that you
configure the routing level to give precedence to the demand route
over the point-to-point route.
CR 23296: Switched Services.
If a slot on the router is connected to an AT&T 4ESS switch, the
router can establish only a single outgoing connection on an ISDN
PRI line. All additional outgoing connection attempts will fail.
The router can, however, successfully receive multiple incoming
connection requests on the ISDN PRI line.
t
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
