Check Icmp Operation
This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the ICMP protocol.
Test IPv4 Destination
Description
In this scenario, ICMP NSM operations are configured in DUT0 (using an IPv4 destination address).
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.215.200.100/24
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 icmp 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
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.000032 0.000011 0.000000 7/100 A al_loss false 0.000032 0.000011 0.000000 7/100 A al_jitter false 0.000032 0.000011 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:40:46.120541 1 50.88 al_loss true 2023-12-13 00:40:45.688622 1 57.80 al_rtt true 2023-12-13 00:40:46.669446 1 42.20
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.520219 0.489819 52.000000 100/100 2023-12-13 00:40:46.669446 A al_loss true 0.520219 0.489819 52.000000 100/100 2023-12-13 00:40:45.688622 A al_jitter true 0.520219 0.489819 52.000000 100/100 2023-12-13 00:40:46.120541
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:40:54.499015 2023-12-13 00:40:46.120541 2 68.98 al_loss false 2023-12-13 00:40:54.798191 2023-12-13 00:40:45.688622 2 75.05 al_rtt false 2023-12-13 00:40:53.801836 2023-12-13 00:40:46.669446 2 58.75
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.000387 0.000060 0.000000 100/100 2023-12-13 00:40:53.801836 2023-12-13 00:40:46.669446 A al_loss false 0.000387 0.000060 0.000000 100/100 2023-12-13 00:40:54.798191 2023-12-13 00:40:45.688622 A al_jitter false 0.000387 0.000060 0.000000 100/100 2023-12-13 00:40:54.499015 2023-12-13 00:40:46.120541
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:40:54.499015 2023-12-13 00:40:46.120541 2 46.11 al_loss false 2023-12-13 00:40:54.798191 2023-12-13 00:40:45.688622 2 50.16 al_rtt true 2023-12-13 00:40:58.001260 2023-12-13 00:40:53.801836 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.801389 0.009063 0.000000 100/100 2023-12-13 00:40:58.001260 2023-12-13 00:40:53.801836 A al_loss false 0.801389 0.009063 0.000000 100/100 2023-12-13 00:40:54.798191 2023-12-13 00:40:45.688622 A al_jitter false 0.801389 0.009063 0.000000 100/100 2023-12-13 00:40:54.499015 2023-12-13 00:40:46.120541
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:40:54.499015 2023-12-13 00:40:46.120541 2 34.93 al_loss false 2023-12-13 00:41:06.618616 2023-12-13 00:41:02.104438 4 56.82 al_rtt false 2023-12-13 00:41:06.113167 2023-12-13 00:40:58.001260 4 63.58
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.000371 0.000052 0.000000 100/100 2023-12-13 00:41:06.113167 2023-12-13 00:40:58.001260 A al_loss false 0.000371 0.000052 0.000000 100/100 2023-12-13 00:41:06.618616 2023-12-13 00:41:02.104438 A al_jitter false 0.000371 0.000052 0.000000 100/100 2023-12-13 00:40:54.499015 2023-12-13 00:40:46.120541
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:41:09.771396 2023-12-13 00:40:54.499015 3 38.60 al_loss false 2023-12-13 00:41:06.618616 2023-12-13 00:41:02.104438 4 45.54 al_rtt true 2023-12-13 00:41:12.658394 2023-12-13 00:41:06.113167 5 51.90
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.242041 0.373867 0.000000 100/100 2023-12-13 00:41:12.658394 2023-12-13 00:41:06.113167 A al_loss false 0.242041 0.373867 0.000000 100/100 2023-12-13 00:41:06.618616 2023-12-13 00:41:02.104438 A al_jitter true 0.242041 0.373867 0.000000 100/100 2023-12-13 00:41:09.771396 2023-12-13 00:40:54.499015
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:41:17.685311 2023-12-13 00:41:09.771396 4 45.66 al_loss false 2023-12-13 00:41:06.618616 2023-12-13 00:41:02.104438 4 38.19 al_rtt false 2023-12-13 00:41:16.183177 2023-12-13 00:41:12.658394 6 52.61
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.000386 0.000067 0.000000 100/100 2023-12-13 00:41:16.183177 2023-12-13 00:41:12.658394 A al_loss false 0.000386 0.000067 0.000000 100/100 2023-12-13 00:41:06.618616 2023-12-13 00:41:02.104438 A al_jitter false 0.000386 0.000067 0.000000 100/100 2023-12-13 00:41:17.685311 2023-12-13 00:41:09.771396
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, ICMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address).
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.215.200.100/24
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 icmp 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 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.000036 0.000006 0.000000 9/100 A al_loss false 0.000036 0.000006 0.000000 9/100 A al_jitter false 0.000036 0.000006 0.000000 9/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2023-12-13 00:41:31.807609 1 51.05 al_loss true 2023-12-13 00:41:31.468707 1 56.25 al_rtt true 2023-12-13 00:41:32.475314 1 40.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.450207 0.459844 45.000000 100/100 2023-12-13 00:41:32.475314 A al_loss true 0.450207 0.459844 45.000000 100/100 2023-12-13 00:41:31.468707 A al_jitter true 0.450207 0.459844 45.000000 100/100 2023-12-13 00:41:31.807609
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:41:40.349077 2023-12-13 00:41:31.807609 2 67.28 al_loss false 2023-12-13 00:41:40.737360 2023-12-13 00:41:31.468707 2 73.04 al_rtt false 2023-12-13 00:41:39.599421 2023-12-13 00:41:32.475314 2 56.10
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.000391 0.000053 0.000000 100/100 2023-12-13 00:41:39.599421 2023-12-13 00:41:32.475314 A al_loss false 0.000391 0.000053 0.000000 100/100 2023-12-13 00:41:40.737360 2023-12-13 00:41:31.468707 A al_jitter false 0.000391 0.000053 0.000000 100/100 2023-12-13 00:41:40.349077 2023-12-13 00:41:31.807609
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:41:40.349077 2023-12-13 00:41:31.807609 2 45.98 al_loss false 2023-12-13 00:41:40.737360 2023-12-13 00:41:31.468707 2 49.91 al_rtt true 2023-12-13 00:41:44.040963 2023-12-13 00:41:39.599421 3 55.17
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.783416 0.009066 0.000000 100/100 2023-12-13 00:41:44.040963 2023-12-13 00:41:39.599421 A al_loss false 0.783416 0.009066 0.000000 100/100 2023-12-13 00:41:40.737360 2023-12-13 00:41:31.468707 A al_jitter false 0.783416 0.009066 0.000000 100/100 2023-12-13 00:41:40.349077 2023-12-13 00:41:31.807609
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:41:40.349077 2023-12-13 00:41:31.807609 2 34.84 al_loss false 2023-12-13 00:41:52.657830 2023-12-13 00:41:48.148207 4 56.21 al_rtt false 2023-12-13 00:41:52.170172 2023-12-13 00:41:44.040963 4 62.21
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000370 0.000047 0.000000 100/100 2023-12-13 00:41:52.170172 2023-12-13 00:41:44.040963 A al_loss false 0.000370 0.000047 0.000000 100/100 2023-12-13 00:41:52.657830 2023-12-13 00:41:48.148207 A al_jitter false 0.000370 0.000047 0.000000 100/100 2023-12-13 00:41:40.349077 2023-12-13 00:41:31.807609
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:41:56.202166 2023-12-13 00:41:40.349077 3 37.35 al_loss false 2023-12-13 00:41:52.657830 2023-12-13 00:41:48.148207 4 45.28 al_rtt true 2023-12-13 00:41:58.500073 2023-12-13 00:41:52.170172 5 51.84
Step 19: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.244948 0.305462 0.000000 100/100 2023-12-13 00:41:58.500073 2023-12-13 00:41:52.170172 A al_loss false 0.244948 0.305462 0.000000 100/100 2023-12-13 00:41:52.657830 2023-12-13 00:41:48.148207 A al_jitter true 0.244948 0.305462 0.000000 100/100 2023-12-13 00:41:56.202166 2023-12-13 00:41:40.349077
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:42:03.932588 2023-12-13 00:41:56.202166 4 44.94 al_loss false 2023-12-13 00:41:52.657830 2023-12-13 00:41:48.148207 4 38.06 al_rtt false 2023-12-13 00:42:01.727791 2023-12-13 00:41:58.500073 6 51.04
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.000390 0.000053 0.000000 100/100 2023-12-13 00:42:01.727791 2023-12-13 00:41:58.500073 A al_loss false 0.000390 0.000053 0.000000 100/100 2023-12-13 00:41:52.657830 2023-12-13 00:41:48.148207 A al_jitter false 0.000390 0.000053 0.000000 100/100 2023-12-13 00:42:03.932588 2023-12-13 00:41:56.202166
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, ICMP NSM operations are configured in DUT0 (using an IPv6 destination address).
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10::3/64
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 icmp 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
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:42:20.092893 2023-12-13 00:42:15.524413 2 65.42 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.000358 0.000052 0.000000 100/100 A al_loss false 0.000358 0.000052 0.000000 100/100 2023-12-13 00:42:20.092893 2023-12-13 00:42:15.524413 A al_jitter false 0.000358 0.000052 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:42:23.536238 1 27.17 al_loss true 2023-12-13 00:42:23.341667 2023-12-13 00:42:20.092893 3 64.13 al_rtt true 2023-12-13 00:42:25.239698 1 13.96
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.430211 0.419860 43.000000 100/100 2023-12-13 00:42:25.239698 A al_loss true 0.430211 0.419860 43.000000 100/100 2023-12-13 00:42:23.341667 2023-12-13 00:42:20.092893 A al_jitter true 0.430211 0.419860 43.000000 100/100 2023-12-13 00:42:23.536238
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:42:32.479075 2023-12-13 00:42:23.536238 2 47.14 al_loss false 2023-12-13 00:42:32.670720 2023-12-13 00:42:23.341667 4 73.29 al_rtt false 2023-12-13 00:42:31.718584 2023-12-13 00:42:25.239698 2 34.16
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.000361 0.000043 0.000000 100/100 2023-12-13 00:42:31.718584 2023-12-13 00:42:25.239698 A al_loss false 0.000361 0.000043 0.000000 100/100 2023-12-13 00:42:32.670720 2023-12-13 00:42:23.341667 A al_jitter false 0.000361 0.000043 0.000000 100/100 2023-12-13 00:42:32.479075 2023-12-13 00:42:23.536238
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:42:32.479075 2023-12-13 00:42:23.536238 2 35.91 al_loss false 2023-12-13 00:42:32.670720 2023-12-13 00:42:23.341667 4 55.82 al_rtt true 2023-12-13 00:42:35.891207 2023-12-13 00:42:31.718584 3 38.68
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.792402 0.009064 0.000000 100/100 2023-12-13 00:42:35.891207 2023-12-13 00:42:31.718584 A al_loss false 0.792402 0.009064 0.000000 100/100 2023-12-13 00:42:32.670720 2023-12-13 00:42:23.341667 A al_jitter false 0.792402 0.009064 0.000000 100/100 2023-12-13 00:42:32.479075 2023-12-13 00:42:23.536238
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:42:32.479075 2023-12-13 00:42:23.536238 2 28.98 al_loss false 2023-12-13 00:42:44.547845 2023-12-13 00:42:40.043479 6 59.65 al_rtt false 2023-12-13 00:42:44.048008 2023-12-13 00:42:35.891207 4 47.44
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000367 0.000055 0.000000 100/100 2023-12-13 00:42:44.048008 2023-12-13 00:42:35.891207 A al_loss false 0.000367 0.000055 0.000000 100/100 2023-12-13 00:42:44.547845 2023-12-13 00:42:40.043479 A al_jitter false 0.000367 0.000055 0.000000 100/100 2023-12-13 00:42:32.479075 2023-12-13 00:42:23.536238
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:42:48.261670 2023-12-13 00:42:32.479075 3 31.53 al_loss false 2023-12-13 00:42:44.547845 2023-12-13 00:42:40.043479 6 50.05 al_rtt false 2023-12-13 00:42:44.048008 2023-12-13 00:42:35.891207 4 39.80
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.168793 0.230691 0.000000 100/100 2023-12-13 00:42:44.048008 2023-12-13 00:42:35.891207 A al_loss false 0.168793 0.230691 0.000000 100/100 2023-12-13 00:42:44.547845 2023-12-13 00:42:40.043479 A al_jitter true 0.168793 0.230691 0.000000 100/100 2023-12-13 00:42:48.261670 2023-12-13 00:42:32.479075
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:42:55.571633 2023-12-13 00:42:48.261670 4 38.25 al_loss false 2023-12-13 00:42:56.175420 2023-12-13 00:42:52.316014 8 52.40 al_rtt false 2023-12-13 00:42:54.019974 2023-12-13 00:42:51.536104 6 40.29
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000378 0.000059 0.000000 100/100 2023-12-13 00:42:54.019974 2023-12-13 00:42:51.536104 A al_loss false 0.000378 0.000059 0.000000 100/100 2023-12-13 00:42:56.175420 2023-12-13 00:42:52.316014 A al_jitter false 0.000378 0.000059 0.000000 100/100 2023-12-13 00:42:55.571633 2023-12-13 00:42:48.261670
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, ICMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address).
Scenario
Step 1: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10::3/64
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 icmp 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 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:43:12.471854 2023-12-13 00:43:07.699254 2 66.50 al_rtt false 2023-12-13 00:43:12.393332 2023-12-13 00:43:08.457461 2 54.78
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.000377 0.000069 0.000000 100/100 2023-12-13 00:43:12.393332 2023-12-13 00:43:08.457461 A al_loss false 0.000377 0.000069 0.000000 100/100 2023-12-13 00:43:12.471854 2023-12-13 00:43:07.699254 A al_jitter false 0.000377 0.000069 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:43:16.464119 1 22.55 al_loss true 2023-12-13 00:43:15.866228 2023-12-13 00:43:12.471854 3 63.47 al_rtt true 2023-12-13 00:43:17.063360 2023-12-13 00:43:12.393332 3 47.94
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.490191 0.399869 49.000000 100/100 2023-12-13 00:43:17.063360 2023-12-13 00:43:12.393332 A al_loss true 0.490191 0.399869 49.000000 100/100 2023-12-13 00:43:15.866228 2023-12-13 00:43:12.471854 A al_jitter true 0.490191 0.399869 49.000000 100/100 2023-12-13 00:43:16.464119
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:43:24.187914 2023-12-13 00:43:16.464119 2 41.01 al_loss false 2023-12-13 00:43:24.595868 2023-12-13 00:43:15.866228 4 71.71 al_rtt false 2023-12-13 00:43:23.527909 2023-12-13 00:43:17.063360 4 55.21
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.000368 0.000046 0.000000 100/100 2023-12-13 00:43:23.527909 2023-12-13 00:43:17.063360 A al_loss false 0.000368 0.000046 0.000000 100/100 2023-12-13 00:43:24.595868 2023-12-13 00:43:15.866228 A al_jitter false 0.000368 0.000046 0.000000 100/100 2023-12-13 00:43:24.187914 2023-12-13 00:43:16.464119
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:43:24.187914 2023-12-13 00:43:16.464119 2 31.15 al_loss false 2023-12-13 00:43:24.595868 2023-12-13 00:43:15.866228 4 54.46 al_rtt true 2023-12-13 00:43:27.892563 2023-12-13 00:43:23.527909 5 54.83
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.801388 0.009064 0.000000 100/100 2023-12-13 00:43:27.892563 2023-12-13 00:43:23.527909 A al_loss false 0.801388 0.009064 0.000000 100/100 2023-12-13 00:43:24.595868 2023-12-13 00:43:15.866228 A al_jitter false 0.801388 0.009064 0.000000 100/100 2023-12-13 00:43:24.187914 2023-12-13 00:43:16.464119
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:43:24.187914 2023-12-13 00:43:16.464119 2 25.20 al_loss false 2023-12-13 00:43:36.602707 2023-12-13 00:43:32.092171 6 58.77 al_rtt false 2023-12-13 00:43:36.111419 2023-12-13 00:43:27.892563 6 60.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.000378 0.000063 0.000000 100/100 2023-12-13 00:43:36.111419 2023-12-13 00:43:27.892563 A al_loss false 0.000378 0.000063 0.000000 100/100 2023-12-13 00:43:36.602707 2023-12-13 00:43:32.092171 A al_jitter false 0.000378 0.000063 0.000000 100/100 2023-12-13 00:43:24.187914 2023-12-13 00:43:16.464119
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:43:39.487632 2023-12-13 00:43:24.187914 3 30.60 al_loss false 2023-12-13 00:43:36.602707 2023-12-13 00:43:32.092171 6 49.09 al_rtt true 2023-12-13 00:43:42.196929 2023-12-13 00:43:36.111419 7 52.89
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.243246 0.336620 0.000000 100/100 2023-12-13 00:43:42.196929 2023-12-13 00:43:36.111419 A al_loss false 0.243246 0.336620 0.000000 100/100 2023-12-13 00:43:36.602707 2023-12-13 00:43:32.092171 A al_jitter true 0.243246 0.336620 0.000000 100/100 2023-12-13 00:43:39.487632 2023-12-13 00:43:24.187914
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:43:47.628573 2023-12-13 00:43:39.487632 4 37.24 al_loss false 2023-12-13 00:43:36.602707 2023-12-13 00:43:32.092171 6 42.29 al_rtt false 2023-12-13 00:43:45.772057 2023-12-13 00:43:42.196929 8 52.10
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.000367 0.000057 0.000000 100/100 2023-12-13 00:43:45.772057 2023-12-13 00:43:42.196929 A al_loss false 0.000367 0.000057 0.000000 100/100 2023-12-13 00:43:36.602707 2023-12-13 00:43:32.092171 A al_jitter false 0.000367 0.000057 0.000000 100/100 2023-12-13 00:43:47.628573 2023-12-13 00:43:39.487632
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.