Re: SUSE under ZVM networking issues

Hi Mark. This is SlLES 12 SP2 s390x. (from /etc/issue) I working from the 3270 session I IPLed the linix from. no graphical environment, not communication from outside. removed the rules file and recycled suse. I found two rule files for qeth for devices 400 and 404. should they be kept? anyway,

Re: SUSE under ZVM networking issues

On Tue, 7 Feb 2017 10:41:11 +0200 Itschak Mugzach wrote: > Hi Mark. > > This is SlLES 12 SP2 s390x. (from /etc/issue) > I working from the 3270 session I IPLed the linix from. no graphical > environment, not communication from outside. > removed the rules file and recycled

Re: SUSE under ZVM networking issues

Hi Berthold I was able to change the network interfaces to dhcp using yast lan edit id=x bootproto=dhcp, and wicked ifup . Now eth0 and eth1 are stalled (?) at setup in progress and both lease of ipv4 and ipv6 are ipvx dhcp requesting status... ITschak On Tue, Feb 7, 2017 at 2:04 PM, Berthold

ClefOS 7.3.1611 (CentOS)

7.3.1611 is now available at http://download.sinenomine.net/clefos/7.3.1611. ClefOS is built from CentOS source but because of brand/trademark requirements. Note for anyone who has been using prior releases we have made a change to package naming. It used to use .cl7 as the distribution id

Re: SUSE under ZVM networking issues

eth1 receives msgs "martian source..." and yes, I can see high count of multicast in /proc/net/dev for this device. it look like it still has iits ipv6 address. ITschak On Tue, Feb 7, 2017 at 3:36 PM, Berthold Gunreben wrote: > On Tue, 7 Feb 2017 15:30:14 +0200 > Itschak Mugzach

Re: SUSE under ZVM networking issues

The problem is that the devices still not getting the IPV4 addresses not the IPV6 addresses from the dhcp... per the messages, I understand the error, but my concern is to activate the devices, which still can't. wicked ifstatus eth0 eth1 shows setup-in-progress and leased: lpvx dhcp requesting.

Re: SUSE under ZVM networking issues

On Tue, 7 Feb 2017 15:30:14 +0200 Itschak Mugzach wrote: > Hi Berthold > > I was able to change the network interfaces to dhcp using yast lan > edit id=x bootproto=dhcp, and wicked ifup . Now eth0 and eth1 are > stalled (?) at setup in progress and both lease of ipv4 and

openSUSE Tumbleweed now in openQA

Hi, since last night, we have openSUSE Tumbleweed for s390x in openQA. This means, that we now get automatic releases along with openSUSE Tumbleweed for other architectures. Currently, just a single installation test is setup. There are not only logfiles, but also a video that captures the run.

Re: SUSE under ZVM networking issues

On Tue, 7 Feb 2017 16:19:50 +0200 Itschak Mugzach wrote: > eth1 receives msgs "martian source..." and yes, I can see high count > of multicast in /proc/net/dev for this device. it look like it still > has iits ipv6 address. martian source means, that you get packages to that

Re: SUSE under ZVM networking issues

>>> On 2/7/2017 at 03:41 PM, Marcy Cortes >>> wrote: > You can go into /etc/udev/rules.d/ > and edit the file associated with the address 402 and set it to layer2 > > Mine has a line like this > ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.3000",

Re: SUSE under ZVM networking issues

You can go into /etc/udev/rules.d/ and edit the file associated with the address 402 and set it to layer2 Mine has a line like this ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.3000", ATTR{layer2}="1" Then reboot -Original Message- From: Linux on 390 Port

Re: SUSE under ZVM networking issues

And ... Thanks to all that helped me understand the problem and led me the way. ITschak On Tue, Feb 7, 2017 at 10:21 PM, Mark Post wrote: > >>> On 2/7/2017 at 03:02 PM, Itschak Mugzach wrote: > > Mark, > > > > I looked into the cookbook (Installing Linux

Re: SUSE under ZVM networking issues

ITschak, I can't seem to respond directly to you since our mail system thinks you are suspicious :) Command line you could do something like qeth_configure -l -f 0.0.0402 0.0.0403 0.0.0404 1 I think that should do it, although haven't tried it myself. I am assuming you are using a real OSA

Re: SUSE under ZVM networking issues

>>> On 2/7/2017 at 03:02 PM, Itschak Mugzach wrote: > Mark, > > I looked into the cookbook (Installing Linux for z Systems on zPDT: A Short > Cookbook) and it instruct not to install layer 2 support... Do they say _why_? Some people seem to avoid Layer 2 for some reason.

Re: SUSE under ZVM networking issues

Mark, I looked into the cookbook (Installing Linux for z Systems on zPDT: A Short Cookbook) and it instruct not to install layer 2 support... OPRMSG: Device address for data channel. (Enter '+++' to abort). OPRMSG: 0.0.0402!> + (enter a null line) OPRMSG: Portname to use. (Enter '+++' to abort).

Re: SUSE under ZVM networking issues

lsqeth returns zero for layer2 on both NICs. using root to echo 1 > /sys/devices/qeth/0.0.0.0400/layer2 returns write error operation not permited... any alternative to this? ITschak On Tue, Feb 7, 2017 at 8:20 PM, Mark Post wrote: > >>> On 2/7/2017 at 08:30 AM, Itschak

Query for Destination z article: How has system programming changed?

How has system programming changed over the mainframe's life? Over your career? What did you do in the early days, what do you do now? Is it still "system programming" or ... what? Has traditional system programming become some/mostly/all system administration? Has how you divide time between

Re: SUSE under ZVM networking issues

>>> On 2/7/2017 at 08:30 AM, Itschak Mugzach wrote: > I was able to change the network interfaces to dhcp using yast lan edit > id=x bootproto=dhcp, and wicked ifup . Now eth0 and eth1 are stalled (?) at > setup in progress and both lease of ipv4 and ipv6 are ipvx dhcp