Additional Reference Information

Special RID Usage

SLToVLMappingTableRecord RID

Each port on a switch, CA, or router implements an SLtoVLMappingTable attribute. The SLToVLMappingTableRecord is identified using the General RID. In a switch port's SLToVLMappingTableRecord, the PortNumber indicates the input port and the Enumeration indicates the output port this record references. For more information, refer to “Switch Port SL-to-VL Mapping” on page 623 and “One SLtoVLMappingTable Per Port” on page 667.

VLArbitrationTableRecord RID

The VLArbitrationTableRecord uses the General RID format. In a switch port's VLArbitrationTableRecord, the Portnumber identifies the switch port this record pertains to, and the enumeration identifies the part of the arbitration table (the upper or lower half of the Low- or High-Priority table) stored in this record (using the same values specified in “VLArbitration Attribute” on page 841).

LinearForwardingTableRecord RID

The LinearForwardingTableRecord use the General RID format, but the PortNumber and Enumeration fields act as a single 16-bit field to identify up to 768 possible records for a switch.

RandomForwardingTableRecord RID

The RandomForwardingTableRecord uses the General RID format, but the PortNumber and Enumeration fields act as a single 16-bit field to identify up to 3072 possible records for a switch.

MulticastForwardingTableRecord RID

The MulticastForwardingTable attribute is divided into 512 blocks, each consisting of an array of 16, 16-bit entries. The MulticastForwardingTableRecord uses the General RID format, but the PortNumber and Enumeration fields act as a single 16-bit field used as follows:

  • The least-significant two bits are not used and are always zero.

  • The next 10 bits identify 1 of 512 blocks with the table.

  • The upper four bits identifies 1 of 16 entries within the block.

PartitionRecord RID

Each PartitionRecord contains a record of a portion of a port's P_KeyTable attribute and is identified by a 32-bit unique RID. The General RID identifies a NodeRecord that relates the record to a specific CA, switch, or router port. The PortNumber field identifies the port this record is associated with.

Path Record Access Authorization

When an entity requests a PathRecord from the SA, the SA is only permitted to return path records for which the source port, destination port, and the port the requester used to issue the request all have a P_Key in common. The P_Key match is based on the following rules:

  • All three of the ports must be in the subnet managed by this SA's SM.

  • Two ports are considered to share a P_Key when there is at least one valid P_Key in one port's P_KeyTable that matches a P_Key in the other port's P_KeyTable.

  • P_Key sharing must exist between three pairs of ports:

    - The path source and destination ports must have a P_Key in common. The path source and destination ports used to determine sharing are the ones that are implicit in the SGID (or SLID) and DGID (or DLID) of the path.

    - The path source port and a port of the requester (see the paragraph that follows this bullet list) must have a P_Key in common.

    - The path destination port and a port of the requester (see the paragraph that follows this bullet list) must have a P_Key in common.

The requester port referred to above (“a port of the requester”) may be any port on the device from which the request came (not just the port from which the request MAD came). The requester port that has a P_Key in common with the source port need not be the same port as the requester port that has a P_Key in common with the destination port.

Access Restrictions for Other Attributes

On receipt of a request for information about a device (or devices), the SA only returns information if the requester shares a P_Key (with some exceptions). “Sharing” is defined as follows:

  • Two ports share a P_Key when there is at least one valid P_Key in one port's P_KeyTable that matches a P_Key in the other port's P_KeyTable.

  • Sharing is determined using the P_Keys assigned to any port on the requester's device and on the device that is the subject of the inquiry.

  • All ports involved in this determination must be in the subnet administered by the SA to which the request is directed.

There are some exceptions. PortInfoRecords are always provided with the M_KEY attribute element set to 0, except in the case of a trusted SM (one with the proper SM_Key). If the requester has provided the proper SM_Key, the M_KEY is also provided. Trust of other SMs is implied by an earlier provision of a valid SM_KEY by the requester during the operations leading to the establishment of the current SM master of the subnet.

SA RA Detail

The following subsections provide a detailed description for each SA RA type.

NodeRecord

Refer to Table 33-12 on this page.

PortInfoRecord

Refer to Table 33-13 on page 963.

SLtoVLMappingTableRecord

Refer to Table 33-14 on page 963.

SwitchRecord

Refer to Table 33-15 on page 963.

Table 33-12. NodeRecord Format
ElementLength (in bits)Description
NodeRID32The record's RID (general RID format).
NodeInfo320NodeInfo attribute contents (see Table 29-3 on page 816).
NodeDescription512NodeDescription attribute contents. 512-bit (64 byte) UTF-8 encoded string describing the node in text format.

Table 33-13. PortInfoRecord Format
ElementLength (in bits)Description
NodeRID32The record's RID (general RID format).
PortInfo432PortInfo attribute content (see Table 29-5 on page 825).

Table 33-14. SLtoVLMappingTableRecord Format
ElementLength (in bits)Description
SLVLRID32Unique RID of this record
NodeRID32RID of NodeRecord this record is associated with.
SLVLMapping64One 8-byte block of the SLToVLMappingTable attribute content.

Table 33-15. SwitchRecord Format
ElementLength (in bits)Description
NodeRID32The record's RID (general RID format).
SwitchInfo132Contents of SwitchInfo attribute.

LinearForwardingTableRecord

Refer to Table 33-16 on this page.

RandomForwardingTableRecord

Refer to Table 33-17 on this page.

MulticastForwardingTableRecord

Refer to Table 33-18 on page 965. The overall size of the actual MFT defines how many records it takes to store the tables image in the SA database. At a maximum, the MFT is 512 blocks in size, each of containing 64 bytes. In that case, it would takes 512 database records to hold the complete table image.

Table 33-16. LinearForwardingTableRecord Format
ElementLength (in bits)Description
LinearFdbRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
LinearFdbInfo51264-byte block of the LinearForwardingTable attribute content.

Table 33-17. RandomForwardingTableRecord Format
ElementLength (in bits)Description
RandomFdbRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
RandomFdb51264-byte block of the RandomForwardingTable attribute content.

Table 33-18. MulticastForwardingTableRecord Format
ElementLength (in bits)Description
McastRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
MulticastForwardingTable51264-byte block of the MulticastForwardingTable attribute content.

VLArbitrationRecord

Refer to Table 33-19 on this page.

SMInfoRecord

Refer to Table 33-20 on this page.

Table 33-19. VLArbitrationRecord Format
ElementLength (in bits)Description
VLArbRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
VLArbitration51264-byte block of the VLArbitrationTable attribute.

Table 33-20. SMInfoRecord Format
ElementLength (in bits)Description
NodeRID32The record's RID (general RID format).
SMInfo168Contents of SMInfo attribute of SM that resides at the port indicated in the RID.

PartitionRecord

Refer to Table 33-21 on this page.

InformRecord

Refer to Table 33-22 on this page.

NoticeRecord

Refer to Table 33-23 on this page.

Table 33-21. PartitionRecord Format
ElementLength (in bits)Description
PartitionRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
P_KeyTable51264-byte block of P_KeyTable attribute content.

Table 33-22. InformRecord Format
ElementLength (in bits)Description
InformRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
Inform344Content of InformInfo attribute.

Table 33-23. NoticeRecord Format
ElementLength (in bits)Description
NoticeRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
Notice512Content of Notice attribute.

LinkRecord

Refer to Table 33-24 on this page.

The only statement the specification makes about the LinkRecord is the following:

“Link records are synthesized by the SA to serve as informational topology data for management entities in need of such data.”

For a path defined by its source and destination ports, it seems to relate the port number and LID address of both the source and destination ports.

Table 33-24. LinkRecord Format
ElementLength (in bits)Description
LinkRID32The record's RID (general RID format).
FromLID16From InfiniBand address.
ToLID16To InfiniBand address.
FromPort8From port number.
ToPort8To port number.

ServiceRecord

Refer to Table 33-25 on page 968.

Service records advertise first level or “bootstrap” basic services that cannot be found prior to query of the SA. These could be services such as boot services, or name or directory services.

ServiceRecords are not intended to do more than to provide a first-level directory to other applications and services normally associated with a network. If there is more than one ServiceLocation associated with a ServiceName, there are multiple Service Records—one for each ServiceLocation.

Table 33-25. ServiceRecord Format
ElementLength (in bits)Description
ServiceRID32The record's RID (general RID format).
ServiceLease32Lease period remaining for this service, in seconds. FFFFFFFFh is an indefinite lease. When the lease expires, the SA automatically deletes the ServiceRecord.
Partition16Partition of this Service.
ServiceSpecificFlags12Information related to this service. Content is service specific.
ServiceGenericFlags4Generic information related to this service. The interpretation of individual bits in the field is as follows:

  • Bit 0 = Indirection. Set if the service provider may redirect requests.

  • Bit 1 = DHCP-capable. Set if a DHCP (Dynamic Host Configuration Protocol) server or a Directory Agent may automatically register this service by querying the SA.

  • Bits 3:2 = Reserved.

ServiceName992Character string identifying what service is being sought (for example “tftp” (Trivial File Transfer Protocol), “CFM.IBTA,” “sendmail,” and so on). This is a 124-byte long, UTF-8 encoded, null-terminated string.
ServiceGID320Text representation of the 128-bit port GID for the service (null-terminated).
ServiceID128Service identifier. String of 16 hex digits (including any leading zeros). It is not null-terminated. Please note that although the specification shows this field's width as 128 bits, it is only 64-bits wide.

RangeRecord

Refer to Table 33-26 on this page.

Range records specify ranges of LIDs. They exist to allow avoidance of LID conflicts. A Master SM can use them to provide ranges of LIDs to standby SMs, thereby enabling the standby SMs to use known unique ranges if a subnet they control is independently initialized (the author does not know what the specification is referring to here; only the Master SM, not a Standby SM, is permitted to assign unique LIDs to each port in the subnet). A SubnAdmConfig() operation can be used to “push” these records from the Master SM to a Standby SM, and SubnAdmGet() operations can be used by Standby SMs to get ranges from the Master SM.

Table 33-26. RangeRecord Format
ElementLength (in bits)Description
RangeRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
FmAssigned64GUID of SM-allotted range.
FromRange16Value of beginning of range.
ToRange16Value of end of range.

MCGroupRecord

Refer to Table 33-27 on page 970.

A multicast group can be created using either the SubnAdmConfig() or the SubnAdmSet() methods to create a MCGroupRecord.

  • Using SubnAdmSet(), the edit modifier is set to either:

    - Add, to create a multicast group. The Q_Key, MTU, and the P_Key are supplied and all other fields are set to zero. If a particular multicast GID is required, it can be specified; otherwise, the SA will assign a multicast GID to the group.

    - Delete, to remove a multicast group, the MCGroupRID is specified. The multicast GID, Q_Key, multicast LID, MTU, and P_Key may also be specified. If a field is set to zero for a delete request, it results in a match for that field in all the MCGroupRecords by the SA.

    - A group cannot be edited (modified).

  • Using SubnAdmConfig(), the edit modifier is set to one of the following:

    - Add.

    - Modify.

    - Delete.

The addition or deletion of a MCGroupRecord requires the SM to reprogram routers and switches with the new multicast information. For a detailed discussion of multicasting, refer to “Multicasting” on page 563.

Table 33-27. MCGroupRecord Format
ElementLength (in bits)Description
McGroupRID32The record's RID (general RID format).
MGID128Multicast GID for this multicast group. When creating a multicast group record, the requester may or may not supply the desired multicast GID address. If the requester desires that the SA select an available multicast GID, the requester sets this field to zero. The SA then assigns an available multicast GID to this field. The assigned multicast GID is returned in the response MAD.
Q_Key16The Q_Key supplied by the requester when the record is added to the database. It should be noted that Q_Key is a 32-bit value, not a 16-bit value as indicated in this table. This is almost certainly an error in the 1.0a specification.
MLID16Multicast LID for this multicast group. It is automatically generated by the SA when the record is added to the database and is returned in the response MAD.
MTU8MTU of this multicast group.

  • For a create, must be specified and zero is invalid.

  • For a delete, zero matches all records.

Possible values:

  • 0: Reserved

  • 1: 256

  • 2: 512

  • 3: 1024

  • 4: 2048

  • 5: 4096

  • 6–255: Reserved

TClass8TClass to be used in the GRH. Specified on a create and distributed to the member record (see “MCMemberRecord” on page 972) on a successful join.
P_Key16Partition Key for this Multicast group (must be specified).
RawTraffic1

  • 0: IBA packet traffic (P_Key must be valid).

  • 1: Raw packet traffic (No P_Key).

Reserved33Reserved (Ignored).
FlowLabel20Flow Label to be used in the GRH. Specified on a create and distributed to the member record (see “MCMemberRecord” on page 972) on a successful join.
HopLimit8Router Hop Limit to be used in the GRH. Specified on a create and distributed to the member record (see “MCMemberRecord” on page 972) on a successful join.

MCMemberRecord

Refer to Table 33-28 on this page.

An entity joins a multicast group by creating a MCMemberRecord. The record can be created using either the SubnAdmConfig() or the SubnAdmSet() method.

When using SubnAdmSet(), the edit modifier is set to:

  • Add for joining a multicast group. The MGID of the group is specified and all other fields are set to zero.

  • Delete for leaving a multicast group. The MCMemberRID is specified, and the LLID, MGID, Q_Key, MLID, MTU, and P_Key may also be specified. If a field is set to zero for a delete request, it results in a match for that field in all the MCMemberRecords by the SA. One could leave all the multicast groups with one SubnAdmSet() delete request specifying just the LLID with all other fields cleared to zero.

  • Edit is not permitted and results in a SubnAdmGetResp() with the Status field set to Invalid Attribute.

The addition or deletion of a MCMemberRecord requires the SM to reprogram routers and switches with the new multicast information. For a detailed discussion of multicasting, refer to “Multicasting” on page 563.

Table 33-28. MCMemberRecord Format
ElementLength (in bits)Description
MCMemberRID32The record's RID (general RID format). Zero specified in a leave request results in a match for all records.
MGID128Multicast GID address of the multicast group being joined. Required in the request and returned in the response.
Q_Key16Q_Key is supplied by the requester when the member record is added to the database. It is returned in the response. It should be noted that Q_Key is a 32-bit value, not a 16-bit value as indicated in this table. This is almost certainly an error in the 1.0a specification.
MLID16Multicast LID address assigned by the SM at creation time. Must be zero when the record is added to the database (it is ignored by the SA). The multicast LID address is automatically assigned by the SA and is returned in the response for a join or a leave.
LLID16LID of requester. Returned in the response for a join or a leave.
TClass16TClass to be used in the GRH. Specified in the group record and distributed to the member record on a successful join. In a query, zero matches all member records.
RawTraffic1

  • 0: IBA packet traffic (P_Key must be valid).

  • 1: Raw packet traffic (No P_Key).

Reserved33Reserved (Ignored).
FlowLabel20Flow Label to be used in the GRH. Specified in the group record and distributed to the member record on a successful join. In a query, zero matches all member records.
HopLimit8Router Hop Limit to be used in the GRH. Specified in the group record and distributed to the member record on a successful join. In a query, zero matches all member records.
P_Key16Partition key is supplied by the requester when the member record is added to the database. It must be a non-zero value and is checked by the SA. Note that Multicast groups can't span partitions with a single MLID.
Reserved4Reserved and must be set to zero.
MCSL4SL to be used for this multicast group.

GuidInfoRecord

Refer to Table 33-29 on this page.

Table 33-29. GUIDInfoRecord Format
ElementLength (in bits)Description
GuidInfoRID32Unique RID of this record.
NodeRID32RID of NodeRecord this record is associated with.
GUIDInfo512Content of GUIDInfo attribute. See “Port's GUID(s) Assignment” on page 156 and “Multiple GUID Assignment Permits Router Multipathing” on page 157 for usage and “GUIDInfo Attribute” on page 823 for programming.

SAResponse

Refer to Table 33-30 on this page.

The SAResponse record is returned in the Admin Data Area of the first SubnAdmGetBulkResp() response packet response returned in response to a SubnAdmGetBulk() request. This record defines the list of tables that will be provided starting immediately after the SAResponse record in this packet's Admin Data Area and continuing in the Admin Data Areas of the series of SubnAdmGetBulkResp() packets that follow the first response packet.

Table 33-30. SAResponseRecord Format
ElementLength (in bits)Description
EndOfTableRIDs32Offset from the beginning of this record to the beginning of the bulk data containing the series of tables that comprise the database.
Current Key32Current SA key.
TableRIDvariable, each entry is 48 bitsA list of n TableRID entries identifying the order in which the tables will be delivered and the offset (from the beginning of this record) to the end of each table. Each entry has the following format:

  • 16-bit AttributeID identifying the table type (i.e., record type).

  • 32-bit EndOfTable value. Offset to the end of records with this AttributeID (i.e., to the end of this table). See note below.

It should be stressed that the specification uses the phrase “Offset to the end of records with this AttributeID.” It does not define whether the offset is from the start of the SAResponse record, or from the start of this table.
TableRIDvariable, each entry is 48 bitsSee the description in the previous row.
TableRID-----------The SA response record may contain any number of TableRID fields.
BulkData The bulk data (consisting of the tables that comprise the database) starts immediately after the TableRID list.

PathRecord
Description

Refer to Table 33-31 on page 976. The PathRecord RA is used to request information (by issuing a database query) regarding routing between a source and destination port pair. The query results are used to create connections and may be useful in other circumstances as well. The data returned in a PathRecord is usually generated based on the routing algorithm used by the SM. When a PathRecord database query is issued, the SA may respond with a redirect to another service to respond to the request.

The database query for the desired path information is issued using the SubnAdmGetTable() request with the appropriate ComponentMask bit settings and corresponding known PathRecord fields. The SA responds with all PathRecords that match the request template. As an example, the requester could supply just the SGID and DGID fields (with the two, respective ComponentMask bits set to one) to obtain all of the PathRecords for all paths from the SGID to the DGID.

In a typical situation, the DGID is already known (e.g., from a Domain Name Server). During a boot sequence, however, only the SGID might be specified to learn all destination addresses that are reachable from that SGID. In this case, a single path record to each reachable port is returned (in the event of multiple paths from this SGID to a specific destination port, which path is returned for that destination port is indeterminate). The only paths returned are to devices that are visible under the partitioning arrangements in force.

Table 33-31. PathRecord Format
ElementLength (in bits)Description
PathRID32The PathRecord's RID (general RID format).
Reserved032Offset for alignment.
DGID128Destination GID to establish path to.
SGID128Source GID to establish path from. Required for Subn AdmGetTable().
DLID16Destination LID.
SLID16Source LID.
RawTraffic1

  • 0 = IBA packet path (P_Key must be valid).

  • 1 = Raw packet path (No P_Key required).

Reserved33Reserved (Ignored).
FlowLabel20FlowLabel (to be used in the GRH if a GRH is used).
HopLimit8Router Hop limit (to be used in the GRH if a GRH is used).
TClass8TClass (to be used in the GRH if a GRH is used).
Reserved11Reserved (Ignored).
NumbPath7Maximum number of paths to return in query response. Required for SubnAdmGetTable().
P_Key16Partition Key for this path.
SL16Service Level. A single bit is set to one, indicating the SL (0 through 15) supported by this path.
MtuSelector2In a query, specifies the relationship of the desired MTU to the MTU specified in the MTU field (see the next row in this table).

  • 0: > MTU specified.

  • 1: < MTU specified.

  • 2: = MTU specified.

Mtu6See the description in the previous row of this table:

  • 1: 256

  • 2: 512

  • 3: 1024

  • 4: 2048

  • 5: 4096

  • 5–63: reserved

RateSelector2Desired transmission rate:

  • 0: > rate specified in next field.

  • 1: < rate specified in next field.

  • 2: = rate specified in next field.

Rate6See the description in the previous row of this table:

  • 1: 1 Gb/s.

  • 2: 2.5 Gb/s.

  • 3: 10 Gb/s.

  • 4: 30 Gb/s.

  • 5–64: reserved

PacketLifeTimeSelector2

  • 0: > PacketLifeTime specified in next field.

  • 1: < PacketLifeTime specified in next field.

  • 2: = PacketLifeTime specified in next field.

PacketLifeTime6Accumulated PacketLifeTime (maximum source/destination flight time) for the path specified (in units of 4.096 microseconds X 2PacketLifeTime). The specification does not explain what is meant by “accumulated” in this context.
Reserved256Offset for alignment.

Example PathRecord Query

In this example scenario, the requester is querying the database for PathRecords defining paths with the following characteristics (see Table 33-32 on this page):

- MTU ≤ 1024 bytes.

- Transmission rate = 2.5 Gb/s.

- The path must be in a partition that the requester belongs to.

- The desired SL = 3.

- Packet Life Time cost = any.

- TClass = any.

- Path supports either raw or IBA traffic.

- FlowLabel = any.

- Number of router hops = any.

Example Response

Table 33-33 on page 980 contains the example query results.

Table 33-32. Example PathRecord Query Contents
PathRecord ElementComponent Mask BitValueMeaning/Implication
PathRID00PathRID is ignored during query.
Reserved000Padding
DGID1GID of desired serviceGID of the service to communicate with (typically obtained from a name service—DNS).
SGID1Source port's GIDSource GID address.
DLID00DLID is ignored during query.
SLID00SLID is ignored during query.
RawTraffic10Only match on paths that carry IBA traffic (rather than raw traffic). Must therefore be a valid P_Key.
Reserved300Ignored and set to 0.
FlowLabel00FlowLabel is ignored during query.
HopLimit00Hop limit is ignored during query.
TClass00TClass is ignored during query.
Reserved100Ignored and set to 0.
NumbPath12Requesting only 2 paths meeting these specifications.
P_Key11234hP_Key to be used for this path = 1234h.
SL10008hOnly match on paths with SL = 3.
MtuSelector111 = Only match on paths with an MTU < the value specified by the Mtu field (= 4, indicating < 2048 bytes).
Mtu14
RateSelector12The RateSelector value of 2 indicates only match on paths with a transmission rate = the rate specified by the Rate value (and a Rate value of 2 indicates 2.5Gb/s).
Rate12
PacketLifeTime Selector00PacketLifeTime is ignored during query.
PacketLifeTime00PacketLifeTime is ignored during query.
Reserved200Padding.

Table 33-33. Example PathRecord Query Result—contains 2 PathRecords
PathRecord ElementValueMeaning/Implication
First returned PathRecord starts here
PathRID00000001hThe PathRecord's RID (general RID format).
Reserved00 
DGIDService global IDGID of the service to communicate with (typically obtained from a name service).
SGIDSource port's GIDSource GID address.
DLID0008hThe LID assigned to the port where this service can be reached.
SLID000AhThe LID assigned to the local port that can be used to access this service.
RawTraffic0This path supports IBA traffic (P_Key will be valid).
Reserved30Ignored and set to 0.
FlowLabel0Default FlowLabel—since this is an intra-subnet DGID (note that the author does not know what is meant by default in this context but it is zero).
HopLimit0Default HopLimit—since this is an intra-subnet DGID (note that the author does not know what is meant by default in this context but it is FFh).
TClass0Default TClass—since this is an intra-subnet DGID (note that the author does not know what is meant by default in this context but it is zero).
Reserved10Ignored and set to 0.
NumbPath2Two paths are being returned.
P_Key1234hP_Key to be used for this path.
SL0008hThis path has a SL of 3.
MtuSelector2Path's MTU is exactly 1024 bytes.
Mtu3
RateSelector2Path transmission rate is exactly 2.5Gb/s.
Rate2
PacketLifeTimeSelector2Path PacketLifeTime = 4.096usec X 22 = 16.384usec exactly.
PacketLifeTime2The power that the PacketLifeTimeSelector is raised to in the previous row.
Reserved20 
Second PathRecord start here
PathRID00000003hThe PathRecord's RID (general RID format).
Reserved00 
DGIDService global IDGID of the service to communicate with (typically obtained from a name service).
SGIDSource port's GIDSource GID address
DLID0009hThe LID assigned to the port where this service can be reached.
SLID000AhThe LID assigned to the local port that can be used to access this service.
RawTraffic0This path supports IBA traffic (P_Key will be valid).
Reserved30Ignored and set to 0.
FlowLabel0Default FlowLabel—since this is an intra-subnet DGID (note that the author does not know what is meant by default in this context but it is zero).
HopLimit0Default HopLimit—since this is an intra-subnet DGID (note that the author does not know what is meant by default in this context but it is FFh).
TClass0Default TClass—since this is an intra-subnet DGID (note that the author does not know what is meant by default in this context but it is zero).
Reserved10Ignored and set to 0.
NumbPath2Two paths are being returned.
P_Key1234hP_Key to be used for this path.
SL0008hThis path has a SL of 3.
MtuSelector2The path MTU is exactly 512 bytes.
Mtu2
RateSelector2Path transmission rate is exactly 2.5Gb/s.
Rate2
PacketLifeTime Selector2Path's PacketLifeTime is 4.096usec X 210 = exactly 4.2ms.
PacketLifeTime0AhThe power that the PacketLifeTimeSelector is raised to in the previous row.
Reserved20 

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.119.118.163