After deploying a virtual machine (VM) in your environment, it's crucial to understand its configuration and networking details. This document outlines the steps to access VM configuration, public and private IP addresses, and provides insights into the private and public networking parameters.

VM Configuration

1. Access VM Configuration: Post VM deployment, you can access the VM configuration details.
2. Identify Public and Private IP: Find information about both the public and private IP addresses associated with the VM.

VM Networking

1. Navigate to VM Networking: Under the VM details, locate and access the VM Networking section.
2. Explore Private Network Parameters:
   • Subnet Name: Identify the name of the private subnet.
   • Subnet Mask: Check the subnet mask associated with the private subnet.
   • Gateway: Find the gateway for the private network.
   • VPC (Virtual Private Cloud): Understand the Virtual Private Cloud associated with the private network.

Public Network

1. Explore Public Network Parameters:
   • Public Subnet: Identify the name of the public subnet.
   • Subnet Mask: Check the subnet mask associated with the public subnet.
   • Gateway: Find the gateway for the public network.
   • Accessing the VM Over the Internet.
2. NAT Configuration:
   • The private IP of the VM is NATed with a public IP address.
   • This NAT configuration allows you to directly access your server over the internet.

Verify Network Interfaces

Your VM comprises several network interfaces designated to connect to specific networks or gateways. It's crucial to verify the operational status of these interfaces.
To check the status of your VM's network interfaces, use the command:
ip -br a
This command provides basic information about the VM's network interfaces. It displays the status of each interface: UP, DOWN, or UNKNOWN.
If any interface appears as DOWN, enable it using:
sudo ifup < your-vm-interface-name >
If all interfaces are UP, restart each one using the commands:
sudo ifdown < your-vm-interface-name > sudo ifup < your-vm-interface-name >
Use the --force flag if necessary:

sudo ifdown --force < your-vm-interface-name > sudo ifup < your-vm-interface-name >

After enabling all interfaces, check for connectivity issues by pinging external hosts. If issues persist, proceed to the next section.

Check Network Configuration File
Your VM's network configuration files contain interface details. Changes to these files might not persist after a reboot or could be incorrectly configured.

Before altering any network files, create a snapshot and backup of the current configuration.
Refer to your VM's operating system for troubleshooting instructions.
CentOS: The configuration files are stored in the /etc/sysconfig/network-scripts/ directory. Make a backup before editing any files:

cp /etc/sysconfig/network-scripts/< interface-file > /etc/sysconfig/network-scripts/< interface-file >.old
Review the network configuration:

vi /etc/sysconfig/network-scripts/< interface-file >

Compare these configurations to those listed in your VMX Control Panel under Networking.

Conclusion

Understanding the VM configuration and networking parameters is crucial for effective management and troubleshooting. By following the steps outlined in this document, you gain insights into the private and public networking details associated with your deployed VM.