Page tree

Contents

NIOS comes with its own hardware box (appliance) on which NIOS will be installed.  Ensure that you verify the hardware that you receive. 

Verifying the Hardware

To verify the secure delivery of the hardware:

  • Use the tracking number of the order to review the status of the shipment.
  • Inspect the tamper-evident seals for any signs of tampering.
  • Verify the product by comparing the shipping slip with the invoice.

Prerequisites

Before you begin the configuration, ensure that you have all the necessary components. The following are needed and must be acquired before continuing with this guidance:

  • Supported NIOS appliances
  • A management station or computer from which you configure and manage the NIOS appliance. See Support Matrix for the system and browser requirements.
  • The IP address of the appliance on your network.

Supported Appliances

For the list of supported physical appliances and virtual appliances that NIOS is supported on, see the Release Notes.

Downloading the NIOS Software

You can download NIOS from the Infoblox Support web site at https://support.infoblox.com/. You must be a registered user to access this web site. 

To download the software:

  1. Log on to the Infoblox Support web site at https://support.infoblox.com/
  2. Click the Downloads tab.
  3. Select NIOS/vNIOS from the Infoblox Software drop-down list.
  4. Select the General maintenance products with full engineering support for routine patches and bug fixes on all significant issues option.
  5. Select NIOS 8.6.1 from the Select version drop-down list.

The NIOS installer files are available for download. The installer files are of two sizes:

  • Files of size 250 GB
  • Files of size 70 GB

Infoblox recommends using a minimum size of 70 GB for any of these files that has resizable as part of the file name and you can resize them depending on your requirement and deployment.

If you download the resizable files, a default disk size is defined on the VM. You then change the default disk size using the VMware UI. When you start the VM for the first time, NIOS detects how much disk space has been reserved for the virtual disk and allocates partitions within that space. You can increase the disk size upto a maximum of 2.5 terabytes. 

If you want to resize the disk space from the current 250 GB to a lower size, remove the member from the Grid and add a replacement member with the required disk size. If you want to resize a smaller disk to a higher size, back up the Grid database, and deploy the new instance with the required disk size. After the deployment, restore the backed up database. Infoblox recommends configuring a scheduled backup so that if the disk limit is reached and the system is unresponsive, the earlier backup can be restored.

Infoblox recommends configuring instances of only 250 GB and higher as Grid Master and Grid Master Candidate.

Note

  • Images of types .vhd and .raw comprise only one file each and can be resized. The minimum size of the .vhd image is 250 GB and that of the .raw image is 43 GB.
  • Infoblox recommends that you provision 70 GB or more disk space for the NIOS instance while deploying resizable images.
  • If you add members to a FIPS mode -enabled Grid Master, ensure that the members have the same NIOS build version. That is, the same NIOS build must be installed on Grid Master and members before joining. You can perform upgrades and install hotfixes in FIPS mode.

Limitations of Using the Scalable Image File

The following are the limitations of using the scalable NIOS image:

  • You can use the scalable image only on the following appliances: IB-V805, IB-V1405, IB-V2205, IB-V4005, IB-V815, IB-V825, IB-V1415, IB-V1425, IB-V2215, IB-V2225, IB-V4015, IB-V4025, IB-FLEX, CP-V805, CP-V1405, CP-V2205.
  • If you use ovftool to deploy the OVA image, there is no command line option to increase the disk-size. As a workaround, you can use ovftool to upload the image but before powering on the VM, you will need to use the UI to change the disk size based on your requirement.
  • The Parental Control feature fails to start because of no space left on the device when downloading Zvelo data.
  • The primary disk size is full if you enable the bloxTools service on the member provisioned with the lower disk size.
  • Infoblox recommends to not run DNS/DHCP/updates on the member provisioned with the lower disk size.
  • Do not try to join a resizable disk image to a Grid running an NIOS version earlier than 8.5.
  • Infoblox does not recommend auto-synchronizing or downgrading resizable disk images to NIOS versions earlier than 8.5.
  • If you have resizable members whose provisioned disk space is lower than 85 GB, disable the rsync-batch mode by running the set upgrade_dist rsync_batch disable command on Grid Master.
  • If you have a reporting member as part of your Grid, then you must have a minimum disk space of 250 GB by default.

 

  • No labels

This page has no comments.