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
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set service nsm operation A alarm al_jitter activate jitter 0.1
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 destination-address 10.215.200.100
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A type icmp
set service nsm operation A window 100
set system alarm al_jitter
set system alarm al_loss
set system alarm al_rtt
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

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_jitter  false   0.000029    0.000016    0.000000  6/100
A          al_loss    false   0.000029    0.000016    0.000000  6/100
A          al_rtt     false   0.000029    0.000016    0.000000  6/100

Note

The previous command output should show that NSM operations have been successfully created and that 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, NSM operation will detect this packet loss in the network and trigger the ‘al_loss’ alarm.

Step 5: Modify the following configuration lines 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-07-30 11:55:01.509394                           1        50.27
al_loss    true    2024-07-30 11:55:00.758319                           1        62.78
al_rtt     true    2024-07-30 11:55:01.853139                           1        44.60

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_jitter  true    0.440317    0.439788    44.000000  100/100  2024-07-30 11:55:01.509394
A          al_loss    true    0.440317    0.439788    44.000000  100/100  2024-07-30 11:55:00.758319
A          al_rtt     true    0.440317    0.439788    44.000000  100/100  2024-07-30 11:55:01.853139

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since packet losses on the network are greater than the configured threshold. In this scenario, the delay and jitter values are also affected, meaning the ‘al_rtt’ and ‘al_jitter’ alarms also go off (since their configured threshold is also exceeded).

Note

If the packet loss emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect packets are no longer being lost and will deactivate the ‘al_loss’ alarm.

Step 8: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:55:09.123607  2024-07-30 11:55:01.509394             2        65.65
al_loss    false   2024-07-30 11:55:09.676769  2024-07-30 11:55:00.758319             2        76.92
al_rtt     false   2024-07-30 11:55:08.725893  2024-07-30 11:55:01.853139             2        59.29

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_jitter  false   0.000490    0.000132    0.000000  100/100  2024-07-30 11:55:09.123607  2024-07-30 11:55:01.509394
A          al_loss    false   0.000490    0.000132    0.000000  100/100  2024-07-30 11:55:09.676769  2024-07-30 11:55:00.758319
A          al_rtt     false   0.000490    0.000132    0.000000  100/100  2024-07-30 11:55:08.725893  2024-07-30 11:55:01.853139

Note

The previous command output should show that alarms are deactivated (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, NSM operation will detect a delay in the network and will trigger the ‘al_rtt’ alarm.

Step 11: Modify the following configuration lines 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-07-30 11:55:09.123607  2024-07-30 11:55:01.509394             2        44.14
al_loss    false   2024-07-30 11:55:09.676769  2024-07-30 11:55:00.758319             2        51.71
al_rtt     true    2024-07-30 11:55:12.682125  2024-07-30 11:55:08.725893             3        57.74

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_jitter  false   0.765753    0.009164    0.000000  100/100  2024-07-30 11:55:09.123607  2024-07-30 11:55:01.509394
A          al_loss    false   0.765753    0.009164    0.000000  100/100  2024-07-30 11:55:09.676769  2024-07-30 11:55:00.758319
A          al_rtt     true    0.765753    0.009164    0.000000  100/100  2024-07-30 11:55:12.682125  2024-07-30 11:55:08.725893

Note

The previous command output should show that the ‘al_rtt’ alarm is activated, since delays on the network are greater than the configured threshold.

Note

If the additional delay emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect significant delays no longer exist and will deactivate the ‘al_rtt’ alarm.

Step 14: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:55:09.123607  2024-07-30 11:55:01.509394             2        33.32
al_loss    false   2024-07-30 11:55:21.057632  2024-07-30 11:55:16.544635             4        58.78
al_rtt     false   2024-07-30 11:55:20.559594  2024-07-30 11:55:12.682125             4        64.56

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_jitter  false   0.000539    0.000154    0.000000  100/100  2024-07-30 11:55:09.123607  2024-07-30 11:55:01.509394
A          al_loss    false   0.000539    0.000154    0.000000  100/100  2024-07-30 11:55:21.057632  2024-07-30 11:55:16.544635
A          al_rtt     false   0.000539    0.000154    0.000000  100/100  2024-07-30 11:55:20.559594  2024-07-30 11:55:12.682125

Note

The previous command output should show the alarms are deactivated (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, NSM operation will detect said jitter in the network and will trigger the ‘al_jitter’ alarm.

Step 17: Modify the following configuration lines 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-07-30 11:55:24.252659  2024-07-30 11:55:09.123607             3        36.55
al_loss    false   2024-07-30 11:55:21.057632  2024-07-30 11:55:16.544635             4        47.03
al_rtt     true    2024-07-30 11:55:27.036450  2024-07-30 11:55:20.559594             5        51.79

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_jitter  true    0.210906    0.251130    0.000000  100/100  2024-07-30 11:55:24.252659  2024-07-30 11:55:09.123607
A          al_loss    false   0.210906    0.251130    0.000000  100/100  2024-07-30 11:55:21.057632  2024-07-30 11:55:16.544635
A          al_rtt     true    0.210906    0.251130    0.000000  100/100  2024-07-30 11:55:27.036450  2024-07-30 11:55:20.559594

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, NSM operation will no longer detect a jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:55:31.483500  2024-07-30 11:55:24.252659             4        43.45
al_loss    false   2024-07-30 11:55:21.057632  2024-07-30 11:55:16.544635             4        39.31
al_rtt     false   2024-07-30 11:55:30.043484  2024-07-30 11:55:27.036450             6        51.98

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_jitter  false   0.000498    0.000113    0.000000  100/100  2024-07-30 11:55:31.483500  2024-07-30 11:55:24.252659
A          al_loss    false   0.000498    0.000113    0.000000  100/100  2024-07-30 11:55:21.057632  2024-07-30 11:55:16.544635
A          al_rtt     false   0.000498    0.000113    0.000000  100/100  2024-07-30 11:55:30.043484  2024-07-30 11:55:27.036450

Note

The previous command output should show the alarms are deactivated (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
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set service dns static host-name testnsm alias test.nsm.fqdn
set service dns static host-name testnsm inet 10.215.200.100
set service nsm operation A alarm al_jitter activate jitter 0.1
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 destination-address test.nsm.fqdn
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A type icmp
set service nsm operation A window 100
set system alarm al_jitter
set system alarm al_loss
set system alarm al_rtt
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

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_jitter  false   0.000018    0.000006    0.000000  6/100
A          al_loss    false   0.000018    0.000006    0.000000  6/100
A          al_rtt     false   0.000018    0.000006    0.000000  6/100

Note

The previous command output should show that NSM operations have been successfully created and that 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, NSM operation will detect this packet loss in the network and trigger the ‘al_loss’ alarm.

Step 5: Modify the following configuration lines 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-07-30 11:55:41.800129                           1        50.80
al_loss    true    2024-07-30 11:55:41.402215                           1        57.32
al_rtt     true    2024-07-30 11:55:42.904078                           1        32.55

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

(al_loss)\s+(true)
Show output
------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled            Prev-toggled
------------------------------------------------------------------------------------------------------------------
A          al_jitter  true    0.410264    0.419842    41.000000  100/100  2024-07-30 11:55:41.800129
A          al_loss    true    0.410264    0.419842    41.000000  100/100  2024-07-30 11:55:41.402215
A          al_rtt     true    0.410264    0.419842    41.000000  100/100  2024-07-30 11:55:42.904078

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since packet losses on the network are greater than the configured threshold. In this scenario, the delay and jitter values are also affected, meaning the ‘al_rtt’ and ‘al_jitter’ alarms also go off (since their configured threshold is also exceeded).

Note

If the packet loss emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect packets are no longer being lost and will deactivate the ‘al_loss’ alarm.

Step 8: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:55:49.474086  2024-07-30 11:55:41.800129             2        65.70
al_loss    false   2024-07-30 11:55:49.628203  2024-07-30 11:55:41.402215             2        70.39
al_rtt     false   2024-07-30 11:55:48.575751  2024-07-30 11:55:42.904078             2        48.55

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_jitter  false   0.000556    0.000145    0.000000  100/100  2024-07-30 11:55:49.474086  2024-07-30 11:55:41.800129
A          al_loss    false   0.000556    0.000145    0.000000  100/100  2024-07-30 11:55:49.628203  2024-07-30 11:55:41.402215
A          al_rtt     false   0.000556    0.000145    0.000000  100/100  2024-07-30 11:55:48.575751  2024-07-30 11:55:42.904078

Note

The previous command output should show that alarms are deactivated (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, NSM operation will detect a delay in the network and will trigger the ‘al_rtt’ alarm.

Step 11: Modify the following configuration lines 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-07-30 11:55:49.474086  2024-07-30 11:55:41.800129             2        44.04
al_loss    false   2024-07-30 11:55:49.628203  2024-07-30 11:55:41.402215             2        47.19
al_rtt     true    2024-07-30 11:55:53.137388  2024-07-30 11:55:48.575751             3        50.39

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_jitter  false   0.774499    0.009139    0.000000  100/100  2024-07-30 11:55:49.474086  2024-07-30 11:55:41.800129
A          al_loss    false   0.774499    0.009139    0.000000  100/100  2024-07-30 11:55:49.628203  2024-07-30 11:55:41.402215
A          al_rtt     true    0.774499    0.009139    0.000000  100/100  2024-07-30 11:55:53.137388  2024-07-30 11:55:48.575751

Note

The previous command output should show that the ‘al_rtt’ alarm is activated, since delays on the network are greater than the configured threshold.

Note

If the additional delay emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect significant delays no longer exist and will deactivate the ‘al_rtt’ alarm.

Step 14: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:55:49.474086  2024-07-30 11:55:41.800129             2        33.20
al_loss    false   2024-07-30 11:56:01.603218  2024-07-30 11:55:57.091489             4        55.10
al_rtt     false   2024-07-30 11:56:01.102455  2024-07-30 11:55:53.137388             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_jitter  false   0.000482    0.000131    0.000000  100/100  2024-07-30 11:55:49.474086  2024-07-30 11:55:41.800129
A          al_loss    false   0.000482    0.000131    0.000000  100/100  2024-07-30 11:56:01.603218  2024-07-30 11:55:57.091489
A          al_rtt     false   0.000482    0.000131    0.000000  100/100  2024-07-30 11:56:01.102455  2024-07-30 11:55:53.137388

Note

The previous command output should show the alarms are deactivated (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, NSM operation will detect said jitter in the network and will trigger the ‘al_jitter’ alarm.

Step 17: Modify the following configuration lines 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-07-30 11:56:04.949900  2024-07-30 11:55:49.474086             3        35.95
al_loss    false   2024-07-30 11:56:01.603218  2024-07-30 11:55:57.091489             4        44.20
al_rtt     false   2024-07-30 11:56:01.102455  2024-07-30 11:55:53.137388             4        47.33

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_jitter  true    0.193465    0.297626    0.000000  100/100  2024-07-30 11:56:04.949900  2024-07-30 11:55:49.474086
A          al_loss    false   0.193465    0.297626    0.000000  100/100  2024-07-30 11:56:01.603218  2024-07-30 11:55:57.091489
A          al_rtt     false   0.193465    0.297626    0.000000  100/100  2024-07-30 11:56:01.102455  2024-07-30 11:55:53.137388

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, NSM operation will no longer detect a jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:56:12.428352  2024-07-30 11:56:04.949900             4        44.03
al_loss    false   2024-07-30 11:56:01.603218  2024-07-30 11:55:57.091489             4        37.01
al_rtt     false   2024-07-30 11:56:10.524472  2024-07-30 11:56:07.828982             6        47.46

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_jitter  false   0.000516    0.000151    0.000000  100/100  2024-07-30 11:56:12.428352  2024-07-30 11:56:04.949900
A          al_loss    false   0.000516    0.000151    0.000000  100/100  2024-07-30 11:56:01.603218  2024-07-30 11:55:57.091489
A          al_rtt     false   0.000516    0.000151    0.000000  100/100  2024-07-30 11:56:10.524472  2024-07-30 11:56:07.828982

Note

The previous command output should show the alarms are deactivated (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'
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address '10::2/64'
set service nsm operation A alarm al_jitter activate jitter 0.1
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 destination-address '10::3'
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A type icmp
set service nsm operation A window 100
set system alarm al_jitter
set system alarm al_loss
set system alarm al_rtt
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

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-07-30 11:56:25.951683  2024-07-30 11:56:20.931462             2        75.11
al_rtt     false   2024-07-30 11:56:25.647912  2024-07-30 11:56:21.685543             2        59.35

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_jitter  false   0.017153    0.004468    0.000000  100/100
A          al_loss    false   0.017153    0.004468    0.000000  100/100  2024-07-30 11:56:25.951683  2024-07-30 11:56:20.931462
A          al_rtt     false   0.017153    0.004468    0.000000  100/100  2024-07-30 11:56:25.647912  2024-07-30 11:56:21.685543

Note

The previous command output should show that NSM operations have been successfully created and that 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, NSM operation will detect this packet loss in the network and trigger the ‘al_loss’ alarm.

Step 5: Modify the following configuration lines 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-07-30 11:56:28.771980                                         1        26.05
al_loss    true    2024-07-30 11:56:28.157369  2024-07-30 11:56:25.951683             3        71.48
al_rtt     true    2024-07-30 11:56:29.511211  2024-07-30 11:56:25.647912             3        52.07

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled                   Prev-toggled
--------------------------------------------------------------------------------------------------------------------------------
A          al_jitter  true    0.480304    0.449738    48.000000  100/100  2024-07-30 11:56:28.771980
A          al_loss    true    0.480304    0.449738    48.000000  100/100  2024-07-30 11:56:28.157369  2024-07-30 11:56:25.951683
A          al_rtt     true    0.480304    0.449738    48.000000  100/100  2024-07-30 11:56:29.511211  2024-07-30 11:56:25.647912

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since packet losses on the network are greater than the configured threshold. In this scenario, the delay and jitter values are also affected, meaning the ‘al_rtt’ and ‘al_jitter’ alarms also go off (since their configured threshold is also exceeded).

Note

If the packet loss emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect packets are no longer being lost and will deactivate the ‘al_loss’ alarm.

Step 8: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:56:36.883491  2024-07-30 11:56:28.771980             2        44.81
al_loss    false   2024-07-30 11:56:37.282751  2024-07-30 11:56:28.157369             4        78.18
al_rtt     false   2024-07-30 11:56:36.282727  2024-07-30 11:56:29.511211             4        59.35

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_jitter  false   0.000567    0.000155    0.000000  100/100  2024-07-30 11:56:36.883491  2024-07-30 11:56:28.771980
A          al_loss    false   0.000567    0.000155    0.000000  100/100  2024-07-30 11:56:37.282751  2024-07-30 11:56:28.157369
A          al_rtt     false   0.000567    0.000155    0.000000  100/100  2024-07-30 11:56:36.282727  2024-07-30 11:56:29.511211

Note

The previous command output should show that alarms are deactivated (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, NSM operation will detect a delay in the network and will trigger the ‘al_rtt’ alarm.

Step 11: Modify the following configuration lines 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-07-30 11:56:36.883491  2024-07-30 11:56:28.771980             2        34.09
al_loss    false   2024-07-30 11:56:37.282751  2024-07-30 11:56:28.157369             4        59.46
al_rtt     true    2024-07-30 11:56:40.284445  2024-07-30 11:56:36.282727             5        58.18

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_jitter  false   0.774527    0.009138    0.000000  100/100  2024-07-30 11:56:36.883491  2024-07-30 11:56:28.771980
A          al_loss    false   0.774527    0.009138    0.000000  100/100  2024-07-30 11:56:37.282751  2024-07-30 11:56:28.157369
A          al_rtt     true    0.774527    0.009138    0.000000  100/100  2024-07-30 11:56:40.284445  2024-07-30 11:56:36.282727

Note

The previous command output should show that the ‘al_rtt’ alarm is activated, since delays on the network are greater than the configured threshold.

Note

If the additional delay emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect significant delays no longer exist and will deactivate the ‘al_rtt’ alarm.

Step 14: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:56:36.883491  2024-07-30 11:56:28.771980             2        27.60
al_loss    false   2024-07-30 11:56:48.706358  2024-07-30 11:56:44.204195             6        63.46
al_rtt     false   2024-07-30 11:56:48.202761  2024-07-30 11:56:40.284445             6        63.49

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_jitter  false   0.000408    0.000125    0.000000  100/100  2024-07-30 11:56:36.883491  2024-07-30 11:56:28.771980
A          al_loss    false   0.000408    0.000125    0.000000  100/100  2024-07-30 11:56:48.706358  2024-07-30 11:56:44.204195
A          al_rtt     false   0.000408    0.000125    0.000000  100/100  2024-07-30 11:56:48.202761  2024-07-30 11:56:40.284445

Note

The previous command output should show the alarms are deactivated (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, NSM operation will detect said jitter in the network and will trigger the ‘al_jitter’ alarm.

Step 17: Modify the following configuration lines 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-07-30 11:56:52.575532  2024-07-30 11:56:36.883491             3        29.29
al_loss    false   2024-07-30 11:56:48.706358  2024-07-30 11:56:44.204195             6        53.02
al_rtt     false   2024-07-30 11:56:48.202761  2024-07-30 11:56:40.284445             6        53.04

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_jitter  true    0.153579    0.204290    0.000000  100/100  2024-07-30 11:56:52.575532  2024-07-30 11:56:36.883491
A          al_loss    false   0.153579    0.204290    0.000000  100/100  2024-07-30 11:56:48.706358  2024-07-30 11:56:44.204195
A          al_rtt     false   0.153579    0.204290    0.000000  100/100  2024-07-30 11:56:48.202761  2024-07-30 11:56:40.284445

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, NSM operation will no longer detect a jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:56:59.584313  2024-07-30 11:56:52.575532             4        37.08
al_loss    false   2024-07-30 11:56:59.934906  2024-07-30 11:56:56.222169             8        54.84
al_rtt     false   2024-07-30 11:56:58.132816  2024-07-30 11:56:56.122376             8        50.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_jitter  false   0.000472    0.000135    0.000000  100/100  2024-07-30 11:56:59.584313  2024-07-30 11:56:52.575532
A          al_loss    false   0.000472    0.000135    0.000000  100/100  2024-07-30 11:56:59.934906  2024-07-30 11:56:56.222169
A          al_rtt     false   0.000472    0.000135    0.000000  100/100  2024-07-30 11:56:58.132816  2024-07-30 11:56:56.122376

Note

The previous command output should show the alarms are deactivated (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'
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address '10::2/64'
set service dns static host-name testnsm alias test.nsm.fqdn
set service dns static host-name testnsm inet '10::3'
set service nsm operation A alarm al_jitter activate jitter 0.1
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 destination-address test.nsm.fqdn
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A type icmp
set service nsm operation A window 100
set system alarm al_jitter
set system alarm al_loss
set system alarm al_rtt
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

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-07-30 11:57:13.298678  2024-07-30 11:57:08.137769             2        77.21
al_rtt     false   2024-07-30 11:57:12.905275  2024-07-30 11:57:08.886134             2        60.21

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_jitter  false   0.020364    0.004812    0.000000  100/100
A          al_loss    false   0.020364    0.004812    0.000000  100/100  2024-07-30 11:57:13.298678  2024-07-30 11:57:08.137769
A          al_rtt     false   0.020364    0.004812    0.000000  100/100  2024-07-30 11:57:12.905275  2024-07-30 11:57:08.886134

Note

The previous command output should show that NSM operations have been successfully created and that 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, NSM operation will detect this packet loss in the network and trigger the ‘al_loss’ alarm.

Step 5: Modify the following configuration lines 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-07-30 11:57:15.904504                                         1        26.30
al_loss    true    2024-07-30 11:57:15.608146  2024-07-30 11:57:13.298678             3        70.38
al_rtt     true    2024-07-30 11:57:17.569381  2024-07-30 11:57:12.905275             3        45.33

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_jitter  true    0.420325    0.389801    42.000000  100/100  2024-07-30 11:57:15.904504
A          al_loss    true    0.420325    0.389801    42.000000  100/100  2024-07-30 11:57:15.608146  2024-07-30 11:57:13.298678
A          al_rtt     true    0.420325    0.389801    42.000000  100/100  2024-07-30 11:57:17.569381  2024-07-30 11:57:12.905275

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since packet losses on the network are greater than the configured threshold. In this scenario, the delay and jitter values are also affected, meaning the ‘al_rtt’ and ‘al_jitter’ alarms also go off (since their configured threshold is also exceeded).

Note

If the packet loss emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect packets are no longer being lost and will deactivate the ‘al_loss’ alarm.

Step 8: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:57:23.737337  2024-07-30 11:57:15.904504             2        43.65
al_loss    false   2024-07-30 11:57:24.180440  2024-07-30 11:57:15.608146             4        76.46
al_rtt     false   2024-07-30 11:57:23.587402  2024-07-30 11:57:17.569381             4        55.91

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_jitter  false   0.000487    0.000153    0.000000  100/100  2024-07-30 11:57:23.737337  2024-07-30 11:57:15.904504
A          al_loss    false   0.000487    0.000153    0.000000  100/100  2024-07-30 11:57:24.180440  2024-07-30 11:57:15.608146
A          al_rtt     false   0.000487    0.000153    0.000000  100/100  2024-07-30 11:57:23.587402  2024-07-30 11:57:17.569381

Note

The previous command output should show that alarms are deactivated (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, NSM operation will detect a delay in the network and will trigger the ‘al_rtt’ alarm.

Step 11: Modify the following configuration lines 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-07-30 11:57:23.737337  2024-07-30 11:57:15.904504             2        33.17
al_loss    false   2024-07-30 11:57:24.180440  2024-07-30 11:57:15.608146             4        58.12
al_rtt     true    2024-07-30 11:57:27.346126  2024-07-30 11:57:23.587402             5        55.48

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_jitter  false   0.765618    0.009143    0.000000  100/100  2024-07-30 11:57:23.737337  2024-07-30 11:57:15.904504
A          al_loss    false   0.765618    0.009143    0.000000  100/100  2024-07-30 11:57:24.180440  2024-07-30 11:57:15.608146
A          al_rtt     true    0.765618    0.009143    0.000000  100/100  2024-07-30 11:57:27.346126  2024-07-30 11:57:23.587402

Note

The previous command output should show that the ‘al_rtt’ alarm is activated, since delays on the network are greater than the configured threshold.

Note

If the additional delay emulated in the network is removed and we wait a reasonable amount of time, NSM operation will detect significant delays no longer exist and will deactivate the ‘al_rtt’ alarm.

Step 14: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:57:23.737337  2024-07-30 11:57:15.904504             2        26.82
al_loss    false   2024-07-30 11:57:35.707244  2024-07-30 11:57:31.196624             6        62.42
al_rtt     false   2024-07-30 11:57:35.207778  2024-07-30 11:57:27.346126             6        61.26

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_jitter  false   0.000430    0.000134    0.000000  100/100  2024-07-30 11:57:23.737337  2024-07-30 11:57:15.904504
A          al_loss    false   0.000430    0.000134    0.000000  100/100  2024-07-30 11:57:35.707244  2024-07-30 11:57:31.196624
A          al_rtt     false   0.000430    0.000134    0.000000  100/100  2024-07-30 11:57:35.207778  2024-07-30 11:57:27.346126

Note

The previous command output should show the alarms are deactivated (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, NSM operation will detect said jitter in the network and will trigger the ‘al_jitter’ alarm.

Step 17: Modify the following configuration lines 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-07-30 11:57:38.804039  2024-07-30 11:57:23.737337             3        30.78
al_loss    false   2024-07-30 11:57:35.707244  2024-07-30 11:57:31.196624             6        52.23
al_rtt     true    2024-07-30 11:57:41.682539  2024-07-30 11:57:35.207778             7        51.35

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_jitter  true    0.206977    0.305224    0.000000  100/100  2024-07-30 11:57:38.804039  2024-07-30 11:57:23.737337
A          al_loss    false   0.206977    0.305224    0.000000  100/100  2024-07-30 11:57:35.707244  2024-07-30 11:57:31.196624
A          al_rtt     true    0.206977    0.305224    0.000000  100/100  2024-07-30 11:57:41.682539  2024-07-30 11:57:35.207778

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, NSM operation will no longer detect a jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Modify the following configuration lines in DUT0:

delete interfaces ethernet eth0 traffic

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-07-30 11:57:46.391227  2024-07-30 11:57:38.804039             4        38.07
al_loss    false   2024-07-30 11:57:35.707244  2024-07-30 11:57:31.196624             6        45.02
al_rtt     false   2024-07-30 11:57:44.483864  2024-07-30 11:57:41.682539             8        51.09

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_jitter  false   0.000392    0.000124    0.000000  100/100  2024-07-30 11:57:46.391227  2024-07-30 11:57:38.804039
A          al_loss    false   0.000392    0.000124    0.000000  100/100  2024-07-30 11:57:35.707244  2024-07-30 11:57:31.196624
A          al_rtt     false   0.000392    0.000124    0.000000  100/100  2024-07-30 11:57:44.483864  2024-07-30 11:57:41.682539

Note

The previous command output should show the alarms are deactivated (since the network quality is good).