Configuring Interswitch Link Diagnostics

Transcript

1 Configuring Interswitch Diagnostics Link with the Cisco MDS NX-OS Release the Cisco MDS 9700 and 9500 series switches Beginning 7.3(0)D1(1), Link (ISL) Diagnostics the Interswitch This chapter describes how to configure the ISL support feature. on the Cisco MDS 9500 and 9700 Series switches. Diagnostics • Information About ISL Diagnostics , on page 1 ISL Diagnostics • Configuring , on page 10 ISL Diagnostics , on page 19 • Debugging • Additional , on page 21 References Information About ISL Diagnostics ISL Diagnostics feature helps in validating the health of interswitch links between the Cisco MDS switches in a network. ISL Diagnostic Overview is supported on the following ISL diagnostics platforms: • Cisco MDS 9396S Switch • Cisco MDS 9396T Switch • Cisco MDS 9148T Switch • Cisco MDS 9132T Switch ISL diagnostics is supported on the following FC modules of the Cisco MDS Switches: • 16-Gbps on Cisco MDS 9700 Series Switches modules • DS-X9448-768K9 • 32-Gbps modules on Cisco MDS 9700 Series Switches • DS-X9648-1536K9 Configuring Interswitch Link Diagnostics 1

2 Diagnostics Link Interswitch Configuring Test Latency Note The ISL diagnostic on the modules is limited to the generator and reflector ports only. support on modules two supported between tests can be performed • The diagnostic of different switch families either side. using ISL diagnostics: tests can be performed The following test • Latency • Single Hop Traffic Test End-to-End • Multihop Traffic Test FC modules of the Cisco MDS Switches: ISL diagnostics on the following is not supported • DS-X9224-96K9 • DS-X9248-96K9 • DS-X9248-48K9 • DS-X9304-18K9 • DS-X9334-K9 Note switches such as Nexus 2000 and Nexus 5000. • ISL diagnostics are not supported on other non-MDS • ISL diagnostics are not supported on Cisco MDS 9148S 16G Multilayer Fabric Switch and Cisco MDS 9250i Multiservice Fabric Switch. on any of the FCoE and IPS modules • ISL diagnostics of the Cisco MDS Switches. are not supported links. • ISL diagnostics are not supported on FEC-enabled Latency Test two Cisco MDS switches. test measures Latency the latency of an ISL between arecaptured. switchwherethetimestamps Theframeisloopedbackbythereflector switchporttothegenerator ofthelinktobemeasured allowthelatency ofthereflector aswellasthelatency Timestamps inbothdirections of the reported The accuracy using only the link latencies. port. The cable length is calculated cable length is +/- 2 meters. On Cisco MDS switches, the cable length (for latency test) is validated up to 50 meters of the cable length. Note there should When a latency test is executed, not be any other traffic running on the same link. Figure 1: Latency test. Test, on page 3 shows the details for the latency Link Interswitch Configuring Diagnostics 2

3 Diagnostics Link Interswitch Configuring Test Traffic Hop Single Test Figure 1: Latency Test Traffic Hop Single the efficiency the health of an ISL by checking The Single Hop Traffic Test validates of the ISL to handle traffic at various frame rates. are generated traffic generator facility Fibre Channel (FC) frames switch using the internal in the generator from the generator are transmitted in the MAC hardware. available switch port over the ISL These frames the frames, switches them via the normal fabric switching path and under test. The reflector switch receives port onto the ISL under test. the received back through transmits the frames based on the number of packets received back on the generator The efficiency of the ISL traffic is calculated switch port. Note When a single hop test is executed, there should not be any other traffic running on the same link. scenarios: The traffic test returns with an error in the following • If the ISL is not up. • If the generator port does not have an internal traffic generator facility. mode. is not put in a loopback • When the reflector Figure 2: Single Hop Traffic Test, on page 3 shows the details for Single Hop Traffic Test: Figure Test 2: Single Hop Traffic Link Interswitch Configuring Diagnostics 3

4 Diagnostics Link Interswitch Configuring Test Traffic End-to-End Multihop Traffic Test Multihop End-to-End a host switch and a target switch in a fabric. the health of the ISL between test evaluates The Mutlihop a host to a target in a fabric, test the fabric path between connecting Before the host port and the target port, using a Multihop test. is required configuration No specific the host switch and the target switch. hops can exist between Multiple switches. on the intermediate Note switches in the fabric can have any interface FC, FCoE, IPS, and so The intermediate or link, for example, on, between them, as long as a route exists between the generator and the reflector port. at the generator switch port and transmitted to the first hop link. Fibre channel (FC) frames are generated These frames switch then The reflector switch. until they reach the reflector switches intermediate traverse switches the frames and returns them to the generator switch. Based on the number of packets received on switch, the generator the efficiency of the ISL is displayed. The Multihop traffic test is based on the domain IDs of the generator and reflector switches. Note there should not be any other traffic running on both the generator traffic test is executed, When a Multihop traffic and thereflector overtheISLsthatisusedby theMultihop , therecanbe trafficrunning ports;however test. Traffic Traffic Test , on page 4 shows the details for Multihop Figure 3: Multihop End-to-End End-to-End Test: Traffic Test Figure 3: Multihop End-to-End Pathtrace suchasingress toprovide ThePathtrace feature buildsontheTraceroute feature information aboutinterfaces, and errors, at each hop in the frames and received of transmitted names and the number and egress interface in a fabric. Pathtrace view of the shortest path without the provides path between 2 devices an end-to-end need to connect to individual switches and check the Fabric Shortest Path First (FSPF) topology hop by hop. pathtrace is used to trace the path from a switch on which the command Pathtrace is run, to a destination works with the Fibre Channel, feature The Pathtrace domain. in a destination device or all the devices Fibre information Channel over Ethernet (FCoE), and Fibre Channel over IP (FCIP) interfaces. Pathtrace collects paths within the fabric and provides about the available information for devices along the shortest path. interface, cost, speed, and other statistics when used with the source interface, Pathtrace displays destination can also be used to display path information the detail keyword. The pathtrace the reverse command (from Diagnostics Link Interswitch Configuring 4

5 Diagnostics Link Interswitch Configuring for Pathtrace and Limitations Guidelines the device on which destination If the destination cannot be reached, Pathtrace displays back to the source). terminated. the connectivity types of interfaces for various displayed The statistics are: • Fibre Channel are displayed for the associated Fibre Channel interfaces. interface—The statistics interfaces. Ethernet fortheassociated aredisplayed statistics (VFC)interface—The • VirtualFibreChannel statistics for port channels. port channel—The • Fibre Channel are displayed for VFC port channels. • VFC port channel—The statistics are displayed or FCIP port for the FCIP interfaces or FCIP port channel—The are displayed statistics • FCIP interface channels. Guidelines and Limitations for Pathtrace that are operating on Cisco MDS switches is not supported • Pathtrace in the Cisco NPV mode. • Pathtrace does not support interop mode. • Pathtrace is supported only on Cisco MDS switches and not on other vendor switches. (Inter-VSAN [IVR] for Pathtrace). • Pathtrace does not support virtual domains Routing • Pathtrace is not manageable (SNMP). Protocol Management Network via Simple supports of16hopswithout amaximum • Pathtrace option, and8hopswiththereverse option. thereverse are displayed • Statistics only for egress interfaces. for FCIP and FCIP port-channel interfaces are not displayed for devices in the path running • Statistics Cisco MDS NX-OS Release 6.2(5). Pathtrace Multipath feature ThePathtrace feature tocollectanddisplay allEqual-Cost Multi-Path Multipath buildsonthePathtrace information This feature for switches. source and destination between paths and statistics (ECMP) provides individual equal-cost links of a port channel. all the links between the 2 endpoints to be displayed, including for example, can aid in troubleshooting when a single link in a port channel This feature difficult situations, do not. has errors and the remaining Guidelines and Limitations for Pathtrace Multipath on Cisco NPV switches. is not supported • Pathtrace Multipath does not support interop mode. • Pathtrace Multipath switches. • Pathtrace Multipath is supported only on Cisco MDS switches and not on other vendor Multipath). Multipath virtualdomains (Inter-VSAN Routing [IVR]forPathtrace • Pathtrace doesnotsupport • Pathtrace Multipath is not manageable via SNMP. on the number does not have any limitation unlike the endpoints • Pathtrace of hops between Multipath feature. the Pathtrace Link Interswitch Configuring Diagnostics 5

6 Diagnostics Link Interswitch Configuring Multipath or Pathtrace Pathtrace Using is supported on F ports that are connected to Qlogic and Emulex host bus adapters • Pathtrace Multipath (HBAs). Multipath or Pathtrace Pathtrace Using information run this command: along the paths between To display per-hop interface 2 devices, vsan id reverse ] [ detail ] | [ multipath ]] fcid | id id domain { pathtrace switch# } [[ shows how to trace the path between and The following example is executed a switch in which the command an edge device, using the edge device's FCID: fcid 0xca016c switch# 2000 vsan pathtrace The final destination port type is F_Port ------------------------------------------------------------------------ Switchname Cost Out-Port In-Port Hop Domain Speed ------------------------------------------------------------------------ 4G 250 switch1 0 111 embedded fc1/6 - 1 202 fc1/6 fc1/1 2G switch2 only for the egress NOTE: The stats are displayed interface The following a switch in path and the return path between shows how to trace both the forward example is executed which the command using the edge device's FCID: and an edge device, pathtrace switch# reverse 2000 vsan 0xca016c fcid is F_Port The final destination port type ------------------------------------------------------------------------ Switchname Cost Speed Out-Port Hop Domain In-Port ------------------------------------------------------------------------ fc1/6 4G 250 switch1 0 111 embedded 1 202 fc1/6 fc1/1 2G - switch2 fc1/6 2 202 250 switch2 embedded 4G switch1 - - embedded fc1/6 3 111 are displayed for the egress NOTE: only The stats interface example path (boththeforward abouttheinterfaces information detailed Thefollowing showshowtodisplay and an edge device, and the return path) between is executed using the edge a switch in which the command FCID: device's pathtrace fcid 0xca016c vsan 2000 reverse detail switch# is F_Port type port destination The final ------------------------------------------------------------------------------- Speed Out-Port Cost Switchname In-Port Domain Hop 0 fc1/6 4G 250 switch1 111 embedded ------------------------------------------------------------------------------- for egress Stats port: fc1/6 TxRt(B/s): 2944 3632 RxRt(B/s): 32 TxB_B: 32 RxB_B: 137467 TxFrame: RxFrame: 137475 0 Errors: Discard: 0 0 CRC: ------------------------------------------------------------------------------- Domain In-Port Out-Port Speed Cost Switchname Hop 1 switch2 fc1/1 202 fc1/6 2G - Diagnostics Configuring Interswitch Link 6

7 Diagnostics Link Interswitch Configuring Multipath or Pathtrace Pathtrace Using ------------------------------------------------------------------------------- fc1/1 port: for egress Stats 1424 TxRt(B/s): 1528 RxRt(B/s): 0 TxB_B: 32 RxB_B: 711 TxFrame: 649 RxFrame: 0 Errors: 15 Discard: 0 CRC: ------------------------------------------------------------------------------- Speed Out-Port In-Port Switchname Domain Hop 2 Cost fc1/6 202 4G 250 embedded switch2 ------------------------------------------------------------------------------- fc1/6 for egress port: Stats TxRt(B/s): 3632 2952 RxRt(B/s): TxB_B: 32 32 RxB_B: 137476 TxFrame: 137467 RxFrame: 0 Errors: Discard: 0 CRC: 0 ------------------------------------------------------------------------------- Speed Switchname Hop 3 Domain In-Port Out-Port Cost embedded 111 fc1/6 switch1 - - ------------------------------------------------------------------------------- for egress port: embedded Stats TxRt(B/s): - - RxRt(B/s): - TxB_B: - RxB_B: TxFrame: - - RxFrame: Errors: - Discard: - CRC: - interface NOTE: The stats are displayed for the egress only links) in the paths parallel equal-cost shows how to trace all the links (including example The following in a domain between and a switch in which the command all the edge devices is executed: domain 1 multipath switch# pathtrace 238 vsan *** ***NOTE I - Ingress E - Egress Port-channel M - Member * - Fport ... PATH 1 switch1 switch2 235 236 Domain ... ----------------------------------------------------------------------- HOP 1 switch1(fc1/11)(E)-------(I)(fc1/12)switch2 ---------------------------------------------------------------------------------------------------------------------- CRC Interface Spd(G) Tx(B/s) Rx(B/s) TxB2B RxB2B Errors Discards ZoneDrops TxWait(1s/1m/1h/72h) FibDrops ---------------------------------------------------------------------------------------------------------------------- 0 0%/0%/0%/0% 64 0 2 (E)fc1/11 8.0 84 44 64 - - 0 0%/0%/0%/0% 0 0 (I)fc1/12 8.0 64 64 84 44 Diagnostics Link Interswitch Configuring 7

8 Diagnostics Link Interswitch Configuring Multipath or Pathtrace Pathtrace Using - - ---------------------------------------------------------------------------------------------------------------------- Device HOP 2 switch2(fc1/3)(E)*End ----------------------------------------------------------------------------------------------------------------------- TxB2B Interface Tx(B/s) Discards CRC Spd(G) RxB2B Rx(B/s) Errors ZoneDrops FibDrops TxWait(1s/1m/1h/72h) ----------------------------------------------------------------------------------------------------------------------- 64 4.0 (E)fc1/3 0 0 0%/0%/0%/0% 0 0 16 0 - - ... PATH switch2 2 switch1 235 236 Domain ... ----------------------------------------------------------------------------------------------------------------------- HOP 1 switch1(fc1/12)(E)-------(I)(fc1/11)switch2 ----------------------------------------------------------------------------------------------------------------------- Spd(G) Tx(B/s) Rx(B/s) TxB2B RxB2B Errors Discards CRC Interface ZoneDrops TxWait(1s/1m/1h/72h) FibDrops ---------------------------------------------------------------------------------------------------------------------- (E)fc1/12 8.0 64 180 64 64 0 0 0 0%/0%/0%/0% - - 0%/0%/0%/0% 0 0 (I)fc1/11 8.0 180 64 64 64 0 - - ---------------------------------------------------------------------------------------------------------------------- Device HOP 2 switch2(fc1/3)(E)*End ---------------------------------------------------------------------------------------------------------------------- Rx(B/s) RxB2B Tx(B/s) TxB2B Spd(G) Interface Discards CRC Errors ZoneDrops FibDrops TxWait(1s/1m/1h/72h) ----------------------------------------------------------------------------------------------------------------------- 0 0%/0%/0%/0% 4.0 0 0 16 (E)fc1/3 0 0 64 - - multipath switch# pathtrace domain 132 vsan 447 *** ***NOTE I - Ingress E - Egress Port-channel M - Member * - Fport ... PATH 1 switch1 switch2 Domain 187 132 ... ----------------------------------------------------------------------------------------------- HOP 1 switch1(port-channel216)(E)-------(I)(port-channel216)switch2 ----------------------------------------------------------------------------------------------- InputRate(B/s) Interface InputFrames(/sec) OutputRate(B/s) OutputFrames(/sec) ----------------------------------------------------------------------------------------------- 1375239938244608 (E)port-channel216 3393959 640827945 161838662680576 27507 3239 292049 (M)fcip50 55048436 3237 27508 (M)fcip51 291539 55052889 3239 (M)fcip52 291702 55080573 27522 3090 (M)fcip53 278265 52552382 26258 (M)fcip54 278291 52561525 3090 26263 3090 52559754 26262 278346 (M)fcip55 3238 27518 (M)fcip65 291647 55073072 Link Interswitch Configuring Diagnostics 8

9 Diagnostics Link Interswitch Configuring Multipath or Pathtrace Pathtrace Using 26274 (M)fcip66 52584017 3092 278491 26268 3091 52571056 278362 (M)fcip67 3090 278290 26259 (M)fcip86 52554341 26276 3092 52587737 278426 (M)fcip87 26283 52602163 278551 (M)fcip88 3093 640830213 3394016 1375252823146496 161842957647872 (I)port-channel216 3240 (M)fcip50 27512 292105 55058685 55080107 291690 27522 3239 (M)fcip51 3240 27530 291794 55097520 (M)fcip52 3090 (M)fcip53 52559881 278311 26262 52570959 (M)fcip54 278345 26268 3091 3091 (M)fcip55 52571081 278410 26268 (M)fcip65 3237 27507 291539 55051714 26264 278387 52564219 (M)fcip66 3091 26264 3090 (M)fcip67 52562847 278324 3091 (M)fcip86 52564931 278345 26265 26268 (M)fcip87 52571632 278350 3091 3091 26271 278416 52576637 (M)fcip88 83 vsan switch# pathtrace 70 multipath domain *** ***NOTE I - Ingress E - Egress M - Member Port-channel * - Fport ... switch2 PATH 1 switch1 Domain 144 83 ... ----------------------------------------------------------------------- switch1(vfc69)(E)-------(I)(vfc69)switch2 HOP 1 --------------------------------------------------------------------------------------- FcoeIn(Oct) FcoeOutPkt Interface Spd(G) FcoeOut(Oct) FcoeInPkt -------------------------------------------------------------------------------------- (E)vfc69 10.0 165604 700 697 153648 166276 10.0 701 698 (I)vfc69 153716 Link Interswitch Configuring Diagnostics 9

10 Diagnostics Link Interswitch Configuring ISL Diagnostics Configuring Note indicates that the respective port is an HBA interface on an edge device. • In the output, embedded table: in the following are defined outputs used in the multipath • Some of the terminologies 1: Multipath Terminologies Table Term Description FCIP on the in per second of bytes received The number InputRate(B/s) port of an FCIP link. of bytes received The number OutputRate(B/s) on the per second out port of an FCIP link. of frames The number InputFrames(/sec) received per second on the in port of an FCIP link. received per second on the The number OutputFrames(/sec) of frames out port of an FCIP link. vFC The number of egress FCoE octets on a vFC FcoeOut(Oct) interface. The number of ingress FcoeIn(Oct) FCoE octets on a vFC interface. The number FcoeOutPkt of egress FCoE packets on a vFC interface. FcoeInPkt of ingress The number FCoE packets on a vFC interface. ISL Diagnostics Configuring Test on Cisco Latency Configuring MDS 9700 Switches Series perform tasks: switches and reflector the generator test between the latency To configure the following Procedure latency by setting it to loopback mode using the 1 Enable the test interface Step switch for testing on the reflector command: following Diagnostics Link Interswitch Configuring 10

11 Diagnostics Link Interswitch Configuring Platforms Supported Test on Other Latency Configuring switch B# isl reflector latency_test loop-back interface interface id enable diagnostic the results: switch to run the test and display the generator Configure 2 Step interface interface switch A# diagnostic isl latency-test id switch: command the following configure testing port for latency the reflector To disable 3 Step on the reflector loop-back id disable diagnostic isl reflector latency_test switch B# interface interface Test Latency switch for latency shows how to enable a port on a reflector testing: This example diagnostic isl reflector latency_test loop-back interface fc1/13 enable switch B# Configuration Reflector Successful. test: shows how to run the latency This example interface fc4/1 switch A# diagnostic isl latency-test Waiting for sync to be achieved on the link ... Sync is achieved, Link has been initialized. ... Starting the test --------------------------------------------------------- fc4/1 Latency test for port: Result Latency 399 (in ns): in the switch in the cable 39 (in ns): Latency 4 m Length of the cable (accuracy +/- 2m): --------------------------------------------------------- testing: This example shows how to disable a port on a reflector switch for latency isl reflector loop-back interface fc1/13 disable switch B# diagnostic latency_test Successful. Configuration Reflector Platforms Supported Test on Other Latency Configuring and reflector switches perform test between the following tasks: the latency the generator To configure Procedure on the reflector mode using the it to loopback latency switch for testing Step the test interface Enable 1 by setting following command: enable switch B# system health isl reflector latency_test loop-back interface interface id the generator Step 2 Configure switch to run the test and display the results: id isl latency-test interface switch A# system health interface configure on the reflector Step 3 To disable the reflector port for latency the following command testing switch: Diagnostics Link Interswitch Configuring 11

12 Configuring Diagnostics Link Interswitch Test on Cisco Traffic Series a Single Configuring Switches 9700 MDS Hop latency_test loop-back interface interface id disable switch B# health isl reflector system Test Latency testing: switch for latency shows how to enable a port on a reflector This example interface switch latency_test isl reflector health fc4/25 system B# loop-back enable Reflector Successful. Configuration test: shows how to run the latency This example interface fc 1/13 isl latency-test health system A# switch to be achieved ... for sync Waiting on the link Sync is achieved, Link has been initialized. ... Starting the test --------------------------------------------------------- fc1/13 Latency test Result for port: 5504 (in ns): Latency in the switch (in ns): 664 Latency in the cable m Length of the cable (accuracy +/- 2m): 4.816514 --------------------------------------------------------- switch for latency This example shows how to disable testing: a port on a reflector health switch B# disable fc4/25 interface loop-back latency_test isl reflector system Configuration Successful. Reflector Configuring a Single Hop Traffic Test on Cisco MDS 9700 Series Switches switch, the To configure a Single Hop Traffic Test between the generator switch and the reflector perform following tasks: Procedure switch for Single Hop Traffic Test by setting on the reflector the test interface mode 1 Step Enable it to loopback command: using the following id enable switch B# isl reflector traffic_test loop-back interface diagnostic interface using one of the following options: the interface Configure 2 Step the interface • Configure on the generator switch to run the traffic test for a given frame count, frame size, and rate (link speed) parameters: interface interface id start frame-count number switch A# value diagnostic isl generator rate size frame_size min minimum num step size maximum max Configuring Interswitch Link Diagnostics 12

13 Configuring Diagnostics Link Interswitch Test on Cisco Traffic Series a Single Configuring Switches 9700 MDS Hop • Configure on the generator switch to run the traffic test for a given duration, frame size, the interface and rate (link speed) parameters: interface seconds duration start id rate interface isl generator diagnostic switchA# value frame_size num min max maximum size minimum step size Step switch use the following the test result on the generator To stop the Single Hop Traffic Test or to display 3 command: id stop interface interface isl generator diagnostic switch A# To disable the following command on the reflector the reflector 4 Step port for Single Hop Traffic Test configure switch: loop-back disable id interface interface traffic_test isl reflector diagnostic switch B# Step View the results of the Single Hop Traffic Test: 5 switch B# show diagnostic isl result interface interface id Test Hop Traffic Single This example shows how to enable the test interface on the reflector switch for Single Hop Traffic Test by setting mode: it to loopback traffic_test fc9/37 enable isl reflector loop-back interface diagnostic B# switch Successful. Configuration Reflector duration, speed, This example shows how to run a traffic teston the generator switchfor a particular and frame size parameters: interface switch A# diagnostic isl generator start fc4/5 duration 100 rate 16G frame_size min 16 max 517 step 1 This example the results for duration shows how to run and stop a traffic test stop and display parameter: interface duration start fc4/3 10 isl generator diagnostic A# switch on the link ... Waiting for sync to be achieved the test. initialized successfully. Starting Link switch fc4/3 interface isl generator diagnostic A# stop --------------------------------------------------------- for port: Result Traffic test fc4/3 6245142 Transmitted: Packets Recieved: 6245142 Packets ISL traffic Efficiency (percent): 100.0000 --------------------------------------------------------- interface disable B# diagnostic isl reflector traffic_test fc9/37 loop-back switch Reflector Configuration Successful. shows the results of the Single Hop Traffic Test: This example Interswitch Link Diagnostics Configuring 13

14 Configuring Diagnostics Link Interswitch Hop Supported Configuring Platforms Test on Other Traffic a Single interface fc 5/3 switch show diagnostic isl result B# --------------------------------------------------------- test fc5/3 for port: Result Traffic hop Single Transmitted: Packets 30621868 Packets Recieved: 30621868 100.0000 (percent): Efficiency ISL traffic --------------------------------------------------------- Configuring Test on Other Supported Traffic Hop a Single Platforms perform the To configure the generator Traffic Test between switch and the reflector switch, a Single-Hop following tasks: Procedure Enable on the reflector the test interface it to loopback 1 Step mode switch for Single Hop Traffic Test by setting using the following command: health isl reflector traffic_test loop-back interface interface id enable switch B# system using one of the following 2 Configure the interface Step options: • Configure the interface on the generator switch to run the traffic test for a given frame count, frame size, and rate (link speed) parameters: system isl generator interface interface id health start frame-count number switch A# rate value num step size max size minimum min frame_size maximum the interface on the generator switch to run the traffic test for a given duration, frame size, • Configure and rate (link speed) parameters: rate interface switch A# system health isl generator interface id start duration seconds value num step size maximum max size minimum min frame_size To stop the Single Hop Traffic Test or to display the test results on the generator Step 3 switch use the following command: id stop interface interface isl generator health system switch A# port for Single Hop Traffic Test configure command on the reflector the reflector 4 Step To disable the following switch: system health isl reflector traffic_test loop-back interface interface id disable switch B# 5 View the results of the Single Hop Traffic Test: Step system show switch B# health isl result interface interface id Traffic Test Hop Single switch for Single Hop Traffic on the reflector shows how to enable the test interface This example Test by setting mode: it to loopback Configuring Link Interswitch Diagnostics 14

15 Configuring Diagnostics Link Interswitch Test on Cisco Traffic Series Configuring Switches 9700 MDS a Multihop health isl reflector traffic_test loop-back interface fc9/37 enable switch system B# Successful. Configuration Reflector parameter the result for duration shows how to run and stop a traffic test and display This example switch: on a generator health start duration 100 isl generator switch A# fc12/16 system interface Waiting ... on the link to be achieved for sync the test. Link Starting successfully. initialized health stop switch isl generator A# fc12/16 system interface --------------------------------------------------------- Traffic test Result for port: fc12/16 Transmitted: 5293153 Packets Packets Recieved: 5293153 (percent): ISL traffic 100.0000 Efficiency --------------------------------------------------------- health isl reflector traffic_test loop-back interface fc9/37 disable switch B# system Successful. Reflector Configuration This example shows the results of the Single Hop Traffic Test: interface switch B# show system health fc 1/18 isl result --------------------------------------------------------- Single hop Traffic fc1/18 test Result for port: 1019885186 Packets Transmitted: Packets Recieved: 1019885186 ISL traffic Efficiency (percent): 100.0000 --------------------------------------------------------- Switches 9700 Configuring a Multihop Traffic Test on Cisco MDS Series switch, To configure a Multihop Traffic Test between the perform the generator switch and the reflector following tasks: Note and destination domain, For a given VSAN, source domain, there can be only one test running. Procedure on the reflector Step and domain mode for a given VSAN switch by setting it to loopback 1 the test interface Enable switch for Multihop ID of the generator Traffic Test: isl multi_hop diagnostic reflector loop-back switch B# interface id vsan vsan id sour ce-domain interface sour ce id enable switch: use the following command on the reflector To obtain the source domain switch B# vsan fcdomain domain-list vsan id show switchtoruntheMultihop TrafficTestforagivenVSAN, destination 2 Step Configure theinterface onthegenerator frame count, link speed, and frame size parameters: switch), ID of the reflector (domain domain Diagnostics Interswitch Configuring Link 15

16 Configuring Diagnostics Link Interswitch Test on Cisco Traffic Series Configuring Switches 9700 MDS a Multihop id start switchA# isl multi_hop generator interface interface id vsan vsan id dest-domain dest diagnostic num size maximum max size minimum min frame_size value rate number frame-count step theinterface destination TrafficTestforagivenVSAN, switchtoruntheMultihop Configure onthegenerator rate (link speed), and frame size parameters: duration, switch), ID of the reflector (domain domain switchA# generator interface interface id vsan vsan id dest-domain diagnostic isl multi_hop dest id start max size duration seconds rate value num step maximum frame_size size minimum min use the following To obtain the destination switch: on the generator command domain id switch A# show fcdomain domain-list vsan vsan To stop the Multihop Step 3 Traffic Test or to display the test results on the generator switch use the following command: stop id vsan id dest-domain dest id switch A# vsan diagnostic isl multi_hop interface interface generator on the reflector the following Traffic Test configure port for Mutlihop the reflector To disable 4 Step command switch: ce-domain switch B# diagnostic isl multi_hop reflector loop-back interface interface id vsan vsan id sour sour ce id disable Step 5 View the results of the Multihop Traffic Test: interface show id switch B# diagnostic isl result interface test Traffic MultiHop switches: and reflector list on both the generator the domain shows how to display This example domain-list switch# show vsan fcdomain 1 of domains: 3 Number WWN Domain ID --------- ----------------------- [Principal] 0x85(133) 20:01:00:0d:ec:b7:20:01 0xef(239) [Local] 20:01:40:55:39:0c:70:81 0x02(2) 20:01:00:0d:ec:b7:28:c1 on the reflector This example shows how to enable the test interface switch by setting it to loopback Traffic Test: mode for a given VSAN and domain ID of the generator switch for Multihop diagnostic isl multi_hop reflector loop-back interface fc9/36 vsan 1 source_domain switch B# 239 enable Thisexample showshowtorun,stop,anddisplay theresultsofthetraffictestonthegenerator switch for frame count parameter: fc4/10 switch 1 dest_domain 133 start A# diagnostic isl multi_hop generator interface vsan duration 100 diagnostic 1 dest_domain switch A# 133 stop isl multi_hop generator vsan fc4/10 interface Generator Clean-up is stopped. in progress. wait... Please Diagnostics Link Interswitch Configuring 16

17 Diagnostics Link Interswitch Configuring Platforms Supported Test on Other Traffic a Multihop Configuring --------------------------------------------------------- fc4/10 for port: Result test Traffic 6291024 Transmitted: Packets 6291024 Recieved: Packets ISL traffic 100.0000 (percent): Efficiency --------------------------------------------------------- interface diagnostic B# fc9/36 switch 1 source_domain reflector isl multi_hop loop-back vsan 239 disable switch for a particular This example shows how to run a traffic test on the generator duration, speed and frame size parameters: 133 start vsan generator fc4/10 interface 1 dest_domain isl multi_hop diagnostic A# switch 16G frame_size min 16 max 517 step 1 duration 100 rate 194 stop 1 dest_domain interface generator isl multi_hop diagnostic switch# fc 1/7 vsan in progress. Generator is stopped. Clean-up wait... Please --------------------------------------------------------- Result Traffic test for port: fc1/7 Packets Transmitted: 52415159 Packets 52415159 Recieved: ISL traffic Efficiency (percent): 100.0000 --------------------------------------------------------- This example Traffic Test: shows the results of the Multihop show diagnostic interface switch# isl result fc 4/17 --------------------------------------------------------- fc4/17 for port: Result test hop Traffic Multi Transmitted: 6131424 Packets 6131424 Packets Recieved: ISL traffic Efficiency (percent): 100.0000 --------------------------------------------------------- Supported Platforms Traffic Configuring a Multihop Test on Other the perform switch, switch and the reflector the generator Traffic Test between a Multihop To configure following tasks: Procedure mode for a given VSAN Enable the test interface on the reflector Step and domain 1 switch by setting it to loopback ID of the generator switch for Multihop Traffic Test: sour ce-domain system ce health isl multi_hop generator interface interface switchB# vsan vsan id sour id id enable To obtain the source domain use the following command on the reflector switch: vsan switch B# show fcdomain domain-list vsan id destination Step 2 Configure theinterface TrafficTestforagivenVSAN, switchtoruntheMultihop onthegenerator domain switch), frame count, link speed, and frame size parameters: (domain ID of the reflector Diagnostics Link Interswitch Configuring 17

18 Diagnostics Link Interswitch Configuring Platforms Supported Test on Other Traffic a Multihop Configuring id dest-domain dest id switch A# health isl multi_hop generator interface interface id vsan vsan system maximum size num minimum min frame_size size value rate number frame-count start max step destination TrafficTestforagivenVSAN, switchtoruntheMultihop onthegenerator theinterface Configure rate (link speed), (domain domain switch), ID of the reflector and frame size parameters: duration, interface dest system id health isl multi_hop generator switch A# dest-domain id vsan vsan id interface step num start duration seconds rate value frame_size min minimum size max maximum size switch: on the generator command use the following To obtain the destination domain vsan vsan id switch A# show fcdomain domain-list Step 3 To stop the Multihop Traffic Test or to display the test result on the generator switch use the following command: dest-domain dest id generator interface id vsan vsan id interface switch A# system health isl multi_hop stop the reflector command the following port for Mutlihop on the reflection To disable 4 Step Traffic Test configure switch: vsan id sour ce-domain switchB# system health isl multi_hop reflector loop-back interface interface id vsan sour ce id disable 5 Step View the results of the Multihop Traffic Test: interface interface id system isl result switch B# show health test Traffic Multihop switches: and reflector list on both the generator the domain shows how to display This example vsan 1 show fcdomain switch# domain-list Number of domains: 3 ID Domain WWN --------- ----------------------- [Principal] 20:01:00:0d:ec:b7:20:01 0x85(133) [Local] 20:01:40:55:39:0c:70:81 0xef(239) 20:01:00:0d:ec:b7:28:c1 0x02(2) in a VSAN present switch interface shows how to enable loop back to the generator This example switch for a Multihop from the reflector Traffic Test: 1 switch B# system health isl multi_hop reflector loop-back interface fc9/36 vsan source_domain 239 enable the results of the traffic test on the generator This example shows how to start, stop, and display switch for frame count parameter: 2 start isl multi_hop interface fc3/18 vsan 1 dest_domain switch A# system health generator frame-count 1000000 vsan 2 stop fc3/18 switch A# system health isl multi_hop generator 1 dest_domain interface in progress. Clean-up is stopped. Generator Diagnostics Link Interswitch Configuring 18

19 Diagnostics Link Interswitch Configuring ISL Diagnostics Debugging Please wait... --------------------------------------------------------- for port: Result test Traffic fc3/18 Packets Transmitted: 1000000 1000000 Recieved: Packets (percent): Efficiency ISL traffic 100.0000 --------------------------------------------------------- system fc9/36 isl multi_hop switch B# vsan 1 interface loop-back reflector health 239 disable source_domain This example shows how to run a traffic test on the generator switch for a particular duration, speed and frame size parameters: fc4/5 vsan 1 dest_domain 133 start switch A# system health isl multi_hop generator interface 16G frame_size duration 100 rate min 16 max 517 step 1 Traffic Test: This example shows the results of the Multihop fc 1/18 switch B# show system health isl result interface --------------------------------------------------------- hop Traffic test Result for port: fc1/7 Multi Transmitted: Packets 3065550 3065550 Recieved: Packets (percent): 100.0000 ISL traffic Efficiency --------------------------------------------------------- Debugging ISL Diagnostics To display test status use The following table lists the debug commands for this feature. the ISL diagnostic commands: one of the following commands 2: Debug Table Command Reference [Cisco MDS NX-OS Release Cisco MDS 9700 Switches 8.2(1) and earlier] tests Displays thestatusofconfigured ISLdiagnostic num show diagnostic isl status index start index per port. number 0 num start index diagnostic show isl status 10 tests in progress: Status of isl_diag ---------------------------------------------------------- Mode Index Interface Test ---------------------------------------------------------- fc1/1 0 Reflector Test Latency SH fc2/7 Reflector 1 Test Traffic Generator MH 2 fc2/48 Test Traffic ---------------------------------------------------------- Diagnostics Link Interswitch Configuring 19

20 Diagnostics Link Interswitch Configuring ISL Diagnostics Debugging Reference Command 8.3(1) and later] Release [Cisco MDS NX-OS Cisco MDS 9700 Switches ISLdiagnostic Displays tests thestatusofconfigured isl status diagnostic show per port. isl status show switch# diagnostic of isl_diag Status in progress: tests ---------------------------------------------------------- Interface Index Mode Test ---------------------------------------------------------- SH Reflector fc2/41 0 Test Traffic ---------------------------------------------------------- the results of the Single Hop or Multihop Displays id interface interface isl result diagnostic show Traffic Tests isl result switch# show diagnostic interface fc 5/3 --------------------------------------------------------- for port: Single hop Traffic test Result fc5/3 30621868 Packets Transmitted: Packets 30621868 Recieved: ISL traffic Efficiency 100.0000 (percent): --------------------------------------------------------- CiscoMDS9396T,CiscoMDS9148T,CiscoMDS9132T[CiscoMDSNX-OS Release CiscoMDS9396S, 8.3(1) and later] the results of the Single Hop or Multihop Displays interface id show system health isl result interface Traffic Tests. interface switch# show system health isl result fc 1/18 --------------------------------------------------------- Result hop Single for port: test Traffic fc1/18 Transmitted: Packets 1019885186 Packets Recieved: 1019885186 ISL traffic (percent): Efficiency 100.0000 --------------------------------------------------------- isl status tests that are Displays show the status of ISL Diagnostics health system in progress. show system health isl status switch# of isl_diag Status tests in progress: ---------------------------------------------------------- Interface Index Mode Test ---------------------------------------------------------- SH 0 fc1/51 Reflector Traffic Test ---------------------------------------------------------- Diagnostics Link Interswitch Configuring 20

21 Diagnostics Link Interswitch Configuring References Additional Additional References sections: online diagnostics, to implementing related information For additional see the following Documents Related Document Title Related Topic Command CLI commands Reference Cisco MDS 9000 Family InterSwitch Link Diagnostics for Online History Feature Diagnostics for this feature. Table 3: Feature History for Online Diagnostics , on page 21 lists the release history Table 3: Feature History for Online Diagnostics Feature Name Information Feature Releases ISLDiagnostics 7.3(0)D1(1) wasintroduced. Thisfeature Link Diagnostics Configuring Interswitch 21

22 Configuring Diagnostics Link Interswitch Additional References Interswitch Diagnostics Link Configuring 22

Related documents