Security Keys
When any security keys should be used with ibdiagnet, it can use option security keys to provide path to all security files that should be used:
|
Parameter |
Description |
|---|---|
|
--security_keys <path to key file> |
Specifies the path to the directory with the key files. (guid2lid, guid2mkey, neighbors, guid2vskey, guid2cckey, guid2_m2n_key, guid2pmkey). |
File names
|
Type |
File names |
|---|---|
|
Management Key (MKEY) |
guid2lid guid2mkey neighbors guid2vskey |
|
VendorSpecific Key (VS Key) |
guid2vskey |
|
CongestionControl Key (CC Key) |
guid2cckey |
|
Manager2Node Key (M2N Key) |
guid2_m2n_key |
|
Performance Management Key (VS Key) |
guid2pmkey |
Management Key (MKEY)
When MKEY protection is enabled by the Subnet Manager on the fabric devices, the following command options should be used in ibdiagnet:
|
Parameter |
Description |
|---|---|
|
--m_key <m_key> |
Specifies constant MKey for the fabric. The MKey value should be specified when a single MKEY is shared by all InfiniBand devices. The mkey value can be obtained from the opensm.conf file (m_key parameter). |
Example of guid2mkey/guid2cckey/guid2vskey file:
|
|
Example of guid2lid file:
|
|
Example of neighbours file:
|
|
Example:
|
|
VendorSpecific Key (VS Key)
When VendorSpecific keys are generated and provisioned by the Subnet Manager, VendorSpecific keys should be sent in VendorSpecific MADs per endport.
|
Parameter |
Description |
|---|---|
|
--vs_key <vs_key> |
Specifies constant vs_key.
|
Example of guid2vskey FILE:
|
|
Example:
|
|
CongestionControl Key (CC Key)
When CongestionControl keys are generated and provisioned by the Subnet Manager, CongestionControl keys should be sent in CongestionControl (CC) MADs perend port.
|
Parameter |
Description |
|---|---|
|
--cc_key <cc_key> |
Specifies constant cc_key.
|
Example of guid2cckey FILE:
|
|
Example:
|
|
Manager2Node Key (M2N Key)
When Manager2Node keys are generated and provisioned by the Subnet Manager, Manager2Node keys should be sent in M2N (pFRN) MADs per node.
|
Parameter |
Description |
|---|---|
|
--m2n_key <m2n_key> |
Specifies constant m2n_key for the fabric.
|
Example of guid2_m2n_key FILE:
|
|
Examples:
|
|
Performance Management Key (VS Key)
When PerformanceManagement keys are generated and provisioned by the Subnet Manager, PerformanceManagement keys should be sent in PerformanceManagement MADs per endport.
|
Parameter |
Description |
|---|---|
|
--pm_key <vs_key> |
Specifies constant pm_key.
|
|
--pm_key_file <path_to_pm_key_file> |
Specifies the path to pm_key_file: guid2pm_key.
(Deprecated, see --security_keys). |
Example of guid2pmkey FILE:
|
|
Example:
|
|
Aggregation Management Key (AMKey)
Aggregation Management Key (AM key) is sent in SHARP Management MADs to the Aggregation nodes. (default 0). Aggregation management key is configured in SHARP Aggregation Manager configuration file.
|
Parameter |
Description |
|---|---|
|
--am_key <am_key> |
Specifies constant am_key.
|
|
--am_key_file <path_to_am_key_file> |
Specifies the path to am_key_file: guid2am_key.
|
Example of guid2amkey file:
|
|
Example:
|
|
Last updated: