home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!bcstec!aw108!vds7789
- From: vds7789@aw2.fsl.ca.boeing.com (Vincent D. Skahan)
- Newsgroups: comp.sys.apollo
- Subject: Re: Help Changing Network Numbers.
- Message-ID: <1992Sep10.174751.9305@aw2.fsl.ca.boeing.com>
- Date: 10 Sep 92 17:47:51 GMT
- References: <1992Sep9.231355.23063@mprgate.mpr.ca>
- Organization: none
- Lines: 55
-
- levesque@mprgate.mpr.ca (Steve Levesque) writes:
-
- >We have a network of about 25 apollo stations and I have to split them
- >into two totally seperate rings, so they don't see each other at all.
- >Because they are currently on both ethernet and token ring, we have two
- >seperate network numbers, so I will have to change the network number on
- >one of the networks back to 0.
-
- no you don't have to do that.
-
- >Reading the "Managing Domain O/S and Domain Routing in an Internet" manual,
- >it first tells me to make sure I have a slave registry somewhere on the
- >new network (network 0), and then make it the master after the split.
-
- smart.
-
- >Rather than waiting and using the slave and deleting all the uneccessary
- >accounts after the split, I used rgy_create to create a new registry,
- >and tried to make all the necessary accounts before the split.
-
- oooohhhh.
-
- >To do this I ran rgyd on the Soon To Be Master node, but didn't tell
- >any of the other machines about this new registry, and then ran edrgy,
- >and set my site to this S.T.B.M. node.
-
- >However, when I tried to add a new account or to change the properties it said:
- >"Unable to add "whatever" - Not authorized to perform operation (RGYC/Server)"
- >Even though I did this as root.
-
- if you did a 'su' to root that's possible
- do a '/com/login root' and it'll work.
-
- you might also want to try it after deleting the `node_data/.rgyloc file,
- which is kind'a like a hint_file for registries.
-
- >Also, has anybody out there changed network numbers before?
-
- sure, we do it all the time :-(
- just split a 170 node ring into 3 interconnected rings...
-
- >Does the book tell all, or are there some unwritten surprises?
-
- Maybe. The not-always-realized part is that you generally get all kinds
- of fun-with-ncs problems when you change an ATR network. You have to recreate
- the glbd database with the new network, then reboot everything so it picks up
- the new network. Also, your hint_file(s) will be all messed up, so do a
- dlf -du on it before you reboot each node.
-
- it's actually reasonably well documented if you look at it after you
- did it the first time...
- --
- --------- Vince Skahan ----------- vince@atc.boeing.com ---------
- I've finally realized that if you throw enough money and bodies
- at non-existant problems, that they really do appear...
-