The original source was ITU-T X.731 but more recently (AP-4575) ITU-T M.3701 is referenced.
It may make sense to open a Jira issue to add an alarmStatus
attribute from M.3701:
"Represents the severity status of fault for a resource. It can have zero or more values, each representing an existing severity.
SEQUENCE OF ENUMERATED {
under repair,
critical,
major,
minor,
alarmOutstanding
}
"
------------------------------
Vance Shipley
SigScale
------------------------------
Original Message:
Sent: May 17, 2024 00:18
From: Srinivasa Vellanki
Subject: Resource status and state fields in TMF639 & TMF702
Hi,
Need a state to indicate the reclaimed device is faulty. Assuming we should use resourceStatus. Is this correct or is resourceStatus more confined to indicate a status of Device deployed? Appreciate any inputs on this. What state or status to use? Any recommended value for the same.
Also it would be good if we can indicate which eTOM process(s) own each of these state and status. This will improve the clarity.
------------------------------
Srinivasa Vellanki
Jio Platforms Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of my employer or TM Forum.
Original Message:
Sent: Nov 12, 2021 01:39
From: Vance Shipley
Subject: Resource status and state fields in TMF639 & TMF702
Roland,
The usageState
attribute indicates (read only) the current usage of the Resource: idle
| active
| busy
The resourceStatus
attribute indicates (read only) the status of the Resource: standby
| alarm
| available
| reserved
| unknown
| suspended
The operationalState
attributes controls (write) whether the Resource may be used in operations: enabled
| disabled
The administrativeState
attributes controls (write), for administrative reasons, whether an otherwise operational Resource is available: locked
| unlocked
| shutdown
------------------------------
Vance Shipley
SigScale
Original Message:
Sent: Nov 11, 2021 05:11
From: Roland Leners
Subject: Resource status and state fields in TMF639 & TMF702
TMF639 (& TMF702) defines 4 status/state fields for a resource, including possible values:
- usageState
- administrativeState
- operationalState
- resourceStatus
Can someone shed some light on the precise meanings of those fields, as well as the enumerations proposed by the standard?
Apologies if this has been addressed elsewhere, but all the threads that I found relate to the resource lifecycle model used by previous releases.
------------------------------
Roland Leners
SATEC GROUP
------------------------------