{"id":2773,"date":"2017-09-24T01:25:52","date_gmt":"2017-09-24T01:25:52","guid":{"rendered":"http:\/\/pariswells.com\/blog\/?p=2773"},"modified":"2017-09-24T01:27:56","modified_gmt":"2017-09-24T01:27:56","slug":"updating-nimbleos","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/random\/updating-nimbleos","title":{"rendered":"Updating NimbleOS"},"content":{"rendered":"

Updating NimbleOS<\/p>

<\/p>

The Basics<\/p>

Upgrading Nimble OS is something clients can complete easily and with confidence, thanks largely to the thorough pre-checks and verifications that are part of the process.<\/p>

If your arrays are communicating back to Nimble Support, InfoSight will be able to determine if there are updates available and present the GA versions of Nimble OS suitable (whitelisted) for your environment. Because InfoSight works to inoculate the WW install base from known issues, it may blacklist some Nimble OS versions from being available upgrade choices. Clients can discuss with Nimble Support in order to understand what changes may be required in the environment before safely being able to install a version currently blacklisted for your environment.<\/p>

Many clients perform upgrades during business hours however there is no shame in scheduling these outside of hours and when there is little workload running. Clients with a valid Support Status may contact Nimble Support anytime 24 x 7.<\/p>

Do not hesitate to contact Nimble Support on 1-800-751-916 https:\/\/www.nimblestorage.com\/customer-support\/<\/a><\/p>

<\/p>

This indicates there is a communication issue preventing the array from sending heartbeats and ASUP detail to Nimble Support and this should be resolved unless installed on a dark site.<\/p>

From InfoSight, Reports \u2013 Asset Report <\/em>you can verify Support status. Contact your local Nimble Representative if you need to renew your Support cover.<\/p>

<\/p>

Nimble Connection Manager<\/p>

 <\/p>

Install or Update Nimble Connection Manager<\/p>

Nimble Connection Manager (NCM) simplifies configuration on iSCSI, automatically creates the optimal number of iSCSI sessions for each Nimble volume and manages the selection of paths to the volumes.<\/p>

<\/p>

NCM is available for Linux, Windows\/Hyper-V and vSphere environments.<\/p>

Please refer to the latest VMware Integration Guide <\/em>which includes details for NCM installation\/upgrade and much more. Available for download from InfoSight (Resources<\/em><\/p>

\u2013 Documentation<\/em>).<\/p>

For Update Manager installs on 6.0 & 6.5 see: https:\/\/connect.nimblestorage.com\/thread\/11802<\/a><\/p>

NCM Version Compatibility With Nimble OS<\/p>

On the Nimble Validated Configuration Matrix, Select NCM for VMware Compatibility with Nimble OS<\/em>, from the drop down, select the version of Nimble OS <\/em>you are running OR planning to run after upgrading.<\/p>

<\/p>

NCM Version Compatibility With vSphere<\/p>

On the Nimble Validated Configuration Matrix, Select Nimble Connection Manager for VM<\/em>, you can then select from the drop down the vSphere Version <\/em>you are running OR planning to run after upgrading.<\/p>

<\/p>

Download NCM for VMware<\/p>

On the Nimble Validated Configuration Matrix, Resources \u2013 Software Downloads<\/em>, select Connection Manager (NCM) for VMware. Download the appropriate package for your vSphere version.<\/p>

<\/p>

From: NTS-2001-I Course<\/p>

One-click, zero-downtime Nimble OS upgrades<\/strong><\/p>

? Before you begin:<\/p>

\u2013 Check your current version<\/p>

\u2013 Obtain the most recent version<\/p>

\u2013 Check system health<\/p>

<\/p>

Selecting Different Versions<\/p>

? If you click Download<\/em>, you may be presented with different versions to upgrade to.<\/p>

<\/p>

Firmware<\/p>

Firmware<\/p>

<\/p>

1. Load new firmware to standby<\/p>

2. Reboot standby to run new rev.<\/p>

3. Load new firmware to other controller<\/p>

4. Reboot active to activate new rev. \u2013 causes failover and the<\/p>

standby becomes active<\/p>

<\/p>

From: Nimble GUI Administrator Guide<\/p>

Software Updates<\/strong><\/p>

Nimble Storage offers several ways to keep an array up-to-date, to improve its performance, and to increase data storage capacity. (The term upgrade <\/em>refers to Nimble array hardware.) The term update <\/em>refers to the NimbleOS software (NOS).<\/p>

Upgrades and Updates<\/strong><\/p>

There are multiple upgrade paths for hardware, as well as NimbleOS software updates available that can run on the array, depending on your array model. If you want to increase data storage capacity, you can add expansion shelves without having to perform an update or upgrade.<\/p>

Upgrades<\/strong><\/p>

Depending on which model of Nimble array you have, there are upgrade paths for the controllers and cache drives. An upgrade procedure is the same as replacing a controller or the cache SSDs. However, the new component is more powerful or has greater capacity.<\/p>

Contact Nimble Storage Support at www.nimblestorage.com\/support<\/em><\/a> when you want to upgrade.<\/p>

See the applicable upgrade quick start guide that ships with the upgrade component. The Nimble Storage<\/em><\/p>

Hardware Guide <\/em>also covers upgrades.<\/p>

Updates<\/strong><\/p>

The NimbleOS is the software that runs on the array. Nimble provides regular maintenance releases and periodic updates to the NimbleOS. Maintenance releases typically correct bugs and enhance features. Updates involve a major new release of the NimbleOS with new features and capabilities.<\/p>

If a NimbleOS update is available for your array, you can accomplish the update in less then an hour for each array in the group. (If you want to combine your Nimble arrays as members of a group, each of them must have the same version of NimbleOS 2.x or later installed.) The update procedure works on one controller at a time and results in a controller failover. To avoid any data service disruption, make sure that the initiators connected to the array have proper MPIO timeouts configured before performing the software update.<\/p>

If the Nimble Windows Toolkit (NWT) is not installed on the Windows hosts, be sure to configure timeout values appropriately. See Timeout Values <\/em>on page 233.<\/p>

The NimbleOS has an automated procedure to download and install updates. Or, you can download NimbleOS software at the Nimble Storage InfoSight\u2122 at https:\/\/infosight.nimblestorage.com<\/em>. If you do not have a user account, you can create one on your first visit.<\/p>

See Update the NimbleOS<\/em>.<\/p>

Find the NimbleOS Version<\/strong><\/p>

Procedure<\/strong><\/p>

To determine which version of the NimbleOS is installed on the array:<\/p>

1 <\/strong>In the NimbleOS GUI, choose Help <\/strong>> About Nimble Storage<\/strong>.<\/p>

2 <\/strong>Look for the Version number just below the Nimble Storage logo.<\/p>

3 <\/strong>Click OK <\/strong>to dismiss the dialog box.<\/p>

Download the NimbleOS Update File <\/strong>This task is required if your Nimble array has no Internet access. Procedure<\/strong><\/p>

To download the NimbleOS update file:<\/p>

1 <\/strong>From another workstation, in your browser address field, type: https:\/\/infosight.nimblestorage.com<\/em><\/p>

The Nimble Storage InfoSight\u2122 opens in a browser window.<\/p>

2 <\/strong>On the NimbleOS tab, select the NimbleOS update version from the drop-down menu.<\/p>

3 <\/strong>In the list of download packages, click Software <\/strong>and save the NimbleOS update file and save the file to a convenient<\/p>

place on your PC or host.<\/p>

Update the NimbleOS<\/strong><\/p>

Procedure<\/strong><\/p>

1 <\/strong>Choose Administration <\/strong>> Software<\/strong>.<\/p>

2 <\/strong>In the Software pane, click Download<\/strong>.<\/p>

3 <\/strong>In the list of NimbleOS Updates, check the update to install and click Download<\/strong>.<\/p>

4 <\/strong>When you see the downloaded NimbleOS update file in the Software pane, click Update<\/strong>.<\/p>

5 <\/strong>When the End User License Agreement (EULA) appears, scroll to the bottom of the EULA, check the box,and click Agree<\/strong>.<\/p>

Installation does not continue until you click Agree<\/strong>.<\/p>

6 <\/strong>Read the Software Update message and click OK<\/strong>.<\/p>

The NimbleOS update process takes about 20 minutes per array. During that time, a controller failover and a browser reload occur automatically. The array itself remains online and available throughout the update.<\/p>

If you have multiple arrays in a storage group, all group arrays are updated, one at a time, to the same version of<\/p>

NimbleOS.<\/p>

Note <\/strong>If your connection to the array drops during the update, you might not be able to re-establish connection until the update is done.<\/p>

When the update is finished, the new NimbleOS version is listed as the Current <\/em>version.<\/p>

Verify the NimbleOS Update<\/strong><\/p>

Procedure<\/strong><\/p>

1 <\/strong>Go to Events<\/strong>.<\/p>

2 <\/strong>Verify the NimbleOS update by checking the Events list for the update event. For example:<\/p>

A successful software update is indicated by two update events, one for each controller<\/p>

From: https:\/\/esxsi.com\/2016\/09\/22\/nimble-os\/<\/p>

 <\/p>

Log into the web interface of the Nimble device. Select<\/p>

the Administration <\/strong>drop down menu and click Software<\/strong>.<\/p>

<\/p>

On the software page click Download <\/strong>to download the latest operating system version, this does not being the update process but downloads the software to the array. If you have obtained the software from Nimble support<\/p>

click Upload <\/strong>and browse to the folder location.<\/p>

<\/p>

Once the software has downloaded click Update<\/strong>. In this example we are upgrading from v2.3.14 to v3.4.1. The process involves updating one controller at a time, since they run as active \/ passive there should be no outage.<\/p>

When prompted with the license agreement click Agree<\/strong>. Click Ok <\/strong>to the message about clearing your browser cache and reloading the page once the update is complete.<\/p>

<\/p>

The update will now commence, keep in mind that you<\/p>

may see the process stages \u20181 of 7\u2019 jump forward and then back a step, this is normal. Once the first controller has finished updating the browser will reload during fail-over.<\/p>

<\/p>

Once the update is complete you will be returned to the software page, where the current version number should now be updated. Depending on what you are upgrading to and from, some of the menu pages look a little different, such as the home page. If you have any issues with the web client at this stage then delete your browsing history and restart the browser.<\/p>

Check in RECENT EVENTS, you should see the software successfully updated message for both controllers. If you have email notifications setup you will also have been notified of this via email. It\u2019s worth checking over the servers that have Nimble storage volumes mounted and that all paths are available.<\/p>

<\/p>

Explanation of Nimble OS Version<\/p>

 <\/p>

Release family Planned maintenance<\/p>

release<\/p>

Unplanned<\/p>

maintenance release<\/p>

Patch release<\/p>

The Meaning of Each Software Release Status<\/p>

 <\/p>

Software Release Status Description<\/strong><\/p><\/td><\/tr>

Initial Production Release (IPR)<\/strong><\/p>

GA Candidate Production Release (GAC)<\/strong><\/p>

General Availability Production Release (GA)<\/strong><\/p><\/td>

The software release is ready for production use. Until the release achieves General Availability status<\/p>

(see below), the release will be available upon request to customers desiring the capabilities of the new release. In addition, the release will also be proactively made available to a subset of customers and\/or systems. The set of such proactively notified \/ white-listed customers\/systems will gradually expand until GA status is achieved.<\/p><\/td><\/tr>

The software release is ready for production use. These are the maintenance releases after IPR up until the release achieves General Availability status (see below). The release will be available upon request to customers desiring the capabilities of the new release. In addition, the release will also be proactively made available to a subset of customers and\/or systems. The set of such proactively notified\/white-listed customers\/systems will gradually expand until GA status is achieved.<\/p><\/td><\/tr>

The release is designated as GA after it has demonstrated a high level of stability across a large number of production systems and sufficiently long runtime across those systems. The specific thresholds are determined by Nimble and will depend on the<\/p><\/td><\/tr><\/tbody><\/table>

Release Notes (READ ME FIRST)<\/strong><\/p>

Release Notes contain important update prerequisite information, and should be reviewed before updating the software.<\/p>

Documentation and downloads are available on InfoSight:<\/p>

\u2022 Release Notes (<\/a>Resources > Documentation > Release Notes > 4.x)<\/p>

\u2022 Nimble Storage Software Release Model (<\/a>Resources > Documentation > Support Policy)<\/p>

o NOTE: An updated version of the \u201cEnd of Availability \/ Support Policy\u201d document was uploaded on 12\/07\/2016<\/em><\/strong><\/p>

\u2022 Software Update FAQ (<\/a>Resources > Documentation > Knowledge Base Article > KB-000351 Nimble Array: Software Update<\/p>

FAQ)<\/p>

\u2022 Compatibility Matrix (<\/a>Resources > Documentation > Compatibility Matrix)<\/p>

\u2022 Host Integration software (<\/a>Resources > Software Downloads > Integration Kits)<\/p>

 <\/p>","protected":false},"excerpt":{"rendered":"

Updating NimbleOSThe BasicsUpgrading Nimble OS is something clients can complete easily and with confidence, thanks largely to the thorough pre-checks and verifications that are part of the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[568,2113,1725,2114,1131],"class_list":["post-2773","post","type-post","status-publish","format-standard","hentry","category-random","tag-firmware","tag-ncm","tag-nimble","tag-os","tag-update"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/posts\/2773","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/comments?post=2773"}],"version-history":[{"count":2,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/posts\/2773\/revisions"}],"predecessor-version":[{"id":2817,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/posts\/2773\/revisions\/2817"}],"wp:attachment":[{"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/media?parent=2773"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/categories?post=2773"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/tags?post=2773"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}