Amazon EC2 ubuntu instance ifconfig does not show interfaces attached by attach_network_interfaceConfiguring...

Check if a string is entirely made of the same substring

What makes accurate emulation of old systems a difficult task?

Implications of cigar-shaped bodies having rings?

Re-entry to Germany after vacation using blue card

How can the Githyanki Supreme Commander move while insubstantial?

Rivers without rain

Which big number is bigger?

How exactly does Hawking radiation decrease the mass of black holes?

What are the steps to solving this definite integral?

How to denote matrix elements succinctly?

Why does nature favour the Laplacian?

Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?

Why did C use the -> operator instead of reusing the . operator?

Checks user level and limit the data before saving it to mongoDB

As an international instructor, should I openly talk about my accent?

Function pointer with named arguments?

Mistake in years of experience in resume?

Minor Revision with suggestion of an alternative proof by reviewer

How could Tony Stark make this in Endgame?

Why didn't the Space Shuttle bounce back into space as many times as possible so as to lose a lot of kinetic energy up there?

Contradiction proof for inequality of P and NP?

How did Captain America manage to do this?

bldc motor, esc and battery draw, nominal vs peak

Can we say “you can pay when the order gets ready”?



Amazon EC2 ubuntu instance ifconfig does not show interfaces attached by attach_network_interface


Configuring eth0 and eth1 on PowerEdge 2900 assigns both to same adapterSecond ENI in AWS VPC is not accessible on Ubuntu instanceEC2 elastic IP not resolving to private IP on debian instanceMultiple network interfaces, routing configuration. IP rule fails (debian based instances)Multiple NIC same subnetI can not attach additional network interface to an existing amazon EC2 instanceWhy does an AWS EC2 instance need public and private DNS?AWS CLI describe volume attachment informationAmazon EC2/VPC LXC Bridge not workingHow to configure iptables for a dial-up VPN with OpenVPN and two interfaces?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I have launched a c3.xlarge ubuntu instance in a VPC. This instance supports 4 interfaces. I use ec2 python APIs to create_network_interface and attach_network_interface to add eth1, eth2, and eth3. On the AWS console, the instance is up and running. All 4 network interfaces are shown in the AWS console with the correct subnet ID.



When I ssh into the instance, and use "ifconfig" to show the interfaces, only eth0 is shown. If I use "ifconfig -a", I can see eth0-3, but only eth0 has an IP address assign to it.



Am I missing anything?
Thanks in advance....





Edit:
From the AWS console EC2 dashboard, I clicked on the instance->Description, scroll down to see the "Network interfaces" portion, it shows all eth0, eth1, eth2, and eth3. If I click on eth1 - eth3, they all show the IP address and status like this:
Network Interface eth1
Interface ID
eni-119f304f
VPC ID
vpc-873db7e2
Attachment Owner
17xxxxxxxx79
Attachment Status
attached
Attachment Time
Fri Sep 09 10:58:58 GMT-700 2016
Delete on Terminate
false
Private IP Address
10.31.2.12
Private DNS Name
ip-10-31-2-12.us-west-2.compute.internal



Elastic IP Address



Source/Dest. Check
true
Description
cluster001-demux-peer1
Security Groups
cluster001-demux



The private IP addresses are created and assigned to those network interfaces from AWS's point of view.



The /etc/network/interfaces shows the normal things:
auto lo
iface lo inet loopback



# Source interfaces
# Please check /etc/network/interfaces.d before changing this file
# as interfaces may have been defined in /etc/network/interfaces.d
# NOTE: the primary ethernet device is defined in
# /etc/network/interfaces.d/eth0
# See LP: #1262951
source /etc/network/interfaces.d/*.cfg









share|improve this question
















bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















    0















    I have launched a c3.xlarge ubuntu instance in a VPC. This instance supports 4 interfaces. I use ec2 python APIs to create_network_interface and attach_network_interface to add eth1, eth2, and eth3. On the AWS console, the instance is up and running. All 4 network interfaces are shown in the AWS console with the correct subnet ID.



    When I ssh into the instance, and use "ifconfig" to show the interfaces, only eth0 is shown. If I use "ifconfig -a", I can see eth0-3, but only eth0 has an IP address assign to it.



    Am I missing anything?
    Thanks in advance....





    Edit:
    From the AWS console EC2 dashboard, I clicked on the instance->Description, scroll down to see the "Network interfaces" portion, it shows all eth0, eth1, eth2, and eth3. If I click on eth1 - eth3, they all show the IP address and status like this:
    Network Interface eth1
    Interface ID
    eni-119f304f
    VPC ID
    vpc-873db7e2
    Attachment Owner
    17xxxxxxxx79
    Attachment Status
    attached
    Attachment Time
    Fri Sep 09 10:58:58 GMT-700 2016
    Delete on Terminate
    false
    Private IP Address
    10.31.2.12
    Private DNS Name
    ip-10-31-2-12.us-west-2.compute.internal



    Elastic IP Address



    Source/Dest. Check
    true
    Description
    cluster001-demux-peer1
    Security Groups
    cluster001-demux



    The private IP addresses are created and assigned to those network interfaces from AWS's point of view.



    The /etc/network/interfaces shows the normal things:
    auto lo
    iface lo inet loopback



    # Source interfaces
    # Please check /etc/network/interfaces.d before changing this file
    # as interfaces may have been defined in /etc/network/interfaces.d
    # NOTE: the primary ethernet device is defined in
    # /etc/network/interfaces.d/eth0
    # See LP: #1262951
    source /etc/network/interfaces.d/*.cfg









    share|improve this question
















    bumped to the homepage by Community 2 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0


      0






      I have launched a c3.xlarge ubuntu instance in a VPC. This instance supports 4 interfaces. I use ec2 python APIs to create_network_interface and attach_network_interface to add eth1, eth2, and eth3. On the AWS console, the instance is up and running. All 4 network interfaces are shown in the AWS console with the correct subnet ID.



      When I ssh into the instance, and use "ifconfig" to show the interfaces, only eth0 is shown. If I use "ifconfig -a", I can see eth0-3, but only eth0 has an IP address assign to it.



      Am I missing anything?
      Thanks in advance....





      Edit:
      From the AWS console EC2 dashboard, I clicked on the instance->Description, scroll down to see the "Network interfaces" portion, it shows all eth0, eth1, eth2, and eth3. If I click on eth1 - eth3, they all show the IP address and status like this:
      Network Interface eth1
      Interface ID
      eni-119f304f
      VPC ID
      vpc-873db7e2
      Attachment Owner
      17xxxxxxxx79
      Attachment Status
      attached
      Attachment Time
      Fri Sep 09 10:58:58 GMT-700 2016
      Delete on Terminate
      false
      Private IP Address
      10.31.2.12
      Private DNS Name
      ip-10-31-2-12.us-west-2.compute.internal



      Elastic IP Address



      Source/Dest. Check
      true
      Description
      cluster001-demux-peer1
      Security Groups
      cluster001-demux



      The private IP addresses are created and assigned to those network interfaces from AWS's point of view.



      The /etc/network/interfaces shows the normal things:
      auto lo
      iface lo inet loopback



      # Source interfaces
      # Please check /etc/network/interfaces.d before changing this file
      # as interfaces may have been defined in /etc/network/interfaces.d
      # NOTE: the primary ethernet device is defined in
      # /etc/network/interfaces.d/eth0
      # See LP: #1262951
      source /etc/network/interfaces.d/*.cfg









      share|improve this question
















      I have launched a c3.xlarge ubuntu instance in a VPC. This instance supports 4 interfaces. I use ec2 python APIs to create_network_interface and attach_network_interface to add eth1, eth2, and eth3. On the AWS console, the instance is up and running. All 4 network interfaces are shown in the AWS console with the correct subnet ID.



      When I ssh into the instance, and use "ifconfig" to show the interfaces, only eth0 is shown. If I use "ifconfig -a", I can see eth0-3, but only eth0 has an IP address assign to it.



      Am I missing anything?
      Thanks in advance....





      Edit:
      From the AWS console EC2 dashboard, I clicked on the instance->Description, scroll down to see the "Network interfaces" portion, it shows all eth0, eth1, eth2, and eth3. If I click on eth1 - eth3, they all show the IP address and status like this:
      Network Interface eth1
      Interface ID
      eni-119f304f
      VPC ID
      vpc-873db7e2
      Attachment Owner
      17xxxxxxxx79
      Attachment Status
      attached
      Attachment Time
      Fri Sep 09 10:58:58 GMT-700 2016
      Delete on Terminate
      false
      Private IP Address
      10.31.2.12
      Private DNS Name
      ip-10-31-2-12.us-west-2.compute.internal



      Elastic IP Address



      Source/Dest. Check
      true
      Description
      cluster001-demux-peer1
      Security Groups
      cluster001-demux



      The private IP addresses are created and assigned to those network interfaces from AWS's point of view.



      The /etc/network/interfaces shows the normal things:
      auto lo
      iface lo inet loopback



      # Source interfaces
      # Please check /etc/network/interfaces.d before changing this file
      # as interfaces may have been defined in /etc/network/interfaces.d
      # NOTE: the primary ethernet device is defined in
      # /etc/network/interfaces.d/eth0
      # See LP: #1262951
      source /etc/network/interfaces.d/*.cfg






      amazon-ec2 linux-networking






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 19 '17 at 17:22









      Duncan X Simpson

      255319




      255319










      asked Sep 9 '16 at 17:50









      Cheng HsiangCheng Hsiang

      11




      11





      bumped to the homepage by Community 2 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 2 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          You're not missing too much. Only eth0 has an IP, so by default ifconfig will show only that one. The other interfaces either need IPs, don't have a configuration in your interfaces file(s), or don't have dhcp services on their layer two broadcast domains.



          How about providing the contents of /etc/networks/interfaces so we can see what's supposed to be what? That is, if you don't just see the problem immediately.






          share|improve this answer































            0














            I figured it out. I need to add a delay, e.g. time.sleep(1), between python API create_network_interface and attach_network_interface. This was not necessary, but now it seems like AWS infrastructure has changed, I do need to add this delay.
            It is now working...






            share|improve this answer
























              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "2"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f802168%2famazon-ec2-ubuntu-instance-ifconfig-does-not-show-interfaces-attached-by-attach%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              You're not missing too much. Only eth0 has an IP, so by default ifconfig will show only that one. The other interfaces either need IPs, don't have a configuration in your interfaces file(s), or don't have dhcp services on their layer two broadcast domains.



              How about providing the contents of /etc/networks/interfaces so we can see what's supposed to be what? That is, if you don't just see the problem immediately.






              share|improve this answer




























                0














                You're not missing too much. Only eth0 has an IP, so by default ifconfig will show only that one. The other interfaces either need IPs, don't have a configuration in your interfaces file(s), or don't have dhcp services on their layer two broadcast domains.



                How about providing the contents of /etc/networks/interfaces so we can see what's supposed to be what? That is, if you don't just see the problem immediately.






                share|improve this answer


























                  0












                  0








                  0







                  You're not missing too much. Only eth0 has an IP, so by default ifconfig will show only that one. The other interfaces either need IPs, don't have a configuration in your interfaces file(s), or don't have dhcp services on their layer two broadcast domains.



                  How about providing the contents of /etc/networks/interfaces so we can see what's supposed to be what? That is, if you don't just see the problem immediately.






                  share|improve this answer













                  You're not missing too much. Only eth0 has an IP, so by default ifconfig will show only that one. The other interfaces either need IPs, don't have a configuration in your interfaces file(s), or don't have dhcp services on their layer two broadcast domains.



                  How about providing the contents of /etc/networks/interfaces so we can see what's supposed to be what? That is, if you don't just see the problem immediately.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Sep 9 '16 at 17:57









                  SpoolerSpooler

                  6,1941228




                  6,1941228

























                      0














                      I figured it out. I need to add a delay, e.g. time.sleep(1), between python API create_network_interface and attach_network_interface. This was not necessary, but now it seems like AWS infrastructure has changed, I do need to add this delay.
                      It is now working...






                      share|improve this answer




























                        0














                        I figured it out. I need to add a delay, e.g. time.sleep(1), between python API create_network_interface and attach_network_interface. This was not necessary, but now it seems like AWS infrastructure has changed, I do need to add this delay.
                        It is now working...






                        share|improve this answer


























                          0












                          0








                          0







                          I figured it out. I need to add a delay, e.g. time.sleep(1), between python API create_network_interface and attach_network_interface. This was not necessary, but now it seems like AWS infrastructure has changed, I do need to add this delay.
                          It is now working...






                          share|improve this answer













                          I figured it out. I need to add a delay, e.g. time.sleep(1), between python API create_network_interface and attach_network_interface. This was not necessary, but now it seems like AWS infrastructure has changed, I do need to add this delay.
                          It is now working...







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Sep 9 '16 at 21:57









                          user5655748user5655748

                          1




                          1






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Server Fault!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f802168%2famazon-ec2-ubuntu-instance-ifconfig-does-not-show-interfaces-attached-by-attach%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

                              Українські прізвища Зміст Історичні відомості |...

                              Список ссавців Італії Природоохоронні статуси | Список |...