[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Digital Brouters Conference |
Notice: | New common-code brouter family: RouteAbout, DECswitch 900 |
Moderator: | MARVIN::HART LL |
|
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 |
838.0. "Area Routing Issue DECNIS - EF900/MP" by UTOPIE::BERG_W () Mon Apr 07 1997 06:28
Hello
This note was also cross posted to the DECnis conference.
Are there some known problems by upgrading a DECnis 600 from Vers.2.2-18 to
V3.1 and then to V3.1-9 and DECSWITCH900EF/MP (V2.0-2).
My customer did this upgrade. After the SW-upgrade he also included a MPC-II
in his NIS (and loaded with the renamed NIS031b.sys image).
After the upgrade it was not possible to connect to other area's as it worked
before.
Config:
Area10 -----EF900/MP(V2.0)--FDDI--EF900(Switch only)----DECNIS600---Area48
10.1005 48.45
Both routers should route DECnet Routing Vector at L1, and Linkstate at L2.
All other protocols will be bridged.
Adjacencies from the other router are seen, but no data will be transmitted
from Aera 10 to Area 48.
At the moment everything works again, because he downgraded again (using the
config from 3.1-9) and inserted the MPC-I.
For test purposes i tried to setup a Routeabout Access EW (no EF900 in our
office at the moment) with the same configuration steps our customer did.
But the one difference i saw is
*t 5
+P OSI
OSI>DNAV-Info
DNAV Level 1 Routing Algorithm: LINK_STATE !!configured as Routing_Vector ??
DNAV Level 2 Routing Algorithm: LINK_STATE
OSI>
Any help will be highly appreciated.
Thanks Wolfgang
=========================================================
P.S.
There are the configuration steps the customer did on his DECswitch900EF/MP.
To be able to communicate with the offline - environment, which
operates in DECnet area 48, a Level 2 Router has to manage the data traffic:
Here a short configuration list to illuminate the DECnet data path:
machine decnet type address
-------------------------------------------------------------------------------
TSFS OSI Endnode (cluster alias !!!) 48.900
FSH1R7 DECswitch 900EF multiprotocol brouter, OSI L2 Router 10.1005
FTSTR2 DECnis 600, OSI L2 & L1 Router 48.45
BP1VAS DECnet Phase IV L1 Router 48.13
The name FSH1R7 means: Fvkz Sfs Hub 1 Router (in Slot) 7
* * * * * *
this is the way to setup the DECswitch 900EF / MP (from scratch)
================================================================
open a telnet connection to 193.80.152.42 (DECswitch900's address)
*T 6
Config>BOOT
Boot config>LOAD REMOTE
load host is Hubwatch PC (193.80.152.101)
load filename is C:\HUBFIRM\DS9Vnnn.BIN
you can see that the TFTP server on hubwatch PC starts counting
the loaded packets
-------------------
setup DECswitch OSI
open a telnet connection to DECswitch
*T 6
Config>P OSI
OSI Config>set net
49000a (49::00-0A, DECnet Phase IV area 10)
aa000400ed2b (10.1005 - DECnet compatible address)
OSI Config> enable osi
OSI Config> set algorithm
Level 1 : DISTANCE_VECTOR
Level 2 : LINK_STATE
OSI Config> set subnet 0 LAN (FDDI - interface)
ES-IS : no
IS-IS : yes
L2 only : no
rest of questions default
OSI Config> set subnet 6 LAN (AUI - interface 7)
ES-IS : yes
IS-IS : yes
L2 only : no
rest of questions default
OSI Config> exit
Config><control-P>
*RESTART
-------------------
setup DECswitch transparent bridging
open a telnet connection to DECswitch
*T 6
Config>P ASRT
ASRT Config>enable bridge
ASRT Config>exit
Config><control-P>
*RESTART
-------------------
setup DECswitch IP - Host mode (IP bridging)
open a telnet connection to DECswitch
*T 6
Config>clear IP (remove IP routing parameters)
Config>P HST
TCP/IP-Host config>SET IP
193.80.152.42
255.255.255.0
TCP/IP-Host config>ADD DEF
193.80.152.127
TCP/IP-Host config>exit
Config><control-P>
*RESTART
T.R | Title | User | Personal Name | Date | Lines
|
---|