This module describes the configuration of
Tunnel-IPSec interfaces on the
Cisco CRS
Router.
Tunnel interfaces are virtual interfaces that
provide encapsulation of arbitrary packets within another transport protocol.
The Tunnel-IPSec interface provides secure communications over otherwise
unprotected public routes.
A virtual interface represents a logical packet
switching entity within the router. Virtual
Interfaces
have a global scope and do not have an associated location. The
Cisco IOS XR
Software
uses the rack/slot/module/port notation for identifying physical
interfaces, but uses a globally unique numerical ID after the interface name to
identify virtual interfaces. Examples of this numerical ID are Loopback 0,
Loopback 1, and
Null99999. The ID is unique
for each virtual interface type so you may simultaneously have a Loopback 0 and
a Null 0.
Virtual interfaces have their control plane
presence on the active route
processor (RP). The configuration and
control plane are mirrored onto the standby
RP
and, in the event of a
switchover, the virtual
interfaces will move to the standby, which then becomes the newly active
RP.
Note |
Subinterfaces can be physical or virtual,
depending on their parent interface.
|
Virtual tunnels are configured on any
RP
or distributed
RP
(DRP), but they are created
and operate only from the
RP.
Note |
Tunnels do not have a one-to-one modular
services card association.
|
Feature History for Configuring Tunnel Interfaces on Cisco IOS XR
Software
Release
|
Modification
|
Release 2.0
|
This feature was introduced on the
Cisco CRS Router.
|