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.000034    0.000005    0.000000  8/100
A          al_loss    false   0.000034    0.000005    0.000000  8/100
A          al_jitter  false   0.000034    0.000005    0.000000  8/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-05-22 08:34:21.860874                           1        55.04
al_loss    true    2024-05-22 08:34:21.574664                           1        59.62
al_rtt     true    2024-05-22 08:34:22.822716                           1        39.82

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.490240    0.549810    49.000000  100/100  2024-05-22 08:34:22.822716
A          al_loss    true    0.490240    0.549810    49.000000  100/100  2024-05-22 08:34:21.574664
A          al_jitter  true    0.490240    0.549810    49.000000  100/100  2024-05-22 08:34:21.860874

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-05-22 08:34:30.091275  2024-05-22 08:34:21.860874             2        68.24
al_loss    false   2024-05-22 08:34:30.581274  2024-05-22 08:34:21.574664             2        74.70
al_rtt     false   2024-05-22 08:34:29.887177  2024-05-22 08:34:22.822716             2        58.61

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.000395    0.000054    0.000000  100/100  2024-05-22 08:34:29.887177  2024-05-22 08:34:22.822716
A          al_loss    false   0.000395    0.000054    0.000000  100/100  2024-05-22 08:34:30.581274  2024-05-22 08:34:21.574664
A          al_jitter  false   0.000395    0.000054    0.000000  100/100  2024-05-22 08:34:30.091275  2024-05-22 08:34:21.860874

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-05-22 08:34:30.091275  2024-05-22 08:34:21.860874             2        45.69
al_loss    false   2024-05-22 08:34:30.581274  2024-05-22 08:34:21.574664             2        50.01
al_rtt     true    2024-05-22 08:34:33.883547  2024-05-22 08:34:29.887177             3        56.77

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.792428    0.009052    0.000000  100/100  2024-05-22 08:34:33.883547  2024-05-22 08:34:29.887177
A          al_loss    false   0.792428    0.009052    0.000000  100/100  2024-05-22 08:34:30.581274  2024-05-22 08:34:21.574664
A          al_jitter  false   0.792428    0.009052    0.000000  100/100  2024-05-22 08:34:30.091275  2024-05-22 08:34:21.860874

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-05-22 08:34:30.091275  2024-05-22 08:34:21.860874             2        34.59
al_loss    false   2024-05-22 08:34:42.513848  2024-05-22 08:34:38.000910             4        56.83
al_rtt     false   2024-05-22 08:34:41.999845  2024-05-22 08:34:33.883547             4        63.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.000391    0.000048    0.000000  100/100  2024-05-22 08:34:41.999845  2024-05-22 08:34:33.883547
A          al_loss    false   0.000391    0.000048    0.000000  100/100  2024-05-22 08:34:42.513848  2024-05-22 08:34:38.000910
A          al_jitter  false   0.000391    0.000048    0.000000  100/100  2024-05-22 08:34:30.091275  2024-05-22 08:34:21.860874

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-05-22 08:34:45.916665  2024-05-22 08:34:30.091275             3        37.28
al_loss    false   2024-05-22 08:34:42.513848  2024-05-22 08:34:38.000910             4        45.45
al_rtt     true    2024-05-22 08:34:48.242231  2024-05-22 08:34:41.999845             5        52.84

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.222190    0.340540    0.000000  100/100  2024-05-22 08:34:48.242231  2024-05-22 08:34:41.999845
A          al_loss    false   0.222190    0.340540    0.000000  100/100  2024-05-22 08:34:42.513848  2024-05-22 08:34:38.000910
A          al_jitter  true    0.222190    0.340540    0.000000  100/100  2024-05-22 08:34:45.916665  2024-05-22 08:34:30.091275

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-05-22 08:34:53.422862  2024-05-22 08:34:45.916665             4        44.31
al_loss    false   2024-05-22 08:34:53.937405  2024-05-22 08:34:49.983230             6        49.21
al_rtt     false   2024-05-22 08:34:51.920628  2024-05-22 08:34:48.242231             6        53.12

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.000397    0.000046    0.000000  100/100  2024-05-22 08:34:51.920628  2024-05-22 08:34:48.242231
A          al_loss    false   0.000397    0.000046    0.000000  100/100  2024-05-22 08:34:53.937405  2024-05-22 08:34:49.983230
A          al_jitter  false   0.000397    0.000046    0.000000  100/100  2024-05-22 08:34:53.422862  2024-05-22 08:34:45.916665

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.000087    0.000067    0.000000  9/100
A          al_loss    false   0.000087    0.000067    0.000000  9/100
A          al_jitter  false   0.000087    0.000067    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-05-22 08:35:07.102506                           1        49.97
al_loss    true    2024-05-22 08:35:06.544891                           1        58.73
al_rtt     true    2024-05-22 08:35:07.899228                           1        37.32

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.410250    0.399853    41.000000  100/100  2024-05-22 08:35:07.899228
A          al_loss    true    0.410250    0.399853    41.000000  100/100  2024-05-22 08:35:06.544891
A          al_jitter  true    0.410250    0.399853    41.000000  100/100  2024-05-22 08:35:07.102506

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-05-22 08:35:15.272179  2024-05-22 08:35:07.102506             2        67.22
al_loss    false   2024-05-22 08:35:15.714204  2024-05-22 08:35:06.544891             2        75.39
al_rtt     false   2024-05-22 08:35:14.861165  2024-05-22 08:35:07.899228             2        57.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.000401    0.000058    0.000000  100/100  2024-05-22 08:35:14.861165  2024-05-22 08:35:07.899228
A          al_loss    false   0.000401    0.000058    0.000000  100/100  2024-05-22 08:35:15.714204  2024-05-22 08:35:06.544891
A          al_jitter  false   0.000401    0.000058    0.000000  100/100  2024-05-22 08:35:15.272179  2024-05-22 08:35:07.102506

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-05-22 08:35:15.272179  2024-05-22 08:35:07.102506             2        45.27
al_loss    false   2024-05-22 08:35:15.714204  2024-05-22 08:35:06.544891             2        50.78
al_rtt     true    2024-05-22 08:35:18.868621  2024-05-22 08:35:14.861165             3        55.88

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.792436    0.009075    0.000000  100/100  2024-05-22 08:35:18.868621  2024-05-22 08:35:14.861165
A          al_loss    false   0.792436    0.009075    0.000000  100/100  2024-05-22 08:35:15.714204  2024-05-22 08:35:06.544891
A          al_jitter  false   0.792436    0.009075    0.000000  100/100  2024-05-22 08:35:15.272179  2024-05-22 08:35:07.102506

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-05-22 08:35:15.272179  2024-05-22 08:35:07.102506             2        34.24
al_loss    false   2024-05-22 08:35:27.434738  2024-05-22 08:35:22.923677             4        57.32
al_rtt     false   2024-05-22 08:35:26.941794  2024-05-22 08:35:18.868621             4        63.01

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.000446    0.000093    0.000000  100/100  2024-05-22 08:35:26.941794  2024-05-22 08:35:18.868621
A          al_loss    false   0.000446    0.000093    0.000000  100/100  2024-05-22 08:35:27.434738  2024-05-22 08:35:22.923677
A          al_jitter  false   0.000446    0.000093    0.000000  100/100  2024-05-22 08:35:15.272179  2024-05-22 08:35:07.102506

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-05-22 08:35:31.521192  2024-05-22 08:35:15.272179             3        35.13
al_loss    false   2024-05-22 08:35:27.434738  2024-05-22 08:35:22.923677             4        45.72
al_rtt     true    2024-05-22 08:35:33.472313  2024-05-22 08:35:26.941794             5        51.55

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.216967    0.274842    0.000000  100/100  2024-05-22 08:35:33.472313  2024-05-22 08:35:26.941794
A          al_loss    false   0.216967    0.274842    0.000000  100/100  2024-05-22 08:35:27.434738  2024-05-22 08:35:22.923677
A          al_jitter  true    0.216967    0.274842    0.000000  100/100  2024-05-22 08:35:31.521192  2024-05-22 08:35:15.272179

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-05-22 08:35:38.714584  2024-05-22 08:35:31.521192             4        43.03
al_loss    false   2024-05-22 08:35:39.108976  2024-05-22 08:35:35.398149             6        48.70
al_rtt     false   2024-05-22 08:35:36.953470  2024-05-22 08:35:33.472313             6        51.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.000436    0.000085    0.000000  100/100  2024-05-22 08:35:36.953470  2024-05-22 08:35:33.472313
A          al_loss    false   0.000436    0.000085    0.000000  100/100  2024-05-22 08:35:39.108976  2024-05-22 08:35:35.398149
A          al_jitter  false   0.000436    0.000085    0.000000  100/100  2024-05-22 08:35:38.714584  2024-05-22 08:35:31.521192

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-05-22 08:35:54.003682  2024-05-22 08:35:49.046025             2        69.98
al_rtt     false   2024-05-22 08:35:53.758686  2024-05-22 08:35:49.788356             2        56.08

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.000393    0.000053    0.000000  100/100  2024-05-22 08:35:53.758686  2024-05-22 08:35:49.788356
A          al_loss    false   0.000393    0.000053    0.000000  100/100  2024-05-22 08:35:54.003682  2024-05-22 08:35:49.046025
A          al_jitter  false   0.000393    0.000053    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-05-22 08:35:57.563725                                         1        24.79
al_loss    true    2024-05-22 08:35:56.958417  2024-05-22 08:35:54.003682             3        67.28
al_rtt     true    2024-05-22 08:35:58.660111  2024-05-22 08:35:53.758686             3        46.76

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.460227    0.419844    46.000000  100/100  2024-05-22 08:35:58.660111  2024-05-22 08:35:53.758686
A          al_loss    true    0.460227    0.419844    46.000000  100/100  2024-05-22 08:35:56.958417  2024-05-22 08:35:54.003682
A          al_jitter  true    0.460227    0.419844    46.000000  100/100  2024-05-22 08:35:57.563725

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-05-22 08:36:06.037677  2024-05-22 08:35:57.563725             2        44.95
al_loss    false   2024-05-22 08:36:06.132288  2024-05-22 08:35:56.958417             4        74.97
al_rtt     false   2024-05-22 08:36:04.870803  2024-05-22 08:35:58.660111             4        54.02

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.000406    0.000061    0.000000  100/100  2024-05-22 08:36:04.870803  2024-05-22 08:35:58.660111
A          al_loss    false   0.000406    0.000061    0.000000  100/100  2024-05-22 08:36:06.132288  2024-05-22 08:35:56.958417
A          al_jitter  false   0.000406    0.000061    0.000000  100/100  2024-05-22 08:36:06.037677  2024-05-22 08:35:57.563725

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-05-22 08:36:06.037677  2024-05-22 08:35:57.563725             2        34.23
al_loss    false   2024-05-22 08:36:06.132288  2024-05-22 08:35:56.958417             4        57.09
al_rtt     true    2024-05-22 08:36:09.343590  2024-05-22 08:36:04.870803             5        53.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.792438    0.009058    0.000000  100/100  2024-05-22 08:36:09.343590  2024-05-22 08:36:04.870803
A          al_loss    false   0.792438    0.009058    0.000000  100/100  2024-05-22 08:36:06.132288  2024-05-22 08:35:56.958417
A          al_jitter  false   0.792438    0.009058    0.000000  100/100  2024-05-22 08:36:06.037677  2024-05-22 08:35:57.563725

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-05-22 08:36:06.037677  2024-05-22 08:35:57.563725             2        27.77
al_loss    false   2024-05-22 08:36:17.904312  2024-05-22 08:36:13.383391             6        61.14
al_rtt     false   2024-05-22 08:36:17.400345  2024-05-22 08:36:09.343590             6        59.78

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.000398    0.000046    0.000000  100/100  2024-05-22 08:36:17.400345  2024-05-22 08:36:09.343590
A          al_loss    false   0.000398    0.000046    0.000000  100/100  2024-05-22 08:36:17.904312  2024-05-22 08:36:13.383391
A          al_jitter  false   0.000398    0.000046    0.000000  100/100  2024-05-22 08:36:06.037677  2024-05-22 08:35:57.563725

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-05-22 08:36:20.946198  2024-05-22 08:36:06.037677             3        32.12
al_loss    false   2024-05-22 08:36:17.904312  2024-05-22 08:36:13.383391             6        51.14
al_rtt     false   2024-05-22 08:36:17.400345  2024-05-22 08:36:09.343590             6        50.01

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.203717    0.285232    0.000000  100/100  2024-05-22 08:36:17.400345  2024-05-22 08:36:09.343590
A          al_loss    false   0.203717    0.285232    0.000000  100/100  2024-05-22 08:36:17.904312  2024-05-22 08:36:13.383391
A          al_jitter  true    0.203717    0.285232    0.000000  100/100  2024-05-22 08:36:20.946198  2024-05-22 08:36:06.037677

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-05-22 08:36:28.974736  2024-05-22 08:36:20.946198             4        39.09
al_loss    false   2024-05-22 08:36:29.126536  2024-05-22 08:36:25.458254             8        52.87
al_rtt     false   2024-05-22 08:36:27.261429  2024-05-22 08:36:24.306034             8        50.21

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.000047    0.000000  100/100  2024-05-22 08:36:27.261429  2024-05-22 08:36:24.306034
A          al_loss    false   0.000370    0.000047    0.000000  100/100  2024-05-22 08:36:29.126536  2024-05-22 08:36:25.458254
A          al_jitter  false   0.000370    0.000047    0.000000  100/100  2024-05-22 08:36:28.974736  2024-05-22 08:36:20.946198

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-05-22 08:36:45.408724  2024-05-22 08:36:40.506180             2        69.45
al_rtt     false   2024-05-22 08:36:45.173936  2024-05-22 08:36:41.264706             2        55.42

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.000393    0.000336    0.000000  100/100  2024-05-22 08:36:45.173936  2024-05-22 08:36:41.264706
A          al_loss    false   0.000393    0.000336    0.000000  100/100  2024-05-22 08:36:45.408724  2024-05-22 08:36:40.506180
A          al_jitter  false   0.000393    0.000336    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-05-22 08:36:48.762099                                         1        25.99
al_loss    true    2024-05-22 08:36:48.613184  2024-05-22 08:36:45.408724             3        64.85
al_rtt     true    2024-05-22 08:36:50.314150  2024-05-22 08:36:45.173936             3        44.13

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.450211    0.439853    45.000000  100/100  2024-05-22 08:36:50.314150  2024-05-22 08:36:45.173936
A          al_loss    true    0.450211    0.439853    45.000000  100/100  2024-05-22 08:36:48.613184  2024-05-22 08:36:45.408724
A          al_jitter  true    0.450211    0.439853    45.000000  100/100  2024-05-22 08:36:48.762099

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-05-22 08:36:57.280717  2024-05-22 08:36:48.762099             2        45.28
al_loss    false   2024-05-22 08:36:57.486158  2024-05-22 08:36:48.613184             4        73.19
al_rtt     false   2024-05-22 08:36:56.479647  2024-05-22 08:36:50.314150             4        53.54

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.000379    0.000041    0.000000  100/100  2024-05-22 08:36:56.479647  2024-05-22 08:36:50.314150
A          al_loss    false   0.000379    0.000041    0.000000  100/100  2024-05-22 08:36:57.486158  2024-05-22 08:36:48.613184
A          al_jitter  false   0.000379    0.000041    0.000000  100/100  2024-05-22 08:36:57.280717  2024-05-22 08:36:48.762099

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-05-22 08:36:57.280717  2024-05-22 08:36:48.762099             2        34.41
al_loss    false   2024-05-22 08:36:57.486158  2024-05-22 08:36:48.613184             4        55.62
al_rtt     true    2024-05-22 08:37:00.797972  2024-05-22 08:36:56.479647             5        53.25

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.783397    0.009056    0.000000  100/100  2024-05-22 08:37:00.797972  2024-05-22 08:36:56.479647
A          al_loss    false   0.783397    0.009056    0.000000  100/100  2024-05-22 08:36:57.486158  2024-05-22 08:36:48.613184
A          al_jitter  false   0.783397    0.009056    0.000000  100/100  2024-05-22 08:36:57.280717  2024-05-22 08:36:48.762099

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-05-22 08:36:57.280717  2024-05-22 08:36:48.762099             2        27.84
al_loss    false   2024-05-22 08:37:09.404204  2024-05-22 08:37:04.892936             6        59.74
al_rtt     false   2024-05-22 08:37:08.903566  2024-05-22 08:37:00.797972             6        59.40

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000378    0.000055    0.000000  100/100  2024-05-22 08:37:08.903566  2024-05-22 08:37:00.797972
A          al_loss    false   0.000378    0.000055    0.000000  100/100  2024-05-22 08:37:09.404204  2024-05-22 08:37:04.892936
A          al_jitter  false   0.000378    0.000055    0.000000  100/100  2024-05-22 08:36:57.280717  2024-05-22 08:36:48.762099

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-05-22 08:37:13.341741  2024-05-22 08:36:57.280717             3        29.70
al_loss    false   2024-05-22 08:37:09.404204  2024-05-22 08:37:04.892936             6        50.06
al_rtt     false   2024-05-22 08:37:08.903566  2024-05-22 08:37:00.797972             6        49.78

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.180335    0.245962    0.000000  100/100  2024-05-22 08:37:08.903566  2024-05-22 08:37:00.797972
A          al_loss    false   0.180335    0.245962    0.000000  100/100  2024-05-22 08:37:09.404204  2024-05-22 08:37:04.892936
A          al_jitter  true    0.180335    0.245962    0.000000  100/100  2024-05-22 08:37:13.341741  2024-05-22 08:36:57.280717

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-05-22 08:37:20.485935  2024-05-22 08:37:13.341741             4        37.00
al_loss    false   2024-05-22 08:37:21.076942  2024-05-22 08:37:17.177867             8        52.40
al_rtt     false   2024-05-22 08:37:18.872915  2024-05-22 08:37:16.014152             8        49.69

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.000373    0.000059    0.000000  100/100  2024-05-22 08:37:18.872915  2024-05-22 08:37:16.014152
A          al_loss    false   0.000373    0.000059    0.000000  100/100  2024-05-22 08:37:21.076942  2024-05-22 08:37:17.177867
A          al_jitter  false   0.000373    0.000059    0.000000  100/100  2024-05-22 08:37:20.485935  2024-05-22 08:37:13.341741

Note

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