Initially we want to run the old and new deployments concurrently and want to use the same IP ranges for the new servers.
Eg:
Current deployment has single persona nodes, excluding out of band management (CIMC)
CPT_Admin1 - 10.12.13.2 (VlanX) Data
CPT_Admin2 - 10.12.13.3 (VlanX) Data
CPT_Mon1 - 10.22.23.4 (VlanY) Data
CPT_Mon2 - 10.22.23.5 (VlanY) Data
CPT_PSN1 - 10.22.23.6 (VlanY) Data
CPT_PSN2 - 10.22.23.7 (VlanY) Data
JHB_PSN1 - 10.32.33.2 (VlanZ) Data
JHB_PSN2 - 10.32.33.3 (VlanZ) Data
New deployment has shared persona nodes, including out of band management (CIMC).
[Primary]CPT_Shared1 (Admin,MnT,PSN) - 10.12.13.10 (VlanX) CIMC
10.22.23.50 (VlanY) Data
CPT_Health - 10.12.13.11 (VlanX) CIMC
10.22.23.51 (VlanY) Data
[Secondary]CPT_Shared2 (Admin,MnT,PSN) - 10.12.13.12 (VlanX) CIMC
10.32.33.3 (VlanZ) Data
Our understanding is that a new node starts up initially as a standalone node and it has to be manually registered in order to join a current deployment, so it cannot just automatically join or override a current primary admin node and its configurations even though they are able to reach each other on the network.
In addition, the only way that NADs can send auth traffic to the new deployment is when their IPs are configured as radius servers on the individual NADs, so having the new radius servers on the network would have no impact in terms of current production radius authentications.
Our plan is to complete the configuration on the new primary shared node, bring the other 2 online as well and register them to the primary shared node and complete the 2nd deployment. No changes will be made to the current production deployment.
