Hello

I am setting up a 2 node SAN using pacemaker/drbd/iscsi on ubuntu. Everything works as expected when a power outage test is performed.
My issue is that when a network outage test is performed on one or both machines (cable pull or power off switch), drbd will be standalone on both nodes when connected again. I have set parameters in drbd (v8.3)to automatically resolve split brain as but no combination has worked I am currently using:

after-sb-0pri discard-least-changes;
after-sb-1pri concensus;
after-sb-2pri call-pri-lost-after-sb;


In case it matters the play by play is as such:
all services fine ->network interruption
both nodes claim all resources as they have no knowledge of the other
->network connection re-established:
one node takes over all resources, drbd is up on the primary/standalone (i believe it is always the machine that was previously primary). other node is secondary/standalone.

How can I get drbd within pacemaker to connect making the drbd with most/newest changes the primary, forcing the secondary to discard data and connect?




other info -crm configure show:
node ubun1 \
attributes standby="off"
node ubun2 \
attributes standby="off"
primitive ClusterIP ocf:heartbeat:IPaddr2 \
params ip="192.168.3.5" cidr_netmask="32" nic="eth1:0" \
op monitor interval="30s"
primitive DataFS ocf:heartbeat:Filesystem \
params device="/dev/drbd0" directory="/datamount" fstype="ext4"
primitive drbd_data ocf:linbit:drbd \
params drbd_resource="data" \
op monitor interval="15s"
primitive iscsi lsb:iscsitarget
group g_services DataFS ClusterIP iscsi
ms ms_drbd_data drbd_data \
meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true"
colocation c_g_services_on_drbd_data inf: g_services ms_drbd_data:Master
order o_g_servicesafter_drbd_data inf: ms_drbd_data:promote g_services:start
property $id="cib-bootstrap-options" \
dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
stonith-enabled="false" \
no-quorum-policy="ignore"
rsc_defaults $id="rsc-options" \
resource-stickiness="100"

Anyone?
More simply put my question would be "How can I get pacemaker to decide a primary based on DRBD freshness"
Failing that, can anyone suggest any further resources to help