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.000037 0.000014 0.000000 7/100 A al_loss false 0.000037 0.000014 0.000000 7/100 A al_jitter false 0.000037 0.000014 0.000000 7/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 2023-12-13 00:44:01.925984 1 50.62 al_loss true 2023-12-13 00:44:01.529565 1 56.80 al_rtt true 2023-12-13 00:44:02.825675 1 36.83
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.410249 0.419881 41.000000 100/100 2023-12-13 00:44:02.825675 A al_loss true 0.410249 0.419881 41.000000 100/100 2023-12-13 00:44:01.529565 A al_jitter true 0.410249 0.419881 41.000000 100/100 2023-12-13 00:44:01.925984
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 2023-12-13 00:44:10.340014 2023-12-13 00:44:01.925984 2 68.17 al_loss false 2023-12-13 00:44:10.635356 2023-12-13 00:44:01.529565 2 73.84 al_rtt false 2023-12-13 00:44:08.941907 2023-12-13 00:44:02.825675 2 49.58
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.000412 0.000072 0.000000 100/100 2023-12-13 00:44:08.941907 2023-12-13 00:44:02.825675 A al_loss false 0.000412 0.000072 0.000000 100/100 2023-12-13 00:44:10.635356 2023-12-13 00:44:01.529565 A al_jitter false 0.000412 0.000072 0.000000 100/100 2023-12-13 00:44:10.340014 2023-12-13 00:44:01.925984
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 2023-12-13 00:44:10.340014 2023-12-13 00:44:01.925984 2 45.76 al_loss false 2023-12-13 00:44:10.635356 2023-12-13 00:44:01.529565 2 49.55 al_rtt true 2023-12-13 00:44:13.951523 2023-12-13 00:44:08.941907 3 50.38
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.792432 0.009071 0.000000 100/100 2023-12-13 00:44:13.951523 2023-12-13 00:44:08.941907 A al_loss false 0.792432 0.009071 0.000000 100/100 2023-12-13 00:44:10.635356 2023-12-13 00:44:01.529565 A al_jitter false 0.792432 0.009071 0.000000 100/100 2023-12-13 00:44:10.340014 2023-12-13 00:44:01.925984
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 2023-12-13 00:44:10.340014 2023-12-13 00:44:01.925984 2 34.84 al_loss false 2023-12-13 00:44:22.525049 2023-12-13 00:44:18.000736 4 56.46 al_rtt false 2023-12-13 00:44:22.016677 2023-12-13 00:44:13.951523 4 58.74
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.000414 0.000059 0.000000 100/100 2023-12-13 00:44:22.016677 2023-12-13 00:44:13.951523 A al_loss false 0.000414 0.000059 0.000000 100/100 2023-12-13 00:44:22.525049 2023-12-13 00:44:18.000736 A al_jitter false 0.000414 0.000059 0.000000 100/100 2023-12-13 00:44:10.340014 2023-12-13 00:44:01.925984
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 2023-12-13 00:44:26.391239 2023-12-13 00:44:10.340014 3 36.32 al_loss false 2023-12-13 00:44:22.525049 2023-12-13 00:44:18.000736 4 45.06 al_rtt true 2023-12-13 00:44:28.429219 2023-12-13 00:44:22.016677 5 48.66
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.238373 0.308697 0.000000 100/100 2023-12-13 00:44:28.429219 2023-12-13 00:44:22.016677 A al_loss false 0.238373 0.308697 0.000000 100/100 2023-12-13 00:44:22.525049 2023-12-13 00:44:18.000736 A al_jitter true 0.238373 0.308697 0.000000 100/100 2023-12-13 00:44:26.391239 2023-12-13 00:44:10.340014
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 2023-12-13 00:44:34.136428 2023-12-13 00:44:26.391239 4 44.67 al_loss false 2023-12-13 00:44:34.353914 2023-12-13 00:44:30.493318 6 48.37 al_rtt false 2023-12-13 00:44:32.539265 2023-12-13 00:44:28.429219 6 50.58
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.000453 0.000125 0.000000 100/100 2023-12-13 00:44:32.539265 2023-12-13 00:44:28.429219 A al_loss false 0.000453 0.000125 0.000000 100/100 2023-12-13 00:44:34.353914 2023-12-13 00:44:30.493318 A al_jitter false 0.000453 0.000125 0.000000 100/100 2023-12-13 00:44:34.136428 2023-12-13 00:44:26.391239
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.000048 0.000003 0.000000 11/100 A al_loss false 0.000048 0.000003 0.000000 11/100 A al_jitter false 0.000048 0.000003 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 2023-12-13 00:44:50.629357 1 43.79 al_loss true 2023-12-13 00:44:50.262169 1 49.32 al_rtt true 2023-12-13 00:44:52.126222 1 21.36
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.340262 0.379872 34.000000 100/100 2023-12-13 00:44:52.126222 A al_loss true 0.340262 0.379872 34.000000 100/100 2023-12-13 00:44:50.262169 A al_jitter true 0.340262 0.379872 34.000000 100/100 2023-12-13 00:44:50.629357
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 2023-12-13 00:44:58.533050 2023-12-13 00:44:50.629357 2 62.69 al_loss false 2023-12-13 00:44:58.929842 2023-12-13 00:44:50.262169 2 68.78 al_rtt false 2023-12-13 00:44:58.087556 2023-12-13 00:44:52.126222 2 47.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.000404 0.000046 0.000000 100/100 2023-12-13 00:44:58.087556 2023-12-13 00:44:52.126222 A al_loss false 0.000404 0.000046 0.000000 100/100 2023-12-13 00:44:58.929842 2023-12-13 00:44:50.262169 A al_jitter false 0.000404 0.000046 0.000000 100/100 2023-12-13 00:44:58.533050 2023-12-13 00:44:50.629357
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 2023-12-13 00:44:58.533050 2023-12-13 00:44:50.629357 2 42.50 al_loss false 2023-12-13 00:44:58.929842 2023-12-13 00:44:50.262169 2 46.62 al_rtt true 2023-12-13 00:45:02.334944 2023-12-13 00:44:58.087556 3 48.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.783439 0.009065 0.000000 100/100 2023-12-13 00:45:02.334944 2023-12-13 00:44:58.087556 A al_loss false 0.783439 0.009065 0.000000 100/100 2023-12-13 00:44:58.929842 2023-12-13 00:44:50.262169 A al_jitter false 0.783439 0.009065 0.000000 100/100 2023-12-13 00:44:58.533050 2023-12-13 00:44:50.629357
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 2023-12-13 00:44:58.533050 2023-12-13 00:44:50.629357 2 32.32 al_loss false 2023-12-13 00:45:10.905889 2023-12-13 00:45:06.391685 4 53.92 al_rtt false 2023-12-13 00:45:10.408407 2023-12-13 00:45:02.334944 4 57.39
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.000080 0.000000 100/100 2023-12-13 00:45:10.408407 2023-12-13 00:45:02.334944 A al_loss false 0.000435 0.000080 0.000000 100/100 2023-12-13 00:45:10.905889 2023-12-13 00:45:06.391685 A al_jitter false 0.000435 0.000080 0.000000 100/100 2023-12-13 00:44:58.533050 2023-12-13 00:44:50.629357
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 2023-12-13 00:45:14.099540 2023-12-13 00:44:58.533050 3 36.64 al_loss false 2023-12-13 00:45:10.905889 2023-12-13 00:45:06.391685 4 43.23 al_rtt true 2023-12-13 00:45:16.863712 2023-12-13 00:45:10.408407 5 47.67
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.235973 0.342732 0.000000 100/100 2023-12-13 00:45:16.863712 2023-12-13 00:45:10.408407 A al_loss false 0.235973 0.342732 0.000000 100/100 2023-12-13 00:45:10.905889 2023-12-13 00:45:06.391685 A al_jitter true 0.235973 0.342732 0.000000 100/100 2023-12-13 00:45:14.099540 2023-12-13 00:44:58.533050
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 2023-12-13 00:45:22.032947 2023-12-13 00:45:14.099540 4 43.59 al_loss false 2023-12-13 00:45:22.577649 2023-12-13 00:45:18.579596 6 47.29 al_rtt false 2023-12-13 00:45:21.077760 2023-12-13 00:45:16.863712 6 50.22
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.000410 0.000057 0.000000 100/100 2023-12-13 00:45:21.077760 2023-12-13 00:45:16.863712 A al_loss false 0.000410 0.000057 0.000000 100/100 2023-12-13 00:45:22.577649 2023-12-13 00:45:18.579596 A al_jitter false 0.000410 0.000057 0.000000 100/100 2023-12-13 00:45:22.032947 2023-12-13 00:45:14.099540
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 2023-12-13 00:45:39.497639 2023-12-13 00:45:34.730816 2 66.09 al_rtt false 2023-12-13 00:45:39.499599 2023-12-13 00:45:35.486206 2 55.63
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.000390 0.000050 0.000000 100/100 2023-12-13 00:45:39.499599 2023-12-13 00:45:35.486206 A al_loss false 0.000390 0.000050 0.000000 100/100 2023-12-13 00:45:39.497639 2023-12-13 00:45:34.730816 A al_jitter false 0.000390 0.000050 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 2023-12-13 00:45:43.007884 1 26.77 al_loss true 2023-12-13 00:45:42.752767 2023-12-13 00:45:39.497639 3 64.81 al_rtt true 2023-12-13 00:45:44.411789 2023-12-13 00:45:39.499599 3 46.52
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.450254 0.479831 45.000000 100/100 2023-12-13 00:45:44.411789 2023-12-13 00:45:39.499599 A al_loss true 0.450254 0.479831 45.000000 100/100 2023-12-13 00:45:42.752767 2023-12-13 00:45:39.497639 A al_jitter true 0.450254 0.479831 45.000000 100/100 2023-12-13 00:45:43.007884
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 2023-12-13 00:45:51.872059 2023-12-13 00:45:43.007884 2 46.12 al_loss false 2023-12-13 00:45:52.113169 2023-12-13 00:45:42.752767 4 73.54 al_rtt false 2023-12-13 00:45:51.424826 2023-12-13 00:45:44.411789 4 57.39
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.000399 0.000047 0.000000 100/100 2023-12-13 00:45:51.424826 2023-12-13 00:45:44.411789 A al_loss false 0.000399 0.000047 0.000000 100/100 2023-12-13 00:45:52.113169 2023-12-13 00:45:42.752767 A al_jitter false 0.000399 0.000047 0.000000 100/100 2023-12-13 00:45:51.872059 2023-12-13 00:45:43.007884
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 2023-12-13 00:45:51.872059 2023-12-13 00:45:43.007884 2 35.17 al_loss false 2023-12-13 00:45:52.113169 2023-12-13 00:45:42.752767 4 56.07 al_rtt true 2023-12-13 00:45:55.370595 2023-12-13 00:45:51.424826 5 56.31
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.792432 0.009083 0.000000 100/100 2023-12-13 00:45:55.370595 2023-12-13 00:45:51.424826 A al_loss false 0.792432 0.009083 0.000000 100/100 2023-12-13 00:45:52.113169 2023-12-13 00:45:42.752767 A al_jitter false 0.792432 0.009083 0.000000 100/100 2023-12-13 00:45:51.872059 2023-12-13 00:45:43.007884
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 2023-12-13 00:45:51.872059 2023-12-13 00:45:43.007884 2 28.63 al_loss false 2023-12-13 00:46:03.952772 2023-12-13 00:45:59.486918 6 60.06 al_rtt false 2023-12-13 00:46:03.440389 2023-12-13 00:45:55.370595 6 61.68
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.000386 0.000050 0.000000 100/100 2023-12-13 00:46:03.440389 2023-12-13 00:45:55.370595 A al_loss false 0.000386 0.000050 0.000000 100/100 2023-12-13 00:46:03.952772 2023-12-13 00:45:59.486918 A al_jitter false 0.000386 0.000050 0.000000 100/100 2023-12-13 00:45:51.872059 2023-12-13 00:45:43.007884
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 2023-12-13 00:46:07.031023 2023-12-13 00:45:51.872059 3 32.63 al_loss false 2023-12-13 00:46:03.952772 2023-12-13 00:45:59.486918 6 50.45 al_rtt true 2023-12-13 00:46:09.905633 2023-12-13 00:46:03.440389 7 52.59
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.217107 0.312434 0.000000 100/100 2023-12-13 00:46:09.905633 2023-12-13 00:46:03.440389 A al_loss false 0.217107 0.312434 0.000000 100/100 2023-12-13 00:46:03.952772 2023-12-13 00:45:59.486918 A al_jitter true 0.217107 0.312434 0.000000 100/100 2023-12-13 00:46:07.031023 2023-12-13 00:45:51.872059
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 2023-12-13 00:46:15.306697 2023-12-13 00:46:07.031023 4 40.09 al_loss false 2023-12-13 00:46:15.357141 2023-12-13 00:46:11.700879 8 52.04 al_rtt false 2023-12-13 00:46:13.012043 2023-12-13 00:46:09.905633 8 51.93
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.000401 0.000048 0.000000 100/100 2023-12-13 00:46:13.012043 2023-12-13 00:46:09.905633 A al_loss false 0.000401 0.000048 0.000000 100/100 2023-12-13 00:46:15.357141 2023-12-13 00:46:11.700879 A al_jitter false 0.000401 0.000048 0.000000 100/100 2023-12-13 00:46:15.306697 2023-12-13 00:46:07.031023
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 2023-12-13 00:46:32.688906 2023-12-13 00:46:27.717448 2 69.57 al_rtt false 2023-12-13 00:46:32.407625 2023-12-13 00:46:28.467084 2 55.10
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.000419 0.000090 0.000000 100/100 2023-12-13 00:46:32.407625 2023-12-13 00:46:28.467084 A al_loss false 0.000419 0.000090 0.000000 100/100 2023-12-13 00:46:32.688906 2023-12-13 00:46:27.717448 A al_jitter false 0.000419 0.000090 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 2023-12-13 00:46:36.194923 1 24.47 al_loss true 2023-12-13 00:46:35.534181 2023-12-13 00:46:32.688906 3 67.59 al_rtt true 2023-12-13 00:46:37.286553 2023-12-13 00:46:32.407625 3 46.26
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.420238 0.409846 42.000000 100/100 2023-12-13 00:46:37.286553 2023-12-13 00:46:32.407625 A al_loss true 0.420238 0.409846 42.000000 100/100 2023-12-13 00:46:35.534181 2023-12-13 00:46:32.688906 A al_jitter true 0.420238 0.409846 42.000000 100/100 2023-12-13 00:46:36.194923
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 2023-12-13 00:46:44.555052 2023-12-13 00:46:36.194923 2 44.37 al_loss false 2023-12-13 00:46:44.812478 2023-12-13 00:46:35.534181 4 75.65 al_rtt false 2023-12-13 00:46:43.753785 2023-12-13 00:46:37.286553 4 55.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.000397 0.000052 0.000000 100/100 2023-12-13 00:46:43.753785 2023-12-13 00:46:37.286553 A al_loss false 0.000397 0.000052 0.000000 100/100 2023-12-13 00:46:44.812478 2023-12-13 00:46:35.534181 A al_jitter false 0.000397 0.000052 0.000000 100/100 2023-12-13 00:46:44.555052 2023-12-13 00:46:36.194923
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 2023-12-13 00:46:44.555052 2023-12-13 00:46:36.194923 2 33.76 al_loss false 2023-12-13 00:46:44.812478 2023-12-13 00:46:35.534181 4 57.56 al_rtt true 2023-12-13 00:46:47.920148 2023-12-13 00:46:43.753785 5 54.81
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.801447 0.009095 0.000000 100/100 2023-12-13 00:46:47.920148 2023-12-13 00:46:43.753785 A al_loss false 0.801447 0.009095 0.000000 100/100 2023-12-13 00:46:44.812478 2023-12-13 00:46:35.534181 A al_jitter false 0.801447 0.009095 0.000000 100/100 2023-12-13 00:46:44.555052 2023-12-13 00:46:36.194923
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 2023-12-13 00:46:44.555052 2023-12-13 00:46:36.194923 2 27.36 al_loss false 2023-12-13 00:46:56.544356 2023-12-13 00:46:52.022823 6 61.44 al_rtt false 2023-12-13 00:46:56.025514 2023-12-13 00:46:47.920148 6 60.59
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.000388 0.000045 0.000000 100/100 2023-12-13 00:46:56.025514 2023-12-13 00:46:47.920148 A al_loss false 0.000388 0.000045 0.000000 100/100 2023-12-13 00:46:56.544356 2023-12-13 00:46:52.022823 A al_jitter false 0.000388 0.000045 0.000000 100/100 2023-12-13 00:46:44.555052 2023-12-13 00:46:36.194923
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 2023-12-13 00:47:00.039647 2023-12-13 00:46:44.555052 3 30.75 al_loss false 2023-12-13 00:46:56.544356 2023-12-13 00:46:52.022823 6 51.27 al_rtt false 2023-12-13 00:46:56.025514 2023-12-13 00:46:47.920148 6 50.56
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.218807 0.320682 0.000000 100/100 2023-12-13 00:47:02.995630 2023-12-13 00:46:56.025514 A al_loss false 0.218807 0.320682 0.000000 100/100 2023-12-13 00:46:56.544356 2023-12-13 00:46:52.022823 A al_jitter true 0.218807 0.320682 0.000000 100/100 2023-12-13 00:47:00.039647 2023-12-13 00:46:44.555052
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 2023-12-13 00:47:07.552173 2023-12-13 00:47:00.039647 4 37.51 al_loss false 2023-12-13 00:47:08.019333 2023-12-13 00:47:04.249716 8 53.27 al_rtt false 2023-12-13 00:47:06.305873 2023-12-13 00:47:02.995630 8 51.57
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.000409 0.000061 0.000000 100/100 2023-12-13 00:47:06.305873 2023-12-13 00:47:02.995630 A al_loss false 0.000409 0.000061 0.000000 100/100 2023-12-13 00:47:08.019333 2023-12-13 00:47:04.249716 A al_jitter false 0.000409 0.000061 0.000000 100/100 2023-12-13 00:47:07.552173 2023-12-13 00:47:00.039647
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.