🚀 go-pugleaf

In article <01bc1e7c$92c519e0$87deaec7@gpaoadmin>, "Etienne Lacour" <100520.465@compuserve.com> writes:
|Help,
|I would like to know how to change the node number of a VAX-station under
|DECNET.
|
|My configuration is two net (DECNet) linking two VAX Station via two
|DECServer and i want to
|link the two network, but i have a problem of conflict between the node
|number of the stations.
|
|Old configuration - It's work
|net A : |1.1|----|1.2|----|1.3| 
|net B : |1.1|----|1.2|----|1.3|
|
|The new :
|          net A         new           net B
||1.1|----|1.2|----|1.3| ----- |1.1|----|1.2|----|1.3| == Conflict
|
|
|(The VMS version is VMS 5.5)

$ MCR NCP SET EXEC STATE OFF
$ @SYS$MANAGER:NETCONFIG
[ answer the questions ]
$ @SYS$MANAGER:STARTNET

Aaron

Aaron Leonard           aaron@cisco.com                 [ work ]        
                        Aaron@Leonard.Tucson.AZ.US      [ home ]

In article <5eflqb$ve4$2@mate.kjsl.com>, I wrote:

||I would like to know how to change the node number of a VAX-station under
||DECNET.
[ ... ]

|$ MCR NCP SET EXEC STATE OFF
|$ @SYS$MANAGER:NETCONFIG
|[ answer the questions ]
|$ @SYS$MANAGER:STARTNET

Someone pointed out to me that you would want to change the value
of the SCSSYSTEMID SYSGEN parameter to match the new DECnet address
- see 
$ MCR SYSGEN HELP PARAM SCSSYSTEMID 
for details.

Aaron

Etienne Lacour wrote:
> 
> Help,
> I would like to know how to change the node number of a VAX-station under
> DECNET.
> 
> My configuration is two net (DECNet) linking two VAX Station via two
> DECServer and i want to
> link the two network, but i have a problem of conflict between the node
> number of the stations.
> 
> Old configuration - It's work
> net A : |1.1|----|1.2|----|1.3|
> net B : |1.1|----|1.2|----|1.3|
> 
> The new :
>           net A         new           net B
> |1.1|----|1.2|----|1.3| ----- |1.1|----|1.2|----|1.3| == Conflict
> 
> (The VMS version is VMS 5.5)

I think what you really need to do is configure your network as follows:

The new :
          net A         new           net B
 |1.1|----|1.2|----|1.3| ----- |2.1|----|2.2|----|2.3| == (No)Conflict?

I would do some DECNET "RTFMing" to find out how to set this up if I
were you.

regards,
-- 
Kevin M. McGrath Sr.		kmcgrath@bug.com - work
(AKA MAXimum JETfan)		kmcgrath@prodigy.net - home
Old Mill Basin			Brooklyn, New York

Hi,

This is a relatively common problem when networks grow and all nodes aren't
given unique names up front allowing for future expansion. Most people
start from node 1.1 and go upwards on each network they set up. The
solution's mostly dependant on the likely future number of nodes and the
physical layout of where the LAN segments are. The easy case (which I
assume and hope this is) is that everything's in one building and there are
no more than 40-50 nodes on the network at most. In that case just set it
all up in one area (1.1 ... 1.6 for example, although I'd probably start at
say 1.100 and move up in say blocks of 10 allowing space for other nodes in
the future). It will work better if at least 1 of the nodes (preferably 2
for resilience) is set up as a Level 1 router to tell other nodes whether
existing nodes are on the network or not. If there's no router then you'll
just get long timeouts when you try to access a dead node. If you decide to
run multiple areas (only really worth it with multiple sites and several
nodes at each site with low bandwidth links between the sites) then you
need a Level 2 router (or 2 for resilience) to let the area 1 nodes be able
to find the area 2 nodes even though they're on the same LAN segment. All
this routing gets a lot more interesting if you move to DECnet/OSI - my
advice is stick with the simple case of everything in the same area!
Reconfiguring the address is simple - just plug the new address into
SCSNODEID (1024*area + number, 1025 = 1.1) and the new name into
SCSNODENAME using MODPARAMS.DAT, then AUTOGEN to the SETPARAMS stage. Also
define the NCP EXEC NODE to the new address and the NCP EXEC NAME to the
new name. Then reboot. Assuming you've fully conditionalised all your
startup code and used the lexical functions to find nodenames you should be
up and running. If you're a cluster beware of licence PAK include=nodename
pitfalls as VMS could fail to load licences.

I'm not sure what all this has to do with DECmcc, however I've not used
this newsgroup before and don't know what to do about things like that.
Maybe whoever moderates it will quietly mail me direct to put me right
please! Internet explorer doesn't do a good job of displaying the full
newsgroup name, so the decmcc part isn't actually visible.

Hope this helps. Colin.