On Thu, Apr 8, 2021, 12:12 PM Davis, Larry (National VM Capability) <
larry.dav...@dxc.com> wrote:
> We are seeing an Issue when Using Hipersockets connected to a DB2 system
> on z/OS
>
> When we perform a VMRELOCATE (LGR) to another member in the complex we
> lose the HS device and it goes
On 4/20/21 2:04 PM, Stefan Raspl wrote:
> This is really a shot in the dark, but: Could it be a case where the
> device number from source and target system are different, and you have
> the target system's device IDs on the cio ignore list prior to the
> migration? I.e. what happens in case you
About LGR and Hipersocket using RHEL 7.7
Larry,
If this isn't resolved, I'd suggest you open a z/VM support case and the team
and take a closer look.
Thanks,
Bill
___
Bill Bitner - z/VM Client Focus and Care
Hi Larry,
On 4/8/21 6:11 PM, Davis, Larry (National VM Capability) wrote:
We are seeing an Issue when Using Hipersockets connected to a DB2 system on z/OS
When we perform a VMRELOCATE (LGR) to another member in the complex we lose the
HS device and it goes offline
The Relocate works fine the
Larry,
If this isn't resolved, I'd suggest you open a z/VM support case and the
team and take a closer look.
Thanks,
Bill
___
Bill Bitner - z/VM Client Focus and Care - 607-429-3286
bitn...@us.ibm.com
"Making
We are seeing an Issue when Using Hipersockets connected to a DB2 system on z/OS
When we perform a VMRELOCATE (LGR) to another member in the complex we lose the
HS device and it goes offline
The Relocate works fine the HS devices have the same EQID and we see the
devices attached on the
a new HiperSocket device (taken from the list with the
unconfigured):
sudo znetconf -a d200
Scanning for network devices...
Successfully configured device 0.0.d200 (encd200)
You should now see it as configured here:
znetconf -c | grep HiperSockets
0.0.d200,0.0.d201,0.0.d202 1731/05 HiperSockets
Answered on IBMVM.
Regards,
Alan
Archana P --- Re: [LINUX-390] How to configure hipersocket for Ubuntu on
LPAR ---
From:"Archana P" <dollarpo...@gmail.com>To:LINUX-390@VM.MARIST.EDUDate:Wed,
Oct 26, 2016 4:21 AMSubject:Re: [LINUX-390] How to configure hipersocket for
Hi guys,
I need your help regarding setting up the hipersocket between the Ubuntu
and zACI lpars , the Ubuntu is directly installed on the LPAR something as
shown below.
Regards,
Archana
On Tue, Oct 25, 2016 at 10:11 PM, Mark Post <mp...@suse.com> wrote:
> >>> On 10/2
Can anyone recommend the best hipersocket MTU size for DB/2 Text Search from
z/OS to z/Linux ?
Choices are 8k/16k/32k/56k.
--
Donald J.
dona...@4email.net
--
http://www.fastmail.com - Access all of your messages and folders
wherever you
...@4email.net wrote:
Can anyone recommend the best hipersocket MTU size for DB/2 Text Search
from z/OS to z/Linux ?
Choices are 8k/16k/32k/56k.
In many cases it probably will not matter unless the data volume is really
massive. If it does matter, then you need very specific configuration
On 28 January 2015 at 15:03, Donald J. dona...@4email.net wrote:
Not sure about massive, but fairly large, 16.5M rows.
The initial build and index setup took 8.1G diskspace on Linux.
I will get a packet trace.
That sounds like enough to at least consider to worry about things.
The benefit
On 28 January 2015 at 14:20, Donald J. dona...@4email.net wrote:
Can anyone recommend the best hipersocket MTU size for DB/2 Text Search
from z/OS to z/Linux ?
Choices are 8k/16k/32k/56k.
In many cases it probably will not matter unless the data volume is really
massive. If it does matter
I am sure that I have ever heard a better word for programming than
Entwicklung
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Peter
Linnell
Sent: Wednesday, August 07, 2013 5:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket
I am sure that I have NOT ever heard a better word for programming than
Entwicklung
-Original Message-
From: Dean, David (I/S)
Sent: Thursday, August 08, 2013 9:11 AM
To: 'Linux on 390 Port'
Subject: RE: TX-Errs on hipersocket interface.
I am sure that I have ever heard a better word
Hi all,
I will not be at SHARE in Boston, there will be some new faces who are new to
mainframe from SUSE SE team. I know you folks will treat them kindly :)
That said the real reason for S.u.S.E is related to a former law in Germany
which required a company's name to reflect what they did.
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten
Otte [co...@de.ibm.com] Sent: Thursday, July 25, 2013 7:53 AM To:
LINUX-390@VM.MARIST.EDU Subject: Re: TX-Errs on hipersocket interface.
Alan wrote:
Carsten, this is information
On 2 August 2013 13:45, Billy R. Bingham brbing...@stx.rr.com wrote:
I for one would like to know. :) You don't have
to post to the list, you can email me private,
or if you perfer you can post a URL where I can
read about it.
Right! Did someone miss the fact that it's Friday? First thing
, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Alan wrote:
Carsten, this is information that really needs to be in the Device Driver
book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right - that would be accouned as dropped
...@linux.vnet.ibm.com]
Sent: Friday, July 26, 2013 3:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Jon,
without any performance data my answer can be only vague. But let's
assume a performance increase for data sending when moving from SLES10
to SLES11. If the receiver has
.
Regards, Ursula Braun, Linux on System z Development, IBM Germany
On Thu, 2013-07-25 at 18:21 +, Veencamp, Jonathon D. wrote:
Question: Why would SLES 11 see hipersocket retransmits and window
adjustments and not SLES 10? Is the device driver either more forgiving or
efficient on SLES 10
www.baldor.com
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Ursula Braun
[ubr...@linux.vnet.ibm.com]
Sent: Friday, July 26, 2013 3:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Jon,
without any
Ron,
TX errors on a Hipersocket are business as usual. When the receiver fails
to pick up packets at the same rate that the transmitter transmits, the
queues will run full over time. TCP uses packet loss as a measure to
tune the TCP window size, which effectively will reduce the transmit rate
On Thursday, 07/25/2013 at 02:58 EDT, Carsten Otte co...@de.ibm.com
wrote:
TX errors on a Hipersocket are business as usual. When the receiver
fails
to pick up packets at the same rate that the transmitter transmits, the
queues will run full over time. TCP uses packet loss as a measure to
tune
Alan wrote:
Carsten, this is information that really needs to be in the Device Driver
book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right - that would be accouned as dropped, not TX error. Forget
about my
reply then, time to look at other causes for that TX
...@de.ibm.com]
Sent: Thursday, July 25, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Alan wrote:
Carsten, this is information that really needs to be in the Device Driver
book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right
Address:rfos...@baldor.com
www.baldor.com
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte
[co...@de.ibm.com]
Sent: Thursday, July 25, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface
Question: Why would SLES 11 see hipersocket retransmits and window adjustments
and not SLES 10? Is the device driver either more forgiving or efficient on
SLES 10?
I'm just curious. I may be in the same situation soon.
Regards
Jon Veencamp
Federated Insurance
-Original Message
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte
[co...@de.ibm.com]
Sent: Thursday, July 25, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Alan wrote:
Carsten, this is information that really needs to be in the Device
Ron,
See page 11 of this presentation:
http://www.vm.ibm.com/service/vmreqzeh.html
This presentation is found on
http://www.ibm.com/developerworks/linux/linux390/perf/tuning_networking.htmlwhere
there are other good tuning tips.
On Thu, Jul 25, 2013 at 2:42 PM, Ron Foster
Hello,
While investigating another problem, I did a netstat -I on our production SAP
Linux App Servers.
To my surprise, I am getting TX-ERRS on a hipersocket interface on two of our
systems. The two systems have recently been converted to SLES11 SP2. The
hipersocket device is connected
On 15 June 2013 17:58, Ron Foster ron.fos...@baldor.abb.com wrote:
Rob,
The traffic is between our Sap application servers running under zvm.
I'm surprised the traffic would be that impressive. Normally I see
bandwidth requirements with SAP for the transport data via NFS. For the
real
On 13 June 2013 23:58, Ron Foster ron.fos...@baldor.abb.com wrote:
3. One of the things that the TCP IP folks want us to do on the hardware
side is to increase the maximum frame size to 64k. for this hipersocket.
4. This would normally increase the MTU size to 56k for the hipersocket.
5
...@gmail.com]
Sent: Saturday, June 15, 2013 2:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Appropriate hipersocket MFS size for use with SAP Apps Servers
On 13 June 2013 23:58, Ron Foster ron.fos...@baldor.abb.com wrote:
3. One of the things that the TCP IP folks want us to do on the hardware
side
3. One of the things that the TCP IP folks want us to do on the hardware side
is to increase the maximum frame size to 64k. for this hipersocket.
4. This would normally increase the MTU size to 56k for the hipersocket.
5. If I remember properly the 56k value would exceed the SAP
On 6/13/2013 2:28 PM, Ron Foster wrote:
Anyone have any experience running SAP apps servers under z/vm with a larger
than 8k MTU size?
We run with a 16K MFS and an 8K MTU. Like you, we use a single
hipersocket CHPID.
However, we're still on z/OS 1.12 with plans to upgrade to z/OS 1.13
Hello listers,
We have a bunch of SAP application servers running under z/vm. They are all
pointed at the same z/os 1.13 system. There are several DB2s running on this
z/OS system. All the Apps servers are using the same hipersocket chpid to
communicate to the z/os system the same
hipersocket chpid
to
communicate to the z/os system the same hipersocket chipid. Since going
to z/OS
1.13, we are experiencing storage creep in our TCPIP address space.
This hipersocket is using a 8k MTU size. I believe this to be the SAP
recommended size.
Our z/os support folks are being told
Alan,
I went to talk to the z/os guy to get a better understanding of what the TCP IP
folks are wanting done.
I now have a better understanding of what is going on.
1. We have so much data flowing through the hipersocket chipid that we are
experiencing queueing in the hipersocket
...@its.ms.gov
Sent: Friday, January 20, 2012 3:18 PM
To: LINUX-390@VM.MARIST.EDU
Subject: hipersocket question for dummies (me )
We are having a connection issue with a couple of our linux guests that
simply proves I don't know what I'm doing AND I can't seem to RTFM
correctly
Environment is Suse 11
it -
would someone please point this dba who is subbing as a sysprog in the
right direction.
You're right, it's simple. That said, it's not obvious. But since you're
just subbing, all is forgiven. :-)
Each HiperSocket chpid is its own LAN segment. They are not bridged
together. So the hosts
that one stack has two sets of hipersockets defined to it the
networks can't see each other.
3. From z/VM MAINT userid do a:
Q CHPID E8
Q CHPID E9
this will show you the devices bolted off each chpid - could be
informative!
4. where possible I like to have only a few hipersocket IQD chpids -
hopefully
in the
right direction.
You're right, it's simple. That said, it's not obvious. But since you're
just subbing, all is forgiven. :-)
Each HiperSocket chpid is its own LAN segment. They are not bridged
together. So the hosts using E8 have to go through a *router* (e.g.
Linux, z/OS, z/VM) to get a host
We are having a connection issue with a couple of our linux guests that
simply proves I don't know what I'm doing AND I can't seem to RTFM
correctly
Environment is Suse 11 guests on z/VM 6 trying to connect to z/OS 1.12 on
a z196,
The first 8 guests work just fine - z/OS IP address is
.
- However our SLES11, despite pinging the other SLES10s in net
192.0.1.x fails on pinging z/VM 192.0.1.x address.
That is, it seems like z/VM TCPIP can ping every SLES10 Hipersocket
but can't ping the SLES11 hipersocket.
I tried to attach a jpg picture explaining this but the system didn't allow
me
other successfully
- All SLES10s ping z/VM 192.0.1.x address successfully.
- However our SLES11, despite pinging the other SLES10s in net
192.0.1.x fails on pinging z/VM 192.0.1.x address.
That is, it seems like z/VM TCPIP can ping every SLES10 Hipersocket
but can't ping the SLES11
What is the recommendation or general practice regarding hipersocket
addresses and dns?
Do you register the hipersocket address in the dns or stick with
referencing it via the octet?
Thanks
Lionel B. Dyck
z/Linux Specialist
IBM Corporation
Global Technology Services - Kaiser Account
Work
isn't that hard.
Mauro
http://mauro.limeiratem.com - registered Linux User: 294521
Scripture is both history, and a love letter from God.
On Mon, Dec 21, 2009 at 1:06 PM, Lionel Dyck ld...@us.ibm.com wrote:
What is the recommendation or general practice regarding hipersocket
addresses and dns
-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Lionel
Dyck
Sent: Monday, December 21, 2009 7:07 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] HiperSocket Advice
What is the recommendation or general practice regarding hipersocket
addresses and dns?
Do you register
On 12/21/09 10:06 AM, Lionel Dyck ld...@us.ibm.com wrote:
What is the recommendation or general practice regarding hipersocket
addresses and dns?
Same as any other address: put it in the DNS with a unique name, eg
host-hsi1.foo.bar.com
Do you register the hipersocket address in the dns
HI All
Anyone got a presentation or document that covers the creation of
Hipersockets using YAST ?,
We have done it via command line but for completeness would like to cove
the YAST option as well.
Gerard Ceruti | Technical Specialist |Mainframe Systems | Standard Bank
South Africa |Riverclub
On 7/7/2009 at 7:50 AM, Ceruti, Gerard G
gerard.cer...@standardbank.co.za
wrote:
HI All
Anyone got a presentation or document that covers the creation of
Hipersockets using YAST ?,
We have done it via command line but for completeness would like to cove
the YAST option as well.
yast
Thanks Mark
Regards
Gerard Ceruti
may the 'z' be with you
SharePoint (internal)
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Mark Post
Sent: 07 July 2009 18:43
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLeS10 SP1 - hipersocket via YAST
On 7/7
Are Hipersocket devices supposed to show up in Yast as 3 different
devices,
where an OSA adapter shows up as 1?SLES10 SP2
IBM OSA Express Network card (0.0.1d00)│
IBM Hipersocket (0.0.0704) │Not configured
│
IBM Hipersocket (0.0.0705) │Not configured
│
IBM Hipersocket
Not having any luck with Hipersockets in SLES10, working great in SLES9
Does this look correct for a Hipersocket device in SLES10?
sles002:/etc/sysconfig/hardware # cat hwcfg-qeth-bus-ccw-0.0.0704
CCW_CHAN_IDS=''
CCW_CHAN_MODE=''
CCW_CHAN_NUM='3'
LCS_LANCMD_TIMEOUT=''
MODULE=''
MODULE_OPTIONS
@VM.MARIST.EDU
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: Hipersocket
Not having any luck with Hipersockets in SLES10, working great in SLES9
Does this look correct for a Hipersocket device in SLES10?
sles002:/etc/sysconfig/hardware # cat hwcfg-qeth-bus-ccw-0.0.0704
CCW_CHAN_IDS=''
CCW_CHAN_MODE
On 3/31/2009 at 3:42 PM, Mark Pace mpac...@gmail.com wrote:
Not having any luck with Hipersockets in SLES10, working great in SLES9
Does this look correct for a Hipersocket device in SLES10?
No. There was a regression (I can't quite call it a bug) in SP2 where going in
to YaST to configure
...@daimler.com roger.ship...@daimler.com
Date: Tue, 31 Mar 2009 14:47:49
To: LINUX-390@VM.MARIST.EDULINUX-390@VM.MARIST.EDU
Subject: Re: Hipersocket
Look at this manual..don't worry about the title..It has a great write up
and directions on HIPER.
We just went from SLES9 th 10 and I use the instructions
Mark,
I haven't specifically worked on a Hipersocket in SLES10 yet, the few
machines I have that utilize them are not yet upgraded from SLES9-10
yet. BUT I have had the exact same problem as you with regular QETH
devices. It seems that YaST doesn't always properly configure and then
hwup
) then a
smaller MTU may be best.
bruce.light...@its.ms.gov wrote:
We are just now setting up our first hipersocket connection(s) from z/VM
and linux to z/OS and will primarily use this first cut for DB2
connect to
talk to DB2 on z/OS. Does anyone have a guide for the MTU size? (
redbook,
whitepaper, etc
We are just now setting up our first hipersocket connection(s) from z/VM
and linux to z/OS and will primarily use this first cut for DB2 connect to
talk to DB2 on z/OS. Does anyone have a guide for the MTU size? ( redbook,
whitepaper, etc )
Thanks,
Bruce Lightsey
Mississippi Dept. of Information
On 2/23/2009 at 3:50 PM, bruce.light...@its.ms.gov wrote:
We are just now setting up our first hipersocket connection(s) from z/VM
and linux to z/OS and will primarily use this first cut for DB2 connect to
talk to DB2 on z/OS. Does anyone have a guide for the MTU size? ( redbook,
whitepaper
up our first hipersocket connection(s) from z/VM
and linux to z/OS and will primarily use this first cut for DB2 connect to
talk to DB2 on z/OS. Does anyone have a guide for the MTU size? ( redbook,
whitepaper, etc )
Thanks,
Bruce Lightsey
Mississippi Dept. of Information Technology Services
301 N
throughput times for these processes.
Currently the HiperSocket channel is defined in the I/O Gen as having a
Maximum Frame Size of 16 KB, the MTU size on both the zOS and z/linux
interfaces is set to 8192 (see Below). The backups are going to our
VTS which is Ficon attached to the Mainframe
On Jan 15, 2009, at 8:40 AM, Rakoczy, Dave wrote:
I've spent the past few days scouring these archives looking for what
others have done. I found a few threads that addressed HiperSocket
throughput speeds between zOS and zLinux, but were using FTP as the
benchmark utility. I have a window
For bulk data transfer, make the MTU size as large as possible, and make
your packet sizes at least 40 bytes smaller than the maximum MTU to avoid
fragmentation of data packets. That allows space for the TCP header on each
packet.
Note that this will affect interactive response, so it's probably
, 2009 10:07 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: HiperSocket Performance
For bulk data transfer, make the MTU size as large as possible, and make
your packet sizes at least 40 bytes smaller than the maximum MTU to
avoid fragmentation of data packets. That allows space for the TCP
header
On 1/15/2009 at 10:35 AM, Rakoczy, Dave dave.rako...@thermofisher.com
wrote:
-snip-
Sorry for all the questions... But I've got to learn this stuff
somewhere.
No need to apologize. The reason this mailing list exists in the first place
is to share knowledge.
Mark Post
implement this
weekend I'll need to live with for the next month, that's why I'm
looking for what others have experienced.
Yes, this HiperSocket interface will be dedicated to Bulk Transfers,
specifically our backups.
-Original Message-
From: Linux on 390 Port [mailto:linux
Rakoczy, Dave wrote:
zLinux assigns the MTU size according to the IQD CHPID definition.
For sake of discussion lets say I set the CHPID to a Max Frame Size of
64K, that would give me an MTU size of 56K according to the Doc.
Where can I control the size of the packets I'll send across the
On Jan 15, 2009, at 9:35 AM, Rakoczy, Dave wrote:
zLinux assigns the MTU size according to the IQD CHPID definition.
For sake of discussion lets say I set the CHPID to a Max Frame Size of
64K, that would give me an MTU size of 56K according to the Doc.
Where can I control the size of the
management tools.
During the last week or so we've been testing the different
FDR/Upstreams backup and restore processes (including the RMAN option).
The backup and restore processes work as advertised, but we are looking
for better throughput times for these processes.
Currently the HiperSocket channel
Hi All
When defining the QDIO CHPID in HCD is there any issue with defining a
Frame Size of 64K ?, if we leave our MTU at 8K other than the some
storage wastage are there any other issues we need to be aware of
Regards
Gerard Ceruti
may the 'z' be with you
Ceruti, Gerard G wrote:
Hi All
When defining the QDIO CHPID in HCD is there any issue with defining a
Frame Size of 64K ?, if we leave our MTU at 8K other than the some
storage wastage are there any other issues we need to be aware of
Regards
Gerard Ceruti
may the 'z' be with you
Hi
Hi Mark
This is pure HiperSocket setup, all internal on the same CEC, RHEL and SUSE
guests talking to DB2 on zOS.
Regards
Gerard Ceruti
may the 'z' be with you
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry
Sent: 16 October 2008 06:03 PM
Gerard,
In a qdio environment, you have a queue of buffers (default 16
inbound). Depending on you situation, the storage wastage can add up.
I am not sure, but I think that these buffers have to be locked in
storage. If you have a large number of hipersocket connections and a
large number
Ceruti, Gerard G wrote:
Hi Mark
This is pure HiperSocket setup, all internal on the same CEC, RHEL and SUSE
guests talking to DB2 on zOS.
Regards
Gerard Ceruti
may the 'z' be with you
Hi Gerard,
I believe you are working with Jochen Roehig?
If so he is in discussions with Volker
If you consider a best practice must be such in all cases to be best (an
absolute), then yes I would agree with you. I just would not put it on
my resume that I never use best practices, ;-), because such absolutes
do not exist. I sense that you have discomfort over the use of the word
best and
Because my organization has yet to implement Linux virtualization on the
mainframe, I tend to use this list as a way to stay abreast of
developments with little to contribute. However, as a networking
professional designing global networks I must state that your advise,
Mr. Boyes, to the list is
From the knitpicking gallery: rather than best practice I would call
it common practice
I see some similarity with a recent discussion about allocation of
cylinder 0 as page. We know that CP does not mind and there should be
no issue. Still, for several good reasons people tend to avoid doing
When setting up the IP address for a hipersocket I am curious as to if
people are giving it the same IP address as with the regular outside
of
the mainframe (OSA or whatever) IP address.
Absolutely DO NOT do this. Each interface needs a unique address (and
IMHO, a unique DNS name). The whole
Absolutely DO NOT do this. Each interface needs a unique address (and
IMHO, a unique DNS name). The whole premise of IP routing and network
function is based on this concept.
You don't have to have a per interface IP address or DNS (or indeed MAC
address), but they must be at least per host
On 2/28/2008 at 8:57 AM, in message
[EMAIL PROTECTED], David
Boyes [EMAIL PROTECTED] wrote:
When setting up the IP address for a hipersocket I am curious as to if
people are giving it the same IP address as with the regular outside
of
the mainframe (OSA or whatever) IP address
You don't have to have a per interface IP address or DNS (or indeed
MAC
address), but they must be at least per host (and virtual machines
with
their own IP stack are a host). IP is quite happy with that situation.
I'd argue that you will have more problems trying to make this work
reliably
O I'd argue that you will have more problems trying to make this work
reliably than just doing it the way I described. If you've got time to
debug this and all the paths have equivalent permissions and usability
characteristics, then yes, it's technically possible. You just have to
have a lot
O I'd argue that you will have more problems trying to make this work
reliably than just doing it the way I described. If you've got time
to
debug this and all the paths have equivalent permissions and
usability
characteristics, then yes, it's technically possible. You just have
to
have a
When setting up the IP address for a hipersocket I am curious as to if people
are giving it the same IP address as with the regular outside of the mainframe
(OSA or whatever) IP address. We have TCP/IP stacks with hipersockets running
on VSE, Linux and z/OS. On some of the VSE stacks we use
When I set up my hipersocket network between two z/VM LPARs, I went to
the networking people and got a 10.x.y.0-255 segment for my own use.
They promised not to let anyone else use it in the rest of the network.
/Tom Kern
Frank Swarbrick wrote:
When setting up the IP address for a hipersocket
The hipersocket network devices should be on a separate subnet from the
rest of your network devices. The hipersocket network is a private
network and it needs to be treated as such.
Also, different hipersocket CHPIDs require different subnets since they
represent different network segments
like I need to give it more thought to determine just how many
Linux guest will want hipersocket access to z/os data. It may not be
worth the effort to configure a hipersocket guest lan for the the Linux
guests to connect into, just save on real hipersocket addresses.
You know those recent posts
On Wednesday, 11/14/2007 at 06:00 EST, Spracklen, Ken
[EMAIL PROTECTED] wrote:
Recently we started planning for Linux guests to access data on the z/os
lpars via hipersockets. As part of that process, we defined a new
hipersocket, IUTIQDEF, to the z/VM TCPIP guest profile and added
Alan and Mark,
Thanks for the help. I haven't tried it yet, but I suspect that if I
change the ip addresses on the new hipersocket interfaces, it will help.
I think part of my confusion came from reading section 4.3 of the Linux
for IBM System z9 and IBM zSeries redbook and mis-interpreting
Hi,
Considering the following scenario possible.
One our CEC we have 3 z/os lpars and an IFL running z/VM 5.3. On the
z/VM we have a few SUSE Linux quests as well as TCPIP and MPROUTE
guests. On all three z/OS lpars and the TCPIP guest I have a hipersocket
device, IUTIQDFF, defined
On Wed, Nov 14, 2007 at 4:21 PM, in message
[EMAIL PROTECTED],
Spracklen, Ken [EMAIL PROTECTED] wrote:
-snip-
Recently we started planning for Linux guests to access data on the z/os
lpars via hipersockets. As part of that process, we defined a new
hipersocket, IUTIQDEF, to the z/VM TCPIP
to find the real bottleneck. Are
you equiped?
Mark Wheeler wrote:
More info:
FTP GET's of this cached 256MB file to /dev/null have run as fast as 205
MB/sec w/ MTU=32760 over hipersocket interfaces, and 168 MB over virtual
CTCs. FTP PUT's are a different matter: hipersocket or CTC doesn't
make
Subject
Re: Hipersocket Performance Problem
on SLES 9
01/19/2007 04:55
AM
Please respond to
Linux on 390 Port
[EMAIL PROTECTED]
IST.EDU
More info:
FTP GET's of this cached 256MB file to /dev/null have run as fast as 205
MB/sec w/ MTU=32760 over hipersocket interfaces, and 168 MB over virtual
CTCs. FTP PUT's are a different matter: hipersocket or CTC doesn't make a
difference. The higher MTU size, the slower the transfer rate
I've seen this a lot. You need to find the real bottleneck. Are
you equiped?
Mark Wheeler wrote:
More info:
FTP GET's of this cached 256MB file to /dev/null have run as fast as 205
MB/sec w/ MTU=32760 over hipersocket interfaces, and 168 MB over virtual
CTCs. FTP PUT's are a different
do others use for hipersocket MTU size?
Mark
Greetings all,
I've been using real hipersockets for a couple years now. Recently a
significant performance problem with SLES 9 and large MTU sizes was
brought
to my attention. I've been using MTU=32760. I set up a test to illustrate
the problem
-390@VM.MARIST.EDU
cc
Subject
Re: Hipersocket Performance Problem on SLES 9
Mark, I saw something similar when we first went to SLES-9 (64 bit). We
had MTU sizes being negotiated down to an idiotic packet size of 1492.
Whether or not this has to do with how our OSA is configured I never did
1 - 100 of 236 matches
Mail list logo
