User Manual

OpenSM – Subnet ManagerRev 2.1-1.0.6
Mellanox Technologies
170
8.6.4 Policy File Syntax Guidelines
• Leading and trailing blanks, as well as empty lines, are ignored, so the indentation in
the example is just for better readability.
• Comments are started with the pound sign (#) and terminated by EOL.
• Any keyword should be the first non-blank in the line, unless it's a comment.
• Keywords that denote section/subsection start have matching closing keywords.
• 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
qos-levels
qos-level
name: DEFAULT
sl: 0
end-qos-level
end-qos-levels
#
# See the comments in the following example.
# They explain different keywords and their meaning.
#
port-groups
port-group # using port GUIDs
name: Storage
# "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
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:
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: