Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

The EIGRP Over the Top feature enables a single end-to-end Enhanced Interior Gateway Routing Protocol (EIGRP) routing domain that is transparent to the underlying public or private WAN transport that is used for connecting disparate EIGRP customer sites. When an enterprise extends its connectivity across multiple sites through a private or a public WAN connection, the service provider mandates that the enterprise use an additional routing protocol, typically the Border Gateway Protocol (BGP), over the WAN links to ensure end-to-end routing. The use of an additional protocol causes additional complexities for the enterprise, such as additional routing processes and sustained interaction between EIGRP and the routing protocol to ensure connectivity, for the enterprise. With the EIGRP Over the Top feature, routing is consolidated into a single protocol (EIGRP) across the WAN, which provides the following benefits:

• There is no dependency on the type of WAN connection used.

• There is no dependency on the service provider to transfer routes.

• There is no security threat because the underlying WAN has no knowledge of enterprise routes.

• This feature simplifies dual carrier deployments and designs by eliminating the need to configure and manage EIGRP-BGP route distribution and route filtering between customer sites.

• This feature allows easy transition between different service providers.

• This feature supports both IPv4 and IPv6 environments.

The EIGRP Over the Top solution can be used to ensure connectivity between disparate Enhanced Interior Gateway Routing Protocol (EIGRP) sites. This feature uses EIGRP on the control plane and Locator ID Separation Protocol (LISP) encapsulation on the data plane to route traffic across the underlying WAN architecture. EIGRP is used to distribute routes between customer edge (CE) devices within the network, and the traffic forwarded across the WAN architecture is LISP encapsulated. Therefore, to connect disparate EIGRP sites, you must configure the neighbor command with LISP encapsulation on every CE in the network.

If your network has many CEs, then you can use EIGRP Route Reflectors (E-RRs) to form a half-mesh topology and ensure connectivity among all CEs in the network. An E-RR is an EIGRP peer that receives EIGRP route updates from CEs in the network and reflects these updates to other EIGRP CE neighbors without changing the next hop or metrics for the routes. An E-RR can also function as a CE in the network. You must configure E-RRs with the remote-neighbors source command to enable E-RRs to listen to unicast messages from peer CE devices and reflect the messages to other EIGRP CE neighbors. You must configure the CEs with the neighbor command to allow them to identify the E-RRs in their network and exchange routes with the E-RRs. Upon learning routes from E-RRs, the CEs install these routes into their routing information base (RIB). You can use dual or multiple E-RRs for redundancy. The CEs form adjacencies with all E-RRs configured in the network, thus enabling multihop remote neighborship amongst themselves.

A security group is a grouping of users, endpoint devices, and resources that share access control policies. Security groups are defined by the administrator in the ACS. As new users and devices are added to the Cisco TrustSec (CTS) domain, the authentication server assigns these new entities to appropriate security groups. CTS assigns to each security group a unique 16-bit security group number whose scope is global within a CTS domain. The number of security groups in the router is limited to the number of authenticated network entities. Security group numbers do not need to be manually configured.

Once a device is authenticated, CTS tags any packet that originates from that device with an SGT that contains the security group number of the device. The packet carries this SGT throughout the network within the CTS header. The SGT is a single label that determines the privileges of the source within the entire CTS domain. The SGT is identified as the source because it contains the security group of the source. The destination device is assigned a destination group tag (DGT).

Note	The CTS packet tag does not contain the security group number of the destination device.

The EIGRP OTP Support enables to propagate SGT from site-to-site across WAN using OTP transport. OTP uses LISP to send the data traffic. OTP carries the SGT over the Layer 3 (L3) clouds across multiple connections/network and also provides access control at a remote site.

1.    enable


2.    configure terminal


3.    router eigrp virtual-name


4.    address-family ipv4 autonomous-system as-number


5.    neighbor{ip-address | ipv6-address} interface-type interface-number [remote maximum-hops [lisp-encap [lisp-id]]]


6.    network ip-address[wildcard-mask]


7.    end

Device> enable

Device# configure terminal

Device(config)# router eigrp test

Device(config-router)# address-family ipv4 autonomous-system 100

Device(config-router-af)# neighbor 10.0.0.1 gigabitethernet 0/0/1 remote 2 lisp-encap 1

Device(config-router-af)# network 192.168.0.0 255.255.0.0

Device(config-router-af)# end

1.    enable


2.    configure terminal


3.    router eigrp virtual-name


4.    address-family ipv4 unicast autonomous-system as-number


5.    af-interface interface-type interface-number


6.    no next-hop-self


7.    no split-horizon


8.    exit


9.    remote-neighbors source interface-type interface-number unicast-listen lisp-encap


10.    network ip-address


11.    end

Device> enable

Device# configure terminal

Device(config)# router eigrp test

Device(config-router)# address-family ipv4 unicast autonomous-system 100

Device(config-router-af)# af-interface gigabitethernet 0/0/1 

Device(config-router-af-interface)# no next-hop-self

Device(config-router-af-interface)# no split-horizon

Device(config-router-af-interface)# exit

Device(config-router-af)# remote-neighbors source gigabitethernet 0/0/1 unicast-listen lisp-encap

Device(config-router-af)# network 192.168.0.0

Device(config-router-af)# end

1.    enable


2.    configure terminal


3.    router eigrp virtual instance name


4.    address-family ipv4 autonomous-system as-number


5.    topology base


6.    cts propagate sgt


7.    end

Device> enable

Device# configure terminal

Device (config)# router eigrp kmd

Device (config-router)# address-family ipv4 autonomous-system 100

Device (config-router-af)# topology base

Device (config-router-af)# cts propagate sgt

Device (config-router-af)# end