Usage Guidelines

Use this command to enable the broadcast functionality on the fabric edge node in a LISP network. Ensure that this command is used in the router-lisp-service-ethernet mode or router-lisp-instance-service-ethernet mode.

Use the no form of the command to remove the broadcast functionality.

Usage Guidelines

In the LISP-instance-service configuration mode, the database-mapping command configures LISP database parameters a specified IPv4 or IPv6 EID-prefix block. The locator is the IPv4 or IPv6 address of any interface used as the RLOC address for the eid-prefix assigned to the site but can also be the loopback address of the interface.

When a LISP site has multiple locators associated with the same EID-prefix block, multiple database-mapping commands are used to configure all of the locators for a given EID-prefix block.

In a multi-site scenario, the LISP border node advertises the site EID that it’s attached to towards the transit map-server to attract site traffic. To do this, it has to obtain the route from the internal border and proxy register with the transit site map-server accordingly. The database-mapping command has the proxy keyword to enable configuration of a static proxy database mapping.

Usage Guidelines

To configure LISP mobility, create a dynamic-EID roaming policy that can be referenced by the lisp mobility interface command. When the dynamic-eid command is entered, the referenced LISP dynamic-EID policy is created and you enter the dynamic-EID configuration mode. In this mode, all attributes associated with the referenced LISP dynamic-EID policy can be entered. When a dynamic-EID policy is configured, you must specify the dynamic-EID-to-RLOC mapping relationship and its associated traffic policy.

Usage Guidelines

Use the no form of the command to negate the eid-record-provider configuration.

Usage Guidelines

Use the no form of the command to negate the eid-record-subscriber configuration.

Usage Guidelines

This command is used only in the instance-service mode.

For Layer 3 (service ipv4 / service ipv6), a VRF table is associated with the instance-service. For Layer 2 (service ethernet), a VLAN is associated with the instance-service.

Note	For Layer 2, ensure that you have defined a VLAN before configuring the eid-table. For Layer 3, ensure that you have defined a VRF table before you configure the eid-table.

Usage Guidelines

Use the encapsulation vxlan command in the service ethernet mode to encapuslate Layer 2 packets. Use the encapsulation lisp command in the service ipv4 or service ipv6 mode to encapsulate the Layer 3 packets.

Use the no form of the command to remove encapsulation on the packets.

Usage Guidelines

Use this command to enable a device to perform the ETR functionality.

Use the no form of the command to remove the ETR functionality.

A router configured as an ETR is also typically configured with database-mapping commands so that the ETR knows what endpoint identifier (EID)-prefix blocks and corresponding locators are used for the LISP site. In addition, the ETR should be configured to register with a map server with the etr map-server command, or to use static LISP EID-to-routing locator (EID-to-RLOC) mappings with the map-cache command to participate in LISP networking.

Usage Guidelines

Use the etr map-server command to configure the locator of the map server to which the ETR will register for its EIDs. The authentication key argument in the command syntax is a password that is used for a SHA-1 HMAC hash (included in the header of the map-register message). The password used for the SHA-1 HMAC may be entered in unencrypted (cleartext) form or encrypted form. To enter an unencrypted password, specify 0. To enter an AES encrypted password, specify 6.

Use the no form of the command to remove the map server functionality.

Usage Guidelines

Use the instance-id command to create a LISP eid instance to group multiple services.

Configuration under this instance-id will apply to all services underneath it.

Example

Native multicast transport supports only PIM SSM in the underlay or the core. Multicast transport uses a grouping mechanism to map the end-point identifiers (EID) entries to the RLOC space SSM group entries. By default, the group range 232.100.100.1 to 232.100.100.255 is used as the SSM range of addresses on a LISP interface to transport multicast traffic. Use the ip pim lisp core-group-range command to manually change this SSM core group range of IP addresses on the LISP interfaces.

The following example defines a group of 1000 IP addresses starting from 232.0.0.1 as the SSM range of addresses on the core for multicast traffic.

Device(config)#interface LISP0.201
Device(config-if)#ip pim lisp core-group-range 232.0.0.1 1000
 

Example

Use the ip pim rp-address command to statically define the RP address for multicast groups that are to operate in sparse mode or bidirectional mode.

You can configure the Cisco IOS software to use a single RP for more than one group. The conditions specified by the access list determine for which groups the RP can be used. If no access list is configured, the RP is used for all groups. A PIM router can use multiple RPs, but only one per group.

The following example sets the PIM RP address to 185.1.1.1 for all multicast groups:

Device(config)#ip pim rp-address 185.1.1.1
 

Usage Guidelines

The NetFlow collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow.

Usage Guidelines

When an SSM range of IP multicast addresses is defined by the ip pim ssm command, no Multicast Source Discovery Protocol (MSDP) Source-Active (SA) messages will be accepted or originated in the SSM range.

Usage Guidelines

Use this command to enable a device to perform the ITR functionality.

Use the no form of the command to remove theITR functionality.

A device configured as an ITR helps find the EID-to-RLOC mapping for all traffic destined to LISP-capable sites.

Usage Guidelines

Use this command to enable a device to perform the ITR map-resolver functionality.

Use the no form of the command to remove the map-resolver functionality.

A device configured as a Map Resolver accepts encapsulated Map-Request messages from ITRs, decapsulates those messages, and then forwards the messages to the Map Server responsible for the egress tunnel routers (ETRs) that are authoritative for the requested EIDs. In a multi-site environment, the site border relies on Map Resolver prefix-list to determine whether to query the transit site MSMR or site MSMR.

Usage Guidelines

The locator-set configured as default with the locator default-set command applies to all services and instances.

Usage Guidelines

You must first define the locator-set before referring to it.

Usage Guidelines

The first use of this command is to configure an Ingress Tunnel Router (ITR) with a static IPv4 or IPv6 EID-to-RLOC mapping relationship and its associated traffic policy. For each entry, a destination EID-prefix block and its associated locator, priority, and weight are entered. The value in the EID-prefix/prefix-length argument is the LISP EID-prefix block at the destination site. The locator is an IPv4 or IPv6 address of the remote site where the IPv4 or IPv6 EID-prefix can be reached. Associated with the locator address is a priority and weight that are used to define traffic policies when multiple RLOCs are defined for the same EID-prefix block.

Usage Guidelines

To support inter-VRF communication, use the map-cache extranet command on the Map Server Map Resolver (MSMR). This command generates map requests for all fabric destinations. Use this command in the service ipv4 or service ipv6 mode under the extranet instance.

Usage Guidelines

Use the prefix-list command to configure an IPV4 or IPv6 prefix list. This command places the router in prefix-list configuration mode, in which you can define IPv4 prefix list, or IPv6 prefix list. Use the exit-prefix-list command to exit the prefix-list-configuration mode.

Usage Guidelines

Use the route-import database command with the proxy option to enable the dynamic import of RIB route as proxy database mapping. When RIB import is in use, the corresponding RIB map-cache import, using route-import map-cache command must also be configured, else the inbound site traffic will not pass the LISP eligibility check due to the presence of RIB route.

Usage Guidelines

The service command creates a service instance under the instance-id and enters the instance-service mode. You cannot confgure service ethernet for the same instance where service ipv4 or service ipv6 is configured.

Use the no form of the command to exit the service submode.

Usage Guidelines

Use the command show lisp instance-id id ipv4 database to display the EID prefixes configured for a site. The following is a sample output:

device#show lisp instance-id 101 ipv4 database
LISP ETR IPv4 Mapping Database for EID-table vrf red (IID 101), LSBs: 0x1
Entries total 1, no-route 0, inactive 0
 
172.168.0.0/16, locator-set RLOC, proxy
  Locator          Pri/Wgt  Source     State
  100.110.110.110    1/100  cfg-intf   site-self, reachable
 
 device#

device#show lisp instance-id 101 ipv4
  Instance ID:                         101
  Router-lisp ID:                      0
  Locator table:                       default
  EID table:                           vrf red
  Ingress Tunnel Router (ITR):         disabled
  Egress Tunnel Router (ETR):          enabled
  Proxy-ITR Router (PITR):             enabled RLOCs: 100.110.110.110
  Proxy-ETR Router (PETR):             disabled
  NAT-traversal Router (NAT-RTR):      disabled
  Mobility First-Hop Router:           disabled
  Map Server (MS):                     enabled
  Map Resolver (MR):                   enabled
  Mr-use-petr:                         enabled
  Mr-use-petr locator set name:        site2
  Delegated Database Tree (DDT):       disabled
  Site Registration Limit:             0
  Map-Request source:                  derived from EID destination
  ITR Map-Resolver(s):                 100.77.77.77
                                       100.78.78.78
                                       100.110.110.110 prefix-list site2
  ETR Map-Server(s):                   100.77.77.77 (11:25:01)
                                       100.78.78.78 (11:25:01)
  xTR-ID:                              0xB843200A-0x4566BFC9-0xDAA75B2D-0x8FBE69B0
  site-ID:                             unspecified
  ITR local RLOC (last resort):        100.110.110.110
  ITR Solicit Map Request (SMR):       accept and process
    Max SMRs per map-cache entry:      8 more specifics
    Multiple SMR suppression time:     20 secs
  ETR accept mapping data:             disabled, verify disabled
  ETR map-cache TTL:                   1d00h
  Locator Status Algorithms:
    RLOC-probe algorithm:              disabled
    RLOC-probe on route change:        N/A (periodic probing disabled)
    RLOC-probe on member change:       disabled
    LSB reports:                       process
    IPv4 RLOC minimum mask length:     /0
    IPv6 RLOC minimum mask length:     /0
  Map-cache:
    Static mappings configured:        1
    Map-cache size/limit:              1/32768
    Imported route count/limit:        0/5000
    Map-cache activity check period:   60 secs
    Map-cache FIB updates:             established
    Persistent map-cache:              disabled
 Database:
    Total database mapping size:       1
    static database size/limit:        1/65535
    dynamic database size/limit:       0/65535
    route-import database size/limit:  0/5000
    import-site-reg database size/limit0/65535
    proxy database size:               1
    Inactive (deconfig/away) size:     0
  Encapsulation type:                  vxlan
 

Usage Guidelines

Use the command show lisp instance-id id ipv6 database to display the EID prefixes configured for a site. The following is a sample output:

device#show lisp instance-id 101 ipv6 database
LISP ETR IPv6 Mapping Database, LSBs: 0x1

EID-prefix: 2610:D0:1209::/48
  172.16.156.222, priority: 1, weight: 100, state: up, local
 
 device#

Usage Guidelines

This command is used to display the current dynamic and static IPv4 EID-to-RLOC map-cache entries. When no IPv4 EID or IPv4 EID prefix is specified, summary information is listed for all current dynamic and static IPv4 EID-to-RLOC map-cache entries. When an IPv4 EID or IPv4 EID prefix is included, information is listed for the longest-match lookup in the cache. When the detail option is used, detailed (rather than summary) information related to all current dynamic and static IPv4 EID-to-RLOC map-cache entries is displayed.

The following are sample outputs from the show lisp instance-id ipv4 map-cache commands:

device# show lisp instance-id 102 ipv4 map-cache 
LISP IPv4 Mapping Cache for EID-table vrf blue (IID 102), 4008 entries
 
0.0.0.0/0, uptime: 2d14h, expires: never, via static-send-map-request
  Negative cache entry, action: send-map-request
128.0.0.0/3, uptime: 00:01:44, expires: 00:13:15, via map-reply, unknown-eid-forward
  PETR        Uptime    State      Pri/Wgt     Encap-IID
  55.55.55.1  13:32:40  up           1/100       103
  55.55.55.2  13:32:40  up           1/100       103
  55.55.55.3  13:32:40  up           1/100       103
  55.55.55.4  13:32:40  up           1/100       103
  55.55.55.5  13:32:40  up           5/100       103
  55.55.55.6  13:32:40  up           6/100       103
  55.55.55.7  13:32:40  up           7/100       103
  55.55.55.8  13:32:40  up           8/100       103
150.150.2.0/23, uptime: 11:47:25, expires: 00:06:30, via map-reply, unknown-eid-forward
  PETR        Uptime    State      Pri/Wgt     Encap-IID
  55.55.55.1  13:32:40  up           1/100       103
  55.55.55.2  13:32:40  up           1/100       103
  55.55.55.3  13:32:40  up           1/100       103
  55.55.55.4  13:32:40  up           1/100       103
  55.55.55.5  13:32:40  up           5/100       103
  55.55.55.6  13:32:40  up           6/100       103
  55.55.55.7  13:32:43  up           7/100       103
  55.55.55.8  13:32:43  up           8/100       103
150.150.4.0/22, uptime: 13:32:43, expires: 00:05:19, via map-reply, unknown-eid-forward
  PETR        Uptime    State      Pri/Wgt     Encap-IID
  55.55.55.1  13:32:43  up           1/100       103
  55.55.55.2  13:32:43  up           1/100       103
  55.55.55.3  13:32:43  up           1/100       103
  55.55.55.4  13:32:43  up           1/100       103
  55.55.55.5  13:32:43  up           5/100       103
  55.55.55.6  13:32:43  up           6/100       103
  55.55.55.7  13:32:43  up           7/100       103
  55.55.55.8  13:32:43  up           8/100       103
150.150.8.0/21, uptime: 13:32:35, expires: 00:05:27, via map-reply, unknown-eid-forward
  PETR        Uptime    State      Pri/Wgt     Encap-IID
 55.55.55.1  13:32:43  up           1/100       103
  55.55.55.2  13:32:43  up           1/100       103
  55.55.55.3  13:32:43  up           1/100       103
  55.55.55.4  13:32:43  up           1/100       103
  55.55.55.5  13:32:43  up           5/100       103
  55.55.55.6  13:32:43  up           6/100       103
  55.55.55.7  13:32:43  up           7/100       103
  55.55.55.8  13:32:45  up           8/100       103
171.171.0.0/16, uptime: 2d14h, expires: never, via dynamic-EID, send-map-request
  Negative cache entry, action: send-map-request
172.172.0.0/16, uptime: 2d14h, expires: never, via dynamic-EID, send-map-request
  Negative cache entry, action: send-map-request
178.168.2.1/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
178.168.2.2/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
178.168.2.3/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
178.168.2.4/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
178.168.2.5/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
178.168.2.6/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete
  Locator     Uptime    State      Pri/Wgt     Encap-IID

device#show lisp instance-id 102 ipv4 map-cache detail
LISP IPv4 Mapping Cache for EID-table vrf blue (IID 102), 4008 entries
 
0.0.0.0/0, uptime: 2d15h, expires: never, via static-send-map-request
  Sources: static-send-map-request
  State: send-map-request, last modified: 2d15h, map-source: local
  Exempt, Packets out: 30531(17585856 bytes) (~ 00:01:36 ago)
  Configured as EID address space
  Negative cache entry, action: send-map-request
128.0.0.0/3, uptime: 00:02:02, expires: 00:12:57, via map-reply, unknown-eid-forward
  Sources: map-reply
  State: unknown-eid-forward, last modified: 00:02:02, map-source: local
  Active, Packets out: 9(5184 bytes) (~ 00:00:36 ago)
  PETR        Uptime    State      Pri/Wgt     Encap-IID
  55.55.55.1  13:32:58  up           1/100       103
  55.55.55.2  13:32:58  up           1/100       103
  55.55.55.3  13:32:58  up           1/100       103
  55.55.55.4  13:32:58  up           1/100       103
  55.55.55.5  13:32:58  up           5/100       103
  55.55.55.6  13:32:58  up           6/100       103
  55.55.55.7  13:32:58  up           7/100       103
  55.55.55.8  13:32:58  up           8/100       103
150.150.2.0/23, uptime: 11:47:43, expires: 00:06:12, via map-reply, unknown-eid-forward
  Sources: map-reply
  State: unknown-eid-forward, last modified: 11:47:44, map-source: local
  Active, Packets out: 4243(2443968 bytes) (~ 00:00:38 ago)
  PETR        Uptime    State      Pri/Wgt     Encap-IID
  55.55.55.1  13:33:00  up           1/100       103
  55.55.55.2  13:33:00  up           1/100       103
  55.55.55.3  13:33:00  up           1/100       103
  55.55.55.4  13:33:00  up           1/100       103
  55.55.55.5  13:33:00  up           5/100       103
  55.55.55.6  13:33:00  up           6/100       103
  55.55.55.7  13:33:00  up           7/100       103
  55.55.55.8  13:33:00  up           8/100       103
150.150.4.0/22, uptime: 13:33:00, expires: 00:05:02, via map-reply, unknown-eid-forward
  Sources: map-reply
  State: unknown-eid-forward, last modified: 13:33:00, map-source: local
  Active, Packets out: 4874(2807424 bytes) (~ 00:00:38 ago)
  PETR        Uptime    State      Pri/Wgt     Encap-IID
  55.55.55.1  13:33:00  up           1/100       103
  55.55.55.2  13:33:00  up           1/100       103
  55.55.55.3  13:33:00  up           1/100       103
  55.55.55.4  13:33:00  up           1/100       103
 55.55.55.5  13:33:00  up           5/100       103
  55.55.55.6  13:33:00  up           6/100       103
  55.55.55.7  13:33:01  up           7/100       103
  55.55.55.8  13:33:01  up           8/100       103
150.150.8.0/21, uptime: 13:32:53, expires: 00:05:09, via map-reply, unknown-eid-forward
  Sources: map-reply
  State: unknown-eid-forward, last modified: 13:32:53, map-source: local
  Active, Packets out: 4874(2807424 bytes) (~ 00:00:39 ago)
  PETR        Uptime    State      Pri/Wgt     Encap-IID
  55.55.55.1  13:33:01  up           1/100       103
  55.55.55.2  13:33:01  up           1/100       103
  55.55.55.3  13:33:01  up           1/100       103
  55.55.55.4  13:33:01  up           1/100       103
  55.55.55.5  13:33:01  up           5/100       103
  55.55.55.6  13:33:01  up           6/100       103
  55.55.55.7  13:33:01  up           7/100       103
  55.55.55.8  13:33:01  up           8/100       103
171.171.0.0/16, uptime: 2d15h, expires: never, via dynamic-EID, send-map-request
  Sources: NONE
  State: send-map-request, last modified: 2d15h, map-source: local
  Exempt, Packets out: 2(1152 bytes) (~ 2d14h ago)
  Configured as EID address space
  Configured as dynamic-EID address space
  Encapsulating dynamic-EID traffic
  Negative cache entry, action: send-map-request
172.172.0.0/16, uptime: 2d15h, expires: never, via dynamic-EID, send-map-request
  Sources: NONE
  State: send-map-request, last modified: 2d15h, map-source: local
  Exempt, Packets out: 2(1152 bytes) (~ 2d14h ago)
  Configured as EID address space
  Configured as dynamic-EID address space
  Encapsulating dynamic-EID traffic
  Negative cache entry, action: send-map-request
178.168.2.1/32, uptime: 2d14h, expires: 09:26:55, via map-reply, complete
  Sources: map-reply
  State: complete, last modified: 2d14h, map-source: 48.1.1.4
  Active, Packets out: 22513(12967488 bytes) (~ 00:00:41 ago)
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
    Last up-down state change:         2d14h, state change count: 1
    Last route reachability change:    2d14h, state change count: 1
    Last priority / weight change:     never/never
    RLOC-probing loc-status algorithm:
      Last RLOC-probe sent:            2d14h (rtt 92ms)
178.168.2.2/32, uptime: 2d14h, expires: 09:26:55, via map-reply, complete
  Sources: map-reply
  State: complete, last modified: 2d14h, map-source: 48.1.1.4
  Active, Packets out: 22513(12967488 bytes) (~ 00:00:45 ago)
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
    Last up-down state change:         2d14h, state change count: 1
    Last route reachability change:    2d14h, state change count: 1
    Last priority / weight change:     never/never
    RLOC-probing loc-status algorithm:
      Last RLOC-probe sent:            2d14h (rtt 91ms)
178.168.2.3/32, uptime: 2d14h, expires: 09:26:51, via map-reply, complete
  Sources: map-reply
  State: complete, last modified: 2d14h, map-source: 48.1.1.4
  Active, Packets out: 22513(12967488 bytes) (~ 00:00:45 ago)
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
    Last up-down state change:         2d14h, state change count: 1
    Last route reachability change:    2d14h, state change count: 1
    Last priority / weight change:     never/never
    RLOC-probing loc-status algorithm:
      Last RLOC-probe sent:            2d14h (rtt 91ms)
178.168.2.4/32, uptime: 2d14h, expires: 09:26:51, via map-reply, complete
  Sources: map-reply
  State: complete, last modified: 2d14h, map-source: 48.1.1.4

device#show lisp instance-id 102 ipv4 map-cache 178.168.2.3/32
LISP IPv4 Mapping Cache for EID-table vrf blue (IID 102), 4008 entries
 
178.168.2.3/32, uptime: 2d14h, expires: 09:26:25, via map-reply, complete
  Sources: map-reply
  State: complete, last modified: 2d14h, map-source: 48.1.1.4
  Active, Packets out: 22519(12970944 bytes) (~ 00:00:11 ago)
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
    Last up-down state change:         2d14h, state change count: 1
    Last route reachability change:    2d14h, state change count: 1
    Last priority / weight change:     never/never
    RLOC-probing loc-status algorithm:
      Last RLOC-probe sent:            2d14h (rtt 91ms)

device#show lisp instance-id 102 ipv4 map-cache 178.168.2.3
LISP IPv4 Mapping Cache for EID-table vrf blue (IID 102), 4008 entries
 
178.168.2.3/32, uptime: 2d14h, expires: 09:26:14, via map-reply, complete
  Sources: map-reply
  State: complete, last modified: 2d14h, map-source: 48.1.1.4
  Active, Packets out: 22519(12970944 bytes) (~ 00:00:22 ago)
  Locator     Uptime    State      Pri/Wgt     Encap-IID
  11.11.11.1  2d14h     up           1/100       -
    Last up-down state change:         2d14h, state change count: 1
    Last route reachability change:    2d14h, state change count: 1
    Last priority / weight change:     never/never
    RLOC-probing loc-status algorithm:
      Last RLOC-probe sent:            2d14h (rtt 91ms)
OTT-LISP-C3K-4-xTR2#show lisp instance-id 102 sta                       
OTT-LISP-C3K-4-xTR2#show lisp instance-id 102 stat
OTT-LISP-C3K-4-xTR2#show lisp instance-id 102 ipv4 stat
OTT-LISP-C3K-4-xTR2#show lisp instance-id 102 ipv4 statistics
LISP EID Statistics for instance ID 102 - last cleared: never
Control Packets:
  Map-Requests in/out:                              5911/66032
    Map-Request receive rate (5 sec/1 min/5 min):   0.00/ 0.00/ 0.00
    Encapsulated Map-Requests in/out:               0/60600
    RLOC-probe Map-Requests in/out:                 5911/5432
    SMR-based Map-Requests in/out:                  0/0
    Extranet SMR cross-IID Map-Requests in:         0
    Map-Requests expired on-queue/no-reply          0/0
    Map-Resolver Map-Requests forwarded:            0
    Map-Server Map-Requests forwarded:              0
  Map-Reply records in/out:                         64815/5911
    Authoritative records in/out:                   12696/5911
    Non-authoritative records in/out:               52119/0
    Negative records in/out:                        8000/0
    RLOC-probe records in/out:                      4696/5911
    Map-Server Proxy-Reply records out:             0
  WLC Map-Subscribe records in/out:                 0/4
    Map-Subscribe failures in/out:                  0/0
  WLC Map-Unsubscribe records in/out:               0/0
    Map-Unsubscribe failures in/out:                0/0
  Map-Register records in/out:                      0/8310
    Map-Register receive rate (5 sec/1 min/5 min):  0.00/ 0.00/ 0.00
    Map-Server AF disabled:                         0
    Authentication failures:                        0
  WLC Map-Register records in/out:                  0/0
    WLC AP Map-Register in/out:                     0/0
    WLC Client Map-Register in/out:                 0/0
    WLC Map-Register failures in/out:               0/0
  Map-Notify records in/out:                        20554/0
    Authentication failures:                        0
  WLC Map-Notify records in/out:                    0/0
    WLC AP Map-Notify in/out:                       0/0
    WLC Client Map-Notify in/out:                   0/0
    WLC Map-Notify failures in/out:                 0/0
  Publish-Subscribe in/out:                        
    Subscription Request records in/out:            0/6
    Subscription Request failures in/out:           0/0
    Subscription Status records in/out:             4/0
      End of Publication records in/out:            4/0
      Subscription rejected records in/out:         0/0
      Subscription removed records in/out:          0/0
    Subscription Status failures in/out:            0/0
    Solicit Subscription records in/out:            0/0
    Solicit Subscription failures in/out:           0/0
    Publication records in/out:                     0/0
    Publication failures in/out:                    0/0
Errors:
  Mapping record TTL alerts:                        0
  Map-Request invalid source rloc drops:            0
  Map-Register invalid source rloc drops:           0
  DDT Requests failed:                              0
  DDT ITR Map-Requests dropped:                     0 (nonce-collision: 0, bad-xTR-nonce: 0)
Cache Related:
  Cache entries created/deleted:                    200103/196095
  NSF CEF replay entry count                        0
  Number of EID-prefixes in map-cache:              4008
  Number of rejected EID-prefixes due to limit :    0
  Number of negative entries in map-cache:          8
  Total number of RLOCs in map-cache:               4000
  Average RLOCs per EID-prefix:                     1
Forwarding:
  Number of data signals processed:                 199173 (+ dropped 5474)
  Number of reachability reports:                   0 (+ dropped 0)
  Number of SMR signals dropped:                    0
ITR Map-Resolvers:
  Map-Resolver         LastReply  Metric ReqsSent Positive Negative No-Reply    AvgRTT(5 sec/1 min/5 min)
  44.44.44.44          00:03:11        6    62253    19675     8000        0    0.00/ 0.00/10.00
  66.66.66.66          never     Unreach        0        0        0        0    0.00/ 0.00/ 0.00
ETR Map-Servers:
  Map-Server           AvgRTT(5 sec/1 min/5 min)
  44.44.44.44          0.00/ 0.00/ 0.00
  66.66.66.66          0.00/ 0.00/ 0.00
LISP RLOC Statistics - last cleared: never
Control Packets:
  RTR Map-Requests forwarded:                       0
  RTR Map-Notifies forwarded:                       0
  DDT-Map-Requests in/out:                          0/0
  DDT-Map-Referrals in/out:                         0/0
Errors:
  Map-Request format errors:                        0
  Map-Reply format errors:                          0
  Map-Referral format errors:                       0
LISP Miscellaneous Statistics - last cleared: never
Errors:
  Invalid IP version drops:                         0
  Invalid IP header drops:                          0
  Invalid IP proto field drops:                     0
  Invalid packet size drops:                        0
  Invalid LISP control port drops:                  0
  Invalid LISP checksum drops:                      0
  Unsupported LISP packet type drops:               0
  Unknown packet drops:                             0      
 

Usage Guidelines

This command is used to display the current dynamic and static IPv6 EID-to-RLOC map-cache entries. When no IPv6 EID or IPv6 EID prefix is specified, summary information is listed for all current dynamic and static IPv4 EID-to-RLOC map-cache entries. When an IPv6 EID or IPv6 EID prefix is included, information is listed for the longest-match lookup in the cache. When the detail option is used, detailed (rather than summary) information related to all current dynamic and static IPv6 EID-to-RLOC map-cache entries is displayed.

The following is a sample output from the show lisp instance-id ipv6 map-cache command:

device# show lisp instance-id 101 ipv6 map-cache 
LISP IPv6 Mapping Cache, 2 entries

::/0, uptime: 00:00:26, expires: never, via static
  Negative cache entry, action: send-map-request
2001:DB8:AB::/48, uptime: 00:00:04, expires: 23:59:53, via map-reply, complete
  Locator   Uptime    State      Pri/Wgt
  10.0.0.6  00:00:04  up           1/100

The following sample output from the show lisp instance-id x ipv6 map-cache detail command displays a detailed list of current dynamic and static IPv6 EID-to-RLOC map-cache entries:

device#show lisp instance-id 101 ipv6 map-cache detail 
LISP IPv6 Mapping Cache, 2 entries

::/0, uptime: 00:00:52, expires: never, via static
  State: send-map-request, last modified: 00:00:52, map-source: local
  Idle, Packets out: 0
  Negative cache entry, action: send-map-request
2001:DB8:AB::/48, uptime: 00:00:30, expires: 23:59:27, via map-reply, complete
  State: complete, last modified: 00:00:30, map-source: 10.0.0.6
  Active, Packets out: 0
  Locator   Uptime    State      Pri/Wgt
  10.0.0.6  00:00:30  up           1/100
    Last up-down state change:         never, state change count: 0
    Last priority / weight change:     never/never
    RLOC-probing loc-status algorithm:
      Last RLOC-probe sent:            never

The following sample output from the show ipv6 lisp map-cache command with a specific IPv6 EID prefix displays detailed information associated with that IPv6 EID prefix entry.

device#show lisp instance-id 101 ipv6 map-cache 2001:DB8:AB::/48 
LISP IPv6 Mapping Cache, 2 entries

2001:DB8:AB::/48, uptime: 00:01:02, expires: 23:58:54, via map-reply, complete
  State: complete, last modified: 00:01:02, map-source: 10.0.0.6
  Active, Packets out: 0
  Locator   Uptime    State      Pri/Wgt
  10.0.0.6  00:01:02  up           1/100
    Last up-down state change:         never, state change count: 0
    Last priority / weight change:     never/never
    RLOC-probing loc-status algorithm:    
        Last RLOC-probe sent:            never

Usage Guidelines

When a host is detected by the tunnel router (xTR), it registers the host with the map server (MS). Use the show lisp instance-id x ipv4 server command to see the site registration details. TCP registrations display the port number, whereas UDP registration do not display port number. The port number is 4342 by default fir UDP registration.

The following are sample outputs of the command :

device# show lisp instance-id 100 ipv4 server
LISP Site Registration Information
* = Some locators are down or unreachable
# = Some registrations are sourced by reliable transport
 
Site Name      Last      Up     Who Last             Inst     EID Prefix
               Register         Registered           ID
XTR            00:03:22  yes*#  172.16.1.4:64200     100      101.1.0.0/16
               00:03:16  yes#   172.16.1.3:19881     100      101.1.1.1/32

device# show lisp instance-id 100 ipv4 server 101.1.0.0/16
LISP Site Registration Information                                       
 
Site name: XTR
Allowed configured locators: any
Requested EID-prefix:          
 
  EID-prefix: 101.1.0.0/16 instance-id 100
    First registered:     00:04:24        
    Last registered:      00:04:20
    Routing table tag:    0
    Origin:               Configuration, accepting more specifics
    Merge active:         No
    Proxy reply:          No
    TTL:                  1d00h
    State:                complete
    Registration errors:
      Authentication failures:   0
      Allowed locators mismatch: 0
    ETR 172.16.1.4:64200, last registered 00:04:20, no proxy-reply, map-notify
                          TTL 1d00h, no merge, hash-function sha1, nonce 0xC1ED8EE1-0x553D05D4
                          state complete, no security-capability
                          xTR-ID 0x46B2F3A5-0x19B0A3C5-0x67055A44-0xF5BF3FBB
                          site-ID unspecified
                          sourced by reliable transport
      Locator     Local  State      Pri/Wgt  Scope
      172.16.1.4  yes    admin-down 255/100  IPv4 none

 

The following is an ouput that shows an UDP registration (without port number):

device# show lisp instance-id 100 ipv4 server 101.1.1.1/32
LISP Site Registration Information                                       
 
Site name: XTR
Allowed configured locators: any
Requested EID-prefix:          
 
  EID-prefix: 101.1.1.1/32 instance-id 100
    First registered:     00:00:08        
    Last registered:      00:00:04        
    Routing table tag:    0               
    Origin:               Dynamic, more specific of 101.1.0.0/16
    Merge active:         No                                   
    Proxy reply:          No                                   
    TTL:                  1d00h                                
    State:                complete                             
    Registration errors:
      Authentication failures:   0
      Allowed locators mismatch: 0
    ETR 172.16.1.3:46245, last registered 00:00:04, no proxy-reply, map-notify
                          TTL 1d00h, no merge, hash-function sha1, nonce 0x1769BD91-0x06E10A06
                          state complete, no security-capability
                          xTR-ID 0x4F5F0056-0xAE270416-0x360B42D6-0x6FCD3F5B
                          site-ID unspecified
                          sourced by reliable transport
      Locator     Local  State      Pri/Wgt  Scope
      172.16.1.3  yes    up         100/100  IPv4 none
    ETR 172.16.1.3, last registered 00:00:08, no proxy-reply, map-notify
                    TTL 1d00h, no merge, hash-function sha1, nonce 0x1769BD91-0x06E10A06
                    state complete, no security-capability
                    xTR-ID 0x4F5F0056-0xAE270416-0x360B42D6-0x6FCD3F5B
                    site-ID unspecified
      Locator     Local  State      Pri/Wgt  Scope
      172.16.1.3  yes    up         100/100  IPv4 none

Usage Guidelines

When a host is detected by the tunnel router (xTR), it registers the host with the map server (MS). Use the show lisp instance-id ipv6 server command to see the site registration details.

Usage Guidelines

This command is used to display IPv4 LISP statistics related to packet encapsulations, de-encapsulations, map requests, map replies, map registers, and other LISP-related packets.

The following are sample outputs of the command :

device# show lisp instance-id 100 ipv4 statistics

Usage Guidelines

This command is used to display IPv4 LISP statistics related to packet encapsulations, de-encapsulations, map requests, map replies, map registers, and other LISP-related packets.

The following are sample outputs of the command :

device# show lisp instance-id 100 ipv6 statistics

Usage Guidelines

The following is a sample output from the show lisp prefix-list command:

device# show lisp prefix-list 
Lisp Prefix List information for router lisp 0

Prefix List: set
    Number of entries: 1       
    Entries:
	1.2.3.4/16
	    Sources: static

Usage Guidelines

The show lisp session command displays only those sessions that are in Up or Down state. Use the show lisp session all command to see all sessions in any state.

The following is a sample output of the command show lisp session on an MSMR:

device# show lisp session
Sessions for VRF default, total: 4, established: 2
Peer                           State      Up/Down        In/Out    Users
172.16.1.3:22667               Up         00:00:52        4/8      2
172.16.1.4:18904               Up         00:22:15        5/13     1

device# show lisp session all
Sessions for VRF default, total: 4, established: 2
Peer                           State      Up/Down        In/Out    Users
172.16.1.3                     Listening  never           0/0      0
172.16.1.3:22667               Up         00:01:13        4/8      2
172.16.1.4                     Listening  never           0/0      0
172.16.1.4:18904               Up         00:22:36        5/13     1

Usage Guidelines

Use the use-petr command to enable an Ingress Tunnel Router (ITR) or Proxy Ingress Tunnel Router (PITR) to use IPv4 Proxy Egress Tunnel Router (PETR) services. When the use of PETR services is enabled, instead of natively forwarding LISP endpoint identifier (EID) (source) packets destined to non-LISP sites, these packets are LISP-encapsulated and forwarded to the PETR. Upon receiving these packets, the PETR decapsulates them and then forwards them natively toward the non-LISP destination.

Do not use use-petr command in Service-Ethernet configuration mode.

PETR services may be necessary in several cases:

1. By default when a LISP site forwards packets to a non-LISP site natively (not LISP encapsulated), the source IP address of the packet is that of an EID. When the provider side of the access network is configured with strict unicast reverse path forwarding (uRPF) or an anti-spoofing access list, it may consider these packets to be spoofed and drop them since EIDs are not advertised in the provider core network. In this case, instead of natively forwarding packets destined to non-LISP sites, the ITR encapsulates these packets using its site locator(s) as the source address and the PETR as the destination address.

   Note

   The use of the use-petr command does not change LISP-to-LISP or non-LISP-to-non-LISP forwarding behavior. LISP EID packets destined for LISP sites will follow normal LISP forwarding processes and be sent directly to the destination ETR as normal. Non-LISP-to-non-LISP packets are never candidates for LISP encapsulation and are always forwarded natively according to normal processes.

2. When a LISP IPv6 (EID) site needs to connect to a non-LISP IPv6 site and the ITR locators or some portion of the intermediate network does not support IPv6 (it is IPv4 only), the PETR can be used to traverse (hop over) the address family incompatibility, assuming that the PETR has both IPv4 and IPv6 connectivity. The ITR in this case can LISP-encapsulate the IPv6 EIDs with IPv4 locators destined for the PETR, which de-encapsulates the packets and forwards them natively to the non-LISP IPv6 site over its IPv6 connection. In this case, the use of the PETR effectively allows the LISP site packets to traverse the IPv4 portion of network using the LISP mixed protocol encapsulation support.