Highlighted
Regular Contributor.. MVCabrera Regular Contributor..
Regular Contributor..
258 views

Debugging a GRE Setup.

Hello.

I'm trying to setup a granular recovery system for our VM backups.

CM and Proxy system are ver.10.40.

GRE plugin installed in a vcenter 6.7, registered on the CM.

CM and Proxy resolve to the vcenter succesfully.

Attaching relevant virgo.log. Any ideas are welcomed.

Spoiler
[2019-10-09T16:02:59.539Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.GREDataService [sendAgentRequest] Calling DPCOM function MonitorRequests;repeatCount=2;this=com.hp.dp.gre.GREDataService@50ee3003
[2019-10-09T16:02:59.540Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.agentcomm.socket.SocketAgentImpl [startAgent] [<ProxySystemIP>]: param2: <ProxySystemIP>
[2019-10-09T16:02:59.540Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.agentcomm.socket.SocketAgentImpl [startAgent] [<ProxySystemIP>]: Socket Added number:0
[2019-10-09T16:02:59.540Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.agentcomm.socket.SocketAgentImpl [startAgent] [<ProxySystemIP>]: Starting vmwaregre agent process...
[2019-10-09T16:02:59.540Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.agentcomm.socket.SocketAgentImpl [startAgent] [<ProxySystemIP>]: thread: agentClient.start;
[2019-10-09T16:02:59.541Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [run] Starting vmwaregre agent process
[2019-10-09T16:02:59.541Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [remoteStartAgentEx] vcenter hostname: VCENTERfqdn.domain
[2019-10-09T16:02:59.541Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [remoteStartAgentEx] targetHostname: <ProxySystemIP>
[2019-10-09T16:02:59.542Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [remoteStartAgentEx] Body string: {"module":"GRE","sourceHostName":"VCENTERfqdn.domain","remoteHostName":"<ProxySystemIP>","cm":"CMfqdn.domain","userName":"Administrator","userGroup":"Administrators"}
[2019-10-09T16:02:59.542Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [remoteStartAgentEx] DP Rest End Point: https://CMfqdn.domain:7116/dp-config-server/restws/agentconnect
[2019-10-09T16:02:59.542Z] [INFO ] Thread-75 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.domain:7116/dp-config-server/restws/agentconnect
[2019-10-09T16:02:59.696Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [remoteStartAgentEx] Successfully started requested agent on target system: <ProxySystemIP>
[2019-10-09T16:02:59.696Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [remoteStartAgentEx] Response data: {"returnCode":"0","column":["port=117916,inetPort=5565"]}
[2019-10-09T16:02:59.696Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [getRunningAgentPort] Agent port: 117916
[2019-10-09T16:02:59.696Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [getRunningAgentPort] Inet port: 5565
[2019-10-09T16:02:59.697Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [connectoToAgent] cellMgrHost: CMfqdn.domain, targetHost: <ProxySystemIP>, vCenter: VCENTERfqdn.domain
[2019-10-09T16:02:59.697Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [connectoToAgent] Connecting to Inet...
[2019-10-09T16:02:59.697Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [connectoToAgent] InetHostname: <ProxySystemIP>
[2019-10-09T16:02:59.697Z] [INFO ] Thread-75 com.hp.im.dp.server.ipc.msg.InetClient Inet socket info: Socket[addr=/<ProxySystemIP>,port=5565,localport=59518]
[2019-10-09T16:02:59.698Z] [INFO ] Thread-75 com.hp.im.dp.server.ipc.msg.InetClient Inet socket info: Socket[addr=/<ProxySystemIP>,port=5565,localport=59518]
[2019-10-09T16:02:59.698Z] [INFO ] Thread-75 com.hp.im.dp.server.ipc.msg.InetClient Inet socket info: Socket[addr=/<ProxySystemIP>,port=5565,localport=59518]
[2019-10-09T16:02:59.698Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [connectoToAgent] Clnt.getSocket(): <ProxySystemIP>
[2019-10-09T16:02:59.698Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [connectoToAgent] connected to inet service
[2019-10-09T16:02:59.698Z] [INFO ] Thread-75 com.hp.im.dp.server.ipc.msg.InetClient Inet socket info: Socket[addr=/<ProxySystemIP>,port=5565,localport=59518]
[2019-10-09T16:02:59.698Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [connectoToAgent] establishing secure protocol handshake with agent...
[2019-10-09T16:02:59.699Z] [ERROR] Thread-75 com.hp.dp.gre.CertificateManager [isCertValid] Certificate is VALID
[2019-10-09T16:02:59.699Z] [INFO ] Thread-75 com.hp.dp.gre.CertificateManager [genX509CertAndUploadThumbPrint] Certificate exist for the host: VCENTERfqdn.domain , and also valid!. Hence not generating new one!
[2019-10-09T16:02:59.699Z] [INFO ] Thread-75 com.hp.dp.gre.jbossquery.JbossQuery [getThumbPrintFromCM] DP Rest End Point: https://CMfqdn.domain:7116/dp-config-server/restws/certmgr/gethosttp/VCENTERfqdn.domain
[2019-10-09T16:02:59.699Z] [INFO ] Thread-75 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.domain:7116/dp-config-server/restws/certmgr/gethosttp/VCENTERfqdn.domain
[2019-10-09T16:02:59.798Z] [INFO ] Thread-75 com.hp.dp.gre.CertificateManager [genX509CertAndUploadThumbPrint] Certificate match ( latest & one stored at cell manager), hence uploading of latest certificate to cell manager is not performed.
[2019-10-09T16:02:59.799Z] [INFO ] Thread-75 com.hp.im.dp.server.ipc.msg.InetClient Inet socket info: Socket[addr=/<ProxySystemIP>,port=5565,localport=59518]
[2019-10-09T16:02:59.799Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.SecureSocketGenerator [upgradeSocketToSSL] vCenter: VCENTERfqdn.domain autoCloseSSLSocket: false
[2019-10-09T16:02:59.799Z] [INFO ] Thread-75 com.hp.dp.gre.CertificateManager [getKeyMgrFactory] vCenterName: VCENTERfqdn.domain
[2019-10-09T16:02:59.799Z] [INFO ] Thread-75 com.hp.dp.gre.CertificateManager [getTrustManager] vCenterName: VCENTERfqdn.domain
[2019-10-09T16:02:59.886Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.SecureSocketGenerator [upgradeSocketToSSL] Handshaking process is completed successfully!
[2019-10-09T16:02:59.886Z] [INFO ] Thread-75 com.hp.dp.gre.jbossquery.JbossQuery [getThumbPrintFromCM] DP Rest End Point: https://CMfqdn.domain:7116/dp-config-server/restws/certmgr/gethosttp/<ProxySystemIP>
[2019-10-09T16:02:59.887Z] [INFO ] Thread-75 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.domain:7116/dp-config-server/restws/certmgr/gethosttp/<ProxySystemIP>
[2019-10-09T16:02:59.980Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [doSecureConnection] Sending MSG_PROTOCOL with pass socket data info: 0 {pass.mode=1;pass.port=52380;}
[2019-10-09T16:02:59.980Z] [INFO ] Thread-75 com.hp.im.dp.server.ipc.msg.MsgBase [getMsgBody] MsgBody: 267^@ 10^@ 100^@ 900^@ 10^@ VMwareGreWebPlugin^@ 0 {pass.mode=1;pass.port=52380;}^@^@
[2019-10-09T16:02:59.981Z] [INFO ] Thread-75 com.hp.im.dp.server.ipc.msg.InetClient Inet socket info: Socket[addr=/<ProxySystemIP>,port=5565,localport=59518]
[2019-10-09T16:03:00.019Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [doSecureConnection] got MSG_PROTOCOL response: 5 {pid=14989;time=132151106223429280;guid='8d0a1031-34e6-4200-b0a4-73cd6e85457a';pass.mode=5;}
[2019-10-09T16:03:00.019Z] [INFO ] Thread-75 com.hp.im.dp.server.ipc.msg.InetClient Inet socket info: Socket[addr=/<ProxySystemIP>,port=5565,localport=59518]
[2019-10-09T16:03:00.019Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.SecureSocketGenerator [upgradeSocketToSSL] vCenter: VCENTERfqdn.domain autoCloseSSLSocket: true
[2019-10-09T16:03:00.019Z] [INFO ] Thread-75 com.hp.dp.gre.CertificateManager [getKeyMgrFactory] vCenterName: VCENTERfqdn.domain
[2019-10-09T16:03:00.019Z] [INFO ] Thread-75 com.hp.dp.gre.CertificateManager [getTrustManager] vCenterName: VCENTERfqdn.domain
[2019-10-09T16:03:00.114Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.SecureSocketGenerator [upgradeSocketToSSL] Handshaking process is completed successfully!
[2019-10-09T16:03:00.114Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [doSecureConnection] Connected successfully to agent => ip: <ProxySystemIP>, port: 5565
[2019-10-09T16:03:00.114Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [connectoToAgent] established secure protocol handshake with agent successfully!
[2019-10-09T16:03:00.114Z] [INFO ] Thread-75 com.hp.dp.gre.agentcomm.socket.client.AgentSocketClient [run] we started the agent
[2019-10-09T16:03:00.114Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.GREDataService [sendAgentRequest] Calling DPCOM function DPComConfig;repeatCount=2;this=com.hp.dp.gre.GREDataService@145fb837
[2019-10-09T16:03:00.115Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.GREDataService Found socket <ProxySystemIP>:5565 => :59518 [0/1]
[2019-10-09T16:03:00.118Z] [INFO ] http-nio-9090-exec-15 com.hp.im.dp.server.ipc.msg.MsgBase [getMsgBody] MsgBody: 6666^@ DPComConfig^@ {"timeout":"600"}^@^@
[2019-10-09T16:03:00.118Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.GREDataService [sendAgentRequest] Prepare response message.
[2019-10-09T16:03:00.158Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.agentcomm.socket.SocketAgentImpl callGRE agent returned from DPComConfig method 0
[2019-10-09T16:03:00.159Z] [INFO ] http-nio-9090-exec-15 com.hp.im.dp.server.ipc.msg.MsgBase [getMsgBody] MsgBody: 6666^@ MonitorRequests^@ {"user":"VSPHERE\\ADMINISTRATOR","vspheresessionid":"31b2d4ed-a0b1-4c3b-b53c-e8c16e149685","vmref":"VirtualMachine:vm-1218","debugging":1,"vsphereSDKHost":"VCENTERip"}^@^@
[2019-10-09T16:03:00.159Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.GREDataService [sendAgentRequest] Prepare response message.
[2019-10-09T16:03:00.269Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.restlayer.services.MonitorRequestServiceImpl callGRE agent returned from MonitorRequests2 {
"status":"Error",
"message":"Log on to Virtual Center VCENTERip could not be performed.",
"details":"Connection information missing. Check that VMware vCenter host has been imported to Data Protector cell."
}
0 Likes
10 Replies
Micro Focus Expert
Micro Focus Expert

Re: Debugging a GRE Setup.

Hello @MVCabrera

What is the build version of vCenter? Please confirm. 

Also, the log shows this at the end: 

[2019-10-09T16:03:00.269Z] [INFO ] http-nio-9090-exec-15 com.hp.dp.gre.restlayer.services.MonitorRequestServiceImpl callGRE agent returned from MonitorRequests2 {
"status":"Error",
"message":"Log on to Virtual Center VCENTERip could not be performed.",
"details":"Connection information missing. Check that VMware vCenter host has been imported to Data Protector cell."
}

Is the user VSPHERE\\ADMINISTRATOR added in DP in the corresponding group as documented?
https://docs.microfocus.com/itom/Data_Protector:2019.05/VMWareGREConfiguration#Adding

Also, I assume that should be correct, the vCenter is added in DP correctly as vCenter. 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
Regular Contributor.. MVCabrera Regular Contributor..
Regular Contributor..

Re: Debugging a GRE Setup.

Hi @Victor_F_DP  , thanks a lot for your prompt response!

What is the build version of vCenter? Please confirm. 

vSphere Client version 6.7.0.30000. I do realize it was outside of the support matrix last time I checked, but I keep my hopes that in the end it will work.

Also, I assume that should be correct, the vCenter is added in DP correctly as vCenter. 

It is added as a vCenter, correct.

Is the user VSPHERE\\ADMINISTRATOR added in DP in the corresponding group as documented?
https://docs.microfocus.com/itom/Data_Protector:2019.05/VMWareGREConfiguration#Adding

That one I missed, gonna try that next. Thanks again!

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Debugging a GRE Setup.

If I am not wrong, that version is 6.7 U2, this is actually supported in DP 10.40: 

https://docs.microfocus.com/DP/SupportMatrix/10.40/Virtualization_Support_Matrix_DP10.x.pdf

Try the steps for the users and let us know. 

Regards, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
Knowledge Partner
Knowledge Partner

Re: Debugging a GRE Setup.

Hello @MVCabrera,

I bet the user VSPHERE\\ADMINISTRATOR does not even exist. The name of the default user is administrator@vsphere.local. Try this one (or a user that can actually login to vCenter) in Data Protector Clients context on the vCenter client properties. Is the VMware backup image backup working at all? You should test this first.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
Regular Contributor.. MVCabrera Regular Contributor..
Regular Contributor..

Re: Debugging a GRE Setup.

Thanks so much for chiming in too, @Sebastian.Koehler 


@Sebastian.Koehler wrote:

Hello @MVCabrera,

I bet the user VSPHERE\\ADMINISTRATOR does not even exist.

I don't understand this. But to be fair, the docs are kind of hard to understand in the whole users creation for the GRE system. There is not a VSPHERE\\ADMINISTRATOR user that I know of nor did I create it.

The name of the default user is administrator@vsphere.local. Try this one (or a user that can actually login to vCenter) in Data Protector Clients context on the vCenter client properties.

This was actually my first try and got me this far. Now I created a GREuser (greuser|gre|vcenterfqdn, along with a matching greuser@vsphere.local), following the docs as closely as I could, they are not very clear, and I think we got closer to the goal.

Is the VMware backup image backup working at all? You should test this first.

I tested it successfully before, both back up and restore.

This is where we are now:

Spoiler
[2019-10-10T15:41:08.867Z] [INFO ] SsoTokenRenewalExecutor-692 ######## 100126 200022 com.vmware.vise.vim.security.sso.impl.SsoUtilInternal Renewing token _c227768e-9b29-428d-a177-2808debbdea9 using https://VSPHEREip/sts/STSService/vsphere.local
[2019-10-10T15:41:08.939Z] [INFO ] SsoTokenRenewalExecutor-692 ######## 100126 200022 com.vmware.vim.sso.client.impl.SiteAffinityServiceDiscovery Site affinity is disabled
[2019-10-10T15:41:09.156Z] [INFO ] SsoTokenRenewalExecutor-692 ######## 100126 200022 com.vmware.identity.token.impl.SamlTokenImpl SAML token for SubjectNameId [value=GREuser@VSPHERE.LOCAL, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element
[2019-10-10T15:41:09.158Z] [INFO ] SsoTokenRenewalExecutor-692 ######## 100126 200022 com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl Successfully renewed token for user: {Name: GREuser, Domain: VSPHERE.LOCAL}
[2019-10-10T15:41:09.158Z] [INFO ] SsoTokenRenewalExecutor-692 ######## 100126 200022 com.vmware.vsphere.client.security.sso.SsoTokenLifetimeManager Token renewed for sessionId 100126, clientId 200022. Token expiration time: Sat Nov 09 15:41:08 UTC 2019
[2019-10-10T15:41:09.159Z] [INFO ] SsoTokenRenewalExecutor-692 ######## 100126 200022 com.vmware.vsphere.client.security.sso.SsoTokenLifetimeManager sessionId 100126, clientId 200022, Token expiration time: Sat Nov 09 15:41:08 UTC 2019
Token renewal scheduled approximately for: Sat Nov 09 15:36:08 UTC 2019
[2019-10-10T15:42:31.073Z] [INFO ] http-nio-9090-exec-16 70003425 100096 200022 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.
[2019-10-10T15:42:33.697Z] [INFO ] http-nio-9090-exec-11 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.CMdomain:7116/auth/realms/DataProtector/protocol/openid-connect/token
[2019-10-10T15:42:33.892Z] [INFO ] http-nio-9090-exec-17 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.CMdomain:7116/dp-gui/GetMountProxies?newMachineTypeParam=MountProxy
[2019-10-10T15:42:33.933Z] [INFO ] http-nio-9090-exec-17 com.hp.dp.gre.configuration.HPDPConfig [updateEntry] cellMgrHost: CMfqdn.CMdomain
[2019-10-10T15:42:33.935Z] [ERROR] http-nio-9090-exec-17 com.hp.dp.gre.configuration.HPDPConfig [updateEntry] Caught 'java.net.UnknownHostException' exception while convertion from hostname to ip!
[2019-10-10T15:42:33.936Z] [ERROR] http-nio-9090-exec-17 com.hp.dp.gre.restlayer.mvc.ServicesController java.lang.Exception: Failed to check older client entries in the non-selected cell managers.
[2019-10-10T15:42:33.937Z] [WARN ] http-nio-9090-exec-17 o.s.w.s.mvc.method.annotation.ExceptionHandlerExceptionResolver Resolved [java.lang.Exception: Failed to check older client entries in the non-selected cell managers.] to ModelAndView: materialized View is [null]; model is {message=Failed to check older client entries in the non-selected cell managers.}

The first part is about renewing a token. I managed to get into the Keycloak Admin console and was looking to emulate the token exchange and catch a glimpse at the responses for the GetMountProxies call. No success there.

The "exception while convertion from hostname to ip" looks like a name resolution issue (we can't use DNS here, everything is on /etc/hosts files, and different networks, to add insult to the injury). I found this error before and don't know how I solved it.

But the one that puzzles me the most is the final one: "Failed to check older client entries in the non-selected cell managers."

No idea where to start for that one.

Thanks for all the help so far!

0 Likes
Knowledge Partner
Knowledge Partner

Re: Debugging a GRE Setup.

Hello @MVCabrera,

The problem is, that this documentation section describes the old and the new GRE agent and a few terms sound quite similar. This should help.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Regular Contributor.. MVCabrera Regular Contributor..
Regular Contributor..

Re: Debugging a GRE Setup.


@Sebastian.Koehler wrote:
Is the VMware image backup working in general?

Yes. It was before I started this thread.

Have you backed up at least one VM?

Yes. Same as before.

Is the Data Protector GRE tab visible in the vCenter (Flash client) on the VM that has been backed up?

Yes.

Follow Add an Inet user account to the Data Protector Admin group on https://docs.microfocus.com/itom/Data_Protector:2019.08/VMWareGREConfiguration#Configure_a_GRE_for_VMware_vSphere_user_group_and_users

Working on that.

On the Data Protector GRE tab you need to login with a Data Protector web user. See https://docs.microfocus.com/itom/Data_Protector:2019.08/ResettingUserPassword for details.

Already realized that.

Thanks a lot!

0 Likes
Knowledge Partner
Knowledge Partner

Re: Debugging a GRE Setup.

Hello @MVCabrera,

Please keep us posted on your progress.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Regular Contributor.. MVCabrera Regular Contributor..
Regular Contributor..

Re: Debugging a GRE Setup.

Well, we are definitely closer, but not quite there yet. @Sebastian.Koehler @Victor_F_DP 

I log on to the vsphere flash client and in the GRE tab I select my CM, add log in info, select the proxy and fail with: "Mount proxy host is not reachable".

Virgo.log extract:

Spoiler
[2019-10-15T15:44:28.347Z] [INFO ] http-nio-9090-exec-5 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.domain:7116/dp-nextgen/js/json/resources/branding.json
[2019-10-15T15:44:28.412Z] [INFO ] data-service-pool-796 70001155 100036 200007 com.hp.dp.gre.agentcomm.socket.SocketAgentImpl [convertProperty] start
[2019-10-15T15:44:28.412Z] [INFO ] data-service-pool-796 70001155 100036 200007 com.hp.dp.gre.agentcomm.socket.SocketAgentImpl [getCurrentProperty] end
[2019-10-15T15:44:31.332Z] [INFO ] http-nio-9090-exec-9 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.domain:7116/auth/realms/DataProtector/protocol/openid-connect/token
[2019-10-15T15:44:31.515Z] [INFO ] http-nio-9090-exec-2 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.domain:7116/dp-gui/GetMountProxies?newMachineTypeParam=MountProxy
[2019-10-15T15:44:31.551Z] [INFO ] http-nio-9090-exec-2 com.hp.dp.gre.configuration.HPDPConfig [updateEntry] cellMgrHost: CMfqdn.domain
[2019-10-15T15:44:31.552Z] [INFO ] Thread-89 com.hp.dp.gre.util.CleanUpUtil Last run time is less than the time interval, so no clean up required.
[2019-10-15T15:44:44.096Z] [INFO ] http-nio-9090-exec-3 com.hp.dp.gre.GREDataService [sendAgentRequest] Calling DPCOM function MonitorRequests;repeatCount=2;this=com.hp.dp.gre.GREDataService@629b2f57
[2019-10-15T15:44:44.096Z] [INFO ] http-nio-9090-exec-3 com.hp.dp.gre.GREDataService Found socket 10.1.107.10:5565 => :40020 [1/2]
[2019-10-15T15:44:44.096Z] [INFO ] http-nio-9090-exec-3 com.hp.im.dp.server.ipc.msg.MsgBase [getMsgBody] MsgBody: 6666 MonitorRequests {"user":"VSPHERE\\ADMINISTRATOR","vspheresessionid":"e1b6e84e-2126-4433-a9ca-b16699c1e40f","vmref":"VirtualMachine:vm-1218","debugging":1,"vsphereSDKHost":"VCENTERIP"}
[2019-10-15T15:44:44.096Z] [INFO ] http-nio-9090-exec-3 com.hp.dp.gre.GREDataService [sendAgentRequest] Prepare response message.
[2019-10-15T15:44:44.097Z] [INFO ] http-nio-9090-exec-10 com.hp.dp.gre.rest.SecureRestCall [excuteQueryService] service url: https://CMfqdn.domain:7116/dp-gui/GetMountProxies?newMachineTypeParam=ESX
[2019-10-15T15:44:44.140Z] [INFO ] http-nio-9090-exec-3 com.hp.dp.gre.restlayer.services.MonitorRequestServiceImpl callGRE agent returned from MonitorRequests2 {
"status":"Error",
"message":"Log on to Virtual Center VCENTERIP could not be performed.",
"details":"Connection information missing. Check that VMware vCenter host has been imported to Data Protector cell."

Finally the VSPHERE\\ADMINISTRATOR user has come up and in need.

Following is the current configuration and how we did to get this far. I suspect I got something wrong and maybe you can point it out:

We log in to the vsphere client as administrator@vsphere.local.

I created a user root|root|proxyhost on DP, in the admin group, with a matching password as the one on the proxyhost.

Also, I created a vsphere\\administrator|nt authority|vcenterfqdn on DP, admin group. Again, matching password but with the vsphere this time.

And lastly:  administrator@vsphere.local|nt authority|vcenterfqdn on DP, admin group, matching password.

I created a GRE group with a greuser|gre|vcenterfqdn on DP. The group has the start restore user right.

Win GUI system is not any of the CM nor the proxy host used. It may not be resolving the vcenter (I feel it should not be a problem, is it?)

0 Likes
Regular Contributor.. MVCabrera Regular Contributor..
Regular Contributor..

Re: Debugging a GRE Setup.

Any more tips, @Sebastian.Koehler , @Victor_F_DP ?

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.