Versions Compared

Old Version 28

changes.mady.by.user W.Erber

Saved on

compared with

New Version 29

changes.mady.by.user W.Erber

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: interface naming warning; NM info

...

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 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 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.


StepDetails
Locate your network interface in the interface list and right-click on it.

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


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

Select your instance and confirm entry.

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


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

Verify that instance has second interface.

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

...