SUMMARY: member and cluster IP address changes

From: jgrijalba <jgrijalba_at_novasoft.es>
Date: Fri, 21 Sep 2001 11:57:42 +0200

Hi admins,
Thanks to Andreas Maagdenberg for their replies.
Original question:
        I have a two node Alpha cluster running Tru64 Unix v4.0D and TruCluster
        Available Server v1.5
        They both have two network cards, one network card is connected to the LAN,
        and the other is only used as a heartbeat and so is connected to the other
        node using a cross-over SCSI cable. The network configuration in the
        cluster is as follows (changing names and IPs for security) :

        Member name: node1
          Member IP address: 196.4.82.100
          Daemon communication use: Primary
          Member aliveness ping use: Primary
          Monitor interface setting: monitor
        Member name: node2
          Member IP address: 196.4.82.101
          Daemon communication use: Primary
          Member aliveness ping use: Primary
          Monitor interface setting: monitor
        (above taken from asecdb)

                ASE Network Configuration

    Member Name Interface Name Member Net Monitor
    ___________ ______________ __________ _______

    node1 node1 Primary Yes
    node2 node2 Primary Yes

(Taken from asemgr)

        The public IPs are 171.42.44.1 for node1 and 171.42.44.2 for node2.

        Besides we have a disk service named service1 and with IP 171.42.44.3

        I wish to change the public IPs and the service IP to another subnet.

        I know how to change the service IP but only it runs when the new IP is in
        the same subnet that the other nodes IPs. I suppose I have to change the
        nodes IPs and service IP to the new subnet at the same time.

Solution from Andreas:

        "I suggest putting the service off-line.
        Edit the hosts-file on both nodes. change the ip of the service.
        As I see, you haven't configured the public network in ase and it's not
        the hostname-network either so you can proceed with netsetup to
        re-configure the public network.
        After that you can bring the service online again.
        I suggest (for private-net failover) that you also configure the public
        network in ase as a backup network."

        A remark:
        I had also to change the IPs from /etc/hosts in each node that made
reference to the other node before that bring the service online. Netsetup
only changed the IPs for each node itself.

Best regards,
        Jorge Grijalba
Received on Fri Sep 21 2001 - 11:02:10 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT