Configure ICMP-path-echo Entity to Detect Network Communication

Network Requirement

• Use the ICMP-path-echo entity on Device1, detecting the path network communication from Device1 to Device3.

Network Topology

Figure 3–2 Networking of configuring the ICMP-path-echo entity

Configuration Steps

Step 1: Configure VLAN and add the port to the corresponding VLAN. (Omitted)

Step 2: Configure the IP address and route of the interface, making Device1, Device2, and Device3 communicate with each other. (Omitted)

Step 3: Configure the ICMP-path-echo entity and add the attribute parameters.

#Configure Device1.

# View the ICMP-path-echo entity parameters.

Device1#show rtr entity 1 
----------------------------------------------------
ID:1           name:IcmpPathEcho1       Created:TRUE 
**************type:ICMPPATHECHO****************
CreatedTime:WED OCT 24 10:18:02 2012
LatestModifiedTime:WED OCT 24 10:19:09 2012
Times-of-schedule:0 
TargetIp:192.0.0.2
SourceIp:110.1.0.1 
Transmit-packets:1 (each hop)
Request-data-size:70
Timeout:5000(ms)
Frequency:60(s)
TargetOnly:FALSE 
Verify-data:FALSE
Alarm-type:none 
Threshold-of-rtt:9000(ms) direction:be
Threshold-of-pktloss:1 direction:be
Number-of-history-kept:255 
Periods:1 
In-scheduling:FALSE
Status:DEFAULT

The result shows that the entity parameters are consistent with the configuration.

In-scheduling:FALSE indicates that the entity is not scheduled.

Status:DEFAULT indicates that the entity status is DEFAULT.

Step 4: Schedule the defined ICMP-path-echo entity and define the attribute parameters of the scheduling.

#Configure Device1.

Step 5: Check the result.

#View the entity status.

Device1#show rtr entity 1
-----------------------------------------------------------------
 	 ID:1           name:IcmpPathEcho1              Created:TRUE 
*********************type:ICMPPATHECHO****************
CreatedTime:WED OCT 24 10:18:02 2012 
LatestModifiedTime:WED OCT 24 10:19:09 2012
Times-of-schedule:1 
Time-of-last-schedule:WED OCT 24 10:20:01 2012
TargetIp:192.0.0.2 
SourceIp:110.1.0.1 
Transmit-packets:1 (each hop)
Request-data-size:70
Timeout:5000(ms)
Frequency:60(s)
TargetOnly:FALSE 
Verify-data:FALSE
Alarm-type:none 
Threshold-of-rtt:9000(ms) direction:be
Threshold-of-pktloss:1 direction:be
Number-of-history-kept:255 
Periods:1 
In-scheduling:TRUE
Status:REACHABLE 

In-scheduling:TRUE indicates that the entity is being scheduled.

Status:REACHABLE indicates that the entity status is reachable, that is, the network connection from Device1to Device3 is normal.

#View the history record content.

Device1#show rtr history 1 
--------------------------------------------------------------
ID:1    Name:IcmpPathEcho1 
History of hop-by-hop: 
 110.1.0.2   PktLoss:0  ,Rtt:2    (ms) 
 192.0.0.2   PktLoss:0  ,Rtt:1    (ms)
History of record from source to dest:
CurHistorySize:1    MaxHistorysize:255 
WED OCT 24 10:20:01 2012 
        PktLoss:0   ,Rtt:1    (ms) 

In the history records, record the packet loss and delay of each scheduling.

#Wait for some time and after scheduling for 10 times, view the entity status.

Device1#show rtr entity 1
----------------------------------------------------------------- 
 	 ID:1            name:IcmpPathEcho1              Created:TRUE 
*********************type:ICMPPATHECHO***************************
CreatedTime:WED OCT 24 10:18:02 2012 
LatestModifiedTime:WED OCT 24 10:19:09 2012
Times-of-schedule:10 
Time-of-last-schedule:WED OCT 24 10:29:01 2012
TargetIp:192.0.0.2 
SourceIp:110.1.0.1 
Transmit-packets:1 (each hop)
Request-data-size:70
Timeout:5000(ms)
Frequency:60(s)
TargetOnly:FALSE 
Verify-data:FALSE
Alarm-type:none 
Threshold-of-rtt:9000(ms) direction:be
Threshold-of-pktloss:1 direction:be
Number-of-history-kept:255 
Periods:1 
In-scheduling:FALSE
Status:DEFAULT

After scheduling for 10 times, the scheduling stops and the entity status is DEFAULT.