Feedback
Table Of Contents
config db-sync cold-sync-limit
config db-sync cold-sync-period
config db-sync cold-sync-timeout
config db-sync new-session-delay
config db-sync resync-interval
config db-sync session-timeout
config multicast-group-ib create
config multicast-group-ib delete
config multicast-group-ipoib create
config multicast-group-ipoib delete
config partition member remove
config pm monitor poll-interval
config sl-vl-mapping oper-vl add
config sl-vl-mapping oper-vl apply
config sl-vl-mapping oper-vl delete
Configure Commands
This chapter includes the following commands::
•
config db-sync cold-sync-limit
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
config ca-link-hoqlife
To configure the Head of Queue Lifetime for switch ports that are attached to channel adapters, use the config ca-link-hoqlife command.
config ca-link-hoqlife value
Syntax Description
value
Specifies the integer value of the Head of Queue Lifetime limit, which is defined as 4.096us * 2^value. This integer value represents the power to which 2 is raised.
Defaults
This value defaults to 18.
Usage Guidelines
This command configures the HeadOfQueue Lifetime for switch ports that are attached to channel adapters in the network. This value specifies how long a packet will live at the front of a port queue before being discarded. The default value of 18 causes packets to be discarded after approximately one second. The maximum value of 20 is a special value that means packets are never discarded. This lifetime is linked to the sw-link-hoqlife.
Examples
ib_sm> config ca-link-hoqlife 15ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config db-sync cold-sync-limit
To configure the cold-sync-limit parameter of the Database Synchronization feature, use the config db-sync cold-sync-limit command.
config db-sync cold-sync-limit limit
Syntax Description
limit
Specifies the maximum number of times the master Subnet Manager will attempt to synchronize with a standby Subnet Manager during a cold sync period.
Defaults
This value defaults to 2.
Usage Guidelines
This command configures the cold-sync-limit db-sync parameter. The cold-sync-limit is the maximum number of times a master Subnet Manager will attempt to synchronize with the standby Subnet Manager in a "cold-sync-period" time window.
Examples
ib_sm> config db-sync cold-sync-limit 4Related Commands
config db-sync cold-sync-period
config db-sync cold-sync-timeout
config db-sync cold-sync-period
To configure the cold-sync-period parameter of the Database Synchronization feature, use the config db-sync cold-sync-period command.
config db-sync cold-sync-period seconds
Syntax Description
Defaults
This value defaults to 900 seconds.
Usage Guidelines
This command configures the cold-sync-period db-sync parameter. This parameter represents the duration in seconds of each db-sync window to which the "cold-sync-limit" is applied.
Examples
ib_sm> config db-sync cold-sync-period 60Related Commands
config db-sync cold-sync-limit
config db-sync cold-sync-timeout
config db-sync cold-sync-timeout
To configure the cold-sync-timeout parameter of the Database Synchronization feature, use the config db-sync cold-sync-timeout command.
config db-sync cold-sync-timeout seconds
Syntax Description
Defaults
This value defaults to 10 seconds.
Usage Guidelines
This command configures the cold-sync-timeout db-sync parameter. This parameter represents the number of seconds the master Subnet Manager will wait for a standby Subnet Manager to complete a full synchronization (cold-sync) after it has dispatched a db-sync request.
Examples
ib_sm> config db-sync cold-sync-timeout 5Related Commands
config db-sync cold-sync-limit
config db-sync cold-sync-period
config db-sync disable
To disable the Database Synchronization feature, use the config db-sync disable command.
config db-sync disable
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled by default.
Usage Guidelines
Disable the synchronization feature when you run only one Subnet Manager.
Examples
ib_sm> config db-sync disableib_sm> show db-sync================================================================================DB Sync Configuration and Status================================================================================admin-state : disabledRelated Commands
config db-sync enable
To enable the Database Synchronization feature on your IB fabric, use the config db-sync enable command.
config db-sync enable
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled by default. To disable synchronization, see config db-sync disable.
Usage Guidelines
Enable the synchronization feature when you run one master Subnet Manager with one or more backup Subnet Managers.
Examples
ib_sm> config db-sync enableib_sm> show db-sync================================================================================DB Sync Configuration and Status================================================================================admin-state : enabledRelated Commands
config db-sync max-dbsync-sms
To configure the maximum number of Subnet Managers with which the master Subnet Manager will attempt to synchronize, use the config db-sync max-dbsync-sms command.
config db-sync max-dbsync-sms num-backups
Syntax Description
num-backups
Specifies the maximum number of backup Subnet Managers with which the master Subnet Manager attempts to synchronize.
Defaults
This value defaults to 1.
Usage Guidelines
Configure this parameter to limit the number of Subnet Managers with which the master Subnet Manager synchronizes.
Examples
ib_sm> config db-sync max-backup-sms 2ib_sm> show db-sync================================================================================DB Sync Configuration and Status================================================================================protocol-version : 25admin-state : enabledmax-backupdbsync-sms : 2session-timeout(sec) : 5poll-interval(sec) : 2cold-sync-timeout(sec) : 5cold-sync-limit : 4cold-sync-period(sec) : 60new-session-delay(sec) : 20resync-interval(sec) : 600state : not in-syncRelated Commands
config db-sync new-session-delay
To configure the new session delay parameter of the Database Synchronization feature, use the config db-sync new-session delay command.
config db-sync new-session-delay seconds
Syntax Description
Defaults
This value defaults to 120 seconds.
Usage Guidelines
This command specifies the amount of time that the master Subnet Manager waits before it attempts to initiate a synchronization session with a standby Subnet Manager.
Examples
ib_sm> config db-sync new-session-delay 20Related Commands
config db-sync poll-interval
To configure the poll interval parameter of the Database Synchronization feature, use the config db-sync poll-interval command.
config db-sync poll-interval seconds
Syntax Description
Defaults
This value defaults to 3.
Usage Guidelines
The poll interval is the interval at which the master Subnet Manager polls an active standby Subnet Manager to verify synchronization. Use this command in conjunction with the config db-sync session-timeout command. The parameter controls how frequently the master Subnet Manager polls a fully-synchronized standby Subnet Manager.
Examples
ib_sm> config db-sync poll-interval 2Related Commands
config db-sync resync-interval
To configure the resynchronization interval parameter of the Database Synchronization feature, use the config db-sync resync-interval command.
config db-sync resync-interval seconds
Syntax Description
Defaults
This value defaults to 3600 seconds.
Usage Guidelines
The resync-interval specifies the interval at which the master Subnet Manager sends a resynchronization request to all active sync sessions. The resynchronization interval controls the frequency with which a synchronized standby Subnet Manager validates its database against the master Subnet Manager. If necessary, the standby Subnet Manager initiates a full resynchronization.
Examples
ib_sm> config db-sync resync-interval 600Related Commands
config db-sync session-timeout
To configure the session timeout parameter of the Database Synchronization feature, use the config db-sync session timeout command.
config db-sync session-timeout seconds
Syntax Description
Defaults
This value defaults to 10 seconds.
Usage Guidelines
The session timeout specifies the interval, in seconds, during which a synchronization session status MAD packet must arrive at the master Subnet Manager to maintain synchronization. This value should be greater than the poll-interval value.
Examples
ib_sm> config db-sync session-timeout 5ib_sm> show db-sync================================================================================DB Sync Configuration and Status================================================================================protocol-version : 25admin-state : enabledmax-dbsync-sms : 2session-timeout(sec) : 5poll-interval(sec) : 2cold-sync-timeout(sec) : 5cold-sync-limit : 4cold-sync-period(sec) : 60new-session-delay(sec) : 20resync-interval(sec) : 600state : not in-syncRelated Commands
config lmc
To configure the LID Mask Control value for all end ports in the subnet, use the config lmc command.
config lmc value
Syntax Description
value
Specifies the number of least significant bits masked by a physical port when attempting to match the destination LID of a packet with its assigned LID.
Defaults
This value defaults to 0.
Usage Guidelines
This command configures the Lid Mask Control (LMC) value for all endports in the subnet. Each port is given 2^lmc LIDs.
A non-zero LMC is typically employed in a subnet to enable multipathing. The LMC value range is (0 <= lmc <= 7).
Examples
ib_sm> show port -s================================================================================Subnet Manager Port Summary================================================================================node-guid port lid state link--------------------------------------------------------------------------------00:05:ad:00:00:01:60:04 0 4 active 4x-sdr00:05:ad:00:00:04:e4:4c 1 896 active 4x-sdr00:05:ad:00:00:04:e5:1c 1 904 active 4x-sdr00:05:ad:00:00:04:e5:24 1 888 active 4x-sdr00:05:ad:00:00:04:e5:64 1 912 active 4x-sdrib_sm> config lmc 2ib_sm> show config================================================================================Subnet Manager Configuration================================================================================LID-mask-control : 2ib_sm>ib_sm> show port -s================================================================================Subnet Manager Port Summary================================================================================node-guid port lid state link--------------------------------------------------------------------------------00:05:ad:00:00:01:60:04 0 2 active 4x-sdr 4x00:05:ad:00:00:04:e4:4c 1 897 active 4x-sdr 4x00:05:ad:00:00:04:e5:1c 1 905 active 4x-sdr 4x00:05:ad:00:00:04:e5:24 1 889 active 4x-sdr 4x00:05:ad:00:00:04:e5:64 1 913 active 4x-sdr 4xRelated Commands
config local-node-retries
To configure the number of times that the Subnet Manager will retry communicating with its local node, use the config local-node-retries command.
config local-node-retries value
Syntax Description
value
Specifies the number of times that the Subnet Manager will retry communicating with its local node.
Defaults
This command defaults to 10.
Usage Guidelines
This command configures the number of times that the Subnet Manager will retry communicating with its local node before giving up and exiting.
ib_sm> config local-node-retries 20ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledib_sm> config wait-report-response falseRelated Commands
config mad-retries
To configure the number of times that the Subnet Manager resends a MAD packet before it labels the transaction as "failed," use the config mad-retries command.
config mad-retries milliseconds value
Syntax Description
milliseconds
Specifies the retry duration, in milliseconds.
value
Specifies the number of times the Subnet Manager retries sending a MAD.
Defaults
This value defaults to 5.
Usage Guidelines
This command configures the number of times that the Subnet Manager will resend a MAD packet before declaring a transaction failed. The packet is retried at each response-timeout interval.
Examples
ib_sm> config mad-retries 7ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledib_sm> config wait-report-response falseRelated Commands
config master-poll-interval
To configure how frequently a standby Subnet Manager polls the master to verify that the master is active, use the config master-poll-interval command.
config master-poll-interval seconds
Syntax Description
Defaults
This value defaults to 3.
Usage Guidelines
This command configures how frequently a standby Subnet Manager polls a master to verify that it is still controlling the subnet.
Examples
ib_sm> config master-poll-interval 5
ib_sm> show config
================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config master-poll-retries
To configure the number of times that a standby Subnet Manager unsuccessfully polls the master Subnet Manager before labeling the master "down," use the config master-poll-retries command.
config master-poll-retries integer
Syntax Description
Defaults
This value defaults to 2.
Usage Guidelines
This command configuresthe number of successive failed attempts by a standby Subnet Manager to successfully poll the master Subnet Manager before triggering master Subnet Manager failover logic.
Examples
ib_sm> config master-poll-retries 3ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config max-active-sms
To configure the maximum number of Subnet Managers active on the subnet, use the config max-active-sms command.
config max-active-sms integer
Syntax Description
Defaults
This value defaults to 0.
Usage Guidelines
This command is not currently used.
Examples
ib_sm> config max-active-sms 2ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config max-hops
To configure the maximum number of switches that the routing algorithm checks on the path to a destination, use the config max-hops command.
config max-hops integer
Syntax Description
Defaults
This value defaults to 64.
Usage Guidelines
This command configures the maximum number of switches the routing algorithm will check on a path to a destination. For large fat-tree networks, reducing this value can greatly speed up the routing calculation. If the value is tuned too low, such that switches would be unable to reach some destinations in the network, the Subnet Manager will ignore the configured value and instead calculate and use the lowest value that will ensure all destinations are still reachable. The value 0 has a special meaning. It means that the Subnet Manager will calculate and use the lowest value that will ensure all destinations are reachable.
Note
ib_sm> config max-hops 5ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config max-operational-vl
To configure the maximum permissible Operational VL value for ports in the subnet, use the config max-operational-vl command.
config max-operational-vl value
Syntax Description
Defaults
This value defaults to auto-link.
Usage Guidelines
This command limits the range of data VLs configured in the subnet.
When this command is set to the default value, the operational VL value of a port is limited only by the VL capabilities of its neighbor port. The number of data VLs available on a link in the subnet is determined by the smallest VL capability of the ports associated with it.
Use this command to further limit the configured operational VL values of ports. If a non-default limit is specified and is lower than the auto-detected operational VL value of a port, the new value is enforced at the port.
You might want to configure this parameter for these reasons:
•
•
Note
Examples
ib_sm> config max-operational-vl auto-subnetib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config multicast-group-ib create
To create a generic IB multicast group, use the config multicast-group-ib create command.
config multicast-group-ib create mgid [-p p_key] [-q qkey] [-m mtu] [-r rate] [-l sl] [-s scope]
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command creates a generic IB multicast group.
Examples
ib_sm> config multicast-group-ib create ff:12:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e -p ff:ffib_sm>ib_sm> show multicast================================================================================All Multicast Groups================================================================================subnet-prefix : fe:80:00:00:00:00:00:00mgid : ff:12:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0eq-key : 00:00:00:0bmlid : 49155mtu : 0t-class : 0p_key : ff:ffrate : 10 gbpspacket-life-time : 2sl : 0flow-label : 00:00:00hop-limit : 0scope : link-localuser-configured : truemulticast-group-members : nonesubnet-prefix : fe:80:00:00:00:00:00:00mgid : ff:12:40:1b:81:81:00:00:00:00:00:00:ff:ff:ff:ffq-key : 80:00:00:0bmlid : 49154mtu : 0t-class : 0p_key : 81:81rate : 10 gbpspacket-life-time : 2sl : 0flow-label : 00:00:00hop-limit : 0scope : link-localuser-configured : truemulticast-group-members : nonesubnet-prefix : fe:80:00:00:00:00:00:00mgid : ff:12:40:1b:ff:ff:00:00:00:00:00:00:00:00:00:01q-key : 00:00:00:0bmlid : 49153mtu : 2048t-class : 0p_key : ff:ffrate : 2500 mbpspacket-life-time : 2sl : 0flow-label : 00:00:00hop-limit : 0scope : link-localuser-configured : falsemulticast-group-members : noneRelated Commands
config multicast-group-ib delete
To delete a previously created IB multicast group, use the config multicast-group-ib delete command.
config multicast-group-ib delete mgid
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command deletes a previously created generic IB multicast group.
Examples
ib_sm> config multicast-group-ib delete ff:12:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e -p ff:ffRelated Commands
config multicast-group-ipoib create
To create a multicast group for use by the IPoIB upper layer protocol, use the config multicast-group-ipoib create command.
config multicast-group-ipoib create p_key [-q qkey] [-m mtu] [-r rate] [-l sl] [-s scope]
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command creates a multicast group for use by the IPoIB upper layer protocol.
Examples
ib_sm> config partition key create 81:81ib_sm> config multicast-group-ipoib create 81:81ib_sm> show multicast================================================================================All Multicast Groups================================================================================subnet-prefix : fe:80:00:00:00:00:00:00mgid : ff:12:40:1b:81:81:00:00:00:00:00:00:ff:ff:ff:ffq-key : 80:00:00:0bmlid : 49154mtu : 0t-class : 0p_key : 81:81rate : 10 gbpspacket-life-time : 2sl : 0flow-label : 00:00:00hop-limit : 0scope : link-localuser-configured : truemulticast-group-members : nonesubnet-prefix : fe:80:00:00:00:00:00:00mgid : ff:12:40:1b:ff:ff:00:00:00:00:00:00:00:00:00:01q-key : 00:00:00:0bmlid : 49153mtu : 2048t-class : 0p_key : ff:ffrate : 2500 mbpspacket-life-time : 2sl : 0flow-label : 00:00:00hop-limit : 0scope : link-localuser-configured : falsemulticast-group-members :Related Commands
config multicast-group-ipoib delete
To delete a multicast group in use by the IPoIB upper layer protocol, use the config multicast-group-ipoib delete command.
config multicast-group-ipoib delete p_key [-s scope]
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Usage Guidelines
This command deletes a multicast group previously created for use by the IPoIB upper layer protocol.
Examples
ib_sm> config multicast-group-ipoib delete 81:81ib_sm> show multicast================================================================================All Multicast Groups================================================================================subnet-prefix : fe:80:00:00:00:00:00:00mgid : ff:12:40:1b:ff:ff:00:00:00:00:00:00:00:00:00:01q-key : 00:00:00:0bmlid : 49153mtu : 2048t-class : 0p_key : ff:ffrate : 2500 mbpspacket-life-time : 2sl : 0flow-label : 00:00:00hop-limit : 0scope : link-localuser-configured : falseRelated Commands
config node-timeout
To configure the interval that the Subnet Manager waits for a Node Info response from a channel adapter before declaring the channel adapter "bad," use the config node-timeout command.
config node-timeout seconds
Syntax Description
Defaults
This value defaults to 10 seconds.
Usage Guidelines
This command configures how long the Subnet Manager will wait for a NodeInfo response from a Channel Adapter before declaring the CA bad and bringing down the attached switch port. This configuration is a failsafe for channel adapters that have become unresponsive.
Examples
ib_sm> config node-timeout 60ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config partition key
To create or delete a partition, use the config partition key command.
config partition key {create | delete} p_key [-i {enabled | disabled}]
Syntax Description
Defaults
IPoIB is enabled by default.
Usage Guidelines
This command creates or deletes a partition with the given P_Key.
Examples
ib_sm> config partition key create 81:81 -i disabledib_sm> show partition================================================================================All Partitions================================================================================subnet-prefix : fe:80:00:00:00:00:00:00p-key : 81:81ipoib : disabledpartition-members : nonesubnet-prefix : fe:80:00:00:00:00:00:00p-key : ff:ffipoib : enabledpartition-members :node-guid : 00:05:ad:00:00:01:60:04port-num : 0member-type : fullnode-guid : 00:05:ad:00:00:04:e4:4cport-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:1cport-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:24port-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:64port-num : 1member-type : fullRelated Commands
config partition member remove
config partition key ipoib
To enable or disable IPoIB on a partition key, use the config partition key ipoib command.
config partition key ipoib p_key {enabled | disabled}
Syntax Description
p_key
Specifies the partition key.
enabled
Specifies that IPoIB is enabled
disabled
Specifies that IPoIB is disabled.
Defaults
IPoIB is enabled by default.
Usage Guidelines
This command enables or disables IPoIB on a partition with the given P_Key.
Examples
ib_sm> config partition key ipoib 81:81 -i disabledib_sm> show partition================================================================================All Partitions================================================================================subnet-prefix : fe:80:00:00:00:00:00:00p-key : 81:81ipoib : disabledpartition-members : nonesubnet-prefix : fe:80:00:00:00:00:00:00p-key : ff:ffipoib : enabledpartition-members :node-guid : 00:05:ad:00:00:01:60:04port-num : 0member-type : fullnode-guid : 00:05:ad:00:00:04:e4:4cport-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:1cport-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:24port-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:64port-num : 1member-type : fullRelated Commands
config partition member remove
config partition member add
To add a port to a partition, use the config partition member add command.
config partition member add p_key guid port {full | limited}
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command adds a port to the given partition as a member of the given type (full or limited).
Examples
ib_sm> config partition member add 81:81 00:05:ad:00:00:04:e4:4c 1 fullib_sm> config partition member add 81:81 00:05:ad:00:00:04:e5:1c 1 limitedib_sm> config partition member add 81:81 00:05:ad:00:00:04:e5:24 1 fullib_sm> show partition -k 81:81================================================================================Partition for specified P_Key================================================================================subnet-prefix : fe:80:00:00:00:00:00:00p-key : 81:81ipoib : disabledpartition-members :node-guid : 00:05:ad:00:00:04:e4:4cport-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:1cport-num : 1member-type : limitednode-guid : 00:05:ad:00:00:04:e5:24port-num : 1member-type : fullRelated Commands
config partition member remove
config partition member remove
To remove a port from a partition, use the config partition member remove command.
config partition member remove p_key guid port
Syntax Description
p_key
Specifies the partition key of the partition to remove from the port.
guid
Specifies the GUID of the node on which the port resides.
port
Specifies the port to remove from the partition.
Defaults
This command has no default settings.
Usage Guidelines
This command removes a port from a partition.
Examples
ib_sm> config partition member remove 81:81 00:05:ad:00:00:04:e5:1c 1ib_sm> show partition -k 81:81================================================================================Partition for specified P_Key================================================================================subnet-prefix : fe:80:00:00:00:00:00:00p-key : 81:81ipoib : disabledpartition-members :node-guid : 00:05:ad:00:00:04:e4:4cport-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:24port-num : 1member-type : full
Note
Related Commands
config partition member type
To change the type of membership assigned to a port in a partition, use the config partition member type command.
config partition member type p_key guid port {full | limited}
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
Use this command to change the membership type for a port that is already a member of the partition.
Examples
ib_sm> config partition member type 81:81 00:05:ad:00:00:04:e5:24 1 limitedib_sm> show partition -k 81:81================================================================================Partition for specified P_Key================================================================================subnet-prefix : fe:80:00:00:00:00:00:00p-key : 81:81ipoib : disabledpartition-members :node-guid : 00:05:ad:00:00:04:e4:4cport-num : 1member-type : fullnode-guid : 00:05:ad:00:00:04:e5:24port-num : 1member-type : limited
Note
Related Commands
config partition member remove
config pm connection monitor
To add a connection to or remove a connection from the list of connections that the PM monitors, use the config pm connection monitor command.
config pm connection monitor {create | delete} src-lid dst-lid
Syntax Description
Defaults
By default, the list of monitored connections is empty.
Usage Guidelines
This command adds or removes a connection (path from a source to a destination) to the list of connections being monitored by the PM.
Examples
ib_sm> config pm connection monitor create 904 888ib_sm> show pm connection monitors================================================================================All PM Monitored Connections================================================================================subnet-prefix : fe:80:00:00:00:00:00:00src-lid : 904dst-lid : 888error-status : not exceededutilization-status : not exceededport-errors : 0utilization-errors : 0ib_sm> show pm connection monitors================================================================================All PM Monitored Connections================================================================================subnet-prefix : fe:80:00:00:00:00:00:00src-lid : 904dst-lid : 888error-status : not exceededutilization-status : exceededport-errors : 0utilization-errors : 2port-error : 1node-guid : 00:05:ad:00:00:04:e5:1cport-num : 1chassis-guid : 00:00:00:00:00:00:00:00slot-num : 0ext-port-num : 0error-type : xmit-rateport-error : 2node-guid : 00:05:ad:00:00:04:e5:24port-num : 1chassis-guid : 00:00:00:00:00:00:00:00slot-num : 0ext-port-num : 0error-type : rcv-rateRelated Commands
show pm connection monitors, page 5-19
config pm monitor poll-interval
To configure the polling interval at which the PM monitors ports in the network, use the config pm monitor poll-interval command.
config pm monitor poll-interval seconds
Syntax Description
Defaults
This value defaults to 10.
Usage Guidelines
This command configures the polling interval at which the PM monitors ports in the network.
Examples
ib_sm> show pm monitor config================================================================================PM monitor configuration================================================================================state : enabled-cisco-switchespoll-interval : 10 secondsstart-delay : 60 secondsib_sm> config pm monitor poll-interval 30ib_sm> show pm monitor config================================================================================PM monitor configuration================================================================================state : enabled-cisco-switchespoll-interval : 30 secondsstart-delay : 5 secondsRelated Commands
show pm monitor config, page 5-24
config pm monitor start-delay
To configure the Performance Monitoring start delay value, use the config pm port monitor start-delay command.
config pm monitor start-delay seconds
Syntax Description
Defaults
This value defaults to 60 seconds.
Usage Guidelines
The start delay determines how long the PM waits after it is enabled to begin to gather counter information.
Examples
ib_sm> config pm monitor start-delay 60Related Commands
show pm monitor config, page 5-24
config pm monitor state
To enable or disable performance monitoring, use the config pm monitor state command.
config pm monitor state {disabled | enabled | enabled-cisco-switches | enabled-all}
Syntax Description
Defaults
Disabled by default.
Usage Guidelines
If you use enabled-cisco-switches, only ports on switches running the port_agent software are monitored. This keyword allows the monitoring to be distributed through the network, which allows the PM to monitor ports without polling.
Examples
ib_sm> show pm monitor config================================================================================PM monitor configuration================================================================================state : disabledpoll-interval : 10 secondsstart-delay : 60 secondsib_sm> config pm monitor state enabled-cisco-switchesib_sm> show pm monitor config================================================================================PM monitor configuration================================================================================state : enabled-cisco-switchespoll-interval : 10 secondsstart-delay : 60 secondsRelated Commands
show pm monitor config, page 5-24
config pm monitored port
To add or remove a port from the list of monitored ports, use the config pm monitored port command.
config pm monitored port {add | remove} guid port
Syntax Description
add
Adds the specified port.
remove
Removes the specified port.
guid
Specifies the GUID of the node on which the port resides.
port
Specifies the port to add or remove.
Defaults
By default, the list of monitored ports is empty.
Usage Guidelines
This command adds or removes a port from the list of ports being monitored by the PM.
Examples
ib_sm> config pm monitored port add 00:05:ad:00:00:04:e5:24 1ib_sm> config pm monitored port add 00:05:ad:00:00:04:e4:4c 1ib_sm> config pm monitored port add 00:05:ad:00:00:04:e5:1c 1ib_sm> config pm monitored port add 00:05:ad:00:00:04:e5:64 1ib_sm> show pm monitored ports================================================================================All PM Monitored Ports================================================================================subnet-prefix : fe:80:00:00:00:00:00:00node-guid : 00:05:ad:00:00:04:e4:4cport-num : 1subnet-prefix : fe:80:00:00:00:00:00:00node-guid : 00:05:ad:00:00:04:e5:1cport-num : 1subnet-prefix : fe:80:00:00:00:00:00:00node-guid : 00:05:ad:00:00:04:e5:24port-num : 1subnet-prefix : fe:80:00:00:00:00:00:00node-guid : 00:05:ad:00:00:04:e5:64port-num : 1Related Commands
show pm monitored ports, page 5-25
config pm port counter access
To grant port counter access, use the config pm port counter access command.
config pm port counter access enabled | disabled
Syntax Description
Defaults
This setting is enabled by default.
Usage Guidelines
This command enables or disables the port counter feature.
Examples
ib_sm> show pm port counter access================================================================================PM Port Counter Access================================================================================port-counter-access : enabledib_sm> config pm port counter access disabledib_sm> show pm port counter access================================================================================PM Port Counter Access================================================================================port-counter-access : disabledib_sm> config pm port counter access enabledib_sm> show pm port counter access================================================================================PM Port Counter Access================================================================================port-counter-access : enabledRelated Commands
show pm port counter access, page 5-26
config pm threshold
To configure the available threshold values for the Performance Monitoring feature, use the config pm threshold command.
config pm threshold threshold value
Syntax Description
Defaults
By default, all thresholds are configured to "none."
Usage Guidelines
Each threshold is checked at every polling interval and any port having a counter (or rate) exceeding a specified threshold is flagged.
The xmit-rate and rcv-rate thresholds are specified as a percentage of available port bandwidth. All other thresholds are specified as absolute counter values.
Examples
ib_sm> config pm threshold xmit-rate 1ib_sm> config pm threshold rcv-rate 1
Note
Related Commands
config priority
To configure the priority of the Subnet Manager, use the config priority command.
config priority integer
Syntax Description
Defaults
This value defaults to 0.
Note
•
•
•
Usage Guidelines
This command configures the Subnet Manager priority. The default value that is compiled into the Subnet Manager is 0, but the invocation script that is shipped with the HSM sets the value to 11, so the HSM will take priority over a Cisco switch-based Subnet Manager.
Examples
ib_sm> config priority 12ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config response-timeout
To configure how long the Subnet Manager waits for a response to a MAD packet before retrying the transaction, use the config response-timeout command.
config response-timeout milliseconds
Syntax Description
Defaults
This value defaults to 200.
Usage Guidelines
This command configures how long the Subnet Manager waits (in milliseconds) for a response to a MAD packet before retrying the transaction. Configure the mad-retries parameter to specify the number of times that the transaction is retried before it is aborted.
Examples
ib_sm> config response-timeout 250ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledib_sm> config wait-report-response falseRelated Commands
config route-around chassis
To create or delete a route-around entry for a chassis, use the config route-around chassis command.
config route-around chassis {create | delete} chassis-guid
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command creates or deletes a route-around entry for a chassis.
Note
Examples
ib_sm> config route-around chassis create 00:05:ad:00:01:00:d0:50ib_sm> show route-around================================================================================All Route-Around entries================================================================================subnet-prefix : fe:80:00:00:00:00:00:00type : chassischassis-guid : 00:05:ad:00:01:00:d0:50Related Commands
config route-around node
To create or delete a route-around entry for a node, use the config route-around node command.
config route-around node {create | delete} node-guid
Syntax Description
create
Creates a route-around entry for a node.
delete
Deletes a route-around entry for a node.
node-guid
Specifies the GUID of the node for which you create or delete a route-around entry.
Defaults
This command has no default settings.
Usage Guidelines
This command creates or deletes a route-around entry for a node.
Examples
ib_sm> config route-around node create 00:05:ad:00:00:01:0c:19ib_sm> show route-around================================================================================All Route-Around entries================================================================================subnet-prefix : fe:80:00:00:00:00:00:00type : nodenode-guid : 00:05:ad:00:00:01:0c:19Related Commands
config route-around port
To create or delete a route-around entry for a port, use the config route-around port command.
config route-around port {create | delete} node-guid port
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command creates or deletes a route-around entry for a port.
Examples
ib_sm> config route-around port create 00:05:ad:00:00:01:0c:19 6ib_sm> show route-around================================================================================All Route-Around entries================================================================================subnet-prefix : fe:80:00:00:00:00:00:00type : portnode-guid : 00:05:ad:00:00:01:0c:19port-num : 6Related Commands
config sa-mad-queue-depth
To configure the depth of the kernel MAD queue for incoming SA requests, use the config sa-mad-queue-depth command.
config sa-mad-queue-depth integer
Syntax Description
Defaults
This value defaults to 256.
Usage Guidelines
This command configures the depth of the kernel MAD queue requested by the Subnet Manager for incoming SA MADs.
Note
Examples
ib_sm> config sa-mad-queue-depth 512ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledib_sm> config wait-report-response falseRelated Commands
config sl-vl-mapping oper-vl add
Note
To specify the mapping of SLs to VLs in the subnet, use the config sl-vl-mapping oper-vl add command.
config sl-vl-mapping oper-vl val add sl :vl
Syntax Description
val
Specifies the Operational VL value of the profile.
sl
Specifies the service level value.
vl
Specifies the virtual lane value.
Defaults
This command has no default settings.
Usage Guidelines
This command adds/updates an entry in the SL-to-VL mapping profile that is associated with an operational-vl value.
Note
SL-to-VL-mapping profiles can be provisioned in the Subnet Manager for any valid Operational VL value. The SL-to-VL-mapping profile tables that are programmed at a port are determined by the PortInfo:OperationalVL value.
If QoS is enabled and user-provisioned SL-to-VL-mapping profiles are not available, the Subnet Manager will configure the SL-to-VL-mapping tables of every active port in the subnet so that each of the 0-15 SLs are mapped in a round-robin fashion to the VLs that are operational at the port.
Because of the devault SL-to-VL mapping behavior available when the the QoS feature is enabled, you do not need to provision sl-vl-mapping profiles to bring up the fabric. However, when overriding the default behavior, you should plan your SL/VL management strategy carefully, especially if the IB fabric does not have uniform VL capabilities. Proper planning and implementation enables the subnet to function properly and aids in overall fabric performance.
See the InfiniBand Specification, Volume 1 from the IBTA website for details about the SL-to-VL mapping framework.
Examples
In a subnet with 8 data VLs, the command sequence below isolates traffic marked for SL0 from the rest of the traffic by mapping it exclusively on to VL0.
ib_sm> config sl-vl-mapping oper-vl 4 add 0:0ib_sm> config sl-vl-mapping oper-vl 4 add 1:1ib_sm> config sl-vl-mapping oper-vl 4 add 2:2ib_sm> config sl-vl-mapping oper-vl 4 add 3:3ib_sm> config sl-vl-mapping oper-vl 4 add 4:4ib_sm> config sl-vl-mapping oper-vl 4 add 5:5ib_sm> config sl-vl-mapping oper-vl 4 add 6:6ib_sm> config sl-vl-mapping oper-vl 4 add 7:7ib_sm> config sl-vl-mapping oper-vl 4 add 8:1ib_sm> config sl-vl-mapping oper-vl 4 add 9:2ib_sm> config sl-vl-mapping oper-vl 4 add 10:3ib_sm> config sl-vl-mapping oper-vl 4 add 11:4ib_sm> config sl-vl-mapping oper-vl 4 add 12:5ib_sm> config sl-vl-mapping oper-vl 4 add 13:6ib_sm> config sl-vl-mapping oper-vl 4 add 14:7ib_sm> config sl-vl-mapping oper-vl 4 add 15:1ib_sm> config sl-vl-mapping oper-vl 4 applyRelated Commands
config sl-vl-mapping oper-vl apply
config sl-vl-mapping oper-vl delete
show sl-vl-mapping-config, page 5-37
config sl-vl-mapping oper-vl apply
To apply the mapping of SLs to VLs in the subnet after using config sl-vl-mapping oper-vl add, use the config sl-vl-mapping oper-vl apply command.
config sl-vl-mapping oper-vl val apply
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command applies the mapping of SLs to VLs in the subnet. SL-to-VL mapping profiles provisioned in the Subnet Manager with the config sl-vl-mapping oper-vl val add command are not applied to the subnet until they are explicitly committed with the apply command. This command commits a pending SL-to-VL mapping profile, triggering the Subnet Manager to apply the changes to all eligible (active) ports in the subnet.
Examples
ib_sm> config sl-vl-mapping oper-vl 4 add 0:0ib_sm> config sl-vl-mapping oper-vl 4 add 1:1ib_sm> config sl-vl-mapping oper-vl 4 add 2:2ib_sm> config sl-vl-mapping oper-vl 4 add 3:3ib_sm> config sl-vl-mapping oper-vl 4 add 4:4ib_sm> config sl-vl-mapping oper-vl 4 add 5:5ib_sm> config sl-vl-mapping oper-vl 4 add 6:6ib_sm> config sl-vl-mapping oper-vl 4 add 7:7ib_sm> config sl-vl-mapping oper-vl 4 add 8:1ib_sm> config sl-vl-mapping oper-vl 4 add 9:2ib_sm> config sl-vl-mapping oper-vl 4 add 10:3ib_sm> config sl-vl-mapping oper-vl 4 add 11:4ib_sm> config sl-vl-mapping oper-vl 4 add 12:5ib_sm> config sl-vl-mapping oper-vl 4 add 13:6ib_sm> config sl-vl-mapping oper-vl 4 add 14:7ib_sm> config sl-vl-mapping oper-vl 4 add 15:1ib_sm> config sl-vl-mapping oper-vl 4 applyRelated Commands
config sl-vl-mapping oper-vl add
config sl-vl-mapping oper-vl delete
show sl-vl-mapping-config, page 5-37
config sl-vl-mapping oper-vl delete
To delete an SL to VL mapping profile in the subnet, use the config sl-vl-mapping oper-vl delete command.
config sl-vl-mapping oper-vl val delete
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command deletes an existing user provisioned SL- to-VL mapping profile. The Subnet Manager has built-in SL- to-VL mapping tables. When a profile is deleted, ports affected are automatically reprogrammed with the built-in default SL- to-VL mapping tables. The Subnet Manager has a built-in SL-to-VL mapping scheme that includes a round robin of the 16 SLs to the VLs that are operational at a port.
Examples
ib_sm> config sl-vl-mapping oper-vl 4 deleteRelated Commands
config sl-vl-mapping oper-vl add
config sl-vl-mapping oper-vl apply
show sl-vl-mapping-config, page 5-37
config sm-key
To configure the sm-key of the Subnet Manager, use the config sm-key command.
config sm-key key
Syntax Description
Defaults
This value defaults to 00:00:00:00:00:00:00:00 (8 bytes).
Usage Guidelines
This Subnet Manager key is a value used by Subnet Managers in a network to validate one another.
Examples
ib_sm> config sm-key 00:00:00:00:00:00:00:ffib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config span
To configure a Switched Port Analyzer (SPAN), use the config span command.
config span {create | delete} src-node-guid src-port dst-node-guid dst-port
Syntax Description
Defaults
This command has no defaults.
Usage Guidelines
This command configures a SPAN. A SPAN mirrors the traffic ingressing a port and routes it to a destination port at a specified node. The destination port must be on the same node as the source port.
Examples
ib_sm> config span create 00:05:ad:00:00:00:18:5d 17 00:05:ad:00:00:00:18:5d 19ib_sm> show span================================================================================All Spanning entries================================================================================src-node-guid : 00:05:ad:00:00:00:18:5dsrc-port : 17dst-node-guid : 00:05:ad:00:00:00:18:5ddst-port : 19state : activestate-detail : noneib_sm> show span -s================================================================================All Spanning entries================================================================================src-node-guid src-port dst-node-guid dst-port state================================================================================00:05:ad:00:00:00:18:5d 17 00:05:ad:00:00:00:18:5d 19 activeRelated Commands
config sweep-interval
To configure how frequently the Subnet Manager sweeps an unchanging subnet, use the config sweep-interval command.
config sweep-interval seconds
Syntax Description
Defaults
The value defaults to 10 seconds.
Usage Guidelines
This command configures how frequently the Subnet Manager resweeps an unchanging subnet. The default is to delay 10 seconds between sweeps, unless a change occurs that causes the Subnet Manager to resweep immediately.
Examples
ib_sm> config sweep-interval 15ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config switch-life-time
To configure the Switch Lifetime Limit on all switches in the subnet, use the config switch-life-time command.
config switch-life-time value
Syntax Description
value
Specifies the SLL (SwitchLifetimeLimit), which is defined as 4.096us * 2^value. This integer value represents the power to which 2 is raised.
Defaults
This command defaults to 18 (discard after approximately one second).
Usage Guidelines
This command configures the SwitchLifetimeLimit on all switches in the subnet. This configuration controls how long a packet is allowed to live in a switch before being discarded. The default value of 18 causes packets to be discarded after approximately one second.
For detailed information about the lifetime value, see the InfiniBand specification on the IBTA website.
Examples
ib_sm> config switch-life-time 15ib_sm> show switch================================================================================Subnet Management Switches================================================================================subnet-prefix : fe:80:00:00:00:00:00:00node-guid : 00:05:ad:00:00:01:60:04linear-fdb-cap : 49152random-fdb-cap : 0mcast-fdb-cap : 1024linear-fdb-top : 10240default-port : 0def-pri-mcast-port : 255def-non-pri-mcast-port : 255life-time-value : 15port-state-change : 1lids-per-port : 0partition-enf-cap : 32in-enf-cap : 1out-enf-cap : 1in-filter-raw-pkt-cap : 1out-filter-raw-pkt-cap : 1enhanced-port-0 : noRelated Commands
config sw-link-hoqlife
To configure the Head of Queue Lifetime for switch ports that are attached to other switch ports, use the config sw-link-hoqlife command.
config sw-link-hoqlife value
Syntax Description
value
Specifies an integer value of the Head of Queue Lifetime Limit, which is defined as 4.096us * 2^LV. This integer value represents the power to which 2 is raised.
Defaults
This value defaults to 18.
Usage Guidelines
This command configures the HeadOfQueue Lifetime for switch ports that are attached to other switch ports in the network. This value specifies how long a packet will live at the front of a port queue before being discarded. The default value of 18 means that packets will be discarded after approximately one second. This lifetime is linked to the ca-link-hoqlife.
For detailed information on head-of-queue lifetimes, see the InfiniBand specification on the IBTA website.
Examples
ib_sm> config sw-link-hoqlife 15ib_sm> show config================================================================================Subnet Manager Configuration================================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 12sm-key : 00:00:00:00:00:00:00:ffoper-status : masteract-count : 17975sweep-interval(sec) : 15response-timeout(msec) : 250mad-retries : 7node-timeout : 60master-poll-interval(sec) : 5master-poll-retries : 3max-active-sms : 2LID-mask-control : 2switch-life-time : 15sw-link-hoqlife : 15ca-link-hoqlife : 15max-hops : 5wait-report-response : truesa-mad-queue-depth : 512local-node-retries : 20qos-admin-state : enabledmax-operational-vl : auto-subnetmin-vl-cap-detected : vl0-vl7max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledRelated Commands
config trace
To configure logging on the HSM, use the config trace command.
config trace level flowmask
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command configures the Subnet Manager logging. An especially useful level of logging when problems arise is "config trace 2 0x1000" which is terse logging of generic IB events.
Examples
config trace 2 0x1000Related Commands
None.
config vl-arbitration add
Note
To manage the vl-arbitration table profiles in the subnet, use the config vl-arbitration add command.
config vl-arbitration add [-e block priority | index | vl | weight] [-l high-limit-value] [-n node-guid [-p port-num] ]
Syntax Description
Defaults
This command has no default settings.
Usage Guidelines
This command adds/updates an entry in a VL arbitration profile. Profiles can be provisioned with the scope of "subnet," "node," or "port." A "subnet" scoped profile is used to provision VL arbitration tables and vl-high-limit values of ports that do not have a matching profile at the "node" or "port" scope.
If the [-n node-guid [-p port-num]] option(s) are omitted, the scope of the profile being manipulated is the "subnet."
Note
If QoS is enabled and user-provisioned arbitration profiles are not available, Subnet Manager will configure every active port with a round robin VL arbitration scheme that is equally weighted and prioritized (low).
The scenarios in which it is necessary to provision vl-arbitration profiles are governed primarily by the type and load of traffic flowing in the fabric.
When the QoS feature is enabled in the Subnet Manager, you do not need to provision vt arbitration profiles to bring up the fabric due to the built-in default behavior. However, when overriding the built-in behavior, you should plan your SL/VL management strategy carefully, especially if the IB fabric does not have uniform VL capabilities. Proper planning and implementation enables the subnet to function properly and aids in overall fabric performance.
Examples
The command sequence below shows an example of modifying the subnet vl-arbitration scheme to a pre-emptive, weighted, fair scheme, with VL0 prioritized higher than the rest of the data VLs:
ib_sm> config vl-arbitration add -l 2ib_sm> config vl-arbitration add -e 3:0:0:1ib_sm> config vl-arbitration add -e 1:0:1:1ib_sm> config vl-arbitration add -e 1:1:2:1ib_sm> config vl-arbitration add -e 1:2:3:1ib_sm> config vl-arbitration add -e 1:3:4:1ib_sm> config vl-arbitration add -e 1:4:5:1ib_sm> config vl-arbitration add -e 1:5:6:1ib_sm> config vl-arbitration add -e 1:6:7:1ib_sm> config vl-arbitration applyRelated Commands
show vl-arbitration, page 5-42
show vl-arbitration-config, page 5-44
config vl-arbitration apply
To apply the vl-arbitration table profiles in the subnet, use the config vl-arbitration apply command.
Note
config vl-arbitration apply [-n node-guid [-p port-num]]
Defaults
This command has no default settings.
Usage Guidelines
If the [-n node-guid [-p num] ] option(s) are omitted, the scope of the profile being manipulated is the "subnet."
VL arbitration profiles provisioned in the Subnet Manager with the config vl-arbitration add command are not applied to the subnet until they are explicitly committed with the apply command. This command commits a pending VL arbitration profile, triggering the Subnet Manager to apply the changes to all eligible (active) ports in the subnet.
Examples
ib_sm> config vl-arbitration add -l 2ib_sm> config vl-arbitration add -e 3:0:0:1ib_sm> config vl-arbitration add -e 1:0:1:1ib_sm> config vl-arbitration add -e 1:1:2:1ib_sm> config vl-arbitration add -e 1:2:3:1ib_sm> config vl-arbitration add -e 1:3:4:1ib_sm> config vl-arbitration add -e 1:4:5:1ib_sm> config vl-arbitration add -e 1:5:6:1ib_sm> config vl-arbitration add -e 1:6:7:1Related Commands ib_sm> config vl-arbitration apply ib_sm> config vl-arbitration apply
show vl-arbitration, page 5-42
show vl-arbitration-config, page 5-44
config vl-arbitration delete
To delete the vl-arbitration table profiles in the subnet, use the config vl-arbitration delete command.
config vl-arbitration delete [-n node-guid [-p port-num]]
Syntax Description
-n
Specifies the arbitration tables for the ports of a given node.
node-guid
Specifies a node.
-p
Specifies the arbitration table for the given port.
port-num
Specifies a port.
Defaults
This command has no default settings.
Usage Guidelines
If the [-n node-guid [-p num] ] option(s) are omitted, the scope of the profile being manipulated is the "subnet."
This command deletes an existing user provisioned VL arbitration profile. When a profile is deleted, ports affected are automatically re-programmed with an alternative user provisioned matching profile or with the VL arbitration tables that are built-in with the Subnet Manager . The built-in tables employ a round robin VL arbitration scheme that is equally weighted and equally (low) prioritized across all the VLs operational at a port.
Examples
ib_sm> config vl-arbitration delete
Related Commands
show vl-arbitration, page 5-42
show vl-arbitration-config, page 5-44
config wait-report-response
To specify the behavior of the Subnet Manager when forwarding events to subscribers, use the config wait-report-response command.
config wait-report-response {true | false}
Syntax Description
true
Configures the Subnet Manager to resend events until it receives a response from a subscriber.
false
Configures the Subnet Manager to generate a report once per event subscriber.
Defaults
This value defaults to false.
Usage Guidelines
This command configures the Subnet Manager behavior when forwarding events to subscribers. If set to "true," the Subnet Manager resends events until it receives a SubnAdmReportResp() from a subscriber. If set to "false," (default) it generates only the SubnAdmReport() once per event subscriber.
Examples
ib_sm> show config==============================================================================Subnet Manager Configuration==============================================================================subnet-prefix : fe:80:00:00:00:00:00:00guid : 00:05:ad:00:00:04:e5:25priority : 11sm-key : 00:00:00:00:00:00:00:00oper-status : masteract-count : 3319sweep-interval(sec) : 10response-timeout(msec) : 200mad-retries : 5node-timeout : 10master-poll-interval(sec) : 3master-poll-retries : 2max-active-sms : 0LID-mask-control : 0switch-life-time : 18sw-link-hoqlife : 18ca-link-hoqlife : 18max-hops : 64wait-report-response : falsesa-mad-queue-depth : 256local-node-retries : 10qos-admin-state : disabledmax-operational-vl : auto-linkmin-vl-cap-detected : vl0-v17max-multicast-groups : 20480max-multicast-ports : 12288max-multicast-lids : 1024multicast-lid-overloading : enabledipv6-ND-group-bundling : enabledib_sm> config wait-report-response falseRelated Commands
