How to Modify the Hostname or IP Address of a Symantec Critical System Protection (SCSP) Management Server and/or Database Server
search cancel

How to Modify the Hostname or IP Address of a Symantec Critical System Protection (SCSP) Management Server and/or Database Server

book

Article ID: 151826

calendar_today

Updated On:

Products

Critical System Protection Data Center Security Server Data Center Security Server Advanced

Issue/Introduction

You want to modify the Hostname or IP Address of a Symantec Critical System Protection (SCSP) Management Server and/or Database Server.    

You want to modify the Hostname or IP Address of a Data Center Security Management Server(DCS) and/or Database Server.    


Symptoms

Conditions
During the installation of the Management Server, the Database Server may have been specified by either its Hostname or IP Address. Similarly, during the installation of the Agent, the Management Server may have been specified by either its Hostname or IP Address. If only the IP Address of the particular SCSP \DCS component is being changed and the Hostname remains the same, it is unlikely that any reconfiguration will be necessary so long as the Hostname was specified during installation and that Hostname now resolves to the new IP Address in the Domain Name System (DNS) server.

If you are unsure whether Hostnames or IP Addresses were used during installation, the steps within this document will allow you to verify this.


 

Cause

  • The Hostname or IP Address of the server running your SCSP  \DCS Microsoft SQL Server Database has changed.

 

  • The Hostname or IP Address of your SCSP \DCS Management Server has changed.

 

Resolution

 

If the Database Server Hostname or IP Address has changed, inspect the Database Server address on the SCSP Management Server as follows:

 

  1. In the Services snap-in (On the Windows Start Menu, click Start > Run, type Services.msc and click OK), stop all Symantec Critical System Protection  \DCS services on the Management Server.
  2. Open the file c:\Program Files\Symantec\Critical System Protection\Server\tomcat\conf\server.xml in Notepad.
  3. On the Edit menu, click Find and search for URL -- you will find 2 occurrences and both need to be checked.
    • If the url= string contains a Hostname that properly resolves to the new database server IP via your DNS server, no change is necessary and you may proceed to step 4.
    • If the Database Server Hostname has changed and the URL= string contains the old Hostname, update it to reflect the new Hostname of the Database Server.
    • If the url= string contains an IP address, modify each URL= string to reflect the new IP address for the database server.
  4. Re-start all Symantec Critical System Protection services on the Management Server.

 

The agent config tool is located in the following directories on an agent computer: Sisipsconfig Tool reference Guide: https://knowledge.broadcom.com/external/article/151857/command-line-options-for-the-the-sisipsc.html 

Windows agents named sisipsconfig.exe

  • Located (for SCSP) in: C:\Program Files\Symantec\Critical System Protection\agent\ips\bin
  • Located (for SDCS) in: C:\Program Files (x86)\Symantec\Data Center Security Server\Agent\IPS\bin

UNIX agents named sisipsconfig.sh ​(You will need to su to sisips to run this tool on *nix su - sisips -c "./opt/Symantec/sdcss/IPS/sisipsconfig.sh)

  • Located (for SCSP) in: opt/Symantec/scspagent/IPS
  • Located (for SDCS) in: opt/Symantec/sdcssagent/IPS

If the Management Server Hostname or IP Address has changed, inspect the Management Server host value on each SCSP Agent as follows:

  • If the Agent is on Windows:
    1. Open a command window on the Agent server (On the Windows Start Menu, click Start > Run, type cmd and click OK)
    2. Run cd c:\Program Files\Symantec\Critical System Protection\Agent\IPS\bin
    3. Run sisipsconfig -v
      • If the Host field contains a Hostname that properly resolves in DNS to the new Management Server IP Address, no change is necessary (the agent will connect on its own) and you may proceed to the next agent.
      • If the Management Server Hostname has changed and the Host string contains the old Hostname, run sisipsconfig -h <new_Management_Server_Hostname> to point the Agent to the new Management Server Hostname.
      • If the Host field contains an IP address for the Management Server, run sisipsconfig -h <new_Management_Server_IP> to point the Agent to the new Management Server IP Address.
  • If the Agent is on UNIX or Linux:
    1. Open a console or Secure Shell (SSH) session on the Agent server as the root user.
    2. Run su - sisips
    3. Run cd /opt/Symantec/scspagent/IPS/bin
    4. Run ./sisipsconfigtool -v
      • If the Server Host List field contains a Hostname that properly resolves in DNS to the new Management Server IP Address, no change is necessary (the agent will connect on its own) and you may proceed to the next agent.
      • If the Management Server Hostname has changed and the Server Host List string contains the old Hostname, run ./sisipsconfigtool -h <new_Management_Server_Hostname> to point the Agent to the new Management Server Hostname.
      • If the Server Host List field contains an IP address for the Management Server, run ./sisipsconfigtool -h <new_Management_Server_IP> to point the Agent to the new Management Server IP Address.
      • Test and validate the connection to the new DCS \ SCSP Management Server by running the command ./sisipsconfig -t(test)

 

Powered by Wolken Software