An administrator is using BlueXP Copy and Sync to move an NFS dataset. The Data Broker shows status "Unknown". The administrator confirms there is NFS connectivity and appropriate access to read all…

Question

Options

• ASMTP
• BKerberos
• CHTTPS
• DSMB

• A
  4% (1)
• B
  4% (1)
• C
  83% (20)
• D
  8% (2)

Explanation

In the scenario where an administrator is using BlueXP Copy and Sync to move an NFS dataset and the Data Broker shows the status "Unknown" despite confirmed NFS connectivity, the required network service is HTTPS. Here's why: HTTPS for Data Broker Communication: The Data Broker, which orchestrates data movement in BlueXP Copy and Sync, uses HTTPS to communicate securely with both the source and destination systems, as well as with NetApp's cloud services. This secure communication channel is essential for managing the data transfer processes reliably and securely. Verifying HTTPS Connectivity: Ensure that all network components, such as firewalls and routers, are configured to allow HTTPS traffic (port 443) from the Data Broker to the NFS endpoints and back. This includes checking for any blocked ports or filtered traffic that could impede the Data Broker's Troubleshooting Network Issues: If the status remains "Unknown," further network diagnostics may be necessary to identify any disruptions or misconfigurations in HTTPS connectivity that could affect the Data Broker's functionality.

No community discussion yet for this question.