Hà Nội: NTT03, Line 1, Thống Nhất Complex, 82 Nguyễn Tuân, Thanh Xuân, Hà Nội. ● HCM: Số 31B, Đường 1, Phường An Phú, Quận 2 (Thủ Đức), TP HCM. ===> Đơn Vị Hàng Đầu Trong Lĩnh Vực Cung Cấp Thiết Bị Security - Network - Wifi - CCTV - Conference - Máy chủ Server - Lưu trữ Storge.
Danh mục sản phẩm

Configure ICMP-echo ipv6 Entity to Detect Network Communication

Network Requirement

  • Use the ICMP echo ipv6 entity on Device1 to detect the basic network communication between Device1 and Device3.

Network Topology

Networking of configuring the ICMP-echo ipv6 entity

Figure 3-7 Networking of configuring the ICMP-echo ipv6 entity

Configuration Steps

Step 1: Configure the IPv6 address, route of the interface, so that Device1 and Device3 can communicate with each other. (omitted)

Step 2: Configure the ICMP-echo ipv6 entity, and add the attribute parameters.

#Configure Device1.

Device1#configure terminal
Device1(config)#rtr enable
Device1(config)#rtr 1 icmpv6echo
Device1(config-rtr-icmpv6echo)#set 2136::2 5 70 2 12 extend 2135::1 0 TRUE
Device1(config-rtr-icmpv6echo)#alarm-type log
Device1(config-rtr-icmpv6echo)#number-of-history-kept 255
Device1(config-rtr-icmpv6echo)#threshold-pktLoss 10 direction be
Device1(config-rtr-icmpv6echo)#threshold-rtt 1000 direction be
Device1(config-rtr-icmpv6echo)#exit

#View the ICMP-echo ipv6 entity parameters.

Device1#show rtr entity 1
----------------------------------------------------------------- 
 	 ID:1            name:Icmpv6Echo1                Created:TRUE 
**********************type:ICMPV6ECHO****************************
CreatedTime:Tue Sep 17 10:05:52 2019
LatestModifiedTime:Tue Sep 17 10:21:06 2019
Times-of-schedule:0 
TargetIpv6:2136::2 
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: 
sourceIpv6:2135::1   tos:0
Verify-data:TRUE
In-scheduling:FALSE 
Schedule frequency:12(s)
Status:DEFAULT
-----------------------------------------------------------

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

In-scheduling:FALSE indicates that the entity does not schedule.

Status:DEFAULT indicates that the entity status is DEFAULT.

note


  • 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 not reachable, the status is UNREACHABLE.

Step 3: Schedule the defined ICMP-echo ipv6 entity, and define the attribute parameters of the scheduling.

#Configure Device1.

Device1(config)#rtr schedule 1 entity 1 start now ageout 20 life forever

Step 4: Check the result.

  1. When the network connectivity between Device1 and Device3 is normal:

#View the entity status.

Device1#show rtr entity 1 
------------------------------------------------------------------
 	 ID:1            name:Icmpv6Echo1                Created:TRUE 
**********************type:ICMPV6ECHO*****************************
CreatedTime:Tue Sep 17 10:05:52 2019
LatestModifiedTime:Tue Sep 17 10:21:06 2019
Times-of-schedule:2 
Time-of-last-schedule:Tue Sep 17 10:24:08 2019
TargetIpv6:2136::2 
Transmit-packets:5
Totally-send-packets:10
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: 
sourceIpv6:2135::1   tos:0
Verify-data:TRUE
In-scheduling:TRUE 
Schedule frequency:12(s)
Status:REACHABLE 
--------------------------------------------------------

In-scheduling:TRUE indicates that the entity is in scheduling.

Status:REACHABLE indicates that the entity status is reachable, that is, the network connectivity between Device1 and Device3 is normal.

  1. When the network connectivity between Device1 and Device3 fails:

Because the entity parameters are configured with the alarm mode of log, when reaching or exceeding the threshold value, print the alarm information as follows:

%SLA-4:Rtr 1 (ICMPV6ECHO) rtt [9000ms] was exceeded(>=) threshold [1000ms].

#View the entity status.

Device1#show rtr entity 1 
-----------------------------------------------------------------
 	 ID:1            name:Icmpv6Echo1                Created:TRUE 
**********************type:ICMPV6ECHO****************************
CreatedTime:Tue Sep 17 10:05:52 2019
LatestModifiedTime:Tue Sep 17 10:21:06 2019
Times-of-schedule:21 
Time-of-last-schedule:Tue Sep 17 10:28:08 2019
TargetIpv6:2136::2 
Transmit-packets:5
Totally-send-packets:105
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: 
sourceIpv6:2135::1   tos:0
Verify-data:TRUE
In-scheduling:TRUE 
Schedule frequency:12(s)
Status:UNREACHABLE 
---------------------------------------------------------------------

In-scheduling:TRUE indicates that the entity is in scheduling.

Status:UNREACHABLE indicates that the entity status is unreachable, that is, the network connectivity between Device1 and Device3 is unreachable.

#View the history record content.

Device1#show rtr history 1 
--------------------------------------------------------------------	 
ID:1    Name:Icmpv6Echo1        CurHistorySize:4  MaxHistorysize:255
History recorded as following: 
Tue Sep 17 10:24:42 2019 
        PktLoss:5    ,Rtt:invalid
Tue Sep 17 10:24:29 2019 
        PktLoss:1    ,Rtt:400   (ms)
Tue Sep 17 10:24:17 2019 
        PktLoss:0    ,Rtt:1    (ms)
Tue Sep 17 10:24:05 2019 
        PktLoss:0    ,Rtt:0    (ms) 
-----------------------------------------------------------------

The packet loss and delay of each scheduling are recorded in detail in the history record; RTT is invalid, which indicates that the network is not reachable due to the failure in the network.