>> MIB - Management Information Base
>> Table: lispMapRsvTable - (.1.3.6.1.4.1.272.4.23.9.5.1)
Description: List of Map-Resolvers (see section 4.1 of RFC-6833) to consult for remote EID-RLOC-mappings.
lispMapRsvTable
OID | Name | Type | Access
.1 | Addr | IpAddress | RW
.2 | AdminStatus | ENUM | D
.3 | OperStatus | ENUM | R
.4 | MinPeriod | Unsigned32 | RW
.5 | MaxPending | Unsigned32 | RW
.6 | PendingCnt | Counter32 | R
.7 | PendingTime | TimeTicks | R
.8 | MaxDelay | Unsigned32 | RW
Addr
RLOC of this Map-Resolver.
AdminStatus
Administrative status of Map-Resolver. Set to delete for killing entry. Enumerations: active (1) inactive (2) delete (3)
OperStatus
Operative status of Map-Resolver. Enumerations: selected (1) not-selected (2)
MinPeriod
Minimum time-distance in seconds for subsequent Map-Requests that are sent to this Map-Resolver for same to-be-resolved EID. In current implementation, subsequent Map-Requests are not triggered automatically but only by subsequent send-attempts from LISP-hosts.
MaxPending
Allowed number of unreplied subsequent Map-Requests before switching to next Map-Resolver (if any) is considered. This defines some kind of frame-loss-tolerance for the Map-Resolver-switching. Additionally, some net-delay-tolerance can be configured via lispMapRsvMaxDelay.
PendingCnt
Current number of unreplied subsequent Map-Requests. This field is valid only if lispMapRsvOperStatus is 'selected'.
PendingTime
Send-time of the (lispMapRsvMaxPending + 1)st still pending Map-Request. This time-stamp is valid only if lispMapRsvOperStatus is 'selected' and lispMapRsvPendingCnt is greater than lispMapRsvMaxPending.
MaxDelay
Allowed number of seconds between lispMapRsvPendingTime (if valid) and receipt of next valid Map-Reply before switching to next Map-Resolver (if any) is considered.

MIB Reference to Software Version 10.1.21 generated on 2016/12/23. Provided by webmaster@bintec-elmeg.com Copyright ©2016 by bintec elmeg GmbH