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.000035    0.000007    0.000000  9/100
A          al_loss    false   0.000035    0.000007    0.000000  9/100
A          al_jitter  false   0.000035    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-01-24 23:04:29.759704                           1        51.04
al_loss    true    2024-01-24 23:04:29.455289                           1        55.83
al_rtt     true    2024-01-24 23:04:30.865188                           1        33.94

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

(al_loss)\s+(true)
Show output
------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled            Prev-toggled
------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.390231    0.419862    39.000000  100/100  2024-01-24 23:04:30.865188
A          al_loss    true    0.390231    0.419862    39.000000  100/100  2024-01-24 23:04:29.455289
A          al_jitter  true    0.390231    0.419862    39.000000  100/100  2024-01-24 23:04:29.759704

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-01-24 23:04:38.294844  2024-01-24 23:04:29.759704             2        68.59
al_loss    false   2024-01-24 23:04:38.234684  2024-01-24 23:04:29.455289             2        70.61
al_rtt     false   2024-01-24 23:04:37.096939  2024-01-24 23:04:30.865188             2        50.10

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000327    0.000040    0.000000  100/100  2024-01-24 23:04:37.096939  2024-01-24 23:04:30.865188
A          al_loss    false   0.000327    0.000040    0.000000  100/100  2024-01-24 23:04:38.234684  2024-01-24 23:04:29.455289
A          al_jitter  false   0.000327    0.000040    0.000000  100/100  2024-01-24 23:04:38.294844  2024-01-24 23:04:29.759704

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-01-24 23:04:38.294844  2024-01-24 23:04:29.759704             2        45.77
al_loss    false   2024-01-24 23:04:38.234684  2024-01-24 23:04:29.455289             2        47.10
al_rtt     true    2024-01-24 23:04:42.092506  2024-01-24 23:04:37.096939             3        50.35

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.801528    0.009228    0.000000  100/100  2024-01-24 23:04:42.092506  2024-01-24 23:04:37.096939
A          al_loss    false   0.801528    0.009228    0.000000  100/100  2024-01-24 23:04:38.234684  2024-01-24 23:04:29.455289
A          al_jitter  false   0.801528    0.009228    0.000000  100/100  2024-01-24 23:04:38.294844  2024-01-24 23:04:29.759704

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-01-24 23:04:38.294844  2024-01-24 23:04:29.759704             2        34.47
al_loss    false   2024-01-24 23:04:50.959076  2024-01-24 23:04:46.465018             4        53.62
al_rtt     false   2024-01-24 23:04:50.468626  2024-01-24 23:04:42.092506             4        59.00

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.000415    0.000120    0.000000  100/100  2024-01-24 23:04:50.468626  2024-01-24 23:04:42.092506
A          al_loss    false   0.000415    0.000120    0.000000  100/100  2024-01-24 23:04:50.959076  2024-01-24 23:04:46.465018
A          al_jitter  false   0.000415    0.000120    0.000000  100/100  2024-01-24 23:04:38.294844  2024-01-24 23:04:29.759704

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-01-24 23:04:54.967267  2024-01-24 23:04:38.294844             3        35.98
al_loss    false   2024-01-24 23:04:50.959076  2024-01-24 23:04:46.465018             4        42.86
al_rtt     false   2024-01-24 23:04:50.468626  2024-01-24 23:04:42.092506             4        47.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     false   0.174124    0.314926    0.000000  100/100  2024-01-24 23:04:50.468626  2024-01-24 23:04:42.092506
A          al_loss    false   0.174124    0.314926    0.000000  100/100  2024-01-24 23:04:50.959076  2024-01-24 23:04:46.465018
A          al_jitter  true    0.174124    0.314926    0.000000  100/100  2024-01-24 23:04:54.967267  2024-01-24 23:04:38.294844

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-01-24 23:05:02.712436  2024-01-24 23:04:54.967267             4        43.91
al_loss    false   2024-01-24 23:05:03.061890  2024-01-24 23:04:59.129852             6        46.42
al_rtt     false   2024-01-24 23:05:00.292595  2024-01-24 23:04:59.034683             6        42.80

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.000415    0.000130    0.000000  100/100  2024-01-24 23:05:00.292595  2024-01-24 23:04:59.034683
A          al_loss    false   0.000415    0.000130    0.000000  100/100  2024-01-24 23:05:03.061890  2024-01-24 23:04:59.129852
A          al_jitter  false   0.000415    0.000130    0.000000  100/100  2024-01-24 23:05:02.712436  2024-01-24 23:04:54.967267

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.000047    0.000008    0.000000  11/100
A          al_loss    false   0.000047    0.000008    0.000000  11/100
A          al_jitter  false   0.000047    0.000008    0.000000  11/100

Note

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

Note

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

Step 5: Set the following configuration in DUT0:

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

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-01-24 23:05:18.430126                           1        49.56
al_loss    true    2024-01-24 23:05:17.828493                           1        58.58
al_rtt     true    2024-01-24 23:05:19.171908                           1        38.46

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.450247    0.499812    45.000000  100/100  2024-01-24 23:05:19.171908
A          al_loss    true    0.450247    0.499812    45.000000  100/100  2024-01-24 23:05:17.828493
A          al_jitter  true    0.450247    0.499812    45.000000  100/100  2024-01-24 23:05:18.430126

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-01-24 23:05:27.253765  2024-01-24 23:05:18.430126             2        68.95
al_loss    false   2024-01-24 23:05:27.178397  2024-01-24 23:05:17.828493             2        73.08
al_rtt     false   2024-01-24 23:05:26.100196  2024-01-24 23:05:19.171908             2        54.11

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.000345    0.000041    0.000000  100/100  2024-01-24 23:05:26.100196  2024-01-24 23:05:19.171908
A          al_loss    false   0.000345    0.000041    0.000000  100/100  2024-01-24 23:05:27.178397  2024-01-24 23:05:17.828493
A          al_jitter  false   0.000345    0.000041    0.000000  100/100  2024-01-24 23:05:27.253765  2024-01-24 23:05:18.430126

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-01-24 23:05:27.253765  2024-01-24 23:05:18.430126             2        46.17
al_loss    false   2024-01-24 23:05:27.178397  2024-01-24 23:05:17.828493             2        48.93
al_rtt     true    2024-01-24 23:05:30.945128  2024-01-24 23:05:26.100196             3        53.08

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.810546    0.009409    0.000000  100/100  2024-01-24 23:05:30.945128  2024-01-24 23:05:26.100196
A          al_loss    false   0.810546    0.009409    0.000000  100/100  2024-01-24 23:05:27.178397  2024-01-24 23:05:17.828493
A          al_jitter  false   0.810546    0.009409    0.000000  100/100  2024-01-24 23:05:27.253765  2024-01-24 23:05:18.430126

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-01-24 23:05:27.253765  2024-01-24 23:05:18.430126             2        35.07
al_loss    false   2024-01-24 23:05:39.812025  2024-01-24 23:05:35.304768             4        55.08
al_rtt     false   2024-01-24 23:05:39.306850  2024-01-24 23:05:30.945128             4        60.75

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.000454    0.000233    0.000000  100/100  2024-01-24 23:05:39.306850  2024-01-24 23:05:30.945128
A          al_loss    false   0.000454    0.000233    0.000000  100/100  2024-01-24 23:05:39.812025  2024-01-24 23:05:35.304768
A          al_jitter  false   0.000454    0.000233    0.000000  100/100  2024-01-24 23:05:27.253765  2024-01-24 23:05:18.430126

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-01-24 23:05:43.238248  2024-01-24 23:05:27.253765             3        37.98
al_loss    false   2024-01-24 23:05:39.812025  2024-01-24 23:05:35.304768             4        44.39
al_rtt     true    2024-01-24 23:05:45.394602  2024-01-24 23:05:39.306850             5        51.77

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.246104    0.369831    0.000000  100/100  2024-01-24 23:05:45.394602  2024-01-24 23:05:39.306850
A          al_loss    false   0.246104    0.369831    0.000000  100/100  2024-01-24 23:05:39.812025  2024-01-24 23:05:35.304768
A          al_jitter  true    0.246104    0.369831    0.000000  100/100  2024-01-24 23:05:43.238248  2024-01-24 23:05:27.253765

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-01-24 23:05:51.150136  2024-01-24 23:05:43.238248             4        44.99
al_loss    false   2024-01-24 23:05:39.812025  2024-01-24 23:05:35.304768             4        37.25
al_rtt     false   2024-01-24 23:05:49.287415  2024-01-24 23:05:45.394602             6        51.56

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000378    0.000050    0.000000  100/100  2024-01-24 23:05:49.287415  2024-01-24 23:05:45.394602
A          al_loss    false   0.000378    0.000050    0.000000  100/100  2024-01-24 23:05:39.812025  2024-01-24 23:05:35.304768
A          al_jitter  false   0.000378    0.000050    0.000000  100/100  2024-01-24 23:05:51.150136  2024-01-24 23:05:43.238248

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-01-24 23:06:10.024622  2024-01-24 23:06:05.055645             2        69.04
al_rtt     false   2024-01-24 23:06:09.768065  2024-01-24 23:06:05.810687             2        54.95

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.000383    0.000106    0.000000  100/100  2024-01-24 23:06:09.768065  2024-01-24 23:06:05.810687
A          al_loss    false   0.000383    0.000106    0.000000  100/100  2024-01-24 23:06:10.024622  2024-01-24 23:06:05.055645
A          al_jitter  false   0.000383    0.000106    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-01-24 23:06:13.374510                                         1        26.58
al_loss    true    2024-01-24 23:06:13.028821  2024-01-24 23:06:10.024622             3        66.72
al_rtt     true    2024-01-24 23:06:15.275393  2024-01-24 23:06:09.768065             3        42.11

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.340237    0.399871    34.000000  100/100  2024-01-24 23:06:15.275393  2024-01-24 23:06:09.768065
A          al_loss    true    0.340237    0.399871    34.000000  100/100  2024-01-24 23:06:13.028821  2024-01-24 23:06:10.024622
A          al_jitter  true    0.340237    0.399871    34.000000  100/100  2024-01-24 23:06:13.374510

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-01-24 23:06:22.031391  2024-01-24 23:06:13.374510             2        45.40
al_loss    false   2024-01-24 23:06:22.335886  2024-01-24 23:06:13.028821             4        74.91
al_rtt     false   2024-01-24 23:06:21.340822  2024-01-24 23:06:15.275393             4        52.58

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000374    0.000055    0.000000  100/100  2024-01-24 23:06:21.340822  2024-01-24 23:06:15.275393
A          al_loss    false   0.000374    0.000055    0.000000  100/100  2024-01-24 23:06:22.335886  2024-01-24 23:06:13.028821
A          al_jitter  false   0.000374    0.000055    0.000000  100/100  2024-01-24 23:06:22.031391  2024-01-24 23:06:13.374510

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-01-24 23:06:22.031391  2024-01-24 23:06:13.374510             2        34.45
al_loss    false   2024-01-24 23:06:22.335886  2024-01-24 23:06:13.028821             4        56.83
al_rtt     true    2024-01-24 23:06:25.539592  2024-01-24 23:06:21.340822             5        52.76

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.801425    0.009101    0.000000  100/100  2024-01-24 23:06:25.539592  2024-01-24 23:06:21.340822
A          al_loss    false   0.801425    0.009101    0.000000  100/100  2024-01-24 23:06:22.335886  2024-01-24 23:06:13.028821
A          al_jitter  false   0.801425    0.009101    0.000000  100/100  2024-01-24 23:06:22.031391  2024-01-24 23:06:13.374510

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-01-24 23:06:22.031391  2024-01-24 23:06:13.374510             2        27.97
al_loss    false   2024-01-24 23:06:34.208872  2024-01-24 23:06:29.703074             6        60.70
al_rtt     false   2024-01-24 23:06:33.718731  2024-01-24 23:06:25.539592             6        58.82

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.000359    0.000055    0.000000  100/100  2024-01-24 23:06:33.718731  2024-01-24 23:06:25.539592
A          al_loss    false   0.000359    0.000055    0.000000  100/100  2024-01-24 23:06:34.208872  2024-01-24 23:06:29.703074
A          al_jitter  false   0.000359    0.000055    0.000000  100/100  2024-01-24 23:06:22.031391  2024-01-24 23:06:13.374510

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-01-24 23:06:37.628858  2024-01-24 23:06:22.031391             3        31.26
al_loss    false   2024-01-24 23:06:34.208872  2024-01-24 23:06:29.703074             6        50.98
al_rtt     true    2024-01-24 23:06:40.082244  2024-01-24 23:06:33.718731             7        50.51

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.221670    0.359858    1.000000  100/100  2024-01-24 23:06:40.082244  2024-01-24 23:06:33.718731
A          al_loss    false   0.221670    0.359858    1.000000  100/100  2024-01-24 23:06:34.208872  2024-01-24 23:06:29.703074
A          al_jitter  true    0.221670    0.359858    1.000000  100/100  2024-01-24 23:06:37.628858  2024-01-24 23:06:22.031391

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-01-24 23:06:45.103028  2024-01-24 23:06:37.628858             4        37.58
al_loss    false   2024-01-24 23:06:34.208872  2024-01-24 23:06:29.703074             6        43.77
al_rtt     false   2024-01-24 23:06:42.849408  2024-01-24 23:06:40.082244             8        48.86

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.000366    0.000071    0.000000  100/100  2024-01-24 23:06:42.849408  2024-01-24 23:06:40.082244
A          al_loss    false   0.000366    0.000071    0.000000  100/100  2024-01-24 23:06:34.208872  2024-01-24 23:06:29.703074
A          al_jitter  false   0.000366    0.000071    0.000000  100/100  2024-01-24 23:06:45.103028  2024-01-24 23:06:37.628858

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-01-24 23:07:03.315602  2024-01-24 23:06:58.486126             2        65.37
al_rtt     false   2024-01-24 23:07:03.167518  2024-01-24 23:06:59.225614             2        53.29

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.000385    0.000129    0.000000  100/100  2024-01-24 23:07:03.167518  2024-01-24 23:06:59.225614
A          al_loss    false   0.000385    0.000129    0.000000  100/100  2024-01-24 23:07:03.315602  2024-01-24 23:06:58.486126
A          al_jitter  false   0.000385    0.000129    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-01-24 23:07:06.862970                                         1        26.31
al_loss    true    2024-01-24 23:07:06.712112  2024-01-24 23:07:03.315602             3        63.65
al_rtt     true    2024-01-24 23:07:08.274002  2024-01-24 23:07:03.167518             3        45.26

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled                   Prev-toggled
--------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.380221    0.379884    38.000000  100/100  2024-01-24 23:07:08.274002  2024-01-24 23:07:03.167518
A          al_loss    true    0.380221    0.379884    38.000000  100/100  2024-01-24 23:07:06.712112  2024-01-24 23:07:03.315602
A          al_jitter  true    0.380221    0.379884    38.000000  100/100  2024-01-24 23:07:06.862970

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-01-24 23:07:15.389698  2024-01-24 23:07:06.862970             2        44.46
al_loss    false   2024-01-24 23:07:15.673839  2024-01-24 23:07:06.712112             4        71.93
al_rtt     false   2024-01-24 23:07:14.193126  2024-01-24 23:07:08.274002             4        51.41

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.000366    0.000060    0.000000  100/100  2024-01-24 23:07:14.193126  2024-01-24 23:07:08.274002
A          al_loss    false   0.000366    0.000060    0.000000  100/100  2024-01-24 23:07:15.673839  2024-01-24 23:07:06.712112
A          al_jitter  false   0.000366    0.000060    0.000000  100/100  2024-01-24 23:07:15.389698  2024-01-24 23:07:06.862970

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-01-24 23:07:15.389698  2024-01-24 23:07:06.862970             2        33.87
al_loss    false   2024-01-24 23:07:15.673839  2024-01-24 23:07:06.712112             4        54.78
al_rtt     true    2024-01-24 23:07:19.035416  2024-01-24 23:07:14.193126             5        51.75

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.801400    0.009077    0.000000  100/100  2024-01-24 23:07:19.035416  2024-01-24 23:07:14.193126
A          al_loss    false   0.801400    0.009077    0.000000  100/100  2024-01-24 23:07:15.673839  2024-01-24 23:07:06.712112
A          al_jitter  false   0.801400    0.009077    0.000000  100/100  2024-01-24 23:07:15.389698  2024-01-24 23:07:06.862970

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-01-24 23:07:15.389698  2024-01-24 23:07:06.862970             2        27.47
al_loss    false   2024-01-24 23:07:27.713786  2024-01-24 23:07:23.186326             6        59.03
al_rtt     false   2024-01-24 23:07:27.205385  2024-01-24 23:07:19.035416             6        58.08

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000371    0.000076    0.000000  100/100  2024-01-24 23:07:27.205385  2024-01-24 23:07:19.035416
A          al_loss    false   0.000371    0.000076    0.000000  100/100  2024-01-24 23:07:27.713786  2024-01-24 23:07:23.186326
A          al_jitter  false   0.000371    0.000076    0.000000  100/100  2024-01-24 23:07:15.389698  2024-01-24 23:07:06.862970

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-01-24 23:07:31.167177  2024-01-24 23:07:15.389698             3        30.78
al_loss    false   2024-01-24 23:07:27.713786  2024-01-24 23:07:23.186326             6        49.51
al_rtt     true    2024-01-24 23:07:33.624644  2024-01-24 23:07:27.205385             7        49.82

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.224251    0.338946    0.000000  100/100  2024-01-24 23:07:33.624644  2024-01-24 23:07:27.205385
A          al_loss    false   0.224251    0.338946    0.000000  100/100  2024-01-24 23:07:27.713786  2024-01-24 23:07:23.186326
A          al_jitter  true    0.224251    0.338946    0.000000  100/100  2024-01-24 23:07:31.167177  2024-01-24 23:07:15.389698

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-01-24 23:07:39.109137  2024-01-24 23:07:31.167177             4        38.35
al_loss    false   2024-01-24 23:07:39.039785  2024-01-24 23:07:35.729937             8        50.37
al_rtt     false   2024-01-24 23:07:37.520408  2024-01-24 23:07:33.624644             8        51.05

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.000370    0.000055    0.000000  100/100  2024-01-24 23:07:37.520408  2024-01-24 23:07:33.624644
A          al_loss    false   0.000370    0.000055    0.000000  100/100  2024-01-24 23:07:39.039785  2024-01-24 23:07:35.729937
A          al_jitter  false   0.000370    0.000055    0.000000  100/100  2024-01-24 23:07:39.109137  2024-01-24 23:07:31.167177

Note

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