This table lists the Cisco IOS XR Software feature set matrix (packages) with associated filenames.

To verfiy the software version running on the router, use the show version command in the EXEC mode.

RP/0/RP0/CPU0:R31-NCS540-VIDEO#show version                       
Sat Dec 14 13:14:34.436 IST                                       
Cisco IOS XR Software, Version 6.6.3                              
Copyright (c) 2013-2019 by Cisco Systems, Inc.                    

Build Information:
 Built By     : hlo
 Built On     : Fri Dec 13 16:41:04 PST 2019
 Built Host   : iox-lnx-028                 
 Workspace    : /auto/srcarchive15/prod/6.6.3/ncs540/ws
 Version      : 6.6.3                                  
 Location     : /opt/cisco/XR/packages/                

cisco NCS-540 () processor
System uptime is 18 minutes

Use the show fpd package command in Admin mode to view the hardware components with their current FPD version and status.

RP/0/RP0/CPU0:R31-NCS540-VIDEO#show fpd package 
Sat Dec 14 13:14:38.526 IST                     

=============================== ================================================
                                        Field Programmable Device Package       
                                ================================================
                                               Req     SW      Min Req   Min Req
Card Type            FPD Description           Reload  Ver     SW Ver  Board Ver
=================== ========================== ====== ======= ======== =========
--------------------------------------------------------------------------------
N540-24Z8Q2C-M       Bootloader(A)              YES     1.12    1.12    0.0
                     CPU-IOFPGA(A)              YES     0.03    0.03    0.0
                     MB-IOFPGA(A)               YES     0.20    0.20    0.0
                     MB-MIFPGA                  YES     0.04    0.04    0.0
                     SATA(A)                    NO      5.00    5.00    0.0
--------------------------------------------------------------------------------
N540-ACC-SYS         Bootloader(A)              YES     1.12    1.12    0.0
                     CPU-IOFPGA(A)              YES     0.03    0.03    0.0
                     MB-IOFPGA(A)               YES     0.20    0.20    0.0
                     MB-MIFPGA                  YES     0.04    0.04    0.0
                     SATA(A)                    NO      5.00    5.00    0.0
--------------------------------------------------------------------------------
N540-X-24Z8Q2C-M     Bootloader(A)              YES     1.12    1.12    0.0
                     CPU-IOFPGA(A)              YES     0.03    0.03    0.0
                     MB-IOFPGA(A)               YES     0.20    0.20    0.0
                     MB-MIFPGA                  YES     0.04    0.04    0.0
                     SATA(A)                    NO      5.00    5.00    0.0
--------------------------------------------------------------------------------
N540X-ACC-SYS        Bootloader(A)              YES     1.12    1.12    0.0
                     CPU-IOFPGA(A)              YES     0.03    0.03    0.0
                     MB-IOFPGA(A)               YES     0.20    0.20    0.0
                     MB-MIFPGA                  YES     0.04    0.04    0.0
                     SATA(A)                    NO      5.00    5.00    0.0

Use the show hw-module fpd command in EXEC mode to view the hardware components with their current FPD version and status. The status of the hardware must be CURRENT; Running and Programed version must be the same.

RP/0/RP0/CPU0:R31-NCS540-VIDEO#show hw-module fpd
Sat Dec 14 13:14:43.226 IST
                                                               FPD Versions
                                                               =================
Location   Card type        HWver FPD device       ATR Status   Running Programd
------------------------------------------------------------------------------
0/RP0     N540-ACC-SYS      1.0   MB-MIFPGA            CURRENT    0.04    0.04
0/RP0     N540-ACC-SYS      1.0   Bootloader           CURRENT    1.12    1.12
0/RP0     N540-ACC-SYS      1.0   CPU-IOFPGA           CURRENT    0.03    0.03
0/RP0     N540-ACC-SYS      1.0   MB-IOFPGA            CURRENT    0.20    0.20

The Access Pseudowire feature allows you to reduce the number of pseudowires (PWs) between the network Provider Edge (N-PE) devices. The user Provider Edge (U-PE) device connects to the N- PE device using access pseudowire (PW). This feature prevents signalling overhead and packet replication.

Unlike traditional VPLS where PWs terminate on a physical or logical port, an access PW terminates on N-PE devices. For each VPLS service, create an access PW between U-PEs and N-PEs.

VPLS requires a full mesh of pseudowire (PWs) between L2VPN PEs that participate in the VPLS service. For each VPLS service, PWs must be set up between the PEs. In a full mesh of PWs, the number of PWs increases as the number of PEs increases causing scalability issues. You can decrease the number of PWs with a hierarchy of PEs.

For more information about this feature, see the Configure Multipoint Layer 2 Services chapter in the , IOS XR Release 6.6.x.

DHCPv6 Relay agents relay all packets that are coming from DHCPv6 clients over the access-interfaces towards external DHCPv6 servers to request IP addresses (::/128) through Internet Assigned Numbers Authority (IANA) allocation for the DHCPv6 clients. DHCPv6 Relay agents also receive response packets from the DHCPv6 servers and forward the packets towards DHCPv6 clients over BVI interfaces. DHCPv6 Relay agents act as stateless, by default, for DHCPv6 clients by not maintaining any DHCPv6 binding and respective route entry for the allocated IP addresses. You can enable a DHCPv6 client to get a particular IPv6 address assigned by the DHCPv6 server over a Bridge Virtual Interface (BVI) through IANA address allocation. Thereby, the DHCPv6 relay agent acts as a stateful relay agent and maintains DHCPv6 binding and respective route entry for the allocated IPv6 addresses.

For more information see the chapter, Implementing the Dynamic Host Configuration Protocol in the

The G.8032 Ethernet Ring Protection feature is supported on Layer 2 bundle interfaces. This feature provides protection for Ethernet traffic in a ring topology. This feature prevents loops within the ring at the Ethernet layer by blocking either a predetermined link or a failed link.

For more information about this feature, see the Configure Point-to-Point Layer 2 Services chapter in the , IOS XR Release 6.6.x.

This feature provides information about the IPv4 and IPv6 multicast route statistics. The multicast statistics includes information on the numbers of packets received for a multicast route over an interface in ingress and egress directions.

This feature is already supported in previous releases, however in this release following enhancements are introduced:

• IPv6 multicast route statistics are supported.

• Multicast route statistics for egress direction is supported.

For more information oh how to enable multicast route statistics, see Implementing Multicast chapter in

IP Loop Free Alternative FRR is a mechanism that enables a router to rapidly switch traffic to a pre-computed or a pre-programmed loop-free alternative (LFA) path (Data Plane Convergence), following either an adjacent link and node failure, or an adjacent link or node failure in both IP and LDP networks. The LFA path is used to switch traffic till the router installs the new primary next-hops based upon the changed network topology (Control Plane Convergence).

For more information see the chapter, Implementing Layer-3 Multicast Routing in

The MPLS VPN Support for EIGRP Between PE and CE feature allows service providers to configure the Enhanced Interior Gateway Routing Protocol (EIGRP) between provider edge (PE) and customer edge (CE) devices in a Multiprotocol Label Switching (MPLS) virtual private network (VPN) and offer MPLS VPN services to those customers that require native support for EIGRP. An MPLS VPN consists of a set of sites that are interconnected by an MPLS provider core network. At each customer site, one or more CE devices attach to one or more PE devices.

For more information, see the chapter, Implementing EIGRP in the .

Multicast over access PWs allows multicast traffic flooding with MLDP core and PWs that are terminating at CEs. Therefore, connecting two IGMP domains and extending the MVPN traffic via MPLS network terminating at a Layer 3 (VRF or global) domain or a Layer 2 domain using PW.

Multicast over access PWs helps service providers to scale and reduce the hardware cost.

For more information see the chapter, Implementing Multicast in .

The MLDP Profile 14 is supported when the router is configured as an edge router.

IP based transport network is a cost efficient and convenient alternative to deliver video services combined with the delivery of other IP based services. To deliver IPTV content MLDP Profile 14 (partitioned MDT) is supported when router is configured as an edge router.

For more information see chapter, Implementing Multicast in

With this release, you now have the ability to perform Layer 2 (802.1p) marking on Layer 3 flows in the egress direction. This allows you to re-mark the priority of Ethernet packets on L3VPN traffic.

For more information, see the section QoS Re-marking of Ethernet Packets in Egress Direction in the .

This feature enables rate limiting the multicast and broadcast storms of punted traffic at the interface level. Normally, there's no rate limit on multicast and broadcast punted traffic reaching a node. This causes high CPU utilization. In order to protect the CPU from processing storms of multicast and broadcast punted traffic, it's recommended to configure a limit on the multicast and broadcast punted traffic at the interface level.

For more information see the chapter, Implementing LPTS in .

Secondary IP subnet is supported on BVI to enable redundancy and reduce traffic downtime. Also, this feature will enable you to support two different networks over a single interface.

For more information, see the Integrated Routing and Bridging chapter in the .

For more information, see the section Restrictions in the .