Re: [Starlingx-discuss] iPXE for IPv6
From the tcpdump it shows that it still tries sending a boot over ipv4 after getting an ipv6 address. I don't see any indication that the controller is doing anything incorrectly, so it is probably something with the configuration on the node you are trying to bring up. What sort of config is this? Is this on hardware(which) or virtualbox(which version)? What steps are you following to setup the initial install of the node that you are trying to boot? ________________________________ From: 张鲲鹏 <zhang.kunpeng@99cloud.net> Sent: Monday, March 16, 2020 11:27 PM To: Richard, Joseph <Joseph.Richard@windriver.com> Cc: Khalil, Ghada <Ghada.Khalil@windriver.com>; 黄舒泉 <huang.shuquan@99cloud.net>; Jolliffe, Ian <Ian.Jolliffe@windriver.com>; Peters, Matt <Matt.Peters@windriver.com>; Le, Huifeng <huifeng.le@intel.com>; Yong Hu <yong.hu@intel.com> Subject: Re: [Starlingx-discuss] iPXE for IPv6 Hi Joseph, Following are the logs when boot a host from ipxe. No errors to be found. And the boot file are not sent as the tcpdump show. sysinv.log sysinv 2020-03-17 02:51:52.977 959934 INFO sysinv.cmd.dnsmasq_lease_update [-] Called 'add' for mac '00:68:27:6e:8a:42' with ip 'fd00::3f' sysinv 2020-03-17 02:51:53.217 959934 INFO sysinv.openstack.common.rpc.common [-] Connected to AMQP server on 192.168.204.1:5672 sysinv 2020-03-17 02:51:53.229 95238 INFO sysinv.conductor.manager [-] receiving dhcp_lease: <sysinv.openstack.common.rpc.amqp.RpcContext object at 0x7f33cb7cf4d0> pxeboot dhcpv6 enp2s2 00:68:27:6e:8a:42 fd00::3f None sysinv 2020-03-17 02:51:53.261 95238 INFO sysinv.conductor.manager [-] Not creating ihost for mac: 00:68:27:6e:8a:42 because it already exists with uuid: 4e8ebd40-11a6-4d8e-8a8e-b2f8a703bc7e sysinv 2020-03-17 02:52:27.718 95238 INFO sysinv.conductor.manager [-] Platform managed application platform-integ-apps: Prerequisites not met. deamon.log 2020-03-17T02:51:49.000 controller-0 collectd[81838]: info ovs interface plugin failed to initial because pid file for ovs-vswitchd doesn't exist 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPDISCOVER(enp2s2) 52:54:00:0e:6a:02 no address available 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info RTR-SOLICIT(enp2s2) 52:54:00:0e:6a:02 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info RTR-ADVERT(enp2s2) fd00:: 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPSOLICIT(enp2s2) 00:04:2c:7e:7b:71:b2:c5:49:df:a6:53:00:68:27:6e:8a:42 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPADVERTISE(enp2s2) fd00::3f 00:04:2c:7e:7b:71:b2:c5:49:df:a6:53:00:68:27:6e:8a:42 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPREQUEST(enp2s2) 00:04:2c:7e:7b:71:b2:c5:49:df:a6:53:00:68:27:6e:8a:42 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPREPLY(enp2s2) fd00::3f 00:04:2c:7e:7b:71:b2:c5:49:df:a6:53:00:68:27:6e:8a:42 2020-03-17T02:51:52.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPDISCOVER(enp2s2) 52:54:00:0e:6a:02 no address available 2020-03-17T02:51:52.000 controller-0 dnsmasq-script[4093358]: debug sysinv 2020-03-17 02:51:52.977 959934 INFO sysinv.cmd.dnsmasq_lease_update [-] Called 'add' for mac '00:68:27:6e:8a:42' with ip 'fd00::3f'^[[00m 2020-03-17T02:51:53.000 controller-0 dnsmasq-script[4093358]: debug sysinv 2020-03-17 02:51:53.217 959934 INFO sysinv.openstack.common.rpc.common [-] Connected to AMQP server on 192.168.204.1:5672^[[00m 2020-03-17T02:51:54.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPDISCOVER(enp2s2) 52:54:00:0e:6a:02 no address available 2020-03-17T02:51:58.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPDISCOVER(enp2s2) 52:54:00:0e:6a:02 no address available tcpdump -i enp2s2 03:03:37.966202 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:38.471640 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:38.501756 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:38.977102 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:39.333447 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 52:54:00:0e:6a:02 (oui Unknown), length 402 03:03:39.333541 IP6 fe80::5054:ff:fe0e:6a02 > ff02::2: ICMP6, router solicitation, length 16 03:03:39.334408 IP6 fe80::5054:ff:fe5c:f3d7 > fe80::5054:ff:fe0e:6a02: ICMP6, router advertisement, length 88 03:03:39.345812 IP6 fe80::5054:ff:fe0e:6a02.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit 03:03:39.346207 IP6 fe80::5054:ff:fe5c:f3d7.dhcpv6-server > fe80::5054:ff:fe0e:6a02.dhcpv6-client: dhcp6 advertise 03:03:39.346488 IP6 fe80::5054:ff:fe0e:6a02.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 request 03:03:39.349335 IP6 fe80::5054:ff:fe5c:f3d7.dhcpv6-server > fe80::5054:ff:fe0e:6a02.dhcpv6-client: dhcp6 reply 03:03:39.482543 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:39.503651 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:39.988061 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:40.311669 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 52:54:00:0e:6a:02 (oui Unknown), length 402 03:03:40.493543 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:40.505647 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:40.999049 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:41.504513 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:41.507747 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:42.010033 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:42.288943 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 52:54:00:0e:6a:02 (oui Unknown), length 402 03:03:42.509638 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:42.515480 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:43.020834 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:43.511663 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:43.526277 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:44.031727 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:44.345728 IP6 fe80::5054:ff:fe5c:f3d7 > fe80::5054:ff:fe0e:6a02: ICMP6, neighbor solicitation, who has fe80::5054:ff:fe0e:6a02, length 32 03:03:44.345968 IP6 fe80::5054:ff:fe0e:6a02 > fe80::5054:ff:fe5c:f3d7: ICMP6, neighbor advertisement, tgt is fe80::5054:ff:fe0e:6a02, length 32 03:03:44.513797 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:44.537218 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:45.042730 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:45.515707 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:45.548183 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:46.053802 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:46.243493 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 52:54:00:0e:6a:02 (oui Unknown), length 402 03:03:46.517640 ARP, Request who-has controller-1 tell controller-0, length 28 在 2020年3月13日,06:10,Richard, Joseph <Joseph.Richard@windriver.com<mailto:Joseph.Richard@windriver.com>> 写道: <PastedGraphic-3.png><PastedGraphic-2.png><PastedGraphic-1.jpeg>_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (1)
-
Richard, Joseph