Cisco High-Performance Subnet Manager for InfiniBand Server Switches, Release 1.3
Configure Commands
Downloads: This chapterpdf (PDF - 575.0KB) The complete bookPDF (PDF - 3.13MB) | Feedback

Configure Commands

Table Of Contents

Configure Commands

config ca-link-hoqlife

config db-sync cold-sync-limit

config db-sync cold-sync-period

config db-sync cold-sync-timeout

config db-sync disable

config db-sync enable

config db-sync max-dbsync-sms

config db-sync new-session-delay

config db-sync poll-interval

config db-sync resync-interval

config db-sync session-timeout

config lmc

config local-node-retries

config mad-retries

config master-poll-interval

config master-poll-retries

config max-active-sms

config max-hops

config max-operational-vl

config multicast-group-ib create

config multicast-group-ib delete

config multicast-group-ipoib create

config multicast-group-ipoib delete

config node-timeout

config partition key

config partition key ipoib

config partition member add

config partition member remove

config partition member type

config pm connection monitor

config pm monitor poll-interval

config pm monitor start-delay

config pm monitor state

config pm monitored port

config pm port counter access

config pm threshold

config priority

config response-timeout

config route-around chassis

config route-around node

config route-around port

config sa-mad-queue-depth

config sl-vl-mapping oper-vl add

config sl-vl-mapping oper-vl apply

config sl-vl-mapping oper-vl delete

config sm-key

config span

config sweep-interval

config switch-life-time

config sw-link-hoqlife

config trace

config vl-arbitration add

config vl-arbitration apply

config vl-arbitration delete

config wait-report-response


Configure Commands


This chapter includes the following commands::

config ca-link-hoqlife

config db-sync cold-sync-limit

config db-sync cold-sync-timeout

config db-sync disable

config db-sync enable

config db-sync max-dbsync-sms

config db-sync new-session-delay

config db-sync poll-interval

config db-sync resync-interval

config db-sync session-timeout

config lmc

config local-node-retries

config mad-retries

config master-poll-interval

config master-poll-retries

config max-active-sms

config max-hops

config max-operational-vl

config multicast-group-ib create

config multicast-group-ib delete

config multicast-group-ipoib create

config multicast-group-ipoib delete

config node-timeout

config partition key

config partition key ipoib

config partition member add

config partition member remove

config partition member type

config pm connection monitor

config pm monitor poll-interval

config pm monitor start-delay

config pm monitor state

config pm monitored port

config pm port counter access

config pm threshold

config priority

config response-timeout

config route-around chassis

config route-around node

config route-around port

config sa-mad-queue-depth

config sl-vl-mapping oper-vl add

config sl-vl-mapping oper-vl apply

config sl-vl-mapping oper-vl delete

config sm-key

config span

config sweep-interval

config switch-life-time

config sw-link-hoqlife

config trace

config vl-arbitration add

config vl-arbitration apply

config vl-arbitration delete

config wait-report-response

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 15
ib_sm> show config
================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

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 4

Related Commands

config db-sync cold-sync-period

config db-sync cold-sync-timeout

show db-sync, page 5-4

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

seconds

Specifies the time period, in seconds, to apply to the cold sync period.


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 60

Related Commands

config db-sync cold-sync-limit

config db-sync cold-sync-timeout

show db-sync, page 5-4

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

seconds

Specifies the time period, in seconds, to apply to the timeout period.


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 5

Related Commands

config db-sync cold-sync-limit

config db-sync cold-sync-period

show db-sync, page 5-4

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 disable
ib_sm> show db-sync

================================================================================
                        DB Sync Configuration and Status
================================================================================
                   admin-state : disabled

Related Commands

config db-sync enable

show db-sync, page 5-4

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 enable
ib_sm> show db-sync

================================================================================
                        DB Sync Configuration and Status
================================================================================
                   admin-state : enabled

Related Commands

config db-sync disable

show db-sync, page 5-4

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 2
ib_sm> show db-sync
================================================================================
                        DB Sync Configuration and Status
================================================================================
              protocol-version : 25
                   admin-state : enabled
          max-backupdbsync-sms : 2
          session-timeout(sec) : 5
            poll-interval(sec) : 2
        cold-sync-timeout(sec) : 5
               cold-sync-limit : 4
         cold-sync-period(sec) : 60
        new-session-delay(sec) : 20
          resync-interval(sec) : 600
                         state : not in-sync

Related Commands

show db-sync, page 5-4

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

seconds

Specifies the time period, in seconds, to apply to the delay period.


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 20

Related Commands

show db-sync, page 5-4

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

seconds

Specifies the time period, in seconds, to apply to the interval.


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 2

Related Commands

show db-sync, page 5-4

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

seconds

Specifies the time period, in seconds, to apply to the interval.


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 600

Related Commands

show db-sync, page 5-4

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

seconds

Specifies the time period, in seconds, to apply to the timeout.


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 5
ib_sm> show db-sync

================================================================================
                        DB Sync Configuration and Status
================================================================================
              protocol-version : 25
                   admin-state : enabled
                max-dbsync-sms : 2
          session-timeout(sec) : 5
            poll-interval(sec) : 2
        cold-sync-timeout(sec) : 5
               cold-sync-limit : 4
         cold-sync-period(sec) : 60
        new-session-delay(sec) : 20
          resync-interval(sec) : 600
                         state : not in-sync

Related Commands

show db-sync, page 5-4

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-sdr

00:05:ad:00:00:04:e4:4c   1     896 	active 4x-sdr
00:05:ad:00:00:04:e5:1c   1     904 	active 4x-sdr
00:05:ad:00:00:04:e5:24   1     888 	active 4x-sdr
00:05:ad:00:00:04:e5:64   1     912 	active 4x-sdr
ib_sm> config lmc 2
ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
              LID-mask-control : 2
ib_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 4x 

00:05:ad:00:00:04:e4:4c   1     897	 active     4x-sdr 4x 
00:05:ad:00:00:04:e5:1c   1     905	 active     4x-sdr 4x 
00:05:ad:00:00:04:e5:24   1     889	 active     4x-sdr 4x 
00:05:ad:00:00:04:e5:64   1     913	 active     4x-sdr 4x 

Related Commands

show config, page 5-3

show port, page 5-31

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 20

ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled
ib_sm> config wait-report-response false

Related Commands

show config, page 5-3

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 7
ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled
ib_sm> config wait-report-response false

Related Commands

config response-timeout

show config, page 5-3

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

seconds

Specifies the poll interval, in seconds.


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:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

config master-poll-retries

show config, page 5-3

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

integer

Specifies the number of retries.


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 3

ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

config master-poll-interval

show config, page 5-3

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

integer

Specifies the number of active Subnet Managers.


Defaults

This value defaults to 0.

Usage Guidelines

This command is not currently used.

Examples

ib_sm> config max-active-sms 2

ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

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

integer

Specifies the number of switches to check.


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 By restricting the length of paths that the Subnet Manager will consider, the Subnet Manager might choose paths that are optimal for distance but not for other factors, such as uniform link capacity.


ib_sm> config max-hops 5
ib_sm> show config
================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

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

value

Specifies the value.


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:

To limit the number of operational data VLs in a fabric, which increases the buffer allocation per VL and could lead to increased link throughput for certain traffic patterns

To achieve uniformity of configured VLs across a fabric with different VL capabilities. A maximum operational VL value can be set either explicitly to the lowest VLCap value of active ports in the fabric or to the "auto detect" value of auto-subnet. The "auto detect" setting allows the Subnet Manager to determine this optimal value duringa fabric sweep and to configure the active ports in the fabric accordingly.


Note To configure the max-operational-vl value, you must enable the QoS feature in the Subnet Manager.


Examples

ib_sm> config max-operational-vl auto-subnet

ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

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

mgid

Specifies the global ID to apply to the multicast group.

-p

Applies a partition key to the multicast group.

p_key

Specifies the partition key to apply to the multicast group.

-q

Applies a qkey to the multicast group.

qkey

Specifies the Qkey to apply to the multicast group.

-m

Applies a maximum transmission unit to the multicast group.

mtu

Specifies the maximum transmission unit to apply to the multicast group.

-r

Applies a rate to the multicast group.

rate

Specifies the rate to apply to the multicast group.

-sl

Indicates that the service level (SL) parameter is present.

sl

Specifies a service level.

-s

Indicates that a scope parameter is present.

scope

Specifies a scope parameter.


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:ff
ib_sm> 
ib_sm> show multicast
================================================================================
                              All Multicast Groups
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          mgid : ff:12:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e
                         q-key : 00:00:00:0b
                          mlid : 49155
                           mtu : 0
                       t-class : 0
                         p_key : ff:ff
                          rate : 10 gbps
              packet-life-time : 2
                            sl : 0
                    flow-label : 00:00:00
                     hop-limit : 0
                         scope : link-local
               user-configured : true
       multicast-group-members : none


                 subnet-prefix : fe:80:00:00:00:00:00:00
                          mgid : ff:12:40:1b:81:81:00:00:00:00:00:00:ff:ff:ff:ff
                         q-key : 80:00:00:0b
                          mlid : 49154
                           mtu : 0
                       t-class : 0
                         p_key : 81:81
                          rate : 10 gbps
              packet-life-time : 2
                            sl : 0
                    flow-label : 00:00:00
                     hop-limit : 0
                         scope : link-local
               user-configured : true

       multicast-group-members : none

subnet-prefix : fe:80:00:00:00:00:00:00
                          mgid : ff:12:40:1b:ff:ff:00:00:00:00:00:00:00:00:00:01
                         q-key : 00:00:00:0b
                          mlid : 49153
                           mtu : 2048
                       t-class : 0
                         p_key : ff:ff
                          rate : 2500 mbps
              packet-life-time : 2
                            sl : 0
                    flow-label : 00:00:00
                     hop-limit : 0
                         scope : link-local
               user-configured : false

       multicast-group-members : none

Related Commands

show multicast, page 5-8

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

mgid

Specifies the global ID of the multicast group.


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:ff

Related Commands

show multicast, page 5-8

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

p_key

Partition key to apply to the multicast group.

-q

Applies a qkey to the multicast group.

qkey

Specifies the Qkey to apply to the multicast group.

-m

Applies a maximum transmission unit to the multicast group.

mtu

Specifies the maximum transmission unit to apply to the multicast group.

-r

Applies a rate to the multicast group.

rate

Specifies the rate to apply to the multicast group.

-l

Indicates that the service level (SL) parameter is present.

sl

Specifies a service level.

-s

Indicates that a scope parameter is present.

scope

Specifies a scope parameter.


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:81
ib_sm> config multicast-group-ipoib create 81:81
ib_sm> show multicast

================================================================================
                              All Multicast Groups
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          mgid : ff:12:40:1b:81:81:00:00:00:00:00:00:ff:ff:ff:ff
                         q-key : 80:00:00:0b
                          mlid : 49154
                           mtu : 0
                       t-class : 0
                         p_key : 81:81
                          rate : 10 gbps
              packet-life-time : 2
                            sl : 0
                    flow-label : 00:00:00
                     hop-limit : 0
                         scope : link-local
               user-configured : true

       multicast-group-members : none


                 subnet-prefix : fe:80:00:00:00:00:00:00
                          mgid : ff:12:40:1b:ff:ff:00:00:00:00:00:00:00:00:00:01
                         q-key : 00:00:00:0b
                          mlid : 49153
                           mtu : 2048
                       t-class : 0
                         p_key : ff:ff
                          rate : 2500 mbps
              packet-life-time : 2
                            sl : 0
                    flow-label : 00:00:00
                     hop-limit : 0
                         scope : link-local
               user-configured : false

       multicast-group-members :

Related Commands

config partition key

show multicast, page 5-8

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:81
ib_sm> show multicast

================================================================================
                              All Multicast Groups
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          mgid : ff:12:40:1b:ff:ff:00:00:00:00:00:00:00:00:00:01
                         q-key : 00:00:00:0b
                          mlid : 49153
                           mtu : 2048
                       t-class : 0
                         p_key : ff:ff
                          rate : 2500 mbps
              packet-life-time : 2
                            sl : 0
                    flow-label : 00:00:00
                     hop-limit : 0
                         scope : link-local
               user-configured : false

Related Commands

show multicast, page 5-8

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

seconds

Specifies the timeout interval, in seconds.


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 60
ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

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

create

Creates a partition.

delete

Deletes a partition.

p_key

Partition key.

-i

(Optional) Configures whether or not IPoIB is enabled for this partition.

enabled

(Optional) Specifies that IPoIB is enabled

disabled

(Optional) Specifies that IPoIB is disabled.


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 disabled
ib_sm> show partition

================================================================================
                                 All Partitions
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                         p-key : 81:81
                         ipoib : disabled

             partition-members : none

                 subnet-prefix : fe:80:00:00:00:00:00:00
                         p-key : ff:ff
                         ipoib : enabled

             partition-members : 
                     node-guid : 00:05:ad:00:00:01:60:04
                      port-num : 0
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e4:4c
                      port-num : 1
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e5:1c
                      port-num : 1
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e5:24
                      port-num : 1
                   member-type : full


                     node-guid : 00:05:ad:00:00:04:e5:64
                      port-num : 1
                   member-type : full

Related Commands

config partition key ipoib

config partition member add

config partition member remove

config partition member type

show partition, page 5-14

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 disabled
ib_sm> show partition

================================================================================
                                 All Partitions
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                         p-key : 81:81
                         ipoib : disabled

             partition-members : none

                 subnet-prefix : fe:80:00:00:00:00:00:00
                         p-key : ff:ff
                         ipoib : enabled

             partition-members : 
                     node-guid : 00:05:ad:00:00:01:60:04
                      port-num : 0
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e4:4c
                      port-num : 1
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e5:1c
                      port-num : 1
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e5:24
                      port-num : 1
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e5:64
                      port-num : 1
                   member-type : full

Related Commands

config partition key

config partition member add

config partition member remove

config partition member type

show partition, page 5-14

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

p_key

Specifies the partition key of the partition to which to add the port.

guid

Specifies the GUID of the node on which the port resides.

port

Specifies the port to add to the partition.

full

Applies full membership to the port.

limited

Applies limited membership to the port.


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 full
ib_sm> config partition member add 81:81 00:05:ad:00:00:04:e5:1c 1 limited
ib_sm> config partition member add 81:81 00:05:ad:00:00:04:e5:24 1 full
ib_sm> show partition -k 81:81

================================================================================
                         Partition for specified P_Key
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                         p-key : 81:81
                         ipoib : disabled

             partition-members : 
                     node-guid : 00:05:ad:00:00:04:e4:4c
                      port-num : 1
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e5:1c
                      port-num : 1
                   member-type : limited

                     node-guid : 00:05:ad:00:00:04:e5:24
                      port-num : 1
                   member-type : full

Related Commands

config partition key

config partition key ipoib

config partition member remove

config partition member type

show partition, page 5-14

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 1
ib_sm> show partition -k 81:81

================================================================================
                         Partition for specified P_Key
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                         p-key : 81:81
                         ipoib : disabled

             partition-members : 
                     node-guid : 00:05:ad:00:00:04:e4:4c
                      port-num : 1
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e5:24
                      port-num : 1
                   member-type : full

Note This example is a continuation of the example for config partition member add.


Related Commands

config partition key

config partition key ipoib

config partition member add

config partition member type

show partition, page 5-14

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

p_key

Specifies the partition key of the partition that includes the port whose type you want to change.

guid

Specifies the GUID of the node on which the port resides.

port

Specifies the port that is a member of the partition.

full

Applies full membership to the port.

limited

Applies limited membership to the port.


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 limited
ib_sm> show partition -k 81:81

================================================================================
                         Partition for specified P_Key
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                         p-key : 81:81
                         ipoib : disabled

             partition-members : 
                     node-guid : 00:05:ad:00:00:04:e4:4c
                      port-num : 1
                   member-type : full

                     node-guid : 00:05:ad:00:00:04:e5:24
                      port-num : 1
                   member-type : limited

Note This example is a continuation of the example for config partition member add.


Related Commands

config partition key

config partition key ipoib

config partition member add

config partition member remove

show partition, page 5-14

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

create

Adds a connection to the list of monitored connections.

delete

Removes a connection from the list of monitored connections.

src-lid

Specifies the source LID of the connection.

dst-lid

Specifies the destination LID of the connection.


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 888
ib_sm> show pm connection monitors

================================================================================
                          All PM Monitored Connections
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                       src-lid : 904
                       dst-lid : 888
                  error-status : not exceeded
            utilization-status : not exceeded
                   port-errors : 0
            utilization-errors : 0

ib_sm> show pm connection monitors

================================================================================
                          All PM Monitored Connections
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                       src-lid : 904
                       dst-lid : 888
                  error-status : not exceeded
            utilization-status : exceeded
                   port-errors : 0
            utilization-errors : 2
                    port-error : 1
                     node-guid : 00:05:ad:00:00:04:e5:1c
                      port-num : 1
                  chassis-guid : 00:00:00:00:00:00:00:00
                      slot-num : 0
                  ext-port-num : 0
                    error-type : xmit-rate
                    port-error : 2
                     node-guid : 00:05:ad:00:00:04:e5:24
                      port-num : 1
                  chassis-guid : 00:00:00:00:00:00:00:00
                      slot-num : 0
                  ext-port-num : 0
                    error-type : rcv-rate

Related 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

seconds

Specifies the duration of the poll interval, in seconds.


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-switches
                 poll-interval : 10 seconds
                   start-delay : 60 seconds

ib_sm> config pm monitor poll-interval 30
ib_sm> show pm monitor config

================================================================================
                            PM monitor configuration
================================================================================
                         state : enabled-cisco-switches
                 poll-interval : 30 seconds
                   start-delay : 5 seconds

Related 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

seconds

Specifies the duration of the delay, in seconds.


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 60 

Related 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

disabled

Disables performance monitoring.

enabled

Monitors only ports that have been configured using the config pm monitored port command.

enabled-cisco-switches

Enables performance monitoring on Cisco switches that run Cisco port_agent software and on any ports that have been configured using the config pm monitored port command.

enabled-all

Enables performance monitoring for all ports in the IB fabric.


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 : disabled
                 poll-interval : 10 seconds
                   start-delay : 60 seconds

ib_sm> config pm monitor state enabled-cisco-switches

ib_sm> show pm monitor config

================================================================================
                            PM monitor configuration
================================================================================
                         state : enabled-cisco-switches
                 poll-interval : 10 seconds
                   start-delay : 60 seconds

Related 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 1
ib_sm> config pm monitored port add 00:05:ad:00:00:04:e4:4c 1
ib_sm> config pm monitored port add 00:05:ad:00:00:04:e5:1c 1
ib_sm> config pm monitored port add 00:05:ad:00:00:04:e5:64 1
ib_sm> show pm monitored ports

================================================================================
                             All PM Monitored Ports
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                     node-guid : 00:05:ad:00:00:04:e4:4c
                      port-num : 1

                 subnet-prefix : fe:80:00:00:00:00:00:00
                     node-guid : 00:05:ad:00:00:04:e5:1c
                      port-num : 1

                 subnet-prefix : fe:80:00:00:00:00:00:00
                     node-guid : 00:05:ad:00:00:04:e5:24
                      port-num : 1

                 subnet-prefix : fe:80:00:00:00:00:00:00
                     node-guid : 00:05:ad:00:00:04:e5:64
                      port-num : 1

Related 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

enabled

Enables the port counter feature.

disabled

Disables the port counter feature.


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 : enabled

ib_sm> config pm port counter access disabled
ib_sm> show pm port counter access

================================================================================
                             PM Port Counter Access
================================================================================
           port-counter-access : disabled

ib_sm> config pm port counter access enabled
ib_sm> show pm port counter access

================================================================================
                             PM Port Counter Access
================================================================================
           port-counter-access : enabled

Related 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

threshold

The following thresholds are available:

symbol-errors

link-recovery-errors

link-downs

rcv-errors

rcv-remote-phy-errors

rcv-switch-relay-errors

xmit-discards

xmit-constraint-errors

rcv-constraint-errors

local-link-integrity-errors

excessive-buf-overrun-errors

vl15-droppeds

xmit-rate

rcv-rate

value

The following options are available:

none

a decimal value


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 1
ib_sm> config pm threshold rcv-rate 1

Note This example sets triggers on all links so when any port exceeds 1% link utilization for a polling interval, on either transmit or receive, the PM will trigger on those ports that exceed the specified threshold.


Related Commands

show pm threshold, page 5-30

config priority

To configure the priority of the Subnet Manager, use the config priority command.

config priority integer

Syntax Description

integer

Specifies the priority of the Subnet Manager.


Defaults

This value defaults to 0.


Note HSM values and embedded Subnet Manager values differ.


Switch/embedded default priority is 10.

HSM default priority is 0.

The default run script for the HSM invokes the HSM at a priority of 11.

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 12
ib_sm> show config
================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

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

milliseconds

Specifies the timeout interval, in milliseconds.


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 250
ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled
ib_sm> config wait-report-response false

Related Commands

config mad-retries

show config, page 5-3

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

create

Creates a route-around entry for a chassis.

delete

Deletes a route-around entry for a chassis.

chassis-guid

Specifies the GUID of the chassis 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 chassis.


Note A chassis GUID is the unique GUID that identifies a chassis. It is based on the system image GUID of any switch node inside the chassis, with the fifth byte zeroed.


Examples

ib_sm> config route-around chassis create 00:05:ad:00:01:00:d0:50
ib_sm> show route-around

================================================================================
                            All Route-Around entries
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          type : chassis
                  chassis-guid : 00:05:ad:00:01:00:d0:50

Related Commands

show route-around, page 5-34

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:19
ib_sm> show route-around

================================================================================
                            All Route-Around entries
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          type : node
                     node-guid : 00:05:ad:00:00:01:0c:19

Related Commands

show route-around, page 5-34

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

create

Creates a route-around entry for a port.

delete

Deletes a route-around entry for a port.

node-guid

Specifies the GUID of the node for which you create or delete a route-around entry.

port

Specifies a port 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 port.

Examples

ib_sm> config route-around port create 00:05:ad:00:00:01:0c:19 6
ib_sm> show route-around

================================================================================
                            All Route-Around entries
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          type : port
                     node-guid : 00:05:ad:00:00:01:0c:19
                      port-num : 6

Related Commands

show route-around, page 5-34

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

integer

Specifies the queue depth.


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 This command is not applicable to HSM on OFED.


Examples

ib_sm> config sa-mad-queue-depth 512
ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled
ib_sm> config wait-report-response false

Related Commands

show config, page 5-3

config sl-vl-mapping oper-vl add


Note The QoS feature must be enabled in the Subnet Manager before you can configure the sl-vl-mapping profiles.


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 Profiles that are configured in the Subnet Manager with the add command are not applied to the subnet until they are explicitly committed with the apply command.


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:0
ib_sm> config sl-vl-mapping oper-vl 4 add 1:1
ib_sm> config sl-vl-mapping oper-vl 4 add 2:2
ib_sm> config sl-vl-mapping oper-vl 4 add 3:3
ib_sm> config sl-vl-mapping oper-vl 4 add 4:4
ib_sm> config sl-vl-mapping oper-vl 4 add 5:5
ib_sm> config sl-vl-mapping oper-vl 4 add 6:6
ib_sm> config sl-vl-mapping oper-vl 4 add 7:7
ib_sm> config sl-vl-mapping oper-vl 4 add 8:1
ib_sm> config sl-vl-mapping oper-vl 4 add 9:2
ib_sm> config sl-vl-mapping oper-vl 4 add 10:3
ib_sm> config sl-vl-mapping oper-vl 4 add 11:4
ib_sm> config sl-vl-mapping oper-vl 4 add 12:5
ib_sm> config sl-vl-mapping oper-vl 4 add 13:6
ib_sm> config sl-vl-mapping oper-vl 4 add 14:7
ib_sm> config sl-vl-mapping oper-vl 4 add 15:1
ib_sm> config sl-vl-mapping oper-vl 4 apply

Related Commands

config sl-vl-mapping oper-vl apply

config sl-vl-mapping oper-vl delete

show sl-vl-mapping, page 5-36

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

val

Specifies the Operational VL value of the profile.


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:0
ib_sm> config sl-vl-mapping oper-vl 4 add 1:1
ib_sm> config sl-vl-mapping oper-vl 4 add 2:2
ib_sm> config sl-vl-mapping oper-vl 4 add 3:3
ib_sm> config sl-vl-mapping oper-vl 4 add 4:4
ib_sm> config sl-vl-mapping oper-vl 4 add 5:5
ib_sm> config sl-vl-mapping oper-vl 4 add 6:6
ib_sm> config sl-vl-mapping oper-vl 4 add 7:7
ib_sm> config sl-vl-mapping oper-vl 4 add 8:1
ib_sm> config sl-vl-mapping oper-vl 4 add 9:2
ib_sm> config sl-vl-mapping oper-vl 4 add 10:3
ib_sm> config sl-vl-mapping oper-vl 4 add 11:4
ib_sm> config sl-vl-mapping oper-vl 4 add 12:5
ib_sm> config sl-vl-mapping oper-vl 4 add 13:6
ib_sm> config sl-vl-mapping oper-vl 4 add 14:7
ib_sm> config sl-vl-mapping oper-vl 4 add 15:1
ib_sm> config sl-vl-mapping oper-vl 4 apply

Related Commands

config sl-vl-mapping oper-vl add

config sl-vl-mapping oper-vl delete

show sl-vl-mapping, page 5-36

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

val

Specifies the Operational VL value of the profile.


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 delete

Related Commands

config sl-vl-mapping oper-vl add

config sl-vl-mapping oper-vl apply

show sl-vl-mapping, page 5-36

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

key

Specifies a unique identifier in the format nn:nn.


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:ff
ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

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

create

Configures a SPAN.

delete

Deletes a SPAN.

src-node-guid

Specifies the GUID of the source node.

src-port

Specifies the source port.

dst-node-guid

Specifies GUID of the destination node.

dst-port

Specifies the destination port.


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 19
ib_sm> show span

================================================================================
                              All Spanning entries
================================================================================
                 src-node-guid : 00:05:ad:00:00:00:18:5d
                      src-port : 17
                 dst-node-guid : 00:05:ad:00:00:00:18:5d
                      dst-port : 19
                         state : active
                  state-detail : none

ib_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        active

Related Commands

show span, page 5-38

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

seconds

Specifies the sweep interval, in seconds.


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 15
ib_sm> show config

================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

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 15
ib_sm> show switch

================================================================================
                           Subnet Management Switches
================================================================================
             subnet-prefix : fe:80:00:00:00:00:00:00
                 node-guid : 00:05:ad:00:00:01:60:04
            linear-fdb-cap : 49152
            random-fdb-cap : 0
             mcast-fdb-cap : 1024
            linear-fdb-top : 10240
              default-port : 0
        def-pri-mcast-port : 255
    def-non-pri-mcast-port : 255
           life-time-value : 15
         port-state-change : 1
             lids-per-port : 0
         partition-enf-cap : 32
                in-enf-cap : 1
               out-enf-cap : 1
     in-filter-raw-pkt-cap : 1
    out-filter-raw-pkt-cap : 1
           enhanced-port-0 : no

Related Commands

show config, page 5-3

show switch, page 5-40

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 15
ib_sm> show config
================================================================================
                          Subnet Manager Configuration
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 12
                        sm-key : 00:00:00:00:00:00:00:ff
                   oper-status : master
                     act-count : 17975
           sweep-interval(sec) : 15
        response-timeout(msec) : 250
                   mad-retries : 7
                  node-timeout : 60
     master-poll-interval(sec) : 5
           master-poll-retries : 3
                max-active-sms : 2
              LID-mask-control : 2
              switch-life-time : 15
               sw-link-hoqlife : 15
               ca-link-hoqlife : 15
                      max-hops : 5
          wait-report-response : true
            sa-mad-queue-depth : 512
            local-node-retries : 20
               qos-admin-state : enabled
            max-operational-vl : auto-subnet
           min-vl-cap-detected : vl0-vl7 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled

Related Commands

show config, page 5-3

config trace

To configure logging on the HSM, use the config trace command.

config trace level flowmask

Syntax Description

level

Specifies the level of verbosity of the trace messages. A higher levels means that the trace message is more verbose; a lower level means that the trace message is less verbose.

flowmask

Specifies a number that represents type of tracing to enable.


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 0x1000

Related Commands

None.

config vl-arbitration add


Note The QoS feature must be enabled in the Subnet Manager before you can configure the vl-arbitration profiles.


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

-e

(Optional) Specifies an entry in the arbitration table.

block priority

(Optional) Specifies an arbitration table block value.

index

(Optional) Specifies the index within a block.

vl

(Optional) Specifies a VL value.

weight

(Optional) Specifies a weight value.

-l

(Optional) Specifies a high limit value.

high-limit-value

(Optional) Specifies a high limit value.

-n

(Optional) Displays the arbitration tables for the ports of a given node.

node-guid

(Optional) Specifies a node.

-p

(Optional) Displays the arbitration table for the given port.

port-num

(Optional) Specifies a port.


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 Profiles configured in the Subnet Manager with the add command are not applied to the subnet until they are explicitly committed with the apply command.


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 2
ib_sm> config vl-arbitration add -e 3:0:0:1
ib_sm> config vl-arbitration add -e 1:0:1:1
ib_sm> config vl-arbitration add -e 1:1:2:1
ib_sm> config vl-arbitration add -e 1:2:3:1
ib_sm> config vl-arbitration add -e 1:3:4:1
ib_sm> config vl-arbitration add -e 1:4:5:1
ib_sm> config vl-arbitration add -e 1:5:6:1
ib_sm> config vl-arbitration add -e 1:6:7:1
ib_sm> config vl-arbitration apply

Related Commands

config vl-arbitration apply

config vl-arbitration delete

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 Profiles configured in the Subnet Manager with the add command are not applied to the subnet until they are explicitly committed with the apply command.


config vl-arbitration apply [-n node-guid [-p port-num]]

-n

(Optional) Specifies the arbitration tables for the ports of a given node.

node-guid

(Optional) Specifies a node.

-p

(Optional) Specifies the arbitration table for the given port.

port-num

(Optional) Specifies a port number.


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 2
ib_sm> config vl-arbitration add -e 3:0:0:1
ib_sm> config vl-arbitration add -e 1:0:1:1
ib_sm> config vl-arbitration add -e 1:1:2:1
ib_sm> config vl-arbitration add -e 1:2:3:1
ib_sm> config vl-arbitration add -e 1:3:4:1
ib_sm> config vl-arbitration add -e 1:4:5:1
ib_sm> config vl-arbitration add -e 1:5:6:1
ib_sm> config vl-arbitration add -e 1:6:7:1

Related Commands ib_sm> config vl-arbitration apply ib_sm> config vl-arbitration apply

config vl-arbitration add

config vl-arbitration delete

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

config vl-arbitration add

config vl-arbitration apply

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:00
                          guid : 00:05:ad:00:00:04:e5:25
                      priority : 11
                        sm-key : 00:00:00:00:00:00:00:00
                   oper-status : master
                     act-count : 3319
           sweep-interval(sec) : 10
        response-timeout(msec) : 200
                   mad-retries : 5
                  node-timeout : 10
     master-poll-interval(sec) : 3
           master-poll-retries : 2
                max-active-sms : 0
              LID-mask-control : 0
              switch-life-time : 18
               sw-link-hoqlife : 18
               ca-link-hoqlife : 18
                      max-hops : 64
          wait-report-response : false
            sa-mad-queue-depth : 256
            local-node-retries : 10
               qos-admin-state : disabled
            max-operational-vl : auto-link
           min-vl-cap-detected : vl0-v17 
          max-multicast-groups : 20480
           max-multicast-ports : 12288
            max-multicast-lids : 1024
     multicast-lid-overloading : enabled
        ipv6-ND-group-bundling : enabled
ib_sm> config wait-report-response false

Related Commands

show config, page 5-3