|
I just replaced one of the LTO4HH drives in one of our libraries. Would
often drop connection well into a save.
When they replaced the drive I had some 'fun'. The serial number of the
drive (not the library) changed.
Drive is controlled by VIOS. That VIOS lpar does the fiber tape drive.
WRKMLBSTS and vary off for all lpars of IBM i.
WRKCFGSTS *DEV TAP* and vary off for all lpars of IBM i.
replace drive
Bounce VIOS lpar. (probably could have done 'iop reset' if I new vios
better.)
WRKHDWRSC *STG
http://mytaplib, record serial number of drives.
STRSST delete old resource for replaced drive. Rename resource of new
drive to that of replaced drive. I'm OCD on this as I like the resource
names to match the drive names. And I like them to be consistent across
all lpars.
WRKMLBSTS ensure that it is still varied off
WRKCFGSTS *DEV TAP* on just one lpar. Vary on replaced tape drive (not
library). Use 'itdt' to stress test drive. Passed. Vary off TAP*
devices.
WRKMLBSTS and vary it on.
make sure that only the replaced drive is 'allocated unprotected'. Do
long extensive BRMS save. When complete, expire the tape.
WRKMLBSTS for all lpars and make sure library is ready and drives are all
allocated unprotected.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 04/01/2015 01:54 PM
Subject: RE: CPP6316 - Hardware configuration change detected,
followed by CPF414C - Command not allowed
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I had a repeat of this issue/failure
We had the exact same series of messages, (from our 2/1 failure) along
with a DUPMEDBRM failure, different LPAR.
There was also a drive auto clean request issued 2:31 am, may or may not
be related.
So the library was busy moving volumes for 4 drives, 2 lpars, between 2:30
and 2:32 am.
CPP6316 - Hardware configuration change detected.
BRM4138 - Media duplication completed with errors.
CPF414C - Command not allowed
I think the issue is related to month end tape processing.
Both LPARS were in the process of starting a DUPMEDBRM with in the same
minute, 2:30 am.
Unfortunately no drive dumps obtained.
Serial Resource
Name Type Model Number Name
TAPMLB01 3573 040 04-7808387 TAPMLB01
Log ID . . . . . . . . . : 800C83F7 Sequence . . . . . . . : 1641240
Date . . . . . . . . . . : 04/01/15 Time . . . . . . . . . : 02:32:03
Reference code . . . . . : 9220 Secondary code . . . . : 00000000
Table ID . . . . . . . . : 94290310 IPL source/state . . . : B/3
System Ref Code . . . . . : 94299220
Server of origin . . . . : 8205-E6C 10-5815R
Class . . . . . . . . . . : Permanent
Hardware configuration change detected.
Below is IBM's PMR explanation from the 2/1 failure.
"The issue is that the library reported it was offline in the middle of a
function. The question is why. There is nothing from the IBM i that would
account for this.
The User command was running, we were processing a mount function, the
library was taking commands and sending data, we were able to identified
the location of the desired tape, we had the tape device, but when we
issued the move command the library returned offline. The library for some
reason decided to respond offline. Which then leads to the PAL and the
CPF414C.
We know the PAL is not the correct one. The SK 2/0412 error was mapped to
a hardware configure error and it should be mapped to a library state
change. But in either case the end result would be the same... CPF414C
library not in library mode. We have this PAL change documented.
So if you or your staff can not account for a reason why the library would
have been offline, then we would need the library and drive logs
collected at the time of the failure to provide why the library responded
the way it did.
If this issue can be reproduced we will need the following collected at
the time of failure....
Call QTADMPDV TAPMLBxx
Library and drive logs captured from the Library GUI Service functions
(Tape Support would assist with the operation if needed)"
Anyone experience something similar?
Any thoughts on which support to contact?
Paul
-----Original Message-----
From: Steinmetz, Paul
Sent: Monday, February 02, 2015 1:26 PM
To: 'Midrange Systems Technical Discussion'
Subject: CPP6316 - Hardware configuration change detected, followed by
CPF414C - Command not allowed
I had this error occur over the weekend, during a DUPMEDBRM.
The Dup failed, and the recovery.
TAPMLB01 then recovered with no operator intervention.
Following DUPMEDBRM, and saves were successful.
Has anyone ever experienced this issue?
Message ID . . . . . . : CPP6316
Date sent . . . . . . : 02/01/15 Time sent . . . . . . : 06:10:20
Message . . . . : Hardware configuration change detected.
Cause . . . . . : Device *N has reported an error that indicates that
the
configuration may have been changed without the IOP being reset. There
may
also be a hardware problem with the device.
Recovery . . . :
Reset the IOP. If the problem continues press F14 to work with the
problem.
Technical description . . . . . . . . :
IOP resource . . . . . . . . . . . . : CMB03
IOA resource . . . . . . . . . . . . : DC02
Device type . . . . . . . . . . . . . : 3573
Reference code . . . . . . . . . . . : X'9220'
Error log ID . . . . . . . . . . . . : X'8021F782'
Problem log ID . . . . . . . . . . . : 1503221191
Message ID . . . . . . : CPF414C
Date sent . . . . . . : 02/01/15 Time sent . . . . . . : 06:10:21
Message . . . . : Command not allowed
Cause . . . . . : Library device TAPMLB01 is not in library mode.
Recovery . . . : Switch library device TAPMLB01 to library mode and
retry
the operation.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
