Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: changes for Azure

...

Table of Contents
excludeContents
stylesquare

When an instance is created, a default Ethernet interface is attached to the system. This is the primary network interface. You can create additional network interfaces and attach them to an instance. 

(warning) If an instance has only one Ethernet interface, a public IP address can be assigned to the interface automatically. However, this address will be removed by AWS if a second interface is added to the instance and the instance is stopped and restarted. Be careful not to lose connectivity to your instance when changing the network configuration.

Creating a New Network Interface

The following steps are required to create a new network interface that can later be added to an instance:

...

Image Removed

Clicking on Network Interfaces opens the list of existing network interfaces.

...

Click on Create Network Interface at the top of the interface list.

Image Removed

This opens the interface creation window.

...

Image Removed

On this screen,

  • enter a description,
  • select the subnet the interface should be on (select the subnet to which your instance is to be connected),
  • allow AWS to automatically assign a private IP address or set a custom one from the subnet IP range, and
  • associate the interface with a security group (often the same as for the instance).

Click on Create when you are done. The new interface will appear in the overview list. There you can assign a name to the interface. Check that the interface is in state available.

...

classpagebreak

Attaching the Interface to your Instance

After creating a network interface, you have to assign it to the instance where it will be used.

Warning
  • Stopping and restarting the instance after adding a second network interface will release any automatically assigned public IP address. If several interfaces are required where one or more are configured with a public address, use Elastic IP addresses.
  • Additionally, adding a second IP network interface to a non-Amazon Linux EC2 instance causes traffic flow issues. This occurs in cases of asymmetric routing where traffic to the instance arrives at one network interface and leaves the instance through the other network interface. This is blocked by AWS because a mismatch between MAC address and IP address. Refer to the AWS documentation and AWS Networking and Charon-SSP (asymmetric routing considerations) for more information. Failure to use the proper steps, may make your instance unreachable!
  • If your instance supports enhanced networking there may be naming inconsistencies when adding additional interfaces to a running instance. Please refer to the interface names section in AWS Networking and Charon-SSP.
  • The NetworkManager is disabled on Charon-SSP AWS. Therefore, ifcfg-files in /etc/sysconfig/network-scripts are required to define the IP configuration of an interface.

...

The right-click opens the context menu. Select Attach.

This will open the window to enter the necessary instance information.

...

Select your instance from the drop-down list and click on Attach.

The state of your interface will change from available to in-use.

...

Select your instance in the instance list. The description tab in instance details should now display two network interfaces:

Image Removed

(info) You can also attach/detach existing interfaces from the instance overview screen. Select your instance and then Actions > Networking > Attach or Detach network interface.

Assigning an Elastic IP Address to the Network Interface

The public IP address assigned to your instance by default when it starts, is not persistent. You will receive a new address when the instance is stopped and started again.

An Elastic IP address is a persistent, public IPv4 address to be used for one of your network interfaces or instances. You can associate an Elastic IP address with any instance or network interface in your account.

(info) The advantage of associating the Elastic IP address with the network interface instead of directly with the instance is that you can move the network interface with its attributes easily from one instance to another.

(warning) The initial automatically assigned public IP address will be removed as soon as you restart the instance after adding a network interface with an Elastic IP address to your instance. Do not restart your instance before you are sure you can reach it via the Elastic IP address. The automatically assigned public IP address will also be disabled if you assign an Elastic IP address to the primary Ethernet interface of the instance.

...

classpagebreak

The table below describes the steps required to add an Elastic IP address to a network interface.

...

Image Removed

This will list the already created Elastic IP addresses.

...

In the overview list, click on Allocate new address if you need to allocate a new address. It is also possible to assign an existing address to an interface. However, each address can only be used for one instance.

Image Removed

This will open the address allocation window.

...

In the address allocation window, select the Amazon pool (or your own pool of public addresses), and click on Allocate.

Image Removed

The new address will be shown in the list.

...

Right-click on the address and select Associate. A window to enter the required options opens.

Image Removed

In the window,

  • select to associate the IP address with a network interface,
  • select your network interface from the drop-down menu,
  • connect the public address to the private address of the interface, and 
  • click on Associate to complete the step.

Detaching a Network Interface from an Instance

You can detach a network interface from your instance in two ways:

  1. Select your instance in the instance list and use the menu Actions > Networking > Detach Network Interface. Or,
  2. Select your network interface in the network interface list and use the menu Actions > Detach.

(warning) Take care that this step will not make your instance unreachable.

...

Adding an Additional Network Interface

It is possible to add additional NICs to the Charon host system in the cloud. Additional NICs can be used to connect the instance to additional subnets. And an additional NIC can also be used to provide an emulated SPARC system running in the emulator with a dedicated network interface. This section shows the basic steps to add a NIC to an existing Azure cloud instance.

(warning) You can create a new interface while the VM is running. However, the VM must be stopped before the new interface can be attached to the system. The VM also must be stopped before detaching an interface.

To add an existing or newly created NIC to the Charon host cloud instance, perform the following steps:

Step 1: Open the Networking screen of your Charon host cloud instance. The sample below shows a VM with only one NIC.

Image Added


Step 2: Click on Attach network interface at the top. This will either let you choose an existing interface or offer the option to create a new one as shown in the sample below:

Image Added


Step 3: Click on Create network interface to open the interface creation screen.

Image Added

Add the mandatory information:

  • Name
  • Subnet
  • Private IP (if static IP is selected)
  • Resource group (same as VM)

Once the information has been added, click on Create to create the new NIC. This will return you to the Networking screen.


Step 4: Attach the selected or newly created interface to your cloud VM.

(warning) Make sure to stop the instance before attaching the interface. Otherwise, you will receive an error.

On the Networking screen, you should now see the new interface. Click on Attach network interface to add the NIC to your VM. The image below shows an example:

Image Added

The Networking screen should now show the two interfaces in two different tabs, as displayed below:

Image Added


Step 5: Restart your VM, log in and check the availability of the second interface.

The output of the ip link show command now shows the second interface (eth1 in the example).

Code Block
languagetext
[root@we-test-vm1 charon]# ip link show |grep eth
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 00:0d:3a:8f:da:f2 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000

Adding a Public IP address to the Second NIC

(warning) If this NIC is used as a dedicated NIC for a Solaris guest system, it is not recommended to expose the Solaris guest to the Internet by adding a public IP to the dedicated NIC. It is highly recommended to use a secure, encrypted VPN connection for any external traffic of the the guest system. The user is responsible for making sure that any external connection complies with the relevant rules and policies of the environment.

Creating a Public IP Address

A public IP address is a resource that can be created using the Create a resource icon on the Home screen. On the overview page, search for public IP address. This will open the initial screen to create public IP address:

Image Added


Clicking on Create takes you to the IP address configuration screen:

Image Added

Add the necessary data, in particular the following:

  • Name
  • Dynamic or Static
  • Resource group (same as your interface)
  • Location

Click on Create to create the address resource.

Attaching the Public IP Address to an Interface

To attach the new public IP address to the second NIC of your instance, perform the following steps:

  • Select your VM in the overview list.
  • Go to the Networking section.
  • Select the interface tab of the relevant interface.
  • On the interface tab page, click on the Network interface link.
  • On the network interface page, under Settings, select IP configurations.
  • Click on the name of the IP configuration to which you want to add the public IP address. This will open the IP configuration screen.

Image Added

On this screen select Enabled for the Public IP address. This will allow you to select the new public IP address.

Then click on Save to save the changes.

(warning) Do not forget to add an appropriate Network Security Group to protect the interface.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc