| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2525.1 | Some info | NETCAD::FORINO | | Mon Jul 17 1995 10:11 | 13 |
| Looks like you need a router in there. Depending on your configuration
and the protocols you need your options are the just announced
RouteAbout Access EW (1 Ethernet and 2 T1 WAN ports)
DECswitch 900EE (6 Ethernet ports)
DECswitch 900EF (1 FDDI and 6 Ethernet ports)
plus some routers that have been out there for a while
DECwanrouter 90 (1 Ethernet and 2 64K WAN ports)
DECbrouter 90 (a few different setups)
Check the appropriate notes conferences for more information.
|
| 2525.2 | All nodes on the same wire. | DPDMAI::WISEE | Pobodys Nerfect | Mon Jul 17 1995 12:15 | 5 |
| Will the products in .1 work if all the systems are on the same LAN?
Efw
p.s. Still can't get them to turn on one node as a full function node.
|
| 2525.3 | Protocols | NETCAD::FORINO | | Mon Jul 17 1995 14:26 | 1 |
| What protocols are you talking about here - IP, DECnet IV, DECnet OSI?
|
| 2525.4 | DECnet Phase V only | DPDMAI::WISEE | Pobodys Nerfect | Mon Jul 17 1995 15:13 | 7 |
| Pathworks using Phase V DECnet only.
I was able to prove to them that turning on routing on the VAX would
fix the problem ... Buuttt... No department or user is willing to let
their VAX be the one to LOOSE the "Horsepower".
So it's back to the router.
|
| 2525.5 | go ask the decnet folks | TOOK::MILLBRANDT | | Mon Jul 17 1995 16:37 | 13 |
| DECnet Phase V does not support host-based routing. Loading
the 'full-function' license gets you cluster support, and
some higher-level OSI things.
If all the systems from both areas are on the same lan,
they should be able to see each other. I haven't dealt
with DECnet-OSI for a couple of years though, and it
gets fuzzy!
See notes conference HELP::DECnet-OSI_for_VMS for better
info than we can give you here.
Dotsie
|
| 2525.6 | I guess I need to check the DECnet folks too ... | MSDOA::REED | John Reed @CBO = Network Services | Mon Jul 17 1995 19:34 | 17 |
| I would be careful about the choice of router. I am trying to get my
WANrouter 90EW to speak with it's load host. I loaded a local PC with
the DECROU DECnet/OSI load host kit, and ran NETSET.
I can download the router using MOP, and the router requests a load,
and gets the software, but the WANrouter 90EW set up for DECnet IV
level 1 routing cannot see my PC, unless my PC is in the same DECnet
area (4.x in my case). I don't want to have a different AREA router
(level 1 and level 2) for each building, just because I have more than 1024
PC's in one site.
I ended up giving the routers all the same area, and running level 1
and 2 routing for Phase IV only. Perhaps I should enable Phase V
routing?
JR
|
| 2525.7 | you're confusing inter and intra area routing | TLSE01::SELLES | Pierre-Jean - Toulouse -France | Fri Jul 21 1995 13:21 | 40 |
|
just as mentionned in reply .5 , on a LAN , with NO routers ,
any Phase IV node can see each other , even with different
area numbers . If you have some problems with your VAX server regarding
this fact , i guess it is a local cache problem or pathworks tables sizing
Beware that a PC can only talk phase IV ( not phase V ) ,
so i guess your VAX is configured as "PHase IV compatible address "
with a phase IV area address ,
even with phase V installed ( phase V = phase IV + OSI stack - routing )
>> but the WANrouter 90EW set up for DECnet IV
>> level 1 routing cannot see my PC, unless my PC is in the same DECnet
>> area (4.x in my case).
of course ; in Decnet phase IV , a level 1 router can only talk with End node ( your PC )
configured in its area : this is "inter-area"
>>I don't want to have a different AREA router
>> (level 1 and level 2) for each building, just because I have more than 1024
>> PC's in one site.
you should !! one area router ( or level 2 router ) for each area :
this is "intra-area "
of course , to optimize your LAN bandwidth , you should
separate each area physically : i guess Decswitch 900EE or EF with
new routing code should do it for you : with Dechub900 powerful distribution
of "VLAN"s and Hubwatch , it 's a pleasure to configure all this
>> I ended up giving the routers all the same area, and running level 1
>> and 2 routing for Phase IV only. Perhaps I should enable Phase V
>> routing?
you really are in a phase IV situation with all those PCs
|
| 2525.8 | .0 Resolved | DPDMAI::WISEE | Pobodys Nerfect | Wed Aug 02 1995 12:08 | 35 |
|
This issue was resolved last night...
Background....
PC PC PC
1.33 3.11 1.13
PW V5.0 PW V5.0 PW V5.0
WFW 3.11a W 3.1 W 3.1
| | |
DEChub900 DEChub900 DEChub900
Repeater 900TM Repeater 900TM Repeater 900TM
| | |
|----------------------------------------| |-------------------|
| | | |
DEChub 900 DEChub 900 DEChub900 DEChub900
Repeater 900TM Repeater 900TM DECswitch 900EF DECswitch 900MX
VAX 3100 VAX 3100 \_______________________/
1.1022 1.1021 FDDI
Level 1 Level 1
{{Level 2}} {{Level 2}}
{{ 3.1022}}
Before the Routing level and Node number changes 3.* systems could not talk
to 1.* systems. When changes were made, in {{ }}'s, the system works fine.
The only strange thing about this is is we changed the 1.1022 to Level 2 and
the network went to its knees. We then put it back to a level 1 and changed
1.1021 to 3.1022 and a level 2, then made 1.1022 a level 2 and everything
worked fine !?!?
Efw
|