A storage administrator has configured a VNX2 as a remote system. Which Import External Storage migration architectural components are now established?

Question

Options

• AData path and management control path to the access host.
• BData path and management control path to the source storage system.
• CHost iSCSI initiators are registered on the VNX2 storage system.
• DHost Fibre Channel initiators are deregistered on the VNX2 storage system.

• A
  5% (1)
• B
  71% (15)
• C
  5% (1)
• D
  19% (4)

Explanation

When a VNX2 is configured as a remote system in Import External Storage (IES), it establishes both a data path (for moving data blocks) and a management control path (for orchestrating the migration) directly to the source storage system - making B correct. The source system is the "remote" being imported from, so both paths logically terminate there, not at the access host.

Why the distractors are wrong:

• A is wrong because the data and management paths go to the source storage system, not the access host - host connectivity is a separate, later configuration step.
• C is wrong because iSCSI initiator registration on the VNX2 is a host-side activity unrelated to establishing the remote system relationship.
• D is wrong because FC initiator deregistration doesn't occur during this phase - and deregistering initiators would disrupt host access, which is the opposite of what a migration setup does.

Memory tip: Associate "remote system" with the source (the array you're migrating from). When you add a remote system, you're reaching out to that source - so both the data pipe and the management handshake go to the source, not to your hosts.

No community discussion yet for this question.