Arif,
yes, it makes sense. It's kind of a new requirement, because current xcat
dns implementation can not meet this case and running command on SN
directly normally is not recommanded though it works for you :)
To Bruce,
for the implementation to set up an individual dns server on SN, I
I'm getting a dhcp timeout issue with xnba/genesis. On discovery, a node
will boot from the network and get the xnba image and then times out
getting network information via dhcp. I'm running xCAT version 2.8.2, if it
helps.
On the xcat management server side, I see the initial sequence of DHCP
Should be ready to be nodeset to do something else.
'standby' in this case is 'completed everything supposed to happen,
awaiting instructions'
If you put in hard drives with os still working:
nodeset node boot
if hard drive needs reinstall:
nodeset node osimage
If stateless:
nodeset node
OK - I'll try booting from the hard drive and see if that works, but...BMC
never got programed. I can't reach this node with any of the rcons/rpower
commands and if I try to telnet to its bmc port it fails.
I'll keep poking to see if there are any other errors related to programing
of BMC.
Perhaps the cmos settings need to be adjusted. If you have a shared nic
(eth0/imm) make sure the the appropriate settings in cmos indicate shared
nic. What is the server machine type?
Thomas Alandt
WW Test Engineer Complex Solutions
IBM-ISC
From: Damir Krstic damir.krs...@gmail.com
To:
I'll bet that ipmi.bmcport is not set.
If that is the case, set:
nodech noderange ipmi.bmcport=0
And from now on, the IMM will move to the right port automatically during
bmcsetup.
From: Damir Krstic damir.krs...@gmail.com
To: xCAT Users Mailing list xcat-user@lists.sourceforge.net
I'm getting a dhcp timeout issue with xnba/genesis. On discovery, a node
will boot from the network and get the xnba image. It then times out
getting network information via dhcp from within xnba. I'm running xCAT
version 2.8.2, if it helps.
On the xcat management server side, I see the initial
We had a problem where the switch ports had been properly configured with
spanning-tree edge mode for the first 32 ports, but when we added new nodes, we
didn't notice that ports 33-48 on the switch had been left to the default.
Edge mode comes up quickly, but the default took too long to
