Conference irocz::common_brouters

                ECO NUMBER:      FIXKIT1
                -----------
                PRODUCT:         Distributed Routing SW V2.0-1
                --------
                UPDATED PRODUCT: Distributed Routing SW V2.0-2
                ----------------




 haggle:/usr1/users/guest/kits:


  aw90-v202-funcIP.ldb    	! IP ONLY AW90_2S Image; Gateway Serial No. 400;
                          	! Digital Unix Checksums 24434 935;

  aw90-v202-funcMP.ldb    	! MultiProtocol AW90_2S Image; 
				  Gateway Serial No. 403;
                          	! Digital Unix Checksums 10783 1300;

  aw900-v202-funcIP.ldb   	! IP Only AW900 Image; Gateway Serial No. 394;
                          	! Digital Unix Checksums 21853 993;

  aw900-v202-funcMP.ldb   	! MultiProtocol AW900 Image; Gateway 
				  Serial No. 401;
                          	! Digital Unix Checksums 54659 1357;

  decswitch900ee-ip-v2.0.2.bin  !DECswitch 900EE ip only image, ser no 6983

  decswitch900ee-mp-v2.0.2.bin  !DECswitch 900EE multiprotocol image, 
                                 ser no 6982

  decswitch900ef-ip-v2.0.2.bin  !DECswitch 900EF ip only image, ser no 6983

  decswitch900ef-mp-v2.0.2.bin  !DECswitch 900EF multiprotocol image, 
			         ser no 6982


For:


    RouteAbout Access  EW
    RouteAbout Access  EI
    RouteAbout Central EW
    RouteAbout Central EI
    DECSwitch 900 EF
    DECSwitch 900 EE   

Fixes:

  ISDN Line activation problems 

      In certain European countries, ISDN interfaces 
      would not correctly initialize at startup, or
      would shut down after startup and not return. 
      Additionally, if the cable to the ISDN
      interface was removed the router would not be 
      able to recover when the cable was
      reinserted. 

   Bridging/DECnet repeating crashes 

      In certain configurations, where both Bridging and 
      DECnet Phase IV where configured, a
      problem would cause the router to repeatedly crash on startup. 

   Interoperability problems with Bridging over PPP to cisco/DECbrouter 

      Most releases of cisco IOS (including the 
      current release supported on the DECbrouter
      90), did not negoiate MRU on PPP links. 
      In the absence of negotiation, the RouteAbouts
      would default to an MRU of 1500 bytes. 
      This is not sufficient to carry a maximally-sized
      bridged Ethernet frame, which would be dropped. 

   Fix for non-standard X25 packet size default settings

	There is a problem when switching between networks with 
	non-standard packet size defaults. 
                                                                                
	This has proved to be a showstopper for some customers       
	but would not be seen on most networks, where the 
	standard default packet size is used.


   Fix for configuration of  'Ifspeed' for SNMP management

      For the purposes of remote management of RouteAbouts via
      SNMP, the correct 'IFspeed' attribute needs to reported
      against each interface. This value was previously defaulted
      the 1Mbyte for lease line interfaces and could not be
      modified. A fix has now been put in place to allow the user
      to modify this value via the 'SET HDLC SPEED' command.

      Note that this value is only used for SNMP reporting
      purposes and does not effect the actual interface speed
      in any way.

--------------------------------------------------------------------------------
                         Problem(s) fixed:
        
        PTR                  Reported                              Category or
ECO#    No                   Date          Reported by             Priority
================================================================================

	15327			 4 Nov 96       NSTG			S    	
	15844     		19 Nov 96       NSTG			S
	15955     		22 Nov 96       Comune di Latina	H
	16135      		 3 Dec 96	Engineering		S
	16809			23 Dec 96	Jean-Yves Peyrache	H
	16972     		 6 Jan 97	Rexel, Italtel		S

+---------------------------+ TM
|   |   |   |   |   |   |   |
| d | i | g | i | t | a | l |
|   |   |   |   |   |   |   |
+---------------------------+   INTEROFFICE  M E M O R A N D U M
                                DIGITAL/PROTEON INTERNAL USE ONLY
 
SUBJECT:  Second Common Code V2.0 (Meteor) Maintenance Release (FIXKIT2)
- ------------------------------------------------------------------------

The second Common Code V2.0 (Meteor) Maintenance Release has completed
System Test regression testing. It is intended that this release be made
available to customers at this time.

THE aw900EW-v203-func[IM]P.ldb IMAGES DO NOT RUN ON A 900 EI. This will
be corrected in the next fix kit (FIXKIT 2A) to be released shortly under
a separate announcement.

Release Notes
--------------

See http://routeabout.zko.dec.com/~tac/relnotv2.html


PTRs Fixed
- ---------
	
The following PTRs have been fixed in this release since the first
Common Code V2.0 (Meteor) Maintenance Release (decvers V2.0-2,
clearcase CC-V2.0-MAINT-B1.2) announced on 12/13/96.

15856	16321	16933	17655	17660
18158	18160	18175	18276	18658
18660	18864	18908	18987	19018



Release Images
- --------------

These images are labeled (decvers V2.0-3, ClearCase CC-V2.0-MAINT-B1.3).

The images associated with this update are accessible via anonymous ftp
on haggle in:

 haggle:/usr1/users/guest/kits:

  aw90-v203-funcIP.ldb    ! IP ONLY AW90_2S Image; Gateway Serial No. 1216;
                          ! Digital Unix Checksums 22709 934;

  aw90-v203-funcMP.ldb    ! MultiProtocol AW90_2S Image; Gateway Serial No. 1222;
                          ! Digital Unix Checksums 02178 1299;

  aw900EW-v203-funcIP.ldb ! IP Only AW900EW Image; Gateway Serial No. 1214;
                          ! Digital Unix Checksums 00019 9886;

  aw900EW-v203-funcMP.ldb ! MultiProtocol AW900EW Image; Gateway Serial No. 1223;
                          ! Digital Unix Checksums 58050 1351;

+---------------------------+ TM
|   |   |   |   |   |   |   |
| d | i | g | i | t | a | l |
|   |   |   |   |   |   |   |
+---------------------------+   INTEROFFICE  M E M O R A N D U M
                                DIGITAL/PROTEON INTERNAL USE ONLY
 
SUBJECT:  Second DECSwitch900 Maintenance Release (FIXKIT2)
-------------------------------------------------------------------------

The second DECSwitch900 Maintenance Release has completed
System Test regression testing. It is intended that this release be made
available to customers at this time.

Release Notes
--------------
   See below.


PTRs Fixed
- ---------
        
The following PTRs have been fixed in this release since 12/13/96.

   15856   16933   17655    18175
   18788   18987   19096



Release Images
- --------------

These images are labeled (decvers V2.0-3) WGE_V2.03.

The images associated with this update are accessible via anonymous ftp
on haggle in:

 haggle:/usr1/users/guest/kits:

      decswitch900ee-ip-v2.0.3.bin   ! IP only DECSwitch900 ee image;
                                     ! Serial Number 1310;      
      decswitch900ee-mp-v2.0.3.bin   ! MultiProtocol DECSwitch900 ee image;
                                     ! Serial Number 1308; 
      decswitch900ef-ip-v2.0.3.bin   ! IP only DECSwitch900 ef image;
                                     ! Serial Number 1310; 
      decswitch900ef-mp-v2.0.3.bin   ! MultiProtocol DECSwitch900 ef image;
                                     ! Serial Number 1318; 


                     DECSwitch900 Release Notes for V2.0-3

The UPDATE VERSION-OF-SRAM command has been deleted from V2.0-3 since
it was unnecessary and could cause problems.

Fixes in V2.0-3:
- --------------

BOOTP relay/DHCP problems 

     The BOOTP relay function (also used for assist DHCP functions)
     was using the incorrect IP address in relayed BOOTP packets. This
     often caused DHCP address assignment to fail on the DHCP server. 

     This problem has been fixed and is available in the V2.0.3 patch release.


     DECnet problems when Host TCP/IP Services (HST) configured 

     When DECnet Phase IV was used in conjuction with HST (i.e., with
     IP routing disabled), the router would silently discard all
     received DECnet packets. 

     This problem has been fixed and is available in the V2.0.3 patch release.


Crash in innetdwn()
     In certain circumstances, the router would crash with the following
message: 

           fatal: Bad type in innetdwn
           

     This problem has been fixed and is available in the V2.0.3 patch release.



DECnet/Bridging initialization failures 

     In certain circumstances where a DECnet Phase IV address was
     configured as well as Bridging, the router could crash on startup. 

     This problem has been fixed and is available in the V2.0.3 patch release.



Bridging/DECnet repeating crashes 

     In certain configurations, where both Bridging and DECnet Phase
     IV where configured, a problem would cause the router to
     repeatedly crash on startup. 

     This problem has been fixed and is available in thhe V2.0.3 patch
release. 

Available patches

A maintenance release (V2.0.3) is available that will incorporate
fixes to these problems. The release will be made available through
standard Digital Support channels, including the Telephone Support Centers.
Additionally, it can be made available for downloading from this
server, once you have been authorized and your software package type
(IP or MP) is determined. 

Digital, the Digital logo, and DECswitch are trademarks of
Digital Equipment Corporation. All other trademarks are properties of
their respective owners. 





[Posted by WWW Notes gateway]

    For those of us with IP access...what is HAGGLE's address and/or fully
    qualified name?
    
    thanks,
    j
    

You could always use vtx easynet to work it out...

    Mark,
    
    Not EVERYBODY always thinks of that when they are looking for things,
    nor does EVERYBODY know about that.  But complete information in a
    pointer is not appreciated...it's a requirement for completion.
    
    Digital dies because of the "oh you could just look it up..." instead
    of doing a complete job.  One of my customers said it best - "You build
    great things, but never finish them..."
    
    Complete, self contained, enabling etc., needs to be our goal to
    survive.
    j

    Jon, I took Mark's suggestion to you as a helpful "tech-tip" on 
    how to find a node, so that in the future, you could find it on your
    own rather than having to ask someone in here. You would then have
    the knowledge to perform this task yourself. U C? :-)
    
    Bob 

C:\>nslookup haggle
Server:  named.lkg.dec.com
Address:  16.20.0.10

Name:    haggle.lkg.dec.com
Address:  16.22.80.36



-John

    From a VMS node & invoking VTX easynet do the following.
    
    1. At your vms prompt type vtx easynet <cr>
    2. At the next prompt, select 3 [node registration] <cr>
    3. At the next prompt, select 2 [node registration procedure] <cr>
    4. At the next prompt, select 6 [display a node] <cr>
    5. Select "D" (for decnet) or I (for IP), type the node name & PF1 Enter
    
    You'll then get a display with information on the node you asked for,
    including the IP address, node address etc.
    
    Bob

  I am pleased to announce that clearVISN Router Configurator
  Version 2.1 has been released and is now available.

  From the 3 Jun 1997 the kits are available on Digital's Networks 
  Product Business web server and can be downloaded from the following 
  page:

        http://www.networks.digital.com/dr/crc

  or    from the home page  http://www.networks.digital.com
        under Technical Information
          then Technical Information/Data (Drivers, Manuals, Tech Tips, etc.)
            then clearVISN Router Configurator


	Internally the REO web site can be accessed from 
	http://www-engreo.reo.dec.com/ipeg/lcm


  The following list notes the major new features included in this release:

o Datalinks/Interfaces dialog revised to use Tree control and support 
  Drag and Drop, with details on property pages. 

o New datalinks supported. 
  -  PPP: PAP, CHAP and Compression. 
  -  MultiLink PPP Bundles 
  -  WAN Restoral PPP to ISDN/Dial 
  -  V.25Bis interface and Dial-up Circuits. 
  -  ISDN Interface configuration, ID Verification, and Dial Circuits 
  -  Frame Relay - over RFC1490 PVC's or point to point PPP circuits. 

o Bridging 
  -  New Bridge ports screens using tree control and extra datalinks. 
  -  Bridge Filtering (Port based) 

o IP 
  -  New IP interface screens using tree control and extra datalinks. 
  -  BGP4 Triggered RIP 
  -  RIP/SAP filtering/spoofing 
  -  OSPF Area Ranges 
  -  IP Packet Filtering 

o OSI/DECnet 
  -  New DECnet interface screens using tree control and extra datalinks. 

o IPX 
  -  New IPX interface screens using tree control and extra datalinks. 

o General 
  -  Dump File configuration/specification 

o Application 
  -  Full support for RouteAbout Access + Central EI 
  -  BootP table viewer, and editor. 



Best wishes,

  Mike Chapman 

clearVISN Router Configurator,  Project Leader.
Digital Equipment Corporation

>        Internally the REO web site can be accessed from 
>
>        http://www-engreo.reo.dec.com/ipeg/lcm

and you get a nice EMPTY page!

the internal web site (checked non-empty) is

http://npbwww.hpn.lkg.dec.com/dr/crc/

Cheers,

Pedro
[Posted by WWW Notes gateway]

RE: 6.37

>and you get a nice EMPTY page!
>the internal web site (checked non-empty) is
>
>http://npbwww.hpn.lkg.dec.com/dr/crc/
>

This was a Netscape specific "feature" There was a comment delimiter 
that was not being handled the same way as MS IE - which turned the
html content into an invisible comment !

I have removed the offending syntax and it seems to work now with Netscape.

Regards
	Mike Chapman

    re: .33
    
    Having dealt with ALL of that for a number of years it only works if
    the node is actually cross-registered correctly.  A DECnet name does
    not always correlate to an IP name - it's nice if it does.
    
    Yes, you can do NSlookup etc., however, the point is, please post
    complete info AND put it on the web.  We now have folks in Digital
    who have *NO* VMS system access nor any UNIX prompt access etc.  Their
    only tool is the PC.  (i.e. my new system engineer who I'm orienting)
    
    Having to lookup systems, figure out which rock things are under etc.
    is not a sustainable way of doing biz.  uc?
    j

    Jon, nslookup works just fine on your average PC configured with
    WinNT, so you don't need a UNIX box to invoke nslookup.
    
    
    Bob