📄 rfc2287.txt
字号:
sysApplInstallPkgDate OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time this software application was installed
on the host."
::= { sysApplInstallPkgEntry 6 }
sysApplInstallPkgLocation OBJECT-TYPE
SYNTAX LongUtf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The complete path name where the application package
is installed. For example, the value would be
'/opt/MyapplDir' if the application package was installed
in the /opt/MyapplDir directory."
::= { sysApplInstallPkgEntry 7 }
-- sysApplInstallElmtTable
-- The table describing the individual application package
-- elements (files and executables) installed on the host computer.
sysApplInstallElmtTable OBJECT-TYPE
SYNTAX SEQUENCE OF SysApplInstallElmtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table details the individual application package
elements (files and executables) which comprise the
applications defined in the sysApplInstallPkg Table.
Each entry in this table has an index to the
sysApplInstallPkg table to identify the application
package of which it is a part. As a result, there may
be many entries in this table for each instance in the
sysApplInstallPkg Table.
Table entries are indexed by sysApplInstallPkgIndex,
sysApplInstallElmtIndex to facilitate retrieval of
all elements associated with a particular installed
application package."
Krupczak & Saperia Standards Track [Page 12]
RFC 2287 MIB for Applications February 1998
::= { sysApplInstalled 2 }
sysApplInstallElmtEntry OBJECT-TYPE
SYNTAX SysApplInstallElmtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The logical row describing an element of an installed
application. The element may be an executable or
non-executable file."
INDEX {sysApplInstallPkgIndex, sysApplInstallElmtIndex}
::= { sysApplInstallElmtTable 1 }
SysApplInstallElmtEntry ::= SEQUENCE {
sysApplInstallElmtIndex Unsigned32,
sysApplInstallElmtName Utf8String,
sysApplInstallElmtType INTEGER,
sysApplInstallElmtDate DateAndTime,
sysApplInstallElmtPath LongUtf8String,
sysApplInstallElmtSizeHigh Unsigned32,
sysApplInstallElmtSizeLow Unsigned32,
sysApplInstallElmtRole BITS,
sysApplInstallElmtModifyDate DateAndTime,
sysApplInstallElmtCurSizeHigh Unsigned32,
sysApplInstallElmtCurSizeLow Unsigned32
}
sysApplInstallElmtIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..'ffffffff'h)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer used for indexing. The value
of this index is unique among all rows in this table
that exist or have existed since the last agent restart."
::= { sysApplInstallElmtEntry 1 }
sysApplInstallElmtName OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of this element which is contained in the
application."
::= { sysApplInstallElmtEntry 2 }
Krupczak & Saperia Standards Track [Page 13]
RFC 2287 MIB for Applications February 1998
sysApplInstallElmtType OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
nonexecutable(2),
operatingSystem(3), -- executable
deviceDriver(4), -- executable
application(5) -- executable
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of element that is part of the installed
application."
::= { sysApplInstallElmtEntry 3 }
sysApplInstallElmtDate OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time that this component was installed on
the system."
::= { sysApplInstallElmtEntry 4 }
sysApplInstallElmtPath OBJECT-TYPE
SYNTAX LongUtf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The full directory path where this element is installed.
For example, the value would be '/opt/EMPuma/bin' for an
element installed in the directory '/opt/EMPuma/bin'.
Most application packages include information about the
elements contained in the package. In addition, elements
are typically installed in sub-directories under the
package installation directory. In cases where the
element path names are not included in the package
information itself, the path can usually be determined
by a simple search of the sub-directories. If the
element is not installed in that location and there is
no other information available to the agent implementation,
then the path is unknown and null is returned."
::= { sysApplInstallElmtEntry 5}
sysApplInstallElmtSizeHigh OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
Krupczak & Saperia Standards Track [Page 14]
RFC 2287 MIB for Applications February 1998
DESCRIPTION
"The installed file size in 2^32 byte blocks. This is
the size of the file on disk immediately after installation.
For example, for a file with a total size of 4,294,967,296
bytes, this variable would have a value of 1; for a file
with a total size of 4,294,967,295 bytes this variable
would be 0."
::= { sysApplInstallElmtEntry 6 }
sysApplInstallElmtSizeLow OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The installed file size modulo 2^32 bytes. This is
the size of the file on disk immediately after installation.
For example, for a file with a total size of 4,294,967,296
bytes this variable would have a value of 0; for a file with
a total size of 4,294,967,295 bytes this variable would be
4,294,967,295."
::= { sysApplInstallElmtEntry 7 }
sysApplInstallElmtRole OBJECT-TYPE
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
Krupczak & Saperia Standards Track [Page 15]
RFC 2287 MIB for Applications February 1998
-- 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),
Krupczak & Saperia Standards Track [Page 16]
RFC 2287 MIB for Applications February 1998
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 }
sysApplInstallElmtModifyDate OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time that this element was last modified.
Modification of the sysApplInstallElmtRole columnar
object does NOT constitute a modification of the element
itself and should not affect the value of this object."
::= { sysApplInstallElmtEntry 9 }
sysApplInstallElmtCurSizeHigh OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 have a value of 1; for a file
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -