text
stringlengths 16
6.86k
|
|---|
[i. 7] ETSI GS NFV-IFA 008: "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Ve-Vnfm reference point - Interface and Information Model Specification". [i. 8] ETSI GS NFV-IFA 013: "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Os-Ma-nfvo reference point - Interface and Information Model Specification". [i. 9] ETSI GS NFV-IFA 030: "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Multiple Administrative Domain Aspect Interfaces Specification". [i. 10] ETSI GS NFV-IFA 032: "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Interface and Information Model Specification for Multi-Site Connectivity Services". [i. 11] ETSI GS NFV-EVE 007: "Network Functions Virtualisation (NFV) Release 3; NFV Evolution and Ecosystem; Hardware Interoperability Requirements Specification". [i. 12] ETSI GS NFV-IFA 040: "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Requirements for service interfaces and object model for OS container management and orchestration specification". [i. 13] ETSI GS NFV-IFA 036: "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Requirements for service interfaces and object model for container cluster management and orchestration specification". [i. 14] ETSI GS NFV-IFA 031: "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Requirements and interfaces specification for management of NFV-MANO". 3 Definition of terms, symbols and abbreviations 3. 1 Terms For the purposes of the present document, the terms given in ETSI GR NFV 003 [i. 1] apply. 3. 2 Symbols Void. 3. 3 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GR NFV 003 [i. <|end_of_text|>
|
1] and the following apply: ECC Error Correction Code MSCS Multi-Site Connectivity Service PCI Peripheral Component Interconnect PCIE PCI Express RAID Redundant Array of Independent Disks SCSI Small Computer System Interface SMART Self-Monitoring Analysis and Reporting Technology TMN Telecommunications Management Network. <|end_of_text|>
|
4 Overview 4. 1 Introduction Fault management is one of the five functional areas of the Telecommunications Management Network (TMN) model. Recommendation ITU-T M. 3400 [i. 2] defines fault management as the set of functions which enables the detection, isolation and correction of abnormal operation of the telecommunication network and its environments. As summarized by ETSI GS NFV-REL 001 [i. 3], fault management systems comprise two main aspects: a) managing alarms and their propagation through the system, and b) mitigating the impact of an occurring failure. Thus, one key functionality related to fault management is alarm management. Alarm surveillance refers to the capabilities to monitor faults on systems. In NFV, different types of resources or elements (logical, virtual, physical) are considered, so monitoring objectives go beyond physical network elements, as typically performed in legacy telecommunications networks. When a fault occurs, an indication can be raised in the form of an alarm. As defined in ETSI GR NFV 003 [i. 1], an alarm is the information about a specific condition requiring attention, with the additional clarification that an alarm does, but not always, represent an error. NOTE: As defined in ETSI GR NFV 003 [i. 1], the terms "failure", "fault", "error" and "alarm" have different meanings. For interoperability purposes, the information that an alarm contains is typically specified and it contains data related to what objects are affected by the fault, the severity of the fault, when the fault event has been observed, the type of event, etc. <|end_of_text|>
|
The specification of alarms is contained in so called "information elements" in the stage 2 level specifications (see related references in clause 4. 2) or "data types" in the stage 3 level specifications of ETSI NFV. However, a subset of the attributes of the Alarm information element are either unspecified in terms of their content type, or when a content type is specified, possible values are not defined. Some of the affected attributes (see the list below) are of key importance for establishing correlation and relationship between alarms raised by different systems, possibly supplied by different providers, including: • "faultType": provides additional information related to the type of fault; • "probableCause": provides information about the probable cause of the fault; and • "faultDetails": provides additional information about the fault. In addition, a specified relationship between "severity", "faultType" and the corresponding resource or managed object types is necessary to enable consumers (network operators or other management systems) interpret the faults and perform root cause analysis in an interoperable multi-vendor environment. The present document defines the alarms (see clause 6), associating the content for the listed attributes to the various NFV-MANO managed objects (see clause 5), with the purpose to specify the missing content of Alarms described above, which is referred in clause 4. 2 as the "part of the content of the alarm". 4. 2 Relationship with other ETSI NFV deliverables The present document relates to other ETSI NFV deliverables as follows: • ETSI GS NFV-IFA 005 [i. <|end_of_text|>
|
4]: specifies the Or-Vi reference point requirements and interfaces including the Virtualised Resource Fault Management interface, which includes the operations for subscribing to, and raising alarm notifications related to virtualised resources. Clause 8. 6. 4 of ETSI GS NFV-IFA 005 [i. 4] specifies the Alarm information element for virtualised resources. The present document specifies part of the content of the alarms (i. e. valid values for certain attributes) related to the faults associated to virtualised resources. <|end_of_text|>
|
• ETSI GS NFV-IFA 006 [i. 5]: idem as ETSI GS NFV-IFA 005 [i. 4] but concerning to the Vi-Vnfm reference point. • ETSI GS NFV-IFA 007 [i. 6]: specifies the Or-Vnfm reference point requirements and interfaces including the VNF Fault Management interface, which includes the operations for subscribing to, and raising alarm notifications related to VNF instances. Clause 8. 8. 4 of ETSI GS NFV-IFA 007 [i. 6] specifies the Alarm information element for VNF instances. The present document specifies part of the content of the alarm related to the faults associated to VNF instances. • ETSI GS NFV-IFA 008 [i. 7]: idem as ETSI GS NFV-IFA 007 [i. 6] but concerning to the Ve-Vnfm reference point. • ETSI GS NFV-IFA 013 [i. 8]: specifies the Os-Ma-nfvo reference point requirements and interfaces including the NS Fault Management interface, which includes the operations for subscribing to, and raising alarm notifications related to NS instances. Clause 8. 5. 4 of ETSI GS NFV-IFA 013 [i. 8] specifies the Alarm information element for NS instances. The present document specifies part of the content of the alarm related to the faults associated to NS instances. • ETSI GS NFV-IFA 030 [i. 9]: idem as ETSI GS NFV-IFA 013 [i. 8] but concerning to the Or-Or reference point. • ETSI GS NFV-IFA 032 [i. 10]: specifies the interface requirements and interfaces for the management of multi-site connectivity services including the Fault Management interface, which includes the operations for subscribing to, and raising alarm notifications related to MSCS instances. Clause 8. <|end_of_text|>
|
4. 2 of ETSI GS NFV-IFA 032 [i. 10] specifies the Alarm information element for MSCS instances. The present document specifies part of the content of the alarm related to the faults associated to MSCS instances. • ETSI GS NFV-IFA 040 [i. 12]: specifies the service interface requirements and object model for the management of containerized workloads and OS container-related resources. See note. The present document specifies part of the content of the alarm related to the faults associated to containerized workloads. • ETSI GS NFV-IFA 036 [i. 13]: specifies the service interface requirements and object model for the management of CIS clusters, which includes the requirements for operations to subscribe to, and raise alarm notifications related to CIS clusters. The present document specifies part of the content of the alarm related to the faults associated to CIS clusters. • ETSI GS NFV-IFA 031 [i. 14]: specifies the interface requirements and object model for the management of NFV-MANO functional entities, which includes the requirements for operations to subscribe to, and raise alarm notifications associated to NFV-MANO functional entities and other related objects. The present document specifies part of the content of the alarm related to the faults associated to NFV-MANO functional entities. 5 Fault monitored object types 5. 1 Introduction Clause 5 identifies and specifies the object types in an NFV environment that can be monitored from a fault management perspective by the NFV-MANO. Alarms are associated to the specified fault monitored object types. As specified in the ETSI NFV specification referenced in clause 4. <|end_of_text|>
|
2, the Alarm information element contains the attribute "managedObjectId", which identifies the managed object associated to the Alarm. For each of the fault monitored object types, the corresponding managed object instance identifiers are identified with a reference to the respective referenced ETSI NFV specification in which such a managed object is specified. <|end_of_text|>
|
5. 2 Object type definitions 5. 2. 1 Virtual compute The fault monitored object type "VirtualCompute" is used to collect and report alarms for one or more instances of virtualised compute resource, i. e. a Virtual Machine (VM). The "managedObjectId", when used in an Alarm, corresponds to "computeId" (see clause 8. 4. 3. 2. 2 of ETSI GS NFV-IFA 006 [i. 5] or clause 8. 4. 3. 2. 2 of ETSI GS NFV-IFA 005 [i. 4]) of the monitored virtualised compute resource. 5. 2. 2 Virtual CPU The fault monitored object type "VirtualCpu" is used to collect and report alarms for one or more instances of virtual CPU which are part of a virtual compute resource. The report of alarm information of virtual CPU is provided via an Alarm associated to the contained object type "VirtualCompute" defined in clause 5. 2. 1. 5. 2. 3 Virtual memory The fault monitored object type "VirtualMemory" is used to collect and report alarms for one or more instances of virtual memory which are part of a virtual compute resource. The report of alarm information of virtual memory is provided via an Alarm associated to the contained object type "VirtualCompute" defined in clause 5. 2. 1. 5. 2. 4 Virtual storage The fault monitored object type "VirtualStorage" is used to collect and report alarms for one or more instances of virtualised storage resource. The "managedObjectId", when used in an Alarm, corresponds to "storageId" (see clause 8. 4. 7. 2. 2 of ETSI GS NFV-IFA 006 [i. 5] or clause 8. <|end_of_text|>
|
4. 7. 2. 2 of ETSI GS NFV-IFA 005 [i. 4]) of the monitored virtualised storage resource. 5. 2. 5 Virtual NIC The fault monitored object type "VirtualNetworkInterface" is used to collect and report alarms for one or more instances of virtualised network interface resource. The "managedObjectId", when used in an Alarm, corresponds to "resourceId" (see clause 8. 4. 3. 6. 2 of ETSI GS NFV-IFA 006 [i. 5] or clause 8. 4. 3. 6. 2 of ETSI GS NFV-IFA 005 [i. 4]) of the monitored virtualised network interface resource. 5. 2. 6 Virtual network The fault monitored object type "VirtualNetwork" is used to collect and report alarms for one or more instances of virtualised network resource. The "managedObjectId", when used in an Alarm, corresponds to "networkResourceId" (see clause 8. 4. 5. 2. 2 of ETSI GS NFV-IFA 006 [i. 5] or clause 8. 4. 5. 2. 2 of ETSI GS NFV-IFA 005 [i. 4]) of the monitored virtualised network resource. <|end_of_text|>
|
5. 2. 7 VNF The fault monitored object type "Vnf" is used to collect and report alarms for one or more instances of a VNF. The "managedObjectId", when used in an Alarm, corresponds to "vnfInstanceId" (see clause 9. 4. 2. 2 of ETSI GS NFV-IFA 008 [i. 7] or clause 8. 5. 2. 2 of ETSI GS NFV-IFA 007 [i. 6]) of the monitored VNF instance. 5. 2. 8 VNF component The fault monitored object type "Vnfc" is used to collect and report alarms for one or more instances of a VNFC. The report of alarm information of VNFC is provided via an Alarm associated to the contained object type "Vnf" defined in clause 5. 2. 7. The identifier of the VNFC, when used in an Alarm, corresponds to "vnfcInstanceId" (see clause 9. 4. 13. 2 of ETSI GS NFV-IFA 008 [i. 7] or clause 8. 5. 4. 2 of ETSI GS NFV-IFA 007 [i. 6]) of the monitored VNFC instance. 5. 2. 9 VNF virtual link The fault monitored object type "VnfVirtualLink" is used to collect and report alarms for one or more instances of an internal VL in a VNF. The report of alarm information of VNF virtual link is provided via an Alarm associated to the contained object type "Vnf" defined in clause 5. 2. 7. The identifier of the internal VL, when used in an Alarm, corresponds to "virtualLinkInstanceId" (see clause 9. 4. 5. 2 of ETSI GS NFV-IFA 008 [i. 7] or clause 8. 5. 5. <|end_of_text|>
|
2 of ETSI GS NFV-IFA 007 [i. 6]) of the monitored internal VL instance of a VNF. 5. 2. 10 VNF internal CP The fault monitored object type "VnfIntCp" is used to collect and report alarms for one or more instances of VNF internal CP. The report of alarm information of VNF internal CP is provided via an Alarm associated to the contained object type "Vnf" defined in clause 5. 2. 7. The identifier of the VNF internal CP, when used in an Alarm, corresponds to "cpInstanceId" (see clause 9. 4. 15. 2 of ETSI GS NFV-IFA 008 [i. 7] or clause 8. 5. 14. 2 of ETSI GS NFV-IFA 007 [i. 6]) of the monitored VNF internal CP instance. 5. 2. 11 VNF external CP The fault monitored object type "VnfExtCp" is used to collect and report alarms for one or more instances of VNF external CP. The report of alarm information of VNF external CP is provided via an Alarm associated to the contained object type "Vnf" defined in clause 5. 2. 7. The identifier of the VNF external CP, when used in an Alarm, corresponds to "cpInstanceId" (see clause 9. 8. 2. 2 of ETSI GS NFV-IFA 008 [i. 7] or clause 8. 5. 12. 2 of ETSI GS NFV-IFA 007 [i. 6]) of the monitored VNF external CP instance. 5. 2. 12 NS The fault monitored object type "Ns" is used to collect and report alarms for one or more instances of a NS. <|end_of_text|>
|
The "managedObjectId", when used in an Alarm, corresponds to "nsInstanceId" (see clause 8. 3. 3. 2. 2 of ETSI GS NFV-IFA 013 [i. 8]) of the monitored NS instance. 5. 2. 13 NS virtual link The fault monitored object type "NsVirtualLink" is used to collect and report alarms for one or more instances of an NS virtual link. <|end_of_text|>
|
The report of alarm information of NS virtual link is provided via an Alarm associated to the contained object type "Ns" defined in clause 5. 2. 12. The identifier of the NS virtual link, when used in an Alarm, corresponds to "nsVirtualLinkInstanceId" (see clause 8. 3. 3. 10. 2 of ETSI GS NFV-IFA 013 [i. 8]) of the monitored NS virtual link instance. 5. 2. 14 NS service access point The fault monitored object type "Sap" is used to collect and report alarms for one or more SAP instances of an NS instance. The report of alarm information of NS SAP is provided via an Alarm associated to the contained object type "Ns" defined in clause 5. 2. 12. The identifier of the NS SAP, when used in an Alarm, corresponds to "sapInstanceId" (see clause 8. 3. 3. 12. 2 of ETSI GS NFV-IFA 013 [i. 8]) of the monitored SAP instance. 5. 2. 15 MSCS The fault monitored object type "Mscs" is used to collect and report alarms for one or more instances of an MSCS. The "managedObjectId", when used in an Alarm, corresponds to "mscsId" (see clause 8. 2. 2. 5. 2 of ETSI GS NFV-IFA 032 [i. 10]) of the monitored MSCS. 5. 2. 16 MSNC The fault monitored object type "Msnc" is used to collect and report alarms for one or more instances of an MSCN. The report of alarm information of MSNC is provided via an Alarm associated to the contained object type "Mscs" defined in clause 5. 2. 15. <|end_of_text|>
|
The identifier of the MSNC, when used in an Alarm, corresponds to "msncId" (see clause 8. 2. 2. 6. 2 of ETSI GS NFV-IFA 032 [i. 10]) of the monitored MSNC. 5. 2. 17 CIS cluster The fault monitored object type "CisCluster" is used to collect and report alarms for one or more instances of a CIS cluster. The "managedObjectId", when used in an Alarm, corresponds to "cisClusterId" (see clause 4. 2. 4 of ETSI GS NFV-IFA 036 [i. 13]) of the monitored CIS cluster. 5. 2. 18 CIS cluster node The fault monitored object type "CisClusterNode" is used to collect and report alarms for one or more instances of a CIS cluster node, which can be a CIS instance, a CISM instance, or both. The report of alarm information of CIS cluster node is provided via an Alarm associated to the contained object type "CisCluster" defined in clause 5. 2. 17. The identifier of the CIS cluster node, when used in an Alarm, corresponds to "cisClusterNodeId" (see clause 4. 2. 4 of ETSI GS NFV-IFA 036 [i. 13]) of the monitored CIS cluster node. 5. 2. 19 CIS cluster storage The fault monitored object type "CisClusterStorage" is used to collect and report alarms for one or more instances of a CIS cluster storage resource. The report of alarm information of CIS cluster storage resource is provided via an Alarm associated to the contained object type "CisCluster" defined in clause 5. 2. 17. <|end_of_text|>
|
The identifier of the CIS cluster storage resource, when used in an Alarm, corresponds to "cisClusterStorageId" (see clause 4. 2. 4 of ETSI GS NFV-IFA 036 [i. 13]) of the monitored CIS cluster storage resource. 5. 2. 20 CIS cluster network The fault monitored object type "CisClusterNetwork" is used to collect and report alarms for one or more instances of a CIS cluster nodes network resource. <|end_of_text|>
|
The report of alarm information of CIS cluster nodes network resource is provided via an Alarm associated to the contained object type "CisCluster" defined in clause 5. 2. 17. The identifier of the CIS cluster nodes network resource, when used in an Alarm, corresponds to "cisClusterNetworkId" (see clause 4. 2. 4 of ETSI GS NFV-IFA 036 [i. 13]) of the monitored CIS cluster nodes network resource. 5. 2. 21 MCCO The fault monitored object type "Mcco" is used to collect and report alarms for one or more instances of an MCCO applied to the CIS cluster. The report of alarm information of an MCCO is provided via an Alarm associated to the contained object type "CisCluster" defined in clause 5. 2. 17. The identifier of the MCCO, when used in an Alarm, corresponds to "mccoId" (see clause 4. 2. 4 of ETSI GS NFV-IFA 036 [i. 13]) of the monitored MCCO. 5. 2. 22 CISI The fault monitored object type "Cisi" is used to collect and report alarms for one or more instances of a CIS. The "managedObjectId", when used in an Alarm, corresponds to "cisiId" (see clause 4. 2. 4 of ETSI GS NFV-IFA 036 [i. 13]) of the monitored CIS instance. 5. 2. 23 MCIO-C The fault monitored object type "Mcio-c" is used to collect and report alarms for one or more instances of a compute MCIO. The "managedObjectId", when used in an Alarm, corresponds to "ID of Compute MCIO" mapped to the resource handle's "resourceId" (see clause 8. 5. <|end_of_text|>
|
7 of ETSI GS NFV-IFA 007 [i. 6] or clause 9. 4. 7 of ETSI GS NFV-IFA 008 [i. 7]) of the monitored compute MCIO. 5. 2. 24 MANO entity The fault monitored object type "ManoEntity" is used to collect and report alarms for NFV-MANO functional entities. The "managedObjectId", when used in an Alarm, corresponds to "manoEntityId" (see clause 7. 2. 3. 2 of ETSI GS NFV-IFA 031 [i. 14]). 5. 2. 25 MANO service The fault monitored object type "ManoEntityService" is used to collect and report alarms for one or more instances of NFV-MANO services provided by the NFV-MANO functional entities. The report of alarm information of MANO service is provided via an Alarm associated to the contained object type "ManoEntity" defined in clause 5. 2. 24. The identifier of the MANO Service, when used in an Alarm, corresponds to "manoServiceId" (see clause 7. 2. 10. 2 of ETSI GS NFV-IFA 031 [i. 14]) of the monitored MANO Service. 5. 2. 26 MANO entity interface The fault monitored object type "ManoEntityInterface" is used to collect and report alarms for one or more instances of NFV-MANO service interfaces provided by the NFV-MANO functional entities. The report of alarm information of MANO entity interface is provided via an Alarm associated to the contained object type "ManoEntity" defined in clause 5. 2. 24. The identifier of the MANO Entity Interface when used in an Alarm, corresponds to "manoEntityInterfaceId" (see clause 7. 2. 10. 2 of ETSI GS NFV-IFA 031 [i. 14]) of the monitored MANO Service. 5. 2. <|end_of_text|>
|
27 MANO entity component The fault monitored object type "ManoEntityComponent" is used to collect and report alarms for one or more instances of NFV-MANO entity components which makes up one or multiple NFV-MANO functional entities. <|end_of_text|>
|
The report of alarm information of MANO entity component is provided via an Alarm associated to the contained object type "ManoEntity" defined in clause 5. 2. 24. The identifier of the MANO Entity Component when used in an Alarm, corresponds to "manoEntityComponentId" (see clause 7. 2. 13. 2 of ETSI GS NFV-IFA 031 [i. 14]) of the monitored MANO Service. 6 Alarm definition template The present clause introduces the template used to specify the additional alarm information. A description is provided about the meaning of the different fields in the template. a) Alarm Definition Identifier This field contains the unique identification of the alarm definition and corresponds to the value of the FaultType of the alarm information element. The identification shall be unique among defined Alarms and be defined as a string. b) Description This field contains the description of the alarm. c) Managed Object Type This field contains the definition of the applicable managed object associated to the alarm. See clause 5 for the managed object types specified in the present document. d) Event Type This field contains the event type of alarm. The event type shall take one of the following values: COMMUNICATIONS_ALARM: an alarm of this type is associated with the procedure and/or process required for conveying information from one point to another (as defined by Recommendation ITU-T X. 733 [1]). PROCESSING_ERROR_ALARM: an alarm of this type is associated with a software or processing fault (as defined by Recommendation ITU-T X. 733 [1]). <|end_of_text|>
|
ENVIRONMENTAL_ALARM: an alarm of this type is associated with a condition related to an enclosure in which the equipment resides (as defined by Recommendation ITU-T X. 733 [1]). QOS_ALARM: an alarm of this type is associated with degradation in the quality of service (as defined by Recommendation ITU-T X. 733 [1]). EQUIPMENT_ALARM: an alarm of this type is associated with an equipment fault (as defined by Recommendation ITU-T X. 733 [1]). Equipment can be either logical devices that are realized via some form of virtualisation or physical devices. e) Perceived Severity This field contains information about the perceived severities that is applicable to the alarm. The values of the perceived severity shall be selected from the following list: CRITICAL: it indicates that a service affecting condition has occurred and an immediate correction action is required (as defined by Recommendation ITU-T X. 733 [1]). MAJOR: it indicates that a service affecting condition has developed and an urgent correction action is required (as defined by Recommendation ITU-T X. 733 [1]). MINOR: it indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious fault (as defined by Recommendation ITU-T X. 733 [1]). WARNING: it indicates the detection of a potential or impeding service affecting fault, before any significant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious service affecting fault (as defined by Recommendation ITU-T X. 733 [1]). <|end_of_text|>
|
INDETERMINATE: it indicates that the severity level cannot be determined (as defined by Recommendation ITU-T X. 733 [1]). NOTE 1: The referenced ETSI NFV specifications that specify NFV-MANO interfaces include "CLEARED" as one of the enumeration values for "Perceived Severity". However, this value indicates the clearing of one or more previously reported alarms, and therefore it is a value that indicates the status of an Alarm and it is not used as a value in the Alarm definition. f) Probable Cause This field contains a description of the probable causes of the alarm. If there is any probable cause details that can be defined, this shall be defined as a string. g) Fault Details This field contains the additional details about the fault associated to the alarm. It can provide information about the form of creation of the alarm (direct or indirect, see note 2). If there are any fault details that can be defined, this shall be defined as one or more elements in an array of strings. NOTE 2: In direct mode, the NFV-MANO functional blocks generate an alarm based on metrics, faults, etc. information received from monitored objects directly. In indirect mode, the NFV-MANO functional blocks generate an alarm based on metrics, faults, etc. information generated by itself and/or alarms received from other functional blocks. 7 Alarm definitions 7. 1 Introduction Clause 7 specifies alarms associated managed objects in an NFV environment that can be monitored from a fault management perspective by NFV-MANO. <|end_of_text|>
|
The specification of the Alarms adheres to the following structure: • Specification of common definitions applicable to one or more specified Alarms. This includes the definition of which probable causes of Alarms can be mapped to event types and be associated to respective managed object types. • Specification of Alarms following the template defined in clause 6. The present document specifies Alarms associated to: • Virtualised resources (see clause 7. 2); • VNF instances (see clause 7. 3); • NS instances (see clause 7. 4); • MSCS (see clause 7. 5); • CIS clusters (see clause 7. 6); and • OS container workloads and CIS instances (see clause 7. 7); and • NFV-MANO functional entities (see clause 7. 8). <|end_of_text|>
|
7. 2 Alarms associated to virtualised resources 7. 2. 1 Common definitions 7. 2. 1. 1 Probable causes and fault details Table 7. 2. 1. 1-1 specifies probable causes and fault details that can be associated to alarms applicable to managed object types related to virtualised resources. <|end_of_text|>
|
NOTE: Entries in table 7. 2. 1. 1-1 are ordered alphabetically per "probable cause". Table 7. 2. 1. 1-1: Probable causes on alarms associated to virtualised resources Probable cause Description Event type Managed object types BIT_ERROR Event related to single/multiple bit errors of the resource associated to the managed object. PROCESSING_ERROR_ALARM VirtualMemory VirtualStorage CERTIFICATE_EXPIRATION Event related to expiration of certificate(s) for the managed object. PROCESSING_ERROR_ALARM VirtualCompute VirtualStorage CONFIGURATION Event related to configuration or state change of the managed object. PROCESSING_ERROR_ALARM VirtualCpu VirtualMemory VirtualStorage VirtualNetwork VirtualNetworkInterface CPU_BUS Event related to CPU's buses. EQUIPMENT_ALARM VirtualCpu CPU_DOWN CPU is down/not available. EQUIPMENT_ALARM VirtualCpu CPU_PROTOCOL CPU protocol related event, e. g. initialization procedure, state transitions, etc. PROCESSING_ERROR_ALARM VirtualCpu CPU_THROTTLING CPU throttling related event or state change. EQUIPMENT_ALARM VirtualCpu ECC Event related to changes in states or rates concerning Error Correction Code (ECC) of memory or storage resources. PROCESSING_ERROR_ALARM VirtualMemory VirtualStorage HOST_OS_ERROR Event related to a processing failure in the host OS. PROCESSING_ERROR_ALARM VirtualCompute MEMORY_STATE Event related to change of state on the memory. PROCESSING_ERROR_ALARM VirtualMemory NETWORK_CONNECTVITY_SIGNAL Event related to loss or changes in the connectivity signal provided/supported by the network resource. COMMUNICATIONS_ALARM VirtualNetwork NETWORK_CPU_OVERLOAD Event related to overload in the CPU/compute subsystems of the network resource. PROCESSING_ERROR_ALARM VirtualNetwork NETWORK_MEMORY_OVERLOAD Event related to overload in the memory subsystems of the network resource. PROCESSING_ERROR_ALARM VirtualNetwork NETWORK_OVERLOAD Event related to overload network input/output on the network resource. QOS_ALARM VirtualNetwork NETWORK_PACKET_LOSS Event related to packet loss experienced on the network resource. <|end_of_text|>
|
COMMUNICATIONS_ALARM VirtualNetwork VirtualNetworkInterface NETWORK_QOS Event related to degradation of QoS levels of the network resource, such as jitter and delay degradation. QOS_ALARM VirtualNetwork NFVI_COMPONENT_MAINTENANCE Event related to maintenance of an NFVI component. EQUIPMENT_ALARM VirtualCompute NFVI_COMPONENT_POWER_OUTAGE Event related to power outage of an NFVI component. EQUIPMENT_ALARM VirtualCompute NIC_CABLE Event related to cabling/connection of the network interface. EQUIPMENT_ALARM VirtualNetworkInterface NIC_LINK_DOWN Event related to a network interface link being down. COMMUNICATIONS_ALARM VirtualNetworkInterface NIC_LINK_TUNING Event related to network interface link tuning. COMMUNICATIONS_ALARM VirtualNetworkInterface NIC_PCI_ERROR Event related to a component of a Peripheral Component Interconnect (PCI) device. EQUIPMENT_ALARM VirtualNetworkInterface NIC_PCI_PARITY_ERROR Event related to PCI parity errors. PROCESSING_ERROR_ALARM VirtualNetworkInterface NIC_PCIE_ERROR Event related to a component of a PCI Express (PCIE) device. EQUIPMENT_ALARM VirtualNetworkInterface. <|end_of_text|>
|
Probable cause Description Event type Managed object types NODE_DOWN Event related to the compute server (machine) hosting the associated managed object is down/not available. EQUIPMENT_ALARM VirtualCompute REDUNDANCY Event related to the redundancy configuration of the managed object. EQUIPMENT_ALARM VirtualMemory VirtualStorage SENSOR Event related to the state of the sensor associated to the managed object. EQUIPMENT_ALARM VirtualCpu VirtualStorage STORAGE_BLOCK_ERROR Event related to bad blocks on the storage drive. PROCESSING_ERROR_ALARM VirtualStorage STORAGE_CACHE Event related to the storage cache. EQUIPMENT_ALARM VirtualStorage STORAGE_CAPACITY Event related to the storage disk capacity such as shortage. QOS_ALARM VirtualStorage STORAGE_CHECK Event related to consistency checks on a storage drive. PROCESSING_ERROR_ALARM VirtualStorage STORAGE_COMMUNICATION Event related to the communication to/from the storage. EQUIPMENT_ALARM VirtualStorage STORAGE_CONTROLLER Event related to the controller of the storage. EQUIPMENT_ALARM VirtualStorage STORAGE_DEFRAGMENTATION Event related to the defragmentation of the storage. PROCESSING_ERROR_ALARM VirtualStorage STORAGE_DOWN Storage is down/not available. PROCESSING_ERROR_ALARM VirtualStorage STORAGE_DRIVE_ARRAY Event related to storage's drive array. EQUIPMENT_ALARM VirtualStorage STORAGE_ENCLOSURE Event related to the storage's enclosure. ENVIRONMENTAL_ALARM VirtualStorage STORAGE_FAILURE_PREDICTION Event related to a predictive failure confirmed on a storage drive PROCESSING_ERROR_ALARM VirtualStorage STORAGE_MEMORY Event related memory resources of the storage drive. PROCESSING_ERROR_ALARM VirtualStorage STORAGE_PHYSICAL_DISK_DEGRADED Event related to the performance of the physical disk. QOS_ALARM VirtualStorage STORAGE_PHYSICAL_DISK_STATE A physical disk state has changed. PROCESSING_ERROR_ALARM VirtualStorage STORAGE_POWER Event related to power supply and/or power status of the storage. PROCESSING_ERROR_ALARM VirtualStorage STORAGE_REBUILD Event related to the rebuild process of the storage drive. PROCESSING_ERROR_ALARM VirtualStorage STORAGE_SCSI Event related to the Small Computer System Interface (SCSI) of the storage drive. <|end_of_text|>
|
EQUIPMENT_ALARM VirtualStorage STORAGE_SMART Event related to the Self-Monitoring Analysis and Reporting Technology (SMART) feature of the storage drive. EQUIPMENT_ALARM VirtualStorage STORAGE_VIRTUAL_DISK_DEGRADED Event related to the performance of the virtual disk. QOS_ALARM VirtualStorage STORAGE_VIRTUAL_DISK_STATE A virtual disk state has changed. PROCESSING_ERROR_ALARM VirtualStorage SYSTEM_LICENSE_EXPIRATION Event related to expiration of a license applicable to the managed object. PROCESSING_ERROR_ALARM VirtualCompute TEMPERATURE Event related to the temperature on the managed object. ENVIRONMENTAL_ALARM VirtualCpu VirtualMemory VirtualStorage VirtualNetwork VirtualNetworkInterface VERSION_ERROR Event related to version mismatches or incompatibilities, e. g. incompatibility between firmware and the resource on which is applied, wrong driver version. PROCESSING_ERROR_ALARM VirtualCpu VirtualStorage. <|end_of_text|>
|
7. 2. 2 COMPUTE_WARNING a) Alarm definition identifier: COMPUTE_WARNING. b) Description: The compute server (machine) hosting the virtualised compute resource has potential impeding service impacts, but the virtualised compute resource is still operational. c) Managed object type: VirtualCompute. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system). 7. 2. 3 COMPUTE_MINOR a) Alarm definition identifier: COMPUTE_MINOR. b) Description: The compute server (machine) hosting the virtualised compute resource has non-service affecting fault conditions. c) Managed object type: VirtualCompute. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system). 7. 2. 4 COMPUTE_MAJOR a) Alarm definition identifier: COMPUTE_MAJOR. b) Description: The compute server (machine) hosting the virtualised compute resource has service affecting conditions, but the virtualised compute resource is still operational. <|end_of_text|>
|
c) Managed object type: VirtualCompute. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system). <|end_of_text|>
|
7. 2. 5 COMPUTE_CRITICAL a) Alarm definition identifier: COMPUTE_CRITICAL. b) Description: The compute server (machine) hosting the virtualised compute resource has service affecting conditions and the virtualised compute resource is not fully operational. c) Managed object type: VirtualCompute. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system). 7. 2. 6 CPU_WARNING a) Alarm definition identifier: CPU_WARNING. b) Description: One or multiple CPUs supporting the virtual CPU used by the virtualised compute resource have potential impeding service impacts, but the CPU is still operational. c) Managed object type: VirtualCpu. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "cpuId=$cpuId", wherein "$cpuId" indicates the CPU id associated to the issue. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the CPU is enclosed. 7. 2. <|end_of_text|>
|
7 CPU_MINOR a) Alarm definition identifier: CPU_MINOR. b) Description: One or multiple CPUs supporting the virtual CPU used by the virtualised compute resource have non-service affecting fault conditions. c) Managed object type: VirtualCpu. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type: g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "cpuId=$cpuId", wherein "$cpuId" indicates the CPU id associated to the issue. <|end_of_text|>
|
- "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the CPU is enclosed. 7. 2. 8 CPU_MAJOR a) Alarm definition identifier: CPU_MAJOR. b) Description: One or multiple CPUs supporting the virtual CPU used by the virtualised compute resource have service affecting conditions, but the CPU is still operational. c) Managed object type: VirtualCpu. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "cpuId=$cpuId", wherein "$cpuId" indicates the CPU id associated to the issue. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the CPU is enclosed. 7. 2. 9 CPU_CRITICAL a) Alarm definition identifier: CPU_CRITICAL. b) Description: One or multiple CPUs supporting the virtual CPU used by the virtualised compute resource have service affecting conditions and the CPU is not fully operational. c) Managed object type: VirtualCpu. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. <|end_of_text|>
|
g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "cpuId=$cpuId", wherein "$cpuId" indicates the CPU id associated to the issue. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the CPU is enclosed. 7. 2. 10 MEMORY_WARNING a) Alarm definition identifier: MEMORY_WARNING. b) Description: One or multiple memory modules supporting the virtual memory used by the virtualised compute resource have potential impeding service impacts, but the memory resource is still operational. c) Managed object type: VirtualMemory. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: WARNING. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "raid", indicating the redundancy issues are related to Redundant Array of Independent Disks (RAID). - "mirrored", indicating redundancy issues are related to mirrored memory. - "spare", indicating redundancy issues are related to spare memory. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the memory is enclosed. 7. 2. 11 MEMORY_MINOR a) Alarm definition identifier: MEMORY_MINOR. b) Description: One or multiple memory modules supporting the virtual memory used by the virtualised compute resource have non-service affecting fault conditions. c) Managed object type: VirtualMemory. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "raid", indicating the redundancy issues are related to RAID. - "mirrored", indicating redundancy issues are related to mirrored memory. - "spare", indicating redundancy issues are related to spare memory. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the memory is enclosed. 7. 2. 12 MEMORY_MAJOR a) Alarm definition identifier: MEMORY_MAJOR. <|end_of_text|>
|
b) Description: One or multiple memory modules supporting the virtual memory used by the virtualised compute resource have service affecting conditions, but the memory resource is still operational. c) Managed object type: VirtualMemory. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "raid", indicating the redundancy issues are related to RAID. - "mirrored", indicating redundancy issues are related to mirrored memory. <|end_of_text|>
|
- "spare", indicating redundancy issues are related to spare memory. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the memory is enclosed. 7. 2. 13 MEMORY_CRITICAL a) Alarm definition identifier: MEMORY_CRITICAL. b) Description: One or multiple memory modules supporting the virtual memory used by the virtualised compute resource have service affecting conditions and the memory is not fully operational. c) Managed object type: VirtualMemory. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "raid", indicating the redundancy issues are related to RAID. - "mirrored", indicating redundancy issues are related to mirrored memory. - "spare", indicating redundancy issues are related to spare memory. - "memoryBank=$memId", wherein "$memId" indicates the memory bank id associated to the issue. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the memory is enclosed. 7. 2. 14 STORAGE_WARNING a) Alarm definition identifier: STORAGE_WARNING. b) Description: One or multiple drives supporting the virtual storage have potential impeding service impacts, but the storage resource is still operational. c) Managed object type: VirtualStorage. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: WARNING. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "driveId=$driveId", wherein "$driveId" indicates the drive id associated to the issue. - "redundancy=$redundancyInfo", wherein "$redundancyInfo" provides information about the current redundancy state of the storage. - "endpoint=$endpointId", wherein "$endpointId" indicates the identifier of the endpoint/port of the storage for connectivity associated to the issue. - "availableCapacity=$availableCapacity", wherein "$availableCapacity" indicates the available capacity of the storage associated to the issue. <|end_of_text|>
|
- "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer or storage system) where the storage drive is enclosed. 7. 2. 15 STORAGE_MINOR a) Alarm definition identifier: STORAGE_MINOR. b) Description: One or multiple drives supporting the virtual storage have non-service affecting fault conditions. c) Managed object type: VirtualStorage. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "driveId=$driveId", wherein "$driveId" indicates the drive id associated to the issue. - "redundancy=$redundancyInfo", wherein "$redundancyInfo" provides information about the current redundancy state of the storage. - "endpoint=$endpointId", wherein "$endpointId" indicates the identifier of the endpoint/port of the storage for connectivity associated to the issue. - "availableCapacity=$availableCapacity", wherein "$availableCapacity" indicates the available capacity of the storage associated to the issue. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer or storage system) where the storage drive is enclosed. 7. 2. 16 STORAGE_MAJOR a) Alarm definition identifier: STORAGE_MAJOR. b) Description: One or multiple drives supporting the virtual storage have service affecting conditions, but the storage resource is still operational. c) Managed object type: VirtualStorage. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MAJOR. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "driveId=$driveId", wherein "$driveId" indicates the drive id associated to the issue. - "redundancy=$redundancyInfo", wherein "$redundancyInfo" provides information about the current redundancy state of the storage. - "endpoint=$endpointId", wherein "$endpointId" indicates the identifier of the endpoint/port of the storage for connectivity associated to the issue. - "availableCapacity=$availableCapacity", wherein "$availableCapacity" indicates the available capacity of the storage associated to the issue. <|end_of_text|>
|
- "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer or storage system) where the storage drive is enclosed. 7. 2. 17 STORAGE_CRITICAL a) Alarm definition identifier: STORAGE_CRITICAL. b) Description: One or multiple drives supporting the virtual storage have service affecting conditions and the storage is not fully operational. c) Managed object type: VirtualStorage. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "driveId=$driveId", wherein "$driveId" indicates the drive id associated to the issue. - "redundancy=$redundancyInfo", wherein "$redundancyInfo" provides information about the current redundancy state of the storage. - "endpoint=$endpointId", wherein "$endpointId" indicates the identifier of the endpoint/port of the storage for connectivity associated to the issue. - "availableCapacity=$availableCapacity", wherein "$availableCapacity" indicates the available capacity of the storage associated to the issue. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer or storage system) where the storage drive is enclosed. 7. 2. 18 NIC_WARNING a) Alarm definition identifier: NIC_WARNING. b) Description: One or multiple network interface cards supporting the virtual network interface have potential impeding service impacts, but the network interface resource is still operational. c) Managed object type: VirtualNetworkInterface. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. <|end_of_text|>
|
1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "address=$busId:$deviceId. $functionId", wherein "$busId" indicates the bus id, "$deviceId" is the device id and "$functionId" is the function id, respectively, of the PCI device associated to the event. - "slot=$slotId", wherein the "$slotId" is the slot number of the device associated to the event. - "ipAddress=$ipAddress", wherein "$ipAddress" is the IP address of the virtual network interface. - "macAddress=$macAddress", wherein "$macAddress" is the MAC address of the virtual network interface. <|end_of_text|>
|
- "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the network device is enclosed. 7. 2. 19 NIC_MINOR a) Alarm definition identifier: NIC_MINOR. b) Description: One or multiple network interface cards supporting the virtual network interface have non-service affecting fault conditions. c) Managed object type: VirtualNetworkInterface. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "address=$busId:$deviceId. $functionId", wherein "$busId" indicates the bus id, "$deviceId" is the device id and "$functionId" is the function id, respectively, of the PCI device associated to the event. - "slot=$slotId", wherein the "$slotId" is the slot number of the device associated to the event. - "ipAddress=$ipAddress", wherein "$ipAddress" is the IP address of the virtual network interface. - "macAddress=$macAddress", wherein "$macAddress" is the MAC address of the virtual network interface. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the network device is enclosed. 7. 2. 20 NIC_MAJOR a) Alarm definition identifier: NIC_MAJOR. b) Description: One or multiple network interface cards supporting the virtual network interface have service affecting conditions, but the network interface resource is still operational. c) Managed object type: VirtualNetworkInterface. <|end_of_text|>
|
d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "address=$busId:$deviceId. $functionId", wherein "$busId" indicates the bus id, "$deviceId" is the device id and "$functionId" is the function id, respectively, of the PCI device associated to the event. - "slot=$slotId", wherein the "$slotId" is the slot number of the device associated to the event. - "ipAddress=$ipAddress", wherein "$ipAddress" is the IP address of the virtual network interface. - "macAddress=$macAddress", wherein "$macAddress" is the MAC address of the virtual network interface. <|end_of_text|>
|
- "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the network device is enclosed. 7. 2. 21 NIC_CRITICAL a) Alarm definition identifier: NIC_CRITICAL. b) Description: One or multiple network interface cards supporting the virtual network interface have service affecting conditions and the network interface is not fully operational. c) Managed object type: VirtualNetworkInterface. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "address=$busId:$deviceId. $functionId", wherein "$busId" indicates the bus id, "$deviceId" is the device id and "$functionId" is the function id, respectively, of the PCI device associated to the event. - "slot=$slotId", wherein the "$slotId" is the slot number of the device associated to the event. - "ipAddress=$ipAddress", wherein "$ipAddress" is the IP address of the virtual network interface. - "macAddress=$macAddress", wherein "$macAddress" is the MAC address of the virtual network interface. - "hostId=$hostId", wherein "$hostId" indicates the identifier of the host (computer system) where the network device is enclosed. 7. 2. 22 NETWORK_WARNING a) Alarm definition identifier: NETWORK_WARNING. b) Description: One or multiple networks supporting the virtual network have potential impeding service impacts, but the network resource is still operational. c) Managed object type: VirtualNetwork. <|end_of_text|>
|
d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "device=$deviceId", wherein "$deviceId" indicates the affected network resource device id. - "port=$portId", wherein the "$portId" is the interface port identifier of the affected network resource devices. - "link=$linkId", wherein the "$linkId" is the link identifier on the affected network resource. <|end_of_text|>
|
7. 2. 23 NETWORK _MINOR a) Alarm definition identifier: NETWORK _MINOR. b) Description: One or multiple networks supporting the virtual network have non-service affecting fault conditions. c) Managed object type: VirtualNetwork. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "device=$deviceId", wherein "$deviceId" indicates the affected network resource device id. - "port=$portId", wherein the "$portId" is the interface port identifier of the affected network resource devices. - "link=$linkId", wherein the "$linkId" is the link identifier on the affected network resource. 7. 2. 24 NETWORK _MAJOR a) Alarm definition identifier: NETWORK _MAJOR. b) Description: One or multiple networks supporting the virtual network have service affecting conditions, but the network resource is still operational. c) Managed object type: VirtualNetwork. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "device=$deviceId", wherein "$deviceId" indicates the affected network resource device id. <|end_of_text|>
|
- "port=$portId", wherein the "$portId" is the interface port identifier of the affected network resource devices. - "link=$linkId", wherein the "$linkId" is the link identifier on the affected network resource. 7. 2. 25 NETWORK _CRITICAL a) Alarm definition identifier: NETWORK _CRITICAL. b) Description: One or multiple networks supporting the virtual network have service affecting conditions and the network resource is not fully operational. c) Managed object type: VirtualNetwork. d) Event type: The event type associated to the probable cause as specified in table 7. 2. 1. 1-1. e) Perceived severity: CRITICAL. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 2. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "device=$deviceId", wherein "$deviceId" indicates the affected network resource device id. - "port=$portId", wherein the "$portId" is the interface port identifier of the affected network resource devices. - "link=$linkId", wherein the "$linkId" is the link identifier on the affected network resource. 7. 3 Alarms associated to VNF instances 7. 3. 1 Common definitions 7. 3. 1. 1 Probable causes and fault details Table 7. 3. 1. 1-1 specifies probable causes and fault details that can be associated to alarms applicable to managed object types related to VNF instances. NOTE: Entries in table 7. 3. 1. 1-1 are ordered alphabetically per "probable cause". <|end_of_text|>
|
Table 7. 3. 1. 1-1: Probable causes on alarms associated to VNF instances Probable cause Description Event type Managed object types CERTIFICATE_EXPIRATION Event related to expiration of certificate(s) for the managed object. PROCESSING_ERROR_ALARM Vnf, Vnfc See note 1 CPU_BUS Event related to buses of a CPU resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 CPU_CONFIGURATION Configuration related event or state change on a CPU resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 CPU_DOWN CPU resource associated to the managed object is down/not available. EQUIPMENT_ALARM Vnfc See note 1 CPU_PROTOCOL Event related to CPU protocol, e. g. initialization procedure, state transitions, etc. , on a CPU resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 CPU_TEMPERATURE Event related to the temperature on a CPU resource associated to the managed object. ENVIRONMENTAL_ALARM Vnfc See note 1 CPU_THROTTLING Throttling related event or state change on a CPU resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 HOST_OS_ERROR Event related to a processing failure in the host OS supporting the applicable managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 MCIO-C_STATE Event related to error states on the set of OS containers realizing an MCIO-C associated to the managed object. PROCESSING_ERROR_ALARM Vnfc MEMORY_BIT_ERROR Event related to single/multiple bit errors of the memory resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 MEMORY_CONFIGURATION Event related to configuration of the memory resource associated to the managed object. <|end_of_text|>
|
PROCESSING_ERROR_ALARM Vnfc See note 1 MEMORY_ECC Event related to changes in states or rates concerning Error Correction Code (ECC) of the memory resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 MEMORY_REDUNDANCY Event related to redundancy configuration of the memory resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 MEMORY_STATE Event related to change of state on the memory resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 MEMORY_TEMPERATURE Event related to the temperature of memory resource associated to the managed object. ENVIRONMENTAL_ALARM Vnfc See note 1 NETWORK_CONFIGURATION Event related to configuration issues with a network resource associated to the managed object. PROCESSING_ERROR_ALARM VnfVirtualLink NETWORK_CONNECTVITY_SIGNAL Event related to loss or changes in the connectivity signal provided/supported by a network resource associated to the managed object. COMMUNICATIONS_ALARM VnfVirtualLink NETWORK_CPU_OVERLOAD Event related to overload in the CPU/compute subsystems of a network resource associated to the managed object. PROCESSING_ERROR_ALARM VnfVirtualLink. <|end_of_text|>
|
Probable cause Description Event type Managed object types NETWORK_MEMORY_OVERLOAD Event related to overload in the memory subsystems of a network resource associated to the managed object. PROCESSING_ERROR_ALARM VnfVirtualLink NETWORK_OVERLOAD Event related to overload network input/output on a network resource associated to the managed object. QOS_ALARM VnfVirtualLink NETWORK_PACKET_LOSS Event related to packet loss experienced on a network resource associated to the managed object. COMMUNICATIONS_ALARM VnfVirtualLink NETWORK_QOS Event related to degradation of QoS levels of a network resource associated to the managed object, such as jitter and delay degradation. QOS_ALARM VnfVirtualLink NFVI_COMPONENT_MAINTENANCE Event related to maintenance of an NFVI component associated to the managed object. EQUIPMENT_ALARM Vnfc VnfVirtualLink See note 1 NIC_CABLE Event related to cabling/connection of the network interface associated to the managed object. EQUIPMENT_ALARM VnfIntCp, VnfExtCp NIC_CONFIGURATION Event related to a configuration of the network interface associated to the managed object. PROCESSING_ERROR_ALARM VnfIntCp, VnfExtCp NIC_LINK_DOWN Event related to a link down on the network interface associated to the managed object. COMMUNICATIONS_ALARM VnfIntCp, VnfExtCp NIC_LINK_TUNING Event related to link tuning of the network interface associated to the managed object. COMMUNICATIONS_ALARM VnfIntCp, VnfExtCp NIC_PCI_ERROR Event related to a component of a Peripheral Component Interconnect (PCI) device of the network interface associated to the managed object. EQUIPMENT_ALARM VnfIntCp, VnfExtCp NIC_PCI_PARITY_ERROR Event related to PCI parity errors of the network interface associated to the managed object. PROCESSING_ERROR_ALARM VnfIntCp, VnfExtCp NIC_PCIE_ERROR Event related to a component of a PCI Express (PCIE) device of the network interface associated to the managed object. <|end_of_text|>
|
EQUIPMENT_ALARM VnfIntCp, VnfExtCp NONRESOURCE_COMMUNICATIONS_ERROR Event related to communication errors not related to underlying resources associated to the managed object. COMMUNICATIONS_ALARM Vnf, Vnfc, VnfVirtualLink, VnfIntCp, VnfExtCp See note 1 NONRESOURCE_PROCESSING_ERROR Event related to processing errors not related to underlying resources associated to the managed object. PROCESSING_ERROR_ALARM Vnf, Vnfc, VnfVirtualLink, VnfIntCp, VnfExtCp See note 1 NONRESOURCE_QOS_ERROR Event related to quality of service errors not related to underlying resources associated to the managed object. QOS_ALARM Vnf, Vnfc, VnfVirtualLink, VnfIntCp, VnfExtCp See note 1 PROCESSOR_SENSOR Sensor related event or state change on a processor resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1. <|end_of_text|>
|
Probable cause Description Event type Managed object types STORAGE_BIT_ERROR Event related to single/multiple bit errors on the storage resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_BLOCK_ERROR Event related to bad blocks on the storage resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_CACHE Event related to the cache of the storage resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 STORAGE_CAPACITY Event related to capacity (such as shortage) of the storage resource associated to the managed object. QOS_ALARM Vnfc See note 1 STORAGE_CHECK Event related to consistency checks on a storage resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_COMMUNICATION Event related to the communication to/from the storage resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 STORAGE_CONFIGURATION Event related to the configuration of the storage associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_CONTROLLER Event related to the controller of the storage resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 STORAGE_DOWN Storage resource associated to the managed object is down/not available. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_DRIVE_ARRAY Event related to storage's drive array associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 STORAGE_ECC Event related to changes in states or rates concerning Error Correction Code (ECC) of the storage or memory resources associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_ENCLOSURE Event related to the enclosure of the storage resource associated to the managed object. <|end_of_text|>
|
ENVIRONMENTAL_ALARM Vnfc See note 1 STORAGE_FAILURE_PREDICTION Event related to a predictive failure confirmed on a storage resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_MEMORY Event related memory resources of the storage resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_PHYSICAL_DISK_DEGRADED Event related to the performance on a physical disk resource associated to the managed object. QOS_ALARM Vnfc See note 1 STORAGE_PHYSICAL_DISK_STATE The state has changed on a physical disk resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_POWER Event related to power supply and/or power status of the storage resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_REBUILD Event related to the rebuild process of the storage resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 STORAGE_REDUNDANCY Event related to redundancy configuration of the storage resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 STORAGE_SCSI Event related to the Small Computer System Interface (SCSI) of the storage resource associated to the managed object type. EQUIPMENT_ALARM Vnfc See note 1. <|end_of_text|>
|
Probable cause Description Event type Managed object types STORAGE_SENSOR Event or state change related to sensor of the storage resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 STORAGE_SMART Event related to the Self-Monitoring Analysis and Reporting Technology (SMART) feature of the storage resource associated to the managed object. EQUIPMENT_ALARM Vnfc See note 1 STORAGE_TEMPERATURE Event related to the temperature of the storage resource associated to the managed object. ENVIRONMENTAL_ALARM Vnfc See note 1 STORAGE_VIRTUAL_DISK_DEGRADED Event related to the performance on a virtual disk resource associated to the managed object. QOS_ALARM Vnfc See note 1 STORAGE_VIRTUAL_DISK_STATE The state has changed on a virtual disk resource associated to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 SYSTEM_LICENSE_EXPIRATION Event related to expiration of a license applicable to the managed object. PROCESSING_ERROR_ALARM Vnfc See note 1 NOTE 1: The probable cause for VNFC is applicable to both virtual compute based VNFC and containerized VNFC. See note 2. NOTE 2: The present document version does not specify the path (i. e. from which NFV-MANO functional block or function) and alarm/event correlation point by which the VNFM can learn about the events or alarms to associate the indicated probable cause to a containerized VNFC. 7. 3. 2 VNF_WARNING a) Alarm definition identifier: VNF_WARNING. b) Description: One or multiple of the underlying resources of the VNF instance have potential impeding service impacts, but the VNF instance is still operational. c) Managed object type: Vnf. d) Event type: The event type associated to the probable cause as specified in table 7. <|end_of_text|>
|
3. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: None defined. <|end_of_text|>
|
7. 3. 3 VNF_MINOR a) Alarm definition identifier: VNF_MINOR. b) Description: One or multiple of the underlying resources of the VNF instance are experimenting non-service affecting fault conditions and the VNF instance has non-service affecting fault conditions. c) Managed object type: Vnf. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: None defined. 7. 3. 4 VNF_MAJOR a) Alarm definition identifier: VNF_MAJOR. b) Description: One or multiple of the underlying resources of the VNF instance have service affecting conditions, but the VNF instance is still operational. c) Managed object type: Vnf. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: None defined. 7. 3. 5 VNF_CRITICAL a) Alarm definition identifier: VNF_CRITICAL. b) Description: One or multiple of the underlying resources of the VNF instance has service affecting conditions and the VNF instance is not fully operational. c) Managed object type: Vnf. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 3. 1. <|end_of_text|>
|
1-1 for the applicable managed object type. g) Fault details: None defined. 7. 3. 6 VNFC_WARNING a) Alarm definition identifier: VNFC_WARNING. b) Description: One or multiple of the underlying resources of the VNFC instance have potential impeding service impacts, but the VNFC instance is still operational. c) Managed object type: Vnfc. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. <|end_of_text|>
|
e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNFC instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying compute, storage and/or network resource associated to the issue. 7. 3. 7 VNFC_MINOR a) Alarm definition identifier: VNFC_MINOR. b) Description: One or multiple of the underlying resources of the VNFC instance are experimenting non-service affecting fault conditions and the VNFC instance has non-service affecting fault conditions. c) Managed object type: Vnfc. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNFC instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying compute, storage and/or network resource associated to the issue. 7. 3. 8 VNFC_MAJOR a) Alarm definition identifier: VNFC_MAJOR. b) Description: One or multiple of the underlying resources of the VNFC instance have service affecting conditions, but the VNFC instance is still operational. c) Managed object type: Vnfc. <|end_of_text|>
|
d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNFC instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying compute, storage and/or network resource associated to the issue. <|end_of_text|>
|
7. 3. 9 VNFC_CRITICAL a) Alarm definition identifier: VNFC_CRITICAL. b) Description: One or multiple of the underlying resources of the VNFC instance have service affecting conditions and the VNFC instance is not fully operational. c) Managed object type: Vnfc. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNFC instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying compute, storage and/or network resource associated to the issue. 7. 3. 10 VNFVIRTUALLINK_WARNING a) Alarm definition identifier: VNFVIRTUALLINK_WARNING. b) Description: One or multiple of the underlying resources of the VNF virtual link have potential impeding service impacts, but the VNF virtual link is still operational. c) Managed object type: VnfVirtualLink. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF virtual link instance id associated to the issue. <|end_of_text|>
|
- "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 11 VNFVIRTUALLINK_MINOR a) Alarm definition identifier: VNFVIRTUALLINK_MINOR. b) Description: One or multiple of the underlying resources of the VNF virtual link are experimenting non-service affecting fault conditions and the VNF virtual link has non-service affecting fault conditions. c) Managed object type: VnfVirtualLink. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. <|end_of_text|>
|
g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF virtual link instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 12 VNFVIRTUALLINK_MAJOR a) Alarm definition identifier: VNFVIRTUALLINK_MAJOR. b) Description: One or multiple of the underlying resources of the VNF virtual link have service affecting conditions, but the VNF virtual link is still operational. c) Managed object type: VnfVirtualLink. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF virtual link instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 13 VNFVIRTUALLINK_CRITICAL a) Alarm definition identifier: VNFVIRTUALLINK_CRITICAL. b) Description: One or multiple of the underlying resources of the VNF virtual link have service affecting conditions and the VNF virtual link is not fully operational. c) Managed object type: VnfVirtualLink. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: CRITICAL. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF virtual link instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. <|end_of_text|>
|
7. 3. 14 VNFINTCP_WARNING a) Alarm definition identifier: VNFINTCP_WARNING. b) Description: One or multiple of the underlying resources of the VNF internal CP have potential impeding service impacts, but the VNF internal CP is still operational. c) Managed object type: VnfIntCp. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF internal CP instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 15 VNFINTCP_MINOR a) Alarm definition identifier: VNFINTCP_MINOR. b) Description: One or multiple of the underlying resources of the VNF internal CP are experimenting non-service affecting fault conditions and the VNF internal CP has non-service affecting fault conditions. c) Managed object type: VnfIntCp. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF internal CPinstance id associated to the issue. <|end_of_text|>
|
- "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 16 VNFINTCP_MAJOR a) Alarm definition identifier: VNFINTCP_MAJOR. b) Description: One or multiple of the underlying resources of the VNF internal CP have service affecting conditions, but the VNF internal CP is still operational. c) Managed object type: VnfIntCp. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. <|end_of_text|>
|
g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF internal CPinstance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 17 VNFINTCP_CRITICAL a) Alarm definition identifier: VNFINTCP_CRITICAL. b) Description: One or multiple of the underlying resources of the VNF internal CP have service affecting conditions and the VNF internal CP is not fully operational. c) Managed object type: VnfIntCp. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF internal CPinstance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 18 VNFEXTCP_WARNING a) Alarm definition identifier: VNFEXTCP_WARNING. b) Description: One or multiple of the underlying resources of the VNF external CP have potential impeding service impacts, but the VNF external CP is still operational. c) Managed object type: VnfExtCp. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: WARNING. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF external CP instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. <|end_of_text|>
|
7. 3. 19 VNFEXTCP_MINOR a) Alarm definition identifier: VNFEXTCP_MINOR. b) Description: One or multiple of the underlying resources of the VNF external CPs are experimenting non-service affecting fault conditions and the VNF external CP has non-service affecting fault conditions. c) Managed object type: VnfExtCp. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF external CP instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 20 VNFEXTCP_MAJOR a) Alarm definition identifier: VNFEXTCP_MAJOR. b) Description: One or multiple of the underlying resources of the VNF external CP have service affecting conditions, but the VNF external CP is still operational. c) Managed object type: VnfExtCp. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF external CP instance id associated to the issue. <|end_of_text|>
|
- "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 3. 21 VNFEXTCP_CRITICAL a) Alarm definition identifier: VNFEXTCP_CRITICAL. b) Description: One or multiple of the underlying resources of the VNF external CP have service affecting conditions and the VNF external CP is not fully operational. c) Managed object type: VnfExtCp. d) Event type: The event type associated to the probable cause as specified in table 7. 3. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 3. 1. 1-1 for the applicable managed object type. <|end_of_text|>
|
g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the VNF external CP instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 4 Alarms associated to NS instances 7. 4. 1 Common definitions 7. 4. 1. 1 Probable causes and fault details Table 7. 4. 1. 1-1 specifies probable causes and fault details that can be associated to alarms applicable to managed object types related to NS instances. NOTE: Entries in table 7. 4. 1. 1-1 are ordered alphabetically per "probable cause". Table 7. 4. 1. 1-1: Probable causes on alarms associated to NS instances Probable cause Description Event type Managed object types NETWORK_CONFIGURATION Event related to configuration issues with the network resource associated to the managed object type. PROCESSING_ERROR_ALARM NsVirtualLink NETWORK_CONNECTVITY_SIGNAL Event related to loss or changes in the connectivity signal provided/supported by the network resource associated to the managed object type. COMMUNICATIONS_ALARM NsVirtualLink NETWORK_CPU_OVERLOAD Event related to overload in the CPU/compute subsystems of the network resource associated to the managed object type. PROCESSING_ERROR_ALARM NsVirtualLink NETWORK_MEMORY_OVERLOAD Event related to overload in the memory subsystems of the network resource associated to the managed object type. PROCESSING_ERROR_ALARM NsVirtualLink NETWORK_OVERLOAD Event related to overload network input/output on the network resource associated to the managed object type. QOS_ALARM NsVirtualLink NETWORK_PACKET_LOSS Event related to packet loss experienced on the network resource associated to the managed object type. <|end_of_text|>
|
COMMUNICATIONS_ALARM NsVirtualLink NETWORK_QOS Event related to degradation of QoS levels of the network resource associated to the managed object type, such as jitter and delay degradation. QOS_ALARM NsVirtualLink NONRESOURCE_COMMUNICATIONS_ERROR Event related to communication errors not related to underlying resources associated to the managed object. COMMUNICATIONS_ALARM Ns, NsVirtualLink, Sap. <|end_of_text|>
|
Probable cause Description Event type Managed object types NONRESOURCE_PROCESSING_ERROR Event related to processing errors not related to underlying resources associated to the managed object. PROCESSING_ERROR_ALARM Ns, NsVirtualLink, Sap NONRESOURCE_QOS_ERROR Event related to quality of service errors not related to underlying resources associated to the managed object. QOS_ALARM Ns, NsVirtualLink, Sap PNF_EXT_CP Event related to network interface resources for external connectivity of a PNF instance associated to the managed object. COMMUNICATIONS_ALARM PROCESSING_ERROR_ALARM EQUIPMENT_ALARM See note Ns, Sap VNF_EXT_CP Event related to network interface resources for external connectivity of a VNF instance associated to the managed object. COMMUNICATIONS_ALARM PROCESSING_ERROR_ALARM EQUIPMENT_ALARM See note Ns, Sap VNF_INT_CP Event related to network interface resources for internal connectivity of a VNF instance associated to the managed object. COMMUNICATIONS_ALARM PROCESSING_ERROR_ALARM EQUIPMENT_ALARM See note Ns VNF_VL Event related to network resources of a VNF instance associated to the managed object. COMMUNICATIONS_ALARM QOS_ALARM PROCESSING_ERROR_ALARM See note Ns VNF_VNFC_COMPUTE Event related to compute resources of a VNF instance associated to the managed object. PROCESSING_ERROR_ALARM EQUIPMENT_ALARM ENVIRONMENTAL_ALARM See note Ns VNF_VNFC_MEMORY Event related to memory resources of a VNF instance associated to the managed object. PROCESSING_ERROR_ALARM EQUIPMENT_ALARM ENVIRONMENTAL_ALARM See note Ns VNF_VNFC_STORAGE Event related to storage resources of a VNF instance associated to the managed object. PROCESSING_ERROR_ALARM EQUIPMENT_ALARM QOS_ALARM ENVIRONMENTAL_ALARM See note Ns NOTE: If more than one event type is mapped to the probable cause and the alarm is generated based on some underlying alarm received by the NFVO, the value of the event type shall be the same as the one from the underlying alarm. <|end_of_text|>
|
If the alarm cannot be correlated to another underlying alarm, the NFVO should set the value to EQUIPMENT_ALARM by default. <|end_of_text|>
|
7. 4. 2 NS_WARNING a) Alarm definition identifier: NS_WARNING. b) Description: One or multiple of the underlying resources and/or constituents of the NS instance have potential impeding service impacts, but NS instance is still operational. c) Managed object type: Ns. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "constituentId=$constituentId", wherein "$constituentId" indicates the instance id of the NS constituent (VNF, PNF) associated to the issue. 7. 4. 3 NS_MINOR a) Alarm definition identifier: NS_MINOR. b) Description: One or multiple of the underlying resources and/or constituents of the NS instance are experimenting non-service affecting fault conditions and the NS instance has non-service affecting fault conditions. c) Managed object type: Ns. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "constituentId=$constituentId", wherein "$constituentId" indicates the instance id of the NS constituent (VNF, PNF) associated to the issue. 7. 4. <|end_of_text|>
|
4 NS_MAJOR a) Alarm definition identifier: NS_MAJOR. b) Description: One or multiple of the underlying resources and/or constituents of the NS instance have service affecting conditions, but the NS instance is still operational. c) Managed object type: Ns. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. <|end_of_text|>
|
g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "constituentId=$constituentId", wherein "$constituentId" indicates the instance id of the NS constituent (VNF, PNF) associated to the issue. 7. 4. 5 NS_CRITICAL a) Alarm definition identifier: NS_CRITICAL. b) Description: One or multiple of the underlying resources and/or constituents of the NS instance have service affecting conditions and the NS instance is not fully operational. c) Managed object type: Ns. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "constituentId=$constituentId", wherein "$constituentId" indicates the instance id of the NS constituent (VNF, PNF) associated to the issue. 7. 4. 6 NSVIRTUALLINK_WARNING a) Alarm definition identifier: NSVIRTUALLINK_WARNING. b) Description: One or multiple of the underlying resources of the NS virtual link have potential impeding service impacts, but NS virtual link resource is still operational. c) Managed object type: NsVirtualLink. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. <|end_of_text|>
|
g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the NS virtual link instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 4. 7 NSVIRTUALLINK_MINOR a) Alarm definition identifier: NSVIRTUALLINK_MINOR. b) Description: One or multiple of the underlying resources of the NS virtual link are experimenting non-service affecting fault conditions and the NS virtual link has non-service affecting fault conditions. c) Managed object type: NsVirtualLink. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: MINOR. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the NS virtual link instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 4. 8 NSVIRTUALLINK_MAJOR a) Alarm definition identifier: NSVIRTUALLINK_MAJOR. b) Description: One or multiple of the underlying resources of the NS virtual link have service affecting conditions, but the NS virtual link is still operational. c) Managed object type: NsVirtualLink. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the NS virtual link instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. 7. 4. 9 NSVIRTUALLINK_CRITICAL a) Alarm definition identifier: NSVIRTUALLINK_CRITICAL. b) Description: One or multiple of the underlying resources of the NS virtual link have service affecting conditions and the NS virtual link is not fully operational. c) Managed object type: NsVirtualLink. <|end_of_text|>
|
d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the NS virtual link instance id associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network resource associated to the issue. <|end_of_text|>
|
7. 4. 10 SAP_WARNING a) Alarm definition identifier: SAP_WARNING. b) Description: One or multiple of the underlying resources of the NS service access point have potential impeding service impacts, but the NS service access point is still operational. c) Managed object type: Sap. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the SAP instance id associated to the issue. - "constituentId=$constituentId", wherein "$constituentId" indicates the instance id of the NS constituent (VNF, PNF) associated to the issue. 7. 4. 11 SAP_MINOR a) Alarm definition identifier: SAP_MINOR. b) Description: One or multiple of the underlying resources of the NS service access point have non-service affecting fault conditions and the NS service access point has non-service affecting fault conditions. c) Managed object type: Sap. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. <|end_of_text|>
|
g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the SAP instance id associated to the issue. - "constituentId=$constituentId", wherein "$constituentId" indicates the instance id of the NS constituent (VNF, PNF) associated to the issue. 7. 4. 12 SAP_MAJOR a) Alarm definition identifier: SAP_MAJOR. b) Description: One or multiple of the underlying resources of the NS service access point have service affecting conditions, but the NS service access point is still operational. c) Managed object type: Sap. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. <|end_of_text|>
|
g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the SAP instance id associated to the issue. - "constituentId=$constituentId", wherein "$constituentId" indicates the instance id of the NS constituent (VNF, PNF) associated to the issue. 7. 4. 13 SAP_CRITICAL a) Alarm definition identifier: SAP_CRITICAL. b) Description: One or multiple of the underlying resources of the NS service access point have service affecting conditions and the NS service access point is not fully operational. c) Managed object type: Sap. d) Event type: The event type associated to the probable cause as specified in table 7. 4. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 4. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following: - "instanceId=$instanceId", wherein "$instanceId" indicates the SAP instance id associated to the issue. - "constituentId=$constituentId", wherein "$constituentId" indicates the instance id of the NS constituent (VNF, PNF) associated to the issue. 7. 5 Alarms associated to MSCS 7. 5. 1 Common definitions 7. 5. 1. 1 Probable causes and fault details Table 7. 5. 1. 1-1 specifies probable causes and fault details that can be associated to alarms applicable to managed object types associated to MSCS. NOTE: Entries in table 7. 5. 1. 1-1 are ordered alphabetically per "probable cause". <|end_of_text|>
|
Table 7. 5. 1. 1-1: Probable causes on alarms associated to MSCS Probable cause Description Event type Managed object types ADAPTER_ERROR See note. Associated to network edge points (ports/interfaces) of a network node. EQUIPMENT_ALARM Msnc APPLICATION_SUBSYSTEM_FAILURE See note. Associated to network nodes. PROCESSING_ERROR_ALARM Mscs, Msnc BANDWIDTH_REDUCED See note. QOS_ALARM Mscs, Msnc CALL_ESTABLISHMENT_ERROR See note. COMMUNICATIONS_ALARM Mscs, Msnc COMMUNICATIONS_PROTOCOL_ERROR See note. COMMUNICATIONS_ALARM Mscs, Msnc COMMUNICATIONS_SUBSYSTEM_FAILURE See note. COMMUNICATIONS_ALARM Mscs, Msnc CONFIGURATION_ERROR See note. PROCESSING_ERROR_ALARM Mscs, Msnc CONGESTION See note. QOS_ALARM Mscs, Msnc CORRUPT_DATA See note. PROCESSING_ERROR_ALARM Mscs, Msnc CPU_CYCLES_LIMIT_EXCEEDED See note. Associated to network nodes. PROCESSING_ERROR_ALARM Msnc DEGRADED_SIGNAL See note. Associated to network links. COMMUNICATIONS_ALARM Msnc EQUIPMENT_MALFUNCTION See note. Associated to network nodes. EQUIPMENT_ALARM Msnc FILE_ERROR See note. Associated to network nodes. PROCESSING_ERROR_ALARM Mscs, Msnc FRAMING_ERROR See note. COMMUNICATIONS_ALARM Msnc INPUT_DEVICE_ERROR See note. Associated to network edge points (ports/interfaces) of a network node. EQUIPMENT_ALARM Msnc IO_DEVICE_ERROR See note. EQUIPMENT_ALARM Msnc LOCAL_NODE_TRANSMISSION_ERROR See note. COMMUNICATIONS_ALARM Msnc LOSS_OF_FRAME See note. COMMUNICATIONS_ALARM Msnc LOSS_OF_SIGNAL See note. Associated to network edge points (ports/interfaces) of a network node and network links. COMMUNICATIONS_ALARM Msnc MULTIPLEXER_PROBLEM See note. Associated to network links. EQUIPMENT_ALARM Msnc OUT_OF_MEMORY See note. Associated to network nodes. PROCESSING_ERROR_ALARM Msnc OUTPUT_DEVICE_ERROR See note. Associated to network edge points (ports/interfaces) of a network node. EQUIPMENT_ALARM Msnc PERFORMANCE_DEGRADED See note. QOS_ALARM Mscs, Msnc POWER_PROBLEM See note. Associated to network nodes. EQUIPMENT_ALARM Msnc PROCESSOR_PROBLEM See note. Associated to network nodes. EQUIPMENT_ALARM Msnc QUEUE_SIZE_EXCEEDED See note. Associated to network nodes. QOS_ALARM Msnc RECEIVE_FAILURE See note. <|end_of_text|>
|
Associated to network edge points (ports/interfaces) of a network node, network nodes and links. EQUIPMENT_ALARM Msnc RECEIVER_FAILURE See note. Associated to network nodes. EQUIPMENT_ALARM Msnc REMOTE_NODE_TRANSMISSION_ERROR See note. Associated to network links. COMMUNICATIONS_ALARM Msnc RESOURCE_NEARING_CAPACITY See note. Associated to network nodes. QOS_ALARM Msnc RETRANSMISSION_RATE_EXCESSIVE See note. QOS_ALARM Mscs, Msnc SOFTWARE_ERROR See note. Associated to network nodes. PROCESSING_ERROR_ALARM Msnc SOFTWARE_PROGRAM_ABNORMALLY_TERMINATED See note. Associated to network nodes. PROCESSING_ERROR_ALARM Msnc SOFTWARE_PROGRAM_ERROR See note. Associated to network nodes. PROCESSING_ERROR_ALARM Msnc. <|end_of_text|>
|
Probable cause Description Event type Managed object types STORAGE_CAPACITY_PROBLEM See note. Associated to network nodes. PROCESSING_ERROR_ALARM Msnc TIMING_PROBLEM See note. Associated to network nodes. EQUIPMENT_ALARM Msnc TRANSMIT_FAILURE See note. Associated to network edge points (ports/interfaces) of a network node, network nodes and network links. EQUIPMENT_ALARM Msnc TRANSMITTER_FAILURE See note. Associated to network nodes. EQUIPMENT_ALARM Msnc UNDERLYING_RESOURCE_UNAVAILABLE See note. Associated to network nodes. PROCESSING_ERROR_ALARM Msnc VERSION_MISMATCH See note. PROCESSING_ERROR_ALARM Mscs, Msnc NOTE: As defined in clause 8. 1. 2. 1 of Recommendation ITU-T X. 733 [1]. 7. 5. 2 MSCS_WARNING a) Alarm definition identifier: MSCS_WARNING. b) Description: One or multiple of the underlying resources of the MSCS have potential impeding service impacts, but the MSCS is still operational. c) Managed object type: Mscs. d) Event type: The event type associated to the probable cause as specified in table 7. 5. 1. 1-1. e) Perceived severity: WARNING. f) Probable cause: One of the probable causes specified in table 7. 5. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network node, network edge point or network link. 7. 5. 3 MSCS_MINOR a) Alarm definition identifier: MSCS_MINOR. b) Description: One or multiple of the underlying resources of the MSCS are experimenting non-service affecting fault conditions and the MSCS has non-service affecting fault conditions. c) Managed object type: Mscs. <|end_of_text|>
|
d) Event type: The event type associated to the probable cause as specified in table 7. 5. 1. 1-1. e) Perceived severity: MINOR. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 5. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network node, network edge point or network link. 7. 5. 4 MSCS_MAJOR a) Alarm definition identifier: MSCS_MAJOR. b) Description: One or multiple of the underlying resources of the MSCS have service affecting conditions, but the MSCS is still operational. c) Managed object type: Mscs. d) Event type: The event type associated to the probable cause as specified in table 7. 5. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 5. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network node, network edge point or network link. 7. 5. 5 MSCS_CRITICAL a) Alarm definition identifier: MSCS_CRITICAL. b) Description: One or multiple of the underlying resources of the MSCS has service affecting conditions and the MSCS is not fully operational. c) Managed object type: Mscs. d) Event type: The event type associated to the probable cause as specified in table 7. 5. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 5. 1. <|end_of_text|>
|
1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network node, network edge point or network link. 7. 5. 6 MSNC_WARNING a) Alarm definition identifier: MSNC_WARNING. b) Description: One or multiple of the underlying resources of the MSNC have potential impeding service impacts, but the MSNC is still operational. c) Managed object type: Msnc. d) Event type: The event type associated to the probable cause as specified in table 7. 5. 1. 1-1. e) Perceived severity: WARNING. <|end_of_text|>
|
f) Probable cause: One of the probable causes specified in table 7. 5. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "instanceId=$instanceId", wherein "$instanceId" indicates the identifier of the MSNC associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network node, network edge point or network link. 7. 5. 7 MSNC_MINOR a) Alarm definition identifier: MSNC_MINOR. b) Description: One or multiple of the underlying resources of the MSNC are experimenting non-service affecting fault conditions and the MSNC has non-service affecting fault conditions. c) Managed object type: Msnc. d) Event type: The event type associated to the probable cause as specified in table 7. 5. 1. 1-1. e) Perceived severity: MINOR. f) Probable cause: One of the probable causes specified in table 7. 5. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "instanceId=$instanceId", wherein "$instanceId" indicates the identifier of the MSNC associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network node, network edge point or network link. 7. 5. 8 MSNC_MAJOR a) Alarm definition identifier: MSNC_MAJOR. b) Description: One or multiple of the underlying resources of the MSNC have service affecting conditions, but the MSNC is still operational. c) Managed object type: Msnc. <|end_of_text|>
|
d) Event type: The event type associated to the probable cause as specified in table 7. 5. 1. 1-1. e) Perceived severity: MAJOR. f) Probable cause: One of the probable causes specified in table 7. 5. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "instanceId=$instanceId", wherein "$instanceId" indicates the identifier of the MSNC associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network node, network edge point or network link. <|end_of_text|>
|
7. 5. 9 MSNC_CRITICAL a) Alarm definition identifier: MSNC_CRITICAL. b) Description: One or multiple of the underlying resources of the MSNC have service affecting conditions and the MSNC is not fully operational. c) Managed object type: Msnc. d) Event type: The event type associated to the probable cause as specified in table 7. 5. 1. 1-1. e) Perceived severity: CRITICAL. f) Probable cause: One of the probable causes specified in table 7. 5. 1. 1-1 for the applicable managed object type. g) Fault details: Depending on the value of the probable cause, zero, one or multiple occurrences of the following strings: - "instanceId=$instanceId", wherein "$instanceId" indicates the identifier of the MSNC associated to the issue. - "resourceId=$resourceId", wherein "$resourceId" indicates the identifier of the underlying network node, network edge point or network link. 7. 6 Alarms associated to CIS clusters 7. 6. 1 Common definitions 7. 6. 1. 1 Probable causes and fault details Table 7. 6. 1. 1-1 specifies probable causes and fault details that can be associated to alarms applicable to managed object types associated to CIS clusters. NOTE: Entries in table 7. 6. 1. 1-1 are ordered alphabetically per "probable cause". <|end_of_text|>
|
Table 7. 6. 1. 1-1: Probable causes on alarms associated to CIS clusters Probable cause Description Event type Managed object types CERTIFICATE_EXPIRATION Event related to expiration of certificate(s) for the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage CIS_CLUSTER_COMMUNICATION Event related to the communication within the CIS cluster between CIS cluster nodes (e. g. between CISM and CIS instances). COMMUNICATIONS_ALARM CisCluster CPU_BUS Event related to buses of a CPU resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1 CPU_CONFIGURATION Configuration related event or state change on a CPU resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode See note 1 CPU_DOWN CPU resource associated to the managed object is down/not available. EQUIPMENT_ALARM CisClusterNode See note 1 CPU_PROTOCOL Event related to CPU protocol, e. g. initialization procedure, state transitions, etc. , on a CPU resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode See note 1 CPU_TEMPERATURE Event related to the temperature on a CPU resource associated to the managed object. ENVIRONMENTAL_ALARM CisClusterNode See note 1 CPU_THROTTLING Throttling related event or state change on a CPU resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1 HOST_OS_ERROR Event related to processing failure in the host OS of the CIS cluster node. PROCESSING_ERROR_ALARM CisClusterNode See note 1 MCCO_CONFIGURATION Event related to a configuration of the MCCO instance applied on the CIS cluster. PROCESSING_ERROR_ALARM Mcco MCCO_CONTROLLER Event related to malfunctioning of the controller part of an MCCO instance applied on the CIS cluster. PROCESSING_ERROR_ALARM Mcco MCCO_RESOURCE Event related to the resources realizing the MCCO instance. <|end_of_text|>
|
EQUIPMENT_ALARM Mcco MEMORY_BIT_ERROR Event related to single/multiple bit errors of the memory resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode See note 1 MEMORY_CONFIGURATION Event related to configuration of the memory resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode See note 1 MEMORY_ECC Event related to changes in states or rates concerning Error Correction Code (ECC) of the memory resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode See note 1 MEMORY_REDUNDANCY Event related to redundancy configuration of the memory resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1 MEMORY_STATE Event related to change of state on the memory resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode See note 1 MEMORY_TEMPERATURE Event related to the temperature of memory resource associated to the managed object. ENVIRONMENTAL_ALARM CisClusterNode See note 1 NETWORK_CONFIGURATION Event related to configuration issues with a network resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNetwork. <|end_of_text|>
|
Probable cause Description Event type Managed object types NETWORK_CONNECTVITY_SIGNAL Event related to loss or changes in the connectivity signal provided/supported by a network resource associated to the managed object. COMMUNICATIONS_ALARM CisClusterNetwork NETWORK_CPU_OVERLOAD Event related to overload in the CPU/compute subsystems of a network resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNetwork NETWORK_MEMORY_OVERLOAD Event related to overload in the memory subsystems of a network resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNetwork NETWORK_OVERLOAD Event related to overload network input/output on a network resource associated to the managed object. QOS_ALARM CisClusterNetwork NETWORK_PACKET_LOSS Event related to packet loss experienced on a network resource associated to the managed object. COMMUNICATIONS_ALARM CisClusterNetwork NETWORK_QOS Event related to degradation of QoS levels of a network resource associated to the managed object, such as jitter and delay degradation. QOS_ALARM CisClusterNetwork NFVI_COMPONENT_MAINTENANCE Event related to maintenance of an NFVI component associated to the managed object. EQUIPMENT_ALARM CisClusterNode NFVI_COMPONENT_POWER_OUTAGE Event related to power outage of an NFVI component. EQUIPMENT_ALARM CisClusterNode NIC_CABLE Event related to cabling/connection of the network interface associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1 NIC_CONFIGURATION Event related to a configuration of the network interface associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode See note 1 NIC_DOWN Event related to the NIC associated to the managed object is down/not available. EQUIPMENT_ALARM CisClusterNode See note 1 NIC_LINK_DOWN Event related to a link down on the network interface associated to the managed object. COMMUNICATIONS_ALARM CisClusterNode See note 1 NIC_LINK_TUNING Event related to link tuning of the network interface associated to the managed object. <|end_of_text|>
|
COMMUNICATIONS_ALARM CisClusterNode See note 1 NIC_PCI_ERROR Event related to a component of a Peripheral Component Interconnect (PCI) device of the network interface associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1 NIC_PCI_PARITY_ERROR Event related to PCI parity errors of the network interface associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode See note 1 NIC_PCIE_ERROR Event related to a component of a PCI Express (PCIE) device of the network interface associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1 NIC_RECEIVE_FAILURE Event related to errors in the reception of packet/frames by the network interface associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1 NIC_TRANSMIT_FAILURE Event related to errors in the transmission of packet/frames by the network interface associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1. <|end_of_text|>
|
Probable cause Description Event type Managed object types NODE_DOWN Event related to the virtual compute or bare-metal machine associated to the managed object is down/not available. EQUIPMENT_ALARM CisClusterNode See note 1 PROCESSOR_SENSOR Sensor related event or state change on a processor resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode See note 1 STORAGE_BIT_ERROR Event related to single/multiple bit errors on the storage resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_BLOCK_ERROR Event related to bad blocks on the storage resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_CACHE Event related to the cache of the storage resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_CAPACITY Event related to capacity (such as shortage) of the storage resource associated to the managed object. QOS_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_CHECK Event related to consistency checks on a storage resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_COMMUNICATION Event related to the communication to/from the storage resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_CONFIGURATION Event related to the configuration of the storage associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_CONTROLLER Event related to the controller of the storage resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_DOWN Storage resource associated to the managed object is down/not available. <|end_of_text|>
|
PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_DRIVE_ARRAY Event related to storage's drive array associated to the managed object. EQUIPMENT_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_ECC Event related to changes in states or rates concerning Error Correction Code (ECC) of the storage or memory resources associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_ENCLOSURE Event related to the enclosure of the storage resource associated to the managed object. ENVIRONMENTAL_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_FAILURE_PREDICTION Event related to a predictive failure confirmed on a storage resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2. <|end_of_text|>
|
Probable cause Description Event type Managed object types STORAGE_MEMORY Event related memory resources of the storage resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_PHYSICAL_DISK_DEGRADED Event related to the performance on a physical disk resource associated to the managed object. QOS_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_PHYSICAL_DISK_STATE The state has changed on a physical disk resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_POWER Event related to power supply and/or power status of the storage resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_REBUILD Event related to the rebuild process of the storage resource associated to the managed object. PROCESSING_ERROR_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_REDUNDANCY Event related to redundancy configuration of the storage resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_SCSI Event related to the Small Computer System Interface (SCSI) of the storage resource associated to the managed object type. EQUIPMENT_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_SENSOR Event or state change related to sensor of the storage resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_SMART Event related to the Self-Monitoring Analysis and Reporting Technology (SMART) feature of the storage resource associated to the managed object. EQUIPMENT_ALARM CisClusterNode CisClusterStorage See notes 1 and 2 STORAGE_TEMPERATURE Event related to the temperature of the storage resource associated to the managed object. <|end_of_text|>
|
End of preview. Expand
in Data Studio
No dataset card yet
- Downloads last month
- 2