Yes, that did the trick. Thanks for the solution with such details!
Frank M. Ramaekers Jr.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Vic Cross
Sent: Monday, March 8, 2021 9:43 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets
Frank wrote:
>Okay, following along in "IBM HiperSockets Implementation Guide"
>Chapter 3 "Software configurations for HiperSockets. The command
>"ifconfig enccw0.0.0800 192.168.250.88 netmask 255.255.255.0 up"
>seems to work, only temporarily.
>
>#
...specifically Clef (CentOS) 7.8. Adding hipersockets to a zLinux instance.
Okay, following along in "IBM HiperSockets Implementation Guide" Chapter 3
"Software configurations for HiperSockets. The command "ifconfig enccw0.0.0800
192.168.250.88 netmask 255.255.255.0 up&
: Problem with Hipersockets z13 SUSE 12 Sp4
>>> On 2/5/2019 at 05:00 PM, Marco Banuelos wrote:
> Hi all,
>
> I'm experiencing some problems with SLES 12 SP4 running on z/vm 7.1, I made
> a SLES 12 SP4 installation and I configured with OSA network, now the
> customer w
>>> On 2/6/2019 at 05:10 PM, Alan Altmark wrote:
> On Wednesday, 02/06/2019 at 09:56 GMT, Mark Post wrote:
>
>> How did you connect the HiperSocket to the guest? Did you ATTACH the
> devices
>> to the guest? Did you DEDICATE them in the CP directory? If the
> latter,
>> you'll need to
>>> On 2/5/2019 at 05:00 PM, Marco Banuelos wrote:
> Hi all,
>
> I'm experiencing some problems with SLES 12 SP4 running on z/vm 7.1, I made
> a SLES 12 SP4 installation and I configured with OSA network, now the
> customer want's to switch from OSA to Hipersocket and the HiperSocket network
Marco,
It sounds like the hipersockets connection has not been made visible to the
Linux guest in the z/VM directory. Please verify with your z/VM administrator
that the hipersockets connection has been defined (and that there is some other
guest on that same hipersocket connection so you can
Marco I have Hipersockets with Suse 15 and Ubuntu 18 running in lpar no z/VM on
a zBC12
Sent from MI A2
On Feb. 5, 2019 10:54 p.m., Marco Banuelos wrote:
Hi all,
I'm experiencing some problems with SLES 12 SP4 running on z/vm 7.1, I made a
SLES 12 SP4 installation and I configured with OSA
Hi all,
I'm experiencing some problems with SLES 12 SP4 running on z/vm 7.1, I made a
SLES 12 SP4 installation and I configured with OSA network, now the customer
want's to switch from OSA to Hipersocket and the HiperSocket network it's not
showed on the SLES 12 SP4 vm, I rebooted the vm, I
Cornelia - thank you for your reply.
I am working from the Redbook: Virtualization Cookbook ... Volume 1 and
am finding typos in it. In this case the cio_ignore command was botched
up and included in the description before a set of steps to configure
hipersockets on RH. it should have been step
On Fri, 13 Jul 2018 14:38:44 -0500
Phillip Gramly wrote:
I'm seconding the suggestion of using chzdev, but some additional notes
from me:
> # vmcp q v 204-206
> OSA 0204 ON NIC 0204 UNIT 000 SUBCHANNEL = 0001
> 0204 DEVTYPE HIPER VIRTUAL CHPID 01 IQD
> 0204 MAC
The chzdev command also simplifies things. It's part of s390utils-base.
On 7/14/18, 06:38, "Linux on 390 Port on behalf of R P Herrold"
wrote:
On Fri, 13 Jul 2018, Phillip Gramly wrote:
> # echo 0.0.204,0.0.205,0.0.206 > /sys/bus/ccwgroup/drivers/qeth/group
> -bash: echo:
On Fri, 13 Jul 2018, Phillip Gramly wrote:
> # echo 0.0.204,0.0.205,0.0.206 > /sys/bus/ccwgroup/drivers/qeth/group
> -bash: echo: write error: Invalid argument
>
> I'm missing something somewhere. can anybody help me?
Hi, Phillip,
Thanks for using ClefOS
1. This is just my OCD talking, but I
I have my ClefOS system up which i initially brought up connected to
our VSWITCH (this is under zVM 6.3)
i want to set up Hipersockets using a guest LAN.
i used :
CP DEFINE LAN ZVTSMLAN OWNERID SYSTEM TYPE HIPER IP MFS 64K
and was able to connect to it from a VSE system.
Now i am
On Friday, 11/20/2015 at 02:28 GMT, Grzegorz Powiedziuk
<gpowiedz...@gmail.com> wrote:
> ohhh I see what you are saying (I think so).
>
> I was thinking about standard usage of vswitch bridge so a scenario
where
> all guests have real dedicated hipersockets a
On Friday, 11/20/2015 at 02:02 GMT, David Kreuter
wrote:
> Another advantage is that it uses only one hipersocket triplet whereas
> dedicated hipersocket will end up using one triplet per Linux virtual.
> You can even use the same hiper triplet on each LPAR.
> There is
LPAR.
There is a limit to how many LPARs can connect to the hiper. I've been
scalded by this a few times.
David
Original Message
Subject: Re: hipersockets
From: Grzegorz Powiedziuk <gpowiedz...@gmail.com>
Date: Fri, November 20, 2015 8:47 am
To: LINUX-390@VM.MARIST.EDU
ohhh I see what you are saying (I think so).
I was thinking about standard usage of vswitch bridge so a scenario where
all guests have real dedicated hipersockets and vswitch has one of these
hipersockets as well. This gives hipersocket virtual machines a way to talk
to each other (via
ught about doing vswitch but then AFIK I would end up with with
> > virtual hipersockets on linux guest.
>
> Linux guests can use real HiperSockets with the HiperSocket VSWITCH bridge
> on z/VM. Their traffic will automatically be bridged to a physical LAN
> that can be accessed by z/
I am planning to use hipersockets for internal communication between oracle
nodes in each RAC cluster (oracle nodes run in different lpars).
I've never used real hipersockets before so I am no sure if I understand
this correctly.
>From what I've learned so far, In order to achieve this, we n
be as fast as hipersocket but it doesn't go far out of the box
either.
David Kreuter
Original Message
Subject: Re: hipersockets
From: Alan Altmark <alan_altm...@us.ibm.com>
Date: Thu, November 19, 2015 3:05 pm
To: LINUX-390@VM.MARIST.EDU
On Thursday, 11/19/2015 at 07:
a
> > shared chpid between LPARS. Hipersockets on the same chpid can
> communicate
> > with each other.
>
> Hosts using the same VLAN on the same HiperSocket chpid can talk to each
> other. There are no controls on the VLAN ID that a host is permitted to
> use, so from
On Thursday, 11/19/2015 at 07:38 GMT, Grzegorz Powiedziuk
<gpowiedz...@gmail.com> wrote:
> From what I've learned so far, In order to achieve this, we need to have
a
> shared chpid between LPARS. Hipersockets on the same chpid can
communicate
> with each other.
Hosts usin
Thanks David.
I thought about doing vswitch but then AFIK I would end up with with
virtual hipersockets on linux guest. And I've read in IBMs redbook for
oracle 12:
IBM HiperSockets™ are certified and
supported for the private network. Only a network that is configured with
*real* HiperSockets
On Thursday, 11/19/2015 at 08:35 GMT, Grzegorz Powiedziuk
<gpowiedz...@gmail.com> wrote:
> I thought about doing vswitch but then AFIK I would end up with with
> virtual hipersockets on linux guest.
Linux guests can use real HiperSockets with the HiperSocket VSWITCH bri
On Thu, 2014-05-29 at 17:26 +, Gerard Howells wrote:
Hello All,
As a result of some issues we've been seeing we're looking to implement the
z/VM Hipersockets Early Completion queue feature in our systems. We run VM
6.2 with z/VSE 5.1 and a mixture of SLES 10 SP4 and 11 SP3 guests. I
Hello All,
As a result of some issues we've been seeing we're looking to implement the
z/VM Hipersockets Early Completion queue feature in our systems. We run VM 6.2
with z/VSE 5.1 and a mixture of SLES 10 SP4 and 11 SP3 guests. I know that it's
supported in SLES 11 my question is whether it's
On 5/29/2014 at 01:26 PM, Gerard Howells ghowe...@americafirst.com wrote:
As a result of some issues we've been seeing we're looking to implement the
z/VM Hipersockets Early Completion queue feature in our systems. We run VM
6.2 with z/VSE 5.1 and a mixture of SLES 10 SP4 and 11 SP3 guests
Hi Offer,
All IPtables are off, both for v4 and v6.
Pinging from z/OS to zLinux does not work, nor does traceroute yield anything.
With all this said, I think it has something to do with the way I have routing
set up on the z/OS side. For all OSA traffic, I use OSPF while for
Hipersockets, I
.
Pinging from z/OS to zLinux does not work, nor does traceroute yield
anything. With all this said, I think it has something to do with the way I
have routing set up on the z/OS side. For all OSA traffic, I use OSPF while
for Hipersockets, I use static routing.
- The reason I think this is because
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets between RHEL and z/OS
Hi
You might be correct and this is a sourcevipa issue but i cant tell as i am
lacking some data...
Not many know this but the order of the home statment matters... you must place
your hiper sockets interface before your
://www.dclibrary.ideascale.com
-Original Message-
From: Diep, David (OCTO-Contractor)
Sent: Monday, November 04, 2013 12:01 PM
To: LINUX-390@VM.MARIST.EDU
Subject: RE: Hipersockets between RHEL and z/OS
Offer,
I have a test system... let me give it a shot.
Right now, I know for a fact that my HS Home IP address
Offer,
It does work... why on earth?
I see from a packet trace that anything going to a Hipersockets address
(5.5.5.0) has a source IP address of 5.5.5.x, while anything going out normal
OSAD, leaves with the VIPA address.
What is with the HOME statement? I recall from OS390 TCPIP
to a Hipersockets address
(5.5.5.0) has a source IP address of 5.5.5.x, while anything going out
normal OSAD, leaves with the VIPA address.
What is with the HOME statement? I recall from OS390 TCPIP that the order
made a difference, but I don't recall why?
David Diep
What would you like to see
12:54 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets between RHEL and z/OS
First of all i am glad to here it works...
The home statment order only matters with vipa addresses...
The way it works is all addresses after the vipa are sourced by it if the
sourcevipa parameter is specified
On Nov 1, 2013 7:06 PM, Diep, David (OCTO-Contractor) david.d...@dc.gov
wrote:
Hi Everyone,
I got a good one (I think)... did I imagine this working at one point?
I am not able to connect from my z/OS Hipersockets to my RHEL6.2
Hipersockets.
I am able to successfully initiate a connection
Hi Everyone,
I got a good one (I think)... did I imagine this working at one point?
I am not able to connect from my z/OS Hipersockets to my RHEL6.2 Hipersockets.
I am able to successfully initiate a connection from my RHEL6.2 Hipersockets to
my z/OS Hipersockets.
I am able
What is the message that is telling you that you can not connect to your
z/OS hipersocket?
Regards,
J.B. Mills III
Solutions Architect
1515 Poydras Street
Suite 1925
New Orleans, LA. 70112
Cell 614-226-0284
jmil...@us.ibm.com
The only difference between a good day and a bad day, is your
Mills
III
Sent: Friday, November 01, 2013 1:43 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets between RHEL and z/OS
What is the message that is telling you that you can not connect to your z/OS
hipersocket?
Regards,
J.B. Mills III
Solutions Architect
1515 Poydras Street
Suite 1925
Is the request going out your default route as opposed to the hipersocket?
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Diep,
David (OCTO-Contractor)
Sent: Friday, November 01, 2013 2:02 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets
Emmit,
That could very well be the case... I did not define a specific route for
Hipersockets in RHEL (always wondered about that). As for my z/OS, I use OSPF
for routing, but static routes for Hipersockets traffic.
;
DEVICE IUTIQDED MPCIPA
, November 01, 2013 2:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets between RHEL and z/OS
Emmit,
That could very well be the case... I did not define a specific route for
Hipersockets in RHEL (always wondered about that). As for my z/OS, I use OSPF
for routing, but static routes
[mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Chase,
John
Sent: Wednesday, February 27, 2013 1:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets broke Ethernet?
-Original Message-
From: Chase, John
[ snip ]
Now, what's missing from this file that is present in the same file
, February 27, 2013 1:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets broke Ethernet?
-Original Message-
From: Chase, John
[ snip ]
Now, what's missing from this file that is present in the same file on
our golden image is the
statement:
OPTIONS=layer2=0 portno=0
I
the penguin that
doesn't talk while he was trying to figure out Hipersockets.
I also notice the golden copy has BOOTPROTO=static instead of none.
I'll set both back to golden and see what happens.
And that fixed that problem. We now have both interfaces working, but the
hipersockets network appears
Hi, All,
We're just getting started with Linux (RHEL6.3) on z/VM (6.2, non-SSI). We
generally followed the Virtualization Cookbook published by Mike MacIsaac and
others at IBM, and got our first RHEL web server up and running. Then we tried
to define a Hipersockets network (this server
On 2/26/2013 at 04:48 PM, Chase, John jch...@ussco.com wrote:
How do we configure Linux so that both interfaces (eth0 and hsi0) are
configured at startup time?
Look at /etc/sysconfig/network-scripts/ifcfg-eth0 to see what is in there for
ONBOOT. For the interface to be started
of the
hipersockets virtual devices (but after the guest is started, ifconfig shows
only the hipersockets interface as active).
Here's the VM logon of the guest:
LOGON AT 15:40:29 CST TUESDAY 02/26/13
Command complete
On 2/26/2013 at 06:08 PM, Chase, John jch...@ussco.com wrote:
-snip-
Tried an interactive IPL and startup of the Linux vm, and saw some error
messages that indicate we've got some misteaks [sic] in the definitions of
the hipersockets virtual devices (but after the guest is started
How are 7000-7002 defined? Seeing the directory entry would be useful too. An
error is happening before the ipl moment.
David Kreuter
Original message
From: Mark Post mp...@suse.com
Date:
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets broke Ethernet?
On 2/26
:
OPTIONS=layer2=0 portno=0
I don't know why that statement is missing, unless our network guy deleted it
from the penguin that doesn't talk while he was trying to figure out
Hipersockets.
I also notice the golden copy has BOOTPROTO=static instead of none.
I'll set both back to golden and see
, what's missing from this file that is present in the same file on our
golden image is the statement:
OPTIONS=layer2=0 portno=0
I don't know why that statement is missing, unless our network guy deleted it
from the penguin that doesn't talk while he was trying to figure out Hipersockets.
I
-Original Message-
From: Linux on 390 Port On Behalf Of Lee Stewart
RHEL has an error where if you use system-config-network on a layer 2
interface it forgets that it
was layer 2. Reported a year ago as Bug
809534 - system-config-network ignores option field. No fix.
Did you
of those
*real* hipersockets.
(haven't we been here before ... ;-)
The ephemeral energy-to-matter converter modules are already included at
no additional charge. ;-)
Alan Altmark
Senior Managing z/VM and Linux Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
I guess my main drive to use a common guest LAN was to avoid having to assign a
unique device set for each zLinux guest by specifying a SPECIAL definition in
each. The main use for the Hipersocket connections would be to run zLinux
backup/restore processing based on the MVS platform, and I
there is a misunderstanding. I have no objection to real
HiperSockets for backups (or any other reason) as long as you realize that
HiperSockets consume z CPU cycles since it is the CPU that moves the data,
not the IOPs.
If I make it simple and define unique devices to each user, how do I
fail over
On Tue, Jul 17, 2012 at 7:50 PM, Alan Altmark alan_altm...@us.ibm.comwrote:
Perhaps there is a misunderstanding. I have no objection to real
HiperSockets for backups (or any other reason) as long as you realize that
HiperSockets consume z CPU cycles since it is the CPU that moves the data
I'm not able to get any response back to my zlinux guest over a guest LAN I've
set up for Hipersocket connections.
I've defined IP/ADDR 5.1.1.1 as a VM home address, 5.1.1.3 as the MVS home and
set up the Linux guest as 5.1.2.10.
A static route for 5.1.2.0/24 has been defined under MVS to point
On Mon, Jul 16, 2012 at 04:59:49PM +, Norris, Chet wrote:
I've defined IP/ADDR 5.1.1.1 as a VM home address, 5.1.1.3 as the MVS home
and set up the Linux guest as 5.1.2.10.
It would be preferable if you could use RFC 1918 allocations for your legacy IP
interconnections. Just using random IP
, and visa versa.
Any ideas?
Yes, your network diagram is messed up. Your picture is
Linux [Guest LAN] TCPIP [HiperSockets] MVS
TCPIP is connected to two HiperSocket networks: one real (to MVS) and one
virtual (to Linux). So TCPIP will need two HiperSocket interfaces, each
with it's own IP
On 7/16/2012 at 04:37 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
TCPIP is connected to two HiperSocket networks: one real (to MVS) and one
virtual (to Linux). So TCPIP will need two HiperSocket interfaces, each
with it's own IP address in each of the two networks. You have the real
On Monday, 07/16/2012 at 09:44 EDT, Mark Post mp...@suse.com wrote:
Alternatively, he could just attach a real HiperSocket device to the
Linux
system and cut out the middle man (z/VM TCPIP) entirely. Unless there's
some
value to be had by having z/VM manage the traffic, it's just unnecessary
On Tue, Jul 17th, 2012 at 6:37 AM, Alan Altmark wrote:
...
TCPIP is connected to two HiperSocket networks: one real (to MVS) and one
virtual (to Linux).
Now, hold it right there fella. I want the order number for one of those
*real* hipersockets.
(haven't we been here before ... ;-)
Shane
@VM.MARIST.EDU
Subject: Re: Hipersockets
If the OP wants to look on the z/OS side, I can think of three methods.
z/OS console command:
D TCPIP,,NETSTAT,DEVLINKS
D TCPIP,,NETSTAT,ROUTE
D TCPIP,,NETSTAT,HOME
z/OS TSO command:
NETSTAT DEVLINKS
NETSTAT ROUTE
NETSTAT HOME
z/OS UNIX command:
netstat -d
Correct the address of z/os is 192.168.1.11
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Tuesday, June 26, 2012 4:13 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets
On 6/26/2012 at 02:29 PM, Marcy Cortes marcy.d.cor
-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On
Behalf Of Schwartz, Rodney (R.)
Sent: Wednesday, June 27, 2012 5:49 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets
The ping times out from both the z/os and zlinux. We have
multiple z/os systems and they can ping each other
, 2012 8:26 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets
Another silly question from me. Is the z/Linux system using iptables to do
firewalling? I don't know what z/Linux installs as a default.
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151
I am trying to get Hipersockets working between z/os and zlinux system (sles 10
SP2 running under z/vm 6.2). I have a dedicated IOD address attached:
OSA FB00 ATTACHED TO LINUX02 7000 DEVTYPE HIPER CHPID FB IQD
OSA FB01 ATTACHED TO LINUX02 7001 DEVTYPE HIPER CHPID FB IQD
OSA
Subject: [LINUX-390] Hipersockets
I am trying to get Hipersockets working between z/os and zlinux system (sles 10
SP2 running under z/vm 6.2). I have a dedicated IOD address attached:
OSA FB00 ATTACHED TO LINUX02 7000 DEVTYPE HIPER CHPID FB IQD
OSA FB01 ATTACHED TO LINUX02 7001 DEVTYPE
On 6/26/2012 at 02:29 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com
wrote:
ip address is 192.169.1.11
I hope that was a typo and you meant the address of z/OS is 192.168.1.11?
One way to figure that out would be to start tcpdump on the hsi0 interface and
see what kind of IP addresses
If the OP wants to look on the z/OS side, I can think of three methods.
z/OS console command:
D TCPIP,,NETSTAT,DEVLINKS
D TCPIP,,NETSTAT,ROUTE
D TCPIP,,NETSTAT,HOME
z/OS TSO command:
NETSTAT DEVLINKS
NETSTAT ROUTE
NETSTAT HOME
z/OS UNIX command:
netstat -d
netstat -r
netstat -h
The
Well I finally was able to schedule a power on reset changing chparm=00
to chparm=C0 on the hipersockets iocp definition. I then added mtu=57344 to
ifcfg-hsi0, did an ifdown and ifup for hsi0. I then changed vse's tcpip
definition to mtu=57344. I conducted another test and the time
of this file?
By the way, you have chosen layer2=1 for your hsi0-device. This is ok,
but it allows communication to other layer2 HiperSockets participants
only, no layer3 HiperSockets participants.
Regards, Ursula Braun, IBM Germany
On Tue, 2011-11-08 at 08:39 +0100, Roger Evans wrote:
Hi
. This is ok,
but it allows communication to other layer2 HiperSockets participants
only, no layer3 HiperSockets participants.
Regards, Ursula Braun, IBM Germany
On Tue, 2011-11-08 at 08:39 +0100, Roger Evans wrote:
Hi, Ursula
uname -a
Linux DPRODDB2 2.6.32.46-0.3-default #1 SMP 2011-09
the ifup step fails. The configuration file
for ifup is /etc/sysconfig/network/ifcfg-hsi0. Can you check the
definitions of this file?
By the way, you have chosen layer2=1 for your hsi0-device. This is ok,
but it allows communication to other layer2 HiperSockets participants
only, no layer3
Roger,
get rid of the LLADDR='00:00:00:00:00:00' definition. ifup does no
longer work for a zero MAC-address. HiperSockets define a MAC-address;
during initialization Linux determines this MAC-address and uses it, if
LLADDR is not defined.
Ursula
On Tue, 2011-11-08 at 10:47 +0100, Roger Evans
Roger,
when configuring a network interface with yast, a udev-rule is created
for the device containing qeth attribute definitions, among them
attribute layer2. Look into /etc/udev/rules.d and check a rule starting
with 51-...7000... . I assume this rule contains a line with layer2=1.
Change this
Thank you, Ursula
That solved the problem. I can now ping and ftp between my layer3
hipersockets. I still get the Waiting for mandatory devices.
hsi-bus-ccw-0.0.7000 No interface found msg. when booting
but now that it works, I'll just stop watching.
You're pretty amazing. Think
ping and ftp between my layer3
hipersockets. I still get the Waiting for mandatory devices.
hsi-bus-ccw-0.0.7000 No interface found msg. when booting
but now that it works, I'll just stop watching.
You're pretty amazing. Think you could fix the Greek deficit crisis,
too
-bus-ccw-0.0.7000. Those are no
longer needed for SLES11 and can be removed.
Ursula
On Tue, 2011-11-08 at 12:58 +0100, Roger Evans wrote:
Thank you, Ursula
That solved the problem. I can now ping and ftp between my layer3
hipersockets. I still get the Waiting for mandatory devices
vennlig hilsen
Roger Evans
Roger,
the HiperSockets issue after HW upgrade requires a Linux upgrade:
- see Novell bugzilla 659101 for SLES11 SP1
- see Novell bugzilla 662984 for SLES10 SP4
- RHEL 5.7
- RHEL 6.1
Description: qdio: use proper QEBSM operand for SIGA-R and SIGA-S
Symptom
QIOASSIST is ON or OFF.
Regards/
Med vennlig hilsen
Roger Evans
Roger,
the HiperSockets issue after HW upgrade requires a Linux upgrade:
- see Novell bugzilla 659101 for SLES11 SP1
- see Novell bugzilla 662984 for SLES10 SP4
- RHEL 5.7
- RHEL 6.1
Description: qdio: use
Roger,
the minimum SLES11 SP1 kernel level should be 2.6.32.29-0.3.1. If you
still have problems with a kernel level greater or equal to this one,
something else is wrong. Which qeth-related messages show up in dmesg?
What does lsqeth return?
Regards, Ursula Braun, IBM Germany
On Mon,
Hi, Ursula
uname -a
Linux DPRODDB2 2.6.32.46-0.3-default #1 SMP 2011-09-29 17:49:31 +0200
s390x s390x s390x GNU/Linux
lsqeth
... [other devices]
Device name : hsi0
-
card_type : HiperSockets
cdev0
Can you try turning off QIOASSIST for the guest and see
if that makes a difference?
Regards,
Sue Farrell
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message:
Hi Sue
Didn't seem to help. When booting with SLES10v2 I see the following
when watching the boot from VM:
-
eth: IPv6 not supported on
Display the kernel storage at 10b03a60.8 - in there is the instruction
giving the exception. The b2220030 is the IPM used to retrieve the condition
code from the previous instruction so it can be placed in a C variable.
On 11/4/11 9:18 AM, Roger Evans ro...@autodata.no wrote:
Hi Sue
Didn't
What version of z/VM is this?
z/VM Version 5 Release 4.0, Service Level 1101 (64-bit),
Do you have all the Linux related maintenance installed for it?
Hard to tell. Is there one place we can go to find out what is needed?
We have installed all the APARS that IBM told us were necessary to run
SuSE 10.2
uname returns: kernel 2.6.16.60-0.21-default
I'm also trying to configure hsi0 with YAST on SuSE 11sp1
When I try to bring the interface up with ifup, I get:
--
#ifup hsi0
hsi0 name: Hipersocket
On 11/1/2011 at 08:12 AM, Roger Evans ro...@autodata.no wrote:
SuSE 10.2
uname returns: kernel 2.6.16.60-0.21-default
That's the SLES10 SP2 GA kernel, which is 2.5 years old. I think it might be
time to apply some maintenance. :(
I'm also trying to configure hsi0 with YAST on SuSE 11sp1
Good morning, Mailing list
We upgraded from a z9 to a z114 during the weekend, Most things seem
to be working fine, but none of my linux hipersocket interfaces come
up.
When I try ifup hsi0, I get the following:
# ifup hsi0
hsi0
hsi0 configuration: hsi-bus-ccw-0.0.7000
On 10/31/2011 at 06:00 AM, Roger Evans ro...@autodata.no wrote:
Good morning, Mailing list
We upgraded from a z9 to a z114 during the weekend, Most things seem
to be working fine, but none of my linux hipersocket interfaces come
up.
-snip-
None of our VM or linux definitions have
Kyle,
please try to add line
ARP=no
to your
/etc/sysconfig/network-scripts/ifcfg-hsi0
configuration file.
Regards, Ursula
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to
On 1/31/2011 at 01:49 PM, Kyle Stewart kyle.stew...@zionsbancorp.com
wrote:
Mark,
Here is what we have:
The hsi0 is a real hipersocket
Linux netstat
[z034876@UTLZ0002 ~]$ netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
On Tuesday, 02/01/2011 at 06:06 EST, Mark Post mp...@novell.com wrote:
What do the US and UH flags mean? What's the reason for the host route
to
10.90.3.20?
U = Up (if interface is down, flag not set, route won't be used)
S = Static (i.e. human-induced config somewhere)
H = Host route
Alan
30, 2011 7:52 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets Not working z/Linux to z/VM z/OS
On 1/30/2011 at 03:19 AM, Naspa stewk...@naspa.net wrote:
Greetings All!
We have been struggling trying to get our z/VM z/OS systems to talk via
hipersockets to our RHEL5.3 Linux (under z
On Monday, 01/31/2011 at 05:22 EST, Kyle Stewart
kyle.stew...@zionsbancorp.com wrote:
We have been struggling trying to get our z/VM z/OS systems to talk
via
hipersockets to our RHEL5.3 Linux (under z/VM 6.1). We can ping out
from
Linux to VM or to z/OS, but when we ping into Linux from z
Greetings All!
We have been struggling trying to get our z/VM z/OS systems to talk via
hipersockets to our RHEL5.3 Linux (under z/VM 6.1). We can ping out from
Linux to VM or to z/OS, but when we ping into Linux from z/VM z/OS the
'tcpdump -I hsi0 ip proto \\icmp' on the Linux only shows
I forgot to mention that we can ping via hsi0 to /from either of the Linux
guests.
-Original Message-
From: Naspa
Sent: Sunday, January 30, 2011 1:19 AM
To: 'Linux on 390 Port'
Subject: Hipersockets Not working z/Linux to z/VM z/OS
Greetings All!
We have been struggling trying to get
On 1/30/2011 at 03:19 AM, Naspa stewk...@naspa.net wrote:
Greetings All!
We have been struggling trying to get our z/VM z/OS systems to talk via
hipersockets to our RHEL5.3 Linux (under z/VM 6.1). We can ping out from
Linux to VM or to z/OS, but when we ping into Linux from z/VM z/OS
1 - 100 of 458 matches
Mail list logo