Network Requirement
- Use the ICMP-echo entity on Device1, detecting the basic communication of the network from Device1 to Device3.
Network Topology
![Networking of configuring ICMP-echo entity](/storage/images/Document/Maipu/monitoring/configuring-icmp-echo-entity.jpg)
Figure 3–1 Networking of configuring ICMP-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 communicate with Device3. (Omitted)
Step 3: Configure the ICMP-echo entity and add the attribute parameters.
#Configure Device1.
Device1#config terminal
Device1(config)#rtr enable
Device1(config)#rtr 1 icmpecho
Device1(config-rtr-icmpecho)#set 132.1.1.1 5 70 2 12 extend 131.1.1.1 0 TRUE FALSE
Device1(config-rtr-icmpecho)#alarm-type log
Device1(config-rtr-icmpecho)#number-of-history-kept 255
Device1(config-rtr-icmpecho)#threshold-pktLoss 10 direction be
Device1(config-rtr-icmpecho)#threshold-rtt 1000 direction be
Device1(config-rtr-icmpecho)#exit
|
#View the ICMP-echo entity parameters.
Device1#show rtr entity 1
---------------------------------------------------------
ID:1 name:IcmpEcho1 Created:TRUE
*********************type:ICMPECHO****************
CreatedTime:WED OCT 31 14:49:31 2012
LatestModifiedTime:WED OCT 31 14:53:53 2012
Times-of-schedule:0
TargetIp:132.1.1.1
Transmit-packets:5
Totally-send-packets:0
Packet-size:70
Timeout:2(s)
Alarm-type:log
Threshold-of-rtt:1000(ms) direction:be
Threshold-of-packet-loss:10 direction:be
Number-of-history-kept:255
Periods:1
Extend parameters:
sourceIp:131.1.1.1 tos:0 DF(DON'T FRAG):TRUE Verify-data:FALSE
In-scheduling:FALSE
Schedule frequency:12(s)
Status:DEFAULT
The result shows that the entity parameters are consistent with the configuration.
In-scheduling: FALSE Description entity is not scheduled.
Status: DEFAULTDescription entity status is DEFAULT.
![note](/storage/images/Document/Maipu/note-icon.jpg)
- When the entity is not scheduled, the status is DEFAULT; when the entity is scheduled and if the entity is reachable, the status is REACHABLE; if the entity is unreachable, the status is UNREACHABLE.
Step 4: Schedule the defined ICMP-echo entity and define the attribute parameters of the scheduling.
#Configure Device1
Device1(config)#rtr schedule 1 entity 1 start now ageout 100 life forever
|
Step 5: Check the result.
(1) When the network connectivity from Device1 to Device3 is normal:
#View the entity status.
Device1#show rtr entity 1
ID:1 name:IcmpEcho1 Created:TRUE
**********************type:ICMPECHO****************
CreatedTime:WED OCT 31 14:49:31 2012
LatestModifiedTime: WED OCT 31 14:53:53 2012
Times-of-schedule: 1
Time-of-last-schedule: WED OCT 31 14:54:07 2012
TargetIp: 132.1.1.1
Transmit-packets:5
Totally-send-packets:5
Packet-size:70
Timeout:2(s)
Alarm-type:log
Threshold-of-rtt:1000(ms) direction:be
Threshold-of-packet-loss:10 direction:be
Number-of-history-kept:255
Periods:1
Extend parameters:
sourceIp:131.1.1.1 tos:0 DF(DON'T FRAG):TRUE Verify-data:FALSE
In-scheduling:TRUE
Schedule frequency:12(s)
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.
(2) When the network connectivity from Device1 to Device3 is faulty:
The alarm mode is configured as log, so when the network is disconnected, print the alarm information on the device, as follows:
Oct 31 14:54:46: [tRtrIcmpRcv]Rtr 1 (ICMPECHO) rtt [9000ms] was exceeded(>=) threshold [1000ms].
#View the entity status.
Device1#show rtr entity 1
---------------------------------------------------------
ID:1 name:IcmpEcho1 Created:TRUE
*********************type:ICMPECHO****************
CreatedTime:WED OCT 31 14:49:31 2012
LatestModifiedTime:WED OCT 31 14:53:53 2012
Times-of-schedule:4
Time-of-last-schedule:WED OCT 31 14:54:43 2012
TargetIp:132.1.1.1
Transmit-packets:5
Totally-send-packets:20
Packet-size:70
Timeout:2(s)
Alarm-type:log
Threshold-of-rtt:1000(ms) direction:be
Threshold-of-packet-loss:10 direction:be
Number-of-history-kept:255
Periods:1
Extend parameters:
sourceIp:131.1.1.1 tos:0 DF(DON'T FRAG):TRUE Verify-data:FALSE
In-scheduling:TRUE
Schedule frequency:12(s)
Status:UNREACHABLE
In-scheduling: TRUED indicates that the entity is being scheduled;
Status: UNREACHABLE indicates that the entity status is unreachable, that is, the network connection from Device1to Device3 is unreachable.
#View the history record content.
Device1#show rtr history 1
--------------------------------------------------------------------
ID:1 Name:IcmpEcho1 CurHistorySize:4 MaxHistorysize:255 History
recorded as following:
WED OCT 31 14:54:46 2012
PktLoss:5 ,Rtt:invalid
WED OCT 31 14:54:32 2012
PktLoss:0 ,Rtt:11 (ms)
WED OCT 31 14:54:20 2012
PktLoss:0 ,Rtt:2 (ms)
WED OCT 31 14:54:07 2012
PktLoss:0 ,Rtt:2 (ms)
In the history records, record the packet loss and delay of each scheduling; if Rtt is invalid, it indicates that there is fault in the network and the network is reachable.