>>> 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",
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
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
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
>>> 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.
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).
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
>>> 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
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.
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
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
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
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
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
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,
>>> 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.
>
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
17 matches
Mail list logo