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.000046    0.000011    0.000000  10/100
A          al_loss    false   0.000046    0.000011    0.000000  10/100
A          al_jitter  false   0.000046    0.000011    0.000000  10/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-10-10 08:11:29.192953                           1        52.70
al_loss    true    2024-10-10 08:11:29.042926                           1        55.02
al_rtt     true    2024-10-10 08:11:30.587215                           1        31.60

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

(al_loss)\s+(true)
Show output
------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled            Prev-toggled
------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.360253    0.389875    36.000000  100/100  2024-10-10 08:11:30.587215
A          al_loss    true    0.360253    0.389875    36.000000  100/100  2024-10-10 08:11:29.042926
A          al_jitter  true    0.360253    0.389875    36.000000  100/100  2024-10-10 08:11:29.192953

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-10-10 08:11:37.974142  2024-10-10 08:11:29.192953             2        69.57
al_loss    false   2024-10-10 08:11:38.211043  2024-10-10 08:11:29.042926             2        72.66
al_rtt     false   2024-10-10 08:11:37.158343  2024-10-10 08:11:30.587215             2        52.09

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.000416    0.000063    0.000000  100/100  2024-10-10 08:11:37.158343  2024-10-10 08:11:30.587215
A          al_loss    false   0.000416    0.000063    0.000000  100/100  2024-10-10 08:11:38.211043  2024-10-10 08:11:29.042926
A          al_jitter  false   0.000416    0.000063    0.000000  100/100  2024-10-10 08:11:37.974142  2024-10-10 08:11:29.192953

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-10-10 08:11:37.974142  2024-10-10 08:11:29.192953             2        46.78
al_loss    false   2024-10-10 08:11:38.211043  2024-10-10 08:11:29.042926             2        48.85
al_rtt     true    2024-10-10 08:11:41.662199  2024-10-10 08:11:37.158343             3        51.99

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.801442    0.009056    0.000000  100/100  2024-10-10 08:11:41.662199  2024-10-10 08:11:37.158343
A          al_loss    false   0.801442    0.009056    0.000000  100/100  2024-10-10 08:11:38.211043  2024-10-10 08:11:29.042926
A          al_jitter  false   0.801442    0.009056    0.000000  100/100  2024-10-10 08:11:37.974142  2024-10-10 08:11:29.192953

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-10-10 08:11:37.974142  2024-10-10 08:11:29.192953             2        35.75
al_loss    false   2024-10-10 08:11:50.345498  2024-10-10 08:11:45.835731             4        55.70
al_rtt     false   2024-10-10 08:11:49.847815  2024-10-10 08:11:41.662199             4        60.10

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.000427    0.000058    0.000000  100/100  2024-10-10 08:11:49.847815  2024-10-10 08:11:41.662199
A          al_loss    false   0.000427    0.000058    0.000000  100/100  2024-10-10 08:11:50.345498  2024-10-10 08:11:45.835731
A          al_jitter  false   0.000427    0.000058    0.000000  100/100  2024-10-10 08:11:37.974142  2024-10-10 08:11:29.192953

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-10-10 08:11:53.614713  2024-10-10 08:11:37.974142             3        38.34
al_loss    false   2024-10-10 08:11:50.345498  2024-10-10 08:11:45.835731             4        44.96
al_rtt     true    2024-10-10 08:11:56.390844  2024-10-10 08:11:49.847815             5        48.87

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.229381    0.322931    0.000000  100/100  2024-10-10 08:11:56.390844  2024-10-10 08:11:49.847815
A          al_loss    false   0.229381    0.322931    0.000000  100/100  2024-10-10 08:11:50.345498  2024-10-10 08:11:45.835731
A          al_jitter  true    0.229381    0.322931    0.000000  100/100  2024-10-10 08:11:53.614713  2024-10-10 08:11:37.974142

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-10-10 08:12:01.177177  2024-10-10 08:11:53.614713             4        45.09
al_loss    false   2024-10-10 08:11:50.345498  2024-10-10 08:11:45.835731             4        37.74
al_rtt     false   2024-10-10 08:11:59.665193  2024-10-10 08:11:56.390844             6        49.76

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.000422    0.000085    0.000000  100/100  2024-10-10 08:11:59.665193  2024-10-10 08:11:56.390844
A          al_loss    false   0.000422    0.000085    0.000000  100/100  2024-10-10 08:11:50.345498  2024-10-10 08:11:45.835731
A          al_jitter  false   0.000422    0.000085    0.000000  100/100  2024-10-10 08:12:01.177177  2024-10-10 08:11:53.614713

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.000041    0.000006    0.000000  10/100
A          al_loss    false   0.000041    0.000006    0.000000  10/100
A          al_jitter  false   0.000041    0.000006    0.000000  10/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-10-10 08:12:14.663038                           1        53.88
al_loss    true    2024-10-10 08:12:14.355655                           1        58.63
al_rtt     true    2024-10-10 08:12:15.851249                           1        35.20

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.480215    0.439835    48.000000  100/100  2024-10-10 08:12:15.851249
A          al_loss    true    0.480215    0.439835    48.000000  100/100  2024-10-10 08:12:14.355655
A          al_jitter  true    0.480215    0.439835    48.000000  100/100  2024-10-10 08:12:14.663038

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-10-10 08:12:23.025219  2024-10-10 08:12:14.663038             2        67.78
al_loss    false   2024-10-10 08:12:23.527680  2024-10-10 08:12:14.355655             2        74.29
al_rtt     false   2024-10-10 08:12:22.163860  2024-10-10 08:12:15.851249             2        51.15

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.000416    0.000051    0.000000  100/100  2024-10-10 08:12:22.163860  2024-10-10 08:12:15.851249
A          al_loss    false   0.000416    0.000051    0.000000  100/100  2024-10-10 08:12:23.527680  2024-10-10 08:12:14.355655
A          al_jitter  false   0.000416    0.000051    0.000000  100/100  2024-10-10 08:12:23.025219  2024-10-10 08:12:14.663038

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-10-10 08:12:23.025219  2024-10-10 08:12:14.663038             2        45.33
al_loss    false   2024-10-10 08:12:23.527680  2024-10-10 08:12:14.355655             2        49.69
al_rtt     true    2024-10-10 08:12:26.980360  2024-10-10 08:12:22.163860             3        51.52

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.801421    0.009056    0.000000  100/100  2024-10-10 08:12:26.980360  2024-10-10 08:12:22.163860
A          al_loss    false   0.801421    0.009056    0.000000  100/100  2024-10-10 08:12:23.527680  2024-10-10 08:12:14.355655
A          al_jitter  false   0.801421    0.009056    0.000000  100/100  2024-10-10 08:12:23.025219  2024-10-10 08:12:14.663038

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-10-10 08:12:23.025219  2024-10-10 08:12:14.663038             2        34.31
al_loss    false   2024-10-10 08:12:35.736433  2024-10-10 08:12:31.230980             4        56.10
al_rtt     false   2024-10-10 08:12:35.244486  2024-10-10 08:12:26.980360             4        59.79

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.000416    0.000067    0.000000  100/100  2024-10-10 08:12:35.244486  2024-10-10 08:12:26.980360
A          al_loss    false   0.000416    0.000067    0.000000  100/100  2024-10-10 08:12:35.736433  2024-10-10 08:12:31.230980
A          al_jitter  false   0.000416    0.000067    0.000000  100/100  2024-10-10 08:12:23.025219  2024-10-10 08:12:14.663038

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-10-10 08:12:39.675665  2024-10-10 08:12:23.025219             3        35.60
al_loss    false   2024-10-10 08:12:35.736433  2024-10-10 08:12:31.230980             4        44.95
al_rtt     false   2024-10-10 08:12:35.244486  2024-10-10 08:12:26.980360             4        47.92

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.198258    0.276730    0.000000  100/100  2024-10-10 08:12:35.244486  2024-10-10 08:12:26.980360
A          al_loss    false   0.198258    0.276730    0.000000  100/100  2024-10-10 08:12:35.736433  2024-10-10 08:12:31.230980
A          al_jitter  true    0.198258    0.276730    0.000000  100/100  2024-10-10 08:12:39.675665  2024-10-10 08:12:23.025219

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-10-10 08:12:47.263747  2024-10-10 08:12:39.675665             4        43.88
al_loss    false   2024-10-10 08:12:47.615917  2024-10-10 08:12:43.664034             6        48.49
al_rtt     false   2024-10-10 08:12:45.826933  2024-10-10 08:12:42.666249             6        48.80

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000430    0.000059    0.000000  100/100  2024-10-10 08:12:45.826933  2024-10-10 08:12:42.666249
A          al_loss    false   0.000430    0.000059    0.000000  100/100  2024-10-10 08:12:47.615917  2024-10-10 08:12:43.664034
A          al_jitter  false   0.000430    0.000059    0.000000  100/100  2024-10-10 08:12:47.263747  2024-10-10 08:12:39.675665

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-10-10 08:13:04.154279  2024-10-10 08:12:59.456558             2        66.04
al_rtt     false   2024-10-10 08:13:04.104822  2024-10-10 08:13:00.212865             2        54.74

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.000387    0.000044    0.000000  100/100  2024-10-10 08:13:04.104822  2024-10-10 08:13:00.212865
A          al_loss    false   0.000387    0.000044    0.000000  100/100  2024-10-10 08:13:04.154279  2024-10-10 08:12:59.456558
A          al_jitter  false   0.000387    0.000044    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-10-10 08:13:07.975637                                         1        25.66
al_loss    true    2024-10-10 08:13:07.591580  2024-10-10 08:13:04.154279             3        63.95
al_rtt     true    2024-10-10 08:13:08.976734  2024-10-10 08:13:04.104822             3        47.46

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled                   Prev-toggled
--------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.440318    0.450058    44.000000  100/100  2024-10-10 08:13:08.976734  2024-10-10 08:13:04.104822
A          al_loss    true    0.440318    0.450058    44.000000  100/100  2024-10-10 08:13:07.591580  2024-10-10 08:13:04.154279
A          al_jitter  true    0.440318    0.450058    44.000000  100/100  2024-10-10 08:13:07.975637

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-10-10 08:13:16.547675  2024-10-10 08:13:07.975637             2        44.99
al_loss    false   2024-10-10 08:13:16.510735  2024-10-10 08:13:07.591580             4        71.48
al_rtt     false   2024-10-10 08:13:15.793804  2024-10-10 08:13:08.976734             4        56.23

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.000380    0.000053    0.000000  100/100  2024-10-10 08:13:15.793804  2024-10-10 08:13:08.976734
A          al_loss    false   0.000380    0.000053    0.000000  100/100  2024-10-10 08:13:16.510735  2024-10-10 08:13:07.591580
A          al_jitter  false   0.000380    0.000053    0.000000  100/100  2024-10-10 08:13:16.547675  2024-10-10 08:13:07.975637

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-10-10 08:13:16.547675  2024-10-10 08:13:07.975637             2        34.25
al_loss    false   2024-10-10 08:13:16.510735  2024-10-10 08:13:07.591580             4        54.42
al_rtt     true    2024-10-10 08:13:19.970518  2024-10-10 08:13:15.793804             5        55.44

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.801404    0.009056    0.000000  100/100  2024-10-10 08:13:19.970518  2024-10-10 08:13:15.793804
A          al_loss    false   0.801404    0.009056    0.000000  100/100  2024-10-10 08:13:16.510735  2024-10-10 08:13:07.591580
A          al_jitter  false   0.801404    0.009056    0.000000  100/100  2024-10-10 08:13:16.547675  2024-10-10 08:13:07.975637

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-10-10 08:13:16.547675  2024-10-10 08:13:07.975637             2        27.84
al_loss    false   2024-10-10 08:13:28.578943  2024-10-10 08:13:24.067423             6        58.89
al_rtt     false   2024-10-10 08:13:28.073522  2024-10-10 08:13:19.970518             6        61.12

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.000386    0.000041    0.000000  100/100  2024-10-10 08:13:28.073522  2024-10-10 08:13:19.970518
A          al_loss    false   0.000386    0.000041    0.000000  100/100  2024-10-10 08:13:28.578943  2024-10-10 08:13:24.067423
A          al_jitter  false   0.000386    0.000041    0.000000  100/100  2024-10-10 08:13:16.547675  2024-10-10 08:13:07.975637

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-10-10 08:13:31.903038  2024-10-10 08:13:16.547675             3        31.45
al_loss    false   2024-10-10 08:13:28.578943  2024-10-10 08:13:24.067423             6        49.27
al_rtt     true    2024-10-10 08:13:34.714882  2024-10-10 08:13:28.073522             7        51.65

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.209169    0.306807    0.000000  100/100  2024-10-10 08:13:34.714882  2024-10-10 08:13:28.073522
A          al_loss    false   0.209169    0.306807    0.000000  100/100  2024-10-10 08:13:28.578943  2024-10-10 08:13:24.067423
A          al_jitter  true    0.209169    0.306807    0.000000  100/100  2024-10-10 08:13:31.903038  2024-10-10 08:13:16.547675

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-10-10 08:13:39.893066  2024-10-10 08:13:31.903038             4        38.79
al_loss    false   2024-10-10 08:13:40.145463  2024-10-10 08:13:36.486958             8        51.03
al_rtt     false   2024-10-10 08:13:38.285915  2024-10-10 08:13:34.714882             8        52.43

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.000386    0.000057    0.000000  100/100  2024-10-10 08:13:38.285915  2024-10-10 08:13:34.714882
A          al_loss    false   0.000386    0.000057    0.000000  100/100  2024-10-10 08:13:40.145463  2024-10-10 08:13:36.486958
A          al_jitter  false   0.000386    0.000057    0.000000  100/100  2024-10-10 08:13:39.893066  2024-10-10 08:13:31.903038

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-10-10 08:13:57.127228  2024-10-10 08:13:51.972845             2        72.81
al_rtt     false   2024-10-10 08:13:56.724236  2024-10-10 08:13:52.724014             2        56.55

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.000396    0.000312    0.000000  100/100  2024-10-10 08:13:56.724236  2024-10-10 08:13:52.724014
A          al_loss    false   0.000396    0.000312    0.000000  100/100  2024-10-10 08:13:57.127228  2024-10-10 08:13:51.972845
A          al_jitter  false   0.000396    0.000312    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-10-10 08:14:00.744301                                         1        22.73
al_loss    true    2024-10-10 08:14:00.178282  2024-10-10 08:13:57.127228             3        66.23
al_rtt     true    2024-10-10 08:14:01.837397  2024-10-10 08:13:56.724236             3        44.85

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.370265    0.389884    37.000000  100/100  2024-10-10 08:14:01.837397  2024-10-10 08:13:56.724236
A          al_loss    true    0.370265    0.389884    37.000000  100/100  2024-10-10 08:14:00.178282  2024-10-10 08:13:57.127228
A          al_jitter  true    0.370265    0.389884    37.000000  100/100  2024-10-10 08:14:00.744301

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-10-10 08:14:08.968934  2024-10-10 08:14:00.744301             2        43.11
al_loss    false   2024-10-10 08:14:09.017676  2024-10-10 08:14:00.178282             4        73.31
al_rtt     false   2024-10-10 08:14:07.845384  2024-10-10 08:14:01.837397             4        52.45

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.000378    0.000048    0.000000  100/100  2024-10-10 08:14:07.845384  2024-10-10 08:14:01.837397
A          al_loss    false   0.000378    0.000048    0.000000  100/100  2024-10-10 08:14:09.017676  2024-10-10 08:14:00.178282
A          al_jitter  false   0.000378    0.000048    0.000000  100/100  2024-10-10 08:14:08.968934  2024-10-10 08:14:00.744301

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-10-10 08:14:08.968934  2024-10-10 08:14:00.744301             2        32.77
al_loss    false   2024-10-10 08:14:09.017676  2024-10-10 08:14:00.178282             4        55.73
al_rtt     true    2024-10-10 08:14:12.553857  2024-10-10 08:14:07.845384             5        52.38

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.792432    0.009063    0.000000  100/100  2024-10-10 08:14:12.553857  2024-10-10 08:14:07.845384
A          al_loss    false   0.792432    0.009063    0.000000  100/100  2024-10-10 08:14:09.017676  2024-10-10 08:14:00.178282
A          al_jitter  false   0.792432    0.009063    0.000000  100/100  2024-10-10 08:14:08.968934  2024-10-10 08:14:00.744301

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-10-10 08:14:08.968934  2024-10-10 08:14:00.744301             2        26.66
al_loss    false   2024-10-10 08:14:21.134870  2024-10-10 08:14:16.609706             6        60.01
al_rtt     false   2024-10-10 08:14:20.621022  2024-10-10 08:14:12.553857             6        58.59

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000371    0.000054    0.000000  100/100  2024-10-10 08:14:20.621022  2024-10-10 08:14:12.553857
A          al_loss    false   0.000371    0.000054    0.000000  100/100  2024-10-10 08:14:21.134870  2024-10-10 08:14:16.609706
A          al_jitter  false   0.000371    0.000054    0.000000  100/100  2024-10-10 08:14:08.968934  2024-10-10 08:14:00.744301

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-10-10 08:14:24.462844  2024-10-10 08:14:08.968934             3        30.34
al_loss    false   2024-10-10 08:14:21.134870  2024-10-10 08:14:16.609706             6        50.29
al_rtt     false   2024-10-10 08:14:20.621022  2024-10-10 08:14:12.553857             6        49.10

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.165596    0.248984    0.000000  100/100  2024-10-10 08:14:20.621022  2024-10-10 08:14:12.553857
A          al_loss    false   0.165596    0.248984    0.000000  100/100  2024-10-10 08:14:21.134870  2024-10-10 08:14:16.609706
A          al_jitter  true    0.165596    0.248984    0.000000  100/100  2024-10-10 08:14:24.462844  2024-10-10 08:14:08.968934

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-10-10 08:14:31.892140  2024-10-10 08:14:24.462844             4        36.73
al_loss    false   2024-10-10 08:14:21.134870  2024-10-10 08:14:16.609706             6        43.44
al_rtt     false   2024-10-10 08:14:29.195942  2024-10-10 08:14:27.838917             8        45.59

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.000368    0.000057    0.000000  100/100  2024-10-10 08:14:29.195942  2024-10-10 08:14:27.838917
A          al_loss    false   0.000368    0.000057    0.000000  100/100  2024-10-10 08:14:21.134870  2024-10-10 08:14:16.609706
A          al_jitter  false   0.000368    0.000057    0.000000  100/100  2024-10-10 08:14:31.892140  2024-10-10 08:14:24.462844

Note

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