xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-06-14 10:20:31 +00:00
Code Issues Releases Wiki Activity

Merge pull request #225 from zet809/bmcdiscover_doc

Browse Source 
replace lsslp with bmcdiscover for discover BMC/FSP
This commit is contained in:
Xiaopeng Wang
2015-09-29 16:54:39 +08:00
parent 7c1d9f94a6 d3eef9d93a
commit 2b48f2a10e
6 changed files with 103 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst
View File

@ -33,17 +33,6 @@ Update DHCP configuration file::
makedhcp -n
makedhcp -a
setup DNS
`````````
Set site.forwarders to your site-wide DNS servers that can resolve site or public hostnames. The DNS on the MN will forward any requests it can't answer to these servers::
chdef -t site forwarders=8.8.8.8
Run makedns to get the hostname/IP pairs copied from /etc/hosts to the DNS on the MN::
makedns -n
Config passwd table
```````````````````
@ -56,10 +45,6 @@ For hardware management with ipmi, add the following line::
"ipmi","ADMIN","admin",,,,
For OS provisioning, add the following line::
"system","root","cluster",,,,
Verify the genesis pkg
``````````````````````

14
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst
View File

@ -11,9 +11,13 @@ Discover server and define
After environment is ready, and the server is powered, we can start server discovery process. The first thing to do is discovering the FSP/BMC of the server. It is automatically powered on when the physical server is powered.
The following command can be used to discovery FSP/BMC within an IP range and write the discovered node definition into a stanza file::
The following command can be used to discovery BMC within an IP range and write the discovered node definition into a stanza file::
lsslp -s PBMC -u --range 50.0.100.1-100 -z > ./pbmc.stanza
bmcdiscover -s nmap --range 50.0.100.1-100 -z > ./bmc.stanza
**Note**: bmcdiscover will use username/password pair set in ``passwd`` table with **key** equal **ipmi**. If you'd like to use other username/password, you can use ::
bmcdiscover -s nmap --range 50.0.100.1-100 -z -u <username> -p <password> > ./bmc.stanza
You need to modify the node definition in stanza file before using them, the stanza file will be like this::
@ -21,12 +25,10 @@ You need to modify the node definition in stanza file before using them, the sta
cn1:
objtype=node
bmc=50.0.100.1
nodetype=mp
mtm=8247-42L
serial=10112CA
groups=pbmc,all
mgt=ipmi
hidden=0
Then, define it into xCATdb::
@ -47,7 +49,7 @@ The server definition will be like this::
postscripts=syslog,remoteshell,syncfiles
serial=10112CA
After the physical server is defined into xCATdb, the next thing is update the node definition with the scheduled node info like this::
After the physical server is defined into xCATdb, the next thing is update the node definition with the example node attributes::
# chdef cn1 ip=10.0.101.1
1 object definitions have been created or modified.
@ -57,6 +59,8 @@ Then, add node info into /etc/hosts and DNS::
makehosts cn1
makedns -n
Start discovery process
-----------------------

40
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery_with_bmcdiscover.rst Normal file
View File

@ -0,0 +1,40 @@
Discover server and define
--------------------------
After environment is ready, and the server is powered, we can start server discovery process. The first thing to do is discovering the FSP/BMC of the server. It is automatically powered on when the physical server is powered.
The following command can be used to discovery BMC within an IP range and write the discovered node definition into xCAT database::
bmcdiscover -s nmap --range 50.0.100.1-100 -z -w
The discovered BMC node will be like this::
# lsdef node-8247-42l-10112ca
Object name: node-8247-42l-10112ca
bmc=50.0.100.1
cons=ipmi
groups=all
mgt=ipmi
mtm=8247-42L
postbootscripts=otherpkgs
postscripts=syslog,remoteshell,syncfiles
serial=10112CA
**Note**:
1. The BMC node is just used to control the physical during hardware discovery process, it will be deleted after the correct server node object is found.
2. bmcdiscover will use username/password pair set in ``passwd`` table with **key** equal **ipmi**. If you'd like to use other username/password pair, you can use ::
bmcdiscover -s nmap --range 50.0.100.1-100 -z -w -u <username> -p <password>
Start discovery process
-----------------------
To start discovery process, just need to power on the PBMC node remotely with the following command, and the discovery process will start automatically after the host is powered on::
rpower node-8247-42l-10112ca on
**[Optional]** If you'd like to monitor the discovery process, you can use::
makeconsercf node-8247-42l-10112ca
rcons node-8247-42l-10112ca

52
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery_with_lsslp.rst Normal file
View File

@ -0,0 +1,52 @@
Discover server and define
--------------------------
After environment is ready, and the server is powered, we can start server discovery process. The first thing to do is discovering the FSP/BMC of the server. It is automatically powered on when the physical server is powered.
The following command can be used to discovery FSP/BMC within an IP range and write the discovered node definition into a stanza file::
lsslp -s PBMC -u --range 50.0.100.1-100 -z > ./pbmc.stanza
You need to modify the node definition in stanza file before using them, the stanza file will be like this::
# cat pbmc.stanza
cn1:
objtype=node
bmc=50.0.100.1
nodetype=mp
mtm=8247-42L
serial=10112CA
groups=pbmc,all
mgt=ipmi
hidden=0
Then, define it into xCATdb::
# cat pbmc.stanza | mkdef -z
1 object definitions have been created or modified.
The server definition will be like this::
# lsdef cn1
Object name: cn1
bmc=50.0.100.1
groups=pbmc,all
hidden=0
mgt=ipmi
mtm=8247-42L
nodetype=mp
postbootscripts=otherpkgs
postscripts=syslog,remoteshell,syncfiles
serial=10112CA
After the physical server is defined into xCATdb, the next thing is update the node definition with the scheduled node info like this::
# chdef cn1 ip=10.0.101.1
1 object definitions have been created or modified.
Then, add node info into /etc/hosts and DNS::
makehosts cn1
makedns -n

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst
View File

@ -47,5 +47,5 @@ Stop the current sequential discovery process::
Note: The sequential discovery process will be stopped automatically when all of the node names in the node pool are used up.
.. include:: pbmc_discovery.rst
.. include:: pbmc_discovery_with_bmcdiscover.rst
.. include:: standard_cn_definition.rst

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst
View File

@ -57,7 +57,7 @@ Add cn1 into DNS::
makehosts cn1
maekdns -n
.. include:: pbmc_discovery.rst
.. include:: pbmc_discovery_with_bmcdiscover.rst
Verify node definition
----------------------