I do have SourceVipa specified:
ASSORTEDPARMS
PROXYARP
IGNOREREDIRECT
SOURCEVIPA
Are you saying that specifying this could cause the problem? Why would it work
OK on the old machine but not on the new? Same config files, only difference
new hardware.
Mike
________________________________
From: The IBM z/VM Operating System on behalf of Ward, Mike S
Sent: Wed 15/12/2010 9:46 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Problems with MPROUTE going from z800 to z9BC computer
Sourcevipa is a TCP configuration parm. The book states:
Note: For requests or connections originating at a z/VM TCP/IP stack,
tolerance of device and adapter failures may be achieved by using the
SOURCEVIPA feature. This capability causes virtual IP addresses to be
used as the source IP addresses in all outbound datagrams except those
associated with routing.
This has burned me a couple of times because it chooses source ip
address from the home list starting from the bottom up. It selects the
first vipa address that it finds as the source ip for all
communications. I.E. you may want to use address 172.26.1.1 as your
source, but you end up using 172.25.1.1 and it may not be in the routing
tables.
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Horlick, Michael
Sent: Wednesday, December 15, 2010 8:12 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Problems with MPROUTE going from z800 to z9BC computer
Have no idea what sourceVIPA is. Maybe you can explain. My configuration
files were the same for TCPIP and MPROUTE.
Would the type of OSA card matter? I believe I have an OSA-2 on the
existing machine but an OSA-Express on the new.
Thanks,
Mike
________________________________
From: The IBM z/VM Operating System on behalf of Ward, Mike S
Sent: Wed 15/12/2010 8:59 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Problems with MPROUTE going from z800 to z9BC computer
Could you possibly be using sourceVipa where before you weren't?
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Horlick, Michael
Sent: Wednesday, December 15, 2010 7:21 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Problems with MPROUTE going from z800 to z9BC computer
Greetings,
A couple of days ago we tried to migrate from our current CPU (Z800 -
Model 2066) to a z9BC Mode R07 (2096).
We had this new machine for a couple of weeks and we created a copy of
our z/VM 5.4 system on it (XXXRES = 540RES, XXXPAG = 540PAGetc...). I
was able to test z/VM 5.4 and TCP/IP on it and it worked fine given that
we were assigned new IP addresses for it. We have 2 TCP/IP stacks, one
for our use, the other for the clients. For the client, on our
production machine we use VIPA/MPROUTE.
We could not test VIPA/MPROUTE on the new machine but static routing
worked fine. We tried the OSA card in QDIO and non-QDIO mode and no
problems. Connectivity for both us and the client.
Come migration time however, we could not get the VIPA/MPROUTE
functionality working. I could not ping from within the mainframe to
anything beyond the OSA card. Tried both QDIO and non-QDIO mode.
Our TCP/IP stack, no problems.
We had to back out and now we have to try to set up a test VIPA/MROUTE
setup and try it on the new machine. Waiting on the telecom architect
for this.
No changes to the configuration files were done (except for QDIO in the
PROFILE TCPIP, but the same configuration files for non-QDIO).
Any clues what could have gone wrong?
Thanks,
Mike Horlick
CGI Montreal
==========================
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity
to which they are addressed. If you have received this email in error
please notify the system manager. This message
contains confidential information and is intended only for the
individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify
the sender immediately by e-mail if you
have received this e-mail by mistake and delete this e-mail from your
system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this
information is strictly prohibited.
==========================
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity
to which they are addressed. If you have received this email in error please
notify the system manager. This message
contains confidential information and is intended only for the individual
named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you
have received this e-mail by mistake and delete this e-mail from your system.
If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this
information is strictly prohibited.
