Re: HELP!! IPL failure
I tried the force, since it was showing as an active connection not in a failed-persistent state, the force command wasn't accepted. I did need to perform a sysplex IPL and shutdown/activate the 2 CF lpars too before bringing things up. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Thursday, October 28th, 2021 at 12:26 AM, Barbara Nitz wrote: > > A D XCF command isn't showing the system active.The ISGLOCK#SYSA connector > > is showing active to structure ISGLOCK > > From the other system, try forcing the connection of ISGLOCK#SYSA to the CF. > Take a dump from the other system of the XCF address space that also includes > the ISGLOCK structure when SYSA is fenced. Doesn't matter which system you > use. This sounds like a serious bug and you should have documentation. > > Try to rebuild everything out of the CF that houses ISGLOCK to the other CF > that you hopefully have. Then check the connection again, it should be gone. > > All else failing, reset the CF lpar (power off/power on that LPAR). That will > cost you all systems in the plex (assuming there're more than 2) and you will > need to IPL the complete sysplex. And use a freshly formatted primary CFRM > dataset to be on the safe side. Start that using the CFRM parm in couplexx. > > HTH, Barbara > > --- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HELP!! IPL failure
>A D XCF command isn't showing the system active.The ISGLOCK#SYSA connector is >showing active to structure ISGLOCK From the other system, try forcing the connection of ISGLOCK#SYSA to the CF. Take a dump from the other system of the XCF address space that also includes the ISGLOCK structure when SYSA is fenced. Doesn't matter which system you use. This sounds like a serious bug and you should have documentation. Try to rebuild everything out of the CF that houses ISGLOCK to the other CF that you hopefully have. Then check the connection again, it should be gone. All else failing, reset the CF lpar (power off/power on that LPAR). That will cost you all systems in the plex (assuming there're more than 2) and you will need to IPL the complete sysplex. And use a freshly formatted primary CFRM dataset to be on the safe side. Start that using the CFRM parm in couplexx. HTH, Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HELP!! IPL failure
Is there a WTOR seen in other LPARs of the sysplex, asking to reply DOWN or whatever? That has bit me before (not with the below message). - KB ‐‐‐ Original Message ‐‐‐ On Thursday, October 28th, 2021 at 8:10 AM, Mark Jacobs <0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > I did. XCF said SYSA is not active in the SYSPLEX. > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, October 27th, 2021 at 9:14 PM, Skip Robinson > jo.skip.robin...@gmail.com wrote: > > > The system is thought to still be active in the plex. Issue V XCF,xx,OFF > > > > from another system. > > > > J. O. Skip Robinson > > > > jo.skip.robin...@gmail.com > > > > 323.715.0595 > > > > On Wed, Oct 27, 2021, 18:07 Mark Jacobs < > > > > 0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > > > > > I'm trying to bring a system back up and it's failing. > > > > > > IXC418I SYSTEM SYSA IS NOW ACTIVE IN SYSPLEX DEVL52 > > > > > > IXL013I IXLCONN REQUEST FOR STRUCTURE ISGLOCK FAILED. > > > > > > JOBNAME: GRS ASID: 0007 CONNECTOR NAME: ISGLOCK#SYSA > > > > > > IXLCONN RETURN CODE: 0008, REASON CODE: 0201081F > > > > > > CONNECTOR WITH SAME NAME ALREADY CONNECTED TO STRUCTURE > > > > > > CONADIAG0: 0002 > > > > > > CONADIAG1: 0008 > > > > > > CONADIAG2: 081F > > > > > > ISG308W GRS PROCESSING TERMINATED. > > > > > > IXLCONN SERVICE FAILED WITH RC=8, RSN=81F. > > > > > > IXL004W CHANNEL SUBSYSTEM HAS BEEN ISOLATED > > > > > > A D XCF command isn't showing the system active.The ISGLOCK#SYSA connector > > > > > > is showing active to structure ISGLOCK > > > > > > Mark Jacobs > > > > > > Sent from ProtonMail, Swiss-based encrypted > > > > > > email. > > > > > > GPG Public Key - > > > > > > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HELP!! IPL failure
I did. XCF said SYSA is not active in the SYSPLEX. Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, October 27th, 2021 at 9:14 PM, Skip Robinson wrote: > The system is thought to still be active in the plex. Issue V XCF,xx,OFF > > from another system. > > J. O. Skip Robinson > > jo.skip.robin...@gmail.com > > 323.715.0595 > > On Wed, Oct 27, 2021, 18:07 Mark Jacobs < > > 0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > > > I'm trying to bring a system back up and it's failing. > > > > IXC418I SYSTEM SYSA IS NOW ACTIVE IN SYSPLEX DEVL52 > > > > IXL013I IXLCONN REQUEST FOR STRUCTURE ISGLOCK FAILED. > > > > JOBNAME: GRS ASID: 0007 CONNECTOR NAME: ISGLOCK#SYSA > > > > IXLCONN RETURN CODE: 0008, REASON CODE: 0201081F > > > > CONNECTOR WITH SAME NAME ALREADY CONNECTED TO STRUCTURE > > > > CONADIAG0: 0002 > > > > CONADIAG1: 0008 > > > > CONADIAG2: 081F > > > > ISG308W GRS PROCESSING TERMINATED. > > > > IXLCONN SERVICE FAILED WITH RC=8, RSN=81F. > > > > IXL004W CHANNEL SUBSYSTEM HAS BEEN ISOLATED > > > > A D XCF command isn't showing the system active.The ISGLOCK#SYSA connector > > > > is showing active to structure ISGLOCK > > > > Mark Jacobs > > > > Sent from ProtonMail, Swiss-based encrypted > > > > email. > > > > GPG Public Key - > > > > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HELP!! IPL failure
The system is thought to still be active in the plex. Issue V XCF,xx,OFF from another system. J. O. Skip Robinson jo.skip.robin...@gmail.com 323.715.0595 On Wed, Oct 27, 2021, 18:07 Mark Jacobs < 0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > I'm trying to bring a system back up and it's failing. > > IXC418I SYSTEM SYSA IS NOW ACTIVE IN SYSPLEX DEVL52 > IXL013I IXLCONN REQUEST FOR STRUCTURE ISGLOCK FAILED. > JOBNAME: GRS ASID: 0007 CONNECTOR NAME: ISGLOCK#SYSA > IXLCONN RETURN CODE: 0008, REASON CODE: 0201081F > CONNECTOR WITH SAME NAME ALREADY CONNECTED TO STRUCTURE > CONADIAG0: 0002 > CONADIAG1: 0008 > CONADIAG2: 081F > ISG308W GRS PROCESSING TERMINATED. > IXLCONN SERVICE FAILED WITH RC=8, RSN=81F. > IXL004W CHANNEL SUBSYSTEM HAS BEEN ISOLATED > > A D XCF command isn't showing the system active.The ISGLOCK#SYSA connector > is showing active to structure ISGLOCK > > Mark Jacobs > > Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted > email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HELP!! IPL failure
I'm trying to bring a system back up and it's failing. IXC418I SYSTEM SYSA IS NOW ACTIVE IN SYSPLEX DEVL52 IXL013I IXLCONN REQUEST FOR STRUCTURE ISGLOCK FAILED. JOBNAME: GRS ASID: 0007 CONNECTOR NAME: ISGLOCK#SYSA IXLCONN RETURN CODE: 0008, REASON CODE: 0201081F CONNECTOR WITH SAME NAME ALREADY CONNECTED TO STRUCTURE CONADIAG0: 0002 CONADIAG1: 0008 CONADIAG2: 081F ISG308W GRS PROCESSING TERMINATED. IXLCONN SERVICE FAILED WITH RC=8, RSN=81F. IXL004W CHANNEL SUBSYSTEM HAS BEEN ISOLATED A D XCF command isn't showing the system active.The ISGLOCK#SYSA connector is showing active to structure ISGLOCK Mark Jacobs Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
