📄 rfc2513.txt
字号:
collected."
::= { acctngSelectionEntry 4 }
acctngSelectionType OBJECT-TYPE
SYNTAX BITS { svcIncoming(0),
svcOutgoing(1),
svpIncoming(2),
svpOutgoing(3),
pvc(4),
pvp(5),
spvcOriginator(6),
spvcTarget(7),
spvpOriginator(8),
spvpTarget(9) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the types of connections for which the
McCloghrie, et. al. Standards Track [Page 12]
RFC 2513 Connection-Oriented Accounting MIB February 1999
information selected by this entry are to be collected."
DEFVAL { { svcIncoming, svcOutgoing,
svpIncoming, svpOutgoing } }
::= { acctngSelectionEntry 5 }
acctngSelectionRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. An agent may refuse to
create new conceptual rows and/or modify existing conceptual
rows, if such creation/modification would cause multiple
rows to have the same values of acctngSelectionSubtree and
acctngSelectionList.
A conceptual row can not have the status of 'active' until
values have been assigned to the acctngSelectionSubtree,
acctngSelectionList and acctngSelectionFile columnar objects
within that row.
An agent must not refuse to change the values of the
acctngSelectionSubtree, acctngSelectionList and
acctngSelectionFile columnar objects within a conceptual row
even while that row's status is 'active'. Similarly, an
agent must not refuse to destroy an existing conceptual row
while the file referenced by that row's instance of
acctngSelectionFile is in active use, i.e., while the
corresponding instance of acctngFileRowStatus has the value
'active'. However, such changes only take effect upon the
next occasion when collection begins into a new (version of
the) file."
::= { acctngSelectionEntry 6 }
-- The Accounting File table
acctngFileTable OBJECT-TYPE
SYNTAX SEQUENCE OF AcctngFileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of files into which accounting information is to be
stored."
::= { acctngFileControl 1 }
acctngFileEntry OBJECT-TYPE
SYNTAX AcctngFileEntry
MAX-ACCESS not-accessible
McCloghrie, et. al. Standards Track [Page 13]
RFC 2513 Connection-Oriented Accounting MIB February 1999
STATUS current
DESCRIPTION
"An entry identifying a file into which accounting
information is to be collected."
INDEX { acctngFileIndex }
::= { acctngFileTable 1 }
AcctngFileEntry ::=
SEQUENCE {
acctngFileIndex FileIndex,
acctngFileName DisplayString,
acctngFileNameSuffix DisplayString,
acctngFileDescription DisplayString,
acctngFileCommand INTEGER,
acctngFileMaximumSize Integer32,
acctngFileCurrentSize Integer32,
acctngFileFormat INTEGER,
acctngFileCollectMode BITS,
acctngFileCollectFailedAttempts BITS,
acctngFileInterval Integer32,
acctngFileMinAge Integer32,
acctngFileRowStatus RowStatus
}
acctngFileIndex OBJECT-TYPE
SYNTAX FileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique value identifying a file into which accounting
data is to be stored. This value is required to be the
permanent 'handle' for an entry in this table for as long as
that entry exists, including across restarts and power
outages."
::= { acctngFileEntry 1 }
acctngFileName OBJECT-TYPE
SYNTAX DisplayString (SIZE(1..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The name of the file into which accounting data is to be
stored. If files are named using suffixes, then the name of
the current file is the concatenation of acctngFileName and
acctngFileNameSuffix.
An agent will respond with an error (e.g., 'wrongValue') to
a management set operation which attempts to modify the
McCloghrie, et. al. Standards Track [Page 14]
RFC 2513 Connection-Oriented Accounting MIB February 1999
value of this object to the same value as already held by
another instance of acctngFileName. An agent will also
respond with an error (e.g., 'wrongValue') if the new value
is invalid for use as a file name on the local file system
(e.g., many file systems do not support white space embedded
in file names).
The value of this object can not be modified while the
corresponding instance of acctngFileRowStatus is 'active'."
::= { acctngFileEntry 2 }
acctngFileNameSuffix OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The suffix, if any, of the name of a file into which
accounting data is currently being stored. If suffixes are
not used, then the value of this object is the zero-length
string. Note that if a separator, such as a period, is used
in appending the suffix to the file name, then that
separator appears as the first character of this value."
::= { acctngFileEntry 3 }
acctngFileDescription OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The textual description of the accounting data which will
be stored (on the next occasion) when header information is
stored in the file. The value of this object may be
modified at any time."
DEFVAL { "" }
::= { acctngFileEntry 4 }
acctngFileCommand OBJECT-TYPE
SYNTAX INTEGER {
-- the following two values are states:
-- they may be read but not written
idle(1),
cmdInProgress(2),
-- the following two values are actions:
-- they may be written, but are never read
swapToNewFile(3),
collectNow(4)
}
MAX-ACCESS read-create
McCloghrie, et. al. Standards Track [Page 15]
RFC 2513 Connection-Oriented Accounting MIB February 1999
STATUS current
DESCRIPTION
"A control object for the collection of accounting data.
When read the value is either 'idle' or 'cmdInProgress'.
Writing a value is only allowed when the current value is
'idle'. When a value is successfully written, the value
changes to 'cmdInProgress' until completion of the action,
at which time the value reverts to 'idle'. Actions are
invoked by writing the following values:
'swapToNewFile' - the collection of data into the current
file is terminated, and collection continues into
a new (version of the) file.
'collectNow' - the agent creates and stores a connection
record into the current file for each active
connection having a type matching
acctngSelectionType and an age greater than
acctngFileMinAge."
DEFVAL { idle }
::= { acctngFileEntry 5 }
acctngFileMaximumSize OBJECT-TYPE
SYNTAX Integer32 (100..2147483647)
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum size of the file (including header
information). When the file of collected data reaches this
size, either the agent automatically swaps to a new version
(i.e., a new value acctngFileNameSuffix) of the file, or new
records are discarded. Since a file must contain an
integral number of connection records, the actual maximum
size of the file may be just less OR Just greater than the
value of this object.
The value of this object can not be modified while the
corresponding instance of acctngFileRowStatus is 'active'.
The largest value of the maximum file size in some agents
will be less than 2147483647 bytes."
DEFVAL { 5000000 }
::= { acctngFileEntry 6 }
acctngFileCurrentSize OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
UNITS "bytes"
MAX-ACCESS read-only
McCloghrie, et. al. Standards Track [Page 16]
RFC 2513 Connection-Oriented Accounting MIB February 1999
STATUS current
DESCRIPTION
"The current size of the file into which data is currently
being collected, including header information."
::= { acctngFileEntry 7 }
acctngFileFormat OBJECT-TYPE
SYNTAX INTEGER { other(1), ber(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An indication of the format in which the accounting data is
to be stored in the file. If the value is modified, the new
value takes effect after the next 'swap' to a new file. The
value ber(2) indicates the standard format."
DEFVAL { ber }
::= { acctngFileEntry 8 }
acctngFileCollectMode OBJECT-TYPE
SYNTAX BITS { onRelease(0), periodically(1) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An indication of when accounting data is to be written into
this file. Note that in addition to the occasions indicated
by the value of this object, an agent always writes
information on appropriate connections to the file when the
corresponding instance of acctngFileCommand is set to
'collectNow'.
- 'onRelease' - whenever a connection (or possibly,
connection attempt) is terminated, either through
a Release message or through management removal,
information on that connection is written.
- 'periodically' - information on appropriate connections
is written on the expiry of a periodic timer,
This value may be modified at any time."
DEFVAL { { onRelease } }
::= { acctngFileEntry 9 }
acctngFileCollectFailedAttempts OBJECT-TYPE
SYNTAX BITS { soft(0), regular(1) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An indication of whether connection data is to be collected
McCloghrie, et. al. Standards Track [Page 17]
RFC 2513 Connection-Oriented Accounting MIB February 1999
for failed connection attempts when the value of the
corresponding instance of acctngFileCollectMode includes
'onRelease'. The individual values have the following
meaning:
'soft' - indicates that connection data is to be collected
for failed Soft PVCs/PVPs which originate or terminate at
the relevant interface.
'regular' - indicates that connection data is to be
collected for failed SVCs, including Soft PVCs/PVPs not
originating or terminating at the relevant interface.
This value may be modified at any time."
DEFVAL { { soft, regular } }
::= { acctngFileEntry 10 }
acctngFileInterval OBJECT-TYPE
SYNTAX Integer32 (60..86400)
UNITS "seconds"
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -