You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you have multiple servers that service a subnet with a pool you would set them up in a failover configuration. This works as expected.
Recently I had the need to service the same subnet from two non failover servers. The scenario was site1 and site2 can back each other up but only in a true disaster situation. The dhcp helpers on the routers would typically only be pointed at site1.. but if an outage of the site1 dhcp server happened I would adjust the helpers to site2. Yes i could set up failover but that is not the normal state I want the systems to run in.
What happened was that all the configurations on site2 were showing fine but the pools on each subnet would not be built. this is due to the way the build query is written so that it only finds the first server to build the pool against. If that is not the current server then it just skips over that pool definition.
need to adjust the code to be aware of the server network and pool relationship.
dont break failover configs however!
what other implications of doing the non failover/same pool design is there? Yes I know I could get allocations of dynamic IPs that are different between servers but for me they are temporary anyway.
The text was updated successfully, but these errors were encountered:
Currently if you have multiple servers that service a subnet with a pool you would set them up in a failover configuration. This works as expected.
Recently I had the need to service the same subnet from two non failover servers. The scenario was site1 and site2 can back each other up but only in a true disaster situation. The dhcp helpers on the routers would typically only be pointed at site1.. but if an outage of the site1 dhcp server happened I would adjust the helpers to site2. Yes i could set up failover but that is not the normal state I want the systems to run in.
What happened was that all the configurations on site2 were showing fine but the pools on each subnet would not be built. this is due to the way the build query is written so that it only finds the first server to build the pool against. If that is not the current server then it just skips over that pool definition.
need to adjust the code to be aware of the server network and pool relationship.
dont break failover configs however!
what other implications of doing the non failover/same pool design is there? Yes I know I could get allocations of dynamic IPs that are different between servers but for me they are temporary anyway.
The text was updated successfully, but these errors were encountered: