PItoPI failover configuration - PI SDK member

Discussion created by MansiP on Mar 7, 2014
Latest reply on Mar 7, 2014 by Marcos Vainer Loeff



Have thrown this question to techsupport many times but haven't found a reasonable answer. I need to unerstand the best practice in order to configure PItoPI interfaces in a failover mode having both source PI and detsination PI configured as collectives.


For a destination PI server ---> "PI SDK Member field" in General Tab :


The primary interface field is configured with the "Primary PI server" node while the backup Interface is configured with the "Secondary PI server node". May I know what would be the consequences if both the interfaces point to the "primary server only"? What are the advantages or purpose of configuring each failover instance pointing to different member in a collective?


Similarly for Source PI :


What are the advantages of selecting different members in a collective for each failover interface or is it not? Question raised because we also have source level failover node wherein the secondary node can be mentioned.


So basically what are the best practices for source and destination servers in a failover interfaces with this kind of architecture.