RFC3970 日本語訳
3970 A Traffic Engineering (TE) MIB. K. Kompella. January 2005. (Format: TXT=88833 bytes) (Status: PROPOSED STANDARD)
プログラムでの自動翻訳です。
英語原文
Network Working Group K. Kompella Request for Comments: 3970 Juniper Networks Category: Standards Track January 2005
Network Working Group K. Kompella Request for Comments: 3970 Juniper Networks Category: Standards Track January 2005
A Traffic Engineering (TE) MIB
A Traffic Engineering (TE) 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.
Copyright Notice
Copyright Notice
Copyright (C) The Internet Society (2005).
Copyright (C) The Internet Society (2005).
Abstract
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths.
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths.
Table of Contents
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Specification of Requirements. . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 2
3. Overview of the MIB Module . . . . . . . . . . . . . . . . . . 2
3.1. Traffic Engineering Information. . . . . . . . . . . . . 3
3.2. Traffic Tunnel Information . . . . . . . . . . . . . . . 3
3.3. Path Information . . . . . . . . . . . . . . . . . . . . 3
3.4. Hop Information. . . . . . . . . . . . . . . . . . . . . 4
3.5. Relationship with Other MIB Modules. . . . . . . . . . . 4
4. Creating, Modifying, and Deleting a TE Tunnel. . . . . . . . . 4
5. MIB Specification. . . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.1. Normative References . . . . . . . . . . . . . . . . . . 40
6.2. Informative References . . . . . . . . . . . . . . . . . 40
7. Security Considerations. . . . . . . . . . . . . . . . . . . . 41
Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . 42
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 43
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 44
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Specification of Requirements. . . . . . . . . . . . . . 2 2. The Internet-Standard Management Framework . . . . . . . . . . 2 3. Overview of the MIB Module . . . . . . . . . . . . . . . . . . 2 3.1. Traffic Engineering Information. . . . . . . . . . . . . 3 3.2. Traffic Tunnel Information . . . . . . . . . . . . . . . 3 3.3. Path Information . . . . . . . . . . . . . . . . . . . . 3 3.4. Hop Information. . . . . . . . . . . . . . . . . . . . . 4 3.5. Relationship with Other MIB Modules. . . . . . . . . . . 4 4. Creating, Modifying, and Deleting a TE Tunnel. . . . . . . . . 4 5. MIB Specification. . . . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.1. Normative References . . . . . . . . . . . . . . . . . . 40 6.2. Informative References . . . . . . . . . . . . . . . . . 40 7. Security Considerations. . . . . . . . . . . . . . . . . . . . 41 Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . 42 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 43 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 44
Kompella Standards Track [Page 1] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 1] RFC 3970 A Traffic Engineering (TE) MIB January 2005
1. Introduction
1. Introduction
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths ([7], [8]). The MIB module defined by this memo allows one to configure TE Tunnels, to assign one or more paths to a Tunnel, and to monitor operational aspects of the Tunnel, such as the number of octets and packets that have passed through the Tunnel.
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths ([7], [8]). The MIB module defined by this memo allows one to configure TE Tunnels, to assign one or more paths to a Tunnel, and to monitor operational aspects of the Tunnel, such as the number of octets and packets that have passed through the Tunnel.
As it stands, this MIB module can only be used to configure or monitor a TE Tunnel at its ingress. The ingress is then expected to use some protocol (such as RSVP-TE) to signal the other routers in the path the information they need to set up the tunnel. The extension of this module for use at other points of a Tunnel is for further study.
As it stands, this MIB module can only be used to configure or monitor a TE Tunnel at its ingress. The ingress is then expected to use some protocol (such as RSVP-TE) to signal the other routers in the path the information they need to set up the tunnel. The extension of this module for use at other points of a Tunnel is for further study.
1.1. Specification of Requirements
1.1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [1].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [1].
2. The Internet-Standard Management Framework
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to Section 7 of RFC 3410 [8].
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to Section 7 of RFC 3410 [8].
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [2], STD 58, RFC 2579 [3] and STD 58, RFC 2580 [4].
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [2], STD 58, RFC 2579 [3] and STD 58, RFC 2580 [4].
3. Overview of the MIB Module
3. Overview of the MIB Module
The Traffic Engineering MIB module consists of four parts:
The Traffic Engineering MIB module consists of four parts:
1) Traffic Engineering information,
2) a table of Traffic Engineering Tunnels,
3) a table of Paths that tunnels take, and
4) a table of Hops that make up a tunnel path.
1) Traffic Engineering information, 2) a table of Traffic Engineering Tunnels, 3) a table of Paths that tunnels take, and 4) a table of Hops that make up a tunnel path.
The MIB module also has statements for minimal and full compliance.
The MIB module also has statements for minimal and full compliance.
Kompella Standards Track [Page 2] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 2] RFC 3970 A Traffic Engineering (TE) MIB January 2005
The following subsections give an overview of each part. All objects are mandatory. For minimal compliance, all objects MAY be implemented read-only; for full compliance, all objects must be implemented to their stated MAX-ACCESS capabilities. Notifications are optional.
The following subsections give an overview of each part. All objects are mandatory. For minimal compliance, all objects MAY be implemented read-only; for full compliance, all objects must be implemented to their stated MAX-ACCESS capabilities. Notifications are optional.
3.1. Traffic Engineering Information
3.1. Traffic Engineering Information
This part contains information about the Link State Protocols used to carry TE information, the signaling protocols used to set up Traffic Tunnels, the number of Traffic Tunnels that have been configured and that are operational, and a mapping of Administrative Group (called Resource Classes in [7]) numbers to names.
This part contains information about the Link State Protocols used to carry TE information, the signaling protocols used to set up Traffic Tunnels, the number of Traffic Tunnels that have been configured and that are operational, and a mapping of Administrative Group (called Resource Classes in [7]) numbers to names.
3.2. Traffic Tunnel Information
3.2. Traffic Tunnel Information
This part contains a table of Traffic Tunnels and information about each one. This information includes the Tunnel name, its configuration information, its operational information, and the active path(s) that the Tunnel takes.
This part contains a table of Traffic Tunnels and information about each one. This information includes the Tunnel name, its configuration information, its operational information, and the active path(s) that the Tunnel takes.
Configuration information includes the end points of the Traffic Tunnel, and the number of configured paths for the Traffic Tunnel.
Configuration information includes the end points of the Traffic Tunnel, and the number of configured paths for the Traffic Tunnel.
Operational information includes the current state (up/down), the count of octets and packets sent on the Traffic Tunnel, how long it has been up, and how many state transitions the Traffic Tunnel has had.
Operational information includes the current state (up/down), the count of octets and packets sent on the Traffic Tunnel, how long it has been up, and how many state transitions the Traffic Tunnel has had.
Operational path information includes the number of operational paths, the number of path changes, and when the last path change was.
Operational path information includes the number of operational paths, the number of path changes, and when the last path change was.
3.3. Path Information
3.3. Path Information
A Tunnel is a logical entity. An instantiation of a Tunnel is one or more Paths; each Path has a route (also called Explicit Route) or sequence of hops. A Path is indexed by a dual index: The primary index is that of the Tunnel to which the Path belongs; the secondary index is that of the Path itself.
A Tunnel is a logical entity. An instantiation of a Tunnel is one or more Paths; each Path has a route (also called Explicit Route) or sequence of hops. A Path is indexed by a dual index: The primary index is that of the Tunnel to which the Path belongs; the secondary index is that of the Path itself.
The configured information for a Path consists of the constraints for the Path and a configured route.
The configured information for a Path consists of the constraints for the Path and a configured route.
The operational information consists of the Path status, the computed route (i.e., the route that was computed to satisfy the constraints), and the actual path as recorded by the signaling protocol.
The operational information consists of the Path status, the computed route (i.e., the route that was computed to satisfy the constraints), and the actual path as recorded by the signaling protocol.
Kompella Standards Track [Page 3] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 3] RFC 3970 A Traffic Engineering (TE) MIB January 2005
3.4. Hop Information
3.4. Hop Information
A path consists of a sequence of hops. A hop can be loose (meaning that the path eventually traverses the specified node) or strict (meaning that the specified node and possibly the link must be the next node in the path). A hop can be specified as an IPv4 address, an IPv6 address, an Autonomous System number or an unnumbered interface index [5].
A path consists of a sequence of hops. A hop can be loose (meaning that the path eventually traverses the specified node) or strict (meaning that the specified node and possibly the link must be the next node in the path). A hop can be specified as an IPv4 address, an IPv6 address, an Autonomous System number or an unnumbered interface index [5].
The Hop Table contains all hops for all paths on a given router. It is organized as follows. There is a primary index that identifies a list of hops and a secondary index that identifies individual hops. Thus, to get the sequence of recorded hops for a path, one looks up the path's tePathRecordedRoute, which is a primary index into the Hop Table. Then to get the list of actual hops in order for the recorded path, one uses a secondary index of 1, 2, ....
The Hop Table contains all hops for all paths on a given router. It is organized as follows. There is a primary index that identifies a list of hops and a secondary index that identifies individual hops. Thus, to get the sequence of recorded hops for a path, one looks up the path's tePathRecordedRoute, which is a primary index into the Hop Table. Then to get the list of actual hops in order for the recorded path, one uses a secondary index of 1, 2, ....
3.5. Relationship with Other MIB Modules
3.5. Relationship with Other MIB Modules
A TE Tunnel can extend objects from two other MIB modules; one is the Interfaces MIB [10], and the other is the IP Tunnel MIB [11]. The mechanism for doing so is to assign the TE Tunnel index (teTunnelIndex) with a valid ifIndex value in ifTable.
A TE Tunnel can extend objects from two other MIB modules; one is the Interfaces MIB [10], and the other is the IP Tunnel MIB [11]. The mechanism for doing so is to assign the TE Tunnel index (teTunnelIndex) with a valid ifIndex value in ifTable.
If a TE Tunnel is deemed an interface, a new interface object is created and assigned an ifIndex value in ifTable. Then a TE Tunnel object is created, setting teTunnelIndex to the same value as the interface index.
If a TE Tunnel is deemed an interface, a new interface object is created and assigned an ifIndex value in ifTable. Then a TE Tunnel object is created, setting teTunnelIndex to the same value as the interface index.
If (and only if) a TE Tunnel is considered an interface, it may also be considered an IP tunnel (if the encapsulation of the TE Tunnel is IP). In that case, the interface associated with the TE Tunnel should have its ifType set to tunnel(131).
If (and only if) a TE Tunnel is considered an interface, it may also be considered an IP tunnel (if the encapsulation of the TE Tunnel is IP). In that case, the interface associated with the TE Tunnel should have its ifType set to tunnel(131).
If a TE Tunnel is not considered an interface, then the TE Tunnel index (teTunnelIndex) SHOULD be set to a value at least 2^24, so that it is distinct from normal interfaces.
If a TE Tunnel is not considered an interface, then the TE Tunnel index (teTunnelIndex) SHOULD be set to a value at least 2^24, so that it is distinct from normal interfaces.
4. Creating, Modifying, and Deleting a TE Tunnel
4. Creating, Modifying, and Deleting a TE Tunnel
To create a TE Tunnel, one first obtains a free Tunnel index by using the object teNextTunnelIndex. One then creates the Tunnel, including all parameters, either as createAndGo or createAndWait. Then, TE Paths for this Tunnel can be created by using the teTunnelNextPathIndex object, again as createAndGo or createAndWait. A particular Path is computed and signaled when both the Path and the enclosing Tunnel have RowStatus 'active'.
To create a TE Tunnel, one first obtains a free Tunnel index by using the object teNextTunnelIndex. One then creates the Tunnel, including all parameters, either as createAndGo or createAndWait. Then, TE Paths for this Tunnel can be created by using the teTunnelNextPathIndex object, again as createAndGo or createAndWait. A particular Path is computed and signaled when both the Path and the enclosing Tunnel have RowStatus 'active'.
Kompella Standards Track [Page 4] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 4] RFC 3970 A Traffic Engineering (TE) MIB January 2005
To build a Path's configured route, one first gets a free PathHop index by using teNextPathHopIndex, and then builds the route hop-by- hop using the secondary index, setting the AddrType, Address, and HopType for each Hop. Finally, one sets the tePathConfiguredRoute in the Path to the PathHop index obtained.
To build a Path's configured route, one first gets a free PathHop index by using teNextPathHopIndex, and then builds the route hop-by- hop using the secondary index, setting the AddrType, Address, and HopType for each Hop. Finally, one sets the tePathConfiguredRoute in the Path to the PathHop index obtained.
Modifying certain properties of a TE Tunnel or a TE Path may require setting the RowStatus of the Tunnel (or Path) to 'notInService' before making the changes and then setting the RowStatus of the Tunnel (or Path) back to 'active' to re-signal all Paths of the Tunnel (or the modified Path).
Modifying certain properties of a TE Tunnel or a TE Path may require setting the RowStatus of the Tunnel (or Path) to 'notInService' before making the changes and then setting the RowStatus of the Tunnel (or Path) back to 'active' to re-signal all Paths of the Tunnel (or the modified Path).
A TE Tunnel and all its Paths can be deleted by setting the Tunnel's RowStatus to 'destroy'. A specific Path within a Tunnel can be destroyed by setting that Path's RowStatus to 'destroy'.
A TE Tunnel and all its Paths can be deleted by setting the Tunnel's RowStatus to 'destroy'. A specific Path within a Tunnel can be destroyed by setting that Path's RowStatus to 'destroy'.
5. MIB Specification
5. MIB Specification
This MIB module IMPORTs objects from RFCs 2578 [2], 2579 [3], 2580 [3], 3411 [6], and 3811 [5] and it also has REFERENCE clauses to RFCs 3209 [8] and 3212 [12].
This MIB module IMPORTs objects from RFCs 2578 [2], 2579 [3], 2580 [3], 3411 [6], and 3811 [5] and it also has REFERENCE clauses to RFCs 3209 [8] and 3212 [12].
TE-MIB DEFINITIONS ::= BEGIN
TE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
NOTIFICATION-TYPE, mib-2,
Integer32, Gauge32, Counter32,
Counter64, Unsigned32, TimeTicks FROM SNMPv2-SMI
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, Integer32, Gauge32, Counter32, Counter64, Unsigned32, TimeTicks FROM SNMPv2-SMI
RowStatus, StorageType, TimeStamp,
TruthValue FROM SNMPv2-TC
RowStatus, StorageType, TimeStamp, TruthValue FROM SNMPv2-TC
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF
TeHopAddress, TeHopAddressType,
MplsBitRate FROM MPLS-TC-STD-MIB;
TeHopAddress, TeHopAddressType, MplsBitRate FROM MPLS-TC-STD-MIB;
teMIB MODULE-IDENTITY
LAST-UPDATED "200501040000Z" -- 01 January 2005
ORGANIZATION "IETF Traffic Engineering Working Group"
CONTACT-INFO "
Editor: Kireeti Kompella
Postal: Juniper Networks, Inc.
1194 Mathilda Ave
teMIB MODULE-IDENTITY LAST-UPDATED "200501040000Z" -- 01 January 2005 ORGANIZATION "IETF Traffic Engineering Working Group" CONTACT-INFO " Editor: Kireeti Kompella Postal: Juniper Networks, Inc. 1194 Mathilda Ave
Kompella Standards Track [Page 5] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 5] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Sunnyvale, CA 94089
Tel: +1 408 745 2000
E-mail: kireeti@juniper.net
Sunnyvale, CA 94089 Tel: +1 408 745 2000 E-mail: kireeti@juniper.net
The IETF Traffic Engineering Working Group is
chaired by Jim Boyle and Ed Kern.
The IETF Traffic Engineering Working Group is chaired by Jim Boyle and Ed Kern.
WG Mailing List information:
WG Mailing List information:
General Discussion: te-wg@ops.ietf.org
To Subscribe: te-wg-request@ops.ietf.org
In Body: subscribe
Archive: ftp://ops.ietf.org/pub/lists
General Discussion: te-wg@ops.ietf.org To Subscribe: te-wg-request@ops.ietf.org In Body: subscribe Archive: ftp://ops.ietf.org/pub/lists
Comments on the MIB module should be sent to the
mailing list. The archives for this mailing list
should be consulted for previous discussion on
this MIB.
"
DESCRIPTION "The Traffic Engineering MIB module.
Comments on the MIB module should be sent to the mailing list. The archives for this mailing list should be consulted for previous discussion on this MIB. " DESCRIPTION "The Traffic Engineering MIB module.
Copyright (C) The Internet Society (2005). This
version of this MIB module is part of RFC 3970;
see the RFC itself for full legal notices.
"
Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 3970; see the RFC itself for full legal notices. "
-- revision history
-- revision history
REVISION "200501040000Z" -- 01 January 2005
DESCRIPTION "Initial version, published as RFC 3970."
::= { mib-2 122 }
REVISION "200501040000Z" -- 01 January 2005 DESCRIPTION "Initial version, published as RFC 3970." ::= { mib-2 122 }
-- Top level objects
-- Top level objects
teMIBNotifications OBJECT IDENTIFIER ::= { teMIB 0 }
teMIBObjects OBJECT IDENTIFIER ::= { teMIB 1 }
teMIBConformance OBJECT IDENTIFIER ::= { teMIB 2 }
teMIBNotifications OBJECT IDENTIFIER ::= { teMIB 0 } teMIBObjects OBJECT IDENTIFIER ::= { teMIB 1 } teMIBConformance OBJECT IDENTIFIER ::= { teMIB 2 }
-- **************************************************************** -- -- TE MIB Objects --
-- **************************************************************** -- -- TE MIB Objects --
-- TE Info
-- TE Info
teInfo OBJECT IDENTIFIER ::= { teMIBObjects 1 }
teInfo OBJECT IDENTIFIER ::= { teMIBObjects 1 }
teDistProtocol OBJECT-TYPE
teDistProtocol OBJECT-TYPE
Kompella Standards Track [Page 6] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 6] RFC 3970 A Traffic Engineering (TE) MIB January 2005
SYNTAX BITS {
other(0),
isis(1),
ospf(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "IGP used to distribute Traffic Engineering
information and topology to each device for the
purpose of automatic path computation. More than
one IGP may be used to distribute TE information.
"
::= { teInfo 1 }
SYNTAX BITS { other(0), isis(1), ospf(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "IGP used to distribute Traffic Engineering information and topology to each device for the purpose of automatic path computation. More than one IGP may be used to distribute TE information. " ::= { teInfo 1 }
teSignalingProto OBJECT-TYPE
SYNTAX BITS {
other(0),
rsvpte(1),
crldp(2),
static(3) -- static configuration
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Traffic Engineering signaling protocols supported
by this device. More than one protocol may be
supported.
"
REFERENCE "For a description of RSVP-TE, see RFC 3209;
for CR-LDP, see RFC 3212.
"
::= { teInfo 2 }
teSignalingProto OBJECT-TYPE SYNTAX BITS { other(0), rsvpte(1), crldp(2), static(3) -- static configuration } MAX-ACCESS read-only STATUS current DESCRIPTION "Traffic Engineering signaling protocols supported by this device. More than one protocol may be supported. " REFERENCE "For a description of RSVP-TE, see RFC 3209; for CR-LDP, see RFC 3212. " ::= { teInfo 2 }
teNotificationEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION "If this object is true, then it enables the
generation of notifications from this MIB module.
Otherwise notifications are not generated.
"
DEFVAL { false }
::= { teInfo 3 }
teNotificationEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of notifications from this MIB module. Otherwise notifications are not generated. " DEFVAL { false } ::= { teInfo 3 }
teNextTunnelIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "An integer that may be used as a new Index in the
teNextTunnelIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "An integer that may be used as a new Index in the
Kompella Standards Track [Page 7] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 7] RFC 3970 A Traffic Engineering (TE) MIB January 2005
teTunnelTable.
teTunnelTable.
The special value of 0 indicates that no more new
entries can be created in that table.
The special value of 0 indicates that no more new entries can be created in that table.
When this MIB module is used for configuration, this
object always contains a legal value (if non-zero)
for an index that is not currently used in that
table. The Command Generator (Network Management
Application) reads this variable and uses the
(non-zero) value read when creating a new row with
an SNMP SET. When the SET is performed, the Command
Responder (agent) must determine whether the value
is indeed still unused; Two Network Management
Applications may attempt to create a row
(configuration entry) simultaneously and use the
same value. If it is currently unused, the SET
succeeds, and the Command Responder (agent) changes
the value of this object according to an
implementation-specific algorithm. If the value is
in use, however, the SET fails. The Network
Management Application must then re-read this
variable to obtain a new usable value.
"
::= { teInfo 4 }
When this MIB module is used for configuration, this object always contains a legal value (if non-zero) for an index that is not currently used in that table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds, and the Command Responder (agent) changes the value of this object according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value. " ::= { teInfo 4 }
teNextPathHopIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "An integer that may be used as a new Index in the
tePathHopTable.
teNextPathHopIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "An integer that may be used as a new Index in the tePathHopTable.
The special value of 0 indicates that no more new
entries can be created in that table.
The special value of 0 indicates that no more new entries can be created in that table.
When this MIB module is used for configuration, this
object always contains a legal value (if non-zero)
for an index that is not currently used in that
table. The Command Generator (Network Management
Application) reads this variable and uses the
(non-zero) value read when creating a new row with
an SNMP SET. When the SET is performed, the Command
Responder (agent) must determine whether the value
is indeed still unused; Two Network Management
Applications may attempt to create a row
(configuration entry) simultaneously and use the
same value. If it is currently unused, the SET
When this MIB module is used for configuration, this object always contains a legal value (if non-zero) for an index that is not currently used in that table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET
Kompella Standards Track [Page 8] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 8] RFC 3970 A Traffic Engineering (TE) MIB January 2005
succeeds, and the Command Responder (agent) changes
the value of this object according to an
implementation-specific algorithm. If the value is
in use, however, the SET fails. The Network
Management Application must then re-read this
variable to obtain a new usable value.
"
::= { teInfo 5 }
succeeds, and the Command Responder (agent) changes the value of this object according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value. " ::= { teInfo 5 }
teConfiguredTunnels OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Number of currently configured Tunnels."
::= { teInfo 6 }
teConfiguredTunnels OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of currently configured Tunnels." ::= { teInfo 6 }
teActiveTunnels OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Number of currently active Tunnels."
::= { teInfo 7 }
teActiveTunnels OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of currently active Tunnels." ::= { teInfo 7 }
tePrimaryTunnels OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Number of currently active Tunnels running on
their primary paths.
"
::= { teInfo 8 }
tePrimaryTunnels OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of currently active Tunnels running on their primary paths. " ::= { teInfo 8 }
teAdminGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeAdminGroupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A mapping of configured administrative groups. Each
entry represents an Administrative Group and
provides a name and index for the group.
Administrative groups are used to label links in the
Traffic Engineering topology in order to place
constraints (include and exclude) on Tunnel paths.
teAdminGroupTable OBJECT-TYPE SYNTAX SEQUENCE OF TeAdminGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A mapping of configured administrative groups. Each entry represents an Administrative Group and provides a name and index for the group. Administrative groups are used to label links in the Traffic Engineering topology in order to place constraints (include and exclude) on Tunnel paths.
A groupName can only be linked to one group number.
The groupNumber is the number assigned to the
administrative group used in constraints,
such as tePathIncludeAny or tePathIncludeAll.
"
A groupName can only be linked to one group number. The groupNumber is the number assigned to the administrative group used in constraints, such as tePathIncludeAny or tePathIncludeAll. "
Kompella Standards Track [Page 9] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 9] RFC 3970 A Traffic Engineering (TE) MIB January 2005
::= { teInfo 9 }
::= { teInfo 9 }
teAdminGroupEntry OBJECT-TYPE
SYNTAX TeAdminGroupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A mapping between a configured group number and
its human-readable name. The group number should
be between 1 and 32, inclusive. Group number n
represents bit number (n-1) in the bit vector for
Include/Exclude constraints.
teAdminGroupEntry OBJECT-TYPE SYNTAX TeAdminGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A mapping between a configured group number and its human-readable name. The group number should be between 1 and 32, inclusive. Group number n represents bit number (n-1) in the bit vector for Include/Exclude constraints.
All entries in this table MUST be kept in stable
storage so that they will re-appear in case of a
restart/reboot.
"
INDEX { teAdminGroupNumber }
::= { teAdminGroupTable 1 }
All entries in this table MUST be kept in stable storage so that they will re-appear in case of a restart/reboot. " INDEX { teAdminGroupNumber } ::= { teAdminGroupTable 1 }
TeAdminGroupEntry ::=
SEQUENCE {
teAdminGroupNumber Integer32,
teAdminGroupName SnmpAdminString,
teAdminGroupRowStatus RowStatus
}
TeAdminGroupEntry ::= SEQUENCE { teAdminGroupNumber Integer32, teAdminGroupName SnmpAdminString, teAdminGroupRowStatus RowStatus }
teAdminGroupNumber OBJECT-TYPE
SYNTAX Integer32 (1..32)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Index of the administrative group."
::= { teAdminGroupEntry 1 }
teAdminGroupNumber OBJECT-TYPE SYNTAX Integer32 (1..32) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index of the administrative group." ::= { teAdminGroupEntry 1 }
teAdminGroupName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION "Name of the administrative group."
::= { teAdminGroupEntry 2 }
teAdminGroupName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "Name of the administrative group." ::= { teAdminGroupEntry 2 }
teAdminGroupRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The status of this conceptual row.
teAdminGroupRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row.
The value of this object has no effect on whether
other objects in this conceptual row can be
The value of this object has no effect on whether other objects in this conceptual row can be
Kompella Standards Track [Page 10] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 10] RFC 3970 A Traffic Engineering (TE) MIB January 2005
modified.
"
::= { teAdminGroupEntry 3 }
modified. " ::= { teAdminGroupEntry 3 }
-- Tunnel Table
-- Tunnel Table
teTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Table of Configured Traffic Tunnels."
::= { teMIBObjects 2 }
teTunnelTable OBJECT-TYPE SYNTAX SEQUENCE OF TeTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of Configured Traffic Tunnels." ::= { teMIBObjects 2 }
teTunnelEntry OBJECT-TYPE
SYNTAX TeTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Entry containing information about a particular
Traffic Tunnel.
"
INDEX { teTunnelIndex }
::= { teTunnelTable 1 }
teTunnelEntry OBJECT-TYPE SYNTAX TeTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry containing information about a particular Traffic Tunnel. " INDEX { teTunnelIndex } ::= { teTunnelTable 1 }
TeTunnelEntry ::=
SEQUENCE {
teTunnelIndex Unsigned32,
teTunnelName SnmpAdminString,
teTunnelNextPathIndex Unsigned32,
-- Conceptual row information:
teTunnelRowStatus RowStatus,
teTunnelStorageType StorageType,
-- Address information:
teTunnelSourceAddressType TeHopAddressType,
teTunnelSourceAddress TeHopAddress,
teTunnelDestinationAddressType TeHopAddressType,
teTunnelDestinationAddress TeHopAddress,
-- State/performance information:
teTunnelState INTEGER,
teTunnelDiscontinuityTimer TimeStamp,
teTunnelOctets Counter64,
teTunnelPackets Counter64,
teTunnelLPOctets Counter32,
teTunnelLPPackets Counter32,
teTunnelAge TimeTicks,
teTunnelTimeUp TimeTicks,
teTunnelPrimaryTimeUp TimeTicks,
teTunnelTransitions Counter32,
teTunnelLastTransition TimeTicks,
TeTunnelEntry ::= SEQUENCE { teTunnelIndex Unsigned32, teTunnelName SnmpAdminString, teTunnelNextPathIndex Unsigned32, -- Conceptual row information: teTunnelRowStatus RowStatus, teTunnelStorageType StorageType, -- Address information: teTunnelSourceAddressType TeHopAddressType, teTunnelSourceAddress TeHopAddress, teTunnelDestinationAddressType TeHopAddressType, teTunnelDestinationAddress TeHopAddress, -- State/performance information: teTunnelState INTEGER, teTunnelDiscontinuityTimer TimeStamp, teTunnelOctets Counter64, teTunnelPackets Counter64, teTunnelLPOctets Counter32, teTunnelLPPackets Counter32, teTunnelAge TimeTicks, teTunnelTimeUp TimeTicks, teTunnelPrimaryTimeUp TimeTicks, teTunnelTransitions Counter32, teTunnelLastTransition TimeTicks,
Kompella Standards Track [Page 11] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella Standards Track [Page 11] RFC 3970 A Traffic Engineering (TE) MIB January 2005
teTunnelPathChanges Counter32,
teTunnelLastPathChange TimeTicks,
teTunnelConfiguredPaths Gauge32,
teTunnelStandbyPaths Gauge32,
teTunnelOperationalPaths Gauge32
}
teTunnelPathChanges Counter32, teTunnelLastPathChange TimeTicks, teTunnelConfiguredPaths Gauge32, teTunnelStandbyPaths Gauge32, teTunnelOperationalPaths Gauge32 }
teTunnelIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A unique index that identifies a Tunnel. If the TE
Tunnel is considered an interface, then this index
must match the interface index of the corresponding
interface. Otherwise, this index must be at least
2^24, so that it does not overlap with any existing
interface index.
"
::= { teTunnelEntry 1 }
teTunnelIndex OBJECT-TYPE SYNTAX Unsigned32(1 .4294967295)のマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「Tunnelを特定するユニークなインデックス。」 TE Tunnelがインタフェースであると考えられるなら、このインデックスは対応するインタフェースのインタフェースインデックスに合わなければなりません。 さもなければ、このインデックスが少なくとも2^24であるに違いないので、それはどんな既存のインタフェースインデックスにも重なりません。 " ::= teTunnelEntry1
teTunnelName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION "Name of the Traffic Tunnel.
teTunnelName OBJECT-TYPE SYNTAX SnmpAdminString(SIZE(1 .32))マックス-ACCESSは「交通の名前はトンネルを堀る」STATUSの現在の記述を読書して作成します。
Note that the name of a Tunnel MUST be unique.
When a SET request contains a name that is already
in use for another entry, then the implementation
must return an inconsistentValue error.
Tunnelという名前がユニークであるに違いないことに注意してください。 SET要求が別のエントリーには、既に使用中の名前を含んでいると、実現がinconsistentValue誤りを返さなければなりません。
The value of this object cannot be changed if the
if the value of the corresponding teTunnelRowStatus
object is 'active'.
"
::= { teTunnelEntry 2 }
この物の値を変えることができない、対応するteTunnelRowStatus物の値が'アクティブである'なら。 " ::= teTunnelEntry2
teTunnelNextPathIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "An integer that may be used as a new Index for the
next Path in this Tunnel.
teTunnelNextPathIndex OBJECT-TYPE SYNTAX Unsigned32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「このTunnelの次のPathに新しいIndexとして使用されるかもしれない整数。」
The special value of 0 indicates that no more Paths
can be created for this Tunnel, or that no more new
entries can be created in tePathTable.
0の特別な値は、このTunnelのためにそれ以上のPathsを全く作成できないか、またはtePathTableでそれ以上の新しいエントリーを作成できないのを示します。
Kompella Standards Track [Page 12] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[12ページ]。
When this MIB module is used for configuration, this
object always contains a legal value (if non-zero)
for an index that is not currently used in that
table. The Command Generator (Network Management
Application) reads this variable and uses the
(non-zero) value read when creating a new row with
an SNMP SET. When the SET is performed, the Command
Responder (agent) must determine whether the value
is indeed still unused; Two Network Management
Applications may attempt to create a row
(configuration entry) simultaneously and use the
same value. If it is currently unused, the SET
succeeds, and the Command Responder (agent) changes
the value of this object according to an
implementation-specific algorithm. If the value is
in use, however, the SET fails. The Network
Management Application must then re-read this
variable to obtain a new usable value.
"
::= { teTunnelEntry 3 }
このMIBモジュールが構成に使用されるとき、この物は現在そのテーブルで使用されないインデックスのためにいつも法定価格を含んでいます(非ゼロであるなら)。 Command Generator(ネットワークManagement Application)はこの変数を読んで、SNMP SETと共に新しい列を作成するとき読まれた(非ゼロ)値を使用します。 SETが実行されるとき、Command Responder(エージェント)は、本当に、値がまだ未使用であるかどうか決定しなければなりません。 2Network Management Applicationsが同時に、列(構成エントリー)を作成して、同じ値を使用するのを試みるかもしれません。 それが現在未使用であるなら、SETは成功します、そして、実現特有のアルゴリズムによると、Command Responder(エージェント)はこの物の値を変えます。 しかしながら、値が使用中であるなら、SETは失敗します。 そして、Network Management Applicationは、新しい使用可能な値を得るためにこの変数を再読しなければなりません。 " ::= teTunnelEntry3
teTunnelRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The status of this conceptual row.
teTunnelRowStatus OBJECT-TYPE SYNTAX RowStatusマックス-ACCESSは「これほど概念的の状態はこぐ」STATUSの現在の記述を読書して作成します。
When the value of this object is 'active', then
the values for the corresponding objects
teTunnelName, teTunnelSourceAddressType,
teTunnelSourceAddress,
teTunnelDestinationAddressType, and
teTunnelDestinationAddress cannot be changed.
"
::= { teTunnelEntry 4 }
この物の値が'アクティブである'と、対応するオブジェクトのteTunnelName、teTunnelSourceAddressType、teTunnelSourceAddress、teTunnelDestinationAddressType、およびteTunnelDestinationAddressのための値を変えることができません。 " ::= teTunnelEntry4
teTunnelStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The storage type for this conceptual row.
teTunnelStorageType OBJECT-TYPE SYNTAX StorageTypeマックス-ACCESSは「これに、概念的な格納タイプはこぐ」STATUSの現在の記述を読書して作成します。
Conceptual rows having the value 'permanent' need
not allow write-access to any columnar objects
in the row.
"
::= { teTunnelEntry 5 }
'永久的'に値を持っている概念的な列は列にいずれにもアクセスを書いている円柱状の物を許容する必要はありません。 " ::= teTunnelEntry5
Kompella Standards Track [Page 13] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[13ページ]。
teTunnelSourceAddressType OBJECT-TYPE
SYNTAX TeHopAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The type of Traffic Engineered Tunnel hop address
for the source of this Tunnel. Typically, this
address type is IPv4 or IPv6, with a prefix length
of 32 or 128, respectively. If the TE Tunnel path
is being computed by a path computation server,
however, it is possible to use more flexible source
address types, such as AS numbers or prefix lengths
less than host address lengths.
teTunnelSourceAddressType OBJECT-TYPE SYNTAX TeHopAddressTypeマックス-ACCESSは「Traffic Engineered TunnelホップのタイプはこのTunnelの源に記述する」STATUSの現在の記述を読書して作成します。 このアドレスタイプは、それぞれ通常、32か128の接頭語の長さがあるIPv4かIPv6です。 しかしながら、TE Tunnel経路が経路計算サーバによって計算されているなら、AS番号か接頭語の長さなどのホスト・アドレスの長さよりフレキシブルなソースアドレスタイプを使用しないのは可能です。
The value of this object cannot be changed
if the value of the corresponding teTunnelRowStatus
object is 'active'.
"
::= { teTunnelEntry 6 }
対応するteTunnelRowStatus物の値が'アクティブである'なら、この物の値を変えることができません。 " ::= teTunnelEntry6
teTunnelSourceAddress OBJECT-TYPE
SYNTAX TeHopAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The Source Traffic Engineered Tunnel hop address of
this Tunnel.
teTunnelSourceAddress OBJECT-TYPE SYNTAX TeHopAddressマックス-ACCESSはSTATUSの現在の記述を読書して作成します。「このTunnelのSource Traffic Engineered Tunnelホップアドレス。」
The type of this address is determined by the value
of the corresponding teTunnelSourceAddressType.
このアドレスのタイプは対応するteTunnelSourceAddressTypeの値で決定します。
Note that the source and destination addresses of a
Tunnel can be different address types.
Tunnelのソースと送付先アドレスが異なったアドレスタイプであるかもしれないことに注意してください。
The value of this object cannot be changed
if the value of the corresponding teTunnelRowStatus
object is 'active'.
"
::= { teTunnelEntry 7 }
対応するteTunnelRowStatus物の値が'アクティブである'なら、この物の値を変えることができません。 " ::= teTunnelEntry7
teTunnelDestinationAddressType OBJECT-TYPE
SYNTAX TeHopAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The type of Traffic Engineered Tunnel hop address
for the destination of this Tunnel.
teTunnelDestinationAddressType OBJECT-TYPE SYNTAX TeHopAddressTypeマックス-ACCESSは「Traffic Engineered TunnelホップのタイプはこのTunnelの目的地に記述する」STATUSの現在の記述を読書して作成します。
The value of this object cannot be changed
if the value of the corresponding teTunnelRowStatus
object is 'active'.
対応するteTunnelRowStatus物の値が'アクティブである'なら、この物の値を変えることができません。
Kompella Standards Track [Page 14] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[14ページ]。
"
::= { teTunnelEntry 8 }
" ::= teTunnelEntry8
teTunnelDestinationAddress OBJECT-TYPE
SYNTAX TeHopAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The Destination Traffic Engineered Tunnel hop
address of this Tunnel.
teTunnelDestinationAddress OBJECT-TYPE SYNTAX TeHopAddressマックス-ACCESSはSTATUSの現在の記述を読書して作成します。「このTunnelのDestination Traffic Engineered Tunnelホップアドレス。」
The type of this address is determined by the value
of the corresponding teTunnelDestinationAddressType.
このアドレスのタイプは対応するteTunnelDestinationAddressTypeの値で決定します。
Note that source and destination addresses of a
Tunnel can be different address types.
Tunnelのソースと送付先アドレスが異なったアドレスタイプであるかもしれないことに注意してください。
The value of this object cannot be changed
if the value of the corresponding teTunnelRowStatus
object is 'active'.
"
::= { teTunnelEntry 9 }
対応するteTunnelRowStatus物の値が'アクティブである'なら、この物の値を変えることができません。 " ::= teTunnelEntry9
teTunnelState OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
up(2),
down(3),
testing(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The operational state of the Tunnel."
::= { teTunnelEntry 10 }
未知(1)は(3)より(2)に倒します、(4)をテストして。teTunnelState OBJECT-TYPE SYNTAX INTEGER、「操作上はTunnelについて述べる」マックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 ::= teTunnelEntry10
teTunnelDiscontinuityTimer OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The value of sysUpTime on the most recent occasion
at which any one or more of this tunnel's counters
suffered a discontinuity. The relevant counters
are teTunnelOctets, teTunnelPackets,
teTunnelLPOctets, and teTunnelLPPackets. If no such
discontinuities have occurred since the last
re-initialization of the local management subsystem
then this object contains a zero value.
"
::= { teTunnelEntry 11 }
teTunnelDiscontinuityTimer OBJECT-TYPE SYNTAX TimeStampのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「いくらかものかこの一層のトンネルのカウンタが不連続を受けた最新の時のsysUpTimeの値。」 関連カウンタは、teTunnelOctetsと、teTunnelPacketsと、teTunnelLPOctetsと、teTunnelLPPacketsです。 現地管理職者サブシステムの最後の再初期化以来どれかそのような不連続が起こっていないなら、この物はaゼロ値を含んでいます。 " ::= teTunnelEntry11
Kompella Standards Track [Page 15] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[15ページ]。
teTunnelOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of octets that have been forwarded over
the Tunnel.
teTunnelOctets OBJECT-TYPE SYNTAX Counter64のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Tunnelの上に送られた八重奏の数。」
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times, as indicated by the value of
teTunnelDiscontinuityTimer.
"
::= { teTunnelEntry 12 }
このカウンタの値における不連続はマネージメントシステムの再初期化において他の時に起こることができます、teTunnelDiscontinuityTimerの値によって示されるように。 " ::= teTunnelEntry12
teTunnelPackets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of packets that have been forwarded over
the Tunnel.
teTunnelPackets OBJECT-TYPE SYNTAX Counter64のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Tunnelの上に送られたパケットの数。」
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times, as indicated by the value of
teTunnelDiscontinuityTimer.
"
::= { teTunnelEntry 13 }
このカウンタの値における不連続はマネージメントシステムの再初期化において他の時に起こることができます、teTunnelDiscontinuityTimerの値によって示されるように。 " ::= teTunnelEntry13
teTunnelLPOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of octets that have been forwarded over
the Tunnel.
teTunnelLPOctets OBJECT-TYPE SYNTAX Counter32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Tunnelの上に送られた八重奏の数。」
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times, as indicated by the value of
teTunnelDiscontinuityTimer.
"
::= { teTunnelEntry 14 }
このカウンタの値における不連続はマネージメントシステムの再初期化において他の時に起こることができます、teTunnelDiscontinuityTimerの値によって示されるように。 " ::= teTunnelEntry14
teTunnelLPPackets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of packets that have been forwarded over
the Tunnel.
teTunnelLPPackets OBJECT-TYPE SYNTAX Counter32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Tunnelの上に送られたパケットの数。」
Kompella Standards Track [Page 16] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[16ページ]。
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times, as indicated by the value of
teTunnelDiscontinuityTimer.
"
::= { teTunnelEntry 15 }
このカウンタの値における不連続はマネージメントシステムの再初期化において他の時に起こることができます、teTunnelDiscontinuityTimerの値によって示されるように。 " ::= teTunnelEntry15
teTunnelAge OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The age (i.e., time from creation of this conceptual
row till now) of this Tunnel in hundredths of a
second. Note that because TimeTicks wrap in about
16 months, this value is best used in interval
measurements.
"
::= { teTunnelEntry 16 }
「aの100分の1における、このTunnelの時代(すなわち、この概念的な現在までの列の創造からの時間)は後援する」teTunnelAge OBJECT-TYPE SYNTAX TimeTicksのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 TimeTicksがおよそ16で何カ月もの、この値を包装するので間隔測定で最も良い使用する注意。 " ::= teTunnelEntry16
teTunnelTimeUp OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The total time in hundredths of a second that this
Tunnel has been operational. Note that because
TimeTicks wrap in about 16 months, this value is
best used in interval measurements.
「100分の1における、このTunnelが操作上であったことの1秒の総時間」の間のteTunnelTimeUp OBJECT-TYPE SYNTAX TimeTicksのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 TimeTicksがおよそ16で何カ月もの、この値を包装するので間隔測定で最も良い使用する注意。
An example of usage of this object would be to
compute the percentage up time over a period of time
by obtaining values of teTunnelAge and
teTunnelTimeUp at two points in time and computing
the following ratio:
((teTunnelTimeUp2 - teTunnelTimeUp1)/
(teTunnelAge2 - teTunnelAge1)) * 100 %. In doing
so, the management station must account for
wrapping of the values of teTunnelAge and
teTunnelTimeUp between the two measurements.
"
::= { teTunnelEntry 17 }
この物の使用法に関する例は以下の比率にタイム・オーバーのteTunnelAgeの値を得るのによる期間と時間内にの2ポイントとコンピューティングにおけるteTunnelTimeUpへの割合を計算するだろうことです: ((teTunnelTimeUp2--teTunnelTimeUp1)/(teTunnelAge2--teTunnelAge1)) * 100 %. そうする際に、管理局は2つの測定値の間でteTunnelAgeとteTunnelTimeUpの値のラッピングを説明しなければなりません。 " ::= teTunnelEntry17
teTunnelPrimaryTimeUp OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The total time in hundredths of a second that this
Tunnel's primary path has been operational. Note
that because TimeTicks wrap in about 16 months, this
「100分の1における、このTunnelの第一の経路が操作上であったことの1秒の総時間」の間のteTunnelPrimaryTimeUp OBJECT-TYPE SYNTAX TimeTicksのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 TimeTicksがおよそ16カ月を中に包装するのでそれに注意してください、これ
Kompella Standards Track [Page 17] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[17ページ]。
value is best used in interval measurements.
間隔測定で値を使用するのは最も良いです。
An example of usage of this field would be to
compute what percentage of time that a TE Tunnel was
on the primary path over a period of time by
computing
((teTunnelPrimaryTimeUp2 - teTunnelPrimaryTimeUp1)/
(teTunnelTimeUp2 - teTunnelTimeUp1))*100 %. In
doing so, the management station must account for
wrapping of the values of teTunnelPrimaryTimeUp and
teTunnelTimeUp between the two measurements.
"
::= { teTunnelEntry 18 }
この分野の用法に関する例は期間の間、((teTunnelPrimaryTimeUp2--teTunnelPrimaryTimeUp1)/(teTunnelTimeUp2--teTunnelTimeUp1))を*100%計算することによってTE Tunnelが第一の経路にあった何パーセントの時間を計算するだろうことです。 そうする際に、管理局は2つの測定値の間でteTunnelPrimaryTimeUpとteTunnelTimeUpの値のラッピングを説明しなければなりません。 " ::= teTunnelEntry18
teTunnelTransitions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of operational state transitions
(up -> down and down -> up) this Tunnel has
undergone.
"
::= { teTunnelEntry 19 }
teTunnelTransitions OBJECT-TYPE SYNTAX Counter32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「このTunnelが受けた操作上の状態遷移(下がっていて下側->に上がっている->への)の数。」 " ::= teTunnelEntry19
teTunnelLastTransition OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The time in hundredths of a second since the last
operational state transition occurred on this
Tunnel.
「最後の操作上の状態遷移がこのTunnelに起こって以来の1秒の100分の1における時間」の間のteTunnelLastTransition OBJECT-TYPE SYNTAX TimeTicksのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。
Note that if the last transition was over 16
months ago, this value will be inaccurate.
"
::= { teTunnelEntry 20 }
立下り区間が16カ月前に終わっていたなら、この値が不正確になることに注意してください。 " ::= teTunnelEntry20
teTunnelPathChanges OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of path changes this Tunnel has had."
::= { teTunnelEntry 21 }
teTunnelPathChanges OBJECT-TYPE SYNTAX Counter32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「このTunnelが持っていた経路変化の数。」 ::= teTunnelEntry21
teTunnelLastPathChange OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
teTunnelLastPathChange OBJECT-TYPE SYNTAX TimeTicksマックス-ACCESS書き込み禁止STATUS海流
Kompella Standards Track [Page 18] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[18ページ]。
DESCRIPTION "The time in hundredths of a second since the last
path change occurred on this Tunnel.
「最後の経路変化がこのTunnelに起こって以来の1秒の100分の1における時間」の間の記述。
Note that if the last transition was over 16
months ago, this value will be inaccurate.
立下り区間が16カ月前に終わっていたなら、この値が不正確になることに注意してください。
Path changes may be caused by network events or by
reconfiguration that affects the path.
"
::= { teTunnelEntry 22 }
経路変化はネットワークイベントか経路に影響する再構成によって引き起こされるかもしれません。 " ::= teTunnelEntry22
teTunnelConfiguredPaths OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of paths configured for this Tunnel."
::= { teTunnelEntry 23 }
「パスの数はこのTunnelのために構成した」teTunnelConfiguredPaths OBJECT-TYPE SYNTAX Gauge32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 ::= teTunnelEntry23
teTunnelStandbyPaths OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of standby paths configured for this
Tunnel.
"
::= { teTunnelEntry 24 }
「予備経路の数はこのTunnelのために構成した」teTunnelStandbyPaths OBJECT-TYPE SYNTAX Gauge32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 " ::= teTunnelEntry24
teTunnelOperationalPaths OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of operational paths for this Tunnel.
This includes the path currently active, as
well as operational standby paths.
"
::= { teTunnelEntry 25 }
teTunnelOperationalPaths OBJECT-TYPE SYNTAX Gauge32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「このTunnelのための操作上の経路の数。」 これは現在操作上の予備経路と同様にアクティブな経路を含んでいます。 " ::= teTunnelEntry25
-- **************************************************************** -- -- Tunnel Path Table --
-- トンネルを堀る..経路..テーブル
tePathTable OBJECT-TYPE
SYNTAX SEQUENCE OF TePathEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Table of Configured Traffic Tunnels."
::= { teMIBObjects 3 }
「構成された交通のテーブルはトンネルを堀る」tePathTable OBJECT-TYPE SYNTAX SEQUENCE OF TePathEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 ::= teMIBObjects3
Kompella Standards Track [Page 19] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[19ページ]。
tePathEntry OBJECT-TYPE
SYNTAX TePathEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Entry containing information about a particular
Traffic Tunnel. Each Traffic Tunnel can have zero
or more Traffic Paths.
tePathEntry OBJECT-TYPE SYNTAX TePathEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「特定のTraffic Tunnelの情報を含むエントリー。」 各Traffic Tunnelはゼロか、より多くのTraffic Pathsを持つことができます。
As a Traffic Path can only exist over an existing
Traffic Tunnel, all tePathEntries with
a value of n for teTunnelIndex MUST be removed by
the implementation when the corresponding
teTunnelEntry with a value of n for teTunnelIndex
is removed.
"
INDEX { teTunnelIndex, tePathIndex }
::= { tePathTable 1 }
Traffic Pathが存在できるだけであるように、teTunnelIndexのためのnの値がある対応するteTunnelEntryが取り外されるとき、実現でteTunnelIndexを取り外さなければならないので、既存のTraffic Tunnel、nの値があるすべてのtePathEntriesの上に存在してください。 「teTunnelIndex、tePathIndexに索引をつけてください:、:、」= tePathTable1
TePathEntry ::=
SEQUENCE {
tePathIndex Unsigned32,
tePathName SnmpAdminString,
-- Conceptual row information
tePathRowStatus RowStatus,
tePathStorageType StorageType,
-- Path properties
tePathType INTEGER,
tePathConfiguredRoute Unsigned32,
tePathBandwidth MplsBitRate,
tePathIncludeAny Unsigned32,
tePathIncludeAll Unsigned32,
tePathExclude Unsigned32,
tePathSetupPriority Integer32,
tePathHoldPriority Integer32,
tePathProperties BITS,
-- Path status
tePathOperStatus INTEGER,
tePathAdminStatus INTEGER,
tePathComputedRoute Unsigned32,
tePathRecordedRoute Unsigned32
}
TePathEntry:、:= 系列{ tePathIndex Unsigned32、tePathName SnmpAdminString--概念的な列の情報tePathRowStatus RowStatus、tePathStorageType StorageType; 経路特性のtePathType INTEGER、tePathConfiguredRoute Unsigned32、tePathBandwidth MplsBitRate、tePathIncludeAny Unsigned32、tePathIncludeAll Unsigned32、tePathExclude Unsigned32、tePathSetupPriority Integer32、tePathHoldPriority Integer32、tePathProperties BITS--経路状態tePathOperStatus INTEGER、tePathAdminStatus INTEGER、tePathComputedRoute Unsigned32、tePathRecordedRoute Unsigned32; }
tePathIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An index that uniquely identifies a path within
a Tunnel.
tePathIndex OBJECT-TYPE SYNTAX Unsigned32(1 .4294967295)のマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「Tunnelの中で唯一経路を特定するインデックス。」
Kompella Standards Track [Page 20] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[20ページ]。
The combination of <teTunnelIndex, tePathIndex> thus
uniquely identifies a path among all paths on this
router.
"
::= { tePathEntry 1 }
<teTunnelIndexの組み合わせであり、その結果、tePathIndex>はこのルータのすべての経路の中で唯一経路を特定します。 " ::= tePathEntry1
tePathName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The name of this path.
tePathName OBJECT-TYPE SYNTAX SnmpAdminString(SIZE(0 .32))マックス-ACCESSはSTATUSの現在の記述を読書して作成します。「この経路の名前。」
A pathName must be unique within the set of paths
over a single tunnel. If a SET request is received
with a duplicate name, then the implementation MUST
return an inconsistentValue error.
pathNameは単一のトンネルにわたって経路のセットの中でユニークであるに違いありません。 写し名でSET要求を受け取るなら、実現はinconsistentValue誤りを返さなければなりません。
The value of this object cannot be changed
if the value of the corresponding teTunnelRowStatus
object is 'active'.
"
::= { tePathEntry 2 }
対応するteTunnelRowStatus物の値が'アクティブである'なら、この物の値を変えることができません。 " ::= tePathEntry2
tePathRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The status of this conceptual row.
tePathRowStatus OBJECT-TYPE SYNTAX RowStatusマックス-ACCESSは「これほど概念的の状態はこぐ」STATUSの現在の記述を読書して作成します。
When the value of this object is 'active', then
the value of tePathName cannot be changed. All
other writable objects may be changed; however,
these changes may affect traffic going over the TE
tunnel or require the path to be computed and/or
re-signaled.
"
::= { tePathEntry 3 }
この物の値が'アクティブである'と、tePathNameの値を変えることができません。 他のすべての書き込み可能な物を変えるかもしれません。 しかしながら、これらの変化は、TEトンネルを調べる交通のふりをするか、または経路が計算される、そして/または、再合図されるのを必要とするかもしれません。 " ::= tePathEntry3
tePathStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The storage type for this conceptual row.
tePathStorageType OBJECT-TYPE SYNTAX StorageTypeマックス-ACCESSは「これに、概念的な格納タイプはこぐ」STATUSの現在の記述を読書して作成します。
Conceptual rows having the value 'permanent' need
not allow write-access to any columnar objects
in the row.
"
'永久的'に値を持っている概念的な列は列にいずれにもアクセスを書いている円柱状の物を許容する必要はありません。 "
Kompella Standards Track [Page 21] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[21ページ]。
::= { tePathEntry 4 }
::= tePathEntry4
tePathType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
primary(2),
standby(3),
secondary(4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The type for this PathEntry; i.e., whether this path
is a primary path, a standby path, or a secondary
path.
"
::= { tePathEntry 5 }
tePathType OBJECT-TYPE SYNTAX INTEGER、他の(1)、予備選挙(2)、予備(3)、マックス-ACCESSがSTATUS現在に読書して作成する二次(4)、記述、「このPathEntryのためのタイプ」。 すなわち、この経路が第一の経路、予備経路、または二次経路であることにかかわらず。 " ::= tePathEntry5
tePathConfiguredRoute OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The route that this TE path is configured to follow;
i.e., an ordered list of hops. The value of this
object gives the primary index into the Hop Table.
The secondary index is the hop count in the path, so
to get the route, one could get the first hop with
index <tePathConfiguredRoute, 1> in the Hop Table
and do a getnext to get subsequent hops.
"
::= { tePathEntry 6 }
tePathConfiguredRoute OBJECT-TYPE SYNTAX Unsigned32マックス-ACCESSはSTATUSの現在の記述を読書して作成します。「このTE経路が構成されるルートは従います」。 すなわち、ホップの規則正しいリスト。 この物の値は基本索引をHop Tableに与えます。 二次索引が経路でのホップカウントであるので、ルートを手に入れるなら、1つは、インデックス<tePathConfiguredRoute、Hop Tableの1>で最初のホップを得て、その後のホップを得るためにgetnextをするかもしれません。 " ::= tePathEntry6
tePathBandwidth OBJECT-TYPE
SYNTAX MplsBitRate
UNITS "Kilobits per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The configured bandwidth for this Tunnel,
in units of thousands of bits per second (Kbps).
"
DEFVAL { 0 }
::= { tePathEntry 7 }
tePathBandwidth OBJECT-TYPE SYNTAX MplsBitRate UNITS「1秒あたりのキロビット」マックス-ACCESSはSTATUSの現在の記述を読書して作成します。「ユニットの何千ものbps(キロビット毎秒)におけるこのTunnelのための構成された帯域幅。」 「DEFVAL0:、:、」= tePathEntry7
tePathIncludeAny OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION "This is a configured set of administrative groups
specified as a bit vector (i.e., bit n is 1 if group
tePathIncludeAny OBJECT-TYPE SYNTAX Unsigned32マックス-ACCESSがSTATUSの現在の記述を読書して作成する、「これがしばらくベクトルとして指定された構成されたセットの管理グループである、(グループであるならすなわち、ビットnが1である、」
Kompella Standards Track [Page 22] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[22ページ]。
n is in the set, where n = 0 is the LSB). For each
link that this path goes through, the link must have
at least one of the groups specified in IncludeAny
to be acceptable. If IncludeAny is zero, all links
are acceptable.
"
DEFVAL { 0 }
::= { tePathEntry 8 }
セットにnがある、)。(そこでは、n=0はLSBです)。 この経路が通る各リンクに関しては、リンクで、許容できるためにIncludeAnyで少なくともグループの1つを指定しなければなりません。 IncludeAnyがゼロであるなら、すべてのリンクが許容できます。 「DEFVAL0:、:、」= tePathEntry8
tePathIncludeAll OBJECT-TYPE
tePathIncludeAllオブジェクト・タイプ
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION "This is a configured set of administrative groups
specified as a bit vector (i.e., bit n is 1 if group
n is in the set, where n = 0 is the LSB). For each
link that this path goes through, the link must have
all of the groups specified in IncludeAll to be
acceptable. If IncludeAll is zero, all links are
acceptable.
"
DEFVAL { 0 }
::= { tePathEntry 9 }
SYNTAX Unsigned32マックス-ACCESSはSTATUSの現在の記述を読書して作成します。「これはしばらくベクトルとして指定された構成されたセットの管理グループ(n=0がLSBであるセットにグループnがあるなら、すなわち、ビットnは1です)です」。 この経路が通る各リンクに関しては、リンクで、許容できるためにIncludeAllでグループのすべてを指定しなければなりません。 IncludeAllがゼロであるなら、すべてのリンクが許容できます。 「DEFVAL0:、:、」= tePathEntry9
tePathExclude OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION "This is a configured set of administrative groups
specified as a bit vector (i.e., bit n is 1 if group
n is in the set, where n = 0 is the LSB). For each
link that this path goes through, the link MUST have
groups associated with it, and the intersection of
the link's groups and the 'exclude' set MUST be
null.
"
DEFVAL { 0 }
::= { tePathEntry 10 }
tePathExclude OBJECT-TYPE SYNTAX Unsigned32マックス-ACCESSはSTATUSの現在の記述を読書して作成します。「これはしばらくベクトルとして指定された構成されたセットの管理グループ(n=0がLSBであるセットにグループnがあるなら、すなわち、ビットnは1です)です」。 この経路が通る各リンクに関しては、リンクには、それに関連しているグループがなければなりません、そして、リンクのグループと'除外'セットの交差点はヌルであるに違いありません。 「DEFVAL0:、:、」= tePathEntry10
tePathSetupPriority OBJECT-TYPE
SYNTAX Integer32 (0..7)
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The setup priority configured for this path, with 0
as the highest priority and 7 as the lowest.
"
DEFVAL { 7 }
tePathSetupPriority OBJECT-TYPE SYNTAX Integer32(0 .7)マックス-ACCESSは「セットアップ優先権は最優先としての0と最も低いとしての7でこの経路に構成した」STATUSの現在の記述を読書して作成します。 "DEFVAL"{ 7 }
Kompella Standards Track [Page 23] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[23ページ]。
::= { tePathEntry 11 }
::= tePathEntry11
tePathHoldPriority OBJECT-TYPE
SYNTAX Integer32 (0..7)
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The hold priority configured for this path, with 0
as the highest priority and 7 as the lowest.
"
DEFVAL { 0 }
::= { tePathEntry 12 }
tePathHoldPriority OBJECT-TYPE SYNTAX Integer32(0 .7)マックス-ACCESSは「保持優先権は最優先としての0と最も低いとしての7でこの経路に構成した」STATUSの現在の記述を読書して作成します。 「DEFVAL0:、:、」= tePathEntry12
tePathProperties OBJECT-TYPE
SYNTAX BITS {
recordRoute(0),
cspf(1),
makeBeforeBreak(2),
mergeable(3),
fastReroute(4),
protected(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The set of configured properties for this path,
expressed as a bit map. For example, if the path
supports 'make before break', then bit 2 is set.
"
::= { tePathEntry 13 }
マックス-ACCESSはSTATUSの現在の記述を読書して作成します。tePathProperties OBJECT-TYPE SYNTAX BITS、recordRoute(0)、cspf(1)、makeBeforeBreak(2)、mergeable(3)(fastReroute(4))が(5)を保護した、「しばらく地図として言い表されたこの経路への構成された特性のセット。」 例えば、経路が'以前、開閉してください'を支持するなら、ビット2は設定されます。 " ::= tePathEntry13
tePathOperStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
down(1),
testing(2),
dormant(3),
ready(4),
operational(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The operational status of the path:
unknown:
down: Signaling failed.
testing: Administratively set aside for testing.
dormant: Not signaled (for a backup tunnel).
ready: Signaled but not yet carrying traffic.
operational: Signaled and carrying traffic.
"
tePathOperStatus OBJECT-TYPE SYNTAX INTEGER、(1) 眠っている(3)、持ち合わせの(4)、操作上の(5)への(2)をテストして、未知(0)、マックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「経路の操作上の状態:」 未知: 以下より倒してください。 シグナリングは. テストに失敗しました: テストするために行政上かたわらに置いてください、眠っている: 合図されない、(バックアップトンネルへの) . 準備ができる: 合図されましたが、まだ運んでいない交通操作上: 合図されて、交通を運びます。 "
Kompella Standards Track [Page 24] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[24ページ]。
::= { tePathEntry 14 }
::= tePathEntry14
tePathAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
normal(1),
testing(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The operational status of the path:
normal: Used normally for forwarding.
testing: Administratively set aside for testing.
"
::= { tePathEntry 15 }
tePathAdminStatus OBJECT-TYPE SYNTAX INTEGER、標準(1)、マックス-ACCESSがSTATUS現在に読書して作成するテスト(2)、記述、「経路の操作上の状態:」 標準: 通常. テストを進めるのに中古: テストするために行政上かたわらに置いてください。 " ::= tePathEntry15
tePathComputedRoute OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The route computed for this path, perhaps using
some form of Constraint-based Routing. The
algorithm is implementation dependent.
「恐らく何らかの形式のConstraintベースのルート設定を使用して、ルートはこの経路に計算した」tePathComputedRoute OBJECT-TYPE SYNTAX Unsigned32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 アルゴリズムは実現に依存しています。
This object returns the computed route as an ordered
list of hops. The value of this object gives the
primary index into the Hop Table. The secondary
index is the hop count in the path, so to get the
route, one could get the first hop with index
<tePathComputedRoute, 1> in the Hop Table and do a
getnext to get subsequent hops.
この物はホップの規則正しいリストとして計算されたルートを返します。 この物の値は基本索引をHop Tableに与えます。 二次索引が経路でのホップカウントであるので、ルートを手に入れるなら、1つは、インデックス<tePathComputedRoute、Hop Tableの1>で最初のホップを得て、その後のホップを得るためにgetnextをするかもしれません。
A value of zero (0) means there is no computedRoute.
"
::= { tePathEntry 16 }
(0)がない値は、computedRouteが全くないことを意味します。 " ::= tePathEntry16
tePathRecordedRoute OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The route actually used for this path, as recorded
by the signaling protocol. This is again an ordered
list of hops; each hop is expected to be strict.
「ルートはこの経路に実際にシグナリングプロトコルによって記録されるように使用した」tePathRecordedRoute OBJECT-TYPE SYNTAX Unsigned32のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 再び、これはホップの規則正しいリストです。 各ホップが厳しいと予想されます。
The value of this object gives the primary index
into the Hop Table. The secondary index is the hop
count in the path, so to get the route, one can get
the first hop with index <tePathRecordedRoute, 1>
in the Hop Table and do a getnext to get subsequent
この物の値は基本索引をHop Tableに与えます。 二次索引が経路でのホップカウントであるので、ルートを手に入れるなら、1つは、インデックス<tePathRecordedRoute、Hop Tableの1>で最初のホップを得て、その後になるようにgetnextができます。
Kompella Standards Track [Page 25] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[25ページ]。
hops.
ホップ。
A value of zero (0) means there is no recordedRoute.
"
::= { tePathEntry 17 }
(0)がない値は、recordedRouteが全くないことを意味します。 " ::= tePathEntry17
-- **************************************************************** -- -- Tunnel Path Hop Table --
-- トンネルを堀る..経路..ホップ..テーブル
tePathHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF TePathHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Table of Tunnel Path Hops."
::= { teMIBObjects 4 }
「トンネル経路のテーブルは飛び越す」tePathHopTable OBJECT-TYPE SYNTAX SEQUENCE OF TePathHopEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 ::= teMIBObjects4
tePathHopEntry OBJECT-TYPE
SYNTAX TePathHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Entry containing information about a particular
hop.
"
INDEX { teHopListIndex, tePathHopIndex }
::= { tePathHopTable 1 }
tePathHopEntry OBJECT-TYPE SYNTAX TePathHopEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「特定のホップの情報を含むエントリー。」 「teHopListIndex、tePathHopIndexに索引をつけてください:、:、」= tePathHopTable1
TePathHopEntry ::=
SEQUENCE {
teHopListIndex Unsigned32,
tePathHopIndex Unsigned32,
-- Conceptual row information
tePathHopRowStatus RowStatus,
tePathHopStorageType StorageType,
tePathHopAddrType TeHopAddressType,
tePathHopAddress TeHopAddress,
tePathHopType INTEGER
}
TePathHopEntry:、:= 系列teHopListIndex Unsigned32、tePathHopIndex Unsigned32--概念的な列の情報tePathHopRowStatus RowStatus、tePathHopStorageType StorageType、tePathHopAddrType TeHopAddressType、tePathHopAddress TeHopAddress、tePathHopType INTEGER
teHopListIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An index that identifies a list of hops. This is
the primary index to access hops.
"
::= { tePathHopEntry 1 }
teHopListIndex OBJECT-TYPE SYNTAX Unsigned32(1 .4294967295)のマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「ホップのリストを特定するインデックス。」 これはホップにアクセスする基本索引です。 " ::= tePathHopEntry1
Kompella Standards Track [Page 26] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[26ページ]。
tePathHopIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An index that identifies a particular hop among the
list of hops for a path. An index of i identifies
the ith hop. This is the secondary index for a hop
entry.
"
::= { tePathHopEntry 2 }
tePathHopIndex OBJECT-TYPE SYNTAX Unsigned32(1 .4294967295)のマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「ホップのリストの中で特定のホップを経路に特定するインデックス。」 iのインデックスはithホップを特定します。 これはホップエントリーへの二次索引です。 " ::= tePathHopEntry2
tePathHopRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The status of this conceptual row.
tePathHopRowStatus OBJECT-TYPE SYNTAX RowStatusマックス-ACCESSは「これほど概念的の状態はこぐ」STATUSの現在の記述を読書して作成します。
Any field in this table can be changed, even if the
value of this object is 'active'. However, such a
change may cause traffic to be rerouted or even
disrupted.
"
::= { tePathHopEntry 3 }
この物の値が'アクティブであっ'ても、このテーブルのどんな分野も変えることができます。 しかしながら、そのような変化は、交通が別ルートで送られるか、または中断するのさえ引き起こすかもしれません。 " ::= tePathHopEntry3
tePathHopStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The storage type for this conceptual row.
tePathHopStorageType OBJECT-TYPE SYNTAX StorageTypeマックス-ACCESSは「これに、概念的な格納タイプはこぐ」STATUSの現在の記述を読書して作成します。
Conceptual rows having the value 'permanent' need
not allow write-access to any columnar objects
in the row.
"
::= { tePathHopEntry 4 }
'永久的'に値を持っている概念的な列は列にいずれにもアクセスを書いている円柱状の物を許容する必要はありません。 " ::= tePathHopEntry4
tePathHopAddrType OBJECT-TYPE
SYNTAX TeHopAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The type of Traffic Engineered Tunnel hop Address
of this hop.
tePathHopAddrType OBJECT-TYPE SYNTAX TeHopAddressTypeマックス-ACCESSは「このTraffic Engineered TunnelホップAddressのタイプは飛び越す」STATUSの現在の記述を読書して作成します。
The value of this object cannot be changed
if the value of the corresponding tePathRowStatus
object is 'active'.
"
::= { tePathHopEntry 5 }
対応するtePathRowStatus物の値が'アクティブである'なら、この物の値を変えることができません。 " ::= tePathHopEntry5
Kompella Standards Track [Page 27] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[27ページ]。
tePathHopAddress OBJECT-TYPE
SYNTAX TeHopAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The Traffic Engineered Tunnel hop Address of this
hop.
tePathHopAddress OBJECT-TYPE SYNTAX TeHopAddressマックス-ACCESSは「このTraffic Engineered TunnelホップAddressは飛び越す」STATUSの現在の記述を読書して作成します。
The type of this address is determined by the value
of the corresponding tePathHopAddressType.
このアドレスのタイプは対応するtePathHopAddressTypeの値で決定します。
The value of this object cannot be changed
if the value of the corresponding teTunnelRowStatus
object is 'active'.
"
::= { tePathHopEntry 6 }
対応するteTunnelRowStatus物の値が'アクティブである'なら、この物の値を変えることができません。 " ::= tePathHopEntry6
tePathHopType OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
loose(1),
strict(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The type of hop:
unknown:
loose: This hop is a LOOSE hop.
strict: This hop is a STRICT hop.
"
::= { tePathHopEntry 7 }
tePathHopType OBJECT-TYPE SYNTAX INTEGER、未知(0)、ゆるい(1)、厳しい(2)、マックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「ホップのタイプ:」 未知: ほどけます: このホップがLOOSEホップである、厳しい: このホップはSTRICTホップです。 " ::= tePathHopEntry7
-- **************************************************************** -- -- TE Notifications --
-- Te..通知
teTunnelUp NOTIFICATION-TYPE
OBJECTS { teTunnelName,
tePathName } -- TunnelPath
STATUS current
DESCRIPTION "A teTunnelUp notification is generated when the
Tunnel indexed by teTunnelName transitions to the
'up' state.
teTunnelUp NOTIFICATION-TYPE OBJECTS、teTunnelName、tePathName--、TunnelPath STATUSの現在の記述、「Tunnelが'up'状態へのteTunnelName変遷で索引をつけたとき、teTunnelUp通知は発生します」。
A tunnel is up when at least one of its paths is up.
The tePathName is the name of the path whose
transition to up made the tunnel go up.
少なくとも経路の1つが上がっているとき、トンネルは上がっています。 tePathNameはトンネルが上への変遷で上がった経路の名前です。
Kompella Standards Track [Page 28] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[28ページ]。
This notification MUST be limited to at most one
every minute, in case the tunnel flaps up and down.
"
::= { teMIBNotifications 1 }
トンネルが上下にばたつくといけないので、最も1つの毎分までこの通知を制限しなければなりません。 " ::= teMIBNotifications1
teTunnelDown NOTIFICATION-TYPE
OBJECTS { teTunnelName,
tePathName } -- TunnelPath
STATUS current
DESCRIPTION "A teTunnelDown notification is generated when the
Tunnel indexed by teTunnelName transitions to the
'down' state.
teTunnelDown NOTIFICATION-TYPE OBJECTS、teTunnelName、tePathName--、TunnelPath STATUSの現在の記述、「Tunnelが'down'状態へのteTunnelName変遷で索引をつけたとき、teTunnelDown通知は発生します」。
A tunnel is up when at least one of its paths is up.
The tePathName is the name of the path whose
transition to down made the tunnel go down.
少なくとも経路の1つが上がっているとき、トンネルは上がっています。 tePathNameはダウンする変遷がトンネルが落ちた経路の名前です。
This notification MUST be limited to at most one
every minute, in case the tunnel flaps up and down.
"
::= { teMIBNotifications 2 }
トンネルが上下にばたつくといけないので、最も1つの毎分までこの通知を制限しなければなりません。 " ::= teMIBNotifications2
teTunnelChanged NOTIFICATION-TYPE
OBJECTS { teTunnelName,
tePathName } -- toTunnelPath
STATUS current
DESCRIPTION "A teTunnelChanged notification is generated when an
active path on the Tunnel indexed by teTunnelName
changes or a new path becomes active. The value
of tePathName is the new active path.
teTunnelChanged NOTIFICATION-TYPE OBJECTS、teTunnelName、tePathName--、toTunnelPath STATUSの現在の記述、「teTunnelName変化によって索引をつけられたTunnelの上のアクティブな経路か新しい経路がアクティブになるとき、teTunnelChanged通知は発生します」。 tePathNameの値は新しいアクティブな経路です。
This notification MUST be limited to at most one
every minute, in case the tunnel changes quickly.
"
::= { teMIBNotifications 3 }
トンネルが急速に変化するといけないので、最も1つの毎分までこの通知を制限しなければなりません。 " ::= teMIBNotifications3
teTunnelRerouted NOTIFICATION-TYPE
OBJECTS { teTunnelName,
tePathName } -- toTunnelPath
STATUS current
DESCRIPTION "A teTunnelRerouted notification is generated when
an active path for the Tunnel indexed by
teTunnelName stays the same, but its route changes.
teTunnelRerouted NOTIFICATION-TYPE OBJECTS、teTunnelName、tePathName--、toTunnelPath STATUSの現在の記述、「teTunnelNameによって索引をつけられたTunnelに、アクティブな経路が同じ状態で残っていると、teTunnelRerouted通知は発生しますが、ルートは変化します」。
This notification MUST be limited to at most one
every minute, in case the tunnel reroutes quickly.
"
::= { teMIBNotifications 4 }
トンネルがすぐにコースを変更するといけないので、最も1つの毎分までこの通知を制限しなければなりません。 " ::= teMIBNotifications4
Kompella Standards Track [Page 29] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[29ページ]。
-- End of TE-MIB objects
-- TE-MIB物の端
-- **************************************************************** -- -- TE Compliance Statements --
-- Te..承諾..声明
teGroups
OBJECT IDENTIFIER ::= { teMIBConformance 1 }
teGroups物の識別子:、:= teMIBConformance1
teModuleCompliance
OBJECT IDENTIFIER ::= { teMIBConformance 2 }
teModuleCompliance物の識別子:、:= teMIBConformance2
-- **************************************************************** -- -- TE object groups --
-- 物..分類
teTrafficEngineeringGroup OBJECT-GROUP
OBJECTS {
teTunnelName,
teTunnelNextPathIndex,
teTunnelRowStatus,
teTunnelStorageType,
teTunnelSourceAddressType,
teTunnelSourceAddress,
teTunnelDestinationAddressType,
teTunnelDestinationAddress,
teTunnelState,
teTunnelDiscontinuityTimer,
teTunnelOctets,
teTunnelPackets,
teTunnelLPOctets,
teTunnelLPPackets,
teTunnelAge,
teTunnelTimeUp,
teTunnelPrimaryTimeUp,
teTunnelTransitions,
teTunnelLastTransition,
teTunnelPathChanges,
teTunnelLastPathChange,
teTunnelConfiguredPaths,
teTunnelStandbyPaths,
teTunnelOperationalPaths,
tePathBandwidth,
tePathIncludeAny,
tePathIncludeAll,
tePathExclude,
teTrafficEngineeringGroup物群対象、teTunnelName、teTunnelNextPathIndex、teTunnelRowStatus、teTunnelStorageType、teTunnelSourceAddressType、teTunnelSourceAddress、teTunnelDestinationAddressType、teTunnelDestinationAddress、teTunnelState、teTunnelDiscontinuityTimer、teTunnelOctets、teTunnelPackets; teTunnelLPOctets、teTunnelLPPackets、teTunnelAge、teTunnelTimeUp、teTunnelPrimaryTimeUp、teTunnelTransitions、teTunnelLastTransition、teTunnelPathChanges、teTunnelLastPathChange、teTunnelConfiguredPaths、teTunnelStandbyPaths、teTunnelOperationalPaths、tePathBandwidth、tePathIncludeAny、tePathIncludeAll、tePathExclude
Kompella Standards Track [Page 30] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[30ページ]。
tePathSetupPriority,
tePathHoldPriority,
tePathProperties,
tePathOperStatus,
tePathAdminStatus,
tePathComputedRoute,
tePathRecordedRoute,
teDistProtocol,
teSignalingProto,
teNotificationEnable,
teNextTunnelIndex,
teNextPathHopIndex,
teAdminGroupName,
teAdminGroupRowStatus,
teConfiguredTunnels,
teActiveTunnels,
tePrimaryTunnels,
tePathName,
tePathType,
tePathRowStatus,
tePathStorageType,
tePathConfiguredRoute,
tePathHopRowStatus,
tePathHopStorageType,
tePathHopAddrType,
tePathHopAddress,
tePathHopType
}
STATUS current
DESCRIPTION "Objects for Traffic Engineering in this MIB module."
::= { teGroups 1 }
tePathSetupPriority、tePathHoldPriority、tePathProperties、tePathOperStatus、tePathAdminStatus、tePathComputedRoute、tePathRecordedRoute、teDistProtocol、teSignalingProto、teNotificationEnable、teNextTunnelIndex、teNextPathHopIndex、teAdminGroupName、teAdminGroupRowStatus、teConfiguredTunnels、teActiveTunnels、tePrimaryTunnels、tePathName、tePathType、tePathRowStatus、tePathStorageType、tePathConfiguredRoute、tePathHopRowStatus、tePathHopStorageType、tePathHopAddrType、tePathHopAddress、tePathHopType 現在の記述が「Traffic EngineeringのためにこのMIBモジュールで反対させる」STATUS。 ::= teGroups1
teNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
teTunnelUp,
teTunnelDown,
teTunnelChanged,
teTunnelRerouted
}
STATUS current
DESCRIPTION "Notifications specified in this MIB module."
::= { teGroups 2 }
teNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS、teTunnelUp、teTunnelDown、teTunnelChanged、teTunnelRerouted、「通知はこのMIBモジュールで指定した」STATUSの現在の記述。 ::= teGroups2
-- **************************************************************** -- -- TE compliance statements -- -- There are four compliance statements: read-only and full
-- 承諾..声明..承諾..声明 書き込み禁止で完全です。
Kompella Standards Track [Page 31] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[31ページ]。
-- compliance for regular TE devices, and read-only and full -- compliance for path computation servers. --
-- そして、通常のTE装置のための承諾である、書き込み禁止と完全--経路計算サーバのための承諾。 --
teModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "When this MIB module is implemented without support
for read-create (i.e., in read-only mode), then such
an implementation can claim read-only compliance.
Such a device can be monitored but cannot be
configured with this MIB module.
"
teModuleReadOnlyCompliance MODULE-COMPLIANCE STATUSの現在の記述、「そして、このMIBモジュールがいつの間、サポートなしで実行されるかがあれほど状態で缶が書き込み禁止承諾であると主張する実現を読書して作成(すなわち、読込み専用モードで)」。 そのような装置をモニターできますが、このMIBモジュールは構成できません。 "
MODULE -- enclosing module, i.e., TE-MIB
MODULE--モジュール、すなわち、TE-MIBを同封すること。
MANDATORY-GROUPS {
teTrafficEngineeringGroup
}
義務的なグループteTrafficEngineeringGroup
GROUP teNotificationGroup
DESCRIPTION "Implementation of this group is optional."
GROUP teNotificationGroup記述、「このグループの実現は任意です」。
OBJECT teNotificationEnable
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teNotificationEnable MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teAdminGroupName
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teAdminGroupName MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teAdminGroupRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teAdminGroupRowStatus SYNTAX RowStatusのアクティブな(1)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelName
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelName MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelRowStatus SYNTAX RowStatusのアクティブな(1)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelStorageType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
Kompella Standards Track [Page 32] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[32ページ]。
OBJECT teTunnelSourceAddressType
SYNTAX TeHopAddressType { ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required. An
implementation is only required to support
IPv4 and IPv6 host addresses."
OBJECT teTunnelSourceAddressType SYNTAX TeHopAddressType、ipv4(1)、ipv6(2)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」 「実現がIPv4とIPv6ホスト・アドレスをサポートするのに必要であるだけです。」
OBJECT teTunnelSourceAddress
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelSourceAddress MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelDestinationAddressType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelDestinationAddressType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelDestinationAddress
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelDestinationAddress MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathName
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathName MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathRowStatus SYNTAX RowStatusのアクティブな(1)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathStorageType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathConfiguredRoute
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathConfiguredRoute MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathBandwidth
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathBandwidth MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathIncludeAny
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathIncludeAny MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
Kompella Standards Track [Page 33] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[33ページ]。
OBJECT tePathIncludeAll
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathIncludeAll MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathExclude
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathExclude MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathSetupPriority
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathSetupPriority MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHoldPriority
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHoldPriority MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathProperties
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathProperties MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathAdminStatus
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathAdminStatus MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHopRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHopRowStatus SYNTAX RowStatusのアクティブな(1)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHopStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHopStorageType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHopAddrType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHopAddrType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHopAddress
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHopAddress MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
::= { teModuleCompliance 1 }
::= teModuleCompliance1
teModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "When this MIB module is implemented with support for
read-create, then the implementation can claim
full compliance. Such devices can be both
teModuleFullCompliance MODULE-COMPLIANCE STATUSの現在の記述、「このMIBモジュールがいつの間、サポートで実行されるか、読書する作成、次に、実現が完全なコンプライアンスを要求できる、」 そのような装置は両方であるかもしれません。
Kompella Standards Track [Page 34] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[34ページ]。
monitored and configured with this MIB module.
"
このMIBモジュールによってモニターされて、構成されます。 "
MODULE -- enclosing module, i.e., TE-MIB
MODULE--モジュール、すなわち、TE-MIBを同封すること。
MANDATORY-GROUPS {
teTrafficEngineeringGroup
}
義務的なグループteTrafficEngineeringGroup
GROUP teNotificationGroup
DESCRIPTION "Implementation of this group is optional."
GROUP teNotificationGroup記述、「このグループの実現は任意です」。
OBJECT teAdminGroupRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION "Support for notInService, createAndWait and
notReady is not required.
"
OBJECT teAdminGroupRowStatus SYNTAX RowStatusのアクティブな(1)WRITE-SYNTAX RowStatus、createAndGo(4)、(6)を破壊してください、記述、「notInService、createAndWait、およびnotReadyのサポートは必要ではありません」。 "
OBJECT teTunnelRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not
required.
"
OBJECT teTunnelRowStatus SYNTAX RowStatus、アクティブな(1)、notInService(2)、WRITE-SYNTAX RowStatus、アクティブな(1)、notInService(2)(createAndGo(4))が(6)を破壊する、記述、「createAndWaitとnotReadyのサポートは必要ではありません」。 "
OBJECT teTunnelSourceAddressType
SYNTAX TeHopAddressType { ipv4(1), ipv6(2) }
DESCRIPTION "Write access is required. An implementation is
only required to support IPv4 and IPv6 host
addresses.
"
OBJECT teTunnelSourceAddressType SYNTAX TeHopAddressType、ipv4(1)、ipv6(2)、記述、「書く、アクセスが必要である、」 実現が、IPv4とIPv6ホスト・アドレスをサポートするのに必要であるだけです。 "
OBJECT tePathRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not
required.
"
OBJECT tePathRowStatus SYNTAX RowStatus、アクティブな(1)、notInService(2)、WRITE-SYNTAX RowStatus、アクティブな(1)、notInService(2)(createAndGo(4))が(6)を破壊する、記述、「createAndWaitとnotReadyのサポートは必要ではありません」。 "
OBJECT tePathHopRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
OBJECT tePathHopRowStatus SYNTAX RowStatus、アクティブな(1)、notInService(2)、WRITE-SYNTAX RowStatus、アクティブな(1)、notInService(2)
Kompella Standards Track [Page 35] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[35ページ]。
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not
required.
"
::= { teModuleCompliance 2 }
createAndGo(4)、(6)を破壊してください。 記述、「createAndWaitとnotReadyのサポートは必要ではありません」。 " ::= teModuleCompliance2
teModuleServerReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "When this MIB module is implemented by a path
computation server without support for read-create
(i.e., in read-only mode), then the implementation
can claim read-only compliance. Such
a device can be monitored but cannot be
configured with this MIB module.
"
teModuleServerReadOnlyCompliance MODULE-COMPLIANCE STATUSの現在の記述、「このMIBモジュールがいつの間、経路計算サーバによってサポートなしで実装されるか、読書する作成(すなわち、読込み専用モードで)、次に、実装が、書き込み禁止が承諾であると主張できる、」 そのようなデバイスをモニターできますが、このMIBモジュールは構成できません。 "
MODULE -- enclosing module, i.e., TE-MIB
MODULE--モジュール、すなわち、TE-MIBを同封すること。
MANDATORY-GROUPS {
teTrafficEngineeringGroup
}
義務的なグループteTrafficEngineeringGroup
GROUP teNotificationGroup
DESCRIPTION "Implementation of this group is optional."
GROUP teNotificationGroup記述、「このグループの実装は任意です」。
OBJECT teNotificationEnable
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teNotificationEnable MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teAdminGroupName
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teAdminGroupName MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teAdminGroupRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teAdminGroupRowStatus SYNTAX RowStatusのアクティブな(1)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelName
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelName MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelRowStatus SYNTAX RowStatusのアクティブな(1)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
Kompella Standards Track [Page 36] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[36ページ]。
OBJECT teTunnelStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelStorageType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelSourceAddressType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required. A path
computation server SHOULD implement all types
of tunnel source address types.
"
OBJECT teTunnelSourceAddressType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」 SHOULDがすべてのタイプのトンネルソースアドレスタイプを実装する経路計算サーバ。 "
OBJECT teTunnelSourceAddress
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelSourceAddress MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelDestinationAddressType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelDestinationAddressType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT teTunnelDestinationAddress
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT teTunnelDestinationAddress MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathName
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathName MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathRowStatus SYNTAX RowStatusのアクティブな(1)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathStorageType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathConfiguredRoute
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathConfiguredRoute MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathBandwidth
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathBandwidth MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
Kompella Standards Track [Page 37] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[37ページ]。
OBJECT tePathIncludeAny
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathIncludeAny MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathIncludeAll
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathIncludeAll MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathExclude
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathExclude MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathSetupPriority
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathSetupPriority MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHoldPriority
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHoldPriority MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathProperties
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathProperties MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathAdminStatus
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathAdminStatus MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHopRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHopRowStatus SYNTAX RowStatusのアクティブな(1)、MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHopStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHopStorageType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHopAddrType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHopAddrType MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
OBJECT tePathHopAddress
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT tePathHopAddress MIN-ACCESS書き込み禁止記述、「書く、アクセスは必要でない、」
::= { teModuleCompliance 3 }
::= teModuleCompliance3
teModuleServerFullCompliance MODULE-COMPLIANCE
teModuleServerFullComplianceモジュールコンプライアンス
Kompella Standards Track [Page 38] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[38ページ]。
STATUS current
DESCRIPTION "When this MIB module is implemented by a path
computation server with support for read-create,
then the implementation can claim full
compliance.
"
STATUSの現在の記述、「このMIBモジュールがいつの間、サポートがある経路計算サーバによって実装されるか、読書する作成、次に、実装が完全なコンプライアンスを要求できる、」 "
MODULE -- enclosing module, i.e., TE-MIB
MANDATORY-GROUPS {
teTrafficEngineeringGroup
}
MODULE--モジュール、すなわち、TE-MIB MANDATORY-GROUPSを同封すること。teTrafficEngineeringGroup
GROUP teNotificationGroup
DESCRIPTION "Implementation of this group is optional."
GROUP teNotificationGroup記述、「このグループの実装は任意です」。
OBJECT teAdminGroupRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION "Support for notInService, createAndWait, and
notReady is not required.
"
OBJECT teAdminGroupRowStatus SYNTAX RowStatusのアクティブな(1)WRITE-SYNTAX RowStatus、createAndGo(4)、(6)を破壊してください、記述、「notInService、createAndWait、およびnotReadyのサポートは必要ではありません」。 "
OBJECT teTunnelRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not
required.
"
OBJECT teTunnelRowStatus SYNTAX RowStatus、アクティブな(1)、notInService(2)、WRITE-SYNTAX RowStatus、アクティブな(1)、notInService(2)(createAndGo(4))が(6)を破壊する、記述、「createAndWaitとnotReadyのサポートは必要ではありません」。 "
OBJECT teTunnelSourceAddressType
DESCRIPTION "Write access is required. An implementation
of a path computation server SHOULD support all
types of tunnel source address types.
"
OBJECT teTunnelSourceAddressType記述、「書く、アクセスが必要である、」 トンネルソースアドレスのすべてのタイプがタイプする経路計算サーバSHOULDサポートの実装。 "
OBJECT tePathRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not
required.
"
OBJECT tePathRowStatus SYNTAX RowStatus、アクティブな(1)、notInService(2)、WRITE-SYNTAX RowStatus、アクティブな(1)、notInService(2)(createAndGo(4))が(6)を破壊する、記述、「createAndWaitとnotReadyのサポートは必要ではありません」。 "
OBJECT tePathHopRowStatus
オブジェクトtePathHopRowStatus
Kompella Standards Track [Page 39] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[39ページ]。
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not
required.
"
::= { teModuleCompliance 4 }
SYNTAX RowStatus、アクティブな(1)、notInService(2)、WRITE-SYNTAX RowStatus、アクティブな(1)、notInService(2)(createAndGo(4))が(6)を破壊する、記述、「createAndWaitとnotReadyのサポートは必要ではありません」。 " ::= teModuleCompliance4
END
終わり
6. References
6. 参照
6.1. Normative References
6.1. 引用規格
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[1] ブラドナー、S.、「Indicate Requirement LevelsへのRFCsにおける使用のためのキーワード」、BCP14、RFC2119、1997年3月。
[2] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[2]McCloghrie、K.、パーキンス、D.、およびJ.Schoenwaelder、「経営情報バージョン2(SMIv2)の構造」、STD58、RFC2578(1999年4月)。
[3] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[3]McCloghrieとK.とパーキンス、D.とJ.Schoenwaelder、「SMIv2"、STD58、RFC2579、1999年4月の原文のコンベンション。」
[4] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[4]McCloghrieとK.とパーキンス、D.とJ.Schoenwaelder、「SMIv2"、STD58、RFC2580、1999年4月のための順応声明。」
[5] Nadeau, T. and J. Cucchiara, "Definitions of Textual Conventions
(TCs) for Multiprotocol Label Switching (MPLS) Management", RFC
3811, June 2004.
[5] ナドー、T.、およびJ.Cucchiara、「Multiprotocolのための原文のコンベンション(TCs)の定義は切り換え(MPLS)を管理とラベルします」、RFC3811、2004年6月。
[6] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing Simple Network Management Protocol (SNMP) Management
Frameworks", STD 62, RFC 3411, December 2002.
[6] ハリントン、D.、Presuhn、R.、およびB.Wijnen、「簡単なネットワーク管理プロトコル(SNMP)管理フレームワークについて説明するためのアーキテクチャ」、STD62、RFC3411(2002年12月)。
[7] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J.
McManus, "Requirements for Traffic Engineering Over MPLS", RFC
2702, September 1999.
[7]AwducheとD.とマルコムとJ.とAgogbuaとJ.とオデル、M.とJ.マクマナス、「MPLSの上の交通工学のための要件」RFC2702(1999年9月)。
6.2. Informative References
6.2. 有益な参照
[8] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G.
Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC
3209, December 2001.
[8] Awduche、D.、バーガー、L.、ガン、D.、李、T.、Srinivasan、V.、およびG.が飲み込まれる、「RSVP-Te:」 「LSP TunnelsのためのRSVPへの拡大」、RFC3209、2001年12月。
Kompella Standards Track [Page 40] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[40ページ]。
[9] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction
and Applicability Statements for Internet-Standard Management
Framework", RFC 3410, December 2002.
[9] ケース、J.、マンディ、R.、パーテイン、D.、およびB.スチュワート、「インターネット標準の管理フレームワークのための序論と適用性声明」、RFC3410(2002年12月)。
[10] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB",
RFC 2863, June 2000.
[10]McCloghrieとK.とF.Kastenholz、「インタフェースはMIBを分類する」RFC2863、2000年6月。
[11] Thaler, D., "IP Tunnel MIB", RFC 2667, August 1999.
D.、「IPトンネルMIB」、RFC2667 1999年8月の[11]ターレル。
[12] Jamoussi, B., Andersson, L., Callon, R., Dantu, R., Wu, L.,
Doolan, P., Worster, T., Feldman, N., Fredette, A., Girish, M.,
Gray, E., Heinanen, J., Kilty, T., and A. Malis, "Constraint-
Based LSP Setup using LDP", RFC 3212, January 2002.
[12]Jamoussi、B.、アンデション、L.、Callon、R.、Dantu、R.、ウー、L.、Doolan、P.、オースター、T.、フェルドマン、N.、Fredette、A.、Girish、M.、グレー、E.、Heinanen、J.、Kilty、T.、およびA.Malis、「規制は自由民主党を使用することでLSPセットアップを基礎づけました」、RFC3212、2002年1月。
7. Security Considerations
7. セキュリティ問題
This MIB module relates to the configuration and management of Traffic Engineering tunnels. The unauthorized manipulation of fields in the tables teAdminGroupTable, teTunnelTable, tePathTable, and tePathHopTable may lead to tunnel flapping, tunnel paths being changed, or traffic being disrupted. In addition, if these tables are read by unauthorized parties, the information can be used to trace traffic patterns, traffic volumes, and tunnel paths. This may be considered proprietary and confidential information by some providers.
このMIBモジュールはTraffic Engineeringトンネルの構成と管理に関連します。 テーブルのteAdminGroupTable、teTunnelTable、tePathTable、およびtePathHopTableでの分野の権限のない操作はトンネルのばたつくこと、変えられるトンネル経路、または混乱させられるトラフィックにつながるかもしれません。 さらに、これらのテーブルが権限のないパーティーによって読まれるなら、トラフィック・パターン、交通量、およびトンネル経路をたどるのに情報を使用できます。 これはいくつかのプロバイダーによって独占で秘密の情報であると考えられるかもしれません。
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
aがあります。読書して書くことのマックス-ACCESS節でこのMIBモジュールで定義された管理オブジェクトに付番する、そして/または、読書して作成します。 そのようなオブジェクトはいくつかのネットワーク環境で敏感であるか、または被害を受け易いと考えられるかもしれません。 適切な保護のない非安全な環境におけるSET操作のサポートはネットワーク操作のときにマイナスの影響がある場合があります。 これらは、テーブルと、オブジェクトとそれらの感度/脆弱性です:
teAdminGroupTable: Changing this will affect the semantics of include and exclude constraints, and thus traffic takes unintended routes.
teAdminGroupTable: これが意味論に影響する変化は、規制を含んで、除きます、そして、その結果、トラフィックは故意でないルートを取ります。
teTunnelTable: Changing this affects many properties of traffic tunnels.
teTunnelTable: これを変えると、トラフィックトンネルの多くの特性が影響されます。
tePathTable: Changing this affects the constraints (including bandwidth) of tunnel paths, as well as the status of the path.
tePathTable: これを変えると、トンネル経路の規制(帯域幅を含んでいる)、および経路の状態は影響されます。
tePathHopTable: Changing this affects the route followed by a traffic tunnel path.
tePathHopTable: これを変えると、ルートは影響されます、続いて、トラフィックトンネル経路に影響します。
Kompella Standards Track [Page 41] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[41ページ]。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
このMIBモジュール(すなわち、アクセスしやすくないのを除いたマックス-ACCESSがあるオブジェクト)によるいくつかの読み込み可能なオブジェクトがいくつかのネットワーク環境で敏感であるか、または被害を受け易いと考えられるかもしれません。 SNMPを通してネットワークの上にそれらを送るとき、その結果、GET、そして/または、これらのオブジェクトへのNOTIFYアクセスさえ制御して、ことによるとこれらのオブジェクトの値を暗号化するのさえ重要です。 これらは、テーブルと、オブジェクトとそれらの感度/脆弱性です:
teTunnelTable: Describes tunnel endpoints and traffic volumes.
tePathTable: Describes path properties.
tePathHopTable: Describes path routes.
teTunnelTable: トンネル終点と交通量tePathTableは説明します: 経路の特性tePathHopTableは説明します: 経路ルートを説明します。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3の前のSNMPバージョンは十分な安全性を含んでいませんでした。 ネットワーク自体が安全であっても(例えば、IPSecを使用するのによる)、その時でさえ、アクセスとGET/SET(読むか、変える、作成する、または削除する)へのオブジェクトが安全なネットワークにこのMIBモジュールでだれに許容されているかに関してコントロールが全くありません。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [9], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
implementersがSNMPv3フレームワークで提供するようにセキュリティ機能を考えるのは([9]を見てください、セクション8)、RECOMMENDEDです、SNMPv3の暗号のメカニズム(認証とプライバシーのための)の全面的な支援を含んでいて。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
さらに、SNMPv3の前のSNMPバージョンの展開はNOT RECOMMENDEDです。 代わりに、それはSNMPv3を配布して、暗号のセキュリティを可能にするRECOMMENDEDです。 そして、このMIBモジュールのインスタンスへのアクセスを与えるSNMP実体が本当にGETに正当な権利を持っている校長(ユーザ)をそれらだけへのオブジェクトへのアクセスに与えるか、または(変えるか、作成する、または削除します)それらをSETに与えるために適切に構成されるのを保証するのは、顧客/オペレータ責任です。
Acknowledgments
承認
It was Tony Li's suggestion that the author embark on this MIB. Many thanks to him and to Der-Hwa Gan for their input and help.
作者がこのMIBを始めるのは、トニー・李の提案でした。 彼らの入力のために彼と、そして、Der-Hwaガンをありがとうございます、助けてください。
Many thanks, too, to Bert Wijnen for his incredible help, both with improving the correctness, structure, and readability of the MIB module, and with the text of the RFC. Thanks also to Adrian Farrel for his detailed review.
また、MIBモジュールの正当性を改良して、構造と、読み易さ、およびRFCのテキストがある彼の信じられないご協力のためにバートWijnenをありがとうございます。 また、彼の詳細なレビューをエードリアン・ファレルをありがとうございます。
Kompella Standards Track [Page 42] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[42ページ]。
Author's Address
作者のアドレス
Kireeti Kompella Juniper Networks, Inc. 1194 N. Mathilda Ave Sunnyvale, CA 94089
Kireeti Kompella杜松はInc.1194N.マチルダ・Aveサニーベル、カリフォルニア 94089をネットワークでつなぎます。
EMail: kireeti@juniper.net
メール: kireeti@juniper.net
Kompella Standards Track [Page 43] RFC 3970 A Traffic Engineering (TE) MIB January 2005
Kompella規格は交通工学(Te)MIB2005年1月にRFC3970を追跡します[43ページ]。
Full Copyright Statement
完全な著作権宣言文
Copyright (C) The Internet Society (2005).
Copyright(C)インターネット協会(2005)。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
このドキュメントはBCP78に含まれた権利、ライセンス、および制限を受けることがあります、そして、そこに詳しく説明されるのを除いて、作者は彼らのすべての権利を保有します。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
このドキュメントと「そのままで」という基礎と貢献者、その人が代表する組織で提供するか、または後援されて、インターネット協会とインターネット・エンジニアリング・タスク・フォースはすべての保証を放棄します、と急行ORが含意したということであり、他を含んでいて、ここに含まれて、情報の使用がここに侵害しないどんな保証も少しもまっすぐになるという情報か市場性か特定目的への適合性のどんな黙示的な保証。
Intellectual Property
知的所有権
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETFはどんなIntellectual Property Rightsの正当性か範囲、実装に関係すると主張されるかもしれない他の権利、本書では説明された技術の使用またはそのような権利の下におけるどんなライセンスも利用可能であるかもしれない、または利用可能でないかもしれない範囲に関しても立場を全く取りません。 または、それはそれを表しません。どんなそのような権利も特定するどんな独立している取り組みも作りました。 BCP78とBCP79でIETF Documentsの権利に関するIETFの手順に関する情報を見つけることができます。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
IPR公開のコピーが利用可能に作られるべきライセンスの保証、または一般的な免許を取得するのが作られた試みの結果をIETF事務局といずれにもしたか、または http://www.ietf.org/ipr のIETFのオンラインIPR倉庫からこの仕様のimplementersかユーザによるそのような所有権の使用のために許可を得ることができます。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org.
IETFはこの規格を実装するのに必要であるかもしれない技術をカバーするかもしれないどんな著作権もその注目していただくどんな利害関係者、特許、特許出願、または他の所有権も招待します。 ietf ipr@ietf.org のIETFに情報を扱ってください。
Acknowledgement
承認
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC Editor機能のための基金は現在、インターネット協会によって提供されます。
Kompella Standards Track [Page 44]
Kompella標準化過程[44ページ]
一覧
スポンサーリンク
