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.000054 0.000015 0.000000 9/100 A al_loss false 0.000054 0.000015 0.000000 9/100 A al_jitter false 0.000054 0.000015 0.000000 9/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:25:51.634057 1 51.36 al_loss true 2024-02-26 19:25:51.133114 1 59.08 al_rtt true 2024-02-26 19:25:52.633622 1 36.16
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.400381 0.499685 40.000000 100/100 2024-02-26 19:25:52.633622 A al_loss true 0.400381 0.499685 40.000000 100/100 2024-02-26 19:25:51.133114 A al_jitter true 0.400381 0.499685 40.000000 100/100 2024-02-26 19:25:51.634057
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:26:00.107701 2024-02-26 19:25:51.634057 2 68.12 al_loss false 2024-02-26 19:26:00.457540 2024-02-26 19:25:51.133114 2 75.02 al_rtt false 2024-02-26 19:25:59.302210 2024-02-26 19:25:52.633622 2 53.63
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.000671 0.000070 0.000000 100/100 2024-02-26 19:25:59.302210 2024-02-26 19:25:52.633622 A al_loss false 0.000671 0.000070 0.000000 100/100 2024-02-26 19:26:00.457540 2024-02-26 19:25:51.133114 A al_jitter false 0.000671 0.000070 0.000000 100/100 2024-02-26 19:26:00.107701 2024-02-26 19:25:51.634057
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:26:00.107701 2024-02-26 19:25:51.634057 2 45.91 al_loss false 2024-02-26 19:26:00.457540 2024-02-26 19:25:51.133114 2 50.54 al_rtt true 2024-02-26 19:26:03.768117 2024-02-26 19:25:59.302210 3 53.11
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.792683 0.009065 0.000000 100/100 2024-02-26 19:26:03.768117 2024-02-26 19:25:59.302210 A al_loss false 0.792683 0.009065 0.000000 100/100 2024-02-26 19:26:00.457540 2024-02-26 19:25:51.133114 A al_jitter false 0.792683 0.009065 0.000000 100/100 2024-02-26 19:26:00.107701 2024-02-26 19:25:51.634057
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:26:00.107701 2024-02-26 19:25:51.634057 2 34.85 al_loss false 2024-02-26 19:26:12.393507 2024-02-26 19:26:07.878115 4 56.95 al_rtt false 2024-02-26 19:26:11.890374 2024-02-26 19:26:03.768117 4 60.85
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.000660 0.000034 0.000000 100/100 2024-02-26 19:26:11.890374 2024-02-26 19:26:03.768117 A al_loss false 0.000660 0.000034 0.000000 100/100 2024-02-26 19:26:12.393507 2024-02-26 19:26:07.878115 A al_jitter false 0.000660 0.000034 0.000000 100/100 2024-02-26 19:26:00.107701 2024-02-26 19:25:51.634057
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:26:16.428806 2024-02-26 19:26:00.107701 3 35.62 al_loss false 2024-02-26 19:26:12.393507 2024-02-26 19:26:07.878115 4 45.67 al_rtt false 2024-02-26 19:26:11.890374 2024-02-26 19:26:03.768117 4 48.81
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.203771 0.293446 0.000000 100/100 2024-02-26 19:26:18.815660 2024-02-26 19:26:11.890374 A al_loss false 0.203771 0.293446 0.000000 100/100 2024-02-26 19:26:12.393507 2024-02-26 19:26:07.878115 A al_jitter true 0.203771 0.293446 0.000000 100/100 2024-02-26 19:26:16.428806 2024-02-26 19:26:00.107701
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:26:23.124955 2024-02-26 19:26:16.428806 4 41.94 al_loss false 2024-02-26 19:26:12.393507 2024-02-26 19:26:07.878115 4 38.27 al_rtt false 2024-02-26 19:26:21.122894 2024-02-26 19:26:18.815660 6 47.28
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.000683 0.000121 0.000000 100/100 2024-02-26 19:26:21.122894 2024-02-26 19:26:18.815660 A al_loss false 0.000683 0.000121 0.000000 100/100 2024-02-26 19:26:12.393507 2024-02-26 19:26:07.878115 A al_jitter false 0.000683 0.000121 0.000000 100/100 2024-02-26 19:26:23.124955 2024-02-26 19:26:16.428806
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.000060 0.000018 0.000000 9/100 A al_loss false 0.000060 0.000018 0.000000 9/100 A al_jitter false 0.000060 0.000018 0.000000 9/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:26:39.024838 1 49.43 al_loss true 2024-02-26 19:26:38.576840 1 56.31 al_rtt true 2024-02-26 19:26:39.824055 1 37.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.430340 0.399766 43.000000 100/100 2024-02-26 19:26:39.824055 A al_loss true 0.430340 0.399766 43.000000 100/100 2024-02-26 19:26:38.576840 A al_jitter true 0.430340 0.399766 43.000000 100/100 2024-02-26 19:26:39.024838
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:26:47.553105 2024-02-26 19:26:39.024838 2 68.65 al_loss false 2024-02-26 19:26:47.701935 2024-02-26 19:26:38.576840 2 73.48 al_rtt false 2024-02-26 19:26:46.902417 2024-02-26 19:26:39.824055 2 56.95
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.000671 0.000051 0.000000 100/100 2024-02-26 19:26:46.902417 2024-02-26 19:26:39.824055 A al_loss false 0.000671 0.000051 0.000000 100/100 2024-02-26 19:26:47.701935 2024-02-26 19:26:38.576840 A al_jitter false 0.000671 0.000051 0.000000 100/100 2024-02-26 19:26:47.553105 2024-02-26 19:26:39.024838
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:26:47.553105 2024-02-26 19:26:39.024838 2 46.30 al_loss false 2024-02-26 19:26:47.701935 2024-02-26 19:26:38.576840 2 49.55 al_rtt true 2024-02-26 19:26:51.010527 2024-02-26 19:26:46.902417 3 55.35
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.792699 0.009102 0.000000 100/100 2024-02-26 19:26:51.010527 2024-02-26 19:26:46.902417 A al_loss false 0.792699 0.009102 0.000000 100/100 2024-02-26 19:26:47.701935 2024-02-26 19:26:38.576840 A al_jitter false 0.792699 0.009102 0.000000 100/100 2024-02-26 19:26:47.553105 2024-02-26 19:26:39.024838
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:26:47.553105 2024-02-26 19:26:39.024838 2 35.12 al_loss false 2024-02-26 19:26:59.633313 2024-02-26 19:26:55.121693 4 56.17 al_rtt false 2024-02-26 19:26:59.135396 2024-02-26 19:26:51.010527 4 62.60
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.000662 0.000038 0.000000 100/100 2024-02-26 19:26:59.135396 2024-02-26 19:26:51.010527 A al_loss false 0.000662 0.000038 0.000000 100/100 2024-02-26 19:26:59.633313 2024-02-26 19:26:55.121693 A al_jitter false 0.000662 0.000038 0.000000 100/100 2024-02-26 19:26:47.553105 2024-02-26 19:26:39.024838
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:27:02.933228 2024-02-26 19:26:47.553105 3 38.33 al_loss false 2024-02-26 19:26:59.633313 2024-02-26 19:26:55.121693 4 45.00 al_rtt true 2024-02-26 19:27:05.490256 2024-02-26 19:26:59.135396 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.251547 0.349010 0.000000 100/100 2024-02-26 19:27:05.490256 2024-02-26 19:26:59.135396 A al_loss false 0.251547 0.349010 0.000000 100/100 2024-02-26 19:26:59.633313 2024-02-26 19:26:55.121693 A al_jitter true 0.251547 0.349010 0.000000 100/100 2024-02-26 19:27:02.933228 2024-02-26 19:26:47.553105
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:27:11.014549 2024-02-26 19:27:02.933228 4 45.93 al_loss false 2024-02-26 19:27:11.317867 2024-02-26 19:27:07.655813 6 47.84 al_rtt false 2024-02-26 19:27:09.510214 2024-02-26 19:27:05.490256 6 53.15
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.000667 0.000056 0.000000 100/100 2024-02-26 19:27:09.510214 2024-02-26 19:27:05.490256 A al_loss false 0.000667 0.000056 0.000000 100/100 2024-02-26 19:27:11.317867 2024-02-26 19:27:07.655813 A al_jitter false 0.000667 0.000056 0.000000 100/100 2024-02-26 19:27:11.014549 2024-02-26 19:27:02.933228
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 2024-02-26 19:27:28.491630 2024-02-26 19:27:23.929161 2 75.49 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.000793 0.000724 0.000000 100/100 A al_loss false 0.000793 0.000724 0.000000 100/100 2024-02-26 19:27:28.491630 2024-02-26 19:27:23.929161 A al_jitter false 0.000793 0.000724 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:27:31.391750 1 26.38 al_loss true 2024-02-26 19:27:31.041967 2024-02-26 19:27:28.491630 3 67.12 al_rtt true 2024-02-26 19:27:32.343545 1 18.51
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.480307 0.449719 48.000000 100/100 2024-02-26 19:27:32.343545 A al_loss true 0.480307 0.449719 48.000000 100/100 2024-02-26 19:27:31.041967 2024-02-26 19:27:28.491630 A al_jitter true 0.480307 0.449719 48.000000 100/100 2024-02-26 19:27:31.391750
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:27:39.514335 2024-02-26 19:27:31.391750 2 45.31 al_loss false 2024-02-26 19:27:39.767478 2024-02-26 19:27:31.041967 4 74.16 al_rtt false 2024-02-26 19:27:38.662494 2024-02-26 19:27:32.343545 2 35.26
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.000660 0.000081 0.000000 100/100 2024-02-26 19:27:38.662494 2024-02-26 19:27:32.343545 A al_loss false 0.000660 0.000081 0.000000 100/100 2024-02-26 19:27:39.767478 2024-02-26 19:27:31.041967 A al_jitter false 0.000660 0.000081 0.000000 100/100 2024-02-26 19:27:39.514335 2024-02-26 19:27:31.391750
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:27:39.514335 2024-02-26 19:27:31.391750 2 33.93 al_loss false 2024-02-26 19:27:39.767478 2024-02-26 19:27:31.041967 4 55.54 al_rtt true 2024-02-26 19:27:43.273128 2024-02-26 19:27:38.662494 3 39.63
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.801679 0.009071 0.000000 100/100 2024-02-26 19:27:43.273128 2024-02-26 19:27:38.662494 A al_loss false 0.801679 0.009071 0.000000 100/100 2024-02-26 19:27:39.767478 2024-02-26 19:27:31.041967 A al_jitter false 0.801679 0.009071 0.000000 100/100 2024-02-26 19:27:39.514335 2024-02-26 19:27:31.391750
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:27:39.514335 2024-02-26 19:27:31.391750 2 27.26 al_loss false 2024-02-26 19:27:51.948724 2024-02-26 19:27:47.435679 6 59.75 al_rtt false 2024-02-26 19:27:51.445156 2024-02-26 19:27:43.273128 4 48.63
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.000658 0.000072 0.000000 100/100 2024-02-26 19:27:51.445156 2024-02-26 19:27:43.273128 A al_loss false 0.000658 0.000072 0.000000 100/100 2024-02-26 19:27:51.948724 2024-02-26 19:27:47.435679 A al_jitter false 0.000658 0.000072 0.000000 100/100 2024-02-26 19:27:39.514335 2024-02-26 19:27:31.391750
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:27:55.679998 2024-02-26 19:27:39.514335 3 30.01 al_loss false 2024-02-26 19:27:51.948724 2024-02-26 19:27:47.435679 6 49.74 al_rtt false 2024-02-26 19:27:51.445156 2024-02-26 19:27:43.273128 4 40.48
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.179490 0.256040 0.000000 100/100 2024-02-26 19:27:51.445156 2024-02-26 19:27:43.273128 A al_loss false 0.179490 0.256040 0.000000 100/100 2024-02-26 19:27:51.948724 2024-02-26 19:27:47.435679 A al_jitter true 0.179490 0.256040 0.000000 100/100 2024-02-26 19:27:55.679998 2024-02-26 19:27:39.514335
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:28:03.382848 2024-02-26 19:27:55.679998 4 37.98 al_loss false 2024-02-26 19:28:03.445922 2024-02-26 19:27:59.922520 8 51.19 al_rtt false 2024-02-26 19:28:02.179794 2024-02-26 19:27:58.727251 6 43.07
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.000644 0.000036 0.000000 100/100 2024-02-26 19:28:02.179794 2024-02-26 19:27:58.727251 A al_loss false 0.000644 0.000036 0.000000 100/100 2024-02-26 19:28:03.445922 2024-02-26 19:27:59.922520 A al_jitter false 0.000644 0.000036 0.000000 100/100 2024-02-26 19:28:03.382848 2024-02-26 19:27:55.679998
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 2024-02-26 19:28:20.825578 2024-02-26 19:28:16.100656 2 65.71 al_rtt false 2024-02-26 19:28:20.826725 2024-02-26 19:28:16.853371 2 55.18
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.000635 0.000092 0.000000 100/100 2024-02-26 19:28:20.826725 2024-02-26 19:28:16.853371 A al_loss false 0.000635 0.000092 0.000000 100/100 2024-02-26 19:28:20.825578 2024-02-26 19:28:16.100656 A al_jitter false 0.000635 0.000092 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:28:24.523184 1 25.27 al_loss true 2024-02-26 19:28:24.121770 2024-02-26 19:28:20.825578 3 64.09 al_rtt true 2024-02-26 19:28:25.824646 2024-02-26 19:28:20.826725 3 45.47
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.370386 0.439733 37.000000 100/100 2024-02-26 19:28:25.824646 2024-02-26 19:28:20.826725 A al_loss true 0.370386 0.439733 37.000000 100/100 2024-02-26 19:28:24.121770 2024-02-26 19:28:20.825578 A al_jitter true 0.370386 0.439733 37.000000 100/100 2024-02-26 19:28:24.523184
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:28:32.643922 2024-02-26 19:28:24.523184 2 42.52 al_loss false 2024-02-26 19:28:32.994673 2024-02-26 19:28:24.121770 4 71.21 al_rtt false 2024-02-26 19:28:31.493502 2024-02-26 19:28:25.824646 4 50.47
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.000674 0.000070 0.000000 100/100 2024-02-26 19:28:31.493502 2024-02-26 19:28:25.824646 A al_loss false 0.000674 0.000070 0.000000 100/100 2024-02-26 19:28:32.994673 2024-02-26 19:28:24.121770 A al_jitter false 0.000674 0.000070 0.000000 100/100 2024-02-26 19:28:32.643922 2024-02-26 19:28:24.523184
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:28:32.643922 2024-02-26 19:28:24.523184 2 32.37 al_loss false 2024-02-26 19:28:32.994673 2024-02-26 19:28:24.121770 4 54.21 al_rtt true 2024-02-26 19:28:36.603806 2024-02-26 19:28:31.493502 5 50.91
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.792671 0.009075 0.000000 100/100 2024-02-26 19:28:36.603806 2024-02-26 19:28:31.493502 A al_loss false 0.792671 0.009075 0.000000 100/100 2024-02-26 19:28:32.994673 2024-02-26 19:28:24.121770 A al_jitter false 0.792671 0.009075 0.000000 100/100 2024-02-26 19:28:32.643922 2024-02-26 19:28:24.523184
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:28:32.643922 2024-02-26 19:28:24.523184 2 26.25 al_loss false 2024-02-26 19:28:45.226078 2024-02-26 19:28:40.709303 6 58.56 al_rtt false 2024-02-26 19:28:44.725738 2024-02-26 19:28:36.603806 6 57.41
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.000650 0.000045 0.000000 100/100 2024-02-26 19:28:44.725738 2024-02-26 19:28:36.603806 A al_loss false 0.000650 0.000045 0.000000 100/100 2024-02-26 19:28:45.226078 2024-02-26 19:28:40.709303 A al_jitter false 0.000650 0.000045 0.000000 100/100 2024-02-26 19:28:32.643922 2024-02-26 19:28:24.523184
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:28:48.352281 2024-02-26 19:28:32.643922 3 30.75 al_loss false 2024-02-26 19:28:45.226078 2024-02-26 19:28:40.709303 6 49.04 al_rtt true 2024-02-26 19:28:50.985408 2024-02-26 19:28:44.725738 7 49.72
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.218373 0.361543 0.000000 100/100 2024-02-26 19:28:50.985408 2024-02-26 19:28:44.725738 A al_loss false 0.218373 0.361543 0.000000 100/100 2024-02-26 19:28:45.226078 2024-02-26 19:28:40.709303 A al_jitter true 0.218373 0.361543 0.000000 100/100 2024-02-26 19:28:48.352281 2024-02-26 19:28:32.643922
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:28:56.766679 2024-02-26 19:28:48.352281 4 38.61 al_loss false 2024-02-26 19:28:57.066633 2024-02-26 19:28:53.152965 8 51.44 al_rtt false 2024-02-26 19:28:54.308237 2024-02-26 19:28:50.985408 8 49.23
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.000664 0.000075 0.000000 100/100 2024-02-26 19:28:54.308237 2024-02-26 19:28:50.985408 A al_loss false 0.000664 0.000075 0.000000 100/100 2024-02-26 19:28:57.066633 2024-02-26 19:28:53.152965 A al_jitter false 0.000664 0.000075 0.000000 100/100 2024-02-26 19:28:56.766679 2024-02-26 19:28:48.352281
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.