CLI Guide

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= time The 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:
Commands 253