Why does the 3rd McAfee cluster member located on a separate chassis at a DR site not become "active"?
Policy and Peer Connection Status
mfedr_1VA.local (secondary - pending connection to Crossbeam master)
Below are the technical mechanics related to how a newly installed MFE Node comes online and attempts to become a part of an existing cluster.
fwregisterd - When a newly installed member comes online, it uses a TCP connection to "discover" any other members
Note- If 'cf cluster status' lists any members, then fwregisterd connected successfully
resolverd - uses a tcp connection to exchange policy back and forth between the "master" node and the "child" nodes
faild - members use multicast to determine whether or not a member is in a good state.
Note: If a new installed member comes online and does not find other cluster members due to a connectivity (multicast) issue, it will form its own separate cluster.