Forum Discussion

AndriiPushkarov's avatar
AndriiPushkarov
Level 5
6 years ago

MSDP and Multi-Networks

Hi all, 

In the work of Media Server Deduplication Pool. StorageServer is created by name (not IP). The server has 2 network interfaces. Network1 - technological; for backup/restore. Network2 - test; for restore (no gateway). MSDP stopped working and changed its status to DOWN.

\msdp_data\log\spoold\spoold.log:

April 20 09:30:30 ERR [000002094C116980]: -1: NetConnectByAddr: Failed to connect to spad on port 10102 using the following interface (s): [ip-network2 ip-network1 :: 1] (No connection could be made because the target machine actively refused it.

Netstat result:

TCP ip-network1: 10102 StorageServer: 53317 ESTABLISHED

TCP ip-network2: 10102 StorageServer: 56044 ESTABLISHED

After deactivate network2, MSDP changed status to UP. StorageServer resumed operation.

I tried to configure \msdp_data\etc\puredisk\agent.cfg:

url=pdde://StorageServer: 10102

replaced by

url=pdde://ip-network1: 10102

With this setting, StorageServer changes its status to DOWN

Question: is it possible to configure/restrict msdp to work only with network1? Hope this should

eliminate conflicts.

Andrii

8
Windows Server 2016

2 Replies

Sort By
  • sdo's avatar
    sdo
    Moderator
    6 years ago

    NetBackup MSDP can use a specific interface when the host has multiple interfaces, see:

    About the network interface for MSDP

    https://www.veritas.com/support/en_US/doc/25074086-127355784-0/v95643989-127355784

    .

    Without knowing for sure, I suspect that this has to be configured at build / MSDP creation time, i.e. changing the interface that MSDP has selected and configured for itself after it has configured itself for that interface might not be a customer supported action.  Maybe you can get it to work if you fudge some hosts file name entries and configure some persistent routes for yourself... but maybe something deep inside MSDP just doesn't like us (the customer) trying to force it like that.

    Anyway, the manual clearly states that you can achieve what it is you want to achieve.  But, IMO, without any specific experience, maybe this is a one-shot action at MSDP creation time.

     

    • AndriiPushkarov's avatar
      AndriiPushkarov
      Level 5
      6 years ago

      Thank you for your reply. You are absolutely right.

      I checked the options that are described below.

      Method 1.

      I set the metric values

      ip-network1 = metric 1

      ip-network2 = metric 5

      Used this in work.

       Method 2.

      It is not in the Veritas documents. You can manually configure the following sections of the configuration files. This was checked on the stand.

      \msdp_data\etc\puredisk\agent.cfg:

      # Host name or IP address of the storagepool authority

      # ReadOnly @restart

      url=pdde://10.80.125.159:10102

       

      # Host name or IP address of the MBS

      # ReadOnly @restart

      url=pdde://10.80.125.159:10102

       

      # Host name or IP address of the controller (ctrl)

      # ReadOnly @restart

      address=10.80.125.159

       

      #template which describes how to contact central logger

      url=pdde://10.80.125.159:10102

       

      #template which describes how to contact central logger

      url=pdde://10.80.125.159:10102

                                       

      # The ip of the central debug daemon

      dldip=10.80.125.159

       

      # Ip address or hostname for the SMTP server

      smtpserver=10.80.125.159

       

      \msdp_data\etc\puredisk\contentrouter.cfg:

      ; IP address or hostname of CA

      ; ReadOnly @restart

      Address=10.80.125.159

       

       \msdp_data\etc\puredisk\spa.cfg:

      [CA]

      Address=10.80.125.159

       The method described in the Veritas documentation is to create msdp. Specify the parameter: “Use Specific Network Interface - ip address”.