Table B-17 show ib sm port Command Field Descriptions (continued)

Field Description

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 in conjunction 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-pkt-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-pkt-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 with traps can be sent from this port. Delay is affected by switch

 

configuration. This parameter, along with resp-time, may be used by requestors 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).

 

 

resp-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.

Show Commands 149