Check Udp Operation
This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the UDP SLA protocol. In addition, the UDP NSM responder service is configured.
Test IPv4 Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using an IPv4 destination address) and the UDP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.215.200.100/24 set service nsm responder type udp port 60000
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10.215.200.50/24 set service nsm operation A destination-address 10.215.200.100 set service nsm operation A type udp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 60000
Step 3: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 0 0.00 al_rtt false 0 0.00
Step 4: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
--------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled --------------------------------------------------------------------------------------------- A al_rtt false 0.000039 0.000006 0.000000 8/100 A al_loss false 0.000039 0.000006 0.000000 8/100 A al_jitter false 0.000039 0.000006 0.000000 8/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-06-20 17:59:53.165073 1 43.62 al_loss true 2024-06-20 17:59:52.554310 1 53.25 al_rtt true 2024-06-20 17:59:53.816667 1 33.43
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------ Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------ A al_rtt true 0.430260 0.409833 43.000000 100/100 2024-06-20 17:59:53.816667 A al_loss true 0.430260 0.409833 43.000000 100/100 2024-06-20 17:59:52.554310 A al_jitter true 0.430260 0.409833 43.000000 100/100 2024-06-20 17:59:53.165073
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:00:00.872815 2024-06-20 17:59:53.165073 2 62.80 al_loss false 2024-06-20 18:00:01.081880 2024-06-20 17:59:52.554310 2 69.51 al_rtt false 2024-06-20 18:00:00.172542 2024-06-20 17:59:53.816667 2 51.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_rtt false 0.000447 0.000053 0.000000 100/100 2024-06-20 18:00:00.172542 2024-06-20 17:59:53.816667 A al_loss false 0.000447 0.000053 0.000000 100/100 2024-06-20 18:00:01.081880 2024-06-20 17:59:52.554310 A al_jitter false 0.000447 0.000053 0.000000 100/100 2024-06-20 18:00:00.872815 2024-06-20 17:59:53.165073
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:00:00.872815 2024-06-20 17:59:53.165073 2 42.11 al_loss false 2024-06-20 18:00:01.081880 2024-06-20 17:59:52.554310 2 46.60 al_rtt true 2024-06-20 18:00:04.728012 2024-06-20 18:00:00.172542 3 51.96
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.801463 0.009067 0.000000 100/100 2024-06-20 18:00:04.728012 2024-06-20 18:00:00.172542 A al_loss false 0.801463 0.009067 0.000000 100/100 2024-06-20 18:00:01.081880 2024-06-20 17:59:52.554310 A al_jitter false 0.801463 0.009067 0.000000 100/100 2024-06-20 18:00:00.872815 2024-06-20 17:59:53.165073
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:00:00.872815 2024-06-20 17:59:53.165073 2 31.78 al_loss false 2024-06-20 18:00:13.444469 2024-06-20 18:00:08.949686 4 53.71 al_rtt false 2024-06-20 18:00:12.956320 2024-06-20 18:00:04.728012 4 60.16
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000449 0.000055 0.000000 100/100 2024-06-20 18:00:12.956320 2024-06-20 18:00:04.728012 A al_loss false 0.000449 0.000055 0.000000 100/100 2024-06-20 18:00:13.444469 2024-06-20 18:00:08.949686 A al_jitter false 0.000449 0.000055 0.000000 100/100 2024-06-20 18:00:00.872815 2024-06-20 17:59:53.165073
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-06-20 18:00:16.593204 2024-06-20 18:00:00.872815 3 36.28 al_loss false 2024-06-20 18:00:13.444469 2024-06-20 18:00:08.949686 4 42.97 al_rtt true 2024-06-20 18:00:19.438997 2024-06-20 18:00:12.956320 5 49.60
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.231011 0.316884 0.000000 100/100 2024-06-20 18:00:19.438997 2024-06-20 18:00:12.956320 A al_loss false 0.231011 0.316884 0.000000 100/100 2024-06-20 18:00:13.444469 2024-06-20 18:00:08.949686 A al_jitter true 0.231011 0.316884 0.000000 100/100 2024-06-20 18:00:16.593204 2024-06-20 18:00:00.872815
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:00:25.017650 2024-06-20 18:00:16.593204 4 44.40 al_loss false 2024-06-20 18:00:13.444469 2024-06-20 18:00:08.949686 4 35.85 al_rtt false 2024-06-20 18:00:23.080722 2024-06-20 18:00:19.438997 6 50.18
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000456 0.000055 0.000000 100/100 2024-06-20 18:00:23.080722 2024-06-20 18:00:19.438997 A al_loss false 0.000456 0.000055 0.000000 100/100 2024-06-20 18:00:13.444469 2024-06-20 18:00:08.949686 A al_jitter false 0.000456 0.000055 0.000000 100/100 2024-06-20 18:00:25.017650 2024-06-20 18:00:16.593204
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv4 FQDN Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address) and the UDP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.215.200.100/24 set service nsm responder type udp port 60000
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10.215.200.50/24 set service nsm operation A destination-address test.nsm.fqdn set service nsm operation A type udp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 60000 set service dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet 10.215.200.100
Step 3: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 0 0.00 al_rtt false 0 0.00
Step 4: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
--------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled --------------------------------------------------------------------------------------------- A al_rtt false 0.000041 0.000008 0.000000 9/100 A al_loss false 0.000041 0.000008 0.000000 9/100 A al_jitter false 0.000041 0.000008 0.000000 9/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-06-20 18:00:38.425646 1 53.40 al_loss true 2024-06-20 18:00:38.030670 1 59.47 al_rtt true 2024-06-20 18:00:39.533352 1 36.15
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------ Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------ A al_rtt true 0.450252 0.599729 45.000000 100/100 2024-06-20 18:00:39.533352 A al_loss true 0.450252 0.599729 45.000000 100/100 2024-06-20 18:00:38.030670 A al_jitter true 0.450252 0.599729 45.000000 100/100 2024-06-20 18:00:38.425646
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:00:46.892271 2024-06-20 18:00:38.425646 2 69.43 al_loss false 2024-06-20 18:00:46.842343 2024-06-20 18:00:38.030670 2 72.21 al_rtt false 2024-06-20 18:00:45.847374 2024-06-20 18:00:39.533352 2 51.76
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000445 0.000058 0.000000 100/100 2024-06-20 18:00:45.847374 2024-06-20 18:00:39.533352 A al_loss false 0.000445 0.000058 0.000000 100/100 2024-06-20 18:00:46.842343 2024-06-20 18:00:38.030670 A al_jitter false 0.000445 0.000058 0.000000 100/100 2024-06-20 18:00:46.892271 2024-06-20 18:00:38.425646
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:00:46.892271 2024-06-20 18:00:38.425646 2 46.43 al_loss false 2024-06-20 18:00:46.842343 2024-06-20 18:00:38.030670 2 48.30 al_rtt true 2024-06-20 18:00:50.498668 2024-06-20 18:00:45.847374 3 51.97
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.801489 0.009059 0.000000 100/100 2024-06-20 18:00:50.498668 2024-06-20 18:00:45.847374 A al_loss false 0.801489 0.009059 0.000000 100/100 2024-06-20 18:00:46.842343 2024-06-20 18:00:38.030670 A al_jitter false 0.801489 0.009059 0.000000 100/100 2024-06-20 18:00:46.892271 2024-06-20 18:00:38.425646
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:00:46.892271 2024-06-20 18:00:38.425646 2 35.21 al_loss false 2024-06-20 18:00:59.125415 2024-06-20 18:00:54.620845 4 55.36 al_rtt false 2024-06-20 18:00:58.614996 2024-06-20 18:00:50.498668 4 60.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_rtt false 0.000465 0.000060 0.000000 100/100 2024-06-20 18:00:58.614996 2024-06-20 18:00:50.498668 A al_loss false 0.000465 0.000060 0.000000 100/100 2024-06-20 18:00:59.125415 2024-06-20 18:00:54.620845 A al_jitter false 0.000465 0.000060 0.000000 100/100 2024-06-20 18:00:46.892271 2024-06-20 18:00:38.425646
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-06-20 18:01:03.240846 2024-06-20 18:00:46.892271 3 35.64 al_loss false 2024-06-20 18:00:59.125415 2024-06-20 18:00:54.620845 4 44.29 al_rtt false 2024-06-20 18:00:58.614996 2024-06-20 18:00:50.498668 4 48.00
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.173633 0.234520 0.000000 100/100 2024-06-20 18:00:58.614996 2024-06-20 18:00:50.498668 A al_loss false 0.173633 0.234520 0.000000 100/100 2024-06-20 18:00:59.125415 2024-06-20 18:00:54.620845 A al_jitter true 0.173633 0.234520 0.000000 100/100 2024-06-20 18:01:03.240846 2024-06-20 18:00:46.892271
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:01:10.094752 2024-06-20 18:01:03.240846 4 42.59 al_loss false 2024-06-20 18:00:59.125415 2024-06-20 18:00:54.620845 4 37.01 al_rtt false 2024-06-20 18:00:58.614996 2024-06-20 18:00:50.498668 4 40.11
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000454 0.000060 0.000000 100/100 2024-06-20 18:00:58.614996 2024-06-20 18:00:50.498668 A al_loss false 0.000454 0.000060 0.000000 100/100 2024-06-20 18:00:59.125415 2024-06-20 18:00:54.620845 A al_jitter false 0.000454 0.000060 0.000000 100/100 2024-06-20 18:01:10.094752 2024-06-20 18:01:03.240846
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv6 Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using an IPv6 destination address) and the UDP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10::3/64 set service nsm responder type udp port 60000
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10::2/64 set service nsm operation A destination-address 10::3 set service nsm operation A type udp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 60000
Step 3: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 2024-06-20 18:01:27.511438 2024-06-20 18:01:22.780332 2 67.90 al_rtt false 2024-06-20 18:01:27.458468 2024-06-20 18:01:23.539189 2 56.28
Step 4: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000641 0.000763 0.000000 100/100 2024-06-20 18:01:27.458468 2024-06-20 18:01:23.539189 A al_loss false 0.000641 0.000763 0.000000 100/100 2024-06-20 18:01:27.511438 2024-06-20 18:01:22.780332 A al_jitter false 0.000641 0.000763 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-06-20 18:01:30.753883 1 28.47 al_loss true 2024-06-20 18:01:30.703732 2024-06-20 18:01:27.511438 3 65.26 al_rtt true 2024-06-20 18:01:32.399851 2024-06-20 18:01:27.458468 3 45.98
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.480228 0.509785 48.000000 100/100 2024-06-20 18:01:32.399851 2024-06-20 18:01:27.458468 A al_loss true 0.480228 0.509785 48.000000 100/100 2024-06-20 18:01:30.703732 2024-06-20 18:01:27.511438 A al_jitter true 0.480228 0.509785 48.000000 100/100 2024-06-20 18:01:30.753883
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:01:39.862488 2024-06-20 18:01:30.753883 2 47.87 al_loss false 2024-06-20 18:01:39.962584 2024-06-20 18:01:30.703732 4 73.54 al_rtt false 2024-06-20 18:01:38.810824 2024-06-20 18:01:32.399851 4 54.31
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000435 0.000055 0.000000 100/100 2024-06-20 18:01:38.810824 2024-06-20 18:01:32.399851 A al_loss false 0.000435 0.000055 0.000000 100/100 2024-06-20 18:01:39.962584 2024-06-20 18:01:30.703732 A al_jitter false 0.000435 0.000055 0.000000 100/100 2024-06-20 18:01:39.862488 2024-06-20 18:01:30.753883
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:01:39.862488 2024-06-20 18:01:30.753883 2 36.39 al_loss false 2024-06-20 18:01:39.962584 2024-06-20 18:01:30.703732 4 55.89 al_rtt true 2024-06-20 18:01:43.373196 2024-06-20 18:01:38.810824 5 53.72
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.792459 0.009063 0.000000 100/100 2024-06-20 18:01:43.373196 2024-06-20 18:01:38.810824 A al_loss false 0.792459 0.009063 0.000000 100/100 2024-06-20 18:01:39.962584 2024-06-20 18:01:30.703732 A al_jitter false 0.792459 0.009063 0.000000 100/100 2024-06-20 18:01:39.862488 2024-06-20 18:01:30.753883
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:01:39.862488 2024-06-20 18:01:30.753883 2 29.46 al_loss false 2024-06-20 18:01:52.037660 2024-06-20 18:01:47.533437 6 59.82 al_rtt false 2024-06-20 18:01:51.543962 2024-06-20 18:01:43.373196 6 59.84
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000453 0.000056 0.000000 100/100 2024-06-20 18:01:51.543962 2024-06-20 18:01:43.373196 A al_loss false 0.000453 0.000056 0.000000 100/100 2024-06-20 18:01:52.037660 2024-06-20 18:01:47.533437 A al_jitter false 0.000453 0.000056 0.000000 100/100 2024-06-20 18:01:39.862488 2024-06-20 18:01:30.753883
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-06-20 18:01:55.541727 2024-06-20 18:01:39.862488 3 32.29 al_loss false 2024-06-20 18:01:52.037660 2024-06-20 18:01:47.533437 6 50.13 al_rtt true 2024-06-20 18:01:57.398250 2024-06-20 18:01:51.543962 7 52.73
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.242494 0.335106 0.000000 100/100 2024-06-20 18:01:57.398250 2024-06-20 18:01:51.543962 A al_loss false 0.242494 0.335106 0.000000 100/100 2024-06-20 18:01:52.037660 2024-06-20 18:01:47.533437 A al_jitter true 0.242494 0.335106 0.000000 100/100 2024-06-20 18:01:55.541727 2024-06-20 18:01:39.862488
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:02:02.669705 2024-06-20 18:01:55.541727 4 38.04 al_loss false 2024-06-20 18:02:03.322471 2024-06-20 18:01:59.800082 8 51.58 al_rtt false 2024-06-20 18:02:01.054765 2024-06-20 18:01:57.398250 8 51.91
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000452 0.000075 0.000000 100/100 2024-06-20 18:02:01.054765 2024-06-20 18:01:57.398250 A al_loss false 0.000452 0.000075 0.000000 100/100 2024-06-20 18:02:03.322471 2024-06-20 18:01:59.800082 A al_jitter false 0.000452 0.000075 0.000000 100/100 2024-06-20 18:02:02.669705 2024-06-20 18:01:55.541727
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv6 FQDN Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address) and the UDP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10::3/64 set service nsm responder type udp port 60000
Step 2: Set the following configuration in DUT0
:
set interfaces ethernet eth0 address 10::2/64 set service nsm operation A destination-address test.nsm.fqdn set service nsm operation A type udp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 60000 set service dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet 10::3
Step 3: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 2024-06-20 18:02:21.501216 2024-06-20 18:02:16.353014 2 72.02 al_rtt false 2024-06-20 18:02:21.106233 2024-06-20 18:02:17.084306 2 56.30
Step 4: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000570 0.000300 0.000000 100/100 2024-06-20 18:02:21.106233 2024-06-20 18:02:17.084306 A al_loss false 0.000570 0.000300 0.000000 100/100 2024-06-20 18:02:21.501216 2024-06-20 18:02:16.353014 A al_jitter false 0.000570 0.000300 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-06-20 18:02:24.762933 1 26.29 al_loss true 2024-06-20 18:02:24.605647 2024-06-20 18:02:21.501216 3 66.21 al_rtt true 2024-06-20 18:02:26.356521 2024-06-20 18:02:21.106233 3 44.57
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.370264 0.459835 37.000000 100/100 2024-06-20 18:02:26.356521 2024-06-20 18:02:21.106233 A al_loss true 0.370264 0.459835 37.000000 100/100 2024-06-20 18:02:24.605647 2024-06-20 18:02:21.501216 A al_jitter true 0.370264 0.459835 37.000000 100/100 2024-06-20 18:02:24.762933
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:02:33.470211 2024-06-20 18:02:24.762933 2 45.52 al_loss false 2024-06-20 18:02:33.422863 2024-06-20 18:02:24.605647 4 72.98 al_rtt false 2024-06-20 18:02:32.584069 2024-06-20 18:02:26.356521 4 53.57
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000396 0.000048 0.000000 100/100 2024-06-20 18:02:32.584069 2024-06-20 18:02:26.356521 A al_loss false 0.000396 0.000048 0.000000 100/100 2024-06-20 18:02:33.422863 2024-06-20 18:02:24.605647 A al_jitter false 0.000396 0.000048 0.000000 100/100 2024-06-20 18:02:33.470211 2024-06-20 18:02:24.762933
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:02:33.470211 2024-06-20 18:02:24.762933 2 34.72 al_loss false 2024-06-20 18:02:33.422863 2024-06-20 18:02:24.605647 4 55.67 al_rtt true 2024-06-20 18:02:36.876080 2024-06-20 18:02:32.584069 5 53.54
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.801411 0.009061 0.000000 100/100 2024-06-20 18:02:36.876080 2024-06-20 18:02:32.584069 A al_loss false 0.801411 0.009061 0.000000 100/100 2024-06-20 18:02:33.422863 2024-06-20 18:02:24.605647 A al_jitter false 0.801411 0.009061 0.000000 100/100 2024-06-20 18:02:33.470211 2024-06-20 18:02:24.762933
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:02:33.470211 2024-06-20 18:02:24.762933 2 28.09 al_loss false 2024-06-20 18:02:45.596553 2024-06-20 18:02:41.097968 6 59.55 al_rtt false 2024-06-20 18:02:45.091659 2024-06-20 18:02:36.876080 6 59.56
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000399 0.000051 0.000000 100/100 2024-06-20 18:02:45.091659 2024-06-20 18:02:36.876080 A al_loss false 0.000399 0.000051 0.000000 100/100 2024-06-20 18:02:45.596553 2024-06-20 18:02:41.097968 A al_jitter false 0.000399 0.000051 0.000000 100/100 2024-06-20 18:02:33.470211 2024-06-20 18:02:24.762933
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-06-20 18:02:49.345360 2024-06-20 18:02:33.470211 3 30.92 al_loss false 2024-06-20 18:02:45.596553 2024-06-20 18:02:41.097968 6 49.70 al_rtt true 2024-06-20 18:02:51.217900 2024-06-20 18:02:45.091659 7 52.14
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.233367 0.340235 0.000000 100/100 2024-06-20 18:02:51.217900 2024-06-20 18:02:45.091659 A al_loss false 0.233367 0.340235 0.000000 100/100 2024-06-20 18:02:45.596553 2024-06-20 18:02:41.097968 A al_jitter true 0.233367 0.340235 0.000000 100/100 2024-06-20 18:02:49.345360 2024-06-20 18:02:33.470211
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-06-20 18:02:56.624175 2024-06-20 18:02:49.345360 4 37.20 al_loss false 2024-06-20 18:02:57.614684 2024-06-20 18:02:53.705816 8 52.05 al_rtt false 2024-06-20 18:02:55.174696 2024-06-20 18:02:51.217900 8 52.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_rtt false 0.000398 0.000052 0.000000 100/100 2024-06-20 18:02:55.174696 2024-06-20 18:02:51.217900 A al_loss false 0.000398 0.000052 0.000000 100/100 2024-06-20 18:02:57.614684 2024-06-20 18:02:53.705816 A al_jitter false 0.000398 0.000052 0.000000 100/100 2024-06-20 18:02:56.624175 2024-06-20 18:02:49.345360
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.