Check Udp Operation
This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the UDP SLA protocol. In addition, the UDP NSM responder service is configured.
Test IPv4 Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using an IPv4 destination address) and the UDP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.215.200.100/24 set service nsm responder type udp port 60000
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10.215.200.50/24 set service nsm operation A destination-address 10.215.200.100 set service nsm operation A type udp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 60000
Step 3: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 0 0.00 al_rtt false 0 0.00
Step 4: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
--------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled --------------------------------------------------------------------------------------------- A al_rtt false 0.000032 0.000005 0.000000 8/100 A al_loss false 0.000032 0.000005 0.000000 8/100 A al_jitter false 0.000032 0.000005 0.000000 8/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-01-24 22:57:48.648645 1 44.95 al_loss true 2024-01-24 22:57:47.818085 1 57.76 al_rtt true 2024-01-24 22:57:49.255403 1 35.71
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------ Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------ A al_rtt true 0.440228 0.399867 44.000000 100/100 2024-01-24 22:57:49.255403 A al_loss true 0.440228 0.399867 44.000000 100/100 2024-01-24 22:57:47.818085 A al_jitter true 0.440228 0.399867 44.000000 100/100 2024-01-24 22:57:48.648645
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:57:56.722628 2024-01-24 22:57:48.648645 2 64.47 al_loss false 2024-01-24 22:57:57.026392 2024-01-24 22:57:47.818085 2 73.60 al_rtt false 2024-01-24 22:57:55.721455 2024-01-24 22:57:49.255403 2 51.66
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000436 0.000110 0.000000 100/100 2024-01-24 22:57:55.721455 2024-01-24 22:57:49.255403 A al_loss false 0.000436 0.000110 0.000000 100/100 2024-01-24 22:57:57.026392 2024-01-24 22:57:47.818085 A al_jitter false 0.000436 0.000110 0.000000 100/100 2024-01-24 22:57:56.722628 2024-01-24 22:57:48.648645
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:57:56.722628 2024-01-24 22:57:48.648645 2 43.14 al_loss false 2024-01-24 22:57:57.026392 2024-01-24 22:57:47.818085 2 49.24 al_rtt true 2024-01-24 22:58:00.633940 2024-01-24 22:57:55.721455 3 51.28
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.792460 0.009133 0.000000 100/100 2024-01-24 22:58:00.633940 2024-01-24 22:57:55.721455 A al_loss false 0.792460 0.009133 0.000000 100/100 2024-01-24 22:57:57.026392 2024-01-24 22:57:47.818085 A al_jitter false 0.792460 0.009133 0.000000 100/100 2024-01-24 22:57:56.722628 2024-01-24 22:57:48.648645
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:57:56.722628 2024-01-24 22:57:48.648645 2 32.87 al_loss false 2024-01-24 22:58:09.258705 2024-01-24 22:58:04.733038 4 55.93 al_rtt false 2024-01-24 22:58:08.748995 2024-01-24 22:58:00.633940 4 59.37
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000382 0.000051 0.000000 100/100 2024-01-24 22:58:08.748995 2024-01-24 22:58:00.633940 A al_loss false 0.000382 0.000051 0.000000 100/100 2024-01-24 22:58:09.258705 2024-01-24 22:58:04.733038 A al_jitter false 0.000382 0.000051 0.000000 100/100 2024-01-24 22:57:56.722628 2024-01-24 22:57:48.648645
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-01-24 22:58:12.372923 2024-01-24 22:57:56.722628 3 36.93 al_loss false 2024-01-24 22:58:09.258705 2024-01-24 22:58:04.733038 4 45.01 al_rtt false 2024-01-24 22:58:08.748995 2024-01-24 22:58:00.633940 4 47.78
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.195600 0.315119 0.000000 100/100 2024-01-24 22:58:08.748995 2024-01-24 22:58:00.633940 A al_loss false 0.195600 0.315119 0.000000 100/100 2024-01-24 22:58:09.258705 2024-01-24 22:58:04.733038 A al_jitter true 0.195600 0.315119 0.000000 100/100 2024-01-24 22:58:12.372923 2024-01-24 22:57:56.722628
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:58:20.417235 2024-01-24 22:58:12.372923 4 44.19 al_loss false 2024-01-24 22:58:09.258705 2024-01-24 22:58:04.733038 4 37.67 al_rtt false 2024-01-24 22:58:17.411994 2024-01-24 22:58:15.835645 6 44.31
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000403 0.000111 0.000000 100/100 2024-01-24 22:58:17.411994 2024-01-24 22:58:15.835645 A al_loss false 0.000403 0.000111 0.000000 100/100 2024-01-24 22:58:09.258705 2024-01-24 22:58:04.733038 A al_jitter false 0.000403 0.000111 0.000000 100/100 2024-01-24 22:58:20.417235 2024-01-24 22:58:12.372923
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv4 FQDN Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address) and the UDP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.215.200.100/24 set service nsm responder type udp port 60000
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10.215.200.50/24 set service nsm operation A destination-address test.nsm.fqdn set service nsm operation A type udp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 60000 set service dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet 10.215.200.100
Step 3: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 0 0.00 al_rtt false 0 0.00
Step 4: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
--------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled --------------------------------------------------------------------------------------------- A al_rtt false 0.000037 0.000006 0.000000 10/100 A al_loss false 0.000037 0.000006 0.000000 10/100 A al_jitter false 0.000037 0.000006 0.000000 10/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-01-24 22:58:35.164311 1 49.15 al_loss true 2024-01-24 22:58:34.765321 1 55.34 al_rtt true 2024-01-24 22:58:35.966630 1 36.76
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------ Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------ A al_rtt true 0.420240 0.439828 42.000000 100/100 2024-01-24 22:58:35.966630 A al_loss true 0.420240 0.439828 42.000000 100/100 2024-01-24 22:58:34.765321 A al_jitter true 0.420240 0.439828 42.000000 100/100 2024-01-24 22:58:35.164311
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:58:43.237228 2024-01-24 22:58:35.164311 2 65.51 al_loss false 2024-01-24 22:58:43.636568 2024-01-24 22:58:34.765321 2 72.02 al_rtt false 2024-01-24 22:58:42.526484 2024-01-24 22:58:35.966630 2 53.21
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000423 0.000067 0.000000 100/100 2024-01-24 22:58:42.526484 2024-01-24 22:58:35.966630 A al_loss false 0.000423 0.000067 0.000000 100/100 2024-01-24 22:58:43.636568 2024-01-24 22:58:34.765321 A al_jitter false 0.000423 0.000067 0.000000 100/100 2024-01-24 22:58:43.237228 2024-01-24 22:58:35.164311
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:58:43.237228 2024-01-24 22:58:35.164311 2 44.04 al_loss false 2024-01-24 22:58:43.636568 2024-01-24 22:58:34.765321 2 48.41 al_rtt true 2024-01-24 22:58:47.030526 2024-01-24 22:58:42.526484 3 53.02
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.792443 0.009092 0.000000 100/100 2024-01-24 22:58:47.030526 2024-01-24 22:58:42.526484 A al_loss false 0.792443 0.009092 0.000000 100/100 2024-01-24 22:58:43.636568 2024-01-24 22:58:34.765321 A al_jitter false 0.792443 0.009092 0.000000 100/100 2024-01-24 22:58:43.237228 2024-01-24 22:58:35.164311
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:58:43.237228 2024-01-24 22:58:35.164311 2 33.50 al_loss false 2024-01-24 22:58:55.665985 2024-01-24 22:58:51.147865 4 55.58 al_rtt false 2024-01-24 22:58:55.149216 2024-01-24 22:58:47.030526 4 60.91
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000419 0.000128 0.000000 100/100 2024-01-24 22:58:55.149216 2024-01-24 22:58:47.030526 A al_loss false 0.000419 0.000128 0.000000 100/100 2024-01-24 22:58:55.665985 2024-01-24 22:58:51.147865 A al_jitter false 0.000419 0.000128 0.000000 100/100 2024-01-24 22:58:43.237228 2024-01-24 22:58:35.164311
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-01-24 22:58:59.288764 2024-01-24 22:58:43.237228 3 35.55 al_loss false 2024-01-24 22:58:55.665985 2024-01-24 22:58:51.147865 4 44.59 al_rtt true 2024-01-24 22:59:01.665709 2024-01-24 22:58:55.149216 5 49.62
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.239873 0.354333 0.000000 100/100 2024-01-24 22:59:01.665709 2024-01-24 22:58:55.149216 A al_loss false 0.239873 0.354333 0.000000 100/100 2024-01-24 22:58:55.665985 2024-01-24 22:58:51.147865 A al_jitter true 0.239873 0.354333 0.000000 100/100 2024-01-24 22:58:59.288764 2024-01-24 22:58:43.237228
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:59:06.874431 2024-01-24 22:58:59.288764 4 43.76 al_loss false 2024-01-24 22:59:07.233334 2024-01-24 22:59:03.424438 6 48.07 al_rtt false 2024-01-24 22:59:05.220111 2024-01-24 22:59:01.665709 6 50.94
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000378 0.000065 0.000000 100/100 2024-01-24 22:59:05.220111 2024-01-24 22:59:01.665709 A al_loss false 0.000378 0.000065 0.000000 100/100 2024-01-24 22:59:07.233334 2024-01-24 22:59:03.424438 A al_jitter false 0.000378 0.000065 0.000000 100/100 2024-01-24 22:59:06.874431 2024-01-24 22:58:59.288764
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv6 Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using an IPv6 destination address) and the UDP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10::3/64 set service nsm responder type udp port 60000
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10::2/64 set service nsm operation A destination-address 10::3 set service nsm operation A type udp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 60000
Step 3: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 2024-01-24 22:59:23.757209 2024-01-24 22:59:18.698593 2 70.30 al_rtt false 2024-01-24 22:59:23.419873 2024-01-24 22:59:19.456146 2 55.05
Step 4: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000442 0.000133 0.000000 100/100 2024-01-24 22:59:23.419873 2024-01-24 22:59:19.456146 A al_loss false 0.000442 0.000133 0.000000 100/100 2024-01-24 22:59:23.757209 2024-01-24 22:59:18.698593 A al_jitter false 0.000442 0.000133 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-01-24 22:59:27.356973 1 23.86 al_loss true 2024-01-24 22:59:26.964531 2024-01-24 22:59:23.757209 3 65.16 al_rtt true 2024-01-24 22:59:28.164106 2024-01-24 22:59:23.419873 3 47.77
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.390238 0.389861 39.000000 100/100 2024-01-24 22:59:28.164106 2024-01-24 22:59:23.419873 A al_loss true 0.390238 0.389861 39.000000 100/100 2024-01-24 22:59:26.964531 2024-01-24 22:59:23.757209 A al_jitter true 0.390238 0.389861 39.000000 100/100 2024-01-24 22:59:27.356973
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:59:35.741310 2024-01-24 22:59:27.356973 2 43.89 al_loss false 2024-01-24 22:59:35.681853 2024-01-24 22:59:26.964531 4 72.14 al_rtt false 2024-01-24 22:59:34.729040 2024-01-24 22:59:28.164106 4 55.13
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000402 0.000067 0.000000 100/100 2024-01-24 22:59:34.729040 2024-01-24 22:59:28.164106 A al_loss false 0.000402 0.000067 0.000000 100/100 2024-01-24 22:59:35.681853 2024-01-24 22:59:26.964531 A al_jitter false 0.000402 0.000067 0.000000 100/100 2024-01-24 22:59:35.741310 2024-01-24 22:59:27.356973
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:59:35.741310 2024-01-24 22:59:27.356973 2 33.32 al_loss false 2024-01-24 22:59:35.681853 2024-01-24 22:59:26.964531 4 54.77 al_rtt true 2024-01-24 22:59:39.292897 2024-01-24 22:59:34.729040 5 54.44
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.801420 0.009057 0.000000 100/100 2024-01-24 22:59:39.292897 2024-01-24 22:59:34.729040 A al_loss false 0.801420 0.009057 0.000000 100/100 2024-01-24 22:59:35.681853 2024-01-24 22:59:26.964531 A al_jitter false 0.801420 0.009057 0.000000 100/100 2024-01-24 22:59:35.741310 2024-01-24 22:59:27.356973
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:59:35.741310 2024-01-24 22:59:27.356973 2 27.12 al_loss false 2024-01-24 22:59:47.870795 2024-01-24 22:59:43.347724 6 59.21 al_rtt false 2024-01-24 22:59:47.367468 2024-01-24 22:59:39.292897 6 60.19
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000412 0.000077 0.000000 100/100 2024-01-24 22:59:47.367468 2024-01-24 22:59:39.292897 A al_loss false 0.000412 0.000077 0.000000 100/100 2024-01-24 22:59:47.870795 2024-01-24 22:59:43.347724 A al_jitter false 0.000412 0.000077 0.000000 100/100 2024-01-24 22:59:35.741310 2024-01-24 22:59:27.356973
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-01-24 22:59:51.302718 2024-01-24 22:59:35.741310 3 30.52 al_loss false 2024-01-24 22:59:47.870795 2024-01-24 22:59:43.347724 6 49.64 al_rtt true 2024-01-24 22:59:53.983618 2024-01-24 22:59:47.367468 7 50.97
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.219535 0.310993 0.000000 100/100 2024-01-24 22:59:53.983618 2024-01-24 22:59:47.367468 A al_loss false 0.219535 0.310993 0.000000 100/100 2024-01-24 22:59:47.870795 2024-01-24 22:59:43.347724 A al_jitter true 0.219535 0.310993 0.000000 100/100 2024-01-24 22:59:51.302718 2024-01-24 22:59:35.741310
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 22:59:59.321963 2024-01-24 22:59:51.302718 4 38.42 al_loss false 2024-01-24 22:59:59.327416 2024-01-24 22:59:55.576133 8 51.65 al_rtt false 2024-01-24 22:59:57.098430 2024-01-24 22:59:53.983618 8 50.87
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000395 0.000065 0.000000 100/100 2024-01-24 22:59:57.098430 2024-01-24 22:59:53.983618 A al_loss false 0.000395 0.000065 0.000000 100/100 2024-01-24 22:59:59.327416 2024-01-24 22:59:55.576133 A al_jitter false 0.000395 0.000065 0.000000 100/100 2024-01-24 22:59:59.321963 2024-01-24 22:59:51.302718
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv6 FQDN Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address) and the UDP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10::3/64 set service nsm responder type udp port 60000
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10::2/64 set service nsm operation A destination-address test.nsm.fqdn set service nsm operation A type udp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 60000 set service dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet 10::3
Step 3: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 2024-01-24 23:00:16.975007 2024-01-24 23:00:11.955746 2 69.97 al_rtt false 2024-01-24 23:00:16.674856 2024-01-24 23:00:12.709128 2 55.21
Step 4: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000390 0.000393 0.000000 100/100 2024-01-24 23:00:16.674856 2024-01-24 23:00:12.709128 A al_loss false 0.000390 0.000393 0.000000 100/100 2024-01-24 23:00:16.975007 2024-01-24 23:00:11.955746 A al_jitter false 0.000390 0.000393 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-01-24 23:00:20.279021 1 25.57 al_loss true 2024-01-24 23:00:19.785881 2024-01-24 23:00:16.975007 3 67.60 al_rtt true 2024-01-24 23:00:21.324747 2024-01-24 23:00:16.674856 3 47.80
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.420225 0.419863 42.000000 100/100 2024-01-24 23:00:21.324747 2024-01-24 23:00:16.674856 A al_loss true 0.420225 0.419863 42.000000 100/100 2024-01-24 23:00:19.785881 2024-01-24 23:00:16.975007 A al_jitter true 0.420225 0.419863 42.000000 100/100 2024-01-24 23:00:20.279021
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 23:00:28.744344 2024-01-24 23:00:20.279021 2 44.57 al_loss false 2024-01-24 23:00:29.102073 2024-01-24 23:00:19.785881 4 75.49 al_rtt false 2024-01-24 23:00:27.637412 2024-01-24 23:00:21.324747 4 54.10
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000403 0.000065 0.000000 100/100 2024-01-24 23:00:27.637412 2024-01-24 23:00:21.324747 A al_loss false 0.000403 0.000065 0.000000 100/100 2024-01-24 23:00:29.102073 2024-01-24 23:00:19.785881 A al_jitter false 0.000403 0.000065 0.000000 100/100 2024-01-24 23:00:28.744344 2024-01-24 23:00:20.279021
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 23:00:28.744344 2024-01-24 23:00:20.279021 2 34.11 al_loss false 2024-01-24 23:00:29.102073 2024-01-24 23:00:19.785881 4 57.77 al_rtt true 2024-01-24 23:00:32.208354 2024-01-24 23:00:27.637412 5 53.99
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.792422 0.009071 0.000000 100/100 2024-01-24 23:00:32.208354 2024-01-24 23:00:27.637412 A al_loss false 0.792422 0.009071 0.000000 100/100 2024-01-24 23:00:29.102073 2024-01-24 23:00:19.785881 A al_jitter false 0.792422 0.009071 0.000000 100/100 2024-01-24 23:00:28.744344 2024-01-24 23:00:20.279021
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 23:00:28.744344 2024-01-24 23:00:20.279021 2 27.70 al_loss false 2024-01-24 23:00:40.738215 2024-01-24 23:00:36.205145 6 61.74 al_rtt false 2024-01-24 23:00:40.238704 2024-01-24 23:00:32.208354 6 59.89
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000392 0.000046 0.000000 100/100 2024-01-24 23:00:40.238704 2024-01-24 23:00:32.208354 A al_loss false 0.000392 0.000046 0.000000 100/100 2024-01-24 23:00:40.738215 2024-01-24 23:00:36.205145 A al_jitter false 0.000392 0.000046 0.000000 100/100 2024-01-24 23:00:28.744344 2024-01-24 23:00:20.279021
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-01-24 23:00:44.106516 2024-01-24 23:00:28.744344 3 31.18 al_loss false 2024-01-24 23:00:40.738215 2024-01-24 23:00:36.205145 6 51.68 al_rtt false 2024-01-24 23:00:40.238704 2024-01-24 23:00:32.208354 6 50.13
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.203746 0.313031 0.000000 100/100 2024-01-24 23:00:47.085050 2024-01-24 23:00:40.238704 A al_loss false 0.203746 0.313031 0.000000 100/100 2024-01-24 23:00:40.738215 2024-01-24 23:00:36.205145 A al_jitter true 0.203746 0.313031 0.000000 100/100 2024-01-24 23:00:44.106516 2024-01-24 23:00:28.744344
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-01-24 23:00:51.294494 2024-01-24 23:00:44.106516 4 36.96 al_loss false 2024-01-24 23:00:40.738215 2024-01-24 23:00:36.205145 6 44.55 al_rtt false 2024-01-24 23:00:49.134141 2024-01-24 23:00:47.085050 8 48.06
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000397 0.000055 0.000000 100/100 2024-01-24 23:00:49.134141 2024-01-24 23:00:47.085050 A al_loss false 0.000397 0.000055 0.000000 100/100 2024-01-24 23:00:40.738215 2024-01-24 23:00:36.205145 A al_jitter false 0.000397 0.000055 0.000000 100/100 2024-01-24 23:00:51.294494 2024-01-24 23:00:44.106516
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.