An operator assigned value used in the determination of
application status. This value is used by the agent to
determine both the mapping of started processes to the
initiation of an application, as well as to allow for a
determination of application health. The default value,
unknown(5), is used when an operator has not yet assigned
one of the other values. If unknown(5) is set, bits
1 - 4 have no meaning. The possible values are:
executable(0),
An application may have one or
more executable elements. The rest of the
bits have no meaning if the element is not
executable.
exclusive(1),
Only one copy of an exclusive element may be
running per invocation of the running
application.
primary(2),
The primary executable. An application can
have one, and only one element that is designated
as the primary executable. The execution of
this element constitutes an invocation of
the application. This is used by the agent
implementation to determine the initiation of
an application. The primary executable must
remain running long enough for the agent
implementation to detect its presence.
required(3),
An application may have zero or more required
elements. All required elements must be running
in order for the application to be judged to be
running and healthy.
dependent(4),
An application may have zero or more
dependent elements. Dependent elements may
not be running unless required elements are.
unknown(5)
Default value for the case when an operator
has not yet assigned one of the other values.
When set, bits 1, 2, 3, and 4 have no meaning.
sysApplInstallElmtRole is used by the agent implementation
in determining the initiation of an application, the
current state of a running application (see
sysApplRunCurrentState), when an application invocation is
no longer running, and the exit status of a terminated
application invocation (see sysApplPastRunExitState).
Parsed from file SYSAPPL-MIB.mib
Module: SYSAPPL-MIB
An operator assigned value used in the determination of
application status. This value is used by the agent to
determine both the mapping of started processes to the
initiation of an application, as well as to allow for a
determination of application health. The default value,
unknown(5), is used when an operator has not yet assigned
one of the other values. If unknown(5) is set, bits
1 - 4 have no meaning. The possible values are:
executable(0),
An application may have one or
more executable elements. The rest of the
bits have no meaning if the element is not
executable.
exclusive(1),
Only one copy of an exclusive element may be
running per invocation of the running
application.
primary(2),
The primary executable. An application can
have one, and only one element that is designated
as the primary executable. The execution of
this element constitutes an invocation of
the application. This is used by the agent
implementation to determine the initiation of
an application. The primary executable must
remain running long enough for the agent
implementation to detect its presence.
required(3),
An application may have zero or more required
elements. All required elements must be running
in order for the application to be judged to be
running and healthy.
dependent(4),
An application may have zero or more
dependent elements. Dependent elements may
not be running unless required elements are.
unknown(5)
Default value for the case when an operator
has not yet assigned one of the other values.
When set, bits 1, 2, 3, and 4 have no meaning.
sysApplInstallElmtRole is used by the agent implementation
in determining the initiation of an application, the
current state of a running application (see
sysApplRunCurrentState), when an application invocation is
no longer running, and the exit status of a terminated
application invocation (see sysApplPastRunExitState).
sysApplInstallElmtRole OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(1))
-- SYNTAX BITS {
-- executable(0),
-- An application may have one or
-- more executable elements. The rest of the
-- bits have no meaning if the element is not
-- executable.
-- exclusive(1),
-- Only one copy of an exclusive element may be
-- running per invocation of the running
-- application.
-- primary(2),
-- The primary executable. An application can
-- have one, and only one element that is designated
-- as the primary executable. The execution of
-- this element constitutes an invocation of
-- the application. This is used by the agent
-- implementation to determine the initiation of
-- an application. The primary executable must
-- remain running long enough for the agent
-- implementation to detect its presence.
-- required(3),
-- An application may have zero or more required
-- elements. All required elements must be running
-- in order for the application to be judged to be
-- running and healthy.
-- dependent(4),
-- An application may have zero or more
-- dependent elements. Dependent elements may
-- not be running unless required elements are.
-- unknown(5)
-- Default value for the case when an operator
-- has not yet assigned one of the other values.
-- When set, bits 1, 2, 3, and 4 have no meaning.
-- }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An operator assigned value used in the determination of
application status. This value is used by the agent to
determine both the mapping of started processes to the
initiation of an application, as well as to allow for a
determination of application health. The default value,
unknown(5), is used when an operator has not yet assigned
one of the other values. If unknown(5) is set, bits
1 - 4 have no meaning. The possible values are:
executable(0),
An application may have one or
more executable elements. The rest of the
bits have no meaning if the element is not
executable.
exclusive(1),
Only one copy of an exclusive element may be
running per invocation of the running
application.
primary(2),
The primary executable. An application can
have one, and only one element that is designated
as the primary executable. The execution of
this element constitutes an invocation of
the application. This is used by the agent
implementation to determine the initiation of
an application. The primary executable must
remain running long enough for the agent
implementation to detect its presence.
required(3),
An application may have zero or more required
elements. All required elements must be running
in order for the application to be judged to be
running and healthy.
dependent(4),
An application may have zero or more
dependent elements. Dependent elements may
not be running unless required elements are.
unknown(5)
Default value for the case when an operator
has not yet assigned one of the other values.
When set, bits 1, 2, 3, and 4 have no meaning.
sysApplInstallElmtRole is used by the agent implementation
in determining the initiation of an application, the
current state of a running application (see
sysApplRunCurrentState), when an application invocation is
no longer running, and the exit status of a terminated
application invocation (see sysApplPastRunExitState)."
-- DEFVAL { 5 }
View at oid-info.com
An operator assigned value used in the determination of
application status. This value is used by the agent to
determine both the mapping of started processes to the
initiation of an application, as well as to allow for a
determination of application health. The default value,
unknown(5), is used when an operator has not yet assigned
one of the other values. If unknown(5) is set, bits
1 - 4 have no meaning. The possible values are:
executable(0),
An application may have one or
more executable elements. The rest of the
bits have no meaning if the element is not
executable.
exclusive(1),
Only one copy of an exclusive element may be
running per invocation of the running
application.
primary(2),
The primary executable. An application can
have one, and only one element that is designated
as the primary executable. The execution of
this element constitutes an invocation of
the application. This is used by the agent
implementation to determine the initiation of
an application. The primary executable must
remain running long enough for the agent
implementation to detect its presence.
required(3),
An application may have zero or more required
elements. All required elements must be running
in order for the application to be judged to be
running and healthy.
dependent(4),
An application may have zero or more
dependent elements. Dependent elements may
not be running unless required elements are.
unknown(5)
Default value for the case when an operator
has not yet assigned one of the other values.
When set, bits 1, 2, 3, and 4 have no meaning.
sysApplInstallElmtRole is used by the agent implementation
in determining the initiation of an application, the
current state of a running application (see
sysApplRunCurrentState), when an application invocation is
no longer running, and the exit status of a terminated
application invocation (see sysApplPastRunExitState).
Parsed from file rfc2287-System-Applications.mib.txt
Company: None
Module: SYSAPPL-MIB
An operator assigned value used in the determination of
application status. This value is used by the agent to
determine both the mapping of started processes to the
initiation of an application, as well as to allow for a
determination of application health. The default value,
unknown(5), is used when an operator has not yet assigned
one of the other values. If unknown(5) is set, bits
1 - 4 have no meaning. The possible values are:
executable(0),
An application may have one or
more executable elements. The rest of the
bits have no meaning if the element is not
executable.
exclusive(1),
Only one copy of an exclusive element may be
running per invocation of the running
application.
primary(2),
The primary executable. An application can
have one, and only one element that is designated
as the primary executable. The execution of
this element constitutes an invocation of
the application. This is used by the agent
implementation to determine the initiation of
an application. The primary executable must
remain running long enough for the agent
implementation to detect its presence.
required(3),
An application may have zero or more required
elements. All required elements must be running
in order for the application to be judged to be
running and healthy.
dependent(4),
An application may have zero or more
dependent elements. Dependent elements may
not be running unless required elements are.
unknown(5)
Default value for the case when an operator
has not yet assigned one of the other values.
When set, bits 1, 2, 3, and 4 have no meaning.
sysApplInstallElmtRole is used by the agent implementation
in determining the initiation of an application, the
current state of a running application (see
sysApplRunCurrentState), when an application invocation is
no longer running, and the exit status of a terminated
application invocation (see sysApplPastRunExitState).
sysApplInstallElmtRole OBJECT-TYPE SYNTAX BITS { executable(0), exclusive(1), primary(2), required(3), dependent(4), unknown(5) } MAX-ACCESS read-write STATUS current DESCRIPTION "An operator assigned value used in the determination of application status. This value is used by the agent to determine both the mapping of started processes to the initiation of an application, as well as to allow for a determination of application health. The default value, unknown(5), is used when an operator has not yet assigned one of the other values. If unknown(5) is set, bits 1 - 4 have no meaning. The possible values are: executable(0), An application may have one or more executable elements. The rest of the bits have no meaning if the element is not executable. exclusive(1), Only one copy of an exclusive element may be running per invocation of the running application. primary(2), The primary executable. An application can have one, and only one element that is designated as the primary executable. The execution of this element constitutes an invocation of the application. This is used by the agent implementation to determine the initiation of an application. The primary executable must remain running long enough for the agent implementation to detect its presence. required(3), An application may have zero or more required elements. All required elements must be running in order for the application to be judged to be running and healthy. dependent(4), An application may have zero or more dependent elements. Dependent elements may not be running unless required elements are. unknown(5) Default value for the case when an operator has not yet assigned one of the other values. When set, bits 1, 2, 3, and 4 have no meaning. sysApplInstallElmtRole is used by the agent implementation in determining the initiation of an application, the current state of a running application (see sysApplRunCurrentState), when an application invocation is no longer running, and the exit status of a terminated application invocation (see sysApplPastRunExitState)." DEFVAL { { unknown } } ::= { sysApplInstallElmtEntry 8 }
sysApplInstallElmtRole OBJECT-TYPE SYNTAX OCTET STRING(SIZE(1)) ACCESS read-write STATUS mandatory DESCRIPTION "An operator assigned value used in the determination of application status. This value is used by the agent to determine both the mapping of started processes to the initiation of an application, as well as to allow for a determination of application health. The default value, unknown(5), is used when an operator has not yet assigned one of the other values. If unknown(5) is set, bits 1 - 4 have no meaning. The possible values are: executable(0), An application may have one or more executable elements. The rest of the bits have no meaning if the element is not executable. exclusive(1), Only one copy of an exclusive element may be running per invocation of the running application. primary(2), The primary executable. An application can have one, and only one element that is designated as the primary executable. The execution of this element constitutes an invocation of the application. This is used by the agent implementation to determine the initiation of an application. The primary executable must remain running long enough for the agent implementation to detect its presence. required(3), An application may have zero or more required elements. All required elements must be running in order for the application to be judged to be running and healthy. dependent(4), An application may have zero or more dependent elements. Dependent elements may not be running unless required elements are. unknown(5) Default value for the case when an operator has not yet assigned one of the other values. When set, bits 1, 2, 3, and 4 have no meaning. sysApplInstallElmtRole is used by the agent implementation in determining the initiation of an application, the current state of a running application (see sysApplRunCurrentState), when an application invocation is no longer running, and the exit status of a terminated application invocation (see sysApplPastRunExitState)." ::= { sysApplInstallElmtEntry 8 }
Automatically extracted from Cisco "SNMP v2 MIBs".
sysApplInstallElmtRole OBJECT-TYPE SYNTAX BITS { executable(0), exclusive(1), primary(2), required(3), dependent(4), unknown(5) } MAX-ACCESS read-write STATUS current DESCRIPTION "An operator assigned value used in the determination of application status. This value is used by the agent to determine both the mapping of started processes to the initiation of an application, as well as to allow for a determination of application health. The default value, unknown(5), is used when an operator has not yet assigned one of the other values. If unknown(5) is set, bits 1 - 4 have no meaning. The possible values are: executable(0), An application may have one or more executable elements. The rest of the bits have no meaning if the element is not executable. exclusive(1), Only one copy of an exclusive element may be running per invocation of the running application. primary(2), The primary executable. An application can have one, and only one element that is designated as the primary executable. The execution of this element constitutes an invocation of the application. This is used by the agent implementation to determine the initiation of an application. The primary executable must remain running long enough for the agent implementation to detect its presence. required(3), An application may have zero or more required elements. All required elements must be running in order for the application to be judged to be running and healthy. dependent(4), An application may have zero or more dependent elements. Dependent elements may not be running unless required elements are. unknown(5) Default value for the case when an operator has not yet assigned one of the other values. When set, bits 1, 2, 3, and 4 have no meaning. sysApplInstallElmtRole is used by the agent implementation in determining the initiation of an application, the current state of a running application (see sysApplRunCurrentState), when an application invocation is no longer running, and the exit status of a terminated application invocation (see sysApplPastRunExitState)." DEFVAL { { unknown } } ::= { sysApplInstallElmtEntry 8 }
sysApplInstallElmtRole OBJECT-TYPE SYNTAX OCTET STRING(SIZE(1)) MAX-ACCESS read-write STATUS current DESCRIPTION "An operator assigned value used in the determination of application status. This value is used by the agent to determine both the mapping of started processes to the initiation of an application, as well as to allow for a determination of application health. The default value, unknown(5), is used when an operator has not yet assigned one of the other values. If unknown(5) is set, bits 1 - 4 have no meaning. The possible values are: executable(0), An application may have one or more executable elements. The rest of the bits have no meaning if the element is not executable. exclusive(1), Only one copy of an exclusive element may be running per invocation of the running application. primary(2), The primary executable. An application can have one, and only one element that is designated as the primary executable. The execution of this element constitutes an invocation of the application. This is used by the agent implementation to determine the initiation of an application. The primary executable must remain running long enough for the agent implementation to detect its presence. required(3), An application may have zero or more required elements. All required elements must be running in order for the application to be judged to be running and healthy. dependent(4), An application may have zero or more dependent elements. Dependent elements may not be running unless required elements are. unknown(5) Default value for the case when an operator has not yet assigned one of the other values. When set, bits 1, 2, 3, and 4 have no meaning. sysApplInstallElmtRole is used by the agent implementation in determining the initiation of an application, the current state of a running application (see sysApplRunCurrentState), when an application invocation is no longer running, and the exit status of a terminated application invocation (see sysApplPastRunExitState)." ::= { sysApplInstallElmtEntry 8 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.54.1.1.2.1.1 | sysApplInstallElmtIndex | 0 | 0 | An arbitrary integer used for indexing. The value of this index is unique among all rows in this table that exist or have existe… |
| 1.3.6.1.2.1.54.1.1.2.1.2 | sysApplInstallElmtName | 0 | 0 | The name of this element which is contained in the application. |
| 1.3.6.1.2.1.54.1.1.2.1.3 | sysApplInstallElmtType | 0 | 0 | The type of element that is part of the installed application. |
| 1.3.6.1.2.1.54.1.1.2.1.4 | sysApplInstallElmtDate | 0 | 0 | The date and time that this component was installed on the system. |
| 1.3.6.1.2.1.54.1.1.2.1.5 | sysApplInstallElmtPath | 0 | 0 | The full directory path where this element is installed. For example, the value would be '/opt/EMPuma/bin' for an element install… |
| 1.3.6.1.2.1.54.1.1.2.1.6 | sysApplInstallElmtSizeHigh | 0 | 0 | The installed file size in 2^32 byte blocks. This is the size of the file on disk immediately after installation. For example, fo… |
| 1.3.6.1.2.1.54.1.1.2.1.7 | sysApplInstallElmtSizeLow | 0 | 0 | The installed file size modulo 2^32 bytes. This is the size of the file on disk immediately after installation. For example, for… |
| 1.3.6.1.2.1.54.1.1.2.1.9 | sysApplInstallElmtModifyDate | 0 | 0 | The date and time that this element was last modified. Modification of the sysApplInstallElmtRole columnar object does NOT consti… |
| 1.3.6.1.2.1.54.1.1.2.1.10 | sysApplInstallElmtCurSizeHigh | 0 | 0 | The current file size in 2^32 byte blocks. For example, for a file with a total size of 4,294,967,296 bytes, this variable would … |
| 1.3.6.1.2.1.54.1.1.2.1.11 | sysApplInstallElmtCurSizeLow | 0 | 0 | The current file size modulo 2^32 bytes. For example, for a file with a total size of 4,294,967,296 bytes this variable would hav… |