Table Of Contents
InfiniBand Tasks
Viewing Subnet Managers
Viewing Subnet Manager Properties
Adding a Subnet Manager
Deleting a Subnet Manager
Configuring Subnet Manager Properties
Viewing InfiniBand Services
Viewing InfiniBand Service Properties
Viewing InfiniBand Nodes
Viewing Node Properties
Viewing Node Ports
Viewing Node Neighbors
Viewing InfiniBand Ports
Viewing InfiniBand Port Properties
Viewing Neighboring InfiniBand Devices
Viewing InfiniBand Neighbor Properties
Viewing IOUs
Viewing IOCs
Viewing IOC Properties
Viewing IOC Services
Viewing Properties of IOC Services
InfiniBand Tasks
This chapter describes the Chassis Manager InfiniBand tasks and contains these sections:
•
Viewing Subnet Managers
•Viewing InfiniBand Services
•Viewing InfiniBand Nodes
•Viewing InfiniBand Ports
•Viewing Neighboring InfiniBand Devices
•Viewing IOUs
•Viewing IOCs
•Viewing IOC Services
Viewing Subnet Managers
The subnet managers display in Chassis Manager provides an abridged version of the output of the show ib sm CLI command. To view the subnet managers in your InfiniBand fabric, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Select the Subnet Managers branch.
The Subnet Managers table appears in the View frame. Table 5-1 describes the fields in the Subnet Managers table.
Table 5-1 Subnet Managers Table Field Descriptions
Field
|
Description
|
Subnet Prefix
|
64-bit value that identifies the InfiniBand subnet.
|
GUID
|
GUID of the Server Switch.
|
Oper-Status
|
Displays the operating status (oper-status) of the SM.
|
Viewing Subnet Manager Properties
To view Subnet Manager properties, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Select the Subnet Managers branch.
The Subnet Managers table appears in the View frame.
Step 3 Click the radio button next to the subnet manager that you want to view, and then click Properties.
The Subnet Manager Properties window opens. Table 5-2 describes the fields in this window.
Table 5-2 Subnet Manager Properties Window Fields
Field
|
Description
|
Subnet Prefix
|
Displays the subnet prefix of the subnet manager.
|
GUID
|
Displays the GUID of the networking device on which the Subnet Manager runs.
|
Status
|
Status of the subnet manager. It may appear as master, standby, inactive, or discovery.
|
Activity Count
|
Activity counter that increments each time that the subnet manager sends a subnet management packet (SMP) or performs other management activities.
|
SM Key
|
Subnet Manager Verification Key is used by the master Subnet Manager to authenticate other master and standby Subnet Managers. Subnet Manager Key is also used in SA query handling to ensure a request is from a trusted source. Note that Subnet Manager Key is not enforced in release 2.7.0.
|
Priority
|
Priority of the Subnet Manager relative to other Subnet Managers in the InfiniBand network. The higher the number, the greater the priority.
|
Sweep Interval
|
Specifies how frequently the Subnet Manager queries the InfiniBand fabric for network changes.
|
Response Timeout
|
Timeout interval that the Subnet Manager waits before resending a MAD.
|
Master Poll Interval
|
Interval at which a standby Subnet Manager polls the master to see if it is still running.
|
Master Poll Retries
|
Number of unanswered polls that cause the standby to identify the master as dead.
|
Max Active SMs
|
Maximum number of standby Subnet Managers that the master supports. A value of 0 indicates unlimited Subnet Managers.
|
LID Mask Control
|
Number of path bits present in the base LID to each channel adapter port. Increasing the LMC value increases the number of LIDs assigned to each port to increase the number of potential paths to reach each port.
|
Switch Life Time
|
Life time of a packet inside a Server Switch.
|
Switch Link HoQ Life
|
Life time of a packet at the head-of-queue of a switch port.
|
CA Link HoQ Life
|
Life time of a packet at the head-of-queue of the host port.
|
Maximum Hop Count
|
Maximum number of hops considered by Subnet Manager when calculating routes in a subnet.
|
MadRetries
|
Number of times the Subnet Manager resends a MAD after not receiving a response. The default value is 5.
|
NodeTimeout
|
Minimum amount of time in seconds that a HCA may be unresponsive before the Subnet Manager removes it from the InfiniBand fabric. The default value is 10 seconds.
|
WaitReportResponse
|
Whether or not the Subnet Manager waits to receive ReportResponse MADs in response to the Report MADs that it forwards. This is a boolean value. If set to false, the Subnet Manager only sends the Report MADs once; if set to true, the Subnet Manager will continue to send the Report MADs until either the ReportResponse MAD is received or the maximum number of Report MADs have been sent. The default value is false.
|
SaMadQueueDepth
|
Size of the SA's internal queue for receiving MADs. The default value is 256.
|
Adding a Subnet Manager
To add a subnet manager, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Select the Subnet Managers branch.
The Subnet Managers table appears in the View frame.
Step 3 Click Add.
The Add Subnet Manager window opens.
Step 4 Enter a subnet prefix in the Subnet Prefix field.
Step 5 Assign a priority value (integer) between 0 and 15 in the Priority field. The higher the integer, the higher the priority.
Step 6 (Optional) Enter a key in the Subnet Manager Key field.
Step 7 Click Apply.
Deleting a Subnet Manager
To delete a subnet manager, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Select the Subnet Managers branch.
The Subnet Managers table appears in the View frame.
Step 3 Click the radio button next to the Subnet Manager that you want to delete, and then click Delete.
Step 4 Click OK.
Configuring Subnet Manager Properties
To configure Subnet Manager properties, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Select the Subnet Managers branch.
The Subnet Managers table appears in the View frame.
Step 3 Click the radio button next to the subnet manager that you want to view, and then click Properties.
The Subnet Manager Properties window opens.
To configure optional Subnet Manager properties, follow these steps:
Step 1 (Optional) Enter an integer in the Priority field to configure the priority of the Subnet Manager; the higher the number, the greater the priority.
Step 2 (Optional) Enter an integer (1- 268435455) in the Sweep Interval field to configure the sweep interval, in seconds, of the Subnet Manager.
Step 3 (Optional) Enter an integer (100 - 5000) in the Response Timeout field to configure low long the Subnet Manager waits, in milliseconds, for a response from a connection before it resends a MAD. The default value is 200 milliseconds.
Step 4 (Optional) Enter an integer in the Master Poll Interval field to configure the interval, in seconds, at which the slave Subnet Manager polls the master to see if the master still runs.
Step 5 (Optional) Enter an integer in the Master Poll Retries field to configure the number of unanswered polls that cause the standby to identify the master as dead.
Step 6 (Optional) Enter an integer value in the Max Active Subnet Managers field to configure the maximum number of standby Subnet Managers that the master supports. This value defaults to 0, which indicates unlimited Subnet Managers.
Step 7 (Optional) Enter an integer value in the LID Mask Control field to configure LID mask control on your Subnet Manager.
Step 8 (Optional) Enter an integer value between 0 and 20 in the Switch Life Time field.
Step 9 (Optional) Enter an integer value between 0 and 20 in the Switch Link HoQ Life field.
Step 10 (Optional) Enter an integer (0 - 100) in the MadRetries field to configure the number of times the Subnet Manager resends a MAD after not receiving a response. The default value is 5.
Step 11 (Optional) Enter an integer (1 - 2000) in the NodeTimeout field to configure the minimum amount of time in seconds that a HCA may be unresponsive before the Subnet Manager removes it from the InfiniBand fabric. The default value is 10 seconds.
Step 12 (Optional) Check or uncheck the WaitReportResponse check box to configure whether or not the Subnet Manager waits to receive ReportResponse MADs in response to the Report MADs that it forwards.
This is a boolean value. If set to false, the Subnet Manager only sends the Report MADs once; if set to true, the Subnet Manager will continue to send the Report MADs until either the ReportResponse MAD is received or the maximum number of Report MADs have been sent. The default value is False.
Step 13 (Optional) Enter an integer (256 - 1024) in the SaMadQueueDepth field to configure the size of the SA's internal queue for receiving MADs. The default value is 256.
Step 14 Click Apply to apply your change(s) to your Server Switch.
Viewing InfiniBand Services
Subnet services provide your InfiniBand fabric with various features, such as the ability to run particular protocols. To view the subnet services on your InfiniBand fabric, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Select the Services branch.
The Services table appears in the View frame. Table 5-3 lists and describes the fields in the Services table.
Table 5-3 Services Table Fields
Field
|
Description
|
Name
|
Name of the subnet service.
|
Subnet Prefix
|
Subnet prefix of the subnet service.
|
Service ID
|
ID of the service.
|
Service GID
|
GID of the port that offers the service.
|
PKey
|
Partition key used to contact the service.
|
Viewing InfiniBand Service Properties
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Select the Services branch.
The Services table appears in the View frame.
Step 3 Click the radio button next to the service whose properties you want to view, and then click Properties.
The InfiniBand Service Properties window opens. Table 5-4 lists and describes the fields in this window.
Table 5-4 InfiniBand Service Properties Window Fields
Field
|
Description
|
Subnet Prefix
|
Subnet prefix of the service.
|
Service ID
|
ID of the service.
|
Service GID
|
GID of the service.
|
PKey
|
Partition key of the service.
|
Lease
|
Lease period of the service.
|
Key
|
Key of the service.
|
Name
|
Name of the service.
|
Data (8 bit)
|
8-bit service data.
|
Data (16 bit)
|
16-bit service data.
|
Data (32 bit)
|
32-bit service data.
|
Data (64 bit)
|
64-bit service data.
|
Viewing InfiniBand Nodes
Both InfiniBand switches and InfiniBand hosts qualify as InfiniBand nodes. To view the nodes in your InfiniBand fabric, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Topology in the InfiniBand frame.
Step 3 Select the Nodes branch.
The Nodes table appears in the View frame. Table 5-5 lists and describes the fields in the Nodes table.
Table 5-5 Nodes Table Field Descriptions
Field
|
Description
|
Subnet Prefix
|
Subnet prefix of the node. The prefix of the node matches the prefix of the Subnet Manager that manages the node.
|
Node GUID
|
GUID of the switch or host.
|
Description
|
Description of the node.
|
Type
|
Identifies the hardware type of the node.
|
Viewing Node Properties
To view the properties of a switch or host in your InfiniBand fabric, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Topology in the InfiniBand frame.
Step 3 Select the Nodes branch.
The Nodes table appears in the View frame.
Step 4 Click the radio button next to the node that you want to view, and then click Properties.
The Topology Node Properties window opens. Table 5-6 describes the Topology Node Properties fields in the window.
Table 5-6 Topology Node Properties Window Field Descriptions
Field
|
Description
|
Subnet Prefix
|
64-bit value that identifies the InfiniBand subnet to which this node belongs.
|
Node GUID
|
GUID of this node.
|
Base Version
|
Supported base management datagram (MAD) version. Indicates that this channel adapter, switch, or router supports versions up to and including this version. See section 13.4.2, Management Datagram Format, in InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
Class Version
|
Supported MAD class format version. Indicates that this channel adapter, switch, or router supports versions up to, and including, this version.
|
Type
|
Type of node being managed. The value is channel adapter, switch, router, or error. An error entry indicates an unknown type.
|
Num Ports
|
Number of physical ports on this node.
|
Port GUID
|
GUID of this port. A port within a node can return the node GUID as its PortGUID if the port is an integral part of the node and is not field-replaceable (i.e., not swappable).
|
Partition Cap
|
Capacity of entries in the partition table for channel adapter, router, and the switch management port. The value is the same for all ports on the node. This is set to at least 1 for all nodes including switches. This value is fixed and unconfigurable.
|
Device ID
|
Manufacturer-assigned device identification.
|
Revision
|
Manufacturer-assigned device revision.
|
Local Port Num
|
The link port number from which this subnet management packet (SMP) arrived. The value is the same for all ports on the node.
|
Vendor ID
|
Device vendor ID. The value is the same for all ports on the node.
|
Description
|
Description of the node.
|
System Image GUID
|
The system image GUID of this node. All nodes within a particular system (chassis) are assigned the same system image GUID.
|
Table 5-7 lists and describes the Switch Properties fields in the window.
Table 5-7 Topology Node Properties Window Field Descriptions, Switch Properties
Field
|
Description
|
Linear FDB Cap
|
Maximum number of entries allowed in the linear unicast forwarding table. 0 (zero) indicates that there is no linear forwarding database.
|
Random FDB Cap
|
Maximum number of entries allowed in the random unicast forwarding table. 0 (zero) indicates that there is no random forwarding database.
|
MCast FDB Cap
|
Maximum number of entries allowed in the multicast forwarding table.
|
Linear FDB Top
|
Specifies the top of the linear forwarding table. Packets received with unicast LIDs greater than this value are discarded by the switch. This parameter applies only to switches that implement linear forwarding tables and is ignored by switches that implement random forwarding tables.
|
Default Port
|
Specifies the default port to which to forward all the unicast packets from other ports whose destination local identifier (DLID) does not exist in the random forwarding table.
|
Default Primary MCast Port
|
Specifies the default port to which to forward all the multicast packets from other ports whose DLID does not exist in the multicast forwarding table.
|
Default Non-Primary
MCast Port
|
Specifies the port to which to forward all the multicast packets from default-pri-mcast-port whose DLID does not exist in the multicast forwarding table.
|
Lifetime Value
|
Specifies the duration a packet can live in the switch. Time units are in milliseconds. See section 18.2.5.4, Transmitter Queueing, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
Switch Port State Change
|
Indicates a change in port state. The value is either 0 (no change) or 1.
|
LID Per Port
|
Number of LID/LMC combinations that may be assigned to a given external port for switches that support the random forwarding table. This value is always 0. 0 indicates that there is one LID per port.
|
Partition Enforce Cap
|
Number of entries in this partition enforcement table per physical port. 0 (zero) indicates that partition enforcement is not supported by the switch.
|
In Enforce Cap
|
Indicates if the switch is capable of partition enforcement on received packets. The value is true (1) or false.
|
Out Enforce Cap
|
Indicates if the switch is capable of partition enforcement on transmitted packets. The value is true (1) or false.
|
In Filter Raw Packet Cap
|
Indicates if the switch is capable of raw packet enforcement on received packets. The value is true (1) or false.
|
Out Filter Raw Packet Cap
|
Indicates if the switch is capable of raw packet enforcement on transmitted packets. The value is true (1) or false.
|
Viewing Node Ports
To view the InfiniBand ports on a node in your InfiniBand fabric, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Topology in the InfiniBand frame.
Step 3 Select the Nodes branch.
The Nodes table appears in the View frame.
Step 4 Click the radio button next to the node whose ports you want to view, and then select Show Ports from the Show Options pull-down menu.
The InfiniBand Ports display appears in the View frame, but lists only the ports that belong to the node that you selected. For details, see the "Viewing InfiniBand Ports" section or see Table 5-8.
Viewing Node Neighbors
To view the neighbors of an InfiniBand node on your fabric, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Topology in the InfiniBand frame.
Step 3 Select the Nodes branch.
The Nodes table appears in the View frame.
Step 4 Click the radio button next to the node whose neighbors you want to view, and then select Show Neighbors from the Show Options pull-down menu.
The InfiniBand Neighbors display appears in the View frame but lists only the neighbors of the node that you selected. For details, see the "Viewing Neighboring InfiniBand Devices" section or see Table 5-10.
Viewing InfiniBand Ports
To view the InfiniBand ports on your InfiniBand fabric, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Topology in the Tree frame.
Step 3 Select the Ports branch in the Tree frame.
The InfiniBand Ports table appears in the View frame. Table 5-8 describes the fields in the InfiniBand Ports table.
Table 5-8 InfiniBand Ports Table Field Descriptions
Field
|
Description
|
Subnet Prefix
|
Subnet prefix of the device on which the port resides.
|
Node GUID
|
GUID of the node on which the port resides.
|
Port
|
Numeric identifier of the port.
|
LID
|
Local identifier of the port.
|
State
|
Displays the port state as active, armed, noStateChange, initialize, reserved, or down.
|
Link Width Active
|
Speed of the connection to this port.
|
Viewing InfiniBand Port Properties
To view the properties of an InfiniBand port, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Topology in the Tree frame.
Step 3 Select the Ports branch in the Tree frame.
The InfiniBand Ports table appears in the View frame.
Step 4 Click the radio button next to the port whose properties you want to view, and then click Properties.
The Topology Port Properties window opens. Table 5-9 describes the fields in the Topology Port Properties window.
Table 5-9 Topology Port Properties Window Field Descriptions
Field
|
Description
|
Subnet Prefix
|
64-bit value that identifies the InfiniBand subnet to which this port belongs.
|
Node GUID
|
64-bit GUID of the node to which this port belongs.
|
Port
|
Port number (integer) of the node.
|
MKey
|
64-bit management key for this port. See section 14.2.4, Management Key and 3.5.3, Keys, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
GID Prefix
|
64-bit GID prefix for this port. This prefix is assigned by the subnet manager, based upon the port router and the rules for local identifiers. See section 4.1.3, Local Identifiers, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
LID
|
16-bit base-LID of this port.
|
Master SM LID
|
16-bit base LID of the master subnet manager managing this port.
|
Cap Mask
|
The capability mask identifies the functions that the host supports. 32-bit bitmask that specifies the supported capabilities of the port. A bit value of 1 (one) indicates a supported capability. The bits are 0, 11-15, 18, 21-31 (Reserved and always 0.), 1 IsSM, 2 IsNoticeSupported, 3 IsTrapSupported, 4 IsResetSupported, 5 IsAutomaticMigrationSupported, 6 IsSLMappingSupported, 7 IsMKeyNVRAM (supports M_Key in NVRAM), 8 IsPKeyNVRAM (supports P_Key in NVRAM), 9 Is LED Info Supported, 10 IsSMdisabled, 16 IsConnectionManagementSupported, 17 IsSNMPTunnelingSupported, 19 IsDeviceManagementSupported, 20 IsVendorClassSupported.Values are expressed in hexadecimal.
|
Diag Code
|
16-bit diagnostic code. See section 14.2.5.6.1 Interpretation of Diagcode, InfiniBand Architecture, Vol. 1, Release 1.0, for more information. This field does not currently apply to your device.
|
MKey Lease Period
|
Initial value of the lease-period timer in seconds. The lease period is the length of time that the M_Key protection bits are to remain nonzero after a SubnSet (PortInfo) fails an M_Key check. After the lease period expires, clearing the M_Key protection bits allows any subnet manager to read (and then set) the M_Key. Set this field to 0 to indicate that the lease period is never to expire. See InfiniBand Architecture, Vol. 1, Release 1.0, section 14.2.4, Management Key, for more information.
|
Link Width Enabled
|
Enabled link width (bandwidth). The value is an integer that indicates the enabled link-width sets for this port. The value may be as follows:
0 (no state change)
•1 (1x)
•2 (4x)
•3 (1x or 4x)
•8 (12x)
•9 (1x or 12x)
•10 (4x or 12x)
•11 (1x, 4x or 12x)
•255 (set this parameter to the link-width-supported value)
|
Link Width Supported
|
Supported link width. The value is 1 (1x), 3 (1x or 4x), or 11 (1x, 4x, or 12x).
|
Link Width Active
|
Active link width. Used with LinkSpeedActive to determine the link rate between two nodes. The value is 1 (1x), 2 (4x), or 8 (12x).
|
Link Speed Supported
|
Supported link speed. The value is 1 (2.5 Gbps).
|
State
|
A higher form of addressing than PhyState, this state determines that the nodes can actually communicate and indicates the state transition that has occurred. A transition is a port change from down to initialize, initialize to down, armed to down, or active to down as a result of link state machine logic. Changes to the port state resulting from SubnSet have no affect on this parameter value. The value is noStateChange, down, initialize, armed, or active.
|
Physical State
|
Indicates the physical state of the port. This is used to determine that electricity is flowing between nodes and they can perform a handshake. The value is noStateChange, sleeping, polling, disabled, portConfigurationTraining, linkup, or linkErrorRecovery. The default state upon power-up is polling.
|
Link Down Def State
|
Default LinkDown state to return to. The value is noStateChange, sleeping, or polling. See section 5.5.2, Status Outputs (MAD GET), InfiniBand Architecture, Vol. 2, Release 1.0, for more information.
|
MKey Protocol Bits
|
Management key protection bits for the port. The bits are 0, 1, 2, and 3. See section 14.2.4.1, Levels of Protection, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
LMC
|
Local-identifier mask control (LMC) for multipath support. A LMC is assigned to each channel adapter and router port on the subnet. It provides multiple virtual ports within a single physical port. The value of the LMC specifies the number of path bits in the LID. A value of 0 (zero) indicates one LID is allowed on this port. See sections 3.5.10, Addressing, and 4.1.3, Local Identifiers, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
Link Speed Active
|
Speed of an active link. The value is 1 (2.5 Gbps).
|
Link Speed Enabled
|
Maximum speed that the link is capable of handling. The value is 0 (No state change), 1 (2.5 Gbps), or 3 (value derived from link-speed-supported).
|
Neighbor MTU
|
Active maximum transmission unit enabled on this port for transmit. Check the mtu-cap value at both ends of every link and use the lesser speed. The value is mtu256, mtu512, mtu1024, mtu2048, or mtu4096.
|
Master SM SL
|
Administrative service level required for this port to send a non-SMP message to the subnet manager.
|
VL Cap
|
Maximum range of data virtual lanes supported by this port. The value is vl0, vl0ToVl1, vl0ToVl3, vl0ToVl7, or vl0ToVl14. See also oper-VL. Each port can support up to 15 virtual lanes (VLs 0-15). The VL-cap field displays the range of those lanes (lanes 0-7) that the port currently supports.
|
VL High Limit
|
Maximum high-priority limit on the number of bytes allowed for transmitting high-priority packets when both ends of a link operate with multiple data virtual-lanes. Used with the virtual-lane arbitration table. The maximum high-limit is determined by checking the vl-arb-high-cap on the other side of the link and then negotiating downward.
|
VL Arb High Cap
|
Highest arbitration value allowed by the arbiter in determining the next packet in a set of packets to send across the link. Used with the virtual-lane arbitration table and specified as a VL/Weight pair. See section 14.2.5.9, VL Arbitration Table, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
Vl Arb Low Cap
|
Lowest arbitration value allowed by the arbiter in determining the next packet in a set of packets to send across the link. Used with the virtual-lane arbitration table and specified as a VL/Weight pair. See section 14.2.5.9, VL Arbitration Table, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
MTU Cap
|
Used with neighbor-mtu to determine the maximum transmission size supported on this port. The lesser of mtu-cap and neighbor-mtu determines the actual MTU used. The value is 256, 512, 1024, 2048, or 4096
|
VL Stall Count
|
Number of sequentially dropped packets at which the port enters a VLStalled state. The virtual lane exits the VLStalled state (8 * HLL) units after entering it. See section 18.2.5.4, Transmitter Queuing, InfiniBand Architecture, Vol. 1, Release 1.0, for a description of HLL.
|
HOQ Life
|
Maximum duration allowed to packets at the head of a virtual-lane queue. Used with VL-stall-count to determine the outgoing packets to discard.
|
Oper VL
|
Administrative limit for the number of virtual lanes allowed to the link. Do not set this above the VL-cap value. The value is vl0, vl0-Vl1, vl0-Vl3, vl0-Vl7, or vl0-Vl14.
|
In Part Enforce
|
Boolean value that indicates whether or not to support optional partition enforcement for the packets received by this port. There is no default value.
|
Out Part Enforce
|
Boolean value that indicates whether or not to support optional partition enforcement for the packets transmitted by this port. There is no default value.
|
In Filter Raw Packet Enforce
|
Boolean value that indicates whether or not to support optional raw packet enforcement for the raw packets received by this port. There is no default value.
|
Out Filter Raw Packet Enforce
|
Boolean value that indicates whether or not to support optional raw packet enforcement for the raw packets transmitted by this port. There is no default value.
|
MKey Violation
|
Number of subnet management packets (SMPs) that have been received on this port with invalid M_Keys since initial power up or the last reset. See section 14.2.4, Management Key, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
PKey Violation
|
Number of subnet management packets that have been received on this port with invalid P_Keys since initial power up or the last reset. See section 9.2.7, partition key (P_KEY), InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
QKey Violation
|
Number of subnet management packets that have been received on this port with invalid Q_Keys since initial power up or the last reset. See section 10.2.4, Q Keys, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
GUID Cap
|
Number of GUID entries allowed for this port in the port table. Any entries that exceed this value are ignored on write and read back as zero. See section 14.2.5.5, GUIDCap, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
Subnet Timeout
|
Maximum propagation delay allowed for this port to reach any other port in the subnet. This value also affects the maximum rate at which traps can be sent from this port. Delay is affected by switch configuration. This parameter, along with resp-time is used to determine the interval to wait for a response to a request before taking other action. Duration is calculated as (4.096 ms * 2^SubnetTimeout).
|
Response Time
|
Maximum time allowed between the port reception of a subnet management packet and the transmission of the associated response. See section 13.4.6.2, Timers and Timeouts, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
Local Physical Error
|
Threshold at which ICRC, VCRC, FCCRC, and all physical errors result in an entry into the BAD PACKET or BAD PACKET DISCARD states of the local packet receiver. See section 7.12.2, Error Recovery Procedures, InfiniBand Architecture, Vol. 1, Release 1.0, for more information.
|
Local Overrun Error
|
Threshold at which the count of buffer overruns, across consecutive flow-control update periods, result in an overrun error. A possible cause of such errors is when an earlier packet has physical errors and the buffers are not immediately reclaimed.
|
Viewing Neighboring InfiniBand Devices
To view the InfiniBand devices that directly connect to your device, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Topology in the Tree frame.
Step 3 Select the Neighbors branch in the Tree frame.
The InfiniBand Neighbors table appears in the View frame. Table 5-10 lists and describes the fields in this table.
Table 5-10 InfiniBand Neighbors Table Field Descriptions
Field
|
Description
|
Subnet Prefix
|
64-bit value that identifies the InfiniBand subnet to which this neighbor node belongs.
|
Local Node GUID
|
64-bit GUID of the InfiniBand node.
|
Local Port ID
|
Port ID of the InfiniBand node. The value is an integer between 0 and 255.
|
Remote Node GUID
|
64-bit Guid of the neighboring InfiniBand node to which the local node is linked.
|
Remote Port ID
|
Port ID of the neighboring InfiniBand node to which the local node is linked. The value is an integer between 0 and 255.
|
Viewing InfiniBand Neighbor Properties
To view InfiniBand neighbor properties, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Topology in the Tree frame.
Step 3 Select the Neighbors branch.
The InfiniBand Neighbors table appears in the View frame.
Step 4 Click the radio button next to the neighbor whose properties you want to view, and then click Properties.
The Topology Neighbor Properties window opens. Table 5-11 describes the fields in this window.
Table 5-11 Topology Neighbor Properties Window Field Descriptions
Field
|
Description
|
Subnet Prefix
|
Subnet prefix of the neighbor node.
|
Local Node GUID
|
GUID of the neighbor that you selected.
|
Local Port ID
|
Local port on the neighbor that you selected that connects to your Server Switch.
|
Local Node Type
|
Node type of the neighbor node.
|
Remote Node GUID
|
GUID of the physical switch within your Server Switch that connects to the neighbor node.
|
Remote Port ID
|
Port on the physical switch within your Server Switch that connects to the neighbor node.
|
Remote Node Type
|
Node type of the physical switch within your Server Switch that connects to the neighbor node.
|
Link State
|
State of the connection between the neighbor and the switch within your Server Switch.
|
Link Width Active
|
Bandwidth of the connection between the neighbor and the switch within your Server Switch.
|
Close
|
Closes the window.
|
Help
|
Opens online help.
|
Viewing IOUs
To view the I/O Units (IOUs) on your device, follow these steps:
Note This feature is not available on all hardware platforms. IOUs and IOCs can be viewed only on chassis that support I/O modules (gateways).
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Device Management in the Tree frame.
Step 3 Select the IOU branch.
The IOU display appears in the View frame. Table 5-12 describes the fields in this display.
Table 5-12 IOU Display Field Descriptions
Field
|
Description
|
Change ID
|
Cumulative number of changes to the controller list since the device last booted.
|
Max Controllers
|
Maximum number of controllers that your device can support.
|
Diag Device ID
|
Indicates that diagnostics can (1) or cannot (0) provide IOC details.
|
Option ROM
|
Indicates the presence or absence of Option ROM.
|
Controller List
|
Lists each slot on your device that can potentially contain a controller and identifies whether or not a controller resides in that slot.
|
Viewing IOCs
To view the I/O controllers (IOCs) on your device, follow these steps:
Note This feature is not available on all hardware platforms. IOUs and IOCs can be viewed only on chassis that support I/O modules (gateways).
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Device Management in the Tree frame.
Step 3 Select the IOCs branch.
The IOCs display appears in the View frame. Table 5-13 describes the fields in this display.
Table 5-13 IOCs Display Field Descriptions
Field
|
Description
|
GUID
|
GUID of the controller.
|
Vendor ID
|
Organization Unique Identifier (OUI) of the vendor.
|
Device ID
|
Vendor-assigned device identifier.
|
Device Version
|
Vendor-assigned device version.
|
IO Class
|
I/O class that the IOC supports.
|
Protocol
|
Standard protocol definition that the IOC supports.
|
Viewing IOC Properties
To view the properties of the I/O controllers (IOCs) on your device, follow these steps:
Note This feature is not available on all hardware platforms.
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Device Management in the Tree frame.
Step 3 Select the IOCs branch.
The IOCs display appears in the View frame.
Step 4 Click the radio button next to the IOC that you want to view, and then click Properties.
The IOC Properties window opens. Table 5-14 describes the fields in this window.
Table 5-14 IOC Properties Window Field Descriptions
Field
|
Description
|
GUID
|
GUID of the controller.
|
Vendor ID
|
Organization Unique Identifier (OUI) of the vendor.
|
Device ID
|
Vendor-assigned device identifier.
|
Device Version
|
Vendor-assigned device version.
|
Subsystem Vendor ID
|
Vendor-assigned subsystem vendor identifier.
|
Subsystem ID
|
Vendor-assigned subsystem identifier.
|
IO Class
|
I/O class that the IOC supports.
|
IO Subclass
|
Subclass of the I/O class protocol of the IOC.
|
Protocol
|
Standard protocol definition that the IOC supports.
|
Protocol Version
|
Protocol version that the IOC supports.
|
Send Msg Queue Depth
|
Maximum number of messages that the send message queue supports.
|
RDMA Read Queue Depth
|
Maximum depth of the per-channel RDMA Read Queue.
|
Send Msg Size
|
Maximum size, in bytes, of send messages.
|
RDMA Transfer Size
|
Maximum size, in bytes, of outbound RDMA transfers that the IOC initiates.
|
Controller Op Cap Mask
|
Integer value (from 8 cumulative bits) between 1 and 255 that represents the operation type(s) that the IOC supports:
•bit 0: ST; Send Messages To IOCs
•bit 1: SF; Send Messages From IOCs
•bit 2: RT; RDMA Read Requests To IOCs
•bit 3: RF; RDMA Read Requests From IOCs
•bit 4: WT; RDMA Write Requests To IOCs
•bit 5: WF; RDMA Write Requests From IOCs
•bit 6: AT; Atomic Operations To IOCs
•bit 7: AF; Atomic Operations From IOCs
|
Service Entries
|
Number of services that the IOC provides.
|
Viewing IOC Services
To view the IOC services on your device, follow these steps:
Note This feature is not available on all hardware platforms.
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Device Management in the Tree frame.
Step 3 Select the IOC Services branch in the Tree frame.
The IOC Services table appears in the View frame. Table 5-15 lists and describes the fields in this table.
Table 5-15 IOC Services Table Field Descriptions
Field
|
Description
|
GUID
|
GUID of the node that provides the service.
|
Service Name
|
ASCII identifier of the service.
|
Service ID
|
Numeric identifier that nodes use to call the service.
|
Viewing Properties of IOC Services
Note This feature is not available on all hardware platforms.
To view the properties of IOC services on your device, follow these steps:
Step 1 Expand InfiniBand in the Tree frame.
Step 2 Expand Device Management in the Tree frame.
Step 3 Select the IOC Services branch in the Tree frame.
The IOC Services table appears in the View frame.
Step 4 Click the radio button next to the service whose properties you want to view, and then click Properties.
The InfiniBand Service Properties window opens. Table 5-16 describes the fields in this window.
Table 5-16 InfiniBand Service Properties Window Field Descriptions
Field
|
Description
|
Subnet Prefix field
|
Subnet prefix of the service.
|
Service ID field
|
Numeric identifier that nodes use to call the service.
|
Service GID field
|
Global ID (GID) of the service.
|
PKey field
|
Partition key of the service.
|
Lease field
|
Lease period of the service.
|
Key field
|
Subnet management key of the service.
|
Name field
|
ASCII identifier of the service.
|
Data (8 bit) field
|
8-bit descriptor of the service.
|
Data (16 bit) field
|
16-bit descriptor of the service.
|
Data (32 bit) field
|
32-bit descriptor of the service.
|
Data (64 bit) field
|
64-bit descriptor of the service.
|
Close
|
Closes the window.
|
Help
|
Opens context-sensitive online help.
|
Feedback