----- Original message -----
From: Michael Moyles <michael.moyles@mavensecurities.com>
To: Stephen Smith6 <esmith@ibm.com>
Cc:
Subject: [EXTERNAL] Re: [ceph-users] Specify monitor IP when CIDR detection fails
Date: Fri, Apr 30, 2021 9:33 AM
 
What do the monitor logs say? I would think that 0.0.0.0/0 tells the monitor that it can bind to any address it finds on its host. If you know the specific interface or address you want it to bind to you can pass that with --public-addr. ‍ ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd

What do the monitor logs say? I would think that 0.0.0.0/0 tells the monitor that it can bind to any address it finds on its host. If you know the specific interface or address you want it to bind to you can pass that with --public-addr.

 

 

On Fri, 30 Apr 2021 at 13:50, Stephen Smith6 <esmith@ibm.com> wrote:

I'm running some specialized routing in my environment such that CIDR detection is failing when trying to add monitors. Is there a way to specify the monitor IP address to bind to when adding a monitor if "public_network = 0.0.0.0/0"? Setting "public_network = 0.0.0.0/0" is the only way I could find to bypass CIDR detection but then new monitors are added with the wrong IP address in the monitor map :( I'm running the latest version of Octopus.

_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-leave@ceph.io

 

 

--

Michael Moyles | Linux Engineer
michael.moyles@mavensecurities.com

Maven Securities Ltd
140 Leadenhall Street, London, EC3V 4QT
mavensecurities.com

This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Maven Securities Ltd is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.

 

This e-mail together with any attachments (the "Message") is confidential and may contain privileged information. If you are not the intended recipient or if you have received this e-mail in error, please notify the sender immediately and permanently delete this Message from your system. Do not copy, disclose or distribute the information contained in this Message.

Maven Investment Partners Ltd (No. 07511928), Maven Investment Partners US Ltd (No. 11494299), Maven Europe Ltd (No. 08966), Maven Derivatives Asia Limited (No.10361312) & Maven Securities Holding Ltd (No. 07505438) are registered as companies in England and Wales and their registered address is Level 3, 6 Bevis Marks, London EC3A 7BA, United Kingdom. The companies’ VAT No. is 135539016. Maven Asia (Hong Kong) Ltd (No. 2444041) is registered in Hong Kong and its registered address is 20/F, Tai Tung Building, 8 Fleming Road, Wan Chai, Hong Kong. Maven Derivatives Amsterdam B.V. (71291377) is registered in the Netherlands and its registered address is 12.02, Spaces, Barbara Strozzilaan 101, Amsterdam, 1083 HN, Netherlands. Maven Europe Ltd is authorised and regulated by the Financial Conduct Authority (FRN:770542). Maven Asia (Hong Kong) Ltd is registered and regulated by the Securities and Futures Commission (CE No: BJF060). Maven Derivatives Amsterdam B.V. is licensed and regulated by the Dutch Authority for the Financial Markets.