Manjunath_J Super Contributor.
Super Contributor.
1066 views

Physical server collector issue

HI Experts,

I have succesfully installed CO 3.02. After installation i have applied the temporary license for 60 days.

Now iam going to deploy the one physical server package collector. I have successfully deployed that package in to the one physical machine and the sensor service also up and running.

But iam not able to see any collection status or any alerts in the collection and analysis tab.

Kindly help me how to proceed further to see the collection status of that physical machine in CO UI.

Is there any configuration is missing please help me resolve the issue. Attachment for sensor service status reference.

Regards,

Pranav R N

0 Likes
8 Replies
Manjunath_J Super Contributor.
Super Contributor.

Re: Physical server collector issue

Hi Experts,

Kindly help me out of this issue.

Regards,

Pranav R N

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Physical server collector issue

Hello Pranav R N,

I apologize for the delay in responding.

There are a number of factors that come into play when using the Physical Server collector.  The Physical Server collector includes 'Compute Sensor' similar to the Guest OS Drill-down for Guest VMs.

Do you have Operations Agent (OA) installed on this same physical server?  If you do, that could cause some problems with communication.

You can stop/kill the Compute Sensor process and restart it to see if anything changes.  There is also the ability to enable debug level logging for both the client and server side of things.

The client will have the hpcs.conf file (/var/opt/OV/hpcs or C:\Program Files\HP\HP BTO Software\hpcs) where you can add the entry similar to the following:
[hpcs.trace]
Debug_Level=ALL

It will be necessary to stop and restart the process for the changes to take effect.

Stopping and restarting client process:

  • Find hpsensor process ID.
  • Run "kill -15 <hpsensor-pid>" where <hpsensor-pid> is the process ID or End Task/Process.
  • To run as a daemon:
           ./hpsensor -srs

The server will have the hpcsrv.conf file (/var/opt/OV/shared/server/hpcsrv) where you can add the entry similar to the following:
[hpcs.trace]
Debug_Level=ALL

Again, it will be necessary to stop and restart the server service for the changes to take effect.

To stop and restart the server service on the CO server.

  • # /opt/OV/bin/ovc -stop hpcsrvd
  • # /opt/OV/bin/ovc -start hpcsrvd

The traces will be within the hpcstrace.log file and hpcsrvtrace.log files respectively.

I hope that this information is helpful.

Regards,

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.softwaregrp.com/
Tags (2)
0 Likes
Manjunath_J Super Contributor.
Super Contributor.

Re: Physical server collector issue

Hi Mark,

Thanks for the information.

Earlier OA agent is running on the physical machine, i have stopped the OA agent. But still there is no data in the CO console.

Also kindly let me know after installing the compute sensor in the physical machine is there any configuration we have to perform from the physical server end to fetch the data in to the CO.

Also let me know what is the JSON file and i'm able to open http://localhost:381 this url from the physical server.

Attached log for your reference.

Regards,

Pranav R N

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Physical server collector issue

Hello Pranav R N,

Unfortunately, the Physical Collector and OA are incompatible.  Stopping the OA is not enough.  You would need to remove the Physical Collector, Remove OA and then reinstall the Physical Collector.

The challenge is that OA uses certicificates and BBC to communicate (LCore).  The Physical Collector also uses BBC (LCore) but not certificates.  This causes a conflict so that the Physical Collector is unable to communicate through BBC.  Without being able to communicate through BBC, it will not work.

I hope that this information is helpful.

Regards,

Mark

 

 

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.softwaregrp.com/
0 Likes
Manjunath_J Super Contributor.
Super Contributor.

Re: Physical server collector issue

Hi Mark,

Thanks for yor reply.

Also kindly let me know if any configurations we have to perform after installting the physical server collector.

Regards,

Pranav R N

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Physical server collector issue

Hello Pranav R N,

Ideally, no.  However, if there is configuration, then it would need to be done within the hpcs.conf file.  This file is located within the %HPCSInstallDir% (Windows) or /opt/OV/hpcs (Linux) directories.

Confirm that the port (Ex. 381) and the hpcs.subscribers entry has the CO server listed.

I hope that this helps.

Regards,

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.softwaregrp.com/
0 Likes
Manjunath_J Super Contributor.
Super Contributor.

Re: Physical server collector issue

Hi Mark,

Still the issue is not yet resolved.

Iam bit confusing on the configuration part. I have attached the hpcs conf file kindly check and let me know where i need to change the hostname and ip in that configuration file. it would be helpfull to me.

Awaiting responce from your side.

Regards,

Pranav R N

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Physical server collector issue

Hello Pranav R N,

Based on the hpcs.conf file that you provided, I can see the following information.

[hpcs.runtime]
port=381
...
collection_Interval=300

[hpcs.trace]
; Debug_Level=INFO

[hpcs.subscribers]
...

http://10.1.1.248:8081/syspulse/HPCSListener=/Metrics/All

This tells me that the collection cycle is every 5 minutes (300 seconds), debug level is not turned on and your CO server should have IP address of 10.1.1.248.

Please be sure that firewalls are not blocking things.

You can check with a browser to see if you can access the json file from your Physical Server.

Ex.

On Physical Server:
http://localhost:381/

On remote server:
http://<FQDN of Physical Server>:381/

If both of those options work properly and you are able to receive (save) the JSON file, then the issue may be with the configuration of the HPCSRV on your CO server.

The log and configuration items are located within the /var/opt/OV/shared/server/hpcsrv directory.

I would suggest adding looking at this data and if problems continue, open a support case.

Regards,

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.softwaregrp.com/
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.