Documentation, Support, and Training
Network Management Connector and Pins
USB Management Connector and Pins
Preparing to Install the Gateway
Suggested Tools for Installation
Antistatic Precautions for Installation
Verify Shipping Carton Contents
Assemble the Ethernet Splitter Data Cables
Install the Gateway in the Rack
Verifying the InfiniBand Fabric
Understanding Routing Through the Gateway
Understanding Administrative Commands
Administering the I4 Switch Chip
Controlling the I4 Switch Chip
Administering Gateway Resources
Installing Gateway Supportive Software
Creating VNICs Under Gateway Manual Mode
Creating VNICs Under Host Manual Mode
Controlling Gateway Ports and Parameters
Administering the InfiniBand Fabric
Monitoring the InfiniBand Fabric
Controlling the InfiniBand Fabric
Administering the Subnet Manager
Controlling the Subnet Manager
Understanding Oracle ILOM on the Gateway
Understanding Oracle ILOM Targets
Administering Oracle ILOM (CLI)
Accessing Oracle ILOM From the CLI
Switching Between the Oracle ILOM Shell and the Linux Shell
Monitoring Oracle ILOM Targets (CLI)
Controlling Oracle ILOM Targets (CLI)
Upgrading the Gateway Firmware Through Oracle ILOM (CLI)
Administering Oracle ILOM (Web)
Access Oracle ILOM From the Web Interface
Monitoring Oracle ILOM Targets (Web)
Controlling Oracle ILOM Targets (Web)
Upgrade the Gateway Firmware (Web)
Accessing the Rear Panel Diagram
Accessing Status Pane Information
Monitoring Parameters and Status
Administering Oracle ILOM (SNMP)
Monitoring Oracle ILOM Targets (SNMP)
Controlling Oracle ILOM Targets (SNMP)
Display the Sensor States (IPMI)
Display the Sensor Information (IPMI)
Display the System Event Log (IPMI)
Display FRU ID Information (IPMI)
Display Gateway Status LED States (IPMI)
Disable the Locator LED (IPMI)
Understanding Oracle ILOM Commands
Understanding Service Procedures
Antistatic Precautions for Service
Remove the Gateway From the Rack
Understanding Hardware Commands
Linux Shells for Hardware Commands
Understanding InfiniBand Commands
Linux Shells for InfiniBand Commands
Understanding the SUN-DCS-MIB MIB OIDs
Understanding the SUN-ILOM-CONTROL-MIB MIB OIDs
Understanding the SUN-PLATFORM-MIB MIB OIDs
Traces the InfiniBand fabric diagnostic path.
ibdiagpath -n[src_name,]dst_name|-l[src_lid,]dst_lid|-d p1,p2,p3,...[-c count][-v][-o outputdir][-t topology][-s system][-i device][-p port][-wt topology][-pm][-pc][-P PM = value][-lw 1x|4x|12x][-ls 2.5|5|10][-h][-V]
where:
src_name is the source port.
dst_name is the destination port.
src_lid is the source LID.
dst_lid is the destination LID.
p1,p2,p3,... is the directed route.
count is the number of packets.
outputdir is the output directory.
topology is the topology file.
system is the local system name.
device is the index of the device connecting to the InfiniBand fabric.
port is the port of the device.
PM is the Performance Manager counter number.
value is the threshold of the Performance Manager counter.
This InfiniBand command traces a path between two endpoints and provides information regarding the nodes and ports traversed along the path. The command uses device-specific health queries for the different devices encountered. The way the ibdiagpath command operates is determined from the addressing mode specified on the command line:
If directed route addressing is used, the local node is the source node and the route to the destination port is known.
If LID route addressing is used, the source and destination ports of a route are specified by their LIDs.
In LID route addressing, the actual path from the local port to the source port, and from the source port to the destination port, is defined by means of Subnet Management Linear Forwarding Table queries of the switch nodes along those paths.
Note - When the ibdiagpath command queries the performance counters along the path between the source and destination ports, the command always traverses the LID route, regardless of whether a directed route is specified. If one or more links along the LID route are not in the Active state, the ibdiagpath command reports an error.
This command produces a set of files in the output directory. By default, the output directory is /tmp. The following table describes the files.
|
The following table describes the options to the ibdiagpath command and their purposes:
|
The following example shows how to display the route from LID 15 to LID 14 with the ibdiagpath command.
Note - The output for your InfiniBand fabric will differ from that in the example.
# ibdiagpath -l 14,15 Loading IBDIAGPATH from: /usr/lib/ibdiagpath1.2 -W- Topology file is not specified. Reports regarding cluster links will use direct routes. Loading IBDM from: /usr/lib/ibdm1.2 -I- Using port 0 as the local port. -I--------------------------------------------------- -I- Traversing the path from local to source -I--------------------------------------------------- -I- From: lid=0x000f guid=0x0021283a8389a0a0 dev=48438 Port=23 -I- To: lid=0x000e guid=0x0003ba000100e38a dev=26428 mnm33-43/P2 -I--------------------------------------------------- -I- Traversing the path from source to destination -I--------------------------------------------------- -I- From: lid=0x000e guid=0x0003ba000100e38a dev=26428 mnm33-43/P2 -I- To: lid=0x000f guid=0x0021283a8389a0a0 dev=48438 Port=23 -I--------------------------------------------------- -I- PM Counters Info -I--------------------------------------------------- -I- No illegal PM counters values were found -I--------------------------------------------------- -I- Path Partitions Report -I--------------------------------------------------- -I- Source mnm33-43/P2 lid=0x000e guid=0x0003ba000100e38a dev=26428 Port 2 PKeys:0xffff -I- Destination lid=0x000f guid=0x0021283a8389a0a0 dev=48438 PKeys:0xffff -I- Path shared PKeys: 0xffff -I--------------------------------------------------- -I- IPoIB Path Check -I--------------------------------------------------- -I- Subnet: IPv4 PKey:0x7fff QKey:0x00000b1b MTU:2048Byte rate:10Gbps SL:0x00 -I--------------------------------------------------- -I- QoS on Path Check -I--------------------------------------------------- -I- The following SLs can be used:0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ---------------------------------------------------------------- -I- Stages Status Report: STAGE Errors Warnings LFT Traversal: local to source 0 0 LFT Traversal: source to destination 0 0 Performance Counters Report 0 0 Path Partitions Check 0 0 Path IPoIB Check 0 0 QoS on Path Check 0 0 Please see /tmp/ibdiagpath.log for complete log ---------------------------------------------------------------- -I- Done. Run time was 0 seconds. #
ibdiagpath man page