Conference irocz::common_brouters

758.0. "DRS V2 FIXKIT1 available (V2.0-2)" by MARVIN::BANAS () Fri Feb 14 1997 08:34

                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

Where can I find more info on the problems fixed by this fix kit?
I search the IPMT WWW for the PTR's but it does not seem to know about them.

The fix I'm particularly interested is :

   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. 


Thanks
Dennis

    Hi,
    
    on node haggle we find  .ldb  .ldc and .bin  loadfiles.
    What's the difference?
    
    
    Thanks
    
    Birgit Blasch                                
    Digital Service Center Munich

>Where can I find more info on the problems fixed by this fix kit?
>I search the IPMT WWW for the PTR's but it does not seem to know about them.
    
    I'm not sure what you searched, but that problem was discovered by the
    Router Configurator developers, and hence was not an IPMT case.  There
    is a PTR for it, as for all bugs found.  Where you searching the
    internal PTR database?
    
    I'm not sure of the number offhand, but I could find it if you really
    need it.
    
    Tim
       

    
>    on node haggle we find  .ldb  .ldc and .bin  loadfiles.
>    What's the difference?
    
    .bin files are for manufacturing only, in the case of RouteAbouts. 
    They are an uncompressed 'image' of the binary pattern to blasted into
    flash.  Only the diagnostics in the boot block understand this format.
    
    .ldb files are for general use.  They are compressed for a variety of
    reasons.  This format is understood by the 'reload' and 'load remote'
    functions, the boot PROM on the RouteAbout Access EW/EI, and the
    diagnostics of the RouteAbout Centrals.
    
    .ldc files are for the RouteAbout Access ET only, I think.  It is
    essentially the same as the ldb format.

RE: .3

Thanks for the reply. Where is the PTR database? Is it accessible for CSC to
browse? I searched this conference for a pointer but couldn't or didn't find
anything.

Dennis

    PTR is the replacement for the old QAR system.  We use it to track
    internal and field-test reported problems.
    
    PTR is at:
    
    http://engptr.zko.dec.com:8030/~ptr_docs/ptr_login.html
    
    you'd have to ask the administrators what the access rules are, etc...
    
    Tim