Check Icmp Operation

This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the ICMP protocol.

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

Test IPv4 Destination

Description

In this scenario, ICMP NSM operations are configured in DUT0 (using an IPv4 destination address).

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set service nsm operation A destination-address 10.215.200.100
set service nsm operation A type icmp
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A window 100
set service nsm operation A alarm al_loss activate loss 5
set service nsm operation A alarm al_rtt activate rtt 0.2
set service nsm operation A alarm al_jitter activate jitter 0.1
set system alarm al_loss
set system alarm al_rtt
set system alarm al_jitter

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------
  Alarm    Status  Toggled  Prev-toggled  Toggle-count  Time up (%)
-------------------------------------------------------------------
al_jitter  false                                     0         0.00
al_loss    false                                     0         0.00
al_rtt     false                                     0         0.00

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
---------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window  Toggled  Prev-toggled
---------------------------------------------------------------------------------------------
A          al_rtt     false   0.000037    0.000004    0.000000  9/100
A          al_loss    false   0.000037    0.000004    0.000000  9/100
A          al_jitter  false   0.000037    0.000004    0.000000  9/100

Note

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

Note

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

Step 5: Set the following configuration in DUT0:

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

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-06-24 13:09:25.741047                           1        50.24
al_loss    true    2024-06-24 13:09:25.149357                           1        59.64
al_rtt     true    2024-06-24 13:09:26.347711                           1        40.70

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

(al_loss)\s+(true)
Show output
------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled            Prev-toggled
------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.460216    0.409861    46.000000  100/100  2024-06-24 13:09:26.347711
A          al_loss    true    0.460216    0.409861    46.000000  100/100  2024-06-24 13:09:25.149357
A          al_jitter  true    0.460216    0.409861    46.000000  100/100  2024-06-24 13:09:25.741047

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.

Note

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

Step 8: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:09:33.867695  2024-06-24 13:09:25.741047             2        66.65
al_loss    false   2024-06-24 13:09:34.378946  2024-06-24 13:09:25.149357             2        75.72
al_rtt     false   2024-06-24 13:09:33.501189  2024-06-24 13:09:26.347711             2        58.71

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000588    0.000414    0.000000  100/100  2024-06-24 13:09:33.501189  2024-06-24 13:09:26.347711
A          al_loss    false   0.000588    0.000414    0.000000  100/100  2024-06-24 13:09:34.378946  2024-06-24 13:09:25.149357
A          al_jitter  false   0.000588    0.000414    0.000000  100/100  2024-06-24 13:09:33.867695  2024-06-24 13:09:25.741047

Note

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

Note

If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.

Step 11: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out RTT
set traffic control RTT type network-emulator network-delay 900

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

(al_rtt)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:09:33.867695  2024-06-24 13:09:25.741047             2        44.29
al_loss    false   2024-06-24 13:09:34.378946  2024-06-24 13:09:25.149357             2        50.31
al_rtt     true    2024-06-24 13:09:37.776423  2024-06-24 13:09:33.501189             3        56.28

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.801403    0.009071    0.000000  100/100  2024-06-24 13:09:37.776423  2024-06-24 13:09:33.501189
A          al_loss    false   0.801403    0.009071    0.000000  100/100  2024-06-24 13:09:34.378946  2024-06-24 13:09:25.149357
A          al_jitter  false   0.801403    0.009071    0.000000  100/100  2024-06-24 13:09:33.867695  2024-06-24 13:09:25.741047

Note

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

Note

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

Step 14: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:09:33.867695  2024-06-24 13:09:25.741047             2        33.56
al_loss    false   2024-06-24 13:09:46.434514  2024-06-24 13:09:41.927430             4        56.74
al_rtt     false   2024-06-24 13:09:45.923143  2024-06-24 13:09:37.776423             4        63.20

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000404    0.000054    0.000000  100/100  2024-06-24 13:09:45.923143  2024-06-24 13:09:37.776423
A          al_loss    false   0.000404    0.000054    0.000000  100/100  2024-06-24 13:09:46.434514  2024-06-24 13:09:41.927430
A          al_jitter  false   0.000404    0.000054    0.000000  100/100  2024-06-24 13:09:33.867695  2024-06-24 13:09:25.741047

Note

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

Note

If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.

Step 17: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out JITTER
set traffic control JITTER type network-emulator network-delay 1 jitter 1000

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

(al_jitter)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-06-24 13:09:50.007295  2024-06-24 13:09:33.867695             3        36.05
al_loss    false   2024-06-24 13:09:46.434514  2024-06-24 13:09:41.927430             4        45.56
al_rtt     true    2024-06-24 13:09:52.696038  2024-06-24 13:09:45.923143             5        50.93

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.238177    0.332055    1.000000  100/100  2024-06-24 13:09:52.696038  2024-06-24 13:09:45.923143
A          al_loss    false   0.238177    0.332055    1.000000  100/100  2024-06-24 13:09:46.434514  2024-06-24 13:09:41.927430
A          al_jitter  true    0.238177    0.332055    1.000000  100/100  2024-06-24 13:09:50.007295  2024-06-24 13:09:33.867695

Note

The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.

Note

If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:09:57.797565  2024-06-24 13:09:50.007295             4        44.32
al_loss    false   2024-06-24 13:09:58.112219  2024-06-24 13:09:54.096527             6        49.43
al_rtt     false   2024-06-24 13:09:56.546942  2024-06-24 13:09:52.696038             6        53.34

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000381    0.000046    0.000000  100/100  2024-06-24 13:09:56.546942  2024-06-24 13:09:52.696038
A          al_loss    false   0.000381    0.000046    0.000000  100/100  2024-06-24 13:09:58.112219  2024-06-24 13:09:54.096527
A          al_jitter  false   0.000381    0.000046    0.000000  100/100  2024-06-24 13:09:57.797565  2024-06-24 13:09:50.007295

Note

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


Test IPv4 FQDN Destination

Description

In this scenario, ICMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address).

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set service nsm operation A destination-address test.nsm.fqdn
set service nsm operation A type icmp
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A window 100
set service nsm operation A alarm al_loss activate loss 5
set service nsm operation A alarm al_rtt activate rtt 0.2
set service nsm operation A alarm al_jitter activate jitter 0.1
set system alarm al_loss
set system alarm al_rtt
set system alarm al_jitter
set service dns static host-name testnsm alias test.nsm.fqdn
set service dns static host-name testnsm inet 10.215.200.100

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------
  Alarm    Status  Toggled  Prev-toggled  Toggle-count  Time up (%)
-------------------------------------------------------------------
al_jitter  false                                     0         0.00
al_loss    false                                     0         0.00
al_rtt     false                                     0         0.00

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
---------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window  Toggled  Prev-toggled
---------------------------------------------------------------------------------------------
A          al_rtt     false   0.000035    0.000006    0.000000  9/100
A          al_loss    false   0.000035    0.000006    0.000000  9/100
A          al_jitter  false   0.000035    0.000006    0.000000  9/100

Note

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

Note

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

Step 5: Set the following configuration in DUT0:

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

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-06-24 13:10:11.840239                           1        49.41
al_loss    true    2024-06-24 13:10:11.206181                           1        59.32
al_rtt     true    2024-06-24 13:10:13.173689                           1        28.38

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

(al_loss)\s+(true)
Show output
------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled            Prev-toggled
------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.390259    0.419841    39.000000  100/100  2024-06-24 13:10:13.173689
A          al_loss    true    0.390259    0.419841    39.000000  100/100  2024-06-24 13:10:11.206181
A          al_jitter  true    0.390259    0.419841    39.000000  100/100  2024-06-24 13:10:11.840239

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.

Note

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

Step 8: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:10:19.962485  2024-06-24 13:10:11.840239             2        66.89
al_loss    false   2024-06-24 13:10:20.065370  2024-06-24 13:10:11.206181             2        72.90
al_rtt     false   2024-06-24 13:10:18.924418  2024-06-24 13:10:13.173689             2        47.34

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000407    0.000060    0.000000  100/100  2024-06-24 13:10:18.924418  2024-06-24 13:10:13.173689
A          al_loss    false   0.000407    0.000060    0.000000  100/100  2024-06-24 13:10:20.065370  2024-06-24 13:10:11.206181
A          al_jitter  false   0.000407    0.000060    0.000000  100/100  2024-06-24 13:10:19.962485  2024-06-24 13:10:11.840239

Note

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

Note

If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.

Step 11: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out RTT
set traffic control RTT type network-emulator network-delay 900

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

(al_rtt)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:10:19.962485  2024-06-24 13:10:11.840239             2        44.71
al_loss    false   2024-06-24 13:10:20.065370  2024-06-24 13:10:11.206181             2        48.75
al_rtt     true    2024-06-24 13:10:23.673326  2024-06-24 13:10:18.924418             3        48.83

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.792442    0.009059    0.000000  100/100  2024-06-24 13:10:23.673326  2024-06-24 13:10:18.924418
A          al_loss    false   0.792442    0.009059    0.000000  100/100  2024-06-24 13:10:20.065370  2024-06-24 13:10:11.206181
A          al_jitter  false   0.792442    0.009059    0.000000  100/100  2024-06-24 13:10:19.962485  2024-06-24 13:10:11.840239

Note

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

Note

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

Step 14: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:10:19.962485  2024-06-24 13:10:11.840239             2        33.83
al_loss    false   2024-06-24 13:10:32.287893  2024-06-24 13:10:27.772696             4        55.69
al_rtt     false   2024-06-24 13:10:31.781209  2024-06-24 13:10:23.673326             4        57.72

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000379    0.000057    0.000000  100/100  2024-06-24 13:10:31.781209  2024-06-24 13:10:23.673326
A          al_loss    false   0.000379    0.000057    0.000000  100/100  2024-06-24 13:10:32.287893  2024-06-24 13:10:27.772696
A          al_jitter  false   0.000379    0.000057    0.000000  100/100  2024-06-24 13:10:19.962485  2024-06-24 13:10:11.840239

Note

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

Note

If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.

Step 17: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out JITTER
set traffic control JITTER type network-emulator network-delay 1 jitter 1000

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

(al_jitter)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-06-24 13:10:35.571134  2024-06-24 13:10:19.962485             3        37.27
al_loss    false   2024-06-24 13:10:32.287893  2024-06-24 13:10:27.772696             4        44.57
al_rtt     true    2024-06-24 13:10:38.291761  2024-06-24 13:10:31.781209             5        47.32

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.244209    0.311958    0.000000  100/100  2024-06-24 13:10:38.291761  2024-06-24 13:10:31.781209
A          al_loss    false   0.244209    0.311958    0.000000  100/100  2024-06-24 13:10:32.287893  2024-06-24 13:10:27.772696
A          al_jitter  true    0.244209    0.311958    0.000000  100/100  2024-06-24 13:10:35.571134  2024-06-24 13:10:19.962485

Note

The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.

Note

If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:10:42.899295  2024-06-24 13:10:35.571134             4        43.12
al_loss    false   2024-06-24 13:10:32.287893  2024-06-24 13:10:27.772696             4        37.32
al_rtt     false   2024-06-24 13:10:41.516907  2024-06-24 13:10:38.291761             6        47.67

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000413    0.000053    0.000000  100/100  2024-06-24 13:10:41.516907  2024-06-24 13:10:38.291761
A          al_loss    false   0.000413    0.000053    0.000000  100/100  2024-06-24 13:10:32.287893  2024-06-24 13:10:27.772696
A          al_jitter  false   0.000413    0.000053    0.000000  100/100  2024-06-24 13:10:42.899295  2024-06-24 13:10:35.571134

Note

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


Test IPv6 Destination

Description

In this scenario, ICMP NSM operations are configured in DUT0 (using an IPv6 destination address).

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10::3/64

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10::2/64
set service nsm operation A destination-address 10::3
set service nsm operation A type icmp
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A window 100
set service nsm operation A alarm al_loss activate loss 5
set service nsm operation A alarm al_rtt activate rtt 0.2
set service nsm operation A alarm al_jitter activate jitter 0.1
set system alarm al_loss
set system alarm al_rtt
set system alarm al_jitter

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false                                                                      0         0.00
al_loss    false   2024-06-24 13:10:59.800133  2024-06-24 13:10:54.335596             2        77.45
al_rtt     false   2024-06-24 13:10:59.301173  2024-06-24 13:10:55.075287             2        59.93

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000366    0.000364    0.000000  100/100  2024-06-24 13:10:59.301173  2024-06-24 13:10:55.075287
A          al_loss    false   0.000366    0.000364    0.000000  100/100  2024-06-24 13:10:59.800133  2024-06-24 13:10:54.335596
A          al_jitter  false   0.000366    0.000364    0.000000  100/100

Note

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

Note

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

Step 5: Set the following configuration in DUT0:

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

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

(al_loss)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-06-24 13:11:02.544716                                         1        26.31
al_loss    true    2024-06-24 13:11:02.336920  2024-06-24 13:10:59.800133             3        70.06
al_rtt     true    2024-06-24 13:11:03.899354  2024-06-24 13:10:59.301173             3        48.48

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled                   Prev-toggled
--------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.460191    0.449850    46.000000  100/100  2024-06-24 13:11:03.899354  2024-06-24 13:10:59.301173
A          al_loss    true    0.460191    0.449850    46.000000  100/100  2024-06-24 13:11:02.336920  2024-06-24 13:10:59.800133
A          al_jitter  true    0.460191    0.449850    46.000000  100/100  2024-06-24 13:11:02.544716

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.

Note

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

Step 8: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:11:11.204155  2024-06-24 13:11:02.544716             2        46.08
al_loss    false   2024-06-24 13:11:11.154226  2024-06-24 13:11:02.336920             4        76.01
al_rtt     false   2024-06-24 13:11:10.404366  2024-06-24 13:11:03.899354             4        57.12

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000383    0.000047    0.000000  100/100  2024-06-24 13:11:10.404366  2024-06-24 13:11:03.899354
A          al_loss    false   0.000383    0.000047    0.000000  100/100  2024-06-24 13:11:11.154226  2024-06-24 13:11:02.336920
A          al_jitter  false   0.000383    0.000047    0.000000  100/100  2024-06-24 13:11:11.204155  2024-06-24 13:11:02.544716

Note

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

Note

If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.

Step 11: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out RTT
set traffic control RTT type network-emulator network-delay 900

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

(al_rtt)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:11:11.204155  2024-06-24 13:11:02.544716             2        35.06
al_loss    false   2024-06-24 13:11:11.154226  2024-06-24 13:11:02.336920             4        57.83
al_rtt     true    2024-06-24 13:11:14.566866  2024-06-24 13:11:10.404366             5        56.09

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.792416    0.009055    0.000000  100/100  2024-06-24 13:11:14.566866  2024-06-24 13:11:10.404366
A          al_loss    false   0.792416    0.009055    0.000000  100/100  2024-06-24 13:11:11.154226  2024-06-24 13:11:02.336920
A          al_jitter  false   0.792416    0.009055    0.000000  100/100  2024-06-24 13:11:11.204155  2024-06-24 13:11:02.544716

Note

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

Note

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

Step 14: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:11:11.204155  2024-06-24 13:11:02.544716             2        28.40
al_loss    false   2024-06-24 13:11:23.132047  2024-06-24 13:11:18.630045             6        61.62
al_rtt     false   2024-06-24 13:11:22.636698  2024-06-24 13:11:14.566866             6        61.68

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000414    0.000063    0.000000  100/100  2024-06-24 13:11:22.636698  2024-06-24 13:11:14.566866
A          al_loss    false   0.000414    0.000063    0.000000  100/100  2024-06-24 13:11:23.132047  2024-06-24 13:11:18.630045
A          al_jitter  false   0.000414    0.000063    0.000000  100/100  2024-06-24 13:11:11.204155  2024-06-24 13:11:02.544716

Note

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

Note

If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.

Step 17: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out JITTER
set traffic control JITTER type network-emulator network-delay 1 jitter 1000

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

(al_jitter)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-06-24 13:11:26.279279  2024-06-24 13:11:11.204155             3        32.20
al_loss    false   2024-06-24 13:11:23.132047  2024-06-24 13:11:18.630045             6        51.70
al_rtt     false   2024-06-24 13:11:22.636698  2024-06-24 13:11:14.566866             6        51.75

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.166185    0.254820    0.000000  100/100  2024-06-24 13:11:22.636698  2024-06-24 13:11:14.566866
A          al_loss    false   0.166185    0.254820    0.000000  100/100  2024-06-24 13:11:23.132047  2024-06-24 13:11:18.630045
A          al_jitter  true    0.166185    0.254820    0.000000  100/100  2024-06-24 13:11:26.279279  2024-06-24 13:11:11.204155

Note

The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.

Note

If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:11:34.151629  2024-06-24 13:11:26.279279             4        39.29
al_loss    false   2024-06-24 13:11:34.708746  2024-06-24 13:11:30.891327             8        53.73
al_rtt     false   2024-06-24 13:11:22.636698  2024-06-24 13:11:14.566866             6        44.70

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000385    0.000061    0.000000  100/100  2024-06-24 13:11:22.636698  2024-06-24 13:11:14.566866
A          al_loss    false   0.000385    0.000061    0.000000  100/100  2024-06-24 13:11:34.708746  2024-06-24 13:11:30.891327
A          al_jitter  false   0.000385    0.000061    0.000000  100/100  2024-06-24 13:11:34.151629  2024-06-24 13:11:26.279279

Note

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


Test IPv6 FQDN Destination

Description

In this scenario, ICMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address).

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10::3/64

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10::2/64
set service nsm operation A destination-address test.nsm.fqdn
set service nsm operation A type icmp
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A window 100
set service nsm operation A alarm al_loss activate loss 5
set service nsm operation A alarm al_rtt activate rtt 0.2
set service nsm operation A alarm al_jitter activate jitter 0.1
set system alarm al_loss
set system alarm al_rtt
set system alarm al_jitter
set service dns static host-name testnsm alias test.nsm.fqdn
set service dns static host-name testnsm inet 10::3

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false                                                                      0         0.00
al_loss    false   2024-06-24 13:11:51.804707  2024-06-24 13:11:46.733455             2        71.28
al_rtt     false   2024-06-24 13:11:51.464841  2024-06-24 13:11:47.492747             2        55.87

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000395    0.000058    0.000000  100/100  2024-06-24 13:11:51.464841  2024-06-24 13:11:47.492747
A          al_loss    false   0.000395    0.000058    0.000000  100/100  2024-06-24 13:11:51.804707  2024-06-24 13:11:46.733455
A          al_jitter  false   0.000395    0.000058    0.000000  100/100

Note

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

Note

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

Step 5: Set the following configuration in DUT0:

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

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

(al_loss)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-06-24 13:11:55.120389                                         1        25.80
al_loss    true    2024-06-24 13:11:55.025935  2024-06-24 13:11:51.804707             3        65.13
al_rtt     true    2024-06-24 13:11:56.713593  2024-06-24 13:11:51.464841             3        43.92

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled                   Prev-toggled
--------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.360286    0.499904    36.000000  100/100  2024-06-24 13:11:56.713593  2024-06-24 13:11:51.464841
A          al_loss    true    0.360286    0.499904    36.000000  100/100  2024-06-24 13:11:55.025935  2024-06-24 13:11:51.804707
A          al_jitter  true    0.360286    0.499904    36.000000  100/100  2024-06-24 13:11:55.120389

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.

Note

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

Step 8: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:12:03.289769  2024-06-24 13:11:55.120389             2        43.29
al_loss    false   2024-06-24 13:12:03.881217  2024-06-24 13:11:55.025935             4        73.76
al_rtt     false   2024-06-24 13:12:02.526891  2024-06-24 13:11:56.713593             4        51.84

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000363    0.000049    0.000000  100/100  2024-06-24 13:12:02.526891  2024-06-24 13:11:56.713593
A          al_loss    false   0.000363    0.000049    0.000000  100/100  2024-06-24 13:12:03.881217  2024-06-24 13:11:55.025935
A          al_jitter  false   0.000363    0.000049    0.000000  100/100  2024-06-24 13:12:03.289769  2024-06-24 13:11:55.120389

Note

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

Note

If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.

Step 11: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out RTT
set traffic control RTT type network-emulator network-delay 900

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

(al_rtt)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:12:03.289769  2024-06-24 13:11:55.120389             2        32.87
al_loss    false   2024-06-24 13:12:03.881217  2024-06-24 13:11:55.025935             4        56.02
al_rtt     true    2024-06-24 13:12:07.097845  2024-06-24 13:12:02.526891             5        52.00

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.792404    0.009056    0.000000  100/100  2024-06-24 13:12:07.097845  2024-06-24 13:12:02.526891
A          al_loss    false   0.792404    0.009056    0.000000  100/100  2024-06-24 13:12:03.881217  2024-06-24 13:11:55.025935
A          al_jitter  false   0.792404    0.009056    0.000000  100/100  2024-06-24 13:12:03.289769  2024-06-24 13:11:55.120389

Note

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

Note

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

Step 14: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:12:03.289769  2024-06-24 13:11:55.120389             2        26.66
al_loss    false   2024-06-24 13:12:15.704456  2024-06-24 13:12:11.201633             6        60.12
al_rtt     false   2024-06-24 13:12:15.201615  2024-06-24 13:12:07.097845             6        58.37

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000382    0.000048    0.000000  100/100  2024-06-24 13:12:15.201615  2024-06-24 13:12:07.097845
A          al_loss    false   0.000382    0.000048    0.000000  100/100  2024-06-24 13:12:15.704456  2024-06-24 13:12:11.201633
A          al_jitter  false   0.000382    0.000048    0.000000  100/100  2024-06-24 13:12:03.289769  2024-06-24 13:11:55.120389

Note

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

Note

If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.

Step 17: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out JITTER
set traffic control JITTER type network-emulator network-delay 1 jitter 1000

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

(al_jitter)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-06-24 13:12:19.140146  2024-06-24 13:12:03.289769             3        29.90
al_loss    false   2024-06-24 13:12:15.704456  2024-06-24 13:12:11.201633             6        50.48
al_rtt     true    2024-06-24 13:12:21.235196  2024-06-24 13:12:15.201615             7        50.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_rtt     true    0.214692    0.266230    0.000000  100/100  2024-06-24 13:12:21.235196  2024-06-24 13:12:15.201615
A          al_loss    false   0.214692    0.266230    0.000000  100/100  2024-06-24 13:12:15.704456  2024-06-24 13:12:11.201633
A          al_jitter  true    0.214692    0.266230    0.000000  100/100  2024-06-24 13:12:19.140146  2024-06-24 13:12:03.289769

Note

The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.

Note

If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-06-24 13:12:26.722937  2024-06-24 13:12:19.140146             4        37.26
al_loss    false   2024-06-24 13:12:15.704456  2024-06-24 13:12:11.201633             6        43.59
al_rtt     false   2024-06-24 13:12:24.130970  2024-06-24 13:12:21.235196             8        49.16

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000347    0.000064    0.000000  100/100  2024-06-24 13:12:24.130970  2024-06-24 13:12:21.235196
A          al_loss    false   0.000347    0.000064    0.000000  100/100  2024-06-24 13:12:15.704456  2024-06-24 13:12:11.201633
A          al_jitter  false   0.000347    0.000064    0.000000  100/100  2024-06-24 13:12:26.722937  2024-06-24 13:12:19.140146

Note

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