RFC2096 日本語訳
2096 IP Forwarding Table MIB. F. Baker. January 1997. (Format: TXT=35930 bytes) (Obsoletes RFC1354) (Obsoleted by RFC4292) (Status: PROPOSED STANDARD)
プログラムでの自動翻訳です。
RFC一覧
英語原文
Network Working Group F. Baker Request for Comments: 2096 Cisco Systems Obsoletes: 1354 January 1997 Category: Standards Track
Network Working Group F. Baker Request for Comments: 2096 Cisco Systems Obsoletes: 1354 January 1997 Category: Standards Track
IP Forwarding Table MIB
IP Forwarding Table MIB
Status of this Memo
Status of this Memo
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Table of Contents
Table of Contents
1. Introduction .......................................... 1 2. The SNMP Network Management Framework ................. 2 2.1 Object Definitions ................................... 2 3. Overview .............................................. 2 4. Definitions ........................................... 3 5. Acknowledgements ...................................... 20 6. References ............................................ 20 7. Security Considerations ............................... 21 8. Author's Address ...................................... 21
1. Introduction .......................................... 1 2. The SNMP Network Management Framework ................. 2 2.1 Object Definitions ................................... 2 3. Overview .............................................. 2 4. Definitions ........................................... 3 5. Acknowledgements ...................................... 20 6. References ............................................ 20 7. Security Considerations ............................... 21 8. Author's Address ...................................... 21
1. Introduction
1. Introduction
This memo defines an update to RFC 1354, "IP Forwarding Table MIB", for Classless Inter-Domain Routing (CIDR). That document was developed by the Router Requirements Working Group as an update to RFC 1213's ipRouteTable, with the display of multiple routes as a primary objective. The significant difference between this MIB and RFC 1354 is the recognition (explicitly discussed but by consensus left to future work) that CIDR routes may have the same network number but different network masks. Note that this MIB obsoletes a number of objects from RFC 1354. The reader should pay careful attention to the STATUS field.
This memo defines an update to RFC 1354, "IP Forwarding Table MIB", for Classless Inter-Domain Routing (CIDR). That document was developed by the Router Requirements Working Group as an update to RFC 1213's ipRouteTable, with the display of multiple routes as a primary objective. The significant difference between this MIB and RFC 1354 is the recognition (explicitly discussed but by consensus left to future work) that CIDR routes may have the same network number but different network masks. Note that this MIB obsoletes a number of objects from RFC 1354. The reader should pay careful attention to the STATUS field.
Baker Standards Track [Page 1] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 1] RFC 2096 IP Forwarding Table MIB January 1997
2. The SNMP Network Management Framework
2. The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of three major components. They are:
The SNMP Network Management Framework presently consists of three major components. They are:
o the SMI, described in RFC 1902 [1], - the mechanisms used
for describing and naming objects for the purpose of
management.
o the SMI, described in RFC 1902 [1], - the mechanisms used for describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [2], - the core set of
managed objects for the Internet suite of protocols.
o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects for the Internet suite of protocols.
o the protocol, RFC 1157 [6] and/or RFC 1905 [4], - the
protocol for accessing managed information.
o the protocol, RFC 1157 [6] and/or RFC 1905 [4], - the protocol for accessing managed information.
Textual conventions are defined in RFC 1903 [3], and conformance statements are defined in RFC 1904 [5].
Textual conventions are defined in RFC 1903 [3], and conformance statements are defined in RFC 1904 [5].
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
2.1. Object Definitions
2.1. Object Definitions
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type.
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type.
3. Overview
3. Overview
The MIB consists of two tables and two global objects.
The MIB consists of two tables and two global objects.
(1) The object ipForwardNumber indicates the number of
current routes. This is primarily to avoid having to
read the table in order to determine this number.
(1) The object ipForwardNumber indicates the number of current routes. This is primarily to avoid having to read the table in order to determine this number.
(2) The ipForwardTable updates the RFC 1213 ipRouteTable to
display multipath IP Routes. This is in turn obsoleted
by the ipCidrRouteTable.
(2) The ipForwardTable updates the RFC 1213 ipRouteTable to display multipath IP Routes. This is in turn obsoleted by the ipCidrRouteTable.
(3) The ipCidrRouteTable updates the RFC 1213 ipRouteTable to
display multipath IP Routes having the same network
number but differing network masks.
(3) The ipCidrRouteTable updates the RFC 1213 ipRouteTable to display multipath IP Routes having the same network number but differing network masks.
Baker Standards Track [Page 2] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 2] RFC 2096 IP Forwarding Table MIB January 1997
4. Definitions
4. Definitions
IP-FORWARD-MIB DEFINITIONS ::= BEGIN
IP-FORWARD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Integer32, Gauge32
FROM SNMPv2-SMI
RowStatus
FROM SNMPv2-TC
ip
FROM RFC1213-MIB
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF;
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Integer32, Gauge32 FROM SNMPv2-SMI RowStatus FROM SNMPv2-TC ip FROM RFC1213-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
ipForward MODULE-IDENTITY
LAST-UPDATED "9609190000Z" -- Thu Sep 26 16:34:47 PDT 1996
ORGANIZATION "IETF OSPF Working Group"
CONTACT-INFO
" Fred Baker
Postal: Cisco Systems
519 Lado Drive
Santa Barbara, California 93111
ipForward MODULE-IDENTITY LAST-UPDATED "9609190000Z" -- Thu Sep 26 16:34:47 PDT 1996 ORGANIZATION "IETF OSPF Working Group" CONTACT-INFO " Fred Baker Postal: Cisco Systems 519 Lado Drive Santa Barbara, California 93111
Phone: +1 805 681 0115
Email: fred@cisco.com
"
DESCRIPTION
"The MIB module for the display of CIDR multipath IP Routes."
REVISION "9609190000Z"
DESCRIPTION
"Revisions made by the OSPF WG."
::= { ip 24 }
Phone: +1 805 681 0115 Email: fred@cisco.com " DESCRIPTION "The MIB module for the display of CIDR multipath IP Routes." REVISION "9609190000Z" DESCRIPTION "Revisions made by the OSPF WG." ::= { ip 24 }
ipCidrRouteNumber OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of current ipCidrRouteTable entries
that are not invalid."
::= { ipForward 3 }
ipCidrRouteNumber OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of current ipCidrRouteTable entries that are not invalid." ::= { ipForward 3 }
-- IP CIDR Route Table
-- IP CIDR Route Table
-- The IP CIDR Route Table obsoletes and replaces the ipRoute -- Table current in MIB-I and MIB-II and the IP Forwarding Table. -- It adds knowledge of the autonomous system of the next hop, -- multiple next hops, and policy routing, and Classless
-- The IP CIDR Route Table obsoletes and replaces the ipRoute -- Table current in MIB-I and MIB-II and the IP Forwarding Table. -- It adds knowledge of the autonomous system of the next hop, -- multiple next hops, and policy routing, and Classless
Baker Standards Track [Page 3] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 3] RFC 2096 IP Forwarding Table MIB January 1997
-- Inter-Domain Routing.
-- Inter-Domain Routing.
ipCidrRouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpCidrRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This entity's IP Routing table."
REFERENCE
"RFC 1213 Section 6.6, The IP Group"
::= { ipForward 4 }
ipCidrRouteTable OBJECT-TYPE SYNTAX SEQUENCE OF IpCidrRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entity's IP Routing table." REFERENCE "RFC 1213 Section 6.6, The IP Group" ::= { ipForward 4 }
ipCidrRouteEntry OBJECT-TYPE
SYNTAX IpCidrRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A particular route to a particular destina-
tion, under a particular policy."
INDEX {
ipCidrRouteDest,
ipCidrRouteMask,
ipCidrRouteTos,
ipCidrRouteNextHop
}
::= { ipCidrRouteTable 1 }
ipCidrRouteEntry OBJECT-TYPE SYNTAX IpCidrRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A particular route to a particular destina- tion, under a particular policy." INDEX { ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, ipCidrRouteNextHop } ::= { ipCidrRouteTable 1 }
IpCidrRouteEntry ::=
SEQUENCE {
ipCidrRouteDest
IpAddress,
ipCidrRouteMask
IpAddress,
ipCidrRouteTos
Integer32,
ipCidrRouteNextHop
IpAddress,
ipCidrRouteIfIndex
Integer32,
ipCidrRouteType
INTEGER,
ipCidrRouteProto
INTEGER,
ipCidrRouteAge
Integer32,
ipCidrRouteInfo
OBJECT IDENTIFIER,
ipCidrRouteNextHopAS
IpCidrRouteEntry ::= SEQUENCE { ipCidrRouteDest IpAddress, ipCidrRouteMask IpAddress, ipCidrRouteTos Integer32, ipCidrRouteNextHop IpAddress, ipCidrRouteIfIndex Integer32, ipCidrRouteType INTEGER, ipCidrRouteProto INTEGER, ipCidrRouteAge Integer32, ipCidrRouteInfo OBJECT IDENTIFIER, ipCidrRouteNextHopAS
Baker Standards Track [Page 4] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 4] RFC 2096 IP Forwarding Table MIB January 1997
Integer32,
ipCidrRouteMetric1
Integer32,
ipCidrRouteMetric2
Integer32,
ipCidrRouteMetric3
Integer32,
ipCidrRouteMetric4
Integer32,
ipCidrRouteMetric5
Integer32,
ipCidrRouteStatus
RowStatus
}
Integer32, ipCidrRouteMetric1 Integer32, ipCidrRouteMetric2 Integer32, ipCidrRouteMetric3 Integer32, ipCidrRouteMetric4 Integer32, ipCidrRouteMetric5 Integer32, ipCidrRouteStatus RowStatus }
ipCidrRouteDest OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The destination IP address of this route.
ipCidrRouteDest OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The destination IP address of this route.
This object may not take a Multicast (Class D)
address value.
This object may not take a Multicast (Class D) address value.
Any assignment (implicit or otherwise) of an
instance of this object to a value x must be
rejected if the bitwise logical-AND of x with
the value of the corresponding instance of the
ipCidrRouteMask object is not equal to x."
::= { ipCidrRouteEntry 1 }
Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipCidrRouteMask object is not equal to x." ::= { ipCidrRouteEntry 1 }
ipCidrRouteMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicate the mask to be logical-ANDed with the
destination address before being compared to
the value in the ipCidrRouteDest field. For
those systems that do not support arbitrary
subnet masks, an agent constructs the value of
the ipCidrRouteMask by reference to the IP Ad-
dress Class.
ipCidrRouteMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipCidrRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipCidrRouteMask by reference to the IP Ad- dress Class.
Any assignment (implicit or otherwise) of an
instance of this object to a value x must be
rejected if the bitwise logical-AND of x with
Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with
Baker Standards Track [Page 5] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 5] RFC 2096 IP Forwarding Table MIB January 1997
the value of the corresponding instance of the
ipCidrRouteDest object is not equal to ipCidrRoute-
Dest."
::= { ipCidrRouteEntry 2 }
the value of the corresponding instance of the ipCidrRouteDest object is not equal to ipCidrRoute- Dest." ::= { ipCidrRouteEntry 2 }
-- The following convention is included for specification -- of TOS Field contents. At this time, the Host Requirements -- and the Router Requirements documents disagree on the width -- of the TOS field. This mapping describes the Router -- Requirements mapping, and leaves room to widen the TOS field -- without impact to fielded systems.
-- The following convention is included for specification -- of TOS Field contents. At this time, the Host Requirements -- and the Router Requirements documents disagree on the width -- of the TOS field. This mapping describes the Router -- Requirements mapping, and leaves room to widen the TOS field -- without impact to fielded systems.
ipCidrRouteTos OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The policy specifier is the IP TOS Field. The encoding
of IP TOS is as specified by the following convention.
Zero indicates the default path if no more specific
policy applies.
ipCidrRouteTos OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies.
+-----+-----+-----+-----+-----+-----+-----+-----+
| | | |
| PRECEDENCE | TYPE OF SERVICE | 0 |
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+
+-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+
IP TOS IP TOS
Field Policy Field Policy
Contents Code Contents Code
0 0 0 0 ==> 0 0 0 0 1 ==> 2
0 0 1 0 ==> 4 0 0 1 1 ==> 6
0 1 0 0 ==> 8 0 1 0 1 ==> 10
0 1 1 0 ==> 12 0 1 1 1 ==> 14
1 0 0 0 ==> 16 1 0 0 1 ==> 18
1 0 1 0 ==> 20 1 0 1 1 ==> 22
1 1 0 0 ==> 24 1 1 0 1 ==> 26
1 1 1 0 ==> 28 1 1 1 1 ==> 30"
::= { ipCidrRouteEntry 3 }
IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 0 0 1 0 ==> 4 0 0 1 1 ==> 6 0 1 0 0 ==> 8 0 1 0 1 ==> 10 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1 1 1 0 ==> 28 1 1 1 1 ==> 30" ::= { ipCidrRouteEntry 3 }
ipCidrRouteNextHop OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"On remote routes, the address of the next sys-
tem en route; Otherwise, 0.0.0.0."
ipCidrRouteNextHop OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "On remote routes, the address of the next sys- tem en route; Otherwise, 0.0.0.0."
Baker Standards Track [Page 6] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 6] RFC 2096 IP Forwarding Table MIB January 1997
::= { ipCidrRouteEntry 4 }
::= { ipCidrRouteEntry 4 }
ipCidrRouteIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The ifIndex value which identifies the local
interface through which the next hop of this
route should be reached."
DEFVAL { 0 }
::= { ipCidrRouteEntry 5 }
ipCidrRouteIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The ifIndex value which identifies the local interface through which the next hop of this route should be reached." DEFVAL { 0 } ::= { ipCidrRouteEntry 5 }
ipCidrRouteType OBJECT-TYPE
SYNTAX INTEGER {
other (1), -- not specified by this MIB
reject (2), -- route which discards traffic
local (3), -- local interface
remote (4) -- remote destination
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of route. Note that local(3) refers
to a route for which the next hop is the final
destination; remote(4) refers to a route for
which the next hop is not the final destina-
tion.
ipCidrRouteType OBJECT-TYPE SYNTAX INTEGER { other (1), -- not specified by this MIB reject (2), -- route which discards traffic local (3), -- local interface remote (4) -- remote destination } MAX-ACCESS read-create STATUS current DESCRIPTION "The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for which the next hop is not the final destina- tion.
Routes which do not result in traffic forwarding or
rejection should not be displayed even if the
implementation keeps them stored internally.
Routes which do not result in traffic forwarding or rejection should not be displayed even if the implementation keeps them stored internally.
reject (2) refers to a route which, if matched, discards
the message as unreachable. This is used in some
protocols as a means of correctly aggregating routes."
::= { ipCidrRouteEntry 6 }
reject (2) refers to a route which, if matched, discards the message as unreachable. This is used in some protocols as a means of correctly aggregating routes." ::= { ipCidrRouteEntry 6 }
ipCidrRouteProto OBJECT-TYPE
SYNTAX INTEGER {
other (1), -- not specified
local (2), -- local interface
netmgmt (3), -- static route
icmp (4), -- result of ICMP Redirect
ipCidrRouteProto OBJECT-TYPE SYNTAX INTEGER { other (1), -- not specified local (2), -- local interface netmgmt (3), -- static route icmp (4), -- result of ICMP Redirect
-- the following are all dynamic
-- routing protocols
-- the following are all dynamic -- routing protocols
Baker Standards Track [Page 7] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 7] RFC 2096 IP Forwarding Table MIB January 1997
egp (5), -- Exterior Gateway Protocol
ggp (6), -- Gateway-Gateway Protocol
hello (7), -- FuzzBall HelloSpeak
rip (8), -- Berkeley RIP or RIP-II
isIs (9), -- Dual IS-IS
esIs (10), -- ISO 9542
ciscoIgrp (11), -- Cisco IGRP
bbnSpfIgp (12), -- BBN SPF IGP
ospf (13), -- Open Shortest Path First
bgp (14), -- Border Gateway Protocol
idpr (15), -- InterDomain Policy Routing
ciscoEigrp (16) -- Cisco EIGRP
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The routing mechanism via which this route was
learned. Inclusion of values for gateway rout-
ing protocols is not intended to imply that
hosts should support those protocols."
::= { ipCidrRouteEntry 7 }
egp (5), -- Exterior Gateway Protocol ggp (6), -- Gateway-Gateway Protocol hello (7), -- FuzzBall HelloSpeak rip (8), -- Berkeley RIP or RIP-II isIs (9), -- Dual IS-IS esIs (10), -- ISO 9542 ciscoIgrp (11), -- Cisco IGRP bbnSpfIgp (12), -- BBN SPF IGP ospf (13), -- Open Shortest Path First bgp (14), -- Border Gateway Protocol idpr (15), -- InterDomain Policy Routing ciscoEigrp (16) -- Cisco EIGRP } MAX-ACCESS read-only STATUS current DESCRIPTION "The routing mechanism via which this route was learned. Inclusion of values for gateway rout- ing protocols is not intended to imply that hosts should support those protocols." ::= { ipCidrRouteEntry 7 }
ipCidrRouteAge OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
DEFVAL { 0 }
::= { ipCidrRouteEntry 8 }
ipCidrRouteAge OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "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." DEFVAL { 0 } ::= { ipCidrRouteEntry 8 }
ipCidrRouteInfo OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A reference to MIB definitions specific to the
particular routing protocol which is responsi-
ble for this route, as determined by the value
specified in the route's ipCidrRouteProto value.
If this information is not present, its value
should be set to the OBJECT IDENTIFIER { 0 0 },
which is a syntactically valid object identif-
ipCidrRouteInfo OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "A reference to MIB definitions specific to the particular routing protocol which is responsi- ble for this route, as determined by the value specified in the route's ipCidrRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identif-
Baker Standards Track [Page 8] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 8] RFC 2096 IP Forwarding Table MIB January 1997
ier, and any implementation conforming to ASN.1
and the Basic Encoding Rules must be able to
generate and recognize this value."
::= { ipCidrRouteEntry 9 }
ier, and any implementation conforming to ASN.1 and the Basic Encoding Rules must be able to generate and recognize this value." ::= { ipCidrRouteEntry 9 }
ipCidrRouteNextHopAS OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Autonomous System Number of the Next Hop.
The semantics of this object are determined by
the routing-protocol specified in the route's
ipCidrRouteProto value. When this object is
unknown or not relevant its value should be set
to zero."
DEFVAL { 0 }
::= { ipCidrRouteEntry 10 }
ipCidrRouteNextHopAS OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The Autonomous System Number of the Next Hop. The semantics of this object are determined by the routing-protocol specified in the route's ipCidrRouteProto value. When this object is unknown or not relevant its value should be set to zero." DEFVAL { 0 } ::= { ipCidrRouteEntry 10 }
ipCidrRouteMetric1 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The primary routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipCidrRouteProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipCidrRouteEntry 11 }
ipCidrRouteMetric1 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { ipCidrRouteEntry 11 }
ipCidrRouteMetric2 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An alternate routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipCidrRouteProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipCidrRouteEntry 12 }
ipCidrRouteMetric2 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { ipCidrRouteEntry 12 }
ipCidrRouteMetric3 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
ipCidrRouteMetric3 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create
Baker Standards Track [Page 9] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 9] RFC 2096 IP Forwarding Table MIB January 1997
STATUS current
DESCRIPTION
"An alternate routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipCidrRouteProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipCidrRouteEntry 13 }
STATUS current DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { ipCidrRouteEntry 13 }
ipCidrRouteMetric4 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An alternate routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipCidrRouteProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipCidrRouteEntry 14 }
ipCidrRouteMetric4 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { ipCidrRouteEntry 14 }
ipCidrRouteMetric5 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An alternate routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipCidrRouteProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipCidrRouteEntry 15 }
ipCidrRouteMetric5 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { ipCidrRouteEntry 15 }
ipCidrRouteStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The row status variable, used according to
row installation and removal conventions."
::= { ipCidrRouteEntry 16 }
ipCidrRouteStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The row status variable, used according to row installation and removal conventions." ::= { ipCidrRouteEntry 16 }
-- conformance information
-- conformance information
ipForwardConformance OBJECT IDENTIFIER ::= { ipForward 5 }
ipForwardConformance OBJECT IDENTIFIER ::= { ipForward 5 }
Baker Standards Track [Page 10] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 10] RFC 2096 IP Forwarding Table MIB January 1997
ipForwardGroups OBJECT IDENTIFIER ::= { ipForwardConformance 1 }
ipForwardCompliances OBJECT IDENTIFIER ::= { ipForwardConformance 2 }
ipForwardGroups OBJECT IDENTIFIER ::= { ipForwardConformance 1 } ipForwardCompliances OBJECT IDENTIFIER ::= { ipForwardConformance 2 }
-- compliance statements
-- compliance statements
ipForwardCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities
which implement the ipForward MIB."
ipForwardCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMPv2 entities which implement the ipForward MIB."
MODULE -- this module
MANDATORY-GROUPS { ipForwardCidrRouteGroup }
MODULE -- this module MANDATORY-GROUPS { ipForwardCidrRouteGroup }
::= { ipForwardCompliances 1 }
::= { ipForwardCompliances 1 }
-- units of conformance
-- units of conformance
ipForwardCidrRouteGroup OBJECT-GROUP
OBJECTS { ipCidrRouteNumber,
ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos,
ipCidrRouteNextHop, ipCidrRouteIfIndex, ipCidrRouteType,
ipCidrRouteProto, ipCidrRouteAge, ipCidrRouteInfo,
ipCidrRouteNextHopAS, ipCidrRouteMetric1,
ipCidrRouteMetric2, ipCidrRouteMetric3,
ipCidrRouteMetric4, ipCidrRouteMetric5, ipCidrRouteStatus
}
STATUS current
DESCRIPTION
"The CIDR Route Table."
::= { ipForwardGroups 3 }
ipForwardCidrRouteGroup OBJECT-GROUP OBJECTS { ipCidrRouteNumber, ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, ipCidrRouteNextHop, ipCidrRouteIfIndex, ipCidrRouteType, ipCidrRouteProto, ipCidrRouteAge, ipCidrRouteInfo, ipCidrRouteNextHopAS, ipCidrRouteMetric1, ipCidrRouteMetric2, ipCidrRouteMetric3, ipCidrRouteMetric4, ipCidrRouteMetric5, ipCidrRouteStatus } STATUS current DESCRIPTION "The CIDR Route Table." ::= { ipForwardGroups 3 }
-- Obsoleted Definitions - Objects
-- Obsoleted Definitions - Objects
ipForwardNumber OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The number of current ipForwardTable entries
that are not invalid."
::= { ipForward 1 }
ipForwardNumber OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The number of current ipForwardTable entries that are not invalid." ::= { ipForward 1 }
-- IP Forwarding Table
-- IP Forwarding Table
-- The IP Forwarding Table obsoletes and replaces the ipRoute -- Table current in MIB-I and MIB-II. It adds knowledge of -- the autonomous system of the next hop, multiple next hop
-- The IP Forwarding Table obsoletes and replaces the ipRoute -- Table current in MIB-I and MIB-II. It adds knowledge of -- the autonomous system of the next hop, multiple next hop
Baker Standards Track [Page 11] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 11] RFC 2096 IP Forwarding Table MIB January 1997
-- support, and policy routing support.
-- support, and policy routing support.
ipForwardTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpForwardEntry
MAX-ACCESS not-accessible
STATUS obsolete
DESCRIPTION
"This entity's IP Routing table."
REFERENCE
"RFC 1213 Section 6.6, The IP Group"
::= { ipForward 2 }
ipForwardTable OBJECT-TYPE SYNTAX SEQUENCE OF IpForwardEntry MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION "This entity's IP Routing table." REFERENCE "RFC 1213 Section 6.6, The IP Group" ::= { ipForward 2 }
ipForwardEntry OBJECT-TYPE
SYNTAX IpForwardEntry
MAX-ACCESS not-accessible
STATUS obsolete
DESCRIPTION
"A particular route to a particular destina-
tion, under a particular policy."
INDEX {
ipForwardDest,
ipForwardProto,
ipForwardPolicy,
ipForwardNextHop
}
::= { ipForwardTable 1 }
ipForwardEntry OBJECT-TYPE SYNTAX IpForwardEntry MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION "A particular route to a particular destina- tion, under a particular policy." INDEX { ipForwardDest, ipForwardProto, ipForwardPolicy, ipForwardNextHop } ::= { ipForwardTable 1 }
IpForwardEntry ::=
SEQUENCE {
ipForwardDest
IpAddress,
ipForwardMask
IpAddress,
ipForwardPolicy
Integer32,
ipForwardNextHop
IpAddress,
ipForwardIfIndex
Integer32,
ipForwardType
INTEGER,
ipForwardProto
INTEGER,
ipForwardAge
Integer32,
ipForwardInfo
OBJECT IDENTIFIER,
ipForwardNextHopAS
IpForwardEntry ::= SEQUENCE { ipForwardDest IpAddress, ipForwardMask IpAddress, ipForwardPolicy Integer32, ipForwardNextHop IpAddress, ipForwardIfIndex Integer32, ipForwardType INTEGER, ipForwardProto INTEGER, ipForwardAge Integer32, ipForwardInfo OBJECT IDENTIFIER, ipForwardNextHopAS
Baker Standards Track [Page 12] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 12] RFC 2096 IP Forwarding Table MIB January 1997
Integer32,
ipForwardMetric1
Integer32,
ipForwardMetric2
Integer32,
ipForwardMetric3
Integer32,
ipForwardMetric4
Integer32,
ipForwardMetric5
Integer32
}
Integer32, ipForwardMetric1 Integer32, ipForwardMetric2 Integer32, ipForwardMetric3 Integer32, ipForwardMetric4 Integer32, ipForwardMetric5 Integer32 }
ipForwardDest OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The destination IP address of this route. An
entry with a value of 0.0.0.0 is considered a
default route.
ipForwardDest OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route.
This object may not take a Multicast (Class D)
address value.
This object may not take a Multicast (Class D) address value.
Any assignment (implicit or otherwise) of an
instance of this object to a value x must be
rejected if the bitwise logical-AND of x with
the value of the corresponding instance of the
ipForwardMask object is not equal to x."
::= { ipForwardEntry 1 }
Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipForwardMask object is not equal to x." ::= { ipForwardEntry 1 }
ipForwardMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"Indicate the mask to be logical-ANDed with the
destination address before being compared to
the value in the ipForwardDest field. For
those systems that do not support arbitrary
subnet masks, an agent constructs the value of
the ipForwardMask by reference to the IP Ad-
dress Class.
ipForwardMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS obsolete DESCRIPTION "Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipForwardDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipForwardMask by reference to the IP Ad- dress Class.
Any assignment (implicit or otherwise) of an
instance of this object to a value x must be
rejected if the bitwise logical-AND of x with
Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with
Baker Standards Track [Page 13] RFC 2096 IP Forwarding Table MIB January 1997
Baker Standards Track [Page 13] RFC 2096 IP Forwarding Table MIB January 1997
the value of the corresponding instance of the
ipForwardDest object is not equal to ipForward-
Dest."
DEFVAL { '00000000'h } -- 0.0.0.0
::= { ipForwardEntry 2 }
the value of the corresponding instance of the ipForwardDest object is not equal to ipForward- Dest." DEFVAL { '00000000'h } -- 0.0.0.0 ::= { ipForwardEntry 2 }
-- The following convention is included for specification -- of TOS Field contents. At this time, the Host Requirements -- and the Router Requirements documents disagree on the width -- of the TOS field. This mapping describes the Router -- Requirements mapping, and leaves room to widen the TOS field -- without impact to fielded systems.
-- The following convention is included for specification -- of TOS Field contents. At this time, the Host Requirements -- and the Router Requirements documents disagree on the width -- of the TOS field. This mapping describes the Router -- Requirements mapping, and leaves room to widen the TOS field -- without impact to fielded systems.
ipForwardPolicy OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The general set of conditions that would cause
the selection of one multipath route (set of
next hops for a given destination) is referred
to as 'policy'.
ipForwardPolicy OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The general set of conditions that would cause the selection of one multipath route (set of next hops for a given destination) is referred to as 'policy'.
Unless the mechanism indicated by ipForwardPro-
to specifies otherwise, the policy specifier is
the IP TOS Field. The encoding of IP TOS is as
specified by the following convention. Zero
indicates the default path if no more specific
policy applies.
Unless the mechanism indicated by ipForwardPro- to specifies otherwise, the policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies.
+-----+-----+-----+-----+-----+-----+-----+-----+
| | | |
| PRECEDENCE | TYPE OF SERVICE | 0 |
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+
+-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+
IP TOS IP TOS
Field Policy Field Policy
Contents Code Contents Code
0 0 0 0 ==> 0 0 0 0 1 ==> 2
0 0 1 0 ==> 4 0 0 1 1 ==> 6
0 1 0 0 ==> 8 0 1 0 1 ==> 10
0 1 1 0 ==> 12 0 1 1 1 ==> 14
1 0 0 0 ==> 16 1 0 0 1 ==> 18
1 0 1 0 ==> 20 1 0 1 1 ==> 22
1 1 0 0 ==> 24 1 1 0 1 ==> 26
1 1 1 0 ==> 28 1 1 1 1 ==> 30
IP TOS IP TOS分野方針分野、方針内容が>18>16>14>12>10コンテンツコード0 0 0 0=>0 0 0 0 1=>2 0 0 1 0=>4 0 0 1 1=>6 0 1 0 0=>8 0 1 0 1=0 1 1 0=0 1 1 1=1 0 0 0=1 0 0 1=1 0 1 0=>20をコード化する、>28>26>24>22 1 0 1 1=1 1 0 0=1 1 0 1=1 1 1 0=1 1 1 1=>30
Baker Standards Track [Page 14] RFC 2096 IP Forwarding Table MIB January 1997
1997年1月にテーブルMIBを進めるベイカー標準化過程[14ページ]RFC2096IP
Protocols defining 'policy' otherwise must ei-
ther define a set of values which are valid for
this object or must implement an integer-
instanced policy table for which this object's
value acts as an index."
::= { ipForwardEntry 3 }
「プロトコル、'方針を定義して、'そうでなければ、必須ei- therは1セットのこの物に、有効な値を定義しなければならないか、またはこの物の値がインデックスとして機能する整数の例証された方針テーブルを実行しなければなりません」。 ::= ipForwardEntry3
ipForwardNextHop OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"On remote routes, the address of the next sys-
tem en route; Otherwise, 0.0.0.0."
::= { ipForwardEntry 4 }
ipForwardNextHop OBJECT-TYPE SYNTAX IpAddressマックス-ACCESS書き込み禁止STATUSは「リモートルート、途中次のsys- temのアドレス」で記述を時代遅れにします。 「そうでなければ、0.0 .0 .0インチ。 ::= ipForwardEntry4
ipForwardIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"The ifIndex value which identifies the local
interface through which the next hop of this
route should be reached."
DEFVAL { 0 }
::= { ipForwardEntry 5 }
ipForwardIfIndex OBJECT-TYPE SYNTAX Integer32マックス-ACCESSはSTATUSの時代遅れの記述を読書して作成します。「このルートの次のホップに達するべきである局所界面を特定するifIndex値。」 DEFVAL0:、:= ipForwardEntry5
ipForwardType OBJECT-TYPE
SYNTAX INTEGER {
other (1), -- not specified by this MIB
invalid (2), -- logically deleted
local (3), -- local interface
remote (4) -- remote destination
}
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"The type of route. Note that local(3) refers
to a route for which the next hop is the final
destination; remote(4) refers to a route for
which the next hop is not the final destina-
tion.
ipForwardType OBJECT-TYPE SYNTAX INTEGERの他の(1)の、そして、遠く離れたこのMIB病人(2)--論理的に削除されたローカル(3)--局所界面リモートな(4)によって指定されないで、目的地マックス-ACCESSはSTATUSの時代遅れの記述を読書して作成します。「ルートのタイプ。」 地方の(3)が次のホップが最終的な目的地であるルートを示すことに注意してください。 リモート(4)は次のホップが最終的なdestina- tionでないルートを示します。
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding
entry in the ipForwardTable object. That is,
it effectively disassociates the destination
identified with said entry from the route iden-
値の病人(2)にこの物を設定するのにおいて、ipForwardTable物で対応するエントリーを無効にするという効果があります。 事実上、すなわち、それはルートidenから前述のエントリーと同一視された目的地を分離します。
Baker Standards Track [Page 15] RFC 2096 IP Forwarding Table MIB January 1997
1997年1月にテーブルMIBを進めるベイカー標準化過程[15ページ]RFC2096IP
tified with said entry. It is an
implementation-specific matter as to whether
the agent removes an invalidated entry from the
table. Accordingly, management stations must
be prepared to receive tabular information from
agents that corresponds to entries not current-
ly in use. Proper interpretation of such en-
tries requires examination of the relevant ip-
ForwardType object."
DEFVAL { invalid }
::= { ipForwardEntry 6 }
前述のエントリーで、tifiedしました。 それはエージェントがテーブルから無効にされたエントリーを取り除くかどうかに関する実現特有の問題です。 それに従って、使用中の現在のlyではなく、エージェントからのエントリーに対応する表情報を受け取るように管理局を準備しなければなりません。 「そのようなアントライの適切な解釈は関連ip- ForwardType物の試験を必要とします。」 DEFVAL病人:、:= ipForwardEntry6
ipForwardProto OBJECT-TYPE
SYNTAX INTEGER {
other (1), -- not specified
local (2), -- local interface
netmgmt (3), -- static route
icmp (4), -- result of ICMP Redirect
ipForwardProto OBJECT-TYPE SYNTAX INTEGER、他の(1)--指定された地方の(2)(局所界面netmgmt(3))スタティックルートicmp(4)でない--ICMP Redirectの結果
-- the following are all dynamic
-- routing protocols
egp (5), -- Exterior Gateway Protocol
ggp (6), -- Gateway-Gateway Protocol
hello (7), -- FuzzBall HelloSpeak
rip (8), -- Berkeley RIP or RIP-II
is-is (9), -- Dual IS-IS
es-is (10), -- ISO 9542
ciscoIgrp (11), -- Cisco IGRP
bbnSpfIgp (12), -- BBN SPF IGP
ospf (13), -- Open Shortest Path First
bgp (14), -- Border Gateway Protocol
idpr (15) -- InterDomain Policy Routing
}
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The routing mechanism via which this route was
learned. Inclusion of values for gateway rout-
ing protocols is not intended to imply that
hosts should support those protocols."
::= { ipForwardEntry 7 }
-- (7)--FuzzBall HelloSpeak裂け目(8)--こんにちは、プロトコルegp(5)--外のゲートウェイプロトコルggp(6)--ゲートウェイゲートウェイプロトコルバークレーRIPかRIP-IIを発送して、以下がすべてダイナミックである、-、(9)--、二元的である、-、es存在、(10)、--ISO9542ciscoIgrp(11)--コクチマスIGRP bbnSpfIgp(12)--BBN SPF IGP ospf(13)--Shortest Path First bgp(14)--ボーダ・ゲイトウェイ・プロトコルidpr(15)--InterDomain Policyルート設定を開いてください マックス-ACCESS書き込み禁止STATUSは記述を時代遅れにします。「を通したこのルートが学習されたルーティングメカニズム。」 「ゲートウェイがingプロトコルを総崩れにするので、値の包含が、ホストがそれらのプロトコルをサポートするべきであるのを含意することを意図しません。」 ::= ipForwardEntry7
ipForwardAge OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The number of seconds since this route was
ipForwardAge OBJECT-TYPE SYNTAX Integer32のマックス-ACCESSの書き込み禁止のSTATUSの時代遅れの記述は「このルートがそうであった時から秒の数」です。
Baker Standards Track [Page 16] RFC 2096 IP Forwarding Table MIB January 1997
1997年1月にテーブルMIBを進めるベイカー標準化過程[16ページ]RFC2096IP
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."
DEFVAL { 0 }
::= { ipForwardEntry 8 }
アップデートするか、または正しいことを別の方法で決定しています。 「ルートが学習されたルーティング・プロトコルに関する知識以外に、'古過ぎること'の意味論を全く含意できないことに注意してください。」 DEFVAL0:、:= ipForwardEntry8
ipForwardInfo OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"A reference to MIB definitions specific to the
particular routing protocol which is responsi-
ble for this route, as determined by the value
specified in the route's ipForwardProto value.
If this information is not present, its value
should be set to the OBJECT IDENTIFIER { 0 0 },
which is a syntactically valid object identif-
ier, and any implementation conforming to ASN.1
and the Basic Encoding Rules must be able to
generate and recognize this value."
::= { ipForwardEntry 9 }
ipForwardInfo OBJECT-TYPE SYNTAX OBJECT IDENTIFIERマックス-ACCESSは「値で決定するようにこのルートへのresponsi- bleである特定のルーティング・プロトコルに特定のMIB定義の参照はルートのipForwardProto値で指定した」STATUSの時代遅れの記述を読書して作成します。 「この情報が存在していないなら、値がシンタクス上有効な物のidentif- ierであるOBJECT IDENTIFIER0 0に設定されるべきであり、ASN.1とBasic Encoding Rulesに従うどんな実現も、この値を発生して、認識できなければなりません。」 ::= ipForwardEntry9
ipForwardNextHopAS OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"The Autonomous System Number of the Next Hop.
When this is unknown or not relevant to the
protocol indicated by ipForwardProto, zero."
DEFVAL { 0 }
::= { ipForwardEntry 10 }
ipForwardNextHopAS OBJECT-TYPE SYNTAX Integer32マックス-ACCESSは「次の自律システム番号は飛び越す」STATUSの時代遅れの記述を読書して作成します。 「これがipForwardProto、ゼロによって示されたプロトコルに未知である、または関連していないとき。」 DEFVAL0:、:= ipForwardEntry10
ipForwardMetric1 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"The primary routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipForwardProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipForwardEntry 11 }
ipForwardMetric1 OBJECT-TYPE SYNTAX Integer32マックス-ACCESSは「これにおける、メートル法の第一のルーティングは発送する」STATUSの時代遅れの記述を読書して作成します。 これほどメートル法の意味論はルートのipForwardProto値で指定されたルーティング・プロトコルで決定します。 「これほどメートル法であることが、使用されていて、値が-1に設定されるべきであるということでない、」 DEFVAL-1:、:= ipForwardEntry11
Baker Standards Track [Page 17] RFC 2096 IP Forwarding Table MIB January 1997
1997年1月にテーブルMIBを進めるベイカー標準化過程[17ページ]RFC2096IP
ipForwardMetric2 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"An alternate routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipForwardProto value. If this metric is not
used, its value should be set to -1."
ipForwardMetric2 OBJECT-TYPE SYNTAX Integer32マックス-ACCESSは「これにおける、メートル法の迂回中継は発送する」STATUSの時代遅れの記述を読書して作成します。 これほどメートル法の意味論はルートのipForwardProto値で指定されたルーティング・プロトコルで決定します。 「これほどメートル法であることが、使用されていて、値が-1に設定されるべきであるということでない、」
DEFVAL { -1 }
::= { ipForwardEntry 12 }
DEFVAL-1:、:= ipForwardEntry12
ipForwardMetric3 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"An alternate routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipForwardProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipForwardEntry 13 }
ipForwardMetric3 OBJECT-TYPE SYNTAX Integer32マックス-ACCESSは「これにおける、メートル法の迂回中継は発送する」STATUSの時代遅れの記述を読書して作成します。 これほどメートル法の意味論はルートのipForwardProto値で指定されたルーティング・プロトコルで決定します。 「これほどメートル法であることが、使用されていて、値が-1に設定されるべきであるということでない、」 DEFVAL-1:、:= ipForwardEntry13
ipForwardMetric4 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"An alternate routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipForwardProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipForwardEntry 14 }
ipForwardMetric4 OBJECT-TYPE SYNTAX Integer32マックス-ACCESSは「これにおける、メートル法の迂回中継は発送する」STATUSの時代遅れの記述を読書して作成します。 これほどメートル法の意味論はルートのipForwardProto値で指定されたルーティング・プロトコルで決定します。 「これほどメートル法であることが、使用されていて、値が-1に設定されるべきであるということでない、」 DEFVAL-1:、:= ipForwardEntry14
ipForwardMetric5 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS obsolete
DESCRIPTION
"An alternate routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in the route's
ipForwardMetric5 OBJECT-TYPE SYNTAX Integer32マックス-ACCESSは「これにおける、メートル法の迂回中継は発送する」STATUSの時代遅れの記述を読書して作成します。 これほどメートル法の意味論はルートのところで指定されたルーティング・プロトコルで決定します。
Baker Standards Track [Page 18] RFC 2096 IP Forwarding Table MIB January 1997
1997年1月にテーブルMIBを進めるベイカー標準化過程[18ページ]RFC2096IP
ipForwardProto value. If this metric is not
used, its value should be set to -1."
DEFVAL { -1 }
::= { ipForwardEntry 15 }
ipForwardProto値。 「これほどメートル法であることが、使用されていて、値が-1に設定されるべきであるということでない、」 DEFVAL-1:、:= ipForwardEntry15
-- Obsoleted Definitions - Groups -- compliance statements
-- 時代遅れにされたDefinitions--グループ--承諾声明
ipForwardOldCompliance MODULE-COMPLIANCE
STATUS obsolete
DESCRIPTION
"The compliance statement for SNMP entities
which implement the ipForward MIB."
ipForwardOldCompliance MODULE-COMPLIANCE STATUSは記述を時代遅れにします。「ipForward MIBを実行するSNMP実体のための承諾声明。」
MODULE -- this module
MANDATORY-GROUPS { ipForwardMultiPathGroup }
MODULE--このモジュールMANDATORY-GROUPSipForwardMultiPathGroup
::= { ipForwardCompliances 2 }
::= ipForwardCompliances2
ipForwardMultiPathGroup OBJECT-GROUP
OBJECTS { ipForwardNumber,
ipForwardDest, ipForwardMask, ipForwardPolicy,
ipForwardNextHop, ipForwardIfIndex, ipForwardType,
ipForwardProto, ipForwardAge, ipForwardInfo,
ipForwardNextHopAS,
ipForwardMetric1, ipForwardMetric2, ipForwardMetric3,
ipForwardMetric4, ipForwardMetric5
}
STATUS obsolete
DESCRIPTION
"IP Multipath Route Table."
::= { ipForwardGroups 2 }
ipForwardMultiPathGroup OBJECT-GROUP OBJECTS、ipForwardNumber、ipForwardDest、ipForwardMask、ipForwardPolicy、ipForwardNextHop、ipForwardIfIndex、ipForwardType、ipForwardProto、ipForwardAge、ipForwardInfo、ipForwardNextHopAS、ipForwardMetric1、ipForwardMetric2、ipForwardMetric3、ipForwardMetric4、STATUSが時代遅れにするipForwardMetric5、記述「IP多重通路ルートテーブル。」 ::= ipForwardGroups2
END
終わり
Baker Standards Track [Page 19] RFC 2096 IP Forwarding Table MIB January 1997
1997年1月にテーブルMIBを進めるベイカー標準化過程[19ページ]RFC2096IP
5. Acknowledgements
5. 承認
This work was originally performed by the Router Requirements Working Group at the request of the OSPF Working Group. This update was performed under the auspices of the OSPF Working Group. John Moy of Proteon Incorporated is the chair.
この仕事が元々、OSPF作業部会の依頼でRouter Requirements作業部会によって行われました。 このアップデートはOSPF作業部会の前兆で実行されました。 Proteon IncorporatedのジョンMoyはいすです。
6. References
6. 参照
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Structure of Management Information for version 2 of the
Simple Network Management Protocol (SNMPv2)", RFC 1442,
SNMP Research, Inc., Hughes LAN Systems, Dover Beach
Consulting, Inc., Carnegie Mellon University, April 1993.
[1]ケース、J.、McCloghrie、K.、ローズ、M.、およびS.Waldbusser、「Simple Network Managementプロトコル(SNMPv2)のバージョン2のためのManagement情報の構造」、RFC1442、SNMP Research Inc.、ヒューズLAN Systems、ドーヴァービーチConsulting Inc.、カーネギーメロン大学(1993年4月)。
[2] Galvin, J., and K. McCloghrie, "Administrative Model for
version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1445, Trusted Information Systems, Hughes
LAN Systems, April 1993.
[2] ガルビン、J.、およびK.McCloghrie、「Simple Network Managementプロトコル(SNMPv2)のバージョン2のための管理Model」、RFC1445、Trusted情報システム、ヒューズLAN Systems(1993年4月)。
[3] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1448, SNMP Research,
Inc., Hughes LAN Systems, Dover Beach Consulting, Inc.,
Carnegie Mellon University, April 1993.
[3] ケース、J.、McCloghrie(K.、ローズ、M.、およびS.Waldbusser)は「Simple Network Managementプロトコル(SNMPv2)のバージョン2のためにOperationsについて議定書の中で述べます」、RFC1448、SNMP Research Inc.、ヒューズLAN Systems、ドーヴァービーチConsulting Inc.、カーネギーメロン大学、1993年4月。
[4] McCloghrie, K., and M. Rose, "Management Information Base
for Network Management of TCP/IP-based internets - MIB-
II", STD 17, RFC 1213, Hughes LAN Systems, Performance
Systems International, March 1991.
[4]McCloghrie、K.、およびM.ローズ、「TCP/IPベースのインターネットのNetwork Managementのための管理Information基地--MIB II」、STD17、RFC1213、ヒューズLAN Systems、国際パフォーマンスSystems、1991年3月。
[5] Postel, J., "Internet Protocol", STD 5, RFC 791,
USC/Information Sciences Institute, September 1981.
[5] ポステル、J.、「インターネットプロトコル」、STD5、RFC791、科学が1981年9月に設けるUSC/情報。
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Textual Conventions for version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1443, SNMP Research,
Inc., Hughes LAN Systems, Dover Beach Consulting, Inc.,
Carnegie Mellon University, April 1993.
[6]ケース、J.、McCloghrie、K.、ローズ、M.、およびS.Waldbusser、「Simple Network Managementプロトコル(SNMPv2)のバージョン2のための原文のConventions」、RFC1443、SNMP Research Inc.、ヒューズLAN Systems、ドーヴァービーチConsulting Inc.、カーネギーメロン大学(1993年4月)。
[7] Baker, F., "IP Forwarding Table MIB", RFC 1354, July 1992.
[7] ベイカー、F.、「IP推進テーブルMIB」、RFC1354 1992年7月。
Baker Standards Track [Page 20] RFC 2096 IP Forwarding Table MIB January 1997
1997年1月にテーブルMIBを進めるベイカー標準化過程[20ページ]RFC2096IP
7. Security Considerations
7. セキュリティ問題
Security is an objective not in this MIB view.
セキュリティはこのMIB視点でないことで目的です。
8. Author's Address
8. 作者のアドレス
Fred Baker Cisco Systems 519 Lado Drive Santa Barbara, California 93111
フレッドベイカーシスコシステムズ519のLado Driveサンタバーバラ、カリフォルニア 93111
Phone: +1 805 681 0115 EMail: fred@cisco.com
以下に電話をしてください。 +1 0115年の805 681メール: fred@cisco.com
Baker Standards Track [Page 21]
ベイカー標準化過程[21ページ]
一覧
スポンサーリンク
