error appeared during validation process:
+ qpid-config -a localhost:5672 add exchange topic my-topic-exchange --ive
Failed: SessionException: ExecutionException(error_code=540, command_id=serial(66), class_code=7, command_code=1, field_index=0, description=u'not-implemented: Cannot use Initial Value Exchanges in a cluster', error_info={}, channel=1, id=serial(63))


# rpm -qa | grep qpid
qpid-cpp-client-ssl-0.7.946106-33.el5
qpid-tools-0.7.946106-12.el5
qpid-cpp-server-xml-0.7.946106-33.el5
python-qpid-0.7.946106-15.el5
qpid-java-common-0.10-6.el5
qpid-cpp-client-devel-0.7.946106-33.el5
qpid-cpp-server-0.7.946106-33.el5
qpid-cpp-server-store-0.7.946106-33.el5
qpid-java-example-0.10-6.el5
qpid-cpp-server-devel-0.7.946106-33.el5
qpid-cpp-client-0.7.946106-33.el5
qpid-cpp-server-cluster-0.7.946106-33.el5
qpid-tests-0.7.946106-1.el5
qpid-cpp-client-devel-docs-0.7.946106-33.el5
qpid-cpp-server-ssl-0.7.946106-33.el5
qpid-java-client-0.10-6.el5
rh-qpid-cpp-tests-0.7.946106-33.el5

QPID-3217 states that IVE feature has been disabled among clustered brokers and thus comment #1 shows that IVE feature will not cause cluster inconsistency with steps to reproduce from comment #0

===quote===
https://issues.apache.org/jira/browse/QPID-3217?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel#issue-tabs

Since this option is rarely used, the short term fix is to disallow IVE in a cluster.
This is not a regression since it didn't work anyway. 
===quote===

This happens when durable IVE exchange is created on standalone broker store and then store is used for clustered node

Daemon startup failed: not-implemented: Cannot use Initial Value Exchanges in a cluster


--> VERIFIED on rhel 5.6 (x86_64 / i386)

Maybe we should open a new BZ to fix the underlying problem so IVE exchanges can be used in a cluster. I'm not sure what the priority on that is.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-1147.html