User Manual

Rev 2.2-1.0.1

Mellanox Technologies

201

• Having a QoS Level named "DEFAULT" is a must - it is applied to PR/MPR requests

that didn't match any of the matching rules.

• Any section/subsection of the policy file is optional.

8.6.5 Examples of Advanced Policy File

As mentioned earlier, any section of the policy file is optional, and the only mandatory part of the

policy file is a default QoS Level.

Here's an example of the shortest policy file:

qos-levels

qos-level

sl: 0

end-qos-level

end-qos-levels

Port groups section is missing because there are no match rules, which means that port groups are

not referred anywhere, and there is no need defining them. And since this policy file doesn't have

any matching rules, PR/MPR query will not match any rule, and OpenSM will enforce default

QoS level. Essentially, the above example is equivalent to not having a QoS policy file at all.

The following example shows all the possible options and keywords in the policy file and their

syntax:

# See the comments in the following example.

# They explain different keywords and their meaning.

port-groups

port-group # using port GUIDs

# "use" is just a description that is used for logging

# Other than that, it is just a comment

use: SRP Targets

port-guid: 0x10000000000001, 0x10000000000005-0x1000000000FFFA

port-guid: 0x1000000000FFFF

end-port-group

port-group

# The syntax of the port name is as follows:

# "node_description/Pnum".

# node_description is compared to the NodeDescription of the node,

# and "Pnum" is a port number on that node.

port-name: vs1 HCA-1/P1, vs2 HCA-1/P1