clear lisp eid
To clear the ASA EID table, use the clear lisp eid command in privileged EXEC mode.
clear lisp eid [ ip_address ]
Syntax Description
ip_address |
Removes the specified IP address from the EID table. |
Command Default
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode |
Firewall Mode |
Security Context |
|||
---|---|---|---|---|---|
Routed |
Transparent |
Single |
Multiple |
||
Context |
System |
||||
Privileged EXEC |
|
|
|
|
— |
Command History
Release |
Modification |
---|---|
9.5(2) |
We introduced this command. |
Usage Guidelines
The ASA maintains an EID table that correlates the EID and the site ID. The clear lisp eid command clears EID entries in the table.
About LISP Inspection for Cluster Flow Mobility
The ASA inspects LISP traffic for location changes and then uses this information for seamless clustering operation. With LISP integration, the ASA cluster members can inspect LISP traffic passing between the first hop router and the ETR or ITR, and can then change the flow owner to be at the new site.
Cluster flow mobility includes several inter-related configurations:
-
(Optional) Limit inspected EIDs based on the host or server IP address—The first hop router might send EID-notify messages for hosts or networks the ASA cluster is not involved with, so you can limit the EIDs to only those servers or networks relevant to your cluster. For example, if the cluster is only involved with 2 sites, but LISP is running on 3 sites, you should only include EIDs for the 2 sites involved with the cluster. See the policy-map type inspect lisp , allowed-eid, and validate-key commands.
-
LISP traffic inspection—The ASA inspects LISP traffic for the EID-notify message sent between the first hop router and the ITR or ETR. The ASA maintains an EID table that correlates the EID and the site ID. For example, you should inspect LISP traffic with a source IP address of the first hop router and a destination address of the ITR or ETR. See the inspect lisp command.
-
Service Policy to enable flow mobility on specified traffic—You should enable flow mobility on business-critical traffic. For example, you can limit flow mobility to only HTTPS traffic, and/or to traffic to specific servers. See the cluster flow-mobility lisp command.
-
Site IDs—The ASA uses the site ID for each cluster unit to determine the new owner. See the site-id command.
-
Cluster-level configuration to enable flow mobility—You must also enable flow mobility at the cluster level. This on/off toggle lets you easily enable or disable flow mobility for a particular class of traffic or applications. See the flow-mobility lisp command.