On Thu, 13 Jun 2013 at 22:49 -0000, Lohit Valleru wrote:
> I have changed the xCAT management server hostname to cluster facing
> NIC hostname,and re-initialized the whole xCAT database with
> xcatconfig -f and xcatconfig -d.
>
> I verified all the tables and ran makedns, makedhcp -n, makehosts
> all and makeconservercf.
>
> After this change - Node got deployed without any issues. It
> installed the default postscripts and also my custom postscript -
> sab-basec6-setup.
I have looked at the configuration differences on this system and
notice that the common name in /etc/xcat/cert/server-cert.pem is now
the name of the cluster facing interface whereas before the common
name was the external interface.
I am guessing that this common name difference might have been causing
issues in authenticating the connection security in the security check
prior to sending credentials to the newly installed host. We will
look at this a little closer.
We tend to use the external facing interface name as the hostname for
our systems in order to reduce user confusion (the hostname thus
matches the name they use to ssh to the system). With our previous
xCAT installs I probably had the hostname set to the internal
interface during the initial xCAT setup, but later changed the
hostname to match the external interface.
Stuart
--
I've never been lost; I was once bewildered for three days, but never lost!
-- Daniel Boone
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
