📄 rfc1271.txt
字号:
Remote Network Monitoring Working Group [Page 17]RFC 1271 Remote Network Monitoring MIB November 1991 etherStatsPkts1024to1518Octets OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of packets (including error packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets)." ::= { etherStatsEntry 19 } etherStatsOwner OBJECT-TYPE SYNTAX OwnerString ACCESS read-write STATUS mandatory DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::= { etherStatsEntry 20 } etherStatsStatus OBJECT-TYPE SYNTAX EntryStatus ACCESS read-write STATUS mandatory DESCRIPTION "The status of this etherStats entry." ::= { etherStatsEntry 21 } -- The History Group -- Implementation of the History group is optional. -- -- The history group records periodic statistical samples from -- a network and stores them for later retrieval. The -- historyControl table stores configuration entries that each -- define an interface, polling period, and other parameters. -- Once samples are taken, their data is stored in an entry -- in a media-specific table. Each such entry defines one -- sample, and is associated with the historyControlEntry that -- caused the sample to be taken. Currently the only media- -- specific table defined is the etherHistoryTable, for -- Ethernet networks. -- -- If the probe keeps track of the time of day, it should -- start the first sample of the history at a time such that -- when the next hour of the day begins, a sample is -- started at that instant. This tends to make moreRemote Network Monitoring Working Group [Page 18]RFC 1271 Remote Network Monitoring MIB November 1991 -- user-friendly reports, and enables comparison of reports -- from different probes that have relatively accurate time -- of day. -- -- The monitor is encouraged to add two history control entries -- per monitored interface upon initialization that describe -- a short term and a long term polling period. Suggested -- parameters are 30 seconds for the short term polling -- period and 30 minutes for the long term period. historyControlTable OBJECT-TYPE SYNTAX SEQUENCE OF HistoryControlEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of history control entries." ::= { history 1 } historyControlEntry OBJECT-TYPE SYNTAX HistoryControlEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of parameters that set up a periodic sampling of statistics." INDEX { historyControlIndex } ::= { historyControlTable 1 } HistoryControlEntry ::= SEQUENCE { historyControlIndex INTEGER (1..65535), historyControlDataSource OBJECT IDENTIFIER, historyControlBucketsRequested INTEGER (1..65535), historyControlBucketsGranted INTEGER (1..65535), historyControlInterval INTEGER (1..3600), historyControlOwner OwnerString, historyControlStatus INTEGER } historyControlIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "An index that uniquely identifies an entry in the historyControl table. Each such entry defines a set of samples at a particular interval for an interface on the device." ::= { historyControlEntry 1 }Remote Network Monitoring Working Group [Page 19]RFC 1271 Remote Network Monitoring MIB November 1991 historyControlDataSource OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-write STATUS mandatory DESCRIPTION "This object identifies the source of the data for which historical data was collected and placed in a media-specific table on behalf of this historyControlEntry. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in [4,6], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. This object may not be modified if the associated historyControlStatus object is equal to valid(1)." ::= { historyControlEntry 2 } historyControlBucketsRequested OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-write STATUS mandatory DESCRIPTION "The requested number of discrete time intervals over which data is to be saved in the part of the media-specific table associated with this historyControl entry. When this object is created or modified, the probe should set historyControlBucketsGranted as closely to this object as is possible for the particular probe implementation and available resources." DEFVAL { 50 } ::= { historyControlEntry 3 } historyControlBucketsGranted OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "The number of discrete sampling intervals over which data shall be saved in the part ofRemote Network Monitoring Working Group [Page 20]RFC 1271 Remote Network Monitoring MIB November 1991 the media-specific table associated with this historyControl entry. When the associated historyControlBucketsRequested object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular probe implementation and available resources. The probe must not lower this value except as a result of a modification to the associated historyControlBucketsRequested object. There will be times when the actual number of buckets associated with this entry is less than the value of this object. In this case, at the end of each sampling interval, a new bucket will be added to the media-specific table. When the number of buckets reaches the value of this object and a new bucket is to be added to the media-specific table, the oldest bucket associated with this historyControlEntry shall be deleted by the agent so that the new bucket can be added. When the value of this object changes to a value less than the current value, entries are deleted from the media-specific table associated with this historyControlEntry. Enough of the oldest of these entries shall be deleted by the agent so that their number remains less than or equal to the new value of this object. When the value of this object changes to a value greater than the current value, the number of associated media-specific entries may be allowed to grow." ::= { historyControlEntry 4 } historyControlInterval OBJECT-TYPE SYNTAX INTEGER (1..3600) ACCESS read-write STATUS mandatory DESCRIPTION "The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this historyControl entry. This interval can be set to any number of seconds between 1 andRemote Network Monitoring Working Group [Page 21]RFC 1271 Remote Network Monitoring MIB November 1991 3600 (1 hour). Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and set the historyControlInterval object to a value less than this interval. This is typically most important for the 'octets' counter in any media-specific table. For example, on an Ethernet network, the etherHistoryOctets counter could overflow in about one hour at the Ethernet's maximum utilization. This object may not be modified if the associated historyControlStatus object is equal to valid(1)." DEFVAL { 1800 } ::= { historyControlEntry 5 } historyControlOwner OBJECT-TYPE SYNTAX OwnerString ACCESS read-write STATUS mandatory DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::= { historyControlEntry 6 } historyControlStatus OBJECT-TYPE SYNTAX EntryStatus ACCESS read-write STATUS mandatory DESCRIPTION "The status of this historyControl entry. Each instance of the media-specific table associated with this historyControlEntry will be deleted by the agent if this historyControlEntry is not equal to valid(1)." ::= { historyControlEntry 7 } -- Ether History table etherHistoryTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherHistoryEntryRemote Network Monitoring Working Group [Page 22]RFC 1271 Remote Network Monitoring MIB November 1991 ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of Ethernet history entries." ::= { history 2 } etherHistoryEntry OBJECT-TYPE SYNTAX EtherHistoryEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An historical sample of Ethernet statistics on a particular Ethernet interface. This sample is associated with the historyControlEntry which set up the parameters for a regular collection of these samples." INDEX { etherHistoryIndex , etherHistorySampleIndex } ::= { etherHistoryTable 1 } EtherHistoryEntry ::= SEQUENCE { etherHistoryIndex INTEGER (1..65535), etherHistorySampleIndex INTEGER, etherHistoryIntervalStart TimeTicks, etherHistoryDropEvents Counter, etherHistoryOctets Counter, etherHistoryPkts Counter,
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -