Revision Notes for Router v11.00 rev 2
============================================================================
TE MANAGER COMPATIBILITY
=============================================================================
Router Version is managed by Site Manager version
v11.00 revision 1 --------------------------> V5.00, 5.00 rev 1
v11.00 revision 2 --------------------------> V5.00, 5.00 rev 1
------------------------------------------------------------------------------
Revision 11.00/2 corrects the following problems:
==============================================================================
CR 26996: DLSw.
When using TCP to establish multiple TCP connections
(50 plus) using DLSw 1795 mode, the router occasionally ignores
the CAPX response, causing the TCP peer connection to use
1434 mode.
CR 26702: LAPB.
Added a third option (activeDisc) to the MIB object
wfLapbEntry.wfLapbActionInitiate to enable LAPB to send a DISC
command as the initial frame after establishing a physical
connection to non-X.25 compliant IBM 5394 and 5294 controllers.
You can configure this option from Site Manager or from the
Technician Interface. From Site Manager, set "Initiate Link Setup
Action" on LAPB screen to ACTIVE DISC. From the Technician
Interface, set the MIB object
wfLapbEntry.wfLapbActionInitiate to 3 (activeDisc).
CR 27012: IP.
Running an unnumbered IP interface on a PPP line with Circuitless IP
configured as the associated address caused the router to fault
when IPCP becomes active.
CR 27023: SDLC.
When you attempt to boot an SDLC session, a full connection is
never established and the session eventually disconnects.
CR 27064: TCP.
When trying to establish a DLSw connection to an IBM 2210 router,
the Bay Networks router receives a DLSw CAPx message from
the IBM router, but fails to send a message back to the IBM router.
CR 26654: DLSw.
A TCP connection in 11.0 rel was consuming more memory than
required.
The following is a known anomaly associated with rev/11.00/2 software:
-----------------------------------------------------------------------------
Anomaly: SNA session connects but fails to transmit data
Number: N/A
Description: In a dual switch environment where SDLC is configured
on a Token Ring host or Ethernet host, an SNA session
connects but fails to transmit data. This problem
can be attributed to a flow control problem tied to the SDLC
1795 code.
Workaround: Bouncing the synchronous line on a router that is
connected to the SDLC station will establish a
connection to the SNA session and permit the
transmission of data.
------------------------------------------------------------------------------
=============================================================================
Revision 11.00/1 corrects the following problem:
==============================================================================
NOTE: Revision 11.00/1 is managed by rel/5.00 and/or revision 5.00/1.
Revision 5.00/1 is necessary to properly manage the new MIB attribute
in revision 11.00/1, but otherwise rel/5.00 will work as usual.
-----------------------------------------------------------------------------
CR 26702: LAPB.
Added a third option (activeDisc) to the MIB object
wfLapbEntry.wfLapbActionInitiate to enable LAPB to send a DISC
command as the initial frame after establishing a physical
connection to non-X.25 compliant IBM 5394 and 5294 controllers.
You can configure this option from Site Manager or from the
Technician Interface. From Site Manager, set "Initiate Link Setup
Action" on LAPB screen to ACTIVE DISC. From the Technician
Interface, set the MIB object
wfLapbEntry.wfLapbActionInitiate to 3 (activeDisc).
at

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