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.000024 0.000008 0.000000 7/100 A al_loss false 0.000024 0.000008 0.000000 7/100 A al_rtt false 0.000024 0.000008 0.000000 7/100
Note
The previous command output should show that NSM operations have been successfully created and that alarms are deactivated (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-10-07 12:59:01.338911793 +00:00 1 50.82 al_loss true 2024-10-07 12:59:00.762364858 +00:00 1 59.88 al_rtt true 2024-10-07 12:59:02.352131586 +00:00 1 35.04
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.440188 0.399886 44.000000 100/100 2024-10-07 12:59:01.338911793 +00:00 A al_loss true 0.440188 0.399886 44.000000 100/100 2024-10-07 12:59:00.762364858 +00:00 A al_rtt true 0.440188 0.399886 44.000000 100/100 2024-10-07 12:59:02.352131586 +00:00
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-10-07 12:59:09.608232091 +00:00 2024-10-07 12:59:01.338911793 +00:00 2 68.04 al_loss false 2024-10-07 12:59:09.701223720 +00:00 2024-10-07 12:59:00.762364858 +00:00 2 73.58 al_rtt false 2024-10-07 12:59:08.653518776 +00:00 2024-10-07 12:59:02.352131586 +00:00 2 51.88
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.000256 0.000041 0.000000 100/100 2024-10-07 12:59:09.608232091 +00:00 2024-10-07 12:59:01.338911793 +00:00 A al_loss false 0.000256 0.000041 0.000000 100/100 2024-10-07 12:59:09.701223720 +00:00 2024-10-07 12:59:00.762364858 +00:00 A al_rtt false 0.000256 0.000041 0.000000 100/100 2024-10-07 12:59:08.653518776 +00:00 2024-10-07 12:59:02.352131586 +00:00
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-10-07 12:59:09.608232091 +00:00 2024-10-07 12:59:01.338911793 +00:00 2 46.10 al_loss false 2024-10-07 12:59:09.701223720 +00:00 2024-10-07 12:59:00.762364858 +00:00 2 49.85 al_rtt true 2024-10-07 12:59:13.011692988 +00:00 2024-10-07 12:59:08.653518776 +00:00 3 52.53
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.783277 0.009062 0.000000 100/100 2024-10-07 12:59:09.608232091 +00:00 2024-10-07 12:59:01.338911793 +00:00 A al_loss false 0.783277 0.009062 0.000000 100/100 2024-10-07 12:59:09.701223720 +00:00 2024-10-07 12:59:00.762364858 +00:00 A al_rtt true 0.783277 0.009062 0.000000 100/100 2024-10-07 12:59:13.011692988 +00:00 2024-10-07 12:59:08.653518776 +00:00
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-10-07 12:59:09.608232091 +00:00 2024-10-07 12:59:01.338911793 +00:00 2 34.97 al_loss false 2024-10-07 12:59:21.567446011 +00:00 2024-10-07 12:59:17.065893443 +00:00 4 56.85 al_rtt false 2024-10-07 12:59:21.071974868 +00:00 2024-10-07 12:59:13.011692988 +00:00 4 60.75
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.000298 0.000064 0.000000 100/100 2024-10-07 12:59:09.608232091 +00:00 2024-10-07 12:59:01.338911793 +00:00 A al_loss false 0.000298 0.000064 0.000000 100/100 2024-10-07 12:59:21.567446011 +00:00 2024-10-07 12:59:17.065893443 +00:00 A al_rtt false 0.000298 0.000064 0.000000 100/100 2024-10-07 12:59:21.071974868 +00:00 2024-10-07 12:59:13.011692988 +00:00
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-10-07 12:59:24.791439624 +00:00 2024-10-07 12:59:09.608232091 +00:00 3 37.85 al_loss false 2024-10-07 12:59:21.567446011 +00:00 2024-10-07 12:59:17.065893443 +00:00 4 45.58 al_rtt false 2024-10-07 12:59:21.071974868 +00:00 2024-10-07 12:59:13.011692988 +00:00 4 48.71
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.158582 0.229532 0.000000 100/100 2024-10-07 12:59:24.791439624 +00:00 2024-10-07 12:59:09.608232091 +00:00 A al_loss false 0.158582 0.229532 0.000000 100/100 2024-10-07 12:59:21.567446011 +00:00 2024-10-07 12:59:17.065893443 +00:00 A al_rtt false 0.158582 0.229532 0.000000 100/100 2024-10-07 12:59:21.071974868 +00:00 2024-10-07 12:59:13.011692988 +00:00
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-10-07 12:59:32.832030351 +00:00 2024-10-07 12:59:24.791439624 +00:00 4 46.41 al_loss false 2024-10-07 12:59:32.936660982 +00:00 2024-10-07 12:59:29.193814884 +00:00 6 48.90 al_rtt false 2024-10-07 12:59:29.629366595 +00:00 2024-10-07 12:59:29.131991555 +00:00 6 42.29
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.000293 0.000060 0.000000 100/100 2024-10-07 12:59:32.832030351 +00:00 2024-10-07 12:59:24.791439624 +00:00 A al_loss false 0.000293 0.000060 0.000000 100/100 2024-10-07 12:59:32.936660982 +00:00 2024-10-07 12:59:29.193814884 +00:00 A al_rtt false 0.000293 0.000060 0.000000 100/100 2024-10-07 12:59:29.629366595 +00:00 2024-10-07 12:59:29.131991555 +00:00
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.000020 0.000003 0.000000 7/100 A al_loss false 0.000020 0.000003 0.000000 7/100 A al_rtt false 0.000020 0.000003 0.000000 7/100
Note
The previous command output should show that NSM operations have been successfully created and that alarms are deactivated (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-10-07 12:59:43.170390316 +00:00 1 52.99 al_loss true 2024-10-07 12:59:42.874582973 +00:00 1 57.65 al_rtt true 2024-10-07 12:59:44.372649956 +00:00 1 33.67
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.470158 0.449877 47.000000 100/100 2024-10-07 12:59:43.170390316 +00:00 A al_loss true 0.470158 0.449877 47.000000 100/100 2024-10-07 12:59:42.874582973 +00:00 A al_rtt true 0.470158 0.449877 47.000000 100/100 2024-10-07 12:59:44.372649956 +00:00
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-10-07 12:59:51.181383175 +00:00 2024-10-07 12:59:43.170390316 +00:00 2 67.16 al_loss false 2024-10-07 12:59:51.750817133 +00:00 2024-10-07 12:59:42.874582973 +00:00 2 74.35 al_rtt false 2024-10-07 12:59:50.579802463 +00:00 2024-10-07 12:59:44.372649956 +00:00 2 52.01
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.000338 0.000090 0.000000 100/100 2024-10-07 12:59:51.181383175 +00:00 2024-10-07 12:59:43.170390316 +00:00 A al_loss false 0.000338 0.000090 0.000000 100/100 2024-10-07 12:59:51.750817133 +00:00 2024-10-07 12:59:42.874582973 +00:00 A al_rtt false 0.000338 0.000090 0.000000 100/100 2024-10-07 12:59:50.579802463 +00:00 2024-10-07 12:59:44.372649956 +00:00
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-10-07 12:59:51.181383175 +00:00 2024-10-07 12:59:43.170390316 +00:00 2 45.28 al_loss false 2024-10-07 12:59:51.750817133 +00:00 2024-10-07 12:59:42.874582973 +00:00 2 50.15 al_rtt true 2024-10-07 12:59:54.838935962 +00:00 2024-10-07 12:59:50.579802463 +00:00 3 52.56
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.774301 0.009084 0.000000 100/100 2024-10-07 12:59:51.181383175 +00:00 2024-10-07 12:59:43.170390316 +00:00 A al_loss false 0.774301 0.009084 0.000000 100/100 2024-10-07 12:59:51.750817133 +00:00 2024-10-07 12:59:42.874582973 +00:00 A al_rtt true 0.774301 0.009084 0.000000 100/100 2024-10-07 12:59:54.838935962 +00:00 2024-10-07 12:59:50.579802463 +00:00
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-10-07 12:59:51.181383175 +00:00 2024-10-07 12:59:43.170390316 +00:00 2 34.29 al_loss false 2024-10-07 13:00:03.296351733 +00:00 2024-10-07 12:59:58.795664154 +00:00 4 57.23 al_rtt false 2024-10-07 13:00:02.801676138 +00:00 2024-10-07 12:59:54.838935962 +00:00 4 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.000295 0.000058 0.000000 100/100 2024-10-07 12:59:51.181383175 +00:00 2024-10-07 12:59:43.170390316 +00:00 A al_loss false 0.000295 0.000058 0.000000 100/100 2024-10-07 13:00:03.296351733 +00:00 2024-10-07 12:59:58.795664154 +00:00 A al_rtt false 0.000295 0.000058 0.000000 100/100 2024-10-07 13:00:02.801676138 +00:00 2024-10-07 12:59:54.838935962 +00:00
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-10-07 13:00:07.085552573 +00:00 2024-10-07 12:59:51.181383175 +00:00 3 36.03 al_loss false 2024-10-07 13:00:03.296351733 +00:00 2024-10-07 12:59:58.795664154 +00:00 4 45.42 al_rtt false 2024-10-07 13:00:02.801676138 +00:00 2024-10-07 12:59:54.838935962 +00:00 4 48.12
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.182076 0.304333 0.000000 100/100 2024-10-07 13:00:07.085552573 +00:00 2024-10-07 12:59:51.181383175 +00:00 A al_loss false 0.182076 0.304333 0.000000 100/100 2024-10-07 13:00:03.296351733 +00:00 2024-10-07 12:59:58.795664154 +00:00 A al_rtt false 0.182076 0.304333 0.000000 100/100 2024-10-07 13:00:02.801676138 +00:00 2024-10-07 12:59:54.838935962 +00:00
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-10-07 13:00:14.115704328 +00:00 2024-10-07 13:00:07.085552573 +00:00 4 42.80 al_loss false 2024-10-07 13:00:03.296351733 +00:00 2024-10-07 12:59:58.795664154 +00:00 4 38.05 al_rtt false 2024-10-07 13:00:12.065512201 +00:00 2024-10-07 13:00:10.163743704 +00:00 6 45.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.000281 0.000061 0.000000 100/100 2024-10-07 13:00:14.115704328 +00:00 2024-10-07 13:00:07.085552573 +00:00 A al_loss false 0.000281 0.000061 0.000000 100/100 2024-10-07 13:00:03.296351733 +00:00 2024-10-07 12:59:58.795664154 +00:00 A al_rtt false 0.000281 0.000061 0.000000 100/100 2024-10-07 13:00:12.065512201 +00:00 2024-10-07 13:00:10.163743704 +00:00
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-10-07 13:00:29.014122153 +00:00 2024-10-07 13:00:24.394229371 +00:00 2 68.54 al_rtt false 2024-10-07 13:00:28.495613505 +00:00 2024-10-07 13:00:25.155367595 +00:00 2 49.58
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.000265 0.000051 0.000000 100/100 A al_loss false 0.000265 0.000051 0.000000 100/100 2024-10-07 13:00:29.014122153 +00:00 2024-10-07 13:00:24.394229371 +00:00 A al_rtt false 0.000265 0.000051 0.000000 100/100 2024-10-07 13:00:28.495613505 +00:00 2024-10-07 13:00:25.155367595 +00:00
Note
The previous command output should show that NSM operations have been successfully created and that alarms are deactivated (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-10-07 13:00:32.053223277 +00:00 1 27.74 al_loss true 2024-10-07 13:00:31.950124187 +00:00 2024-10-07 13:00:29.014122153 +00:00 3 65.65 al_rtt true 2024-10-07 13:00:33.710365408 +00:00 2024-10-07 13:00:28.495613505 +00:00 3 41.27
Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ---------------------------------------------------------------------------------------------------------------------------------------------------- A al_jitter true 0.410175 0.429895 41.000000 100/100 2024-10-07 13:00:32.053223277 +00:00 A al_loss true 0.410175 0.429895 41.000000 100/100 2024-10-07 13:00:31.950124187 +00:00 2024-10-07 13:00:29.014122153 +00:00 A al_rtt true 0.410175 0.429895 41.000000 100/100 2024-10-07 13:00:33.710365408 +00:00 2024-10-07 13:00:28.495613505 +00:00
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-10-07 13:00:40.629113764 +00:00 2024-10-07 13:00:32.053223277 +00:00 2 47.28 al_loss false 2024-10-07 13:00:40.567390529 +00:00 2024-10-07 13:00:31.950124187 +00:00 4 73.01 al_rtt false 2024-10-07 13:00:39.710511549 +00:00 2024-10-07 13:00:33.710365408 +00:00 4 51.53
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.000316 0.000182 0.000000 100/100 2024-10-07 13:00:40.629113764 +00:00 2024-10-07 13:00:32.053223277 +00:00 A al_loss false 0.000316 0.000182 0.000000 100/100 2024-10-07 13:00:40.567390529 +00:00 2024-10-07 13:00:31.950124187 +00:00 A al_rtt false 0.000316 0.000182 0.000000 100/100 2024-10-07 13:00:39.710511549 +00:00 2024-10-07 13:00:33.710365408 +00:00
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-10-07 13:00:40.629113764 +00:00 2024-10-07 13:00:32.053223277 +00:00 2 35.77 al_loss false 2024-10-07 13:00:40.567390529 +00:00 2024-10-07 13:00:31.950124187 +00:00 4 55.22 al_rtt true 2024-10-07 13:00:43.921754857 +00:00 2024-10-07 13:00:39.710511549 +00:00 5 51.90
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.783277 0.009076 0.000000 100/100 2024-10-07 13:00:40.629113764 +00:00 2024-10-07 13:00:32.053223277 +00:00 A al_loss false 0.783277 0.009076 0.000000 100/100 2024-10-07 13:00:40.567390529 +00:00 2024-10-07 13:00:31.950124187 +00:00 A al_rtt true 0.783277 0.009076 0.000000 100/100 2024-10-07 13:00:43.921754857 +00:00 2024-10-07 13:00:39.710511549 +00:00
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-10-07 13:00:40.629113764 +00:00 2024-10-07 13:00:32.053223277 +00:00 2 28.94 al_loss false 2024-10-07 13:00:52.380791914 +00:00 2024-10-07 13:00:47.869814451 +00:00 6 59.89 al_rtt false 2024-10-07 13:00:51.887541011 +00:00 2024-10-07 13:00:43.921754857 +00:00 6 58.41
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.000274 0.000064 0.000000 100/100 2024-10-07 13:00:40.629113764 +00:00 2024-10-07 13:00:32.053223277 +00:00 A al_loss false 0.000274 0.000064 0.000000 100/100 2024-10-07 13:00:52.380791914 +00:00 2024-10-07 13:00:47.869814451 +00:00 A al_rtt false 0.000274 0.000064 0.000000 100/100 2024-10-07 13:00:51.887541011 +00:00 2024-10-07 13:00:43.921754857 +00:00
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-10-07 13:00:55.872710806 +00:00 2024-10-07 13:00:40.629113764 +00:00 3 31.59 al_loss false 2024-10-07 13:00:52.380791914 +00:00 2024-10-07 13:00:47.869814451 +00:00 6 50.07 al_rtt false 2024-10-07 13:00:51.887541011 +00:00 2024-10-07 13:00:43.921754857 +00:00 6 48.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.171620 0.245654 0.000000 100/100 2024-10-07 13:00:55.872710806 +00:00 2024-10-07 13:00:40.629113764 +00:00 A al_loss false 0.171620 0.245654 0.000000 100/100 2024-10-07 13:00:52.380791914 +00:00 2024-10-07 13:00:47.869814451 +00:00 A al_rtt false 0.171620 0.245654 0.000000 100/100 2024-10-07 13:00:51.887541011 +00:00 2024-10-07 13:00:43.921754857 +00:00
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-10-07 13:01:03.346027064 +00:00 2024-10-07 13:00:55.872710806 +00:00 4 39.07 al_loss false 2024-10-07 13:00:52.380791914 +00:00 2024-10-07 13:00:47.869814451 +00:00 6 43.21 al_rtt false 2024-10-07 13:01:00.544287195 +00:00 2024-10-07 13:00:59.638969010 +00:00 8 44.35
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.000274 0.000077 0.000000 100/100 2024-10-07 13:01:03.346027064 +00:00 2024-10-07 13:00:55.872710806 +00:00 A al_loss false 0.000274 0.000077 0.000000 100/100 2024-10-07 13:00:52.380791914 +00:00 2024-10-07 13:00:47.869814451 +00:00 A al_rtt false 0.000274 0.000077 0.000000 100/100 2024-10-07 13:01:00.544287195 +00:00 2024-10-07 13:00:59.638969010 +00:00
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-10-07 13:01:17.895789736 +00:00 2024-10-07 13:01:12.524177941 +00:00 2 68.58 al_rtt false 2024-10-07 13:01:17.425692686 +00:00 2024-10-07 13:01:13.271116849 +00:00 2 53.09
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.000256 0.000051 0.000000 100/100 A al_loss false 0.000256 0.000051 0.000000 100/100 2024-10-07 13:01:17.895789736 +00:00 2024-10-07 13:01:12.524177941 +00:00 A al_rtt false 0.000256 0.000051 0.000000 100/100 2024-10-07 13:01:17.425692686 +00:00 2024-10-07 13:01:13.271116849 +00:00
Note
The previous command output should show that NSM operations have been successfully created and that alarms are deactivated (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-10-07 13:01:21.492780555 +00:00 1 23.94 al_loss true 2024-10-07 13:01:20.939301615 +00:00 2024-10-07 13:01:17.895789736 +00:00 3 67.36 al_rtt true 2024-10-07 13:01:22.532258896 +00:00 2024-10-07 13:01:17.425692686 +00:00 3 46.78
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.430177 0.339902 43.000000 100/100 2024-10-07 13:01:21.492780555 +00:00 A al_loss true 0.430177 0.339902 43.000000 100/100 2024-10-07 13:01:20.939301615 +00:00 2024-10-07 13:01:17.895789736 +00:00 A al_rtt true 0.430177 0.339902 43.000000 100/100 2024-10-07 13:01:22.532258896 +00:00 2024-10-07 13:01:17.425692686 +00:00
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-10-07 13:01:29.802863952 +00:00 2024-10-07 13:01:21.492780555 +00:00 2 42.98 al_loss false 2024-10-07 13:01:29.849066669 +00:00 2024-10-07 13:01:20.939301615 +00:00 4 73.81 al_rtt false 2024-10-07 13:01:28.594665899 +00:00 2024-10-07 13:01:22.532258896 +00:00 4 52.82
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.000290 0.000066 0.000000 100/100 2024-10-07 13:01:29.802863952 +00:00 2024-10-07 13:01:21.492780555 +00:00 A al_loss false 0.000290 0.000066 0.000000 100/100 2024-10-07 13:01:29.849066669 +00:00 2024-10-07 13:01:20.939301615 +00:00 A al_rtt false 0.000290 0.000066 0.000000 100/100 2024-10-07 13:01:28.594665899 +00:00 2024-10-07 13:01:22.532258896 +00:00
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-10-07 13:01:29.802863952 +00:00 2024-10-07 13:01:21.492780555 +00:00 2 33.16 al_loss false 2024-10-07 13:01:29.849066669 +00:00 2024-10-07 13:01:20.939301615 +00:00 4 56.95 al_rtt true 2024-10-07 13:01:33.095123961 +00:00 2024-10-07 13:01:28.594665899 +00:00 5 53.11
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.774278 0.009062 0.000000 100/100 2024-10-07 13:01:29.802863952 +00:00 2024-10-07 13:01:21.492780555 +00:00 A al_loss false 0.774278 0.009062 0.000000 100/100 2024-10-07 13:01:29.849066669 +00:00 2024-10-07 13:01:20.939301615 +00:00 A al_rtt true 0.774278 0.009062 0.000000 100/100 2024-10-07 13:01:33.095123961 +00:00 2024-10-07 13:01:28.594665899 +00:00
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-10-07 13:01:29.802863952 +00:00 2024-10-07 13:01:21.492780555 +00:00 2 27.00 al_loss false 2024-10-07 13:01:41.612640006 +00:00 2024-10-07 13:01:37.101434042 +00:00 6 61.02 al_rtt false 2024-10-07 13:01:41.108844682 +00:00 2024-10-07 13:01:33.095123961 +00:00 6 59.21
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.000259 0.000065 0.000000 100/100 2024-10-07 13:01:29.802863952 +00:00 2024-10-07 13:01:21.492780555 +00:00 A al_loss false 0.000259 0.000065 0.000000 100/100 2024-10-07 13:01:41.612640006 +00:00 2024-10-07 13:01:37.101434042 +00:00 A al_rtt false 0.000259 0.000065 0.000000 100/100 2024-10-07 13:01:41.108844682 +00:00 2024-10-07 13:01:33.095123961 +00:00
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-10-07 13:01:44.242782986 +00:00 2024-10-07 13:01:29.802863952 +00:00 3 32.17 al_loss false 2024-10-07 13:01:41.612640006 +00:00 2024-10-07 13:01:37.101434042 +00:00 6 51.38 al_rtt true 2024-10-07 13:01:47.525195284 +00:00 2024-10-07 13:01:41.108844682 +00:00 7 50.31
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.217298 0.311665 0.000000 100/100 2024-10-07 13:01:44.242782986 +00:00 2024-10-07 13:01:29.802863952 +00:00 A al_loss false 0.217298 0.311665 0.000000 100/100 2024-10-07 13:01:41.612640006 +00:00 2024-10-07 13:01:37.101434042 +00:00 A al_rtt true 0.217298 0.311665 0.000000 100/100 2024-10-07 13:01:47.525195284 +00:00 2024-10-07 13:01:41.108844682 +00:00
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-10-07 13:01:51.378412092 +00:00 2024-10-07 13:01:44.242782986 +00:00 4 36.49 al_loss false 2024-10-07 13:01:41.612640006 +00:00 2024-10-07 13:01:37.101434042 +00:00 6 44.38 al_rtt false 2024-10-07 13:01:49.826819582 +00:00 2024-10-07 13:01:47.525195284 +00:00 8 48.50
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.000274 0.000059 0.000000 100/100 2024-10-07 13:01:51.378412092 +00:00 2024-10-07 13:01:44.242782986 +00:00 A al_loss false 0.000274 0.000059 0.000000 100/100 2024-10-07 13:01:41.612640006 +00:00 2024-10-07 13:01:37.101434042 +00:00 A al_rtt false 0.000274 0.000059 0.000000 100/100 2024-10-07 13:01:49.826819582 +00:00 2024-10-07 13:01:47.525195284 +00:00
Note
The previous command output should show the alarms are deactivated (since the network quality is good).