rfc1066.txt
来自「中、英文RFC文档大全打包下载完全版 .」· 文本 代码 · 共 2,716 行 · 第 1/5 页
TXT
2,716 行
Access: read-write. Status: mandatory.McCloghrie & Rose [Page 39] RFC 1066 MIB August 1988 OBJECT: ------- ipRouteType { ipRouteEntry 8 } Syntax: INTEGER { other(1), -- none of the following invalid(2), -- an invalidated route -- route to directly direct(3), -- connected (sub-)network -- route to a non-local remote(4), -- host/network/sub-network } Definition: The type of route. Access: read-write. Status: mandatory. OBJECT: ------- ipRouteProto { ipRouteEntry 9 } Syntax: INTEGER { other(1), -- none of the following -- non-protocol information, -- e.g., manually configured local(2), -- entries -- set via a network management netmgmt(3), -- protocol -- obtained via ICMP, icmp(4), -- e.g., Redirect -- the remaining values are -- all gateway routing protocols egp(5),McCloghrie & Rose [Page 40] RFC 1066 MIB August 1988 ggp(6), hello(7), rip(8), is-is(9), es-is(10), ciscoIgrp(11), bbnSpfIgp(12), oigp(13) } Definition: The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols. Access: read-only. Status: mandatory. OBJECT: ------- ipRouteAge { ipRouteEntry 10 } Syntax: INTEGER Definition: The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of "too old" can be implied except through knowledge of the routing protocol by which the route was learned. Access: read-write. Status: mandatory.McCloghrie & Rose [Page 41] RFC 1066 MIB August 19885.5. The ICMP Group Implementation of the ICMP group is mandatory for all systems. The ICMP group contains the ICMP input and output statistics. Note that individual counters for ICMP message (sub-)codes have been omitted from this (version of the) MIB for simplicity. OBJECT: ------- icmpInMsgs { icmp 1 } Syntax: Counter Definition: The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors. Access: read-only. Status: mandatory. OBJECT: ------- icmpInErrors { icmp 2 } Syntax: Counter Definition: The number of ICMP messages which the entity received but determined as having errors (bad ICMP checksums, bad length, etc.). Access: read-only. Status: mandatory.McCloghrie & Rose [Page 42] RFC 1066 MIB August 1988 OBJECT: ------- icmpInDestUnreachs { icmp 3 } Syntax: Counter Definition: The number of ICMP Destination Unreachable messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpInTimeExcds { icmp 4 } Syntax: Counter Definition: The number of ICMP Time Exceeded messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpInParmProbs { icmp 5 } Syntax: Counter Definition: The number of ICMP Parameter Problem messages received. Access: read-only.McCloghrie & Rose [Page 43] RFC 1066 MIB August 1988 Status: mandatory. OBJECT: ------- icmpInSrcQuenchs { icmp 6 } Syntax: Counter Definition: The number of ICMP Source Quench messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpInRedirects { icmp 7 } Syntax: Counter Definition: The number of ICMP Redirect messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpInEchos { icmp 8 } Syntax: Counter Definition: The number of ICMP Echo (request) messages received.McCloghrie & Rose [Page 44] RFC 1066 MIB August 1988 Access: read-only. Status: mandatory. OBJECT: ------- icmpInEchoReps { icmp 9 } Syntax: Counter Definition: The number of ICMP Echo Reply messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpInTimestamps { icmp 10 } Syntax: Counter Definition: The number of ICMP Timestamp (request) messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpInTimestampReps { icmp 11 } Syntax: CounterMcCloghrie & Rose [Page 45] RFC 1066 MIB August 1988 Definition: The number of ICMP Timestamp Reply messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpInAddrMasks { icmp 12 } Syntax: Counter Definition: The number of ICMP Address Mask Request messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpInAddrMaskReps { icmp 13 } Syntax: Counter Definition: The number of ICMP Address Mask Reply messages received. Access: read-only. Status: mandatory. OBJECT: ------- icmpOutMsgs { icmp 14 }McCloghrie & Rose [Page 46] RFC 1066 MIB August 1988 Syntax: Counter Definition: The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors. Access: read-only. Status: mandatory. OBJECT: ------- icmpOutErrors { icmp 15 } Syntax: Counter Definition: The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value. Access: read-only. Status: mandatory. OBJECT: ------- icmpOutDestUnreachs { icmp 16 } Syntax: Counter Definition: The number of ICMP Destination Unreachable messages sent.McCloghrie & Rose [Page 47] RFC 1066 MIB August 1988 Access: read-only. Status: mandatory. OBJECT: ------- icmpOutTimeExcds { icmp 17 } Syntax: Counter Definition: The number of ICMP Time Exceeded messages sent. Access: read-only. Status: mandatory. OBJECT: ------- icmpOutParmProbs { icmp 18 } Syntax: Counter Definition: The number of ICMP Parameter Problem messages sent. Access: read-only. Status: mandatory. OBJECT: ------- icmpOutSrcQuenchs { icmp 19 } Syntax: CounterMcCloghrie & Rose [Page 48] RFC 1066 MIB August 1988 Definition: The number of ICMP Source Quench messages sent. Access: read-only. Status: mandatory. OBJECT: ------- icmpOutRedirects { icmp 20 } Syntax: Counter Definition: The number of ICMP Redirect messages sent. Access: read-only⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?