book
Article ID: 312668
calendar_today
Updated On:
Issue/Introduction
Symptoms:
1. When the SRM certificate expires, the plugin can automatically unregister itself from vCenter.
2. Option to reconfigure is no longer available in SRM VAMI, instead you will see Configure (Just like a new install)
3. You won’t be able to register the appliance to vCenter
4. You won’t find any log traces of SRM unregistered in the drconfigui.log / dr.log
Launching SRM from vCenter displays the messages :
ERROR
Server for guid '28dc11f4-a6e4-4b60-83a9-c5bc2aa58d8d' not found, but pair server(s) exist: [PairSetupImpl {
_server = SrmServerImpl {
_guid = 1bac4759-1880-4da5-9a62-7cae158647d0
_url = https://10.X.X.X:443/drserver/vcdr/vmomi/sdk
}
_pairServerGuid = 28dc11f4-a6e4-4b60-83a9-c5bc2aa58d8d
_pairLsppUrl = https://vcenter.prod.local:443/lookupservice/sdk
_pairLsppsThumbprint = 18:96:CF:51:5B:B0:D9:B9:4A:60:19:A3:FB:5E:7C:2A:5D:FE:22:00
}]
Operation ID: 7093d2c9-156d-418b-a6c2-51774d57e91e
8/14/20, 5:15:30 PM +0200
ERROR
Unable to retrieve Site Recovery Manager summary data.
Server with UUID '28dc11f4-a6e4-4b60-83a9-c5bc2aa58d8d' not found.
Operation ID: 3e83de0f-e037-4a69-955a-6c2a03923ef3
8/14/20, 5:15:30 PM +0200
2020-08-14 14:22:21,713 [srm-reactive-thread-4] WARN com.vmware.dr.configservice.taskMonitor.ConfigureTaskHandler 847dcbd6-6d30-4fb4-9e7d-b91cc5d889c6 getConfigureTaskProgress - Task finished with error!
(vmodl.fault.SystemError) {
faultCause = null,
faultMessage = null,
reason = 22ConfigurationException Failed to configure DR server with the Infrastructure Node services. Reason: Fault cause: vmodl.fault.InvalidArgument
When you try to configure SRM appliance to register with vCenter, it throws the error :
ERROR
Operation Failed
A general system error occurred: 22ConfigurationException Failed to configure DR server with the Infrastructure Node services. Reason: Fault cause: vmodl.fault.InvalidArgument
Exit code: 61
[context]zKq7AVECAAQAAL+xzQAOZHJjb25maWcAAIvFGGxpYnZtYWNvcmUuc28AAcicC2RyLWNvbmZpZ3VyYXRvcgABIvILAVWNBgFrmQYBG6AGARcCBwHb7QUB3EsHAFGeKQD/uikAGjQ3ApV0AGxpYnB0aHJlYWQuc28uMAADbwIPbGliYy5zby42AA==[/context]
[backtrace begin] product: VMware vCenter Site Recovery Manager, version: 8.2.0, build: build-13480383, tag: drconfig, cpu: x86_64, os: linux, buildType: release
backtrace[03] libvmacore.so[0x0018C58B]: Vmacore::Throwable::Throwable(std::string&&)
backtrace[04] dr-configurator[0x000B9CC8]
backtrace[05] dr-configurator[0x000BF222]
backtrace[06] dr-configurator[0x00068D55]
backtrace[07] dr-configurator[0x0006996B]
backtrace[08] dr-configurator[0x0006A01B]
backtrace[09] dr-configurator[0x00070217]
backtrace[10] dr-configurator[0x0005EDDB]
backtrace[11] dr-configurator[0x00074BDC]
backtrace[12] libvmacore.so[0x00299E51]
backtrace[13] libvmacore.so[0x0029BAFF]
backtrace[14] libvmacore.so[0x0037341A]
backtrace[15] libpthread.so.0[0x00007495]
backtrace[16] libc.so.6[0x000F026F]
[backtrace end]
Caused by:
(vmodl.fault.InvalidArgument)
faultCause = (vmodl.MethodFault) null,
faultMessage = <unset>,
invalidProperty = "Invalid certificate"
msg = "Received SOAP response fault from [<cs p:00007f766c00e960, TCP:rdc1vc01v.za.sbicdirectory.com:443>]: create
"
[context]zKq7AVECAAQAAL+xzQAUZHJjb25maWcAAIvFGGxpYnZtYWNvcmUuc28AAb6gDmxpYnZtb21pLnNvAAEBhx4BatQNAYwJEgGDDhICAzQGbGliZHItdm1vbWkuc28AATIrFAHGKBQDbVkCbGlibGtwLXR5cGVzLnNvAAQPjAxkci1jb25maWd1cmF0b3IABGzfDAQ96QsEVY0GBGuZBgQboAYEFwIHBNvtBQTcSwcAUZ4p[/context]
[backtrace begin] product: VMware vCenter Site Recovery Manager, version: 8.2.0, build: build-13480383, tag: drconfig, cpu: x86_64, os: linux, buildType: release
backtrace[03] libvmacore.so[0x0018C58B]: Vmacore::Throwable::Throwable(std::string&&)
backtrace[04] libvmomi.so[0x000EA0BE]
backtrace[05] libvmomi.so[0x001E8701]: Vmomi::Fault::InvalidArgument::ThrowInternal()
backtrace[06] libvmomi.so[0x000DD46A]
backtrace[07] libvmomi.so[0x0012098C]
backtrace[08] libvmomi.so[0x00120E83]
backtrace[09] libdr-vmomi.so[0x00063403]
backtrace[10] libvmomi.so[0x00142B32]: Vmomi::StubImpl::_Invoke_Task(Vmomi::ManagedMethod*, std::vector<Vmacore::Ref<Vmomi::Any>, std::allocator<Vmacore::Ref<Vmomi::Any> > >&, Vmacore::Ref<Vmomi::Any>&)
backtrace[11] libvmomi.so[0x001428C6]: Vmomi::StubImpl::_Invoke_Task(Vmomi::ManagedMethod*, std::vector<Vmacore::Ref<Vmomi::Any>, std::allocator<Vmacore::Ref<Vmomi::Any> > >&)
backtrace[12] liblkp-types.so[0x0002596D]: Lookup::ServiceRegistrationStub::Create(std::string const&, Lookup::ServiceRegistration::CreateSpec*)
backtrace[13] dr-configurator[0x000C8C0F]
backtrace[14] dr-configurator[0x000CDF6C]
backtrace[15] dr-configurator[0x000BE93D]
backtrace[16] dr-configurator[0x00068D55]
backtrace[17] dr-configurator[0x0006996B]
backtrace[18] dr-configurator[0x0006A01B]
backtrace[19] dr-configurator[0x00070217]
backtrace[20] dr-configurator[0x0005EDDB]
backtrace[21] dr-configurator[0x00074BDC]
backtrace[22] libvmacore.so[0x00299E51]
[backtrace end]
Operation ID: b01aa8a2-9a27-49c7-b133-ea2962451c3c
Resolution
1. Login to SRM VAMI
2. Click on the Access tab and click on
CHANGE to renew the certificate
3. Register SRM with vCenter
Change the Site Recovery Manager Appliance Certificate