Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Configuration Guide, Release 5.1.x
Configuring the Satellite Network Virtualization (nV) System
Downloads: This chapterpdf (PDF - 0.99MB) The complete bookPDF (PDF - 9.31MB) | Feedback

Table of Contents

Configuring the Satellite Network Virtualization (nV) System

Contents

Prerequisites for Configuration

Overview of Satellite nV Switching System

Benefits of Satellite nV System

Restrictions of the Satellite nV System

Overview of Port Extender Model

Advanced Satellite nV System Network Topologies

Features of Dual Home Network Architecture

General Limitations of Satellite nV System Network Topologies

Simple Ring Satellite nV Topology

Simple Ring Topology Configuration

Limitations of Simple Ring Topology

Layer 2 Fabric Network Architecture

Limitations of Layer 2 Fabric Network Topology

Features Supported in the Satellite nV System

Satellite System Physical Topology

Inter-Chassis Link Redundancy Modes and Load Balancing

Port Partitioning

Satellite Discovery and Control Protocols

Satellite Discovery and Control Protocol IP Connectivity

Layer-2 and L2VPN Features

Layer-3 and L3VPN Features

Layer-2 and Layer-3 Multicast Features

Quality of Service

Cluster Support

Time of Day Synchronization

Satellite Chassis Management

Ethernet Link OAM

Implementing a Satellite nV System

Defining the Satellite nV System

Configuring the Host IP Address

Configuring the Inter-Chassis Links and IP Connectivity

Configuring the Inter-Chassis Links in a Dual Home Network Topology

Configuring the Inter-Chassis Links for a Simple Ring Topology

Auto-IP

Configuring the Satellite nV Access Interfaces

Configuring the Fabric CFM

Plug and Play Satellite nV Switch Turn up: (Rack, Plug, and Go installation)

Upgrading and Managing Satellite nV Software

Image Upgrade for Cisco ASR 9000v Satellite

Prerequisites

Installing a Satellite

Monitoring the Satellite Software

Show Commands for Advanced Network Topologies

Monitoring the Satellite Protocol Status

Monitoring the Satellite Inventory

Reloading the Satellite Device

Port Level Parameters Configured on a Satellite

Loopback Types on Satellite Ports

Configuration Examples for Satellite nV System

Satellite System Configuration: Example

Satellite Global Configuration

ICL (satellite-fabric-link) Interface Configuration

Satellite Interface Configuration

Satellite Management using private VRF

Configuration of Satellite using Auto-IP

Satellite Configuration with Dual-homed Hosts

Dual-Home for multiple satellites with Single physical ICLs on both Hosts and Satellites

Dual Home configuration for SAT1:

Dual Home configuration for SAT2:

Configuring a Satellite nV System in Simple Ring Topology

Configuring a Satellite nV System in Layer 2 Fabric Network Topology

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Configuring the Satellite Network Virtualization (nV) System

This module describes the configuration of the Satellite Network Virtualization (Satellite nV) system on the Cisco ASR 9000 Series Aggregation Services Routers.

Feature History for Configuring Satellite System

Release
Modification

Release 4.2.1

  • Support for Satellite Network Virtualization (Satellite nV) Service was included on the Cisco ASR 9000 Series Router.

Release 4.2.3

  • Support for 36-Port 10-Gigabit Ethernet Line Card was included.

Release 4.3.0

  • Support for Cisco ASR 9001 and Cisco ASR 9922 Series Routers as hosts was included.
  • Support for Cisco ASR 901, and Cisco ASR 903 as Satellite devices was included.

Release 4.3.1

  • Support for Auto-IP feature was included.
  • Support for Link Layer Discovery Protocol (LLDP) over Satellite access interface over bundle ICL was included.
  • Support for Cisco CRS-3 Router with Cisco CRS-3 Modular Services Line Card as host was included.
  • Procedure to convert a Cisco ASR 901 or Cisco ASR 903 Router to a satellite was added.

Release 5.1.1

These features are included on Cisco ASR 9000v and Cisco ASR 901 satellites:

  • Support for Simple Ring Satellite nV topology was included.
  • Support for dual-homed Satellite nV network architecture was included.
  • Support for Layer 2 Fabric network architecture was included.
  • Support for Fabric Ethernet Connectivity Fault Management (Ethernet CFM) was included.
  • Support for 1G ICL on ports 1/45 and 1/46 on Cisco ASR 9000v satellite was included for all the Satellite nV topologies by using 1G SFPs.
  • Support for these new satellites was included:

Cisco ASR 901 Series Aggregation Services Router Chassis, Ethernet-only interfaces, 10 GE, DC power, USB
(A901-6CZ-F-D)

Cisco ASR 901 Series Aggregation Services Router Chassis, Ethernet and TDM interfaces, 10 GE, DC power, USB (A901-6CZ-FT-D)

Cisco ASR 901 Series Aggregation Services Router Chassis, Ethernet-only interfaces, 10 GE, AC power, USB
(A901-6CZ-F-A)

Cisco ASR 901 Series Aggregation Services Router Chassis, Ethernet and TDM interfaces, 10 GE, AC power, USB (A901-6CZ-FT-A)

  • Support for QoS Offload over Satellite was supported. See
    Cisco ASR 9000 Series Aggregation Services Router QoS Configuration Guide for more details.

Release 5.1.2

  • Support for 200 satellites on the Satellite nV System for each
    Cisco ASR 9000 Series Router (host) was included.
  • Support for 200 satellites on the Satellite nV System for each Network Processor (NP) was included.
  • Support for 200 satellites on the Satellite nV System for each Line Card was included.

Prerequisites for Configuration

You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Before configuring the Satellite nV system, you must have these hardware and software installed in your chassis:

  • Hardware (Host):

Cisco ASR 9000 Series Aggregation Services Routers with Cisco ASR 9000 Enhanced Ethernet line cards as the location of Inter Chassis Links. Cisco ASR 9000 Ethernet Line Cards can co-exist in the Satellite nV System but cannot be used for Satellite ICLs and also with ISM/VSM. Also, only RSP3 is the supported Route processor for the Cisco ASR 9000 Series Routers.

  • Hardware (Satellite) :

Cisco ASR9000v, Cisco ASR 901, or Cisco ASR 903 routers

Cisco ASR 901 Series Aggregation Services Router Chassis, Ethernet-only interfaces, 10 GE, DC power, USB (PID: A901-6CZ-F-D)

Cisco ASR 901 Series Aggregation Services Router Chassis, Ethernet and TDM interfaces, 10 GE, DC power, USB (PID: A901-6CZ-FT-D)

Cisco ASR 901 Series Aggregation Services Router Chassis, Ethernet-only interfaces, 10 GE, AC power, USB (PID: A901-6CZ-F-A)

Cisco ASR 901 Series Aggregation Services Router Chassis, Ethernet and TDM interfaces, 10 GE, AC power, USB (PID: A901-6CZ-FT-A)


Note 10-Gigabit Ethernet interfaces are not supported as ICL or access ports for Cisco ASR 901 Router.


  • Software — Cisco IOS XR Software Release 4.2.1 or later.

For more information on other hardware requirements and list of TMG optics supported, see
Cisco ASR 9000 Series Aggregation Services Router Hardware Installation Guide and
Cisco ASR 9000 Series Aggregated Services Router Satellite Systems Installation Guide
.

Overview of Satellite nV Switching System

The Cisco ASR 9000 Series Router Satellite Network Virtualization (nV) service or the Satellite Switching System enables you to configure a topology in which one or more satellite switches complement one or more Cisco ASR 9000 Series routers, to collectively realize a single virtual switching system. In this system, the satellite switches act under the management control of the routers. The complete configuration and management of the satellite chassis and features is performed through the control plane and management plane of the Cisco ASR 9000 Series Router, which is referred to as the host.


Note Cisco ASR 9001 and Cisco ASR 9922 Series Routers, and Cisco CRS-3 Router with Modular Services Line Card can also be used as hosts in the Satellite nV System.


Interconnection between the Cisco ASR 9000 Series Router and its satellites is through standard Ethernet interfaces. When the Satellite nV service was introduced in Cisco IOS XR Release 4.2.x,
Cisco ASR 9000v was used as the satellite device. It had four 10 Gigabit ports that were used as Interchassis Links (ICL).

On the other hand, the Cisco ASR 901 has two 1-Gigabit Ethernet ports that are used as ICL.
Cisco ASR 903 can have upto two 10 Gigabit ports that can be used as ICL and the 10 Gigabit IMs must be inserted in subslots 0 and 1 only on the ASR903 chassis. The rest of the subslots can be used for 1 Gigabit SFP/Ethernet IMs for access ports. In general, the type of interface used on the host is decided on the basis of the satellite device used. See Figure 36.


Note Both the 1-Gigabit Ethernet or 10-Gigabit Ethernet interfaces used as ICL are supported on the
Cisco ASR 9000 Enhanced Ethernet line card and not on the Cisco ASR 9000 Ethernet line card.



Note When Cisco ASR 903 is used as a satellite, TDM interfaces cannot be used in the Satellite nV System and RP redundancy on the chassis is not available.


 

Figure 36 Cisco ASR 9000 Series Satellite nV Switching System

This type of architecture can be realized in a carrier Ethernet transport network, with the satellite switches used as either access switches, or pre-aggregation and aggregation switches. These switches feed into an edge router, such as the Cisco ASR 9000 Series Router or Cisco CRS-3 Router where more advanced Layer 2 and Layer 3 services are provisioned. The network topology depicted in Figure 36 is called the Hub and Spoke network topology.

You can also utilize this model in a Fiber To The Business (FTTB) network application, where business internet and VPN services are offered on a commercial basis. Further, it can also be used in other networks, such as wireless or Radio Access Network(RAN) backhaul aggregation networks.

Benefits of Satellite nV System

The Cisco ASR 9000 Series satellite nV system offers these benefits:

1. Extended port scalability and density - You can create a virtual line card with more than 400 physical Gigabit Ethernet ports. There is a significant increase of Ethernet port density in the resulting logical Cisco ASR 9000 Series Router. For example, a single 24-port Ten Gigabit Ethernet line card on the Cisco ASR 9000 Series Router could integrate up to 24 satellite switches each with 44 GigE ports; this results in an effective port density of 1056 Gigabit Ethernet ports for each
Cisco ASR 9000 Series Router line card slot. In other configurations, even higher port density can be achieved. This is beneficial because the Cisco ASR 9000 Series Router has a per-slot non blocking capacity of up to 400 Gbps (with appropriate RSPs) and there is no other way of physically fitting hundreds of gigabit ethernet ports/ SFPs on the face plate of a single Cisco ASR 9000 Series line card. As a result, in order to utilize the full capacity of an Cisco ASR 9000 Series line card, it is necessary to physically separate out the ethernet ports, while maintaining logical management control. This would appear as if all ports were physically on a single large line card of the Cisco ASR 9000 Series Router.

2. Reduced cost - All the edge-routing capabilities and application features of the Cisco IOS XR software are available on low cost access switches.

3. Reduced operating expense - You can seamlessly upgrade software images, and also manage the chassis and services from a common point. This includes a single logical router view, single point of applying CLI or XML interface for the entire system of switches, a single point of monitoring the entire system of switches and a single point of image management and software upgrades for the entire system.

4. Enhanced feature consistency - All the features on the regular GigE ports of
Cisco ASR 9000 Series Router are also available on the access ports of a satellite access switch in a functionally identical and consistent manner. The typical application of a satellite system would be in the access and aggregation layers of a network. By integrating the access switches along with the aggregation or core switch, you can ensure that there are no feature gaps between the access switch and the aggregation or core switch. All features, such as carrier ethernet features, QoS and OAM, function consistently, from access to core, because of this integrated approach.

5. Improved feature velocity - With the satellite solution, every feature that is implemented on the Cisco ASR 9000 Series Router becomes instantly available at the same time in the access switch, resulting in an ideal feature velocity for the edge switch.

6. Better resiliency - The nV satellite solution enables better multi-chassis resiliency, as well as better end-to-end QoS. For more information on QoS capabilities, see Cisco ASR 9000 Series Aggregation Services Router QoS Configuration Guide .

 

Restrictions of the Satellite nV System

These are some of the software restrictions of the satellite nV system:

  • 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.
  • 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.
  • The Cisco Discovery Protocol (CDP) is not supported on a bundle Inter Chassis Link (ICL) between the Cisco ASR 9000 Series Router and satellite.
  • Cisco ASR 903 Router is not supported on RSP2 Route Processor due to the image size.
  • Cisco ASR 903 Router does not support the advanced topologies such as dual home, ring and
    Layer 2 fabric Network topologies.
  • When you convert from one satellite topology to another topology, such as hub and spoke to
    Layer 2 Fabric network topology, you must remove the existing ICL configurations from the interface in one commit followed by the new ICL configurations on the interface in a separate commit.

Note Refer to the Cisco ASR 9000 Series Aggregation Services Router Release Notes for additional software restrictions.


Overview of Port Extender Model

In the Port Extender Satellite switching system also called as Hub and Spoke model, a satellite switch is attached to its host through physical ethernet ports.


Note In releases later than Cisco IOS XR Software Release 4.2.1, attachment models beyond the port extender model are also supported.


The parent Cisco ASR 9000 Series Router is referred as the host in this model. From a management or a provisioning point of view, the physical access ports of the satellite switch are equivalent to the physical ethernet ports on the Cisco ASR 9000 Series Router. You do not need a specific console connection for managing the Satellite Switching System, except for debugging purposes. The interface and chassis level features of the satellite are visible in the control plane of Cisco IOS XR software running on the host. This allows the complete management of the satellites and the host as a single logical router.

Figure 37 Port Extender Satellite Switching System

In this model, a single Cisco ASR 9000 Series Router hosts two satellite switches, SAT1 and SAT2, to form an overall virtual Cisco ASR 9000 switching system; this is shown by the dotted line surrounding the Cisco ASR 9000 Series Router, SAT1, and SAT2 in Figure 37.

This structure effectively appears as a single logical Cisco ASR 9000 Series Router to the external network. External access switches A1, A2 and A3 connect to this overall virtual switch by physically connecting to SAT1 and SAT2 using normal ethernet links. The links between the satellite switches and the Cisco ASR 9000 Series Router are ethernet links, and are referred as ICLs (Inter-Chassis Links). The Cisco ASR 9000 Series Router is referred as the host in this system. When there is congestion on the interchassis links, an inbuilt QoS protection mechanism is available for the traffic.


Note SAT1, SAT2, and the host Cisco ASR 9000 Series Router need not be located in the same geographic location. This means that the ICLs need not be of nominal length for only intra-location or intra-building use. The ICLs may be tens, hundreds, or even thousands of miles in length, thereby creating a logical satellite switch spanning a large geography.



Note In a Cisco ASR 9000 Series Router multi-chassis cluster system, there are multiple
Cisco ASR 9000 Series Router systems within a single virtual switch system. Logically, however, it is still considered a single host system.


Advanced Satellite nV System Network Topologies

The Satellite nV system supports the dual-homed network architecture as shown in Figure 38. In the dual home architecture, two hosts are connected to a satellite through the Satellite Discovery And Control (SDAC) Protocol. The SDAC Protocol provides the behavioral, semantic, and syntactic definition of the relationship between a satellite device and its host.

Both these dual-homed hosts act in the active/standby mode for the satellite. The standby host takes control of the satellite only when the active host is down. The two hosts can leverage the ICCP infrastructure to provide redundant Layer 2 and Layer 3 services for Satellite Ethernet interfaces. The network traffic is switched through the active host. In case of connection loss to the active host due to various types of failure such as cut cable and host or client connection interface failure, the standby host becomes the active host and the active host becomes the new standby host. The hosts communicate with each other using ORBIT/ICCP protocols.

Figure 38 Dual Home Network Architecture

The advanced satellite nV system network topologies can be realized based on one of these architecture:

This table summarizes the network encapsulation techniques used by different Satellite nV System topologies.

Table 26 Supported Satellite Network Encapsulation

Topology Type
SDAC Discovery Protcol Packets
SDAC Control Protocol Packets
Data Packets

Hub and Spoke

Untagged LLC SNAP

Untagged TCP

802.1ad + customer payload

Layer 2 Fabric

Single tagged LLC SNAP

Single tagged TCP

802.1ah1 + customer payload

Simple Ring

Untagged LLC SNAP

Untagged TCP

802.1ah 1 + customer payload

1.Supports both 802.1ad and 802.1q as outer tag. Using 802.1q outer tag is a non-standard way of 802.1ah Encapsulation.

Features of Dual Home Network Architecture

These are some of the enhanced features offered by the dual home network architecture:

  • Shared control for chassis functionality — Chassis control functionality which includes software upgrade, chassis reload, and environment monitoring is completely shared by all hosts connected to the Satellite. Both the hosts get equal access to the information, and have full control of any available actions. As a result, a disruptive change initiated by one host, such as an upgrade is noticed by the other host as well. This means that here is no segregation of the chassis functionality and provides multiple views to the same information.

Note During a Dual Home switchover,there is a convergece of around 2.5 to 3 secs when bundle access interfaces are used. In order to get better convergence, you need to configure bundle wait-timer to 0.
By default this value is 2 seconds.


  • Active/Standby determination for per-port unicast traffic and per-stream multicast traffic — Active/Standby determination is controlled by the hosts. They exchange the pertinent information through ORBIT protocol, which includes electing a priority selection algorithm to use. This algorithm determines the factors that are taken into account when calculating priority information. The hosts then each send a single numerical priority value to the Satellite. The Satellite only picks the lowest priority value, and forwards data to that host. Independently, the hosts make the same determination, and the traffic flows bi-directionally between the Active host and the Satellite.
    The hosts take a number of parameters into account when calculating the priority value, including the user-configured priority, the hop-count (path length) from the host to the Satellite, and a tie-break of the chassis MAC for each host.

    Cisco IOS XR Software uses these parameters to calculate the priority, where each item is more important than any of the subsequent ones. This means that the subsequent parameters are only taken into account, if the higher-priority items are identical across the two hosts.

Connectivity – Indicates whether the Host and Satellite can currently exchange data

PE isolation – Indicates that if the PE is isolated, then it defers to the other host

Configured Priority – this is as early as possible to allow the greatest flexibility for the operator

Hop Count – this only affects simple rings, and provides a default traffic engineering algorithm based on number of intervening Satellite devices

Parity of the Satellite ID – this is used as a late tie breaker to provide some load balancing across two Hosts with numerous hub-and-spoke Satellites, in which the even-numbered Satellites prefer one host, while the odd-numbered Satellites prefer the other host

On a tie-breaker of all the previous priorities, it falls back to the Primary host, which is the one with the lowest chassis MAC address based on byte size.

  • Support for seamless Split Brain handling — A Split Brain is a condition in which the two hosts are no longer able to communicate with each other, but each of them can still communicate with the Satellite device. This scenario can be hazardous, because the devices can reach different conclusions, resulting in traffic loss, or loops and broadcast storms.

    The Satellite protocol has these features to cope with such a situation:

When connected to each other, the two hosts publish a shared System MAC. This allows the Satellites to recognize probes from what appear to be different hosts, but in fact come from a paired set of hosts.

Whenever a host-to-host connection is lost, each peer publsihes the Chassis MAC as the System MAC. This operation is seamless and does not require a reset of the state machines, and hence causes no traffic loss. This allows the Satellite to react, most likely by dropping its connection to one of the hosts.

Whenever the connection is restored, the hosts again start publishing the System MAC seamlessly and allowing the Satellite to restore functionality to the standby host.

If the host-to-host connection is lost while the host is PE-isolated, it immediately drops discovery to the satellite. This ensures that the satellite uses the host with an available path to the core, if one exists.

General Limitations of Satellite nV System Network Topologies

1. A satellite can be connected to only one Host in the Hub and Spoke topology model and can be connected to only two hosts in a Dual-homed network architecture.

2. A host can only be in one dual-home pairing.

3. All the advanced Satellite nV network topologies are supported on the Cisco ASR9000v and
Cisco ASR 901 Satellite types.

4. On the 10 Gigabit Ethernet Cisco ASR 901 AC model, 10G ports for ICL or access port is not supported.

Simple Ring Satellite nV Topology

These are the salient features of this topology:

  • A satellite or ring of satellites can be dual-homed to two hosts. In the Figure 39, all the three satellites are connected to the redundant hosts Host A and Host B.
  • The two hosts communicate using the ORBIT protocol over ICCP.
  • In simple ring topology, the satellite chassis serial number is a mandatory configuration to identify the satellite.
  • When the ring span is broken. the satellite and hosts detect the link failure using LOS mechanism and perform the necessary switching based Dual Home management.
  • The link failure is detected by LOS (loss of signal) in the case of Ring and Hub and Spoke topologies.

Figure 39 Simple Ring Topology

 

For configuration samples of Dual home architecture, see Satellite Configuration with Dual-homed Hosts. For a sample configuration of the simple ring topology, see the Configuration Examples for Satellite nV System section.

 
 

Simple Ring Topology Configuration

This is a sample ICL running configuration for a simple ring topology:

interface GigabitEthernet0/1/0/0
ipv4 point-to-point
ipv4 unnumbered Loopback10
nv
satellite-fabric-link network
redundancy
iccp-group 2
!
satellite 500
remote-ports GigabitEthernet 0/0/0-9
!
satellite 600
remote-ports GigabitEthernet 0/0/0-9
!
satellite 700
remote-ports GigabitEthernet 0/0/0-9
!
satellite 800
remote-ports GigabitEthernet 0/0/0-9
!

Limitations of Simple Ring Topology

  • If one of the satellite in a simple ring setup is removed from the ICL configuration, the subtending satellites remain in the connected state.
  • When the configuration for a new satellite is applied, then the existing conflicting nV configuration must be removed.
  • Bundle ICL interfaces are not supported in the Simple Ring topology.
  • When you activate a new image on the satellite in a simple ring topology based network, you need to initiate install transfer followed by an install activate. For more information, see Installing a Satellite.

Layer 2 Fabric Network Architecture

In the Layer 2 Fabric network architecture, a satellite is connected to one or two hosts through one of two Ethernet Virtual Circuits (EVC) of Layer 2 Fabric network. An EVC can be identified by two transports VLAN IDs, such as TP-VID-S and TP-VID-H. TP-VID-S is the VLAN ID assigned by the satellite side transport and TP-VID-H is the VLAN ID assigned by the host. The CFM based Fast Fabric Link Failure Detection is supported only in the Layer 2 Fabric Network Architecture. The illustrations Figure 40, Figure 41, and Figure 42 show different variants of Layer 2 Fabric network topology.


Note CFM is mandatory in the case of Layer 2 Fabric Network Architecture to ensure that link failure detection is fast.


Figure 40 Layer 2 Fabric Satellite Network Architecture with dual host

 

Figure 41 Layer 2 Fabric Single Home (SH) with Single Physical ICL on Host and Satellite

Figure 42 DH : Single physical ICLs on hosts and Multiple physical ICLs on satellite

Limitations of Layer 2 Fabric Network Topology

1. Bundle interfaces are not supported in Layer 2 Fabric architecture. In the Layer 2 Fabric topology, bundle ICL is not supported but sat-ether port bundle is supported.

2. Point to Multi-point Layer 2 cloud is not supported.

3. A Satellite can support only one encapsulation on a given physical interface. So, the Layer 2 fabric connections from both hosts must be configured with the same encapsulation type.

4. A Satellite cannot support multiple Layer 2 fabric connections with the same VLAN on the same physical ICL interface.

5. When Satellite ethernet bundle interfaces are configured on the access ports, we need to configure the bundle wait timer 0 to get better convergence.

6. Cisco ASR 9000v has these limitations on the Layer 2 Fabric network topology:

The usable VLAN range is from 2 to 4093.

Only four 10 Gigabit Ethernet ICLs can be used on the ports 1/45 to 1/48.

Only two 1 Gigabit Ethernet ICLs can be used on the ports 1/45 and 1/46.

Only 44 satellite ports are present (namely Gig1/1 to Gig1/44).

7. Cisco ASR 901 has these limitations on the Layer 2 Fabric network topology:

The usable VLAN range is from 2 to 4094.

Only two 1Gigabit Ethernet ICLs can be used (Gig0/10, Gig0/11).

Only 10 satellite ports (Gig0/0 to Gig 0/9).

8. These service state synchronization are not supported.

ANCP

IGMP

ARP

DHCP

Features Supported in the Satellite nV System

This section provides details of the features of a satellite system.

Satellite System Physical Topology

The satellite system supports the point-to-point, simple ring, hub and spoke physical topology, and the
Layer 2 Fabric network topology for the ICLs between satellite switches and the host. These topologies allows a physical Ethernet MAC layer connection from the satellite to the host. This can be realized using a direct Ethernet over Fiber or Ethernet over Optical transport (such as Ethernet over a SONET/ SDH/ CWDM/ DWDM network).

These topologies also allow a satellite switch to be geographically at a separate location, other than that of the host. There is no limit set for the distance, and the solution works even when the satellite is placed at a distance of tens, hundreds, or even thousands of miles from the host.

Inter-Chassis Link Redundancy Modes and Load Balancing

The Cisco ASR 9000 Series Satellite system supports these redundancy modes:

  • Non-redundant inter-chassis links mode - In this mode, there is no link level redundancy between inter-chassis links of a satellite.
  • Redundant inter-chassis links mode - In this mode, the link level redundancy between inter-chassis links are provided using a single link aggregation (LAG) bundle.

In the redundant ICL mode, the load balancing of traffic between members of the IC bundle is done using a simple hashing function based on the satellite access port ID, and not based on the flow based hash using L2 or L3 header contents from the packets. This ensures that a single ICL is used by all packets for a given satellite access port. As a result, the actions applied for QoS and other features consider all the packets belonging to a single satellite access port.


Note Cisco IOS XR Software supports the co-existence of redundant and non-redundant ICL modes on the same nV satellite shelf (only for 9000v) from Cisco IOS XR Software Release 4.3.x onwards. 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.



Note If a satellite system is operating in redundant ICL mode, then Ethernet OAM features are not supported on the access ports of that satellite. Additionally, redundant ICL mode is not supported for Layer 2 fabric and simple ring network topologies.


For more details on QoS application and configuration on ICLs, see Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide .

Port Partitioning

The Cisco ASR 9000 Series Satellite system allows you to split or partition the satellite ethernet ports across multiple ICL interfaces. You can split the satellite ports between 4 ICLs in Cisco ASR 9000v satellite and 2 ICLs in Cisco ASR 901 satellite.


Note Port partitioning is not supported for simple ring and Layer 2 fabric network topologies.


Satellite Discovery and Control Protocols

A Cisco proprietary discovery and control protocol is used between the satellite switches and the host Cisco ASR 9000 Series Router devices, to handle discovery, provisioning, and monitoring of the satellite devices from the host Cisco ASR 9000 Series Satellite System in-band over the ICLs. The Satellite Discovery And Control (SDAC) Protocol provides the behavioural, semantic, and syntactic definition of the relationship between a satellite device and its host.

Satellite Discovery and Control Protocol IP Connectivity

The connectivity for the SDAC protocol is provided through a normal in-band IP routed path over the ICLs using private and public IP addresses appropriate for the carrier's network.

You can configure a management IP address on the host CLI for each satellite switch and corresponding IP addresses on the ICLs. You can select addresses from the private IPv4 address space (for example, 10.0.0.0/8 or 192.1.168.0/24) in order to prevent any conflict with normal service level IPv4 addresses being used in the IPv4 FIB. You can also configure a private VRF that is used for only satellite management traffic, so that the IP addresses assigned to the satellites can be within this private VRF. This reduces the risk of address conflict or IP address management complexity compared to other IP addresses and VRFs that are used on the router.

Layer-2 and L2VPN Features

All L2 and L2VPN features that are supported on physical ethernet or bundle ethernet interfaces are also supported on Satellite Ethernet interfaces. The maximum number of bundles supported by Cisco ASR 9000 Series Router is increased to 510. For more details on L2VPN features supported on the Cisco ASR 9000 Series Satellite System, see Cisco ASR 9000 Series Aggregation Services Router L2VPN and Ethernet Services Configuration Guide .

Layer-3 and L3VPN Features

All MPLS L3VPN features that are supported on ethernet interfaces such as GRE, netflow, and so on, are also supported on the Cisco ASR 9000 Series Satellite System. For more information on these features, see Cisco ASR 9000 Series Aggregation Services Router MPLS Layer 3 VPN Configuration Guide and Cisco ASR 9000 Series Aggregation Services Router Netflow Configuration Guide .

Layer-2 and Layer-3 Multicast Features

All Layer-2 and Layer-3 multicast features, including IGMP, IGMP snooping, PIM, mLDP, MVPN, P2MP TE, are supported on Satellite Ethernet interfaces, as they are supported on normal Ethernet and bundle ethernet interfaces. For more information on these features supported on a satellite system, see Cisco ASR 9000 Series Aggregation Services Routers Multicast Configuration Guide .

Quality of Service

Most Layer-2, Layer-3 QoS and ACL features are supported on Satellite Ethernet interfaces that are similar to normal physical Ethernet interfaces, with the exception of any ingress policy with a queueing action. However, for QoS, there may be some functional differences in the behavior because in the
Cisco IOS XR Software Release 4.2.x, user-configured MQC policies are applied on the Cisco ASR 9000 Series Router, and not on the satellite switch interfaces. For more detailed information on QoS Offload and QoS policy attributes, features, and their configuration, see Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide.


Note User-configured QoS policies are independent of any default port level QoS that are applied in order to handle IC link congestion and oversubscription scenarios. In addition to the default port-level QoS applied on the satellite system ports, there is also some default QoS applied on the Cisco ASR 9000 Series Router side, to the ingress and egress traffic from and to the Satellite Ethernet ports.


Cluster Support

A cluster of Cisco ASR 9000 Series Routers is supported along with the satellite mode. A single cluster system can act like one logical Cisco ASR 9000 Series Router host system for a group of satellite switches. A satellite switch can also have some ICLs connect to rack 0 and other ICLs connect to rack 1 of a cluster system. For more information, see Configuring the nV Edge System on the Cisco ASR 9000 Series Router chapter.


Note The Satellite Ethernet interfaces cannot be used as cluster inter-rack links.


Time of Day Synchronization

The Time of Day parameter on the satellite switch is synchronized with the time of day on the host. This ensures that time stamps on debug messages and other satellite event logs are consistent with the host, and with all satellite switches across the network. This is achieved through the SDAC Discovery Protocol from the host to the satellite switch when the ICLs are discovered.

Satellite Chassis Management

The chassis level management of the satellite is done through the host because the satellite switch is a logical portion of the overall virtual switch. This ensures that service providers get to manage a single logical device with respect to all aspects including service-level, as well as box-level management. This simplifies the network operations. These operations include inventory management, environmental sensor monitoring, and fault/alarm monitoring for the satellite chassis through the corresponding CLI, SNMP, and XML interfaces of the host Cisco ASR 9000 Series Router.


Note The satellite system hardware features, support for SFPs, and compatible topologies are described in the Cisco ASR 9000 Series Aggregation Services Router Hardware Installation Guide.


Ethernet Link OAM

The Satellite nV Ethernet interfaces support Ethernet Link OAM feature when ICL is physical interface. But the feature does not work for SE with bundle ICL. Cisco IOS XR Software also supports Ethernet Link OAM feature over Satellite Ethernet interfaces when the ICL is a bundle interface.

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.

SUMMARY STEPS

1. configure

2. nv

3. satellite Satellite ID

4. serial-number string

5. description string (Optional)

6. type type

7. ipv4 address address

8. secret <password>

9. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2

nv

 

RP/0/RSP0/CPU0:router(config)# nv

Enters the nV configuration submode.

Step 3

satellite Sat ID

 

RP/0/RSP0/CPU0:router(config-nV)# satellite <100-65534>

Declares a new satellite that is to be attached to the host and enters the satellite configuration submode.

Step 4

serial-number string

 

RP/0/RSP0/CPU0:router(config-satellite)# serial-number CAT1521B1BB

Serial number is used for satellite authentication.

Step 5

description string

 

RP/0/RSP0/CPU0:router(config-satellite)# description Milpitas Building12

(Optional) Specifies any description string that is associated with a satellite such as location and so on.

Step 6

type type_name

 

RP/0/RSP0/CPU0:router(config-satellite)# satellite 200 type ?

asr9000v Satellite type

Defines the expected type of the attached satellite. The satellite types are ASR9000v, ASR901v, and ASR 903v. For other supported satellite types, see Prerequisites for Configuration.

Step 7

ipv4 address address

 

RP/0/RSP0/CPU0:router(config-satellite)# ipv4 address 10.22.1.2

Specifies the IP address to assign to the satellite. ICPE sets up a connected route to the specified IP address through all configured ICLs.

Step 8

secret password

 

RP/0/RSP0/CPU0:router(config-satellite)# secret <password>

Specifies the secret password to access the satellite. In order to login you must use root as the user name and password as the secret password.

Step 9

end

or

commit

 

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Host IP Address

This procedure gives you the steps to configure a host IP address on a loopback interface.

SUMMARY STEPS

1. configure

2. interface Loopback0

3. ipv4 address 8.8.8.8 255.255.255.255

4. end
or
commit

DETAILED STEPS

Command or Action
Purpose

Step 1

configure

 

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2

interface loopback0

 

 

 

RP/0/RSP0/CPU0:router(config)# interface loopback0

Specifies the loopback address for the interface.

Step 3

ipv4 address

 

RP/0/RSP0/CPU0:router(config-int)# ipv4 address 8.8.8.8 255.255.255.255

Configures the host IP address on a loopback interface.

Step 4

end

or

commit

 

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Inter-Chassis Links and IP Connectivity

Inter-Chassis Links (ICLs) need to be explicitly configured, in order to indicate which satellite is expected to be connected. You must also specify the access port, that is down-stream GigE ports, which crosslink up to the Host through the configured ICL. In order to establish connectivity between the host and satellite, suitable IP addresses must be configured on both sides. The satellite IP address is forwarded through the Discovery protocol. The configuration is described in the section, Defining the Satellite nV System.


Note This configuration shows the use of the global default VRF. The recommended option is to use a private VRF for nV IP addresses as shown in the Satellite Management using private VRF subsection under Satellite System Configuration: Example.


SUMMARY STEPS

1. configure

2. interface interface_name

3. description

4. ipv4 point-to-point (optional)

5. ipv4 unnumbered Loopback0 (optional)

6. nv

7. satellite-fabric-link satellite id

8. remote-ports interface-type

9. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2

interface interface-name

 

 

 

RP/0/RSP0/CPU0:router(config)# interface TenGigE0/2/1/0

The supported inter-chassis link interface types are limited by the connectivity provided on the supported satellites. GigabitEthernet, TenGigE, and Bundle-Ether interfaces are the only support ICL types.

Step 3

description

 

 

 

RP/0/RSP0/CPU0:router(config-interface)# description To Sat5 1/46

Specifies the description of the supported inter-chassis link interface type.

Step 4

ipv4 point-to-point

 

 

 

RP/0/RSP0/CPU0:router(config-interface)# ipv4 point-to-point

(Optional) Configures the IPv4 point to point address.

Step 5

ipv4 unnumbered loopback0

 

 

 

RP/0/RSP0/CPU0:router(config-interface)# interface unnumbered loopback0

(Optional) Configures the IPv4 loopback address on the interface.

Step 6

nv

 

RP/0/RSP0/CPU0:router(config-if)# nv

Enters the Network Virtualization configuration mode.

Step 7

satellite-fabric-link satellite <id>

 

RP/0/RSP0/CPU0:router(config-int-nv)# satellite-fabric-link satelite 200

Specifies that the interface is an ICPE inter-chassis link.

Step 8

remote-ports interface-type

 

RP/0/RSP0/CPU0:router(config-int-nv)# remote-ports GigabitEthernet 0/0/0-30

Configures the remote satellite ports 0 to 30.

Step 9

end

or

commit

 

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Note For information on QoS configuration on ICLs , see Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide.


Configuring the Inter-Chassis Links in a Dual Home Network Topology

These are the steps for configuring Inter-chassis links in the case of a dual home topology.

Prerequisites

  • MPLS LDP needs to be up and running between the two hosts for the dual home configuration.

SUMMARY STEPS

1. configure

2. interface interface_name

3. satellite-fabric-link satellite 100

4. ipv4 point-to-point

5. ipv4 unnumbered Loopback10

6. redundancy iccp-group

7. member neighbor 9.9.9.9

8. backbone interface interface_type

9. remote-ports interface-type

10. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2

interface interface-name

 

 

 

RP/0/RSP0/CPU0:router(config)# interface TenGigE0/2/1/0

The supported inter-chassis link interface types are limited by the connectivity provided on the supported satellites. GigabitEthernet, TenGigE, and Bundle-Ether interfaces are the only support ICL types.

Step 3

satellite-fabric-link satellite <satellite id>

 

 

 

RP/0/RSP0/CPU0:router(config-interface)# satellite-fabric-link satellite 100

Configures the ICPE inter-chassis link for the specified satellite.

Step 4

ipv4 point-to-point

 

 

 

RP/0/RSP0/CPU0:router(config-interface)# ipv4 point-to-point

(Optional) Configures the IPv4 point to point address.

Step 5

ipv4 unnumbered loopback0

 

 

 

RP/0/RSP0/CPU0:router(config-interface)# interface unnumbered loopback0

(Optional) Configures the IPv4 loopback address on the interface.

Step 6

redundancy iccp-group

 

 

 

RP/0/RSP0/CPU0:router(config-interface)# redundancy iccp-group 1

Configures the ICCP redundancy group.

Step 7

member neighbor 9.9.9.9

 

RP/0/RSP0/CPU0:router(config-interface)# member neighbor 9.9.9.9

Configures the LDP neighbor.

Step 8

backbone interface interface_type

 

RP/0/RSP0/CPU0:router(config-interface)# backbone interface TenGigE0/1/0/3

(Optional) Configures the backbone interface for the PE isolation.

Step 9

remote-ports interface-type

 

RP/0/RSP0/CPU0:router(config-int-nv)# remote-ports GigabitEthernet 0/0/0-30

 

Configures the remote satellite ports 0 to 30..

Step 10

end

or

commit

 

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Inter-Chassis Links for a Simple Ring Topology

These are the steps for configuring Inter-chassis links in the case of a simple ring topology.

SUMMARY STEPS

1. configure

2. redundancy iccp-group

3. member-neighbor 9.9.9.9

4. host-priority value (Optional)

5. nv satellite system-mac dcddc.dcdc.dcdc

6. interface interface_name

7. ipv4 point-to-point

8. ipv4 unnumbered Loopback10

9. nV

10. satellite-fabric-link network

11. redundancy iccp-group

12. satellite < satellite id1>

13. remote-ports interface-type

14. satellite <satellite id2>

15. remote-ports interface-type

16. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2

redundancy iccp group

 

RP/0/RSP0/CPU0:router(config)# redundancy iccp group 2

Configures the redundancy ICCP group between the hosts.

Step 3

member neighbor 9.9.9.9

 

RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)# member neighbor 9.9.9.9

Configures the LDP neighbor.

Step 4

host-priority <0-255>

 

RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)# host-priority 128

(Optional) Specifies the priority for the satellite on each of the host. The host with the lower priority is preferred as the active host. The default priority is 128.

Step 5

nv satellite system-mac <mac_address>

 

RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)# nv satellite system-mac dcddc.dcdc.dcdc

(Optional) Specifies the MAC address. Two hosts in the same redundancy group will sync up the system MAC address and satellite priority information. The System MAC must be the same. If it is different, then the Host with low chassis MAC gets priority. If the system MAC is not configured, then it uses low host chassis MAC as the system MAC.

Step 6

interface interface-name

 

 

 

RP/0/RSP0/CPU0:router(config)# interface TenGigE0/2/1/0

The supported inter-chassis link interface types are limited by the connectivity provided on the supported satellites. GigabitEthernet, TenGigE, and Bundle-Ether interfaces are the supported ICL types.

Step 7

ipv4 point-to-point

 

 

 

RP/0/RSP0/CPU0:router(config-if)# ipv4 point-to-point

(Optional) Configures the IPv4 point to point address.

Step 8

ipv4 unnumbered loopback0

 

 

 

RP/0/RSP0/CPU0:router(config-if)# interface unnumbered loopback0

(Optional) Configures the IPv4 loopback address on the interface.

Step 9

nV

 

RP/0/RSP0/CPU0:router(config-if)# nV

Enters the nV satellite mode.

Step 10

satellite-fabric-link network

 

 

 

RP/0/RSP0/CPU0:router(config-if-nV)# satellite-fabric-link network

Specifies the network type of ICPE inter-chassis link.

Step 11

redundancy iccp-group

 

 

 

RP/0/RSP0/CPU0:router(config-sfl-network)# redundancy iccp-group 2

Configures the ICCP redundancy group.

Step 12

satellite <satellite id>

 

 

 

RP/0/RSP0/CPU0:router(config-sfl-network)# satellite 500

Specifies the satellite ID of the satellite.

Step 13

remote-ports interface-type

 

RP/0/RSP0/CPU0:router(config-sfl-network)# remote-ports GigabitEthernet 0/0/9,5

 

Configures the remote satellite ports for the satellite 500.

Step 14

satellite <satellite id>

 

 

 

RP/0/RSP0/CPU0:router(config-sfl-network)# satellite 600

Specifies the satellite ID of the connected satellite in the simple ring.

Step 15

remote-ports interface-type

 

RP/0/RSP0/CPU0:router(config-sfl-network)# remote-ports GigabitEthernet 0/0/9,5

 

Configures the remote satellite ports for the satellite 600.

Step 16

end

or

commit

 

RP/0/RSP0/CPU0:router(configsfl-network)# end

or

RP/0/RSP0/CPU0:router(configsfl-network)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Auto-IP

The Auto IP feature improves the plug-and-play set up of an nV satellite system. With the Auto IP feature, IP connectivity to the satellite is automatically provisioned. As a result:

  • The nV Satellite Loopback interface is created on the host
  • Loopback interface is given an IP address from a private satellite VRF
  • Satellite fabric links are unnumbered to the loopback interface
  • The IP address assigned to satellite is auto-generated from the satellite VRF

In the case of Auto IP, you need not specify any IP addresses (including the IP address on the Satellite itself, under the satellite submode), and the nV Satellite infrastructure assigns suitable IP addresses, which are taken from the 10.0.0.0/8 range within a private VRF to both the satellites and the satellite fabric links. All such Auto IP allocated satellites are in the same VRF, and you must manually configure IP addresses, if separate VRFs are required.


Note You cannot combine auto-configured Satellites with manually configured Satellites within the same satellite fabric.


The auto-IP feature assigns an IP address in the format 10.x.y.1 automatically, where:

  • x is the top (most significant) 8 bits of the satellite ID
  • y is the bottom 8 bits (the rest) of the satellite ID

Note You can also override the Auto IP feature by using the standard IP configuration.


For examples on configuration using the Auto-IP feature, see Configuration Examples for Satellite nV System.

Configuring the Satellite nV Access Interfaces

The access Gigabit Ethernet interfaces on the satellite are represented locally in Cisco IOS XR Software using interfaces named Gigabit Ethernet similar to other non-satellite Gigabit Ethernet interfaces. The only difference is that the rack ID used for a satellite access Gigabit Ethernet interface is the configured satellite ID for that satellite.

These interfaces support all features that are normally configurable on Gigabit Ethernet interfaces (when running over a physical ICL), or Bundle-Ether interfaces (when running over a virtual ICL).


Note With respect to the dual home topology, the satellite access port configuration needs to be done on both the active and standby hosts. The administrator needs to make sure that the same configuration is applied for a particular access port on both the active and standby hosts. In addition, any feature configurations on satellite-access ports needs to be configured identically on both the hosts. Also, the configuration synchronization between the hosts is not currently supported. See Satellite Interface Configuration.


Configuring the Fabric CFM

This procedure gives you the steps to configure CFM on a Satellite nV Fabric link interface. This is mandatory in the case of Layer 2 Fabric Network architecture.

SUMMARY STEPS

1. configure

2. interface interface_name

3. nv

4. satellite-fabric-link { satellite <id> | network }

5. ethernet cfm

6. level

7. continuity-check interval time

8. end
or
commit

DETAILED STEPS

Command or Action
Purpose

Step 1

configure

 

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2

interface interface_name

 

 

 

RP/0/RSP0/CPU0:router(config)# interface Gigabit 0/1/0/0

Specifies the supported inter-chassis link interface types limited by the connectivity provided on the supported satellites.

Step 3

nv

 

RP/0/RSP0/CPU0:router(config-int)# nv

Enters the Network Virtualization configuration mode.

Step 4

satellite-fabric-link satellite <id>

 

RP/0/RSP0/CPU0:router(config-int-nv)# satellite-fabric-link satelite 200

Specifies that the interface is an ICPE inter-chassis link.

Step 5

ethernet cfm

 

RP/0/RSP0/CPU0:router(config-int-nv)# ethernet cfm

Enters Ethernet Connectivity Fault Management (CFM) configuration mode.

Step 6

level

 

RP/0/RSP0/CPU0:router(config-int-nv-cfm)# level

Specifies the CFM level. It ranges from 0 to 7.

Step 7

continuity-check interval time

 
RP/0/RSP0/CPU0:router(config-int-nv-cfm)# continuity-check interval 100m

(Optional) Enables Continuity Check and specifies the time interval at which CCMs are transmitted.

Step 8

end

or

commit

 

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Plug and Play Satellite nV Switch Turn up: (Rack, Plug, and Go installation)

1. Unpack the satellite rack, stack, and connect to the power cord.

2. Plug in the qualified optics of correct type into any one or more of the SFP+ slots and appropriate qualified optics into SFP+ or XFP slots on the host. Connect through the SMF/MMF fiber.


Note Connect the 10GigE fibers from the host to any of the 10G SFP+ ports on the satellite device in any order.



Note The Satellite nV service can use Cisco ASR 9000 Series Router or Cisco ASR 9001 and Cisco ASR 9922 Series Routers as hosts. The Cisco ASR 9000v, Cisco ASR 901, or Cisco ASR 903 Routers can be used as satellite devices.


3. Configure the satellite nV system through CLI or XML on the host 10GigE ports. Configure the host for nV operations as described in the sections Defining the Satellite nV System, Configuring the Host IP Address, and Configuring the Inter-Chassis Links and IP Connectivity.

4. Power up the chassis of the satellite device.


Note For power supply considerations of ASR 9000v, ASR 901, and ASR 903, refer to the Appendix C, Cisco ASR 9000 and Cisco CRS Satellite Systems (ASR 9000v, ASR 903, ASR 901) of the Cisco ASR 9000 Series Aggregation Services Router Hardware Installation Guide online.


5. You can check the status of the satellite chassis based on these chassis error LEDs on the front face plate.

If the Critical Error LED turns ON, then it indicates a serious hardware failure.

If the Major Error LED turns ON, then it indicates that the hardware is functioning well but unable to connect to the host.

If the Critical and Major LEDs are OFF, then the satellite device is up and running and connected to the host.

You can do satellite ethernet port packet loopback tests through the host, if needed, to check end to end data path.


Note When the satellite software requires an upgrade, it notifies the host. You can do an inband software upgrade from the host, if needed. Use the show nv satellite status on the host to check the status of the satellite.



Note For the satellite image upgrade to work, you must ensure that the management-plane CLI is not configured on the Cisco ASR 9000 Series Router. If it is configured, then you need to add this exception for each of the 10GigE interfaces, which are the satellite ICLs.


Upgrading and Managing Satellite nV Software

Satellite software images are bundled inside a PIE and the PIE name is dependent on the type of satellite, such as asr9k-9000v-nV-px.pie, asr9k-asr901-nV-px.pie , asr9k-asr903-nV-px.pie within the
Cisco ASR 9000 Series Router package. The Cisco IOS XR software production SMU tool can be used to generate patches for the satellite image in the field to deliver bug fixes or minor enhancements without requiring a formal software upgrade.

Image Upgrade for Cisco ASR 9000v Satellite

The asr9k-asr9000v-nV-px.pie contains two sets of binaries, namely, the intermediate binaries and the final binaries. When a Satellite nV system running Cisco IOS XR Software prior to
Cisco IOS XR Software Release 5.1.1 is upgraded to Cisco IOS XR Release 5.1.1, the satellite downloads the intermediate binaries and reloads as per the instructions of the operator. These intermediate binaries include the logic to request the file name from the host rather than hard coding the file name. Also, they automatically trigger the second download (final binaries) without requiring manual intervention.


Note The show nv satellite status command does not display the intermediate version. However, it displays the final Cisco IOS XR Software Release 5.1.1 and prompts for any further upgrade. But, internally two reloads happen. On the other hand, when you upgrade from Cisco IOS XR Release 5.1.x to future releases, two reloads do not occur and also during downgrade the system does not downgrade two releases.



Note An auto transfer internal message comes up when the second software reload happens, which requires no explicit user-intervention.



Note For upgrading from a release prior to Cisco IOS XR Software Release 5.1.1, the Satellite nV System must be connected in the Hub and Spoke topology as the previous releases do not support the advanced Satellite system topologies such as dual head, simple ring, or Layer 2 Fabric network topologies.


This section provides the commands to manage the satellite nV Software.

Prerequisites

You must have installed the satellite installation procedure using the Plug and Play Satellite installation procedure. For more information, see Plug and Play Satellite nV Switch Turn up: (Rack, Plug, and Go installation).

Installing a Satellite

To download and activate the software image on the satellite, use the install nv satellite satellite ID / all transfer/activate commands . The transfer command downloads the image to the satellite. When the transfer command is followed by the activate command, the software is activated on the satellite.


Note In the case of simple ring topology, the image must be transferred to all the satellites using install nv satellite transfer <range of satellites> command followed by install nv satellite activate <range of satellites> command. You cannot use only the install nv satellite activate command in the case of simple ring topology.



Note On a simple ring topology, you can have two hosts running different versions of Cisco IOS XR Software during the image upgrade phase.


Example

RP/0/RSP0/CPU0:sat-host# install nv satellite 100 transfer
 
Install operation initiated successfully.
RP/0/RSP0/CPU0:sat-host#RP/0/RSP0/CPU0:May 3 20:12:46.732 : icpe_gco[1146]: %PKT_INFRA-ICPE_GCO-6-TRANSFER_DONE : Image transfer completed on Satellite 100
 
RP/0/RSP0/CPU0:sat-host# install nv satellite 100 activate
 
Install operation initiated successfully.
LC/0/2/CPU0:May 3 20:13:50.363 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet100/0/0/28, changed state to Down
RP/0/RSP0/CPU0:May 3 20:13:50.811 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: Node 100 removed
 

Note If the activate command is run directly, then the software image is transferred to the satellite and also activated.


Example

RP/0/RSP0/CPU0:sat-host# install nv satellite 101 activate
 
Install operation initiated successfully.
 
RP/0/RSP0/CPU0:sat-host#RP/0/RSP0/CPU0:May 3 20:06:33.276 : icpe_gco[1146]: %PKT_INFRA-ICPE_GCO-6-TRANSFER_DONE : Image transfer completed on Satellite 101
RP/0/RSP0/CPU0:May 3 20:06:33.449 : icpe_gco[1146]: %PKT_INFRA-ICPE_GCO-6-INSTALL_DONE : Image install completed on Satellite 101
RP/0/RSP0/CPU0:May 3 20:06:33.510 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: Node 101 removed

 


Note For the satellite image upgrade to work, you must ensure that the management-plane CLI is not configured on the Cisco ASR 9000 Series Router. If it is configured, then you need to add this exception for each of the 10GigE interfaces, which are the satellite ICLs.


Ensure that the tftp homedir, tftp vrf default ipv4 server homedir disk0 is not configured on the host when using manual IP default configuration, because this may cause the image transfer to fail.

You can include the exception using this CLI:

control-plane
management-plane
inband
!
!
interface TenGigE0/0/0/5 <=== To enable TFTP on nV satellite ICL
allow TFTP

 

If you do not include this exception, then the image download and upgrade fails.

Converting a Standard Cisco ASR 901 to Satellite

In order to convert a standard Cisco ASR 901 Router to Satellite, see Network Virtualization Using Cisco ASR 901 Series Aggregation Services Router as a Satellite.

Converting a Standard Cisco ASR 903 to Satellite

In order to convert a standard Cisco ASR 903 Router to a Satellite, see Enabling Network Virtualization Satellite Mode on the Cisco ASR 903 Router .

In order to upgrade the Cisco ASR 903 Router to the latest Satellite nV image from Cisco ASR 9000 Series Router, carry out these steps:


Note These steps are applicable only in Cisco IOS XR Software Release 4.3.x. Future releases will follow the standard nV upgrade procedure.


1. Install the 903 satellite PIE on the Cisco ASR 9000 Series Router.

2. Install the 903 satellite SMU, if any, on the Cisco ASR 9000 Series Router.

3. Configure a sufficiently-long session timeout value on the Cisco ASR 9000 Series Router to ensure that the session does not time out while the satellite image is copied to the satellite.

RP/0/RSP0/CPU0:router(config)# line default
RP/0/RSP0/CPU0:router(config-line)# session-timeout 120
 

4. Log in to the satellite using the procedure described in the Defining the Satellite nV System section.

RP/0/RSP0/CPU0:router# Telnet 66.66.66.60
 

a. If there is no secret configured on the host for satellite, you can telnet to the satellite.

b. If there is a secret configured on the host for satellite, you must telnet to the satellite and login using username "root" and password as configured in the Implementing a Satellite nV System section.

5. After you log in to the satellite, download the 903 nv binary to the Cisco ASR 903 Router. Use TFTP IP address as the address of the host loopback address.

Example :

LC:Satellite# copy tftp bootflash:
 
Address or name of remote host []? 66.66.66.61
Source filename []? /rp_super_universalk9_npe.rudy.bin
Destination filename [rp_super_universalk9_npe.rudy.bin]?
Accessing t ftp://66.66.66.61//rp_super_universalk9_npe.rudy.bin...
Loading rp_super_universalk9_npe.rudy.bin .from 66.66.66.61 (via BDI100): !!!!!!!!!!!!!!!!!!!!

Note Ensure to put the "/" (slash) before image name - /rp_super_universalk9_npe.rudy.bin.


6. Exit from the telnet session to the satellite.

7. Reload the satellite using the command hw-module satellite sat id reload .

Monitoring the Satellite Software

  • To perform a basic status check, use the show nv satellite status brief command.
RP/0/RSP0/CPU0:router# show nv satellite status brief
 
Sat-ID Type IP Address MAC address State
------ -------- ------------ -------------- --------------------------------
100 asr9000v 101.102.103.105 dc7b.9426.1594 Connected (Stable)
200 asr9000v 101.102.103.106 0000.0000.0000 Halted; Conflict: no links configured
400 194.168.9.9 0000.0000.0000 Halted; Conflict: satellite has no type configured
 
  • To check if an upgrade is required on satellite, run the show nv satellite status satellite satellite_id .

Example

RP/0/RSP0/CPU0:router# show nv satellite status satellite 100
 
Satellite 100
-------------
State: Connected (Stable)
Type: asr9000v
Description: sat-test
MAC address: dc7b.9427.47e4
IPv4 address: 100.1.1.1
Configured Serial Number: CAT1521B1BB
Received Serial Number: CAT1521B1BB
Remote version: Compatible (latest version)
ROMMON: 125.0 (Latest)
FPGA: 1.13 (Latest)
IOS: 200.8 (Latest)
Configured satellite fabric links:
TenGigE0/2/0/6
--------------
State: Satellite Ready
Port range: GigabitEthernet0/0/0-9
TenGigE0/2/0/13
---------------
State: Satellite Ready
Port range: GigabitEthernet0/0/30-39
TenGigE0/2/0/9
--------------
State: Satellite Ready
Port range: GigabitEthernet0/0/10-19

Example

This example shows the ouput of show nv satellite status command for a Satellite configured in dual home network topology.

RP/0/RSP0/CPU0:router# show nv satellite status
 
Satellite 100
-------------
Status: Connected (Stable)
Redundancy: Active (Group: 10)
Type: asr9000v
Description: sat100
MAC address: 4055.3958.61e4
IPv4 address: 100.100.1.2 (VRF: default)
Serial Number: CAT1604B1AN
Remote version: Compatible (not latest version)
ROMMON: 126.0 (Latest)
FPGA: 1.13 (Latest)
IOS: 322.5 (Available: 322.3)
Configured satellite fabric links:
TenGigE0/1/0/0
--------------
Status: Satellite Ready
Remote ports: GigabitEthernet0/0/30-43
 
TenGigE0/1/0/1
--------------
Status: Satellite Ready
Remote ports: GigabitEthernet0/0/0-29
 
 
 

Note In this example output, Remote version, ROMMON, FPGA, and IOS must show the latest version. If it does not, an upgrade is required on the satellite. The version numbers displayed are the installed version on the ASR 90000v. If a version number is displayed, instead of latest key word in the above output, that would correspond to the ASR9000v image bundles in the satellite pie.


Show Commands for Advanced Network Topologies

Dual Home Network Topology

RP/0/RSP1/CPU0:Router# show iccp group 10
 
Redundancy Group 10
member ip:1.1.1.1 (vkg1), up (connected)
monitor: route-watch (up)
No backbone interfaces.
enabled applications: SatelliteORBIT
isolation recovery delay timer: 30 s, not running
 
RP/0/RSP1/CPU0:Router#show nv satellite protocol redundancy
 
ICCP Group: 10
--------------
Status: Connected since 2014/01/22 15:47:35.845
Role: Primary (System MAC: 0000.0001.1234)
Channels:
Control (0)
-----------
Channel status: Open
Messages sent: 8 (4 control), received: 6 (3 control).
 
Topology (14)
-------------
Channel status: Open
Messages sent: 4 (3 control), received: 11 (0 control).
 
 
 
 
 
 
 
## active host:
 
RP/0/RSP1/CPU0:Router# show nv satellite status satellite 200
Satellite 200
-------------
Status: Connected (Stable)
Redundancy: Active (Group: 10)
Type: asr9000v
MAC address: 8478.ac01.d2d8
IPv4 address: 192.1.1.200 (VRF: default)
Serial Number: CAT1708U0LV
Remote version: Compatible (latest version)
ROMMON: 126.0 (Latest)
FPGA: 1.13 (Latest)
IOS: 322.6 (Latest)
Configured satellite fabric links:
TenGigE0/0/0/1
--------------
Status: Satellite Ready
Remote ports: GigabitEthernet0/0/0-10
 
 
 
##Standby host:
 
 
RP/0/RSP1/CPU0:Router# show nv satellite status satellite 200
 
Satellite 200
-------------
Status: Connected (Stable)
Redundancy: Standby (Group: 10)
Type: asr9000v
MAC address: 8478.ac01.d2d8
IPv4 address: 192.1.1.200 (VRF: default)
Serial Number: CAT1708U0LV
Remote version: Compatible (latest version)
ROMMON: 126.0 (Latest)
FPGA: 1.13 (Latest)
IOS: 322.6 (Latest)
Configured satellite fabric links:
TenGigE0/3/0/6
--------------
Status: Satellite Ready
Remote ports: GigabitEthernet0/0/0-10
 

Simple Ring Topology

RP/0/RSP1/CPU0:Router# show nv satellite topology interface tenGigE 0/3/0/6
 
TenGigE0/3/0/6
--------------
Redundancy-Group: 10
Discovery status: Running
Satellites:
Satellite 100 (BVID 2002)
-------------------------
Received Serial Number: CAT1547B30S
MAC address: 4055.3957.5f50
Satellite fabric links:
TenGE/0/0/0 (Remote ID: 0x1):
Host (TenGigE0/3/0/6)
TenGE/0/0/3 (Remote ID: 0x4):
Sat 200 (TenGE/0/0/3 (Remote ID: 0x4))
 
Satellite 200 (BVID 2003)
-------------------------
Received Serial Number: CAT1708U0LV
MAC address: 8478.ac01.d2d8
Satellite fabric links:
TenGE/0/0/3 (Remote ID: 0x4):
Sat 100 (TenGE/0/0/3 (Remote ID: 0x4))
TenGE/0/0/0 (Remote ID: 0x1):
Remote port not yet identified
 

Monitoring the Satellite Protocol Status

  • To check the status of the satellite discovery protocol, use the show nv satellite protocol discovery command.
RP/0/RSP0/CPU0:router# show nv satellite protocol discovery brief
 
Interface Sat-ID Status Discovered links
-------------- ------ ------------------------------ -----------------------
Te0/1/0/0 100 Satellite Ready Te0/1/0/0
Te0/1/0/1 100 Satellite Ready Te0/1/0/1
 

(Or)

RP/0/RSP0/CPU0:router# show nv satellite protocol discovery interface TenGigE 0/1/0/0
 
Satellite ID: 100
Status: Satellite Ready
Remote ports: GigabitEthernet0/0/0-15
Host IPv4 Address: 101.102.103.104
Satellite IPv4 Address: 101.102.103.105
Vendor: cisco, ASR9000v-DC-E
Remote ID: 2
Remote MAC address: dc7b.9426.15c2
Chassis MAC address: dc7b.9426.1594

 

  • To check the status of the satellite control protocol status, use the show nv satellite protocol control command.
RP/0/RSP0/CPU0:router# show nv satellite protocol control brief
 
Sat-ID IP Address Protocol state Channels
------ ------------ -------------- -----------------------------------
101.102.103.105 Connected Ctrl, If-Ext L1, If-Ext L2, X-link, Soft Reset, Inventory, EnvMon, Alarm
 
 
RP/0/RSP0/CPU0:shanghai# sh nv satellite protocol control
Satellite 100
-------------
IP address: 101.102.103.105
Status: Connected
Channels:
Control
-------
Channel status: Open
Messages sent: 24 (24 control), received: 23 (23 control).
Interface Extension Layer 1
---------------------------
Channel status: Open
Messages sent: 7 (3 control), received: 14 (2 control).
Interface Extension Layer 2
---------------------------
Channel status: Open
Messages sent: 11 (3 control), received: 10 (2 control).
Interface Extension Cross-link
------------------------------
Channel status: Open
Messages sent: 4 (3 control), received: 3 (2 control).
….
 
  • To check the status of satellite protocol redundancy, use the show nv satellite protocol redundancy command.
RP/0/RSP0/CPU0:router# show nv satellite protocol redundancy
 
ICCP Group: 10
--------------
Status: Connected since 2014/01/11 08:44:58.764
Role: Secondary (System MAC: 6c9c.ed23.c4e6)
Channels:
Control (0)
-----------
Channel status: Open
Messages sent: 18 (9 control), received: 24 (12 control).
 
Topology (14)
-------------
Channel status: Open
Messages sent: 88 (10 control), received: 60 (0 control).
 

 

Monitoring the Satellite Inventory

You can use the show inventory chassis , show inventory fans, show environment temperatures commands in the admin configuration mode to monitor the status of satellite inventory.

RP/0/RSP0/CPU0:router(admin)# show inventory chassis
 
NAME: "module 0/RSP0/CPU0", DESCR: "ASR9K Fabric, Controller, 4G memory"
PID: A9K-RSP-4G, VID: V02, SN: FOC143781GJ
...
NAME: "fantray SAT100/FT0/SP", DESCR: "ASR9000v"
PID: ASR-9000v-FTA, VID: V00 , SN: CAT1507B228
 
NAME: "module SAT100/0/CPU0", DESCR: "ASR-9000v GE-SFP Line Card"
PID: ASR-9000v, VID: N/A, SN:
NAME: "module mau GigabitEthernet100/0/CPU0/8", DESCR: "CISCO-AVAGO "
PID: SFP-GE-S, VID: V01, SN: AGM1424P08N
 
NAME: "module mau TenGigE100/0/CPU0/3", DESCR: "CISCO-FINISAR "
PID: SFP-10G-SR, VID: V02, SN: FNS144502Y3
 
NAME: "power-module SAT100/PM0/SP", DESCR: "ASR-9000v Power Module"
PID: ASR-9000v, VID: N/A, SN:
NAME: "Satellite Chassis ASR-9000v ID 100", DESCR: "ASR9000v"
PID: ASR-9000v-AC-A, VID: V00 , SN: CAT12345678
 
 
 
RP/0/RSP0/CPU0:router(admin)# show inventory fans
 
NAME: "fantray 0/FT0/SP", DESCR: "ASR-9006 Fan Tray"
PID: ASR-9006-FAN, VID: V02, SN: FOX1519XHU8
 
NAME: "fantray 0/FT1/SP", DESCR: "ASR-9006 Fan Tray"
PID: ASR-9006-FAN, VID: V02, SN: FOX1519XHTM
 
NAME: "fantray SAT100/FT0/SP", DESCR: "ASR9000v"
PID: ASR-9000v-FTA, VID: V01 , SN: CAT1531B4TC
 
NAME: "fantray SAT101/FT0/SP", DESCR: "ASR9000v"
PID: ASR-9000v-FTA, VID: V01 , SN: CAT1542B0LJ
 
NAME: "fantray SAT102/FT0/SP", DESCR: "ASR9000v"
PID: ASR-9000v-FTA, VID: V01 , SN: CAT1531B4T7
 
 
RP/0/RSP0/CPU0:sat-host(admin)# show inventory | b GigabitEthernet100/
 
NAME: "module mau GigabitEthernet100/0/CPU0/0", DESCR: "CISCO-FINISAR "
PID: SFP-GE-S, VID: , SN: FNS11350L5E
 
NAME: "module mau GigabitEthernet100/0/CPU0/1", DESCR: "CISCO-FINISAR "
PID: SFP-GE-S, VID: V01, SN: FNS0934M290
 
NAME: "module mau GigabitEthernet100/0/CPU0/2", DESCR: "CISCO-FINISAR "
PID: SFP-GE-S, VID: , SN: FNS12280L59
 
 
RP/0/RSP0/CPU0:router(admin)# show environment temperatures
 
R/S/I Modules Sensor (deg C)
0/RSP0/*
host Inlet0 33.1
host Hotspot0 46.9
0/RSP1/*
host Inlet0 32.1
host Hotspot0 45.9
0/0/*
host Inlet0 37.3
host Hotspot0 52.3
0/1/*
spa0 InletTemp 34.0
spa0 Hotspot 34.5
spa1 LocalTemp 38.0
spa1 Chan1Temp 36.0
spa1 Chan2Temp 39.0
spa1 Chan3Temp 39.0
spa1 Chan4Temp 48.0
host Inlet0 36.1
host Hotspot0 64.0
0/2/*
host Inlet0 39.2
host Hotspot0 54.6
0/3/*
host Inlet0 41.3
host Hotspot0 48.5
0/FT0/*
host Inlet0 42.3
host Hotspot0 36.1
0/FT1/*
host Inlet0 40.4
host Hotspot0 35.8
SAT100/FT0/*
host Hotspot0 53.0
 
SAT101/FT0/*
host Hotspot0 56.0
 
SAT102/FT0/*
host Hotspot0 53.0

Reloading the Satellite Device

In order to reload the satellite device, use the hw-module satellite satellite id/all reload command.

Example

RP/0/RSP0/CPU0:router# hw-module satellite 101 reload
 
Reload operation completed successfully.
RP/0/RSP0/CPU0:May 3 20:26:51.883 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: Node 101 removed
 

Port Level Parameters Configured on a Satellite

These are the port-level parameters that can be configured on a satellite nV system:

  • Admin state (shut and no shut)
  • Ethernet MTU
  • Ethernet MAC Address.
  • Ethernet link auto-negotiation that includes,

Half and full duplex

Link speed

Flow control

  • Static configuration of auto-negotiation parameters such as speed, duplex, and flow control
  • Carrier delay
  • Layer-1 packet loopback which includes,

Line loopback

Internal loopback

  • All satellite access port features on Cisco ASR 9000 Series Router.

Loopback Types on Satellite Ports

There are two types of loopback interfaces that can be configured on satellite ports. They are,

  • Line Loopback
  • Internal Loopback

These illustrations show how the loopback interface types function on a satellite.

Figure 43 Line Loopback

Figure 44 Internal Loopback

You can specify the type of loopback to be used, as specified in this example:

Interface GigabitEthernet 100/0/0/0
loopback line | internal

Configuration Examples for Satellite nV System

This section contains these examples:

Satellite Global Configuration

ICL (satellite-fabric-link) Interface Configuration

Satellite Interface Configuration

Satellite Management using private VRF

Satellite System Configuration: Example

This example shows a sample configuration for setting up the connectivity of a Satellite System.

Satellite Global Configuration

The satellite ID, type, serial number, description, and satellite IP address are configured in the satellite global configuration submode:

nv
satellite 100
type asr9000v
serial-number CAT1521B1BB
description milpitas bldg20
ipv4 address 10.0.0.100
!
!

ICL (satellite-fabric-link) Interface Configuration

On the interface connected to the satellite (TenGig or Bundle interface), the ports associated with the satellite ID must be specified. All fabric links connected to the same satellite must use the same (host) IPv4 address. The same or different host IPv4 addresses can be used for the same host to connect to different satellites.

interface Loopback1000
vrf <vrf_name>
ipv4 address 10.0.0.1 255.0.0.0
vrf <vrf_name>
interface TenGigE0/2/1/0
description To Sat5 1/46
ipv4 point-to-point
ipv4 unnumbered Loopback1000
nv
satellite-fabric-link satellite 200
remote-ports GigabitEthernet 0/0/0-30
!
!
!

Note These examples illustrate using IP addresses from the global VRF of the router for satellite management traffic. As discussed Satellite Discovery and Control Protocol IP Connectivity section, this can also be done using a private VRF, to prevent IP address conflict with the global VRF. In this case, the loopback interface and the ICL interfaces in the examples must be assigned to the private VRF dedicated for satellite management traffic.


Satellite Interface Configuration

The Satellite interface can be used as any other regular Gigabit Ethernet interfaces:

interface GigabitEthernet200/0/0/0
l2transport
!
!
 
interface GigabitEthernet200/0/0/0
ip address 99.0.0.1 255.255.255.0
!
!
 
interface GigabitEthernet200/0/0/2
bundle id 100 mode active
!
!

This is a sample satellite interface configuration in the case of a dual home topology on the active and standby hosts:

Active host:

interface GigabitEthernet100/0/0/32
ipv4 address 1.1.1.1 255.255.255.0
!
 

Standby host:

interface GigabitEthernet100/0/0/32
ipv4 address 1.1.1.1 255.255.255.0
!
 

For an L3 interface, the IPv4 protocol states in the output of show ipv4 interface brief command show as up; up on the active host and up; down on the standby host.

Active host:
 
GigabitEthernet100/0/0/32 1.1.1.1 Up Up
Standby host:
 
GigabitEthernet100/0/0/32 1.1.1.1 Up Down
 

For an L2 interface, the ports show as up on both the hosts.

Active host:
 
GigabitEthernet100/0/0/33 unassigned Up Up
Standby host:
 
GigabitEthernet100/0/0/33 unassigned Up Up
 

Satellite Management using private VRF

You can use a special private VRF instead of the global default routing table, to configure the loopback interface and ICLs used for satellite management traffic. IP addresses in this VRF will not conflict with any other addresses used on the router.

router(config)# vrf NV_MGMT_VRF
router(config)# address ipv4 unicast
 
router(config)# interface Loopback 1000
router(config)# vrf NV_MGMT_VRF
router(config)# ipv4 address 10.0.0.1 / 24
 
router(config)# interface TenGige 0/1/0/3
router(config)# vrf NV_MGMT_VRF
router(config)# ipv4 point-to-point
router(config)# ipv4 unnumbered Loopback 1000
router(config)# nv
router(config-nv)# satellite-fabric-link satellite 500
router(config-nv)# remote-ports GigabitEthernet 0/0/28-39
router(config)# nv satellite 500
router(config)# ipv4 address 10.0.0.2 / 24

Configuration of Satellite using Auto-IP

show run nv satellite 1200
nv
satellite 1200
type asr901
!
interface GigabitEthernet0/1/0/5
transceiver permit pid all
nv
satellite-fabric-link satellite 1200
remote-ports GigabitEthernet 0/0/0-7
!
!
!

Satellite Configuration with Dual-homed Hosts

You can configure satellite with dual-homed hosts as shown in this example.

redundancy
iccp group <group-id>
nv satellite
system mac <macaddr>
!
Interface TenGigE0/1/0/0
nv
satellite-fabric-link {network | satellite <id>}
host-redundancy
iccp-group <group-id>
!
nv
satellite <id>
host-redundancy
host-priority <0-255>

Dual-Home for multiple satellites with Single physical ICLs on both Hosts and Satellites

Dual Home configuration for SAT1:


Note When you use either a manual IP address or an IPv4 unnumbered loopback address for the ICL, the IP address must be different on both the hosts.


Host1:
 
interface TenGigE0/1/1/23.100
ipv4 point-to-point
ipv4 address 100.100.1.101 255.255.255.0
encapsulation dot1q 100
nv
satellite-fabric-link satellite 100
redundancy
iccp-group 1
!
remote-ports GigabitEthernet 0/0/0-35
!
!
!
 
Host2:
 
interface TenGigE0/1/1/2.100
ipv4 point-to-point
ipv4 address 100.100.1.102 255.255.255.0
encapsulation dot1q 120
nv
satellite-fabric-link satellite 100
redundancy
iccp-group 1
!
remote-ports GigabitEthernet 0/0/0-35

Dual Home configuration for SAT2:

Host1:
 
interface TenGigE0/1/1/23.200
ipv4 point-to-point
ipv4 address 100.100.1.101 255.255.255.0
encapsulation dot1ad 100
nv
satellite-fabric-link satellite 200
redundancy
iccp-group 1
!
remote-ports GigabitEthernet 0/0/0-35
!
!
!
 
 
Host2:
 
interface TenGigE0/1/1/2.200
ipv4 point-to-point
ipv4 address 100.100.1.102 255.255.255.0
encapsulation dot1ad 120
nv
satellite-fabric-link satellite 200
redundancy
iccp-group 1
!
remote-ports GigabitEthernet 0/0/0-35
!
 

Configuring a Satellite nV System in Simple Ring Topology

On HOST1

redundancy
iccp
group 2
member
neighbor 9.9.9.9
!
nv satellite
system-mac dcdc.dcdc.dcdc
!
!
!
nv
satellite 500
type asr901
ipv4 address 100.100.1.2
description sat500
redundancy
host-priority 30
!
serial-number CAT1603U04Q
!
satellite 600
type asr901
ipv4 address 100.100.1.3
description sat600
redundancy
host-priority 30
!
serial-number CAT1603U035
!
satellite 700
type asr901
ipv4 address 100.100.1.4
description sat700
redundancy
host-priority 30
!
serial-number CAT1710U03C
!
satellite 800
type asr901
ipv4 address 100.100.1.5
description sat800
redundancy
host-priority 30
!
serial-number CAT1651U09N
!
!
 
 
RP/0/RSP0/CPU0:HOST1# show runn | b mpls ldp
 
mpls ldp
router-id 8.8.8.8
address-family ipv4
neighbor 9.9.9.9 targeted
!
interface GigabitEthernet0/1/0/3
!
!
End
 
RP/0/RSP0/CPU0:HOST1#show runn interface Gi0/1/0/0
 
interface GigabitEthernet0/1/0/0
ipv4 point-to-point
ipv4 unnumbered Loopback10
nv
satellite-fabric-link network
redundancy
iccp-group 2
!
satellite 500
remote-ports GigabitEthernet 0/0/0-9
!
satellite 600
remote-ports GigabitEthernet 0/0/0-9
!
satellite 700
remote-ports GigabitEthernet 0/0/0-9
!
satellite 800
remote-ports GigabitEthernet 0/0/0-9
!
!
!
!
 

On HOST2

nv
satellite 500
type asr901
ipv4 address 100.100.1.2
description sat500
redundancy
host-priority 101
!
serial-number CAT1603U04Q
!
satellite 600
type asr901
ipv4 address 100.100.1.3
description sat600
redundancy
host-priority 101
!
serial-number CAT1603U035
!
satellite 700
type asr901
ipv4 address 100.100.1.4
description sat700
redundancy
host-priority 101
!
serial-number CAT1710U03C
!
satellite 800
type asr901
ipv4 address 100.100.1.5
description sat800
redundancy
host-priority 101
!
serial-number CAT1651U09N
!
!
interface Bundle-Ether10
bundle wait-while 0
load-interval 30
l2transport
!
!
 
RP/0/RSP0/CPU0:HOST2# show runn | b mpls ldp
 
mpls ldp
router-id 9.9.9.9
address-family ipv4
neighbor 8.8.8.8 targeted
!
interface GigabitEthernet0/0/0/2
!
!
End
 
 
RP/0/RSP0/CPU0:HOST2# show runn | b redundancy
 
redundancy
iccp
group 2
member
neighbor 8.8.8.8
!
nv satellite
system-mac dcdc.dcdc.dcdc
!
!
 
 
 
RP/0/RSP0/CPU0:HOST2# show runn interface Gi0/0/0/18
 
interface GigabitEthernet0/0/0/18
ipv4 point-to-point
ipv4 unnumbered Loopback10
nv
satellite-fabric-link network
redundancy
iccp-group 2
!
satellite 500
remote-ports GigabitEthernet 0/0/0-9
!
satellite 600
remote-ports GigabitEthernet 0/0/0-9
!
satellite 700
remote-ports GigabitEthernet 0/0/0-9
!
satellite 800
remote-ports GigabitEthernet 0/0/0-9
!
!
!
!

Configuring a Satellite nV System in Layer 2 Fabric Network Topology

interface TenGigE0/0/0/0.102
ipv4 point-to-point
ipv4 unnumbered Loopback0
load-interval 30
encapsulation dot1q 102
nv
satellite-fabric-link satellite 300
ethernet cfm
continuity-check interval 10ms
!
redundancy
iccp-group 10
!
remote-ports GigabitEthernet 0/0/0-10
 

Additional References

These sections provide references to related documents.

Related Documents

Related Topic
Document Title

Cisco IOS XR master command reference

Cisco IOS XR Master Commands List

Satellite System software upgrade and downgrade on Cisco IOS XR Software

Cisco ASR 9000 Series Aggregation Services Router Getting Started Guide

Cisco IOS XR interface configuration commands

Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Command Reference

Satellite QoS configuration information for the Cisco IOS XR software

Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide

Bidirectional Forwarding Detection features on the satellite system

Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide

Layer-2 and L2VPN features on the satellite system

Cisco ASR 9000 Series Aggregation Services Router L2VPN and Ethernet Services Configuration Guide

Layer-3 and L3VPN features on the satellite system

Cisco ASR 9000 Series Aggregation Services Router MPLS Layer 3 VPN Configuration Guide

Multicast features on the satellite system

Cisco ASR 9000 Series Aggregation Services Router Multicast Configuration Guide

Broadband Network Gateway features on the satellite system

Cisco ASR 9000 Series Aggregation Services Router Broadband Network Gateway Configuration Guide

AAA related information and configuration on the satellite system

Cisco ASR 9000 Series Aggregation Services Router System Security Configuration Guide

Cisco ASR 901 Router configuration

Network Virtualization Using Cisco ASR 901 Series Aggregation Services Router as a Satellite

Cisco ASR 903 Router configuration

Enabling Network Virtualization Satellite Mode on the Cisco ASR 903 Router

Information about user groups and task IDs

Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide

Standards

Standards
Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

MIBs

MIBs
MIBs Link

There are no applicable MIBs for this module.

To locate and download MIBs for selected platforms using
Cisco IOS XR software, use the Cisco MIB Locator found at the following URL:

http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

RFCs

RFCs
Title

None

N.A

Technical Assistance

Description
Link

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/support