setting up samba cluster in a storage cluster spanning multiple subnets

Solution In Progress - Updated -

Issue

Suppose there is a storage cluster where few nodes (usually half of the nodes) are in one sub network and the remaining nodes are in a different sub network. And the 2 subnets are managed by a vLAN. In such deployments, lets assume the 1st subnet has IP address 10.100.x.y and the second subnet has the IP address range in 10.200.x.y (It can be anything. 10.a.b.c is just an example. The main thing here is to understand that there are 2 different IP address ranges belonging to 2 different subnets).

In such cases, setting CTDB or a samba cluster across all the nodes of the storage cluster becomes difficult. Because, the public virtual ip address (to be updated in the file /etc/ctdb/public_address) to be used by the smb clients should always be reachable. Suppose, the virtual public IP address is 10.200.20.20. Then if that VIP gets assigned to a node from 1st subnet (whose IP address range is 10.100.x.y), then the smb clients might not be able to reach the samba server. This is because, the address 10.200.20.20 referred by the smb clients will always gets resolved to 2nd subnet by the vLAN. But CTDB has assigned the public IP address to a node from the 1st subnet.

This leads to not being able to access the volume via SMB

Environment

  • RHGS-3.1
  • RHGS-3.2
  • RHGS-3.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content