This is an old revision of the document!
Deploying an Infoblox Reporting Server in a Lab
Replacing old Reporting Licence with New
- Run
show license_uidon the Grid Manager - Create “Virtual Appliance” in the support portal using the Grid UID from step 1. Assign the Grid Wide reporting licence.
- Remove the old permanent reporting license from the Grid.
- Power off the old reporting server.
- Power on the new reporting server.
- Add the new reporting server to the Grid.
- And the new “Grid Wide” subscription reporting license to the Grid.
Useful Guide to replacing old reporting type with new reporting type
NOTE: You will need to run show license_uid to get the Grid UID.
NOTE: Even when you have a proper reporting licence, you will still need to set the permanent reporting license using the set temp_licence command on the reporting server after it has joined the Grid.
NOTE: When you add the extra logging disk, it can be as large as you like but it cannot be resized after deployment without redeploying the whole VM.
NOTE: Officially, Infoblox recommends provisioning the reporting disk of size greater than or equal to 250 GB.
To deploy an Infoblox Reporting server in a lab, you will need the same OVA file that you use to deploy the Grid Master/Grid Member VMs.
When you deploy the OVA file, select IB-5005 as the model number.
When the VM deploys, it will have 8 CPU cores and 64 GB of RAM. For a lab (e.g. VMware Workstation on your laptop) reduce this to something sensible such as 2 CPU cores and 8 GB RAM (or even less? I got it to boot with 1 CPU and 2Gb of RAM. However, I didn't 'test' it much after boot). As you are adjusting this, add a second data disk. This will be used for storing data and you can't add the NIOS IB-V5005 licence to the VM without it.
Power on the machine.
Run set temp_licence and add a NIOS licence and then select IB-V5005.
This restart the system.
Run set temp_licence and you should now see only three options instead of sixteen. Add a Grid licence (option #7).
Run set network to set the appropriate IP.
This restart the system.
Ensure that the Grid Master has a member entry for this appliance.
On this appliance, run set membership to join it to the Grid.
This restarts the system.
Log into the Grid Master and check that the member is connected by checking Grid > Grid Manger > Members.
Run set temp_licence and you should now see only three options instead of sixteen.
Choose option 3 “Add Reporting subscription license”. This installs a Reporting subscription grid-wide. It is this bit that adds the “Reporting” tab to the Grid Master GUI top banner.
NOTE: I have seen it before where the reporting appliance is already joined to the Grid. Even then, we consoled onto the reporting box and still only saw three options. We installed the Reporting subscription license on the reporting member and it popped up on the Grid wide licence tab.
Set the reporting settings by going to Grid > Grid Manager > Reporting > Services and clicking the “Edit” button the right.
Under General > Basic tick “Enable Data Indexing”. Then select the check boxes and enter the index percentages below this box. Where a category is ticked, it must be configured to have an index % greater than 0 and you cannot exceed 100%.
Save and close.
Go to the Grid Master Grid > Grid Manager > Reporting > Services.
Click the member and then click start (play button). It may take a few minutes to start up.
You should now be able to view the reporting server under the Reporting tab on the Grid Master.
