OID reference

fCPortController-OperationalStatus

1.3.6.1.4.1.14851.3.1.15.2.1.6

Description

Indicates the current status(es) of the element. Various health and operational statuses are defined. Many of the enumeration's values are self- explanatory. However, a few are not and are described in more detail. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' sta…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.14851.3.1.15.2.1 (fCPortEntry)
Node code
6
Node name
fCPortController-OperationalStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.14851.3.1.15.2.1.6
URN notation
urn:oid:1.3.6.1.4.1.14851.3.1.15.2.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 14851 3 1 15 2 1 6}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) snia(14851) libraries(3) smlRoot(1) fCPortGroup(15) fCPortTable(2) fCPortEntry(1) fCPortController-OperationalStatus(6)}
OID-IRI notation
  • /1/3/6/1/4/1/14851/3/1/15/2/1/6
  • /ISO/Identified-Organization/6/1/4/1/14851/3/1/15/2/1/6
  • /ISO/3/6/1/4/1/14851/3/1/15/2/1/6
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/14851/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/identified-organization/dod/internet/private/enterprise/snia/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/identified-organization/dod/internet/private/enterprises/14851/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/identified-organization/dod/internet/private/enterprises/snia/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/14851/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/snia/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/14851/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/snia/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/org/dod/internet/private/enterprise/14851/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/org/dod/internet/private/enterprise/snia/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/org/dod/internet/private/enterprises/14851/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/org/dod/internet/private/enterprises/snia/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/org/dod/internet/private/ldap-enterprise/14851/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/org/dod/internet/private/ldap-enterprise/snia/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/org/dod/internet/private/vendor-objects/14851/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • /iso/org/dod/internet/private/vendor-objects/snia/libraries/smlRoot/fCPortGroup/fCPortTable/fCPortEntry/fCPortController-OperationalStatus
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
mandatory

Enumerated values

ValueName
0unknown
1other
2ok
3degraded
4stressed
5predictiveFailure
6error
7non-RecoverableError
8starting
9stopping
10stopped
11inService
12noContact
13lostCommunication
14aborted
15dormant
16supportingEntityInError
17completed
18powerMode
19dMTFReserved
32768vendorReserved

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: fCPortIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.14851.3.1.15.2.1.6

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

fCPortController-OperationalStatus  OBJECT-TYPE 
    SYNTAX          INTEGER { unknown (0),
                              other (1),
                              ok (2),
                              degraded (3),
                              stressed (4),
                              predictiveFailure (5),
                              error (6),
                              non-RecoverableError (7),
                              starting (8),
                              stopping (9),
                              stopped  (10),
                              inService (11),
                              noContact (12),
                              lostCommunication (13),
                              aborted (14),
                              dormant (15),
                              supportingEntityInError (16),
                              completed (17),
                              powerMode (18),
                              dMTFReserved (19),
                              vendorReserved (32768) }
    MAX-ACCESS      read-only
    STATUS          mandatory
    DESCRIPTION     
         "Indicates the current status(es) of the element.
         Various health and operational statuses are defined. Many of
         the enumeration's values are self- explanatory. However, a few
         are not and are described in more detail. \n
         'Stressed' indicates that the element is functioning, but
         needs attention. Examples of 'Stressed' states are
         overload, overheated, etc. \n
         'Predictive Failure' indicates that an element is
         functioning nominally but predicting a failure in the near
         future. \n
         'In Service' describes an element being configured,
         maintained, cleaned, or otherwise administered. \n
         'No Contact' indicates that the monitoring system has
         knowledge of this element, but has never been able to
         establish communications with it. \n
         'Lost Communication' indicates that the ManagedSystem
         Element is known to exist and has been contacted
         successfully in the past, but is currently unreachable. \n
         'Stopped' and 'Aborted' are similar, although the
         former implies a clean and orderly stop, while the latter
         implies an abrupt stop where the element's state and
         configuration may need to be updated. \n
         'Dormant' indicates that the element is inactive or
         quiesced. \n
         'Supporting Entity in Error' describes that this element
         may be 'OK' but that another element, on which it is
         dependent, is in error. An example is a network service or
         endpoint that cannot function due to lower layer networking
         problems. \n
         'Completed' indicates the element has completed its
         operation. This value should be combined with either OK,
         Error, or Degraded so that a client can till if the
         complete operation passed (Completed with OK), and failure
         (Completed with Error). Completed with Degraded would imply
         the operation finished, but did not complete OK or report
         an error. \n
         'Power Mode' indicates the element has additional power
         model information contained in the Associated
         PowerManagementService association. \n
         OperationalStatus replaces the Status property on
         ManagedSystemElement to provide a consistent approach to
         enumerations, to address implementation needs for an array
         property, and to provide a migration path from today's
         environment to the future. This change was not made earlier
         since it required the DEPRECATED qualifier. Due to the
         widespread use of the existing Status property in
         management applications, it is strongly RECOMMENDED that
         providers/instrumentation provide BOTH the Status and
         OperationalStatus properties. Further, the first value of
         OperationalStatus SHOULD contain the primary status for the
         element. When instrumented, Status (since it is
         single-valued) SHOULD also provide the primary status of
         the element.
         
         SMI-S 1.1 Section 8.1.2.2.3 additional description for FC Ports
         OK        -  Port is online
         Error     -  Port has a failure
         Stopped   -  Port is disabled
         InService -  Port is in Self Test
         Unknown"
    ::=  {  fCPortEntry  6  }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Indicates the current status(es) of the element. Various health and operational statuses are defined. Many of the enumeration's values are self- explanatory. However, a few are not and are described in more detail. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n 'Stopped' and 'Aborted' are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the element's state and configuration may need to be updated. \n 'Dormant' indicates that the element is inactive or quiesced. \n 'Supporting Entity in Error' describes that this element may be 'OK' but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower layer networking problems. \n 'Completed' indicates the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can till if the complete operation passed (Completed with OK), and failure (Completed with Error). Completed with Degraded would imply the operation finished, but did not complete OK or report an error. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today's environment to the future. This change was not made earlier since it required the DEPRECATED qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly RECOMMENDED that providers/instrumentation provide BOTH the Status and OperationalStatus properties. Further, the first value of OperationalStatus SHOULD contain the primary status for the element. When instrumented, Status (since it is single-valued) SHOULD also provide the primary status of the element. SMI-S 1.1 Section 8.1.2.2.3 additional description for FC Ports OK - Port is online Error - Port has a failure Stopped - Port is disabled InService - Port is in Self Test Unknown

Sources for this description

IBM MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1IBM MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

fCPortController-OperationalStatus · mandatoryIBM MIB copies (LibreNMS/Observium Community)1 source

Status in source: mandatory.

Names: fCPortController-OperationalStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fCPortController-OperationalStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "unknown",
    "(",
    "0",
    ")",
    ",",
    "other",
    "(",
    "1",
    ")",
    ",",
    "ok",
    "(",
    "2",
    ")",
    ",",
    "degraded",
    "(",
    "3",
    ")",
    ",",
    "stressed",
    "(",
    "4",
    ")",
    ",",
    "predictiveFailure",
    "(",
    "5",
    ")",
    ",",
    "error",
    "(",
    "6",
    ")",
    ",",
    "non-RecoverableError",
    "(",
    "7",
    ")",
    ",",
    "starting",
    "(",
    "8",
    ")",
    ",",
    "stopping",
    "(",
    "9",
    ")",
    ",",
    "stopped",
    "(",
    "10",
    ")",
    ",",
    "inService",
    "(",
    "11",
    ")",
    ",",
    "noContact",
    "(",
    "12",
    ")",
    ",",
    "lostCommunication",
    "(",
    "13",
    ")",
    ",",
    "aborted",
    "(",
    "14",
    ")",
    ",",
    "dormant",
    "(",
    "15",
    ")",
    ",",
    "supportingEntityInError",
    "(",
    "16",
    ")",
    ",",
    "completed",
    "(",
    "17",
    ")",
    ",",
    "powerMode",
    "(",
    "18",
    ")",
    ",",
    "dMTFReserved",
    "(",
    "19",
    ")",
    ",",
    "vendorReserved",
    "(",
    "32768",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Indicates the current status(es) of the element. Various health and operational statuses are defined. Many of the enumeration's values are self- explanatory. However, a few are not and are described in more detail. \\n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \\n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \\n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \\n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \\n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \\n 'Stopped' and 'Aborted' are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the element's state and configuration may need to be updated. \\n 'Dormant' indicates that the element is inactive or quiesced. \\n 'Supporting Entity in Error' describes that this element may be 'OK' but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower layer networking problems. \\n 'Completed' indicates the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can till if the complete operation passed (Completed with OK), and failure (Completed with Error). Completed with Degraded would imply the operation finished, but did not complete OK or report an error. \\n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \\n OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today's environment to the future. This change was not made earlier since it required the DEPRECATED qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly RECOMMENDED that providers/instrumentation provide BOTH the Status and OperationalStatus properties. Further, the first value of OperationalStatus SHOULD contain the primary status for the element. When instrumented, Status (since it is single-valued) SHOULD also provide the primary status of the element. SMI-S 1.1 Section 8.1.2.2.3 additional description for FC Ports OK - Port is online Error - Port has a failure Stopped - Port is disabled InService - Port is in Self Test Unknown\"",
    "::=",
    "{",
    "fCPortEntry",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unknown",
            0
          ],
          [
            "other",
            1
          ],
          [
            "ok",
            2
          ],
          [
            "degraded",
            3
          ],
          [
            "stressed",
            4
          ],
          [
            "predictiveFailure",
            5
          ],
          [
            "error",
            6
          ],
          [
            "non-RecoverableError",
            7
          ],
          [
            "starting",
            8
          ],
          [
            "stopping",
            9
          ],
          [
            "stopped",
            10
          ],
          [
            "inService",
            11
          ],
          [
            "noContact",
            12
          ],
          [
            "lostCommunication",
            13
          ],
          [
            "aborted",
            14
          ],
          [
            "dormant",
            15
          ],
          [
            "supportingEntityInError",
            16
          ],
          [
            "completed",
            17
          ],
          [
            "powerMode",
            18
          ],
          [
            "dMTFReserved",
            19
          ],
          [
            "vendorReserved",
            32768
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Indicates the current status(es) of the element. Various health and operational statuses are defined. Many of the enumeration's values are self- explanatory. However, a few are not and are described in more detail. \\n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \\n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \\n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \\n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \\n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \\n 'Stopped' and 'Aborted' are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the element's state and configuration may need to be updated. \\n 'Dormant' indicates that the element is inactive or quiesced. \\n 'Supporting Entity in Error' describes that this element may be 'OK' but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower layer networking problems. \\n 'Completed' indicates the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can till if the complete operation passed (Completed with OK), and failure (Completed with Error). Completed with Degraded would imply the operation finished, but did not complete OK or report an error. \\n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \\n OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today's environment to the future. This change was not made earlier since it required the DEPRECATED qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly RECOMMENDED that providers/instrumentation provide BOTH the Status and OperationalStatus properties. Further, the first value of OperationalStatus SHOULD contain the primary status for the element. When instrumented, Status (since it is single-valued) SHOULD also provide the primary status of the element. SMI-S 1.1 Section 8.1.2.2.3 additional description for FC Ports OK - Port is online Error - Port has a failure Stopped - Port is disabled InService - Port is in Self Test Unknown"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.14851)

Jones Arnold

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.14851.3.1.15.2.1.1 fCPortIndex00
1.3.6.1.4.1.14851.3.1.15.2.1.2 fCPort-DeviceID00
1.3.6.1.4.1.14851.3.1.15.2.1.3 fCPort-ElementName00
1.3.6.1.4.1.14851.3.1.15.2.1.4 fCPort-Caption00
1.3.6.1.4.1.14851.3.1.15.2.1.5 fCPort-Description00
1.3.6.1.4.1.14851.3.1.15.2.1.7 fCPort-PermanentAddress00
1.3.6.1.4.1.14851.3.1.15.2.1.8 fCPort-Realizes-scsiProtocolControllerIndex00