Reference record for OID 1.3.6.1.2.1.54.1.1.2.1.8
- Parent
- 1.3.6.1.2.1.54.1.1.2.1 (sysApplInstallElmtEntry)
- Node code
- 8
- Node name
- sysApplInstallElmtRole
- Numeric OID
- 1.3.6.1.2.1.54.1.1.2.1.8
- URN notation
- urn:oid:1.3.6.1.2.1.54.1.1.2.1.8
- Type
- OBJECT-TYPE
- ASN.1 notation
-
{1 3 6 1 2 1 54 1 1 2 1 8}
- {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) sysApplMIB(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) sysApplTc(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) sysApplMIB(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) sysApplTc(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) sysApplMIB(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) sysApplTc(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) sysApplMIB(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) sysApplTc(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) sysApplMIB(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) sysApplTc(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) sysApplMIB(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) sysApplTc(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) sysApplMIB(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) sysApplTc(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) sysApplMIB(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) sysApplTc(54) sysApplOBJ(1) sysApplInstalled(1) sysApplInstallElmtTable(2) sysApplInstallElmtEntry(1) sysApplInstallElmtRole(8)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/2/1/54/1/1/2/1/8
- /ISO/Identified-Organization/6/1/2/1/54/1/1/2/1/8
- /ISO/3/6/1/2/1/54/1/1/2/1/8
- Named path variants
- /iso/identified-organization/dod/internet/mgmt/mib-2/sysApplMIB/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/identified-organization/dod/internet/mgmt/mib-2/sysApplTc/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/identified-organization/dod/internet/mgmt/mib/sysApplMIB/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/identified-organization/dod/internet/mgmt/mib/sysApplTc/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/sysApplMIB/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/sysApplTc/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/identified-organization/dod/internet/mgmt/stdmib-2/sysApplMIB/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/identified-organization/dod/internet/mgmt/stdmib-2/sysApplTc/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/org/dod/internet/mgmt/mib-2/sysApplMIB/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/org/dod/internet/mgmt/mib-2/sysApplTc/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/org/dod/internet/mgmt/mib/sysApplMIB/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/org/dod/internet/mgmt/mib/sysApplTc/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/sysApplMIB/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/sysApplTc/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/org/dod/internet/mgmt/stdmib-2/sysApplMIB/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- /iso/org/dod/internet/mgmt/stdmib-2/sysApplTc/sysApplOBJ/sysApplInstalled/sysApplInstallElmtTable/sysApplInstallElmtEntry/sysApplInstallElmtRole
- Additional combinations skipped.
Descriptions
Descriptions may differ between sources. The primary description is shown first.
Primary description: OID Repository
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-base.com
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-base.com
Automatically extracted from Cisco "SNMP v2 MIBs".
Alternative description: Circitor
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
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
Source file: Download SYSAPPL-MIB.mib · Publisher's file
File: DGS-1510_MIB_20150902/standardMIB/Reference MIB/SYSAPPL-MIB.mib; Publisher path: pub/Switch/DGS-1510-20/SNMP/DGS-1510_Series_A1_FW_v1.30.007_MIB.zip; 67,573 bytes
Related source files and packages:
- MIB package: DGS-1510_Series_A1_FW_v1.30.007_MIB.zipFile: pub/Switch/DGS-1510-28P/SNMP/DGS-1510_Series_A1_FW_v1.30.007_MIB.zip; Publisher Last-Modified: Mon, 15 Aug 2016 14:09:15 GMT; 935,503 bytes
- MIB package: DGS-1510_Series_A1_FW_v1.30.007_MIB.zipFile: pub/Switch/DGS-1510-52/SNMP/DGS-1510_Series_A1_FW_v1.30.007_MIB.zip; Publisher Last-Modified: Mon, 15 Aug 2016 14:09:29 GMT; 935,503 bytes
- MIB package: DXS-1100-R1.10-mibs-20161221.zipFile: pub/Switch/DXS-1100-10TS/SNMP/DXS-1100-R1.10-mibs-20161221.zip; Publisher Last-Modified: Mon, 05 Jun 2017 11:12:46 GMT; 580,984 bytes
Show all 20 related files and packages
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-28L/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:13:01 GMT; 1.0 MiB
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-28XS/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:12:49 GMT; 1.0 MiB
- MIB package: DXS-1100-R1.10-mibs-20161221.zipFile: pub/Switch/DXS-1100-16TC/SNMP/DXS-1100-R1.10-mibs-20161221.zip; Publisher Last-Modified: Mon, 05 Jun 2017 11:13:32 GMT; 580,984 bytes
- MIB package: DGS-1520_MIB_20200430.zipFile: pub/Switch/DGS-1520-52MP/SNMP/DGS-1520_MIB_20200430.zip; Publisher Last-Modified: Wed, 20 Jul 2022 09:20:48 GMT; 1.2 MiB
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-52L/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:12:46 GMT; 1.0 MiB
- MIB package: DGS-1520_MIB_20200430.zipFile: pub/Switch/DGS-1520-52/SNMP/DGS-1520_MIB_20200430.zip; Publisher Last-Modified: Fri, 17 Dec 2021 12:37:49 GMT; 1.2 MiB
- MIB package: DGS-1510_Series_A1_FW_v1.30.007_MIB.zipFile: pub/Switch/DGS-1510-28X/SNMP/DGS-1510_Series_A1_FW_v1.30.007_MIB.zip; Publisher Last-Modified: Mon, 15 Aug 2016 14:10:04 GMT; 935,503 bytes
- MIB package: DGS-1520_MIB_20200430.zipFile: pub/Switch/DGS-1520-28MP/SNMP/DGS-1520_MIB_20200430.zip; Publisher Last-Modified: Fri, 17 Dec 2021 12:37:34 GMT; 1.2 MiB
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-28XMP/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:12:52 GMT; 1.0 MiB
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-52X/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:12:42 GMT; 1.0 MiB
- MIB package: DGS-1510_Series_A1_FW_v1.30.007_MIB.zipFile: pub/Switch/DGS-1510-28/SNMP/DGS-1510_Series_A1_FW_v1.30.007_MIB.zip; Publisher Last-Modified: Mon, 15 Aug 2016 14:08:49 GMT; 935,503 bytes
- MIB package: DGS-1510_Series_A1_FW_v1.30.007_MIB.zipFile: pub/Switch/DGS-1510-52X/SNMP/DGS-1510_Series_A1_FW_v1.30.007_MIB.zip; Publisher Last-Modified: Mon, 15 Aug 2016 14:10:16 GMT; 935,503 bytes
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-28LP/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:13:05 GMT; 1.0 MiB
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-10L/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:12:55 GMT; 1.0 MiB
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-28X/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:13:08 GMT; 1.0 MiB
- MIB package: DGS-3000_R4.00_mibs_20171229_2.zipFile: pub/Switch/DGS-3000-20L/SNMP/DGS-3000_R4.00_mibs_20171229_2.zip; Publisher Last-Modified: Mon, 18 Mar 2019 09:12:58 GMT; 1.0 MiB
- MIB package: DGS-1510_Series_A1_FW_v1.30.007_MIB.zipFile: pub/Switch/DGS-1510-20/SNMP/DGS-1510_Series_A1_FW_v1.30.007_MIB.zip; Publisher Last-Modified: Mon, 15 Aug 2016 14:09:42 GMT; 935,503 bytes
Other official packages with the same file
DXS-1100-R1.10-mibs-20161221.zip
DXS-1100-R1.10-mibs-20161221.zip
Source file: Download SYSAPPL-MIB · Publisher's file
Copy from LibreNMS; 65,956 bytes
Vendor MIB copy from the LibreNMS archive.
Related source files and packages:
- LibreNMS original distribution archiveFile: librenms/librenms/tar.gz/…; 80.2 MiB
- Archive revision metadata: librenms/librenms (JSON)File: repos/librenms/librenms/commits/master; 36,945 bytes
Source file: Download rfc2287-sysappl.mib · Publisher's file
IES3220-8T4F Switch SNMP MIB Files; Models: IES3220-8T4F; Catalog updated: 2025-12-03 14:28:43; File: FS_MIB/rfc2287-sysappl.mib; Publisher path: mall/resource/ies3220-8t4f-switch-snmp-mib-files.zip; 61,851 bytes
Related source files and packages:
- IES5120-28TF Switch SNMP MIB FilesIES5120-28TF Switch SNMP MIB Files; Models: IES5120-28TF; Catalog updated: 2026-02-27 15:56:52; File: mall/resource/ies5120-28tf-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:14:36 GMT; 2.6 MiB
- IES3220-8T4F Switch SNMP MIB FilesIES3220-8T4F Switch SNMP MIB Files; Models: IES3220-8T4F; Catalog updated: 2025-12-03 14:28:43; File: mall/resource/ies3220-8t4f-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:08:16 GMT; 2.6 MiB
- IES5120-48T4S Switch SNMP MIB FilesIES5120-48T4S Switch SNMP MIB Files; Models: IES5120-48T4S; Catalog updated: 2026-02-27 16:10:26; File: mall/resource/ies5120-48t4s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:16:11 GMT; 2.6 MiB
Show all 10 related files and packages
- TSN3220-10S Switch SNMP MIB FilesTSN3220-10S Switch SNMP MIB Files; Models: TSN3220-10S; Catalog updated: 2026-01-08 09:53:00; File: mall/resource/tsn3220-10s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:10:41 GMT; 2.6 MiB
- IES5120-28TS-P Switch SNMP MIB FilesIES5120-28TS-P Switch SNMP MIB Files; Models: IES5120-28TS-P; Catalog updated: 2026-02-27 16:09:52; File: mall/resource/ies5120-28ts-p-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:40 GMT; 2.6 MiB
- IES5220-30TS-3ES Switch SNMP MIB FilesIES5220-30TS-3ES Switch SNMP MIB Files; Models: IES5220-30TS-3ES; Catalog updated: 2025-08-19 16:17:18; File: mall/resource/ies5220-30ts-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:17:18 GMT; 2.6 MiB
- IES5220-6S-3ES Switch SNMP MIB FilesIES5220-6S-3ES Switch SNMP MIB Files; Models: IES5220-6S-3ES; Catalog updated: 2026-02-27 16:11:15; File: mall/resource/ies5220-6s-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:32:47 GMT; 2.6 MiB
- IES3220-8T4F-U Switch SNMP MIB FilesIES3220-8T4F-U Switch SNMP MIB Files; Models: IES3220-8T4F-U; Catalog updated: 2025-12-03 14:47:49; File: mall/resource/ies3220-8t4f-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:09:07 GMT; 2.6 MiB
- IES5120-28TS Switch SNMP MIB FilesIES5120-28TS Switch SNMP MIB Files; Models: IES5120-28TS; Catalog updated: 2026-02-27 15:57:39; File: mall/resource/ies5120-28ts-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:08 GMT; 2.6 MiB
- TSN3220-10S-U Switch SNMP MIB FilesTSN3220-10S-U Switch SNMP MIB Files; Models: TSN3220-10S-U; Catalog updated: 2025-12-16 18:11:48; File: mall/resource/tsn3220-10s-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:13:57 GMT; 2.6 MiB
Other official packages with the same file
tsn3220-10s-u-switch-snmp-mib-files.zip
tsn3220-10s-switch-snmp-mib-files.zip
Source file: Download SYSAPPL.mib · Publisher's file
File: DGS-3630-R2.0-MIB-20170927/Standard MIB/SYSAPPL.mib; Publisher path: pub/Switch/DGS-3630-28SC/SNMP/DGS-3630-R2.0-MIB-20170927.zip; 67,488 bytes
Related source files and packages:
- MIB package: DGS-3630-R2.0-MIB-20170927.zipFile: pub/Switch/DGS-3630-28TC/SNMP/DGS-3630-R2.0-MIB-20170927.zip; Publisher Last-Modified: Wed, 11 Oct 2017 12:49:25 GMT; 2.2 MiB
- MIB package: DGS-3630_MIB_R1.00.zipFile: pub/Switch/DGS-3630-28TC/SNMP/DGS-3630_MIB_R1.00.zip; Publisher Last-Modified: Mon, 28 Nov 2016 13:32:39 GMT; 2.2 MiB
- MIB package: DGS-3630_MIB_R1.00.zipFile: pub/Switch/DGS-3630-28SC/SNMP/DGS-3630_MIB_R1.00.zip; Publisher Last-Modified: Mon, 28 Nov 2016 13:32:27 GMT; 2.2 MiB
Show all 14 related files and packages
- MIB package: DXS-3400_MIB_R2.0.zipFile: pub/Switch/DXS-3400-24TC/SNMP/DXS-3400_MIB_R2.0.zip; Publisher Last-Modified: Mon, 28 Nov 2016 11:06:51 GMT; 2.7 MiB
- MIB package: DXS3400_MIB_20181212.zipFile: pub/Switch/DXS-3400-24SC/SNMP/DXS3400_MIB_20181212.zip; Publisher Last-Modified: Fri, 23 Jul 2021 08:48:20 GMT; 2.7 MiB
- MIB package: DGS-3630_MIB_R1.00.zipFile: pub/Switch/DGS-3630-52TC/SNMP/DGS-3630_MIB_R1.00.zip; Publisher Last-Modified: Mon, 28 Nov 2016 13:32:48 GMT; 2.2 MiB
- MIB package: DGS-3630-R2.0-MIB-20170927.zipFile: pub/Switch/DGS-3630-52TC/SNMP/DGS-3630-R2.0-MIB-20170927.zip; Publisher Last-Modified: Wed, 11 Oct 2017 12:58:14 GMT; 2.2 MiB
- MIB package: DXS-3400_MIB_R1.00.B040.zipFile: pub/Switch/DXS-3400-24SC/SNMP/DXS-3400_MIB_R1.00.B040.zip; Publisher Last-Modified: Thu, 26 May 2016 12:08:17 GMT; 1.3 MiB
- MIB package: MIB.rarFile: pub/Switch/DXS-3410-32XY/SNMP/MIB.rar; Publisher Last-Modified: Wed, 19 Mar 2025 07:06:32 GMT; 1.2 MiB
- MIB package: DXS3400_MIB_20181212.zipFile: pub/Switch/DXS-3400-24TC/SNMP/DXS3400_MIB_20181212.zip; Publisher Last-Modified: Fri, 23 Jul 2021 08:44:52 GMT; 2.7 MiB
- MIB package: DXS-3400_MIB_R2.0.zipFile: pub/Switch/DXS-3400-24SC/SNMP/DXS-3400_MIB_R2.0.zip; Publisher Last-Modified: Mon, 28 Nov 2016 11:07:03 GMT; 2.7 MiB
- MIB package: DXS-3400_MIB_R1.00.B040.zipFile: pub/Switch/DXS-3400-24TC/SNMP/DXS-3400_MIB_R1.00.B040.zip; Publisher Last-Modified: Thu, 26 May 2016 12:08:02 GMT; 1.3 MiB
- MIB package: MIB.rarFile: pub/Switch/DXS-3410-32SY/SNMP/MIB.rar; Publisher Last-Modified: Wed, 19 Mar 2025 07:07:02 GMT; 1.2 MiB
- MIB package: DGS-3630-R2.0-MIB-20170927.zipFile: pub/Switch/DGS-3630-28SC/SNMP/DGS-3630-R2.0-MIB-20170927.zip; Publisher Last-Modified: Wed, 11 Oct 2017 12:34:14 GMT; 2.2 MiB
Other official packages with the same file
Source file: Download rfc2287a.txt · Publisher's file Junos OS Evolved 26.2R1
Junos OS Evolved 26.2R1; File: ./rfc2287a.txt; Publisher path: mib-explorer/downloadArchive; 65,972 bytes
Source file: Download mib-rfc2287a.txt · Publisher's file Junos OS 26.2R1
Junos OS 26.2R1; File: StandardMibs/mib-rfc2287a.txt; Publisher path: mib-explorer/downloadArchive; 65,956 bytes
Source file: Download RFC 2287 · Publisher's file · RFC errata
File: rfc/rfc2287.txt; 98,210 bytes
Source file: Download SYSAPPL-MIB.mib
Publisher path: Mibs; 69,104 bytes
Alternative description: Cisco
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).
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).
Source file: Download SYSAPPL-MIB.txt · Publisher's file
Copy from Netdisco; File: rfc/SYSAPPL-MIB.txt; 66,546 bytes
Vendor MIB copy from the Netdisco archive.
Related source files and packages:
- Netdisco archive revision metadata (not a manufacturer release date)File: repos/netdisco/netdisco-mibs/commits/master; 15,422 bytes
- Netdisco MIB distribution at the selected archive revision38.9 MiB
Source file: Download SYSAPPL-MIB · Publisher's file
Copy from Observium Community; File: rfc/SYSAPPL-MIB; 66,546 bytes
Vendor MIB copy from the Observium Community archive.
Related source files and packages:
- Observium Community original distribution archivePublisher Last-Modified: Tue, 05 May 2026 13:47:48 GMT; 127.4 MiB
Source file: Download SYSAPPL-MIB.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v2/SYSAPPL-MIB.my; 66,546 bytes
Source file: Download SYSAPPL-MIB.my.txt
File: cisco/SYSAPPL-MIB.my.txt; 68,098 bytes
Alternative description: Cisco SMIv1
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).
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).
Source file: Download SYSAPPL-MIB-V1SMI.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v1/SYSAPPL-MIB-V1SMI.my; 52,707 bytes
Source file: Download SYSAPPL-MIB-V1SMI.my.txt
File: cisco/SYSAPPL-MIB-V1SMI.my.txt; 54,108 bytes
Alternative description: MIBdepot
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).
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).
Source file: Download rfc2287-System-Applications.mib.txt
File: ietf_rfcs/rfc2287-System-Applications.mib.txt; 67,911 bytes
Information from Circitor
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 }
Information from Cisco SMIv1
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 }
Information from MIBdepot
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 }
Information from Cisco
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 }
First Registration Authority (inferred from ancestor 1.3.6)
Current Registration Authority (inferred from ancestor 1.3.6.1.2)
Internet Assigned Numbers Authority
Siblings (10)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.54.1.1.2.1.1 | sysApplInstallElmtIndex | 0 | 0 | sysApplInstallElmtIndex OBJECT-TYPE SYNTAX Unsigned32 (1.. fffffffh) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An a… |
| 1.3.6.1.2.1.54.1.1.2.1.2 | sysApplInstallElmtName | 0 | 0 | sysApplInstallElmtName OBJECT-TYPE SYNTAX Utf8String MAX-ACCESS read-only STATUS current DESCRIPTION "The name of this element … |
| 1.3.6.1.2.1.54.1.1.2.1.3 | sysApplInstallElmtType | 0 | 0 | sysApplInstallElmtType OBJECT-TYPE SYNTAX INTEGER { unknown(1), nonexecutable(2), operatingSystem(3), -- executable deviceDrive… |
| 1.3.6.1.2.1.54.1.1.2.1.4 | sysApplInstallElmtDate | 0 | 0 | sysApplInstallElmtDate OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The date and time that t… |
| 1.3.6.1.2.1.54.1.1.2.1.5 | sysApplInstallElmtPath | 0 | 0 | sysApplInstallElmtPath OBJECT-TYPE SYNTAX LongUtf8String MAX-ACCESS read-only STATUS current DESCRIPTION "The full directory pa… |
| 1.3.6.1.2.1.54.1.1.2.1.6 | sysApplInstallElmtSizeHigh | 0 | 0 | sysApplInstallElmtSizeHigh OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The installed file si… |
| 1.3.6.1.2.1.54.1.1.2.1.7 | sysApplInstallElmtSizeLow | 0 | 0 | sysApplInstallElmtSizeLow OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The installed file siz… |
| 1.3.6.1.2.1.54.1.1.2.1.9 | sysApplInstallElmtModifyDate | 0 | 0 | sysApplInstallElmtModifyDate OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The date and time … |
| 1.3.6.1.2.1.54.1.1.2.1.10 | sysApplInstallElmtCurSizeHigh | 0 | 0 | sysApplInstallElmtCurSizeHigh OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The current file s… |
| 1.3.6.1.2.1.54.1.1.2.1.11 | sysApplInstallElmtCurSizeLow | 0 | 0 | sysApplInstallElmtCurSizeLow OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The current file si… |