The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Book Contents Book Contents Find Matches in This Book Log in to Save Content Available Languages Download OptionsCisco MDS 9000 Series Command Reference, Release 9.x
To configure the required mode to initiate an IP connection, use the passive-mode command. To enable passive mode for the FCIP interface, use the no form of the command.
This command has no keywords or arguments.
Interface configuration submode.
This command was introduced.
Access this command from the switch(config-if)# submode.
By default, the active mode is enabled to actively attempt an IP connection.
If you enable the passive mode, the switch does not initiate a TCP connection and only waits for the peer to connect to it.
The following example enables passive mode on an FCIP interface:
switch# config terminal switch(config)# interface fcip 1 switch(config-if)# passive-mode
show interface fcip
Displays an interface configuration for a specified FCIP interface.
To enable password strength checking, use the password strength-check command. To disable this feature, use the no form of the command.
no password strength-check
This command has no arguments or keywords.
This command was introduced.
When you enable password strength checking, the NX-OS software only allows you to create strong passwords.
The characteristics for strong passwords included the following:
The following are examples of strong passwords:
The following example shows how to enable secure standard password:
switch(config)# password strength-check switch(config)#
show password strength-check
Displays if the password strength check is enabled.
To add a sensor to a sensor group, use the path command. To remove the sensor, use the no form of this command.
path analytics: query
path transceiver: range
path transceiver_peer: range
path show_stats_ range
no path analytics: query
no path transceiver: range
no path transceiver_peer: range
no path show_stats_ range
analytics
Data traffic analytics information.
A user defined analytics query name.
transceiver
Local transceiver diagnostic information.
A single FC interface or continuous range of FC interfaces separated by '-'.
transceiver_peer
Local and remote transceiver diagnostic information.
A single FC interface or continuous range of FC interfaces separated by '-'.
show_stats_range
Interface counter information. range is a single FC interface or a continuous range of FC interfaces separated by '-'.
No sensor paths are configured.
Telemetry sensor configuration mode (conf-tm-sensor)
Added transceiver and transceiver_peer options.
This command was introduced.
The distinguished name of a sensor is followed by the parameters for the sensor. Not all sensors have parameters.
Multiple sensors may be added to a sensor group. This allows discontiguous interface ranges to be defined in a single sensor group.
When using the transceiver_peer sensor, ensure that the peer devices in the specified interface range support FC Read Diagnostic Parameters (RDP) ELS requests. RDP allows the switch to collect peer port diagnostic information over the link to the peer. To determine if a peer device supports RDP, execute the show rdp fcid fcid vsan vsan command. If an interface rejects the RDP ELS command, the interface will be marked as not supporting it and will not be sent the RDP ELS again until the next time the interface comes up. In this case the streamed data will not include the remote transceiver data.
This example shows how to add interface counters for fc3/1 to a sensor group:
switch# configure switch(config)# telemetry switch(config-telemetry)# sensor-group 1 switch(conf-tm-sensor)# path show_stats_fc3/1
This example shows how to remove an analytics query from a sensor group:
switch# configure switch(config)# telemetry switch(config-telemetry)# sensor-group 2 switch(conf-tm-sensor)# no path analytics:init
This example shows how to create a subscription that streams local transceiver data from Fibre Channel interface 1/1 through 1/5 every 10 minutes to IP 192.0.2.1 port 50003:
switch# configure switch(config)# telemetry switch(config-telemetry)# sensor-group 3 switch(conf-tm-sensor)# path transceiver:fc1/1-5 switch(conf-tm-sensor)# destination group 1 switch(conf-tm-dest)# ip address 192.0.2.1 port 50003 protocol gRPC encoding GPB-compact subscription 1 switch(conf-tm-sub)# snr-grp 1 sample-interval 600000 switch(conf-tm-sub)# dst-grp 1
Configure a user-defined analytics query.
Enable the SAN Analytics feature.
Enables the SAN Telemetry Streaming feature.
Creates a sensor group and enters sensor group configuration.
show running-config telemetry
Displays the existing telemetry configuration.
Displays RDP details of a device.
Displays telemetry runtime information.
Enters SAN Telemetry Streaming configuration mode.
To display per-hop interface information along the paths between 2 devices, use the pathtrace command.
pathtrace < domain id | fcid id >vsan id [ [ reverse ] [ detail ]]
pathtrace < domain id | fcid id >vsan id [ [ reverse ] [ detail ] | [ multipath ]]
Traces the paths to all the edge devices in the domain ID. The range is from 1 to 239.
Specifies the Fibre Channel ID of the destination N-port. The range is from 0x0 to 0xffffff.
Specified the VSAN ID. The range is from 1 to 4094.
(Optional) Displays information about the reverse (or return) path.
(Optional) Displays detailed information about each egress interface at every hop.
(Optional) Displays information about all Equal-Cost Multipath (ECMP) links.
This command was modified. The multipath keyword was added.
This command was introduced.
Depending on the keywords used, Pathtace displays the following information for every egress interface in a path:
The operational speed of an active interface. It represents the capable bandwidth of an inactive interface.
Not displayed for internal interfaces.
The bits transmitted per second.
Not displayed for internal interfaces.
The bits received per second.
Not displayed for internal interfaces.
The number of frames transmitted.
Not displayed for internal interfaces.
The number of frames received.
Not displayed for internal interfaces.
The transmit buffer-to-buffer credit that is remaining.
Not displayed for internal interfaces.
The receive buffer-to-buffer credit that is remaining.
Not displayed for internal interfaces.
The aggregate of ingress and egress errors.
Not displayed for internal interfaces.
The aggregate of ingress and egress frame discards.
Not displayed for internal interfaces.
The Cyclic Redundancy Check (CRC) errors on the incoming frames.
Not displayed for internal interfaces.
An interface’s total transmission waiting time due to nonavailability of transmit buffer-to-buffer credits.
Displays a percentage of transmit wait time for last 1 second, 1 minute, 1 hour, and last 72 hours.
The number of frames dropped due to access control list (ACL) rules.
Displays only for Cisco MDS 9700 48-Port 32-Gbps Fibre Channel Switching Module (DS-X9648-1536K9).
The number of frames dropped due to forwarding information base (FIB) rules.
Displays only for Cisco MDS 9700 48-Port 32-Gbps Fibre Channel Switching Module (DS-X9648-1536K9).
The following example shows how to trace the path between a switch in which the command is executed and an edge device, using the edge device's FCID:
switch# pathtrace fcid 0xca016c vsan 2000 switch# pathtrace fcid 0xca016c vsan 2000 The final destination port type is F_Port ------------------------------------------------------------------------ Hop Domain In-Port Out-Port Speed Cost Switchname ------------------------------------------------------------------------ 0 111 embedded fc1/6 4G 250 switch1 1 202 fc1/6 fc1/1 2G - switch2 NOTE: The stats are displayed for the egress interface only
The following example shows how to trace both the forward path and the return path between a switch in which the command is executed and all the edge devices in domain 83 on the 'sw-fcip69' switch:
switch# pathtrace domain 83 vsan 70 reverse The final destination port type is Embedded ------------------------------------------------------------------------------- Hop Domain In-Port Out-Port Speed Cost Switchname ------------------------------------------------------------------------ 0 144 embedded vfc69(Eth1/8) 10.0G 100 sw-ioa-70 1 83 vfc69(Eth1/1) embedded - - sw-fcip69 2 83 embedded vfc69(Eth1/1) 10.0G 100 sw-fcip69 3 144 vfc69(Eth1/8) embedded - - sw-ioa-70 NOTE: The stats are displayed for the egress interface only
The following example shows how to display detailed information about the interfaces (both the forward path and the return path) between a switch in which the command is executed and an edge device, using the edge device's FCID:
switch# pathtrace fcid 0xca016c vsan 2000 reverse detail The final destination port type is F_Port ------------------------------------------------------------------------------- Hop 0 Domain In-Port Out-Port Speed Cost Switchname 111 embedded fc1/6 4G 250 switch1 ------------------------------------------------------------------------------- Stats for egress port: fc1/6 TxRt(B/s): 2944 RxRt(B/s): 3632 TxB_B: 32 RxB_B: 32 TxFrame: 137467 RxFrame: 137475 Errors: 0 Discard: 0 CRC: 0 ------------------------------------------------------------------------------- Hop 1 Domain In-Port Out-Port Speed Cost Switchname 202 fc1/6 fc1/1 2G - switch2 ------------------------------------------------------------------------------- Stats for egress port: fc1/1 TxRt(B/s): 1424 RxRt(B/s): 1528 TxB_B: 0 RxB_B: 32 TxFrame: 711 RxFrame: 649 Errors: 0 Discard: 15 CRC: 0 ------------------------------------------------------------------------------- Hop 2 Domain In-Port Out-Port Speed Cost Switchname 202 embedded fc1/6 4G 250 switch2 ------------------------------------------------------------------------------- Stats for egress port: fc1/6 TxRt(B/s): 3632 RxRt(B/s): 2952 TxB_B: 32 RxB_B: 32 TxFrame: 137476 RxFrame: 137467 Errors: 0 Discard: 0 CRC: 0 ------------------------------------------------------------------------------- Hop 3 Domain In-Port Out-Port Speed Cost Switchname 111 fc1/6 embedded - - switch1 ------------------------------------------------------------------------------- Stats for egress port: embedded TxRt(B/s): - RxRt(B/s): - TxB_B: - RxB_B: - TxFrame: - RxFrame: - Errors: - Discard: - CRC: - NOTE: The stats are displayed for the egress interface only
The following example shows how to trace the path between a switch in which the pathtrace command is executed and all the edge devices in the specified domain and VSAN:
switch# pathtrace domain 83 vsan 70 The final destination port type is Embedded ------------------------------------------------------------------------------- Hop Domain In-Port Out-Port Speed Cost Switchname ------------------------------------------------------------------------ 0 144 embedded vfc69(Eth1/8) 10.0G 100 sw-ioa-70 1 83 vfc69(Eth1/1) embedded - - sw-fcip69 NOTE: The stats are displayed for the egress interface only
The following example shows how to trace all the links (including equal-cost parallel links) in the paths between all the edge devices in a domain and a switch in which the command is executed for Fibre Channel, FCIP, and vFC respectively:
switch# pathtrace domain 238 vsan 1 multipath ***NOTE *** I - Ingress E - Egress M - Member Port-channel * - Fport . PATH 1 switch1 switch2 Domain 236 235 . --------------------------------------------------------------------------------------------------------------------- HOP 1 switch1(fc1/11)(E)-------(I)(fc1/12)switch2 ---------------------------------------------------------------------------------------------------------------------- Interface Spd(G) Tx(B/s) Rx(B/s) TxB2B RxB2B Errors Discards CRC TxWait(1s/1m/1h/72h) FibDrops ZoneDrops ---------------------------------------------------------------------------------------------------------------------- (E)fc1/11 8.0 84 44 64 64 0 2 0 0%/0%/0%/0% - - (I)fc1/12 8.0 44 84 64 64 0 0 0 0%/0%/0%/0% - - ---------------------------------------------------------------------------------------------------------------------- HOP 2 switch2(fc1/3)(E)*End Device ----------------------------------------------------------------------------------------------------------------------- Interface Spd(G) Tx(B/s) Rx(B/s) TxB2B RxB2B Errors Discards CRC TxWait(1s/1m/1h/72h) FibDrops ZoneDrops ----------------------------------------------------------------------------------------------------------------------- (E)fc1/3 4.0 0 0 16 64 0 0 0 0%/0%/0%/0% - - . PATH 2 switch1 switch2 Domain 236 235 . ----------------------------------------------------------------------------------------------------------------------- HOP 1 switch1(fc1/12)(E)-------(I)(fc1/11)switch2 ----------------------------------------------------------------------------------------------------------------------- Interface Spd(G) Tx(B/s) Rx(B/s) TxB2B RxB2B Errors Discards CRC TxWait(1s/1m/1h/72h) FibDrops ZoneDrops ---------------------------------------------------------------------------------------------------------------------- (E)fc1/12 8.0 64 180 64 64 0 0 0 0%/0%/0%/0% - - (I)fc1/11 8.0 180 64 64 64 0 0 0 0%/0%/0%/0% - - ---------------------------------------------------------------------------------------------------------------------- HOP 2 switch2(fc1/3)(E)*End Device ---------------------------------------------------------------------------------------------------------------------- Interface Spd(G) Tx(B/s) Rx(B/s) TxB2B RxB2B Errors Discards CRC TxWait(1s/1m/1h/72h) FibDrops ZoneDrops ----------------------------------------------------------------------------------------------------------------------- (E)fc1/3 4.0 0 0 16 64 0 0 0 0%/0%/0%/0% - - switch# pathtrace domain 132 vsan 447 multipath ***NOTE *** I - Ingress E - Egress M - Member Port-channel * - Fport . PATH 1 switch1 switch2 Domain 187 132 . ----------------------------------------------------------------------------------------------- HOP 1 switch1(port-channel216)(E)-------(I)(port-channel216)switch2 ----------------------------------------------------------------------------------------------- Interface InputRate(B/s) OutputRate(B/s) InputFrames(/sec) OutputFrames(/sec) ----------------------------------------------------------------------------------------------- (E)port-channel216 3393959 640827945 161838662680576 1375239938244608 (M)fcip50 292049 55048436 3239 27507 (M)fcip51 291539 55052889 3237 27508 (M)fcip52 291702 55080573 3239 27522 (M)fcip53 278265 52552382 3090 26258 (M)fcip54 278291 52561525 3090 26263 (M)fcip55 278346 52559754 3090 26262 (M)fcip65 291647 55073072 3238 27518 (M)fcip66 278491 52584017 3092 26274 (M)fcip67 278362 52571056 3091 26268 (M)fcip86 278290 52554341 3090 26259 (M)fcip87 278426 52587737 3092 26276 (M)fcip88 278551 52602163 3093 26283 (I)port-channel216 640830213 3394016 1375252823146496 161842957647872 (M)fcip50 55058685 292105 27512 3240 (M)fcip51 55080107 291690 27522 3239 (M)fcip52 55097520 291794 27530 3240 (M)fcip53 52559881 278311 26262 3090 (M)fcip54 52570959 278345 26268 3091 (M)fcip55 52571081 278410 26268 3091 (M)fcip65 55051714 291539 27507 3237 (M)fcip66 52564219 278387 26264 3091 (M)fcip67 52562847 278324 26264 3090 (M)fcip86 52564931 278345 26265 3091 (M)fcip87 52571632 278350 26268 3091 (M)fcip88 52576637 278416 26271 3091 switch# pathtrace domain 83 vsan 70 multipath ***NOTE *** I - Ingress E - Egress M - Member Port-channel * - Fport . PATH 1 switch1 switch2 Domain 144 83 . ----------------------------------------------------------------------- HOP 1 switch1(vfc69)(E)-------(I)(vfc69)switch2 --------------------------------------------------------------------------------------- Interface Spd(G) FcoeOut(Oct) FcoeIn(Oct) FcoeOutPkt FcoeInPkt -------------------------------------------------------------------------------------- (E)vfc69 10.0 165604 153648 697 700 (I)vfc69 10.0 153716 166276 701 698
| Term | Description |
|---|---|
| FCIP | |
| InputRate(B/s) | The number of bytes received per second on the in port of an FCIP link. |
| OutputRate(B/s) | The number of bytes received per second on the out port of an FCIP link. |
| InputFrames(/sec) | The number of frames received per second on the in port of an FCIP link. |
| OutputFrames(/sec) | The number of frames received per second on the out port of an FCIP link. |
| vFC | |
| FcoeOut(Oct) | The number of egress FCoE octets on a vFC interface. |
| FcoeIn(Oct) | The number of ingress FCoE octets on a vFC interface. |
| FcoeOutPkt | The number of egress FCoE packets on a vFC interface. |
| FcoeInPkt | The number of ingress FCoE packets on a vFC interface. |