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

rom: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Itschak Mugzach Sent: Tuesday, February 07, 2017 12:03 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SUSE under ZVM networking issues Mark, I looked into the cookbook (Installing Linux for z Systems on zPDT: A Short Cookbo

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

rom: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Itschak Mugzach Sent: Tuesday, February 07, 2017 12:03 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SUSE under ZVM networking issues Mark, I looked into the cookbook (Installing Linux for z Systems on zPDT: A Short Cookbook

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

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

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

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

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

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

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 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 2/5/2017 at 11:21 AM, Itschak Mugzach wrote: > I installed SLES 12 on a zPDT server as a stand alone ("basic mode"). I was Is this a SLES12 GA, SLES12 SP1, or SLES12 SP2 system? Hopefully SLES12 SP2, since SLES12 GA is out of support and SLES12 SP1 will be soon. >

Re: SUSE under ZVM networking issues

For what you describe, I would recommend attaching the NIC to the guest, which is what you did. But sinfe Linux was already installed, it should be the same zPDT NIC as the one online when you did the installation. The system typically fingerprints (my term) hardware these days, so if the NIC

SUSE under ZVM networking issues

I installed SLES 12 on a zPDT server as a stand alone ("basic mode"). I was able to connect to the image using vnc using the tap connection. I than defined a user in VM's user direct and IPLed the image. That works find, but now I am unable to connect to network. It is my understanding that there