How to Disable a Node in NeoLoad: Step-by-Step Configuration Guide

Managing performance tests can feel like juggling flaming torches. Especially when you are working with multiple load generators in NeoLoad. Sometimes you need to take one node out of the action. Maybe it is overloaded. Maybe it needs maintenance. Or maybe you just want to test a new setup. Whatever the reason, knowing how to disable a node in NeoLoad is an essential skill. The good news? It is easier than you think.

TLDR: Disabling a node in NeoLoad helps you control your load testing environment without deleting configurations. Go to the Load Generators panel, select the node you want to disable, and either disconnect or deactivate it depending on your goal. This keeps your tests flexible and clean. Always verify your changes before running a new test.

Let’s break it down step by step. Simple. Clear. No headaches.

What Is a Node in NeoLoad?

Before we start clicking buttons, let’s understand what we are touching.

In NeoLoad, a node is also called a Load Generator. It is the machine that simulates virtual users. It creates traffic. It puts pressure on your system. It acts like hundreds or thousands of real users.

You can have:

• Local nodes – installed on your own machine.
• Remote nodes – installed on other servers.
• Cloud nodes – provided via cloud platforms.

If one of these nodes is not needed, unstable, or under maintenance, you may want to disable it temporarily.

Why Disable a Node Instead of Deleting It?

Great question.

Deleting removes the configuration completely. That can be risky. You may lose custom settings. You may forget server details. You may regret it later.

Disabling, on the other hand:

• Keeps your configuration safe.
• Lets you reactivate it anytime.
• Helps with troubleshooting.
• Makes test control easier.

Think of it like muting a microphone instead of smashing it.

Step-by-Step: How to Disable a Node in NeoLoad

Now let’s get practical.

Step 1: Open NeoLoad

Launch NeoLoad as you normally would. Wait for your project to load fully.

Make sure you have access to the project where the node is configured.

Step 2: Go to the Load Generators Panel

On the left-hand menu, find:

• Infrastructure
• Then click Load Generators

This area shows all configured nodes.

You will see important information like:

• Hostname
• Status (Connected or Disconnected)
• IP address
• Type (Local, Remote, Cloud)

Step 3: Identify the Node You Want to Disable

Take a moment here.

Make sure you select the correct node. Especially in big environments.

Look at:

• Server name
• Environment tag
• Capacity limits

Double-checking saves drama later.

Step 4: Disconnect the Node

Right-click on the selected node.

Choose:

• Disconnect

If the node is running, NeoLoad will stop communication with it.

The status should change to Disconnected.

That effectively disables it for upcoming test runs.

Step 5: Adjust Scenario Settings (Optional but Smart)

If your test scenario was using that node, you may need to adjust load distribution.

Go to:

• Scenarios
• Select your active test
• Review load generator allocation

Make sure the remaining nodes can handle the virtual users.

This prevents overload.

Alternative Method: Remove from Active Scenario Only

Sometimes you do not want to disconnect the node entirely.

You only want it excluded from one test.

Here is how:

Step 1: Open Your Scenario

Navigate to Run → Scenarios.

Step 2: Manage Load Generators

In the scenario settings, locate the load generator assignment section.

Step 3: Unassign the Node

Simply remove or deselect the node from the scenario allocation list.

This way:

• The node remains configured.
• It stays connected.
• It just does not execute this test.

Clean. Controlled. Reversible.

How to Verify the Node Is Truly Disabled

You do not want surprises.

Always confirm.

Checklist:

• Status shows Disconnected in Infrastructure.
• Node is not assigned in the test scenario.
• No virtual users are distributed to it.
• No live metrics coming from that server.

If all these are true, your node is officially off duty.

Common Issues and Quick Fixes

Sometimes things do not go smoothly. Here are common hiccups.

Problem 1: Node Reconnects Automatically

This may happen if:

• Auto-connect settings are enabled.
• The agent service is running continuously.

Fix:

• Stop the NeoLoad Load Generator service on the remote machine.
• Or disable auto-connect in settings.

Problem 2: Scenario Still Sending Traffic

You disconnected the node. Yet traffic continues.

That means other nodes are active.

Fix:

• Review scenario distribution carefully.

Problem 3: Cannot Disconnect

If right-click → Disconnect does not work:

• Check your user permissions.
• Confirm network connectivity.
• Restart NeoLoad Controller.

Best Practices When Disabling Nodes

Here are smart habits to adopt.

• Document changes. Always log why you disabled a node.
• Check capacity. Ensure remaining nodes handle the load.
• Monitor performance. Watch CPU and memory.
• Re-test configuration. Run a small validation test.

Small steps prevent big testing failures.

When Should You Disable a Node?

There are many valid reasons.

• Server maintenance.
• Hardware problems.
• Network instability.
• Cloud cost control.
• Testing new infrastructure.

For example:

If a remote server shows high CPU usage during a test, disable it temporarily. Investigate the issue. Then bring it back stronger.

Deleting vs Disabling: Quick Comparison

In most real-world situations, disable first. Delete only if you are 100% sure.

How to Re-Enable a Disabled Node

Good news. Turning it back on is easy.

Step 1: Go to Infrastructure → Load Generators

Step 2: Right-Click the Node

Step 3: Select Connect

Wait for the status to change to Connected.

Then reassign it to your scenario if needed.

And just like that, it is back in action.

Final Thoughts

Disabling a node in NeoLoad is not complicated. It is a simple but powerful control feature. Whether you are troubleshooting, saving cloud costs, or managing test load, knowing how to disconnect a load generator gives you flexibility.

Remember these golden rules:

• Disable instead of delete when possible.
• Always review scenario distribution.
• Validate before running full-scale tests.

Performance testing is all about control. Small changes matter. A single active node can shape your test results. So manage them wisely.

Now you know exactly how to disable a node in NeoLoad. Go ahead. Take control of your test environment. And test smarter.