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.000117    0.000118    0.000000  11/100
A          al_loss    false   0.000117    0.000118    0.000000  11/100
A          al_jitter  false   0.000117    0.000118    0.000000  11/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-12-02 21:40:38.674065                           1        46.40
al_loss    true    2024-12-02 21:40:38.228242                           1        53.05
al_rtt     true    2024-12-02 21:40:39.534077                           1        33.71

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.420332    0.480039    42.000000  100/100  2024-12-02 21:40:39.534077
A          al_loss    true    0.420332    0.480039    42.000000  100/100  2024-12-02 21:40:38.228242
A          al_jitter  true    0.420332    0.480039    42.000000  100/100  2024-12-02 21:40:38.674065

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-12-02 21:40:47.006319  2024-12-02 21:40:38.674065             2        65.34
al_loss    false   2024-12-02 21:40:47.157302  2024-12-02 21:40:38.228242             2        70.05
al_rtt     false   2024-12-02 21:40:45.865943  2024-12-02 21:40:39.534077             2        49.69

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.000481    0.000259    0.000000  100/100  2024-12-02 21:40:45.865943  2024-12-02 21:40:39.534077
A          al_loss    false   0.000481    0.000259    0.000000  100/100  2024-12-02 21:40:47.157302  2024-12-02 21:40:38.228242
A          al_jitter  false   0.000481    0.000259    0.000000  100/100  2024-12-02 21:40:47.006319  2024-12-02 21:40:38.674065

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-12-02 21:40:47.006319  2024-12-02 21:40:38.674065             2        43.85
al_loss    false   2024-12-02 21:40:47.157302  2024-12-02 21:40:38.228242             2        47.00
al_rtt     true    2024-12-02 21:40:50.930163  2024-12-02 21:40:45.865943             3        49.81

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.792517    0.009293    0.000000  100/100  2024-12-02 21:40:50.930163  2024-12-02 21:40:45.865943
A          al_loss    false   0.792517    0.009293    0.000000  100/100  2024-12-02 21:40:47.157302  2024-12-02 21:40:38.228242
A          al_jitter  false   0.792517    0.009293    0.000000  100/100  2024-12-02 21:40:47.006319  2024-12-02 21:40:38.674065

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-12-02 21:40:47.006319  2024-12-02 21:40:38.674065             2        33.52
al_loss    false   2024-12-02 21:40:59.540239  2024-12-02 21:40:55.019305             4        54.11
al_rtt     false   2024-12-02 21:40:59.027171  2024-12-02 21:40:50.930163             4        58.06

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.000333    0.000046    0.000000  100/100  2024-12-02 21:40:59.027171  2024-12-02 21:40:50.930163
A          al_loss    false   0.000333    0.000046    0.000000  100/100  2024-12-02 21:40:59.540239  2024-12-02 21:40:55.019305
A          al_jitter  false   0.000333    0.000046    0.000000  100/100  2024-12-02 21:40:47.006319  2024-12-02 21:40:38.674065

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-12-02 21:41:02.858912  2024-12-02 21:40:47.006319             3        37.29
al_loss    false   2024-12-02 21:40:59.540239  2024-12-02 21:40:55.019305             4        43.32
al_rtt     true    2024-12-02 21:41:05.062618  2024-12-02 21:40:59.027171             5        49.84

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.244751    0.361857    0.000000  100/100  2024-12-02 21:41:05.062618  2024-12-02 21:40:59.027171
A          al_loss    false   0.244751    0.361857    0.000000  100/100  2024-12-02 21:40:59.540239  2024-12-02 21:40:55.019305
A          al_jitter  true    0.244751    0.361857    0.000000  100/100  2024-12-02 21:41:02.858912  2024-12-02 21:40:47.006319

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-12-02 21:41:10.711739  2024-12-02 21:41:02.858912             4        43.72
al_loss    false   2024-12-02 21:40:59.540239  2024-12-02 21:40:55.019305             4        36.33
al_rtt     false   2024-12-02 21:41:08.854196  2024-12-02 21:41:05.062618             6        49.23

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.000374    0.000071    0.000000  100/100  2024-12-02 21:41:08.854196  2024-12-02 21:41:05.062618
A          al_loss    false   0.000374    0.000071    0.000000  100/100  2024-12-02 21:40:59.540239  2024-12-02 21:40:55.019305
A          al_jitter  false   0.000374    0.000071    0.000000  100/100  2024-12-02 21:41:10.711739  2024-12-02 21:41:02.858912

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.000111    0.000132    0.000000  11/100
A          al_loss    false   0.000111    0.000132    0.000000  11/100
A          al_jitter  false   0.000111    0.000132    0.000000  11/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-12-02 21:41:28.392510                           1        43.52
al_loss    true    2024-12-02 21:41:28.149700                           1        47.00
al_rtt     true    2024-12-02 21:41:29.961662                           1        20.51

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.320357    0.430057    32.000000  100/100  2024-12-02 21:41:29.961662
A          al_loss    true    0.320357    0.430057    32.000000  100/100  2024-12-02 21:41:28.149700
A          al_jitter  true    0.320357    0.430057    32.000000  100/100  2024-12-02 21:41:28.392510

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-12-02 21:41:36.468896  2024-12-02 21:41:28.392510             2        62.69
al_loss    false   2024-12-02 21:41:36.940009  2024-12-02 21:41:28.149700             2        68.17
al_rtt     false   2024-12-02 21:41:36.066000  2024-12-02 21:41:29.961662             2        47.36

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.000365    0.000046    0.000000  100/100  2024-12-02 21:41:36.066000  2024-12-02 21:41:29.961662
A          al_loss    false   0.000365    0.000046    0.000000  100/100  2024-12-02 21:41:36.940009  2024-12-02 21:41:28.149700
A          al_jitter  false   0.000365    0.000046    0.000000  100/100  2024-12-02 21:41:36.468896  2024-12-02 21:41:28.392510

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-12-02 21:41:36.468896  2024-12-02 21:41:28.392510             2        42.40
al_loss    false   2024-12-02 21:41:36.940009  2024-12-02 21:41:28.149700             2        46.12
al_rtt     true    2024-12-02 21:41:40.374486  2024-12-02 21:41:36.066000             3        48.89

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.810391    0.009065    0.000000  100/100  2024-12-02 21:41:40.374486  2024-12-02 21:41:36.066000
A          al_loss    false   0.810391    0.009065    0.000000  100/100  2024-12-02 21:41:36.940009  2024-12-02 21:41:28.149700
A          al_jitter  false   0.810391    0.009065    0.000000  100/100  2024-12-02 21:41:36.468896  2024-12-02 21:41:28.392510

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-12-02 21:41:36.468896  2024-12-02 21:41:28.392510             2        32.32
al_loss    false   2024-12-02 21:41:49.150252  2024-12-02 21:41:44.646642             4        53.18
al_rtt     false   2024-12-02 21:41:48.667389  2024-12-02 21:41:40.374486             4        57.61

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.000547    0.000378    0.000000  100/100  2024-12-02 21:41:48.667389  2024-12-02 21:41:40.374486
A          al_loss    false   0.000547    0.000378    0.000000  100/100  2024-12-02 21:41:49.150252  2024-12-02 21:41:44.646642
A          al_jitter  false   0.000547    0.000378    0.000000  100/100  2024-12-02 21:41:36.468896  2024-12-02 21:41:28.392510

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-12-02 21:41:52.608325  2024-12-02 21:41:36.468896             3        36.20
al_loss    false   2024-12-02 21:41:49.150252  2024-12-02 21:41:44.646642             4        42.40
al_rtt     true    2024-12-02 21:41:55.315338  2024-12-02 21:41:48.667389             5        47.73

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.245283    0.358742    0.000000  100/100  2024-12-02 21:41:55.315338  2024-12-02 21:41:48.667389
A          al_loss    false   0.245283    0.358742    0.000000  100/100  2024-12-02 21:41:49.150252  2024-12-02 21:41:44.646642
A          al_jitter  true    0.245283    0.358742    0.000000  100/100  2024-12-02 21:41:52.608325  2024-12-02 21:41:36.468896

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-12-02 21:42:01.171650  2024-12-02 21:41:52.608325             4        44.52
al_loss    false   2024-12-02 21:41:49.150252  2024-12-02 21:41:44.646642             4        35.56
al_rtt     false   2024-12-02 21:41:59.372889  2024-12-02 21:41:55.315338             6        49.37

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.000371    0.000035    0.000000  100/100  2024-12-02 21:41:59.372889  2024-12-02 21:41:55.315338
A          al_loss    false   0.000371    0.000035    0.000000  100/100  2024-12-02 21:41:49.150252  2024-12-02 21:41:44.646642
A          al_jitter  false   0.000371    0.000035    0.000000  100/100  2024-12-02 21:42:01.171650  2024-12-02 21:41:52.608325

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-12-02 21:42:18.547809  2024-12-02 21:42:13.735952             2        66.74
al_rtt     false   2024-12-02 21:42:18.388163  2024-12-02 21:42:14.481267             2        54.22

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.000318    0.000037    0.000000  100/100  2024-12-02 21:42:18.388163  2024-12-02 21:42:14.481267
A          al_loss    false   0.000318    0.000037    0.000000  100/100  2024-12-02 21:42:18.547809  2024-12-02 21:42:13.735952
A          al_jitter  false   0.000318    0.000037    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-12-02 21:42:22.509468                                         1        24.15
al_loss    true    2024-12-02 21:42:22.164799  2024-12-02 21:42:18.547809             3        62.69
al_rtt     true    2024-12-02 21:42:24.413763  2024-12-02 21:42:18.388163             3        39.14

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.370295    0.379996    37.000000  100/100  2024-12-02 21:42:24.413763  2024-12-02 21:42:18.388163
A          al_loss    true    0.370295    0.379996    37.000000  100/100  2024-12-02 21:42:22.164799  2024-12-02 21:42:18.547809
A          al_jitter  true    0.370295    0.379996    37.000000  100/100  2024-12-02 21:42:22.509468

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-12-02 21:42:30.878389  2024-12-02 21:42:22.509468             2        43.39
al_loss    false   2024-12-02 21:42:31.067315  2024-12-02 21:42:22.164799             4        71.12
al_rtt     false   2024-12-02 21:42:30.015982  2024-12-02 21:42:24.413763             4        49.32

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.000320    0.000043    0.000000  100/100  2024-12-02 21:42:30.015982  2024-12-02 21:42:24.413763
A          al_loss    false   0.000320    0.000043    0.000000  100/100  2024-12-02 21:42:31.067315  2024-12-02 21:42:22.164799
A          al_jitter  false   0.000320    0.000043    0.000000  100/100  2024-12-02 21:42:30.878389  2024-12-02 21:42:22.509468

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-12-02 21:42:30.878389  2024-12-02 21:42:22.509468             2        32.96
al_loss    false   2024-12-02 21:42:31.067315  2024-12-02 21:42:22.164799             4        54.02
al_rtt     true    2024-12-02 21:42:34.584154  2024-12-02 21:42:30.015982             5        49.92

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.792406    0.009148    0.000000  100/100  2024-12-02 21:42:34.584154  2024-12-02 21:42:30.015982
A          al_loss    false   0.792406    0.009148    0.000000  100/100  2024-12-02 21:42:31.067315  2024-12-02 21:42:22.164799
A          al_jitter  false   0.792406    0.009148    0.000000  100/100  2024-12-02 21:42:30.878389  2024-12-02 21:42:22.509468

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-12-02 21:42:30.878389  2024-12-02 21:42:22.509468             2        26.79
al_loss    false   2024-12-02 21:42:43.246631  2024-12-02 21:42:38.727188             6        58.38
al_rtt     false   2024-12-02 21:42:42.736622  2024-12-02 21:42:34.584154             6        56.56

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000457    0.000244    0.000000  100/100  2024-12-02 21:42:42.736622  2024-12-02 21:42:34.584154
A          al_loss    false   0.000457    0.000244    0.000000  100/100  2024-12-02 21:42:43.246631  2024-12-02 21:42:38.727188
A          al_jitter  false   0.000457    0.000244    0.000000  100/100  2024-12-02 21:42:30.878389  2024-12-02 21:42:22.509468

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-12-02 21:42:46.878265  2024-12-02 21:42:30.878389             3        30.11
al_loss    false   2024-12-02 21:42:43.246631  2024-12-02 21:42:38.727188             6        48.73
al_rtt     false   2024-12-02 21:42:42.736622  2024-12-02 21:42:34.584154             6        47.21

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.198437    0.280960    0.000000  100/100  2024-12-02 21:42:42.736622  2024-12-02 21:42:34.584154
A          al_loss    false   0.198437    0.280960    0.000000  100/100  2024-12-02 21:42:43.246631  2024-12-02 21:42:38.727188
A          al_jitter  true    0.198437    0.280960    0.000000  100/100  2024-12-02 21:42:46.878265  2024-12-02 21:42:30.878389

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-12-02 21:42:54.909886  2024-12-02 21:42:46.878265             4        37.82
al_loss    false   2024-12-02 21:42:55.186390  2024-12-02 21:42:51.356303             8        50.88
al_rtt     false   2024-12-02 21:42:52.555034  2024-12-02 21:42:50.231583             8        46.09

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000369    0.000100    0.000000  100/100  2024-12-02 21:42:52.555034  2024-12-02 21:42:50.231583
A          al_loss    false   0.000369    0.000100    0.000000  100/100  2024-12-02 21:42:55.186390  2024-12-02 21:42:51.356303
A          al_jitter  false   0.000369    0.000100    0.000000  100/100  2024-12-02 21:42:54.909886  2024-12-02 21:42:46.878265

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-12-02 21:43:14.021466  2024-12-02 21:43:09.044056             2        68.28
al_rtt     false   2024-12-02 21:43:13.724026  2024-12-02 21:43:09.774769             2        54.22

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.000492    0.000213    0.000000  100/100  2024-12-02 21:43:13.724026  2024-12-02 21:43:09.774769
A          al_loss    false   0.000492    0.000213    0.000000  100/100  2024-12-02 21:43:14.021466  2024-12-02 21:43:09.044056
A          al_jitter  false   0.000492    0.000213    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-12-02 21:43:17.836563                                         1        24.12
al_loss    true    2024-12-02 21:43:17.337462  2024-12-02 21:43:14.021466             3        64.70
al_rtt     true    2024-12-02 21:43:19.139312  2024-12-02 21:43:13.724026             3        43.74

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.390210    0.439869    39.000000  100/100  2024-12-02 21:43:19.139312  2024-12-02 21:43:13.724026
A          al_loss    true    0.390210    0.439869    39.000000  100/100  2024-12-02 21:43:17.337462  2024-12-02 21:43:14.021466
A          al_jitter  true    0.390210    0.439869    39.000000  100/100  2024-12-02 21:43:17.836563

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-12-02 21:43:26.525687  2024-12-02 21:43:17.836563             2        44.40
al_loss    false   2024-12-02 21:43:26.677348  2024-12-02 21:43:17.337462             4        73.12
al_rtt     false   2024-12-02 21:43:25.763488  2024-12-02 21:43:19.139312             4        54.02

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000335    0.000032    0.000000  100/100  2024-12-02 21:43:25.763488  2024-12-02 21:43:19.139312
A          al_loss    false   0.000335    0.000032    0.000000  100/100  2024-12-02 21:43:26.677348  2024-12-02 21:43:17.337462
A          al_jitter  false   0.000335    0.000032    0.000000  100/100  2024-12-02 21:43:26.525687  2024-12-02 21:43:17.836563

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-12-02 21:43:26.525687  2024-12-02 21:43:17.836563             2        33.82
al_loss    false   2024-12-02 21:43:26.677348  2024-12-02 21:43:17.337462             4        55.69
al_rtt     true    2024-12-02 21:43:30.121230  2024-12-02 21:43:25.763488             5        53.53

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.801377    0.009055    0.000000  100/100  2024-12-02 21:43:30.121230  2024-12-02 21:43:25.763488
A          al_loss    false   0.801377    0.009055    0.000000  100/100  2024-12-02 21:43:26.677348  2024-12-02 21:43:17.337462
A          al_jitter  false   0.801377    0.009055    0.000000  100/100  2024-12-02 21:43:26.525687  2024-12-02 21:43:17.836563

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-12-02 21:43:26.525687  2024-12-02 21:43:17.836563             2        27.50
al_loss    false   2024-12-02 21:43:38.847228  2024-12-02 21:43:34.344525             6        59.53
al_rtt     false   2024-12-02 21:43:38.361058  2024-12-02 21:43:30.121230             6        59.53

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.000351    0.000049    0.000000  100/100  2024-12-02 21:43:38.361058  2024-12-02 21:43:30.121230
A          al_loss    false   0.000351    0.000049    0.000000  100/100  2024-12-02 21:43:38.847228  2024-12-02 21:43:34.344525
A          al_jitter  false   0.000351    0.000049    0.000000  100/100  2024-12-02 21:43:26.525687  2024-12-02 21:43:17.836563

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-12-02 21:43:42.232231  2024-12-02 21:43:26.525687             3        31.19
al_loss    false   2024-12-02 21:43:38.847228  2024-12-02 21:43:34.344525             6        49.92
al_rtt     true    2024-12-02 21:43:44.530891  2024-12-02 21:43:38.361058             7        51.95

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.220277    0.317950    0.000000  100/100  2024-12-02 21:43:44.530891  2024-12-02 21:43:38.361058
A          al_loss    false   0.220277    0.317950    0.000000  100/100  2024-12-02 21:43:38.847228  2024-12-02 21:43:34.344525
A          al_jitter  true    0.220277    0.317950    0.000000  100/100  2024-12-02 21:43:42.232231  2024-12-02 21:43:26.525687

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-12-02 21:43:50.639708  2024-12-02 21:43:42.232231             4        39.09
al_loss    false   2024-12-02 21:43:38.847228  2024-12-02 21:43:34.344525             6        43.02
al_rtt     false   2024-12-02 21:43:47.619912  2024-12-02 21:43:44.530891             8        50.08

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000370    0.000182    0.000000  100/100  2024-12-02 21:43:47.619912  2024-12-02 21:43:44.530891
A          al_loss    false   0.000370    0.000182    0.000000  100/100  2024-12-02 21:43:38.847228  2024-12-02 21:43:34.344525
A          al_jitter  false   0.000370    0.000182    0.000000  100/100  2024-12-02 21:43:50.639708  2024-12-02 21:43:42.232231

Note

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