***SPAM*** Re: [ofa-general] opensm: bad multicast forwarding table entries

Hal Rosenstock hal.rosenstock at gmail.com
Wed Nov 12 18:08:09 PST 2008


On Wed, Nov 12, 2008 at 7:39 PM, Sasha Khapyorsky <sashak at voltaire.com> wrote:
> On 15:54 Wed 12 Nov     , akepner at sgi.com wrote:
>> > .....
>> > > So far, so good. But we also have r4i2n10, connected to the switch with
>> > > lid 1533 port 7:
>> > >
>> > > switchguid=0x800690000002e50(800690000002e50)
>> > > Switch  24 "S-0800690000002e50"         # "MT47396 Infiniscale-III Mellanox Technologies" base port 0 lid 1533 lmc 0
>> > > ......
>> > > [7]     "H-003048c2438a0000"[1](3048c2438a0001)                 # "r4i2n10 HCA-1" lid 771 4xDDR
>> > >
>> > > with this mft entry:
>> > >
>> > > Multicast mlids [0xc000-0xc3ff] of switch Lid 1533 guid 0x0800690000002e50 (MT47396 Infiniscale-III Mellanox Technologies):
>> > >            0                   1                   2
>> > >     Ports: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
>> > >  MLid
>> > > .....
>> > > 0xc069                    x
>> > >
>> > > Any idea why "r4i2n10", with PortGid fe80::3048c2438a0001 would have a
>> > > mft entry for the multicast group with MGID ff12601bffff::1ff26d289?
>
> Any chance that port "r4i2n10" joins MGID ff12601bffff::1ff26d289 as
> non-member?

Wouldn't saquery -m show this member too ? Arthur said there was only
1 member indicated.

-- Hal

> You can run OpenSM with -V flag and track all joins.
>
> Sasha
>



More information about the general mailing list