Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

  • Upload the new software to the Grid Master, as described in Uploading NIOS Software below.
  • Distribute the software upgrade files, as described in Distributing Software Upgrade Files below.
  • Optionally, test the upgrade, as described in Testing Software Upgrades below.
  • Perform the software upgrade, as described in Performing Software Upgrades below.

Before upgrading, Infoblox recommends that all members in the Grid be connected to the network and operating normally. If one or more members are offline when you upgrade the Grid, they automatically receive the distributed software and upgrade when they join the Grid or come back online.

...

When you upgrade from NIOS 6.4.0 to a later release, you can start, stop, or restart DNS and DHCP services, or only the DHCP service on a member that has not been upgraded. When you start, stop, or restart other services, such as reporting or file distribution, the operation is put in queue for execution until after the targeted member has been upgraded.

...

Uploading NIOS Software

...

...

After you download the NIOS software upgrade to your management station, upload it to the Grid Master, as follows:

...

Note: When you upload the NIOS software upgrade to an HA Grid Master, only the active node receives the software. The passive node does not. Therefore, if the Grid Master fails over before a distribution starts, you must upload the software again. If you do not, the distribution fails because the new active node does not have the uploaded software.

...

Distributing Software Upgrade Files

Distributing

...

Distributing the software upgrade files involves unpacking the software files and loading the new software. When you perform a distribution, the NIOS appliance loads the new software code into an alternate disk partition, which overwrites any previously saved version of code that is already there. Therefore starting the distribution disables the appliance from reverting to a release prior to the current version.
The time this process takes depends on the number of appliances to which the software is distributed; the more appliances, the longer it takes. Therefore, you might want to schedule the Grid distribution during times when your network is less busy. You can distribute the software immediately or schedule the distribution of any software upgrade file, even if it is not Upgrade Lite compatible.

...

The Grid Master distributes the software upgrade to each member in the Grid, including itself. As an alternative to scheduling the Grid distribution (see Scheduling Distributions below), you can distribute the software upgrade throughout the Grid immediately, as follows:

...

The distribution starts and if there is an active distribution scheduled, the appliance changes its status to inactive. The appliance distributes the upgrade files and displays the status of the distribution in the status bar. You can pause, resume, or stop the distribution by clicking the corresponding icon in the status bar. For information, see Managing Distributions below.
Note that starting a manual distribution cancels a scheduled distribution.

...

Scheduling Distributions

When you schedule a distri Anchorbookmark1115bookmark1115butiondistribution, you schedule the distribution of the Grid Master as well as the upgrade groups, including the Default group. The Grid Master distribution must always occur before the distribution of the upgrade groups.
To schedule a software distribution:

  1. From the Grid tab, select the Upgrade tab, and then click Distribute -> Schedule Distribution from the Toolbar.
  2. In the Schedule Distribution editor, complete the following:
    • Activate Distribution Schedule: Select this to enable the distribution schedule. Clear this if you are creating a distribution schedule you plan to activate at a later date. You can configure and save information in this editor even when you deactivate a scheduled distribution.
    • Grid Master Distribution Start Information: Enter a Grid Master distribution date, time, and time zone. The distribution date and time must be before those of the upgrade groups.
      • Date: Enter a start date of the Grid Master distribution 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 distribution in hh:mm:ss AM/PM (hour:minute:second in AM or PM) format. You can also 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 selecting the Grid and member time zones, see Managing Time Settings.)
      • Admin Local Time: Displays the Grid Master distribution start date and time in the time zone of the administrator, as explained in Creating Local Admins.
    • In the upgrade group table, specify the following for each upgrade group by clicking the corresponding field in each row:
      • Start Distribution: Specify when the distribution occurs. Select one of the following from the drop-down list:
        • Date/Time: Select this to configure the distribution 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. When 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 Distribution.
        • Date: Enter a distribution 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 a distribution 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.) To change the default time zone of the upgrade group, change the time zone of the first group member, as explained in Adding Upgrade Groups.
        • Admin Local Time: Displays the start date and time in the time zone of the administrator, as explained in Creating Local Admins.
        • Distribute to Members: Indicates whether the distribution 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.
  3. Save the configuration and click Restart if it appears at the top of the screen.

...

When the distribution successfully completes, the appliance updates the distribution status and sets the schedule, if configured, to inactive. The new software is now staged on all member appliances and is ready for use. Grid Manager displays the software version in the Distribution field in the Grid Version Information section.

...

Information section.

Managing Distributions

After you start a distribution, you can pause, resume, or stop it. For information, see Pausing and Resuming Distributions and Stopping Distributions below. Grid Manager displays the status of the overall distribution as well as the status of individual members. You can view this information in the Upgrade tab.

...

Pausing and Resuming Distributions

The following are some operational guidelines for performing a distribution:

...

The Grid Distribution Status bar indicates the distribution is paused. For information about the distribution status of each member, see Monitoring Distribution and Upgrade Status below.
To skip a member from a distribution:

...

Members that have not completed or started distributions that were scheduled at an earlier time resume the distribution.

...

Stopping Distributions

You can stop a distribution immediately, for example, if there are offline members and you do not want to wait for them to come back online, or if you realize that you have uploaded the wrong software version. When you stop a distribution, you can do the following:

...

  1. From the Grid Distribution Status bar, click the Stop icon.
  2. When the appliance displays a dialog box confirming that you want to stop the distribution, click Yes to continue.

...


...

Testing Software Upgrades

...

After you successfully distribute a software upgrade to the Grid Master, you can test an upgrade on the Grid Master before actually implementing it. This allows you to resolve potential data migration issues before the actual upgrade. The length of time the upgrade test takes depends on the amount of data and the difference between the current NIOS version and the software upgrade. The test does not affect NIOS services and you can perform other administrative tasks during the upgrade test.
To start an upgrade test:

...

Note that if an admin restarts the Grid services or reboots the Grid Master, or if an HA failover occurs on the Grid Master during the upgrade test, the appliance automatically stops the test. The appliance always resets the status of the Grid to "Distributed" when it stops the upgrade test.
If the appliance encounters an error during the test, it stops the test and displays a message in the Upgrade Status panel indicating that the upgrade test failed and the reason for the failure, such as a data translation error or data import error. You can review the syslog for specific error messages before downloading the Support Bundle and contacting Infoblox Technical Support.
After the test successfully finishes, the appliance displays a message confirming that the test upgrade is complete. You can then perform the actual upgrade as described in Performing Software Upgrades below.

...

Performing Software Upgrades


Performing

...

Performing a software upgrade involves rebooting the appliances and then running the new software. Essentially, each appliance switches between the two software partitions on its system, activating the staged software and saving the previously active software and database as backup.

...

Note: Before you upgrade the software, Infoblox recommends that you back up the current configuration and database. For information, see Backing Up Files9.


Depending on your upgrade paths, you can upgrade to a new release immediately or you can schedule the upgrade. For information about how to upgrade immediately, see Upgrading the Grid Immediately below. Before you schedule an upgrade, ensure that you understand the limitations, as described in Managing Upgrade Groups. For information about how to schedule an upgrade, see Scheduling Upgrades below.

...

...

Upgrading the Grid Immediately

For unschedulable full upgrades, all the Grid members in the Grid must upgrade at the same time. For lite upgrades and schedulable full upgrades, you can schedule the upgrades as described in Scheduling Upgrades below, or you can upgrade all the Grid members at the same time.
To upgrade a Grid immediately:

...

Note: The Grid upgrades immediately and if there is an active upgrade schedule, it becomes inactive.

...

Scheduling Upgrades

You can schedule lite up Anchorbookmark1124bookmark1124grades lite upgrades and full upgrades for certain NIOS versions. For limitations about scheduling a full upgrade, see Managing Upgrade Groups. When you schedule an upgrade, you schedule the upgrade for the Grid Master and the upgrade groups, including the Default group. The Grid Master must always upgrade before the upgrade groups. Depending on your upgrade paths, you can schedule the upgrade for the Grid Master and upgrade groups at different times over a period of nine days. If you schedule an upgrade that takes more than nine days, the appliance displays a warning.
To schedule an upgrade:

  1. From the Grid tab, select the Upgrade tab, and then click Upgrade -> Schedule Upgrade from the Toolbar.
  2. 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 Anchorbookmark1125bookmark1125tributiondistribution.
    • 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 Settings12.)
      • 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 below. 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 Settings12.) 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Ā 
  3. Save the configuration.

The appliance does not save the schedule and displays an error message if the schedule contains the following:

...

      • .
  1. Save the configuration.

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 now:

  1. From the Grid tab, select the Upgrade tab, and then click Toggle Group List View.
  2. In the Group List view, click the Upgrade Group Now icon in the upgrade group row. Grid Manager immediately upgrades the selected group.

...

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 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 below.
Otherwise, the appliance confirms that the schedule is saved and indicates whether the upgrade schedule is active.

Resolving Upgrade Warnings

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:

  1. From the Grid tab, select the Upgrade tab.
  2. Pause the upgrade.
  3. Click Toggle Member List View, and select the member check box from the table.
  4. From the Toolbar, click Upgrade -> Upgrade Single Member, and then click Toggle Group List View.
  5. In the Group List view, click the Upgrade Group Now icon in the upgrade group row. Grid Manager immediately upgrades the selected membergroup.

...

Upgrading a Single Member

...

Immediately

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 revert upgrade 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:

  1. From the Grid tab, select the Upgrade tab.
  2. Pause the upgrade.
  3. Click Toggle Member List View, and then select the member check box.
  4. 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).
Anchorbookmark1129bookmark1129 Figure 10.1 Upgrade Sequence for an HA Grid Master and Grid Members
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
HA Grid Master
The passive node (Node 2) of the Grid Master upgrades.
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
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. 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:

  1. From the Grid tab, select the Upgrade tab.
  2. Pause the upgrade.
  3. Click Toggle Member List View, and select the member check box from the table.
  4. From the Toolbar, click Upgrade -> Upgrade Single Member. Grid Manager immediately upgrades the selected member.

Reverting a Single 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 upgrade is paused and you have reverted a member in an upgrade group that has already completed the upgrade, you must move the member to another upgrade group that has not been upgraded before you can proceed with the upgrade.

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 below. 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:

  1. From the Grid tab, select the Upgrade tab.
  2. Pause the upgrade.
  3. Click Toggle Member List View, and then select the member check box.
  4. 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 the following figure 10.1 (for an HA Grid Master) and figure 10.2 (for a single Grid Master).


Figure 10.1 Upgrade Sequence for an HA Grid Master and Grid Members


Drawio
border1
baseUrlhttps://infoblox-docs.atlassian.net/wiki
diagramName10.1
zoom1
custContentId7083337
pageId22251217
lbox1
contentVer1
revision1


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.
Image Removed
554NIOS Administrator Guide (Rev. A)NIOS 8.1
Upgrading NIOS Software
Anchorbookmark1130bookmark1130.



Figure 10.2 Upgrade Sequence for a Single Grid Master and Grid Members Image Removed


Drawio
Image Removed
border
Image Removed
1
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
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.
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Image Removed
Grid
1FailoverActive3Passive4 2Node 1Node 2212Node 2 (passive) of the HA member and the single member upgrade.
HA Grid Member3The HA member fails over from Node 1 to Node 2.
4Node 1 (now passive) of the HA member upgrades.
Single Grid Member
baseUrlhttps://infoblox-docs.atlassian.net/wiki
diagramName10.2
zoom1
custContentId8656166
pageId22251217
lbox1
contentVer1
revision1



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.

...

Managing Upgrades

...

...

During an upgrade, Grid Manager displays a system message at the top of the screen indicating the Grid is being upgraded. After you start an upgrade, you can pause or resume it. For information, see Pausing and Resuming Upgrades UpgradesĀ and Monitoring Distribution and Upgrade Status below.

...

Pausing and Resuming Upgrades

The following are some operational guidelines for performing an upgrade:

...

To pause an upgrade, from the Grid Upgrade Status bar, click the Pause icon. When you pause an upgrade, Grid Manager displays a system message at the top of the screen indicating the upgrade is paused, until you resume the upgrade. For information about the upgrade status of each member, see Monitoring Distribution and Upgrade Status bookmark1133.
Image Removed
NIOS 8.1NIOS Administrator Guide (Rev. A)555
Managing NIOS Software and Configuration Files
below.

To resume an upgrade:

  1. From the Grid Upgrade Status bar, click the Resume icon.
  2. When the appliance displays a dialog box confirming that you want to resume the upgrade, click Yes to continue.

Members that have not completed or started upgrades that were scheduled at an earlier time resume the upgrade.

...

Monitoring Distribution and Upgrade

...

Status

During a distribution or an upgrade, Grid Manager displays the status of the distribution or upgrade in the status bar. It also displays the process status for each member. You can view the status in either the Member List view or Group List view from the Grid tab -> Upgrade tab.
When you perform a distribution or an upgrade, the status bar displays the overall Grid distribution status with a progress bar that describes the process being performed. The status bar also displays the number of members that have completed the distribution or upgrade.
A difference between a distribution and an upgrade process is that during an upgrade, the Grid Manager session terminates when an HA Grid Master fails over from Node 1 to Node 2, or when a single Grid Master reboots and goes offline. You can log back in to the appliance after the upgrade.

...

Grid and Member Status

You can view the distribution Anchorbookmark1136bookmark1136 and upgrade process status at the Grid and member level. To view the process status, from the Grid tab, select the Upgrade tab, and then click Toggle Member List View.
The status bar displays the status of the overall Grid process. It contains a progress bar that indicates the percentage of completion. It also shows the number of members that have completed the process.
Grid Manager displays the following information for each member:

...

You can view the distribution or upgrade status of an upgrade group in the group list view. In this view, the distribution or upgrade status rolls up to the group level. You can expand an upgrade group to view the status of individual member. However, you cannot view detailed status of a selected member from this view.
Image Removed
556NIOS Administrator Guide (Rev. A)NIOS 8.1
Downgrading Software
To view the process status of an upgrade group, from the Grid tab, select the Upgrade tab, and then click Toggle Group List View. Grid Manager displays the following information for each member in an upgrade group:

...