Comment 22 for bug 1561096

------- Comment From <email address hidden> 2016-05-09 19:14 EDT-------
==== State: Working by: furrer on 09 May 2016 17:50:45 ====

#=#=# 2016-05-09 17:50:43 (CDT) #=#=#
Action = [rejectfix]

I have just installed a fresh install of Ubuntu 16.04 on br16p05.aus.stglabs.ibm.com and followed the setup from the WIKI to use "eth0" as its network access. I completed the install and it was working as desired.

I then added two adapters to the partitions' configuration using the HMC GUI under I/O to add "As Desired" to the partition, a Mason adapter at location FHZ0145-P2-C6 and a Travis_EN adapter at location CSS00HL-P1-C5. I then rebooted the partition to activate both adapters in prep for an attempt at two TER completions.

I attempted to run "build_net help" to set up the network but when I ran the command, it appeared to hang. I exited the instance and checked the state of the network access by running the command "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock" to make sure the test/tools directory was mounted. The command returned:

(0) root @ br16p05: /root
# mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock
mount.nfs: Failed to resolve server iofnim.aus.stglabs.ibm.com: Temporary failure in name resolution

I then checked the /etc/network/interfaces file I had modified for network access for the Ubuntu 16.04 according to the WIKI via .ISO and it is set up as it was when I originally set up the fresh install. Thinking the interface may have an issue, I ran "ifdown eth0" and it returned:

(0) root @ br16p05: /root
# ifdown eth0
ifdown: interface eth0 not configured

To double-check there is more at play here, I also ran "ifup eth0" just to see what it returned:

(0) root @ br16p05: /root
# ifup eth0
Cannot find device "eth0"
Failed to bring up eth0.

As the setup for eth0 DOES exist in /etc/network/interfaces, I ran "ifconfig -a" to view the existing interfaces and it returned this:

(0) root @ br16p05: /root
# ifconfig -a
enP1p160s0f0 Link encap:Ethernet HWaddr 00:c0:dd:10:1d:c4
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:256
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:249

enP1p160s0f1 Link encap:Ethernet HWaddr 00:c0:dd:10:1d:c6
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:256
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:250

enp1s0 Link encap:Ethernet HWaddr e4:1d:2d:54:70:82
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

enp1s0d1 Link encap:Ethernet HWaddr e4:1d:2d:54:70:83
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ibmveth2 Link encap:Ethernet HWaddr 46:de:e7:23:26:02
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:19

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

As the first four interfaces appear in the naming convention for past instances of network adapters in Linux, the only one left (with the exception of "lo" is "ibmveth2" which is not set up either but appears to show a similar issue of the original defect where the name "eth0" is being replaced by something else that is subsequently not set up.

I will attempt to modify /etc/network/interfaces for "ibmveth2" after copying the original interfaces file to /etc/network/interfaces.old, reboot the partition and see if that will allow network access in case a developer would like to look at the fresh install overnight.

NOTE: The modification to set up "ibmveth2" in /etc/network/interfaces appeared to work after rebooting the partition but I am unable to ssh or telnet into the partition from an LCB as I get these returns:

$ ssh root@9.3.137.40
root@9.3.137.40's password:
Received disconnect from 9.3.137.40: 2: Invalid ssh2 packet type: 192

$ telnet 9.3.137.40
Trying 9.3.137.40...
telnet: connect to address 9.3.137.40: Connection refused

Please advise.
#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#