hacmp 5.1 on aix 5.1 - sync issues with hw addr not unique - Aix

This is a discussion on hacmp 5.1 on aix 5.1 - sync issues with hw addr not unique - Aix ; Hi, Trying to define a new service ip address to one of the nodes, something went wrong and now I'm getting : ERROR: Hardware address 0.de.ad.be.ef.82 is not unique between adapter porthos on node porthos and adapter en2* on node ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: hacmp 5.1 on aix 5.1 - sync issues with hw addr not unique

  1. hacmp 5.1 on aix 5.1 - sync issues with hw addr not unique

    Hi,

    Trying to define a new service ip address to one of the nodes,
    something went wrong and now I'm getting :

    ERROR: Hardware address 0.de.ad.be.ef.82 is not unique between adapter
    porthos on node porthos and adapter en2* on node aramis

    Being aramis and porthos the 2 nodes on the cluster, and the service
    ip_address I wanted to change was on Porthos.

    I changed the hosts files, and set HACMP to reload configurations from
    the operating system, and from there on things went bad.

    Any pointers on how to straighten things out?

    PS : I didn't make a snapshot before screwing things around, and the
    lastest one I have has old LV sizes, does this matter? Or can I get
    around this doing an exportvg & importvg etc. ?


  2. Re: hacmp 5.1 on aix 5.1 - sync issues with hw addr not unique

    Alex,

    You have to set the alternate etheradress on 1 of the 2 with another
    deadbeef number (i.e. 83) The mac-addr will be the same now.

    Marcel
    Alex Goncalves wrote:
    > Hi,
    >
    > Trying to define a new service ip address to one of the nodes,
    > something went wrong and now I'm getting :
    >
    > ERROR: Hardware address 0.de.ad.be.ef.82 is not unique between adapter
    > porthos on node porthos and adapter en2* on node aramis
    >
    > Being aramis and porthos the 2 nodes on the cluster, and the service
    > ip_address I wanted to change was on Porthos.
    >
    > I changed the hosts files, and set HACMP to reload configurations from
    > the operating system, and from there on things went bad.
    >
    > Any pointers on how to straighten things out?
    >
    > PS : I didn't make a snapshot before screwing things around, and the
    > lastest one I have has old LV sizes, does this matter? Or can I get
    > around this doing an exportvg & importvg etc. ?



+ Reply to Thread