Also in 18.2.7 the I was having multiple disk failures I have to enable to true 
to below….but its not amiable in 19.2.2

osd osd_skip_check_past_interval_bounds true 
Regards
Dev

> On Jun 22, 2025, at 9:22 AM, Eugen Block <ebl...@nde.ag> wrote:
> 
> The command 'ceph osd find <ID>' is not the right one to query an OSD for the 
> cluster network, it just shows the public address of an OSD (like a client 
> would need to). Just use 'ceph osd dump' and look at the OSD output.
> 
> 
> Zitat von Devender Singh <deven...@netskrt.io>:
> 
>> Hello
>> 
>> I checked on my all clusters everywhere OSD’s not using cluster network.
>> Here is another example in my lab where I have three hosts in vlan1 and 
>> vlan2 running on one proxmox server and here also same thing…
>> No MTU change, these are default to 1500.
>> 
>> I don’t understand what I am missing?
>> 
>> root@ceph-01:~# ceph config dump |grep -i network
>> global                                      advanced  cluster_network        
>>                 192.168.2.0/24                                               
>>                               *
>> mon                                         advanced  public_network         
>>                 192.168.1.0/24                                               
>>                               *
>> 
>> root@ceph-01:~# ceph osd find 1
>> {
>>    "osd": 1,
>>    "addrs": {
>>        "addrvec": [
>>            {
>>                "type": "v2",
>>                "addr": "192.168.1.212:6800",
>>                "nonce": 811374774
>>            },
>>            {
>>                "type": "v1",
>>                "addr": "192.168.1.212:6801",
>>                "nonce": 811374774
>>            }
>>        ]
>>    },
>>    "osd_fsid": "3abeb495-fe1f-4d4a-8263-b920f552681e",
>>    "host": "ceph-02.tinihub.com",
>>    "crush_location": {
>>        "host": "ceph-02",
>>        "root": "default"
>>    }
>> }
>> 
>> 
>> public_network                         192.168.1.0/24
>> 
>> root@ceph-01:/etc/netplan# telnet 192.168.1.212 6800
>> Trying 192.168.1.212...
>> Connected to 192.168.1.212.
>> Escape character is '^]'.
>> ceph v2
>> ^]
>> telnet> quit
>> Connection closed.
>> 
>> root@ceph-01:/etc/netplan# telnet 192.168.1.212 6801
>> Trying 192.168.1.212...
>> Connected to 192.168.1.212.
>> Escape character is '^]'.
>> ceph v027\0b^]
>> telnet> quit
>> Connection closed.
>> 
>> 
>> cluster_network                        192.168.2.0/24
>> 
>> root@ceph-01:/etc/netplan# telnet 192.168.2.211 6800
>> Trying 192.168.2.211...
>> Connected to 192.168.2.211.
>> Escape character is '^]'.
>> ceph v2
>> ^]
>> telnet> quit
>> Connection closed.
>> root@ceph-01:/etc/netplan# telnet 192.168.2.211 6801
>> Trying 192.168.2.211...
>> Connected to 192.168.2.211.
>> Escape character is '^]'.
>> ceph v027}/^]
>> telnet> quit
>> Connection closed.
>> 
>> 
>> 
>> root@ceph-01:/etc/netplan# ls
>> 00-installer-config.yaml  01-installer-config.yaml
>> root@ceph-01:/etc/netplan# cat 00-installer-config.yaml
>> # This file is generated from information provided by the datasource.  
>> Changes
>> # to it will not persist across an instance reboot.  To disable cloud-init's
>> # network configuration capabilities, write a file
>> # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
>> # network: {config: disabled}
>> network:
>>    ethernets:
>>        ens18:
>>            dhcp4: false
>>            addresses:
>>              - 192.168.1.210/24
>>            routes:
>>              - to: default
>>                via: 192.168.1.254
>>            nameservers:
>>              addresses:
>>                - 192.168.1.201
>>    version: 2
>> root@ceph-01:/etc/netplan# cat 01-installer-config.yaml
>> # This file is generated from information provided by the datasource.  
>> Changes
>> # to it will not persist across an instance reboot.  To disable cloud-init's
>> # network configuration capabilities, write a file
>> # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
>> # network: {config: disabled}
>> network:
>>    ethernets:
>>        ens19:
>>            dhcp4: false
>>            addresses:
>>              - 192.168.2.211/24
>>            nameservers:
>>              addresses:
>>                - 192.168.1.201
>>    version: 2
>> 
>> 
>> 
>> Regards
>> Dev
>> 
>>> On Jun 22, 2025, at 1:50 AM, Michel Jouvin <michel.jou...@ijclab.in2p3.fr> 
>>> wrote:
>>> 
>>> d of ok before the upgrade, for me there is no reason to reformat OSDs or 
>>> change anything to the cluster c
>> 
>> _______________________________________________
>> ceph-users mailing list -- ceph-users@ceph.io
>> To unsubscribe send an email to ceph-users-le...@ceph.io
> 
> 
> _______________________________________________
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io

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

Reply via email to