Check Udp Operation

This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the UDP SLA protocol. In addition, the UDP NSM responder service is configured.

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

Test IPv4 Destination

Description

In this scenario, UDP NSM operations are configured in DUT0 (using an IPv4 destination address) and the UDP NSM responder service is configured in DUT1.

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set service nsm responder type udp port 60000
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 destination-port 60000
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A type udp
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.000027    0.000011    0.000000  6/100
A          al_loss    false   0.000027    0.000011    0.000000  6/100
A          al_rtt     false   0.000027    0.000011    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-17 17:04:51.843008                           1        49.51
al_loss    true    2024-07-17 17:04:51.037292                           1        62.89
al_rtt     true    2024-07-17 17:04:52.744230                           1        34.64

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.420283    0.499807    42.000000  100/100  2024-07-17 17:04:51.843008
A          al_loss    true    0.420283    0.499807    42.000000  100/100  2024-07-17 17:04:51.037292
A          al_rtt     true    0.420283    0.499807    42.000000  100/100  2024-07-17 17:04:52.744230

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-17 17:04:59.952271  2024-07-17 17:04:51.843008             2        69.61
al_loss    false   2024-07-17 17:05:00.003166  2024-07-17 17:04:51.037292             2        76.99
al_rtt     false   2024-07-17 17:04:59.153408  2024-07-17 17:04:52.744230             2        55.05

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.000489    0.000122    0.000000  100/100  2024-07-17 17:04:59.952271  2024-07-17 17:04:51.843008
A          al_loss    false   0.000489    0.000122    0.000000  100/100  2024-07-17 17:05:00.003166  2024-07-17 17:04:51.037292
A          al_rtt     false   0.000489    0.000122    0.000000  100/100  2024-07-17 17:04:59.153408  2024-07-17 17:04:52.744230

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-17 17:04:59.952271  2024-07-17 17:04:51.843008             2        46.60
al_loss    false   2024-07-17 17:05:00.003166  2024-07-17 17:04:51.037292             2        51.54
al_rtt     true    2024-07-17 17:05:03.110790  2024-07-17 17:04:59.153408             3        54.57

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.765543    0.009137    0.000000  100/100  2024-07-17 17:04:59.952271  2024-07-17 17:04:51.843008
A          al_loss    false   0.765543    0.009137    0.000000  100/100  2024-07-17 17:05:00.003166  2024-07-17 17:04:51.037292
A          al_rtt     true    0.765543    0.009137    0.000000  100/100  2024-07-17 17:05:03.110790  2024-07-17 17:04:59.153408

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-17 17:04:59.952271  2024-07-17 17:04:51.843008             2        35.23
al_loss    false   2024-07-17 17:05:11.480345  2024-07-17 17:05:06.968559             4        58.57
al_rtt     false   2024-07-17 17:05:10.977170  2024-07-17 17:05:03.110790             4        62.04

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.000429    0.000122    0.000000  100/100  2024-07-17 17:04:59.952271  2024-07-17 17:04:51.843008
A          al_loss    false   0.000429    0.000122    0.000000  100/100  2024-07-17 17:05:11.480345  2024-07-17 17:05:06.968559
A          al_rtt     false   0.000429    0.000122    0.000000  100/100  2024-07-17 17:05:10.977170  2024-07-17 17:05:03.110790

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-17 17:05:14.335353  2024-07-17 17:04:59.952271             3        39.33
al_loss    false   2024-07-17 17:05:11.480345  2024-07-17 17:05:06.968559             4        46.91
al_rtt     true    2024-07-17 17:05:16.715607  2024-07-17 17:05:10.977170             5        52.52

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.237880    0.323561    0.000000  100/100  2024-07-17 17:05:14.335353  2024-07-17 17:04:59.952271
A          al_loss    false   0.237880    0.323561    0.000000  100/100  2024-07-17 17:05:11.480345  2024-07-17 17:05:06.968559
A          al_rtt     true    0.237880    0.323561    0.000000  100/100  2024-07-17 17:05:16.715607  2024-07-17 17:05:10.977170

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-17 17:05:22.517159  2024-07-17 17:05:14.335353             4        47.36
al_loss    false   2024-07-17 17:05:22.709277  2024-07-17 17:05:18.898483             6        50.27
al_rtt     false   2024-07-17 17:05:20.753631  2024-07-17 17:05:16.715607             6        53.26

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.000537    0.000153    0.000000  100/100  2024-07-17 17:05:22.517159  2024-07-17 17:05:14.335353
A          al_loss    false   0.000537    0.000153    0.000000  100/100  2024-07-17 17:05:22.709277  2024-07-17 17:05:18.898483
A          al_rtt     false   0.000537    0.000153    0.000000  100/100  2024-07-17 17:05:20.753631  2024-07-17 17:05:16.715607

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, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address) and the UDP NSM responder service is configured in DUT1.

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set service nsm responder type udp port 60000
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 destination-port 60000
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A type udp
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.000034    0.000009    0.000000  6/100
A          al_loss    false   0.000034    0.000009    0.000000  6/100
A          al_rtt     false   0.000034    0.000009    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-17 17:05:34.312164                           1        46.83
al_loss    true    2024-07-17 17:05:33.361165                           1        62.25
al_rtt     true    2024-07-17 17:05:35.512069                           1        27.27

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.380267    0.359888    38.000000  100/100  2024-07-17 17:05:34.312164
A          al_loss    true    0.380267    0.359888    38.000000  100/100  2024-07-17 17:05:33.361165
A          al_rtt     true    0.380267    0.359888    38.000000  100/100  2024-07-17 17:05:35.512069

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-17 17:05:42.096809  2024-07-17 17:05:34.312164             2        66.32
al_loss    false   2024-07-17 17:05:42.331441  2024-07-17 17:05:33.361165             2        76.37
al_rtt     false   2024-07-17 17:05:41.580300  2024-07-17 17:05:35.512069             2        51.68

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.000447    0.000136    0.000000  100/100  2024-07-17 17:05:42.096809  2024-07-17 17:05:34.312164
A          al_loss    false   0.000447    0.000136    0.000000  100/100  2024-07-17 17:05:42.331441  2024-07-17 17:05:33.361165
A          al_rtt     false   0.000447    0.000136    0.000000  100/100  2024-07-17 17:05:41.580300  2024-07-17 17:05:35.512069

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-17 17:05:42.096809  2024-07-17 17:05:34.312164             2        44.55
al_loss    false   2024-07-17 17:05:42.331441  2024-07-17 17:05:33.361165             2        51.32
al_rtt     true    2024-07-17 17:05:45.440492  2024-07-17 17:05:41.580300             3        52.35

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_jitter  false   0.765481    0.009125    0.000000  100/100  2024-07-17 17:05:42.096809  2024-07-17 17:05:34.312164
A          al_loss    false   0.765481    0.009125    0.000000  100/100  2024-07-17 17:05:42.331441  2024-07-17 17:05:33.361165
A          al_rtt     true    0.765481    0.009125    0.000000  100/100  2024-07-17 17:05:45.440492  2024-07-17 17:05:41.580300

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-17 17:05:42.096809  2024-07-17 17:05:34.312164             2        33.74
al_loss    false   2024-07-17 17:05:53.814806  2024-07-17 17:05:49.294027             4        58.45
al_rtt     false   2024-07-17 17:05:53.311180  2024-07-17 17:05:45.440492             4        60.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_jitter  false   0.000449    0.000114    0.000000  100/100  2024-07-17 17:05:42.096809  2024-07-17 17:05:34.312164
A          al_loss    false   0.000449    0.000114    0.000000  100/100  2024-07-17 17:05:53.814806  2024-07-17 17:05:49.294027
A          al_rtt     false   0.000449    0.000114    0.000000  100/100  2024-07-17 17:05:53.311180  2024-07-17 17:05:45.440492

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-17 17:05:56.781907  2024-07-17 17:05:42.096809             3        37.74
al_loss    false   2024-07-17 17:05:53.814806  2024-07-17 17:05:49.294027             4        46.79
al_rtt     true    2024-07-17 17:05:58.919935  2024-07-17 17:05:53.311180             5        51.66

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.258225    0.334355    0.000000  100/100  2024-07-17 17:05:56.781907  2024-07-17 17:05:42.096809
A          al_loss    false   0.258225    0.334355    0.000000  100/100  2024-07-17 17:05:53.814806  2024-07-17 17:05:49.294027
A          al_rtt     true    0.258225    0.334355    0.000000  100/100  2024-07-17 17:05:58.919935  2024-07-17 17:05:53.311180

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-17 17:06:04.835583  2024-07-17 17:05:56.781907             4        45.91
al_loss    false   2024-07-17 17:06:05.079770  2024-07-17 17:06:01.370700             6        49.85
al_rtt     false   2024-07-17 17:06:03.026430  2024-07-17 17:05:58.919935             6        52.30

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.000404    0.000105    0.000000  100/100  2024-07-17 17:06:04.835583  2024-07-17 17:05:56.781907
A          al_loss    false   0.000404    0.000105    0.000000  100/100  2024-07-17 17:06:05.079770  2024-07-17 17:06:01.370700
A          al_rtt     false   0.000404    0.000105    0.000000  100/100  2024-07-17 17:06:03.026430  2024-07-17 17:05:58.919935

Note

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


Test IPv6 Destination

Description

In this scenario, UDP NSM operations are configured in DUT0 (using an IPv6 destination address) and the UDP NSM responder service is configured in DUT1.

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address '10::3/64'
set service nsm responder type udp port 60000
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 destination-port 60000
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A type udp
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-17 17:06:18.087730  2024-07-17 17:06:13.326779             2        70.18
al_rtt     false   2024-07-17 17:06:17.988484  2024-07-17 17:06:14.075079             2        57.72

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.014745    0.004184    0.000000  100/100
A          al_loss    false   0.014745    0.004184    0.000000  100/100  2024-07-17 17:06:18.087730  2024-07-17 17:06:13.326779
A          al_rtt     false   0.014745    0.004184    0.000000  100/100  2024-07-17 17:06:17.988484  2024-07-17 17:06:14.075079

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-17 17:06:21.649677                                         1        22.67
al_loss    true    2024-07-17 17:06:20.948635  2024-07-17 17:06:18.087730             3        66.35
al_rtt     true    2024-07-17 17:06:22.698133  2024-07-17 17:06:17.988484             3        45.59

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.400298    0.419781    40.000000  100/100  2024-07-17 17:06:21.649677
A          al_loss    true    0.400298    0.419781    40.000000  100/100  2024-07-17 17:06:20.948635  2024-07-17 17:06:18.087730
A          al_rtt     true    0.400298    0.419781    40.000000  100/100  2024-07-17 17:06:22.698133  2024-07-17 17:06:17.988484

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-17 17:06:29.615118  2024-07-17 17:06:21.649677             2        43.75
al_loss    false   2024-07-17 17:06:29.717679  2024-07-17 17:06:20.948635             4        74.32
al_rtt     false   2024-07-17 17:06:29.018055  2024-07-17 17:06:22.698133             4        56.22

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_jitter  false   0.000519    0.000132    0.000000  100/100  2024-07-17 17:06:29.615118  2024-07-17 17:06:21.649677
A          al_loss    false   0.000519    0.000132    0.000000  100/100  2024-07-17 17:06:29.717679  2024-07-17 17:06:20.948635
A          al_rtt     false   0.000519    0.000132    0.000000  100/100  2024-07-17 17:06:29.018055  2024-07-17 17:06:22.698133

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-17 17:06:29.615118  2024-07-17 17:06:21.649677             2        33.27
al_loss    false   2024-07-17 17:06:29.717679  2024-07-17 17:06:20.948635             4        56.52
al_rtt     true    2024-07-17 17:06:32.821312  2024-07-17 17:06:29.018055             5        55.69

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_jitter  false   0.774576    0.009161    0.000000  100/100  2024-07-17 17:06:29.615118  2024-07-17 17:06:21.649677
A          al_loss    false   0.774576    0.009161    0.000000  100/100  2024-07-17 17:06:29.717679  2024-07-17 17:06:20.948635
A          al_rtt     true    0.774576    0.009161    0.000000  100/100  2024-07-17 17:06:32.821312  2024-07-17 17:06:29.018055

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-17 17:06:29.615118  2024-07-17 17:06:21.649677             2        26.94
al_loss    false   2024-07-17 17:06:41.215374  2024-07-17 17:06:36.683733             6        61.11
al_rtt     false   2024-07-17 17:06:40.696830  2024-07-17 17:06:32.821312             6        61.27

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.000575    0.000191    0.000000  100/100  2024-07-17 17:06:29.615118  2024-07-17 17:06:21.649677
A          al_loss    false   0.000575    0.000191    0.000000  100/100  2024-07-17 17:06:41.215374  2024-07-17 17:06:36.683733
A          al_rtt     false   0.000575    0.000191    0.000000  100/100  2024-07-17 17:06:40.696830  2024-07-17 17:06:32.821312

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-17 17:06:44.010870  2024-07-17 17:06:29.615118             3        31.74
al_loss    false   2024-07-17 17:06:41.215374  2024-07-17 17:06:36.683733             6        51.22
al_rtt     true    2024-07-17 17:06:47.032246  2024-07-17 17:06:40.696830             7        51.95

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.216350    0.271711    0.000000  100/100  2024-07-17 17:06:44.010870  2024-07-17 17:06:29.615118
A          al_loss    false   0.216350    0.271711    0.000000  100/100  2024-07-17 17:06:41.215374  2024-07-17 17:06:36.683733
A          al_rtt     true    0.216350    0.271711    0.000000  100/100  2024-07-17 17:06:47.032246  2024-07-17 17:06:40.696830

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-17 17:06:52.368836  2024-07-17 17:06:44.010870             4        39.91
al_loss    false   2024-07-17 17:06:52.469459  2024-07-17 17:06:48.456602             8        53.98
al_rtt     false   2024-07-17 17:06:50.714478  2024-07-17 17:06:47.032246             8        53.29

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.000418    0.000104    0.000000  100/100  2024-07-17 17:06:52.368836  2024-07-17 17:06:44.010870
A          al_loss    false   0.000418    0.000104    0.000000  100/100  2024-07-17 17:06:52.469459  2024-07-17 17:06:48.456602
A          al_rtt     false   0.000418    0.000104    0.000000  100/100  2024-07-17 17:06:50.714478  2024-07-17 17:06:47.032246

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, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address) and the UDP NSM responder service is configured in DUT1.

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address '10::3/64'
set service nsm responder type udp port 60000
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 destination-port 60000
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A type udp
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-17 17:07:06.304914  2024-07-17 17:07:01.491295             2        71.25
al_rtt     false   2024-07-17 17:07:06.149680  2024-07-17 17:07:02.234602             2        57.98

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.016673    0.004387    0.000000  100/100
A          al_loss    false   0.016673    0.004387    0.000000  100/100  2024-07-17 17:07:06.304914  2024-07-17 17:07:01.491295
A          al_rtt     false   0.016673    0.004387    0.000000  100/100  2024-07-17 17:07:06.149680  2024-07-17 17:07:02.234602

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-17 17:07:09.000208                                         1        29.12
al_loss    true    2024-07-17 17:07:08.906584  2024-07-17 17:07:06.304914             3        68.25
al_rtt     true    2024-07-17 17:07:10.413740  2024-07-17 17:07:06.149680             3        49.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.430267    0.559767    43.000000  100/100  2024-07-17 17:07:09.000208
A          al_loss    true    0.430267    0.559767    43.000000  100/100  2024-07-17 17:07:08.906584  2024-07-17 17:07:06.304914
A          al_rtt     true    0.430267    0.559767    43.000000  100/100  2024-07-17 17:07:10.413740  2024-07-17 17:07:06.149680

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-17 17:07:17.473495  2024-07-17 17:07:09.000208             2        46.31
al_loss    false   2024-07-17 17:07:17.982759  2024-07-17 17:07:08.906584             4        75.89
al_rtt     false   2024-07-17 17:07:16.975530  2024-07-17 17:07:10.413740             4        57.25

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.000522    0.000156    0.000000  100/100  2024-07-17 17:07:17.473495  2024-07-17 17:07:09.000208
A          al_loss    false   0.000522    0.000156    0.000000  100/100  2024-07-17 17:07:17.982759  2024-07-17 17:07:08.906584
A          al_rtt     false   0.000522    0.000156    0.000000  100/100  2024-07-17 17:07:16.975530  2024-07-17 17:07:10.413740

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-17 17:07:17.473495  2024-07-17 17:07:09.000208             2        35.27
al_loss    false   2024-07-17 17:07:17.982759  2024-07-17 17:07:08.906584             4        57.80
al_rtt     true    2024-07-17 17:07:21.032640  2024-07-17 17:07:16.975530             5        56.56

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.774534    0.009155    0.000000  100/100  2024-07-17 17:07:17.473495  2024-07-17 17:07:09.000208
A          al_loss    false   0.774534    0.009155    0.000000  100/100  2024-07-17 17:07:17.982759  2024-07-17 17:07:08.906584
A          al_rtt     true    0.774534    0.009155    0.000000  100/100  2024-07-17 17:07:21.032640  2024-07-17 17:07:16.975530

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-17 17:07:17.473495  2024-07-17 17:07:09.000208             2        28.58
al_loss    false   2024-07-17 17:07:29.450928  2024-07-17 17:07:24.938437             6        62.06
al_rtt     false   2024-07-17 17:07:28.949412  2024-07-17 17:07:21.032640             6        62.04

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.000514    0.000139    0.000000  100/100  2024-07-17 17:07:17.473495  2024-07-17 17:07:09.000208
A          al_loss    false   0.000514    0.000139    0.000000  100/100  2024-07-17 17:07:29.450928  2024-07-17 17:07:24.938437
A          al_rtt     false   0.000514    0.000139    0.000000  100/100  2024-07-17 17:07:28.949412  2024-07-17 17:07:21.032640

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-17 17:07:33.004089  2024-07-17 17:07:17.473495             3        31.08
al_loss    false   2024-07-17 17:07:29.450928  2024-07-17 17:07:24.938437             6        51.95
al_rtt     false   2024-07-17 17:07:28.949412  2024-07-17 17:07:21.032640             6        51.93

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_jitter  true    0.189368    0.263789    0.000000  100/100  2024-07-17 17:07:33.004089  2024-07-17 17:07:17.473495
A          al_loss    false   0.189368    0.263789    0.000000  100/100  2024-07-17 17:07:29.450928  2024-07-17 17:07:24.938437
A          al_rtt     false   0.189368    0.263789    0.000000  100/100  2024-07-17 17:07:28.949412  2024-07-17 17:07:21.032640

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-17 17:07:40.126423  2024-07-17 17:07:33.004089             4        37.91
al_loss    false   2024-07-17 17:07:40.885170  2024-07-17 17:07:36.920189             8        54.36
al_rtt     false   2024-07-17 17:07:38.278791  2024-07-17 17:07:36.028571             8        50.18

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.000483    0.000132    0.000000  100/100  2024-07-17 17:07:40.126423  2024-07-17 17:07:33.004089
A          al_loss    false   0.000483    0.000132    0.000000  100/100  2024-07-17 17:07:40.885170  2024-07-17 17:07:36.920189
A          al_rtt     false   0.000483    0.000132    0.000000  100/100  2024-07-17 17:07:38.278791  2024-07-17 17:07:36.028571

Note

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