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.

../../../_images/common3.svg

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.000039    0.000007    0.000000  9/100
A          al_loss    false   0.000039    0.000007    0.000000  9/100
A          al_jitter  false   0.000039    0.000007    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-06-20 17:56:34.650268                           1        47.67
al_loss    true    2024-06-20 17:56:34.203237                           1        54.60
al_rtt     true    2024-06-20 17:56:35.858459                           1        29.07

Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(true)
Show output
------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled            Prev-toggled
------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.430225    0.419849    43.000000  100/100  2024-06-20 17:56:35.858459
A          al_loss    true    0.430225    0.419849    43.000000  100/100  2024-06-20 17:56:34.203237
A          al_jitter  true    0.430225    0.419849    43.000000  100/100  2024-06-20 17:56:34.650268

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-06-20 17:56:42.831841  2024-06-20 17:56:34.650268             2        66.15
al_loss    false   2024-06-20 17:56:43.225815  2024-06-20 17:56:34.203237             2        72.98
al_rtt     false   2024-06-20 17:56:41.812308  2024-06-20 17:56:35.858459             2        48.17

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.000409    0.000069    0.000000  100/100  2024-06-20 17:56:41.812308  2024-06-20 17:56:35.858459
A          al_loss    false   0.000409    0.000069    0.000000  100/100  2024-06-20 17:56:43.225815  2024-06-20 17:56:34.203237
A          al_jitter  false   0.000409    0.000069    0.000000  100/100  2024-06-20 17:56:42.831841  2024-06-20 17:56:34.650268

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-06-20 17:56:42.831841  2024-06-20 17:56:34.650268             2        44.46
al_loss    false   2024-06-20 17:56:43.225815  2024-06-20 17:56:34.203237             2        49.04
al_rtt     true    2024-06-20 17:56:46.471275  2024-06-20 17:56:41.812308             3        49.69

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.810539    0.009204    0.000000  100/100  2024-06-20 17:56:46.471275  2024-06-20 17:56:41.812308
A          al_loss    false   0.810539    0.009204    0.000000  100/100  2024-06-20 17:56:43.225815  2024-06-20 17:56:34.203237
A          al_jitter  false   0.810539    0.009204    0.000000  100/100  2024-06-20 17:56:42.831841  2024-06-20 17:56:34.650268

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-06-20 17:56:42.831841  2024-06-20 17:56:34.650268             2        33.49
al_loss    false   2024-06-20 17:56:55.343856  2024-06-20 17:56:50.850790             4        55.33
al_rtt     false   2024-06-20 17:56:54.855702  2024-06-20 17:56:46.471275             4        58.71

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.000478    0.000196    0.000000  100/100  2024-06-20 17:56:54.855702  2024-06-20 17:56:46.471275
A          al_loss    false   0.000478    0.000196    0.000000  100/100  2024-06-20 17:56:55.343856  2024-06-20 17:56:50.850790
A          al_jitter  false   0.000478    0.000196    0.000000  100/100  2024-06-20 17:56:42.831841  2024-06-20 17:56:34.650268

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-06-20 17:56:58.594508  2024-06-20 17:56:42.831841             3        37.33
al_loss    false   2024-06-20 17:56:55.343856  2024-06-20 17:56:50.850790             4        44.23
al_rtt     true    2024-06-20 17:57:01.381603  2024-06-20 17:56:54.855702             5        48.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.231414    0.317653    0.000000  100/100  2024-06-20 17:57:01.381603  2024-06-20 17:56:54.855702
A          al_loss    false   0.231414    0.317653    0.000000  100/100  2024-06-20 17:56:55.343856  2024-06-20 17:56:50.850790
A          al_jitter  true    0.231414    0.317653    0.000000  100/100  2024-06-20 17:56:58.594508  2024-06-20 17:56:42.831841

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-06-20 17:57:06.871947  2024-06-20 17:56:58.594508             4        45.09
al_loss    false   2024-06-20 17:57:07.218634  2024-06-20 17:57:03.558801             6        47.06
al_rtt     false   2024-06-20 17:57:05.387080  2024-06-20 17:57:01.381603             6        50.27

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.000420    0.000063    0.000000  100/100  2024-06-20 17:57:05.387080  2024-06-20 17:57:01.381603
A          al_loss    false   0.000420    0.000063    0.000000  100/100  2024-06-20 17:57:07.218634  2024-06-20 17:57:03.558801
A          al_jitter  false   0.000420    0.000063    0.000000  100/100  2024-06-20 17:57:06.871947  2024-06-20 17:56:58.594508

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.000037    0.000006    0.000000  9/100
A          al_loss    false   0.000037    0.000006    0.000000  9/100
A          al_jitter  false   0.000037    0.000006    0.000000  9/100

Note

The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.

Note

If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.

Step 5: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out PLOSS
set traffic control PLOSS type network-emulator packet-loss 50

Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-06-20 17:57:20.553665                           1        49.42
al_loss    true    2024-06-20 17:57:19.891691                           1        59.59
al_rtt     true    2024-06-20 17:57:21.410079                           1        36.14

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.470219    0.539789    47.000000  100/100  2024-06-20 17:57:21.410079
A          al_loss    true    0.470219    0.539789    47.000000  100/100  2024-06-20 17:57:19.891691
A          al_jitter  true    0.470219    0.539789    47.000000  100/100  2024-06-20 17:57:20.553665

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-06-20 17:57:28.766106  2024-06-20 17:57:20.553665             2        66.59
al_loss    false   2024-06-20 17:57:28.814723  2024-06-20 17:57:19.891691             2        72.30
al_rtt     false   2024-06-20 17:57:27.809573  2024-06-20 17:57:21.410079             2        51.87

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.000419    0.000064    0.000000  100/100  2024-06-20 17:57:27.809573  2024-06-20 17:57:21.410079
A          al_loss    false   0.000419    0.000064    0.000000  100/100  2024-06-20 17:57:28.814723  2024-06-20 17:57:19.891691
A          al_jitter  false   0.000419    0.000064    0.000000  100/100  2024-06-20 17:57:28.766106  2024-06-20 17:57:20.553665

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-06-20 17:57:28.766106  2024-06-20 17:57:20.553665             2        44.88
al_loss    false   2024-06-20 17:57:28.814723  2024-06-20 17:57:19.891691             2        48.74
al_rtt     true    2024-06-20 17:57:32.417327  2024-06-20 17:57:27.809573             3        52.26

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.792443    0.009072    0.000000  100/100  2024-06-20 17:57:32.417327  2024-06-20 17:57:27.809573
A          al_loss    false   0.792443    0.009072    0.000000  100/100  2024-06-20 17:57:28.814723  2024-06-20 17:57:19.891691
A          al_jitter  false   0.792443    0.009072    0.000000  100/100  2024-06-20 17:57:28.766106  2024-06-20 17:57:20.553665

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-06-20 17:57:28.766106  2024-06-20 17:57:20.553665             2        34.07
al_loss    false   2024-06-20 17:57:41.042574  2024-06-20 17:57:36.535419             4        55.70
al_rtt     false   2024-06-20 17:57:40.544906  2024-06-20 17:57:32.417327             4        60.26

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.000406    0.000052    0.000000  100/100  2024-06-20 17:57:40.544906  2024-06-20 17:57:32.417327
A          al_loss    false   0.000406    0.000052    0.000000  100/100  2024-06-20 17:57:41.042574  2024-06-20 17:57:36.535419
A          al_jitter  false   0.000406    0.000052    0.000000  100/100  2024-06-20 17:57:28.766106  2024-06-20 17:57:20.553665

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-06-20 17:57:44.257030  2024-06-20 17:57:28.766106             3        37.69
al_loss    false   2024-06-20 17:57:41.042574  2024-06-20 17:57:36.535419             4        44.60
al_rtt     true    2024-06-20 17:57:46.512748  2024-06-20 17:57:40.544906             5        51.16

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.248018    0.346958    0.000000  100/100  2024-06-20 17:57:46.512748  2024-06-20 17:57:40.544906
A          al_loss    false   0.248018    0.346958    0.000000  100/100  2024-06-20 17:57:41.042574  2024-06-20 17:57:36.535419
A          al_jitter  true    0.248018    0.346958    0.000000  100/100  2024-06-20 17:57:44.257030  2024-06-20 17:57:28.766106

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-06-20 17:57:52.222194  2024-06-20 17:57:44.257030             4        44.98
al_loss    false   2024-06-20 17:57:41.042574  2024-06-20 17:57:36.535419             4        37.34
al_rtt     false   2024-06-20 17:57:49.958304  2024-06-20 17:57:46.512748             6        49.97

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.000398    0.000055    0.000000  100/100  2024-06-20 17:57:49.958304  2024-06-20 17:57:46.512748
A          al_loss    false   0.000398    0.000055    0.000000  100/100  2024-06-20 17:57:41.042574  2024-06-20 17:57:36.535419
A          al_jitter  false   0.000398    0.000055    0.000000  100/100  2024-06-20 17:57:52.222194  2024-06-20 17:57:44.257030

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-06-20 17:58:10.122150  2024-06-20 17:58:04.818295             2        75.10
al_rtt     false   2024-06-20 17:58:09.661335  2024-06-20 17:58:05.569185             2        57.97

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.000408    0.000093    0.000000  100/100  2024-06-20 17:58:09.661335  2024-06-20 17:58:05.569185
A          al_loss    false   0.000408    0.000093    0.000000  100/100  2024-06-20 17:58:10.122150  2024-06-20 17:58:04.818295
A          al_jitter  false   0.000408    0.000093    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-06-20 17:58:13.319760                                         1        24.63
al_loss    true    2024-06-20 17:58:12.917868  2024-06-20 17:58:10.122150             3        68.30
al_rtt     true    2024-06-20 17:58:14.381356  2024-06-20 17:58:09.661335             3        47.84

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.440222    0.379860    44.000000  100/100  2024-06-20 17:58:14.381356  2024-06-20 17:58:09.661335
A          al_loss    true    0.440222    0.379860    44.000000  100/100  2024-06-20 17:58:12.917868  2024-06-20 17:58:10.122150
A          al_jitter  true    0.440222    0.379860    44.000000  100/100  2024-06-20 17:58:13.319760

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-06-20 17:58:21.551211  2024-06-20 17:58:13.319760             2        43.52
al_loss    false   2024-06-20 17:58:21.647604  2024-06-20 17:58:12.917868             4        74.21
al_rtt     false   2024-06-20 17:58:20.942251  2024-06-20 17:58:14.381356             4        56.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.000398    0.000066    0.000000  100/100  2024-06-20 17:58:20.942251  2024-06-20 17:58:14.381356
A          al_loss    false   0.000398    0.000066    0.000000  100/100  2024-06-20 17:58:21.647604  2024-06-20 17:58:12.917868
A          al_jitter  false   0.000398    0.000066    0.000000  100/100  2024-06-20 17:58:21.551211  2024-06-20 17:58:13.319760

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-06-20 17:58:21.551211  2024-06-20 17:58:13.319760             2        32.93
al_loss    false   2024-06-20 17:58:21.647604  2024-06-20 17:58:12.917868             4        56.15
al_rtt     true    2024-06-20 17:58:25.301393  2024-06-20 17:58:20.942251             5        55.29

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.801457    0.009129    0.000000  100/100  2024-06-20 17:58:25.301393  2024-06-20 17:58:20.942251
A          al_loss    false   0.801457    0.009129    0.000000  100/100  2024-06-20 17:58:21.647604  2024-06-20 17:58:12.917868
A          al_jitter  false   0.801457    0.009129    0.000000  100/100  2024-06-20 17:58:21.551211  2024-06-20 17:58:13.319760

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-06-20 17:58:21.551211  2024-06-20 17:58:13.319760             2        26.64
al_loss    false   2024-06-20 17:58:33.968143  2024-06-20 17:58:29.454957             6        60.03
al_rtt     false   2024-06-20 17:58:33.461498  2024-06-20 17:58:25.301393             6        60.90

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.000400    0.000061    0.000000  100/100  2024-06-20 17:58:33.461498  2024-06-20 17:58:25.301393
A          al_loss    false   0.000400    0.000061    0.000000  100/100  2024-06-20 17:58:33.968143  2024-06-20 17:58:29.454957
A          al_jitter  false   0.000400    0.000061    0.000000  100/100  2024-06-20 17:58:21.551211  2024-06-20 17:58:13.319760

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-06-20 17:58:37.288654  2024-06-20 17:58:21.551211             3        30.72
al_loss    false   2024-06-20 17:58:33.968143  2024-06-20 17:58:29.454957             6        50.22
al_rtt     true    2024-06-20 17:58:40.039015  2024-06-20 17:58:33.461498             7        51.93

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.232467    0.288422    0.000000  100/100  2024-06-20 17:58:40.039015  2024-06-20 17:58:33.461498
A          al_loss    false   0.232467    0.288422    0.000000  100/100  2024-06-20 17:58:33.968143  2024-06-20 17:58:29.454957
A          al_jitter  true    0.232467    0.288422    0.000000  100/100  2024-06-20 17:58:37.288654  2024-06-20 17:58:21.551211

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-06-20 17:58:45.208804  2024-06-20 17:58:37.288654             4        37.65
al_loss    false   2024-06-20 17:58:45.720203  2024-06-20 17:58:42.197870             8        51.45
al_rtt     false   2024-06-20 17:58:43.249553  2024-06-20 17:58:40.039015             8        51.35

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.000398    0.000077    0.000000  100/100  2024-06-20 17:58:43.249553  2024-06-20 17:58:40.039015
A          al_loss    false   0.000398    0.000077    0.000000  100/100  2024-06-20 17:58:45.720203  2024-06-20 17:58:42.197870
A          al_jitter  false   0.000398    0.000077    0.000000  100/100  2024-06-20 17:58:45.208804  2024-06-20 17:58:37.288654

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-06-20 17:59:02.725582  2024-06-20 17:58:57.741271             2        70.27
al_rtt     false   2024-06-20 17:59:02.460201  2024-06-20 17:58:58.525314             2        55.51

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.000410    0.000060    0.000000  100/100  2024-06-20 17:59:02.460201  2024-06-20 17:58:58.525314
A          al_loss    false   0.000410    0.000060    0.000000  100/100  2024-06-20 17:59:02.725582  2024-06-20 17:58:57.741271
A          al_jitter  false   0.000410    0.000060    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-06-20 17:59:06.231688                                         1        25.27
al_loss    true    2024-06-20 17:59:05.974528  2024-06-20 17:59:02.725582             3        65.05
al_rtt     true    2024-06-20 17:59:07.626583  2024-06-20 17:59:02.460201             3        44.55

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.400237    0.459838    40.000000  100/100  2024-06-20 17:59:07.626583  2024-06-20 17:59:02.460201
A          al_loss    true    0.400237    0.459838    40.000000  100/100  2024-06-20 17:59:05.974528  2024-06-20 17:59:02.725582
A          al_jitter  true    0.400237    0.459838    40.000000  100/100  2024-06-20 17:59:06.231688

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-06-20 17:59:14.441206  2024-06-20 17:59:06.231688             2        43.22
al_loss    false   2024-06-20 17:59:14.882860  2024-06-20 17:59:05.974528             4        73.12
al_rtt     false   2024-06-20 17:59:14.189829  2024-06-20 17:59:07.626583             4        55.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.000410    0.000057    0.000000  100/100  2024-06-20 17:59:14.189829  2024-06-20 17:59:07.626583
A          al_loss    false   0.000410    0.000057    0.000000  100/100  2024-06-20 17:59:14.882860  2024-06-20 17:59:05.974528
A          al_jitter  false   0.000410    0.000057    0.000000  100/100  2024-06-20 17:59:14.441206  2024-06-20 17:59:06.231688

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-06-20 17:59:14.441206  2024-06-20 17:59:06.231688             2        32.79
al_loss    false   2024-06-20 17:59:14.882860  2024-06-20 17:59:05.974528             4        55.48
al_rtt     true    2024-06-20 17:59:18.302844  2024-06-20 17:59:14.189829             5        54.42

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.783453    0.009069    0.000000  100/100  2024-06-20 17:59:18.302844  2024-06-20 17:59:14.189829
A          al_loss    false   0.783453    0.009069    0.000000  100/100  2024-06-20 17:59:14.882860  2024-06-20 17:59:05.974528
A          al_jitter  false   0.783453    0.009069    0.000000  100/100  2024-06-20 17:59:14.441206  2024-06-20 17:59:06.231688

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-06-20 17:59:14.441206  2024-06-20 17:59:06.231688             2        26.63
al_loss    false   2024-06-20 17:59:26.872307  2024-06-20 17:59:22.345482             6        59.74
al_rtt     false   2024-06-20 17:59:26.355411  2024-06-20 17:59:18.302844             6        60.17

Step 16: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000386    0.000046    0.000000  100/100  2024-06-20 17:59:26.355411  2024-06-20 17:59:18.302844
A          al_loss    false   0.000386    0.000046    0.000000  100/100  2024-06-20 17:59:26.872307  2024-06-20 17:59:22.345482
A          al_jitter  false   0.000386    0.000046    0.000000  100/100  2024-06-20 17:59:14.441206  2024-06-20 17:59:06.231688

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-06-20 17:59:31.764650  2024-06-20 17:59:14.441206             3        26.19
al_loss    false   2024-06-20 17:59:26.872307  2024-06-20 17:59:22.345482             6        50.04
al_rtt     false   2024-06-20 17:59:26.355411  2024-06-20 17:59:18.302844             6        50.40

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.169436    0.206926    0.000000  100/100  2024-06-20 17:59:26.355411  2024-06-20 17:59:18.302844
A          al_loss    false   0.169436    0.206926    0.000000  100/100  2024-06-20 17:59:26.872307  2024-06-20 17:59:22.345482
A          al_jitter  true    0.169436    0.206926    0.000000  100/100  2024-06-20 17:59:31.764650  2024-06-20 17:59:14.441206

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-06-20 17:59:38.327240  2024-06-20 17:59:31.764650             4        34.58
al_loss    false   2024-06-20 17:59:38.628251  2024-06-20 17:59:34.675669             8        52.37
al_rtt     false   2024-06-20 17:59:36.487524  2024-06-20 17:59:34.078363             8        49.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.000406    0.000059    0.000000  100/100  2024-06-20 17:59:36.487524  2024-06-20 17:59:34.078363
A          al_loss    false   0.000406    0.000059    0.000000  100/100  2024-06-20 17:59:38.628251  2024-06-20 17:59:34.675669
A          al_jitter  false   0.000406    0.000059    0.000000  100/100  2024-06-20 17:59:38.327240  2024-06-20 17:59:31.764650

Note

The previous command output should show that the alarms are desactivated, since the network quality is good.