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:Router #show version
Cisco IOS XR Software, Version 6.6.25 
Copyright (c) 2013-2019 by Cisco Systems, Inc.

Build Information:
 Built By     : <username>
 Built On     : Wed May 29 07:03:08 PDT 2019
 Built Host   : iox-lnx-028                 
 Workspace    : /auto/srcarchive13/prod/6.6.25/ncs540/ws
 Version      : 6.6.25                                  
 Location     : /opt/cisco/XR/packages/                 

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

RP/0/RP0/CPU0:Router# show install active 
Node 0/RP0/CPU0 [RP]                        
  Boot Partition: xr_lv147                  
  Active Packages: 9                        
        ncs540-xr-6.6.25 version=6.6.25 [Boot image]
        ncs540-mgbl-1.0.0.0-r6625                   
        ncs540-mpls-1.0.0.0-r6625                   
        ncs540-ospf-1.0.0.0-r6625                   
        ncs540-mpls-te-rsvp-1.0.0.0-r6625           
        ncs540-mcast-1.0.0.0-r6625                  
        ncs540-isis-1.0.0.0-r6625                   
        ncs540-li-1.0.0.0-r6625                     
        ncs540-k9sec-1.0.0.0-r6625    

Node 0/0/CPU0 [LC]
  Boot Partition: xr_lcp_lv148
  Active Packages: 9          
        ncs540-xr-6.6.25 version=6.6.25 [Boot image]
        ncs540-mgbl-1.0.0.0-r6625                   
        ncs540-mpls-1.0.0.0-r6625                   
        ncs540-ospf-1.0.0.0-r6625                   
        ncs540-mpls-te-rsvp-1.0.0.0-r6625           
        ncs540-mcast-1.0.0.0-r6625                  
        ncs540-isis-1.0.0.0-r6625                   
        ncs540-li-1.0.0.0-r6625
        ncs540-k9sec-1.0.0.0-r6625

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:Router# show fpd package

=============================== ================================================
                                        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.11    1.11    0.0
                     CPU-IOFPGA(A)              YES     0.03    0.03    0.0
                     MB-IOFPGA(A)               YES     0.18    0.18    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.11    1.11    0.0
                     CPU-IOFPGA(A)              YES     0.03    0.03    0.0
                     MB-IOFPGA(A)               YES     0.18    0.18    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.11    1.11    0.0
                     CPU-IOFPGA(A)              YES     0.03    0.03    0.0
                     MB-IOFPGA(A)               YES     0.18    0.18    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.11    1.11    0.0
                     CPU-IOFPGA(A)              YES     0.03    0.03    0.0
                     MB-IOFPGA(A)               YES     0.18    0.18    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:Router# show hw-module fpd
Wed May 29 17:31:51.715 UTC
                                                               FPD Versions
                                                               =================
Location   Card type        HWver FPD device       ATR Status   Running Programd
------------------------------------------------------------------------------
0/RP0     N540-24Z8Q2C-M    1.0   MB-MIFPGA            CURRENT    0.04    0.04  
0/RP0     N540-24Z8Q2C-M    1.0   Bootloader           CURRENT    1.11    1.11  
0/RP0     N540-24Z8Q2C-M    1.0   CPU-IOFPGA           CURRENT    0.03    0.03  
0/RP0     N540-24Z8Q2C-M    1.0   MB-IOFPGA            CURRENT    0.18    0.18

PCE protocol (PCEP) (RFC5440) is a client-server model running over TCP/IP, where the server (PCE) opens a port and the clients (PCC) initiate connections. After the peers establish a TCP connection, they create a PCE session on top of it.

The ACL Support for PCEP Connection feature provides a way to protect a PCE server using an Access Control List (ACL) to restrict the PCC peers at the time the TCP connection is created based on the source address of client. When a client initiates the TCP connection, the ACL is referenced, and the client source address is compared. The ACL can either permit or deny the address and the TCP connection will proceed or not.

For more information about ACLs, see the Implementing Access Lists and Prefix Lists chapter in the IP Addresses and Services Configuration Guide.

For more information about the ACL Support for PCEP Connection feature, see the Configure Segment Routing Path Computation Element chapter in the .

The number of bridge domains depends on the number of attachment circuits (ACs) per bridge domain and if the Bridge-Group Virtual Interface (BVI) is configured or not. In Release 6.6.25, only 750 BDs are supported.

The Ethernet flow point (EFP) visibility feature enables you to configure multiple VLANs in the same bridge-domain.

The EFP service instance is a logical interface that connects a bridge domain to a physical port or to an EtherChannel group. A VLAN tag identifies the EFP.

Prior to this release, only one EFP is allowed per bridge-domain. With the EFP visibility feature, you can configure a maximum of 600 EFPs per bridge-domain.

For more information refer the chapter Configure Virtual LANs in Layer 2 VPNs in the , Release 6.6.x

The Expilicit Congestion Notification (ECN) feature is an extension to WRED (Weighted Random Early Detection). This feature will mark packets instead of dropping them when the average queue length exceeds a specific threshold value. When configured, ECN helps routers and end hosts to understand that the network is congested and slow down sending packets.

For more information on this feature, see the .

The Flow Label support for EVPN VPWS feature enables provider (P) routers to use a flow-based load balancing to forward traffic between the provider edge (PE) devices. Flow-Aware Transport (FAT) pseudowires (PW) over an MPLS packet switched network is used for load-balancing traffic across BGP-signaled pseudowires for an EVPN virtual private wire service (VPWS).

For more information on this feature, see the EVPN Virtual Private Wire Service (VPWS) chapter in the , IOS XR Release 6.6.x.

Usually, DSCP and precedence-based classifications are supported in QoS traffic only when there is no MPLS label in the packet. Using the ingress short-pipe feature, however, you can classify a packet that contains one MPLS label using the type-of-service (ToS) field of the IPv4 or IPv6 header.

With the ingress short-pipe feature, you get increased visibility into traffic packets. Plus, the feature also removes the limitation of classifying MPLS packets that come into IPv4 or IPv6 networks.

To know more about the selective egress policy-based queue mapping feature, see the . To see the command reference details, see match mpls disposition class-map child_pipe in Modular QoS Command Reference for Cisco NCS 5500 Series and Cisco NCS 540 Series Routers.

Before this release IPv6 multicast support was limited to a single source for each multicast group. However, when multiple sources were involved then it resulted in duplicating multicast flows of multiple sources to all interested receivers.

The LDP-based VPLS and VPWS FAT Pseudowire feature enable provider (P) routers to use a flow-based load balancing to forward traffic between the provider edge (PE) devices. Flow-Aware Transport (FAT) of pseudowires (PW) over an MPLS packet switched network is used for load-balancing traffic across LDP-signaled pseudowires for Virtual Private LAN Services (VPLS) and Virtual PrivateWire Service (VPWS).

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

The LDP over Segment Routing Policy feature enables an LDP-targeted adjacency over Segment Routing (SR) policy between two routers. This feature extends the existing MPLS LDP address family neighbor configuration to specify an SR policy as the targeted end-point.

For more information about the LDP over Segment Routing Policy feature, see the Configure SR-TE Policies chapter in the .

The MAC Address Withdrawal feature provides faster convergence by removing MAC addresses that are dynamically learned. This feature uses Label Distribution Protocol (LDP)-based MAC address withdrawal message. A MAC list Type Length Value (TLV) is part of the MAC address withdrawal message.

This feature also supports optimization of MAC address withdrawal. The optimization allows PEs to retain the MAC addresses that are learned from the CE devices over the access side. Only MAC addresses that are learned from peer PEs are flushed out. This avoids unnecessary MAC flushing toward AC side and ensures better utilization of bandwidth and resources.

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

Earlier, you could associate Segment Routing Label Switched Paths (SR-LSP) with a static route. The Static Route Traffic-Steering using SRTE Policy feature adds support to specify a Segment Routing (SR) policy as an interface type when configuring static routes for MPLS and IPv6 data planes.

For more information about the Static Route Traffic-Steering using SRTE Policy feature, see the Configure SR-TE Policies chapter in the .

The Three-level Hierarchical QoS (H-QoS) feature enables enforcement of class/service, group/ ethernet flow point (EFP), and port level SLAs.

As earlier, you can apply the regular two-level egress H-QoS policies on the sub-interfaces to achieve class and EFP SLAs at child and parent levels. In addition, with this feature, you can apply a port shaper policy on the main interface to achieve an aggregated port level SLA in a 1+2 H-QoS model.

The advantage of three-level H-QoS is that the parent shaper on the sub-interfaces is allowed to oversubscribe, thus enabling best effort sharing of the aggregate port shaper at the third level.

To know more about the three-level Hierarchical QoS feature, its sample configuration, and other information, see the .

The following optics are supported on the Cisco NCS 540 Series router in this release:

• GLC-BX40-D-I

• GLC-BX40-DA-I

• GLC-BX40-U-I

• GLC-BX80-DI

• GLC-BX80-UI

• SFP-10G-BX-D-I

• SFP-10G-BXU-I

• SFP-10G-BX40-DI

• SFP-10G-BX40-UI

• GLC-LX-SM-RGD

• SFP-10/25G-LR-S

• GLC-T-RGD