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 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10.215.200.50/24 set service nsm operation A alarm al_jitter activate jitter 0.1 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 destination-address 10.215.200.100 set service nsm operation A destination-port 60000 set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A type udp set service nsm operation A window 100 set system alarm al_jitter set system alarm al_loss set system alarm al_rtt set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
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_jitter false 0.000025 0.000006 0.000000 6/100 A al_loss false 0.000025 0.000006 0.000000 6/100 A al_rtt false 0.000025 0.000006 0.000000 6/100
Note
The previous command output should show that NSM operations have been successfully created and that 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, NSM operation will detect this packet loss in the network and trigger the ‘al_loss’ alarm.
Step 5: Modify the following configuration lines 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-07-03 16:02:27.760989 1 51.88 al_loss true 2024-07-03 16:02:27.112718 1 62.54 al_rtt true 2024-07-03 16:02:28.714817 1 36.27
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_jitter true 0.400306 0.459787 40.000000 100/100 2024-07-03 16:02:27.760989 A al_loss true 0.400306 0.459787 40.000000 100/100 2024-07-03 16:02:27.112718 A al_rtt true 0.400306 0.459787 40.000000 100/100 2024-07-03 16:02:28.714817
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since packet losses on the network are greater than the configured threshold. In this scenario, the delay and jitter values are also affected, meaning the ‘al_rtt’ and ‘al_jitter’ alarms also go off (since their configured threshold is also exceeded).
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect packets are no longer being lost and will deactivate the ‘al_loss’ alarm.
Step 8: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:02:35.581366 2024-07-03 16:02:27.760989 2 66.51 al_loss false 2024-07-03 16:02:36.182737 2024-07-03 16:02:27.112718 2 77.16 al_rtt false 2024-07-03 16:02:34.981706 2024-07-03 16:02:28.714817 2 53.33
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_jitter false 0.000458 0.000133 0.000000 100/100 2024-07-03 16:02:35.581366 2024-07-03 16:02:27.760989 A al_loss false 0.000458 0.000133 0.000000 100/100 2024-07-03 16:02:36.182737 2024-07-03 16:02:27.112718 A al_rtt false 0.000458 0.000133 0.000000 100/100 2024-07-03 16:02:34.981706 2024-07-03 16:02:28.714817
Note
The previous command output should show that alarms are deactivated (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, NSM operation will detect a delay in the network and will trigger the ‘al_rtt’ alarm.
Step 11: Modify the following configuration lines 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-07-03 16:02:35.581366 2024-07-03 16:02:27.760989 2 44.79 al_loss false 2024-07-03 16:02:36.182737 2024-07-03 16:02:27.112718 2 51.95 al_rtt true 2024-07-03 16:02:39.196237 2024-07-03 16:02:34.981706 3 53.62
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_jitter false 0.774517 0.009159 0.000000 100/100 2024-07-03 16:02:35.581366 2024-07-03 16:02:27.760989 A al_loss false 0.774517 0.009159 0.000000 100/100 2024-07-03 16:02:36.182737 2024-07-03 16:02:27.112718 A al_rtt true 0.774517 0.009159 0.000000 100/100 2024-07-03 16:02:39.196237 2024-07-03 16:02:34.981706
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since delays on the network are greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect significant delays no longer exist and will deactivate the ‘al_rtt’ alarm.
Step 14: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:02:35.581366 2024-07-03 16:02:27.760989 2 33.89 al_loss false 2024-07-03 16:02:47.605279 2024-07-03 16:02:43.098266 4 58.84 al_rtt false 2024-07-03 16:02:47.102963 2024-07-03 16:02:39.196237 4 61.44
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_jitter false 0.000464 0.000140 0.000000 100/100 2024-07-03 16:02:35.581366 2024-07-03 16:02:27.760989 A al_loss false 0.000464 0.000140 0.000000 100/100 2024-07-03 16:02:47.605279 2024-07-03 16:02:43.098266 A al_rtt false 0.000464 0.000140 0.000000 100/100 2024-07-03 16:02:47.102963 2024-07-03 16:02:39.196237
Note
The previous command output should show the alarms are deactivated (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, NSM operation will detect said jitter in the network and will trigger the ‘al_jitter’ alarm.
Step 17: Modify the following configuration lines 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-07-03 16:02:50.719073 2024-07-03 16:02:35.581366 3 37.19 al_loss false 2024-07-03 16:02:47.605279 2024-07-03 16:02:43.098266 4 47.19 al_rtt true 2024-07-03 16:02:53.174064 2024-07-03 16:02:47.102963 5 50.75
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_jitter true 0.202926 0.294385 0.000000 100/100 2024-07-03 16:02:50.719073 2024-07-03 16:02:35.581366 A al_loss false 0.202926 0.294385 0.000000 100/100 2024-07-03 16:02:47.605279 2024-07-03 16:02:43.098266 A al_rtt true 0.202926 0.294385 0.000000 100/100 2024-07-03 16:02:53.174064 2024-07-03 16:02:47.102963
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, NSM operation will no longer detect a jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:02:57.375630 2024-07-03 16:02:50.719073 4 42.10 al_loss false 2024-07-03 16:02:47.605279 2024-07-03 16:02:43.098266 4 39.48 al_rtt false 2024-07-03 16:02:55.723437 2024-07-03 16:02:53.174064 6 48.64
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_jitter false 0.000410 0.000124 0.000000 100/100 2024-07-03 16:02:57.375630 2024-07-03 16:02:50.719073 A al_loss false 0.000410 0.000124 0.000000 100/100 2024-07-03 16:02:47.605279 2024-07-03 16:02:43.098266 A al_rtt false 0.000410 0.000124 0.000000 100/100 2024-07-03 16:02:55.723437 2024-07-03 16:02:53.174064
Note
The previous command output should show the alarms are deactivated (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 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10.215.200.50/24 set service dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet 10.215.200.100 set service nsm operation A alarm al_jitter activate jitter 0.1 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 destination-address test.nsm.fqdn set service nsm operation A destination-port 60000 set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A type udp set service nsm operation A window 100 set system alarm al_jitter set system alarm al_loss set system alarm al_rtt set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
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_jitter false 0.000021 0.000004 0.000000 6/100 A al_loss false 0.000021 0.000004 0.000000 6/100 A al_rtt false 0.000021 0.000004 0.000000 6/100
Note
The previous command output should show that NSM operations have been successfully created and that 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, NSM operation will detect this packet loss in the network and trigger the ‘al_loss’ alarm.
Step 5: Modify the following configuration lines 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-07-03 16:03:08.611549 1 56.31 al_loss true 2024-07-03 16:03:08.360288 1 60.39 al_rtt true 2024-07-03 16:03:10.205465 1 29.95
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_jitter true 0.330296 0.439856 33.000000 100/100 2024-07-03 16:03:08.611549 A al_loss true 0.330296 0.439856 33.000000 100/100 2024-07-03 16:03:08.360288 A al_rtt true 0.330296 0.439856 33.000000 100/100 2024-07-03 16:03:10.205465
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since packet losses on the network are greater than the configured threshold. In this scenario, the delay and jitter values are also affected, meaning the ‘al_rtt’ and ‘al_jitter’ alarms also go off (since their configured threshold is also exceeded).
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect packets are no longer being lost and will deactivate the ‘al_loss’ alarm.
Step 8: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:03:16.783525 2024-07-03 16:03:08.611549 2 70.00 al_loss false 2024-07-03 16:03:17.282257 2024-07-03 16:03:08.360288 2 76.38 al_rtt false 2024-07-03 16:03:16.425992 2024-07-03 16:03:10.205465 2 53.27
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_jitter false 0.000508 0.000125 0.000000 100/100 2024-07-03 16:03:16.783525 2024-07-03 16:03:08.611549 A al_loss false 0.000508 0.000125 0.000000 100/100 2024-07-03 16:03:17.282257 2024-07-03 16:03:08.360288 A al_rtt false 0.000508 0.000125 0.000000 100/100 2024-07-03 16:03:16.425992 2024-07-03 16:03:10.205465
Note
The previous command output should show that alarms are deactivated (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, NSM operation will detect a delay in the network and will trigger the ‘al_rtt’ alarm.
Step 11: Modify the following configuration lines 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-07-03 16:03:16.783525 2024-07-03 16:03:08.611549 2 47.09 al_loss false 2024-07-03 16:03:17.282257 2024-07-03 16:03:08.360288 2 51.39 al_rtt true 2024-07-03 16:03:20.241117 2024-07-03 16:03:16.425992 3 53.59
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_jitter false 0.774524 0.009135 0.000000 100/100 2024-07-03 16:03:16.783525 2024-07-03 16:03:08.611549 A al_loss false 0.774524 0.009135 0.000000 100/100 2024-07-03 16:03:17.282257 2024-07-03 16:03:08.360288 A al_rtt true 0.774524 0.009135 0.000000 100/100 2024-07-03 16:03:20.241117 2024-07-03 16:03:16.425992
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since delays on the network are greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect significant delays no longer exist and will deactivate the ‘al_rtt’ alarm.
Step 14: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:03:16.783525 2024-07-03 16:03:08.611549 2 35.44 al_loss false 2024-07-03 16:03:28.730927 2024-07-03 16:03:24.189635 4 58.36 al_rtt false 2024-07-03 16:03:28.220981 2024-07-03 16:03:20.241117 4 61.57
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_jitter false 0.000422 0.000140 0.000000 100/100 2024-07-03 16:03:16.783525 2024-07-03 16:03:08.611549 A al_loss false 0.000422 0.000140 0.000000 100/100 2024-07-03 16:03:28.730927 2024-07-03 16:03:24.189635 A al_rtt false 0.000422 0.000140 0.000000 100/100 2024-07-03 16:03:28.220981 2024-07-03 16:03:20.241117
Note
The previous command output should show the alarms are deactivated (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, NSM operation will detect said jitter in the network and will trigger the ‘al_jitter’ alarm.
Step 17: Modify the following configuration lines 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-07-03 16:03:31.761434 2024-07-03 16:03:16.783525 3 38.72 al_loss false 2024-07-03 16:03:28.730927 2024-07-03 16:03:24.189635 4 46.81 al_rtt true 2024-07-03 16:03:33.865328 2024-07-03 16:03:28.220981 5 52.36
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_jitter true 0.243030 0.336995 0.000000 100/100 2024-07-03 16:03:31.761434 2024-07-03 16:03:16.783525 A al_loss false 0.243030 0.336995 0.000000 100/100 2024-07-03 16:03:28.730927 2024-07-03 16:03:24.189635 A al_rtt true 0.243030 0.336995 0.000000 100/100 2024-07-03 16:03:33.865328 2024-07-03 16:03:28.220981
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, NSM operation will no longer detect a jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:03:39.324454 2024-07-03 16:03:31.761434 4 45.78 al_loss false 2024-07-03 16:03:39.976297 2024-07-03 16:03:36.063914 6 50.54 al_rtt false 2024-07-03 16:03:38.124467 2024-07-03 16:03:33.865328 6 53.70
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_jitter false 0.000583 0.000173 0.000000 100/100 2024-07-03 16:03:39.324454 2024-07-03 16:03:31.761434 A al_loss false 0.000583 0.000173 0.000000 100/100 2024-07-03 16:03:39.976297 2024-07-03 16:03:36.063914 A al_rtt false 0.000583 0.000173 0.000000 100/100 2024-07-03 16:03:38.124467 2024-07-03 16:03:33.865328
Note
The previous command output should show the alarms are deactivated (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 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address '10::2/64' set service nsm operation A alarm al_jitter activate jitter 0.1 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 destination-address '10::3' set service nsm operation A destination-port 60000 set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A type udp set service nsm operation A window 100 set system alarm al_jitter set system alarm al_loss set system alarm al_rtt set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
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-07-03 16:03:54.100519 2024-07-03 16:03:49.287856 2 71.74 al_rtt false 2024-07-03 16:03:53.952201 2024-07-03 16:03:50.044003 2 58.29
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_jitter false 0.012553 0.003850 0.000000 100/100 A al_loss false 0.012553 0.003850 0.000000 100/100 2024-07-03 16:03:54.100519 2024-07-03 16:03:49.287856 A al_rtt false 0.012553 0.003850 0.000000 100/100 2024-07-03 16:03:53.952201 2024-07-03 16:03:50.044003
Note
The previous command output should show that NSM operations have been successfully created and that 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, NSM operation will detect this packet loss in the network and trigger the ‘al_loss’ alarm.
Step 5: Modify the following configuration lines 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-07-03 16:03:56.974006 1 27.68 al_loss true 2024-07-03 16:03:56.710447 2024-07-03 16:03:54.100519 3 68.48 al_rtt true 2024-07-03 16:03:58.208515 2024-07-03 16:03:53.952201 3 49.19
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_jitter true 0.410279 0.459814 41.000000 100/100 2024-07-03 16:03:56.974006 A al_loss true 0.410279 0.459814 41.000000 100/100 2024-07-03 16:03:56.710447 2024-07-03 16:03:54.100519 A al_rtt true 0.410279 0.459814 41.000000 100/100 2024-07-03 16:03:58.208515 2024-07-03 16:03:53.952201
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since packet losses on the network are greater than the configured threshold. In this scenario, the delay and jitter values are also affected, meaning the ‘al_rtt’ and ‘al_jitter’ alarms also go off (since their configured threshold is also exceeded).
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect packets are no longer being lost and will deactivate the ‘al_loss’ alarm.
Step 8: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:04:04.977695 2024-07-03 16:03:56.974006 2 44.34 al_loss false 2024-07-03 16:04:05.628879 2024-07-03 16:03:56.710447 4 76.09 al_rtt false 2024-07-03 16:04:04.836397 2024-07-03 16:03:58.208515 4 58.40
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_jitter false 0.000417 0.000108 0.000000 100/100 2024-07-03 16:04:04.977695 2024-07-03 16:03:56.974006 A al_loss false 0.000417 0.000108 0.000000 100/100 2024-07-03 16:04:05.628879 2024-07-03 16:03:56.710447 A al_rtt false 0.000417 0.000108 0.000000 100/100 2024-07-03 16:04:04.836397 2024-07-03 16:03:58.208515
Note
The previous command output should show that alarms are deactivated (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, NSM operation will detect a delay in the network and will trigger the ‘al_rtt’ alarm.
Step 11: Modify the following configuration lines 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-07-03 16:04:04.977695 2024-07-03 16:03:56.974006 2 33.73 al_loss false 2024-07-03 16:04:05.628879 2024-07-03 16:03:56.710447 4 57.88 al_rtt true 2024-07-03 16:04:08.583961 2024-07-03 16:04:04.836397 5 57.55
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_jitter false 0.774511 0.009146 0.000000 100/100 2024-07-03 16:04:04.977695 2024-07-03 16:03:56.974006 A al_loss false 0.774511 0.009146 0.000000 100/100 2024-07-03 16:04:05.628879 2024-07-03 16:03:56.710447 A al_rtt true 0.774511 0.009146 0.000000 100/100 2024-07-03 16:04:08.583961 2024-07-03 16:04:04.836397
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since delays on the network are greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect significant delays no longer exist and will deactivate the ‘al_rtt’ alarm.
Step 14: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:04:04.977695 2024-07-03 16:03:56.974006 2 27.29 al_loss false 2024-07-03 16:04:17.014180 2024-07-03 16:04:12.496992 6 62.23 al_rtt false 2024-07-03 16:04:16.505824 2024-07-03 16:04:08.583961 6 62.96
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_jitter false 0.000447 0.000131 0.000000 100/100 2024-07-03 16:04:04.977695 2024-07-03 16:03:56.974006 A al_loss false 0.000447 0.000131 0.000000 100/100 2024-07-03 16:04:17.014180 2024-07-03 16:04:12.496992 A al_rtt false 0.000447 0.000131 0.000000 100/100 2024-07-03 16:04:16.505824 2024-07-03 16:04:08.583961
Note
The previous command output should show the alarms are deactivated (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, NSM operation will detect said jitter in the network and will trigger the ‘al_jitter’ alarm.
Step 17: Modify the following configuration lines 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-07-03 16:04:20.684288 2024-07-03 16:04:04.977695 3 29.52 al_loss false 2024-07-03 16:04:17.014180 2024-07-03 16:04:12.496992 6 52.06 al_rtt false 2024-07-03 16:04:16.505824 2024-07-03 16:04:08.583961 6 52.66
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_jitter true 0.185331 0.261628 0.000000 100/100 2024-07-03 16:04:20.684288 2024-07-03 16:04:04.977695 A al_loss false 0.185331 0.261628 0.000000 100/100 2024-07-03 16:04:17.014180 2024-07-03 16:04:12.496992 A al_rtt false 0.185331 0.261628 0.000000 100/100 2024-07-03 16:04:16.505824 2024-07-03 16:04:08.583961
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, NSM operation will no longer detect a jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:04:27.328986 2024-07-03 16:04:20.684288 4 36.00 al_loss false 2024-07-03 16:04:17.014180 2024-07-03 16:04:12.496992 6 44.85 al_rtt false 2024-07-03 16:04:25.581010 2024-07-03 16:04:23.298661 8 50.98
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_jitter false 0.000455 0.000115 0.000000 100/100 2024-07-03 16:04:27.328986 2024-07-03 16:04:20.684288 A al_loss false 0.000455 0.000115 0.000000 100/100 2024-07-03 16:04:17.014180 2024-07-03 16:04:12.496992 A al_rtt false 0.000455 0.000115 0.000000 100/100 2024-07-03 16:04:25.581010 2024-07-03 16:04:23.298661
Note
The previous command output should show the alarms are deactivated (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 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address '10::2/64' set service dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet '10::3' set service nsm operation A alarm al_jitter activate jitter 0.1 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 destination-address test.nsm.fqdn set service nsm operation A destination-port 60000 set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A type udp set service nsm operation A window 100 set system alarm al_jitter set system alarm al_loss set system alarm al_rtt set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
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-07-03 16:04:41.402537 2024-07-03 16:04:36.488519 2 73.12 al_rtt false 2024-07-03 16:04:41.200347 2024-07-03 16:04:37.231459 2 59.10
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_jitter false 0.018416 0.004631 0.000000 100/100 A al_loss false 0.018416 0.004631 0.000000 100/100 2024-07-03 16:04:41.402537 2024-07-03 16:04:36.488519 A al_rtt false 0.018416 0.004631 0.000000 100/100 2024-07-03 16:04:41.200347 2024-07-03 16:04:37.231459
Note
The previous command output should show that NSM operations have been successfully created and that 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, NSM operation will detect this packet loss in the network and trigger the ‘al_loss’ alarm.
Step 5: Modify the following configuration lines 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-07-03 16:04:44.302604 1 26.94 al_loss true 2024-07-03 16:04:43.853848 2024-07-03 16:04:41.402537 3 69.74 al_rtt true 2024-07-03 16:04:45.256377 2024-07-03 16:04:41.200347 3 51.01
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_jitter true 0.410290 0.479803 41.000000 100/100 2024-07-03 16:04:44.302604 A al_loss true 0.410290 0.479803 41.000000 100/100 2024-07-03 16:04:43.853848 2024-07-03 16:04:41.402537 A al_rtt true 0.410290 0.479803 41.000000 100/100 2024-07-03 16:04:45.256377 2024-07-03 16:04:41.200347
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since packet losses on the network are greater than the configured threshold. In this scenario, the delay and jitter values are also affected, meaning the ‘al_rtt’ and ‘al_jitter’ alarms also go off (since their configured threshold is also exceeded).
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect packets are no longer being lost and will deactivate the ‘al_loss’ alarm.
Step 8: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:04:52.625309 2024-07-03 16:04:44.302604 2 45.84 al_loss false 2024-07-03 16:04:52.970717 2024-07-03 16:04:43.853848 4 77.24 al_rtt false 2024-07-03 16:04:51.765857 2024-07-03 16:04:45.256377 4 57.70
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_jitter false 0.000381 0.000133 0.000000 100/100 2024-07-03 16:04:52.625309 2024-07-03 16:04:44.302604 A al_loss false 0.000381 0.000133 0.000000 100/100 2024-07-03 16:04:52.970717 2024-07-03 16:04:43.853848 A al_rtt false 0.000381 0.000133 0.000000 100/100 2024-07-03 16:04:51.765857 2024-07-03 16:04:45.256377
Note
The previous command output should show that alarms are deactivated (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, NSM operation will detect a delay in the network and will trigger the ‘al_rtt’ alarm.
Step 11: Modify the following configuration lines 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-07-03 16:04:52.625309 2024-07-03 16:04:44.302604 2 34.80 al_loss false 2024-07-03 16:04:52.970717 2024-07-03 16:04:43.853848 4 58.65 al_rtt true 2024-07-03 16:04:55.972697 2024-07-03 16:04:51.765857 5 56.77
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_jitter false 0.774462 0.009144 0.000000 100/100 2024-07-03 16:04:52.625309 2024-07-03 16:04:44.302604 A al_loss false 0.774462 0.009144 0.000000 100/100 2024-07-03 16:04:52.970717 2024-07-03 16:04:43.853848 A al_rtt true 0.774462 0.009144 0.000000 100/100 2024-07-03 16:04:55.972697 2024-07-03 16:04:51.765857
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since delays on the network are greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect significant delays no longer exist and will deactivate the ‘al_rtt’ alarm.
Step 14: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:04:52.625309 2024-07-03 16:04:44.302604 2 28.17 al_loss false 2024-07-03 16:05:04.393980 2024-07-03 16:04:59.878296 6 62.76 al_rtt false 2024-07-03 16:05:03.892141 2024-07-03 16:04:55.972697 6 62.27
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_jitter false 0.000469 0.000120 0.000000 100/100 2024-07-03 16:04:52.625309 2024-07-03 16:04:44.302604 A al_loss false 0.000469 0.000120 0.000000 100/100 2024-07-03 16:05:04.393980 2024-07-03 16:04:59.878296 A al_rtt false 0.000469 0.000120 0.000000 100/100 2024-07-03 16:05:03.892141 2024-07-03 16:04:55.972697
Note
The previous command output should show the alarms are deactivated (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, NSM operation will detect said jitter in the network and will trigger the ‘al_jitter’ alarm.
Step 17: Modify the following configuration lines 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-07-03 16:05:07.462976 2024-07-03 16:04:52.625309 3 32.13 al_loss false 2024-07-03 16:05:04.393980 2024-07-03 16:04:59.878296 6 52.47 al_rtt true 2024-07-03 16:05:10.450129 2024-07-03 16:05:03.892141 7 52.18
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_jitter true 0.206929 0.262635 0.000000 100/100 2024-07-03 16:05:07.462976 2024-07-03 16:04:52.625309 A al_loss false 0.206929 0.262635 0.000000 100/100 2024-07-03 16:05:04.393980 2024-07-03 16:04:59.878296 A al_rtt true 0.206929 0.262635 0.000000 100/100 2024-07-03 16:05:10.450129 2024-07-03 16:05:03.892141
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, NSM operation will no longer detect a jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Modify the following configuration lines in DUT0
:
delete interfaces ethernet eth0 traffic
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-07-03 16:05:14.515761 2024-07-03 16:05:07.462976 4 37.54 al_loss false 2024-07-03 16:05:04.393980 2024-07-03 16:04:59.878296 6 45.28 al_rtt false 2024-07-03 16:05:12.813606 2024-07-03 16:05:10.450129 8 50.69
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_jitter false 0.000503 0.000145 0.000000 100/100 2024-07-03 16:05:14.515761 2024-07-03 16:05:07.462976 A al_loss false 0.000503 0.000145 0.000000 100/100 2024-07-03 16:05:04.393980 2024-07-03 16:04:59.878296 A al_rtt false 0.000503 0.000145 0.000000 100/100 2024-07-03 16:05:12.813606 2024-07-03 16:05:10.450129
Note
The previous command output should show the alarms are deactivated (since the network quality is good).