Hi Erwann,
Yes, that's indeed what I discovered too. When I issue the command q
monitorstatus status=error, the error status trigger which SPOC uses is
displayed. In my case:
Server Name Activity Date Activity Name Element Name Element
Element String Element State
Numeric
Value Value
--------------- --------------- --------------- ---------------
--------------- --------------- ---------------
AMSE3 26-03-2020 NON-SHARED DBBACKUP 50
ERROR
12:40:41 FILE DEV
PERCENTAGE
SCRATCH
VOLUMES
UNALLOCATABLE
The Element Numeric Value indeed changes when I raise or lower the deviceclass
mount limit or maxcap. However, I cannot find how it is being calculated.
My deviceclass currently uses:
Device Class Name: DBBACKUP
Device Access Strategy: Sequential
Storage Pool Count: 0
Device Type: FILE
Format: DRIVE
Est/Max Capacity (MB): 204,800.0
Mount Limit: 8
The directory it uses has 997G of free space available:
df -Ph|grep dbbackup
/dev/mapper/vgl_etsm01-lvl_dbbackup 1.2T 140G 997G 13%
/tech/tsm/AMSE3/dbbackup
But 8 * 200GB is 1.6 TB. So why is the Element Numeric Value 50 at this moment?
I have a case open at this moment and I requested support to ask the developers
how this value is being calculated. If I receive an answer, I will let you all
know.
Thanks for your help!
Kind regards,
Eric van Loon
Air France/KLM Storage & Backup
-----Original Message-----
From: ADSM: Dist Stor Manager <[email protected]> On Behalf Of Erwann SIMON
Sent: woensdag 25 maart 2020 05:02
To: [email protected]
Subject: Re: Error in OC for device class
Hi Eric,
When there is no Storage Pool associated with a FILE Device Class, the
following parameters are considered to trigger a warning or error status :
- maxcapacity (device class parameter)
- mountlimit (device class parameter)
- available space (in the filesystem pointed by the directory device class
parameter)
- DEF_FILEDEVCLASSPCTSCRUNALLOCATABLE_[W|E] (statusthresholds)
maxcapacity * mountlimit should not exceed the status thresholds.
I generally adjust the mountlimit parameter value to avoir crossing the
threshold.
PS : I'm pretty there was a technote describing this in the past, but I've been
unable to find it. Here's another one, describing a similar issue :
https://www.ibm.com/support/pages/file-devclass-reported-warning-operations-center
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
----- Mail original -----
De: "Eric van Loon (ITOP NS) - KLM" <[email protected]>
À: [email protected]
Envoyé: Mercredi 18 Mars 2020 12:57:44
Objet: [ADSM-L] Error in OC for device class
Hi guys,
In Operation Center an critical error is shown for some of my servers with a
device class without a storagepool. When I issue the command q monitorstatus
status=error, the following error is listed:
Server Name Activity Date Activity Name Element Name Element
Element String Element State
Numeric
Value Value
--------------- --------------- --------------- ---------------
--------------- --------------- ---------------
AMSE4 18-03-2020 NON-SHARED DBBACKUP 50
ERROR
12:44:09 FILE DEV
PERCENTAGE
SCRATCH
VOLUMES
UNALLOCATABLE
This device class is used for database backup only and has no storagepool
connected, so that's why there is no percentage of scratch volumes available.
Anybody know how to solve this error?
Thanks for your help in advance!
Kind regards,
Eric van Loon
Air France/KLM Storage & Backup
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************