User Tools

Site Tools


network_stuff:infiniband

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
network_stuff:infiniband [2025/07/07 12:29] jotasandokunetwork_stuff:infiniband [2025/10/03 16:04] (current) jotasandoku
Line 1: Line 1:
 __**INFINIBAND**__: __**INFINIBAND**__:
 +\\
 {{ :network_stuff:infiniband_technical_guide_for_network_engineers.pdf |}} {{ :network_stuff:infiniband_technical_guide_for_network_engineers.pdf |}}
 \\ \\
Line 11: Line 12:
   * RDMA provides access to the memory from one computer to the memory of another computer without involving either computer’s operating system. This technology enables high-throughput and low-latency networking with low CPU utilization.   * RDMA provides access to the memory from one computer to the memory of another computer without involving either computer’s operating system. This technology enables high-throughput and low-latency networking with low CPU utilization.
     * Mellanox provides RDMA via the OFED package     * Mellanox provides RDMA via the OFED package
-  * lid : local indentifier (All devices in a subnet have a Local Identifier (LID)). Routing between different subnets is done on the basis of a Global Identifier (GID)+  * **LID** : local indentifier (All devices in a subnet have a Local Identifier (LID)). Routing between different subnets is done on the basis of a **Global Identifier (GID)** 
 +  * GID: Is another identifier but is to route BETWEEN SUBNETS. Contains : Subnet Prefix and a GUID (Global Unique Identifier).
   * NSD (Network Shared Disks): In our context, NSD is the server that connects to the storage via the Mellanox switch. The servers share the NSD's to the clients, creating some sort of distributed logical disk (a bit like the hyperflex technology). Particuartly in our setupm the servers dont share their local disks but they expose the DDN's disks.   * NSD (Network Shared Disks): In our context, NSD is the server that connects to the storage via the Mellanox switch. The servers share the NSD's to the clients, creating some sort of distributed logical disk (a bit like the hyperflex technology). Particuartly in our setupm the servers dont share their local disks but they expose the DDN's disks.
-  * SM (Subnet Manager):  It performs the InfiniBand specification's required tasks for initializing InfiniBand hardware. One SM must be running for each InfiniBand subnet. It's run by the OpenSM daemon which can run bith in the switches and  the servers+  * **SM (Subnet Manager):**  It performs the InfiniBand specification's required tasks for initializing InfiniBand hardware. One SM must be running for each InfiniBand subnet. It's run by the OpenSM daemon which can run bith in the switches and  the servers
     * SM master is the node truly acting as SM. The node with the highest priority [0-15] wins.     * SM master is the node truly acting as SM. The node with the highest priority [0-15] wins.
     * In our setup, servers all have priority 14 while switch has priority 15.     * In our setup, servers all have priority 14 while switch has priority 15.
Line 33: Line 35:
      
 Useful server side ib commands Useful server side ib commands
-  ibstatus  # server infiniband (ib) interfaces status+  ibstatus  # server infiniband (ib) interfaces status + HCA model 
 +  ibping -S -L 10  ---- ibping -L 20 -c 10 -n 3     # to ping, we need to run one in the server (LID 20) and one in the client (LID 10). This is because even ping makes RDMA calls
  
  
Line 44: Line 47:
  
 Tshoot commands: Tshoot commands:
-  show ib smnodes+  show ib smnodes    # also smquery can be useful for information about the SM itself.
   show ib smnode nyzsfsll51 sm-state   show ib smnode nyzsfsll51 sm-state
   show guids   # so we can identify the macs   show guids   # so we can identify the macs
network_stuff/infiniband.1751891369.txt.gz · Last modified: by jotasandoku