Dario, I just disabled IPv6 on the xCAT server and added --noipv6=yes to the network conf of my kick start script. These two changes resolved all of the issues I was facing with xCAT. Provisioning with xCAT is now working as expected.
Regards, Jamie I. Fargen Research Computing University of South Florida [email protected] ________________________________________ From: Dario Dorella [[email protected]] Sent: Tuesday, October 18, 2011 3:30 AM To: xCAT Users Mailing list; Fargen, Jamie Subject: Re: [xcat-user] xCAT-user Digest, Vol 26, Issue 10 Hello Jamie et all, I think I go it! :-) Somehow xcatd believes it needs to resolve addresses using IPv6. To try this out I've modified /opt/xcat/sbin/xcatd and forced $inet6support to be "0": [...] my $inet6support; if ($^O =~ /^aix/i) { # disable AIX IPV6 TODO $inet6support = 0; } else { $inet6support=eval { require Socket6 }; } $inet6support = 0; # <--------------- Inserted this line After restarting xcatd updateflag.awk started to behave, so indeed it was a name resolution issue, but a little more tricky than what I supposed initially. We're now trying to understand why "$inet6support=eval { require Socket6 };" is returning something it should not in our understanding. At least now we have something working, even if not exactly using a fix I perfectly like. In case we have something more worth sharing, I'll push the updates to the list. Thanks everybody for the help and notes, Dario ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
