Highlighted
Absent Member.. Oscar_Pereira Absent Member..
Absent Member..
193 views

(PPM) Support Tip: Key information to add in a Support case when having Multicast Error in ServerLog

1-Always include the kSupport output for each machine part of the cluster.

2-Review sever.conf, make sure the required multicast parameters are there and properly set according the Installation and Administration Guide.

For example:

com.kintana.core.server.MULTICAST_IP 

com.kintana.core.server.MULTICAST_PORT

com.kintana.core.server.MULTICAST_CLUSTER_NAME

 

3-Make sure that MULTICAST_IP and MULTICAST_CLUSTER_NAME are unique among PPM environments (Production, test, QA)

4-Ask Network team to confirm that Multicast is enable in the server NIC and associated VLANs

Multicast protocol must be enabled on the network components, i.e. NIC/HUB/Bridge/Router/etc.

 

5-Check ip configuration in each machine and its routing table. Provide screenshots of this.

 

Windows: 

route print | grep 224

Ipconfig /all


Redhat: 

/sbin/route | grep 224

ifconfig

6-If the Server has several NICs, you may need to bind the IP address with the parameter MULTICAST_NIC_IP.

 

If the MULTICAST_NIC_IP parameter is specified in the server.conf file, the JGroup and MULTICAST Channel multicast sockets will bind to the NIC that you specified by using the MULTICAST_NIC_IP parameter. The value of the MULTICAST_NIC_IP parameter can be a host name or an IP address.

7-Enable multicast debug in PPM_HOME/conf/logging.conf file

 com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL=com.kintana.core.server.cluster.ClusterMonitor, DEBUG

com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL=org.jboss.ha.framework.server.DistributedReplicantManagerImpl.{REPLACE IT WITH YOUR CLUSTER NAME},INFO

 com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL=com.kintana.core.server.cluster.MulticastAgent,DEBUG

com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL=com.kintana.core.server.cluster.MulticastCommsFailureMonitor,DEBUG

 com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL=com.mercury.itg.core.monitor.impl.ServerManagerImpl,DEBUG

 

8-In addition to these, the SYSTEM_THRESHOLD setting in logging.conf should also be set to DEBUG. Get the serverLog.txt attached to the support case, the debug settings can be disabled simply by setting the value ERROR again.

9-Perform a jgroup test to verify that the cluster machines are able to communicate

 A) open command window in one of the machines

run "export CLASSPATH=/ ppm_home /server/kintana/deploy/itg.war/WEB-INF/lib/jgroups-2.6.15.GA.jar"

(if the path is not right, please correct it as your path)

    run "java org.jgroups.tests.McastSenderTest -mcast_addr 225.39.39.244 -port 9101"

B) open a command window in the other Machine

 run "export CLASSPATH=/ppm_home/server/kintana/deploy/itg.war/WEB-INF/lib/jgroups-2.6.15.GA.jar"

 ( if the path is not right, please correct it as your path)

 run "java org.jgroups.tests.McastReceiverTest -mcast_addr 225.39.39.244 -port 9101"

 

10-OPTIONAL only when using a VLAN setup:

 Confirm if ip pim sparse-mode is enabled in the VLAN? 

https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01526989

 

 

Thanks,

Oscar

Labels (1)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.