Tom Ammon wrote:
Eli,
Is there a quick workaround we could put in place? I want to map out our
fabric, and I especially need the spine GUIDs on the GD4200 because I'm
going to be doing up/down routing and want to specify the root GUIDs. I
can also submit a support case to Voltaire, if you
Hi Tom,
On 16:14 Wed 08 Dec , Tom Ammon wrote:
Is there a quick workaround we could put in place? I want to map out our
fabric, and I especially need the spine GUIDs on the GD4200 because I'm
going to be doing up/down routing and want to specify the root GUIDs. I
can also submit a
Hi,
I get the following when I try to run ibnetdiscover from a server
plugged in to a voltaire 4036 switch. We're using OFED 1.5.2:
[r...@sm1 ~]# ibnetdiscover
src/chassis.c:535; Unexpected node found: guid 0x0008f1050075134c
ibnetdiscover: iberror: failed: discover failed
However,
Hi Tom,
On 12/8/2010 12:48 PM, Tom Ammon wrote:
Hi,
I get the following when I try to run ibnetdiscover from a server
plugged in to a voltaire 4036 switch. We're using OFED 1.5.2:
[r...@sm1 ~]# ibnetdiscover
src/chassis.c:535; Unexpected node found: guid 0x0008f1050075134c
ibnetdiscover:
Eli,
Is there a quick workaround we could put in place? I want to map out our
fabric, and I especially need the spine GUIDs on the GD4200 because I'm
going to be doing up/down routing and want to specify the root GUIDs. I
can also submit a support case to Voltaire, if you think that would
Hi Hal,
On 13:27 Wed 25 Aug , Hal Rosenstock wrote:
I'm seeing an issue with ibnetdiscover from a CA port where it appears
to extend a path at a remote CA port (it's actually another port on
the same CA) to query NodeInfo of the next hop beyond it. I get the
following error message:
Hi Sasha,
On Wed, Sep 1, 2010 at 9:43 AM, Sasha Khapyorsky sas...@voltaire.com wrote:
Hi Hal,
On 13:27 Wed 25 Aug , Hal Rosenstock wrote:
I'm seeing an issue with ibnetdiscover from a CA port where it appears
to extend a path at a remote CA port (it's actually another port on
the same
On 09:47 Wed 01 Sep , Hal Rosenstock wrote:
I thought this used to work and those changes looked related to me.
Maybe the fix is right but that part of the problem description isn't.
Do you want a revised patch without that part of the description ?
No needs - I applied this already.
Sasha,
I'm seeing an issue with ibnetdiscover from a CA port where it appears
to extend a path at a remote CA port (it's actually another port on
the same CA) to query NodeInfo of the next hop beyond it. I get the
following error message:
src/query_smp.c:188; umad (DR path slid 0; dlid 0;
