Check your MTU. I think ospf has issues when fragmenting. Try setting your interface MTU to something obnoxiously small to ensure that anything upstream isn't fragmenting - say 1200. If it works try a saner value like 1496 which accounts for any vlan headers. If you're running in a spine/leaf you might just want to consider segregating Ceph replication traffic by interface and not network. <shrug> I'd also be interested in seeing any reference arch around Ceph in spine leaf that anyone has implemented. > On Nov 23, 2016, at 11:29 AM, Darrell Enns <darrelle@xxxxxxxxxxxx> wrote: > > You may also need to do something with the "public network" and/or "cluster network" options in ceph.conf. > > -----Original Message----- > From: ceph-users [mailto:ceph-users-bounces@xxxxxxxxxxxxxx] On Behalf Of Darrell Enns > Sent: Wednesday, November 23, 2016 9:24 AM > To: ceph-users@xxxxxxxx > Subject: Re: ceph in an OSPF environment > > As far as I am aware, there is no broadcast or multicast traffic involved (at least, I don't see any on my cluster). So there should be no issue with routing it over layer 3. Have you checked the following: > > - name resolution working on all hosts > - firewall/acl rules > - selinux > - tcpdump the mon traffic (port 6789) to see that it's getting through _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |