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.000068 0.000023 0.000000 11/100 A al_loss false 0.000068 0.000023 0.000000 11/100 A al_jitter false 0.000068 0.000023 0.000000 11/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-10-10 08:08:12.235933 1 46.64 al_loss true 2024-10-10 08:08:11.336986 1 60.62 al_rtt true 2024-10-10 08:08:12.596847 1 41.10
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.490243 0.359864 49.000000 100/100 2024-10-10 08:08:12.596847 A al_loss true 0.490243 0.359864 49.000000 100/100 2024-10-10 08:08:11.336986 A al_jitter true 0.490243 0.359864 49.000000 100/100 2024-10-10 08:08:12.235933
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-10-10 08:08:20.414029 2024-10-10 08:08:12.235933 2 66.43 al_loss false 2024-10-10 08:08:20.564121 2024-10-10 08:08:11.336986 2 74.99 al_rtt false 2024-10-10 08:08:19.703685 2024-10-10 08:08:12.596847 2 57.78
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.000468 0.000065 0.000000 100/100 2024-10-10 08:08:19.703685 2024-10-10 08:08:12.596847 A al_loss false 0.000468 0.000065 0.000000 100/100 2024-10-10 08:08:20.564121 2024-10-10 08:08:11.336986 A al_jitter false 0.000468 0.000065 0.000000 100/100 2024-10-10 08:08:20.414029 2024-10-10 08:08:12.235933
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-10-10 08:08:20.414029 2024-10-10 08:08:12.235933 2 44.76 al_loss false 2024-10-10 08:08:20.564121 2024-10-10 08:08:11.336986 2 50.51 al_rtt true 2024-10-10 08:08:23.914769 2024-10-10 08:08:19.703685 3 56.17
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.792489 0.009070 0.000000 100/100 2024-10-10 08:08:23.914769 2024-10-10 08:08:19.703685 A al_loss false 0.792489 0.009070 0.000000 100/100 2024-10-10 08:08:20.564121 2024-10-10 08:08:11.336986 A al_jitter false 0.792489 0.009070 0.000000 100/100 2024-10-10 08:08:20.414029 2024-10-10 08:08:12.235933
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-10-10 08:08:20.414029 2024-10-10 08:08:12.235933 2 34.04 al_loss false 2024-10-10 08:08:32.478237 2024-10-10 08:08:28.022529 4 56.97 al_rtt false 2024-10-10 08:08:31.995645 2024-10-10 08:08:23.914769 4 63.24
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.000464 0.000068 0.000000 100/100 2024-10-10 08:08:31.995645 2024-10-10 08:08:23.914769 A al_loss false 0.000464 0.000068 0.000000 100/100 2024-10-10 08:08:32.478237 2024-10-10 08:08:28.022529 A al_jitter false 0.000464 0.000068 0.000000 100/100 2024-10-10 08:08:20.414029 2024-10-10 08:08:12.235933
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-10-10 08:08:36.202963 2024-10-10 08:08:20.414029 3 35.75 al_loss false 2024-10-10 08:08:32.478237 2024-10-10 08:08:28.022529 4 45.73 al_rtt true 2024-10-10 08:08:38.651793 2024-10-10 08:08:31.995645 5 51.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 true 0.212090 0.307141 0.000000 100/100 2024-10-10 08:08:38.651793 2024-10-10 08:08:31.995645 A al_loss false 0.212090 0.307141 0.000000 100/100 2024-10-10 08:08:32.478237 2024-10-10 08:08:28.022529 A al_jitter true 0.212090 0.307141 0.000000 100/100 2024-10-10 08:08:36.202963 2024-10-10 08:08:20.414029
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-10-10 08:08:43.761597 2024-10-10 08:08:36.202963 4 44.00 al_loss false 2024-10-10 08:08:32.478237 2024-10-10 08:08:28.022529 4 38.26 al_rtt false 2024-10-10 08:08:41.750565 2024-10-10 08:08:38.651793 6 51.14
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.000467 0.000067 0.000000 100/100 2024-10-10 08:08:41.750565 2024-10-10 08:08:38.651793 A al_loss false 0.000467 0.000067 0.000000 100/100 2024-10-10 08:08:32.478237 2024-10-10 08:08:28.022529 A al_jitter false 0.000467 0.000067 0.000000 100/100 2024-10-10 08:08:43.761597 2024-10-10 08:08:36.202963
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.000204 0.000302 0.000000 11/100 A al_loss false 0.000204 0.000302 0.000000 11/100 A al_jitter false 0.000204 0.000302 0.000000 11/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-10-10 08:08:57.742365 1 53.09 al_loss true 2024-10-10 08:08:57.492686 1 56.78 al_rtt true 2024-10-10 08:08:58.584565 1 40.23
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.530209 0.359855 53.000000 100/100 2024-10-10 08:08:58.584565 A al_loss true 0.530209 0.359855 53.000000 100/100 2024-10-10 08:08:57.492686 A al_jitter true 0.530209 0.359855 53.000000 100/100 2024-10-10 08:08:57.742365
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-10-10 08:09:06.363079 2024-10-10 08:08:57.742365 2 69.24 al_loss false 2024-10-10 08:09:06.306057 2024-10-10 08:08:57.492686 2 70.71 al_rtt false 2024-10-10 08:09:05.214804 2024-10-10 08:08:58.584565 2 53.23
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.000051 0.000000 100/100 2024-10-10 08:09:05.214804 2024-10-10 08:08:58.584565 A al_loss false 0.000447 0.000051 0.000000 100/100 2024-10-10 08:09:06.306057 2024-10-10 08:08:57.492686 A al_jitter false 0.000447 0.000051 0.000000 100/100 2024-10-10 08:09:06.363079 2024-10-10 08:08:57.742365
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-10-10 08:09:06.363079 2024-10-10 08:08:57.742365 2 46.32 al_loss false 2024-10-10 08:09:06.306057 2024-10-10 08:08:57.492686 2 47.32 al_rtt true 2024-10-10 08:09:10.116006 2024-10-10 08:09:05.214804 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_rtt true 0.801694 0.009417 0.000000 100/100 2024-10-10 08:09:10.116006 2024-10-10 08:09:05.214804 A al_loss false 0.801694 0.009417 0.000000 100/100 2024-10-10 08:09:06.306057 2024-10-10 08:08:57.492686 A al_jitter false 0.801694 0.009417 0.000000 100/100 2024-10-10 08:09:06.363079 2024-10-10 08:08:57.742365
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-10-10 08:09:06.363079 2024-10-10 08:08:57.742365 2 35.23 al_loss false 2024-10-10 08:09:18.783586 2024-10-10 08:09:14.275982 4 54.42 al_rtt false 2024-10-10 08:09:18.276807 2024-10-10 08:09:10.116006 4 60.44
Step 16: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000466 0.000061 0.000000 100/100 2024-10-10 08:09:18.276807 2024-10-10 08:09:10.116006 A al_loss false 0.000466 0.000061 0.000000 100/100 2024-10-10 08:09:18.783586 2024-10-10 08:09:14.275982 A al_jitter false 0.000466 0.000061 0.000000 100/100 2024-10-10 08:09:06.363079 2024-10-10 08:08:57.742365
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-10-10 08:09:22.401183 2024-10-10 08:09:06.363079 3 37.06 al_loss false 2024-10-10 08:09:18.783586 2024-10-10 08:09:14.275982 4 43.84 al_rtt true 2024-10-10 08:09:25.022460 2024-10-10 08:09:18.276807 5 48.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.217116 0.310189 0.000000 100/100 2024-10-10 08:09:25.022460 2024-10-10 08:09:18.276807 A al_loss false 0.217116 0.310189 0.000000 100/100 2024-10-10 08:09:18.783586 2024-10-10 08:09:14.275982 A al_jitter true 0.217116 0.310189 0.000000 100/100 2024-10-10 08:09:22.401183 2024-10-10 08:09:06.363079
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-10-10 08:09:30.007529 2024-10-10 08:09:22.401183 4 44.85 al_loss false 2024-10-10 08:09:30.108638 2024-10-10 08:09:26.498196 6 46.78 al_rtt false 2024-10-10 08:09:28.304941 2024-10-10 08:09:25.022460 6 49.95
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.000451 0.000066 0.000000 100/100 2024-10-10 08:09:28.304941 2024-10-10 08:09:25.022460 A al_loss false 0.000451 0.000066 0.000000 100/100 2024-10-10 08:09:30.108638 2024-10-10 08:09:26.498196 A al_jitter false 0.000451 0.000066 0.000000 100/100 2024-10-10 08:09:30.007529 2024-10-10 08:09:22.401183
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-10-10 08:09:46.776277 2024-10-10 08:09:41.767288 2 70.38 al_rtt false 2024-10-10 08:09:46.475732 2024-10-10 08:09:42.525806 2 55.53
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.000400 0.000061 0.000000 100/100 2024-10-10 08:09:46.475732 2024-10-10 08:09:42.525806 A al_loss false 0.000400 0.000061 0.000000 100/100 2024-10-10 08:09:46.776277 2024-10-10 08:09:41.767288 A al_jitter false 0.000400 0.000061 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-10-10 08:09:50.498381 1 23.99 al_loss true 2024-10-10 08:09:49.888525 2024-10-10 08:09:46.776277 3 66.40 al_rtt true 2024-10-10 08:09:51.839282 2024-10-10 08:09:46.475732 3 43.70
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.430235 0.339872 43.000000 100/100 2024-10-10 08:09:51.839282 2024-10-10 08:09:46.475732 A al_loss true 0.430235 0.339872 43.000000 100/100 2024-10-10 08:09:49.888525 2024-10-10 08:09:46.776277 A al_jitter true 0.430235 0.339872 43.000000 100/100 2024-10-10 08:09:50.498381
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-10-10 08:09:58.461092 2024-10-10 08:09:50.498381 2 41.87 al_loss false 2024-10-10 08:09:58.703566 2024-10-10 08:09:49.888525 4 72.71 al_rtt false 2024-10-10 08:09:57.445870 2024-10-10 08:09:51.839282 4 50.27
Step 10: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000401 0.000050 0.000000 100/100 2024-10-10 08:09:57.445870 2024-10-10 08:09:51.839282 A al_loss false 0.000401 0.000050 0.000000 100/100 2024-10-10 08:09:58.703566 2024-10-10 08:09:49.888525 A al_jitter false 0.000401 0.000050 0.000000 100/100 2024-10-10 08:09:58.461092 2024-10-10 08:09:50.498381
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-10-10 08:09:58.461092 2024-10-10 08:09:50.498381 2 31.73 al_loss false 2024-10-10 08:09:58.703566 2024-10-10 08:09:49.888525 4 55.09 al_rtt true 2024-10-10 08:10:02.309049 2024-10-10 08:09:57.445870 5 50.89
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.819451 0.009076 0.000000 100/100 2024-10-10 08:10:02.309049 2024-10-10 08:09:57.445870 A al_loss false 0.819451 0.009076 0.000000 100/100 2024-10-10 08:09:58.703566 2024-10-10 08:09:49.888525 A al_jitter false 0.819451 0.009076 0.000000 100/100 2024-10-10 08:09:58.461092 2024-10-10 08:09:50.498381
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-10-10 08:09:58.461092 2024-10-10 08:09:50.498381 2 25.66 al_loss false 2024-10-10 08:10:11.134337 2024-10-10 08:10:06.631773 6 59.07 al_rtt false 2024-10-10 08:10:10.627640 2024-10-10 08:10:02.309049 6 57.62
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.000408 0.000055 0.000000 100/100 2024-10-10 08:10:10.627640 2024-10-10 08:10:02.309049 A al_loss false 0.000408 0.000055 0.000000 100/100 2024-10-10 08:10:11.134337 2024-10-10 08:10:06.631773 A al_jitter false 0.000408 0.000055 0.000000 100/100 2024-10-10 08:09:58.461092 2024-10-10 08:09:50.498381
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-10-10 08:10:15.029811 2024-10-10 08:09:58.461092 3 28.02 al_loss false 2024-10-10 08:10:11.134337 2024-10-10 08:10:06.631773 6 49.52 al_rtt false 2024-10-10 08:10:10.627640 2024-10-10 08:10:02.309049 6 48.30
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.191239 0.273433 0.000000 100/100 2024-10-10 08:10:10.627640 2024-10-10 08:10:02.309049 A al_loss false 0.191239 0.273433 0.000000 100/100 2024-10-10 08:10:11.134337 2024-10-10 08:10:06.631773 A al_jitter true 0.191239 0.273433 0.000000 100/100 2024-10-10 08:10:15.029811 2024-10-10 08:09:58.461092
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-10-10 08:10:22.602757 2024-10-10 08:10:15.029811 4 36.26 al_loss false 2024-10-10 08:10:22.746258 2024-10-10 08:10:18.936553 8 51.67 al_rtt false 2024-10-10 08:10:20.138084 2024-10-10 08:10:18.533669 8 45.47
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.000420 0.000049 0.000000 100/100 2024-10-10 08:10:20.138084 2024-10-10 08:10:18.533669 A al_loss false 0.000420 0.000049 0.000000 100/100 2024-10-10 08:10:22.746258 2024-10-10 08:10:18.936553 A al_jitter false 0.000420 0.000049 0.000000 100/100 2024-10-10 08:10:22.602757 2024-10-10 08:10:15.029811
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-10-10 08:10:40.406543 2024-10-10 08:10:35.002609 2 76.31 al_rtt false 2024-10-10 08:10:39.907748 2024-10-10 08:10:35.743370 2 58.84
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.000422 0.000067 0.000000 100/100 2024-10-10 08:10:39.907748 2024-10-10 08:10:35.743370 A al_loss false 0.000422 0.000067 0.000000 100/100 2024-10-10 08:10:40.406543 2024-10-10 08:10:35.002609 A al_jitter false 0.000422 0.000067 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-10-10 08:10:43.667719 1 23.68 al_loss true 2024-10-10 08:10:43.316446 2024-10-10 08:10:40.406543 3 67.44 al_rtt true 2024-10-10 08:10:44.929263 2024-10-10 08:10:39.907748 3 45.76
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.440251 0.419830 44.000000 100/100 2024-10-10 08:10:44.929263 2024-10-10 08:10:39.907748 A al_loss true 0.440251 0.419830 44.000000 100/100 2024-10-10 08:10:43.316446 2024-10-10 08:10:40.406543 A al_jitter true 0.440251 0.419830 44.000000 100/100 2024-10-10 08:10:43.667719
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-10-10 08:10:51.627247 2024-10-10 08:10:43.667719 2 42.21 al_loss false 2024-10-10 08:10:51.828227 2024-10-10 08:10:43.316446 4 73.76 al_rtt false 2024-10-10 08:10:50.827396 2024-10-10 08:10:44.929263 4 53.35
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.000433 0.000058 0.000000 100/100 2024-10-10 08:10:50.827396 2024-10-10 08:10:44.929263 A al_loss false 0.000433 0.000058 0.000000 100/100 2024-10-10 08:10:51.828227 2024-10-10 08:10:43.316446 A al_jitter false 0.000433 0.000058 0.000000 100/100 2024-10-10 08:10:51.627247 2024-10-10 08:10:43.667719
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-10-10 08:10:51.627247 2024-10-10 08:10:43.667719 2 32.05 al_loss false 2024-10-10 08:10:51.828227 2024-10-10 08:10:43.316446 4 56.02 al_rtt true 2024-10-10 08:10:55.333138 2024-10-10 08:10:50.827396 5 53.15
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.783475 0.009075 0.000000 100/100 2024-10-10 08:10:55.333138 2024-10-10 08:10:50.827396 A al_loss false 0.783475 0.009075 0.000000 100/100 2024-10-10 08:10:51.828227 2024-10-10 08:10:43.316446 A al_jitter false 0.783475 0.009075 0.000000 100/100 2024-10-10 08:10:51.627247 2024-10-10 08:10:43.667719
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-10-10 08:10:51.627247 2024-10-10 08:10:43.667719 2 25.99 al_loss false 2024-10-10 08:11:03.900600 2024-10-10 08:10:59.392565 6 60.15 al_rtt false 2024-10-10 08:11:03.415718 2024-10-10 08:10:55.333138 6 59.24
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.000435 0.000057 0.000000 100/100 2024-10-10 08:11:03.415718 2024-10-10 08:10:55.333138 A al_loss false 0.000435 0.000057 0.000000 100/100 2024-10-10 08:11:03.900600 2024-10-10 08:10:59.392565 A al_jitter false 0.000435 0.000057 0.000000 100/100 2024-10-10 08:10:51.627247 2024-10-10 08:10:43.667719
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-10-10 08:11:07.428599 2024-10-10 08:10:51.627247 3 29.27 al_loss false 2024-10-10 08:11:03.900600 2024-10-10 08:10:59.392565 6 50.44 al_rtt true 2024-10-10 08:11:10.099709 2024-10-10 08:11:03.415718 7 49.84
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.201356 0.288096 0.000000 100/100 2024-10-10 08:11:10.099709 2024-10-10 08:11:03.415718 A al_loss false 0.201356 0.288096 0.000000 100/100 2024-10-10 08:11:03.900600 2024-10-10 08:10:59.392565 A al_jitter true 0.201356 0.288096 0.000000 100/100 2024-10-10 08:11:07.428599 2024-10-10 08:10:51.627247
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-10-10 08:11:14.623046 2024-10-10 08:11:07.428599 4 35.74 al_loss false 2024-10-10 08:11:03.900600 2024-10-10 08:10:59.392565 6 43.44 al_rtt false 2024-10-10 08:11:12.966850 2024-10-10 08:11:10.099709 8 49.55
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.000442 0.000061 0.000000 100/100 2024-10-10 08:11:12.966850 2024-10-10 08:11:10.099709 A al_loss false 0.000442 0.000061 0.000000 100/100 2024-10-10 08:11:03.900600 2024-10-10 08:10:59.392565 A al_jitter false 0.000442 0.000061 0.000000 100/100 2024-10-10 08:11:14.623046 2024-10-10 08:11:07.428599
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.