Implementing A Satellite Nv System - Cisco ASR 9000 Series Configuring Network Settings

Implementing a Satellite nV System

Restrictions of the Satellite nV System
These are some of the software restrictions of the satellite nV system in the current release. These
restrictions will be eliminated in the future releases.
•
•
•
•
Refer to the Cisco ASR 9000 Series Aggregation Services Router Release Notes, Release 4.2.1 for
Note
additional software restrictions.
Implementing a Satellite nV System
The Interface Control Plane Extender(ICPE) infrastructure has a mechanism to provide the Control
Plane of an interface physically located on the Satellite device in the local Cisco IOS XR software. After
this infrastructure is established, the interfaces behave like other physical ethernet interfaces on the
router.
The ICPE configuration covers these functional areas, which are each required to set up full connectivity
with a Satellite device:
•
•
•
•
Defining the Satellite nV System
Each satellite that is to be attached to Cisco IOS XR software must be configured on the host, and also
be provided with a unique identifier. In order to provide suitable verification of configuration and
functionality, the satellite type, and its capabilities must also be specified.
Further, in order to provide connectivity with the satellite, an IP address must be configured, which will
be pushed down to the satellite through the Discovery protocol, and allows Control protocol
connectivity.
This task explains how to define the satellite system by assigning an ID and basic identification
information.
Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Configuration Guide
HC-714
Configuring the Satellite Network Virtualization (nV) System on the Cisco ASR 9000 Series Router
The inter-chassis link redundancy is supported only through the static EtherChannel, and not
through LACP based link bundles. Minimum and maximum link commands are not applicable when
ICL is a bundle.
If a satellite system is operating in redundant ICL mode, then you cannot configure link bundles of
any form (with or without LACP) on the access ports of that same satellite switch.
If a satellite system is operating in redundant ICL mode, then Ethernet OAM features are not
supported on the access ports of that satellite.
Multi-chassis Link Aggregation is supported if there are two independent
Cisco ASR 9000 Series Routers acting as the POA (Point of Attachment), each with its own satellite
switch, and the DHD (Dual Homed Device) connecting through each of the satellite switches.
However, MC-LAG is not supported with a single satellite switch that connects two separate
Cisco ASR 9000 Series Routers through an ICL LAG.
Defining the Satellite nV System, page 714
Configuring the host IP address, page 717
Configuring the Inter-Chassis Links and IP Connectivity, page 718
Plug and Play Satellite nV Switch Turn up: (Rack, Plug, and Go installation), page 721
OL-26061-03