Usage Guidelines
When you enter the ping command, a ping is sent to the node at the specified location or to nodes with the specified FGID. The received response is compared byte-by-byte to the sent packet. If a ping response is not received before the specified time-out, or if the ping response does not match the transmitted ping, the ping is considered failed.
A node that is unreachable or intermittently working impacts the total run time for the test as follows:
(received_packet_count * RTT + lost_packet_count * timeout + (count-1) * interval)
Line cards have two fabricq ASICs and an egressq ASIC. From the first fabricq ASIC (instance 0), the CPU can be reached directly or via the egressq ASIC. From the second fabricq ASIC (instance 1), the CPU can be reached only via the egressq ASIC. In other words, no direct packet path exists between instance 1 and the CPU.
The route processor (RP) and distributed route processor (DRP) cards have only one fabricq ASIC per node (CPU) and no egressq ASIC. Therefore, a fabric ping on an RP or DRP destination specified with the via-egressq or via-fabricq-1 keyword fails.
Examples
The following example shows sample output from a control-ethernet ping to an SP node in slot 0/0:
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# ping control-eth location 0/0/SP count 5
Src node: 529 : 0/RP0/CPU0
Dest node: 0 : 0/0/SP
Local node: 529 : 0/RP0/CPU0
Packet cnt: 5 Packet size: 128 Payload ptn type: default (0)
Hold-off (ms): 300 Time-out(s): 2 Max retries: 5
Destination node has MAC addr 5246.4800.0000
Running CE node ping.
Please wait...
Src: 529:, Dest: 0, Sent: 5, Rec'd: 5, Mismatched: 0
Min/Avg/Max RTT: 0/200/1000
CE node ping succeeded for node: 0
The following example shows a fabric ping from the active RP to the active RP. In this example, the ping contains 72 packets of 1 kilobyte each. This command performs a good coverage test of the entire switch fabric:
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# ping fabric location 0/RP0/CPU0 count 72 size 1024
Src node: 529 : 0/RP0/CPU0
Dest node: 529 : 0/RP0/CPU0
Local node: 529 : 0/RP0/CPU0
Packet cnt: 72 Packet size: 1024 Payload ptn type: default (0)
Hold-off (ms): 300 Time-out(s): 2 Max retries: 5
Running Fabric node ping.
Please wait...
Src: 529:, Dest: 529, Sent: 72, Rec'd: 72, Mismatched: 0
Min/Avg/Max RTT: 3000/3013/4000
Fabric node ping succeeded for node: 529
The following example shows a ping to a control Ethernet node that has a problem or does not exist:
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# ping control-eth location 0/1/CPU0 count 3
Src node: 529 : 0/RP0/CPU0
Dest node: 17 : 0/1/CPU0
Local node: 529 : 0/RP0/CPU0
Packet cnt: 3 Packet size: 128 Payload ptn type: default (0)
Hold-off (ms): 300 Time-out(s): 2 Max retries: 5
Destination node has MAC addr 5246.4800.0011
Running CE node ping.
Please wait...
Src: 529:, Dest: 17, Sent: 3, Rec'd: 0, Mismatched: 0
Requested ping failed for node: 17
The following example shows how to send a multicast fabric ping to nodes with the FGID of 1024. The node that sent the multicast ping waits 1 second for a response from each node.
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# ping fabric fgid 1024 tlate 1
Src node: 513 : 0/RP0/CPU0
fgid: 1024
Local node: 513 : 0/RP0/CPU0
Packet cnt: 1 Packet size: 128 Payload ptn type: default (0)
Hold-off (ms): 1 Time-out(s): 2 Max retries: 5
DelayTimeout: 1 Priority: High
Running Fabric node ping.
Please wait...
Multicast (Pinging fgid) ...
Node Sent Rcv. Late Lost
______________________________________________________________
0/1/CPU0 (0x11:17) 1 1 0 0
0/4/CPU0 (0x41:65) 1 1 0 0
0/4/CPU1 (0x42:66) 1 1 0 0
0/6/CPU0 (0x61:97) 1 1 0 0
0/RP0/CPU0 (0x201:513) 1 1 0 0
0/RP1/CPU0 (0x211:529) 1 1 0 0
diag_ping: All 6 nodes responded to all 1 pings
The following example shows how to send a multicast fabric ping to nodes with the FGID of 1024. The ping packets are routed from the first fabricq ASIC (instance 0) to the destination CPU via the egressq ASIC. The pings to the two line cards (0/1/CPU0 and 0/6/CPU0) succeeded, while the pings to the RPs (0/RP0/CPU0 and 0/RP1/CPU0) and DRPs (0/4/CPU0 and 0/4/CPU1) failed because they do not have an egressq ASIC.
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# ping fabric fgid 1024 count 10 via-egressq
Src node: 513 : 0/RP0/CPU0
fgid: 1024
Local node: 513 : 0/RP0/CPU0
Packet cnt: 10 Packet size: 128 Payload ptn type: default (0)
Hold-off (ms): 1 Time-out(s): 2 Max retries: 5
DelayTimeout: 1 Priority: High
Reaching destination CPUs via egressq
Running Fabric node ping.
Please wait...
Multicast (Pinging fgid) ...
Node Sent Rcv. Late Lost
______________________________________________________________
0/1/CPU0 (0x11:17) 10 10 0 0
0/4/CPU0 (0x41:65) 10 0 0 10
0/4/CPU1 (0x42:66) 10 0 0 10
0/6/CPU0 (0x61:97) 10 10 0 0
0/RP0/CPU0 (0x201:513) 10 0 0 10
0/RP1/CPU0 (0x211:529) 10 0 0 10
diag_ping: Out of 6 node(s), 2 node(s) responded to all 10 pings, 4 node(s) hads
The following example shows how to send a unicast ping to nodes with the FGID of 1024. The ping packets are routed from the second fabricq ASIC (instance 1) to the destination CPU via the egressq ASIC. The pings to the two line cards (0/1/CPU0 and 0/6/CPU0) succeeded, while the pings to the RPs (0/RP0/CPU0 and 0/RP1/CPU0) and DRPs (0/4/CPU0 and 0/4/CPU1) failed because they do not have a second fabricq ASIC nor an egressq ASIC.
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# ping fabric fgid 1024 count 10 uc via-fabricq-1
Src node: 513 : 0/RP0/CPU0
fgid: 1024
Local node: 513 : 0/RP0/CPU0
Packet cnt: 10 Packet size: 128 Payload ptn type: default (0)
Hold-off (ms): 1 Time-out(s): 2 Max retries: 5
DelayTimeout: 1 Priority: High
Using other fabricq instance
Running Fabric node ping.
Please wait...
Multicast (Pinging Individual Sponge Ids) ...
Node Sent Rcv. Late Lost
______________________________________________________________
0/1/CPU0 (0x11:17) 10 10 0 0
0/4/CPU0 (0x41:65) 10 0 0 10
0/4/CPU1 (0x42:66) 10 0 0 10
0/6/CPU0 (0x61:97) 10 10 0 0
0/RP0/CPU0 (0x201:513) 10 0 0 10
0/RP1/CPU0 (0x211:529) 10 0 0 10
diag_ping: Out of 6 node(s), 2 node(s) responded to all 10 pings, 4 node(s) hads