Help needed on moving manual cert from BSM to Sitescope and ovconf file parameters setting.

I have an existing Sitescope which is connected to a BSM which is working fine. For some reason i need to move all this Sitescope and integrate it to a new BSM server. I tried to request the ceritificated and it did not work. My GW and DPS are sitting on the same box.

Therefore i decided to create and import the new cert from the new BSM which is not working. Steps is what i have done as below:-

On the new BSM server

=================

ovcert -exporttrusted -file  bsm.cert

ovcm -issue -file sitescope.cert -name <sitescope_server_FQDN> -coreid <coreid>

Both files above were created well. Then i copied them into Sitescope server and did the following steps below:-

ovcert -importtrusted -file bsm.cert

ovcert -importcert -file sitescope.cert

Both were imported properly as below:-

C:\>ovcert -list
---------------------------------------------------------
| Keystore Content                                        |
---------------------------------------------------------
| Certificates:                                           |
|     ef4027b2-f2c6-758b-1c9b-eb0904d4cc92 (*)            |
---------------------------------------------------------
| Trusted Certificates:                                   |
|     CA_e4db4f62-f84e-758b-17f3-cd45551d907a_2048        |
---------------------------------------------------------

 

But when i do a HP Operations Manager integration on Sitescope, im getting error like below:-

Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

opcactivate Info: OVO activation script starting ...
opcactivate Info: Check whether trusted certificate exists
opcactivate Info: Trusted certificate exists; Use -f option to change the configuration
opcactivate Warning: Not registering opcauth.dll. Passwordless switch-user operations for OVO actions will not be possible.
opcactivate Info: Not disabling remote trace access.
opcactivate Info: Setting required licenses.
opcactivate Info: Starting agent processes.
opcactivate Info: opcactivate ended successfully.


Executing command: C:\Program Files\HP\HP BTO Software\bin\win64\ovcoreid
ef4027b2-f2c6-758b-1c9b-eb0904d4cc92

Note: BSM users should run a BSM server command: ovcm -grant <request id>. In order to retrieve your <request id>, Run ovcm -listpending -l and find the <request id> that matches your agent core id ef4027b2-f2c6-758b-1c9b-eb0904d4cc92


Executing command: C:\Program Files\HP\HP BTO Software\bin\win64\ovconfget sec.core.auth MANAGER_ID
e4db4f62-f84e-758b-17f3-cd45551d907a


Executing command: "C:\Program Files\HP\HP BTO Software\bin\win64\opcagt.bat" -status

dsisrv        (DSI service)                                  (2932)   Running
midaemon      (measurement interface)                        (1572)   Running
misrv         (measurement interface service)                (1544)   Running
perfalarm     (Alarm generator)                              (5680)   Running
perfalarmsrv  (Alarm generator service)                      (6588)   Running
scopent       (data collector)                               (9884)   Running
scopesrv      (collector service)                            (9868)   Running
perfd         (Real Time Metric Access Daemon)               (6844)   Running
perfdsrv      (Real Time Metric Access Service)              (9932)   Running
ttd           (transaction tracking)                         (2240)   Running
ttsrv         (transaction tracking service)                 (2192)   Running
Mwecsrv       (extended collection service)                  (5996)   Running
coda          OV Performance Core               COREXT       (2564)   Running
opcacta       OVO Action Agent                  AGENT,EA     (6140)   Running
opcmsga       OVO Message Agent                 AGENT,EA     (2920)   Running
ovbbccb       OV Communication Broker           CORE         (9536)   Running
ovcd          OV Control                        CORE         (5020)   Running
ovconfd       OV Config and Deploy              COREXT       (9532)   Running

 

Im on Sitescope 11.32 with HPO 11.15.019 Agent. Can someone help me on this issue please. Appreciate your feedback.

I also changed some of the paramaterson on the ovconfchg like sec.cm.client,sec.core,sec.core.auth.

Previous BSM was using proxy and i had some parameter on bbc.http and the new BSM is sitting on the same network, just without any proxy, is there something i need to change on the bbc.http ?

 

 

 

Parents
  • When i do a analyse - error message below

    (bbc-288) status=eServiceError coreID= bbcV= appN= appV=
                    conn=0 time=16 ms

     

    But i can ping manually from the sitescope machine to the new BSM

  • All,

        I have made some progress now, im already getting

    status=eServiceOK coreID=1ca016c2-9abb-758b-0a48-d5ca34f248d5
                    bbcV=11.15.019 appN=ovbbccb appV=11.15.019 conn=2 time=188 ms --- sounds good

     

    But only some cert issue now as below, pls help me

    opcactivate Info: OVO activation script starting ...
    opcactivate Info: Check whether trusted certificate exists
    opcactivate Info: Trusted certificate exists; Use -f option to change the configuration
    opcactivate Warning: Not registering opcauth.dll. Passwordless switch-user operations for OVO actions will not be possible.
    opcactivate Info: Not disabling remote trace access.
    opcactivate Info: Setting required licenses.
    opcactivate Info: Starting agent processes.
    opcactivate Info: opcactivate ended successfully.

    dsisrv        (DSI service)                                  (1288)   Running
    midaemon      (measurement interface)                        (1580)   Running
    misrv         (measurement interface service)                (1560)   Running
    perfalarm     (Alarm generator)                              (5248)   Running
    perfalarmsrv  (Alarm generator service)                      (5160)   Running
    scopent       (data collector)                               (2476)   Running
    scopesrv      (collector service)                            (2348)   Running
    perfd         (Real Time Metric Access Daemon)               (1792)   Running
    perfdsrv      (Real Time Metric Access Service)              (1744)   Running
    ttd           (transaction tracking)                         (2236)   Running
    ttsrv         (transaction tracking service)                 (2164)   Running
    Mwecsrv       (extended collection service)                  (1628)   Running
    agtrep        OV Discovery Agent                AGENT,AgtRep (5800)   Running
    coda          OV Performance Core               COREXT                Stopping
    opcacta       OVO Action Agent                  AGENT,EA     (5964)   Running
    opcle         OVO Logfile Encapsulator          AGENT,EA     (5344)   Running
    opcmsga       OVO Message Agent                 AGENT,EA     (3744)   Running
    opcmsgi       OVO Message Interceptor           AGENT,EA     (3148)   Running
    ovbbccb       OV Communication Broker           CORE         (1756)   Running
    ovcd          OV Control                        CORE         (2228)   Running

     

    C:\Windows\System32>ovcert -list
    ---------------------------------------------------------
    | Keystore Content                                        |
    ---------------------------------------------------------
    | Certificates:                                           |
    |     4f883442-0899-758c-1d68-a047c961b2b3 (*)            |
    ---------------------------------------------------------
    | Trusted Certificates:                                   |
    |     CA_e4db4f62-f84e-758b-17f3-cd45551d907a_2048        |
    ---------------------------------------------------------

  • Would i get the cert error if i was running the BSM on port 80 (http) ?

  • The port on which you run BSM web server (like port 80) has nothing to do with certificates used for BBC datacomm which use port 383 by default.

    Anyway, you can keep enjoing your troubleshooting exercise if you like, but if I needed to move SiteScope from BSM1 to BSM2, I would simply delete the existing integration settings (configured for BSM1) from SiteScope > Integration Preferences, and re-create them from scratch for BSM2. All from UI (BSM Integration settings - handling metrics and topology - from BSM SAM; OM integration settings - handling events - from SiteScope itself), no exporttrusted/importtrusted and similar fancy stuff that only complicates everything.

Reply
  • The port on which you run BSM web server (like port 80) has nothing to do with certificates used for BBC datacomm which use port 383 by default.

    Anyway, you can keep enjoing your troubleshooting exercise if you like, but if I needed to move SiteScope from BSM1 to BSM2, I would simply delete the existing integration settings (configured for BSM1) from SiteScope > Integration Preferences, and re-create them from scratch for BSM2. All from UI (BSM Integration settings - handling metrics and topology - from BSM SAM; OM integration settings - handling events - from SiteScope itself), no exporttrusted/importtrusted and similar fancy stuff that only complicates everything.

Children
No Data