MAC Address Mania

Status
Not open for further replies.

survive

Behold the Wumpus
Moderator
Joined
May 28, 2011
Messages
875
Hi guys,

My filer has a pair of Intel NIC on-board and I've added a dual port Intel NIC to to give me a total of 4 "em" gig-e interfaces. The card boots in the system and everything looks ok, but upon further inspection I noticed ther's something funny going on. In "dmesg" I can see all 4 interfaces and each one has a proper distinct MAC address:

Code:
em0: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xf020-0xf03f mem 0xf7900000-0xf791ffff,0xf7925000-0xf7925fff irq 20 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:25:90:74:dd:af
em1: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xd020-0xd03f mem 0xf7f60000-0xf7f7ffff,0xf7f40000-0xf7f5ffff irq 16 at device 0.0 on pci3
em1: Using an MSI interrupt
em1: [FILTER]
em1: Ethernet address: 00:15:17:29:14:96
em2: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xd000-0xd01f mem 0xf7f20000-0xf7f3ffff,0xf7f00000-0xf7f1ffff irq 17 at device 0.1 on pci3
em2: Using an MSI interrupt
em2: [FILTER]
em2: Ethernet address: 00:15:17:29:14:97
em3: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xc000-0xc01f mem 0xf7e00000-0xf7e1ffff,0xf7e20000-0xf7e23fff irq 16 at device 0.0 on pci4
em3: Using MSIX interrupts with 3 vectors
em3: [ITHREAD]
em3: [ITHREAD]
em3: [ITHREAD]
em3: Ethernet address: 00:25:90:74:dd:ae


But once it's up and I do an "ifconfig" I see that em0 & em1 have the same MAC address!

Code:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
        ether 00:25:90:74:dd:af  <----The same as em1
        inet6 fe80::225:90ff:fe74:ddaf%em0 prefixlen 64 scopeid 0x1 
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether 00:25:90:74:dd:af <----The same as em0
        inet6 fe80::215:17ff:fe29:1496%em1 prefixlen 64 scopeid 0x3 
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet autoselect
        status: no carrier
em2: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether 00:15:17:29:14:97
        media: Ethernet autoselect
        status: no carrier
em3: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
        ether 00:25:90:74:dd:ae
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active


The only thing I notice is that em3 is using MSIX interrupts (em0 & em3 are on-board) while the other 3 report MSI interrupts.

Anybody have any suggestions or thoughts about whats going on here?

-Will
 

paleoN

Wizard
Joined
Apr 22, 2012
Messages
1,403
Not really. You aren't or haven't run these in a LAGG have you?
 

survive

Behold the Wumpus
Moderator
Joined
May 28, 2011
Messages
875
Hi paleoN,

Indeed, it was the lagg I had set up. It's all sorted out now.

-Will
 
Status
Not open for further replies.
Top