During the puresetup portion of the new controller setup of an NDU, the Implementation Engineer gets the error message shown in the exhibit. What action should the Implementation Engineer take next?
A.
Continue with the setup process and manually add the affected ports once it is complete.
B.
Identify which services will be affected, stop the process, and split a case to TSE before moving forward.
C.
Identify which services will be affected, and then re-run the puresetup command with the affected ports included.
During a controller upgrade (e.g., //X to //XL), the puresetup script attempts to migrate network configurations from the old controller's ports to the new controller's ports. If the script detects that certain ports configured on the source array are physically missing or "link down" on the target array, it halts to prevent a configuration mismatch that could cause a service outage.
The error message explicitly lists the affected ports. The correct resolution path is to:
Identify the services: Determine if the missing ports are critical (e.g., a replication link that hasn't been cabled yet) or non-critical (e.g., an unused interface).
Re-run with override: Execute the puresetup command again, this time appending the specific flags or arguments (often suggested in the error output or upgrade guide) to explicitly acknowledge and include those affected ports. This tells the script, "I know these ports are down/missing; proceed with the migration anyway."
This allows the upgrade logic to complete the configuration transfer so the new controller can boot, after which the engineer can physically troubleshoot the link status.
=========
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit