仅限 RecoverPoint Classic：不同 RecoverPoint 系统对象之间的连接问题

RecoverPoint Classic 系统中不同对象之间的连接问题。
这些错误与特定的 RecoverPoint Appliance （RPA） 相关。

系统警报和 CLI get_system_status 显示不同的连接相关问题。
可能会出现以下任何一个或多个错误 ：

RPAs:

WARNING: States of all RPAs are unknown
WARNING: LAN connection between all RPAs is unknown
WARNING: RPA 2 in Site2: LAN network interface status is unknown

卷：

WARNING: States of all devices are unknown
WARNING: User volume [VM1_CG, prod, VM2_0_0_scsi] is unknown to RPA x
WARNING: Journal volume [VM2_CG, prod, IOFilter_JVOL_00005] is unknown to RPA x

分配器：

WARNING: States of all splitters are unknown
ERROR: RP_esxi_cluster-xx.xx.xx.xx1's connection status with RPA x is unknown
ERROR: RP_esxi_cluster-xx.xx.xx.xx0's connection status with RPA x is unknown
ERROR: RP_esxi_cluster-xx.xx.xx.xx2's connection status with RPA x is unknown
ERROR: RP_esxi_cluster-xx.xx.xx.xx3's connection status with RPA x is unknown

WAN 问题：

Items: WARNING: No remote communication between clusters in the system
Items: WARNING: Data link status is unknown for RPA 1 between clusters Site2 and Site1, WARNING: Data link status is unknown for RPA 2 between clusters Site2 and Site1

控制日志（提取的*/files/home/kos/control/result.log）中的错误示例：

2020/05/08 19:23:03.235 - #2 - 21038/20782 - lockboxSet: fips-security: lockboxSet: inserting to lockbox:  name = SiteUID_List  value.size() = 18
2020/05/08 19:23:03.236 - #1 - 21038/20782 - Lockbox:  The Lockbox contains no entries.
2020/05/08 19:23:03.236 - #2 - 20916/20782 - WatchDogLEPInterface:  service manager expects watchdog keep-alive notification messages!
2020/05/08 19:23:03.236 - #1 - 21038/20782 - Lockbox: insert: Can't open lockbox: -35
2020/05/08 19:23:03.236 - #1 - 21038/20782 - ControlCryptoUtils: fips-security: lockboxSet: error updating value in lockbox: -35
2020/05/08 19:23:03.236 - #2 - 21038/20782 - aux::updateLockboxWithKvolTriplet: fips-security: error writing updated site list into lockbox.
2020/05/08 19:23:03.236 - #0 - 20916/20782 - LEP2: errno=0 WatchDog 0 time is low (lease =-39.6798)! RPA might be rebooted.
2020/05/08 19:23:03.237 - #2 - 21034/20782 - BC::handleUpdateLockboxWithKvolTriplet: fips-security: auxAsyncWorker returned error. rc=MRC_LOCKBOX_ACCESS_ERROR

2020/05/11 16:54:53.366 - #1 - 1702/1644 - Lockbox: Lockbox tampering was detected, so it cannot be read.
2020/05/11 16:54:53.366 - #2 - 1702/1644 - lockboxGet: fips-security: error=-60
2020/05/11 16:54:53.366 - #0 - 1702/1644 - BSAFE_FIPS_TLSHandler: errno=2 loadLocalCert: Unable to get server certificate from lockbox
2020/05/11 16:54:53.366 - #0 - 1702/1644 - BSAFE_FIPS_TLSHandler: errno=2 init: Unable to retrieve server certificate
2020/05/11 16:54:53.366 - #0 - 1702/1644 - xTE: errno=2 1762817320: MessageHandler::open()unable to initialize a socket handler!

RPA 上的密码箱文件在某些方面已损坏，因此 RPA 无法使用证书与其他对象通信。

它可能无法与系统中的任何对象通信，包括其他 RPA、拆分器（这些拆分器下的任何卷）、其他站点等。

密码箱损坏的可能原因之一是 RPA 上的文件系统已满情况。

解决方法：
运行以下脚本以清除每个受影响的 RPA 上的密码箱问题。
当脚本运行时，RPA 有时可能会重新启动。

通过 PuTTY 或 SSH 以 boxmgmt 用户身份登录，然后选择以下选项：[2] 设置 -> [8] 高级选项 -> [4] 运行脚本 -> 粘贴以下脚本：

MWRjNmQ3ZGY2YzM2NWI0NWFjNTQ5NmE1MjliYzg2ZjMKdW5saW1pdGVkCm5vdF9yZXN0cmljdGVk
ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOgpGaW5kIGFuZCBmaXggbG9ja2JveCBpc3N1ZXMKQXNz
aWYgSGFsClZFUlNJT049JChncmVwIHRfd2luSW5zdGFsbFNoaWVsZFZlcnNpb24gL2hvbWUva29z
L2tib3gvc3JjL2luaXRpYWxpemF0aW9uL3R3ZWFrX3BhcmFtcy90d2Vhay5wYXJhbXMudmVyc2lv
bnxncmVwIC1vICJbMS05XS4qWzAtOV0iKQpNQUpPUlZFUlNJT049IiR7VkVSU0lPTjowOjF9IgpN
SU5PUlZFUlNJT049IiR7VkVSU0lPTjoyOjF9IgppZiBbICRNQUpPUlZFUlNJT04gLWd0IDUgXSB8
fCAoWyAkTUFKT1JWRVJTSU9OIC1lcSA1IF0gJiYgWyAkTUlOT1JWRVJTSU9OIC1nZSAzIF0pOyB0
aGVuCglpZiBbWyBgemVncmVwIC1hICJyZXRyaWV2ZTogZmFpbGVkIHRvIHJldHJpZXZlIGl0ZW0u
KnByaXZfY3VycnxMb2NrYm94IHRhbXBlcmluZ3xNUkNfTE9DS0JPWF9BQ0NFU1NfRVJST1IiIC9o
b21lL2tvcy9jb250cm9sL3Jlc3VsdC5sb2cubGF0ZXN0IC9ob21lL2tvcy9jb250cm9sL3Jlc3Vs
dC5sb2cucHJldmlvdXMuZ3p8d2MgLWxgIC1ndCAwIF1dOyB0aGVuCgkJZWNobyAiTG9ja2JveCBp
c3N1ZXMgd2VyZSBmb3VuZCwgYnV0IHNpbmNlIHRoaXMgaXMgNS4zLCBQbGVhc2UgY29udGFjdCBh
IFJlY292ZXJQb2ludCBTdXBwb3J0IFNNRS4iCgkJZXhpdCAwCgllbHNlCgkJZWNobyAiTm8gaXNz
dWVzIGZvdW5kIgoJCWV4aXQgMAoJZmkKZWxzZQoJaWYgW1sgYHplZ3JlcCAtYSAiTG9ja2JveCB0
YW1wZXJpbmd8TVJDX0xPQ0tCT1hfQUNDRVNTX0VSUk9SIiAvaG9tZS9rb3MvY29udHJvbC9yZXN1
bHQubG9nLmxhdGVzdCAvaG9tZS9rb3MvY29udHJvbC9yZXN1bHQubG9nLnByZXZpb3VzLmd6fHdj
IC1sYCAtZ3QgMCBdXTsgdGhlbgoJCWVjaG8gIkRldGVjdGVkIGxvY2tib3ggaXNzdWUuIENsZWFy
aW5nIGl0IGFuZCByZXN0YXJ0aW5nIGNvbnRyb2wiCgkJcm0gLWYgL2hvbWUva29zL2xvY2tib3gv
KgoJCXBraWxsIC05IGNvbnRyb2xfcHJvY2VzcwoJZWxzZQoJCWVjaG8gIk5vIGlzc3VlcyBmb3Vu
ZCIKCWZpCmZpCg==
#

按 Enter 键，输入您的名称以应用脚本。

分辨率：
Dell Technologies 工程部门正在调查此问题。目前正在开发永久修复。请联系 Dell Technologies 客户支持中心或您的服务代表寻求帮助，并提供此解决方案 ID。

关键信息：
此知识库文章仅适用于 RecoverPoint Classic 和 RecoverPoint for VMs 版本 5.2 及更低版本。

请勿尝试在 RecoverPoint for VMs 5.3 及更高版本上运行解决方法！
对于 RecoverPoint for VMs 5.3 及更高版本，请使用 RecoverPoint for VMs：由于密码箱损坏，远程群集之间没有通信 （需要登录）

对于 RecoverPoint Classic：
下面的签名脚本可以启用密码箱调试，从而帮助工程部门了解将来出现密码箱问题的原因。
如果用户看到这种情况无缘无故地发生，我们可以启用调试日志记录，并在再次出现后收集日志。

启用调试日志记录，在每个 RPA 上以 boxmgmt/admin身份登录并运行以下脚本：

OWFkNmQ5YWEzMWRjZDk0ZWIxZTRiMzQ4ZTFkZTYyNTQKdW5saW1pdGVkCm5vdF9yZXN0cmljdGVk ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOjEwMTAzCkxvY2tib3ggZGVidWcgdHJhY2Ugc2V0CkVF CiMhL2Jpbi9iYXNoCmVjaG8gIlN0YXJ0IGFkZGluZyB0cmFjZSBDU1RfVFJBQ0UsQ0xCX1RSQUNF IGluIGZpbGUgL2V0Yy9yYy5sb2NhbCIKc2VkIC1pICcvbGRjb25maWcvaSBcZXhwb3J0IENTVF9U UkFDRT0iL3Vzci9DU1RfVFJBQ0UuTE9HIicgL2V0Yy9yYy5sb2NhbApzZWQgLWkgJy9sZGNvbmZp Zy9pIFxleHBvcnQgQ0xCX1RSQUNFPSIvdXNyL0NMQl9UUkFDRS5MT0ciJyAvZXRjL3JjLmxvY2Fs CkNTVF9UUkFDRV9DT1VOVD1gZ3JlcCAnZXhwb3J0IENTVF9UUkFDRT0iL3Vzci9DU1RfVFJBQ0Uu TE9HIicgL2V0Yy9yYy5sb2NhbCB8IHdjIC1sYApDTEJfVFJBQ0VfQ09VTlQ9YGdyZXAgJ2V4cG9y dCBDTEJfVFJBQ0U9Ii91c3IvQ0xCX1RSQUNFLkxPRyInIC9ldGMvcmMubG9jYWwgfCB3YyAtbGAK aWYgW1sgKCAiJENTVF9UUkFDRV9DT1VOVCIgLWd0IDAgKSAmJiAoICIkQ0xCX1RSQUNFX0NPVU5U IiAtZ3QgMCApIF1dCnRoZW4KICAgICBlY2hvICJBZGRlZCBib3RoIENTVF9UUkFDRSxDTEJfVFJB Q0Ugc3VjZXNzZnVsbHkiCiAgICAgZWxzZQogICAgICAgICAgZWNobyAiQ291bGQgbm90IGFkZCBD U1RfVFJBQ0UsQ0xCX1RSQUNFIHN1Y2Vzc2Z1bGx5IgogICAgICAgICAgZmkK #

然后重新启动 RPA 并等待再次出现。