[ClusterLabs] Verifying DRBD Run-Time Configuration

[Eric Robinson]

> -----Original Message-----
> From: Strahil Nikolov <hunter86_bg at yahoo.com>
> Sent: Sunday, April 12, 2020 2:54 AM
> To: Cluster Labs - All topics related to open-source clustering welcomed
> <users at clusterlabs.org>; Eric Robinson <eric.robinson at psmnv.com>
> Subject: Re: [ClusterLabs] Verifying DRBD Run-Time Configuration
>
> On April 11, 2020 6:17:14 PM GMT+03:00, Eric Robinson
> <eric.robinson at psmnv.com> wrote:
> >If I want to know the current DRBD runtime settings such as timeout,
> >ping-int, or connect-int, how do I check that? I'm assuming they may
> >not be the same as what shows in the config file.
> >
> >--Eric
> >
> >
> >
> >
> >Disclaimer : This email and any files transmitted with it are
> >confidential and intended solely for intended recipients. If you are
> >not the named addressee you should not disseminate, distribute, copy or
> >alter this email. Any views or opinions presented in this email are
> >solely those of the author and might not represent those of Physician
> >Select Management. Warning: Although Physician Select Management has
> >taken reasonable precautions to ensure no viruses are present in this
> >email, the company cannot accept responsibility for any loss or damage
> >arising from the use of this email or attachments.
>
> You can get everything the cluster know via 'cibadmin -Q
> /tmp/cluster_conf.xml'
>
> Then you can examine it.
>

As usual, I guess there's more than one way to get things. Someone suggested 'drbdsetup show <res> --show-defaults' and that works great.


Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.