Use dxsnmp to quickly verify the status of replication for a CA Directory implementation
search cancel

Use dxsnmp to quickly verify the status of replication for a CA Directory implementation

book

Article ID: 397903

calendar_today

Updated On:

Products

CA Directory

Issue/Introduction

There are various scenaros when a CA Directory administrator needs to verify the status of the replication for a CA Directory implementatin. In this article, we are focusing on verifying the status for a working CA Directory implmentation that is being migrated.

 

Environment

Release 14.1
Component: CA Directory

Resolution

Traditionally, the following tools can be used to monitor the status of a multiwrite replication:

  • alarm log
  • trace log
  • replication log
  • get dsp command after connecting to the Console port

These tools, however, is relatively more labor intensive to perform. When the number of DSAs are large, the task can becomme rather tedious as well.

The sample tool dxsnmp included in a CA Directory implementation can be used to retrieve a number of server-side data remotely and can be used to help verify the multiwrite replication statuses:

DXsnmp Sample Tool -- Monitor DSAs

Assumption

Assume the set dsa command, usually in a knowledge/dxc file contains the following snippet:

set dsa DSANAME =
{
...
    address = tcp "999.999.999.999" port 9999
...
    snmp-port = 9999
...
};

For a DSA, the snmp-port number is usually set to the same port number as of the interface the DSA listens to. In this case, both are set to port number 9999. This is because the DSA listens at the TCP port, while snmp protocol uses UDP protocol.

Also, before checking the status, you will need to cause certain updates to your DSAs.

Linux

For a linux implemetation, login as the user dsa

cd "$DXHOME/samples/snmp
./dxsnmp 999.999.999.999/9999 | grep dxMWStatus
...
(sample output)
dxMWStatus.1 : 1 (ok)
...
dxMWStatus.1 : 2 (failed)

This will show the Multiwrite status of all the muliwrite partners of the DSA. You can further identify the particular DSA if you see any of the status shows something other than "(ok)", then the following command will allow you to match up the remote DSA through matching the n of the dxMWStatus.n:

cd "$DXHOME/samples/snmp
./dxsnmp 999.999.999.999/9999 | grep dxRemoteDsaName
...
(sample output)
dxRemoteDsaName.1 : aRemoteDsaName

Windows

For a Windows implementation, login as an Administrator user

cd /d "%DXHOME%\samples\snmp
.\dxsnmp 999.999.999.999/9999 | findstr dxMWStatus
...
(sample output)
dxMWStatus.1 : 1 (ok)
...
dxMWStatus.1 : 2 (failed)

 

This will show the Multiwrite status of all the muliwrite partners of the DSA. You can further identify the particular DSA if you see any of the status shows something other than "(ok)", then the following command will allow you to match up the remote DSA through matching the n of the dxMWStatus.n:

cd /d "%DXHOME%\samples\snmp
.\dxsnmp 999.999.999.999/9999 | findstr dxRemoteDsaName
...
(sample output)
dxRemoteDsaName.1 : aRemoteDsaName

 

Additional Information

For more details about how to further configure CA Directory snmp, see the following product link:

Monitoring with SNMP