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 Gunreben <b...@suse.de> wrote:
> On Tue, 7 Feb 2017 10:41:11 +0200
> Itschak Mugzach <imugz...@gmail.com> 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 suse. I found two rule files for
> > qeth for devices 400 and 404. should they be kept?
> > anyway, after recycle I had many "martian source" mesages that ifoff
> > eth0 eth1 stopped. When I try to config the nics with other
> > addresses, and ping, I get "network is unreachable" on both. I am
> > using a dhcp with mac reservation so no need static addresses. How
> > can I cause suse ask for an address from dhcp?
>
> I would proceed like this:
>
> 1. # lsqeth -> this should result in some device that is online. If this
> there is none, you can use
> # qeth_configure -l 0.0.0400 0.0.0401 0.0.0402 1
> # qeth_configure -l 0.0.0404 0.0.0405 0.0.0406 1
> assuming the OSA devices are located at 400 and 404
>
> 2. From lsqeth, you have a device name like eth0. Then:
> # cd /etc/sysconfig/network
> # echo "BOOTPROTO='dhcp'" > ifcfg-eth0
> # echo "STARTMODE='auto'" >> ifcfg-eth0
>
> 3. restart the network
> # rcnetwork restart
>
> 4. check if you got some ip address with
> # ip a s
> check if you got a default route
> # ip r s
> try to ping some machine from there. To stop the ping, you can use
> ^C (two characters) in 3270.
>
> Berthold
>
> >
> > Best,
> > ITschak
> >
> > On Mon, Feb 6, 2017 at 11:23 PM, Mark Post <mp...@suse.com> wrote:
> >
> > > >>> On 2/5/2017 at 11:21 AM, Itschak Mugzach <imugz...@gmail.com>
> > > >>> 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.
> > > > 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 are two option: using a vswitch
> > > > or
> > > attach
> > > > the osa device to the guest. I tried the second one. However, as
> > > > I can't connect to the server I can only use cli...
> > >
> > > Neither one will make any difference to the Linux system. Either
> > > NIC looks the same to it.
> > >
> > > > I am looking for a document that explain step by step how to
> > > > configure networking in a 4 level environment: Linux > zPDT > ZVM
> > > > > SLES guest.
> > >
> > > There isn't one, specifically, since as I said above, the Linux
> > > system doesn't care about all the higher layers. So, when you say
> > > "cli" do you mean a z/VM console environment, or a Linux terminal
> > > environment? If the latter, then "yast lan" will let you take care
> > > of things.
> > >
> > > If you're working from the z/VM console for the guest, then things
> > > get a bit more tedious, but still very workable. If that is the
> > > case, let us know and we can walk you through it. The easiest
> > > thing to try might be to simply
> > > delete /etc/udev/rules.d/70-persistent-net.rules and reboot.
> > >
> > >
> > > Mark Post
> > >
> > > ----------------------------------------------------------------------
> > > 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/
> > >
> >
> >
> >
> > --
> > ITschak Mugzach
> > *|** IronSphere Platform* *|** An IT GRC for Legacy systems* *|
> > Automated Security Readiness Reviews (SRR) **|*
> >
> > ----------------------------------------------------------------------
> > 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/
>
>
>
> --
> ----------------------------------------------------------------------
> Berthold Gunreben OPS Services Team
> http://www.suse.de/ Maxfeldstr. 5
> SUSE Linux GmbH, D-90409 Nuernberg, Germany, HRB 21284 (AG Nürnberg)
> GF: Felix Imendörffer, Jane Smithard, Graham Norton
>
> ----------------------------------------------------------------------
> 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/
>
--
ITschak Mugzach
*|** IronSphere Platform* *|** An IT GRC for Legacy systems* *| Automated
Security Readiness Reviews (SRR) **|*
----------------------------------------------------------------------
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/
