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.000022 0.000006 0.000000 6/100 A al_loss false 0.000022 0.000006 0.000000 6/100 A al_jitter false 0.000022 0.000006 0.000000 6/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 07:41:39.855892 1 47.62 al_loss true 2024-10-10 07:41:39.266735 1 57.45 al_rtt true 2024-10-10 07:41:40.958277 1 29.28
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.360295 0.439826 36.000000 100/100 2024-10-10 07:41:40.958277 A al_loss true 0.360295 0.439826 36.000000 100/100 2024-10-10 07:41:39.266735 A al_jitter true 0.360295 0.439826 36.000000 100/100 2024-10-10 07:41:39.855892
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 07:41:47.679381 2024-10-10 07:41:39.855892 2 67.54 al_loss false 2024-10-10 07:41:47.988036 2024-10-10 07:41:39.266735 2 75.31 al_rtt false 2024-10-10 07:41:46.775785 2024-10-10 07:41:40.958277 2 50.24
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.000588 0.000138 0.000000 100/100 2024-10-10 07:41:46.775785 2024-10-10 07:41:40.958277 A al_loss false 0.000588 0.000138 0.000000 100/100 2024-10-10 07:41:47.988036 2024-10-10 07:41:39.266735 A al_jitter false 0.000588 0.000138 0.000000 100/100 2024-10-10 07:41:47.679381 2024-10-10 07:41:39.855892
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 07:41:47.679381 2024-10-10 07:41:39.855892 2 45.53 al_loss false 2024-10-10 07:41:47.988036 2024-10-10 07:41:39.266735 2 50.76 al_rtt true 2024-10-10 07:41:50.786178 2024-10-10 07:41:46.775785 3 51.95
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.774544 0.009164 0.000000 100/100 2024-10-10 07:41:50.786178 2024-10-10 07:41:46.775785 A al_loss false 0.774544 0.009164 0.000000 100/100 2024-10-10 07:41:47.988036 2024-10-10 07:41:39.266735 A al_jitter false 0.774544 0.009164 0.000000 100/100 2024-10-10 07:41:47.679381 2024-10-10 07:41:39.855892
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 07:41:47.679381 2024-10-10 07:41:39.855892 2 34.41 al_loss false 2024-10-10 07:41:59.158264 2024-10-10 07:41:54.643543 4 58.23 al_rtt false 2024-10-10 07:41:58.661216 2024-10-10 07:41:50.786178 4 60.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.000633 0.000140 0.000000 100/100 2024-10-10 07:41:58.661216 2024-10-10 07:41:50.786178 A al_loss false 0.000633 0.000140 0.000000 100/100 2024-10-10 07:41:59.158264 2024-10-10 07:41:54.643543 A al_jitter false 0.000633 0.000140 0.000000 100/100 2024-10-10 07:41:47.679381 2024-10-10 07:41:39.855892
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 07:42:02.781634 2024-10-10 07:41:47.679381 3 35.69 al_loss false 2024-10-10 07:41:59.158264 2024-10-10 07:41:54.643543 4 46.65 al_rtt true 2024-10-10 07:42:05.062483 2024-10-10 07:41:58.661216 5 48.34
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.211377 0.262692 0.000000 100/100 2024-10-10 07:42:05.062483 2024-10-10 07:41:58.661216 A al_loss false 0.211377 0.262692 0.000000 100/100 2024-10-10 07:41:59.158264 2024-10-10 07:41:54.643543 A al_jitter true 0.211377 0.262692 0.000000 100/100 2024-10-10 07:42:02.781634 2024-10-10 07:41:47.679381
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 07:42:09.356006 2024-10-10 07:42:02.781634 4 42.32 al_loss false 2024-10-10 07:41:59.158264 2024-10-10 07:41:54.643543 4 38.91 al_rtt false 2024-10-10 07:42:07.726716 2024-10-10 07:42:05.062483 6 48.09
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.000611 0.000140 0.000000 100/100 2024-10-10 07:42:07.726716 2024-10-10 07:42:05.062483 A al_loss false 0.000611 0.000140 0.000000 100/100 2024-10-10 07:41:59.158264 2024-10-10 07:41:54.643543 A al_jitter false 0.000611 0.000140 0.000000 100/100 2024-10-10 07:42:09.356006 2024-10-10 07:42:02.781634
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.000022 0.000003 0.000000 6/100 A al_loss false 0.000022 0.000003 0.000000 6/100 A al_jitter false 0.000022 0.000003 0.000000 6/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 07:42:19.850454 1 56.64 al_loss true 2024-10-10 07:42:19.399578 1 64.09 al_rtt true 2024-10-10 07:42:20.703248 1 42.42
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.450267 0.449795 45.000000 100/100 2024-10-10 07:42:20.703248 A al_loss true 0.450267 0.449795 45.000000 100/100 2024-10-10 07:42:19.399578 A al_jitter true 0.450267 0.449795 45.000000 100/100 2024-10-10 07:42:19.850454
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 07:42:28.374202 2024-10-10 07:42:19.850454 2 73.46 al_loss false 2024-10-10 07:42:28.531632 2024-10-10 07:42:19.399578 2 78.66 al_rtt false 2024-10-10 07:42:27.424676 2024-10-10 07:42:20.703248 2 57.91
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.000506 0.000146 0.000000 100/100 2024-10-10 07:42:27.424676 2024-10-10 07:42:20.703248 A al_loss false 0.000506 0.000146 0.000000 100/100 2024-10-10 07:42:28.531632 2024-10-10 07:42:19.399578 A al_jitter false 0.000506 0.000146 0.000000 100/100 2024-10-10 07:42:28.374202 2024-10-10 07:42:19.850454
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 07:42:28.374202 2024-10-10 07:42:19.850454 2 49.31 al_loss false 2024-10-10 07:42:28.531632 2024-10-10 07:42:19.399578 2 52.81 al_rtt true 2024-10-10 07:42:31.430702 2024-10-10 07:42:27.424676 3 56.82
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.774486 0.009123 0.000000 100/100 2024-10-10 07:42:31.430702 2024-10-10 07:42:27.424676 A al_loss false 0.774486 0.009123 0.000000 100/100 2024-10-10 07:42:28.531632 2024-10-10 07:42:19.399578 A al_jitter false 0.774486 0.009123 0.000000 100/100 2024-10-10 07:42:28.374202 2024-10-10 07:42:19.850454
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 07:42:28.374202 2024-10-10 07:42:19.850454 2 37.37 al_loss false 2024-10-10 07:42:39.753756 2024-10-10 07:42:35.244696 4 59.79 al_rtt false 2024-10-10 07:42:39.258166 2024-10-10 07:42:31.430702 4 63.77
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.000499 0.000129 0.000000 100/100 2024-10-10 07:42:39.258166 2024-10-10 07:42:31.430702 A al_loss false 0.000499 0.000129 0.000000 100/100 2024-10-10 07:42:39.753756 2024-10-10 07:42:35.244696 A al_jitter false 0.000499 0.000129 0.000000 100/100 2024-10-10 07:42:28.374202 2024-10-10 07:42:19.850454
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 07:42:43.049853 2024-10-10 07:42:28.374202 3 39.20 al_loss false 2024-10-10 07:42:39.753756 2024-10-10 07:42:35.244696 4 47.99 al_rtt false 2024-10-10 07:42:39.258166 2024-10-10 07:42:31.430702 4 51.18
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.199591 0.286163 0.000000 100/100 2024-10-10 07:42:39.258166 2024-10-10 07:42:31.430702 A al_loss false 0.199591 0.286163 0.000000 100/100 2024-10-10 07:42:39.753756 2024-10-10 07:42:35.244696 A al_jitter true 0.199591 0.286163 0.000000 100/100 2024-10-10 07:42:43.049853 2024-10-10 07:42:28.374202
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 07:42:49.675655 2024-10-10 07:42:43.049853 4 44.55 al_loss false 2024-10-10 07:42:50.827279 2024-10-10 07:42:46.713934 6 52.20 al_rtt false 2024-10-10 07:42:49.627892 2024-10-10 07:42:45.772668 6 54.12
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.000518 0.000106 0.000000 100/100 2024-10-10 07:42:49.627892 2024-10-10 07:42:45.772668 A al_loss false 0.000518 0.000106 0.000000 100/100 2024-10-10 07:42:50.827279 2024-10-10 07:42:46.713934 A al_jitter false 0.000518 0.000106 0.000000 100/100 2024-10-10 07:42:49.675655 2024-10-10 07:42:43.049853
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 07:43:03.782212 2024-10-10 07:42:59.056814 2 70.43 al_rtt false 2024-10-10 07:43:03.721580 2024-10-10 07:42:59.809408 2 58.33
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.012838 0.003867 0.000000 100/100 2024-10-10 07:43:03.721580 2024-10-10 07:42:59.809408 A al_loss false 0.012838 0.003867 0.000000 100/100 2024-10-10 07:43:03.782212 2024-10-10 07:42:59.056814 A al_jitter false 0.012838 0.003867 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 07:43:07.096754 1 24.22 al_loss true 2024-10-10 07:43:06.275211 2024-10-10 07:43:03.782212 3 69.28 al_rtt true 2024-10-10 07:43:07.827645 2024-10-10 07:43:03.721580 3 50.07
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.460255 0.339884 46.000000 100/100 2024-10-10 07:43:07.827645 2024-10-10 07:43:03.721580 A al_loss true 0.460255 0.339884 46.000000 100/100 2024-10-10 07:43:06.275211 2024-10-10 07:43:03.782212 A al_jitter true 0.460255 0.339884 46.000000 100/100 2024-10-10 07:43:07.096754
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 07:43:14.852985 2024-10-10 07:43:07.096754 2 43.46 al_loss false 2024-10-10 07:43:15.147831 2024-10-10 07:43:06.275211 4 76.21 al_rtt false 2024-10-10 07:43:13.955714 2024-10-10 07:43:07.827645 4 56.28
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.000488 0.000119 0.000000 100/100 2024-10-10 07:43:13.955714 2024-10-10 07:43:07.827645 A al_loss false 0.000488 0.000119 0.000000 100/100 2024-10-10 07:43:15.147831 2024-10-10 07:43:06.275211 A al_jitter false 0.000488 0.000119 0.000000 100/100 2024-10-10 07:43:14.852985 2024-10-10 07:43:07.096754
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 07:43:14.852985 2024-10-10 07:43:07.096754 2 33.06 al_loss false 2024-10-10 07:43:15.147831 2024-10-10 07:43:06.275211 4 57.97 al_rtt true 2024-10-10 07:43:18.112964 2024-10-10 07:43:13.955714 5 56.07
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.774576 0.009150 0.000000 100/100 2024-10-10 07:43:18.112964 2024-10-10 07:43:13.955714 A al_loss false 0.774576 0.009150 0.000000 100/100 2024-10-10 07:43:15.147831 2024-10-10 07:43:06.275211 A al_jitter false 0.774576 0.009150 0.000000 100/100 2024-10-10 07:43:14.852985 2024-10-10 07:43:07.096754
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 07:43:14.852985 2024-10-10 07:43:07.096754 2 26.69 al_loss false 2024-10-10 07:43:26.524994 2024-10-10 07:43:22.018967 6 62.31 al_rtt false 2024-10-10 07:43:26.024771 2024-10-10 07:43:18.112964 6 61.79
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.000450 0.000110 0.000000 100/100 2024-10-10 07:43:26.024771 2024-10-10 07:43:18.112964 A al_loss false 0.000450 0.000110 0.000000 100/100 2024-10-10 07:43:26.524994 2024-10-10 07:43:22.018967 A al_jitter false 0.000450 0.000110 0.000000 100/100 2024-10-10 07:43:14.852985 2024-10-10 07:43:07.096754
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 07:43:30.152807 2024-10-10 07:43:14.852985 3 29.00 al_loss false 2024-10-10 07:43:26.524994 2024-10-10 07:43:22.018967 6 52.19 al_rtt true 2024-10-10 07:43:32.257133 2024-10-10 07:43:26.024771 7 52.33
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.233890 0.310504 0.000000 100/100 2024-10-10 07:43:32.257133 2024-10-10 07:43:26.024771 A al_loss false 0.233890 0.310504 0.000000 100/100 2024-10-10 07:43:26.524994 2024-10-10 07:43:22.018967 A al_jitter true 0.233890 0.310504 0.000000 100/100 2024-10-10 07:43:30.152807 2024-10-10 07:43:14.852985
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 07:43:36.651278 2024-10-10 07:43:30.152807 4 35.43 al_loss false 2024-10-10 07:43:26.524994 2024-10-10 07:43:22.018967 6 45.00 al_rtt false 2024-10-10 07:43:35.098257 2024-10-10 07:43:32.257133 8 51.68
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.000529 0.000131 0.000000 100/100 2024-10-10 07:43:35.098257 2024-10-10 07:43:32.257133 A al_loss false 0.000529 0.000131 0.000000 100/100 2024-10-10 07:43:26.524994 2024-10-10 07:43:22.018967 A al_jitter false 0.000529 0.000131 0.000000 100/100 2024-10-10 07:43:36.651278 2024-10-10 07:43:30.152807
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 07:43:51.607847 2024-10-10 07:43:46.340772 2 78.90 al_rtt false 2024-10-10 07:43:51.174654 2024-10-10 07:43:47.101451 2 61.04
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.017756 0.010106 0.000000 100/100 2024-10-10 07:43:51.174654 2024-10-10 07:43:47.101451 A al_loss false 0.017756 0.010106 0.000000 100/100 2024-10-10 07:43:51.607847 2024-10-10 07:43:46.340772 A al_jitter false 0.017756 0.010106 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 07:43:54.367332 1 24.11 al_loss true 2024-10-10 07:43:53.619280 2024-10-10 07:43:51.607847 3 73.04 al_rtt true 2024-10-10 07:43:55.061149 2024-10-10 07:43:51.174654 3 51.61
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.430332 0.339838 43.000000 100/100 2024-10-10 07:43:55.061149 2024-10-10 07:43:51.174654 A al_loss true 0.430332 0.339838 43.000000 100/100 2024-10-10 07:43:53.619280 2024-10-10 07:43:51.607847 A al_jitter true 0.430332 0.339838 43.000000 100/100 2024-10-10 07:43:54.367332
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 07:44:02.286628 2024-10-10 07:43:54.367332 2 44.47 al_loss false 2024-10-10 07:44:02.536558 2024-10-10 07:43:53.619280 4 79.63 al_rtt false 2024-10-10 07:44:01.133716 2024-10-10 07:43:55.061149 4 56.96
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.000546 0.000144 0.000000 100/100 2024-10-10 07:44:01.133716 2024-10-10 07:43:55.061149 A al_loss false 0.000546 0.000144 0.000000 100/100 2024-10-10 07:44:02.536558 2024-10-10 07:43:53.619280 A al_jitter false 0.000546 0.000144 0.000000 100/100 2024-10-10 07:44:02.286628 2024-10-10 07:43:54.367332
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 07:44:02.286628 2024-10-10 07:43:54.367332 2 33.81 al_loss false 2024-10-10 07:44:02.536558 2024-10-10 07:43:53.619280 4 60.54 al_rtt true 2024-10-10 07:44:05.338637 2024-10-10 07:44:01.133716 5 56.66
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.774490 0.009133 0.000000 100/100 2024-10-10 07:44:05.338637 2024-10-10 07:44:01.133716 A al_loss false 0.774490 0.009133 0.000000 100/100 2024-10-10 07:44:02.536558 2024-10-10 07:43:53.619280 A al_jitter false 0.774490 0.009133 0.000000 100/100 2024-10-10 07:44:02.286628 2024-10-10 07:43:54.367332
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 07:44:02.286628 2024-10-10 07:43:54.367332 2 27.35 al_loss false 2024-10-10 07:44:13.712018 2024-10-10 07:44:09.203192 6 64.55 al_rtt false 2024-10-10 07:44:13.204726 2024-10-10 07:44:05.338637 6 62.20
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.000520 0.000151 0.000000 100/100 2024-10-10 07:44:13.204726 2024-10-10 07:44:05.338637 A al_loss false 0.000520 0.000151 0.000000 100/100 2024-10-10 07:44:13.712018 2024-10-10 07:44:09.203192 A al_jitter false 0.000520 0.000151 0.000000 100/100 2024-10-10 07:44:02.286628 2024-10-10 07:43:54.367332
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 07:44:17.056552 2024-10-10 07:44:02.286628 3 30.41 al_loss false 2024-10-10 07:44:13.712018 2024-10-10 07:44:09.203192 6 53.98 al_rtt true 2024-10-10 07:44:19.459205 2024-10-10 07:44:13.204726 7 52.62
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.208518 0.289268 0.000000 100/100 2024-10-10 07:44:19.459205 2024-10-10 07:44:13.204726 A al_loss false 0.208518 0.289268 0.000000 100/100 2024-10-10 07:44:13.712018 2024-10-10 07:44:09.203192 A al_jitter true 0.208518 0.289268 0.000000 100/100 2024-10-10 07:44:17.056552 2024-10-10 07:44:02.286628
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 07:44:24.230358 2024-10-10 07:44:17.056552 4 37.56 al_loss false 2024-10-10 07:44:13.712018 2024-10-10 07:44:09.203192 6 46.51 al_rtt false 2024-10-10 07:44:22.324350 2024-10-10 07:44:19.459205 8 51.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.000540 0.000154 0.000000 100/100 2024-10-10 07:44:22.324350 2024-10-10 07:44:19.459205 A al_loss false 0.000540 0.000154 0.000000 100/100 2024-10-10 07:44:13.712018 2024-10-10 07:44:09.203192 A al_jitter false 0.000540 0.000154 0.000000 100/100 2024-10-10 07:44:24.230358 2024-10-10 07:44:17.056552
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.