ok, thanks for your help. Mike ________________________________
From: The IBM z/VM Operating System on behalf of Ward, Mike S Sent: Wed 15/12/2010 10:46 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems with MPROUTE going from z800 to z9BC computer I agree with Alan, use ping to see if it's getting out. You may find that the sourceip used does not have a route back to you. -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Wednesday, December 15, 2010 9:30 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems with MPROUTE going from z800 to z9BC computer On Wednesday, 12/15/2010 at 08:21 EST, "Horlick, Michael" <michael.horl...@cgi.com> wrote: > 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? Mike, network problems are all solved the same way: Divide and Conquer. If I understand you correctly: 1. The new system and the old one have the same IP configuration. That is, the same files on TCPIP and MPROUTE's A-disks. The same configuration files on TCPMAINT 198. The systems even have the same SYSTEM_IDENTIFIER. 2. The new system works fine *until* you bring up MPROUTE (it throws away any static routes not specifically marked as permanent). 3. The old and new systems are NOT up at the same time. When you PING something, a packet goes out and a packet comes back. To resolve why PING doesn't work, you need to figure out which of those two things didn't happen. Your network techs can help you, as they do this kind of stuff all the time with sniffers and queries on the switches/routers. Only then will you be able to take corrective action. Prior to that, you're just guessing, flailing at the problem in the hope you will accidentally fix it. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott ========================== 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.
