idnits 2.17.1 draft-ietf-lisp-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (October 2, 2012) is 4217 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'RFC 2578' is mentioned on line 321, but not defined == Missing Reference: 'RFC 2579' is mentioned on line 323, but not defined == Missing Reference: 'RFC 2580' is mentioned on line 324, but not defined == Missing Reference: 'RFC 4382' is mentioned on line 326, but not defined == Missing Reference: 'RFC4382' is mentioned on line 678, but not defined == Missing Reference: 'Section 7' is mentioned on line 678, but not defined == Unused Reference: 'RFC1035' is defined on line 2974, but no explicit reference was found in the text == Unused Reference: 'RFC2404' is defined on line 2980, but no explicit reference was found in the text == Unused Reference: 'RFC4634' is defined on line 2997, but no explicit reference was found in the text == Unused Reference: 'LISP-MCAST' is defined on line 3006, but no explicit reference was found in the text == Unused Reference: 'LISP-MN' is defined on line 3011, but no explicit reference was found in the text == Unused Reference: 'RFC2784' is defined on line 3016, but no explicit reference was found in the text == Unused Reference: 'RFC4271' is defined on line 3025, but no explicit reference was found in the text == Unused Reference: 'RFC4760' is defined on line 3028, but no explicit reference was found in the text == Outdated reference: A later version (-24) exists of draft-ietf-lisp-23 ** Obsolete normative reference: RFC 4634 (Obsoleted by RFC 6234) == Outdated reference: A later version (-22) exists of draft-ietf-lisp-lcaf-00 == Outdated reference: A later version (-16) exists of draft-meyer-lisp-mn-07 Summary: 1 error (**), 0 flaws (~~), 20 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Schudel 3 Internet-Draft A. Jain 4 Intended status: Experimental V. Moreno 5 Expires: April 5, 2013 cisco Systems 6 October 2, 2012 8 LISP MIB 9 draft-ietf-lisp-mib-06 11 Abstract 13 This document defines managed objects for the Locator/ID Separation 14 Protocol (LISP). These objects provide information useful for 15 monitoring LISP devices, including basic configuration information, 16 LISP status, and operational statistics. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on April 5, 2013. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 53 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. The Internet-Standard Management Framework . . . . . . . . . . 3 55 4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 56 5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 6 57 6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 6 58 6.1. Overview of Defined Notifications . . . . . . . . . . . . 6 59 6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 7 60 7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 8 61 8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 62 62 8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 62 63 9. Security Considerations . . . . . . . . . . . . . . . . . . . 62 64 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 65 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63 66 11.1. Normative References . . . . . . . . . . . . . . . . . . . 63 67 11.2. Informative References . . . . . . . . . . . . . . . . . . 64 68 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 65 69 Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 65 71 1. Requirements Notation 73 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 74 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 75 document are to be interpreted as described in [RFC2119]. 77 2. Introduction 79 This draft describes the Management Information Base (MIB) module for 80 use with network management protocols in the Internet community. 81 Specifically, the MIB for managing Locator/ID Separation Protocol 82 (LISP) devices is described. 84 LISP [LISP] specifies a network-based architecture and mechanisms 85 that implement a new semantic for IP addressing using two separate 86 name spaces: Endpoint Identifiers (EIDs), used within sites, and 87 Routing Locators (RLOCs), used on the transit networks that make up 88 the Internet infrastructure. To achieve this separation, LISP 89 defines protocol mechanisms for mapping from EIDs to RLOCs. 91 From a data plane perspective, LISP traffic is handled exclusively at 92 the network layer by devices performing Ingress Tunnel Router (ITR) 93 and Egress Tunnel Router (ETR) LISP functions. Data plane operations 94 performed by these devices are described in [LISP]. Additionally, 95 data plane interworking between legacy (Internet) and LISP sites is 96 implemented by devices performing Proxy ITR (PITR) and Proxy ETR 97 (PETR) functions. The data plane operations of these devices is 98 described in [INTERWORK]. 100 From a control plane perspective, LISP employs mechanisms related to 101 creating, maintaining, and resolving mappings from EIDs to RLOCs. 102 LISP ITRs, ETRs, PITRs, and PETRs perform specific control plane 103 functions, and these control plane operations are described in 104 [LISP]. Additionally, LISP infrastructure devices supporting LISP 105 control plane functionality include Map-Servers and Map-Resolvers, 106 and the control plane operations of these devices are described in 107 [LISP-MS]. Finally, while not specifically required, this document 108 assumes the existence of a database to store and propagate those 109 mappings globally. 111 3. The Internet-Standard Management Framework 113 For a detailed overview of the documents that describe the current 114 Internet-Standard Management Framework, please refer to section 7 of 115 RFC 3410 [RFC3410]. 117 Managed objects are accessed via a virtual information store, termed 118 the Management Information Base or MIB. MIB objects are generally 119 accessed through the Simple Network Management Protocol (SNMP). 120 Objects in the MIB are defined using the mechanisms defined in the 121 Structure of Management Information (SMI). This memo specifies a MIB 122 module that is compliant to the SMIv2, which is described in STD 58, 123 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 124 [RFC2580]. 126 4. Definition of Terms 128 Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value 129 used in the source and destination address fields of the first 130 (inner-most) IP header of a LISP packet. A source EID is 131 allocated to a host from an EID-prefix block associated with the 132 site where the host is located. A host determines a destination 133 address in the same way that it determines a destination address 134 today, for example through a DNS lookup or SIP exchange. 136 Routing Locator (RLOC): a 32-bit (for IPv4) or 128-bit (for IPv6) 137 value used in the source and destination address fields of the 138 second (outer-most) IP header of a LISP packet. RLOC addresses 139 are allocated to an egress tunnel router (ETR) and numbered from 140 topologically-aggregatable blocks assigned to a site at each point 141 to which it attaches to the global Internet. 143 EID-to-RLOC Map-Cache: a short-lived, on-demand table maintained 144 locally in an ITR or PITR that stores, tracks, and is responsible 145 for timing-out and otherwise validating EID-to-RLOC mappings. 146 This table is distinct from the full "database" of EID-to-RLOC 147 mappings in that it is dynamic and relatively small. At a given 148 moment in time, it consists only of entries for those sites to 149 which the ITR or PITR is currently communicating or has 150 communicated with within the configured TTL period. 152 EID-to-RLOC Mapping-Database: a global distributed database that 153 contains all known EID-to-RLOC mappings. Each potential ETR 154 typically contains a small piece of the database consisting of 155 only the EID-to-RLOC mappings for the EID prefix(es) for which the 156 ETR is "authoritative" and the RLOC(s) by which those EID 157 prefix(es) are reachable from the global Internet. 159 Ingress Tunnel Router (ITR): a router that accepts an IP packet with 160 a single IP header (more precisely, an IP packet that does not 161 contain a LISP header), treats this "inner" IP destination address 162 as an EID and performs an EID-to-RLOC mapping lookup, and then 163 prepends an "outer" IP header with one of its own globally- 164 routable RLOCs in the source address field and the RLOC resulting 165 from the mapping lookup in the destination address field. That 166 is, in general an ITR receives an IP packet from site end-systems 167 on one side and sends a LISP-encapsulated IP packet toward the 168 Internet on the other side. 170 Egress Tunnel Router (ETR): a router that accepts an IP packet where 171 the destination address in the "outer" IP header is one of its own 172 RLOCs, strips the "outer" header, and forwards the packet based on 173 the next IP header found. That is, in general an ETR receives 174 LISP-encapsulated IP packets from the Internet on one side and 175 sends decapsulated IP packets toward site end-systems on the other 176 side. 178 xTR: a term of general reference to an ITR or ETR when direction of 179 data flow is not part of the context description. xTR refers to 180 the router that is the tunnel endpoint and performs both ITR and 181 ETR functionality. For example, "An xTR can be located at the 182 Customer Edge (CE) router," meaning both ITR and ETR functionality 183 is activated at the CE router. 185 Proxy ITR (PITR): a router that acts like an ITR but does so on 186 behalf of non-LISP sites which send packets to destinations at 187 LISP sites. The PITR, also known as a PTR, is defined and 188 described in [INTERWORK]. 190 Proxy ETR (PETR): a router that acts like an ETR but does so on 191 behalf of LISP sites which send packets to destinations at non- 192 LISP sites. The PETR is defined and described in [INTERWORK]. 194 LISP Site: a set of routers in an edge network that are under a 195 single technical administration. LISP routers which reside in the 196 edge network are the demarcation points to separate the edge 197 network from the core network. 199 Map-Server: a LISP network infrastructure component which learns 200 EID-to-RLOC mapping entries from an authoritative source such as 201 an ETR though static configuration, or another out-of-band 202 mechanism. A Map-Server advertises these mappings into the 203 distributed mapping database. 205 Map-Resolver: a LISP network infrastructure component which accepts 206 LISP Encapsulated Map-Requests, typically from an ITR, and quickly 207 determines whether or not the destination IP address is part of 208 the EID namespace. If it is, the Map-Resolver finds the 209 appropriate EID-to-RLOC mapping by consulting the distributed 210 mapping database. If it is not, a Negative Map-Reply is 211 immediately returned. 213 Map-Request: a LISP Map-Request message type sent by an ITR or PITR 214 to a Map-Resolver when it needs a mapping for an EID, wants to 215 test an RLOC for reachability, or wants to refresh a mapping 216 before TTL expiration. 218 Map-Reply: a LISP Map-Reply message type returned in response to a 219 Map-Request for a destination EID that exists in the mapping 220 database and contains the locator-set and associated policy for 221 the queried EID. Information returned in a Map-Reply is stored in 222 the EID-to-RLOC Map-Cache. 224 Negative Map-Reply: a LISP Map-Reply message type that contains an 225 empty locator-set. Returned in response to a Map-Request if the 226 destination EID does not exist in the mapping database. 227 Typically, this means that the "EID" being requested is an IP 228 address connected to a non-LISP site. Information returned in a 229 Negative Map-Reply is stored in the EID-to-RLOC Map-Cache. 231 5. LISP MIB Objectives 233 The objectives for defining this LISP MIB module are as follows: 235 o Provide a means for obtaining a list of enabled LISP features and 236 the current status of configuration attributes related to those 237 features. As an example, LISP capabilities which could be enabled 238 include ITR, ETR, PITR, PETR, MS or MR support for IPv4 or IPv6 239 address families. Other examples include, indicating whether 240 rloc-probing is enabled, and indicating the configured map-cache 241 limit value. 243 o Provide a means for obtaining the current attributes of various 244 LISP tables, such as the EID-to-RLOC policy data contained in the 245 Map-Cache, or the local EID-to-RLOC policy data contained in the 246 Mapping-Database. 248 o Provide a means for obtaining the current operational statistics 249 of various LISP functions, such as the number of packets 250 encapsulated and decapsulated by the device. Other counters of 251 operational interest, depending on LISP function, include things 252 like the current number of map-cache entries, and the total number 253 and rate of map-requests received and sent. 255 6. Structure of LISP MIB Module 257 6.1. Overview of Defined Notifications 259 No LISP MIB notifications are defined. 261 6.2. Overview of Defined Tables 263 The LISP MIB module is composed of the following tables of objects: 265 lispFeatures - This table provides information representing the 266 various lisp features that can be enabled on LISP devices. 268 lispIidToVrf - This table provides information representing the 269 mapping of a LISP instance ID to a VRF. 271 lispGlobalStats - This table provides global statistics for a given 272 Instance ID per address-family on a LISP device. 274 lispMappingDatabase - This table represents the EID-to-RLOC database 275 that contains the EID-prefix to RLOC mappings configured on an 276 ETR. In general, this table would be representative of all such 277 mappings for a given site that this device belongs to. 279 lispMappingDatabaseLocator - This table represents the set of 280 routing locators contained in the EID-to-RLOC database configured 281 on an ETR. 283 lispMapCache - This table represents the short-lived, on-demand 284 table on an ITR that stores, tracks, and is responsible for 285 timing-out and otherwise validating EID-to-RLOC mappings. 287 lispMapCacheLocator - This table represents the set of locators per 288 EID prefix contained in the map-cache table of an ITR. 290 lispConfiguredLocator - This table represents the set of routing 291 locators configured on a LISP device. 293 lispEidRegistration - This table provides the properties of each EID 294 prefix that is registered with this device when configured to be a 295 Map-Server. 297 lispEidRegistrationEtr - This table provides the properties of the 298 different ETRs that send registers, for a given EID prefix, to 299 this device when configured to be a Map-Server. 301 lispEidRegistrationLocator - This table provides the properties of 302 the different locators per EID prefix that is registered with this 303 device when configured to be a Map-Server. 305 lispUseMapServer - This table provides the properties of all Map- 306 Servers that this device is configured to use. 308 lispUseMapResolver - This table provides the properties of all Map- 309 Resolvers that this device is configured to use. 311 lispUseProxyEtr - This table provides the properties of all Proxy 312 ETRs that this device is configured to use. 314 7. LISP MIB Definitions 316 LISP-MIB DEFINITIONS ::= BEGIN 318 IMPORTS 319 MODULE-IDENTITY, OBJECT-TYPE, 320 mib-2, Unsigned32, Counter64, 321 Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC 2578] 322 TruthValue, TEXTUAL-CONVENTION, 323 TimeStamp FROM SNMPv2-TC -- [RFC 2579] 324 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC 2580] 325 MplsL3VpnName 326 FROM MPLS-L3VPN-STD-MIB -- [RFC 4382] 327 AddressFamilyNumbers 328 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA] 330 lispMIB MODULE-IDENTITY 331 LAST-UPDATED "201209280000Z" -- 28 September 2012 332 ORGANIZATION 333 "IETF Locator/ID Separation Protocol (LISP) Working Group" 334 CONTACT-INFO 335 "Email: lisp@ietf.org 336 WG charter: 337 http://www.ietf.org/html.charters/lisp-charter.html" 338 DESCRIPTION 339 "Locator/ID Separation Protocol (LISP) MIB Textual 340 Conventions module. The LISP MIB is intended for 341 management of LISP routers. 343 Copyright (C) The IETF Trust (2012)." 344 REVISION "201209280000Z" -- 28 September 2012 345 DESCRIPTION "Initial version of the IETF LISP-MIB module. Published 346 as RFC xxxx." 347 -- RFC Ed.: RFC-editor pls fill in xxxx 348 ::= { mib-2 XXX } 349 -- RFC Ed.: assigned by IANA, see section 10 for details 351 -- 352 -- Textual Conventions 353 -- 354 LispAddressType ::= TEXTUAL-CONVENTION 355 DISPLAY-HINT "39a" 356 STATUS current 357 DESCRIPTION 358 "LISP architecture can be applied to a wide variety of 359 address-families. This textual-convention is a 360 generalization for representing addresses that belong to those 361 address-families. For convenience, this document refers to any 362 such address as a LISP address. LispAddressType 363 textual-convention consists of the following four-tuple: 364 1. IANA Address Family Number: A field of length 2-octets, 365 whose value is of the form following the assigned 366 AddressFamilyNumbers textual-convention described in 367 [IANA]. The enumerations are listed in [IANA]. Note that 368 this list of address family numbers is maintained by IANA. 369 2. Length of LISP address: A field of length 1-octet, whose 370 value indicates the octet-length of the next (third) field 371 of this LispAddressType four-tuple. 372 3. LISP address: A field of variable length as indicated in 373 the previous (second) field, whose value is an address of 374 the IANA Address Family indicated in the first field of 375 this LispAddressType four-tuple. Note that any of the 376 IANA Address Families can be represented. Particularly 377 when the address family is LISP Canonical Address Format 378 (LCAF) [LCAF] with IANA assigned Address Family Number 379 16387, then the first octet of this field indicates the 380 LCAF type, and the rest of this field is same as the 381 encoding format of the LISP Canonical Address after the 382 length field, as defined in [LCAF]. 383 4. Mask-length of address: A field of length 1-octet, whose 384 value is the mask-length to be applied to the LISP 385 address specified in the previous (third) field. 387 To illustrate the use of this object, consider the LISP MIB 388 Object below entitled lispMapCacheEntry. This object begins 389 with the following entities: 391 lispMapCacheEntry ::= SEQUENCE { 392 lispMapCacheEidLength INTEGER, 393 lispMapCacheEid LispAddressType, 394 ... [skip] ... 396 Example 1: Suppose that the IPv4 EID prefix stored is 397 10.10.10.0/24. In this case, the values within 398 lispMapCacheEntry would be: 400 lispMapCacheEidLength = 8 401 lispMapCacheEid = 1, 4, 10.10.10.0, 24 402 ... [skip] ... 404 where 8 is the total length in octets of the next 405 object (lispMapCacheEID of type LispAddressType). Then, 406 the value 1 indicates the IPv4 AF (per [IANA]), the 407 value 4 indicates that the AF is 4-octets in length, 408 10.10.10.0 is the IPv4 address, and the value 24 is the 409 mask-length in bits. Note that the lispMapCacheEidLength 410 value of 8 is used to compute the length of the fourth 411 (last) field in lispMapCacheEid to be 1 octet - as 412 computed by 8 - (2 + 1 + 4) = 1. 414 Example 2: Suppose that the IPv6 EID prefix stored is 415 2001:db8:a::/48. In this case, the values within 416 lispMapCacheEntry would be: 418 lispMapCacheEidLength = 20 419 lispMapCacheEid = 2, 16, 2001:db8:a::, 48 420 ... [skip] ... 422 where 20 is the total length in octets of the next 423 object (lispMapCacheEID of type LispAddressType). Then, 424 the value 2 indicates the IPv4 AF (per [IANA]), the 425 value 16 indicates that the AF is 16-octets in length, 426 2001:db8:a:: is the IPv6 address, and the value 48 is the 427 mask-length in bits. Note that the lispMapCacheEidLength 428 value of 20 is used to compute the length of the fourth 429 (last) field in lispMapCacheEid to be 1 octet - as 430 computed by 20 - (2 + 1 + 16) = 1. 432 Example 3: As an example where LCAF is used, suppose 433 that the IPv4 EID prefix stored is 10.10.10.0/24 and it 434 is part of LISP Instance ID 101. In this case, the values 435 within lispMapCacheEntry would be: 437 lispMapCacheEidLength = 11 438 lispMapCacheEid = 16387, 7, 2, 101, 1, 10.10.10.0, 24 439 ... [skip] ... 441 where 11 is the total length in octets of the next object 442 (lispMapCacheEID of type LispAddressType). Then, the value 443 16387 indicates the LCAF AF (see [IANA]), the value 7 444 indicates that the LCAF AF is 7-octets in length in this 445 case, 2 indicates that LCAF Type 2 encoding is used (see 446 [LCAF]), 101 gives the Instance ID, 1 gives the AFI (per 447 [IANA]) for an IPv4 address, 10.10.10.0 is the IPv4 448 address, and 24 is the mask-length in bits. Note that the 449 lispMapCacheEidLength value of 11 octets is used to compute 450 the length of the last field in lispMapCacheEid to be 1 octet, 451 as computed by 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) = 1." 453 REFERENCE 454 "[LISP], Section 14.2." 455 SYNTAX OCTET STRING (SIZE (5..39)) 457 -- 458 -- Top level components of this MIB. 459 -- 460 lispObjects OBJECT IDENTIFIER ::= { lispMIB 1 } 461 lispConformance OBJECT IDENTIFIER ::= { lispMIB 2 } 463 lispFeaturesTable OBJECT-TYPE 464 SYNTAX SEQUENCE OF LispFeaturesEntry 465 MAX-ACCESS not-accessible 466 STATUS current 467 DESCRIPTION 468 "This table represents the various LISP features 469 that can be enabled on LISP devices." 470 REFERENCE 471 "[LISP], Section 4.0., Section 5.5., Section 6.3." 472 ::= { lispObjects 1 } 474 lispFeaturesEntry OBJECT-TYPE 475 SYNTAX LispFeaturesEntry 476 MAX-ACCESS not-accessible 477 STATUS current 478 DESCRIPTION 479 "An entry (conceptual row) in the lispFeaturesTable." 480 INDEX { lispFeaturesInstanceID, 481 lispFeaturesAddressFamily } 482 ::= { lispFeaturesTable 1 } 484 LispFeaturesEntry ::= SEQUENCE { 485 lispFeaturesInstanceID Unsigned32, 486 lispFeaturesAddressFamily AddressFamilyNumbers, 487 lispFeaturesItrEnabled TruthValue, 488 lispFeaturesEtrEnabled TruthValue, 489 lispFeaturesProxyItrEnabled TruthValue, 490 lispFeaturesProxyEtrEnabled TruthValue, 491 lispFeaturesMapServerEnabled TruthValue, 492 lispFeaturesMapResolverEnabled TruthValue, 493 lispFeaturesMapCacheSize Unsigned32, 494 lispFeaturesMapCacheLimit Unsigned32, 495 lispFeaturesEtrMapCacheTtl Unsigned32, 496 lispFeaturesRlocProbeEnabled TruthValue, 497 lispFeaturesEtrAcceptMapDataEnabled TruthValue, 498 lispFeaturesEtrAcceptMapDataVerifyEnabled TruthValue, 499 lispFeaturesRouterTimeStamp TimeStamp 500 } 502 lispFeaturesInstanceID OBJECT-TYPE 503 SYNTAX Unsigned32 (0..16777215) 504 MAX-ACCESS not-accessible 505 STATUS current 506 DESCRIPTION 507 "This represents the Instance ID of the LISP header. 508 An Instance ID in the LISP address encoding helps 509 uniquely identify the AFI-based address space to which 510 a given EID belongs. It's default value is 0." 511 ::= { lispFeaturesEntry 1 } 513 lispFeaturesAddressFamily OBJECT-TYPE 514 SYNTAX AddressFamilyNumbers 515 MAX-ACCESS not-accessible 516 STATUS current 517 DESCRIPTION 518 "The IANA address family number that the LISP device 519 is enabled to LISP process a packet for as a 520 destination address family." 521 ::= { lispFeaturesEntry 2 } 523 lispFeaturesItrEnabled OBJECT-TYPE 524 SYNTAX TruthValue 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "Indicates the status of ITR role on this device. If 529 this object is TRUE, then ITR feature is enabled." 530 ::= { lispFeaturesEntry 3 } 532 lispFeaturesEtrEnabled OBJECT-TYPE 533 SYNTAX TruthValue 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "Indicates the status of ETR role on this device. If 538 this object is TRUE, then ETR feature is enabled." 539 ::= { lispFeaturesEntry 4 } 541 lispFeaturesProxyItrEnabled OBJECT-TYPE 542 SYNTAX TruthValue 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "Indicates the status of Proxy-ITR role on this device. 547 If this object is TRUE, then Proxy-ITR feature is enabled." 548 ::= { lispFeaturesEntry 5 } 550 lispFeaturesProxyEtrEnabled OBJECT-TYPE 551 SYNTAX TruthValue 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION 555 "Indicates the status of Proxy-ETR role on this device. 556 If this object is TRUE, then Proxy-ETR feature is enabled." 557 ::= { lispFeaturesEntry 6 } 559 lispFeaturesMapServerEnabled OBJECT-TYPE 560 SYNTAX TruthValue 561 MAX-ACCESS read-only 562 STATUS current 563 DESCRIPTION 564 "Indicates the status of Map Server role on this device. 565 If this object is TRUE, then Map Server feature is 566 enabled." 567 ::= { lispFeaturesEntry 7 } 569 lispFeaturesMapResolverEnabled OBJECT-TYPE 570 SYNTAX TruthValue 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "Indicates the status of Map Resolver role on this device. 575 If this object is TRUE, then Map Resolver feature is 576 enabled." 577 ::= { lispFeaturesEntry 8 } 579 lispFeaturesMapCacheSize OBJECT-TYPE 580 SYNTAX Unsigned32 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "Size of EID-to-RLOC map cache on this device." 585 ::= { lispFeaturesEntry 9 } 587 lispFeaturesMapCacheLimit OBJECT-TYPE 588 SYNTAX Unsigned32 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "Maximum permissible size of EID-to-RLOC map cache on 593 this device." 594 ::= { lispFeaturesEntry 10 } 596 lispFeaturesEtrMapCacheTtl OBJECT-TYPE 597 SYNTAX Unsigned32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "The stored Record TTL of the EID-to-RLOC map record in 602 the map cache." 603 ::= { lispFeaturesEntry 11 } 605 lispFeaturesRlocProbeEnabled OBJECT-TYPE 606 SYNTAX TruthValue 607 MAX-ACCESS read-only 608 STATUS current 609 DESCRIPTION 610 "Indicates the status of rloc-probing feature on this device. 611 If this object is TRUE, then this feature is enabled." 612 ::= { lispFeaturesEntry 12 } 614 lispFeaturesEtrAcceptMapDataEnabled OBJECT-TYPE 615 SYNTAX TruthValue 616 MAX-ACCESS read-only 617 STATUS current 618 DESCRIPTION 619 "Indicates the status of accepting piggybacked mapping data 620 received in a map-request on this device. If this object is 621 TRUE, then this device accepts piggybacked mapping data." 622 ::= { lispFeaturesEntry 13 } 624 lispFeaturesEtrAcceptMapDataVerifyEnabled OBJECT-TYPE 625 SYNTAX TruthValue 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "Indicates the status of verifying accepted piggybacked 630 mapping data received in a map-request on this device. If 631 this object is TRUE, then this device verifies accepted 632 piggybacked mapping data." 633 ::= { lispFeaturesEntry 14 } 635 lispFeaturesRouterTimeStamp OBJECT-TYPE 636 SYNTAX TimeStamp 637 MAX-ACCESS read-only 638 STATUS current 639 DESCRIPTION 640 "The value of sysUpTime at which LISP feature was enabled 641 on this device. 643 If this information was present at the most recent 644 re-initialization of the local management subsystem, 645 then this object contains a zero value." 646 ::= { lispFeaturesEntry 15 } 648 lispIidToVrfTable OBJECT-TYPE 649 SYNTAX SEQUENCE OF LispIidToVrfEntry 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "This table represents the mapping of LISP Instance ID 654 to a VRF." 655 REFERENCE 656 "[LISP], Section 5.5." 657 ::= { lispObjects 2 } 659 lispIidToVrfEntry OBJECT-TYPE 660 SYNTAX LispIidToVrfEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "An entry (conceptual row) in the lispIidToVrfTable." 665 INDEX { lispFeaturesInstanceID } 666 ::= { lispIidToVrfTable 1 } 668 LispIidToVrfEntry ::= SEQUENCE { 669 lispIidToVrfName MplsL3VpnName 670 } 672 lispIidToVrfName OBJECT-TYPE 673 SYNTAX MplsL3VpnName 674 MAX-ACCESS read-only 675 STATUS current 676 DESCRIPTION 677 "The identifier for each VPN, as specified in 678 [RFC4382, Section 7], that is mapped to the given 679 LISP Instance ID." 680 ::= { lispIidToVrfEntry 2 } 682 lispGlobalStatsTable OBJECT-TYPE 683 SYNTAX SEQUENCE OF LispGlobalStatsEntry 684 MAX-ACCESS not-accessible 685 STATUS current 686 DESCRIPTION 687 "This table provides global statistics for a given 688 Instance ID per address-family on a LISP device." 689 REFERENCE 690 "[LISP], Section 6.1." 691 ::= { lispObjects 3 } 693 lispGlobalStatsEntry OBJECT-TYPE 694 SYNTAX LispGlobalStatsEntry 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "An entry (conceptual row) in the 699 lispGlobalStatsTable." 700 INDEX { lispFeaturesInstanceID, 701 lispFeaturesAddressFamily } 702 ::= { lispGlobalStatsTable 1 } 704 LispGlobalStatsEntry ::= SEQUENCE { 705 lispGlobalStatsMapRequestsIn Counter64, 706 lispGlobalStatsMapRequestsOut Counter64, 707 lispGlobalStatsMapRepliesIn Counter64, 708 lispGlobalStatsMapRepliesOut Counter64, 709 lispGlobalStatsMapRegistersIn Counter64, 710 lispGlobalStatsMapRegistersOut Counter64 711 } 713 lispGlobalStatsMapRequestsIn OBJECT-TYPE 714 SYNTAX Counter64 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "Total number of map requests received by this device for 719 any EID prefix of the given address family and Instance ID. 721 Discontinuities in this monotonically increasing value occur 722 at re-initialization of the management system. 723 Discontinuities can also occur as a result of LISP features 724 being removed, which can be detected by observing the value 725 of lispFeaturesRouterTimeStamp." 726 ::= { lispGlobalStatsEntry 1 } 728 lispGlobalStatsMapRequestsOut OBJECT-TYPE 729 SYNTAX Counter64 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "Total number of map requests sent by this device for any 734 EID prefix of the given address family and Instance ID. 736 Discontinuities in this monotonically increasing value occur 737 at re-initialization of the management system. 738 Discontinuities can also occur as a result of LISP features 739 being removed, which can be detected by observing the value 740 of lispFeaturesRouterTimeStamp." 741 ::= { lispGlobalStatsEntry 2 } 743 lispGlobalStatsMapRepliesIn OBJECT-TYPE 744 SYNTAX Counter64 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "Total number of map replies received by this device for any 749 EID prefix of the given address family and Instance ID. 751 Discontinuities in this monotonically increasing value occur 752 at re-initialization of the management system. 753 Discontinuities can also occur as a result of LISP features 754 being removed, which can be detected by observing the value 755 of lispFeaturesRouterTimeStamp." 756 ::= { lispGlobalStatsEntry 3 } 758 lispGlobalStatsMapRepliesOut OBJECT-TYPE 759 SYNTAX Counter64 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "Total number of map replies sent by this device for any EID 764 prefix of the given address family and Instance ID. 766 Discontinuities in this monotonically increasing value occur 767 at re-initialization of the management system. 768 Discontinuities can also occur as a result of LISP features 769 being removed, which can be detected by observing the value 770 of lispFeaturesRouterTimeStamp." 771 ::= { lispGlobalStatsEntry 4 } 773 lispGlobalStatsMapRegistersIn OBJECT-TYPE 774 SYNTAX Counter64 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "Total number of map registers received by this device for 779 any EID prefix of the given address family and Instance ID. 781 Discontinuities in this monotonically increasing value occur 782 at re-initialization of the management system. 783 Discontinuities can also occur as a result of LISP features 784 being removed, which can be detected by observing the value 785 of lispFeaturesRouterTimeStamp." 786 ::= { lispGlobalStatsEntry 5 } 788 lispGlobalStatsMapRegistersOut OBJECT-TYPE 789 SYNTAX Counter64 790 MAX-ACCESS read-only 791 STATUS current 792 DESCRIPTION 793 "Total number of map registers sent by this device for any 794 EID prefix of the given address family and Instance ID. 796 Discontinuities in this monotonically increasing value occur 797 at re-initialization of the management system. 798 Discontinuities can also occur as a result of LISP features 799 being removed, which can be detected by observing the value 800 of lispFeaturesRouterTimeStamp." 801 ::= { lispGlobalStatsEntry 6 } 803 lispMappingDatabaseTable OBJECT-TYPE 804 SYNTAX SEQUENCE OF LispMappingDatabaseEntry 805 MAX-ACCESS not-accessible 806 STATUS current 807 DESCRIPTION 808 "This table represents the EID-to-RLOC mapping database that 809 contains the EID-prefix to RLOC mappings configured on an 810 ETR. In general, this table would be representative of all 811 such mappings for the given LISP site to which this device 812 belongs." 813 REFERENCE 814 "[LISP], Section 6.0." 815 ::= { lispObjects 4 } 817 lispMappingDatabaseEntry OBJECT-TYPE 818 SYNTAX LispMappingDatabaseEntry 820 MAX-ACCESS not-accessible 821 STATUS current 822 DESCRIPTION 823 "An entry (conceptual row) in the lispMappingDatabaseTable." 824 INDEX { lispMappingDatabaseEidLength, 825 lispMappingDatabaseEid } 826 ::= { lispMappingDatabaseTable 1 } 828 LispMappingDatabaseEntry ::= SEQUENCE { 829 lispMappingDatabaseEidLength Integer32, 830 lispMappingDatabaseEid LispAddressType, 831 lispMappingDatabaseLsb Unsigned32, 832 lispMappingDatabaseEidPartitioned TruthValue, 833 lispMappingDatabaseTimeStamp TimeStamp, 834 lispMappingDatabaseDecapOctets Counter64, 835 lispMappingDatabaseDecapPackets Counter64, 836 lispMappingDatabaseEncapOctets Counter64, 837 lispMappingDatabaseEncapPackets Counter64 838 } 840 lispMappingDatabaseEidLength OBJECT-TYPE 841 SYNTAX Integer32 (5..259) 842 MAX-ACCESS not-accessible 843 STATUS current 844 DESCRIPTION 845 "This object gives the octet-length of 846 lispMappingDatabaseEid." 847 ::= { lispMappingDatabaseEntry 1 } 849 lispMappingDatabaseEid OBJECT-TYPE 850 SYNTAX LispAddressType 851 MAX-ACCESS not-accessible 852 STATUS current 853 DESCRIPTION 854 "The EID prefix of the mapping database." 855 ::= { lispMappingDatabaseEntry 2 } 857 lispMappingDatabaseLsb OBJECT-TYPE 858 SYNTAX Unsigned32 (0..4294967295) 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "The locator status bits for this EID prefix." 863 ::= { lispMappingDatabaseEntry 3 } 865 lispMappingDatabaseEidPartitioned OBJECT-TYPE 866 SYNTAX TruthValue 867 MAX-ACCESS read-only 869 STATUS current 870 DESCRIPTION 871 "Indicates if this device is partitioned from the site that 872 contains this EID prefix. If this object is TRUE, then it 873 means this device is partitioned from the site." 874 ::= { lispMappingDatabaseEntry 4 } 876 lispMappingDatabaseTimeStamp OBJECT-TYPE 877 SYNTAX TimeStamp 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "The value of sysUpTime at which the EID Prefix information 882 represented by this mapping database entry was configured 883 on this device. 885 If this information was present at the most recent 886 re-initialization of the local management subsystem, then 887 this object contains a zero value." 888 ::= { lispMappingDatabaseEntry 5 } 890 lispMappingDatabaseDecapOctets OBJECT-TYPE 891 SYNTAX Counter64 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "The number of octets of LISP packets that were decapsulated 896 by this device addressed to a host within this EID-prefix. 898 Discontinuities in this monotonically increasing value occur 899 at re-initialization of the management system. 900 Discontinuities can also occur as a result of LISP features 901 being removed, which can be detected by observing the value 902 of lispMappingDatabaseTimeStamp." 903 ::= { lispMappingDatabaseEntry 6 } 905 lispMappingDatabaseDecapPackets OBJECT-TYPE 906 SYNTAX Counter64 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "The number of LISP packets that were decapsulated by this 911 device addressed to a host within this EID-prefix. 913 Discontinuities in this monotonically increasing value occur 914 at re-initialization of the management system. 915 Discontinuities can also occur as a result of LISP features 916 being removed, which can be detected by observing the value 917 of lispMappingDatabaseTimeStamp." 918 ::= { lispMappingDatabaseEntry 7 } 920 lispMappingDatabaseEncapOctets OBJECT-TYPE 921 SYNTAX Counter64 922 MAX-ACCESS read-only 923 STATUS current 924 DESCRIPTION 925 "The number of octets of LISP packets that were encapsulated 926 by this device, whose inner header source address matched 927 this EID prefix. 929 Discontinuities in this monotonically increasing value occur 930 at re-initialization of the management system. 931 Discontinuities can also occur as a result of LISP features 932 being removed, which can be detected by observing the value 933 of lispMappingDatabaseTimeStamp." 934 ::= { lispMappingDatabaseEntry 8 } 936 lispMappingDatabaseEncapPackets OBJECT-TYPE 937 SYNTAX Counter64 938 MAX-ACCESS read-only 939 STATUS current 940 DESCRIPTION 941 "The number of LISP packets that were encapsulated by this 942 device whose inner header source address matched this EID 943 prefix. 945 Discontinuities in this monotonically increasing value occur 946 at re-initialization of the management system. 947 Discontinuities can also occur as a result of LISP features 948 being removed, which can be detected by observing the value 949 of lispMappingDatabaseTimeStamp." 950 ::= { lispMappingDatabaseEntry 9 } 952 lispMappingDatabaseLocatorTable OBJECT-TYPE 953 SYNTAX SEQUENCE OF LispMappingDatabaseLocatorEntry 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION 957 "This table represents the set of routing locators per EID 958 prefix contained in the EID-to-RLOC database configured on 959 this ETR." 960 REFERENCE 961 "[LISP], Section 6.2." 962 ::= { lispObjects 5 } 964 lispMappingDatabaseLocatorEntry OBJECT-TYPE 965 SYNTAX LispMappingDatabaseLocatorEntry 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "An entry (conceptual row) in the 970 lispMappingDatabaseLocatorTable." 972 INDEX { lispMappingDatabaseEidLength, 973 lispMappingDatabaseEid, 974 lispMappingDatabaseLocatorRlocLength, 975 lispMappingDatabaseLocatorRloc } 976 ::= { lispMappingDatabaseLocatorTable 1 } 978 LispMappingDatabaseLocatorEntry ::= SEQUENCE { 979 lispMappingDatabaseLocatorRlocLength Integer32, 980 lispMappingDatabaseLocatorRloc LispAddressType, 981 lispMappingDatabaseLocatorRlocPriority Integer32, 982 lispMappingDatabaseLocatorRlocWeight Integer32, 983 lispMappingDatabaseLocatorRlocMPriority Integer32, 984 lispMappingDatabaseLocatorRlocMWeight Integer32, 985 lispMappingDatabaseLocatorRlocState INTEGER, 986 lispMappingDatabaseLocatorRlocLocal INTEGER, 987 lispMappingDatabaseLocatorRlocTimeStamp TimeStamp, 988 lispMappingDatabaseLocatorRlocDecapOctets Counter64, 989 lispMappingDatabaseLocatorRlocDecapPackets Counter64, 990 lispMappingDatabaseLocatorRlocEncapOctets Counter64, 991 lispMappingDatabaseLocatorRlocEncapPackets Counter64 992 } 994 lispMappingDatabaseLocatorRlocLength OBJECT-TYPE 995 SYNTAX Integer32 (5..259) 996 MAX-ACCESS not-accessible 997 STATUS current 998 DESCRIPTION 999 "This object is used to get the octet-length of 1000 lispMappingDatabaseLocatorRloc, the next object." 1001 ::= { lispMappingDatabaseLocatorEntry 1 } 1003 lispMappingDatabaseLocatorRloc OBJECT-TYPE 1004 SYNTAX LispAddressType 1005 MAX-ACCESS not-accessible 1006 STATUS current 1007 DESCRIPTION 1008 "This object is a locator for the given EID prefix in the 1009 mapping database." 1010 ::= { lispMappingDatabaseLocatorEntry 2 } 1012 lispMappingDatabaseLocatorRlocPriority OBJECT-TYPE 1013 SYNTAX Integer32 (0..255) 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "The unicast priority of the RLOC." 1018 ::= { lispMappingDatabaseLocatorEntry 3 } 1020 lispMappingDatabaseLocatorRlocWeight OBJECT-TYPE 1021 SYNTAX Integer32 (0..100) 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "The unicast weight of the RLOC." 1026 ::= { lispMappingDatabaseLocatorEntry 4 } 1028 lispMappingDatabaseLocatorRlocMPriority OBJECT-TYPE 1029 SYNTAX Integer32 (0..255) 1030 MAX-ACCESS read-only 1031 STATUS current 1032 DESCRIPTION 1033 "The multicast priority of the RLOC." 1034 ::= { lispMappingDatabaseLocatorEntry 5 } 1036 lispMappingDatabaseLocatorRlocMWeight OBJECT-TYPE 1037 SYNTAX Integer32 (0..100) 1038 MAX-ACCESS read-only 1039 STATUS current 1040 DESCRIPTION 1041 "The multicast weight of the RLOC." 1042 ::= { lispMappingDatabaseLocatorEntry 6 } 1044 lispMappingDatabaseLocatorRlocState OBJECT-TYPE 1045 SYNTAX INTEGER { 1046 up (1), 1047 down (2), 1048 unreachable (3) 1049 } 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION 1053 "The state of this RLOC as per this device. 1054 (1 = RLOC is up; 2 = RLOC is down; 3 = RLOC is unreachable)." 1055 ::= { lispMappingDatabaseLocatorEntry 7 } 1057 lispMappingDatabaseLocatorRlocLocal OBJECT-TYPE 1058 SYNTAX INTEGER { 1059 siteself (1), 1060 sitelocal (2) 1061 } 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "Indicates whether the RLOC is local to this device 1066 (or remote, meaning local to another device in the same LISP 1067 site). (1 = RLOC is an address on this device; 2 = RLOC is 1068 an address on another device)." 1069 ::= { lispMappingDatabaseLocatorEntry 8 } 1071 lispMappingDatabaseLocatorRlocTimeStamp OBJECT-TYPE 1072 SYNTAX TimeStamp 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "The value of sysUpTime at which the RLOC of the EID Prefix 1077 represented by this mapping database entry was configured 1078 on this device. 1080 If this information was present at the most recent 1081 re-initialization of the local management subsystem, then 1082 this object contains a zero value." 1083 ::= { lispMappingDatabaseLocatorEntry 9 } 1085 lispMappingDatabaseLocatorRlocDecapOctets OBJECT-TYPE 1086 SYNTAX Counter64 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "The number of octets of LISP packets that were 1091 addressed to this RLOC of the EID-prefix and 1092 were decapsulated. 1094 Discontinuities in this monotonically increasing value occur 1095 at re-initialization of the management system. 1096 Discontinuities can also occur as a result of database 1097 mappings getting re-configured or RLOC status changes, which 1098 can be detected by observing the value of 1099 lispMappingDatabaseLocatorRlocTimeStamp." 1100 ::= { lispMappingDatabaseLocatorEntry 10 } 1102 lispMappingDatabaseLocatorRlocDecapPackets OBJECT-TYPE 1103 SYNTAX Counter64 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "The number of LISP packets that were addressed to this RLOC 1108 of the EID-prefix and were decapsulated. 1110 Discontinuities in this monotonically increasing value occur 1111 at re-initialization of the management system. 1112 Discontinuities can also occur as a result of database 1113 mappings getting re-configured or RLOC status changes, which 1114 can be detected by observing the value of 1115 lispMappingDatabaseLocatorRlocTimeStamp." 1117 ::= { lispMappingDatabaseLocatorEntry 11 } 1119 lispMappingDatabaseLocatorRlocEncapOctets OBJECT-TYPE 1120 SYNTAX Counter64 1121 MAX-ACCESS read-only 1122 STATUS current 1123 DESCRIPTION 1124 "The number of octets of LISP packets that were encapsulated 1125 by this device using this RLOC address as the source, and 1126 that were sourced by an address of this EID-prefix. 1128 Discontinuities in this monotonically increasing value occur 1129 at re-initialization of the management system. 1130 Discontinuities can also occur as a result of database 1131 mappings getting re-configured or RLOC status changes, which 1132 can be detected by observing the value of 1133 lispMappingDatabaseLocatorRlocTimeStamp." 1134 ::= { lispMappingDatabaseLocatorEntry 12 } 1136 lispMappingDatabaseLocatorRlocEncapPackets OBJECT-TYPE 1137 SYNTAX Counter64 1138 MAX-ACCESS read-only 1139 STATUS current 1140 DESCRIPTION 1141 "The number of LISP packets that were encapsulated by this 1142 device using this RLOC address as the source, and that were 1143 sourced by an address of this EID-prefix. 1145 Discontinuities in this monotonically increasing value occur 1146 at re-initialization of the management system. 1147 Discontinuities can also occur as a result of database 1148 mappings getting re-configured or RLOC status changes, which 1149 can be detected by observing the value of 1150 lispMappingDatabaseLocatorRlocTimeStamp." 1151 ::= { lispMappingDatabaseLocatorEntry 13 } 1153 lispMapCacheTable OBJECT-TYPE 1154 SYNTAX SEQUENCE OF LispMapCacheEntry 1155 MAX-ACCESS not-accessible 1156 STATUS current 1157 DESCRIPTION 1158 "This table represents the short-lived, on-demand table on 1159 an ITR that stores, tracks, and is responsible for 1160 timing-out and otherwise validating EID-to-RLOC mappings." 1161 REFERENCE 1162 "[LISP], Section 6.0., Section 12.0." 1163 ::= { lispObjects 6 } 1165 lispMapCacheEntry OBJECT-TYPE 1166 SYNTAX LispMapCacheEntry 1167 MAX-ACCESS not-accessible 1168 STATUS current 1169 DESCRIPTION 1170 "An entry (conceptual row) in the 1171 lispMapCacheTable." 1172 INDEX { lispMapCacheEidLength, 1173 lispMapCacheEid } 1174 ::= { lispMapCacheTable 1 } 1176 LispMapCacheEntry ::= SEQUENCE { 1177 lispMapCacheEidLength Integer32, 1178 lispMapCacheEid LispAddressType, 1179 lispMapCacheEidTimeStamp TimeStamp, 1180 lispMapCacheEidExpiryTime TimeTicks, 1181 lispMapCacheEidState TruthValue, 1182 lispMapCacheEidAuthoritative TruthValue, 1183 lispMapCacheEidDecapOctets Counter64, 1184 lispMapCacheEidDecapPackets Counter64, 1185 lispMapCacheEidEncapOctets Counter64, 1186 lispMapCacheEidEncapPackets Counter64 1187 } 1189 lispMapCacheEidLength OBJECT-TYPE 1190 SYNTAX Integer32 (5..259) 1191 MAX-ACCESS not-accessible 1192 STATUS current 1193 DESCRIPTION 1194 "This object is used to get the octet-length of 1195 lispMapCacheEid, the next object." 1196 ::= { lispMapCacheEntry 1 } 1198 lispMapCacheEid OBJECT-TYPE 1199 SYNTAX LispAddressType 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "The EID prefix in the mapping cache." 1204 ::= { lispMapCacheEntry 2 } 1206 lispMapCacheEidTimeStamp OBJECT-TYPE 1207 SYNTAX TimeStamp 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "The value of sysUpTime at which the EID Prefix information 1212 represented by this entry was learned by this device. 1214 If this information was present at the most recent 1215 re-initialization of the local management subsystem, then 1216 this object contains a zero value." 1217 ::= { lispMapCacheEntry 3 } 1219 lispMapCacheEidExpiryTime OBJECT-TYPE 1220 SYNTAX TimeTicks 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "The time remaining before the ITR times-out this 1225 EID prefix." 1226 ::= { lispMapCacheEntry 4 } 1228 lispMapCacheEidState OBJECT-TYPE 1229 SYNTAX TruthValue 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "This object is used to indicate the activity of this EID 1234 prefix. If this object is TRUE, then it means this EID 1235 prefix is seeing activity." 1236 ::= { lispMapCacheEntry 5 } 1238 lispMapCacheEidAuthoritative OBJECT-TYPE 1239 SYNTAX TruthValue 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "This object is used to indicate whether the EID prefix was 1244 installed by an authoritative map-reply. If this object is 1245 TRUE, then it means this EID prefix was installed by an 1246 authoritative map-reply." 1247 ::= { lispMapCacheEntry 6 } 1249 lispMapCacheEidDecapOctets OBJECT-TYPE 1250 SYNTAX Counter64 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "The number of octets of LISP packets that were decapsulated 1255 by this device and were sourced from a remote host within 1256 this EID-prefix. 1258 Discontinuities in this monotonically increasing value occur 1259 at re-initialization of the management system. 1260 Discontinuities can also occur as a result of cache being 1261 removed and replaced, which can be detected by observing the 1262 value of lispMapCacheEidTimeStamp." 1263 ::= { lispMapCacheEntry 7 } 1265 lispMapCacheEidDecapPackets OBJECT-TYPE 1266 SYNTAX Counter64 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "The number of LISP packets that were decapsulated by this 1271 device and were sourced from a remote host within this 1272 EID-prefix. 1274 Discontinuities in this monotonically increasing value occur 1275 at re-initialization of the management system. 1276 Discontinuities can also occur as a result of cache being 1277 removed and replaced, which can be detected by observing the 1278 value of lispMapCacheEidTimeStamp." 1279 ::= { lispMapCacheEntry 8 } 1281 lispMapCacheEidEncapOctets OBJECT-TYPE 1282 SYNTAX Counter64 1283 MAX-ACCESS read-only 1284 STATUS current 1285 DESCRIPTION 1286 "The number of octets of LISP packets that were encapsulated 1287 by this device using the given EID-prefix in the map cache. 1289 Discontinuities in this monotonically increasing value occur 1290 at re-initialization of the management system. 1291 Discontinuities can also occur as a result of cache being 1292 removed and replaced, which can be detected by observing the 1293 value of lispMapCacheEidTimeStamp." 1294 ::= { lispMapCacheEntry 9 } 1296 lispMapCacheEidEncapPackets OBJECT-TYPE 1297 SYNTAX Counter64 1298 MAX-ACCESS read-only 1299 STATUS current 1300 DESCRIPTION 1301 "The number of LISP packets that were encapsulated by this 1302 device using the given EID-prefix in the map cache. 1304 Discontinuities in this monotonically increasing value occur 1305 at re-initialization of the management system. 1306 Discontinuities can also occur as a result of cache being 1307 removed and replaced, which can be detected by observing the 1308 value of lispMapCacheEidTimeStamp." 1309 ::= { lispMapCacheEntry 10 } 1311 lispMapCacheLocatorTable OBJECT-TYPE 1312 SYNTAX SEQUENCE OF LispMapCacheLocatorEntry 1313 MAX-ACCESS not-accessible 1314 STATUS current 1315 DESCRIPTION 1316 "This table represents the set of locators per EID prefix 1317 contained in the map-cache table of an ITR." 1318 REFERENCE 1319 "[LISP], Section 6.3." 1320 ::= { lispObjects 7 } 1322 lispMapCacheLocatorEntry OBJECT-TYPE 1323 SYNTAX LispMapCacheLocatorEntry 1324 MAX-ACCESS not-accessible 1325 STATUS current 1326 DESCRIPTION 1327 "An entry (conceptual row) in the 1328 lispMapCacheLocatorTable." 1329 INDEX { lispMapCacheEidLength, 1330 lispMapCacheEid, 1331 lispMapCacheLocatorRlocLength, 1332 lispMapCacheLocatorRloc } 1333 ::= { lispMapCacheLocatorTable 1 } 1335 LispMapCacheLocatorEntry ::= SEQUENCE { 1336 lispMapCacheLocatorRlocLength Integer32, 1337 lispMapCacheLocatorRloc LispAddressType, 1338 lispMapCacheLocatorRlocPriority Integer32, 1339 lispMapCacheLocatorRlocWeight Integer32, 1340 lispMapCacheLocatorRlocMPriority Integer32, 1341 lispMapCacheLocatorRlocMWeight Integer32, 1342 lispMapCacheLocatorRlocState INTEGER, 1343 lispMapCacheLocatorRlocTimeStamp TimeStamp, 1344 lispMapCacheLocatorRlocLastPriorityChange TimeTicks, 1345 lispMapCacheLocatorRlocLastWeightChange TimeTicks, 1346 lispMapCacheLocatorRlocLastMPriorityChange TimeTicks, 1347 lispMapCacheLocatorRlocLastMWeightChange TimeTicks, 1348 lispMapCacheLocatorRlocLastStateChange TimeTicks, 1349 lispMapCacheLocatorRlocRtt TimeTicks, 1350 lispMapCacheLocatorRlocDecapOctets Counter64, 1351 lispMapCacheLocatorRlocDecapPackets Counter64, 1352 lispMapCacheLocatorRlocEncapOctets Counter64, 1353 lispMapCacheLocatorRlocEncapPackets Counter64 1354 } 1356 lispMapCacheLocatorRlocLength OBJECT-TYPE 1357 SYNTAX Integer32 (5..259) 1358 MAX-ACCESS not-accessible 1359 STATUS current 1360 DESCRIPTION 1361 "This object is used to get the octet-length of 1362 lispMapCacheLocatorRloc, the next object." 1363 ::= { lispMapCacheLocatorEntry 1 } 1365 lispMapCacheLocatorRloc OBJECT-TYPE 1366 SYNTAX LispAddressType 1367 MAX-ACCESS not-accessible 1368 STATUS current 1369 DESCRIPTION 1370 "The locator for the EID prefix in the mapping cache." 1371 ::= { lispMapCacheLocatorEntry 2 } 1373 lispMapCacheLocatorRlocPriority OBJECT-TYPE 1374 SYNTAX Integer32 (0..255) 1375 MAX-ACCESS read-only 1376 STATUS current 1377 DESCRIPTION 1378 "The unicast priority of the RLOC for this EID prefix 1379 (0-255); lower more preferred. " 1380 ::= { lispMapCacheLocatorEntry 3 } 1382 lispMapCacheLocatorRlocWeight OBJECT-TYPE 1383 SYNTAX Integer32 (0..100) 1384 MAX-ACCESS read-only 1385 STATUS current 1386 DESCRIPTION 1387 "The unicast weight of the RLOC for this EID prefix 1388 (0 - 100) percentage. " 1389 ::= { lispMapCacheLocatorEntry 4 } 1391 lispMapCacheLocatorRlocMPriority OBJECT-TYPE 1392 SYNTAX Integer32 (0..255) 1393 MAX-ACCESS read-only 1394 STATUS current 1395 DESCRIPTION 1396 "The multicast priority of the RLOC for this EID prefix 1397 (0-255); lower more preferred." 1398 ::= { lispMapCacheLocatorEntry 5 } 1400 lispMapCacheLocatorRlocMWeight OBJECT-TYPE 1401 SYNTAX Integer32 (0..100) 1402 MAX-ACCESS read-only 1403 STATUS current 1404 DESCRIPTION 1405 "The multicast weight of the RLOC for this EID prefix 1406 (0 - 100) percentage." 1408 ::= { lispMapCacheLocatorEntry 6 } 1410 lispMapCacheLocatorRlocState OBJECT-TYPE 1411 SYNTAX INTEGER { 1412 up (1), 1413 down (2) 1414 } 1415 MAX-ACCESS read-only 1416 STATUS current 1417 DESCRIPTION 1418 "The state of this RLOC as per this device 1419 (1 = RLOC is up; 2 = RLOC is down)." 1420 ::= { lispMapCacheLocatorEntry 7 } 1422 lispMapCacheLocatorRlocTimeStamp OBJECT-TYPE 1423 SYNTAX TimeStamp 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "The value of sysUpTime at which the RLOC of EID prefix 1428 information represented by this entry was learned by 1429 this device. 1431 If this information was present at the most recent 1432 re-initialization of the local management subsystem, 1433 then this object contains a zero value." 1434 ::= { lispMapCacheLocatorEntry 8 } 1436 lispMapCacheLocatorRlocLastPriorityChange OBJECT-TYPE 1437 SYNTAX TimeTicks 1438 MAX-ACCESS read-only 1439 STATUS current 1440 DESCRIPTION 1441 "Time since the last change of the unicast priority of the 1442 RLOC for this EID prefix." 1443 ::= { lispMapCacheLocatorEntry 9 } 1445 lispMapCacheLocatorRlocLastWeightChange OBJECT-TYPE 1446 SYNTAX TimeTicks 1447 MAX-ACCESS read-only 1448 STATUS current 1449 DESCRIPTION 1450 "Time since the last change of the unicast weight of the 1451 RLOC for this EID prefix." 1452 ::= { lispMapCacheLocatorEntry 10 } 1454 lispMapCacheLocatorRlocLastMPriorityChange OBJECT-TYPE 1455 SYNTAX TimeTicks 1456 MAX-ACCESS read-only 1457 STATUS current 1458 DESCRIPTION 1459 "Time since the last change of the multicast priority of the 1460 RLOC for this EID prefix." 1461 ::= { lispMapCacheLocatorEntry 11 } 1463 lispMapCacheLocatorRlocLastMWeightChange OBJECT-TYPE 1464 SYNTAX TimeTicks 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "Time since the last change of the multicast weight of the 1469 RLOC for this EID prefix." 1470 ::= { lispMapCacheLocatorEntry 12 } 1472 lispMapCacheLocatorRlocLastStateChange OBJECT-TYPE 1473 SYNTAX TimeTicks 1474 MAX-ACCESS read-only 1475 STATUS current 1476 DESCRIPTION 1477 "Time since the last change of the up/down state of the 1478 RLOC for this EID prefix." 1479 ::= { lispMapCacheLocatorEntry 13 } 1481 lispMapCacheLocatorRlocRtt OBJECT-TYPE 1482 SYNTAX TimeTicks 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "Round trip time of RLOC probe and map-reply for this RLOC 1487 address for this prefix." 1488 ::= { lispMapCacheLocatorEntry 14 } 1490 lispMapCacheLocatorRlocDecapOctets OBJECT-TYPE 1491 SYNTAX Counter64 1492 MAX-ACCESS read-only 1493 STATUS current 1494 DESCRIPTION 1495 "The number of octets of LISP packets that were decapsulated 1496 by this device and were sourced from a remote host within 1497 this EID-prefix and were encapsulated for this RLOC. 1499 Discontinuities in this monotonically increasing value occur 1500 at re-initialization of the management system. 1501 Discontinuities can also occur as a result of RLOC of cache 1502 being removed and replaced, which can be detected by 1503 observing the value of lispMapCacheLocatorRlocTimeStamp." 1505 ::= { lispMapCacheLocatorEntry 15 } 1507 lispMapCacheLocatorRlocDecapPackets OBJECT-TYPE 1508 SYNTAX Counter64 1509 MAX-ACCESS read-only 1510 STATUS current 1511 DESCRIPTION 1512 "The number of LISP packets that were decapsulated by this 1513 device and were sourced from a remote host within this 1514 EID-prefix and were encapsulated for this RLOC. 1516 Discontinuities in this monotonically increasing value occur 1517 at re-initialization of the management system. 1518 Discontinuities can also occur as a result of RLOC of cache 1519 being removed and replaced, which can be detected by 1520 observing the value of lispMapCacheLocatorRlocTimeStamp." 1521 ::= { lispMapCacheLocatorEntry 16 } 1523 lispMapCacheLocatorRlocEncapOctets OBJECT-TYPE 1524 SYNTAX Counter64 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "The number of octets of LISP packets that matched this 1529 EID prefix and were encapsulated using this RLOC address. 1531 Discontinuities in this monotonically increasing value occur 1532 at re-initialization of the management system. 1533 Discontinuities can also occur as a result of RLOC of cache 1534 being removed and replaced, which can be detected by 1535 observing the value of lispMapCacheLocatorRlocTimeStamp." 1536 ::= { lispMapCacheLocatorEntry 17 } 1538 lispMapCacheLocatorRlocEncapPackets OBJECT-TYPE 1539 SYNTAX Counter64 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "The number of LISP packets that matched this EID prefix 1544 and were encapsulated using this RLOC address. 1546 Discontinuities in this monotonically increasing value occur 1547 at re-initialization of the management system. 1548 Discontinuities can also occur as a result of RLOC of cache 1549 being removed and replaced, which can be detected by 1550 observing the value of lispMapCacheLocatorRlocTimeStamp." 1551 ::= { lispMapCacheLocatorEntry 18 } 1553 lispConfiguredLocatorTable OBJECT-TYPE 1554 SYNTAX SEQUENCE OF LispConfiguredLocatorEntry 1555 MAX-ACCESS not-accessible 1556 STATUS current 1557 DESCRIPTION 1558 "This table represents the set of routing locators 1559 configured on this device. Note that the Proxy-ITR 1560 configured addresses are treated as routing locators 1561 and therefore can be part of this table." 1562 REFERENCE 1563 "[LISP], Section 6.3." 1564 ::= { lispObjects 8 } 1566 lispConfiguredLocatorEntry OBJECT-TYPE 1567 SYNTAX LispConfiguredLocatorEntry 1568 MAX-ACCESS not-accessible 1569 STATUS current 1570 DESCRIPTION 1571 "An entry (conceptual row) in the 1572 lispConfiguredLocatorTable." 1573 INDEX { lispConfiguredLocatorRlocLength, 1574 lispConfiguredLocatorRloc } 1575 ::= { lispConfiguredLocatorTable 1 } 1577 LispConfiguredLocatorEntry ::= SEQUENCE { 1578 lispConfiguredLocatorRlocLength Integer32, 1579 lispConfiguredLocatorRloc LispAddressType, 1580 lispConfiguredLocatorRlocState INTEGER, 1581 lispConfiguredLocatorRlocLocal INTEGER, 1582 lispConfiguredLocatorRlocTimeStamp TimeStamp, 1583 lispConfiguredLocatorRlocDecapOctets Counter64, 1584 lispConfiguredLocatorRlocDecapPackets Counter64, 1585 lispConfiguredLocatorRlocEncapOctets Counter64, 1586 lispConfiguredLocatorRlocEncapPackets Counter64 1587 } 1589 lispConfiguredLocatorRlocLength OBJECT-TYPE 1590 SYNTAX Integer32 (5..259) 1591 MAX-ACCESS not-accessible 1592 STATUS current 1593 DESCRIPTION 1594 "This object is used to get the octet-length of 1595 lispConfiguredLocatorRloc, the next object." 1596 ::= { lispConfiguredLocatorEntry 1 } 1598 lispConfiguredLocatorRloc OBJECT-TYPE 1599 SYNTAX LispAddressType 1600 MAX-ACCESS not-accessible 1601 STATUS current 1602 DESCRIPTION 1603 "This object is a RLOC address configured on this device. 1604 It can be an RLOC that is local to this device or can be an 1605 RLOC which belongs to another ETR within the same site. 1606 Proxy-ITR address is treated as an RLOC." 1607 ::= { lispConfiguredLocatorEntry 2 } 1609 lispConfiguredLocatorRlocState OBJECT-TYPE 1610 SYNTAX INTEGER { 1611 up (1), 1612 down (2), 1613 unreachable (3) 1614 } 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "The state of this RLOC as per this device. (1 = RLOC is up; 1619 2 = RLOC is down; 3 = RLOC is unreachable)." 1620 ::= { lispConfiguredLocatorEntry 3 } 1622 lispConfiguredLocatorRlocLocal OBJECT-TYPE 1623 SYNTAX INTEGER { 1624 siteself (1), 1625 sitelocal (2) 1626 } 1627 MAX-ACCESS read-only 1628 STATUS current 1629 DESCRIPTION 1630 "Indicates whether the RLOC is local to this device (or 1631 remote, meaning local to another device in the same LISP 1632 site). (1 = RLOC is an address on this device; 2 = RLOC is 1633 an address on another device)." 1634 ::= { lispConfiguredLocatorEntry 4 } 1636 lispConfiguredLocatorRlocTimeStamp OBJECT-TYPE 1637 SYNTAX TimeStamp 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "The value of sysUpTime at which the RLOC was configured on 1642 this device. 1644 If this information was present at the most recent 1645 re-initialization of the local management subsystem, then 1646 this object contains a zero value." 1647 ::= { lispConfiguredLocatorEntry 5 } 1649 lispConfiguredLocatorRlocDecapOctets OBJECT-TYPE 1650 SYNTAX Counter64 1651 MAX-ACCESS read-only 1652 STATUS current 1653 DESCRIPTION 1654 "The number of octets of LISP packets that were addressed to 1655 this RLOC and were decapsulated. 1657 Discontinuities in this monotonically increasing value occur 1658 at re-initialization of the management system. 1659 Discontinuities can also occur as a result of configured 1660 RLOC being removed and replaced, which can be detected by 1661 observing the value of lispConfiguredLocatorRlocTimeStamp." 1662 ::= { lispConfiguredLocatorEntry 6 } 1664 lispConfiguredLocatorRlocDecapPackets OBJECT-TYPE 1665 SYNTAX Counter64 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "The number of LISP packets that were addressed to this RLOC 1670 and were decapsulated. 1672 Discontinuities in this monotonically increasing value occur 1673 at re-initialization of the management system. 1674 Discontinuities can also occur as a result of configured 1675 RLOC being removed and replaced, which can be detected by 1676 observing the value of lispConfiguredLocatorRlocTimeStamp." 1677 ::= { lispConfiguredLocatorEntry 7 } 1679 lispConfiguredLocatorRlocEncapOctets OBJECT-TYPE 1680 SYNTAX Counter64 1681 MAX-ACCESS read-only 1682 STATUS current 1683 DESCRIPTION 1684 "The number of octets of LISP packets that were encapsulated 1685 by this device using this RLOC address as the source. 1687 Discontinuities in this monotonically increasing value occur 1688 at re-initialization of the management system. 1689 Discontinuities can also occur as a result of configured 1690 RLOC being removed and replaced, which can be detected by 1691 observing the value of lispConfiguredLocatorRlocTimeStamp." 1692 ::= { lispConfiguredLocatorEntry 8 } 1694 lispConfiguredLocatorRlocEncapPackets OBJECT-TYPE 1695 SYNTAX Counter64 1696 MAX-ACCESS read-only 1697 STATUS current 1698 DESCRIPTION 1699 "The number of LISP packets that were encapsulated by this 1700 device using this RLOC address as the source. 1702 Discontinuities in this monotonically increasing value occur 1703 at re-initialization of the management system. 1704 Discontinuities can also occur as a result of configured 1705 RLOC being removed and replaced, which can be detected by 1706 observing the value of lispConfiguredLocatorRlocTimeStamp." 1707 ::= { lispConfiguredLocatorEntry 9 } 1709 lispEidRegistrationTable OBJECT-TYPE 1710 SYNTAX SEQUENCE OF LispEidRegistrationEntry 1711 MAX-ACCESS not-accessible 1712 STATUS current 1713 DESCRIPTION 1714 "This table provides the properties of each LISP EID prefix 1715 that is registered with this device when configured to be 1716 a Map-Server." 1717 REFERENCE 1718 "[LISP-MS], Section 4.0." 1719 ::= { lispObjects 9 } 1721 lispEidRegistrationEntry OBJECT-TYPE 1722 SYNTAX LispEidRegistrationEntry 1723 MAX-ACCESS not-accessible 1724 STATUS current 1725 DESCRIPTION 1726 "An entry (conceptual row) in the lispEidRegistrationTable." 1727 INDEX { lispEidRegistrationEidLength, 1728 lispEidRegistrationEid } 1729 ::= { lispEidRegistrationTable 1 } 1731 LispEidRegistrationEntry ::= SEQUENCE { 1732 lispEidRegistrationEidLength Integer32, 1733 lispEidRegistrationEid LispAddressType, 1734 lispEidRegistrationSiteName OCTET STRING, 1735 lispEidRegistrationSiteDescription OCTET STRING, 1736 lispEidRegistrationIsRegistered TruthValue, 1737 lispEidRegistrationFirstTimeStamp TimeStamp, 1738 lispEidRegistrationLastTimeStamp TimeStamp, 1739 lispEidRegistrationLastRegisterSenderLength Integer32, 1740 lispEidRegistrationLastRegisterSender LispAddressType, 1741 lispEidRegistrationRouteTag Unsigned32, 1742 lispEidRegistrationAuthenticationErrors Counter64, 1743 lispEidRegistrationRlocsMismatch Counter64 1744 } 1746 lispEidRegistrationEidLength OBJECT-TYPE 1747 SYNTAX Integer32 (5..259) 1748 MAX-ACCESS not-accessible 1749 STATUS current 1750 DESCRIPTION 1751 "This object is used to get the octet-length of 1752 lispEidRegistrationEid, the next object." 1753 ::= { lispEidRegistrationEntry 1 } 1755 lispEidRegistrationEid OBJECT-TYPE 1756 SYNTAX LispAddressType 1757 MAX-ACCESS not-accessible 1758 STATUS current 1759 DESCRIPTION 1760 "The EID prefix that is being registered." 1761 ::= { lispEidRegistrationEntry 2 } 1763 lispEidRegistrationSiteName OBJECT-TYPE 1764 SYNTAX OCTET STRING (SIZE(0..63)) 1765 MAX-ACCESS read-only 1766 STATUS current 1767 DESCRIPTION 1768 "Site name used by a Map-Server to distinguish different 1769 LISP sites that are registering with it." 1770 ::= { lispEidRegistrationEntry 3 } 1772 lispEidRegistrationSiteDescription OBJECT-TYPE 1773 SYNTAX OCTET STRING (SIZE(0..255)) 1774 MAX-ACCESS read-only 1775 STATUS current 1776 DESCRIPTION 1777 "Description for a site name used by a Map-Server. The EID 1778 prefix that is being registered belongs to this site." 1779 ::= { lispEidRegistrationEntry 4 } 1781 lispEidRegistrationIsRegistered OBJECT-TYPE 1782 SYNTAX TruthValue 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "Indicates the registration status of the given EID prefix. 1787 If this object is TRUE, then it means the EID prefix is 1788 registered." 1789 ::= { lispEidRegistrationEntry 5 } 1791 lispEidRegistrationFirstTimeStamp OBJECT-TYPE 1792 SYNTAX TimeStamp 1793 MAX-ACCESS read-only 1794 STATUS current 1795 DESCRIPTION 1796 "The value of sysUpTime at which the first valid register 1797 message for the EID Prefix information represented by this 1798 entry was received by this device. 1800 If this information was present at the most recent 1801 re-initialization of the local management subsystem, then 1802 this object contains a zero value." 1803 ::= { lispEidRegistrationEntry 6 } 1805 lispEidRegistrationLastTimeStamp OBJECT-TYPE 1806 SYNTAX TimeStamp 1807 MAX-ACCESS read-only 1808 STATUS current 1809 DESCRIPTION 1810 "The value of sysUpTime at which the last valid register 1811 message for the EID Prefix information represented by this 1812 entry was received by this device. 1814 If this information was present at the most recent 1815 re-initialization of the local management subsystem, then 1816 this object contains a zero value." 1817 ::= { lispEidRegistrationEntry 7 } 1819 lispEidRegistrationLastRegisterSenderLength OBJECT-TYPE 1820 SYNTAX Integer32 (5..259) 1821 MAX-ACCESS read-only 1822 STATUS current 1823 DESCRIPTION 1824 "This object is used to get the octet-length of 1825 lispEidRegistrationLastRegisterSender, the next 1826 object." 1827 ::= { lispEidRegistrationEntry 8 } 1829 lispEidRegistrationLastRegisterSender OBJECT-TYPE 1830 SYNTAX LispAddressType 1831 MAX-ACCESS read-only 1832 STATUS current 1833 DESCRIPTION 1834 "Source address of the last valid register message for the 1835 given EID prefix that was received by this device." 1836 ::= { lispEidRegistrationEntry 9 } 1838 lispEidRegistrationRouteTag OBJECT-TYPE 1839 SYNTAX Unsigned32 (0..4294967295) 1840 MAX-ACCESS read-only 1841 STATUS current 1842 DESCRIPTION 1843 "Value of the routing table tag assigned to the given EID 1844 prefix." 1845 ::= { lispEidRegistrationEntry 10 } 1847 lispEidRegistrationAuthenticationErrors OBJECT-TYPE 1848 SYNTAX Counter64 1849 MAX-ACCESS read-only 1850 STATUS current 1851 DESCRIPTION 1852 "Count of total authentication errors of map-registers 1853 received for the given EID prefix. 1855 Discontinuities in this monotonically increasing value occur 1856 at re-initialization of the management system. 1857 Discontinuities can also occur as a result of site config 1858 changes, which can be detected by observing the value of 1859 lispEidRegistrationFirstTimeStamp." 1860 ::= { lispEidRegistrationEntry 11 } 1862 lispEidRegistrationRlocsMismatch OBJECT-TYPE 1863 SYNTAX Counter64 1864 MAX-ACCESS read-only 1865 STATUS current 1866 DESCRIPTION 1867 "Count of total map-registers received that had at least one 1868 RLOC that was not in the allowed list of RLOCs for the given 1869 EID prefix. 1871 Discontinuities in this monotonically increasing value occur 1872 at re-initialization of the management system. 1873 Discontinuities can also occur as a result of site config 1874 changes, which can be detected by observing the value of 1875 lispEidRegistrationFirstTimeStamp." 1876 ::= { lispEidRegistrationEntry 12 } 1878 lispEidRegistrationEtrTable OBJECT-TYPE 1879 SYNTAX SEQUENCE OF LispEidRegistrationEtrEntry 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "This table provides the properties of ETRs that register 1884 the given EID prefix with this device when configured to 1885 be a Map-Server." 1887 REFERENCE 1888 "[LISP], Section 6.1." 1889 ::= { lispObjects 10 } 1891 lispEidRegistrationEtrEntry OBJECT-TYPE 1892 SYNTAX LispEidRegistrationEtrEntry 1893 MAX-ACCESS not-accessible 1894 STATUS current 1895 DESCRIPTION 1896 "An entry (conceptual row) in the 1897 lispEidRegistrationEtrTable." 1898 INDEX { lispEidRegistrationEidLength, 1899 lispEidRegistrationEid, 1900 lispEidRegistrationEtrSenderLength, 1901 lispEidRegistrationEtrSender } 1902 ::= { lispEidRegistrationEtrTable 1 } 1904 LispEidRegistrationEtrEntry ::= SEQUENCE { 1905 lispEidRegistrationEtrSenderLength Integer32, 1906 lispEidRegistrationEtrSender LispAddressType, 1907 lispEidRegistrationEtrLastTimeStamp TimeStamp, 1908 lispEidRegistrationEtrTtl Unsigned32, 1909 lispEidRegistrationEtrProxyReply TruthValue, 1910 lispEidRegistrationEtrWantsMapNotify TruthValue 1911 } 1913 lispEidRegistrationEtrSenderLength OBJECT-TYPE 1914 SYNTAX Integer32 (5..259) 1915 MAX-ACCESS not-accessible 1916 STATUS current 1917 DESCRIPTION 1918 "This object is used to get the octet-length of 1919 lispEidRegistrationEtrSender, the next object." 1920 ::= { lispEidRegistrationEtrEntry 1 } 1922 lispEidRegistrationEtrSender OBJECT-TYPE 1923 SYNTAX LispAddressType 1924 MAX-ACCESS not-accessible 1925 STATUS current 1926 DESCRIPTION 1927 "Source address of the ETR that is sending valid register 1928 messages for this EID prefix to this device." 1929 ::= { lispEidRegistrationEtrEntry 2 } 1931 lispEidRegistrationEtrLastTimeStamp OBJECT-TYPE 1932 SYNTAX TimeStamp 1933 MAX-ACCESS read-only 1934 STATUS current 1935 DESCRIPTION 1936 "The value of sysUpTime at which the last valid register 1937 message from this ETR for the EID Prefix information 1938 represented by this entry was received by this device. 1940 If this information was present at the most recent 1941 re-initialization of the local management subsystem, 1942 then this object contains a zero value." 1943 ::= { lispEidRegistrationEtrEntry 3 } 1945 lispEidRegistrationEtrTtl OBJECT-TYPE 1946 SYNTAX Unsigned32 1947 MAX-ACCESS read-only 1948 STATUS current 1949 DESCRIPTION 1950 "The Record TTL of the registering ETR device for this 1951 EID prefix." 1952 ::= { lispEidRegistrationEtrEntry 4 } 1954 lispEidRegistrationEtrProxyReply OBJECT-TYPE 1955 SYNTAX TruthValue 1956 MAX-ACCESS read-only 1957 STATUS current 1958 DESCRIPTION 1959 "Indicates proxy-replying status of the registering ETR for 1960 this EID prefix. If this object is TRUE, then it means the 1961 Map-Server can proxy-reply." 1962 ::= { lispEidRegistrationEtrEntry 5 } 1964 lispEidRegistrationEtrWantsMapNotify OBJECT-TYPE 1965 SYNTAX TruthValue 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 "Indicates whether the EID prefix wants Map-Notifications. 1970 If this object is TRUE, then it means the EID prefix wants 1971 Map-Notifications." 1972 ::= { lispEidRegistrationEtrEntry 6 } 1974 lispEidRegistrationLocatorTable OBJECT-TYPE 1975 SYNTAX SEQUENCE OF LispEidRegistrationLocatorEntry 1976 MAX-ACCESS not-accessible 1977 STATUS current 1978 DESCRIPTION 1979 "This table provides the properties of all locators per 1980 LISP site that are served by this device when configured 1981 to be a Map-Server." 1983 REFERENCE 1984 "[LISP], Section 6.1." 1985 ::= { lispObjects 11 } 1987 lispEidRegistrationLocatorEntry OBJECT-TYPE 1988 SYNTAX LispEidRegistrationLocatorEntry 1989 MAX-ACCESS not-accessible 1990 STATUS current 1991 DESCRIPTION 1992 "An entry (conceptual row) in the 1993 lispEidRegistrationLocatorTable." 1994 INDEX { lispEidRegistrationEidLength, 1995 lispEidRegistrationEid, 1996 lispEidRegistrationEtrSenderLength, 1997 lispEidRegistrationEtrSender, 1998 lispEidRegistrationLocatorRlocLength, 1999 lispEidRegistrationLocatorRloc } 2000 ::= { lispEidRegistrationLocatorTable 1 } 2002 LispEidRegistrationLocatorEntry ::= SEQUENCE { 2003 lispEidRegistrationLocatorRlocLength Integer32, 2004 lispEidRegistrationLocatorRloc LispAddressType, 2005 lispEidRegistrationLocatorRlocState INTEGER, 2006 lispEidRegistrationLocatorIsLocal TruthValue, 2007 lispEidRegistrationLocatorPriority Integer32, 2008 lispEidRegistrationLocatorWeight Integer32, 2009 lispEidRegistrationLocatorMPriority Integer32, 2010 lispEidRegistrationLocatorMWeight Integer32 2011 } 2013 lispEidRegistrationLocatorRlocLength OBJECT-TYPE 2014 SYNTAX Integer32 (5..259) 2015 MAX-ACCESS not-accessible 2016 STATUS current 2017 DESCRIPTION 2018 "This object is used to get the octet-length of 2019 lispEidRegistrationLocatorRloc, the next object." 2020 ::= { lispEidRegistrationLocatorEntry 1 } 2022 lispEidRegistrationLocatorRloc OBJECT-TYPE 2023 SYNTAX LispAddressType 2024 MAX-ACCESS not-accessible 2025 STATUS current 2026 DESCRIPTION 2027 "The locator of the given EID prefix being registered by the 2028 given ETR with this device." 2029 ::= { lispEidRegistrationLocatorEntry 2 } 2031 lispEidRegistrationLocatorRlocState OBJECT-TYPE 2032 SYNTAX INTEGER { 2033 up (1), 2034 down (2) 2035 } 2036 MAX-ACCESS read-only 2037 STATUS current 2038 DESCRIPTION 2039 "The cached state of this RLOC received in map-register from 2040 the ETR by the device, in the capacity of a Map-Server. 2041 Value 1 refers to up, value 2 refers to down." 2042 ::= { lispEidRegistrationLocatorEntry 3 } 2044 lispEidRegistrationLocatorIsLocal OBJECT-TYPE 2045 SYNTAX TruthValue 2046 MAX-ACCESS read-only 2047 STATUS current 2048 DESCRIPTION 2049 "Indicates if the given locator is local to the registering 2050 ETR. If this object is TRUE, it means the locator is local." 2051 ::= { lispEidRegistrationLocatorEntry 4 } 2053 lispEidRegistrationLocatorPriority OBJECT-TYPE 2054 SYNTAX Integer32 (0..255) 2055 MAX-ACCESS read-only 2056 STATUS current 2057 DESCRIPTION 2058 "The unicast priority of the RLOC for this EID prefix in the 2059 register message sent by the given ETR." 2060 ::= { lispEidRegistrationLocatorEntry 5 } 2062 lispEidRegistrationLocatorWeight OBJECT-TYPE 2063 SYNTAX Integer32 (0..100) 2064 MAX-ACCESS read-only 2065 STATUS current 2066 DESCRIPTION 2067 "The unicast weight of the RLOC for this EID prefix in the 2068 register message sent by the given ETR." 2069 ::= { lispEidRegistrationLocatorEntry 6 } 2071 lispEidRegistrationLocatorMPriority OBJECT-TYPE 2072 SYNTAX Integer32 (0..255) 2073 MAX-ACCESS read-only 2074 STATUS current 2075 DESCRIPTION 2076 "The multicast priority of the RLOC for this EID prefix in 2077 the register message sent by the given ETR." 2078 ::= { lispEidRegistrationLocatorEntry 7 } 2080 lispEidRegistrationLocatorMWeight OBJECT-TYPE 2081 SYNTAX Integer32 (0..100) 2082 MAX-ACCESS read-only 2083 STATUS current 2084 DESCRIPTION 2085 "The multicast weight of the RLOC for this EID prefix in the 2086 register message sent by the given ETR." 2087 ::= { lispEidRegistrationLocatorEntry 8 } 2089 lispUseMapServerTable OBJECT-TYPE 2090 SYNTAX SEQUENCE OF LispUseMapServerEntry 2091 MAX-ACCESS not-accessible 2092 STATUS current 2093 DESCRIPTION 2094 "This table provides the properties of the map-server(s) 2095 with which this device is configured to register." 2096 REFERENCE 2097 "[LISP-MS], Section 4.3." 2098 ::= { lispObjects 12 } 2100 lispUseMapServerEntry OBJECT-TYPE 2101 SYNTAX LispUseMapServerEntry 2102 MAX-ACCESS not-accessible 2103 STATUS current 2104 DESCRIPTION 2105 "An entry (conceptual row) in the lispUseMapServerTable." 2106 INDEX { lispUseMapServerAddressLength, 2107 lispUseMapServerAddress } 2108 ::= { lispUseMapServerTable 1 } 2110 LispUseMapServerEntry ::= SEQUENCE { 2111 lispUseMapServerAddressLength Integer32, 2112 lispUseMapServerAddress LispAddressType, 2113 lispUseMapServerState INTEGER 2114 } 2116 lispUseMapServerAddressLength OBJECT-TYPE 2117 SYNTAX Integer32 (5..259) 2118 MAX-ACCESS not-accessible 2119 STATUS current 2120 DESCRIPTION 2121 "This object is used to get the octet-length of 2122 lispUseMapServerAddress, the next object." 2123 ::= { lispUseMapServerEntry 1 } 2125 lispUseMapServerAddress OBJECT-TYPE 2126 SYNTAX LispAddressType 2127 MAX-ACCESS not-accessible 2128 STATUS current 2129 DESCRIPTION 2130 "Address of Map-Server configured on this device." 2131 ::= { lispUseMapServerEntry 2 } 2133 lispUseMapServerState OBJECT-TYPE 2134 SYNTAX INTEGER { 2135 up (1), 2136 down (2) 2137 } 2138 MAX-ACCESS read-only 2139 STATUS current 2140 DESCRIPTION 2141 "State of this Map-Server configured on this device 2142 (1 = Map-Server is up; 2 = Map-Server is down)." 2143 ::= { lispUseMapServerEntry 3 } 2145 lispUseMapResolverTable OBJECT-TYPE 2146 SYNTAX SEQUENCE OF LispUseMapResolverEntry 2147 MAX-ACCESS not-accessible 2148 STATUS current 2149 DESCRIPTION 2150 "This table provides the properties of the map-resolver(s) 2151 this device is configured to use." 2152 REFERENCE 2153 "[LISP-MS], Section 4.4." 2154 ::= { lispObjects 13 } 2156 lispUseMapResolverEntry OBJECT-TYPE 2157 SYNTAX LispUseMapResolverEntry 2158 MAX-ACCESS not-accessible 2159 STATUS current 2160 DESCRIPTION 2161 "An entry (conceptual row) in the 2162 lispUseMapResolverTable." 2163 INDEX { lispUseMapResolverAddressLength, 2164 lispUseMapResolverAddress } 2165 ::= { lispUseMapResolverTable 1 } 2167 LispUseMapResolverEntry ::= SEQUENCE { 2168 lispUseMapResolverAddressLength Integer32, 2169 lispUseMapResolverAddress LispAddressType, 2170 lispUseMapResolverState INTEGER 2171 } 2173 lispUseMapResolverAddressLength OBJECT-TYPE 2174 SYNTAX Integer32 (5..259) 2175 MAX-ACCESS not-accessible 2176 STATUS current 2177 DESCRIPTION 2178 "This object is used to get the octet-length of 2179 lispUseMapResolverAddress, the next object." 2180 ::= { lispUseMapResolverEntry 1 } 2182 lispUseMapResolverAddress OBJECT-TYPE 2183 SYNTAX LispAddressType 2184 MAX-ACCESS not-accessible 2185 STATUS current 2186 DESCRIPTION 2187 "Address of map-resolver configured on this device." 2188 ::= { lispUseMapResolverEntry 2 } 2190 lispUseMapResolverState OBJECT-TYPE 2191 SYNTAX INTEGER { 2192 up (1), 2193 down (2) 2194 } 2195 MAX-ACCESS read-only 2196 STATUS current 2197 DESCRIPTION 2198 "State of this Map-Resolver configured on this device 2199 (1 = Map-Resolver is up; 2 = Map-Resolver is down)." 2200 ::= { lispUseMapResolverEntry 3 } 2202 lispUseProxyEtrTable OBJECT-TYPE 2203 SYNTAX SEQUENCE OF LispUseProxyEtrEntry 2204 MAX-ACCESS not-accessible 2205 STATUS current 2206 DESCRIPTION 2207 "This table provides the properties of all Proxy ETRs that 2208 this device is configured to use." 2209 REFERENCE 2210 "[INTERWORK], Section 6.0." 2211 ::= { lispObjects 14 } 2213 lispUseProxyEtrEntry OBJECT-TYPE 2214 SYNTAX LispUseProxyEtrEntry 2215 MAX-ACCESS not-accessible 2216 STATUS current 2217 DESCRIPTION 2218 "An entry (conceptual row) in the 2219 lispUseProxyEtrTable." 2220 INDEX { lispUseProxyEtrAddressLength, 2221 lispUseProxyEtrAddress } 2222 ::= { lispUseProxyEtrTable 1 } 2224 LispUseProxyEtrEntry ::= SEQUENCE { 2225 lispUseProxyEtrAddressLength Integer32, 2226 lispUseProxyEtrAddress LispAddressType, 2227 lispUseProxyEtrPriority Integer32, 2228 lispUseProxyEtrWeight Integer32, 2229 lispUseProxyEtrMPriority Integer32, 2230 lispUseProxyEtrMWeight Integer32, 2231 lispUseProxyEtrState INTEGER 2232 } 2234 lispUseProxyEtrAddressLength OBJECT-TYPE 2235 SYNTAX Integer32 (5..259) 2236 MAX-ACCESS not-accessible 2237 STATUS current 2238 DESCRIPTION 2239 "This object is used to get the octet-length of 2240 lispUseProxyEtrAddress, the next object." 2241 ::= { lispUseProxyEtrEntry 1 } 2243 lispUseProxyEtrAddress OBJECT-TYPE 2244 SYNTAX LispAddressType 2245 MAX-ACCESS not-accessible 2246 STATUS current 2247 DESCRIPTION 2248 "Address of Proxy ETR configured on this device." 2249 ::= { lispUseProxyEtrEntry 2 } 2251 lispUseProxyEtrPriority OBJECT-TYPE 2252 SYNTAX Integer32 (0..255) 2253 MAX-ACCESS read-only 2254 STATUS current 2255 DESCRIPTION 2256 "The unicast priority of the PETR locator." 2257 ::= { lispUseProxyEtrEntry 3 } 2259 lispUseProxyEtrWeight OBJECT-TYPE 2260 SYNTAX Integer32 (0..100) 2261 MAX-ACCESS read-only 2262 STATUS current 2263 DESCRIPTION 2264 "The unicast weight of the PETR locator." 2265 ::= { lispUseProxyEtrEntry 4 } 2267 lispUseProxyEtrMPriority OBJECT-TYPE 2268 SYNTAX Integer32 (0..255) 2269 MAX-ACCESS read-only 2270 STATUS current 2271 DESCRIPTION 2272 "The multicast priority of the PETR locator." 2273 ::= { lispUseProxyEtrEntry 5 } 2275 lispUseProxyEtrMWeight OBJECT-TYPE 2276 SYNTAX Integer32 (0..100) 2277 MAX-ACCESS read-only 2278 STATUS current 2279 DESCRIPTION 2280 "The multicast weight of the PETR locator." 2281 ::= { lispUseProxyEtrEntry 6 } 2283 lispUseProxyEtrState OBJECT-TYPE 2284 SYNTAX INTEGER { 2285 down (0), 2286 up (1) 2287 } 2288 MAX-ACCESS read-only 2289 STATUS current 2290 DESCRIPTION 2291 "State of this Proxy ETR configured on this device 2292 (0 = Proxy ETR is down; 1 = Proxy ETR is up)." 2293 ::= { lispUseProxyEtrEntry 7 } 2295 -- 2296 -- Conformance Information 2297 -- 2299 lispCompliances OBJECT IDENTIFIER ::= { lispConformance 1 } 2300 lispGroups OBJECT IDENTIFIER ::= { lispConformance 2 } 2302 -- 2303 -- Compliance Statements 2304 -- 2306 lispMIBComplianceEtr MODULE-COMPLIANCE 2307 STATUS current 2308 DESCRIPTION 2309 "The compliance statement for LISP ETRs." 2310 MODULE -- this module 2311 MANDATORY-GROUPS { lispMIBEtrGroup } 2313 GROUP lispMIBItrGroup 2314 DESCRIPTION 2315 "This group is optional." 2317 GROUP lispMIBPetrGroup 2318 DESCRIPTION 2319 "This group is optional." 2321 GROUP lispMIBPitrGroup 2322 DESCRIPTION 2323 "This group is optional." 2325 GROUP lispMIBMapServerGroup 2326 DESCRIPTION 2327 "This group is optional." 2329 GROUP lispMIBMapResolverGroup 2330 DESCRIPTION 2331 "This group is optional." 2333 GROUP lispMIBEtrExtendedGroup 2334 DESCRIPTION 2335 "This group is optional." 2337 GROUP lispMIBItrExtendedGroup 2338 DESCRIPTION 2339 "This group is optional." 2341 GROUP lispMIBMapServerExtendedGroup 2342 DESCRIPTION 2343 "This group is optional." 2345 GROUP lispMIBTuningParametersGroup 2346 DESCRIPTION 2347 "This group is optional." 2349 GROUP lispMIBEncapStatisticsGroup 2350 DESCRIPTION 2351 "This group is optional." 2353 GROUP lispMIBDecapStatisticsGroup 2354 DESCRIPTION 2355 "This group is optional." 2357 GROUP lispMIBDiagnosticsGroup 2358 DESCRIPTION 2359 "This group is optional." 2361 GROUP lispMIBVrfGroup 2362 DESCRIPTION 2363 "This group is optional." 2365 ::= { lispCompliances 1 } 2367 lispMIBComplianceItr MODULE-COMPLIANCE 2368 STATUS current 2369 DESCRIPTION 2370 "The compliance statement for LISP ITRs." 2371 MODULE -- this module 2372 MANDATORY-GROUPS { lispMIBItrGroup } 2374 GROUP lispMIBEtrGroup 2375 DESCRIPTION 2376 "This group is optional." 2378 GROUP lispMIBPetrGroup 2379 DESCRIPTION 2380 "This group is optional." 2382 GROUP lispMIBPitrGroup 2383 DESCRIPTION 2384 "This group is optional." 2386 GROUP lispMIBMapServerGroup 2387 DESCRIPTION 2388 "This group is optional." 2390 GROUP lispMIBMapResolverGroup 2391 DESCRIPTION 2392 "This group is optional." 2394 GROUP lispMIBEtrExtendedGroup 2395 DESCRIPTION 2396 "This group is optional." 2398 GROUP lispMIBItrExtendedGroup 2399 DESCRIPTION 2400 "This group is optional." 2402 GROUP lispMIBMapServerExtendedGroup 2403 DESCRIPTION 2404 "This group is optional." 2406 GROUP lispMIBTuningParametersGroup 2407 DESCRIPTION 2408 "This group is optional." 2410 GROUP lispMIBEncapStatisticsGroup 2411 DESCRIPTION 2412 "This group is optional." 2414 GROUP lispMIBDecapStatisticsGroup 2415 DESCRIPTION 2416 "This group is optional." 2418 GROUP lispMIBDiagnosticsGroup 2419 DESCRIPTION 2420 "This group is optional." 2422 GROUP lispMIBVrfGroup 2423 DESCRIPTION 2424 "This group is optional." 2426 ::= { lispCompliances 2 } 2428 lispMIBCompliancePetr MODULE-COMPLIANCE 2429 STATUS current 2430 DESCRIPTION 2431 "The compliance statement for LISP Proxy-ETRs." 2432 MODULE -- this module 2433 MANDATORY-GROUPS { lispMIBPetrGroup } 2435 GROUP lispMIBEtrGroup 2436 DESCRIPTION 2437 "This group is optional." 2439 GROUP lispMIBItrGroup 2440 DESCRIPTION 2441 "This group is optional." 2443 GROUP lispMIBPitrGroup 2444 DESCRIPTION 2445 "This group is optional." 2447 GROUP lispMIBMapServerGroup 2448 DESCRIPTION 2449 "This group is optional." 2451 GROUP lispMIBMapResolverGroup 2452 DESCRIPTION 2453 "This group is optional." 2455 GROUP lispMIBEtrExtendedGroup 2456 DESCRIPTION 2457 "This group is optional." 2459 GROUP lispMIBItrExtendedGroup 2460 DESCRIPTION 2461 "This group is optional." 2463 GROUP lispMIBMapServerExtendedGroup 2464 DESCRIPTION 2465 "This group is optional." 2467 GROUP lispMIBTuningParametersGroup 2468 DESCRIPTION 2469 "This group is optional." 2471 GROUP lispMIBEncapStatisticsGroup 2472 DESCRIPTION 2473 "This group is optional." 2475 GROUP lispMIBDecapStatisticsGroup 2476 DESCRIPTION 2477 "This group is optional." 2479 GROUP lispMIBDiagnosticsGroup 2480 DESCRIPTION 2481 "This group is optional." 2483 GROUP lispMIBVrfGroup 2484 DESCRIPTION 2485 "This group is optional." 2487 ::= { lispCompliances 3 } 2489 lispMIBCompliancePitr MODULE-COMPLIANCE 2490 STATUS current 2491 DESCRIPTION 2492 "The compliance statement for LISP Proxy-ITRs." 2493 MODULE -- this module 2494 MANDATORY-GROUPS { lispMIBPitrGroup } 2496 GROUP lispMIBEtrGroup 2497 DESCRIPTION 2498 "This group is optional." 2500 GROUP lispMIBItrGroup 2501 DESCRIPTION 2502 "This group is optional." 2504 GROUP lispMIBPetrGroup 2505 DESCRIPTION 2506 "This group is optional." 2508 GROUP lispMIBMapServerGroup 2509 DESCRIPTION 2510 "This group is optional." 2512 GROUP lispMIBMapResolverGroup 2513 DESCRIPTION 2514 "This group is optional." 2516 GROUP lispMIBEtrExtendedGroup 2517 DESCRIPTION 2518 "This group is optional." 2520 GROUP lispMIBItrExtendedGroup 2521 DESCRIPTION 2522 "This group is optional." 2524 GROUP lispMIBMapServerExtendedGroup 2525 DESCRIPTION 2526 "This group is optional." 2528 GROUP lispMIBTuningParametersGroup 2529 DESCRIPTION 2530 "This group is optional." 2532 GROUP lispMIBEncapStatisticsGroup 2533 DESCRIPTION 2534 "This group is optional." 2536 GROUP lispMIBDecapStatisticsGroup 2537 DESCRIPTION 2538 "This group is optional." 2540 GROUP lispMIBDiagnosticsGroup 2541 DESCRIPTION 2542 "This group is optional." 2544 GROUP lispMIBVrfGroup 2545 DESCRIPTION 2546 "This group is optional." 2548 ::= { lispCompliances 4 } 2550 lispMIBComplianceMapServer MODULE-COMPLIANCE 2551 STATUS current 2552 DESCRIPTION 2553 "The compliance statement for LISP Map Servers." 2554 MODULE -- this module 2555 MANDATORY-GROUPS { lispMIBMapServerGroup } 2556 GROUP lispMIBEtrGroup 2557 DESCRIPTION 2558 "This group is optional." 2560 GROUP lispMIBItrGroup 2561 DESCRIPTION 2562 "This group is optional." 2564 GROUP lispMIBPetrGroup 2565 DESCRIPTION 2566 "This group is optional." 2568 GROUP lispMIBPitrGroup 2569 DESCRIPTION 2570 "This group is optional." 2572 GROUP lispMIBMapResolverGroup 2573 DESCRIPTION 2574 "This group is optional." 2576 GROUP lispMIBEtrExtendedGroup 2577 DESCRIPTION 2578 "This group is optional." 2580 GROUP lispMIBItrExtendedGroup 2581 DESCRIPTION 2582 "This group is optional." 2584 GROUP lispMIBMapServerExtendedGroup 2585 DESCRIPTION 2586 "This group is optional." 2588 GROUP lispMIBTuningParametersGroup 2589 DESCRIPTION 2590 "This group is optional." 2592 GROUP lispMIBEncapStatisticsGroup 2593 DESCRIPTION 2594 "This group is optional." 2596 GROUP lispMIBDecapStatisticsGroup 2597 DESCRIPTION 2598 "This group is optional." 2600 GROUP lispMIBDiagnosticsGroup 2601 DESCRIPTION 2602 "This group is optional." 2604 GROUP lispMIBVrfGroup 2605 DESCRIPTION 2606 "This group is optional." 2608 ::= { lispCompliances 5 } 2610 lispMIBComplianceMapResolver MODULE-COMPLIANCE 2611 STATUS current 2612 DESCRIPTION 2613 "The compliance statement for LISP Map Resolvers." 2614 MODULE -- this module 2615 MANDATORY-GROUPS { lispMIBMapResolverGroup } 2617 GROUP lispMIBEtrGroup 2618 DESCRIPTION 2619 "This group is optional." 2621 GROUP lispMIBItrGroup 2622 DESCRIPTION 2623 "This group is optional." 2625 GROUP lispMIBPetrGroup 2626 DESCRIPTION 2627 "This group is optional." 2629 GROUP lispMIBPitrGroup 2630 DESCRIPTION 2631 "This group is optional." 2633 GROUP lispMIBMapServerGroup 2634 DESCRIPTION 2635 "This group is optional." 2637 GROUP lispMIBEtrExtendedGroup 2638 DESCRIPTION 2639 "This group is optional." 2641 GROUP lispMIBItrExtendedGroup 2642 DESCRIPTION 2643 "This group is optional." 2645 GROUP lispMIBMapServerExtendedGroup 2646 DESCRIPTION 2647 "This group is optional." 2649 GROUP lispMIBTuningParametersGroup 2650 DESCRIPTION 2651 "This group is optional." 2653 GROUP lispMIBEncapStatisticsGroup 2654 DESCRIPTION 2655 "This group is optional." 2657 GROUP lispMIBDecapStatisticsGroup 2658 DESCRIPTION 2659 "This group is optional." 2661 GROUP lispMIBDiagnosticsGroup 2662 DESCRIPTION 2663 "This group is optional." 2665 GROUP lispMIBVrfGroup 2666 DESCRIPTION 2667 "This group is optional." 2669 ::= { lispCompliances 6 } 2671 -- 2672 -- Units of Conformance 2673 -- 2675 lispMIBEtrGroup OBJECT-GROUP 2676 OBJECTS { lispFeaturesEtrEnabled, 2677 lispMappingDatabaseLsb, 2678 lispMappingDatabaseLocatorRlocPriority, 2679 lispMappingDatabaseLocatorRlocWeight, 2680 lispMappingDatabaseLocatorRlocMPriority, 2681 lispMappingDatabaseLocatorRlocMWeight, 2682 lispMappingDatabaseLocatorRlocState, 2683 lispMappingDatabaseLocatorRlocLocal, 2684 lispConfiguredLocatorRlocState, 2685 lispConfiguredLocatorRlocLocal, 2686 lispUseMapServerState 2687 } 2688 STATUS current 2689 DESCRIPTION 2690 "A collection of objects to support basic 2691 management of LISP ETRs." 2692 ::= { lispGroups 1 } 2694 lispMIBItrGroup OBJECT-GROUP 2695 OBJECTS { lispFeaturesItrEnabled, 2696 lispFeaturesMapCacheSize, 2697 lispMappingDatabaseLsb, 2698 lispMapCacheLocatorRlocPriority, 2699 lispMapCacheLocatorRlocWeight, 2700 lispMapCacheLocatorRlocMPriority, 2701 lispMapCacheLocatorRlocMWeight, 2702 lispMapCacheLocatorRlocState, 2703 lispMapCacheEidTimeStamp, 2704 lispMapCacheEidExpiryTime, 2705 lispUseMapResolverState, 2706 lispUseProxyEtrPriority, 2707 lispUseProxyEtrWeight, 2708 lispUseProxyEtrMPriority, 2709 lispUseProxyEtrMWeight, 2710 lispUseProxyEtrState 2711 } 2712 STATUS current 2713 DESCRIPTION 2714 "A collection of objects to support basic 2715 management of LISP ITRs." 2716 ::= { lispGroups 2 } 2718 lispMIBPetrGroup OBJECT-GROUP 2719 OBJECTS { lispFeaturesProxyEtrEnabled 2720 } 2721 STATUS current 2722 DESCRIPTION 2723 "A collection of objects to support basic 2724 management of LISP Proxy-ETRs." 2725 ::= { lispGroups 3 } 2727 lispMIBPitrGroup OBJECT-GROUP 2728 OBJECTS { lispFeaturesProxyItrEnabled, 2729 lispConfiguredLocatorRlocState, 2730 lispConfiguredLocatorRlocLocal 2731 } 2733 STATUS current 2734 DESCRIPTION 2735 "A collection of objects to support basic 2736 management of LISP Proxy-ITRs." 2737 ::= { lispGroups 4 } 2739 lispMIBMapServerGroup OBJECT-GROUP 2740 OBJECTS { lispFeaturesMapServerEnabled, 2741 lispEidRegistrationIsRegistered, 2742 lispEidRegistrationLocatorRlocState 2743 } 2744 STATUS current 2745 DESCRIPTION 2746 "A collection of objects to support basic 2747 management of LISP Map Servers." 2749 ::= { lispGroups 5 } 2751 lispMIBMapResolverGroup OBJECT-GROUP 2752 OBJECTS { lispFeaturesMapResolverEnabled 2753 } 2754 STATUS current 2755 DESCRIPTION 2756 "A collection of objects to support basic 2757 management of LISP Map Resolvers." 2758 ::= { lispGroups 6 } 2760 lispMIBEtrExtendedGroup OBJECT-GROUP 2761 OBJECTS { lispFeaturesRlocProbeEnabled, 2762 lispFeaturesEtrAcceptMapDataEnabled, 2763 lispFeaturesEtrAcceptMapDataVerifyEnabled, 2764 lispMappingDatabaseEidPartitioned 2765 } 2766 STATUS current 2767 DESCRIPTION 2768 "A collection of objects to support management 2769 of LISP features and properties on ETRs." 2770 ::= { lispGroups 7 } 2772 lispMIBItrExtendedGroup OBJECT-GROUP 2773 OBJECTS { lispFeaturesRlocProbeEnabled, 2774 lispMapCacheEidState, 2775 lispMapCacheEidAuthoritative, 2776 lispMapCacheLocatorRlocTimeStamp, 2777 lispMapCacheLocatorRlocLastPriorityChange, 2778 lispMapCacheLocatorRlocLastWeightChange, 2779 lispMapCacheLocatorRlocLastMPriorityChange, 2780 lispMapCacheLocatorRlocLastMWeightChange, 2781 lispMapCacheLocatorRlocLastStateChange, 2782 lispMapCacheLocatorRlocRtt 2783 } 2784 STATUS current 2785 DESCRIPTION 2786 "A collection of objects to support management 2787 of LISP features and properties on ITRs." 2788 ::= { lispGroups 8 } 2790 lispMIBMapServerExtendedGroup OBJECT-GROUP 2791 OBJECTS { lispEidRegistrationSiteName, 2792 lispEidRegistrationSiteDescription, 2793 lispEidRegistrationIsRegistered, 2794 lispEidRegistrationFirstTimeStamp, 2795 lispEidRegistrationLastTimeStamp, 2796 lispEidRegistrationLastRegisterSenderLength, 2797 lispEidRegistrationLastRegisterSender, 2798 lispEidRegistrationRouteTag, 2799 lispEidRegistrationEtrLastTimeStamp, 2800 lispEidRegistrationEtrTtl, 2801 lispEidRegistrationEtrProxyReply, 2802 lispEidRegistrationEtrWantsMapNotify, 2803 lispEidRegistrationLocatorIsLocal, 2804 lispEidRegistrationLocatorPriority, 2805 lispEidRegistrationLocatorWeight, 2806 lispEidRegistrationLocatorMPriority, 2807 lispEidRegistrationLocatorMWeight 2808 } 2809 STATUS current 2810 DESCRIPTION 2811 "A collection of objects to support management 2812 of LISP features and properties on Map Servers." 2813 ::= { lispGroups 9 } 2815 lispMIBTuningParametersGroup OBJECT-GROUP 2816 OBJECTS { lispFeaturesMapCacheLimit, 2817 lispFeaturesEtrMapCacheTtl 2818 } 2819 STATUS current 2820 DESCRIPTION 2821 "A collection of writeable objects used to 2822 configure LISP behavior and to tune performance." 2823 ::= { lispGroups 10 } 2825 lispMIBEncapStatisticsGroup OBJECT-GROUP 2826 OBJECTS { lispMappingDatabaseTimeStamp, 2827 lispMappingDatabaseEncapOctets, 2828 lispMappingDatabaseEncapPackets, 2829 lispMappingDatabaseLocatorRlocTimeStamp, 2830 lispMappingDatabaseLocatorRlocEncapOctets, 2831 lispMappingDatabaseLocatorRlocEncapPackets, 2832 lispMapCacheEidTimeStamp, 2833 lispMapCacheEidEncapOctets, 2834 lispMapCacheEidEncapPackets, 2835 lispMapCacheLocatorRlocTimeStamp, 2836 lispMapCacheLocatorRlocEncapOctets, 2837 lispMapCacheLocatorRlocEncapPackets, 2838 lispConfiguredLocatorRlocTimeStamp, 2839 lispConfiguredLocatorRlocEncapOctets, 2840 lispConfiguredLocatorRlocEncapPackets 2841 } 2842 STATUS current 2843 DESCRIPTION 2844 "A collection of LISP encapsulation statistics 2845 by the device." 2846 ::= { lispGroups 11 } 2848 lispMIBDecapStatisticsGroup OBJECT-GROUP 2849 OBJECTS { lispMappingDatabaseTimeStamp, 2850 lispMappingDatabaseDecapOctets, 2851 lispMappingDatabaseDecapPackets, 2852 lispMappingDatabaseLocatorRlocTimeStamp, 2853 lispMappingDatabaseLocatorRlocDecapOctets, 2854 lispMappingDatabaseLocatorRlocDecapPackets, 2855 lispMapCacheEidTimeStamp, 2856 lispMapCacheEidDecapOctets, 2857 lispMapCacheEidDecapPackets, 2858 lispMapCacheLocatorRlocTimeStamp, 2859 lispMapCacheLocatorRlocDecapOctets, 2860 lispMapCacheLocatorRlocDecapPackets, 2861 lispConfiguredLocatorRlocTimeStamp, 2862 lispConfiguredLocatorRlocDecapOctets, 2863 lispConfiguredLocatorRlocDecapPackets 2864 } 2865 STATUS current 2866 DESCRIPTION 2867 "A collection of LISP decapsulation statistics 2868 by the device." 2869 ::= { lispGroups 12 } 2871 lispMIBDiagnosticsGroup OBJECT-GROUP 2872 OBJECTS { lispFeaturesRouterTimeStamp, 2873 lispGlobalStatsMapRequestsIn, 2874 lispGlobalStatsMapRequestsOut, 2875 lispGlobalStatsMapRepliesIn, 2876 lispGlobalStatsMapRepliesOut, 2877 lispGlobalStatsMapRegistersIn, 2878 lispGlobalStatsMapRegistersOut, 2879 lispEidRegistrationAuthenticationErrors, 2880 lispEidRegistrationRlocsMismatch 2881 } 2882 STATUS current 2883 DESCRIPTION 2884 "Objects providing additional diagnostics 2885 related to a LISP router." 2886 ::= { lispGroups 13 } 2888 lispMIBVrfGroup OBJECT-GROUP 2889 OBJECTS { lispIidToVrfName 2890 } 2891 STATUS current 2892 DESCRIPTION 2893 "Objects providing information related to VRF 2894 configurations on a LISP router." 2895 ::= { lispGroups 14 } 2897 END 2899 8. Relationship to Other MIB Modules 2901 8.1. MIB modules required for IMPORTS 2903 The LISP MIB imports the textual-convention AddressFamilyNumbers from 2904 the IANA-ADDRESS-FAMILY-NUMBERS-MIB [IANA]. 2906 9. Security Considerations 2908 There are no management objects defined in this MIB module that have 2909 a MAX-ACCESS clause of read-write and/or read-create. As long as 2910 these MIB modules are implemented correctly, there are no risks that 2911 any management objects of this MIB module can modify device settings 2912 via direct SNMP SET operations. 2914 There are no readable objects in this MIB module (i.e., objects with 2915 a MAX-ACCESS other than not-accessible) that are considered 2916 sensitive. 2918 SNMP versions prior to SNMPv3 did not include adequate security. 2919 Even if the network itself is secure (for example by using IPsec), 2920 there is no control as to who on the secure network is allowed to 2921 access and GET/SET (read/change/create/delete) the objects in this 2922 MIB module. 2924 It is RECOMMENDED that implementers consider the security features as 2925 provided by the SNMPv3 framework (see [RFC3410], section 8), 2926 including full support for the SNMPv3 cryptographic mechanisms (for 2927 authentication and privacy). 2929 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2930 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2931 enable cryptographic security. It is then a customer/operator 2932 responsibility to ensure that the SNMP entity giving access to an 2933 instance of these MIB modules is properly configured to give access 2934 to the objects only to those principals (users) that have legitimate 2935 rights to indeed GET or SET (change/create/delete) them. 2937 10. IANA Considerations 2939 The MIB module in this document uses the following IANA-assigned 2940 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2942 Descriptor OBJECT IDENTIFIER value 2943 ---------- ----------------------- 2945 lispMib { mib-2 XXX } 2947 [Editor's Note (to be removed prior to publication): the IANA is 2948 requested to assign a value for "XXX" under the 'mib-2' subtree and 2949 to record the assignment in the SMI Numbers registry. When the 2950 assignment has been made, the RFC Editor is asked to replace "XXX" 2951 (here and in the MIB module) with the assigned value and to remove 2952 this note.] 2954 11. References 2956 11.1. Normative References 2958 [IANA] "IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS", . 2961 [INTERWORK] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller, 2962 "Interworking LISP with IPv4 and IPv6", 2963 draft-ietf-lisp-interworking-06.txt (work in progress), 2964 March 2012. 2966 [LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, 2967 "Locator/ID Separation Protocol (LISP)", 2968 draft-ietf-lisp-23.txt (work in progress), May 2012. 2970 [LISP-MS] Farinacci, D. and V. Fuller, "LISP Map Server", 2971 draft-ietf-lisp-ms-16.txt (work in progress), 2972 March 2012. 2974 [RFC1035] Mockapetris, P., "Domain names - implementation and 2975 specification", STD 13, RFC 1035, November 1987. 2977 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2978 Requirement Levels", BCP 14, RFC 2119, March 1997. 2980 [RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96 2981 within ESP and AH", RFC 2404, November 1998. 2983 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2985 Schoenwaelder, Ed., "Structure of Management 2986 Information Version 2 (SMIv2)", STD 58, RFC 2578, 2987 April 1999. 2989 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2990 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2991 STD 58, RFC 2579, April 1999. 2993 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2994 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2995 April 1999. 2997 [RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms 2998 (SHA and HMAC-SHA)", RFC 4634, July 2006. 3000 11.2. Informative References 3002 [LCAF] Farinacci, D., Meyer, D., and J. Snijders, "LISP 3003 Canonical Address Format", draft-ietf-lisp-lcaf-00.txt 3004 (work in progress), August 2012. 3006 [LISP-MCAST] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, 3007 "LISP for Multicast Environments", 3008 draft-ietf-lisp-multicast-14.txt (work in progress), 3009 February 2012. 3011 [LISP-MN] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, 3012 "LISP Mobile Node Architecture", 3013 draft-meyer-lisp-mn-07.txt (work in progress), 3014 April 2012. 3016 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 3017 Traina, "Generic Routing Encapsulation (GRE)", 3018 RFC 2784, March 2000. 3020 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3021 "Introduction and Applicability Statements for 3022 Internet-Standard Management Framework", RFC 3410, 3023 December 2002. 3025 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 3026 Protocol 4 (BGP-4)", RFC 4271, January 2006. 3028 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 3029 "Multiprotocol Extensions for BGP-4", RFC 4760, 3030 January 2007. 3032 Appendix A. Open Issues 3034 Open issues for the LISP MIB include the following: 3036 1. This LISP MIB draft does not include LISP Multicast 3037 considerations. Multicast considerations will be added in a 3038 separate LISP Multicast MIB draft. 3040 Appendix B. Acknowledgments 3042 A thank you is owed to Dino Farinacci for his inputs and review 3043 comments on the initial versions of this draft. In addition, the 3044 authors would like to gratefully acknowledge several others who have 3045 reviewed and commented on this draft. They include: Darrel Lewis, 3046 Isidor Kouvelas, Jesper Skriver, Selina Heimlich, and Parna Agrawal. 3048 Authors' Addresses 3050 Gregg Schudel 3051 cisco Systems 3052 Tasman Drive 3053 San Jose, CA 95134 3054 USA 3056 EMail: gschudel@cisco.com 3058 Amit Jain 3059 cisco Systems 3060 Tasman Drive 3061 San Jose, CA 95134 3062 USA 3064 EMail: amijain@cisco.com 3066 Victor Moreno 3067 cisco Systems 3068 Tasman Drive 3069 San Jose, CA 95134 3070 USA 3072 EMail: vimoreno@cisco.com