search cancel

Symantec Directory : After adding ipV6 address to DNS, MW-DISP replication is not working.

book

Article ID: 253596

calendar_today

Updated On:

Products

CA Directory

Issue/Introduction

You may come across a problem where after adding ipV6 address to DNS, MW-DISP replication stops working.

Reviewing the trace log (when 'set trace=all;') is enabled, you will see something similar to what is outlined below as an example.

e.g. dsa_1_name DSA will report the following:

? [64] 20221017.093902.478 WARN : Entry 'dsa_2_name x -1' not found in DISP file
* [64] 20221017.093902.479 DSA_W2650 Cannot get Multiwrite last update time for 'dsa_2_name'
! [64] Send MW-DISP Bind request
! [64] Creating Bind request
! [64]
> [64] -> #10000029 [dsa_2_name] MWDISP BIND-REQ
> [64]   invoke-id = 0   credit = -5
> [64]   User:
> [64]     <countryName "US">
> [64]     <commonName "dsa_1_name">
> [64]   Password: (masked)
> [64]   Remote address:
> [64]     psap = "$MWDISP$"
> [64]     nsap = [2610:30:201c:791:0:0:0:99]:22235
> [64]
> [64]
! [64] Connecting to TCP [2610:30:201c:791:0:0:0:99]:22235
? [3] 20221017.093902.479 WARN : comms_recv: Connection refused

Environment

Release : 14.1

Resolution

Even though ipV6 protocol is supported there is a change required for this to work.

There are two options:

1) Do not use ipV6 protocol. i.e. remove it from your DNS.

2) Modify the KNOWLEDGE .dxc file where you currently may have 'tcp' or 'ipv4' defined in "address" line , to explicitly add 'ipv6' in the same line and restart the DSAs.

e.g. you may have one of the following in all KNOWLEDGE .dxc files.

address = tcp "hostname or ip" port 19389
OR
address = ipv4 "hostname or ip" port 19389

Change the above to:

address = tcp "hostname or ip" port 19389, ipv6 "hostname or ip" port 19389
OR
address = ipv4 "hostname or ip" port 19389, ipv6 "hostname or ip" port 19389

Once done, restart all DSAs and after that MW-DISP replication will work over ipV6 protocol as well.