Dumb Newbie Issues (VCS) - Veritas Cluster Server

This is a discussion on Dumb Newbie Issues (VCS) - Veritas Cluster Server ; Problems with IP failover. We have it set up between two machines, ha00 and ha01. Two groups, ip_ha00, ip_ha01. Four resources, ha00_ip, ha00_nic and ha01_ip, ha01_nic. The types speak for themselves. We can successfully use the ifconfig command to bring ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Dumb Newbie Issues (VCS)

  1. Dumb Newbie Issues (VCS)

    Problems with IP failover.

    We have it set up between two machines, ha00 and ha01. Two groups,
    ip_ha00, ip_ha01. Four resources, ha00_ip, ha00_nic and ha01_ip,
    ha01_nic. The types speak for themselves.

    We can successfully use the ifconfig command to bring down either hme0
    interface and the other system will take up the burden, however, the
    hastop -all command brings down the interfaces. Ifconfig -a produces
    all normal except an IP of 0.0.0.0 Also, there is no automatic recovery
    when the interface is brought back up with the ifconfig command.

    Also encountered disk contention issues using Volume Manager on a
    shared, fiber-attatched SSA.

    Any ideas appreciated.

    Thanks in advance.

    Alex Dreyer.


  2. Re: Dumb Newbie Issues (VCS)


    Alex...

    For automatic failover, the resource must be both enabled & critical.

    Also, hastop -force is used to stop VCS and leave the resources up & running.
    It is normal that hastop without the "-force" option will bring down the
    interfaces and
    other resources.

    Chris Romano

    Alex Dreyer wrote:
    >Problems with IP failover.
    >
    >We have it set up between two machines, ha00 and ha01. Two groups,
    >ip_ha00, ip_ha01. Four resources, ha00_ip, ha00_nic and ha01_ip,
    >ha01_nic. The types speak for themselves.
    >
    >We can successfully use the ifconfig command to bring down either hme0
    >interface and the other system will take up the burden, however, the
    >hastop -all command brings down the interfaces. Ifconfig -a produces
    >all normal except an IP of 0.0.0.0 Also, there is no automatic recovery
    >when the interface is brought back up with the ifconfig command.
    >
    >Also encountered disk contention issues using Volume Manager on a
    >shared, fiber-attatched SSA.
    >
    >Any ideas appreciated.
    >
    >Thanks in advance.
    >
    >Alex Dreyer.
    >



+ Reply to Thread