Novell Home

My Favorites

Close

Please to see your favorites.

ERROR: fencing_topology not supported by the RNG schema (COROSYNC)

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

Environment

SUSE Linux Enterprise High Availability Extension 11 Service Pack 2

Situation

Trying to setup a fencing topology on SLES 11 SP2 HAE with something like

   mars:/tmp # crm configure fencing_topology p_stonith-sbd moerder

or

   mars:/tmp # crm configure fencing_topology mars: p_stonith-sbd moerder

results in an error message

   ERROR: fencing_topology not supported by the RNG schema

so despite the changelog states it is available seemingly it does not work.


Resolution

On SLES 11 SP2 the fencing topology was introduced as experimental. It is only implemented in schema 1.1 but not in the default schema 1.2. To change to the experimental setting one can issue

   cibadmin -U -X '<cib validate-with="pacemaker-1.1"/>'

to use the schema 1.1 and then the fencing topology will work.

This will not be necessary anymore with SLES 11 SP3 HAE, as the fencing topology will be fully supported and part of the default schema.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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:7012682
  • Creation Date:24-JUN-13
  • Modified Date:24-JUN-13
    • SUSESUSE Linux Enterprise High Availability Extension

Did this document solve your problem? Provide Feedback