Show Commands

show aaa accounting

To display the accounting configuration, use the show aaa accounting command.

show aaa accounting

Syntax Description

This command has no other arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(x)

This command was introduced.

Usage Guidelines

None.

Examples

The following example displays accounting log configuration:


switch# show aaa accounting
         default: local

show aaa authentication

To display configured authentication information, use the show aaa authentication command.

show aaa authentication [login {error-enable | | }]

Syntax Description

login error-enable

(Optional) Displays the authentication login error message enable configuration.

login mschap

(Optional) Displays the authentication login MS-CHAP enable configuration.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.3(1)

This command was introduced.

2.0(x)

Added the login error-enable option.

3.0(1)

Added the login mschap option.

Usage Guidelines

None.

Examples

The following example displays the configured authentication parameters:


switch# show aaa authentication
         default: group TacServer local none
         console: local
         iscsi: local
         dhchap: local

The following example displays the authentication login error message enable configuration:


switch# show aaa authentication login error-enable
disabled

The following example displays the authentication login MS-CHAP enable configuration:


switch# show aaa authentication login mschap
disabled

show aaa authentication login ascii-authentication

To display configured ascii authentication method, use the show aaa authentication login ascii-authentication command.

show aaa authentication login ascii-authentication

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

NX-OS 4.1(3a)

enable the password aging command changed from show aaa authentication login password-aging enable to show aaa authentication login ascii-authentication.

Usage Guidelines

None.

Examples

The following example shows how to enable ascii authentication:


switch#(config)# aaa authentication login ascii-authentication
switch#(config)#

show aaa authentication login chap enable

To display CHAP authentication for login, use the show aaa authentication login chap enable command.

show aaa authentication login chap enable

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

NX-OS 5.0(1a)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display CHAP authentication for login:


switch# show aaa authentication login chap enable
CHAP is enabled
switch#

show aaa authentication login mschapv2

To display MS-CHAPv2 authentication for login, use the show aaa authentication login mschapv2 command.

show aaa authentication login mschapv2

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

NX-OS 4.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display MS-CHAPv2 authentication for login:


switch# show aaa authentication login mschapv2
MSCHAP V2 is disabled
switch#

show aaa authorization all

To display all authorization information, use the aaa authorization all command.

show aaa authorization all

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

NX-OS 4.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display all authorization information:


switch# show aaa authorization all
AAA command authorization:
         default authorization for config-commands: local
         default authorization for commands: local

show aaa groups

To display configured server groups, use the show aaa groups command.

show aaa groups

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.3(1)

This command was introduced.

Usage Guidelines

None.

Examples

This example shows how to display configured server groups:


switch# show aaa groups
radius
TacServer

show aaa user default-role

To display the AAA user default role configuration, use the show aaa user default-role command.

show aaa user default-role

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes


Any command mode

Command History

Release

Modification

1.3(1)

This command was introduced.

Usage Guidelines

User the aaa user default-role command to configure the AAA user default role.

This command does not require a license.

Examples

This example shows how to display the AAA user default role configuration:


switch# show aaa user default-role
enabled

show accounting log

To display the accounting log contents, use the show accounting log command.

show accounting log [size]

Syntax Description

size

(Optional) Specifies the size of the log to display in bytes. The range is 0 to 250000.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(x)

This command was introduced.

Usage Guidelines

None.

Examples

The following example displays the entire accounting log:


switch# show accounting log 
2002:stop:snmp_1033151784_171.71.49.83:admin:
Fri Sep 27 18:36:24 2002:start:_1033151784:root
Fri Sep 27 18:36:28 2002:update:::fcc configuration requested
Fri Sep 27 18:36:33 2002:start:snmp_1033151793_171.71.49.83:admin
Fri Sep 27 18:36:33 2002:stop:snmp_1033151793_171.71.49.83:admin:
Fri Sep 27 18:39:28 2002:start:snmp_1033151968_171.71.49.96:admin
Fri Sep 27 18:39:28 2002:stop:snmp_1033151968_171.71.49.96:admin:
Fri Sep 27 18:39:28 2002:start:_1033151968:root
Fri Sep 27 18:39:31 2002:update:::fcc configuration requested
Fri Sep 27 18:39:37 2002:start:snmp_1033151977_171.71.49.96:admin
Fri Sep 27 18:39:37 2002:stop:snmp_1033151977_171.71.49.96:admin:
Fri Sep 27 18:39:37 2002:start:snmp_1033151977_171.71.49.96:admin
Fri Sep 27 18:42:12 2002:start:snmp_1033152132_171.71.49.96:admin
Fri Sep 27 18:42:12 2002:stop:snmp_1033152132_171.71.49.96:admin:
Fri Sep 27 18:42:12 2002:start:snmp_1033152132_171.71.49.96:admin
Fri Sep 27 18:42:40 2002:start:snmp_1033152160_171.71.49.96:admin
...

The following example displays 400 bytes of the accounting log:


switch# show accounting log 400
Tue Dec  8 22:06:59 1981:start:/dev/pts/2_376697219:admin:
Tue Dec  8 22:07:03 1981:stop:/dev/pts/2_376697219:admin:shell terminated
Tue Dec  8 22:07:13 1981:start:/dev/pts/2_376697233:admin:
Tue Dec  8 22:07:53 1981:stop:/dev/pts/2_376697233:admin:shell terminated
Tue Dec  8 22:08:15 1981:update:/dev/ttyS0_376628597:admin:iSCSI Interface Vsan Enabled

show analytics port-sampling

To display the SAN analytics port sampling information, use the show analytics port-sampling command.

show analytics port-sampling module number

Syntax Description

module number

Module number.

Command Default

None.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

8.4(1)

The command output was modified.

8.3(1)

This command was introduced.

Examples

This example shows how to check the port sampling status and the instantaneous network processing unit (NPU) load:


Note

The star symbol (*) next to a port indicates that the port is currently being sampled.



switch# show analytics port-sampling module 1
Sampling Window Size: 12
Rotation Interval: 30
NPU LOAD : 64%      [SCSI 64%, NVMe 0%]  
========================================================================
  Port               Monitored Start Time           Monitored End Time
========================================================================
  fc4/25             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/26             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/27             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/28             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/29             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/30             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/31             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/32             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/33             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/34             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/35             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/36             04/01/19 - 05:25:29            04/01/19 - 05:25:59    
  fc4/37*            04/01/19 - 05:25:59            -                      
  fc4/38*            04/01/19 - 05:25:59            -                      
  fc4/39*            04/01/19 - 05:25:59            -                      
  fc4/40*            04/01/19 - 05:25:59            -                      
  fc4/41*            04/01/19 - 05:25:59            -                      
  fc4/42*            04/01/19 - 05:25:59            -                      
  fc4/43*            04/01/19 - 05:25:59            -                      
  fc4/44*            04/01/19 - 05:25:59            -                      
  fc4/45*            04/01/19 - 05:25:59            -                      
  fc4/46*            04/01/19 - 05:25:59            -                      
  fc4/47*            04/01/19 - 05:25:59            -                      
  fc4/48*            04/01/19 - 05:25:59            -                      
========================================================================
! - Denotes port is link down but analytics enabled.
* - Denotes port in active analytics port sampling window.


show analytics query

To display the SAN analytics query information, use the show analytics query command.

show analytics query {"query_string" [clear] [differential] | all | name query_name [result]}

Syntax Description

“query_string”

Query syntax.

clear

Clears all the minimum, maximum, and peak metrics after each fetch.

differential

Fetches only updated metrics.

all

Displays all queries.

name query_name

Query name.

result

Result of a push query name.

Command Default

None.

Command Modes


Privileged EXEC (#)

Command History

Release

Modification

8.3(1)

This command was modified. The command was changed from show analytics query {“query_string” | id result} to show analytics query {"query_string" [clear] [differential] | all | name query_name [result]} .

8.2(1)

This command was introduced.

Usage Guidelines

The show analytics query command is a pull query (one-time query) which is used to extract flow metrics that are stored in a database at the instant the query was executed. The output is in JSON format. Only one pull query can be executed at a time.

The “query_string” is a query syntax where you can specify query semantics such as select, table, limit, and so on. For example, “select all from fc-scsi.port.” For more information, see the “Cisco MDS 9000 Series NX-OS SAN Analytics and Telemetry Configuration Guide.”

Examples

This example shows the output of all the flow metrics of the SCSI initiator ITL flow view instance:


switch#  show analytics query 'select all from fc-scsi.scsi_initiator_itl_flow'
{ "values": {
        "1": {
                "port": "fc1/1",
                "vsan": "10",
                "app_id": "255",
                "initiator_id": "0xe80041",
                "target_id": "0xd60200",
                "lun": "0000-0000-0000-0000",
                "active_io_read_count": "0",
                "active_io_write_count": "1",
                "total_read_io_count": "0",
                "total_write_io_count": "1162370362",
                "total_seq_read_io_count": "0",
                "total_seq_write_io_count": "1",
                "total_read_io_time": "0",
                "total_write_io_time": "116204704658",
                "total_read_io_initiation_time": "0",
                "total_write_io_initiation_time": "43996934029",
                "total_read_io_bytes": "0",
                "total_write_io_bytes": "595133625344",
                "total_read_io_inter_gap_time": "0",
                "total_write_io_inter_gap_time": "41139462314556",
                "total_time_metric_based_read_io_count": "0",
                "total_time_metric_based_write_io_count": "1162370358",
                "total_time_metric_based_read_io_bytes": "0",
                "total_time_metric_based_write_io_bytes": "595133623296",
                "read_io_rate": "0",
                "peak_read_io_rate": "0",
                "write_io_rate": "7250",
                "peak_write_io_rate": "7304",
                "read_io_bandwidth": "0",
                "peak_read_io_bandwidth": "0",
                "write_io_bandwidth": "3712384",
                "peak_write_io_bandwidth": "3739904",
                "read_io_size_min": "0",
                "read_io_size_max": "0",
                "write_io_size_min": "512",
                "write_io_size_max": "512",
                "read_io_completion_time_min": "0",
                "read_io_completion_time_max": "0",
                "write_io_completion_time_min": "89",
                "write_io_completion_time_max": "416",
                "read_io_initiation_time_min": "0",
                "read_io_initiation_time_max": "0",
                "write_io_initiation_time_min": "34",
                "write_io_initiation_time_max": "116",
                "read_io_inter_gap_time_min": "0",
                "read_io_inter_gap_time_max": "0",
                "write_io_inter_gap_time_min": "31400",
                "write_io_inter_gap_time_max": "118222",
                "peak_active_io_read_count": "0",
                "peak_active_io_write_count": "5",
                "read_io_aborts": "0",
                "write_io_aborts": "0",
                "read_io_failures": "0",
                "write_io_failures": "0",
                "read_io_timeouts": "0",
                "write_io_timeouts": "1",
                "read_io_scsi_check_condition_count": "0",
                "write_io_scsi_check_condition_count": "0",
                "read_io_scsi_busy_count": "0",
                "write_io_scsi_busy_count": "0",
                "read_io_scsi_reservation_conflict_count": "0",
                "write_io_scsi_reservation_conflict_count": "0",
                "read_io_scsi_queue_full_count": "0",
                "write_io_scsi_queue_full_count": "0",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697457"
        },
        .
        .
        .
        "5": {
                "port": "fc1/8",
                "vsan": "10",
                "app_id": "255",
                "initiator_id": "0xe80001",
                "target_id": "0xe800a1",
                "lun": "0000-0000-0000-0000",
                "active_io_read_count": "0",
                "active_io_write_count": "1",
                "total_read_io_count": "0",
                "total_write_io_count": "1138738309",
                "total_seq_read_io_count": "0",
                "total_seq_write_io_count": "1",
                "total_read_io_time": "0",
                "total_write_io_time": "109792480881",
                "total_read_io_initiation_time": "0",
                "total_write_io_initiation_time": "39239145641",
                "total_read_io_bytes": "0",
                "total_write_io_bytes": "583034014208",
                "total_read_io_inter_gap_time": "0",
                "total_write_io_inter_gap_time": "41479779998852",
                "total_time_metric_based_read_io_count": "0",
                "total_time_metric_based_write_io_count": "1138738307",
                "total_time_metric_based_read_io_bytes": "0",
                "total_time_metric_based_write_io_bytes": "583034013184",
                "read_io_rate": "0",
                "peak_read_io_rate": "0",
                "write_io_rate": "7074",
                "peak_write_io_rate": "7903",
                "read_io_bandwidth": "0",
                "peak_read_io_bandwidth": "0",
                "write_io_bandwidth": "3622144",
                "peak_write_io_bandwidth": "4046336",
                "read_io_size_min": "0",
                "read_io_size_max": "0",
                "write_io_size_min": "512",
                "write_io_size_max": "512",
                "read_io_completion_time_min": "0",
                "read_io_completion_time_max": "0",
                "write_io_completion_time_min": "71",
                "write_io_completion_time_max": "3352",
                "read_io_initiation_time_min": "0",
                "read_io_initiation_time_max": "0",
                "write_io_initiation_time_min": "26",
                "write_io_initiation_time_max": "2427",
                "read_io_inter_gap_time_min": "0",
                "read_io_inter_gap_time_max": "0",
                "write_io_inter_gap_time_min": "25988",
                "write_io_inter_gap_time_max": "868452",
                "peak_active_io_read_count": "0",
                "peak_active_io_write_count": "5",
                "read_io_aborts": "0",
                "write_io_aborts": "0",
                "read_io_failures": "0",
                "write_io_failures": "0",
                "read_io_timeouts": "0",
                "write_io_timeouts": "1",
                "read_io_scsi_check_condition_count": "0",
                "write_io_scsi_check_condition_count": "0",
                "read_io_scsi_busy_count": "0",
                "write_io_scsi_busy_count": "0",
                "read_io_scsi_reservation_conflict_count": "0",
                "write_io_scsi_reservation_conflict_count": "0",
                "read_io_scsi_queue_full_count": "0",
                "write_io_scsi_queue_full_count": "0",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697457"
        }
}}

This example shows the output of all the flow metrics of the NVMe initiator ITN flow view instance:


switch# show analytics query 'select all from fc-nvme.nvme_initiator_itn_flow'
{ "values": {
        "1": {
                "port": "fc1/9",
                "vsan": "5",
                "app_id": "255",
                "initiator_id": "0xa40160",
                "target_id": "0xa4018c",
                "connection_id": "0000-0000-0000-0000",
                "namespace_id": "1",
                "active_io_read_count": "0",
                "active_io_write_count": "0",
                "total_read_io_count": "414106348",
                "total_write_io_count": "0",
                "total_seq_read_io_count": "0",
                "total_seq_write_io_count": "0",
                "total_read_io_time": "204490863437",
                "total_write_io_time": "0",
                "total_read_io_initiation_time": "132775579977",
                "total_write_io_initiation_time": "0",
                "total_read_io_bytes": "16226866588672",
                "total_write_io_bytes": "0",
                "total_read_io_inter_gap_time": "19198018763772",
                "total_write_io_inter_gap_time": "0",
                "total_time_metric_based_read_io_count": "414106244",
                "total_time_metric_based_write_io_count": "0",
                "total_time_metric_based_read_io_bytes": "16226860198912",
                "total_time_metric_based_write_io_bytes": "0",
                "read_io_rate": "0",
                "peak_read_io_rate": "16826",
                "write_io_rate": "0",
                "peak_write_io_rate": "0",
                "read_io_bandwidth": "0",
                "peak_read_io_bandwidth": "656438400",
                "write_io_bandwidth": "0",
                "peak_write_io_bandwidth": "0",
                "read_io_size_min": "1024",
                "read_io_size_max": "262144",
                "write_io_size_min": "0",
                "write_io_size_max": "0",
                "read_io_completion_time_min": "16",
                "read_io_completion_time_max": "7057",
                "write_io_completion_time_min": "0",
                "write_io_completion_time_max": "0",
                "read_io_initiation_time_min": "16",
                "read_io_initiation_time_max": "5338",
                "write_io_initiation_time_min": "0",
                "write_io_initiation_time_max": "0",
                "read_io_inter_gap_time_min": "32",
                "read_io_inter_gap_time_max": "83725169",
                "write_io_inter_gap_time_min": "0",
                "write_io_inter_gap_time_max": "0",
                "peak_active_io_read_count": "11",
                "peak_active_io_write_count": "0",
                "read_io_aborts": "24",
                "write_io_aborts": "0",
                "read_io_failures": "80",
                "write_io_failures": "0",
                "read_io_timeouts": "0",
                "write_io_timeouts": "0",
                "read_io_nvme_lba_out_of_range_count": "0",
                "write_io_nvme_lba_out_of_range_count": "0",
                "read_io_nvme_ns_not_ready_count": "0",
                "write_io_nvme_ns_not_ready_count": "0",
                "read_io_nvme_reservation_conflict_count": "0",
                "write_io_nvme_reservation_conflict_count": "0",
                "read_io_nvme_capacity_exceeded_count": "0",
                "write_io_nvme_capacity_exceeded_count": "0",
                "sampling_start_time": "1512847422",
                "sampling_end_time": "1513166516"
        },
       .
       .
       .
        "5": {
                "port": "fc1/9",
                "vsan": "5",
                "app_id": "255",
                "initiator_id": "0xa40165",
                "target_id": "0xa40190",
                "connection_id": "0000-0000-0000-0000",
                "namespace_id": "1",
                "active_io_read_count": "0",
                "active_io_write_count": "0",
                "total_read_io_count": "33391955",
                "total_write_io_count": "643169087",
                "total_seq_read_io_count": "0",
                "total_seq_write_io_count": "0",
                "total_read_io_time": "13005795783",
                "total_write_io_time": "131521212441",
                "total_read_io_initiation_time": "5696099596",
                "total_write_io_initiation_time": "71938348902",
                "total_read_io_bytes": "1309083368448",
                "total_write_io_bytes": "329302572544",
                "total_read_io_inter_gap_time": "19175084866843",
                "total_write_io_inter_gap_time": "19182318062480",
                "total_time_metric_based_read_io_count": "33391919",
                "total_time_metric_based_write_io_count": "643168808",
                "total_time_metric_based_read_io_bytes": "1309074355200",
                "total_time_metric_based_write_io_bytes": "329302429696",
                "read_io_rate": "0",
                "peak_read_io_rate": "574",
                "write_io_rate": "0",
                "peak_write_io_rate": "9344",
                "read_io_bandwidth": "0",
                "peak_read_io_bandwidth": "19122176",
                "write_io_bandwidth": "0",
                "peak_write_io_bandwidth": "4784384",
                "read_io_size_min": "1024",
                "read_io_size_max": "262144",
                "write_io_size_min": "512",
                "write_io_size_max": "512",
                "read_io_completion_time_min": "16",
                "read_io_completion_time_max": "5123",
                "write_io_completion_time_min": "27",
                "write_io_completion_time_max": "2254",
                "read_io_initiation_time_min": "16",
                "read_io_initiation_time_max": "3650",
                "write_io_initiation_time_min": "12",
                "write_io_initiation_time_max": "1377",
                "read_io_inter_gap_time_min": "32",
                "read_io_inter_gap_time_max": "3234375975",
                "write_io_inter_gap_time_min": "32",
                "write_io_inter_gap_time_max": "38886219",
                "peak_active_io_read_count": "6",
                "peak_active_io_write_count": "16",
                "read_io_aborts": "6",
                "write_io_aborts": "18",
                "read_io_failures": "30",
                "write_io_failures": "261",
                "read_io_timeouts": "0",
                "write_io_timeouts": "0",
                "read_io_nvme_lba_out_of_range_count": "0",
                "write_io_nvme_lba_out_of_range_count": "0",
                "read_io_nvme_ns_not_ready_count": "0",
                "write_io_nvme_ns_not_ready_count": "0",
                "read_io_nvme_reservation_conflict_count": "0",
                "write_io_nvme_reservation_conflict_count": "0",
                "read_io_nvme_capacity_exceeded_count": "0",
                "write_io_nvme_capacity_exceeded_count": "0",
                "sampling_start_time": "1512847422",
                "sampling_end_time": "1513166516"
        }
}}


This example shows an output of specific flow metrics for a specific initiator ID of an initiator ITL flow view type:


switch# show analytics query 'select port,initiator_id, target_id,lun,
total_read_io_count,total_write_io_count,read_io_rate, write_io_rate from 
fc-scsi.scsi_initiator_itl_flow where initiator_id=0xe80001'
{ "values": {
        "1": {
                "port": "fc1/8",
                "initiator_id": "0xe80001",
                "target_id": "0xe800a1",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1139010960",
                "read_io_rate": "0",
                "write_io_rate": "7071",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697495"
        }
}}

This example shows an output of specific flow metrics for a specific initiator ID and LUN of an initiator ITL flow view type:


switch#   show analytics query 'select port,initiator_id, target_id,lun,
total_read_io_count,total_write_io_count,read_io_rate, write_io_rate from 
fc-scsi.scsi_initiator_itl_flow where initiator_id=0xe80001 and lun= 0000-0000-0000-0000'
{ "values": {
        "1": {
                "port": "fc1/8",
                "initiator_id": "0xe80001",
                "target_id": "0xe800a1",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1139453979",
                "read_io_rate": "0",
                "write_io_rate": "7070",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697559"
        }
}}

This example shows an output of specific flow metrics for a specific LUN with the output sorted for the write_io_rate flow metrics of a target ITL flow view type:


switch#   show analytics query 'select port,initiator_id, target_id,lun,total_read_io_count,
total_write_io_count,read_io_rate, write_io_rate from fc-scsi.scsi_initiator_itl_flow where 
lun= 0000-0000-0000-0000 sort write_io_rate'
{ "values": {
        "1": {
                "port": "fc1/6",
                "initiator_id": "0xe80020",
                "target_id": "0xd60040",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1103394068",
                "read_io_rate": "0",
                "write_io_rate": "6882",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697630"
        },
        "2": {
                "port": "fc1/6",
                "initiator_id": "0xe80021",
                "target_id": "0xe80056",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1119199742",
                "read_io_rate": "0",
                "write_io_rate": "6946",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697630"
        },
        "3": {
                "port": "fc1/8",
                "initiator_id": "0xe80000",
                "target_id": "0xe80042",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1119506589",
                "read_io_rate": "0",
                "write_io_rate": "6948",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697630"
        },
        "4": {
                "port": "fc1/8",
                "initiator_id": "0xe80001",
                "target_id": "0xe800a1",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1139953183",
                "read_io_rate": "0",
                "write_io_rate": "7068",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697630"
        },
        "5": {
                "port": "fc1/1",
                "initiator_id": "0xe80041",
                "target_id": "0xd60200",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1163615698",
                "read_io_rate": "0",
                "write_io_rate": "7247",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697630"
        }
}}

This example shows an output of specific flow metrics for a specific LUN with the output limited to three records and sorted for the write_io_rate flow metrics of an initiator ITL flow view type:


switch#   show analytics query 'select port,initiator_id, target_id,lun,total_read_io_count,
total_write_io_count,read_io_rate, write_io_rate from fc-scsi.scsi_initiator_itl_flow where 
lun= 0000-0000-0000-0000 sort write_io_rate limit 3'
{ "values": {
        "1": {
                "port": "fc1/6",
                "initiator_id": "0xe80020",
                "target_id": "0xd60040",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1103901828",
                "read_io_rate": "0",
                "write_io_rate": "6885",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697704"
        },
        "2": {
                "port": "fc1/8",
                "initiator_id": "0xe80000",
                "target_id": "0xe80042",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1120018575",
                "read_io_rate": "0",
                "write_io_rate": "6940",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697704"
        },
        "3": {
                "port": "fc1/6",
                "initiator_id": "0xe80021",
                "target_id": "0xe80056",
                "lun": "0000-0000-0000-0000",
                "total_read_io_count": "0",
                "total_write_io_count": "1119711583",
                "read_io_rate": "0",
                "write_io_rate": "6942",
                "sampling_start_time": "1528535447",
                "sampling_end_time": "1528697704"
        }
}}

These examples show how to clear all the minimum, maximum, and peak flow metrics:

  • This example show the output before clearing the all the minimum, maximum, and peak flow metrics:


    Note

    You must execute the clear command twice for the first time for clearing all the minimum, maximum, and peak flow metrics. Thereafter, you can execute the clear command once for clearing the flow metrics.


    
    switch# show analytics query "select all from  
    fc-scsi.scsi_target_itl_flow where port=fc1/17"
    { "values": {
            "1": {
                    "port": "fc1/17",
                    "vsan": "1",
                    "app_id": "255",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0000",
                    "lun": "0000-0000-0000-0000",
                    "active_io_read_count": "0",
                    "active_io_write_count": "1",
                    "total_read_io_count": "0",
                    "total_write_io_count": "84701",
                    "total_seq_read_io_count": "0",
                    "total_seq_write_io_count": "1",
                    "total_read_io_time": "0",
                    "total_write_io_time": "7007132",
                    "total_read_io_initiation_time": "0",
                    "total_write_io_initiation_time": "2421756",
                    "total_read_io_bytes": "0",
                    "total_write_io_bytes": "86733824",
                    "total_read_io_inter_gap_time": "0",
                    "total_write_io_inter_gap_time": "2508109021",
                    "total_time_metric_based_read_io_count": "0",
                    "total_time_metric_based_write_io_count": "84701",
                    "total_time_metric_based_read_io_bytes": "0",
                    "total_time_metric_based_write_io_bytes": "86733824",
                    "read_io_rate": "0",
                    "peak_read_io_rate": "0",
                    "write_io_rate": "8711",
                    "peak_write_io_rate": "8711",
                    "read_io_bandwidth": "0",
                    "peak_read_io_bandwidth": "0",
                    "write_io_bandwidth": "8920576",
                    "peak_write_io_bandwidth": "8920576",
                    "read_io_size_min": "0",
                    "read_io_size_max": "0",
                    "write_io_size_min": "1024",
                    "write_io_size_max": "1024",
                    "read_io_completion_time_min": "0",
                    "read_io_completion_time_max": "0",
                    "write_io_completion_time_min": "74",
                    "write_io_completion_time_max": "844",
                    "read_io_initiation_time_min": "0",
                    "read_io_initiation_time_max": "0",
                    "write_io_initiation_time_min": "24",
                    "write_io_initiation_time_max": "775",
                    "read_io_inter_gap_time_min": "0",
                    "read_io_inter_gap_time_max": "0",
                    "write_io_inter_gap_time_min": "26903",
                    "write_io_inter_gap_time_max": "287888",
                    "peak_active_io_read_count": "0",
                    "peak_active_io_write_count": "3",
                    "read_io_aborts": "0",
                    "write_io_aborts": "0",
                    "read_io_failures": "0",
                    "write_io_failures": "0",
                    "read_io_timeouts": "0",
                    "write_io_timeouts": "0",
                    "read_io_scsi_check_condition_count": "0",
                    "write_io_scsi_check_condition_count": "0",
                    "read_io_scsi_busy_count": "0",
                    "write_io_scsi_busy_count": "0",
                    "read_io_scsi_reservation_conflict_count": "0",
                    "write_io_scsi_reservation_conflict_count": "0",
                    "read_io_scsi_queue_full_count": "0",
                    "write_io_scsi_queue_full_count": "0",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530684301"
            },
            "2": {
                    "port": "fc1/17",
                    "vsan": "1",
                    "app_id": "255",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0020",
                    "lun": "0000-0000-0000-0000",
                    "active_io_read_count": "0",
                    "active_io_write_count": "0",
                    "total_read_io_count": "0",
                    "total_write_io_count": "84700",
                    "total_seq_read_io_count": "0",
                    "total_seq_write_io_count": "1",
                    "total_read_io_time": "0",
                    "total_write_io_time": "6973333",
                    "total_read_io_initiation_time": "0",
                    "total_write_io_initiation_time": "2400011",
                    "total_read_io_bytes": "0",
                    "total_write_io_bytes": "86732800",
                    "total_read_io_inter_gap_time": "0",
                    "total_write_io_inter_gap_time": "2508096990",
                    "total_time_metric_based_read_io_count": "0",
                    "total_time_metric_based_write_io_count": "84700",
                    "total_time_metric_based_read_io_bytes": "0",
                    "total_time_metric_based_write_io_bytes": "86732800",
                    "read_io_rate": "0",
                    "peak_read_io_rate": "0",
                    "write_io_rate": "8711",
                    "peak_write_io_rate": "8711",
                    "read_io_bandwidth": "0",
                    "peak_read_io_bandwidth": "0",
                    "write_io_bandwidth": "8920576",
                    "peak_write_io_bandwidth": "8920576",
                    "read_io_size_min": "0",
                    "read_io_size_max": "0",
                    "write_io_size_min": "1024",
                    "write_io_size_max": "1024",
                    "read_io_completion_time_min": "0",
                    "read_io_completion_time_max": "0",
                    "write_io_completion_time_min": "74",
                    "write_io_completion_time_max": "1134",
                    "read_io_initiation_time_min": "0",
                    "read_io_initiation_time_max": "0",
                    "write_io_initiation_time_min": "24",
                    "write_io_initiation_time_max": "345",
                    "read_io_inter_gap_time_min": "0",
                    "read_io_inter_gap_time_max": "0",
                    "write_io_inter_gap_time_min": "26789",
                    "write_io_inter_gap_time_max": "298809",
                    "peak_active_io_read_count": "0",
                    "peak_active_io_write_count": "3",
                    "read_io_aborts": "0",
                    "write_io_aborts": "0",
                    "read_io_failures": "0",
                    "write_io_failures": "0",
                    "read_io_timeouts": "0",
                    "write_io_timeouts": "0",
                    "read_io_scsi_check_condition_count": "0",
                    "write_io_scsi_check_condition_count": "0",
                    "read_io_scsi_busy_count": "0",
                    "write_io_scsi_busy_count": "0",
                    "read_io_scsi_reservation_conflict_count": "0",
                    "write_io_scsi_reservation_conflict_count": "0",
                   "read_io_scsi_queue_full_count": "0",
                    "write_io_scsi_queue_full_count": "0",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530684301"
            }
    }}
    
    
  • This examples shows the output after clearing all the minimum, maximum, and peak flow metrics. The metrics that were cleared are highlighted in the output.

    
    switch# show analytics query "select all from  
    fc-scsi.scsi_target_itl_flow where port=fc1/17" clear
    { "values": {
            "1": {
                    "port": "fc1/17",
                   "vsan": "1",
                    "app_id": "255",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0000",
                    "lun": "0000-0000-0000-0000",
                    "active_io_read_count": "0",
                    "active_io_write_count": "0",
                    "total_read_io_count": "0",
                    "total_write_io_count": "800615",
                    "total_seq_read_io_count": "0",
                    "total_seq_write_io_count": "1",
                    "total_read_io_time": "0",
                    "total_write_io_time": "66090290",
                    "total_read_io_initiation_time": "0",
                    "total_write_io_initiation_time": "22793874",
                    "total_read_io_bytes": "0",
                    "total_write_io_bytes": "819829760",
                    "total_read_io_inter_gap_time": "0",
                    "total_write_io_inter_gap_time": "23702347887",
                    "total_time_metric_based_read_io_count": "0",
                    "total_time_metric_based_write_io_count": "800615",
                    "total_time_metric_based_read_io_bytes": "0",
                    "total_time_metric_based_write_io_bytes": "819829760",
                    "read_io_rate": "0",
                    "peak_read_io_rate": "0",
                    "write_io_rate": "0",
                    "peak_write_io_rate": "0",
                    "read_io_bandwidth": "0",
                    "peak_read_io_bandwidth": "0",
                    "write_io_bandwidth": "0",
                    "peak_write_io_bandwidth": "0",
                    "read_io_size_min": "0",
                    "read_io_size_max": "0",
                    "write_io_size_min": "0",
                    "write_io_size_max": "0",
                    "read_io_completion_time_min": "0",
                    "read_io_completion_time_max": "0",
                    "write_io_completion_time_min": "0",
                    "write_io_completion_time_max": "0",
                    "read_io_initiation_time_min": "0",
                    "read_io_initiation_time_max": "0",
                    "write_io_initiation_time_min": "0",
                    "write_io_initiation_time_max": "0",
                    "read_io_inter_gap_time_min": "0",
                    "read_io_inter_gap_time_max": "0",
                    "write_io_inter_gap_time_min": "0",
                    "write_io_inter_gap_time_max": "0",
                    "peak_active_io_read_count": "0",
                    "peak_active_io_write_count": "0",
                    "read_io_aborts": "0",
                    "write_io_aborts": "0",
                    "read_io_failures": "0",
                    "write_io_failures": "0",
                    "read_io_timeouts": "0",
                    "write_io_timeouts": "0",
                    "read_io_scsi_check_condition_count": "0",
                    "write_io_scsi_check_condition_count": "0",
                    "read_io_scsi_busy_count": "0",
                    "write_io_scsi_busy_count": "0",
                    "read_io_scsi_reservation_conflict_count": "0",
                    "write_io_scsi_reservation_conflict_count": "0",
                    "read_io_scsi_queue_full_count": "0",
                    "write_io_scsi_queue_full_count": "0",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530684428"
            },
    }}
    
    

These examples show how to stream only the ITL flow metrics that have changed between streaming intervals:

  • This example shows the output before using the differential option:

    
    switch# show analytics query "select port, target_id, initiator_id,lun,
    total_write_io_count from fc-scsi.scsi_target_itl_flow where port=fc1/17" 
    differential 
    { "values": {
            "1": {
                    "port": "fc1/17",
                    "target_id": "0xef0040",
                   "initiator_id": "0xef0000",
                    "lun": "0001-0000-0000-0000",
                    "total_write_io_count": "1515601",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530683484"
            },
            "2": {
                    "port": "fc1/17",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0020",
                    "lun": "0000-0000-0000-0000",
                    "total_write_io_count": "1515601",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530683484"
            },
            "3": {
                    "port": "fc1/17",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0020",
                    "lun": "0001-0000-0000-0000",
                    "total_write_io_count": "1515600",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530683484"
            },
            "4": {
                    "port": "fc1/17",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0000",
                    "lun": "0000-0000-0000-0000",
                    "total_write_io_count": "1515600",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530683484"
            }
    }}
    
    
  • This example shows the output with the differential option and shows only the records that have changed:

    
    switch# show analytics query "select port, target_id, 
    initiator_id,lun,total_write_io_count from fc-scsi.scsi_target_itl_flow where port=fc1/17" 
    differential 
    { "values": {
           "1": {
                    "port": "fc1/17",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0000",
                    "lun": "0001-0000-0000-0000",
                    "total_write_io_count": "1892021",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530683534"
            },
            "2": {
                    "port": "fc1/17",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0020",
                    "lun": "0000-0000-0000-0000",
                    "total_write_io_count": "1892021",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530683534"
            },
            "3": {
                    "port": "fc1/17",
                    "target_id": "0xef0040",
                    "initiator_id": "0xef0000",
                    "lun": "0000-0000-0000-0000",
                    "total_write_io_count": "1892021",
                    "sampling_start_time": "1530683133",
                    "sampling_end_time": "1530683534"
            }
    }}
    
    

This example shows an output of all the installed push analytics queries:


switch# show analytics query all  
Total queries:7
============================
Query Name      :init
Query String    :select all from fc-scsi.scsi_initiator
Query Type      :periodic, interval 30

Query Name      :targettl
Query String    :select all from fc-scsi.scsi_target_tl_flow
Query Type      :periodic, interval 30
Query Options   :differential clear

Query Name      :port
Query String    :select all from fc-scsi.logical_port
Query Type      :periodic, interval 30

Query Name      :targetit
Query String    :select all from fc-scsi.scsi_target_it_flow
Query Type      :periodic, interval 30

Query Name      :targetitl
Query String    :select all from fc-scsi.scsi_target_itl_flow
Query Type      :periodic, interval 30
Query Options   :differential clear

Query Name      :inititl
Query String    :select all from fc-scsi.scsi_initiator_itl_flow
Query Type      :periodic, interval 30

Query Name      :initit
Query String    :select all from fc-scsi.scsi_initiator_it_flow
Query Type      :periodic, interval 30

This example shows how to view an installed push analytics query:


switch# show analytics query name tartl 
Query Name      :tartl
Query String    :select all from fc-scsi.scsi_target_tl_flow
Query Type      :periodic, interval 30

This example shows the output of a push query that has already been configured:


switch# show analytics query name iniitl result 
{ "values": {
        "1": {
                "port": "fc1/6",
                "vsan": "10",
                "app_id": "255",
                "initiator_id": "0xe800a0",
                "target_id": "0xd601e0",
                "lun": "0000-0000-0000-0000",
                "active_io_read_count": "0",
                "active_io_write_count": "7",
                "total_read_io_count": "0",
                "total_write_io_count": "1008608573",
                "total_seq_read_io_count": "0",
                "total_seq_write_io_count": "1",
                "total_read_io_time": "0",
                "total_write_io_time": "370765952314",
                "total_read_io_initiation_time": "0",
                "total_write_io_initiation_time": "52084968152",
                "total_read_io_bytes": "0",
                "total_write_io_bytes": "2065630357504",
                "total_read_io_inter_gap_time": "0",
                "total_write_io_inter_gap_time": "16171468343166",
                "total_time_metric_based_read_io_count": "0",
                "total_time_metric_based_write_io_count": "1008608566",
                "total_time_metric_based_read_io_bytes": "0",
                "total_time_metric_based_write_io_bytes": "2065630343168",
                "read_io_rate": "0",
                "peak_read_io_rate": "0",
                "write_io_rate": "16070",
                "peak_write_io_rate": "32468",
                "read_io_bandwidth": "0",
                "peak_read_io_bandwidth": "0",
                "write_io_bandwidth": "32912384",
                "peak_write_io_bandwidth": "66494976",
                "read_io_size_min": "0",
                "read_io_size_max": "0",
                "write_io_size_min": "2048",
                "write_io_size_max": "2048",
                "read_io_completion_time_min": "0",
                "read_io_completion_time_max": "0",
                "write_io_completion_time_min": "111",
                "write_io_completion_time_max": "9166",
                "read_io_initiation_time_min": "0",
                "read_io_initiation_time_max": "0",
                "write_io_initiation_time_min": "36",
                "write_io_initiation_time_max": "3265",
                "read_io_inter_gap_time_min": "0",
                "read_io_inter_gap_time_max": "0",
                "write_io_inter_gap_time_min": "100",
                "write_io_inter_gap_time_max": "1094718",
                "peak_active_io_read_count": "0",
                "peak_active_io_write_count": "23",
                "read_io_aborts": "0",
                "write_io_aborts": "0",
                "read_io_failures": "0",
                "write_io_failures": "0",
                "read_io_timeouts": "0",
                "write_io_timeouts": "0",
                "read_io_scsi_check_condition_count": "0",
                "write_io_scsi_check_condition_count": "0",
                "read_io_scsi_busy_count": "0",
                "write_io_scsi_busy_count": "0",
                "read_io_scsi_reservation_conflict_count": "0",
                "write_io_scsi_reservation_conflict_count": "0",
                "read_io_scsi_queue_full_count": "0",
                "write_io_scsi_queue_full_count": "0",
                "sampling_start_time": "1529993232",
                "sampling_end_time": "1529993260"
        },
        "2": {
                "port": "fc1/6",
                "vsan": "10",
                "app_id": "255",
                "initiator_id": "0xe800a1",
                "target_id": "0xd601e1",
                "lun": "0000-0000-0000-0000",
                "active_io_read_count": "0",
                "active_io_write_count": "8",
                "total_read_io_count": "0",
                "total_write_io_count": "1004271260",
                "total_seq_read_io_count": "0",
                "total_seq_write_io_count": "1",
                "total_read_io_time": "0",
                "total_write_io_time": "370004164726",
                "total_read_io_initiation_time": "0",
                "total_write_io_initiation_time": "51858511487",
                "total_read_io_bytes": "0",
                "total_write_io_bytes": "2056747540480",
                "total_read_io_inter_gap_time": "0",
                "total_write_io_inter_gap_time": "16136686881766",
                "total_time_metric_based_read_io_count": "0",
                "total_time_metric_based_write_io_count": "1004271252",
                "total_time_metric_based_read_io_bytes": "0",
                "total_time_metric_based_write_io_bytes": "2056747524096",
                "read_io_rate": "0",
                "peak_read_io_rate": "0",
                "write_io_rate": "16065",
                "peak_write_io_rate": "16194",
                "read_io_bandwidth": "0",
                "peak_read_io_bandwidth": "0",
                "write_io_bandwidth": "32901632",
                "peak_write_io_bandwidth": "33165824",
                "read_io_size_min": "0",
                "read_io_size_max": "0",
                "write_io_size_min": "2048",
                "write_io_size_max": "2048",
                "read_io_completion_time_min": "0",
                "read_io_completion_time_max": "0",
                "write_io_completion_time_min": "114",
                "write_io_completion_time_max": "9019",
                "read_io_initiation_time_min": "0",
                "read_io_initiation_time_max": "0",
                "write_io_initiation_time_min": "37",
                "write_io_initiation_time_max": "3158",
                "read_io_inter_gap_time_min": "0",
                "read_io_inter_gap_time_max": "0",
                "write_io_inter_gap_time_min": "101",
                "write_io_inter_gap_time_max": "869035",
                "peak_active_io_read_count": "0",
                "peak_active_io_write_count": "19",
                "read_io_aborts": "0",
                "write_io_aborts": "0",
                "read_io_failures": "0",
                "write_io_failures": "0",
                "read_io_timeouts": "0",
                "write_io_timeouts": "0",
                "read_io_scsi_check_condition_count": "0",
                "write_io_scsi_check_condition_count": "0",
                "read_io_scsi_busy_count": "0",
                "write_io_scsi_busy_count": "0",
                "read_io_scsi_reservation_conflict_count": "0",
                "write_io_scsi_reservation_conflict_count": "0",
                "read_io_scsi_queue_full_count": "0",
                "write_io_scsi_queue_full_count": "0",
                "sampling_start_time": "1529993232",
                "sampling_end_time": "1529993260"
        }
}}

show analytics schema

To display the list of view instances and flow metrics supported in SAN Analytics, use the show analytics schema command.

show analytics schema {fc-nvme | fc-scsi} {view-instance instance-name | views}

Syntax Description

fc-nvme

Non-Volatile Memory Express (NVMe) analytics type.

fc-scsi

Small Computer System Interface (SCSI) analytics type.

view-instance instance-name

Specifies a view instance.

views

Lists view instances.

Command Default

Displays analytics schema.

Command Modes


Privileged EXEC (#)

Command History

Release

Modification

8.4(1)

This command was introduced.

Examples

This example shows the list of view instances supported in the fc-scsi analytics type:


switch# show analytics schema fc-scsi views

fc-scsi db schema tables:
        port
        logical_port
        app
        scsi_target
        scsi_initiator
        scsi_target_app
        scsi_initiator_app
        scsi_target_tl_flow
        scsi_target_it_flow
        scsi_initiator_it_flow
        scsi_target_itl_flow
        scsi_initiator_itl_flow
        scsi_target_io
        scsi_initiator_io
 

This example shows the list of view instances supported in the fc-nvme analytics type:


switch# show analytics schema fc-nvme views

fc-nvme db schema tables:
        port
        logical_port
        app
        nvme_target
        nvme_initiator
        nvme_target_app
        nvme_initiator_app
        nvme_target_tn_flow
        nvme_target_it_flow
        nvme_initiator_it_flow
        nvme_target_itn_flow
        nvme_initiator_itn_flow
        nvme_target_io
        nvme_initiator_io
 

This example shows the list of flow metrics supported in the fc-scsi.port view instance:


Note

The exceed_count counters in the output will be supported in a future Cisco MDS NX-OS Release.



switch# show analytics schema fc-scsi view port

fc-scsi.port table schema columns:
        *port
         scsi_target_count
         scsi_initiator_count
         io_app_count
         logical_port_count
         scsi_target_app_count
         scsi_initiator_app_count
         active_io_read_count
         active_io_write_count
         scsi_target_it_flow_count
         scsi_initiator_it_flow_count
         scsi_target_itl_flow_count
         scsi_initiator_itl_flow_count
         scsi_target_tl_flow_count
         total_abts_count
         total_read_io_count
         total_write_io_count
         total_seq_read_io_count
         total_seq_write_io_count
         total_read_io_time
         total_write_io_time
         total_read_io_initiation_time
         total_write_io_initiation_time
         total_read_io_bytes
         total_write_io_bytes
         total_read_io_inter_gap_time
         total_write_io_inter_gap_time
         total_time_metric_based_read_io_count
         total_time_metric_based_write_io_count
         total_time_metric_based_read_io_bytes
         total_time_metric_based_write_io_bytes
         read_io_rate
         peak_read_io_rate
         write_io_rate
         peak_write_io_rate
         read_io_bandwidth
         peak_read_io_bandwidth
         write_io_bandwidth
         peak_write_io_bandwidth
         read_io_size_min
         read_io_size_max
         write_io_size_min
         write_io_size_max
         read_io_completion_time_min
         read_io_completion_time_max
         write_io_completion_time_min
         write_io_completion_time_max
         read_io_initiation_time_min
         read_io_initiation_time_max
         write_io_initiation_time_min
         write_io_initiation_time_max
         read_io_inter_gap_time_min
         read_io_inter_gap_time_max
         write_io_inter_gap_time_min
         write_io_inter_gap_time_max
         peak_active_io_read_count
         peak_active_io_write_count
         read_io_aborts
         write_io_aborts
         read_io_failures
         write_io_failures
         read_io_timeouts
         write_io_timeouts
         read_io_scsi_check_condition_count
         write_io_scsi_check_condition_count
         read_io_scsi_busy_count
         write_io_scsi_busy_count
         read_io_scsi_reservation_conflict_count
         write_io_scsi_reservation_conflict_count
         read_io_scsi_queue_full_count
         write_io_scsi_queue_full_count
         read_io_rate_exceed_count
         write_io_rate_exceed_count
         read_io_bandwidth_exceed_count
         write_io_bandwidth_exceed_count
         read_io_size_min_exceed_count
         read_io_size_max_exceed_count
         write_io_size_min_exceed_count
         write_io_size_max_exceed_count
         read_io_initiation_time_min_exceed_count
         read_io_initiation_time_max_exceed_count
         write_io_initiation_time_min_exceed_count
         write_io_initiation_time_max_exceed_count
         read_io_completion_time_min_exceed_count
         read_io_completion_time_max_exceed_count
         write_io_completion_time_min_exceed_count
         write_io_completion_time_max_exceed_count
         read_io_inter_gap_time_min_exceed_count
         read_io_inter_gap_time_max_exceed_count
         write_io_inter_gap_time_min_exceed_count
         write_io_inter_gap_time_max_exceed_count
         read_io_abort_exceed_count
         write_io_abort_exceed_count
         read_io_failure_exceed_count
         write_io_failure_exceed_count
         sampling_start_time
         sampling_end_time

        (* - indicates the metric is a 'key' for the table)
 

This example shows the list of flow metrics supported in the fc-nvme.port view instance:


Note

The exceed_count counters in the output will be supported in a future Cisco MDS NX-OS Release.



switch# show analytics schema fc-nvme view port

fc-nvme.port table schema columns:
        *port
         nvme_target_count
         nvme_initiator_count
         io_app_count
         logical_port_count
         nvme_target_app_count
         nvme_initiator_app_count
         active_io_read_count
         active_io_write_count
         nvme_target_it_flow_count
         nvme_initiator_it_flow_count
         nvme_target_itn_flow_count
         nvme_initiator_itn_flow_count
         nvme_target_tn_flow_count
         total_abts_count
         total_read_io_count
         total_write_io_count
         total_seq_read_io_count
         total_seq_write_io_count
         total_read_io_time
         total_write_io_time
         total_read_io_initiation_time
         total_write_io_initiation_time
         total_read_io_bytes
         total_write_io_bytes
         total_read_io_inter_gap_time
         total_write_io_inter_gap_time
         total_time_metric_based_read_io_count
         total_time_metric_based_write_io_count
         total_time_metric_based_read_io_bytes
         total_time_metric_based_write_io_bytes
         read_io_rate
         peak_read_io_rate
         write_io_rate
         peak_write_io_rate
         read_io_bandwidth
         peak_read_io_bandwidth
         write_io_bandwidth
         peak_write_io_bandwidth
         read_io_size_min
         read_io_size_max
         write_io_size_min
         write_io_size_max
         read_io_completion_time_min
         read_io_completion_time_max
         write_io_completion_time_min
         write_io_completion_time_max
         read_io_initiation_time_min
         read_io_initiation_time_max
         write_io_initiation_time_min
         write_io_initiation_time_max
         read_io_inter_gap_time_min
         read_io_inter_gap_time_max
         write_io_inter_gap_time_min
         write_io_inter_gap_time_max
         peak_active_io_read_count
         peak_active_io_write_count
         read_io_aborts
         write_io_aborts
         read_io_failures
         write_io_failures
         read_io_timeouts
         write_io_timeouts
         read_io_nvme_lba_out_of_range_count
         write_io_nvme_lba_out_of_range_count
         read_io_nvme_ns_not_ready_count
         write_io_nvme_ns_not_ready_count
         read_io_nvme_reservation_conflict_count
         write_io_nvme_reservation_conflict_count
         read_io_nvme_capacity_exceeded_count
         write_io_nvme_capacity_exceeded_count
         read_io_rate_exceed_count
         write_io_rate_exceed_count
         read_io_bandwidth_exceed_count
         write_io_bandwidth_exceed_count
         read_io_size_min_exceed_count
         read_io_size_max_exceed_count
         write_io_size_min_exceed_count
         write_io_size_max_exceed_count
         read_io_initiation_time_min_exceed_count
         read_io_initiation_time_max_exceed_count
         write_io_initiation_time_min_exceed_count
         write_io_initiation_time_max_exceed_count
         read_io_completion_time_min_exceed_count
         read_io_completion_time_max_exceed_count
         write_io_completion_time_min_exceed_count
         write_io_completion_time_max_exceed_count
         read_io_inter_gap_time_min_exceed_count
         read_io_inter_gap_time_max_exceed_count
         write_io_inter_gap_time_min_exceed_count
         write_io_inter_gap_time_max_exceed_count
         read_io_abort_exceed_count
         write_io_abort_exceed_count
         read_io_failure_exceed_count
         write_io_failure_exceed_count
         sampling_start_time
         sampling_end_time

        (* - indicates the metric is a 'key' for the table)
 

show analytics system-load

To display the network processing unit (NPU) load per module, use the show analytics system-load command.

show analytics system-load

Syntax Description

This command has no arguments or keywords.

Command Default

Displays NPU load for modules.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

8.4(1)

The command output was modified.

8.3(2)

This command was introduced.

Usage Guidelines

This command provides the system load information based on all ITL counts, including active and inactive ITL counts. Hence, we recommend that you use the purge analytics query “query_string” command to remove the inactive ITL counts, and then run this command to get the active ITL counts.

Examples

This example shows how to display the NPU load per module:


switch# show analytics system-load 
 n/a - not applicable
 ----------------------------------- Analytics System Load Info -------------------------------
 | Module | NPU Load (in %) | ITLs   ITNs   Both  |        Hosts        |       Targets       |
 |        | SCSI NVMe Total | SCSI   NVMe   Total | SCSI   NVMe   Total | SCSI   NVMe   Total |
 ----------------------------------------------------------------------------------------------
 |   1    | 0    0    0     | 0      0      0     | 0      0      0     | 0      0      0     |
 |   4    | 64   0    64    | 20743  0      20743 | 0      0      0     | 346    0      346   |
 |   5    | 0    0    0     | 0      0      0     | 0      0      0     | 0      0      0     |
 |   8    | 0    0    0     | 0      0      0     | 0      0      0     | 0      0      0     |
 |   12   | 0    12   12    | 0      300    300   | 0      0      0     | 0      40     40    |
 |   13   | 0    0    0     | 0      0      0     | 0      0      0     | 0      0      0     |
 |   18   | 0    13   13    | 1      1      2     | 1      1      2     | 0      0      0     |
 | Total  | n/a  n/a  n/a   | 20744  301    21045 | 1      1      2     | 346    40     386   |

As of Mon Apr  1 05:31:10 2019

show analytics flow congestion-drops

To display the packet drops on a per-flow basis, use the show analytics flow congestion-drops command.

show analytics flow congestion-drops [vsan number] [module number port number]

Syntax Description

vsan number

VSAN number.

module number

Module number.

port number

Port number.

Command Default

Displays packet drops on a per-flow basis.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

8.4(1)

This command was changed from show analytics type fc-scsi flow congestion-drops [vsan number] [module number port number] to show analytics flow congestion-drops [vsan number] [module number port number] .

8.2(1)

This command was introduced.

Examples

This example displays flows where frames are dropped due to congestion. The source and destination FCIP, differential frame drop count for the IT pair, and timestamp of the drops are displayed.


Note

The congestion drop entries are updated every 20 seconds.



switch# show analytics flow congestion-drops
|=====================================================================================|
|       	| Source    |Destination| Congestion    |     Timestamp                |
| INTF  | VSAN |  FCID     |  FCID     | Drops(delta)  |                              |
|=====================================================================================|
| fc2/13| 0002 | 0x9900E1  | 0x640000  |  00000105     | 1. 09/13/17 11:09:48.762     |
| fc2/13| 0002 | 0x9900E1  | 0x640000  |  00000002     | 2. 09/13/17 09:05:39.527     |
| fc2/13| 0002 | 0x990000  | 0x640020  |  00000002     | 3. 09/13/17 09:05:39.527     |
|=====================================================================================|
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000084     | 1. 09/12/17 08:17:11.905     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000076     | 2. 09/12/17 05:50:37.721     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000067     | 3. 09/12/17 03:24:03.319     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000088     | 4. 09/12/17 00:57:28.019     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000088     | 5. 09/11/17 22:30:53.723     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000086     | 6. 09/11/17 20:04:18.001     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000026     | 7. 09/11/17 17:37:24.273     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000076     | 8. 09/11/17 15:10:50.240     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000074     | 9. 09/11/17 12:44:15.866     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000087     |10. 09/11/17 10:17:41.402     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000086     |11. 09/11/17 07:51:10.412     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000084     |12. 09/11/17 05:24:35.981     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000083     |13. 09/11/17 02:58:01.067     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000086     |14. 09/11/17 00:31:26.709     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000079     |15. 09/10/17 22:04:51.399     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000084     |16. 09/10/17 19:38:17.217     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000082     |17. 09/10/17 17:11:42.594     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000086     |18. 09/10/17 14:44:52.786     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000089     |19. 09/10/17 12:18:18.394     |
| fc2/31| 0002 | 0x640000  | 0x9900E1  |  00000087     |20. 09/10/17 09:51:44.067     |
|=====================================================================================|

show arp

To display Address Resolution Protocol (ARP) entries, use the show arp command.

show arp

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.0(2)

This command was introduced.

Usage Guidelines

None.

Examples

This example shows how to display the ARP table:


switch# show arp
Protocol Address           Age (min)											Hardware Addr  	Type  	Interface
Internet  171.1.1.1 							0  				0006.5bec.699c  ARPA  mgmt0
Internet  172.2.0.1 							4				0000.0c07.ac01  ARPA  mgmt0

show autonomous-fabric-id database

To display the contents of the AFID database, use the show autonomous-fabric-id database command in EXEC mode.

show autonomous-fabric-id database

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes


EXEC mode.

Command History

Release

Modification

2.1(1a)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows contents of the AFID database:


switch# show autonomous-fabric-id database
SWITCH WWN                      Default-AFID
--------------------------------------------------------------
20:00:00:0c:91:90:3e:80            5
Total:   1 entry in default AFID table
SWITCH WWN                      AFID     VSANS
--------------------------------------------------------------
20:00:00:0c:91:90:3e:80           10     1,2,5-8
Total: 1 entry in AFID table

show banner motd

To display a configured message of the day (MOTD) banner, use the show banner motd command.

show banner motd

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.3(4)

This command was introduced.

Usage Guidelines

The configured MOTD banner is displayed before the login prompt on the terminal whenever a user logs in to a switch.

Examples

The following example displays the configured banner message:


switch# show banner motd
Testing the MOTD Feature

The configured message is visible the next time you log in to the switch:


 Testing the MOTD Feature switch login: 

show boot

To display the boot variables or modules, use the show boot command.

show boot [module [slot | variable-name] | sup-1 | sup-2 | variables]

Syntax Description

module

(Optional) Displays the boot variables for modules.

slot

Specifies a module by the slot number.

variable-name

Specifies the variable. Maximum length is 80 characters.

sup-1

(Optional) Displays the upper sup configuration.

sup-2

(Optional) Displays the lower sup configuration.

variables

(Optional) Displays the list of boot variables.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.2(2)

This command was introduced.

Usage Guidelines

None.

Examples

The following example displays the current contents of the boot variable:


switch# show boot 
kickstart variable = bootflash:/kickstart-image
system variable = bootflash:/system-image
Module 2
asm-sfn variable = bootflash:/asm-image

The following example displays the images on the specified module:


switch# show boot module
Module 2
asm-sfn variable = bootflash:/asm-image

The following example displays a list of all boot variables:


switch# show boot variables
List of boot variables are:
     asm-sfn
	 system
     kickstart

show boot auto-copy

To display state of the auto-copy feature, use the show boot auto-copy command.

show boot auto-copy [list]

Syntax Description

list

(Optional) Displays the list of files to be auto-copied

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows the message that displays on the console when you enable the auto-copy feature:


switch(config)# boot auto-copy
 Auto-copy administratively enabled 

The following example shows the message that displays on the console when you disable the auto-copy feature:


switch(config)# boot auto-copy
 Auto-copy administratively disabled 

The following example displays the current state of the auto-copy feature when it is enabled:


switch# show boot auto-copy
Auto-copy feature is enabled

The following example displays the current state of the auto-copy feature when it is disabled:


switch# show boot auto-copy
Auto-copy feature is disabled

The following example displays the ilc1.bin image being copied to the standby supervisor module's bootflash, and once this is successful, the next file will be lasilc1.bin. This command only displays files on the active supervisor module.


switch# show boot auto-copy list
File: /bootflash/ilc1.bin
Bootvar: ilce
File:/bootflash/lasilc1.bin
Bootvar: lasilc

The following example displays a typical message when the auto-copy option is disabled or if no files are copied:


switch# show boot auto-copy list
No file currently being auto-copied

show callhome

To display Call Home information configured on a switch, use the show callhome command.

show callhome [destination-profile [profile {profile | full-txt-destination | short-txt-destination | XML-destination}] | last {action status | merge status} | pending | pending-diff | script-mapping | transport-email | user-def-cmds]

Syntax Description

destination-profile

(Optional) Displays the Call Home destination profile information.

profile

(Optional) Specifies the destination profile.

profile

Specifies a user-defined destination profile.

full-txt-destination

Specifies the full text destination profile.

short-txt-destination

Specifies the short text destination profile.

XML-destination

Specifies the XML destination profile.

last action status

(Optional) Displays the status of the last CFS commit or discard operation.

last merge status

(Optional) Displays the status of the last CFS merge operation.

pending

(Optional) Displays the status of pending Call Home configuration.

pending-diff

(Optional) Displays the difference between running and pending Call Home configurations.

script-mapping

(Optional) Displays the scripts that are configured for each alert-group.

transport-email

(Optional) Displays the Call Home e-mail transport information.

user-def-cmds

(Optional) Displays the CLI commands configured for each alert group.

Command Default

None

Command Modes


Privilege EXEC(#)

Command History

Release

Modification

1.0(2)

This command was introduced.

2.0(x)

Added last action status , pending , and pending-diff options.

3.0(1)

Added the user-def-cmds argument.

7.3(1)DY(1)

Added the script-mapping keyword.

Usage Guidelines


Note

The script-mapping option is only for use by certain customers. Do not configure it if you are not approved by Cisco to use it.


Examples

The following example shows configured Call Home information:


switch# show callhome
 
callhome enabled
Callhome Information:
contact person name:who@where
contact person's email:person@place.com
contact person's phone number:310-408-4000
street addr:1234 Picaboo Street, Any city, Any state, 12345
site id:Site1ManhattanNewYork
customer id:Customer1234
contract id:Andiamo1234
switch priority:0
duplicate message throttling : enabled
periodic inventory : disabled
periodic inventory time-period : 7 days
distribution of callhome configuration data using cfs : disabled

The following example shows all destination profile information:


switch# show callhome destination-profile
 
XML destination profile information
maximum message size:250000
email addresses configured:
findout@.cisco.com
Short-txt destination profile information
maximum message size:4000
email addresses configured:
person1@epage.company.com
full-txt destination profile information
maximum message size:250000
email addresses configured:
person2@company2.com

The following example shows the full-text destination profile:


switch# show callhome destination-profile profile full-txt-destination
 
full-txt destination profile information
maximum message size:250000
email addresses configured:
person2@company2.com

The following example shows the short-text destination profile:


switch# show callhome destination-profile profile short-txt-destination 
Short-txt destination profile information
maximum message size:4000
email addresses configured:
person2@company2.com

The following example shows the XML destination profile:


switch# show callhome destination-profile profile XML-destination 
XML destination profile information
maximum message size:250000
email addresses configured:
findout@.cisco.com

The following example shows email and SMTP information:


switch# show callhome transport-email 
from email addr:user@company1.com
reply to email addr:pointer@company.com
return receipt email addr:user@company1.com
smtp server:server.company.com
smtp server port:25

The following example shows user-defined CLI commands for the alert groups:


switch# show callhome user-def-cmds
User configured commands for alert groups :
alert-group test user-def-cmd "show version"

show callhome transport

To display the Call Home transport configuration, use the show callhome transport command.

show callhome transport

Syntax Description

This command has no arguments or keywords.

Command Default

Enabled.

Command Modes


EXEC mode.

Command History

Release

Modification

NX-OS 5.2(1)

Changed the command output.

NX-OS 5.0(1a)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the Call Home transport when the proxy is not configured :


switch# show callhome transport 
http vrf:management
from email addr:S1-2@cisco.com
smtp server:171.69.21.28
smtp server port:25
smtp server vrf:management
smtp server priority:0
http proxy server:10.64.65.62
http proxy server port:8080
http proxy status:Enabled
switch#

show cdp

To display CDP parameters configured globally or for a specific interface, use the show cdp command.

show cdp {all | entry [all | name cdp-name] | global | interface [gigabitethernet slot / port | mgmt 0] | neighbors [detail | interface {gigabitethernet slot / port | mgmt 0}] | traffic interface [gigabitethernet slot / port | mgmt 0]}

Syntax Description

all

Displays all enabled CDP interfaces.

entry

Displays CDP database entries.

all

(Optional) Displays all CDP entries in the database

name cdp-name

(Optional) Displays CDP entries that match a specified name. Maximum length is 256 characters.

global

Displays global CDP parameters.

interface

Displays CDP information for neighbors on a specified interface.

gigabitethernet slot / port

(Optional) Specifies the Gigabit Ethernet interface at the slot number and port number separated by a slash (/).

mgmt 0

(Optional) Specifies the Ethernet management interface.

neighbors

Displays all CDP neighbors.

detail

(Optional) Displays detailed information for all CDP neighbors

interface

Displays CDP information for neighbors on a specified interface.

traffic

Displays CDP traffic statistics for an interface.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.1(1)

This command was introduced.

Usage Guidelines

This command is allowed only on the active supervisor module in the Cisco MDS 9500 Series.

Examples

The following example displays all CDP-capable interfaces and parameters:


switch# show cdp all
GigabitEthernet4/1 is up
    CDP enabled on interface
    Sending CDP packets every 60 seconds
    Holdtime is 180 seconds
GigabitEthernet4/8 is down
    CDP enabled on interface
    Sending CDP packets every 60 seconds
    Holdtime is 180 seconds
mgmt0 is up
    CDP enabled on interface
    Sending CDP packets every 100 seconds
    Holdtime is 200 seconds

The following example displays all CDP neighbor entries:


switch# show cdp entry all
----------------------------------------
Device ID:Switch
System Name:
Interface address(es):
Platform: cisco WS-C2950T-24, Capabilities: Switch IGMP Filtering 
Interface: mgmt0, Port ID (outgoing port): FastEthernet0/24
Holdtime: 152 sec
 
Version:
Cisco Internetwork Operating System Software 
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(19)EA1c, RELEASE SOFTWARE
 (fc2)
Copyright (c) 1986-2004 by cisco Systems, Inc.
Compiled Mon 02-Feb-04 23:29 by yenanh
 
Advertisement Version: 2
Native VLAN: 1
Duplex: full

The following example displays the specified CDP neighbor:


switch# show cdp entry name 0
----------------------------------------
Device ID:0
Entry address(es):
    IP Address: 209.165.200.226
Platform: DS-X9530-SF1-K9, Capabilities: Host
Interface: GigabitEthernet4/1, Port ID (outgoing port): GigabitEthernet4/1
Holdtime: 144 sec
Version:
1.1(0.144)
Advertisement Version: 2
Duplex: full

The following example displays global CDP parameters:


switch# show cdp global
Global CDP information:
    CDP enabled globally
    Sending CDP packets every 60 seconds
    Sending a holdtime value of 180 seconds
    Sending CDPv2 advertisements is enabled

The following example displays CDP parameters for the management interface:


switch# show cdp interface mgmt 0
mgmt0 is up
    CDP enabled on interface
    Sending CDP packets every 60 seconds
    Holdtime is 180 seconds

The following example displays CDP parameters for the Gigabit Ethernet interface:


switch# show cdp interface gigabitethernet 4/1
GigabitEthernet4/1 is up
    CDP enabled on interface
    Sending CDP packets every 80 seconds
    Holdtime is 200 seconds

The following example displays CDP neighbors (brief):


switch# show cdp neighbors
Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater
Device ID        Local Intrfce   Hldtme  Capability  Platform      Port ID
0                Gig4/1          135     H           DS-X9530-SF1- Gig4/1
069038732(Kiowa2 mgmt0           132     T S         WS-C5500      8/11
069038747(Kiowa3 mgmt0           156     T S         WS-C5500      6/20
069038747(Kiowa3 mgmt0           158     T S         WS-C5500      5/22

The following example displays CDP neighbors (detail):


switch# show CDP neighbor detail
----------------------------------------
Device ID:Switch
System Name:
Interface address(es):
Platform: cisco WS-C2950T-24, Capabilities: Switch IGMP Filtering 
Interface: mgmt0, Port ID (outgoing port): FastEthernet0/24
Holdtime: 137 sec
 
Version:
Cisco Internetwork Operating System Software 
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(19)EA1c, RELEASE SOFTWARE
 (fc2)
Copyright (c) 1986-2004 by cisco Systems, Inc.
Compiled Mon 02-Feb-04 23:29 by yenanh
 
Advertisement Version: 2
Native VLAN: 1
Duplex: full

The following example displays the specified CDP neighbor (detail):


switch# show CDP neighbors interface gigabitethernet 4/1 detail
----------------------------------------
Device ID:0
Entry address(es):
    IP Address: 209.165.200.226
Platform: DS-X9530-SF1-K9, Capabilities: Host
Interface: GigabitEthernet4/1, Port ID (outgoing port): GigabitEthernet4/1
Holdtime: 144 sec
Version:
1.1(0.144)
Advertisement Version: 2
Duplex: full

The following example displays CDP traffic statistics for the management interface:


switch# show cdp traffic interface mgmt 0
----------------------------------------
Traffic statistics for mgmt0
Input Statistics:
    Total Packets: 1148
    Valid CDP Packets: 1148
        CDP v1 Packets: 1148
        CDP v2 Packets: 0
    Invalid CDP Packets: 0
        Unsupported Version: 0
        Checksum Errors: 0
        Malformed Packets: 0
Output Statistics:
    Total Packets: 2329
        CDP v1 Packets: 1164
        CDP v2 Packets: 1165
    Send Errors: 0

The following example displays CDP traffic statistics for the Gigabit Ethernet interface:


switch# show cdp traffic interface gigabitethernet 4/1
----------------------------------------
Traffic statistics for GigabitEthernet4/1
Input Statistics:
    Total Packets: 674
    Valid CDP Packets: 674
        CDP v1 Packets: 0
        CDP v2 Packets: 674
    Invalid CDP Packets: 0
        Unsupported Version: 0
        Checksum Errors: 0
        Malformed Packets: 0
Output Statistics:
    Total Packets: 674
        CDP v1 Packets: 0
        CDP v2 Packets: 674
    Send Errors: 0 

show cfs

To display Cisco Fabric Services (CFS) information, use the show cfs command.

show cfs {application [name app-name] | lock [name app-name] | merge status [name app-name] | peers [name app-name] | status [name app-name]}

Syntax Description

application

Displays locally registered applications.

name app-name

(Optional) Specifies a local application information by name. Maximum length is 64 characters.

lock

Displays the state of application logical or physical locks.

merge status

(Optional) Displays CFS merge information.

peers

Displays logical or physical CFS peers.

status

Displays if CFS distribution is enabled or disabled. Enabled is the default configuration.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(1b)

This command was introduced.

2.1(1a)

  • Added status keyword.
  • Replaced vsan with fctimer for the fctimer application in the Application field in the command output.

3.0(1)

Modified the show cfs application example with output that shows which applications support CFS distribution over IP and Fibre Channel and those that support only CFS distribution over Fibre Channel.

Usage Guidelines

None.


Note

As soon as the customer encounters the syslog " %VSHD_4_VSHD_ROLE_DATABASE_OUT_OF _SYNC", Role configuration database is found to be different between the switches during merge. Role configuration database is recommended to be identical among all switches in the fabric. Edit the configuration on one of the switches to obtain the desire role configuration database and then commit it. For more information, Refer to the System Messages Guide.

Examples

The following example shows how to display CFS physical peer information for all applications:


switch# show cfs peers
Physical Fabric
--------------------------------------------------
 Switch WWN               IP Address
--------------------------------------------------
 20:00:00:05:30:00:61:de 209.165.200.226 [Local]
 20:00:00:0d:ec:08:66:c0 209.165.200.226 
 20:00:00:05:30:00:f1:e2 209.165.200.226 
 20:00:00:05:30:00:eb:46 209.165.200.226 
 20:00:00:05:30:00:cb:56 209.165.200.227
20:00:00:05:30:00:5b:5e 209.165.200.228
 20:00:00:05:30:00:34:9e 209.165.200.229
Total number of entries = 7

The following example shows how to display CFS information for all applications on the switch:


switch# show cfs application
----------------------------------------------
 Application    Enabled   Scope
----------------------------------------------
ntp            No        Physical-all
fscm           Yes       Physical-fc
role           No        Physical-all
rscn           No        Logical
radius         No        Physical-all
fctimer        No        Physical-fc
syslogd        No        Physical-all
callhome       No        Physical-all
fcdomain       Yes       Logical
device-alias   Yes       Physical-fc
Total number of entries = 10

Note

The show cfs application command displays only those applications that are registered with CFS. Conditional services that use CFS do not appear in the output unless those services are running.

The following example shows how to display CFS information for the device alias application:


switch# show cfs application name device-alias
 Enabled        : Yes
 Timeout        : 5s
 Merge Capable  : Yes
 Scope          : Physical

The following example shows how to display CFS merge operation information for the device alias application:


switch# show cfs merge status device-alias
Physical  Merge Status: Success
 Local Fabric
---------------------------------------------------------
 Switch WWN               IP Address
---------------------------------------------------------
 20:00:00:05:30:00:34:9e 209.165.200.226 [Merge Master]
 20:00:00:05:30:00:5b:5e 209.165.200.227 
 20:00:00:05:30:00:61:de 209.165.200.228 
 20:00:00:05:30:00:cb:56 209.165.200.229 
 20:00:00:05:30:00:eb:46 209.165.200.230 
 20:00:00:05:30:00:f1:e2 209.165.200.231 

The following example shows whether or not CFS distribution is enabled:


switch# show cfs status
 
Fabric distribution Enabled
switch# 

show cfs regions

To display the list of distribution-enabled applications with peers in a region, use the show cfs region command.

show cfs regions [brief [region-id] | name [name app-name] | region [region-id]]

Syntax Description

brief region-id

(Optional) Displays all configured regions and applications without peers.

name name app-name

(Optional) Displays all peers and region information for a given application.

region region-id

(Optional) Displays all configured applications with peers.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows all the region information with peers:


switch# show cfs regions
Region-ID  : 1
Application: callhome
Scope      : Physical-all
-------------------------------------------------------------------------
 Switch WWN              IP Address
-------------------------------------------------------------------------
 20:00:00:0d:ec:04:99:c0 209.165.200.226 [Local]
                         switch- 
 20:00:00:0d:ec:04:99:c1 209.165.200.226 
                         switch-2.cisco.com
 20:00:00:0d:ec:04:99:c2 209.165.200.226 
                         switch-3.cisco.com
Total number of entries = 3
Region-ID  : 1
Application: ntp
Scope      : Physical-all
-------------------------------------------------------------------------
 Switch WWN              IP Address
-------------------------------------------------------------------------
 20:00:00:0d:ec:06:55:c0 209.165.200.226 [Local]
                         switch-1
Total number of entries = 1

The following example shows the list of applications without peers in a region:


switch# show cfs regions brief
---------------------------------------
 Region         Application   Enabled
---------------------------------------
   1            callhome      yes
   1            ntp           yes

The following example shows the peer and region information for a given application in a region:


switch# show cfs regions name callhome
Region-ID  : 1
Application: callhome
Scope      : Physical-all
-------------------------------------------------------------------------
 Switch WWN              IP Address
-------------------------------------------------------------------------
 20:00:00:0d:ec:06:55:c0 209.165.200.226 [Local]
                         switch 1
Total number of entries = 1

show cfs static peers

To display all the configured static peers with status, use the show cfs static peers command.

show cfs static peers

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

4.1(1b)

This command was introduced.

Usage Guidelines

None.

Examples

The following example displays the CFS static peers:


-----------------------------------------------------------------------------
 IP address                      WWN name                Status
-----------------------------------------------------------------------------
 1.2.3.4              00:00:00:00:00:00:00:00          Un Reachable
 1.2.3.5              00:00:00:00:00:00:00:00          Un Reachable
 10.64.66.47          20:00:00:0d:ec:06:55:c0          Reachable
 10.64.66.56          20:00:08:00:88:04:99:80          Local
Total number of entries = 4

show cfs status

To display the Cisco Fabric Services (CFS) status, use the show cfs region command.

show cfs status

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode

Command History

Release

Modification

4.1(1b)

This command was introduced.

Usage Guidelines

None.

Examples

The following example displays the CFS status:


switch# show cfs status
Distribution: Enabled
Distribution over IP: Enabled (static)
IPv4 multicast address : 239.255.70.83
IPv6 multicast address : ff15::efff:4563

show cimserver

To display the Common Information Model (CIM) configurations and settings, use the show cimserver command.

show cimserver [certificateName | HttpsStatus | HttpStatus | status]

Syntax Description

certificateName

(Optional) Displays the installed Secure Socket Layer (SSL) certificate.

HttpsStatus

(Optional) Displays the HTTPS (secure) protocol settings for the CIM server.

HttpStatus

(Optional) Displays the HTTP (non-secure) protocol for the CIM server.

status

(Optional) Displays the CIM server status.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.3(1)

This command was introduced.

5.2(1)

This command was deprecated.

Usage Guidelines

None.

Examples

The following example displays CIM server certificate files:


switch# show cimserver certificateName
cimserver certificate file name is servcert.pem

The following example displays the CIM server configuration:


switch# show cimserver
 cimserver is enabled
 cimserver Http is not enabled
 cimserver Https is enabled
 cimserver certificate file name is servcert.pem

The following example displays the CIM server HTTPS status:


switch# show cimserver httpsstatus
 cimserver Https is enabled

The following example displays the CIM server HTTP status:


switch# show cimserver httpstatus
 cimserver Http is not enabled

show cimserver indications

To display cimserver indications such as filters, recipients, and subscriptions, use the show cimserver indication command.

show cimserver indication

Syntax Description

This command has no arguments or keywords:

Command Default

None.

Command Modes


EXEC mode

Command History

Release

Modification

3.3(1a)

This command was introduced.

5.2(1)

This command was deprecated.

Usage Guidelines

None.

Examples

The following example displays the cimserver indications:


switch# show cimserver indication
Filter:           root/cimv2:Feb 7, 2008 2:32:11 PM
Query:            "SELECT * FROM CISCO_LinkUp"
Query Language:   WQL
-----------------------------------------
Handler:           root/cimv2:CIM_ListenerDestinationCIMXML.Thu Feb 07 14:32:44 IST 20081202374964083
Destination:       http://10.77.91.110:59901
PersistenceType:   Transient
-----------------------------------------
Namespace:         root/cimv2
Filter:            root/cimv2:Feb 7, 2008 2:32:11 PM
Handler:           root/cimv2:CIM_ListenerDestinationCIMXML.Thu Feb 07 14:32:44 IST 20081202374964083
Query:             "SELECT * FROM CISCO_LinkUp"
Destination:       http://10.77.91.110:59901
SubscriptionState: Enabled
The following example displays the cimserver’s indication filters:
switch# show cimserver indication filters
Filter:           root/cimv2:Feb 7, 2008 2:32:11 PM
Query:            "SELECT * FROM CISCO_LinkUp"
Query Language:   WQL
The following example displays the cimserver’s indication recipient:
switch# show cimserver indication recipients
Handler:           root/cimv2:CIM_ListenerDestinationCIMXML.Thu Feb 07 14:32:44 IST 20081202374964083
Destination:       http://10.77.91.110:59901
PersistenceType:   Transient
The following example displays the subscriptions on cimserver:
switch# show cimserver indication subscriptions
Namespace:         root/cimv2
Filter:            root/cimv2:Feb 7, 2008 2:32:11 PM
Handler:           root/cimv2:CIM_ListenerDestinationCIMXML.Thu Feb 07 14:32:44 IST 20081202374964083
Query:             "SELECT * FROM CISCO_LinkUp"
Destination:       http://10.77.91.110:59901
SubscriptionState: Enabled

show cimserver logs

To display the cimserver logs, use the show cimserver logs command.

show cimserver logs

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode

Command History

Release

Modification

3.3(1a)

This command was introduced.

5.2(1)

This command was deprecated.

Usage Guidelines

None.

Examples

The following example displays the cimserver logs:


switch# show cimserver logs
02/07/2008-16:38:14 INFO    cimserver: Sent response to: localhost
02/07/2008-16:38:26 INFO    cimserver: Received request from: 10.77.91.110
02/07/2008-16:38:27 INFO    cimserver: Sent response to: 10.77.91.110

show cimserver status

To display the cimserver status, use the show cimserver status command.

show cimserver status

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode

Command History

Release

Modification

3.3(1a)

This command was introduced.

5.2(1)

This command was deprecated.

Usage Guidelines

None.

Examples

The following example displays the cimserver status:


switch# show cimserver status
cimserver is enabled

show cli alias

To display configured aliases on a switch, use the show cli alia s command.

show cli alias [name name]

Syntax Description

name name

(Optional) Specifies an alias name. The maximum size of the name is 31 characters.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(1)

This command was introduced.

Usage Guidelines

The show cli alias command shows the default alias and other user-defined aliases. The default alias is alias , which means show cli alias .

Examples

The following example displays CLI aliases:


switch# show cli alias
CLI alias commands
==================
alias  :show cli alias
env    :show environment
clock  :show clock

The following example displays a specific alias by name:


switch# show cli alias name qos
qos :show qos

show cli variables

To display user-defined session and persistent CLI variables, use the show cli variables command.

show cli variables

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(1)

This command was introduced.

Usage Guidelines

The show CLI variables command shows all available CLI variables, including user-defined session CLI variables, user-defined persistent CLI variables, and system-defined CLI variables. There is no distinction between the types of CLI variables in the output.

Examples

The following example displays CLI variables:


switch# show cli variables
VSH Variable List
-----------------
TIMESTAMP="2005-10-24-21.29.33"
testinterface="fc 1/1"

Note

The TIMESTAMP variable shown in the output in the preceding example is a predefined variable supported by Cisco MDS NX-OS. For more information about the TIMESTAMP variable, refer to the Cisco MDS 9000 Family CLI Configuration Guide .

show clock

To display the system date and time and verify the time zone configuration, use the show clock command.

show clock

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

1.0(2)

This command was introduced.

Usage Guidelines

None.

Examples

The following example displays the system date, time, and time zone configuration:


switch# show clock
Fri Mar 14 01:31:48 UTC 2003

show cloud discovery

To display discovery information about the cloud, use the show cloud discovery command.

show cloud discovery {config | stats | status}

Syntax Description

config

Displays global discovery configuration information.

stats

Displays discovery statistics information.

status

Displays discovery status information.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(1)

This command was introduced.

3.2(2c)

This command was deprecated.

Usage Guidelines

None.

Examples

The following example shows information about a cloud:


switch# show cloud discovery config
Auto discovery: Enabled

The following example shows statistics about a cloud:


switch# show cloud discovery stats
Global statistics
    Number of Auto Discovery                       = 4
    Number of Manual (demand) Discovery                     = 0
    Number of cloud discovery (ping) messages sent = 17
    Number of cloud discovery (ping) success       = 1

show cloud membership

To display membership information about the cloud, use the show cloud membership command.

show cloud membership [all | interface {gigabitethernet slot/ port | port-channel number} | unresolved]

Syntax Description

all

(Optional) Displays all clouds and cloud members.

interface

(Optional) Displays all members of a cloud containing a specified interface.

gigabitethernet slot/port

Specifies a Gigabit Ethernet interface by slot and port number. The range is 1 to 6.

port-channel number

Specifies a PortChannel interface. The range is 1 to 128.

unresolved

(Optional) Displays unresolved members of the cloud.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(1)

This command was introduced.

3.2(2c)

This command was deprecated.

Usage Guidelines

None.

Examples

The following example displays the members of clouds:


switch# show cloud membershp
Undiscovered Cloud
    port-channel 1[20:00:00:05:30:00:a7:9e] IP Addr fe80::205:30ff:fe00:a412
    port-channel 1.250[20:00:00:05:30:00:a7:9e] IP Addr 3000:2::1
    port-channel 1.250[20:00:00:05:30:00:a7:9e] IP Addr fe80::205:30ff:fe00:a412
  #members=3
Cloud 2
    port-channel 1[20:00:00:05:30:00:a7:9e] IP Addr 3000:1::1
  #members=1
Cloud 3
    GigabitEthernet1/1[20:00:00:05:30:00:a7:9e] IP Addr 10.10.10.1
  #members=1
Cloud 4
    GigabitEthernet1/2[20:00:00:05:30:00:a7:9e] IP Addr 10.10.60.1
  #members=1

show congestion-isolation

To display information about the devices configured for the Congestion Isolation feature, use the show congestion-isolation command.

show congestion-isolation {exclude-list | | global-list | | ifindex-list | | include-list | | pmon-list | | remote-list | | status} [vsan vsan-id]

Syntax Description

exclude-list

Lists the devices that were manually excluded as slow devices.

global-list

Lists the devices that were detected as slow in a fabric, when the Congestion Isolation feature was enabled.

ifindex-list

Lists the interfaces that are isolated as slow devices.

include-list

Lists the devices that were manually configured as slow devices.

pmon-list

Lists the devices that were detected as slow devices on a local switch.

remote-list

Lists the devices that were detected as slow devices on remote switches (not locally detected slow devices).

status

Displays the status of the Congestion Isolation feature.

vsan

Specifies a virtual storage area network (VSAN).

vsan-id

VSAN ID. Range is 1 to 4093.

Command Default

None.

Command Modes

Privilege EXEC (#)

Command History

Release

Modification

8.5(1)

This command was deprecated.

8.1(1)

This command was introduced.

Usage Guidelines

From Cisco MDS NX-OS Release 8.5(1), use the show fpm command instead of this command.

Examples

The following example shows the list of devices that are detected as slow on a local switch:


switch# show congestion-isolation pmon-list vsan 4
PMON detected list for vsan 4 : PWWN(FCID)
===============================================
10:00:00:00:c9:f9:16:8d(0xbe0000)

 

The following example shows the global list of devices that are detected as slow in a fabric where the Congestion Isolation feature is enabled:


switch# show congestion-isolation global-list vsan 4
Global list for vsan 4 PWWN(FCID)
========================================
10:00:00:00:c9:f9:16:8d(0xbe0000)

The following example shows the list of devices that are detected as slow on remote switches (not locally detected slow devices):


switch# show congestion-isolation remote-list vsan 4
Remote list for vsan 4 : PWWN(FCID)
===============================================
10:00:00:00:c9:f9:16:8d(0xbe0000)

The following example shows the list of devices that are manually configured as slow devices on a local switch:


switch# show congestion-isolation include-list vsan 4
Include list for vsan 4 : PWWN(FCID) (online/offline)
=========================================================
10:00:00:00:c9:f9:16:8d(0xbe0000) - (Online)
switch# show fcns database vsan 4
VSAN 4:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x040000 N 10:00:40:55:39:0c:80:85 (Cisco) ipfc
0x040020 N 21:00:00:24:ff:4f:70:47 (Qlogic) scsi-fcp:target
0xbe0000 N 10:00:00:00:c9:f9:16:8d (Emulex) scsi-fcp:init slow-dev <<<slow
device [testing]Total number of entries = 3

The following example shows the list of devices that are manually excluded as slow devices on a local switch:


switch# show congestion-isolation exclude-list vsan 4
Exclude list for vsan 4 : PWWN(FCID) (online/offline)
=========================================================

show consistency-checker

To verify the consistency between various internal system tables, use the show consistency-checker command.

show consistency-checker { {acl-table-status | fib-table-status} [module number] | pss}

Syntax Description

acl-table-status

Compares software and hardware access control list (ACL) table status.

fib-table-status

Compares software and hardware forwarding information base (FIB) table status.

module number

(Optional) Module number.

pss

Checks for inconsistency across memory, shared, and persistent data.

Command Default

Displays consistency information for all modules.

Command Modes


Privileged EXEC (#)

Command History

Release

Modification

8.4(1)

This command was introduced.

Usage Guidelines

The show consistency-checker command is a troubleshooting tool that helps to identify inconsistent state between software and hardware tables in the switch. Such conditions are abnormal and may lead to data forwarding issues in the switch. Programmatic checking by this command assures accuracy of checks and reduces the time to identify the table inconsistencies.

This command should be used as part of troubleshooting when data forwarding issues are suspected. It compares the software state of the supervisor with the hardware state of supported I/O modules. The specified consistency check is done at the time the command is issued and the results are displayed. Detailed information about detected inconsistencies is displayed to direct further detailed debugging.

Examples

The following example runs the ACL Consistency Checker for module 3 on demand and displays the results. This example shows the abnormal case of test failure.


switch# show coonsistency-checker acl-table-status module 3
Running ACL Consistency checker. Please wait, while consistency checks are in progress!!!

-----------------------------------------------------------------------------------------------------------------------
                                                     MODULE-3                                                     
Validating ingress ACL IPS entries for all fwd-engine...
Validating egress ACL IPS entries for all fwd-engine...
Validating ingress ACL FC entries
fwd-engine 0...
fwd-engine 1...
fwd-engine 2...
Validating egress ACL FC entries
fwd-engine 0...
fwd-engine 1...
fwd-engine 2...

DETAILED SUMMARY:
input
    Fwd-Engine: all
        Shadow & Hardware Sync Errors: 
            Mismatch Count: HW(1) SW(1)
Hardware Mismatch Entries:
   d ALL     0      0      0 ANY       NA   4       22   0    0  78   0    0 |    1  0    0      0      0
Shadow Mismatch Entries:
   d ALL     0      0      0  15  2ec ANY       -    4       22   0    0  78   0    0 |    1  0    0      0      0

output
============================================================
SUMMARY:
MODULE : 3
    TIME TAKEN:                       61.23 seconds
    IPS HARDWARE & SHADOW SYNC STATUS: FAILED 
    FC HARDWARE & SHADOW SYNC STATUS: PASSED 
    FC DUPLICATE CHECKS:              PASSED
============================================================
 

The following example runs the FIB Consistency Checker for module 1 on demand and displays the results. This example shows the abnormal case of test failures.


switch# show consistency-checker fib-table-status module 1
Running FC FIB Consistency checker. Please wait, while consistency checks are in progress!!!

-------------------------------------------------------------------------------
                                  MODULE-1                                                 
Validating FIB IPS Fwd Hardware and Software Entries
fwd-engine 0...
Validating FIB FC Fwd Hardware and Software Entries
fwd-engine 0...
fwd-engine 1...
fwd-engine 2...
Validating FIB FC ADJ Hardware and Shadow Entries...
fwd-engine 0...
fwd-engine 1...
fwd-engine 2...

DETAILED SUMMARY:
Fwd Engine: 0 
 FORWARDING TABLE
All fields in hex except VSAN

Route                Fwd   Fwd  | Num   Grp   Path  Adj   
Type   VSAN D ID     Idx   DRAM | Path  Idx   Idx   Idx   VDC  FE
----   ---- ------  -----  ---- + ----  ----  ----  ----  ---  --
 Hardware Mismatch Entries: 
wka    0000 fffffe   07d2  1d01 | 1     ....  ....  004c  01   00 0

 Software Mismatch Entries: 
wka    0000 fffffe   07d2  1d01 | 1     ....  ....  004f  01   00 0

Fwd Engine: 0 
 ADJACENCY TABLE
M:multicast I:D_IDX_CTL S:span B:bundle F:fcoe_bit 
All fields in hex.

Adj                                         | Fwd
Idx   DIdx/fcoe_base M I B Span  fcoe_bit   | Idx
----- ------------------------------------- + ----
 Hardware Mismatch Entries: 
00001    000         F F F 00000    T        | 0017 0

 Software Mismatch Entries: 
00001    03e        F F F 00000      F       | 0017 0
============================================================
SUMMARY:
Module : 1
    Time Taken:                        31.24 seconds
    FWDFC Table Hardware & Software Sync Status: PASSED
    FWDIPS Table Hardware & Software Sync Status: FAILED
         Hardware Mismatch Counts: 1
         Software Mismatch Counts: 1
    ADJFC Table Hardware & Software Sync Status: FAILED
         Hardware Mismatch Counts: 1
         Software Mismatch Counts: 1
============================================================
 

The following example displays the persistent storage service (PSS) Consistency Checker information on an active supervisor. This example shows the abnormal case of test failure.


switch# show consistency-checker pss
PSS CONSISTENCY CHECK RESULT FOR ELTM: SUCCESS
---------------------------------------------------------------
No inconsistency detected in ELTM data
==============================================================
PSS CONSISTENCY CHECK RESULT FOR ETHPM: SUCCESS
---------------------------------------------------------------
No inconsistency detected in ethpm persistent, runtime and shared data.
==============================================================
---------------------------------------------------------
ATTRIBUTE NAME         : Flogi info Runtime Data 
INCONSISTENT INTERFACE : fc2/13 
---------------------------------------------------------
PSS CONSISTENCY CHECK RESULT FOR FPORT_SVR: FAILURE
---------------------------------------------------------------
Please collect tech-support for fport_svr for more details.
==============================================================
PSS CONSISTENCY CHECK RESULT FOR STP: SUCCESS 
---------------------------------------------------------------
No inconsistency detected in STP CBL data
==============================================================
PSS CONSISTENCY CHECK RESULT FOR VLAN_MGR: SUCCESS
---------------------------------------------------------------
No inconsistency detected in vlan_mgr persistent, runtime and shared data.
==============================================================
 

show consistency-checker analytics

To identify inconsistencies in SAN analytics components such as NPU, modules, queries, database, analytics ACL entries, and so on, use the show consistency-checker analytics command.

show consistency-checker analytics

Command Default

None.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

9.2(1)

This command was introduced.

Usage Guidelines

This command is a troubleshooting tool that helps to identify inconsistencies in SAN analytics components such as NPU, modules, queries, database, port-sampling configuration and so on. Such inconsistencies are abnormal and may lead to issues on the switch. Programmatic checking by this command assures accuracy of checks and reduces the time to identify such inconsistencies.

This command should be used as part of troubleshooting when SAN analytics issues are suspected. The specified consistency check is done at the time the command is issued and the results are displayed. Detailed information about the detected inconsistencies is displayed to direct further detailed debugging.

Examples

The following example displays how to display the inconsistencies in SAN analytics:


switch# show consistency-checker analytics 


Analytics Consistency Checker: 

Checking for Analytics related consistency checks for the SUP: 

Checking for queries consistency...  - Skipped (Queries not configured) Checking for global database consistency... - Passed Checking for query_id consistency...  - Passed

Checking for Analytics related consistencies for the Line Cards: 

Module 1 :


Checking for ifindex consistency...  - Passed Checking for ACL consistency...
Running config: SCSI+NVME both for interface fc1/3 Running config: SCSI+NVME both for interface fc1/4 ACL TCAM: SCSI+NVME both for interface fc1/3 ACL TCAM: SCSI+NVME both for interface fc1/4 Running config and ACL TCAM entries are consistent for all interfaces Checking for extra entries in ACL. Please wait...
No extra analytics entry found for non-analytics interfaces. Consistency check successful.
Checking for bcm status...
BCM Status passed successfully.
Checking for Port-Sampling Config Consistency.....
========>>>>>>> Skipped (Not Configured on SUP and Linecard)


No EIOA drops seen
No MPP drops seen
XGMAC9 Port Link =>  UP!!!


Both XFI links are UP!

Traps observed in ncpmgr: 0


show copyright

To display the NX-OS software copyright statement, use the show copyright command in EXEC mode.

show copyright

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(2)

This command was introduced.

NX-OS 4.1(1b)

Changed the command output from SAN-OS to NX-OS.

Usage Guidelines

Use the show copyright command to verify the copyright statement of the current NX-OS image.

Examples

The following example displays copyright information for NX-OS software:


switch# show copyright
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
switch#

show cores

To display a list of core bundles in the switch core repository, use the show cores command.

show cores

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


Privileged EXEC (#)

Command History

Release

Modification

1.0(2)

This command was introduced.

Usage Guidelines

The core repository can hold around 10 core bundles. Each platform has different limits. Therefore, it is important to copy core bundles to mass storage and then delete them from the repository to free up space.

Examples

This example shows the list of core bundles in the switch core repository:


switch# show cores
Module  Instance  Process-name     PID       Date(Year-Month-Day Time)
------  --------  ---------------  --------  -------------------------
5       1         kernel           1         2021-04-20 08:18:55

show crypto ca certificates

To display configured trust point certificates, use the show crypto ca certificates command.

show crypto ca certificates trustpoint-label

Syntax Description

trustpoint-label

Specifies the name of the trust point. The maximum size is 64 characters.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(1)

This command was introduced.

Usage Guidelines

This command displays the important fields in the identity certificate, if present, followed by those in the CA certificate (or each CA certificate if it is a chain, starting from the lowest to the self-signed root certificate), or the trust point. If the trust point name is not specified, all trust point certificate details are displayed.

Examples

The following example displays configured trust point certificates:


switch# show crypto ca certificates
Trustpoint: admin-ca
certificate:
subject= /CN=switch160
issuer= /C=US/O=cisco/CN=Aparna CA2
serial=6CDB2D9E000100000006
notBefore=Jun  9 10:51:45 2005 GMT
notAfter=May  3 23:10:36 2006 GMT
MD5 Fingerprint=0A:22:DC:A3:07:2A:9F:9A:C2:2C:BA:96:EC:D8:0A:95
purposes: sslserver sslclient ike
CA certificate 0:
subject= /C=US/O=cisco/CN=Aparna CA2
issuer= /emailAddress=amandke@cisco.com/C=IN/ST=Maharashtra/L=Pune/O=cisco/OU=ne
tstorage/CN=Aparna CA1
serial=14A3A877000000000005
notBefore=May  5 18:43:36 2005 GMT
notAfter=May  3 23:10:36 2006 GMT
MD5 Fingerprint=32:50:26:9B:16:B1:40:A5:D0:09:53:0A:98:6C:14:CC
purposes: sslserver sslclient ike
CA certificate 1:
subject= /emailAddress=amandke@cisco.com/C=IN/ST=Maharashtra/L=Pune/O=cisco/OU=n
etstorage/CN=Aparna CA1
issuer= /emailAddress=amandke@cisco.com/C=IN/ST=Karnataka/L=Bangalore/O=Cisco/OU
=netstorage/CN=Aparna CA
serial=611B09A1000000000002
notBefore=May  3 23:00:36 2005 GMT
notAfter=May  3 23:10:36 2006 GMT
MD5 Fingerprint=65:CE:DA:75:0A:AD:B2:ED:69:93:EF:5B:58:D4:E7:AD
purposes: sslserver sslclient ike
CA certificate 2:
subject= /emailAddress=amandke@cisco.com/C=IN/ST=Karnataka/L=Bangalore/O=Cisco/O
U=netstorage/CN=Aparna CA
issuer= /emailAddress=amandke@cisco.com/C=IN/ST=Karnataka/L=Bangalore/O=Cisco/OU
=netstorage/CN=Aparna CA
serial=0560D289ACB419944F4912258CAD197A
notBefore=May  3 22:46:37 2005 GMT
notAfter=May  3 22:55:17 2007 GMT
MD5 Fingerprint=65:84:9A:27:D5:71:03:33:9C:12:23:92:38:6F:78:12
purposes: sslserver sslclient ike

show crypto ca crl

To display configured certificate revocation lists (CRLs), use the show crypto ca crl command.

show crypto ca crl trustpoint-label

Syntax Description

trustpoint-label

Specifies the name of the trust point. The maximum size is 64 characters.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(1)

This command was introduced.

Usage Guidelines

This command lists serial numbers of revoked certificates in the CRL of the specified trust point.

Examples

The following example displays a configured CRL:


switch# show crypto ca crl admin-ca
Trustpoint: admin-ca
CRL:
Certificate Revocation List (CRL):
        Version 2 (0x1)
        Signature Algorithm: sha1WithRSAEncryption
        Issuer: /emailAddress=rviyyoka@cisco.com/C=IN/ST=Kar/L=Bangalore/O=Cisco
 Systems/OU=1/CN=cisco-blr
        Last Update: Sep 22 07:05:23 2005 GMT
        Next Update: Sep 29 19:25:23 2005 GMT
        CRL extensions:
            X509v3 Authority Key Identifier:
            keyid:CF:72:E1:FE:14:60:14:6E:B0:FA:8D:87:18:6B:E8:5F:70:69:05:3F
            1.3.6.1.4.1.311.21.1:
                ...
Revoked Certificates:
    Serial Number: 1E0AE838000000000002
        Revocation Date: Mar 15 09:12:36 2005 GMT
    Serial Number: 1E0AE9AB000000000003
        Revocation Date: Mar 15 09:12:45 2005 GMT
    Serial Number: 1E721E50000000000004
        Revocation Date: Apr  5 11:04:20 2005 GMT
    Serial Number: 3D26E445000000000005
        Revocation Date: Apr  5 11:04:16 2005 GMT
    Serial Number: 3D28F8DF000000000006
        Revocation Date: Apr  5 11:04:12 2005 GMT
    Serial Number: 3D2C6EF3000000000007
        Revocation Date: Apr  5 11:04:09 2005 GMT
    Serial Number: 3D4D7DDC000000000008
        Revocation Date: Apr  5 11:04:05 2005 GMT
    Serial Number: 5BF1FE87000000000009
        Revocation Date: Apr  5 11:04:01 2005 GMT
    Serial Number: 5BF22FB300000000000A
        Revocation Date: Apr  5 11:03:45 2005 GMT
    Serial Number: 5BFA4A4900000000000B
        Revocation Date: Apr  5 11:03:42 2005 GMT
    Serial Number: 5C0BC22500000000000C
        Revocation Date: Apr  5 11:03:39 2005 GMT
    Serial Number: 5C0DA95E00000000000D
        Revocation Date: Apr  5 11:03:35 2005 GMT
    Serial Number: 5C13776900000000000E
        Revocation Date: Apr  5 11:03:31 2005 GMT
    Serial Number: 4864FD5A00000000000F
        Revocation Date: Apr  5 11:03:28 2005 GMT
    Serial Number: 48642E2E000000000010
        Revocation Date: Apr  5 11:03:24 2005 GMT
    Serial Number: 486D4230000000000011
        Revocation Date: Apr  5 11:03:20 2005 GMT
    Serial Number: 7FCB75B9000000000012
        Revocation Date: Apr  5 10:39:12 2005 GMT
    Serial Number: 1A7519000000000013
        Revocation Date: Apr  5 10:38:52 2005 GMT
    Serial Number: 20F1B0000000000014
        Revocation Date: Apr  5 10:38:38 2005 GMT
    Serial Number: 436E43A9000000000023
        Revocation Date: Sep  9 09:01:23 2005 GMT
        CRL entry extensions:
            X509v3 CRL Reason Code:
            Cessation Of Operation
    Serial Number: 152D3C5E000000000047
        Revocation Date: Sep 22 07:12:41 2005 GMT
    Serial Number: 1533AD7F000000000048
        Revocation Date: Sep 22 07:13:11 2005 GMT
    Serial Number: 1F9EB8EA00000000006D
        Revocation Date: Jul 19 09:58:45 2005 GMT
        CRL entry extensions:
            X509v3 CRL Reason Code:
            Cessation Of Operation
    Serial Number: 1FCA9DC600000000006E
        Revocation Date: Jul 19 10:17:34 2005 GMT
        CRL entry extensions:
            X509v3 CRL Reason Code:
            Cessation Of Operation
    Serial Number: 2F1B5E2E000000000072
        Revocation Date: Jul 22 09:41:21 2005 GMT
        CRL entry extensions:
            X509v3 CRL Reason Code:
            Cessation Of Operation
    Signature Algorithm: sha1WithRSAEncryption
        4e:3b:4e:7a:55:6b:f2:ec:72:29:70:16:2a:fd:d9:9a:9b:12:
        f9:cd:dd:20:cc:e0:89:30:3b:4f:00:4b:88:03:2d:80:4e:22:
        9f:46:a5:41:25:f4:a5:26:b7:b6:db:27:a9:64:67:b9:c0:88:
        30:37:cf:74:57:7a:45:5f:5e:d0

show crypto ca remote-certstore

To display configured remote certstores, use the show crypto ca remote-certstore command.

show crypto ca remote certstore

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command Default

None.

Command History

Release

Modification

NX-OS 5.0(1a)

This command was introduced.

Usage Guidelines

None.


Note

In the current 5.0 release only ssh-client will use remote certstore. Other applications like ike, callhome will continue using local certstore irrespective of the configurations.

Examples

The following example shows how to display configured remote certstores:


switch# show crypto ca remote-certstore
Remote Certstore:LDAP
CRL Timer : 10 Hours
LDAP Server group : Ldap1
switch#

show crypto ca trustpoints

To display trust point configurations, use the show crypto ca trustpoints command.

show crypto ca trustpoints

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example displays configured trust points:


switch# show crypto ca trustpoints
trustpoint: CAname; key:
revokation methods:  crl

show crypto certificatemap

To display certificatemap filters, use the show crypto certificatemap command.

show crypto certificatemap

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command Default

None.

Command History

Release

Modification

NX-OS 5.0(1a)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display certificatemap filters:


switch# show crypto certificatemap
Map Name: map1
Subject name: /DCBU
Altname Email: koukumar@cisco.com
Altname UPN:
switch#

show crypto global domain ipsec

To display global IPsec crypto map set information, use the show crypto global domain ipsec command.

show crypto global domain ipsec [interface gigabitethernet slot/ port | security-association lifetime]

Syntax Description

interface gigabitethernet slot/port

(Optional) Displays crypto IPsec domain information for the specified Gigabit Ethernet interface slot and port.

security-association lifetime

(Optional) Displays crypto IPsec domain security association lifetime parameters.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(x)

This command was introduced.

Usage Guidelines

To use this command, IPsec must be enabled using the crypto ipsec enable command.

Examples

The following example shows how to display crypto global domain IPsec statistics:


switch# show crypto global domain ipsec
IPSec global statistics:
        Number of crypto map sets: 2

The following example shows how to display crypto global domain IPsec statistics for an interface:


switch# show crypto global domain ipsec interface gigabitethernet 1/2
IPSec interface statistics:
        IKE transaction stats: 0 num
        Inbound SA stats: 0 num, 512 max
        Outbound SA stats: 0 num, 512 max

The following example shows how to display crypto global domain IPsec security association lifetime parameters:


switch# show crypto global domain ipsec security-association lifetime
Security Association Lifetime: 4500 megabytes/3600 seconds

show crypto ike domain ipsec

To display IKE protocol information, use the show crypto ike domain ipsec command.

show crypto ike domain ipsec [initiator [address ip-address] | keepalive | key [address ip-address] | policy [policy-number] | sa]

Syntax Description

initiator

(Optional) Displays initiator configuration information.

address ip-address

Specifies the initiator peer IP address.

keepalive

(Optional) Displays keepalive for the IKE protocol in seconds

key

(Optional) Displays pre-shared authentication keys.

policy policy-number

Displays IKE configuration policies for IPsec. The range is 1 to 255.

sa

(Optional) Displays IKE Security Associations for IPsec.

Command Default

To use this command, the IKE protocol must be enabled using the crypto ike enable command.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(x)

This command was introduced.

Usage Guidelines

To use this command, the IKE protocol must be enabled using the crypto ike enable command.

Examples

The following example shows how to display IKE keepalive value configuration information:


switch# show crypto ike domain ipsec keepalive
keepalive 3600

show crypto key mypubkey rsa

To display any RSA public key configurations, use the show crypto key mypubkey rsa command.

show crypto key mypubkey rsa

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.0(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example displays RSA public key configurations:


switch# show crypto key mupubkey rsa
key label: myrsa
key size: 512
exportable: yes

show crypto map domain ipsec

To map configuration information for IPsec, use the show crypto map domain ipsec command.

show crypto map domain ipsec [interface gigabitethernet slot / port | tag tag-name]

Syntax Description

interface gigabitethernet slot /port

(Optional) Displays IPsec map information for a specific Gigabit Ethernet interface.

tag tag-name

(Optional) Displays IPsec map information for a specific tag name. The maximum length is 63 characters.

Command Default

Displays all IPsec map information.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(x)

This command was introduced.

Usage Guidelines

To use this command, IPsec must be enabled using the crypto ipsec enable command.

Examples

The following example shows how to display IPsec crypto map information:


switch# show crypto map domain ipsec
Crypto Map "cm10" 1 ipsec
        Peer = 10.10.10.4
        IP ACL = aclmds10
            permit ip 10.10.10.1 255.255.255.255 10.10.10.4 255.255.255.255
        Transform-sets: 3des-md5, 3des-sha, des-md5, des-sha,
        Security Association Lifetime: 450 gigabytes/3600 seconds
        PFS (Y/N): N
Crypto Map "cm10" 2 ipsec
        Peer = Auto Peer
        IP ACL = acl10
            permit ip 10.10.10.0 255.255.255.0 10.10.10.0 255.255.255.0
        Transform-sets: 3des-md5, 3des-sha, des-md5, des-sha,
        Security Association Lifetime: 450 gigabytes/3600 seconds
        PFS (Y/N): N
Crypto Map "cm11" 1 ipsec
        Peer = 10.10.11.2
        IP ACL = aclany
            permit ip any any
        Transform-sets: 3des-md5, 3des-sha, des-md5, des-sha,
        Security Association Lifetime: 450 gigabytes/3600 seconds
        PFS (Y/N): N
Crypto Map "cm50" 1 ipsec
        Peer = 10.10.50.2
        IP ACL = aclany
            permit ip any any
        Transform-sets: 3des-md5,
        Security Association Lifetime: 450 gigabytes/3600 seconds
        PFS (Y/N): N
Interface using crypto map set cm50:
    GigabitEthernet1/2.1
Crypto Map "cm51" 1 ipsec
        Peer = 10.10.51.2
        IP ACL = aclany
            permit ip any any
        Transform-sets: 3des-md5,
        Security Association Lifetime: 450 gigabytes/3600 seconds
        PFS (Y/N): N
Interface using crypto map set cm51:
    GigabitEthernet1/2.2
Crypto Map "cm60" 1 ipsec
        Peer = 10.10.60.2
        IP ACL = acl60
            permit ip 10.10.60.0 255.255.255.0 10.10.60.0 255.255.255.0
        Transform-sets: 3des-md5,
        Security Association Lifetime: 450 gigabytes/3600 seconds
        PFS (Y/N): N
Interface using crypto map set cm60:
    GigabitEthernet1/2
Crypto Map "cm100" 1 ipsec
        Peer = 10.10.100.221
        IP ACL = aclmds100
            permit ip 10.10.100.231 255.255.255.255 10.10.100.221 255.255.255.255
        Transform-sets: 3des-md5, 3des-sha, des-md5, des-sha,
        Security Association Lifetime: 450 gigabytes/3600 seconds
        PFS (Y/N): N
Crypto Map "cm100" 2 ipsec
        Peer = Auto Peer
        IP ACL = acl100
            permit ip 10.10.100.0 255.255.255.0 10.10.100.0 255.255.255.0
        Transform-sets: 3des-md5, 3des-sha, des-md5, des-sha,
        Security Association Lifetime: 450 gigabytes/3600 seconds
        PFS (Y/N): N

show crypto sad domain ipsec

To display IPsec security association database information, use the show crypto sad domain ipsec command.

show crypto sad domain ipsec [interface gigabitethernet slot / port [ {inbound | outbound} sa-index index]]

Syntax Description

interface gigabitethernet slot /port

(Optional) Displays IPsec security association information for a specific Gigabit Ethernet interface.

inbound

(Optional) Specifies the inbound association.

outbound

(Optional) Specifies the outbound association.

sa-index index

(Optional) Specifies the security association index. The range is 0 to 2147483647.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(x)

This command was introduced.

Usage Guidelines

To use this command, IPsec must be enabled using the crypto ipsec enable command.

Examples

The following example shows how to display IPsec security association information:


switch# show crypto sad domain ipsec
interface: GigabitEthernet4/1
    Crypto map tag: cm10, local addr. 10.10.10.1
    protected network:
    local ident (addr/mask): (10.10.10.0/255.255.255.0)
    remote ident (addr/mask): (10.10.10.4/255.255.255.255)
    current_peer: 10.10.10.4
      local crypto endpt.: 10.10.10.1, remote crypto endpt.: 10.10.10.4
      mode: tunnel, crypto algo: esp-3des, auth algo: esp-md5-hmac
    current outbound spi: 0x30e000f (51249167), index: 0
      lifetimes in seconds:: 120
      lifetimes in bytes:: 423624704
    current inbound spi: 0x30e0000 (51249152), index: 0
      lifetimes in seconds:: 120
      lifetimes in bytes:: 423624704

show crypto spd domain ipsec

To display the security policy database (SPD), use the show crypto spd domain ipsec command.

show crypto spd domain ipsec [interface gigabitethernet slot / port [policy number]]

Syntax Description

interface gigabitethernet slot /port

(Optional) Displays SPD information for a specific Gigabit Ethernet interface.

policy number

(Optional) Specifies a SPD policy number.

Command Default

Displays all SPD information.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(x)

This command was introduced.

Usage Guidelines

To use this command, IPsec must be enabled using the crypto ipsec enable command.

Examples

The following example shows how to display the SPD:


switch# show crypto spd domain ipsec
Policy Database for interface: GigabitEthernet1/1, direction: Both
#   0:      deny  udp any port eq 500 any
#   1:      deny  udp any any port eq 500
#   2:      permit ip any any
#  63:      deny  ip any any
Policy Database for interface: GigabitEthernet1/2, direction: Both
#   0:      deny  udp any port eq 500 any
#   1:      deny  udp any any port eq 500
#   3:      permit ip 10.10.50.1 255.255.255.255 10.10.50.2 255.255.255.255
#   4:      permit ip 10.10.51.1 255.255.255.255 10.10.51.2 255.255.255.255
#  63:      deny  ip any any

show crypto ssh-auth-map

To display mapping filters applied for SSH authentication, use the show crypto ssh-auth-map command.

show crypto ssh-auth-map

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command Default

None.

Command History

Release

Modification

NX-OS 5.0(1a)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display mapping filters applied for SSH authentication:


switch# show crypto ssh-auth-map
Issuer Name: /DCBU
Map1: map1
Map2: map2
switch#

show crypto transform-set domain ipsec

To display transform set information for IPsec, use the show crypto transform-set domain ipsec command.

show crypto transform-set domain ipsec [set-name]

Syntax Description

set-name

(Optional) Specifies the transform set name. Maximum length is 63 characters.

Command Default

Displays information for all transform sets.

Command Modes


EXEC mode.

Command History

Release

Modification

2.0(x)

This command was introduced.

Usage Guidelines

To use this command, IPsec must be enabled using the crypto ipsec enable command.

Examples

The following example shows how to display information for all IPsec transform sets:


switch# show crypto transform-set domain ipsec
Transform set: ipsec_default_transform_set {esp-aes-256-ctr esp-aes-xcbc-mac}
    will negotiate {tunnel}

show debug

To display all Cisco SME related debug commands configured on the switch, use the show debug command.

show debug {cluster {bypass | sap sap bypass} | sme bypass}

Syntax Description

cluster

Displays all the debugging flags.

bypass

Displays the bypass flags.

sap sap

Displays all debugging flags of SAP. Specifies the SAP in the range from 1 to 65535.

sme

Displays all the debugging flags of Cisco SME.

bypass

Displays all the bypass flags of Cisco SME.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.2(2c)

This command was introduced.

NX-OS 4.1(1c)

Added the syntax description.

Usage Guidelines

None.

Examples

The following example shows all debug commands configured on the switch:


switch# show debug
ILC helper:
 ILC_HELPER errors debugging is on
 ILC_HELPER info debugging is on

show debug logfile

To display the debug messages that are saved in the debug log file, use the show debug logfile command.

show debug logfile filename

Syntax Description

filename

Specifies the debug log file name. Maximum length is 80 characters.

Command Default

None.

Command Modes


EXEC mode.

This command was introduced in Cisco MDS SAN-OS Release 1.0(2).

Usage Guidelines

None.

Examples

The following example displays the debug messages in the specified debug log file.


switch# show debug logfile SampleFile
2004 Jun 28 00:14:17 snmpd[2463]: header_fspfLinkEntry : Sending GETNEXT request
 for fspfLsrTable for vsanIndex  =0,fspfLsrDomainId = 0, fspfLsrType = 0
2004 Jun 28 00:14:17 snmpd[2463]: header_fspfLinkEntry : Sending GETNEXT request
 for fspfLsrTable for vsanIndex  =0,fspfLsrDomainId = 0, fspfLsrType = 0
2004 Jun 28 00:14:17 snmpd[2463]: header_fspfLinkEntry : Recd rsp for GETNEXT fo
r entry (vsanIndex=1,fspfLsrDomainId = 10, fspfLsrType=0, fspfLinkIndex = 1,fspf
LinkNbrDomainId = 84, fspfLinkPortIndex = 67331,fspfLinkNbrPortIndex = 66064, fs
pfLinkType = 1,fspfLinkCost = 500
2004 Jun 28 00:14:17 snmpd[2463]: header_fspfLinkEntry : Sending GETNEXT request
 for fspfLsrTable for vsanIndex  =1,fspfLsrDomainId = 209, fspfLsrType = 0
2004 Jun 28 00:14:17 snmpd[2463]: header_fspfLinkEntry : Sending GETNEXT request
 for fspfLsrTable for vsanIndex  =16777216,fspfLsrDomainId = 3506438144, fspfLsr
Type = 0
2004 Jun 28 00:14:17 snmpd[2463]: header_fspfLinkEntry : Sending GETNEXT request
 for fspfLsrTable for vsanIndex  =33554432,fspfLsrDomainId = 4009754624, fspfLsr
Type = 16777216

show debug npv

To display the N Port Virtualization (NPV) debug commands configured on the switch, use the show debug npv command.

show debug npv

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows all NPV debug commands configured on the switch:


switch# show debug npv
N_port Virtualizer:
 FC Receive Packets debugging is on
 FC Transmit Packets debugging is on
 FC Receive Packet header debugging is on
 FC Transmit Packet header debugging is on
 MTS Receive Packets debugging is on
 MTS Transmit Packets debugging is on
 MTS Receive Packet header/payload debugging is on
 MTS Transmit Packet header/payload debugging is on
 High Availability debugging is on
 FSM Transitions debugging is on
 Error debugging is on
 Warning debugging is on
 Trace debugging is on
 Trace Detail debugging is on
 Demux debugging is on
 Dequeue debugging is on
 Packets debugging is on
 Database debugging is on
 Timers debugging is on
 External Interface FSM Events debugging is on
 External Interface FSM Errors debugging is on
 External Interface FSM Trace debugging is on
 FLOGI FSM Events debugging is on
 FLOGI FSM Errors debugging is on
 FLOGI FSM Trace debugging is on
 Server Interface FSM Events debugging is on
 Server Interface FSM Errors debugging is on
 Server Interface FSM Trace debugging is on
 Events debugging is on

show debug sme

To display all Cisco SME related debug commands configured on the switch, use the show debug command.

show debug {cluster {bypass | sap sap} | sme bypass}

Syntax Description

cluster

Displays all the debugging flags.

bypass

Displays the bypass flags.

sap sap

Displays all debugging flags of SAP. Specifies the SAP in the range from 1 to 65535.

sme

Displays all the debugging flags of Cisco SME.

bypass

Displays all the bypass flags of Cisco SME.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

3.2(2)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows all debug commands configured on the switch:


switch# show debug
ILC helper:
 ILC_HELPER errors debugging is on
 ILC_HELPER info debugging is on

show device-alias

To display the device name information, use the show device-alias command.

show device-alias {database [pending | pending-diff] | name device-name [pending] | pwwn pwwn-id [pending] | session {rejected | status} | statistics | status}

Syntax Description

database

Displays the entire device name database.

pending

(Optional) Displays the pending device name database information.

pending-diff

(Optional) Displays pending differences in the device name database information.

name device-name

Displays device name database information for a specific device name.

pwwn pwwn-id

Displays device name database information for a specific pWWN. The format is hh : hh : hh : hh : hh : hh : hh : hh , where h is a hexadecimal number.

session

Displays the session information.

rejected

Display the rejected command list.

status

Displays the device-alias session status.

statistics

Displays device name database statistics.

status

Displays the device name database status.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(9)

Added the rejected keyword to the syntax description.

2.0(x)

This command was introduced.

Usage Guidelines

To make use of fcaliases as device names instead of using the cryptic device name, add only one member per fcalias.

The device-alias configuration best practice has been described in the configuration guide.

Examples

The following example shows the set of rejected device-alias commands in a session:


switch(config-device-alias-db)# show device-alias session rejected
To avoid command rejections, within a device alias session
Do not reuse:
a) a device alias name while configuring a rename command
b) a PWWN while configuring an add or delete command
c) a device alias name already renamed while configuring add command
Rejected commands must be committed in a separate device alias session
which may cause traffic interruption for those devices. Plan accordingly.
Refer to this command in the NX-OS Command Reference Guide
for more information about device alias configuration best practices

Rejected Command List
---------------------
device-alias name Dev1 pwwn 01:01:01:01:02:02:02:02
device-alias name Dev20 pwwn 01:01:01:01:02:02:02:02
switch(config-device-alias-db)#         

The following examples shows the device-alias session status:


switch(config)# show device-alias session status
Last Action Time Stamp     : Tue Jul  1 01:54:21 2014
Last Action                : Commit
Last Action Result         : Success
Last Action Failure Reason : none
switch(config)# 

The following example shows how to display the contents of the device alias database:


switch# show device-alias database
device-alias name efg pwwn 21:00:00:20:37:9c:48:e5
device-alias name fred pwwn 10:00:00:00:c9:2d:5a:de
device-alias name myalias pwwn 21:21:21:21:21:21:21:21
device-alias name test pwwn 21:00:00:20:37:6f:db:bb
device-alias name test2 pwwn 21:00:00:20:37:a6:be:35
Total number of entries = 5

The following example shows how to display all global fcaliases and all VSAN dependent fcaliases:


switch# show device-alias name efg
device-alias name efg pwwn 21:00:00:20:37:9c:48:e5

The following example shows how to display all global fcaliases and all VSAN dependent fcaliases:


switch# show device-alias statistics
        Device Alias Statistics
===========================================
Lock requests sent: 1
Database update requests sent: 1
Unlock requests sent: 1
Lock requests received: 0
Database update requests received: 0
Unlock requests received: 0
Lock rejects sent: 0
Database update rejects sent: 0
Unlock rejects sent: 0
Lock rejects received: 0
Database update rejects received: 0
Unlock rejects received: 0
Merge requests received: 5
Merge request rejects sent: 0
Merge responses received: 0
Merge response rejects sent: 0
Activation requests received: 5
Activation request rejects sent: 0
Activation requests sent: 0
Activation request rejects received: 0
v_226# pwwn 21:00:00:20:37:6f:dc:0e

show device-alias status

To view the current device alias mode setting, use the device-alias status command.

show device-alias status

Syntax Description

This command has no arguments or keywords.

Command Default

Basic mode.

Command Modes


EXEC mode.

Command History

Release

Modification

3.1(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the device alias status:


switch# show device-alias status
Fabric Distribution: Enabled
Database:- Device Aliases 0 Mode: Basic
Locked By:- User "admin" SWWN 20:00:00:0d:ec:30:90:40
Pending Database:- Device Aliases 0 Mode: Basic

show diagnostic bootup level

To display the diagnostic bootup level information (bypass or complete) that is currently in place on the device, use the show diagnostic bootup level command.

show diagnostic bootup level

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the diagnostic bootup level information (bypass or complete) that is currently in place on the device:


switch# show diagnostic bootup level
Current bootup diagnostic level: complete
switch#

show diagnostic content module

To display information about diagnostic test content for a module, use the show diagnostic content module command.

show diagnostic content module {module-number | all}

Syntax Description

module-number

Displays the module number. The range is from 1 to 10.

all

Displays all module ID.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display information about diagnostic test content for a module:


switch# show diagnostic content module 1
Module 1: 2/4/8/10/16 Gbps Advanced FC Module  
Diagnostics test suite attributes: 
B/C/* - Bypass bootup level test / Complete bootup level test
 / NA 
P/*   - Per port test / NA 
M/S/* - Only applicable to active / standby unit / NA 
D/N/* - Disruptive test / Non-disruptive test / NA 
H/O/* - Always enabled monitoring test / Conditionally enable
d test / NA 
F/*   - Fixed monitoring interval test / NA 
X/*   - Not a health monitoring test / NA 
E/*   - Sup to line card test / NA 
L/*   - Exclusively run this test / NA 
T/*   - Not an ondemand test / NA 
A/I/* - Monitoring is active / Monitoring is inactive / NA 
switch#

show diagnostic description module

To display the diagnostic test description for a module, use the show diagnostic description module command.

show diagnostic description module module-number test [test-id test-name | all]

Syntax Description

module-number

Displays the module number. The range is from 1 to 10.

test

Displays the diagnostic test selection.

test-id

Displays the diagnostic test ID.

test-name

Displays the test name.

all

Displays all test ID.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the diagnostic test description for a module:


switch# show diagnostic description module 1 test all
ASICRegisterCheck :
        A health monitoring test,enabled by default that chec
ks read/write
        access to scratch registers on ASICs on the module.
PrimaryBootROM :
        A health monitoring test that verifies the primary Bo
otROM
        state.
SecondaryBootROM :
        A health monitoring test that verifies the secondary 
BootROM
        state.
EOBCPortLoopback :
switch#

show diagnostic events

To display the diagnostic events by error and information event type, use the show diagnostic events command.

show diagnostic events [error | info]

Syntax Description

error

Displays the error event type.

info

Displays the information event type.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the diagnostic events by error event type:


switch# show diagnostic events error
switch#

show diagnostic isl result interface

To display the results of a Single Hop or Multihop Traffic Test on Cisco MDS 9700 Series Switches, use the show diagnostic isl result interface command.

show diagnostic isl result interface interface id

Syntax Description

interface id

Specifies the slot and port of an interface.

Command Default

None

Command Modes

Previleged EXEC mode

Command History

Release Modification
8.3(1)

This command was introduced.

Examples

This example shows the results of a Single Hop Traffic Test:

switch# show  diagnostic isl result interface fc 5/3
---------------------------------------------------------
 Single hop  Traffic test Result for port: fc5/3
Packets Transmitted:                             30621868
Packets Recieved:                                30621868
ISL traffic Efficiency (percent):                100.0000
---------------------------------------------------------

show diagnostic isl status

To display the status of configured Inter-Switch Link (ISL) diagnostic tests per port, use the show diagnostic isl status command.

show diagnostic isl status index start index num number

Syntax Description

index Index of an ISL diagnostic port status.

start index

Index number of an ISL diagnostic port status.

num number

Number of entries of an ISL diagnostic port status array.

Command Default

None

Command Modes


User EXEC (#)
Privileged EXEC (#)

Command History

Release

Modification

8.1(1)

This command was introduced.

Examples

This example displays ISL diagnostic tests for the port fc2/2:


switch# show diagnostic isl status index start 1 num 1
Status of isl_daig tests in progress:
----------------------------------------------------------
Index  Interface        Mode <Gen/Ref>          Test
----------------------------------------------------------

 1      fc2/2           Generator        MH Traffic Test
----------------------------------------------------------

show diagnostic ondemand setting

To display the information about on demand diagnostic settings, use the show diagnostic ondemand setting command.

show diagnostic ondemand setting

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the information about on demand diagnostic settings:


switch# show diagnostic ondemand setting
Test iterations = 1
        Action on test failure = continue until test failure 
limit reaches 1
switch#
switch#

show diagnostic result interface fc test link-diag

To display the results of the link diagnostics tests that are performed on a diagnostic port and to check the host bus adapter (HBA) capability, use the show diagnostic result interface fc test link-diag command.

show diagnostic result interface fc slot/port test link-diag [peer-capability]

Syntax Description

slot/port

Slot and the port numbers of the Fibre Channel interface.

peer-capability

Displays the link diagnostics capabilities of the peer device.

Command Default

None

Command Modes

Previleged EXEC mode

Command History

Release Modification
8.2(1)

This command was introduced.

Usage Guidelines

Examples

The following command output displays the results of the link diagnostics tests that are performed on a diagnostic port:

switch# show diagnostic result interface fc7/28 test link-diag
PWWN of peer port: 21:00:00:24:ff:17:09:ac
Status: Supported (Reflector)
Reflector loopback capabilities:  Xcvr-optical Electrical
Time of Test: Thu Sep 14 00:20:11 2017
Total time taken: 30 seconds
===================|=================|=================|===========================|==================|=================
                   |                 |                 |     Discards              |    Latency (ns)  |
Loopback Level     |    Tx Frames    |    Rx Frames    |  IN    |  OUT   |BAD WORDS|In-Switch|External|    Status
===================|=================|=================|========|========|=========|=========|========|=================
Remote-Switched(R) |                0|                0|       0|       0|        0|        0|       0|       -NA-
Mac(R)             |                0|                0|       0|       0|        0|        0|       0|       -NA-
Xcvr-optical(R)    |          1000000|          1000000|       0|       0|        0|     2136|     632|    Success
Electrical(R)      |            20000|            20000|            -NA-           |     -NA-|    -NA-|    Success
========================================================================================================================
 
Overall Status                          : Success
Cable Length (approx. +/- 5 metres)     : 38.2 metres

Examples

The following command output displays the result of the terminated tests on a diagnostic port:

switch# show diagnostic result interface fc1/23 test link-diag
PWWN of peer port: 10:00:00:90:fa:c7:e1:e9
Status: Supported (Reflector)
Reflector loopback capabilities:  Remote-switched MAC Xcvr-optical
Time of Test: Wed Sep 20 12:54:59 2017
Total time taken: 10 seconds
===================|=================|=================|===========================|==================|=================
                   |                 |                 |     Discards              |    Latency (ns)  |
Loopback Level     |    Tx Frames    |    Rx Frames    |  IN    |  OUT   |BAD WORDS|In-Switch|External|    Status
===================|=================|=================|========|========|=========|=========|========|=================
Remote-Switched(R) |                0|                0|       0|       0|        0|        0|       0|       -NA-
Mac(R)             |                0|                0|       0|       0|        0|        0|       0|       -NA-
Xcvr-optical(R)    |              439|              439|            -NA-           |        0|       0|    Stopped
Electrical(R)      |                0|                0|       0|       0|        0|        0|       0|       -NA-
========================================================================================================================

Overall Status                          : User Stop/Module Reload/PortDown/ELS error
                                          [DIAG TEST STOPPED]
Cable Length (approx. +/- 5 metres)     : -NA-

Examples

The following command output displays the link diagnostics capabilities of the peer device:

switch# show diagnostic result interface fc1/1 test link-diag peer-capability
pWWN of Peer Port: 10:23:34:90:fa:cd:16:6c
Status: Supported (Reflector)
Reflector loopback capabilities: Remote-switched MAC Xcvr-optical


show diagnostic result module

To display the information about the diagnostic test result for a module, use the show diagnostic result module command.

show diagnostic result module module-number all [detail | statistics | test]

Syntax Description

module-number

Displays the module number. The range is from 1 to 10.

detail

(Optional) Displays the detailed result.

statistics

Displays the statistics result.

test

Displays the diagnostic test selection.

all

Displays all test ID.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the detailed information about the diagnostic test result for a module:


switch# show diagnostic result module 1 detail 
Current bootup diagnostic level: complete
Module 1: 2/4/8/10/16 Gbps Advanced FC Module  
  Diagnostic level at card bootup: complete
        Test results: (. = Pass, F = Fail, I = Incomplete,
        U = Untested, A = Abort, E = Error disabled)
        _____________________________________________________
_________________
        1) ASICRegisterCheck .
                Error code ------------------> DIAG TEST SUCC
ESS
                Total run count -------------> 23
                Last test execution time ----> Fri Jun 26 21:
25:33 2009
                First test failure time ----->  n/a
                Last test failure time ------>  n/a
--More--
switch#

show diagnostic simulation module

To display the information about a simulated diagnostic result for a module, use the show diagnostic simulation module command.

show diagnostic simulation module module-number

Syntax Description

module-number

Displays the module number. The range is from 1 to 10.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the information about a simulated diagnostic result for a module:


switch# show diagnostic simulation module 1
Card(1): 2/4/8/10/16 Gbps Advanced FC Module
__________________________________________________
    -NA-    
switch# 

show diagnostic status module

To display test status for a module, use the show diagnostic status module command.

show diagnostic status module module-number

Syntax Description

module-number

Displays the module number. The range is from 1 to 10.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to displays test status for a module:


switch# show diagnostic status module 1
<BU>-Bootup Diagnostics, <HM>-Health Monitori
ng Diagnostics
                <OD>-OnDemand Diagnostics, <SCH>-Scheduled Di
agnostics
==============================================
Card:(1) 2/4/8/10/16 Gbps Advanced FC Module
==============================================
Current running test               Run by
    -NA-                           -NA-
Currently Enqueued Test            Run by
    -NA-                           -NA-
indapex-03# 
switch#
switch#

show diagnostic status module

To display the test status for all tests on a module, use the show diagnostic status module command.

show diagnostic status module module-number

Syntax Description

module-number

Displays the module number. The range is from 1 to 10.

Command Default

None.

Command Modes


EXEC mode.

Command History

Release

Modification

6.2(1)

This command was introduced.

Usage Guidelines

None.

Examples

The following example shows how to display the test status for all tests on a module:


switch# show diagnostic status module 1
<BU>-Bootup Diagnostics, <HM>-Health Monitori
ng Diagnostics
                <OD>-OnDemand Diagnostics, <SCH>-Scheduled Di
agnostics
==============================================
Card:(1) 2/4/8/10/16 Gbps Advanced FC Module
==============================================
Current running test               Run by
    -NA-                           -NA-
Currently Enqueued Test            Run by
    -NA-                           -NA-
switch# 

show diagnostic test link-diag status

To check the status of the link diagnostics tests that are running on all the ports in a switch, use the show diagnostic test link-diag status command

show diagnostic test link-diag status

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Previleged EXEC mode

Command History

Release Modification

8.2(1)

This command was introduced.

Examples

The following command output displays the status of the link diagnostics tests that are performed on a diagnostic port:

switch# show diagnostic test link-diag status
---------------------------------------------------------------------------------------------------------------------
Index  Diag-Interface    Gen-Interface    Link-diag Status
----------------------------------------------------------------------------------------------------------------------
                                          Remote-Switched(R)      MAC(R)          Electrical(R)    Xcvr-optical(R)
----------------------------------------------------------------------------------------------------------------------
1       fc1/23            fc1/9               NA               Success               NA               Running