Deployment

Question

During deployment by scanning barcodes using the CloudCampus APP, iMaster NCE-Campus verifies the validity of the client IP address for security purposes. In such cases, administrators may be forcibly logged out. To solve this problem, you can disable client IP address verification if a firewall is deployed outside the iMaster NCE-Campus cluster and DDoS attack defense is configured. How do I disable client IP address verification?

Answer

1. Log in to all controller nodes.

   1. Use PuTTY to log in to a collector node as the sopuser user in SSH mode.

   2. Run the following command to switch to the root user:
   > su - root

   Password: Password for the root user

2. Run the following command to find the nodes where ERService is deployed:

   # cd /opt/oss/manager/var/envs/Product-ERService

   Determine the nodes where ERService is deployed based on the command output. In a controller cluster, ERService is deployed on two controller nodes. If the preceding directory is found on a node and can be accessed, ERService is deployed on this node.

3. Open and modify the ERService.properties file on the two nodes where the ERService directory exists.

   # cd /opt/oss/manager/var/envs/Product-ERService/Timestamp/envs

   Timestamp indicates the name of the timestamp folder. If there are multiple timestamp folders, go to the latest timestamp folder.

   # vi ERService.properties

   Press i and add CHECK_SESSION_IP=false in the last line. Press Esc and enter :wq to save the modification and exit.

   Run the following command to check whether the operation is successful:

   # cat ERService.properties

4. On the nodes where the ERService service is deployed, run the following command to restart the ERService service. During the restart, the northbound service plane will be unavailable for about 1 minute.

   # su - ossadm -c "bash /opt/oss/manager/agent/bin/ipmc_adm -cmd restartapp -app ERService" 

   On the primary ERService node, both the messages indicating that the service is stopped successfully and indicating that the service is started successfully are displayed.

   On the secondary ERService node, only the message indicating that the service is stopped successfully is displayed.