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.000022 0.000003 0.000000 6/100 A al_loss false 0.000022 0.000003 0.000000 6/100 A al_rtt false 0.000022 0.000003 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-30 11:57:55.734156 1 52.00 al_loss true 2024-07-30 11:57:55.384600 1 57.86 al_rtt true 2024-07-30 11:57:56.886176 1 32.86
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.470264 0.399819 47.000000 100/100 2024-07-30 11:57:55.734156 A al_loss true 0.470264 0.399819 47.000000 100/100 2024-07-30 11:57:55.384600 A al_rtt true 0.470264 0.399819 47.000000 100/100 2024-07-30 11:57:56.886176
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-30 11:58:03.555328 2024-07-30 11:57:55.734156 2 67.19 al_loss false 2024-07-30 11:58:03.906038 2024-07-30 11:57:55.384600 2 73.23 al_rtt false 2024-07-30 11:58:02.653675 2024-07-30 11:57:56.886176 2 49.58
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.000545 0.000122 0.000000 100/100 2024-07-30 11:58:03.555328 2024-07-30 11:57:55.734156 A al_loss false 0.000545 0.000122 0.000000 100/100 2024-07-30 11:58:03.906038 2024-07-30 11:57:55.384600 A al_rtt false 0.000545 0.000122 0.000000 100/100 2024-07-30 11:58:02.653675 2024-07-30 11:57:56.886176
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-30 11:58:03.555328 2024-07-30 11:57:55.734156 2 45.13 al_loss false 2024-07-30 11:58:03.906038 2024-07-30 11:57:55.384600 2 49.18 al_rtt true 2024-07-30 11:58:07.061542 2024-07-30 11:58:02.653675 3 51.30
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.774583 0.009137 0.000000 100/100 2024-07-30 11:58:03.555328 2024-07-30 11:57:55.734156 A al_loss false 0.774583 0.009137 0.000000 100/100 2024-07-30 11:58:03.906038 2024-07-30 11:57:55.384600 A al_rtt true 0.774583 0.009137 0.000000 100/100 2024-07-30 11:58:07.061542 2024-07-30 11:58:02.653675
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-30 11:58:03.555328 2024-07-30 11:57:55.734156 2 34.07 al_loss false 2024-07-30 11:58:15.481056 2024-07-30 11:58:10.969012 4 56.79 al_rtt false 2024-07-30 11:58:14.982531 2024-07-30 11:58:07.061542 4 59.65
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.000541 0.000129 0.000000 100/100 2024-07-30 11:58:03.555328 2024-07-30 11:57:55.734156 A al_loss false 0.000541 0.000129 0.000000 100/100 2024-07-30 11:58:15.481056 2024-07-30 11:58:10.969012 A al_rtt false 0.000541 0.000129 0.000000 100/100 2024-07-30 11:58:14.982531 2024-07-30 11:58:07.061542
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-30 11:58:19.427651 2024-07-30 11:58:03.555328 3 34.52 al_loss false 2024-07-30 11:58:15.481056 2024-07-30 11:58:10.969012 4 45.51 al_rtt false 2024-07-30 11:58:14.982531 2024-07-30 11:58:07.061542 4 47.80
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.185790 0.234109 0.000000 100/100 2024-07-30 11:58:19.427651 2024-07-30 11:58:03.555328 A al_loss false 0.185790 0.234109 0.000000 100/100 2024-07-30 11:58:15.481056 2024-07-30 11:58:10.969012 A al_rtt false 0.185790 0.234109 0.000000 100/100 2024-07-30 11:58:14.982531 2024-07-30 11:58:07.061542
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-30 11:58:26.451985 2024-07-30 11:58:19.427651 4 43.35 al_loss false 2024-07-30 11:58:26.602924 2024-07-30 11:58:22.740544 6 49.35 al_rtt false 2024-07-30 11:58:24.504898 2024-07-30 11:58:22.192263 6 46.74
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.000489 0.000105 0.000000 100/100 2024-07-30 11:58:26.451985 2024-07-30 11:58:19.427651 A al_loss false 0.000489 0.000105 0.000000 100/100 2024-07-30 11:58:26.602924 2024-07-30 11:58:22.740544 A al_rtt false 0.000489 0.000105 0.000000 100/100 2024-07-30 11:58:24.504898 2024-07-30 11:58:22.192263
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.000030 0.000008 0.000000 6/100 A al_loss false 0.000030 0.000008 0.000000 6/100 A al_rtt false 0.000030 0.000008 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-30 11:58:37.060907 1 47.57 al_loss true 2024-07-30 11:58:36.311488 1 59.88 al_rtt true 2024-07-30 11:58:37.463514 1 40.90
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.480267 0.339868 48.000000 100/100 2024-07-30 11:58:37.060907 A al_loss true 0.480267 0.339868 48.000000 100/100 2024-07-30 11:58:36.311488 A al_rtt true 0.480267 0.339868 48.000000 100/100 2024-07-30 11:58:37.463514
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-30 11:58:44.833428 2024-07-30 11:58:37.060907 2 66.47 al_loss false 2024-07-30 11:58:45.034361 2024-07-30 11:58:36.311488 2 74.55 al_rtt false 2024-07-30 11:58:43.932000 2024-07-30 11:58:37.463514 2 55.30
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.000518 0.000121 0.000000 100/100 2024-07-30 11:58:44.833428 2024-07-30 11:58:37.060907 A al_loss false 0.000518 0.000121 0.000000 100/100 2024-07-30 11:58:45.034361 2024-07-30 11:58:36.311488 A al_rtt false 0.000518 0.000121 0.000000 100/100 2024-07-30 11:58:43.932000 2024-07-30 11:58:37.463514
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-30 11:58:44.833428 2024-07-30 11:58:37.060907 2 44.61 al_loss false 2024-07-30 11:58:45.034361 2024-07-30 11:58:36.311488 2 50.05 al_rtt true 2024-07-30 11:58:48.239377 2024-07-30 11:58:43.932000 3 54.73
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.765530 0.009145 0.000000 100/100 2024-07-30 11:58:44.833428 2024-07-30 11:58:37.060907 A al_loss false 0.765530 0.009145 0.000000 100/100 2024-07-30 11:58:45.034361 2024-07-30 11:58:36.311488 A al_rtt true 0.765530 0.009145 0.000000 100/100 2024-07-30 11:58:48.239377 2024-07-30 11:58:43.932000
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-30 11:58:44.833428 2024-07-30 11:58:37.060907 2 33.71 al_loss false 2024-07-30 11:58:56.609970 2024-07-30 11:58:52.096486 4 57.39 al_rtt false 2024-07-30 11:58:56.107784 2024-07-30 11:58:48.239377 4 62.17
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.000546 0.000087 0.000000 100/100 2024-07-30 11:58:44.833428 2024-07-30 11:58:37.060907 A al_loss false 0.000546 0.000087 0.000000 100/100 2024-07-30 11:58:56.609970 2024-07-30 11:58:52.096486 A al_rtt false 0.000546 0.000087 0.000000 100/100 2024-07-30 11:58:56.107784 2024-07-30 11:58:48.239377
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-30 11:59:00.179070 2024-07-30 11:58:44.833428 3 35.61 al_loss false 2024-07-30 11:58:56.609970 2024-07-30 11:58:52.096486 4 46.00 al_rtt false 2024-07-30 11:58:56.107784 2024-07-30 11:58:48.239377 4 49.83
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.180754 0.266644 0.000000 100/100 2024-07-30 11:59:00.179070 2024-07-30 11:58:44.833428 A al_loss false 0.180754 0.266644 0.000000 100/100 2024-07-30 11:58:56.609970 2024-07-30 11:58:52.096486 A al_rtt false 0.180754 0.266644 0.000000 100/100 2024-07-30 11:58:56.107784 2024-07-30 11:58:48.239377
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-30 11:59:07.436389 2024-07-30 11:59:00.179070 4 43.73 al_loss false 2024-07-30 11:58:56.609970 2024-07-30 11:58:52.096486 4 38.51 al_rtt false 2024-07-30 11:59:05.587799 2024-07-30 11:59:03.013818 6 49.20
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.000468 0.000124 0.000000 100/100 2024-07-30 11:59:07.436389 2024-07-30 11:59:00.179070 A al_loss false 0.000468 0.000124 0.000000 100/100 2024-07-30 11:58:56.609970 2024-07-30 11:58:52.096486 A al_rtt false 0.000468 0.000124 0.000000 100/100 2024-07-30 11:59:05.587799 2024-07-30 11:59:03.013818
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-30 11:59:21.073098 2024-07-30 11:59:16.058293 2 75.42 al_rtt false 2024-07-30 11:59:20.780010 2024-07-30 11:59:16.809480 2 59.74
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.021997 0.005006 0.000000 100/100 A al_loss false 0.021997 0.005006 0.000000 100/100 2024-07-30 11:59:21.073098 2024-07-30 11:59:16.058293 A al_rtt false 0.021997 0.005006 0.000000 100/100 2024-07-30 11:59:20.780010 2024-07-30 11:59:16.809480
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-30 11:59:24.177653 1 23.69 al_loss true 2024-07-30 11:59:23.176737 2024-07-30 11:59:21.073098 3 72.34 al_rtt true 2024-07-30 11:59:24.728989 2024-07-30 11:59:20.780010 3 51.35
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.480263 0.439809 48.000000 100/100 2024-07-30 11:59:24.177653 A al_loss true 0.480263 0.439809 48.000000 100/100 2024-07-30 11:59:23.176737 2024-07-30 11:59:21.073098 A al_rtt true 0.480263 0.439809 48.000000 100/100 2024-07-30 11:59:24.728989 2024-07-30 11:59:20.780010
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-30 11:59:31.953339 2024-07-30 11:59:24.177653 2 43.27 al_loss false 2024-07-30 11:59:32.048540 2024-07-30 11:59:23.176737 4 77.28 al_rtt false 2024-07-30 11:59:31.299632 2024-07-30 11:59:24.728989 4 58.68
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.000511 0.000160 0.000000 100/100 2024-07-30 11:59:31.953339 2024-07-30 11:59:24.177653 A al_loss false 0.000511 0.000160 0.000000 100/100 2024-07-30 11:59:32.048540 2024-07-30 11:59:23.176737 A al_rtt false 0.000511 0.000160 0.000000 100/100 2024-07-30 11:59:31.299632 2024-07-30 11:59:24.728989
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-30 11:59:31.953339 2024-07-30 11:59:24.177653 2 32.88 al_loss false 2024-07-30 11:59:32.048540 2024-07-30 11:59:23.176737 4 58.74 al_rtt true 2024-07-30 11:59:35.305793 2024-07-30 11:59:31.299632 5 57.61
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.765560 0.009152 0.000000 100/100 2024-07-30 11:59:31.953339 2024-07-30 11:59:24.177653 A al_loss false 0.765560 0.009152 0.000000 100/100 2024-07-30 11:59:32.048540 2024-07-30 11:59:23.176737 A al_rtt true 0.765560 0.009152 0.000000 100/100 2024-07-30 11:59:35.305793 2024-07-30 11:59:31.299632
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-30 11:59:31.953339 2024-07-30 11:59:24.177653 2 26.59 al_loss false 2024-07-30 11:59:43.671708 2024-07-30 11:59:39.171098 6 62.88 al_rtt false 2024-07-30 11:59:43.171458 2024-07-30 11:59:35.305793 6 62.95
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.000224 0.000058 0.000000 100/100 2024-07-30 11:59:31.953339 2024-07-30 11:59:24.177653 A al_loss false 0.000224 0.000058 0.000000 100/100 2024-07-30 11:59:43.671708 2024-07-30 11:59:39.171098 A al_rtt false 0.000224 0.000058 0.000000 100/100 2024-07-30 11:59:43.171458 2024-07-30 11:59:35.305793
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-30 11:59:46.875917 2024-07-30 11:59:31.953339 3 30.28 al_loss false 2024-07-30 11:59:43.671708 2024-07-30 11:59:39.171098 6 52.63 al_rtt true 2024-07-30 11:59:49.666140 2024-07-30 11:59:43.171458 7 52.73
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.202449 0.267843 0.000000 100/100 2024-07-30 11:59:46.875917 2024-07-30 11:59:31.953339 A al_loss false 0.202449 0.267843 0.000000 100/100 2024-07-30 11:59:43.671708 2024-07-30 11:59:39.171098 A al_rtt true 0.202449 0.267843 0.000000 100/100 2024-07-30 11:59:49.666140 2024-07-30 11:59:43.171458
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-30 11:59:53.998295 2024-07-30 11:59:46.875917 4 36.76 al_loss false 2024-07-30 11:59:54.949904 2024-07-30 11:59:51.086380 8 54.90 al_rtt false 2024-07-30 11:59:52.191259 2024-07-30 11:59:49.666140 8 51.65
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.000536 0.000160 0.000000 100/100 2024-07-30 11:59:53.998295 2024-07-30 11:59:46.875917 A al_loss false 0.000536 0.000160 0.000000 100/100 2024-07-30 11:59:54.949904 2024-07-30 11:59:51.086380 A al_rtt false 0.000536 0.000160 0.000000 100/100 2024-07-30 11:59:52.191259 2024-07-30 11:59:49.666140
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-30 12:00:07.781960 2024-07-30 12:00:03.077943 2 70.63 al_rtt false 2024-07-30 12:00:07.738583 2024-07-30 12:00:03.828067 2 58.74
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.017736 0.004539 0.000000 100/100 A al_loss false 0.017736 0.004539 0.000000 100/100 2024-07-30 12:00:07.781960 2024-07-30 12:00:03.077943 A al_rtt false 0.017736 0.004539 0.000000 100/100 2024-07-30 12:00:07.738583 2024-07-30 12:00:03.828067
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-30 12:00:11.137571 1 24.06 al_loss true 2024-07-30 12:00:10.536067 2024-07-30 12:00:07.781960 3 66.94 al_rtt true 2024-07-30 12:00:11.937269 2024-07-30 12:00:07.738583 3 49.21
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.420329 0.439792 42.000000 100/100 2024-07-30 12:00:11.137571 A al_loss true 0.420329 0.439792 42.000000 100/100 2024-07-30 12:00:10.536067 2024-07-30 12:00:07.781960 A al_rtt true 0.420329 0.439792 42.000000 100/100 2024-07-30 12:00:11.937269 2024-07-30 12:00:07.738583
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-30 12:00:18.964621 2024-07-30 12:00:11.137571 2 43.55 al_loss false 2024-07-30 12:00:19.166493 2024-07-30 12:00:10.536067 4 74.17 al_rtt false 2024-07-30 12:00:18.275705 2024-07-30 12:00:11.937269 4 57.02
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.000590 0.000168 0.000000 100/100 2024-07-30 12:00:18.964621 2024-07-30 12:00:11.137571 A al_loss false 0.000590 0.000168 0.000000 100/100 2024-07-30 12:00:19.166493 2024-07-30 12:00:10.536067 A al_rtt false 0.000590 0.000168 0.000000 100/100 2024-07-30 12:00:18.275705 2024-07-30 12:00:11.937269
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-30 12:00:18.964621 2024-07-30 12:00:11.137571 2 33.06 al_loss false 2024-07-30 12:00:19.166493 2024-07-30 12:00:10.536067 4 56.30 al_rtt true 2024-07-30 12:00:22.321260 2024-07-30 12:00:18.275705 5 56.39
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.774675 0.009151 0.000000 100/100 2024-07-30 12:00:18.964621 2024-07-30 12:00:11.137571 A al_loss false 0.774675 0.009151 0.000000 100/100 2024-07-30 12:00:19.166493 2024-07-30 12:00:10.536067 A al_rtt true 0.774675 0.009151 0.000000 100/100 2024-07-30 12:00:22.321260 2024-07-30 12:00:18.275705
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-30 12:00:18.964621 2024-07-30 12:00:11.137571 2 26.75 al_loss false 2024-07-30 12:00:30.692573 2024-07-30 12:00:26.181861 6 60.98 al_rtt false 2024-07-30 12:00:30.191000 2024-07-30 12:00:22.321260 6 61.92
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.000118 0.000000 100/100 2024-07-30 12:00:18.964621 2024-07-30 12:00:11.137571 A al_loss false 0.000469 0.000118 0.000000 100/100 2024-07-30 12:00:30.692573 2024-07-30 12:00:26.181861 A al_rtt false 0.000469 0.000118 0.000000 100/100 2024-07-30 12:00:30.191000 2024-07-30 12:00:22.321260
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-30 12:00:34.175327 2024-07-30 12:00:18.964621 3 29.73 al_loss false 2024-07-30 12:00:30.692573 2024-07-30 12:00:26.181861 6 50.97 al_rtt false 2024-07-30 12:00:30.191000 2024-07-30 12:00:22.321260 6 51.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.138661 0.226720 0.000000 100/100 2024-07-30 12:00:34.175327 2024-07-30 12:00:18.964621 A al_loss false 0.138661 0.226720 0.000000 100/100 2024-07-30 12:00:30.692573 2024-07-30 12:00:26.181861 A al_rtt false 0.138661 0.226720 0.000000 100/100 2024-07-30 12:00:30.191000 2024-07-30 12:00:22.321260
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-30 12:00:41.270772 2024-07-30 12:00:34.175327 4 36.75 al_loss false 2024-07-30 12:00:41.671114 2024-07-30 12:00:38.063044 8 52.83 al_rtt false 2024-07-30 12:00:30.191000 2024-07-30 12:00:22.321260 6 44.62
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.000554 0.000160 0.000000 100/100 2024-07-30 12:00:41.270772 2024-07-30 12:00:34.175327 A al_loss false 0.000554 0.000160 0.000000 100/100 2024-07-30 12:00:41.671114 2024-07-30 12:00:38.063044 A al_rtt false 0.000554 0.000160 0.000000 100/100 2024-07-30 12:00:30.191000 2024-07-30 12:00:22.321260
Note
The previous command output should show the alarms are deactivated (since the network quality is good).