Quantcast
Channel: Mellanox Interconnect Community: Message List
Viewing all articles
Browse latest Browse all 6211

Re: Mellanox eSwitchd issue on Openstack Kilo?

$
0
0

Hi Martijn,

 

>When you followed the installation Wiki document, did you also configured the SubnetManager through the "Manual OpenSM Configuration" section?

Yes, I copied the document setting like this. And I restarted the opensmd.

[root@xxxx neutron]# cat /etc/opensm/partitions.conf

management=0x7fff,ipoib, sl=0, defmember=full : ALL, ALL_SWITCHES=full,SELF=full;

vlan1=0x1, ipoib, sl=0, defmember=full : ALL;

vlan2=0x2, ipoib, sl=0, defmember=full : ALL;

vlan3=0x3, ipoib, sl=0, defmember=full : ALL;

vlan4=0x4, ipoib, sl=0, defmember=full : ALL;

vlan5=0x5, ipoib, sl=0, defmember=full : ALL;

vlan6=0x6, ipoib, sl=0, defmember=full : ALL;

[root@xxxx neutron]# cat /etc/opensm/opensm.conf

allow_both_pkeys TRUE

------------------------------------------------------------------

The number of vlan is the same as the number of sriov.

 

>Can you also share which HCA you are using?

Sure. Here are the results for ibstat and other hardware information commands.

----------------------------------------------

[root@xxxx neutron]# ibstat

CA 'mlx4_0'

        CA type: MT4103

        Number of ports: 2

        Firmware version: 2.34.5000

        Hardware version: 0

        Node GUID: 0x7cfe9003009b8ae0

        System image GUID: 0x7cfe9003009b8ae3

        Port 1:

                State: Active

                Physical state: LinkUp

                Rate: 56

                Base lid: 63

                LMC: 0

                SM lid: 24

                Capability mask: 0x02514868

                Port GUID: 0x7cfe9003009b8ae1

                Link layer: InfiniBand

        Port 2:

                State: Down

                Physical state: Polling

                Rate: 10

                Base lid: 0

                LMC: 0

                SM lid: 0

                Capability mask: 0x02514868

                Port GUID: 0x7cfe9003009b8ae2

                Link layer: InfiniBand

[root@xxxx neutron]# mst status

MST modules:

------------

    MST PCI module loaded

    MST PCI configuration module loaded

 

MST devices:

------------

/dev/mst/mt4103_pciconf0         - PCI configuration cycles access.

                                   domain:bus:dev.fn=0000:06:00.0 addr.reg=88 data.reg=92

                                   Chip revision is: 00

/dev/mst/mt4103_pci_cr0          - PCI direct access.

                                   domain:bus:dev.fn=0000:06:00.0 bar=0x90700000 size=0x100000

                                   Chip revision is: 00

[root@xxxx neutron]# flint -d /dev/mst/mt4103_pci_cr0 query

Image type:          FS2

FW Version:          2.34.5000

FW Release Date:     28.7.2015

Product Version:     02.34.50.00

Rom Info:            type=PXE version=3.4.521 devid=4103

                     type=UEFI version=14.7.24

Device ID:           4103

Description:         Node             Port1            Port2            Sys image

GUIDs:               7cfe9003009b8ae0 7cfe9003009b8ae1 7cfe9003009b8ae2 7cfe9003009b8ae3

MACs:                                     7cfe909b8ae1     7cfe909b8ae2

VSD:

PSID:                IBM2000110021

[root@xxxx neutron]# lspci |grep Mell

06:00.0 Network controller: Mellanox Technologies MT27520 Family [ConnectX-3 Pro]

06:00.1 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]

06:00.2 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]

06:00.3 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]

06:00.4 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]

06:00.5 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]

06:00.6 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]

--------------------------------

 

It might be a firmware problem(not still up-to-date), but I need a conviction for updating a firmware because the firmware version is fixed by a rule of our project..Though I can make an exception if I have an understandable reason.

 

Thank you and best regards,

Muneyoshi


Viewing all articles
Browse latest Browse all 6211

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>