rfc3371.txt
来自「RFC 的详细文档！」· 文本 代码 · 共 1,749 行 · 第 1/5 页
TXT
1,749 行
1 0
2 1
3 2
4 2
5 2
6 2
7 3
7 4
L2TP Access Concentrator (LAC) tunnel interfaces on the other hand
appear at the top of the interface layering stack. In this case the
layering model is as described in [RFC2667].
However in order to support the tunneling of packets received from
interfaces carrying framed PPP packets on the LAC to the LNS (and the
propagation of decapsulated PPP packets to that interface) additional
configuration is required. This is further described in section 3.4.
3.1.2 Interface MIB Objects
Except where noted in the tables below, all objects MUST be supported
from the ifGeneralInformationGroup and one of the following three
groups:
o ifPacketGroup OR
o ifHCPacketGroup OR
o ifVHCPacketGroup
depending on the particular implementation.
The following tables describe how objects from the
ifGeneralInformationGroup and ifPacketGroup (similar support should
be provided for the high and very high capacity packet groups) are to
be interpreted and supported for L2TP tunnel interfaces.
3.1.2.1 L2TP Tunnel Interfaces
All Interface MIB objects not listed in the above groups for L2TP
tunnel interfaces MUST be supported as described in [RFC2863].
Caves, et. al. Standards Track [Page 7]
RFC 3371 L2TP Management Information Base August 2002
Interface MIB Object Support Description
==================== ========================================
ifTable.ifDescr Refer to the Interface MIB.
ifTable.ifType tunnel(131).
ifTable.ifMtu Dependent on the tunnel transport layer.
For UDP/IP transports the MTU should
be 65467 (65535-60(IP)-8(UDP)).
ifTable.ifSpeed Return zero.
ifTable.ifPhyAddress The assigned tunnel identifier.
ifTable.ifAdminStatus Setting ifAdminStatus to 'up' injects a
'Local Open' request into the tunnel FSM.
Setting ifAdminStatus to 'down' injects
a 'Tunnel Close' event into the tunnel
FSM. Setting ifAdminStatus to 'testing'
is not currently defined but could be
used to test tunnel connectivity.
ifTable.ifOperStatus ifOperStatus values are to be interpreted
as follows:
'up' - tunnel is established.
'down' - administratively down
or peer unreachable.
'testing' - in some test mode.
'unknown' - status cannot be
determined for some
reason.
'dormant' - operational but
waiting for local or
remote trigger to bring
up the tunnel.
'notPresent' - configuration missing.
'lowerLayerDown' - down due to state of
lower-layer
interface(s).
ifTable.ifInOctets The total number of octets received on the
tunnel including control and payload
octets.
ifTable.ifInUcastPkts The total number of packets received on
the tunnel including control and payload
packets.
Caves, et. al. Standards Track [Page 8]
RFC 3371 L2TP Management Information Base August 2002
ifTable.ifInDiscards The total number of received packets that
were discarded on both control and payload
channels.
ifTable.ifInErrors The total number of packets received in
error including control and payload
packets.
ifTable.ifInUnknownProtos
Return zero.
ifTable.ifOutOctets The total number of octets transmitted
from the tunnel including control and
payload octets.
ifTable.ifOutUcastPkts The total number of packets transmitted
from the tunnel including control and
payload packets.
ifTable.ifOutDiscards The total number of discarded packets that
were requested to be transmitted including
control and payload packets.
ifTable.ifOutErrors The total number of packets that were
requested to be transmitted that were in
error including control and payload
packets.
ifXTable.ifName Refer to the Interface MIB.
ifXTable.ifInMulticastPkts
Return zero.
ifXTable.ifInBroadcastPkts
Return zero.
ifXTable.ifOutMulticastPkts
Return zero.
ifXTable.ifOutBroadcastPkts
Return zero.
ifXTable.ifOutBroadcastPkts
Return zero.
ifXTable.ifLinkUpDownTrapEnable
Default set to enabled(1).
Caves, et. al. Standards Track [Page 9]
RFC 3371 L2TP Management Information Base August 2002
ifXTable.ifHighSpeed Return zero.
ifXTable.ifPromiscuousMode
Set to false(2).
ifXTable.ifConnectorPresent
Set to false(2).
3.2 Relationship to other MIBs
3.2.1 Relationship to the IP Tunnel MIB
The IP Tunnel MIB [RFC2667] describes tunnel interfaces that have an
ifType of tunnel(131). The IP Tunnel MIB is considered to contain a
collection of objects common to all IP tunneling protocols, including
L2TP. In addition to the IP Tunnel MIB, tunnel encapsulation
specific MIBs (like this MIB) extend the IP Tunnel MIB to further
describe encapsulation specific information. Implementation of the
IP Tunnel MIB is required for L2TP tunnels over IP.
3.3 L2TP Tunnel Creation
Tunnel creation is detailed for tunnels over IP in the IP Tunnel MIB.
The creation of a tunnelIfEntry in [RFC2667] when the encapsulation
method is "l2tp" will have the side effect of creating entries in the
l2tpTunnelConfigTable, l2tpTunnelStatsTable and the
l2tpUdpStatsTable's.
The creation of L2TP tunnel interfaces over transports other than IP
is expected to be defined in the MIB definition for that specific
L2TP tunnel transport.
3.4 L2TP Session Mapping
The l2tpSessionMapTable table allows management applications to
determine which session within a tunnel a particular interface
(either a PPP or DS0 interface) is mapped to. On the LAC it also
provides a management application the ability to map a particular
physical or virtual interface terminating a PPP link to a particular
L2TP tunnel. This is required since the interface stacking as
performed (and instrumented by the ifStackTable) on the LNS cannot be
applied at the LAC.
Caves, et. al. Standards Track [Page 10]
RFC 3371 L2TP Management Information Base August 2002
The following diagram illustrates the conceptual binding that occurs.
+---------------------------------------+
| L2TP Session Map Database |
+----------+-----------------+----------+
| |
+---+---+ +-----+------+
| ds0 | | Tunnel I/F |
+---+---+ +-----+------+
| |
+---+---+ +-----+------+
| ds1 | | Ethernet |
+-------+ +------------+
The stacking of the individual interface stacks would be described by
the ifStackTable.
4.0 L2TP Object Definitions
L2TP-MIB DEFINITIONS ::= BEGIN
IMPORTS
Integer32, Unsigned32, Counter32, Gauge32,
Counter64, transmission, MODULE-IDENTITY,
OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TruthValue,
StorageType
FROM SNMPv2-TC
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InterfaceIndex
FROM IF-MIB;
l2tp MODULE-IDENTITY
LAST-UPDATED "200208230000Z" -- 23 August 2002
ORGANIZATION "IETF L2TP Working Group"
CONTACT-INFO
"Evan Caves
Postal: Occam Networks
77 Robin Hill Road
Santa Barbara, CA, 93117
Tel: +1 805692 2900
Email: evan@occamnetworks.com
Pat R. Calhoun
Caves, et. al. Standards Track [Page 11]
RFC 3371 L2TP Management Information Base August 2002
Postal: Black Storm Networks
110 Nortech Parkway
San Jose, CA, 95143
Tel: +1 408 941-0500
Email: pcalhoun@bstormnetworks.com
Ross Wheeler
Postal: DoubleWide Software, Inc.
2953 Bunker Hill Lane
Suite 101
Santa Clara, CA 95054
Tel: +1 6509260599
Email: ross@doublewidesoft.com
Layer Two Tunneling Protocol Extensions WG
Working Group Area: Internet
Working Group Name: l2tpext
General Discussion: l2tp@l2tp.net"
DESCRIPTION
"The MIB module that describes managed objects of
general use by the Layer Two Transport Protocol."
-- revision log
REVISION "200208230000Z" -- 23 August 2002
DESCRIPTION
"First revision, published as RFC 3371."
::= { transmission 95 }
--
-- Textual Conventions
--
L2tpMilliSeconds ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-3"
STATUS current
DESCRIPTION
"A period of time measured in units of .001 of seconds
when used in conjunction with the DISPLAY-HINT will
show seconds and fractions of second with a resolution
of .001 of a second."
SYNTAX Integer32 (0..2147483646)
--
-- Definitions of significant branches
--
Caves, et. al. Standards Track [Page 12]
RFC 3371 L2TP Management Information Base August 2002
l2tpNotifications OBJECT IDENTIFIER ::= { l2tp 0 }
l2tpObjects OBJECT IDENTIFIER ::= { l2tp 1 }
l2tpTransports OBJECT IDENTIFIER ::= { l2tp 3 }
l2tpConformance OBJECT IDENTIFIER ::= { l2tp 4 }
--
-- Definitions of significant branches under l2tpObjects
--
l2tpScalar OBJECT IDENTIFIER ::= { l2tpObjects 1 }
l2tpConfig OBJECT IDENTIFIER ::= { l2tpScalar 1 }
l2tpStats OBJECT IDENTIFIER ::= { l2tpScalar 2 }
--
-- Definitions of significant branches under l2tpTransports
--
-- Note that future transports of L2TP (e.g.: Frame relay)
-- should create their own branch under l2tpTransports.
l2tpTransportIpUdp OBJECT IDENTIFIER ::= { l2tpTransports 1 }
l2tpIpUdpObjects OBJECT IDENTIFIER ::= { l2tpTransportIpUdp 1 }
l2tpIpUdpTraps OBJECT IDENTIFIER ::= { l2tpTransportIpUdp 2 }
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?