Infoblox frequently releases updated NIOS software. Contact Infoblox Technical Support to learn which file name to use when downloading a new upgrade file, or watch your email for periodic notifications that a new software upgrade is available. To get the latest upgrade, your local network must be capable of downloading a file from the Internet.
After you download and store the new upgrade file on your local network, complete the following tasks to upgrade an Infoblox independent appliance or a Grid.
...
- From the Grid tab, select the Upgrade tab, and then click Upgrade -> Schedule Upgrade from the Toolbar.
- In the Upgrade Schedule editor, complete the following:
- Activate Upgrade Schedule: Select this to enable the upgrade schedule. Clear it if you are creating an upgrade schedule that you plan to activate at a later date. You can configure and save information in this editor even when you deactivate a dis
tribution.Anchor bookmark1125 bookmark1125 - Grid Master Upgrade Start Information: Enter a Grid Master upgrade date, time, and time zone. The date and time must be before those of the upgrade groups.
- Date: Enter a start date of the Grid Master upgrade in YYYY-MM-DD (year-month-day) format. You can click the calendar icon to select a date from the calendar widget.
- Time: Enter a start time of the Grid Master upgrade in hh:mm:ss AM/PM (hour:minute:second in AM or PM) format. You can select a time from the drop-down list.
- Time Zone: Select a time zone that applies to the start time you enter. If this time zone is different from the Grid time zone, the appliance converts the time you enter here based on the Grid time zone, after you save this schedule. When you display this schedule again, it displays the converted time. Selecting the time zone here does not affect any time zone settings in the Grid. (For information about setting the Grid and member time zones, see Managing Time Settings 12.)
- Admin Local Time: Displays the Grid Master upgrade date and start time in the time zone of the administrator, as explained in Creating Local Admins .
- In the upgrade member table, specify the following by clicking the corresponding field in each row:
- Group: The name of the upgrade group. You can assign a different upgrade group by selecting the group from the drop-down list.
- Group Members: When you expand an upgrade group, this field displays the group members.
- Warning: This field turns yellow when there is a conflict among the upgrade groups. Hover your mouse over the field and the tooltip displays the member that contains the conflict. It also displays recommended upgrade groups in the Group column so you can change the group assignment to resolve the conflict. The tooltip can display one of the following: GMC, DNS Primary, DHCP Logging Member, or DHCP Failover. For information about how to resolve a conflict, see Resolving Upgrade Warnings . Select an upgrade group from the drop-down list in the Group column to assign a different upgrade group. Click Validate and Refresh to validate the new group assignment.
- Start Upgrade: Specify when the upgrade occurs. Select one of the following from the drop-down list:
- Date/Time: Select this to configure the upgrade start date, time, and time zone.
- After <group> : Select After Grid Master to start the distribution immediately after the completion of the Grid Master distribution. Select an upgrade group that must complete its distribution before the group you are configuring. If you select this option, you cannot enter a date, time, and time zone.
Date, Time, and Time Zone are enabled only when you select Date/Time for Start Upgrade.
- Date: Enter an upgrade start date in YYYY-MM-DD (year-month-day) format. You can click the calendar icon to select a date from the calendar widget.
- Time: Enter an upgrade start time in hh:mm:ss AM/PM (hour:minute:second in AM or PM) format. You can select a time from the drop-down list.
- Time Zone: By default, the appliance displays the time zone of the first Grid member in the Upgrade Group. You can change this time zone, if you want to enter the time using a different time zone. After you save the schedule though, the appliance converts the time you entered to the time zone of the upgrade group, if it is different. (For information about setting the Grid and member time zones, see Managing Time Settings 12.) To change the default time zone of an upgrade group, change the first group member in the Upgrade Group list, as explained in Adding Upgrade Groups on page 544.
- Admin Local Time: Displays the data and time in the time zone of the administrator, as explained in Creating Local Admins .
- Upgrade Members: Indicates whether the upgrade within the group occurs simultaneously or sequentially. You cannot edit this field here. You define this when you create the upgrade group. To change this setting, see Modifying Upgrade Groups
- Activate Upgrade Schedule: Select this to enable the upgrade schedule. Clear it if you are creating an upgrade schedule that you plan to activate at a later date. You can configure and save information in this editor even when you deactivate a dis
- Save the configuration.
The appliance does not save the schedule and displays an error message if the schedule contains the following:
- Circular dependencies between upgrade groups; for example, the upgrade of Group A is scheduled after Group B, and the upgrade of Group B is scheduled after Group A.
- The upgrade time is in the past.
The appliance also does not save the schedule and displays an error message if the schedule contains the following:
- Circular dependencies between upgrade groups; for example, the upgrade of Group A is scheduled after Group B, and the upgrade of Group B is scheduled after Group A.
- The upgrade time is in the past.
The appliance also does not save the schedule and displays a warning when there is a group assignment conflict. For information about how to resolve these conflicts, see Resolving Upgrade Warnings .
Otherwise, the appliance confirms that the schedule is saved and indicates whether the upgrade schedule is active.
...
The appliance can generate the following warnings when you schedule an upgrade:
- GMC: To resolve this warning, put all Grid Master candidates in the first upgrade group.
- DNS Primary: To resolve this warning, put all the members that are serving as DNS primaries in the first upgrade group.
- DHCP Logging Member: To resolve this warning, put the DHCP logging member in the first upgrade group.
- DHCP Failover: To resolve this warning, place the peers of a DHCP failover association in separate upgrade groups. Ensure that you schedule upgrades of the failover peers close to each other to minimize configuration rules. NIOS does not allow DHCP configuration changes that affect the communication between the peers until both peers are upgraded.
Upgrading Groups Immediately
After you schedule an upgrade with multiple upgrade groups, you can choose to immediately upgrade an upgrade group that has not been upgraded yet. This function is available only for scheduled upgrades.
To upgrade an upgrade group a warning when there is a group assignment conflict. For information about how to resolve these conflicts, see Resolving Upgrade Warnings .
Otherwise, the appliance confirms that the schedule is saved and indicates whether the upgrade schedule is active.
| Anchor | ||||
|---|---|---|---|---|
|
The appliance can generate the following warnings when you schedule an upgrade:
- GMC: To resolve this warning, put all Grid Master candidates in the first upgrade group.
- DNS Primary: To resolve this warning, put all the members that are serving as DNS primaries in the first upgrade group.
- DHCP Logging Member: To resolve this warning, put the DHCP logging member in the first upgrade group.
- DHCP Failover: To resolve this warning, place the peers of a DHCP failover association in separate upgrade groups. Ensure that you schedule upgrades of the failover peers close to each other to minimize configuration rules. NIOS does not allow DHCP configuration changes that affect the communication between the peers until both peers are upgraded.
Upgrading Groups Immediately
After you schedule an upgrade with multiple upgrade groups, you can choose to immediately upgrade an upgrade group that has not been upgraded yet. This function is available only for scheduled upgrades.
To upgrade an upgrade group now:
- From the Grid tab, select the Upgrade tab, and then click Toggle Group List View.
- In the Group List view, click the Upgrade Group Now icon in the upgrade group row. Grid Manager immediately upgrades the selected group.
| Anchor | ||||
|---|---|---|---|---|
|
After the Grid Master has been upgraded, you can choose to immediately upgrade a specific member that has not been upgraded yet. This function is available only for scheduled Grid upgrades from NIOS 6.4.0 to a later release. You can upgrade a single member only when the Grid upgrade is paused, and you cannot upgrade the Grid Master, reporting appliance, and an offline member. Once the member has been manually upgrades, the appliance skips this member when its scheduled upgrade time is reached.
To upgrade a specific member now:
- From the Grid tab, select the Upgrade tab, and then click Toggle Group List View.In the Group List view, click the Upgrade Group Now icon in the upgrade group row.
- Pause the upgrade.
- Click Toggle Member List View, and select the member check box from the table.
- From the Toolbar, click Upgrade -> Upgrade Single Member. Grid Manager immediately upgrades the selected groupmember.
| Anchor |
|---|
...
|
...
|
...
Reverting a Single Member
...
During an upgrade from NIOS 6.4.0 to a later release, you can choose to immediately upgrade revert a specific member that has not already been upgraded yet. This function is available only for scheduled Grid upgrades from NIOS 6.4.0 to a later release. You can upgrade a single and is within its revert time window. The revert single member feature is useful when you want to troubleshoot issues, such as service outages, on a specific member after it has been upgraded. You can revert a member only when the Grid upgrade is paused, and you cannot upgrade revert the Grid Master, reporting appliance, and an offline member. If the member you want to revert is in an upgrade group that has already completed the upgrade, and an offline member. Once the member has been manually upgrades, the appliance skips this member when its scheduled upgrade time is reached.
To upgrade a specific member now:
- From the Grid tab, select the Upgrade tab.
- Pause the upgrade.
- Click Toggle Member List View, and select the member check box from the table.
- From the Toolbar, click Upgrade -> Upgrade Single Member. Grid Manager immediately upgrades the selected member.
...
During an upgrade from NIOS 6.4.0 to a later release, you can revert a specific member that has already been upgraded and is within its revert time window. The revert single member feature is useful when you want to troubleshoot issues, such as service outages, on a specific member after it has been upgraded. You can revert a member only when the Grid upgrade is paused, and you cannot revert the Grid Master, reporting appliance, and an offline member. If the member you want to revert is in an upgrade group that has already completed the upgrade, you must move the member to another upgrade group that has not been upgraded.
Once a member is upgraded, the appliance starts counting down and displays the time that is left for you to revert this member. You can revert the member before the revert time window expires. The default time window to revert a member is 24 hours. You can view the time that is left to revert the member in the Member List view, as described in Grid and Member Status . You can also use the CLI commands set default_revert_window to configure the default revert time window for the Grid. For information about this command, refer to the Infoblox CLI Guide. Once a member exits the revert time window, you must revert the entire Grid in order to revert the member.
Note: You may potentially lose some data when you revert a member. The appliance keeps information about DHCP leases and DNS records intact.
To revert a specific Grid member during a scheduled Grid upgrade:
- From the Grid tab, select the Upgrade tab.
- Pause the upgrade.
- Click Toggle Member List View, and then select the member check box.
- From the Toolbar, click Revert -> Revert Single Member.
Grid Manager displays a message indicating that the revert process disrupts Grid services. Read the message carefully, and then click Yes to confirm your decision to revert the member. Be aware that when you revert a member, some changes made since the member was last upgraded may get lost.
Upgrade Process
...
Note: Grid members that do not have the correct NIOS version on their alternate partitions due to an incomplete distribution automatically resynchronize the NIOS version with the Grid Master, and then upgrade.
...
you must move the member to another upgrade group that has not been upgraded.
Once a member is upgraded, the appliance starts counting down and displays the time that is left for you to revert this member. You can revert the member before the revert time window expires. The default time window to revert a member is 24 hours. You can view the time that is left to revert the member in the Member List view, as described in Grid and Member Status . You can also use the CLI commands set default_revert_window to configure the default revert time window for the Grid. For information about this command, refer to the Infoblox CLI Guide. Once a member exits the revert time window, you must revert the entire Grid in order to revert the member.
...
Note: You may potentially lose some data when you revert a member. The appliance keeps information about DHCP leases and DNS records intact.
...
To revert a specific Grid member during a scheduled Grid upgrade:
- From the Grid tab, select the Upgrade tab.
- Pause the upgrade.
- Click Toggle Member List View, and then select the member check box.
- From the Toolbar, click Revert -> Revert Single Member.
Grid Manager displays a message indicating that the revert process disrupts Grid services. Read the message carefully, and then click Yes to confirm your decision to revert the member. Be aware that when you revert a member, some changes made since the member was last upgraded may get lost.
Upgrade Process
When an upgrade starts, Grid Manager checks if the nodes of an HA Grid Master have the same NIOS software version on their alternate partitions. If they do not have the same software version, the upgrade process stops. Grid Manager displays an error message and if it is a scheduled upgrade, Grid Manager deactivates the schedule as well. Otherwise, the upgrade process continues.
Note: During the upgrade, you can view the status of the Grid Master in the serial console.
During the upgrade, if a Grid member has not completed its distribution, it automatically resynchronizes with the Grid Master after the Grid Master upgrade is complete.
Due to the nature of the upgrade sequence, HA pairs fail over during the upgrade. Therefore, be aware that the active and passive nodes reverse roles. The order in which Grid members upgrade, including when HA pairs fail over, is shown in Figure 10.1 (for an HA Grid Master) and Figure 10.2 (for a single Grid Master).
| Anchor | ||||
|---|---|---|---|---|
|
HA Grid Master
The passive node (Node 2) of the Grid Master upgrades.
Grid2 FailoverActivePassive3 1Node 1Node 24FailoverActivePassive5 3Node 1Node 23123The Grid Master fails over from Node 1 to Node 2. At this point, the active Grid Master (Node 2) is using the upgraded code. All other nodes, including the passive node (Node 1) and all Grid members, rejoin the newly updated active node (Node 2). Since the NIOS version on these nodes does not match that of the active Grid Master, the nodes are directed to upgrade.
HA Grid Member
Node 1 (now passive) of the Grid Master upgrades. The passive node (Node 2) of the HA member and the single Grid member upgrade.
54The HA Grid member fail overs from Node 1 to Node 2.
Single Grid Member
Node 1 (now passive) of the HA member upgrades.
Note: Grid members that do not have the correct NIOS version on their alternate partitions due to an incomplete distribution automatically resynchronize the NIOS version with the Grid Master, and then upgrade.
554NIOS Administrator Guide (Rev. A)NIOS 8.1
Upgrading NIOS Software
| Anchor | ||||
|---|---|---|---|---|
|
Single Grid Master
Single Grid Master upgrades. All other members rejoin the newly updated Grid Master. Since the NIOS version on these nodes does not match that of the Grid Master, the nodes are directed to upgrade.
Grid
1FailoverActive3Passive4 2Node 1Node 2212Node 2 (passive) of the HA member and the single member upgrade.
HA Grid Member
3The HA member fails over from Node 1 to Node 2.
4Node 1 (now passive) of the HA member upgrades.
Single Grid Member
The Grid Manager session terminates when the HA Grid Master fails over from Node 1 to Node 2, or when the single Grid Master reboots and goes offline.
During a scheduled upgrade, the Grid members that have not upgraded yet can join the Grid and function normally until their scheduled upgrade time. When the upgrade finishes, the upgrade schedule is set to inactive.
...