[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irocz::common_brouters

Title:Digital Brouters Conference
Notice:New common-code brouter family: RouteAbout, DECswitch 900
Moderator:MARVIN::HARTLL
Created:Mon Jul 17 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:929
Total number of notes:3736

890.0. "DEC-AREA=IV Router ?" by PRSSOS::PEYRACHE (Jean-Yves Peyrache Country Support Group France) Tue May 06 1997 14:47

    
      hi,
    
    
     what is exactly the meaning of "DEC-AREA" on executor
     under DN protocol configuration ?
     if the executor is set to this option
     should Routeabout send level 2 Routing update  IV compatible
    
    
     thanks in advance
    
    
     JYP
T.RTitleUserPersonal
Name
DateLines
890.1MARVIN::WALTERWed May 07 1997 06:4121
    
>     what is exactly the meaning of "DEC-AREA" on executor
>     under DN protocol configuration ?

	As you know from previous discussions, the "DEC-" part selects
	whether the software supports DNA or Proteon style X,25 circuits
	for DECnet *and* OSI. The "AREA" part is as for the standard DECnet
	routing types, that is, it turns on Level 2 routing if the router
	is using Distance Vector routing ( but this must be compatible
	with anything you set via OSI config).


>     if the executor is set to this option
>     should Routeabout send level 2 Routing update  IV compatible
    
	If you are using DN (DECnet Phase IV) only, then yes.

	If you want OSI/Phase V and DNA X.25 style circuits, then you must run
	Link State at L1 and L2, and directly connected routers must also be
	Link State routers. This is a restriction. 
	
890.2CLPR01::PEYRACHEJean-Yves Peyrache Country Support Group FranceWed May 07 1997 12:0223
  Walter 


 


 Thanks for this explanation, it's really unclear because
 all other DEC routers  products (Wanrouter90,Decnis)can be level 2
 for DECnet IV and OSI simultanously, it's really important during
  migration phase from IV to OSI to have this kind of Function on the BOX
 (cisco does it..)


    >>If you want OSI/Phase V and DNA X.25 style circuits, then you must run
    >>Link State at L1 and L2, and directly connected routers must also be
    >>Link State routers. This is a restriction

should be leave in future version ?

thanks

JYP
890.3ATYV00::CARRAYROUWed May 07 1997 14:4324
    
    The complete configuration checked with J-Yves is discribe in 
    note  880.1 .
    
    The real question is : 
    
    Can we use DN and OSI at the time with different algorithm at level 1
    and level 2. 
    
    if yes 
    
    In this case the level 2 router must inform all level 1 router in 
    this area with a common algorithm , I am area router for your area.
    
    
    note 880.0 and .2 
    it seems there is a problem in pure phase IV mode only . 
    
    if not
    
    this is an other restriction and the routeabout will be unusable 
    during all transitions phaseIV -> phaseV.
    
    In the phase V spec ,  does the doc discribe the 
890.4MARVIN::WALTERThu May 08 1997 08:589
>    The real question is : 
    
>    Can we use DN and OSI at the time with different algorithm at level 1
>    and level 2. 
    
	Not if you want to use DECnet over X.25 with DA/Static style
	connections. It has to be Link State at L1 and L2.

	Otherwise, yes.
890.5"DECnet IV / OSI" compatibility specification.ATYV00::CARRAYROUMon May 12 1997 05:4621
    Yes , I know in our case all X.25 router use L1/LSP and L2/LSP . 
    
    We respect the X.25 limitation describe in the SPD by adding an extra
    area on the same LAN.
    
    During the migration only a pur LAN area Router use L1/RVR and L2/LSP .
    This router saw the network correctly.
    
    The real questions were : 
    
    Is it normal the old phase IV L1 router (X25router or VAX) does not
    see the reachability of the own area ?????? 
    
    Is it normal the AW90 L1/RVR L2/LSP does not send correct area information
    to the L1 router.
    
    Wanrouter and DECnis works fine . Does the routeabout doesn't follow
    the same "DECnet IV / OSI" compatibility specification.
    
    Didier
         
890.6MARVIN::WALTERMon May 12 1997 07:454
	Assuming you are using the configuration described in 880.1, then
	you are certainly going to run into the problem discussed in 880.0
	and 880.2. This is a bug that needs fixing, so please raise an
	IPMT.