SAP Knowledge Base Article - Preview

3395593 - HADR Fault Manager sybdbfm status got 'VIPA status: ERROR' for SRS


  • HADR with Fault Manager installed on premise environment using virtual IP
  • FM status returned VIPA status ERROR -

    user@hostname$ sybdbfm status
    fault manager running, pid = xx, fault manager overall status = OK, currently executing in mode PAUSING
    *** sanity check report (xxxxxx)***.
    node 1: server hostname1, site Site1.
    db host status: OK.
    db status DB INDOUBT hadr status PRIMARY.
    node 2: server hostname2, site Site2.
    db host status: OK.
    db status OK hadr status STANDBY.
    replication status: SYNC_OK.
    VIPA status: ERROR.
    failover prerequisites fulfilled: YES.

  • FM heartbeat log /usr/sap/hostctrl/work/dev_hbeat reports message:

    ***LOG Q0I=> NiPConnect2: <host_ip>:1128: connect (111: Connection refused) [/bas/749_REL/src/base/ni/nixxi.cpp xxx

  • FM log file $SYBASE/FaultManager/dev_sybdbfm may also reports message:

    GET_IP_ADDRESS_PROPERTIES=No address <FM_host_ip> with ipv4 address family assigned to any network interface is found.



SAP Adaptive Server Enterprise (ASE) 16.0 with High Availability Disaster Recovery (HADR) for Business Suite


SAP Adaptive Server Enterprise 16.0


sybase, ASE, REP, Replication, SAP Replication Server, SHA, hostagent, network, hosts, SRS, 4905, 4909, 1128, port , KBA , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.