[OmniOS-discuss] LACP Omnios , igb and C3750
Floris van Essen ..:: House of Ancients Amstafs ::..
info at houseofancients.nl
Fri Dec 12 20:36:16 UTC 2014
Hi Dan,
So..
Pulled a working i350 ( connected to the same switch) from one of my vmware hosts.
This would be the 3rd broke i350
Plugged it in, went into BIOS, reset config data
Still no joy no ping, not arp
My last option would be an HP NC quad nic, but I don't think that is supported by omnios
Met vriendelijke groet / With kind regards,
Floris van Essen
-----Oorspronkelijk bericht-----
Van: Dan McDonald [mailto:danmcd at omniti.com]
Verzonden: vrijdag 12 december 2014 21:10
Aan: Floris van Essen ..:: House of Ancients Amstafs ::..
CC: Eric Sproul; omnios-discuss at lists.omniti.com
Onderwerp: Re: [OmniOS-discuss] LACP Omnios , igb and C3750
> On Dec 12, 2014, at 3:06 PM, Floris van Essen ..:: House of Ancients Amstafs ::.. <info at houseofancients.nl> wrote:
>
> ipadm create-addr -T static -a 192.168.0.1/24 igb3/v4
>
> let's check :
> # dladm show-ether
> LINK PTYPE STATE AUTO SPEED-DUPLEX PAUSE
> e1000g1 current up yes 1G-f bi
> e1000g0 current up yes 1G-f bi
> igb0 current down yes 0M-h bi
> igb1 current unknown yes 0M-h bi
> igb2 current unknown yes 0M-h bi
> igb3 current up yes 1G-f bi
>
> awesome
>
> root at PSD01:/root# dladm show-link
> LINK CLASS MTU STATE BRIDGE OVER
> e1000g1 phys 1500 up -- --
> e1000g0 phys 1500 up -- --
> aggr0 aggr 1500 up -- e1000g0 e1000g1
> igb0 phys 1500 down -- --
> igb1 phys 1500 unknown -- --
> igb2 phys 1500 unknown -- --
> igb3 phys 1500 up -- --
>
> awesome
>
> root at PSD01:/root# ifconfig -a
> lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
> inet 127.0.0.1 netmask ff000000
> aggr0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
> inet x.x.x.11 netmask ffffff00 broadcast 192.168.254.255
> ether 0:30:48:d5:ec:94
> igb3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 10
> inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
> ether a0:36:9f:2:c2:6f
> lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
> inet6 ::1/128
> aggr0: flags=20002000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2
> inet6 ::/0
> ether 0:30:48:d5:ec:94
> igb3: flags=20002000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 10
> inet6 ::/0
> ether a0:36:9f:2:c2:6f
>
> awesome
>
> root at PSD01:/root# ping 192.168.0.1
> 192.168.0.1 is alive
NOTE: Pinging the local address doesn't prove anything about a NIC.
> core-stack#sh arp | inc a036.9f:2.c26f core-stack# oh oh
>
> let's see if we can ping another host in the same subnet :
>
> root at PSD01:/root# ping 192.168.0.5
> no answer from 192.168.0.5
> root at PSD01:/root#
>
> let check the arp again :
>
> core-stack#sh arp | inc a036.9f:2.c26f core-stack#
>
> so I'm (again ) baffled
I'm actually relieved. I think your card is broken. The old driver doesn't improve your situation from what was previously happening.
See if putting that card in another machine helps. Or perhaps just re-seating it.
Dan
...:: House of Ancients ::...
American Staffordshire Terriers
+31-628-161-350
+31-614-198-389
Het Perk 48
4903 RB
Oosterhout
Netherlands
www.houseofancients.nl
More information about the OmniOS-discuss
mailing list