Hi,

This IP is provided by Automatic Private IP Addressing. This process assigns an IP address even in the absence of a DHCP server. If a DISCOVER message is not answered, the client picks a random 16-bit number and prepends it with 169.254.x.x. It performs a gratuitous ARP and assigns that address to itself. It means that the DHCP server is not reachable.

Br,
Blockchain, DevOps & Open Source Cloud Solutions Architect
----------------------------------------
Founder & CEO 
Skype ID: d.overload
 +34 682 740 973 / +39 392 1289553 / +49 152 26917722 / Česká republika: +420 774 274 882  
-----------------------------------------------------


El lun., 26 nov. 2018 a las 10:39, Saju M (<sajuptpm@gmail.com>) escribió:
HI,

I have noticed that sysinv is trying to listen to 6385 with 2 different IPs.
I dont know, How 169.254.202.2 came in etc/sysinv/sysinv.conf, I could not find that IP in hiera.

Error from /var/log/sysinv.log
==========================
2018-11-26 08:46:09.298 18046 INFO oslo.service.wsgi [-] sysinv_api listening on 0.0.0.0:6385
ERROR oslo.service.wsgi [-] Could not bind to 169.254.202.2:6385


Somebody please explain the use of sysinv_api() and sysinv_pxe()
==========================================


Regards
Saju Madhavan
+91 09535134654
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss