Migration Hub Network diagram showing no connections info

When using AWS Migration Hub to visualize server dependencies in the network diagram, but no network connection information is displayed, several issues could be causing this problem. Here are steps to troubleshoot and potentially resolve the issue:

1. Verify Agent Installation and Configuration Ensure that the AWS Application Discovery Service (ADS) agents are properly installed and configured on the on-premise servers. Check the following:

• Agent Status: Confirm that the agents are running and have a status of 'healthy' in the Migration Hub console.
• Permissions: Make sure that the agents have sufficient permissions to collect and send network data. This includes network configuration and traffic monitoring capabilities.
• Firewall and Network Security: Verify that firewalls or security groups are not blocking the outbound connections of the ADS agents to AWS endpoints.

2. Check Data Collection Settings ADS agents should be configured to collect and send network traffic data. Confirm the settings related to data collection:

• Configuration File: Review the agent’s configuration file to ensure network performance data collection is enabled.
• Supported Data: Ensure that the types of collected data include network connections. Sometimes, only basic inventory data (like CPU, volume, and system performance) might be configured.

3. Review Network Visibility The ADS agents must have visibility into the network traffic to capture connection data. This can be affected by the network architecture and the position of the servers in it:

• Server Position: Ensure that servers are not isolated by VLANs or other network segmentation methods that could hide their traffic from one another.
• Spanning Tree Protocols and Other Network Features: Sometimes, network features can prevent certain types of traffic from being visible to the ADS agents.

4. Inspect Logs Check the logs of the ADS agents for any errors or warnings that could indicate problems with data collection or communication with AWS:

• Agent Logs: Look for any error messages that suggest issues with capturing network data or communicating with AWS services.
• AWS CloudWatch Logs: If logs are forwarded to CloudWatch, inspect them for any insights into operational issues.

5. Ensure Adequate Data Collection Period Network dependencies might not show up if there hasn't been enough time for adequate data collection:

• Operation Time: Network connections might need to be observed over a longer period to ensure all possible connections are captured, especially for intermittent or periodic communications.

6. AWS Support If the above steps do not resolve the issue, consider contacting AWS Support for more in-depth troubleshooting. They can provide guidance specific to your architecture and the configurations of your AWS and on-premise environments.