| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
G'day Friends, DECers and ALL-IN-1ers :-),
A customer has upgraded to our latest and greatest VAXen a 7000
machine, which will no doubt be upgraded to an Alpha when ALL-IN-1 is
ported. This has replaced a cluster of VAXens.
The customer wants to update the NETWORK.DAT and replace the cluster
alias name with the nodename, on an ALL-IN-1 3.0-1 system. My first
thoughts on a procedure to do this is as follows:
1. MC NCP CLEAR EXEC ALIAS
2. Deassign the logical SYS$CLUSTER_NODE
3. Ensure that SYS$NODE is defined
4. Rename the OA$DATA:NETWORK.DAT to *.OLD
5. Create/fdl=oa$lib:network oa$data:network.dat
6. Enter ALLIN1/USER=MANAGER
7. <do smnetinit
8. Submit the housekeeping routine UA
This is all to be done when no is using ALL-IN-1 IOS. I would be
grateful if someone could advise me if the above steps are correct.
Have I missed anything out ?
Regards,
Sunil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2801.1 | What about? | AIMTEC::WICKS_A | June 7-13 Real Football in the U.S | Fri Jun 04 1993 17:23 | 7 |
Sunil,
Anything about the FCS and drawer/pertition stuff?
Regards,
Andrew.D.Wicks
| |||||
| 2801.2 | Assuming DECnet naming of course, DNS changes things | CHRLIE::HUSTON | Fri Jun 04 1993 17:56 | 17 | |
though I am not really sure on what .0 is trying to do, I don't
see any FCS problem.
The FCS does not know anything about network.dat, if he is simply
removing the cluster alias and making it a node name, then he would
need to restart the FCS to get the cluster alias out of the
cache and to update the node names of the cluster members.
The only other possible catch is that if some user has a node name
in their filecab.dat instead of 0::, then if that node name goes
away, the next attempted access to that drawer would fail. Or he
may also suddenly "loose" the drawer. it would be there but I
believe ignored by IOS when you do an index of your drawers.
--Bob
| |||||