Oracle Exalogic Elastic Cloud, Руководство пользователя

Страница: 183 / 342

-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- Discovering ... 2 nodes (1 Switches & 1 CA-s) discovered.
.
.
.
-I- Links With links width != 4x (as set by -lw option)
-I---------------------------------------------------
-I- No unmatched Links (with width != 4x) were found
-I---------------------------------------------------
-I- Links With links speed != 10 (as set by -ls option)
-I---------------------------------------------------
-I- No unmatched Links (with speed != 10) were found
.
.
.
-I- Stages Status Report:
STAGE Errors Warnings
Bad GUIDs/LIDs Check 0 0
Link State Active Check 0 0
Performance Counters Report 0 0
Specific Link Width Check 0 0
Specific Link Speed Check 0 0
Partitions Check 0 0
IPoIB Subnets Check 0 0
Please see /tmp/ibdiagnet.log for complete log
----------------------------------------------------------------
-I- Done. Run time was 1 seconds.
Note:
The actual output for your InfiniBand fabric will differ from that in the
example.
14.6.3 Check for Errors in the InfiniBand Fabric in a Multirack Configuration
Use the
ibcheckerrors
command that uses the topology file to scan the InfiniBand
fabric and validate the connectivity as described in the topology file, and to report
errors as indicated by the port counters.
On the command-line interface (CLI) of the spine switch, enter the following
command:
# ibcheckerrors
## Summary: 4 nodes checked, 0 bad nodes found
## 34 ports checked, 0 ports have errors beyond threshold
Note:
The actual output for your InfiniBand fabric will differ from that in the
example.
Verify the InfiniBand Fabric in a Multirack Configuration
Use the Sun Datacenter InfiniBand Switch 36 in Multirack Configurations 14-7