This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We run into a LANfree backup issue. Diagnosing the issue took a long time because the STA was not reporting the drive failures into the SP server activity log.
Environment:
SP AIX library manager (LM) server 8.1.21.0, SP server name LIBMGR.
SP AIX library client (LC) server 8.1.21.0, SP server name LIBCLNT.
SP AIX STA 8.1.21.0, STA name STA-LIBCLNT.
All SP server and STA components running on different AIX 7.2.0.0 LPARs.
STA STA-LIBCLNT is connecting to LC server LIBCLNT.
Description:
The DB2 SP client node LANfree backup through STA STA-LIBCLNT failed.
The SP server LIBCLNT activity log shows for DB2 SP client node/ STA-LIBCLNT:
10/01/24 08:13:16 ANR0525W Transaction failed for session 435381 for node ...
10/01/24 08:13:17 ANR0525W Transaction failed for session 435390 for node ...
10/01/24 08:16:33 ANR0525W Transaction failed for session 435400 for node ...
10/02/24 08:10:23 ANR0525W Transaction failed for session 477889 for node ...
10/02/24 08:14:44 ANR0525W Transaction failed for session 477899 for node ...
No more errors or more details to narrow down the root cause of the failure are available in the SP LC and LM server activity logs.
My colleague finally found the reason for the failure to be 2 tape drive device special files set to defined on the STA AIX LPAR.
The STA logged the errors to its dsmffdc.log file:
[10-02-2024 08:06:53.055][ FFDC_GENERAL_SERVER_ERROR ]: [260](pvrutil.c:820)(SESSION: 13118) Unable to open drive /dev/rmt365 rc 2843 errno 2.
[10-02-2024 08:07:55.302][ FFDC_GENERAL_SERVER_ERROR ]: [260](pvrutil.c:820)(SESSION: 13118) Unable to open drive /dev/rmt365 rc 2843 errno 2.
[10-02-2024 08:08:57.030][ FFDC_GENERAL_SERVER_ERROR ]: [260](pvrutil.c:820)(SESSION: 13118) Unable to open drive /dev/rmt365 rc 2843 errno 2.
[10-02-2024 08:09:38.030][ FFDC_GENERAL_SERVER_ERROR ]: [256](afcreate.c:1177)(SESSION: 13118) ssStore result rc 3011, ck1 487
[10-02-2024 08:10:44.078][ FFDC_GENERAL_SERVER_ERROR ]: [261](pvrutil.c:820)(SESSION: 13125) Unable to open drive /dev/rmt365 rc 2843 errno 2.
[10-02-2024 08:11:53.459][ FFDC_GENERAL_SERVER_ERROR ]: [261](pvrutil.c:820)(SESSION: 13125) Unable to open drive /dev/rmt365 rc 2843 errno 2.
[10-02-2024 08:13:03.086][ FFDC_GENERAL_SERVER_ERROR ]: [261](pvrutil.c:820)(SESSION: 13125) Unable to open drive /dev/rmt365 rc 2843 errno 2.
If the STA is logging the drive open error to the dsmffdc.log file only, it is impossible to monitor for such errors and it takes a long time to identify these errors.
We request to change the STA error logging so that the STA is logging this kind of errors to the SP LC server activity log.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.