| Since resources are limited, we do not have the time to generate a "formal"
(installable) fix kit containing the latest set of fixes for all of the host
platforms. Consequently we have decided to generate the latest set of
router images along with some release notes detailing the problems that have
been fixed since ECO01.
Since the images are load-host independent they can simply be copied to the
load-host as required. For those users not running V1.3.3, they should
install ECO01 (see .0) and then upgrade by copying these latest images. For
those users running V1.3.3, they can simply copy the latest images.
The images and notes can be found at:
MARVIN::CBN$KITS:[VR2013.FIX_KITS.V135]
Directory MARVIN""::CBN$KITS_ROOT:[VR2013.FIX_KITS.V135]
FIX_NOTES.PS;1 97 12-FEB-1997 11:32:05.00
FIX_NOTES.TXT;1 21 12-FEB-1997 11:29:52.00
VR22013.SYS;1 4710 6-FEB-1997 13:36:03.00 - WR250
VR29013.SYS;1 4870 6-FEB-1997 13:33:57.00 - WR90
VR29F013.SYS;1 3172 6-FEB-1997 13:35:19.00 - WR90EW
Total of 5 files, 12870 blocks.
The router identifies itself as "V1.3.5".
Enjoy,
Your WANrouter 90/250 support team.
|
|
DEC WANrouter 90/250 V1.3
Update Kit Notes
Kit Reference Number : V1.3.5
11-February-1997
_________________
While Digital believes the information in this publication is
correct as of the date of publication, it is subject to change
without notice.
Possession, use, or copying of the software described in this
documentation is authorized only pursuant to a valid written
license from Digital or an authorized sublicensor.
Digital Equipment Corporation makes no representations that the
use of its products in the manner described in this publication
will not infringe on existing or future patent rights, nor
do the descriptions contained in this publication imply the
granting of licenses to make, use, or sell equipment or software
in accordance with the description.
_________________
__________
Copyright �1997
All other trademarks and registered trademarks are the property
of their respective holders.
Permission to use, copy and modify the software and its doc-
umentation is granted provided that this copyright notice and
these terms shall appear in all copies of the software and its
supporting documentation. The origin of this software may not be
misrepresented, either by explicit claim or by omission.
The Software is provided "AS IS" and without any express or
implied warranties, including but not limited to, the implied
warranties of merchantability and fitness for a particular
purpose.
CONTENTS
Chapter 1 INTRODUCTION................................... 3
Chapter 2 PROBLEMS FIXED BY THIS RELEASE................. 5
2.1 SNMP returning invalid ipAdEntIfIndex values....... 5
2.2 X.25 Originally Called Address facility............ 5
2.3 X.25 sending oversized packets..................... 5
2.4 WANrouter 90EW not detecting change in modem
signals............................................ 5
2.5 IP multicast message crash......................... 5
2.6 Unusual NSAP address crash......................... 5
2.7 Problems clearing an X.25 SVC...................... 6
2.8 Problems with PhaseIV DLM circuits................. 6
2.9 Corrupt Phase IV routing vector crash.............. 6
2.10 Incorrect Designated Router election.............. 6
2.11 Crash with more than 150 prefixes................. 6
2.12 Unmanageable attributes........................... 6
2.13 WANrouter 250 MOP load failure.................... 7
2.14 Reachable Address with incorrect attributes....... 7
2.15 Multiple PhaseIV Init messages.................... 7
iii
DEC WANrouter 90/250 V1.3 Update Kit Notes
This information describes the problems in the software that are
corrected by this kit.
This document is intended for use with DEC WANrouter 90/250 V1.3
software.
1
CHAPTER 1
INTRODUCTION
This is a maintenance release for the DEC WANrouter 90/250 V1.3
product. It is identified as V1.3.5. This version supersedes all
other versions of this software.
After installing the update kit all WANrouter systems which
require updating with the latest image must be rebooted.
Introduction 3
CHAPTER 2
PROBLEMS FIXED BY THIS RELEASE
2.1 SNMP returning invalid ipAdEntIfIndex values
SNMP get requests on the ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex
and ip.ipRoutingTable.ipRoute.ipRouteIfIndex variables would
sometimes return incorrect (out of range) values. This problem
has now been fixed.
2.2 X.25 Originally Called Address facility
The X.25 "Originally Called Address" facility was not being
parsed correctly, resulting in calls being cleared. The facility
is now parsed correctly.
2.3 X.25 sending oversized packets
If an IP packet was fragmented and forwarded out over a X.25
routing circuit (Static or DA), X.25 would occasionally produce
a packet that was greater that the negotiated maximum packet
size. This problem has now been fixed.
2.4 WANrouter 90EW not detecting change in modem signals
On the WANrouter 90EW, changes in the CTS & DCD modem signals
were not being detected. Thus if a cable was removed, IP routing
would fail to detect the change in circuit state and continue to
announce routes as reachable through that circuit. This has now
been fixed.
2.5 IP multicast message crash
Certain types of IP multicast messages would not get correctly
processed and would subsequently cause the router to crash. This
problem has now been fixed.
2.6 Unusual NSAP address crash
The router would crash if it attempted to forward, via Level 2
routing, a packet with a destination address of the form:
3700000000000000:loc-area:id:ss
Where loc-area was of the form "00-aa". This problem has been
fixed.
Problems fixed by this release 5
2.7 Problems clearing an X.25 SVC
Under certain conditions the router would crash when an X.25
SVC, used by an X.25 static routing circuit, was cleared.
If the Update Process was about to generate an update packet,
eg. a routing vector, and the SVC was cleared, the system would
crash. Alternatively if both ends of an X.25 routing circuit
simultaneously cleared the supporting SVC, the system would
crash.
Both these problems have been fixed.
2.8 Problems with PhaseIV DLM circuits
If the underlying X.25 negotiated packet size was less that 256,
the router would crash whilst attempting to initialise an X.25
routing circuit to a Phase IV system. This problem has now been
fixed.
2.9 Corrupt Phase IV routing vector crash
On receipt of a corrupt PhaseIV routing vector, the PhaseIV
update process would attempt take down the associated (point-to-
point) adjacency. In doing so the system would crash. The system
does not now take down the adjacency, instead it logs an event
("Corrupted PhaseIV Routing Packet Received") and increments a
counter ("Corrupted LSPs Received")
2.10 Incorrect Designated Router election
Under certain conditions following a system boot, a router would
fail to correctly elect the LAN Level 1/2 designated router. The
problem has now been fixed.
2.11 Crash with more than 150 prefixes
Part of the Level 2 forwarding database was incorrectly sized
(part of the database was too small), thus the router would
only support just less than 150 Level 2 forwarding entries.
Any attempt to generate more forwarding entries would cause the
system to crash. This has now been fixed.
2.12 Unmanageable attributes
Any attempt to set one or more of the following management
characteristic attributes from within the script would fail. The
system would always come up with the default value associated
with the characteristic.
o "Network Protocols" on a PPP circuit;
o "Maximum Call Setup Timer" on a Modem Connect Line;
6 Problems fixed by this release
o "Retransmit Timer" on a DDCMP Link;
All these problems have been fixed.
2.13 WANrouter 250 MOP load failure
If the WANrouter 250 should receive a "bad" MOP message whilst
attempting to load its script, the system would hang. The image
would load successfully by the script would never complete.
This problem has now been fixed.
2.14 Reachable Address with incorrect attributes
The set of characteristics associated with a Reachable Address
entity on an X.25 Static Routing circuit was incorrect. This has
now been fixed.
2.15 Multiple PhaseIV Init messages
With a PhaseIV point-to-point circuit (DDCMP or X.25 Static), if
the router receives an invalid sequence of control messages,
for example back-to-back "Init" messages, the router would
eventually crash.
This problem has now been fixed.
Problems fixed by this release 7
|