Check Icmp Operation
This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the ICMP protocol.
Test IPv4 Destination
Description
In this scenario, ICMP NSM operations are configured in DUT0 (using an IPv4 destination address).
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.215.200.100/24 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 interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A type icmp 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.000028 0.000007 0.000000 6/100 A al_loss false 0.000028 0.000007 0.000000 6/100 A al_rtt false 0.000028 0.000007 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-17 17:10:50.786040 1 49.05 al_loss true 2024-07-17 17:10:50.474269 1 54.20 al_rtt true 2024-07-17 17:10:51.924214 1 30.40
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.370261 0.339907 37.000000 100/100 2024-07-17 17:10:50.786040 A al_loss true 0.370261 0.339907 37.000000 100/100 2024-07-17 17:10:50.474269 A al_rtt true 0.370261 0.339907 37.000000 100/100 2024-07-17 17:10:51.924214
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-17 17:10:58.843017 2024-07-17 17:10:50.786040 2 68.33 al_loss false 2024-07-17 17:10:58.943116 2024-07-17 17:10:50.474269 2 71.84 al_rtt false 2024-07-17 17:10:58.092694 2024-07-17 17:10:51.924214 2 52.34
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.000536 0.000113 0.000000 100/100 2024-07-17 17:10:58.843017 2024-07-17 17:10:50.786040 A al_loss false 0.000536 0.000113 0.000000 100/100 2024-07-17 17:10:58.943116 2024-07-17 17:10:50.474269 A al_rtt false 0.000536 0.000113 0.000000 100/100 2024-07-17 17:10:58.092694 2024-07-17 17:10:51.924214
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-17 17:10:58.843017 2024-07-17 17:10:50.786040 2 46.05 al_loss false 2024-07-17 17:10:58.943116 2024-07-17 17:10:50.474269 2 48.41 al_rtt true 2024-07-17 17:11:02.106679 2024-07-17 17:10:58.092694 3 52.84
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.765438 0.009125 0.000000 100/100 2024-07-17 17:10:58.843017 2024-07-17 17:10:50.786040 A al_loss false 0.765438 0.009125 0.000000 100/100 2024-07-17 17:10:58.943116 2024-07-17 17:10:50.474269 A al_rtt true 0.765438 0.009125 0.000000 100/100 2024-07-17 17:11:02.106679 2024-07-17 17:10:58.092694
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-17 17:10:58.843017 2024-07-17 17:10:50.786040 2 34.72 al_loss false 2024-07-17 17:11:10.586658 2024-07-17 17:11:06.063915 4 55.99 al_rtt false 2024-07-17 17:11:10.091548 2024-07-17 17:11:02.106679 4 61.00
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.000467 0.000144 0.000000 100/100 2024-07-17 17:10:58.843017 2024-07-17 17:10:50.786040 A al_loss false 0.000467 0.000144 0.000000 100/100 2024-07-17 17:11:10.586658 2024-07-17 17:11:06.063915 A al_rtt false 0.000467 0.000144 0.000000 100/100 2024-07-17 17:11:10.091548 2024-07-17 17:11:02.106679
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-17 17:11:14.570550 2024-07-17 17:10:58.843017 3 34.85 al_loss false 2024-07-17 17:11:10.586658 2024-07-17 17:11:06.063915 4 44.96 al_rtt false 2024-07-17 17:11:10.091548 2024-07-17 17:11:02.106679 4 48.98
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.174019 0.251063 0.000000 100/100 2024-07-17 17:11:14.570550 2024-07-17 17:10:58.843017 A al_loss false 0.174019 0.251063 0.000000 100/100 2024-07-17 17:11:10.586658 2024-07-17 17:11:06.063915 A al_rtt false 0.174019 0.251063 0.000000 100/100 2024-07-17 17:11:10.091548 2024-07-17 17:11:02.106679
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-17 17:11:21.666768 2024-07-17 17:11:14.570550 4 43.83 al_loss false 2024-07-17 17:11:21.869666 2024-07-17 17:11:17.860194 6 49.18 al_rtt false 2024-07-17 17:11:20.006664 2024-07-17 17:11:17.409669 6 48.46
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.000390 0.000116 0.000000 100/100 2024-07-17 17:11:21.666768 2024-07-17 17:11:14.570550 A al_loss false 0.000390 0.000116 0.000000 100/100 2024-07-17 17:11:21.869666 2024-07-17 17:11:17.860194 A al_rtt false 0.000390 0.000116 0.000000 100/100 2024-07-17 17:11:20.006664 2024-07-17 17:11:17.409669
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, ICMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address).
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.215.200.100/24 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 interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A type icmp 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.000026 0.000009 0.000000 7/100 A al_loss false 0.000026 0.000009 0.000000 7/100 A al_rtt false 0.000026 0.000009 0.000000 7/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-17 17:11:32.823442 1 54.40 al_loss true 2024-07-17 17:11:32.525013 1 59.19 al_rtt true 2024-07-17 17:11:33.725208 1 39.68
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.470245 0.439841 47.000000 100/100 2024-07-17 17:11:32.823442 A al_loss true 0.470245 0.439841 47.000000 100/100 2024-07-17 17:11:32.525013 A al_rtt true 0.470245 0.439841 47.000000 100/100 2024-07-17 17:11:33.725208
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-17 17:11:40.944189 2024-07-17 17:11:32.823442 2 68.42 al_loss false 2024-07-17 17:11:41.203441 2024-07-17 17:11:32.525013 2 73.07 al_rtt false 2024-07-17 17:11:40.406026 2024-07-17 17:11:33.725208 2 56.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.000432 0.000108 0.000000 100/100 2024-07-17 17:11:40.944189 2024-07-17 17:11:32.823442 A al_loss false 0.000432 0.000108 0.000000 100/100 2024-07-17 17:11:41.203441 2024-07-17 17:11:32.525013 A al_rtt false 0.000432 0.000108 0.000000 100/100 2024-07-17 17:11:40.406026 2024-07-17 17:11:33.725208
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-17 17:11:40.944189 2024-07-17 17:11:32.823442 2 45.98 al_loss false 2024-07-17 17:11:41.203441 2024-07-17 17:11:32.525013 2 49.11 al_rtt true 2024-07-17 17:11:44.549841 2024-07-17 17:11:40.406026 3 55.58
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.774484 0.009129 0.000000 100/100 2024-07-17 17:11:40.944189 2024-07-17 17:11:32.823442 A al_loss false 0.774484 0.009129 0.000000 100/100 2024-07-17 17:11:41.203441 2024-07-17 17:11:32.525013 A al_rtt true 0.774484 0.009129 0.000000 100/100 2024-07-17 17:11:44.549841 2024-07-17 17:11:40.406026
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-17 17:11:40.944189 2024-07-17 17:11:32.823442 2 34.38 al_loss false 2024-07-17 17:11:53.023993 2024-07-17 17:11:48.516893 4 55.81 al_rtt false 2024-07-17 17:11:52.519672 2024-07-17 17:11:44.549841 4 62.02
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.000455 0.000147 0.000000 100/100 2024-07-17 17:11:40.944189 2024-07-17 17:11:32.823442 A al_loss false 0.000455 0.000147 0.000000 100/100 2024-07-17 17:11:53.023993 2024-07-17 17:11:48.516893 A al_rtt false 0.000455 0.000147 0.000000 100/100 2024-07-17 17:11:52.519672 2024-07-17 17:11:44.549841
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-17 17:11:56.863377 2024-07-17 17:11:40.944189 3 36.21 al_loss false 2024-07-17 17:11:53.023993 2024-07-17 17:11:48.516893 4 44.93 al_rtt false 2024-07-17 17:11:52.519672 2024-07-17 17:11:44.549841 4 49.93
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.171243 0.247132 0.000000 100/100 2024-07-17 17:11:56.863377 2024-07-17 17:11:40.944189 A al_loss false 0.171243 0.247132 0.000000 100/100 2024-07-17 17:11:53.023993 2024-07-17 17:11:48.516893 A al_rtt false 0.171243 0.247132 0.000000 100/100 2024-07-17 17:11:52.519672 2024-07-17 17:11:44.549841
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-17 17:12:04.294006 2024-07-17 17:11:56.863377 4 44.36 al_loss false 2024-07-17 17:12:04.695687 2024-07-17 17:12:00.844034 6 48.59 al_rtt false 2024-07-17 17:12:03.146397 2024-07-17 17:12:00.207885 6 50.17
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.000387 0.000122 0.000000 100/100 2024-07-17 17:12:04.294006 2024-07-17 17:11:56.863377 A al_loss false 0.000387 0.000122 0.000000 100/100 2024-07-17 17:12:04.695687 2024-07-17 17:12:00.844034 A al_rtt false 0.000387 0.000122 0.000000 100/100 2024-07-17 17:12:03.146397 2024-07-17 17:12:00.207885
Note
The previous command output should show the alarms are deactivated (since the network quality is good).
Test IPv6 Destination
Description
In this scenario, ICMP NSM operations are configured in DUT0 (using an IPv6 destination address).
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address '10::3/64' 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 interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A type icmp 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-17 17:12:17.077517 2024-07-17 17:12:11.960566 2 76.11 al_rtt false 2024-07-17 17:12:16.724825 2024-07-17 17:12:12.711027 2 59.73
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.014342 0.004116 0.000000 100/100 A al_loss false 0.014342 0.004116 0.000000 100/100 2024-07-17 17:12:17.077517 2024-07-17 17:12:11.960566 A al_rtt false 0.014342 0.004116 0.000000 100/100 2024-07-17 17:12:16.724825 2024-07-17 17:12:12.711027
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-17 17:12:19.979873 1 25.02 al_loss true 2024-07-17 17:12:19.477611 2024-07-17 17:12:17.077517 3 70.18 al_rtt true 2024-07-17 17:12:21.487877 2024-07-17 17:12:16.724825 3 45.18
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.380274 0.489781 38.000000 100/100 2024-07-17 17:12:19.979873 A al_loss true 0.380274 0.489781 38.000000 100/100 2024-07-17 17:12:19.477611 2024-07-17 17:12:17.077517 A al_rtt true 0.380274 0.489781 38.000000 100/100 2024-07-17 17:12:21.487877 2024-07-17 17:12:16.724825
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-17 17:12:28.253201 2024-07-17 17:12:19.979873 2 45.76 al_loss false 2024-07-17 17:12:28.198158 2024-07-17 17:12:19.477611 4 76.55 al_rtt false 2024-07-17 17:12:27.450533 2024-07-17 17:12:21.487877 4 55.20
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.000440 0.000135 0.000000 100/100 2024-07-17 17:12:28.253201 2024-07-17 17:12:19.979873 A al_loss false 0.000440 0.000135 0.000000 100/100 2024-07-17 17:12:28.198158 2024-07-17 17:12:19.477611 A al_rtt false 0.000440 0.000135 0.000000 100/100 2024-07-17 17:12:27.450533 2024-07-17 17:12:21.487877
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-17 17:12:28.253201 2024-07-17 17:12:19.979873 2 34.63 al_loss false 2024-07-17 17:12:28.198158 2024-07-17 17:12:19.477611 4 57.93 al_rtt true 2024-07-17 17:12:31.456313 2024-07-17 17:12:27.450533 5 54.67
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.765497 0.009143 0.000000 100/100 2024-07-17 17:12:28.253201 2024-07-17 17:12:19.979873 A al_loss false 0.765497 0.009143 0.000000 100/100 2024-07-17 17:12:28.198158 2024-07-17 17:12:19.477611 A al_rtt true 0.765497 0.009143 0.000000 100/100 2024-07-17 17:12:31.456313 2024-07-17 17:12:27.450533
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-17 17:12:28.253201 2024-07-17 17:12:19.979873 2 28.03 al_loss false 2024-07-17 17:12:39.874051 2024-07-17 17:12:35.372942 6 62.14 al_rtt false 2024-07-17 17:12:39.372913 2024-07-17 17:12:31.456313 6 60.64
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.000130 0.000000 100/100 2024-07-17 17:12:28.253201 2024-07-17 17:12:19.979873 A al_loss false 0.000422 0.000130 0.000000 100/100 2024-07-17 17:12:39.874051 2024-07-17 17:12:35.372942 A al_rtt false 0.000422 0.000130 0.000000 100/100 2024-07-17 17:12:39.372913 2024-07-17 17:12:31.456313
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-17 17:12:43.092145 2024-07-17 17:12:28.253201 3 31.38 al_loss false 2024-07-17 17:12:39.874051 2024-07-17 17:12:35.372942 6 52.07 al_rtt true 2024-07-17 17:12:45.276021 2024-07-17 17:12:39.372913 7 52.50
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.226187 0.309904 0.000000 100/100 2024-07-17 17:12:43.092145 2024-07-17 17:12:28.253201 A al_loss false 0.226187 0.309904 0.000000 100/100 2024-07-17 17:12:39.874051 2024-07-17 17:12:35.372942 A al_rtt true 0.226187 0.309904 0.000000 100/100 2024-07-17 17:12:45.276021 2024-07-17 17:12:39.372913
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-17 17:12:51.101255 2024-07-17 17:12:43.092145 4 39.74 al_loss false 2024-07-17 17:12:51.149635 2024-07-17 17:12:47.397923 8 53.92 al_rtt false 2024-07-17 17:12:49.194715 2024-07-17 17:12:45.276021 8 53.24
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.000429 0.000105 0.000000 100/100 2024-07-17 17:12:51.101255 2024-07-17 17:12:43.092145 A al_loss false 0.000429 0.000105 0.000000 100/100 2024-07-17 17:12:51.149635 2024-07-17 17:12:47.397923 A al_rtt false 0.000429 0.000105 0.000000 100/100 2024-07-17 17:12:49.194715 2024-07-17 17:12:45.276021
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, ICMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address).
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address '10::3/64' 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 interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A type icmp 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-17 17:13:04.995642 2024-07-17 17:13:00.283580 2 70.04 al_rtt false 2024-07-17 17:13:04.953115 2024-07-17 17:13:01.042242 2 58.17
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.018148 0.004601 0.000000 100/100 A al_loss false 0.018148 0.004601 0.000000 100/100 2024-07-17 17:13:04.995642 2024-07-17 17:13:00.283580 A al_rtt false 0.018148 0.004601 0.000000 100/100 2024-07-17 17:13:04.953115 2024-07-17 17:13:01.042242
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-17 17:13:07.849327 1 28.23 al_loss true 2024-07-17 17:13:07.649640 2024-07-17 17:13:04.995642 3 67.77 al_rtt true 2024-07-17 17:13:09.154009 2024-07-17 17:13:04.953115 3 49.22
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.457491 0.323795 39.000000 100/100 2024-07-17 17:13:07.849327 A al_loss true 0.457491 0.323795 39.000000 100/100 2024-07-17 17:13:07.649640 2024-07-17 17:13:04.995642 A al_rtt true 0.457491 0.323795 39.000000 100/100 2024-07-17 17:13:09.154009 2024-07-17 17:13:04.953115
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-17 17:13:16.523515 2024-07-17 17:13:07.849327 2 47.89 al_loss false 2024-07-17 17:13:16.482634 2024-07-17 17:13:07.649640 4 74.75 al_rtt false 2024-07-17 17:13:15.575009 2024-07-17 17:13:09.154009 4 57.03
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.000408 0.000127 0.000000 100/100 2024-07-17 17:13:16.523515 2024-07-17 17:13:07.849327 A al_loss false 0.000408 0.000127 0.000000 100/100 2024-07-17 17:13:16.482634 2024-07-17 17:13:07.649640 A al_rtt false 0.000408 0.000127 0.000000 100/100 2024-07-17 17:13:15.575009 2024-07-17 17:13:09.154009
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-17 17:13:16.523515 2024-07-17 17:13:07.849327 2 36.23 al_loss false 2024-07-17 17:13:16.482634 2024-07-17 17:13:07.649640 4 56.55 al_rtt true 2024-07-17 17:13:19.786761 2024-07-17 17:13:15.575009 5 56.09
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.774465 0.009139 0.000000 100/100 2024-07-17 17:13:16.523515 2024-07-17 17:13:07.849327 A al_loss false 0.774465 0.009139 0.000000 100/100 2024-07-17 17:13:16.482634 2024-07-17 17:13:07.649640 A al_rtt true 0.774465 0.009139 0.000000 100/100 2024-07-17 17:13:19.786761 2024-07-17 17:13:15.575009
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-17 17:13:16.523515 2024-07-17 17:13:07.849327 2 29.27 al_loss false 2024-07-17 17:13:28.253631 2024-07-17 17:13:23.739134 6 60.92 al_rtt false 2024-07-17 17:13:27.750149 2024-07-17 17:13:19.786761 6 61.73
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.000511 0.000149 0.000000 100/100 2024-07-17 17:13:16.523515 2024-07-17 17:13:07.849327 A al_loss false 0.000511 0.000149 0.000000 100/100 2024-07-17 17:13:28.253631 2024-07-17 17:13:23.739134 A al_rtt false 0.000511 0.000149 0.000000 100/100 2024-07-17 17:13:27.750149 2024-07-17 17:13:19.786761
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-17 17:13:31.274435 2024-07-17 17:13:16.523515 3 33.18 al_loss false 2024-07-17 17:13:28.253631 2024-07-17 17:13:23.739134 6 51.00 al_rtt true 2024-07-17 17:13:34.298863 2024-07-17 17:13:27.750149 7 51.81
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.208014 0.265319 0.000000 100/100 2024-07-17 17:13:31.274435 2024-07-17 17:13:16.523515 A al_loss false 0.208014 0.265319 0.000000 100/100 2024-07-17 17:13:28.253631 2024-07-17 17:13:23.739134 A al_rtt true 0.208014 0.265319 0.000000 100/100 2024-07-17 17:13:34.298863 2024-07-17 17:13:27.750149
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-17 17:13:39.227738 2024-07-17 17:13:31.274435 4 40.44 al_loss false 2024-07-17 17:13:39.787094 2024-07-17 17:13:35.765106 8 53.69 al_rtt false 2024-07-17 17:13:37.270738 2024-07-17 17:13:34.298863 8 51.72
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.000408 0.000134 0.000000 100/100 2024-07-17 17:13:39.227738 2024-07-17 17:13:31.274435 A al_loss false 0.000408 0.000134 0.000000 100/100 2024-07-17 17:13:39.787094 2024-07-17 17:13:35.765106 A al_rtt false 0.000408 0.000134 0.000000 100/100 2024-07-17 17:13:37.270738 2024-07-17 17:13:34.298863
Note
The previous command output should show the alarms are deactivated (since the network quality is good).