[OmniOS-discuss] LACP Omnios , igb and C3750

Floris van Essen ..:: House of Ancients Amstafs ::.. info at houseofancients.nl
Sat Dec 13 14:01:04 UTC 2014


So i replaced the Igb adapter with a HP NC375t, loaded the drivers from HP,left cables and switch alone :

ntxn0  	 ntxn0  	 Ethernet  	 up  	 1000  	 full  	 BOUND  	 192.168.249.104  	 255.255.255.0  	 78:ac:c0:11:d4:88  	 1500  	 ok  	    	   
 ntxn1  	 ntxn1  	 Ethernet  	 unknown  	 1000  	 full  	 static  	 unset  	 -  	 -  	 1500  	   	    	   
 ntxn2  	 ntxn2  	 Ethernet  	 unknown  	 1000  	 full  	 static  	 unset  	 -  	 -  	 1500  	   	    	   
 ntxn3  	 ntxn3  	 Ethernet  	 unknown  	 1000  	 full  	 static  	 unset  	 -  	 -  	 1500  	   	

this all lead me to conclude that there is something wrong with the IGB implementation as it sits
Weather it be drivers, or something more to the background..don't know, but would love to find out

Met vriendelijke groet / With kind regards,



               Floris van Essen

-----Oorspronkelijk bericht-----
Van: Floris van Essen ..:: House of Ancients Amstafs ::.. 
Verzonden: zaterdag 13 december 2014 11:38
Aan: Dan McDonald
CC: omnios-discuss at lists.omniti.com
Onderwerp: Re: [OmniOS-discuss] LACP Omnios , igb and C3750

So,

To add to the weirdness.

Got ready to reinstall the whole machine, to set the interface back to DHCP, set it back to VLAN I could use for reinstalling, was about to clear the arp table, and then I noticed something very strange :
	
	Sh arp
	Internet  x.x.x.104        52   a036.9f17.abc0  ARPA   Vlanx

Wait, that is the mac of my IGB interface...  did I miss something ?
	
	ifconfig
	igb0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 13
       	 inet 0.0.0.0 netmask ff000000
       	 ether a0:36:9f:17:ab:c0

so it did do an ARP, did get an IP from DHCP server, but it's simply not registering on the Omnios box...
This means hardware, and drivers are ok!

then I booted the machine using a KNOPPIX os, just to confirm my suspicions about the hardware and got ip x.x.x.104 on IGB0

I think this is something within Omnios , however, would like some pointers where to look

Met vriendelijke groet / With kind regards,



               Floris van Essen

-----Oorspronkelijk bericht-----
Van: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] Namens Floris van Essen ..:: House of Ancients Amstafs ::..
Verzonden: vrijdag 12 december 2014 18:11
Aan: Dan McDonald
CC: omnios-discuss at lists.omniti.com
Onderwerp: Re: [OmniOS-discuss] LACP Omnios , igb and C3750






> On Dec 12, 2014, at 11:49 AM, Floris van Essen ..:: House of Ancients Amstafs ::.. <info at houseofancients.nl> wrote:
> 
> Hi Dann,
> 
> No problem, just happy you did :-)
> 
> Right, so as might remember I had to reinstall because I was running 
> bloody R11 , but there was a problem upgrading , so just did a fresh install Had to skip r12 because I simply couldn't install it, as there was a installer issue with r12...

>> Weird.  I JUST updated the 012 install media thanks to illumos #5421, so you may want to try that again.

Did the installation 2 weeks ago, so guessing that that was before you did the changes.
No problem, I'll update to stable next release :-)

> So here we are again, running bloody r13 , fully updated :-)
> 
> # 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  up       yes   1G-f                            bi
> igb1            current  up       yes   1G-f                            bi
> igb2            current  up       yes   1G-f                            bi
> igb3            current  up       yes   1G-f                            bi
> # 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   up       --         --
> igb1        phys      1500   up       --         --
> igb2        phys      1500   up       --         --
> igb3        phys      1500   up       --         --

>>Tis all looks sane.  You're showing 1Gig, full dupliex, and up.  This seems sane.

> # 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 x.x.x.255
>        ether 0:30:48:d5:ec:94

And you have no problems pinging x.x.x.0/24 addresses?  Or do you?

Non, actually connecting on that interface with ssh

> igb0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
>        inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
>        ether a0:36:9f:2:c2:6c
> igb1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
>        inet 192.168.0.2 netmask ffffff00 broadcast 192.168.0.255
>        ether a0:36:9f:2:c2:6d
> igb2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
>        inet 192.168.0.3 netmask ffffff00 broadcast 192.168.0.255
>        ether a0:36:9f:2:c2:6e
> igb3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
>        inet 192.168.0.4 netmask ffffff00 broadcast 192.168.0.255
>        ether a0:36:9f:2:c2:6f

>>Now I can totally see some potential confusion here.  You've four addrs all in the same netstack and all with the same prefix.  Now granted, they're different MAC addresses, but packets coming in on one interface may have their return traffic going out >>another.

>>If these are the problem, try using just one (igb0) for starters and "ifconfig igbX down" for 1, 2, and 3.

That is exactly what i did.. for each test brought the others down Just to add, when doing a  SH ARP on my cisco's, don't see the macs popping up, which is even more worring , no arps on a switch usually is very bad news

>>Also, I need to ask --> are either of your e1000g0's shared IPMI/host links?  If so, disable the sharing feature in the BIOS.  We don't cope with shared-with-IPMI NICs.

They are not... besides.. the e1000G's ( and their aggr) are working fully as expected.
To make it more interesting.. this was the same setup as I had on r11 , and then it did seem to work 100%

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
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
...:: House of Ancients ::...
American Staffordshire Terriers

+31-628-161-350
+31-614-198-389
Het Perk 48
4903 RB
Oosterhout
Netherlands
www.houseofancients.nl

...:: 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