3

Platform Configuration

Last Update 2 months ago

SMTP Configuration SSL Certificate Configuration Network Configuration

Network Configuration

Dinesh

Last Update 2 months ago

Overview 

The On-Prem Management Console allows administrators to update the network configuration of the SecOps Central Server.
The platform supports two network configuration modes:

  • Static IP (Recommended) - Manually configure the server's network settings.
  • Dynamic IP (DHCP) - Automatically obtain network settings from a DHCP server.

For production deployments, SecOps Solution strongly recommends using a Static IP address to ensure consistent platform access, agent communication, and integration reliability.

Before You Begin 

Before modifying the Central Server network settings, review the following guide:
Central Server Network Configuration Guide
This guide covers network planning, DNS considerations, routing requirements, and deployment best practices.

Access Network Configuration 

Step 1: Open the On-Prem Management Console 

Open:

Step 2: Open Network Configuration 

From the left navigation menu, select:

Static IP Configuration 

Static IP mode allows administrators to manually define the network settings of the Central Server.
  • Select Static IP from the Network Mode dropdown.
  • Enter the required network settings:
    • IP Address
    • Subnet Mask
    • Gateway
    • Primary DNS Server
    • Secondary DNS Server
  • Click Configure to apply the changes.
A Static IP is recommended for production deployments because it provides predictable access to the platform and ensures reliable communication with agents and integrations.

DHCP Configuration 

DHCP mode allows the Central Server to automatically obtain network settings from a DHCP server.

  • Select Dynamic (DHCP) from the Network Mode dropdown.
  • Review the displayed warning.
  • Configure the DNS servers if required.
  • Click Configure to apply the changes.


Using DHCP may result in IP address changes after a reboot. This can impact platform access, agent communication, integrations, and Jump Host connectivity.
For environments that require DHCP, consider using a DHCP reservation to ensure the server receives the same IP address consistently.

Important Considerations 

If the IP Address Changes 

After applying a new IP address:

  • The SecOps Platform URL will change.
  • The On-Prem Management Console URL will change.
  • Existing bookmarks and integrations may need to be updated.

Example:

Verify Connectivity 

After applying the configuration:

  • Verify the server is reachable on the configured IP address.
  • Confirm access to:
    • SecOps Platform (:58443)
    • On-Prem Management Console (:49431)
  • Verify internet connectivity.
  • Confirm agents can communicate with the Central Server.

Product Unreachable After IP Address Change 

If the product becomes unreachable after updating the network configuration, verify whether the newly assigned IP address is reachable from your current network.
This commonly occurs when a static IP address is configured and the device is later moved to a different network or VLAN.

Step 1: Verify Connectivity 

  1. Check the IP address currently assigned to the machine.
  2. Confirm that the IP address is reachable from the network where the Central Server is deployed.
  3. If the configured IP address is not reachable, you may need to manually update the network configuration on the affected machine.

Step 2: Configure DHCP 

Connect to the machine directly (via console, or SSH if accessible) and navigate to the Netplan configuration directory:

Example:

View the existing configuration file:
Update the network configuration to use DHCP by ensuring the network interface contains:
Note: The network interface name (for example, ens33) may differ in your environment. Keep the existing interface name and only ensure that dhcp4: true is configured.
If a static IP configuration is present, remove the static address, gateway, and nameserver entries, and enable DHCP as shown above.

Step 3: Apply the Configuration 

After saving the file, apply the changes:
Once DHCP is enabled, the machine will obtain an IP address from the current network and should become reachable again from the Central Server.

Important 

For roaming devices or systems that are moved between different networks, DHCP is strongly recommended. Using a static IP address and then changing networks can result in the product becoming unreachable from the Central Server until the network configuration is manually corrected.

If you are planning network changes for a production deployment, refer to the Central Server Network Configuration Guide before applying the configuration

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us