On 8/25/16 2:25 , Ian Collins wrote: > On 08/13/16 05:58 AM, Robert Mustacchi wrote: >> On 8/12/16 1:10 , Ian Collins wrote: >>> On 08/12/16 07:43 PM, Kilian Ries wrote: >>>> Hi Ian, >>>> are you running the nics standalone or in bonding mode? >>>> I had the same or a similar problem a while ago: >>>> >>>> https://www.mail-archive.com/[email protected]/msg02842.html >>>> >>>> >>>> Unfortunately we didn't find a solution for the problem ... >>>> >>> It's just a single NIC which (I assume) is directly connected to a >>> switch. There's an identical box next to it in the rack running hyperv >>> which works fine. >>> >> I think these are likely related problems, which is getting close to >> what Garrett said. One of the things we should probably look at is >> updating the 5719/5720 to leverage the newer virtualization bits instead >> of the legacy format that we're using. > > Well this is embarrassing... > > After seeing the same issue with Linux on the same static IP (not DHCP) > I got the networking people to double check everything and they found > they had given me an address block on the wrong VLAN. > > Now I have a block on the correct VLAN, everything is working on this > nice 32 core box. Next is a head to head with HyperV running on its > twin :)
Thanks for the update, I'm glad that it turned out not to be a hardware / driver problem. Robert ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
