search for: ib0

...ting this to work properly within XCP virtual machines. This is what happens: Starting out I have 2 nodes in a pool; both are clean with only lo, eth0/xenbr0 and eth1/xenbr1 configured. I run the following commands to add the IB NICs to the pool: xe pif-scan host-uuid=NODE1 xe pif-plug uuid=NODE1_IB0 xe pif-scan host-uuid=NODE2 xe pif-plug uuid=NODE2_IB0 As expected this adds ib0/brib0 on both nodes and a single pool-wide network, but there is no connectivity between the hosts after I give brib0 an IP: xe pif-reconfigure-ip uuid=NODE1_IB0 IP=10.1.2.2 netmask=255.255.255.0 mode=static xe pif-r...

...t of sles11 kernel 2.6.27 + Lustre 1.8.3 + ofed 1.4.2 right, because it allows me to see and use the infiniband fabric, and because ko2iblnd loads without any complaints. In /etc/modprobe.d/lustre (this is a Debian system, hence this subdir of modprobe-configs), I have > options ip2nets="o2ib0 192.168.0.[1-5]" I load lnet and do ''lctl network up'', but then ''lctl list_nids'' will invariably give me only > 192.168.0.1 at tcp no matter how I twist the modprobe-config (ip2nets="o2ib", network="o2ib", network="o2ib(ib0), etc....

...hoses the NID (a) with the fewest hops (to minimize routing) and (b) appearing first in the "networks" or "ip2nets" LNET configuration strings. Now consider a 2-rail IB cluster running the OFA stack (i.e. OFED) with the following IPoIB address assignments... ib0 ib1 Servers 192.168.0.* 192.168.1.* Clients 192.168.[2-127].* 192.168.[128-253].* ...here are some different configurations you could create... A. I''ve got many more clients than servers in my cluster. I don''t care if an individual client...

...ot: SMB signing is mandatory and the server doesn't support it. protocol negotiation failed: NT_STATUS_ACCESS_DENIED $ smbclient -V Version 3.6.23-12.el5_11 $ uname -a Linux YYYY 2.6.18-409.el5 #1 SMP Tue Mar 15 18:13:50 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux $ smbpasswd -D3 added interface ib0 ip=:::::%ib0 bcast=::ffff:ffff:ffff:ffff%ib0 netmask=ffff:ffff:ffff:ffff:: added interface eth2 ip=:::::%eth2 bcast=::ffff:ffff:ffff:ffff%eth2 netmask=ffff:ffff:ffff:ffff:: added interface eth1 ip=:::::fe%eth1 bcast=::ffff:ffff:ffff:ffff%eth1 netmask=ffff:ffff:ffff:ffff:: added interface ib0 ip=...

...so-good performance I"m getting, I don't realistically know if I'm in the right ballfield. It seems to me, that with so many mellanox cards out there, and so many users of CentOS 6.x, there might be someone who has gotten good performance and who might be willing to publish the ifcfg-ib0 or whatever mechanism, combined with volume tunings. As another question -- it looks to me that if you use those Mellanox VNICS, you're limited to small MTU -- is that correct? Thanks to everyone in this community. --- still just getting started... Matt Temple ------ Matt Temple Director, R...

...17 2008 Subject: Re: [Lustre-discuss] Multihomed question: want Lustre over IB andEthernet On Fri, Mar 7, 2008 at 9:39 AM, Craig Prescott <prescott at hpc.ufl.edu> wrote: > > I think your client modprobe.conf lnet option > should be this: > > > options lnet networks=o2ib(ib0) > > (not ''o2ib0''). It still seems to want the TCP connection: Lustre: Added LNI 36.122.255.1 at o2ib [8/64] Lustre: Lustre Client File System; info at clusterfs.com LustreError: 11043:0:(events.c:401:ptlrpc_uuid_to_peer()) No NID found for 36.121.255.201 at tcp LustreErr...

...d started a single node up by hand, then tried to add a public address as follows: [root at gp-1-0 ctdb]# ctdb ip Public IPs on node 0 [root at gp-1-0 ctdb]# ctdb ip -Y :Public IP:Node:ActiveInterface:AvailableInterfaces:ConfiguredInterfaces: [root at gp-1-0 ctdb]# ctdb addip 192.168.5.151/24 ib0 2014/05/20 06:44:31.202611 [180506]: client/ctdb_client.c:2184 ctdb_control for takeover_ip failed 2014/05/20 06:44:31.202746 [180506]: Failed to take over IP on node 0 2014/05/20 06:44:31.202762 [180506]: Failed to move ip to node 0 [root at gp-1-0 ctdb]# ctdb ip -Y :Public IP:Node:ActiveInte...

...sn't support it. > protocol negotiation failed: NT_STATUS_ACCESS_DENIED > > $ smbclient -V > Version 3.6.23-12.el5_11 > $ uname -a > Linux YYYY 2.6.18-409.el5 #1 SMP Tue Mar 15 18:13:50 EDT 2016 x86_64 > x86_64 x86_64 GNU/Linux > > $ smbpasswd -D3 > added interface ib0 ip=:::::%ib0 bcast=::ffff:ffff:ffff:ffff%ib0 > netmask=ffff:ffff:ffff:ffff:: > added interface eth2 ip=:::::%eth2 bcast=::ffff:ffff:ffff:ffff%eth2 > netmask=ffff:ffff:ffff:ffff:: > added interface eth1 ip=:::::fe%eth1 bcast=::ffff:ffff:ffff:ffff%eth1 > netmask=ffff:ffff:ffff:ffff:: &...

We have a new install of CentOS 6.7 with infiniband support installed. We can see the card in hardware and we can see the mlx4 drivers loaded in the kernel but cannot see the card as an ethernet interface, using ifconfig -a. Can you recommend an install procedure to see this as an ethernet interface? Thanks On 05/25/2016 07:32 AM, Fabian Arrotin wrote: > On 25/05/16 03:08, Pat Haley

...own to module ko2iblnd, which I attempt to remove first (added to PRE_UNLOAD_MODULES in /etc/init.d/openibd), but it doesn''t work. Strangely, in "lsmod" the use count of the module is one, but I don''t see where it''s used. # umount /mnt/lustre # ifconfig ib0 down # modprobe -r ko2iblnd FATAL: Module ko2iblnd is in use. # lsmod | grep ko2 ko2iblnd 143136 1 lnet 258088 5 lustre,ksocklnd,ko2iblnd,ptlrpc,obdclass libcfs 189784 12 osc,mgc,lustre,lov,lquota,mdc,ksocklnd,ko2iblnd,ptlrpc,obdclass,lnet,lvf s rd...

Greetings! I am working with Lustre-2.1.2 on RHEL 6.2. First I configured it using the standard defaults over TCP/IP. Everything worked very nicely usnig a real, static --mgsnode=a.b.c.x value which was the actual IP of the MGS/MDS system1 node. I am now trying to integrate it with Pacemaker-1.1.7. I believe I have most of the set-up completed with a particular exception. The "lctl

...tcp? A little more info about the setup: we've got 10 storage nodes/bricks, each of which has a single 1GB NIC and a FRD IB port. Likewise for the test clients. Now, the 1GB nic is for management only, and we have all of the systems on this fabric configured with IPoIB, so there is eth0, and ib0 on each node. All storage nodes are peer'd using the ib0 interface, ie: gluster peer probe storage_node01-ib etc thats all well and good. Volume was created: gluster volume create holyscratch transport rdma,tcp holyscratch01-ib:/holyscratch01/brick for i in `seq -w 2 10` ; do gluster volum...

...% I have put the packet captures in http://mseas.mit.edu/download/phaley/GlusterUsers/TestNFSmount/ capture_nfsfail.pcap has the results from the failed touch experiment capture_nfssucceed.pcap has the results from the successful touch experiment The command I used for these was tcpdump -i ib0 -nnSs 0 host 172.16.1.119 -w /root/capture_nfstest.pcap The brick log files are also in the above link. If I read them correctly they both funny times. Specifically I see entries from around 2017-06-27 14:02:37.404865 even though the system time was 2017-06-27 12:00:00. One final item, anot...

...http://mseas.mit.edu/download/phaley/GlusterUsers/TestNFSmount/ > > capture_nfsfail.pcap has the results from the failed touch experiment > capture_nfssucceed.pcap has the results from the successful touch > experiment > > The command I used for these was > > tcpdump -i ib0 -nnSs 0 host 172.16.1.119 -w /root/capture_nfstest.pcap > > The brick log files are also in the above link. If I read them > correctly they both funny times. Specifically I see entries from > around 2017-06-27 14:02:37.404865 even though the system time was > 2017-06-27 12:00:0...

On 06/27/2017 10:17 AM, Pranith Kumar Karampuri wrote: > The only problem with using gluster mounted via NFS is that it does not > respect the group write permissions which we need. > > We have an exercise coming up in the a couple of weeks. It seems to me > that in order to improve our write times before then, it would be good > to solve the group write permissions for gluster

...phaley/GlusterUsers/TestNFSmount/ >> >> capture_nfsfail.pcap has the results from the failed touch experiment >> capture_nfssucceed.pcap has the results from the successful touch >> experiment >> >> The command I used for these was >> >> tcpdump -i ib0 -nnSs 0 host 172.16.1.119 -w /root/capture_nfstest.pcap I hope these pkts were captured on the node where NFS server is running. Could you please use '-i any' as I do not see glusterfs traffic in the tcpdump. Also looks like NFS v4 is used between client & nfs server. Are you using...

.../ >>> >>> capture_nfsfail.pcap has the results from the failed touch experiment >>> capture_nfssucceed.pcap has the results from the successful touch >>> experiment >>> >>> The command I used for these was >>> >>> tcpdump -i ib0 -nnSs 0 host 172.16.1.119 -w /root/capture_nfstest.pcap > > I hope these pkts were captured on the node where NFS server is > running. Could you please use '-i any' as I do not see glusterfs > traffic in the tcpdump. > > Also looks like NFS v4 is used between client &amp...

...m the failed touch >>>>> experiment >>>>> capture_nfssucceed.pcap has the results from the successful touch >>>>> experiment >>>>> >>>>> The command I used for these was >>>>> >>>>> tcpdump -i ib0 -nnSs 0 host 172.16.1.119 -w >>>>> /root/capture_nfstest.pcap >>> >>> I hope these pkts were captured on the node where NFS server is >>> running. Could you please use '-i any' as I do not see glusterfs >>> traffic in the tcpdump. >>...

...level hardware support loaded: ??????? mlx4_ib Upper layer protocol modules: ??????? ib_ipoib User space access modules: ??????? rdma_ucm ib_ucm ib_uverbs ib_umad Connection management modules: ??????? rdma_cm ib_cm iw_cm Configured IPoIB interfaces: none Currently active IPoIB interfaces: ib0

...container with access to a Infiniband card with IP over IB. I have scripts written to create the device in the container and add all the proper cgroup permissions on the host. I can access the card from the container, but there is no Infiniband network device present. I can't create the ib0 and ib1, and I have come to believe this is because they are made on the host when the modules are inserted. Is inserting modules possible with lxc and libvirt? Is it currently possible to use IP over IB in any of the virtualization technologies that libvirt supports? I'm not bound to lxc...