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

Performance Management Commands

Table Of Contents

Performance Management Commands

pm reset connection counters

pm reset counters

pm test connection


Performance Management Commands


This chapter describes commands related to the Cisco Performance Management (PM) feature, but it does not include every Performance Management-related command. Commands that configure the PM feature appear in the "Configure Commands" chapter. Commands that display PM configuration output appear in the "Show Commands" chapter. The commands in this chapter represent the PM commands that do not overlap with the other chapters.

This chapter includes the following commands:

pm reset connection counters

pm reset counters

pm test connection

pm reset connection counters

To reset all port counters along a specified connection, use the pm reset connection counters command.

pm reset connection counters src-lid dst-lid

Syntax Description

src-lid

Specifies the source Logical ID of the connection.

dst-lid

Specifies the destination Logical ID of the connection.


Defaults

This command has no default settings.

Usage Guidelines

None.

Examples

ib_sm> pm reset connection counters 904 888
....
Counter reset succeeded.

Related Commands

show pm port counters, page 5-27

pm reset counters

To reset port counters, use the pm reset counters command.

pm reset counters [-n guid [-p port]]

Syntax Description

-n

Resets counters for one node only.

guid

Specifies a node.

-p

Resets counters for one port only.

port

Specifies a port.


Defaults

This command has no default settings.

Usage Guidelines

This command resets all the port counters in the IB subnet, or only the ports on a specified node, or only the specified port. Note that during the delay between resetting the counters and showing the cumulative counters, some ports had activity, which is why the values for some xmit and recv counters are non-zero in the example output.

Examples

ib_sm> pm reset counters
.
Counter reset succeeded.
ib_sm> show pm cumulative counters -n 00:05:ad:00:00:01:60:04


================================================================================
               All PM Cumulative Port Counters for specified node
================================================================================
                 subnet-prefix : fe:80:00:00:00:00:00:00
                     node-guid : 00:05:ad:00:00:01:60:04
                      port-num : 1
                  chassis-guid : 00:05:ad:03:00:01:60:04
                      slot-num : 1
                  ext-port-num : 1
                 data-is-valid : true
                  error-status : not exceeded
            utilization-status : not exceeded
                 symbol-errors : 0
          link-recovery-errors : 0
                    link-downs : 0
                    rcv-errors : 0
         rcv-remote-phy-errors : 0
       rcv-switch-relay-errors : 0
                 xmit-discards : 0
        xmit-constraint-errors : 0
         rcv-constraint-errors : 0
   local-link-integrity-errors : 0
  excessive-buf-overrun-errors : 0
                 vl15-droppeds : 0
                     xmit-data : 6624
                      rcv-data : 6624
                     xmit-pkts : 92
                      rcv-pkts : 92
                     xmit-rate : 0 %
                      rcv-rate : 0 %

                 subnet-prefix : fe:80:00:00:00:00:00:00
                     node-guid : 00:05:ad:00:00:01:60:04
                      port-num : 2
                  chassis-guid : 00:05:ad:03:00:01:60:04
                      slot-num : 1
                  ext-port-num : 2
                 data-is-valid : true
                  error-status : not exceeded
            utilization-status : not exceeded
                 symbol-errors : 0
          link-recovery-errors : 0
                    link-downs : 0
                    rcv-errors : 0
         rcv-remote-phy-errors : 0
       rcv-switch-relay-errors : 0
                 xmit-discards : 0
        xmit-constraint-errors : 0
         rcv-constraint-errors : 0
   local-link-integrity-errors : 0
  excessive-buf-overrun-errors : 0
                 vl15-droppeds : 0
                     xmit-data : 0
                      rcv-data : 0
                     xmit-pkts : 0
                      rcv-pkts : 0
                     xmit-rate : 0 %
                      rcv-rate : 0 %
...
                 subnet-prefix : fe:80:00:00:00:00:00:00
                     node-guid : 00:05:ad:00:00:01:60:04
                      port-num : 5
                  chassis-guid : 00:05:ad:03:00:01:60:04
                      slot-num : 1
                  ext-port-num : 5
                 data-is-valid : true
                  error-status : not exceeded
            utilization-status : not exceeded
                 symbol-errors : 0
          link-recovery-errors : 0
                    link-downs : 0
                    rcv-errors : 0
         rcv-remote-phy-errors : 0
       rcv-switch-relay-errors : 0
                 xmit-discards : 0
        xmit-constraint-errors : 0
         rcv-constraint-errors : 0
   local-link-integrity-errors : 0
  excessive-buf-overrun-errors : 0
                 vl15-droppeds : 0
                     xmit-data : 432
                      rcv-data : 432
                     xmit-pkts : 6
                      rcv-pkts : 6
                     xmit-rate : 0 %
                      rcv-rate : 0 %

Related Commands

show pm monitored ports, page 5-25

pm test connection

To test the connection between a given source LID and a given destination LID, use the
pm test connection command.

pm test connection src-lid dst-lid

Syntax Description

src-lid

Specifies the source Logical ID of the connection.

dst-lid

Specifies the destination Logical ID of the connection.


Defaults

This command has no default settings.

Usage Guidelines

This command tests the connection between the given source LID and destination LID. This test is done by discovering an intermediate switch along the path from source to destination and by having the switch send a test packet to both source and destination. If it succeeds, the path from source to destination is good.

Examples

(This example shows that the path from the source port to the destination port is good.)
ib_sm> pm test connection 904 888
.
Connection test succeeded.

Related Commands

None.