Menu
▾
▴
#3965 getmacs -D -S -G does not return mac hangs at 0 >
pending
hw ctrl
5
2014-07-23
2014-01-15
No
The getmacs command on hosts without LHEA does not appear to be working. The syntax I am using is
getmacs node -D -S 192.168.1.1 -G 192.168.1.1
It reboots the LPAR as expected but never comes back with the MAC address. When logging into the terminal it seems to be sitting at the 0 > prompt.
I do not believe this is related to https://sourceforge.net/p/xcat/bugs/3943/ but could be wrong.
I am currently using xCAT 2.7 in production and have tested the following in a test env on xCAT 2.8.3.
Thanks
Discussion
Could you please use the following steps and post the output?
Run "rcons <nodename>" to open a console for the node.</nodename>
Run "getmacs <nodename> -D -V -S 192.168.1.1 -G 192.168.1.1" to start the process with verbose turned on.</nodename>
Post the console output during the process, and the getmacs command output
[root@adm01 ~]# getmacs fs01 -D -V -S 192.168.1.1 -G 192.168.1.1
20140115.08:58:59 (10228) getmacs START.
20140115.08:58:59 (10228) getmacs :lssyscfg filter 'name,lpar_id'.
20140115.08:59:00 (10228) getmacs :do_getmacs for node:fs01.
20140115.08:59:00 (10228) getmacs :lparnetbootexp for node:fs01.
lpar_netboot Status: List only ent adapters
lpar_netboot Status: -n (no boot) flag detected
lpar_netboot Status: -D (discovery) flag detected
lpar_netboot Status: -A (discover all) flag detected
lpar_netboot Status: -v (verbose debug) flag detected
lpar_netboot Status: -M (discover mac address) flag detected
lpar_netboot Status: -i (force immediate shutdown) flag detected
lpar_netboot Status: -d (debug) flag detected
lpar_netboot Status: using adapter speed of auto
lpar_netboot Status: using adapter duplex of auto
lpar_netboot Status: using server IP address of 192.168.1.1
lpar_netboot Status: using client IP address of 192.168.1.55
lpar_netboot Status: using gateway IP address of 192.168.1.1
node:fs01
open port
spawn_id is 10232.
Connecting to the fs01.
Connected.
Checking for power off.
Status: run_lssyscg : partition status : fs01: Not Activated
msg:fs01: Not Activated
The lpar state is fs01: Not Activated.
Power off complete.
Power on the fs01 to the Open Firmware.
Waiting for power on...
Check the node state again;
Status: run_lssyscg : partition status : fs01: Starting
msg:fs01: Starting
The node state is fs01: Starting.
Status: run_lssyscg : partition status : fs01: Starting
msg:fs01: Starting
The node state is fs01: Starting.
Status: run_lssyscg : partition status : fs01: Running
msg:fs01: Running
The node state is fs01: Running.
Status: run_lssyscg : partition status : fs01: Running
msg:fs01: Running
The node state is fs01: Running.
Status: run_lssyscg : partition status : fs01: Running
msg:fs01: Running
The node state is fs01: Running.
Status: run_lssyscg : partition status : fs01: Open Firmware
msg:fs01: Open Firmware
The node state is fs01: Open Firmware.
Power on complete.
Check for active console.
Timeout waiting for ok prompt; exiting.
fs01:
09:00:10 10222 Total Elapsed Time: 71.227 sec
[root@adm01 ~]#
[root@adm01 ~]# rcons fs01
[Enter `^Ec?' for help]
[forced to `spy' mode by root@adm01.wd2.local]
[attached]
Last edit: tjbauman 2014-01-15
Will you pls paste the node definition here? We have encountered the similar issue which was caused by not completed definition.
Since the user haven't response for a log time, I move it further.
Since we could not recreate this problem and the originator is not responding, putting it to pending status, the originator could change it back to open status after provided responses to our questions.