Trending Topics

Implement and configure AWS Backup for VMware Cloud on AWS VM workloads

In our previous post we saw the design of the AWS Backup on VMC. In this post we’re going through the implementation steps As per the design and best practice, we are going to use the ENI for the Backup traffic CREATE A VPC ENDPOINT  TO CREATE AN INTERFACE ENDPOINT FOR AN AWS SERVICE 1. Open the Amazon VPC console at    2. In the navigation pane, choose Endpoints 3. Choose Create endpoint 4. Name the endpoint   5. For Service category, choose AWS services 6. For Service name, search “ Backup ” and select “ backup-gateway ” service from the dropdown 7. For VPC, select the VPC which we used for SDDC deployment and extension 8. To create an interface endpoint for Amazon S3, you must “uncheck” Additional settings, Enable DNS name. This is because Amazon S3 does not support private DNS for interface VPC endpoints 9. For  Subnets , select one subnet per Availability Zone which we used for SDDC VMC selection  10. For Security group , sel

Assign Virtual IPs to your NIC

Assigning a virtual IP to a NIC is a very easy task either you use the system-config-networktool or just do some text file editing. The script ifconfig can also be used to create a virtual network interface, but this would not be permanent since the changes ifconfig makes do not survive a reboot. In this post I’ll stick with the “manual” way…

In Fedora, all information about the network interfaces is kept in the following directories:

I assume that the default NIC configuration script is:
/etc/sysconfig/network-scripts/ifcfg-eth0. Mine looks like this:DEVICE=eth0 BOOTPROTO=static BROADCAST= HWADDR=00:00:00:00:00:00 IPADDR= NETMASK= NETWORK= ONBOOT=yes TYPE=Ethernet GATEWAY=

BOOTPROTO: sets the protocol that is used when the device is initialized. Since we use static IPs we set it to static.
HWADDR: is the MAC address of your network card. Do not change it. If this is missing in your configuration file, then don’t add it.
The rest of the options used are self-explanatory.

Make a copy of this in the same directory naming the new file ifcfg-eth0:1# cp ifcfg-eth0 ifcfg-eth0\:1

eth0:1 is an alias of the eth0 interface. Now, let’s assign a different IP address to eth0:1. Other NIC aliases could be named eth0:2, eth0:3 etc. Fire up your favourite text editor and edit ifcfg-eth0:1. The modifications are shown in bold:DEVICE=eth0:1 BOOTPROTO=static BROADCAST= HWADDR=00:00:00:00:00:00 IPADDR= NETMASK= NETWORK= ONBOOT=yes TYPE=Ethernet GATEWAY=

So, its IP address will be Save the file and copy it to/etc/sysconfig/networking/devices/:# cp ifcfg-eth0\:1 /etc/sysconfig/networking/devices/

Also, copy it to your default network profile or whichever profile you use:# cp ifcfg-eth0\:1 /etc/sysconfig/networking/profiles/default/

Now, bring up the new interface using the ifup script:# ifup eth0\:1

Running ifconfig, the new interface should be listed. You can also check it by pinging:# ping

You can now assign a host name on this virtual interface, by updating your local DNS server’s zone files or by adding it to the /etc/hosts files on all your LAN computers.

Popular posts from this blog


AD LDS – Syncronizing AD LDS with Active Directory

DNS Scavenging.