 |
|||
     |
|||
Revision Notes for Router Software 12.00/revision 1 and 2=============================================================
SITE MANAGER COMPATIBILITY
=============================================================
Router Version is managed by Site Manager version v12.00 revision 1 ------------------------> 6.00 and 6.00 rev 1
v12.00 revision 2 ------------------------> 6.00 and 6.00 rev 2
Revision 2 of Bay RS 12.0 is Year 2000 Compliance Certified by Bay Networks. It has successfully passed Bay Networks Test Procedure which tests conformance to Bay Networks Year 2000 compliance definition, both of which can be found at Bay Networks Year 2000 Web Site at http://www.baynetworks.com/year2000/. -------------------------------------------------------------------------------- --------------------------- Revision 12.00/2 corrects the following problems: ============================================================= CR 34374: FireWall.
Multilayer 2 protocol encapsulation over different media will not
work if packets are received together in a list of buffers rather
than one buffer at a time. Similarly, multilayer 3 protocol,
(i.e., IP and IPX), may not work either.
CR 32753: OSPF.
A problem exists in which an area border router with area range
summaries configured can get stuck in a load state while the
other side of the adjacency is in a full state.
CR 33735: Switched Services.
When you attempt to configure DOR dynamically, a routing update
(RIP/SAP for both IP and IPX) problem occurs, preventing the
exchange of routes with the data packet call.
CR 33666: DLSw.
A reserved capx incorrectly returns an error code of
DLS_CAPX_INVALID_CTRL_VEC_ID.
CR 33729: DLSw.
A VBM error may occur when DLS packets are fragmented in the
network.
CR 33749: WCP.
A dial-on-demand circuit configured with WCP fails to come up
on a router.
CR 33799: WCP.
When you attempt to configure WCP on a dial-on-demand circuit in
dynamic mode, CCP remains at zero and fails to start.
CR 30361: MIB.
The synchronous external clock speed fails to map over to the
MIB II clock speed, causing improper aggregation between the
the internal and external lines.
CR 33155: SDLC.
An SDLC connection will be dropped when an ARN router sends a
packet before it is polled.
CR 31684: DLSw.
Enhancement request to disable DLS multislot broadcasts from the
DLC side.
CR 32854: OSPF.
33434:
OSPF sends link state requests (LSR) when either the retransmit
timer activated or a link state update (LSU) was received.
Sending a LSR when an LSU was received resulted in multiple
duplicate LSRs.
CR 31035: ATM.
When disabling the ATM driver, the ATM service record remains in
an up state when it should be in a down state.
CR 32843: Telnet.
If you Telnet into the router via the ATM (LANE) port and
disconnect abnormally (physically remove Telnet client station
off the network without disconnecting Telnet), the router fails to
terminate the Telnet process.
CR 33330: Learning Bridge.
Bouncing a learning bridge interface results in a bus error when
you disable learning bridge globally. On an ARE, a Vector 2 MCP
error can occur.
CR 19135: Source Route Bridge.
An enhancement request to produce a new script called "show srb
traffic filters" that would function in the same manner as the
"show ip traffic filters" script.
CR 32240: X.25.
Call requests are always cleared if full addressing is set to OFF.
CR 33151: IPEX.
A problem exists between 11.00 and 11.02 (and later)
implementations of IPEX in which an 11.02 router cannot establish
calls with an 11.00 router. Added a new MIB parameter,
wfipexInscallingDte, in IPEX base. The default is disabled to
prevent the calling DTE address from being added, but will allow
router software version 11.02 or greater to interoperate with
lower revisions of code.
CR 33379: DLSw.
ATM Data Direct fails to establish after the ATM link is disrupted.
CR 32580: Spanning Tree.
The Spanning tree algorithm fails to converge predictably under
failure conditions.
CR 33181: RSVP.
The TSpec bucket rate, depth, and peak rate values get corrupted
when the RSVP soloist is running on an ARE processor.
CR 33653: OSPF.
The TOS and metric fields in a summary link state update are
corrupted.
CR 30499: IP.
Added new MIB variable wfBgpPeerEntry.wfBgpPeerASLoopDetect
(Default value = disabled) to determine if a Peering session should
be torn down if an AS-Loop is detected in the AS Path. In all
cases the route(s) will be marked as unusable.
Disabled = Peering will remain up.Enabled = Peering will be dropped.
CR 27239: Translation Bridge.
Enhancement request to allow packets larger than Ethernet to be
translated. The current implementation allows only packet sizes of
1500. A new MIB parameter, wfBrXbFddiBridge, was added to the
translation bridge base to allow FDDI and Token Ring size packets
to be translated. You enable this parameter only if there are no
Ethernet ports being used for translation bridge on the router. The
mode must also be set to Ethernet II, not 802.3.
CR 25171: DECnet.
The router experiences a bus error when you delete DECnet in
dynamic mode on a frame relay circuit.
CR 26560: SDLC.
Unable to establish an SNA session between a 3174 device
configured as a pu2.1 device, an SDLC attached frad630 device
connected to another frad630 device via frame relay (ban or bnn),
and an Ethernet attached host (3172).
CR 32886: DLSw.
After a PU1 controller is disconnected and reconnected to the
SDLC primary line on a router, DLSw fails to cycle properly between
disconnected and established states. After entering an
established state, the AS/400 sends an XID poll, which is
transported across to the remote controller. The remote controller
responds with an XID Final, which is transported back to the
central site, received by DLSw and by the SDLC code, but never
transmitted back to the AS/400.
CR 33853: DLSw.
The router faults when the MIB object wfDlsConnectionEntry is aged
out.
CR 33921: SDLC.
An AN router can experience a bus error fault when you set the
SDLC line to "VARY ON" on the AS400 for the remote SDLC
controllers.
CR 33922: SDLC.
An AN router may experience a bus error fault when the SDLC is set
to "VARIED OFF" on the AS400 for the remote SDLC
controllers.
CR 33806: IPX.
A problem exists where the router stops passing IPX NetBIOS
traffic in a frame relay group mode hub and spoke environment
using NetBIOS static routes with Novell Conformance disabled.
CR 33778: OSPF.
When multiple ASBRs announcing default routes in their
ASEs exist, the Technician Interface lists only one.
CR 33779: OSPF/MOSPF.
In a fail-over test involving Ethernet and FDDI, multicast
failed to take the correct path through the Ethernet after pulling
the FDDI cable. However, if you pulled the Ethernet cable instead,
multicast traffic successfully moved to the FDDI link.
CR 33056: IPX.
The router fails to apply two IPX filters of equal priority in the
order in which they appear in the route filter table.
CR 33404: APPN.
A router configured for APPN may fault with tag violations.
CR 33785: DLSw.
When you globally disable DLS, wfDls.wfDlsTotalCircuits.0
shows active DLSw connections. wfDls.wfDlsTotalCircuits.0
should be set to zero when DLS is disabled.
CR 33764: APPN.
Large topology updates may not be completely exchanged when the
sending CP is simultaneously receiving multiple updates from a
third CP.
CR 33933: APPN.
When an EN (AS/400) has a large enough number of CP-CP sessions,
the router that receives a Cross_Domain_Initiate GDS variable as a
part of ENís LOCATE message incurs a tag violation. This problem
stems from memory corruption during the allocation and release
of buffers in Session Services.
CR 33700: RSVP.
A tag violation occurred on a router running router software
version 12.00 while starting the soloist.
CR 33120: Switched Services.
A problem exists on routers running software version
11.01 and later in which the router sends ISDN call set ups
requesting the same B channel on a PRI for successive calls. This
condition occurs when attempting to establish multiple dial on
demand or dial backup circuits in a short period of time.
CR 28383: Technician Interface.
A router experiences random faults and slot resets on an ARE slot
while using the Technician Interface.
CR 34358: Technician Interface.
If you enter a year other than one between 1971 and 2070, the year
will not be set correctly on the router. The router accepts only
years between 1971 and 2070. If you use 2-digit notation, 71 through
99 becomes 1971 through 1999, and 00 through 70 becomes 2000 through
2070.
CR 33910: SYSLOG.
A bus error may occur when you telnet to a router on which SYSLOG
and WCP is enabled.
CR 33307: IPX.
Packets are not always forwarded out the direct route. This
problem can occur when an IPX route learned via RIP is also
a directly-connected route. If the route is learned through RIP
first, and the cost of the RIP-learned route is less than the
directly connected route, the directly-connected route is dropped.
CR 34135: DLSw.
Heavy SDLC traffic volume occurring on the router may result in
packet loss.
CR 34000: Firewall.
Communication between the FireWall router and the management
station will not occur properly if the firewall control gate
initializes on a slot that does not have the IP address used to
communicate from the router to the management station.
CR 32814: Technician Interface.
When you disable a terminal attached to a router running the
Technician Interface on an ARE card, the router enters the
diagnostics state and fails to exit until you reset it.
CR 28911: GAME.
If you schedule a boot for the year 2000 or later, you receive
a "Success" status message instead of a "Pending" status message.
CR 32980: GAME.
File Manager misinterprets file date stamps beyond the year 1999;
it displays the date as the year 19xx.
CR 24909: Flash.
Routers will not boot using Hitachi Maxell type flash cards.
CR 33798: HW_PROCESSOR.
The router periodically checks to verify that the I/O module
has not disconnected from the chassis by sending a signal to a
certain pin on the I/O module. Noise occurring on that pin at the
time of the check can cause the signal to be interpreted
incorrectly, causing the router to generate the following message:
# 816: 07/08/97 08:31:03.769 WARNING SLOT MODULE Code: 3
I/O module has been removed.
CR 33959: IPEX.
An enhancement request for the calling address insertion/overwrite
feature. The alarm management system used relies on the calling
address field in the incoming call to identify the device
reporting the alarm. The X.25 devices used in this network do not
fill the calling address in their calling request packets. However,
the alarm system still works because the public X.25 network
inserts the correct calling address when it receives a call
request with this field empty.
Created a new MIB variable, wfIpexMappingXlateCallingX121. When
wfIpexInsCallingDte is enabled, the calling address is
overwritten by the value specified in
wfIpexMappingXlateCallingX121, if configured.
-----------------------------------------------------------------------------
Revision 12.00/1 corrects the following problems:
Modified 12/22/97: X.25 Operational Note.
=============================================================================
No CR: X.25 Operational Note.
If you create an X.25 Service entry in dynamic mode, you must
perform one of the following operations before the X.25 VC entry
will be operational: reboot the router or reset the slot where the
newly created entry is configured.
CR 34517: IPEX.
A problem in the Gateway Mode data flow routine causes calls not to
be processed when there is no new data to process. This can cause
data transfer to stop and never re-start for one-way traffic.
CR 34518: IPEX.
A problem in the Gateway Mode data flow routine causes the TCP
window to be updated when data is stored in the data FIFO and by the
value of an uninitialized variable. The TCP window should only be
updated only when data is sent to PLP.
CR 34524: IPEX.
When IPEX detects that it received data from X.25 in out-of-sequence
order, IPEX should drop the data instead of processing it.
CR 34525: X.25.
Error in PktDATind() in x25_lirif.c causes vc_env pointer to
be tested for less than zero. Pointers are unsigned
and are never less than zero.
CR 34519: IPEX.
The IPEX FSM does not process TCP_RETRY_CONT messages in the
Established State.
CR 34520: IPEX.
The IPEX FSM does not process PLP_WIN_MSG in the Connected (CONN)
state.
CR 34526: X.25.
When booting a router with an X.25 line that is disabled, the log
message always reports that line 1 is disabled for logical lines on
an MCT1 circuit. The value 1 is not a valid line number. Line
numbers are made up of channel, type, slot, module, and connector.
CR 34521: IPEX.
An error in the IPEX Gateway Mode routine can occur when data is
sent to X.25 to test if there is PLP credit.
CR 34523: IPEX.
In IPEX FSM there is a case for IPEX_MSG_POLL_TCP
message in 4 states, but there is no code that sends that
message. Also there is no need to poll TCP. These cases
should be removed.
CR 34522: IPEX.
In ipex_pri.h there is a define statement that uses an
attribute that was deleted.
/* dynamically turn on logs through hidden mib parameter */
#define IPEX_DEBUG_LOG_ON(ipex_env) \
(ipex_env->init_env->base_rec->wfIpexMaxSlotSessions == 1111)
The MIB attribute wfIpexMaxSlotSessions does not exist. CR 33717: FDDI.
The DA30 was used to send SMT Port Management Request packets to
the router. The response packet indicated that the long term link
error rates on the ports were 10e-8 and 10e-15. The MIB indicated
the link error rate to be 10e-15 on both ports.
CR 34582: X.25.
When the VC Gate environment is created for PVCs,
the vc_state is init to X25_DATAXFR. This is
incorrect because VC is not ready to transfer data;
VC must wait for a client response message before
entering X25_DATAXFR state.
CR 34583: IPEX
When IPEX is in gateway mode and receives a reset when it
is in the CONN state, it does not verify that the cause code
is 09 (Operational) before switching to the EST state.
CR 34586: IPEX.
When IPEX receives a TCP Open request, it needs to send a
connect request to X.25. But, no check is made to see if
the needed circuit is operational. This leads to a bus error,
no lapb buffers, and other errors.
CR 34584: IPEX.
The PLP bound FIFO needs to be flushed when you get a TCP_CLOSE_MSG
in the IPEX Establish state before sending a Packet Level Reset
request to X.25.
CR 34599: X.25
You cannot configure LAPB Direct Interface-only circuits on SYNC and
MCT1 interfaces.
CR 32864: IPEX.
If a failure occurs at the remote IPEX IP interface, IPEX can no
longer establish TCP connections with the remote IPEX routers.
An enhancement to the current IPEX implementation allows you to
configure the secondary remote IP interface for backup using
the new MIB attribute wfIpexMappingRemoteBackupIp.
CR 33576: X.25.
Attempting to scale X.25 to 10 PVCs over 24 T1 logical channels
using the FRE2-040-32M causes a GAME system error. The same
error occurs when attempting to scale X.25 to 32 PVCs over 24 T1
logical channels.
CR 33871: IPEX.
Clearing inbound X.25 calls causes bus errors to occur on a
router configured with IPEX in end-to-end mode.
CR 32855: X.25.
PVC fails to come up after dynamically adding an X.25/PVC circuit.
CR 33410: IPEX.
If the X.25 client timer expires while IPEX is waiting for
a clear confirmation from the remote X.25 connection (end-to-end
mode only), X.25 will clear the call locally, causing the LCN to
be freed. However, all structures related to the virtual connection
(VC) do not get cleaned up properly. As a result, any calls placed
to this LCN will fail.
CR 34290: X.25.
When booting a router that has a configuration with a
wfLapbPktEntry that is set to Disable, X.25 restarts with
the following error message:
X25 System Error - DLRESind(), bad dlc_p pointer CR 34292: X.25.
When you set multiple wfLapPktEntry to Disable using the Technician
Interface and then enter the Commit command, the router faults in
mib_ent.c at line 726.
CR 34293: X.25.
When you disable an X.25 line, the log message reports that line 1
is disabled for logical lines on a MCT1 circuit. The value "1" is
an invalid line number. Line numbers are made up of channel, type,
slot, module, and connector.
CR 33714: IPEX.
The server process was disabled with 240 sessions running. When the
listener process was restarted and the TCP connections had
been reestablished, the server and router both showed over 280
established connections.
CR 34295: IPEX.
The IPEX FSM does not process DATA_IND messages in the connected
(CONN) state. IPEX now can go from established (EST) state to the
CONN State and back to EST state while maintaining active
X.25 connections.
CR 33712: IPEX.
A PTOP virtual circuit may stop transmitting traffic on the network.
CR 33715: IPEX.
34483:
Traffic is started over 240 sessions at 45-percent capacity.
Channel 1 is reset by toggling the wfLogicalLineDisable parameter
on bln43 (client). Each time you reenable channel 1, traffic is
restarted over it, eventually causing a bus error to occurs on the
client side router.
CR 34417: IPEX.
The IPEX audit gate checks for both a buflist and signal parameter
each time the gate is schedule. This violates GAMEís
operational model, which states that the signal parameter is valid
only when buflist is set to NULL.
CR 34418: IPEX.
After receiving credits from X.25, IPEX should check whether it
has data to send to X.25. If IPEX fails to perform this check,
data could be retained in the FIFO.
CR 34419: IPEX.
Bad code segment occurring in IPEX FSM for the VC_DIED message
while operating in an establish state.
CR 33716: IPEX.
Unable to restart IPEX client sessions on the router after
terminating them.
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
