Hi, I''m having trouble creating a guest domain that uses dhcp for its address. I''m wondering if maybe someone can point out something simple I may be missing. So here''s my setup. Everything is all on one machine. We''re running a dhcp server within a zone. I''ve confirmed that the server is up, and that it is handing out addresses. I have another zone set up that uses it, and I can halt and boot that zone and it gets an ip address from the server. So I can do this with a zone but not with a guest domU yet. I''ve tried two approaches to getting the domU to get an IP address. One was to run a virt-install in which I explicitly choose to have the machine networked using dhcp. I bridge it over the same network interface that the zones are using. Unfortunately it always times out during the install and tells me it could not find a dhcp server. The other thing I tried, and I think maybe this was misguided, it might only work for zones, but I installed a guest image without networking and then edited the sysidcfg file to enable dhcp, and then rebooted the guest. That didn''t seem to work either. I hope you can understand my rambling, but is there anything that comes to mind that I may be missing? Thanks for any help. -Dan -- This message posted from opensolaris.org
Daniel wrote:> Hi, > > I''m having trouble creating a guest domain that uses dhcp for> its address. I''m wondering if maybe someone can point out something > simple I may be missing.> > So here''s my setup. Everything is all on one machine. We''re running> a dhcp server within a zone. I''ve confirmed that the server is up, > and that it is handing out addresses. I have another zone set up that > uses it, and I can halt and boot that zone and it gets an ip address > from the server. So I can do this with a zone but not with a guest domU yet. Have you tried using a VNIC in the zone with the dhcp server (i.e. exclusive IP stack)? I would expect that this will work, although I''m not sure what the problem would be. e.g. # dladm create-vnic -l e1000g0 dhcp-server ... zonecfg:dhcp> set ip-type=exclusive zonecfg:dhcp> add net zonecfg:dhcp:net> set physical=dhcp-server zonecfg:dhcp:net> end> I''ve tried two approaches to getting the domU to get an IP address. One> was to run a virt-install in which I explicitly choose to have the > machine networked using dhcp. I bridge it over the same network interface> that the zones are using. Unfortunately it always times out during the> install and tells me it could not find a dhcp server.> > The other thing I tried, and I think maybe this was misguided, it might> only work for zones, but I installed a guest image without networking > and then edited the sysidcfg file to enable dhcp, and then rebooted > the guest. That didn''t seem to work either.> > I hope you can understand my rambling, but is there anything that comes> to mind that I may be missing? Thanks for any help. can you do a dladm show-link and then snoop on the vnic used for the guest? Thanks, MRJ
> > > Daniel wrote: > > Hi, > > > > I''m having trouble creating a guest domain that > uses dhcp for > > its address. I''m wondering if maybe someone can > point out something > > simple I may be missing. > > > > So here''s my setup. Everything is all on one > machine. We''re running > > a dhcp server within a zone. I''ve confirmed that > the server is up, > > and that it is handing out addresses. I have > another zone set up that > > uses it, and I can halt and boot that zone and it > gets an ip address > > from the server. So I can do this with a zone but > not with a guest domU yet. > > Have you tried using a VNIC in the zone with the dhcp > server > (i.e. exclusive IP stack)? I would expect that this > will work, > although I''m not sure what the problem would be. > > e.g. > > # dladm create-vnic -l e1000g0 dhcp-server > ... > zonecfg:dhcp> set ip-type=exclusive > zonecfg:dhcp> add net > zonecfg:dhcp:net> set physical=dhcp-server > zonecfg:dhcp:net> endYes. The dhcp server zone is using a vnic and it''s bridged over the same interface as the guest domU.> > > > > > I''ve tried two approaches to getting the domU to > get an IP address. One > > was to run a virt-install in which I explicitly > choose to have the > > machine networked using dhcp. I bridge it over the > same network interface > > that the zones are using. Unfortunately it always > times out during the > > install and tells me it could not find a dhcp > server. > > The other thing I tried, and I think maybe this was > misguided, it might > > only work for zones, but I installed a guest image > without networking > > and then edited the sysidcfg file to enable dhcp, > and then rebooted > > the guest. That didn''t seem to work either. > > > > I hope you can understand my rambling, but is there > anything that comes > > to mind that I may be missing? Thanks for any > help. > can you do a dladm show-link and then snoop on the > vnic used for > the guest? >here''s a sample of the snoop output during the virt-install at the step where it looks for the dhcp server. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ r69s27.SFBay.Sun.COM -> (broadcast) ARP C Who is 10.5.184.53, sca11bxvm01.SFBay.Sun.COM ? omalley-iron6.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48366 Offset=0 MF=1 TOS=0x0 TTL=1 omalley-iron6.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48366 Offset=1480 MF=1 TOS=0x0 TTL=1 omalley-iron6.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48366 Offset=2960 MF=0 TOS=0x0 TTL=1 ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7820 Offset=0 MF=1 TOS=0x0 TTL=1 ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7820 Offset=1480 MF=1 TOS=0x0 TTL=1 ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7820 Offset=2960 MF=0 TOS=0x0 TTL=1 omalley4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=24383 Offset=0 MF=1 TOS=0x0 TTL=1 omalley4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=24383 Offset=1480 MF=1 TOS=0x0 TTL=1 omalley4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=24383 Offset=2960 MF=0 TOS=0x0 TTL=1 omalley-iron4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48566 Offset=0 MF=1 TOS=0x0 TTL=1 omalley-iron4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48566 Offset=1480 MF=1 TOS=0x0 TTL=1 omalley-iron4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48566 Offset=2960 MF=0 TOS=0x0 TTL=1 ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7821 Offset=0 MF=1 TOS=0x0 TTL=1 ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7821 Offset=1480 MF=1 TOS=0x0 TTL=1 ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7821 Offset=2960 MF=0 TOS=0x0 TTL=1 ccdev-sca11-06.SFBay.Sun.COM -> 239.100.1.1 UDP D=9090 S=64049 LEN=84 omalley1.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=49801 Offset=0 MF=1 TOS=0x0 TTL=1 omalley1.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=49801 Offset=1480 MF=1 TOS=0x0 TTL=1 omalley1.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=49801 Offset=2960 MF=0 TOS=0x0 TTL=1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Not sure that this helps. but thanks for any help. -Dan> > > Thanks, > > MRJ > > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org-- This message posted from opensolaris.org
Daniel, The snoop output you show below doesn''t look like DHCP traffic at all. You might want to do a "snoop dhcp" to limit the packets captured or use the -m option with virt-install to explicitly set a specific MAC address on your new domain which you could then "snoop ether <addr>" on. --joe Daniel wrote:>> Daniel wrote: >> >>> Hi, >>> >>> I''m having trouble creating a guest domain that >>> >> uses dhcp for >> >>> its address. I''m wondering if maybe someone can >>> >> point out something >> >>> simple I may be missing. >>> >>> So here''s my setup. Everything is all on one >>> >> machine. We''re running >> >>> a dhcp server within a zone. I''ve confirmed that >>> >> the server is up, >> >>> and that it is handing out addresses. I have >>> >> another zone set up that >> >>> uses it, and I can halt and boot that zone and it >>> >> gets an ip address >> >>> from the server. So I can do this with a zone but >>> >> not with a guest domU yet. >> >> Have you tried using a VNIC in the zone with the dhcp >> server >> (i.e. exclusive IP stack)? I would expect that this >> will work, >> although I''m not sure what the problem would be. >> >> e.g. >> >> # dladm create-vnic -l e1000g0 dhcp-server >> ... >> zonecfg:dhcp> set ip-type=exclusive >> zonecfg:dhcp> add net >> zonecfg:dhcp:net> set physical=dhcp-server >> zonecfg:dhcp:net> end >> > > Yes. The dhcp server zone is using a vnic and it''s bridged over the same interface as the guest domU. > > >> >> >> >>> I''ve tried two approaches to getting the domU to >>> >> get an IP address. One >> >>> was to run a virt-install in which I explicitly >>> >> choose to have the >> >>> machine networked using dhcp. I bridge it over the >>> >> same network interface >> >>> that the zones are using. Unfortunately it always >>> >> times out during the >> >>> install and tells me it could not find a dhcp >>> >> server. >> >> The other thing I tried, and I think maybe this was >> misguided, it might >> >>> only work for zones, but I installed a guest image >>> >> without networking >> >>> and then edited the sysidcfg file to enable dhcp, >>> >> and then rebooted >> >>> the guest. That didn''t seem to work either. >>> >>> I hope you can understand my rambling, but is there >>> >> anything that comes >> >>> to mind that I may be missing? Thanks for any >>> >> help. >> can you do a dladm show-link and then snoop on the >> vnic used for >> the guest? >> >> > > here''s a sample of the snoop output during the virt-install at the step where it looks for the dhcp server. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > r69s27.SFBay.Sun.COM -> (broadcast) ARP C Who is 10.5.184.53, sca11bxvm01.SFBay.Sun.COM ? > omalley-iron6.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48366 Offset=0 MF=1 TOS=0x0 TTL=1 > omalley-iron6.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48366 Offset=1480 MF=1 TOS=0x0 TTL=1 > omalley-iron6.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48366 Offset=2960 MF=0 TOS=0x0 TTL=1 > ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7820 Offset=0 MF=1 TOS=0x0 TTL=1 > ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7820 Offset=1480 MF=1 TOS=0x0 TTL=1 > ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7820 Offset=2960 MF=0 TOS=0x0 TTL=1 > omalley4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=24383 Offset=0 MF=1 TOS=0x0 TTL=1 > omalley4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=24383 Offset=1480 MF=1 TOS=0x0 TTL=1 > omalley4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=24383 Offset=2960 MF=0 TOS=0x0 TTL=1 > omalley-iron4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48566 Offset=0 MF=1 TOS=0x0 TTL=1 > omalley-iron4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48566 Offset=1480 MF=1 TOS=0x0 TTL=1 > omalley-iron4.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=48566 Offset=2960 MF=0 TOS=0x0 TTL=1 > ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7821 Offset=0 MF=1 TOS=0x0 TTL=1 > ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7821 Offset=1480 MF=1 TOS=0x0 TTL=1 > ccdev-sca11-05-z03.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=7821 Offset=2960 MF=0 TOS=0x0 TTL=1 > ccdev-sca11-06.SFBay.Sun.COM -> 239.100.1.1 UDP D=9090 S=64049 LEN=84 > omalley1.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=49801 Offset=0 MF=1 TOS=0x0 TTL=1 > omalley1.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=49801 Offset=1480 MF=1 TOS=0x0 TTL=1 > omalley1.SFBay.Sun.COM -> reserved-multicast-range-NOT-delegated.example.com UDP IP fragment ID=49801 Offset=2960 MF=0 TOS=0x0 TTL=1 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Not sure that this helps. but thanks for any help. > > -Dan > > >> Thanks, >> >> MRJ >> >> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >>
Thanks Joe, I restarted the virt-install and snooped the domU''s vnic and got the following: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Using device vnic7 (promiscuous mode) OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER 172.0.94.153 -> BROADCAST DHCP/BOOTP DHCPREQUEST OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Dan -- This message posted from opensolaris.org
Hi Dan. Daniel wrote:> Thanks Joe, > > I restarted the virt-install and snooped the domU''s vnic and got the following: > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Using device vnic7 (promiscuous mode) > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > 172.0.94.153 -> BROADCAST DHCP/BOOTP DHCPREQUEST > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~What''s the output of dladm show-link? What do you see if you snoop on the dhcp server vnic? Thanks, MRJ
Also, assuming you''re using the daemon supplied with [Open]Solaris, I found it useful to run in.dhcpd in debug mode (-d) which will keep the daemon running as a foreground process and spew out messages as it does things. (make you sure svcadm disable it first if you do) --joe Mark Johnson wrote:> > Hi Dan. > > > Daniel wrote: >> Thanks Joe, >> >> I restarted the virt-install and snooped the domU''s vnic and got the >> following: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Using device vnic7 (promiscuous mode) >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> 172.0.94.153 -> BROADCAST DHCP/BOOTP DHCPREQUEST >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > What''s the output of dladm show-link? What do you see if > you snoop on the dhcp server vnic? > > > > Thanks, > > > MRJ > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
i was just about to post that :) snooping the server''s vnic shows: Using device jms2 (promiscuous mode) OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPREQUEST jms02.network.com -> 172.0.94.151 DHCP/BOOTP DHCPACK OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER 172.0.94.174 -> jms02.network.com DHCP/BOOTP DHCPREQUEST jms02.network.com -> 172.0.94.174 DHCP/BOOTP DHCPACK OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER and dladm show-link shows $ dladm show-link LINK CLASS MTU STATE OVER e1000g0 phys 1500 up -- e1000g2 phys 1500 unknown -- e1000g1 phys 1500 unknown -- e1000g3 phys 1500 unknown -- ldp1 vnic 1500 up e1000g0 jms2 vnic 1500 up e1000g0 r1 vnic 1500 up e1000g0 ldp2 vnic 1500 up e1000g0 ctl1 vnic 1500 up e1000g0 ctl2 vnic 1500 up e1000g0 mon1 vnic 1500 up e1000g0 mon2 vnic 1500 up e1000g0 jms1 vnic 1500 up e1000g0 web1 vnic 1500 up e1000g0 web2 vnic 1500 up e1000g0 dbs1 vnic 1500 up e1000g0 dbs2 vnic 1500 up e1000g0 dav1 vnic 1500 up e1000g0 dav2 vnic 1500 up e1000g0 dav3 vnic 1500 up e1000g0 dav4 vnic 1500 up e1000g0 sqd1 vnic 1500 up e1000g0 sqd2 vnic 1500 up e1000g0 test1 vnic 1500 up e1000g0 vnic7 vnic 1500 up e1000g0 master1 vnic 1500 up e1000g0 ldp103 vnic 1500 up e1000g0 btw all those vnics except for vnic7 are zones. jms2 is the vnic where the dhcp-server is running -Dan -- This message posted from opensolaris.org
So the dhcp server appears to be seeing the requests come in (DHCPREQUEST) but is not offering anything back to the client (DHCPOFFER), kinda strange, unless either you''re out of IPs or you have permanently assigned IPs in your dhcp daemon configuration. You might get some deeper information by running "in.dhcpd -d". You might even see something in dmesg or messages or syslog. --joe Daniel wrote:> i was just about to post that :) > > snooping the server''s vnic shows: > > Using device jms2 (promiscuous mode) > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPREQUEST > jms02.network.com -> 172.0.94.151 DHCP/BOOTP DHCPACK > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > 172.0.94.174 -> jms02.network.com DHCP/BOOTP DHCPREQUEST > jms02.network.com -> 172.0.94.174 DHCP/BOOTP DHCPACK > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER > > > and dladm show-link shows > > $ dladm show-link > LINK CLASS MTU STATE OVER > e1000g0 phys 1500 up -- > e1000g2 phys 1500 unknown -- > e1000g1 phys 1500 unknown -- > e1000g3 phys 1500 unknown -- > ldp1 vnic 1500 up e1000g0 > jms2 vnic 1500 up e1000g0 > r1 vnic 1500 up e1000g0 > ldp2 vnic 1500 up e1000g0 > ctl1 vnic 1500 up e1000g0 > ctl2 vnic 1500 up e1000g0 > mon1 vnic 1500 up e1000g0 > mon2 vnic 1500 up e1000g0 > jms1 vnic 1500 up e1000g0 > web1 vnic 1500 up e1000g0 > web2 vnic 1500 up e1000g0 > dbs1 vnic 1500 up e1000g0 > dbs2 vnic 1500 up e1000g0 > dav1 vnic 1500 up e1000g0 > dav2 vnic 1500 up e1000g0 > dav3 vnic 1500 up e1000g0 > dav4 vnic 1500 up e1000g0 > sqd1 vnic 1500 up e1000g0 > sqd2 vnic 1500 up e1000g0 > test1 vnic 1500 up e1000g0 > vnic7 vnic 1500 up e1000g0 > master1 vnic 1500 up e1000g0 > ldp103 vnic 1500 up e1000g0 > > > btw all those vnics except for vnic7 are zones. jms2 is the vnic where the dhcp-server is running > > -Dan >
Does your Box connect to the LAN outside the Box? Does your LAN have another DHCP server? I think you should confirm that only one DHCP server in your SubNet, and confirm the IP address is not used up. Could your try binding the MAC to the IP on your own DHCP server in the zones? Joseph Mocker wrote:> So the dhcp server appears to be seeing the requests come in > (DHCPREQUEST) but is not offering anything back to the client > (DHCPOFFER), kinda strange, unless either you''re out of IPs or you > have permanently assigned IPs in your dhcp daemon configuration. > > You might get some deeper information by running "in.dhcpd -d". You > might even see something in dmesg or messages or syslog. > > --joe > > Daniel wrote: >> i was just about to post that :) >> >> snooping the server''s vnic shows: >> >> Using device jms2 (promiscuous mode) >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPREQUEST >> jms02.network.com -> 172.0.94.151 DHCP/BOOTP DHCPACK >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> 172.0.94.174 -> jms02.network.com DHCP/BOOTP DHCPREQUEST >> jms02.network.com -> 172.0.94.174 DHCP/BOOTP DHCPACK >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> OLD-BROADCAST -> BROADCAST DHCP/BOOTP DHCPDISCOVER >> >> >> and dladm show-link shows >> >> $ dladm show-link >> LINK CLASS MTU STATE OVER >> e1000g0 phys 1500 up -- >> e1000g2 phys 1500 unknown -- >> e1000g1 phys 1500 unknown -- >> e1000g3 phys 1500 unknown -- >> ldp1 vnic 1500 up e1000g0 >> jms2 vnic 1500 up e1000g0 >> r1 vnic 1500 up e1000g0 >> ldp2 vnic 1500 up e1000g0 >> ctl1 vnic 1500 up e1000g0 >> ctl2 vnic 1500 up e1000g0 >> mon1 vnic 1500 up e1000g0 >> mon2 vnic 1500 up e1000g0 >> jms1 vnic 1500 up e1000g0 >> web1 vnic 1500 up e1000g0 >> web2 vnic 1500 up e1000g0 >> dbs1 vnic 1500 up e1000g0 >> dbs2 vnic 1500 up e1000g0 >> dav1 vnic 1500 up e1000g0 >> dav2 vnic 1500 up e1000g0 >> dav3 vnic 1500 up e1000g0 >> dav4 vnic 1500 up e1000g0 >> sqd1 vnic 1500 up e1000g0 >> sqd2 vnic 1500 up e1000g0 >> test1 vnic 1500 up e1000g0 >> vnic7 vnic 1500 up e1000g0 >> master1 vnic 1500 up e1000g0 >> ldp103 vnic 1500 up e1000g0 >> >> >> btw all those vnics except for vnic7 are zones. jms2 is the vnic >> where the dhcp-server is running >> >> -Dan >> > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Thank you all for your help in narrowing this problem down. It did in fact turn out to be an issue with the dhcp server. We''re not sure exactly what the root cause was, but after a restart of the server the domU now gets addresses. So no clear understanding of exactly what went wrong, but at least it works now. Thanks again for all the help on this. This forum has been very helpful to me several times already and it is very appreciated. -Dan -- This message posted from opensolaris.org