[Info-vax] removing a node completely

Phillip Helbig---undress to reply helbig at astro.multiCLOTHESvax.de
Sun Feb 3 01:11:01 EST 2013


In article <kek4ef$qsh$1 at dont-email.me>, Stephen Hoffman
<seaohveh at hoffmanlabs.invalid> writes: 

> > Just to be clear, neither LANCP> LIST NODE nor SHOW NODE shows the old
> > node.  As expected, the new node shows up in SHOW NODE on the one node
> > configured as a boot server for it.  What surprises me is that LIST NODE
> > shows the new node on all nodes.  Where is the permanent LAN database
> > and how did it become cluster-wide?
> 
> If you're using DECnet MOP to boot satellites, use CLUSTER_CONFIG.  If 
> the LANCP, use CLUSTER_CONFIG_LAN.

Right, no DECnet running here, thus the latter.

> SCSSYSTEMID and SCSNODE are treated as a pair, and remembered as a 
> pair.  Once you've booted with a pair and joined a cluster, the pair is 
> remembered until the cluster is rebooted.  Get the misconfigured 
> cluster member shut down, and ensure the SCSSYSTEMID and SCSNODE pairs 
> are set uniquely.  If you want to "break" an existing SCSSYSTEMID and 
> SCSNODE pair --- as opposed to using a wholly new pair for the host --- 
> you'll have to reboot the whole cluster, as the cluster remembers all 
> of the pairs it has ever seen.

OK, not a LAN thing at all, but rather part of the "cluster memory".




More information about the Info-vax mailing list