Configure UDP-echo Entity to Detect Network Transmitting UDP Packets
Network Requirement
- Use the UDP-echo entity on Device1 and detect the network transmitting UDP packets from Device1 to Device3.
Network Topology
![Networking of configuring the UDP-echo entity](/storage/images/Document/Maipu/monitoring/config-udp-echo-entity.jpg)
Figure 3–5 Networking of configuring the UDP-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 responder on Device3 as the responder end.
#Configure Device3
Device3#config terminal
Device3(config)#rtr enable
Device3(config)#rtr responder
|
Step 4: Configure the UDP-echoentity on Device1 and add the attribute parameters.
#Configure Device1.
Device1#config terminal
Device1(config)#rtr enable
Device1(config)#rtr 1 udpecho
Device1(config-rtr-udpecho)#set dest-ipaddr 192.0.0.2 dest-port 1001 source-ipaddr 110.1.0.1 source-port 1001
Device1(config-rtr-udpecho)#number-of-history-kept 255
Device1(config-rtr-udpecho)#frequency 10
Device1(config-rtr-udpecho)#exit
|
#View the entity parameter.
Device1#show rtr entity 1
------------------------------------------------------------
ID:1 name:UdpEcho1 Created:TRUE
**********************type:UDPECHO**************************
CreatedTime:WED OCT 24 16:36:45 2012
LatestModifiedTime:WED OCT 24 16:37:44 2012
Times-of-schedule:0
Entry-state:Pend
TargetIp:192.0.0.2 TargetPort:1001
SourceIp:110.1.0.1 SourePort:1001
TimeOut:5000(ms)
request-data-size:16
Frequecy:10(s)
Alarm-type:none
Threshold-of-rtt:9000(ms) direction:be
Threshold-of-pktloss:1 direction:be
Number-of-history-kept:255
Periods:1
Status:DEFAULT
--------------------------------------------------------------
The result shows that the entity parameters are consistent with the configuration.
Status: DEFAULT indicates that the entity status is DEFAULT.
Step 5: Schedule the defined UDP-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 6: Check the result.
#View the entity status.
Device1#show rtr entity 1
------------------------------------------------------------
ID:1 name:UdpEcho1 Created:TRUE
**********************type:UDPECHO***************************
CreatedTime:WED OCT 24 16:36:45 2012
LatestModifiedTime:WED OCT 24 16:37:44 2012
Times-of-schedule:5
Time-of-last-schedule:WED OCT 24 16:39:50 2012
Entry-state:Pend
TargetIp:192.0.0.2 TargetPort:1001
SourceIp:110.1.0.1 SourePort:1001
TimeOut:5000(ms)
request-data-size:16
Frequecy:10(s)
Alarm-type:none
Threshold-of-rtt:9000(ms) direction:be
Threshold-of-pktloss:1 direction:be
Data-pattern:ABCD
Number-of-history-kept:255
Periods:1
Status:REACHABLE
-------------------------------------------------------------
Status: REACHABLE indicates that the entity status is reachable, that is, the network from Device1 to Device2 can transmits the UDP packets normally.
#View the history record content.
Device1#show rtr history 1
--------------------------------------------------------------
ID:1 Name:UdpEcho1 CurHistorySize:5 MaxHistorysize:255 History
recorded as following:
WED OCT 24 16:39:54 2012
PktLoss:0 ,Rtt:1 (ms)
WED OCT 24 16:39:44 2012
PktLoss:0 ,Rtt:1 (ms)
WED OCT 24 16:39:33 2012
PktLoss:0 ,Rtt:2 (ms)
WED OCT 24 16:39:23 2012
PktLoss:0 ,Rtt:2 (ms)
WED OCT 24 16:39:13 2012
PktLoss:0 ,Rtt:2 (ms)
---------------------------------------------------------------
In the history records, record the packet loss and delay of each scheduling.
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
Before configuring the UDP-echo entity, we need to configure the rtr responder command at the destination end as the responder. If the responder end is not configured, the scheduling result is wrong.