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
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 = 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
Re: Problems with MPROUTE going from z800 to z9BC computer
Hello Larry, We had new cables from the OSA card on the new CPU c 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 = 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
Re: Problems with MPROUTE going from z800 to z9BC computer
Oops , I may accidently sent an earlier incomplete reply. Sorry. 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. Thanks, Mike 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 = 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
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.
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.
Re: Problems with MPROUTE going from z800 to z9BC computer
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.
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.
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.
Re: Problems with MPROUTE going from z800 to z9BC computer
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
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
Re: Problems with MPROUTE going from z800 to z9BC computer
Yes, you're right. Will wait till network people are involved. Thanks, Mike From: The IBM z/VM Operating System on behalf of Alan Altmark Sent: Wed 15/12/2010 10:29 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
Re: Problems with MPROUTE going from z800 to z9BC computer
Setup correctly it should work ok. -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:59 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems with MPROUTE going from z800 to z9BC computer 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
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.
Re: Problems with MPROUTE going from z800 to z9BC computer
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.
