[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] host internal management network


  • To: 'Shakeel Butt' <shakeel.butt@xxxxxxxxx>
  • From: Rob Hoes <Rob.Hoes@xxxxxxxxxx>
  • Date: Mon, 17 Mar 2014 10:50:49 +0000
  • Accept-language: en-GB, en-US
  • Cc: "xen-api@xxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxx>
  • Delivery-date: Mon, 17 Mar 2014 10:51:29 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
  • Thread-index: AQHPQaccvARu5SARuU+2Bgjq+nMLj5rlGX1A
  • Thread-topic: [Xen-API] host internal management network

Hi Shakeel,

> I have few queries regarding Host Internal Management Network (HIMN).
> I see that ip range used for HIMS is 169.254.*.* and dom0 always get IP
> 169.254.0.1 for the interface connected to HIMS. Is this IP range and dom0
> IP are statically assigned and will remain same for compatibility reason?
> Or can this IP range and dom0 IP can be changed dynamically? And similarly
> is there an xenapi to retrieve the dom0 IP for interface connecting HIMN
> (if it can be dynamic)?

The IP range is configurable using other-config keys. I think dom0 always gets 
the first IP in the range. Take a look here: 
https://github.com/xapi-project/xen-api/blob/master/apis/udhcp.md.

Cheers,
Rob

> thanks,
> Shakeel
> 
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.