>> MIB - Management Information Base
>> Table: lispCchSiteTable - (.1.3.6.1.4.1.272.4.23.9.6.1)
Description: List of cached remote LISP-sites (see section 4.1 of RFC-6833).
lispCchSiteTable
OID | Name | Type | Access
.1 | InstId | INTEGER | R
.2 | Addr | IpAddress | R
.3 | Len | INTEGER | R
.4 | State | ENUM | R
.5 | Ttl | INTEGER | R
.6 | Start | TimeTicks | R
.7 | FlagA | ENUM | R
.8 | Lru | TimeTicks | R
.9 | ReqTime | TimeTicks | R
.10 | Nonce | Counter64 | R
.11 | Action | ENUM | R
InstId
Refers to lispInstId-field of related lispInst-entry. Range: -1 to 16777215
Addr
Together with lispCchSiteLen, specifies EID-prefix of this cached remote LISP-site.
Len
See description of lispCchSiteAddr. Range: 0 to 32
State
State of this cache-entry. 'to-be-resolved' means that entry is not yet valid, and related Map-Request is still pending. 'valid-not-refreshing' means that entry is valid, and refresh has not yet been triggered. 'valid-refreshing' means that entry is valid, and refresh has already been triggered. Enumerations: to-be-resolved (0) valid-not-refreshing (1) valid-refreshing (2)
Ttl
Time-to-live in minutes of this cache-entry, starting at lispCchSiteStart. See 6.1.4 of RFC-6830 for details. Range: 0 to -1
Start
Start of time-to-live period. See lispCchSiteTtl for more details.
FlagA
Flag A of this cache-entry. See 6.1.4 of RFC-6830 for details. This field is not relevant/valid in state to-be-resolved. Current implementation mostly yet ignores this value. Enumerations: not-authoritative (0) authoritative (1)
Lru
Time-stamp of latest use (LRU) of this cache-entry.
ReqTime
Time-stamp of latest Map-Request sent for resolving (in state to-be-resolved) or updating (in state valid-refreshing) this cache-entry. This field is not relevant/valid in state valid-not-refreshing.
Nonce
Nonce-value of latest Map-Request sent for resolving (in state to-be-resolved) or updating (in state valid-refreshing) this cache-entry. This field is not relevant/valid in state valid-not-refreshing.
Action
Requested action for negative Map-Replies (i.e. no cached ETRs, see description of 'ACT' field in section 6.1.4 of RFC-6830). This field is not relevant/valid for positive Map-Replies (and in state to-be-resolved). Current code supports only 'no-action' and special variant of 'natively-forward' (see 'lispInstProxyEtrAddr' for details). Enumerations: no-action (0) natively-forward (1) send-map-request (2) drop (3)

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