Troubleshooting HAE Cluster Membership

This document (7015225) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise High Availability Extension
SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 10

Situation

Cluster redundancy requires unique bind addresses with multiple interfaces. Unique multicast ports are also preferred. Partial totem sections from /etc/corosync/corosync.conf for invalid or discouraged configurations follow.
totem {
    rrp_mode:    passive
    transport:    udp
    version:    2
    interface {
        bindnetaddr:    192.168.64.0
        mcastaddr:    239.52.65.210
        mcastport:    5410
        ringnumber:    0
    }
    interface {
        bindnetaddr:    192.168.64.0
        mcastaddr:    239.52.65.211
        mcastport:    5411
        ringnumber:    1
    }
}
or
totem {
    rrp_mode:    passive
    transport:    udpu
    version:    2
    interface {
        bindnetaddr:    10.1.0.0
        member {
            memberaddr:    10.1.0.2
        }
        member {
            memberaddr:    10.1.0.3
        }
        mcastport:    5405
        ringnumber:    0
    }
    interface {
        bindnetaddr:    172.16.0.0
        member {
            memberaddr:    172.16.1.1
        }
        member {
            memberaddr:    172.16.1.2
        }
        mcastport:    5405
        ringnumber:    1
    }
}

Resolution

The bindnetaddr values must be unique among interfaces. For optimal troubleshooting, the mcastport should likewise be unique. Corrected examples follow.
totem {
    rrp_mode:    passive
    transport:    udp
    version:    2
    interface {
        bindnetaddr:    172.16.2.0
        mcastaddr:    239.52.65.210
        mcastport:    5410
        ringnumber:    0
    }
    interface {
        bindnetaddr:    192.168.64.0
        mcastaddr:    239.52.65.211
        mcastport:    5411
        ringnumber:    1
    }
}
and
totem {
    rrp_mode:    passive
    transport:    udpu
    version:    2
    interface {
        bindnetaddr:    10.1.0.0
        member {
            memberaddr:    10.1.0.2
        }
        member {
            memberaddr:    10.1.0.3
        }
        mcastport:    5405
        ringnumber:    0
    }
    interface {
        bindnetaddr:    172.16.0.0
        member {
            memberaddr:    172.16.1.1
        }
        member {
            memberaddr:    172.16.1.2
        }
        mcastport:    5406
        ringnumber:    1
    }
}

Additional Information

The mcastport values do not need to be unique, but it helps when reading a LAN trace to isolate the traffic on that interface by port number.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7015225
  • Creation Date: 18-Jun-2014
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise High Availability Extension
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center