Reply

Unable to remove a GRID member from a GRID

aceacero
Techie
Posts: 2
1521     0

I have a grid with 6 members.

I must to remove all members, leaving only the master pair in HA.

 

When trying to remove a member shows message "can't remove because is member of a DHCP failover".

I will try to remove failover association, but shows message "can't remove because failover association is currently asssigned to range range xxx-yyy"

 

Is ther any way to remove all fileover association from all subnets or ranges? or must I go one per one to change?

 

I must to remove the 5 member grids...:-(

 

 

Re: Unable to remove a GRID member from a GRID

Adviser
Posts: 80
1522     0

You must remove all configuration items related to this member first. If there are failover assocociations configured, you could try to export the configuration (infoblox .csv format), edit/add the ranges to the export and import the new .csv configuration. This is how I do bulk changes. You can also write a Perl script or use the REST WAPI to do this, but this requires programming skills.

Re: Unable to remove a GRID member from a GRID

TTiscareno Community Manager
Community Manager
Posts: 340
1522     0

To add to this- the CSV export/import idea is the way to go and will help make short work of this for you. In newer versions of NIOS, you will find a global export feature. Using this, you can export all networks and ranges, modify the resulting CSV output and then import in the changes that you want to make. To do this:

 

  1. Navigate to the Data Management tab in your Grid Manager GUI.
  2. Click on the CSV Job Manager button in the toolbar on the right hand side of the page.
  3. Switch to the CSV Export tab.
  4. Click on the "New CSV Export job" button (just to the left of the delete button).
  5. Uncheck the "All Objects" check box to clear all selected items.
  6. Enable the check boxes for "IPv4 Network".
  7. Click on the "Export Data" button.
  8. Once the job completes (and this will probably take a while to run), save the CSV output if prompted (will depend on your browser settings) and then click on the Close button.
  9. Repeat the same steps again, but for step 6, select "IPv4 DHCP Ranges" instead.
  • Note: You can export the networks and ranges at the same time but doing so separately would make it easier to modify the data output without worrying about corrupting the data on accident.

 

Once the exports have completed, open the files using a spreadsheet program (Excel, etc) and remove any columns that are not required (the column name for the header row will be appended with an asterisk), and that you do not intend to modify. Be sure to also remove any rows for networks and ranges that you do not want to modify and which you can easily do when sorting the data.

 

For your use case, the syntax might look like the following:

 

  header-network,address*,netmask*,dhcp_members,network_view

  network,172.31.0.0,255.255.240.0,"server1.infoblox.local,server2.infoblox.local",default

 

  header-dhcprange,end_address*,start_address*,failover_association,member,network_view

  dhcprange,10.60.27.175,10.60.27.160,,server1.infoblox.local,default

 

Note: If you are not using network views and it shows as 'default' for all of your networks and ranges, you can omit that column as well.

 

 

Using these examples:

 

For networks, you would replace the server name(s) to be the servers that you want to use for these networks and ranges, or leave it blank altogether to leave the networks unassigned.

 

For ranges, you would either clear out the name under the failover_association column for any rows that contain the DHCP Failover Association name in question, or employ a global search and replace to change the failover association name from the one you are removing to the one you will want to use going forward. If you no longer want to assign the ranges to a failover association, fill out the name for the Grid member that you want to assign to these ranges (this same server must also be assigned at the network level), or leave both the failover_association and member columns blank (where applicable) to leave them unassigned (this converts them to a 'reserved range'.

 

For further reference and details on how the CSV file should be structured, refer to the CSV Import Reference Guide. This can be found through the help panel in your Grid Manager GUI, or through our Support site (https://support.infoblox.com/).

 

Once the CSV file has been structured the way you are looking for, you can then import this back in to update the networks and ranges. This might be easiest to do in one step by combining the CSV data into a single file so that NIOS can apply the changes as appropriate; otherwise, you will most likely see errors as you would need to do this in a specific order:

 

  1. Update all ranges, unassigning the failover associations and member assignments, converting the ranges to a 'reserved range'
  2. Update the networks, changing the Grid member assignments as required.
  3. Update the ranges, changing the Grid member or DHCP failover assignments as required.

To run the CSV import to update the networks and ranges:

 

  1. Navigate to the Data Management tab in your Grid Manager GUI.
  2. Click on the CSV Job Manager button in the toolbar on the right hand side of the page.
  3. Click on the "New CSV Import job" button.
  4. Set the "Type of import" to "Override" and click Next.
  5. Browse to the updated CSV file that you want to import.
  6. Toggle the "On error" option to "Skip to the next row and continue" and click Next.
  7. Verify that the data looks correct in the preview window and click Import.

If any errors are reported, view the resulting error output and verify that the syntax in your CSV file is correct.

 

Note: A service restart will be required for these changes to take effect. Once done, you will need to delete the failover association, or modify it to no longer use the Grid member(s) that are being removed. After that, you can verify that everything has been cleaned up by navigating to Data management -> DHCP -> Members/Servers and clicking on the name for the Grid member that is being removed. If everything has been fully cleaned up, no results should be displayed for the Grid member.

 

Regards,

Tony

Showing results for 
Search instead for 
Do you mean 

Recommended for You