If you define the mac address and set the chain table so xCAT will not try to
"do" anything with the node:
chdef {NODE} currstate=boot currchain=boot chain=boot
nodeset {NODE} boot
You probably don't need all of those chain table settings, but that should
catch everything. This way, the DHCP server will not attempt to discover or
install when a PXE request is received.
Regards,
Christian Caruthers
Lenovo Professional Services
Mobile: 757-289-9872
From: Casandra H Qiu <[email protected]>
Sent: Wednesday, November 28, 2018 15:12
To: xCAT Users Mailing list <[email protected]>
Subject: [External] Re: [xcat-user] Excluding a node from discovery?
If mac address defined, DHCP server already knows this node. bmcdiscover will
not send genesis kernel , but the node attribute will be replaced from discover
packet if there are difference.
For the mtms-based discover, the bmcdiscover will send findme packet and
looking for per-definied node with same mtm/serial. Yes, if it didn't find,
that would cause bmcdiscover to think this node hasn't been discovered, the
temp bmc discover will not be removed from xcat database.
The discover packet should contain same info as what defined for the storage
node (CPU, disksize, mtm/serial, memory....), i think you should just keep mac,
mtm/serial for the storage node, it will not run into discovery process.
...................................................................
Casandra Hong Qiu
Phone: (845) 433-9291, t/l 293-9291
Office: Building 8, 3-B-04
[email protected]<mailto:[email protected]>
[Inactive hide details for Kevin Keane ---11/28/2018 02:18:03 PM---If I remove
mtms and serial from the storage node definition,]Kevin Keane ---11/28/2018
02:18:03 PM---If I remove mtms and serial from the storage node definition, how
would that cause bmcdiscover to ig
From: Kevin Keane <[email protected]<mailto:[email protected]>>
To: xCAT Users Mailing list
<[email protected]<mailto:[email protected]>>
Date: 11/28/2018 02:18 PM
Subject: Re: [xcat-user] Excluding a node from discovery?
________________________________
If I remove mtms and serial from the storage node definition, how would that
cause bmcdiscover to ignore this node? It seems to me that in the contrary,
that would cause bmcdiscover to think this node hasn't been discovered yet.
But your response inspired a thought - if I do the opposite and *add* mtms,
serial and MAC address to the storage node object, would that be enough to get
bmcdiscover to think this node has already been discovered? Or do I need any
other settings?
_____________________________________________________________________
Kevin Keane | Systems Architect | University of San Diego ITS |
[email protected]<mailto:[email protected]>
Maher Hall, 192 |5998 Alcalá Park | San Diego, CA 92110-2492 | 619.260.6859
REMEMBER! No one from IT at USD will ever ask to confirm or supply your
password.
These messages are an attempt to steal your username and password. Please do
not reply to, click the links within, or open the attachments of these
messages. Delete them!
On Wed, Nov 28, 2018 at 11:02 AM Casandra H Qiu
<[email protected]<mailto:[email protected]>> wrote:
You may need to remove mtms/serial number from storage node definition.
Also, you should remove mac address from storage node definition,
"makedhcp -d storagenode " to remove from DHCP lease file
Thanks,
Casandra Qiu
...................................................................
Casandra Hong Qiu
Phone: (845) 433-9291, t/l 293-9291
Office: Building 8, 3-B-04
[email protected]<mailto:[email protected]>
Kevin Keane ---11/28/2018 01:03:36 PM---I am looking for a way to exclude one
node from being discovered (MTMS-based discovery).
From: Kevin Keane <[email protected]<mailto:[email protected]>>
To: xCAT Users Mailing list
<[email protected]<mailto:[email protected]>>
Date: 11/28/2018 01:03 PM
Subject: [xcat-user] Excluding a node from discovery?
________________________________
I am looking for a way to exclude one node from being discovered (MTMS-based
discovery).
The background is that we have quite a few compute nodes, and one storage node.
The storage node is managed separately, but is of course connected to the same
networks as the compute nodes. If I blindly run bmcdiscover on the whole
subnet, it will discover the storage node. The worst-case scenario is that I
accidentally reformat it and lose data.
So I am looking for a way to keep this node from ever even being discovered in
the first place. Any ideas?
Thanks!
_______________________________________________________________________
Kevin Keane | Systems Architect | University of San Diego ITS |
[email protected]<mailto:[email protected]>
Maher Hall, 192 |5998 Alcalá Park | San Diego, CA 92110-2492 | 619.260.6859
REMEMBER! No one from IT at USD will ever ask to confirm or supply your
password.
These messages are an attempt to steal your username and password. Please do
not reply to, click the links within, or open the attachments of these
messages. Delete them!
_______________________________________________
xCAT-user mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/xcat-user
_______________________________________________
xCAT-user mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/xcat-user[attachment "graycol.gif"
deleted by Casandra H Qiu/Poughkeepsie/IBM] [attachment "graycol.gif" deleted
by Casandra H Qiu/Poughkeepsie/IBM]
_______________________________________________
xCAT-user mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/xcat-user
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
