I don't think a TS31xx can auto boot upon power resumption..... The larger
libraries might be able to.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Monday, June 8, 2020 10:29 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: CPP6310 - Interface error: Device TAPMLB01 (resource TAPMLB01)
Not sure how much of a PITA a visit to the DC is to you but an intelligent
PDU might assist. With that you can cut the power to an outlet thereby
doing a restart remotely. Providing the media library is set to
automatically start upon power restore.
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
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steinmetz, Paul via MIDRANGE-L
Sent: Monday, June 8, 2020 11:22 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: CPP6310 - Interface error: Device TAPMLB01 (resource TAPMLB01)
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
I had an Interface failure, CPP3610, on my 3573 Fiber Channel 4 Half Height
Tape library.
Caused multiple BRMS failures.
Two of the four drives were in a failed status, another was deallocated.
Varying off/on the TAPMLB01 did not resolve the issue.
Library would not reboot via the GUI interface.
Took a midnight trip to the data center to power down/recycle the library.
All errors cleared.
I had a similar issue back in March, Library would reboot, took a midnight
trip.
This failure the power button was non-responsive, had to pull the power
cords to reboot the tape library.
Reviewing the issue/errors, and the fact that two drives went into a failed
state, (each port on the ENOA controls two drives)
the root cause was either
1) the EN0A- PCIe3 16Gb 2-port Fibre Channel Adapter
2) or the Cisco 9148 Fiber channel switch.
Is there any way to determine the root cause?
A new VTL is in progress, but if the TAPMLB01 library is not the root cause,
can this same type of error occur on a VTL?
Any thoughts from the group?
Message ID . . . . . . : CPP6310
Date sent . . . . . . : 06/06/20 Time sent . . . . . . : 22:00:28
Message . . . . : Interface error: Device TAPMLB01 (resource TAPMLB01)
Cause . . . . . : The IOA or the device detected an error when a command
or
data was being transferred through the Fibre Channel or SAS interface.
Recovery . . . :
Press F14 to work with the problem.
Technical description . . . . . . . . : Device TAPMLB01 (resource
TAPMLB01)
is attached to IOA resource DC04.
Device type . . . . . . . . . . . . . : 3580
Reference code . . . . . . . . . . . : X'9101'
Product Activity log ID . . . . . . : X'8056AB03'
IOP resource . . . . . . . . . . . . : CMB06
More...
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@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
