Rlinks are not visible in Veritas InfoScale Operations Manager when Veritas Volume Replicator (VVR) Replication Hosts are on RHEL 7.2

book

Article ID: 100033086

calendar_today

Updated On:

Cause

The library shipped with Veritas InfoScale Operations Manager is not compatible with the operating system.  The /opt/VRTSsfmh/lib/libstdc++.so.6 that is shipped in the Veritas InfoScale Operations Managed Host package is not compatible with RHEL 7.2. This is causing vradmin commands to fail and not able to discover information about the rlinks.

Resolution

Follow this procedure on the problematic Managed Hosts in the environment.

1. Run the following command:
export LD_LIBRARY_PATH=/opt/VRTSsfmh/lib

2. Run the following command:
vradmin printrvg   Replace

with the appropriate RVG name.

Note: The above vradmin command will fail with an error like this:

vradmin: /opt/VRTSsfmh/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found

The specific library mentioned above is required by the vradmin daemon.

3. Run the following command:   
mv /opt/VRTSsfmh/lib/libstdc++.so.6 /opt/VRTSsfmh/lib/libstdc++.so.6.bkp

4. Run the following command:   
cp /usr/lib64/libstdc++.so.6 /opt/VRTSsfmh/lib/

5. Run the following command:   
vradmin printrvg

6. Refresh the Managed Hosts discovery from Veritas InfoScale Operations Manager, and check the rlinks information.

7. Repeat the same procedure on all other nodes involved.

Issue/Introduction

Rlinks are not visible in Veritas InfoScale Operations Manager when Veritas Volume Replicator (VVR) Replication Hosts are on RHEL (Red Hat Enterprise Linux) 7.2.


Here is an example vxprint -Pl output showing a valid rlink:
Disk group: testdg01

Rvg: testrvg
info: rid=0.1067 version=4 rvg_version=45 last_tag=3
state: state=ACTIVE kernel=ENABLED
assoc: datavols=testbin01,testdata01,testlogs01
srl=testsrl
rlinks=rlk_dr_testrvg
exports=(none)
vsets=(none)
att: rlinks=rlk_dr_testrvg
flags: closed secondary enabled attached logging
device: minor=29004 bdev=199/29004 cdev=199/29004
path=/dev/vx/dsk/testdg01/testrvg
perms: user=root group=root mode=0600


Rlink: rlk_dr_testrvg
info: timeout=500 rid=0.1071
latency_high_mark=10000 latency_low_mark=9950
bandwidth_limit=none
state: state=ACTIVE
synchronous=off latencyprot=override srlprot=off
assoc: rvg=testrvg
remote_host=remote.example.com
IP_addr=192.168.10.10 port=4145
remote_dg=testdg01

remote_dg_dgid=1469582932.13.test.example.com
remote_rvg_version=45
remote_rlink=rlk_prod_testrvg
remote_rlink_rid=0.1082
local_host=local.example.com
IP_addr=192.168.10.2 port=4145
protocol: TCP/IP
flags: write enabled attached consistent connected


When viewing the rlinks in Veritas InfoScale Operations Manager, no RVG (Replicated Volume Group) link is present. But the vxprint syntax above shows an existing RVG link:
Powered by Wolken Software