Re: Same MAC address in 2 different VLANs

2013-07-24 Thread Olivier Nicole
> I think you maybe ok. Ive just looked at my esx config and the esx > management interfaces use their own generated macs, not the physical > interfaces ones. All the vms obviously use generated macs as well. > > However I only looked over it at a superficial level. > > Have you considered using a

Re: bce(4) panics, 9.2rc1

2013-07-24 Thread Steven Hartland
- Original Message - From: "Sean Bruno" As a guess its likely the interrupt handler is triggering while the watchdog timeout handler is re-initialising the card so you inconsitent state resulting in the crash. In from /var/crash should help determine the cause and confirm / deny that.

Re: kern/180791: [ofed] [patch] Kernel crash on ifdown and kldunload mlxen

2013-07-24 Thread linimon
Old Synopsis: Kernel crash on ifdown and kldunload mlxen New Synopsis: [ofed] [patch] Kernel crash on ifdown and kldunload mlxen Responsible-Changed-From-To: freebsd-amd64->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Jul 24 21:48:47 UTC 2013 Responsible-Changed-Why:

Re: bce(4) panics, 9.2rc1

2013-07-24 Thread hiren panchasara
On Wed, Jul 24, 2013 at 2:23 PM, Sean Bruno wrote: > On Wed, 2013-07-24 at 14:07 -0700, Sean Bruno wrote: >> Running 9.2 in production load mail servers. We're hitting the >> "watchdog" message and crashing with the stable/9 version. We're >> reverting the change from 2 weeks ago and seeing if i

Re: bce(4) panics, 9.2rc1

2013-07-24 Thread Sean Bruno
On Wed, 2013-07-24 at 14:07 -0700, Sean Bruno wrote: > Running 9.2 in production load mail servers. We're hitting the > "watchdog" message and crashing with the stable/9 version. We're > reverting the change from 2 weeks ago and seeing if it still happens. > We didn't see this from stable/9 from

bce(4) panics, 9.2rc1

2013-07-24 Thread Sean Bruno
Running 9.2 in production load mail servers. We're hitting the "watchdog" message and crashing with the stable/9 version. We're reverting the change from 2 weeks ago and seeing if it still happens. We didn't see this from stable/9 from about a month ago. Sean ref: http://svnweb.freebsd.org/ba

Recommendations for 10gbps NIC

2013-07-24 Thread Boris Kochergin
Hi. I am looking for recommendations for a 10gbps NIC from someone who has successfully used it on FreeBSD. It will be used on FreeBSD 9.1-R/amd64 to capture packets. Some desired features are: - PCIe - LC connectors - 10GBASE-SR - Either single- or dual-port - Multiqueue Specific part numbe

RE: kern/180430: [ofed] [patch] Bad UDP checksum calc for fragmented packets

2013-07-24 Thread Meny Yossefi
The following reply was made to PR kern/180430; it has been noted by GNATS. From: Meny Yossefi To: John Baldwin Cc: "bug-follo...@freebsd.org" Subject: RE: kern/180430: [ofed] [patch] Bad UDP checksum calc for fragmented packets Date: Wed, 24 Jul 2013 13:14:53 + --_000_F2E47A38E4D0B9499D

Re: How can I remove one interface from lagg, without destroying all lagg?

2013-07-24 Thread Jason Hellenthal
Use -laggport portN -- Jason Hellenthal Inbox: jhellent...@dataix.net Voice: +1 (616) 953-0176 JJH48-ARIN On Jul 24, 2013, at 5:14, Alex Liptsin wrote: > Hi. > > I have lagg interface created on my server: > > [root@h-qa-094 ~]$ ifconfig lagg0 > lagg0: flags=8802 metric 0 mtu 1500 >

Re: How can I remove one interface from lagg, without destroying all lagg?

2013-07-24 Thread Maciej Milewski
On 24.07.2013 11:14, Alex Liptsin wrote: Hi. I have lagg interface created on my server: [root@h-qa-094 ~]$ ifconfig lagg0 lagg0: flags=8802 metric 0 mtu 1500 options=401bb ether 00:02:c9:19:82:80 nd6 options=21 media: Ethernet autoselect status: ac

How can I remove one interface from lagg, without destroying all lagg?

2013-07-24 Thread Alex Liptsin
Hi. I have lagg interface created on my server: [root@h-qa-094 ~]$ ifconfig lagg0 lagg0: flags=8802 metric 0 mtu 1500 options=401bb ether 00:02:c9:19:82:80 nd6 options=21 media: Ethernet autoselect status: active laggproto failover lagghash l2,l3,l