I am having an issue configuring a failover pair to use a /25 subnet for the acquisition LAN interface.
When using a /25 subnet, it won't connect the databases.
Basically, the failover connectivity won't work if we use a /25 subnet. Is this a known issue or perhaps a software bug?
Could this be related to the IP configuration of the cassandra databases? Do you have to manually define the broadcast address in the YAML file to be for a /25 instead of a /24?
Michael, that’s indeed a strange one, we’ll have to dig deeper in order to provide an explanation for this.
Just wanted to mention that DataMiner Failover itself doesn't really care what the network mask is.
The configuration (IP + mask) get applied on the network interface, and from there typical networking rules apply. You'll have your network interface with a local IP address with its mask and at times a virtual IP address with its mask.
If there would be further issues reaching a certain IP address, my main advice would be to start by looking at the ipconfig and routing configuration, along with running tools like ping or tracert.
UPDATE: If you initially deploy the failover repair in a /25 (255.255.255.128), it seems to not work, but if you first setup failover in /24 (255.255.255.0), then switch to /25 it seems to work just fine.