[et-mgmt-tools] "Could not communicate with" error

[Bill McGonigle]

On Jun 1, 2007, at 12:34, Michael DeHaan wrote:

> I'll see what's up with the docs...

Sorry, I should have just included what I was talking about:

     "Note that if a cobbler import provides enough information
     to use the boot server as a yum mirror for core packages,
     cobbler will set up kickstarts to use the cobbler server
     as a mirror instead of the outside world. If this feature
     is undesirable, it can be turned off by setting
     yum_core_mirror_from_server to 0 in /var/lib/cobbler/settings
     (and rerunning ``cobbler sync''). You may want to disable this
     feature if machines are provisioned on a different
     VLAN/network than production."

I'm also starting to understand the wisdom of setting up using MAC  
addresses, even under Xen.  Are there 'best practices' for this?  I  
just made up a prefix (BF:CC in my case, so we can remember that my  
company set it up) and for the remainder I used the IP address, in  
hex, human order.  If there's a better way that might sync up later  
with virt-factory I'd be happy to change over.

Thanks,
-Bill

-----
Bill McGonigle, Owner           Work: 603.667.4000
BFC Computing, LLC              Home: 603.448.1668
bill at bfccomputing.com           Cell: 603.252.2606
http://www.bfccomputing.com/    Page: 603.442.1833
Blog: http://blog.bfccomputing.com/
VCard: http://bfccomputing.com/vcard/bill.vcf