draft-ietf-lisp-mib-09.txt   draft-ietf-lisp-mib-10.txt 
Network Working Group G. Schudel Network Working Group G. Schudel
Internet-Draft A. Jain Internet-Draft cisco Systems
Intended status: Experimental V. Moreno Intended status: Experimental A. Jain
Expires: August 8, 2013 cisco Systems Expires: November 23, 2013 Juniper Networks
February 4, 2013 V. Moreno
cisco Systems
May 22, 2013
LISP MIB LISP MIB
draft-ietf-lisp-mib-09 draft-ietf-lisp-mib-10
Abstract Abstract
This document defines managed objects for the Locator/ID Separation This document defines managed objects for the Locator/ID Separation
Protocol (LISP). These objects provide information useful for Protocol (LISP). These objects provide information useful for
monitoring LISP devices, including basic configuration information, monitoring LISP devices, including determining basic LISP
LISP status, and operational statistics. configuration information, LISP functional status, and operational
counters and other statistics.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 8, 2013. This Internet-Draft will expire on November 23, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 11 skipping to change at page 2, line 14
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 6 5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 4
6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 6 6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 5
6.1. Overview of Defined Notifications . . . . . . . . . . . . 6 6.1. Overview of Defined Notifications . . . . . . . . . . . . 5
6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 7 6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 5
7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 8 7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 6
8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 63 8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 61
8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 63 8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 61
9. Security Considerations . . . . . . . . . . . . . . . . . . . 63 9. Security Considerations . . . . . . . . . . . . . . . . . . . 61
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62
11.1. Normative References . . . . . . . . . . . . . . . . . . . 64 11.1. Normative References . . . . . . . . . . . . . . . . . . . 62
11.2. Informative References . . . . . . . . . . . . . . . . . . 65 11.2. Informative References . . . . . . . . . . . . . . . . . . 63
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 65 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 64
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 65
1. Requirements Notation 1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
2. Introduction 2. Introduction
skipping to change at page 3, line 42 skipping to change at page 3, line 42
(PETR) functions. The data plane operations of these devices is (PETR) functions. The data plane operations of these devices is
described in [RFC6832]. described in [RFC6832].
From a control plane perspective, LISP employs mechanisms related to From a control plane perspective, LISP employs mechanisms related to
creating, maintaining, and resolving mappings from EIDs to RLOCs. creating, maintaining, and resolving mappings from EIDs to RLOCs.
LISP ITRs, ETRs, PITRs, and PETRs perform specific control plane LISP ITRs, ETRs, PITRs, and PETRs perform specific control plane
functions, and these control plane operations are described in functions, and these control plane operations are described in
[RFC6830]. Additionally, LISP infrastructure devices supporting LISP [RFC6830]. Additionally, LISP infrastructure devices supporting LISP
control plane functionality include Map-Servers and Map-Resolvers, control plane functionality include Map-Servers and Map-Resolvers,
and the control plane operations of these devices are described in and the control plane operations of these devices are described in
[RFC6833]. Finally, while not specifically required, this document [RFC6833].
assumes the existence of a database to store and propagate those
mappings globally.
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 6 skipping to change at page 4, line 4
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
4. Definition of Terms 4. Definition of Terms
Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value This document does not define any new terms. All terms used in this
used in the source and destination address fields of the first document are listed here for completeness; the authoritative
(inner-most) IP header of a LISP packet. A source EID is definition of each term can be found in the definition section of the
allocated to a host from an EID-prefix block associated with the respective, specified reference.
site where the host is located. A host determines a destination
address in the same way that it determines a destination address
today, for example through a DNS lookup or SIP exchange.
Routing Locator (RLOC): a 32-bit (for IPv4) or 128-bit (for IPv6) Endpoint ID (EID): [RFC6830]
value used in the source and destination address fields of the
second (outer-most) IP header of a LISP packet. RLOC addresses
are allocated to an egress tunnel router (ETR) and numbered from
topologically-aggregatable blocks assigned to a site at each point
to which it attaches to the global Internet.
EID-to-RLOC Map-Cache: a short-lived, on-demand table maintained Routing Locator (RLOC): [RFC6830]
locally in an ITR or PITR that stores, tracks, and is responsible
for timing-out and otherwise validating EID-to-RLOC mappings.
This table is distinct from the full "database" of EID-to-RLOC
mappings in that it is dynamic and relatively small. At a given
moment in time, it consists only of entries for those sites to
which the ITR or PITR is currently communicating or has
communicated with within the configured TTL period.
EID-to-RLOC Mapping-Database: a global distributed database that EID-to-RLOC Cache: [RFC6830]
contains all known EID-to-RLOC mappings. Each potential ETR
typically contains a small piece of the database consisting of
only the EID-to-RLOC mappings for the EID prefix(es) for which the
ETR is "authoritative" and the RLOC(s) by which those EID
prefix(es) are reachable from the global Internet.
Ingress Tunnel Router (ITR): a router that accepts an IP packet with EID-to-RLOC Database: [RFC6830]
a single IP header (more precisely, an IP packet that does not
contain a LISP header), treats this "inner" IP destination address
as an EID and performs an EID-to-RLOC mapping lookup, and then
prepends an "outer" IP header with one of its own globally-
routable RLOCs in the source address field and the RLOC resulting
from the mapping lookup in the destination address field. That
is, in general an ITR receives an IP packet from site end-systems
on one side and sends a LISP-encapsulated IP packet toward the
Internet on the other side.
Egress Tunnel Router (ETR): a router that accepts an IP packet where Ingress Tunnel Router (ITR): [RFC6830]
the destination address in the "outer" IP header is one of its own
RLOCs, strips the "outer" header, and forwards the packet based on
the next IP header found. That is, in general an ETR receives
LISP-encapsulated IP packets from the Internet on one side and
sends decapsulated IP packets toward site end-systems on the other
side.
xTR: a term of general reference to an ITR or ETR when direction of Egress Tunnel Router (ETR): [RFC6830]
data flow is not part of the context description. xTR refers to
the router that is the tunnel endpoint and performs both ITR and
ETR functionality. For example, "An xTR can be located at the
Customer Edge (CE) router," meaning both ITR and ETR functionality
is activated at the CE router.
Proxy ITR (PITR): a router that acts like an ITR but does so on xTR: [RFC6830]
behalf of non-LISP sites which send packets to destinations at
LISP sites. The PITR, also known as a PTR, is defined and
described in [RFC6832].
Proxy ETR (PETR): a router that acts like an ETR but does so on Proxy ITR (PITR): [RFC6832]
behalf of LISP sites which send packets to destinations at non-
LISP sites. The PETR is defined and described in [RFC6832].
LISP Site: a set of routers in an edge network that are under a Proxy ETR (PETR): [RFC6832]
single technical administration. LISP routers which reside in the
edge network are the demarcation points to separate the edge
network from the core network.
Map-Server: a LISP network infrastructure component which learns LISP Site: [RFC6830]
EID-to-RLOC mapping entries from an authoritative source such as
an ETR through static configuration, or another out-of-band
mechanism. A Map-Server advertises these mappings into the
distributed mapping database.
Map-Resolver: a LISP network infrastructure component which accepts Map-Server: [RFC6833]
LISP Encapsulated Map-Requests, typically from an ITR, and quickly
determines whether or not the destination IP address is part of
the EID namespace. If it is, the Map-Resolver finds the
appropriate EID-to-RLOC mapping by consulting the distributed
mapping database. If it is not, a Negative Map-Reply is
immediately returned.
Map-Request: a LISP Map-Request message type sent by an ITR or PITR Map-Resolver: [RFC6833]
to a Map-Resolver when it needs a mapping for an EID, wants to
test an RLOC for reachability, or wants to refresh a mapping
before TTL expiration.
Map-Reply: a LISP Map-Reply message type returned in response to a Map-Request: [RFC6833]
Map-Request for a destination EID that exists in the mapping
database and contains the locator-set and associated policy for
the queried EID. Information returned in a Map-Reply is stored in
the EID-to-RLOC Map-Cache.
Negative Map-Reply: a LISP Map-Reply message type that contains an Map-Reply: [RFC6833]
empty locator-set. Returned in response to a Map-Request if the
destination EID does not exist in the mapping database. Negative Map-Reply: [RFC6833]
Typically, this means that the "EID" being requested is an IP
address connected to a non-LISP site. Information returned in a
Negative Map-Reply is stored in the EID-to-RLOC Map-Cache.
5. LISP MIB Objectives 5. LISP MIB Objectives
The objectives for defining this LISP MIB module are as follows: The objectives for this LISP MIB module are to provide a read-only
meachanisms to support the following functions:
o Provide a means for obtaining a list of enabled LISP features and o Provide a means for obtaining an ON/OFF list of LISP features
the current status of configuration attributes related to those configured on a device, and the current status of configuration
features. As an example, LISP capabilities which could be enabled attributes related to those features. As an example, LISP
include ITR, ETR, PITR, PETR, MS or MR support for IPv4 or IPv6 features that could be enabled might include ITR, ETR, PITR, PETR,
address families. Other examples include, indicating whether MS or MR support for IPv4 or IPv6 address families. Other
rloc-probing is enabled, and indicating the configured map-cache examples could include indicating whether rloc-probing is enabled,
limit value. or whether the use of a PETR is enabled. Configuration attributes
related to these features could include the setting of a
configured map-cache limit value, or the setting of a mapping
time-to-live value.
o Provide a means for obtaining the current attributes of various o Provide a means for obtaining the current attributes of various
LISP tables, such as the EID-to-RLOC policy data contained in the LISP tables, such as the EID-to-RLOC policy data contained in the
Map-Cache, or the local EID-to-RLOC policy data contained in the Map-Cache, or the local EID-to-RLOC policy data contained in the
Mapping-Database. Mapping-Database.
o Provide a means for obtaining the current operational statistics o Provide a means for obtaining the current operational statistics
of various LISP functions, such as the number of packets of various LISP functions, such as the number of packets
encapsulated and decapsulated by the device. Other counters of encapsulated and decapsulated by the device. Other counters of
operational interest, depending on LISP function, include things operational interest, depending on LISP function, include things
like the current number of map-cache entries, and the total number like the current number of map-cache entries, and the total number
and rate of map-requests received and sent. and rate of map-requests received and sent by the device.
6. Structure of LISP MIB Module 6. Structure of LISP MIB Module
6.1. Overview of Defined Notifications 6.1. Overview of Defined Notifications
No LISP MIB notifications are defined. No LISP MIB notifications are defined.
6.2. Overview of Defined Tables 6.2. Overview of Defined Tables
The LISP MIB module is composed of the following tables of objects: The LISP MIB module is composed of the following tables of objects:
skipping to change at page 7, line 29 skipping to change at page 6, line 10
lispMappingDatabase - This table represents the EID-to-RLOC database lispMappingDatabase - This table represents the EID-to-RLOC database
that contains the EID-prefix to RLOC mappings configured on an that contains the EID-prefix to RLOC mappings configured on an
ETR. In general, this table would be representative of all such ETR. In general, this table would be representative of all such
mappings for a given site that this device belongs to. mappings for a given site that this device belongs to.
lispMappingDatabaseLocator - This table represents the set of lispMappingDatabaseLocator - This table represents the set of
routing locators contained in the EID-to-RLOC database configured routing locators contained in the EID-to-RLOC database configured
on an ETR. on an ETR.
lispMapCache - This table represents the short-lived, on-demand lispMapCache - This table represents the short-lived, on-demand
table on an ITR that stores, tracks, and is responsible for table maintained on an ITR that stores, tracks, and times-out EID-
timing-out and otherwise validating EID-to-RLOC mappings. to-RLOC mappings.
lispMapCacheLocator - This table represents the set of locators per lispMapCacheLocator - This table represents the set of locators per
EID prefix contained in the map-cache table of an ITR. EID prefix contained in the map-cache table of an ITR.
lispConfiguredLocator - This table represents the set of routing lispConfiguredLocator - This table represents the set of routing
locators configured on a LISP device. locators configured on a LISP device.
lispEidRegistration - This table provides the properties of each EID lispEidRegistration - This table provides the properties of each EID
prefix that is registered with this device when configured to be a prefix that is registered with this device when configured to be a
Map-Server. Map-Server.
skipping to change at page 8, line 31 skipping to change at page 7, line 9
Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC2578] Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC2578]
TruthValue, TEXTUAL-CONVENTION, TruthValue, TEXTUAL-CONVENTION,
TimeStamp FROM SNMPv2-TC -- [RFC2579] TimeStamp FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
MplsL3VpnName MplsL3VpnName
FROM MPLS-L3VPN-STD-MIB -- [RFC4382] FROM MPLS-L3VPN-STD-MIB -- [RFC4382]
AddressFamilyNumbers AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA] FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA]
lispMIB MODULE-IDENTITY lispMIB MODULE-IDENTITY
LAST-UPDATED "201302040000Z" -- 04 February 2013 LAST-UPDATED "201305240000Z" -- 22 May 2013
ORGANIZATION ORGANIZATION
"IETF Locator/ID Separation Protocol (LISP) Working Group" "IETF Locator/ID Separation Protocol (LISP) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: lisp@ietf.org "Email: lisp@ietf.org
WG charter: WG charter:
http://www.ietf.org/html.charters/lisp-charter.html" http://www.ietf.org/html.charters/lisp-charter.html"
DESCRIPTION DESCRIPTION
"Locator/ID Separation Protocol (LISP) MIB Textual "Locator/ID Separation Protocol (LISP) MIB Managed Object
Conventions module. The LISP MIB is intended for module. The LISP MIB is intended for management of LISP
management of LISP routers. devices.
Copyright (C) The IETF Trust (2013)." Copyright (C) The IETF Trust (2013)."
REVISION "201302040000Z" -- 04 February 2013 REVISION "201305240000Z" -- 22 May 2013
DESCRIPTION "Initial version of the IETF LISP-MIB module. Published DESCRIPTION "Initial version of the IETF LISP-MIB module. Published
as RFC xxxx." as RFC xxxx."
-- RFC Ed.: RFC-editor pls fill in xxxx -- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: assigned by IANA, see section 10 for details -- RFC Ed.: assigned by IANA, see section 10 for details
-- --
-- Textual Conventions -- Textual Conventions
-- --
LispAddressType ::= TEXTUAL-CONVENTION LispAddressType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "39a" DISPLAY-HINT "39a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"LISP architecture can be applied to a wide variety of "LISP architecture can be applied to a wide variety of
address-families. This textual-convention is a address-families. This textual-convention is a
generalization for representing addresses that belong to those generalization for representing addresses that belong to
address-families. For convenience, this document refers to any those address-families. For convenience, this document
such address as a LISP address. LispAddressType refers to any such address as a LISP address.
textual-convention consists of the following four-tuple: LispAddressType textual-convention consists of the
following four-tuple:
1. IANA Address Family Number: A field of length 2-octets, 1. IANA Address Family Number: A field of length 2-octets,
whose value is of the form following the assigned whose value is of the form following the assigned
AddressFamilyNumbers textual-convention described in AddressFamilyNumbers textual-convention described in
[IANA]. The enumerations are listed in [IANA]. Note that [IANA]. The enumerations are listed in [IANA]. Note
this list of address family numbers is maintained by IANA. that this list of address family numbers is maintained
by IANA.
2. Length of LISP address: A field of length 1-octet, whose 2. Length of LISP address: A field of length 1-octet, whose
value indicates the octet-length of the next (third) field value indicates the octet-length of the next (third)
of this LispAddressType four-tuple. field of this LispAddressType four-tuple.
3. LISP address: A field of variable length as indicated in 3. LISP address: A field of variable length as indicated in
the previous (second) field, whose value is an address of the previous (second) field, whose value is an address
the IANA Address Family indicated in the first field of of the IANA Address Family indicated in the first field
this LispAddressType four-tuple. Note that any of the of this LispAddressType four-tuple. Note that any of
IANA Address Families can be represented. Particularly the IANA Address Families can be represented.
when the address family is LISP Canonical Address Format Particularly when the address family is LISP Canonical
(LCAF) [LCAF] with IANA assigned Address Family Number Address Format (LCAF) [LCAF] with IANA assigned Address
16387, then the first octet of this field indicates the Family Number 16387, then the first octet of this field
LCAF type, and the rest of this field is same as the indicates the LCAF type, and the rest of this field is
encoding format of the LISP Canonical Address after the same as the encoding format of the LISP Canonical Address
length field, as defined in [LCAF]. after the length field, as defined in [LCAF].
4. Mask-length of address: A field of length 1-octet, whose 4. Mask-length of address: A field of length 1-octet, whose
value is the mask-length to be applied to the LISP value is the mask-length to be applied to the LISP
address specified in the previous (third) field. address specified in the previous (third) field.
To illustrate the use of this object, consider the LISP MIB To illustrate the use of this object, consider the LISP MIB
Object below entitled lispMapCacheEntry. This object begins Object below entitled lispMapCacheEntry. This object begins
with the following entities: with the following entities:
lispMapCacheEntry ::= SEQUENCE { lispMapCacheEntry ::= SEQUENCE {
lispMapCacheEidLength INTEGER, lispMapCacheEidLength INTEGER,
skipping to change at page 10, line 52 skipping to change at page 9, line 32
lispMapCacheEidLength = 11 lispMapCacheEidLength = 11
lispMapCacheEid = 16387, 7, 2, 101, 1, 192.0.2.0, 24 lispMapCacheEid = 16387, 7, 2, 101, 1, 192.0.2.0, 24
... [skip] ... ... [skip] ...
where 11 is the total length in octets of the next object where 11 is the total length in octets of the next object
(lispMapCacheEID of type LispAddressType). Then, the value (lispMapCacheEID of type LispAddressType). Then, the value
16387 indicates the LCAF AF (see [IANA]), the value 7 16387 indicates the LCAF AF (see [IANA]), the value 7
indicates that the LCAF AF is 7-octets in length in this indicates that the LCAF AF is 7-octets in length in this
case, 2 indicates that LCAF Type 2 encoding is used (see case, 2 indicates that LCAF Type 2 encoding is used (see
[LCAF]), 101 gives the Instance ID, 1 gives the AFI (per [LCAF]), 101 gives the Instance ID, 1 gives the AFI (per
[IANA]) for an IPv4 address, 192.0.2.0 is the IPv4 [IANA]) for an IPv4 address, 192.0.2.0 is the IPv4 address,
address, and 24 is the mask-length in bits. Note that the and 24 is the mask-length in bits. Note that the
lispMapCacheEidLength value of 11 octets is used to compute lispMapCacheEidLength value of 11 octets is used to compute
the length of the last field in lispMapCacheEid to be 1 octet, the length of the last field in lispMapCacheEid to be 1 octet,
as computed by 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) = 1." as computed by 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) = 1."
REFERENCE REFERENCE
"RFC6830, Section 14.2, "RFC6830, Section 14.2, draft-ietf-lisp-lcaf-02.txt."
draft-ietf-lisp-lcaf-00.txt."
SYNTAX OCTET STRING (SIZE (5..39)) SYNTAX OCTET STRING (SIZE (5..39))
-- --
-- Top level components of this MIB. -- Top level components of this MIB.
-- --
lispObjects OBJECT IDENTIFIER ::= { lispMIB 1 } lispObjects OBJECT IDENTIFIER ::= { lispMIB 1 }
lispConformance OBJECT IDENTIFIER ::= { lispMIB 2 } lispConformance OBJECT IDENTIFIER ::= { lispMIB 2 }
lispFeaturesTable OBJECT-TYPE lispFeaturesTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispFeaturesEntry SYNTAX SEQUENCE OF LispFeaturesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents the various LISP features "This table represents the ON/OFF status of the
that can be enabled on LISP devices." various LISP features that can be enabled on LISP devices."
REFERENCE REFERENCE
"RFC6830, Section 4.0., Section 5.5., Section 6.3." "RFC6830, Section 4.0., Section 5.5., Section 6.3."
::= { lispObjects 1 } ::= { lispObjects 1 }
lispFeaturesEntry OBJECT-TYPE lispFeaturesEntry OBJECT-TYPE
SYNTAX LispFeaturesEntry SYNTAX LispFeaturesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the lispFeaturesTable." "An entry (conceptual row) in the lispFeaturesTable."
INDEX { lispFeaturesInstanceID, INDEX { lispFeaturesInstanceID,
lispFeaturesAddressFamily } lispFeaturesAddressFamily }
::= { lispFeaturesTable 1 } ::= { lispFeaturesTable 1 }
LispFeaturesEntry ::= SEQUENCE { LispFeaturesEntry ::= SEQUENCE {
lispFeaturesInstanceID Unsigned32, lispFeaturesInstanceID Unsigned32,
lispFeaturesAddressFamily AddressFamilyNumbers, lispFeaturesAddressFamily AddressFamilyNumbers,
lispFeaturesItrEnabled TruthValue, lispFeaturesItrEnabled TruthValue,
lispFeaturesEtrEnabled TruthValue, lispFeaturesEtrEnabled TruthValue,
lispFeaturesProxyItrEnabled TruthValue, lispFeaturesProxyItrEnabled TruthValue,
lispFeaturesProxyEtrEnabled TruthValue, lispFeaturesProxyEtrEnabled TruthValue,
lispFeaturesMapServerEnabled TruthValue, lispFeaturesMapServerEnabled TruthValue,
lispFeaturesMapResolverEnabled TruthValue, lispFeaturesMapResolverEnabled TruthValue,
lispFeaturesMapCacheSize Unsigned32, lispFeaturesMapCacheSize Unsigned32,
lispFeaturesMapCacheLimit Unsigned32, lispFeaturesMapCacheLimit Unsigned32,
lispFeaturesEtrMapCacheTtl Unsigned32, lispFeaturesEtrMapCacheTtl Unsigned32,
lispFeaturesRlocProbeEnabled TruthValue, lispFeaturesRlocProbeEnabled TruthValue,
lispFeaturesEtrAcceptMapDataEnabled TruthValue, lispFeaturesEtrAcceptMapDataEnabled TruthValue,
lispFeaturesEtrAcceptMapDataVerifyEnabled TruthValue, lispFeaturesEtrAcceptMapDataVerifyEnabled TruthValue,
lispFeaturesRouterTimeStamp TimeStamp lispFeaturesRouterTimeStamp TimeStamp
} }
lispFeaturesInstanceID OBJECT-TYPE lispFeaturesInstanceID OBJECT-TYPE
SYNTAX Unsigned32 (0..16777215) SYNTAX Unsigned32 (0..16777215)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This represents the Instance ID of the LISP header. "This represents the Instance ID of the LISP header.
An Instance ID in the LISP address encoding helps An Instance ID in the LISP address encoding helps
uniquely identify the AFI-based address space to which uniquely identify the AFI-based address space to which
a given EID belongs. It's default value is 0." a given EID belongs. It's default value is 0."
::= { lispFeaturesEntry 1 } DEFVAL { 0 }
::= { lispFeaturesEntry 1 }
lispFeaturesAddressFamily OBJECT-TYPE lispFeaturesAddressFamily OBJECT-TYPE
SYNTAX AddressFamilyNumbers SYNTAX AddressFamilyNumbers
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IANA address family number of destination address "The IANA address family number of destination address
of packets that this LISP device is enabled to process." of packets that this LISP device is enabled to process."
::= { lispFeaturesEntry 2 } ::= { lispFeaturesEntry 2 }
lispFeaturesItrEnabled OBJECT-TYPE lispFeaturesItrEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of ITR role on this device. If "Indicates the status of ITR role on this device. If
this object is TRUE, then ITR feature is enabled." this object is TRUE, then ITR feature is enabled."
::= { lispFeaturesEntry 3 } ::= { lispFeaturesEntry 3 }
lispFeaturesEtrEnabled OBJECT-TYPE lispFeaturesEtrEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of ETR role on this device. If "Indicates the status of ETR role on this device. If
this object is TRUE, then ETR feature is enabled." this object is TRUE, then ETR feature is enabled."
::= { lispFeaturesEntry 4 } ::= { lispFeaturesEntry 4 }
lispFeaturesProxyItrEnabled OBJECT-TYPE lispFeaturesProxyItrEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of Proxy-ITR role on this device. "Indicates the status of Proxy-ITR role on this device.
If this object is TRUE, then Proxy-ITR feature is enabled." If this object is TRUE, then Proxy-ITR feature is enabled."
::= { lispFeaturesEntry 5 } ::= { lispFeaturesEntry 5 }
lispFeaturesProxyEtrEnabled OBJECT-TYPE lispFeaturesProxyEtrEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of Proxy-ETR role on this device. "Indicates the status of Proxy-ETR role on this device.
If this object is TRUE, then Proxy-ETR feature is enabled." If this object is TRUE, then Proxy-ETR feature is enabled."
::= { lispFeaturesEntry 6 } ::= { lispFeaturesEntry 6 }
lispFeaturesMapServerEnabled OBJECT-TYPE lispFeaturesMapServerEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of Map Server role on this device. "Indicates the status of Map Server role on this device.
If this object is TRUE, then Map Server feature is If this object is TRUE, then Map Server feature is
enabled." enabled."
::= { lispFeaturesEntry 7 } ::= { lispFeaturesEntry 7 }
lispFeaturesMapResolverEnabled OBJECT-TYPE lispFeaturesMapResolverEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of Map Resolver role on this device. "Indicates the status of Map Resolver role on this device.
If this object is TRUE, then Map Resolver feature is If this object is TRUE, then Map Resolver feature is
enabled." enabled."
::= { lispFeaturesEntry 8 } ::= { lispFeaturesEntry 8 }
lispFeaturesMapCacheSize OBJECT-TYPE lispFeaturesMapCacheSize OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Size of EID-to-RLOC map cache on this device." "Size of EID-to-RLOC map cache on this device."
::= { lispFeaturesEntry 9 } ::= { lispFeaturesEntry 9 }
lispFeaturesMapCacheLimit OBJECT-TYPE lispFeaturesMapCacheLimit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum permissible entries in EID-to-RLOC map cache on "Maximum permissible entries in EID-to-RLOC map cache on
this device." this device."
::= { lispFeaturesEntry 10 } ::= { lispFeaturesEntry 10 }
lispFeaturesEtrMapCacheTtl OBJECT-TYPE lispFeaturesEtrMapCacheTtl OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The stored Record TTL of the EID-to-RLOC map record in "The stored Record TTL of the EID-to-RLOC map record in
the map cache." the map cache."
::= { lispFeaturesEntry 11 } ::= { lispFeaturesEntry 11 }
lispFeaturesRlocProbeEnabled OBJECT-TYPE lispFeaturesRlocProbeEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of rloc-probing feature on this device. "Indicates the status of rloc-probing feature on this
If this object is TRUE, then this feature is enabled." device. If this object is TRUE, then this feature is
::= { lispFeaturesEntry 12 } enabled."
::= { lispFeaturesEntry 12 }
lispFeaturesEtrAcceptMapDataEnabled OBJECT-TYPE lispFeaturesEtrAcceptMapDataEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of accepting piggybacked mapping data "Indicates the status of accepting piggybacked mapping
received in a map-request on this device. If this object is data received in a map-request on this device. If this
TRUE, then this device accepts piggybacked mapping data." object is TRUE, then this device accepts piggybacked
::= { lispFeaturesEntry 13 } mapping data."
::= { lispFeaturesEntry 13 }
lispFeaturesEtrAcceptMapDataVerifyEnabled OBJECT-TYPE lispFeaturesEtrAcceptMapDataVerifyEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the status of verifying accepted piggybacked "Indicates the status of verifying accepted piggybacked
mapping data received in a map-request on this device. If mapping data received in a map-request on this device.
this object is TRUE, then this device verifies accepted If this object is TRUE, then this device verifies
piggybacked mapping data." accepted piggybacked mapping data."
::= { lispFeaturesEntry 14 } ::= { lispFeaturesEntry 14 }
lispFeaturesRouterTimeStamp OBJECT-TYPE lispFeaturesRouterTimeStamp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which LISP feature was enabled "The value of sysUpTime at which LISP feature was
on this device. enabled on this device.
If this information was present at the most recent If this information was present at the most recent
re-initialization of the local management subsystem, re-initialization of the local management subsystem,
then this object contains a zero value." then this object contains a zero value."
::= { lispFeaturesEntry 15 } DEFVAL { 0 }
::= { lispFeaturesEntry 15 }
lispIidToVrfTable OBJECT-TYPE lispIidToVrfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispIidToVrfEntry SYNTAX SEQUENCE OF LispIidToVrfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents the mapping of LISP Instance ID "This table represents the mapping of LISP Instance ID
to a VRF." to a VRF."
REFERENCE REFERENCE
"RFC6830, Section 5.5." "RFC6830, Section 5.5. and RFC4382, Section 7."
::= { lispObjects 2 } ::= { lispObjects 2 }
lispIidToVrfEntry OBJECT-TYPE lispIidToVrfEntry OBJECT-TYPE
SYNTAX LispIidToVrfEntry SYNTAX LispIidToVrfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the lispIidToVrfTable." "An entry (conceptual row) in the lispIidToVrfTable."
INDEX { lispFeaturesInstanceID } INDEX { lispFeaturesInstanceID }
::= { lispIidToVrfTable 1 } ::= { lispIidToVrfTable 1 }
skipping to change at page 16, line 36 skipping to change at page 14, line 36
lispIidToVrfName MplsL3VpnName lispIidToVrfName MplsL3VpnName
} }
lispIidToVrfName OBJECT-TYPE lispIidToVrfName OBJECT-TYPE
SYNTAX MplsL3VpnName SYNTAX MplsL3VpnName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for each VPN that is mapped to the "The identifier for each VPN that is mapped to the
given LISP Instance ID." given LISP Instance ID."
::= { lispIidToVrfEntry 2 } ::= { lispIidToVrfEntry 1 }
REFERENCE
"RFC 4382, Section 7."
lispGlobalStatsTable OBJECT-TYPE lispGlobalStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispGlobalStatsEntry SYNTAX SEQUENCE OF LispGlobalStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides global statistics for a given "This table provides global statistics for a given
Instance ID per address-family on a LISP device." Instance ID per address-family on a LISP device."
REFERENCE REFERENCE
"RFC6830, Section 6.1." "RFC6830, Section 6.1."
skipping to change at page 19, line 21 skipping to change at page 17, line 20
Discontinuities can also occur as a result of LISP features Discontinuities can also occur as a result of LISP features
being removed, which can be detected by observing the value being removed, which can be detected by observing the value
of lispFeaturesRouterTimeStamp." of lispFeaturesRouterTimeStamp."
::= { lispGlobalStatsEntry 6 } ::= { lispGlobalStatsEntry 6 }
lispMappingDatabaseTable OBJECT-TYPE lispMappingDatabaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispMappingDatabaseEntry SYNTAX SEQUENCE OF LispMappingDatabaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents the EID-to-RLOC mapping database that "This table represents the EID-to-RLOC mapping database
contains the EID-prefix to RLOC mappings configured on an that contains the EID-prefix to RLOC mappings configured
ETR. In general, this table would be representative of all on an ETR.
In general, this table would be representative of all
such mappings for the given LISP site to which this device such mappings for the given LISP site to which this device
belongs." belongs."
REFERENCE REFERENCE
"RFC6830, Section 6.0." "RFC6830, Section 6.0."
::= { lispObjects 4 } ::= { lispObjects 4 }
lispMappingDatabaseEntry OBJECT-TYPE lispMappingDatabaseEntry OBJECT-TYPE
SYNTAX LispMappingDatabaseEntry SYNTAX LispMappingDatabaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the lispMappingDatabaseTable." "An entry (conceptual row) in lispMappingDatabaseTable."
INDEX { lispMappingDatabaseEidLength, INDEX { lispMappingDatabaseEidLength,
lispMappingDatabaseEid } lispMappingDatabaseEid }
::= { lispMappingDatabaseTable 1 } ::= { lispMappingDatabaseTable 1 }
LispMappingDatabaseEntry ::= SEQUENCE { LispMappingDatabaseEntry ::= SEQUENCE {
lispMappingDatabaseEidLength Integer32, lispMappingDatabaseEidLength Integer32,
lispMappingDatabaseEid LispAddressType, lispMappingDatabaseEid LispAddressType,
lispMappingDatabaseLsb Unsigned32, lispMappingDatabaseLsb Unsigned32,
lispMappingDatabaseEidPartitioned TruthValue, lispMappingDatabaseEidPartitioned TruthValue,
lispMappingDatabaseTimeStamp TimeStamp, lispMappingDatabaseTimeStamp TimeStamp,
skipping to change at page 21, line 6 skipping to change at page 19, line 8
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which the EID Prefix information "The value of sysUpTime at which the EID Prefix information
represented by this mapping database entry was configured represented by this mapping database entry was configured
on this device. on this device.
If this information was present at the most recent If this information was present at the most recent
re-initialization of the local management subsystem, then re-initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
DEFVAL { 0 }
::= { lispMappingDatabaseEntry 5 } ::= { lispMappingDatabaseEntry 5 }
lispMappingDatabaseDecapOctets OBJECT-TYPE lispMappingDatabaseDecapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of LISP packets that were decapsulated "The number of octets of LISP packets that were decapsulated
by this device addressed to a host within this EID-prefix. by this device addressed to a host within this EID-prefix.
skipping to change at page 23, line 30 skipping to change at page 21, line 32
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "This object is used to get the octet-length of
lispMappingDatabaseLocatorRloc." lispMappingDatabaseLocatorRloc."
::= { lispMappingDatabaseLocatorEntry 1 } ::= { lispMappingDatabaseLocatorEntry 1 }
lispMappingDatabaseLocatorRloc OBJECT-TYPE lispMappingDatabaseLocatorRloc OBJECT-TYPE
SYNTAX LispAddressType SYNTAX LispAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is a locator for the given EID prefix in the "This object is a locator for the given EID prefix in
mapping database." the mapping database."
::= { lispMappingDatabaseLocatorEntry 2 } ::= { lispMappingDatabaseLocatorEntry 2 }
lispMappingDatabaseLocatorRlocPriority OBJECT-TYPE lispMappingDatabaseLocatorRlocPriority OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast priority of the RLOC." "The unicast priority of the RLOC."
::= { lispMappingDatabaseLocatorEntry 3 } ::= { lispMappingDatabaseLocatorEntry 3 }
skipping to change at page 25, line 9 skipping to change at page 23, line 11
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which the RLOC of the EID Prefix "The value of sysUpTime at which the RLOC of the EID Prefix
represented by this mapping database entry was configured represented by this mapping database entry was configured
on this device. on this device.
If this information was present at the most recent If this information was present at the most recent
re-initialization of the local management subsystem, then re-initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
DEFVAL { 0 }
::= { lispMappingDatabaseLocatorEntry 9 } ::= { lispMappingDatabaseLocatorEntry 9 }
lispMappingDatabaseLocatorRlocDecapOctets OBJECT-TYPE lispMappingDatabaseLocatorRlocDecapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of LISP packets that were "The number of octets of LISP packets that were
addressed to this RLOC of the EID-prefix and addressed to this RLOC of the EID-prefix and
were decapsulated. were decapsulated.
skipping to change at page 27, line 46 skipping to change at page 25, line 50
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which the EID Prefix information "The value of sysUpTime at which the EID Prefix information
represented by this entry was learned by this device. represented by this entry was learned by this device.
If this information was present at the most recent If this information was present at the most recent
re-initialization of the local management subsystem, then re-initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
DEFVAL { 0 }
::= { lispMapCacheEntry 3 } ::= { lispMapCacheEntry 3 }
lispMapCacheEidExpiryTime OBJECT-TYPE lispMapCacheEidExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time remaining before the ITR times-out this "The time remaining before the ITR times-out this
EID prefix." EID prefix."
::= { lispMapCacheEntry 4 } ::= { lispMapCacheEntry 4 }
skipping to change at page 29, line 43 skipping to change at page 27, line 48
"The number of LISP packets that were encapsulated by this "The number of LISP packets that were encapsulated by this
device using the given EID-prefix in the map cache. device using the given EID-prefix in the map cache.
Discontinuities in this monotonically increasing value occur Discontinuities in this monotonically increasing value occur
at re-initialization of the management system. at re-initialization of the management system.
Discontinuities can also occur as a result of cache being Discontinuities can also occur as a result of cache being
removed and replaced, which can be detected by observing the removed and replaced, which can be detected by observing the
value of lispMapCacheEidTimeStamp." value of lispMapCacheEidTimeStamp."
::= { lispMapCacheEntry 10 } ::= { lispMapCacheEntry 10 }
lispMapCacheLocatorTable OBJECT-TYPE lispMapCacheLocatorTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispMapCacheLocatorEntry SYNTAX SEQUENCE OF LispMapCacheLocatorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents the set of locators per EID prefix "This table represents the set of locators per EID prefix
contained in the map-cache table of an ITR." contained in the map-cache table of an ITR."
REFERENCE REFERENCE
"RFC6830, Section 6.3." "RFC6830, Section 6.3."
::= { lispObjects 7 } ::= { lispObjects 7 }
lispMapCacheLocatorEntry OBJECT-TYPE
SYNTAX LispMapCacheLocatorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the
lispMapCacheLocatorTable."
INDEX { lispMapCacheEidLength,
lispMapCacheEid,
lispMapCacheLocatorRlocLength,
lispMapCacheLocatorRloc }
::= { lispMapCacheLocatorTable 1 }
LispMapCacheLocatorEntry ::= SEQUENCE {
lispMapCacheLocatorRlocLength Integer32,
lispMapCacheLocatorRloc LispAddressType,
lispMapCacheLocatorRlocPriority Integer32,
lispMapCacheLocatorRlocWeight Integer32,
lispMapCacheLocatorRlocMPriority Integer32,
lispMapCacheLocatorRlocMWeight Integer32,
lispMapCacheLocatorRlocState INTEGER,
lispMapCacheLocatorRlocTimeStamp TimeStamp,
lispMapCacheLocatorRlocLastPriorityChange TimeTicks,
lispMapCacheLocatorRlocLastWeightChange TimeTicks,
lispMapCacheLocatorRlocLastMPriorityChange TimeTicks,
lispMapCacheLocatorRlocLastMWeightChange TimeTicks,
lispMapCacheLocatorRlocLastStateChange TimeTicks,
lispMapCacheLocatorRlocRtt TimeTicks,
lispMapCacheLocatorRlocDecapOctets Counter64,
lispMapCacheLocatorRlocDecapPackets Counter64,
lispMapCacheLocatorRlocEncapOctets Counter64,
lispMapCacheLocatorRlocEncapPackets Counter64
}
lispMapCacheLocatorRlocLength OBJECT-TYPE lispMapCacheLocatorEntry OBJECT-TYPE
SYNTAX Integer32 (5..259) SYNTAX LispMapCacheLocatorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "An entry (conceptual row) in the
lispMapCacheLocatorRloc." lispMapCacheLocatorTable."
::= { lispMapCacheLocatorEntry 1 } INDEX { lispMapCacheEidLength,
lispMapCacheEid,
lispMapCacheLocatorRlocLength,
lispMapCacheLocatorRloc }
::= { lispMapCacheLocatorTable 1 }
lispMapCacheLocatorRloc OBJECT-TYPE LispMapCacheLocatorEntry ::= SEQUENCE {
SYNTAX LispAddressType lispMapCacheLocatorRlocLength Integer32,
MAX-ACCESS not-accessible lispMapCacheLocatorRloc LispAddressType,
STATUS current lispMapCacheLocatorRlocPriority Integer32,
DESCRIPTION lispMapCacheLocatorRlocWeight Integer32,
"The locator for the EID prefix in the mapping cache." lispMapCacheLocatorRlocMPriority Integer32,
::= { lispMapCacheLocatorEntry 2 } lispMapCacheLocatorRlocMWeight Integer32,
lispMapCacheLocatorRlocState INTEGER,
lispMapCacheLocatorRlocTimeStamp TimeStamp,
lispMapCacheLocatorRlocLastPriorityChange TimeTicks,
lispMapCacheLocatorRlocLastWeightChange TimeTicks,
lispMapCacheLocatorRlocLastMPriorityChange TimeTicks,
lispMapCacheLocatorRlocLastMWeightChange TimeTicks,
lispMapCacheLocatorRlocLastStateChange TimeTicks,
lispMapCacheLocatorRlocRtt TimeTicks,
lispMapCacheLocatorRlocDecapOctets Counter64,
lispMapCacheLocatorRlocDecapPackets Counter64,
lispMapCacheLocatorRlocEncapOctets Counter64,
lispMapCacheLocatorRlocEncapPackets Counter64
}
lispMapCacheLocatorRlocPriority OBJECT-TYPE lispMapCacheLocatorRlocLength OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (5..259)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast priority of the RLOC for this EID prefix "This object is used to get the octet-length of
(0-255); lower more preferred. " lispMapCacheLocatorRloc."
::= { lispMapCacheLocatorEntry 3 } ::= { lispMapCacheLocatorEntry 1 }
lispMapCacheLocatorRlocWeight OBJECT-TYPE lispMapCacheLocatorRloc OBJECT-TYPE
SYNTAX Integer32 (0..100) SYNTAX LispAddressType
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast weight of the RLOC for this EID prefix "The locator for the EID prefix in the mapping cache."
(0 - 100) percentage. " ::= { lispMapCacheLocatorEntry 2 }
::= { lispMapCacheLocatorEntry 4 }
lispMapCacheLocatorRlocMPriority OBJECT-TYPE lispMapCacheLocatorRlocPriority OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast priority of the RLOC for this EID prefix "The unicast priority of the RLOC for this EID prefix
(0-255); lower more preferred." (0-255); lower more preferred. "
::= { lispMapCacheLocatorEntry 5 } ::= { lispMapCacheLocatorEntry 3 }
lispMapCacheLocatorRlocMWeight OBJECT-TYPE lispMapCacheLocatorRlocWeight OBJECT-TYPE
SYNTAX Integer32 (0..100) SYNTAX Integer32 (0..100)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast weight of the RLOC for this EID prefix "The unicast weight of the RLOC for this EID prefix
(0 - 100) percentage." (0 - 100) percentage. "
::= { lispMapCacheLocatorEntry 6 } ::= { lispMapCacheLocatorEntry 4 }
lispMapCacheLocatorRlocState OBJECT-TYPE lispMapCacheLocatorRlocMPriority OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 (0..255)
up (1), MAX-ACCESS read-only
down (2), STATUS current
unreachable (3) DESCRIPTION
} "The multicast priority of the RLOC for this EID prefix
(0-255); lower more preferred."
::= { lispMapCacheLocatorEntry 5 }
MAX-ACCESS read-only lispMapCacheLocatorRlocMWeight OBJECT-TYPE
STATUS current SYNTAX Integer32 (0..100)
DESCRIPTION MAX-ACCESS read-only
"The state of this RLOC as per this device STATUS current
(1 = RLOC is up; 2 = RLOC is down)." DESCRIPTION
::= { lispMapCacheLocatorEntry 7 } "The multicast weight of the RLOC for this EID prefix
(0 - 100) percentage."
::= { lispMapCacheLocatorEntry 6 }
lispMapCacheLocatorRlocTimeStamp OBJECT-TYPE lispMapCacheLocatorRlocState OBJECT-TYPE
SYNTAX TimeStamp SYNTAX INTEGER {
MAX-ACCESS read-only up (1),
STATUS current down (2),
DESCRIPTION unreachable (3)
"The value of sysUpTime at which the RLOC of EID prefix }
information represented by this entry was learned by MAX-ACCESS read-only
this device. STATUS current
DESCRIPTION
"The state of this RLOC as per this device
(1 = RLOC is up; 2 = RLOC is down; 3 = RLOC is unreachable)."
::= { lispMapCacheLocatorEntry 7 }
If this information was present at the most recent lispMapCacheLocatorRlocTimeStamp OBJECT-TYPE
re-initialization of the local management subsystem, SYNTAX TimeStamp
then this object contains a zero value." MAX-ACCESS read-only
::= { lispMapCacheLocatorEntry 8 } STATUS current
DESCRIPTION
"The value of sysUpTime at which the RLOC of EID prefix
information represented by this entry was learned by
this device.
lispMapCacheLocatorRlocLastPriorityChange OBJECT-TYPE If this information was present at the most recent
SYNTAX TimeTicks re-initialization of the local management subsystem,
MAX-ACCESS read-only then this object contains a zero value."
STATUS current DEFVAL { 0 }
DESCRIPTION ::= { lispMapCacheLocatorEntry 8 }
"Time elapsed since the last change of the unicast priority
of the RLOC for this EID prefix. Note that this is
independent of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 9 }
lispMapCacheLocatorRlocLastWeightChange OBJECT-TYPE lispMapCacheLocatorRlocLastPriorityChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time elapsed since the last change of the unicast weight "Time elapsed since the last change of the unicast priority
of the RLOC for this EID prefix.Note that this is of the RLOC for this EID prefix. Note that this is
independent of lispMapCacheLocatorRlocTimeStamp." independent of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 10 } ::= { lispMapCacheLocatorEntry 9 }
lispMapCacheLocatorRlocLastMPriorityChange OBJECT-TYPE lispMapCacheLocatorRlocLastWeightChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last change of the multicast priority of the "Time elapsed since the last change of the unicast weight
RLOC for this EID prefix." of the RLOC for this EID prefix.Note that this is
independent of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 10 }
::= { lispMapCacheLocatorEntry 11 } lispMapCacheLocatorRlocLastMPriorityChange OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since the last change of the multicast priority of the
RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 11 }
lispMapCacheLocatorRlocLastMWeightChange OBJECT-TYPE lispMapCacheLocatorRlocLastMWeightChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last change of the multicast weight of the "Time since the last change of the multicast weight of the
RLOC for this EID prefix." RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 12 } ::= { lispMapCacheLocatorEntry 12 }
lispMapCacheLocatorRlocLastStateChange OBJECT-TYPE lispMapCacheLocatorRlocLastStateChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last change of the up/down state of the "Time since the last change of the up/down state of the
RLOC for this EID prefix." RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 13 } ::= { lispMapCacheLocatorEntry 13 }
lispMapCacheLocatorRlocRtt OBJECT-TYPE lispMapCacheLocatorRlocRtt OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Round trip time of RLOC probe and map-reply for this RLOC "Round trip time of RLOC probe and map-reply for this RLOC
address for this prefix." address for this prefix."
::= { lispMapCacheLocatorEntry 14 } ::= { lispMapCacheLocatorEntry 14 }
lispMapCacheLocatorRlocDecapOctets OBJECT-TYPE lispMapCacheLocatorRlocDecapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of LISP packets that were decapsulated "The number of octets of LISP packets that were decapsulated
by this device and were sourced from a remote host within by this device and were sourced from a remote host within
this EID-prefix and were encapsulated for this RLOC. this EID-prefix and were encapsulated for this RLOC.
Discontinuities in this monotonically increasing value occur Discontinuities in this monotonically increasing value occur
at re-initialization of the management system. at re-initialization of the management system.
Discontinuities can also occur as a result of RLOC of cache Discontinuities can also occur as a result of RLOC of cache
being removed and replaced, which can be detected by being removed and replaced, which can be detected by
observing the value of lispMapCacheLocatorRlocTimeStamp." observing the value of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 15 } ::= { lispMapCacheLocatorEntry 15 }
lispMapCacheLocatorRlocDecapPackets OBJECT-TYPE lispMapCacheLocatorRlocDecapPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of LISP packets that were decapsulated by this "The number of LISP packets that were decapsulated by this
device and were sourced from a remote host within this device and were sourced from a remote host within this
EID-prefix and were encapsulated for this RLOC. EID-prefix and were encapsulated for this RLOC.
Discontinuities in this monotonically increasing value occur Discontinuities in this monotonically increasing value occur
at re-initialization of the management system. at re-initialization of the management system.
Discontinuities can also occur as a result of RLOC of cache Discontinuities can also occur as a result of RLOC of cache
being removed and replaced, which can be detected by being removed and replaced, which can be detected by
observing the value of lispMapCacheLocatorRlocTimeStamp." observing the value of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 16 } ::= { lispMapCacheLocatorEntry 16 }
lispMapCacheLocatorRlocEncapOctets OBJECT-TYPE lispMapCacheLocatorRlocEncapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of LISP packets that matched this "The number of octets of LISP packets that matched this
EID prefix and were encapsulated using this RLOC address. EID prefix and were encapsulated using this RLOC address.
Discontinuities in this monotonically increasing value occur Discontinuities in this monotonically increasing value occur
at re-initialization of the management system. at re-initialization of the management system.
Discontinuities can also occur as a result of RLOC of cache Discontinuities can also occur as a result of RLOC of cache
being removed and replaced, which can be detected by being removed and replaced, which can be detected by
observing the value of lispMapCacheLocatorRlocTimeStamp." observing the value of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 17 } ::= { lispMapCacheLocatorEntry 17 }
lispMapCacheLocatorRlocEncapPackets OBJECT-TYPE lispMapCacheLocatorRlocEncapPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of LISP packets that matched this EID prefix "The number of LISP packets that matched this EID prefix
and were encapsulated using this RLOC address. and were encapsulated using this RLOC address.
Discontinuities in this monotonically increasing value occur Discontinuities in this monotonically increasing value occur
at re-initialization of the management system. at re-initialization of the management system.
Discontinuities can also occur as a result of RLOC of cache Discontinuities can also occur as a result of RLOC of cache
being removed and replaced, which can be detected by being removed and replaced, which can be detected by
observing the value of lispMapCacheLocatorRlocTimeStamp." observing the value of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 18 } ::= { lispMapCacheLocatorEntry 18 }
lispConfiguredLocatorTable OBJECT-TYPE lispConfiguredLocatorTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispConfiguredLocatorEntry SYNTAX SEQUENCE OF LispConfiguredLocatorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents the set of routing locators "This table represents the set of routing locators
configured on this device. Note that the Proxy-ITR configured on this device. Note that the Proxy-ITR
configured addresses are treated as routing locators configured addresses are treated as routing locators
and therefore can be part of this table." and therefore can be part of this table."
skipping to change at page 36, line 46 skipping to change at page 34, line 50
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which the RLOC was configured on "The value of sysUpTime at which the RLOC was configured on
this device. this device.
If this information was present at the most recent If this information was present at the most recent
re-initialization of the local management subsystem, then re-initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
DEFVAL { 0 }
::= { lispConfiguredLocatorEntry 5 } ::= { lispConfiguredLocatorEntry 5 }
lispConfiguredLocatorRlocDecapOctets OBJECT-TYPE lispConfiguredLocatorRlocDecapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of LISP packets that were addressed to "The number of octets of LISP packets that were addressed to
this RLOC and were decapsulated. this RLOC and were decapsulated.
skipping to change at page 40, line 15 skipping to change at page 38, line 20
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which the first valid register "The value of sysUpTime at which the first valid register
message for the EID Prefix information represented by this message for the EID Prefix information represented by this
entry was received by this device. entry was received by this device.
If this information was present at the most recent If this information was present at the most recent
re-initialization of the local management subsystem, then re-initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
DEFVAL { 0 }
::= { lispEidRegistrationEntry 6 } ::= { lispEidRegistrationEntry 6 }
lispEidRegistrationLastTimeStamp OBJECT-TYPE lispEidRegistrationLastTimeStamp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which the last valid register "The value of sysUpTime at which the last valid register
message for the EID Prefix information represented by this message for the EID Prefix information represented by this
entry was received by this device. entry was received by this device.
If this information was present at the most recent If this information was present at the most recent
re-initialization of the local management subsystem, then re-initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
DEFVAL { 0 }
::= { lispEidRegistrationEntry 7 } ::= { lispEidRegistrationEntry 7 }
lispEidRegistrationLastRegisterSenderLength OBJECT-TYPE lispEidRegistrationLastRegisterSenderLength OBJECT-TYPE
SYNTAX Integer32 (5..259) SYNTAX Integer32 (5..259)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "This object is used to get the octet-length of
lispEidRegistrationLastRegisterSender, the next lispEidRegistrationLastRegisterSender, the next
object." object."
skipping to change at page 42, line 50 skipping to change at page 41, line 8
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which the last valid register "The value of sysUpTime at which the last valid register
message from this ETR for the EID Prefix information message from this ETR for the EID Prefix information
represented by this entry was received by this device. represented by this entry was received by this device.
If this information was present at the most recent If this information was present at the most recent
re-initialization of the local management subsystem, re-initialization of the local management subsystem,
then this object contains a zero value." then this object contains a zero value."
DEFVAL { 0 }
::= { lispEidRegistrationEtrEntry 3 } ::= { lispEidRegistrationEtrEntry 3 }
lispEidRegistrationEtrTtl OBJECT-TYPE lispEidRegistrationEtrTtl OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Record TTL of the registering ETR device for this "The Record TTL of the registering ETR device for this
EID prefix." EID prefix."
::= { lispEidRegistrationEtrEntry 4 } ::= { lispEidRegistrationEtrEntry 4 }
skipping to change at page 63, line 22 skipping to change at page 61, line 30
"Objects providing information related to VRF "Objects providing information related to VRF
configurations on a LISP router." configurations on a LISP router."
::= { lispGroups 14 } ::= { lispGroups 14 }
END END
8. Relationship to Other MIB Modules 8. Relationship to Other MIB Modules
8.1. MIB modules required for IMPORTS 8.1. MIB modules required for IMPORTS
The LISP MIB imports the textual-convention AddressFamilyNumbers from The LISP MIB imports the TEXTUAL-CONVENTION AddressFamilyNumbers from
the IANA-ADDRESS-FAMILY-NUMBERS-MIB [IANA]. the IANA-ADDRESS-FAMILY-NUMBERS-MIB [IANA].
The LISP MIB imports mib-2, Unsigned32, Counter64, Integer32, and
TimeTicks from SNMPv2-SMI -- [RFC2578].
The LISP MIB imports TruthValue, TEXTUAL-CONVENTION, TimeStamp, and
TimeTicks from SNMPv2-TC -- [RFC2579].
The LISP MIB imports MODULE-COMPLIANCE from SNMPv2-TC -- [RFC2580].
The LISP MIB imports MplsL3VpnName from MPLS-L3VPN-STD-MIB --
[RFC4382].
9. Security Considerations 9. Security Considerations
There are no management objects defined in this MIB module that have There are no management objects defined in this MIB module that have
a MAX-ACCESS clause of read-write and/or read-create. As long as a MAX-ACCESS clause of read-write and/or read-create. As long as
these MIB modules are implemented correctly, there are no risks that these MIB modules are implemented correctly, there are no risks that
any management objects of this MIB module can modify device settings any management objects of this MIB module can modify device settings
via direct SNMP SET operations. via direct SNMP SET operations.
There are no readable objects in this MIB module (i.e., objects with There are no readable objects in this MIB module (i.e., objects with
a MAX-ACCESS other than not-accessible) that are considered a MAX-ACCESS other than not-accessible) that are considered
skipping to change at page 65, line 20 skipping to change at page 63, line 39
"Interworking between Locator/ID Separation Protocol "Interworking between Locator/ID Separation Protocol
(LISP) and Non-LISP Sites", RFC 6832, January 2013. (LISP) and Non-LISP Sites", RFC 6832, January 2013.
[RFC6833] Fuller, V. and D. Farinacci, "Locator/ID Separation [RFC6833] Fuller, V. and D. Farinacci, "Locator/ID Separation
Protocol (LISP) Map-Server Interface", RFC 6833, Protocol (LISP) Map-Server Interface", RFC 6833,
January 2013. January 2013.
11.2. Informative References 11.2. Informative References
[LCAF] Farinacci, D., Meyer, D., and J. Snijders, "LISP Canonical [LCAF] Farinacci, D., Meyer, D., and J. Snijders, "LISP Canonical
Address Format", draft-ietf-lisp-lcaf-00.txt (work in Address Format", draft-ietf-lisp-lcaf-02.txt (work in
progress), August 2012. progress), March 2013.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The [RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The
Locator/ID Separation Protocol (LISP) for Multicast Locator/ID Separation Protocol (LISP) for Multicast
Environments", RFC 6831, January 2013. Environments", RFC 6831, January 2013.
Appendix A. Open Issues Appendix A. Acknowledgments
Open issues for the LISP MIB include the following:
1. This LISP MIB draft does not include LISP Multicast [LISP-MCAST]
considerations. Multicast considerations will be added in a
separate LISP Multicast MIB draft.
Appendix B. Acknowledgments
A thank you is owed to Dino Farinacci for his inputs and review A thank you is owed to Dino Farinacci for his inputs and review
comments on the initial versions of this draft. In addition, the comments on the initial versions of this draft. In addition, the
authors would like to gratefully acknowledge several others who have authors would like to gratefully acknowledge several others who have
reviewed and commented on this draft. They include: Darrel Lewis, reviewed and commented on this draft. They include: Darrel Lewis,
Isidor Kouvelas, Jesper Skriver, Selina Heimlich, Parna Agrawal, Dan Isidor Kouvelas, Jesper Skriver, Selina Heimlich, Parna Agrawal, Dan
Romascanu, and Luigi Iannone. A special thanks to Brian Haberman, Romascanu, and Luigi Iannone. Special thanks are owed to Brian
the Internet Area AD, for his very detailed review. Also to Miguel Haberman, the Internet Area AD, for his very detailed review, Miguel
Garcia for reviewing this document as part of the General Area Review Garcia for reviewing this document as part of the General Area Review
Team. Team, and Harrie Hazewinkel for the detailed MIB review comments.
Authors' Addresses Authors' Addresses
Gregg Schudel Gregg Schudel
cisco Systems cisco Systems
Tasman Drive Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
EMail: gschudel@cisco.com EMail: gschudel@cisco.com
Amit Jain Amit Jain
cisco Systems Juniper Networks
Tasman Drive 1133 Innovation Way
San Jose, CA 95134 Sunnyvale, CA 94089
USA USA
EMail: amijain@cisco.com EMail: atjain@juniper.net
Victor Moreno Victor Moreno
cisco Systems cisco Systems
Tasman Drive Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
EMail: vimoreno@cisco.com EMail: vimoreno@cisco.com
 End of changes. 100 change blocks. 
564 lines changed or deleted 515 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/