Make sure you get a snapdump next time. There's quite a few HIPERs out there beyond 0701, you may want to go pull them all. Sounds kinda similar to something we've experienced - resolved by VM64269 and VM64297.
Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Leland Sent: Monday, October 15, 2007 11:45 AM To: [email protected] Subject: [IBMVM] Upgrade to z/VM 5.3 hangs I am wondering if anyone has seen this when upgrading from VM 5.2 to VM 5.3. We opened an ETR for our issue with IBM this morning. Yesterday we attempted to upgrade to z/VM 5.3 0701 and ran into a problem that caused us to back out to z/VM 5.2. After bringing up 10 service machines and roughly 50 Linux guests, we started 2 more Linux guests. This caused MAINT's and another tn3270 session to hang. We thought perhaps TCPIP had died, so we went to our Visara console and that was hung to. We were able to ssh into some of the Linux guests and bring down stuff like Websphere and Oracle, but we could not get into all of the guests. When we tried a vmcp command in one guest, it immediatey locked that guest. We have all of our guests connected to VSWITCHes directly, so no ROUTED stuff was involved. The two guests are similar to others that started fine. One was a Websphere and the other is an Oracle guest. The Oracle is different in that its database is on SCSI disk with direct attached FCP channels, it is the only guest we have using FCP and SCSI. We weren't doing any paging and our IFL's were running at around 20%. We didn't get a dump, but are scheduling a time soon to do so. Any ideas would be appreciated. Thank you. Mark Ristvedt BCBSMN (via me ;-))
