Hello Eric,
 
Yes, I believe the two mainframes were connected to the same VLAN subnets. The 
client had no problem accessing the new CPU without VIPA/MPROUTE.
 
Beyond that I don't know the answers to your questions. Something to ask the 
network people. 
 
Thanks,
 
Mike

________________________________

From: The IBM z/VM Operating System on behalf of Eric Schadow
Sent: Wed 15/12/2010 8:54 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Problems with MPROUTE going from z800 to z9BC computer



Mike

Were the two mainframes on the same or different VLAN/subnets?

It could have been a ARP/MAC timeout issue?

Are the MAC's locally administered on the mainframe?

You may have private VLAN or some other mechanism setup to limit the
host interactions on the switch.

Eric

-----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:46 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Problems with MPROUTE going from z800 to z9BC computer

Oops , I may accidently sent an earlier incomplete reply. Sorry.
=20
Anyways, we had new cables attached from the OSA card on the new CPU =
attached one to our switch, the other to the switch for the client. No =
new cabling was done at migration time. We tested before the migration =
and all well, non-VIPA.=20
=20
Thanks,
=20
Mike=20

________________________________

From: The IBM z/VM Operating System on behalf of Davis, Larry (National
=
VM/VSE Capability)
Sent: Wed 15/12/2010 8:34 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Problems with MPROUTE going from z800 to z9BC computer



Are you using the same or New Network connections to the network. Make =
sure the two OSA ports are not cross connected at the switch. If they =
are TRUNC'd together then you will have routing issues.

Just get a new set of IP's to test with on the new box, and get your =
network and firewall people involved.

Larry Davis

-----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: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 =3D 540RES, XXXPAG =3D 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
=20



------------------------------------------------------------------------
The information contained in this communication is intended
only for the use of the recipient(s) named above. It may
contain information that is privileged or confidential, and
may be protected by State and/or Federal Regulations. If
the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,
distribution, or copying of this communication, or any of
its contents, is strictly prohibited. If you have received
this communication in error, please return it to the sender
immediately and delete the original message and any copy
of it from your computer system. If you have any questions
concerning this message, please contact the sender.
------------------------------------------------------------------------

Reply via email to