Skip to main content

Windows Network Latency

Windows Network Latency causes a network packet delay on Windows VMs for the target hosts by causing network packet delay using Clumsy. It checks the performance of the application running on the Windows VMs.

tip

When Clumsy is downloaded, the path is exported, that is used while executing the experiment.

Windows Network Latency

Use cases

  • Determines the resilience of an application when a network delay scenario is simulated on a Windows virtual machine.
  • Simulates the situation of network delay for dependent processes and microservices running on the application, which degrades their performance.
  • Helps verify the application's ability to handle network failures and its failover mechanisms.

Prerequisites

  • Ensure that the prerequisites are fulfilled before executing the experiment.
  • Verify that Clumsy is installed on the Windows VM.

Mandatory tunables

Tunable Description Notes
NETWORK_LATENCY The network latency (or delay) that you want to introduce during chaos, in milliseconds. For example, 2000. For more information, go to network latency.
DESTINATION_HOSTS DNS or FQDN names of services whose access is affected. You can specify multiple inputs as comma-separated values. DESTINATION_HOSTS and DESTINATION_IPS are mutually exclusive, which means you can specify one of the values at a given time. For example, "abc.com,github.com". For more information, go to destination hosts.
DESTINATION_IPS IP addresses of target destination services. You can specify multiple inputs as comma-separated values. DESTINATION_HOSTS and DESTINATION_IPS are mutually exclusive, which means you can specify one of the values at a given time. For example, '0.8.0.8,192.168.5.6'. For more information, go to destination IPS.

Optional tunables

Tunable Description Notes
DURATION Duration that you specify, through which chaos is injected into the target resource (in seconds). Default: 60s. For more information, go to duration of the chaos.
RAMP_TIME Period to wait before and after injecting chaos (in seconds). For example, 30s. For more information, go to ramp time.

Network latency

The NETWORK_LATENCY environment variable specifies the amount of delay to induce (in ms).

Use the following example to specify network latency:

apiVersion: litmuschaos.io/v1alpha1
kind: MachineChaosExperiment
metadata:
name: windows-network-latency
spec:
engineState: "active"
chaosServiceAccount: litmus-admin
experiments:
infraType: windows
steps:
- - name: windows-network-latency
tasks:
- definition:
chaos:
env:
- name: NETWORK_LATENCY
value: "2000"

Destination hosts

The DESTINATION_HOSTS environment variable specifies the destination hosts to induce latency on the target Windows VM. You can specify multiple inputs as comma-separated values. DESTINATION_HOSTS and DESTINATION_IPS environment variables are mutually exclusive. Use the following example to specify destination hosts:

apiVersion: litmuschaos.io/v1alpha1
kind: MachineChaosExperiment
metadata:
name: windows-network-latency
spec:
engineState: "active"
chaosServiceAccount: litmus-admin
experiments:
infraType: windows
steps:
- - name: windows-network-latency
tasks:
- definition:
chaos:
env:
- name: DESTINATION_HOSTS
value: "aws.amazon.com,github.com"

Destination IPS

The DESTINATION_IPS environment variable specifies the IP addresses of target destination services. You can specify multiple inputs as comma-separated values. DESTINATION_IPS and DESTINATION_HOSTS environment variables are mutually exclusive.

Use the following example to specify destination IPS:

apiVersion: litmuschaos.io/v1alpha1
kind: MachineChaosExperiment
metadata:
name: windows-network-latency
spec:
engineState: "active"
chaosServiceAccount: litmus-admin
experiments:
infraType: windows
steps:
- - name: windows-network-latency
tasks:
- definition:
chaos:
env:
- name: DESTINATION_IPS
value: '0.8.0.8,192.168.5.6'