Network Requirement
- Use the ICMP-path-jitter entity on Device1, detecting the path network communication from Device1 to Device3.
Network Topology
![Networking of configuring the ICMP-path-jitter entity](/storage/images/Document/Maipu/monitoring/config-icmp-path-jitter-entity.jpg)
Figure 3–3 Networking of configuring the ICMP-path-jitter 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-jitter entity and add the attribute parameters.
#Configure Device1.
Device1#config terminal
Device1(config)#rtr enable
Device1(config)#rtr 1 icmp-path-jitter
Device1(config-rtr-icmppathjitter)#set dest-ipaddr 192.0.0.2 10 20 source-ipaddr 110.1.0.1
Device1(config-rtr-icmppathjitter)#number-of-history-kept 255
Device1(config-rtr-icmppathjitter)#targetOnly false
Device1(config-rtr-icmppathjitter)#exit
|
#View the ICMP-path-jitter entity parameters.
Device1#show rtr entity 1
------------------------------------------------------------------
ID:1 name:IcmpPathJitter1 Created:TRUE
**********************type:ICMPPATHJITTER****************
CreatedTime:WED OCT 24 10:54:31 2012
LatestModifiedTime:WED OCT 24 10:56:12 2012
Times-of-schedule:0
TargetIp:192.0.0.2
SourceIp:110.1.0.1
Transmit-packets:10 (each hop)
Packets-interval:20(ms)
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: 200000000 direction:be
Threshold-of-jitter:6000(ms) 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-jitter entity and define the attribute parameters of the scheduling.
#Configure Device1.
Device1(config)#rtr schedule 1 entity 1 start now ageout 100 life foreve
|
Step 5: Check the result.
#View the entity status.
Device1#show rtr entity 1
---------------------------------------------------------------------
ID:1 name:IcmpPathJitter1 Created:TRUE
**********************type:ICMPPATHJITTER****************
CreatedTime:WED OCT 24 10:54:31 2012
LatestModifiedTime:WED OCT 24 10:56:12 2012
Times-of-schedule:4
Time-of-last-schedule:WED OCT 24 11:00:25 2012
TargetIp:192.0.0.2
SourceIp:110.1.0.1
Transmit-packets:10 (each hop)
Packets-interval:20(ms)
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: 200000000 direction:be
Threshold-of-jitter:6000(ms) 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:IcmpPathJitter1
History of hop-by-hop:
110.1.0.2 PktLoss:0 Rtt:1 (ms),Jitter:0 (ms)
192.0.0.2 PktLoss:0 Rtt:0 (ms),Jitter:0 (ms)
History of record from source to dest:
CurHistorySize:4 MaxHistorysize:255
WED OCT 24 11:00:25 2012
PktLoss:0 ,Rtt:1 (ms),Jitter:0 (ms)
WED OCT 24 10:59:25 2012
PktLoss:0 ,Rtt:0 (ms),Jitter:0 (ms)
WED OCT 24 10:58:25 2012
PktLoss:0 ,Rtt:0 (ms),Jitter:0 (ms)
WED OCT 24 10:57:25 2012
PktLoss:0 ,Rtt:0 (ms),Jitter:0 (ms)
---------------------------------------------------------------------------
In the history records, record the packet loss, delay and jitter of each scheduling.