7022970: Configuring VHI to use separate network interfaces for management and session server communication

Before making any changes, it is recommended systems bebacked up.

Below are instructions for configuration changes to servers to force which interface VHI will use forcommunication.

If a cluster is not being used then the parts about breaking and creating a cluster can be skipped.

1.Remove the servers from the Management Clusterand make sure they are completely separated.

2.Remove the Load Distribution Domain and thesecond session server from the Host Integrator.

3.Add the session server that was removed, backinto its Host Integrator Session Server installation via the AdministrativeConsole.

4.Steps 5 through 27 need to be done on bothservers.

5.Open the “Verastream Administrative Console” oneither server.

6.Select the menu item “Perspective/HostIntegrator/Session Servers”

7.Right click on the server name under“Installation/Servers” and select “Properties”

8.Change the “Address:” to the IP address of thelocal production interface. On host “TestServer1” you would change theentry to “Address:192.168.1.1” and on host “TestServer2” would be“Address:192.168.1.2”.

9.Select “OK” and close the “VerastreamAdministrative Console”.

10.Stop the “Verastream Host Integrator SessionServer” and “Verastream Management Server” services on both servers.

11.Open the file “sesssrvr.config” which is bydefault located at “C:Program FilesAttachmateVerastreamHostIntegratoretc”in a text editor.

12.At the top of the file, change the “Server”entry to the fully qualified server name. For example: “testserver1.company.com”

13.Save the file and close it.

14.Open the file “container.properties” located bydefault in “C:Program FilesAttachmateVerastreamManagementServerconf” in atext editor.

15.On the first line append the IP address of thelocal production interface you want to use to the “host=” entry. On host“TestServer1” you would change the entry to “host=192.168.1.1” and “TestServer2”would be “host=1192.16.1.2”.

16.Save the file and close it.

17.Open the file “container.properties” located bydefault in “C:ProgramFilesAttachmateVerastreamHostIntegratorsesssrvrconf” in a text editor.

18.On the first line append the IP address of thelocal production interface you want to use to the “host=” entry. On host“TestServer1” you would change the entry to “host=192.168.1.1” and“TestServer2” would be “host=1192.16.1.2”.

19.Save the file and close it.

20.Open the file “container.conf” located bydefault in “C:Program FilesAttachmateVerastreamManagementServerconf” in atext editor.

21.Add the following line after the entry “wrapper.java.additional.5=-Duser.country=US”. On host “TestServer1” you would change the entry to“-Djava.rmi.server.hostname=192.168.1.1” and “TestServer2” it would be“-Djava.rmi.server.hostname=192.168.1.2”

wrapper.java.additional.6=-Djava.rmi.server.hostname=172.168.xxx.xxx

22.Save the file and close it.

23.Open the file “sesssrvr.conf” located by defaultin “C:Program FilesAttachmateVerastreamHostIntegratoretc” in a texteditor.

24.Add the following line after the entry“scriptmgr.java.additional.6=-Dcom.attachmate.integration.container.BSAFE.SSL-J.enabled=false”. On host “TestServer1” you would change the entry to “-Djava.rmi.server.hostname=192.168.1.1”and “TestServer2” it would be “-Djava.rmi.server.hostname=192.168.1.1”

scriptmgr.java.additional.7=-Djava.rmi.server.hostname=192.168.xxx.xxx

25.Save the file and close it.

26.Start the “Verastream Host Integrator SessionServer” and “Verastream Management Server” services on both servers.

27.Verify the Management Server and Host IntegratorSever are working. (i.e. Try deploying a model to the session server, execute aweb service procedure, confirm no new errors in the logs, etc)

28.Please recreate your Load Distribution Domainand Management Cluster

Related:

7022556: Setting Primary for Stacked DRBD Backup Node Causes Server Crash

There is no fix yet for the issue, but a work-around is available.

This configuration syntax is known to trigger the issue (specifically in the r0-U resource section):-

resource r0 {

disk {

on-io-error pass_on;

}

net {

protocol C;

}

connection-mesh {

hosts sles12sp3s1 sles12sp3s2;

}

on sles12sp3s1 {

address 192.200.2.34:7788; # address of sles12sp3s1

device /dev/drbd0 ;

disk /dev/sdb;

meta-disk internal;

node-id 0;

}

on sles12sp3s2 {

address 192.200.2.35:7788; # address of sles12sp3s2

device /dev/drbd0 ;

disk /dev/sdb;

meta-disk internal;

node-id 1;

}

}

resource r0-U {

disk {

on-io-error pass_on;

}

net {

protocol A;

}

stacked-on-top-of r0 {

address 192.200.3.34:7790; # address of drbd0 clustered resource

device /dev/drbd10;

}

on sles12sp3s3 {

device /dev/drbd10;

disk /dev/sdc;

address 192.200.3.36:7790; # address of sles12sp3s3

meta-disk internal;

}

}


By reorganizing the syntax in the ‘upper’ resource section, it is possible to avoid the issue:-

<snip>

resource r0-U {

disk drbd0;

protocol A;

device /dev/drbd10;

meta-disk internal;

stacked-on-top-of r0 {

address 192.200.3.34:7790; # address of drbd0 clustered resource

}

on sles12sp3s3 {

disk /dev/sdc;

address 192.200.3.36:7790; # address of sles12sp3s3

}

}

</snip>

Related:

Couldn’t build the Address Book hierarchy table. Will try to rebuild the hierarchy table again in %1 minutes.

Details
Product: Windows Operating System
Event ID: 1161
Source: Active Directory
Version: 5.0
Symbolic Name: DIRLOG_BUILD_HIERARCHY_TABLE_FAILED
Message: Couldn’t build the Address Book hierarchy table. Will try to rebuild the hierarchy table again in %1 minutes.
   
Explanation

Active Directory could not build the Address Book hierarchy table. The next attempt will occur after the specified time has elapsed. Address Book searches will be disabled on this domain controller during this interval. Attempts to build the Address Book hierarchy table will continue until the task is completed.

   
User Action

No user action is required.

Related: