Map Lids To Guids - Oracle Exalogic Elastic Cloud Owner's Manual

RespTimeVal:.....................0
LocalPhysErr:....................8
OverrunErr:......................8
MaxCreditHint:...................85
RoundTrip:.......................16777215
#

15.1.10 Map LIDs to GUIDs

In the InfiniBand fabric in Exalogic machines, as a Subnet Manager and Subnet
administrator, you may want to assign subnet-specific LIDs to nodes in the fabric.
Often in the use of the InfiniBand commands, you must provide an LID to issue a
command to a particular InfiniBand device.
Alternatively, the output of a command might identify InfiniBand devices by their
LID. You can create a file that is a mapping of node LIDs to node GUIDs, which can
help with administrating your InfiniBand fabric.
The following procedure creates a file that lists the LID in hexadecimal, the GUID in
hexadecimal, and the node description:
Create an inventory file:
1.
# osmtest -f c -i inventory.txt
The inventory.txt file can be used for other purposes too, besides this
procedure.
Create a mapping file:
2.
# cat inventory.txt |grep -e '^lid' -e 'port_guid' -e 'desc'
|sed 's/^lid/\nlid/'> mapping.txt
Edit the latter half of the mapping.txt file to remove the nonessential
3.
information. The content of the mapping.txt file looks similar to the following:
lid 0x14
port_guid 0x0021283a8620b0a0
# node_desc Sun DCS 72 QDR switch 1.2(LC)
lid 0x15
port_guid 0x0021283a8620b0b0
# node_desc Sun DCS 72 QDR switch 1.2(LC)
lid 0x16
port_guid 0x0021283a8620b0c0
# node_desc Sun DCS 72 QDR switch 1.2(LC)
Note:
The actual output for your InfiniBand fabric will differ from that in the
example, and it is just a portion of the full output.
Note:
Creation of the mapping file is not a requirement for InfiniBand
administration.
Monitor the InfiniBand Fabric
Monitor and Control the InfiniBand Fabric 15-7