Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC Metro node 7.1 CLI Guide

PDF

ndu start

Begins the non-disruptive upgrade (NDU) process of the director firmware.

Contexts

All contexts.

Syntax

ndu start

[--io-fwd-ask-for-confirmation] prompt type [-u|--firmware] firmware-tar-file [optional-argument [optional-argument]]

Arguments

Required arguments
[-u|--firmware] firmware-tar-file * Full path to director firmware package on the management server.
[--io-fwd-ask-for-confirmation] prompt type The type of the prompt that you want to see during the IO forwarding phase of the NDU. The available options are:
  • always - Choose this option if you have hosts that require manual scanning for the paths to be visible. Assistance from the customer is required to verify that initiator paths on the hosts are alive. If the path is unavailable, resolve the issue within the timeout period that you have specified. The prompts for this options are:
    • Continue: NDU continues even when there are missing initiator logins. Make sure that the customer is aware that missing logins can cause DU.
    • Rollback: NDU rolls back and DU is avoided. The customer can check the host, resolve the issue that led to the missing initiator logins, and rerun the NDU.
    • Refresh: Get the new list of initiators. If all the initiators are logged in, metro node displays the prompts to move forward.
  • on-missing-logins - Assistance from the customer is required to determine whether any missing initiators are from critical hosts. If paths are unavailable from critical hosts, the customer will need to resolve the issue before continuing with the NDU. The prompts for this options are:
    • Continue: NDU continues even when there are missing initiator logins. Make sure that the customer is aware that missing logins can cause DU.
    • Rollback: NDU rolls back and DU is avoided. The customer can check the host, resolve the issue that led to the missing initiator logins, and rerun the NDU.
    • Refresh: Get the new list of initiators. After all the initiators are logged in, NDU continues without displaying any prompt.
  • never - No interaction is required or the customer is not available to check the host connectivity. NDU waits for all the initiators to log back in within the specified timeout period. Resolve any issues within this period. If metro node identifies any missing logins after the timeout period, NDU is rolled back. It is important to check whether this value must be modified according to the environment requirements of the customers and weighed against the risks.
Optional arguments
--io-fwd-timeout= timeThe period after which the I/O forward phase times out. In the I/O forward phase, the I/Os that are serviced to the first set of directors are forwarded to the second set of directors. The hosts are expected to connect back to the first set of directors during this period. By default, this phase lasts for 180 minutes. You can set this timeout period to a minimum of 6 minutes and a maximum of 12 hours. Use:
  • s for seconds
  • m for minutes
  • h for hours
  • d for days
--cws-package cws-firmware-tar-file Full path to Cluster Witness Server package on the management server.
NOTE Not required if upgrading to an official product release.
--force Ignore manifest checking of supported upgrades.
--skip-cws-upgrade Skips the upgrade of the Cluster Witness Server and proceeds with the rest of the NDU.
--skip-be-switch-check Skips the NDU pre-check for unhealthy back-end switches.
--skip-cluster-status-check Skips the NDU pre-check for cluster problems (missing directors, suspended exports, inter-cluster link failure, and so on).
--skip-confirmations Skips any user confirmations normally required before proceeding when there are NDU pre-check warnings.
--skip-distributed-device-settings-check Skips the NDU pre-check for distributed device settings (auto-resume set to true).
--skip-fe-switch-check Skips the NDU pre-check for unhealthy front-end switches.
--skip-group-be-checks Skips all NDU pre-checks related to back-end validation. This includes pre-checks for system configuration validation and unreachable storage volumes.
--skip-group-config-checks Skips all NDU pre-checks related to system configuration. This includes the system configuration validation and director commission pre-checks.
--skip-group-fe-checks Skips all NDU pre-checks related to front-end validation. This includes the unhealthy storage views and storage view configuration pre-checks.
--skip-group-health-checks Skips all NDU pre-checks related to system health validation. This includes the system configuration validation, unhealthy virtual volumes, cluster status, and the inter-cluster communications connectivity pre-checks.
--skip-meta-volume-backup-check Skips the check to verify that backups for the meta-data volumes at all clusters have been configured.
--skip-meta-volume-redundancy-check Skips the NDU pre-check for verifying the meta-volume redundancy.
----skip-storage-volumes-check Skip the NDU pre-check for unreachable storage volumes.
--skip-sysconfig-check Skips the system configuration validation NDU pre-check and proceed with NDU even if there are errors with cache replication, logging volume setup, back-end connectivity, and metadata volume health.
--skip-view-config-check Skips the NDU pre-check for storage view configuration (front-end high availability). This option is required to pass the NDU pre-checks when operating a minimum configuration. For minimum configurations, front-end high-availability pre-checks must be performed manually.
--skip-view-health-check Skips the NDU pre-check for unhealthy storage views.
--skip-virtual-volumes-check Skips the NDU pre-check for unhealthy virtual volumes.
--skip-wan-com-check Skips the inter-cluster communications connectivity NDU pre-check and proceed with NDU even if there are errors specifically related to inter-cluster communications connectivity.
--skip-local-com-check Skips the intra-cluster communications connectivity NDU pre-check and proceed with NDU even if there are errors specifically related to intra-cluster communications.
--skip-total-number-of-volumes-check Skips the NDU pre-check for total number of volumes.
--skip-inter-director-mgmt-connectivity-check Skips the NDU pre-check for inter-director management connectivity.
--do-not-verify-wanlink-after-upgrade NDU does not check whether first-upgraders see each other on the WAN link after the upgrade.
--skip-storage-view-missing-lun0-checkSkips the NDU pre-check for storage-views with virtual-volumes that do not have a LUN0 ID.
skip-hypervisor-rolling-upgrade-checkSkips the hypervisor rolling upgrade check.

Description

This command starts a non-disruptive upgrade and can skip certain checks to push a non-disruptive upgrade when the ndu pre-checks command fails. The pre-checks executed by the ndu pre-check command verify that the upgrade from the current software to the new software is supported, the configuration supports NDU, and the system state is ready (clusters and volumes are healthy).

You must resolve all issues disclosed by the ndu pre-check command before running the ndu start command.

Skip options enable ndu start to skip one or more NDU pre-checks. Skip options should be used only after fully understanding the problem reported by the pre-check to minimize the risk of data unavailability.

NOTE Skip options may be combined to skip more than one pre-check. Multiple skip options must be separated by a space.
NOTE It is recommended that you upgrade metro node using the upgrade procedure found in the SolVe Desktop. This procedure also details when the ndu start command should be used with skip options and how to select and use those skip options.

See also

  • ndu pre-check
  • ndu recover
  • ndu status

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\