On Mon, 13 Nov 2017 14:01:11 +0000
"Frank M. Ramaekers" <framaek...@ailife.com> wrote:
> Okay, I have a Fedora release 23 install. Everything work
> great....well that's until I reboot (re-IPL). There is an
> inconsistency in the initialization of the Ethernet interfaces:
how the interface are configured? With static IPs or DHCP? Anything
network or device related in the journal?
Dan
>
> 1) Interfaces come up w/o an IP address (see enccw0.0600 and
> enccw0.0700 ifconfig
> enccw0.0.0600: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 02:00:01:00:00:1f txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> enccw0.0.0700: flags=4097<UP,MULTICAST> mtu 1492
> ether 02:00:01:00:00:20 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1 (Local Loopback)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast
> 192.168.122.255 ether 52:54:00:df:e7:ba txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> 2) One comes up (although w/o an IP address) and the other
> doesn't come up at all ifconfig
> enccw0.0.0700: flags=4097<UP,MULTICAST> mtu 1492
> ether 02:00:01:00:00:20 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1 (Local Loopback)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast
> 192.168.122.255 ether 52:54:00:df:e7:ba txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> 3) Both interfaces come up normally:
> ifconfig
> enccw0.0.0600: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 4096
> inet 10.1.20.84 netmask 255.255.0.0 broadcast 10.1.255.255
> inet6 fe80::1ff:fe00:1f prefixlen 64 scopeid 0x20<link>
> ether 02:00:01:00:00:1f txqueuelen 1000 (Ethernet)
> RX packets 1542 bytes 182508 (178.2 KiB)
> RX errors 0 dropped 98 overruns 0 frame 0
> TX packets 46 bytes 4642 (4.5 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> enccw0.0.0700: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 4096
> inet 192.168.199.84 netmask 255.255.255.0 broadcast
> 192.168.199.25 inet6 fe80::200:100:100:20 prefixlen 64 scopeid
> 0x20<link> ether 02:00:01:00:00:20 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 26 bytes 2962 (2.8 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1 (Local Loopback)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast
> 192.168.122.255 ether 52:54:00:df:e7:ba txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> I'm not seeing any differences in the startup messages, so I'm a bit
> puzzled. (I also have a SUSE-SLES12 that doesn't experience this
> behavior)
>
> TIA,
> Frank M. Ramaekers Jr. | Systems Programmer | Information Technology
> | American Income Life Insurance Company | 254-761-6649 (732-6649)
>
> ----------------------------------------------------------------------
> This message contains information which is privileged and
> confidential and is solely for the use of the intended recipient. If
> you are not the intended recipient, be aware that any review,
> disclosure, copying, distribution, or use of the contents of this
> message is strictly prohibited. If you have received this in error,
> please destroy it immediately and notify us at
> privacy...@torchmarkcorp.com.
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390
> or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
