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.000022 0.000005 0.000000 6/100 A al_loss false 0.000022 0.000005 0.000000 6/100 A al_jitter false 0.000022 0.000005 0.000000 6/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-10-10 07:35:53.291530 1 54.55 al_loss true 2024-10-10 07:35:52.741979 1 63.75 al_rtt true 2024-10-10 07:35:54.358079 1 36.80
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.410260 0.489804 41.000000 99/100 2024-10-10 07:35:54.358079 A al_loss true 0.410260 0.489804 41.000000 99/100 2024-10-10 07:35:52.741979 A al_jitter true 0.410260 0.489804 41.000000 99/100 2024-10-10 07:35:53.291530
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:36:01.378860 2024-10-10 07:35:53.291530 2 69.68 al_loss false 2024-10-10 07:36:01.569272 2024-10-10 07:35:52.741979 2 76.07 al_rtt false 2024-10-10 07:36:00.414684 2024-10-10 07:35:54.358079 2 52.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.000559 0.000133 0.000000 100/100 2024-10-10 07:36:00.414684 2024-10-10 07:35:54.358079 A al_loss false 0.000559 0.000133 0.000000 100/100 2024-10-10 07:36:01.569272 2024-10-10 07:35:52.741979 A al_jitter false 0.000559 0.000133 0.000000 100/100 2024-10-10 07:36:01.378860 2024-10-10 07:35:53.291530
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:36:01.378860 2024-10-10 07:35:53.291530 2 46.80 al_loss false 2024-10-10 07:36:01.569272 2024-10-10 07:35:52.741979 2 51.09 al_rtt true 2024-10-10 07:36:04.721628 2024-10-10 07:36:00.414684 3 53.15
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.774574 0.009154 0.000000 100/100 2024-10-10 07:36:04.721628 2024-10-10 07:36:00.414684 A al_loss false 0.774574 0.009154 0.000000 100/100 2024-10-10 07:36:01.569272 2024-10-10 07:35:52.741979 A al_jitter false 0.774574 0.009154 0.000000 100/100 2024-10-10 07:36:01.378860 2024-10-10 07:35:53.291530
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:36:01.378860 2024-10-10 07:35:53.291530 2 35.50 al_loss false 2024-10-10 07:36:13.093280 2024-10-10 07:36:08.580426 4 58.57 al_rtt false 2024-10-10 07:36:12.593280 2024-10-10 07:36:04.721628 4 61.16
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.000538 0.000153 0.000000 100/100 2024-10-10 07:36:12.593280 2024-10-10 07:36:04.721628 A al_loss false 0.000538 0.000153 0.000000 100/100 2024-10-10 07:36:13.093280 2024-10-10 07:36:08.580426 A al_jitter false 0.000538 0.000153 0.000000 100/100 2024-10-10 07:36:01.378860 2024-10-10 07:35:53.291530
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-10 07:36:16.091315 2024-10-10 07:36:01.378860 3 38.61 al_loss false 2024-10-10 07:36:13.093280 2024-10-10 07:36:08.580426 4 46.97 al_rtt true 2024-10-10 07:36:18.221532 2024-10-10 07:36:12.593280 5 51.68
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.250103 0.315270 0.000000 100/100 2024-10-10 07:36:18.221532 2024-10-10 07:36:12.593280 A al_loss false 0.250103 0.315270 0.000000 100/100 2024-10-10 07:36:13.093280 2024-10-10 07:36:08.580426 A al_jitter true 0.250103 0.315270 0.000000 100/100 2024-10-10 07:36:16.091315 2024-10-10 07:36:01.378860
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:36:23.524410 2024-10-10 07:36:16.091315 4 45.76 al_loss false 2024-10-10 07:36:24.074499 2024-10-10 07:36:20.260799 6 50.58 al_rtt false 2024-10-10 07:36:22.222185 2024-10-10 07:36:18.221532 6 52.87
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.000489 0.000138 0.000000 100/100 2024-10-10 07:36:22.222185 2024-10-10 07:36:18.221532 A al_loss false 0.000489 0.000138 0.000000 100/100 2024-10-10 07:36:24.074499 2024-10-10 07:36:20.260799 A al_jitter false 0.000489 0.000138 0.000000 100/100 2024-10-10 07:36:23.524410 2024-10-10 07:36:16.091315
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.000026 0.000008 0.000000 6/100 A al_loss false 0.000026 0.000008 0.000000 6/100 A al_jitter false 0.000026 0.000008 0.000000 6/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-10-10 07:36:33.542109 1 51.17 al_loss true 2024-10-10 07:36:32.945024 1 61.16 al_rtt true 2024-10-10 07:36:34.343092 1 37.69
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.430324 0.389893 43.000000 99/100 2024-10-10 07:36:34.343092 A al_loss true 0.430324 0.389893 43.000000 99/100 2024-10-10 07:36:32.945024 A al_jitter true 0.430324 0.389893 43.000000 99/100 2024-10-10 07:36:33.542109
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:36:41.317432 2024-10-10 07:36:33.542109 2 67.58 al_loss false 2024-10-10 07:36:41.863742 2024-10-10 07:36:32.945024 2 77.48 al_rtt false 2024-10-10 07:36:40.713259 2024-10-10 07:36:34.343092 2 55.35
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000522 0.000136 0.000000 100/100 2024-10-10 07:36:40.713259 2024-10-10 07:36:34.343092 A al_loss false 0.000522 0.000136 0.000000 100/100 2024-10-10 07:36:41.863742 2024-10-10 07:36:32.945024 A al_jitter false 0.000522 0.000136 0.000000 100/100 2024-10-10 07:36:41.317432 2024-10-10 07:36:33.542109
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:36:41.317432 2024-10-10 07:36:33.542109 2 45.31 al_loss false 2024-10-10 07:36:41.863742 2024-10-10 07:36:32.945024 2 51.96 al_rtt true 2024-10-10 07:36:44.668480 2024-10-10 07:36:40.713259 3 55.34
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.774641 0.009201 0.000000 100/100 2024-10-10 07:36:44.668480 2024-10-10 07:36:40.713259 A al_loss false 0.774641 0.009201 0.000000 100/100 2024-10-10 07:36:41.863742 2024-10-10 07:36:32.945024 A al_jitter false 0.774641 0.009201 0.000000 100/100 2024-10-10 07:36:41.317432 2024-10-10 07:36:33.542109
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:36:41.317432 2024-10-10 07:36:33.542109 2 34.33 al_loss false 2024-10-10 07:36:53.000632 2024-10-10 07:36:48.477260 4 59.34 al_rtt false 2024-10-10 07:36:52.490931 2024-10-10 07:36:44.668480 4 62.66
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.000465 0.000172 0.000000 100/100 2024-10-10 07:36:52.490931 2024-10-10 07:36:44.668480 A al_loss false 0.000465 0.000172 0.000000 100/100 2024-10-10 07:36:53.000632 2024-10-10 07:36:48.477260 A al_jitter false 0.000465 0.000172 0.000000 100/100 2024-10-10 07:36:41.317432 2024-10-10 07:36:33.542109
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-10 07:36:55.645283 2024-10-10 07:36:41.317432 3 39.01 al_loss false 2024-10-10 07:36:53.000632 2024-10-10 07:36:48.477260 4 47.57 al_rtt false 2024-10-10 07:36:52.490931 2024-10-10 07:36:44.668480 4 50.23
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.197837 0.260008 0.000000 100/100 2024-10-10 07:36:52.490931 2024-10-10 07:36:44.668480 A al_loss false 0.197837 0.260008 0.000000 100/100 2024-10-10 07:36:53.000632 2024-10-10 07:36:48.477260 A al_jitter true 0.197837 0.260008 0.000000 100/100 2024-10-10 07:36:55.645283 2024-10-10 07:36:41.317432
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:37:03.128227 2024-10-10 07:36:55.645283 4 45.08 al_loss false 2024-10-10 07:36:53.000632 2024-10-10 07:36:48.477260 4 39.70 al_rtt false 2024-10-10 07:36:52.490931 2024-10-10 07:36:44.668480 4 41.92
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.000560 0.000143 0.000000 100/100 2024-10-10 07:36:52.490931 2024-10-10 07:36:44.668480 A al_loss false 0.000560 0.000143 0.000000 100/100 2024-10-10 07:36:53.000632 2024-10-10 07:36:48.477260 A al_jitter false 0.000560 0.000143 0.000000 100/100 2024-10-10 07:37:03.128227 2024-10-10 07:36:55.645283
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-10-10 07:37:16.617894 2024-10-10 07:37:11.900927 2 70.03 al_rtt false 2024-10-10 07:37:16.585409 2024-10-10 07:37:12.652356 2 58.41
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.009301 0.003343 0.000000 100/100 2024-10-10 07:37:16.585409 2024-10-10 07:37:12.652356 A al_loss false 0.009301 0.003343 0.000000 100/100 2024-10-10 07:37:16.617894 2024-10-10 07:37:11.900927 A al_jitter false 0.009301 0.003343 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-10 07:37:19.676167 1 27.02 al_loss true 2024-10-10 07:37:19.344823 2024-10-10 07:37:16.617894 3 67.68 al_rtt true 2024-10-10 07:37:20.669354 2024-10-10 07:37:16.585409 3 50.71
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.450273 0.439819 45.000000 100/100 2024-10-10 07:37:20.669354 2024-10-10 07:37:16.585409 A al_loss true 0.450273 0.439819 45.000000 100/100 2024-10-10 07:37:19.344823 2024-10-10 07:37:16.617894 A al_jitter true 0.450273 0.439819 45.000000 100/100 2024-10-10 07:37:19.676167
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:37:27.801703 2024-10-10 07:37:19.676167 2 45.32 al_loss false 2024-10-10 07:37:28.193369 2024-10-10 07:37:19.344823 4 75.68 al_rtt false 2024-10-10 07:37:26.991448 2024-10-10 07:37:20.669354 4 57.22
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.000475 0.000131 0.000000 100/100 2024-10-10 07:37:26.991448 2024-10-10 07:37:20.669354 A al_loss false 0.000475 0.000131 0.000000 100/100 2024-10-10 07:37:28.193369 2024-10-10 07:37:19.344823 A al_jitter false 0.000475 0.000131 0.000000 100/100 2024-10-10 07:37:27.801703 2024-10-10 07:37:19.676167
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:37:27.801703 2024-10-10 07:37:19.676167 2 34.48 al_loss false 2024-10-10 07:37:28.193369 2024-10-10 07:37:19.344823 4 57.58 al_rtt true 2024-10-10 07:37:31.055502 2024-10-10 07:37:26.991448 5 56.77
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.774603 0.009148 0.000000 100/100 2024-10-10 07:37:31.055502 2024-10-10 07:37:26.991448 A al_loss false 0.774603 0.009148 0.000000 100/100 2024-10-10 07:37:28.193369 2024-10-10 07:37:19.344823 A al_jitter false 0.774603 0.009148 0.000000 100/100 2024-10-10 07:37:27.801703 2024-10-10 07:37:19.676167
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:37:27.801703 2024-10-10 07:37:19.676167 2 27.89 al_loss false 2024-10-10 07:37:39.471360 2024-10-10 07:37:34.960449 6 62.05 al_rtt false 2024-10-10 07:37:38.971053 2024-10-10 07:37:31.055502 6 62.38
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.000467 0.000139 0.000000 100/100 2024-10-10 07:37:38.971053 2024-10-10 07:37:31.055502 A al_loss false 0.000467 0.000139 0.000000 100/100 2024-10-10 07:37:39.471360 2024-10-10 07:37:34.960449 A al_jitter false 0.000467 0.000139 0.000000 100/100 2024-10-10 07:37:27.801703 2024-10-10 07:37:19.676167
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-10 07:37:42.650843 2024-10-10 07:37:27.801703 3 31.17 al_loss false 2024-10-10 07:37:39.471360 2024-10-10 07:37:34.960449 6 52.03 al_rtt true 2024-10-10 07:37:44.988301 2024-10-10 07:37:38.971053 7 53.36
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.231205 0.323387 0.000000 100/100 2024-10-10 07:37:44.988301 2024-10-10 07:37:38.971053 A al_loss false 0.231205 0.323387 0.000000 100/100 2024-10-10 07:37:39.471360 2024-10-10 07:37:34.960449 A al_jitter true 0.231205 0.323387 0.000000 100/100 2024-10-10 07:37:42.650843 2024-10-10 07:37:27.801703
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:37:50.109276 2024-10-10 07:37:42.650843 4 38.71 al_loss false 2024-10-10 07:37:50.352764 2024-10-10 07:37:46.487725 8 54.50 al_rtt false 2024-10-10 07:37:48.744134 2024-10-10 07:37:44.988301 8 54.47
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000460 0.000115 0.000000 100/100 2024-10-10 07:37:48.744134 2024-10-10 07:37:44.988301 A al_loss false 0.000460 0.000115 0.000000 100/100 2024-10-10 07:37:50.352764 2024-10-10 07:37:46.487725 A al_jitter false 0.000460 0.000115 0.000000 100/100 2024-10-10 07:37:50.109276 2024-10-10 07:37:42.650843
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-10-10 07:38:03.305937 2024-10-10 07:37:58.043757 2 79.31 al_rtt false 2024-10-10 07:38:02.855249 2024-10-10 07:37:58.792724 2 61.25
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.028498 0.010100 1.000000 100/100 2024-10-10 07:38:02.855249 2024-10-10 07:37:58.792724 A al_loss false 0.028498 0.010100 1.000000 100/100 2024-10-10 07:38:03.305937 2024-10-10 07:37:58.043757 A al_jitter false 0.028498 0.010100 1.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-10 07:38:05.662006 1 26.92 al_loss true 2024-10-10 07:38:05.207675 2024-10-10 07:38:03.305937 3 73.72 al_rtt true 2024-10-10 07:38:06.714859 2024-10-10 07:38:02.855249 3 51.57
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.400287 0.399857 40.000000 100/100 2024-10-10 07:38:06.714859 2024-10-10 07:38:02.855249 A al_loss true 0.400287 0.399857 40.000000 100/100 2024-10-10 07:38:05.207675 2024-10-10 07:38:03.305937 A al_jitter true 0.400287 0.399857 40.000000 100/100 2024-10-10 07:38:05.662006
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:38:13.383011 2024-10-10 07:38:05.662006 2 43.49 al_loss false 2024-10-10 07:38:13.937193 2024-10-10 07:38:05.207675 4 78.78 al_rtt false 2024-10-10 07:38:13.433907 2024-10-10 07:38:06.714859 4 60.72
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.000449 0.000103 0.000000 100/100 2024-10-10 07:38:13.433907 2024-10-10 07:38:06.714859 A al_loss false 0.000449 0.000103 0.000000 100/100 2024-10-10 07:38:13.937193 2024-10-10 07:38:05.207675 A al_jitter false 0.000449 0.000103 0.000000 100/100 2024-10-10 07:38:13.383011 2024-10-10 07:38:05.662006
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:38:13.383011 2024-10-10 07:38:05.662006 2 33.05 al_loss false 2024-10-10 07:38:13.937193 2024-10-10 07:38:05.207675 4 59.87 al_rtt true 2024-10-10 07:38:16.990490 2024-10-10 07:38:13.433907 5 59.47
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.774504 0.009159 0.000000 100/100 2024-10-10 07:38:16.990490 2024-10-10 07:38:13.433907 A al_loss false 0.774504 0.009159 0.000000 100/100 2024-10-10 07:38:13.937193 2024-10-10 07:38:05.207675 A al_jitter false 0.774504 0.009159 0.000000 100/100 2024-10-10 07:38:13.383011 2024-10-10 07:38:05.662006
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:38:13.383011 2024-10-10 07:38:05.662006 2 26.73 al_loss false 2024-10-10 07:38:25.323610 2024-10-10 07:38:20.797279 6 64.11 al_rtt false 2024-10-10 07:38:24.811296 2024-10-10 07:38:16.990490 6 64.40
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.000445 0.000117 0.000000 100/100 2024-10-10 07:38:24.811296 2024-10-10 07:38:16.990490 A al_loss false 0.000445 0.000117 0.000000 100/100 2024-10-10 07:38:25.323610 2024-10-10 07:38:20.797279 A al_jitter false 0.000445 0.000117 0.000000 100/100 2024-10-10 07:38:13.383011 2024-10-10 07:38:05.662006
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-10 07:38:29.122432 2024-10-10 07:38:13.383011 3 28.66 al_loss false 2024-10-10 07:38:25.323610 2024-10-10 07:38:20.797279 6 53.56 al_rtt false 2024-10-10 07:38:24.811296 2024-10-10 07:38:16.990490 6 53.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 false 0.182518 0.250484 0.000000 100/100 2024-10-10 07:38:24.811296 2024-10-10 07:38:16.990490 A al_loss false 0.182518 0.250484 0.000000 100/100 2024-10-10 07:38:25.323610 2024-10-10 07:38:20.797279 A al_jitter true 0.182518 0.250484 0.000000 100/100 2024-10-10 07:38:29.122432 2024-10-10 07:38:13.383011
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0
:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-10 07:38:35.938743 2024-10-10 07:38:29.122432 4 36.27 al_loss false 2024-10-10 07:38:25.323610 2024-10-10 07:38:20.797279 6 46.19 al_rtt false 2024-10-10 07:38:24.811296 2024-10-10 07:38:16.990490 6 46.40
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.000363 0.000098 0.000000 100/100 2024-10-10 07:38:24.811296 2024-10-10 07:38:16.990490 A al_loss false 0.000363 0.000098 0.000000 100/100 2024-10-10 07:38:25.323610 2024-10-10 07:38:20.797279 A al_jitter false 0.000363 0.000098 0.000000 100/100 2024-10-10 07:38:35.938743 2024-10-10 07:38:29.122432
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.