Ops Center

 Analyzer Adapter NOT FOUND - It comes with Analyzer Probe

Jump to  Best Answer
Sudhir BISHT's profile image
Sudhir BISHT posted 08-26-2025 20:29

Hi All & Mr. William.

Going by the excellent guidance provided in this earlier post - https://community.hitachivantara.com/question/ops-center-analyzer-adapter-for-grafana

we went ahead with this setup.

And, as per the documentation by Hitachi:

The Analyzer Adapter already comes with the Analyzer Probe-Server.
The RAID Agent also comes with the Analyzer Probe-Server  -  <= Yes, we already have this working fine.

But, we didn't find 'Adapter'. There is no folder there as mentioned in doc - /opt/hitachi/analyzer_adapter/registerdb.sh

So, we can't register influxdb at all.  So, how to get this analyzer_adapter(supposed to come with intial install). Please advise.

As, we already setup Grafana/Influxdb successfully.

Also, sample dashboards were also not found in either Express Installer and Anayzer Installer ISOs/OVAs that were used for the Ops installs..  How to find them, as the same doc tells that they are there for usage as a sample dashboard. Please advise.

Thanks

William Jansen Van Nieuwenhuizen's profile image
William Jansen Van Nieuwenhuizen  Best Answer

Hello Sudhir :-)

It's important that you login to the Probe not the Ops Center VM. Could you check that you're on the probe via Analyzer Detailed view > status and check the hostnames or IP's listed there. That is where you configure it. Below is for instance my probe, you'll also see the sample reports and the configuration script in there:

[root@oc-probe-emea-dc1 ~]# cd /opt/
hitachi/ jp1pc/   OpsVM/   
[root@oc-probe-emea-dc1 ~]# cd /opt/
hitachi/ jp1pc/   OpsVM/   
[root@oc-probe-emea-dc1 ~]# cd /opt/hitachi/
Analytics/                   HORCM/
analyzer_adapter/            protector/
backup/                      RMLIB/
backup_HORCM/                ubi_backup/
ConfManager/                 VirtualStorageSoftwareAgent/
[root@oc-probe-emea-dc1 ~]# cd /opt/hitachi/analyzer_adapter/
analyzer-adapter.jar  definition/           run.sh
build                 libs/                 sample_reports/
change-etl-config     lock/                 sbin/
config/               registerdb.sh         uninstaller/
[root@oc-probe-emea-dc1 ~]# cd /opt/hitachi/analyzer_adapter/registerdb.sh 
-bash: cd: /opt/hitachi/analyzer_adapter/registerdb.sh: Not a directory
[root@oc-probe-emea-dc1 ~]# cd /opt/hitachi/analyzer_adapter/
[root@oc-probe-emea-dc1 analyzer_adapter]# ./registerdb.sh 
KNAQ60053-I An InfluxDB connection configuration already exists.
Protocol : http
Host     : influxdb-grafana.apps.os.ecoe.io
Port     : 80
Bucket   : analyzer
Token    : *****
Sudhir BISHT's profile image
Sudhir BISHT

Hi William.  Thanks.  

Yes, I am there only. Actually we have all stuff on one server only, except Probe Server, as the requirement at that time was it has to be a separate. So, I am on that only.

[root@XXXXXX hitachi]# pwd
/opt/hitachi
[root@XXXXXX hitachi]# ls
Analytics  backup  backup_HORCM  ConfManager  HORCM  RMLIB  VirtualStorageSoftwareAgent

[root@XXXXXX hitachi]# find / -name analyzer_adapter -print
[root@XXXXXX hitachi]#

[root@XXXXXX hitachi]# /usr/local/megha/bin/megha-jetty.sh status
Megha probe is running

[root@XXXXXX jp1pc]# /opt/jp1pc/htnm/bin/htmsrv status -all
KATR10032-I The specified service is already running. (service = Status Server, serviceid=PT1XXXXXXXXXXXXX)
KATR10032-I The specified service is already running. (service = Action Handler, serviceid=PH1XXXXXXXXXXXXX)
KATR10032-I The specified service is already running. (service = Agent Store, serviceid=DS1E1090_74XXXX[XXXXXXXXXXXXX])
KATR10032-I The specified service is already running. (service = Agent Store, serviceid=DS174XXXX[XXXXXXXXXXXXX])
KATR10032-I The specified service is already running. (service = Agent Store, serviceid=DS144XXXX[XXXXXXXXXXXXX])
KATR10032-I The specified service is already running. (service = Agent Collector, serviceid=DA1E1090_74XXXX[XXXXXXXXXXXXX])
KATR10032-I The specified service is already running. (service = Agent Collector, serviceid=DA174XXXX[XXXXXXXXXXXXX])
KATR10032-I The specified service is already running. (service = Agent Collector, serviceid=DA144XXXX[XXXXXXXXXXXXX])
KATR10032-I The specified service is already running. (service = Agent REST Application Service)
KATR10032-I The specified service is already running. (service = Agent REST Web Service)

[root@XXXXX tools]# ./jpctdchkinst -inst 74XXXX

KAVF18814-I The instance is configured not to use a TCP/IP connection to collect performance data.
KAVF18815-I No error was found during verification of the collection of performance data by using a command device.
KAVF18830-I No error was found during verification of the collection of performance data over a REST-API connection.
[Monitored storage system information]
PRODUCT  : VSP E1090

Nothing there.  Is there a way to now install it on top, without breaking anything.

Thanks

William Jansen Van Nieuwenhuizen's profile image
William Jansen Van Nieuwenhuizen

Hello

No theres not since the Detailed view services and the probe services uses similar ports etc. Youll have to deploy a probe server and configure it on there.  

With VSP 360 (went GA today) this might be different since the probes run as containers all on the same server but it doesnt yet have all the finctionaily of Ops Center today. I havent tested yet if I can configure it on VSP 360. 

Sudhir BISHT's profile image
Sudhir BISHT

Hi William.  Thanks.

I don't agree. We've a separate Probe Server already configured and working fine.  Al the services are running fine in it, and it can Probe well. We get all performance data in Analyzer and Detailed View as well.  This was configured by HDS tech and he did configured it properly with all components. There is nothing to configure more there. There can't be two Probe Servers. Not needed.  Also, the point on VSP 360 has nothing to do with this.

Also, in the manual this statement seem incorrect as well , as I mounted the two ISOs media and searched in them (Not found):

Sample dashboard location in the Analyzer Installer and Express installer:
root-directory-of-the-installation-media
/DCAPROBE/ADAPTER/SAMPLE_REPORTS/sample.json

Also, I see this with the installer run. So, shall I go for just upgrade/repair one more time, and Adapter arrives ?

 Thanks

William Jansen Van Nieuwenhuizen's profile image
William Jansen Van Nieuwenhuizen

Sorry, I miss understood I thought you wanted to configure this on the ops center VM. Can you send a screenshot of your probe status and version?

Sudhir BISHT's profile image
Sudhir BISHT

Hi William.  Thanks.  Let me clear it a bit more.

We've One VM(lets call it Ops Center VM as you say) -  It has 5 things - Analyzer Detail/Analyzer/Automator/API Conf Mgr and Common Services.

We' also have a separate VM (Analyzer Probe Server) - This has RAID Agent, API Conf Mgr/Analyzer Prober. But somehow Analyzer Adapter is missing, or was not installed by HDS tech at that time. So, I want to check on this, and how to install it and from which ISO media (I've them all mounted).

I think we need to find that 'Analyzer Adapter' component in those media ISOs, and then install it. Not sure.

Thanks.

William Jansen Van Nieuwenhuizen's profile image
William Jansen Van Nieuwenhuizen

Hello

No install, its just on the probe. 

What version are you running of the probe if you go to https://<probe ip>:8443?

Sudhir BISHT's profile image
Sudhir BISHT

Hi.

William Jansen Van Nieuwenhuizen's profile image
William Jansen Van Nieuwenhuizen

Yes, I'm not sure which version it got introducted but 11.0.2 is quite old. Upgrade the probe and try again for reference i'm running 11.0.5 but I think I configured the adapter in 11.0.4 already. 

Sudhir BISHT's profile image
Sudhir BISHT

Hi Bill. Thanks.

I think that was it. Much appreciated. When I upgraded to version 11-04-01, I started seeing those missing folders. So, I also imported 'sample.json' to see and went ahead with other steps. 

# /opt/hitachi/analyzer_adapter/registerdb.sh
KNAQ60053-I An InfluxDB connection configuration already exists.
Protocol : http
Host     : 10.X.X.XX
Port     : 8086
Bucket   : REPOSITORY
Token    : *****
Do you want to update it? (y/n): y
Enter your InfluxDB connection protocol (http/https) [http]:
Enter your InfluxDB host [10.X.X.XX]:
Enter your InfluxDB port [8086]:
Enter your InfluxDB bucket name [REPOSITORY]:
Enter your InfluxDB token [*****]:
Verifying the connection to InfluxDB... OK.
KNAQ60047-I Successfully connected to InfluxDB, but the token includes read permission. As a best practice, the token should only have write permission for the bucket.
Do you want to save the InfluxDB connection configuration? (y/n): y
KNAQ60051-I The InfluxDB connection configuration saved successfully.

However, there is no data in 'Grafana'.   It should show something. Right.  How it looks like at your end , when you see in your lab. 

Thanks

Sudhir BISHT's profile image
Sudhir BISHT

Hi William. Thanks again.  

Could you please check in your setup what port is configured for RAID Agent in influxdb.  Due to some reasons mine looks for Port 24222.  But actually it is 24221 on my Hitachi Probe Server.

[root@ABMDEBPANA01V ~]# /opt/hitachi/analyzer_adapter/run.sh --startTime 202508281012 --endTime 202508281200
KNAQ60003-I ETL for RAID Agent started. (RAID Agent url:"https://localhost:24222/")
KNAQ60001-I ETL for Agent instance started. (RAID Agent url:"https://localhost:24222/", Agent instance name:"E1090_7X5XXX")
KNAQ60012-E An error occurred communicating with the RAID Agent. (RAID Agent url:"https://localhost:24222/", Agent instance name:"E1090_7X5XXX", cause:"Connect to localhost:24222 [localhost/127.0.0.1] failed: Connection refused") Check the network and RAID Agent status and try again. If the same error occurs, use the data collection tool to collect the necessary data, and then contact your customer support.

Thanks

Sudhir BISHT's profile image
Sudhir BISHT

Hi All.

Hi All.  There is a file named user.properties ,  under analyzer adapter folder.  Changed the agent access port to 24221, and Agent instance started and connected successfully.   
 
KNAQ60003-I ETL for RAID Agent started. (RAID Agent url:"http://localhost:24221/")
KNAQ60001-I ETL for Agent instance started. (RAID Agent url:"http://localhost:24221/", Agent instance name:"E1090_7XXXXX")
KNAQ60002-I ETL for Agent instance ended successfully. (RAID Agent url:"http://localhost:24221/", Agent instance name:"E1090_7XXXXX")
 
Soon, performance data was seen on Grafana dashboard.  All good.
Thanks.