First Published: October 20, 2022

Introduction

This document contains the following information about Cisco Evolved Programmable Network Manager 6.1.1:

Functionality Added in Cisco EPN Manager 6.1.1

This section lists the new features/functionalities delivered in Cisco EPN Manager 6.1.1.

Device Support

  • Advantage (Full) RTM Support for Cisco ASR 9902 Router with IOS-XR 7.4.1

  • Chassis view support for multiport adapter NC57-MPA-12L-S

  • Chassis view support for Cisco ASR 9902 router

  • Chassis view support for flexible consumption port expansion card A9903-8HG-PEC-FC on Cisco ASR 9903 800G

  • Chassis view support for NC55-2KW-DCFW on Cisco NCS-55A1-36H-SE-S

  • Chassis view support for Cisco 8201-24H8FH router

  • Full RTM Support for Cisco 8201-24H8FH

  • Full RTM Support for Cisco NCS-55A1-24Q6H-SS

  • Support for Cisco ASR 902-U router

  • Support for Cisco ASR 903-U router

  • Support for Cisco ASR 1001-HX Router on IOS-XE v16.6.6​

Optical

  • Validation of Cisco NCS 2000 series on SVO 12.3.1 operating system

  • ODU circuits provisioning and discovery with T5 XC mode and Cisco NCS 4000 series devices

  • Support: RMON-DFON-GMM MON end-to-end view of 1+1 ODUK in Cisco EPN Manager with different photonics domain

Discovery and Provisioning of ODU Circuits Between Cisco NCS 2000 Series and Cisco NCS 4000 Series Devices

Cisco EPN Manager supports provisioning of end-to-end ODU circuits between Cisco NCS 2000 series and Cisco NCS 4000 series devices.

ODU circuit provisioning between Cisco NCS 2000 series and Cisco NCS 4000 series devices involves discovery of OTU links between their end nodes, after which the circuit can be provisioned.

To discover OTU links between Cisco NCS 2000 series and Cisco NCS 4000 series devices, see Discovering OTU Links Between Cisco NCS 2000 Series Devices and Cisco NCS 4000 Series Devices.

To create an ODU circuit between any endpoints, see Create and Provision an ODU Circuit in the Cisco EPN Manager 6.1 User and Administrator Guide.

Prerequisites to provision ODU circuits:

  • To provision end-to-end circuits, the client ports must have free endpoints.

Cisco EPN Manager supports the following scenarios for discovering and provisioning ODU circuits between Cisco NCS 2000 series and Cisco NCS 4000 series devices:

  • Brownfield discovery with ODU UNI circuits (between Cisco NCS 4000 series devices) and local ODU XC circuits (between Cisco NCS 2000 series devices).

    In this scenario, an ODU circuit is provisioned between Cisco NCS 2000 series devices with Cisco NCS 4000 series devices as the mid-nodes. To provision this ODU circuit:

    1. Create local ODU cross-connects on the nodes of participating Cisco NCS 2000 series devices.

    2. Create ODU UNI circuits on the nodes of participating Cisco NCS 4000 series devices.

    3. Use the OCH-Trials (discovered on OCH-NC WSON circuits) to connect the nodes of Cisco NCS 2000 series and Cisco NCS 4000 series devices. On successful OCH-Trial connection between these nodes, an OTU link will be discovered.

    4. An ODU circuit will be discovered on top of the above-mentioned circuits with the circuit name: E2E:<local odu xc name Aend>---<local odu xc name Zend>.


    Note

    Promote/Modify/Delete operations are not supported on Brownfield ODU circuits.

    Note

    Brownfield discovery is not supported when static cross-connects exist on the Cisco NCS 4000 series devices.

    Note

    ODU UNI circuits must not be created on the ports of Cisco NCS 4000 series devices that form a part of the ODU circuit.

  • Greenfield discovery between Cisco NCS 2000 series and Cisco NCS 4000 series devices.

    In this scenario, ODU circuits are provisioned between Cisco NCS 2000 series devices, or between Cisco NCS 2000 series devices and Cisco NCS 4000 series devices.

    In this case:

    • OTU links are discovered on top of an OCH-Trail WSON (Cisco NCS 2000 series devices to Cisco NCS 2000 series devices), or on top of an OCH-Trail (Cisco NCS 2000 series devices to Cisco NCS 4000 series devices). Create an ODU circuit on top of these discovered OTU links, see Create and Provision an ODU Circuit.

    • You can choose OTU links as constraints.

Discovering OTU Links Between Cisco NCS 2000 Series Devices and Cisco NCS 4000 Series Devices

To provision a successful end-to-end ODU circuit between the Cisco NCS 2000 series and Cisco NCS 4000 series devices, an OTU link must be discovered.

To successfully discover an OTU link:

  1. Create GMPLS LMP circuits between the participating Cisco NCS 2000 series and Cisco NCS 4000 series devices (Trunk and ADD/DROP ports). OCH links appear in the topology between the trunk and ADD/DROP ports.

  2. Create OCH-NC WSON circuits between the participating Cisco NCS 2000 series devices (ADD/DROP ports).

  3. On successful creation of OCH-NC WSON circuits, an OCH-Trail is discovered between the devices, which prompts the discovery of an OTU link between the trail endpoints.


Note

To successfully discover an OTU link, the OCH-Trail must be in the FULL state.

Note

If an OCH-Trail is discovered on the ports of an existing OTU link (created using the managed link), then the existing OTU link (Managed) is converted into the discovered OTU link.

Functionality Deprecated in Cisco EPN Manager 6.1.1

  • Device support for Cisco IOS XRv 9000 on IOS-XR 7.7.1 has been deprecated from Cisco EPN Manager 6.1 onwards, see bug CSCwc46515.

Following features were deprecated in the Cisco EPN Manager 5.1 and removed from Cisco EPN Manager 6.1:

  • Support for Internet Explorer 11 browser

  • Bare metal installation

  • Classic license

Device/OS Support Added in Cisco EPN Manager 6.1.1

This section lists the new support provided in Cisco EPN Manager 6.1.1. For a list of all support information, click the gear icon at the top right of the web GUI and choose Help > Supported Devices.

Cisco Network Convergence System 5500 Series—New Operating System Support

Device Model Device OS
Cisco NCS 5500 Series IOS-XR 7.5.3
Cisco NCS 5500 Series IOS-XR 7.6.2

Cisco NCS-55A1-24Q6H-SS

 IOS-XR 7.4.2

Cisco Network Convergence System 5700 Series Routers—New Operating System Support

Device Model Device OS
Cisco NCS 5700 Router IOS-XR 7.5.3
Cisco NCS 5700 Router IOS-XR 7.6.2

Cisco 8000 Series Routers —New Operating System Support

Device Model Device OS
Cisco 8000 Router IOS-XR 7.5.3

Cisco 8201-24H8FH Router

 IOS-XR 7.5.2

Cisco Network Convergence System 560 Series Routers —New Operating System Support

Device Model Device OS
Cisco NCS 560 Router IOS-XR 7.6.2

Cisco Network Convergence System 540 Series Routers —New Operating System Support

Device Model Device OS
Cisco NCS 540 Router IOS-XR 7.6.2

Cisco ASR 9000 Series Aggregation Services Routers—New Operating System Support

Device Model Device OS
Cisco ASR 9000 Router IOS-XR 7.5.3
Cisco ASR 9000 Router IOS-XR 7.6.2
Cisco ASR 9000 32-bit Router IOS-XR 6.9.1
Cisco ASR 9000 32-bit Router IOS-XR 6.7.3

Cisco ASR 1000 Series Aggregation Services Routers—New Operating System Support

Device Model Device OS
Cisco ASR 1001-HX Router IOS-XE 16.6.6

Cisco ASR 900 Series Aggregation Services Routers—New Operating System Support

Device Model Device OS
Cisco ASR 903-U Router IOS-XE 17.6.1
Cisco ASR 902-U Router IOS-XE 17.6.1

Cisco Network Convergence System 2000 Series —New Operating System Support

Device Model Device OS
Cisco NCS 2000 Series SVO 12.3.1

Supported Installation/Upgrade Paths

The following table lists the valid paths for installing/upgrading to Cisco EPN Manager 6.1.1 from previous versions.

Current Cisco EPN Manager Version

Installation Path to Cisco EPN Manager 6.1.1

Cisco EPN Manager 6.1.0

 Cisco EPN Manager 6.1.0 (restore) > 6.1.1

Cisco EPN Manager 6.0.1

Cisco EPN Manager 6.0.0 (restore) > 6.0.1 > 6.1.1

Cisco EPN Manager 6.0.2

 Cisco EPN Manager 6.0.0 (restore) > 6.0.2 > 6.1.1

Cisco EPN Manager 6.0.0

 Cisco EPN Manager 6.0.0 (restore) > 6.1.1

Cisco EPN Manager 5.1.4.1

Cisco EPN Manager 5.1.4.1 > 6.0.0 (restore) > 6.1.1

See the relevant installation guide for installation prerequisites and procedures for Cisco EPN Manager versions.

For point patch installation instructions, see the readme file that is supplied with the patch file on the Software Download site on Cisco.com.

Important Notes

Upgrade Issues

  • FTP and TPTP are disabled by default.

  • Active Threshold Crossing Alarms (TCA) for temperature remain active and are not cleared automatically. Clear these alarms manually.

  • You must resync your devices to view ISIS links.

  • You must resync LDP-enabled devices to view LDP feature-related information.

  • You must recreate the TCAs for inbound/outbound errors and inbound/outbound discards in the Interface Health monitoring policy.

CTC Launch Failure on Google Chrome Browser

Launching Cisco Transport Controller (CTC) from the Cisco EPN Manager using Google Chrome browser may fail because .jnlp files cannot be downloaded on a secure chrome connection (https://). Therefore, to manually launch a CTC from the Google chrome browser, open a new tab and add the url: http://[device IP]/.

Limitations on Carrier Ethernet Circuit Provisioning

  • Promotion of service using an old probe name format is now supported. These probes are listed in the user interface with an appropriate standard OAM Profile name after promotion.

  • Sample profile: profile PM2_3_8_CoS5_DM type cfm-delay-measurement.

  • While custom profile names are supported in Cisco EPN Manager, modifying brownfield services with a different naming format deletes the existing custom profile and adds a new profile with a supported naming format.

  • Inventory models do not correctly display the profiles that are not associated to a service.

  • Validation limit for number of profiles is 100. If you create a new SLA operation profile after 100 existing profiles, the device generates an error and deployment fails.

TLS 1.2 Required for Secured Channel Communication for HTTPS and TLS

Only Transport Layer Security (TLS) 1.2 is supported for HTTPS and TLS related secured communication, for example, RADIUS EAP-TLS.

Support for TLS 1.0, TLS 1.1, and all versions of SSL has been disabled due to security vulnerabilities.

This means that all peer systems and clients that transact with Cisco EPN Manager using HTTPS/TLS must support TLS 1.2. If they do not support TLS 1.2, you must upgrade these systems. Wherever possible, the Cisco EPN Manager documentation highlights the potentially affected systems. Please contact your Cisco representative for support in this regard, if necessary.

Reconciliation Report Limitations

If you have not provided a value for an attribute while provisioning a service, the provisioned value for that attribute is displayed as “Missing” in the reconciliation report. The device may have a default value for this attribute, but Cisco EPN Manager does configure this value.

Limitations on ME 1200 Devices

The Y.1564 performance test does not work if the source/destination is a ME 1200 device.

Limitations on Editing Alarm Notification Policies

If the upgrade conditions of existing categories are different from the condition of categories on Cisco EPN Manager 5.1, then the conditions post upgrade will not match. As a result, policy might not be created or UI selection might not take place for the unmatched events. In this case, you should delete the upgraded policies and create new policies.

Limitations on Cisco NCS 4200 Series Running IOS-XE 16.8.1

The following functionalities do not work on Cisco NCS 4200 devices running IOS-XE 16.8.1:

  • Alarm profile

  • Configuration of SONET LOP and CT3 LOP from the GUI

  • Admin shut/no shut functionality on SONET/T1/T3 HOP/LOP

Limitations on Cisco NCS 540 Series Routers and Cisco NCS 5500 Series Devices

Cisco NCS 540 series routers and Cisco NCS 5500 series device do not support Fault-OAM, Wrap-Protection, and BFD.

Use CLI Templates for Configuring PTP Commands

On Cisco ASR 920 series aggregation services routers with software version 16.9.1, IEEE 1588-2008 BC/MC license is required to execute the 1588 PTP commands.

Configuration and Inventory Not Supported for PTP Templates

The behavior of modeling the configurations that are pushed through PTP templates may not work as expected because the model may not be in place for all the configurations that are pushed through PTP templates. Configuration/Inventory is not supported for these configurations.

Deprecation of Support for ONS 10.00.10, 10.01.00, 10.03.00

ONS 10.00.10, 10.01.00, and 10.03.00 are no longer supported on Cisco NCS 2002, 2006, and 2015 devices.

Data Center Device Lifecycle Support Only

Cisco EPN Manager provides foundation lifecycle support for UCS compute systems, CSR 1000v, and Cisco Nexus series devices but does not provide data center topology.

LINK_DOWN Alarm on Sub Interfaces in Gig Port

LINK_DOWN alarms will not be generated when the link is down on subinterfaces in a Gig Port.

Cisco EPN Manager Bugs

Open Bugs

The table below lists the open bugs in Cisco EPN Manager Release 6.1.1 according to the following criteria:

  • Severity 1, 2, and high priority severity 3 open bugs

  • All open customer-found bugs

  • High-impact bugs that are likely to affect Cisco EPN Manager workflows.

Click the identifier link to view the impact and workaround for the bug in the Bug Search Tool. Use this tool to track the status of the open bugs.

Bugs Description
CSCwd19383

When LAG is configured in device, it is shown under PAgP in Cisco EPN Manager instead of LACP.
CSCwd15192

[6-1-1]: On the ZR+, the physical port displays a few extra hundredGig ports that are not displayed
CSCwd33756

Duplicate OCHNC WSON services not getting discovered in BnR setup
CSCwc01484

Config archive Job run time has been changed after backup and restore has been done
CSCwd33869

Modify X21 circuit generates no clock rate command even with no changes to the service attributes

Closed Bugs

The table below lists the closed bugs in Cisco EPN Manager Release 6.1.1.

Click the identifier link to view the impact and workaround for the bug in the Bug Search Tool. Use this tool to track the status of the bugs.

Bugs Description
CSCvq68100

Create UNI: TenGig Port is not listing in provisioning UI
CSCvo29772

MUT: Inventory restconf notifications are delayed by 1.5 hours
CSCvo32160

Two devices had the same engine ID in Cisco EPN Manager, causing SNMP connectivity failures
CSCvs41600

[Upgrade] Upgrade in Bare Metal fails with Grub ERROR
CSCvt05351

SR TE policy does not get updated when Segment-lists gets updated
CSCvt23322

Port-status combo impact is not clear during termination of service
CSCvu26031

NCS2K ->Data under Configuration Tab -> Line not loading without refresh after creation of cardmode/ppm
CSCvu70810

NCS2K -> Dropdown for configuration not working for chassis view when opened in a new window
CSCvu91759

Optical VC Primary State is not updated on VC admin down when there is already an alarm on the VC
CSCvu94288

OCHCC service provisioning failing, error in getting response as '@xpath /beans[1]/CFS[1]/serviceId[1]'
CSCvv07473

NCS2K-> Filtering not working properly for inventory in chassis view
CSCvv24917

Chrome: Edit alarm notification policies and UI issues
CSCvv39261

SRTE Overlay - Z endpoint is not marked and "Show backup path" is not available
CSCvv53356

Duplicate services are getting listed after performing upgrade from 4.0.3 ->5.0
CSCvw13954

NCS2K: Modification of OTN Trail trace identifier/Section trace values are not retained after resync
CSCvw19016

[Scale] Cisco NCS 4000 devices: SDN/SONET slow policy collection, causing other schedulers job to start with delay
CSCvx57785

DTS: Report scheduling discrepancy
CSCvx59103

OTU2E rate is not supported for OCH-CC circuits for coherent/non-coherent TXP
CSCvx64278

4K TE over LAG - overlay displays the old path instead of the new one
CSCvy03910

Editing of optics/coherent controller should not be allowed if it is a part of a circuit
CSCwb46808

Performance dashboard, back end response is 500, UI showing spin whell for deleted breakout
CSCwb52175

ZRP optics port not showing the value of speed
CSCwb54915

ODU circuit (4K-2K) - Admin state shows partial in circuit details
CSCwb86147

Verify Credentials and Node Sync failing at Cisco EPN Manager for TACACS/Radius enabled 2K Nodes
CSCwb91125

Unable to promote EVPL between XE device with error of Failed to invoke. String.substring (int,int)
CSCvt90840

Scroll bar is not visible in notification policies edit page in a scenario
CSCwa74983

Cisco NCS 4000 devices: Frequncy (lable and value) not updated in if DWDM grid unit representation is changed
CSCwb03234

A-End or Z-End (icon) is not reading when it's in EDIT mode
CSCwb12659

Cisco-resource-physical: node does not return complete data for multi-chassis device

Resolved Bugs

The table below lists bugs that have been resolved in Cisco EPN Manager 6.1.1.

For more information about the resolved bugs, go to the Bug Search Tool.

Bugs Description
CSCwb95075

Few devices are in CF when we did first device sync on upgrade server (6.0 to 6.1)
CSCwc19985

6.1.1 GA 140C - Sometimes Link Arrow shows wrong direction
CSCwc44726

EPN - alarm notification policy email, SMS, and MMS gateway differences
CSCwc46815

SVO brown circuit appears in ENEs map not related to the circuit when we create circuit with same name

CSCwb70088

55A2/57C3/5508 (NC57-MOD-S with NC57-MPA-2D4H-S): Not showing Physical & breakout siice ports

CSCwc52020

NCS2K SVO Span loss showing incorrectly

CSCwb54803

5508: Click on alarm ID link from alarm tab in device 360 view, alarm not shown

CSCwc67858

Physical port is not populating for Cisco 8201-24H8FH Router running IOS-XR 7.5.3

Get Information about Cisco EPN Manager Bugs

Use the Bug Search tool (BST) to get the latest information about Cisco EPN Manager bugs. BST allows partners and customers to search for software bugs based on product, release, and keyword, and it aggregates key data such as bug details, product, and version.

Cisco EPN Manager bugs may be caused by defects in a device's platform or operating system. In such cases, the Cisco EPN Manager bug will be resolved when the hardware/operating system bug is resolved.

Procedure

Step 1

Log into the Bug Search Tool.

  1. Go to https://tools.cisco.com/bugsearch/.

  2. At the Log In screen, enter your registered Cisco.com username and password; then, click Log In.

Note 
If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do
Step 2

To list all bugs for this version, click the Select from list hyperlink that is next to the Product field and select the product.

  1. Choose Cloud and Systems Management > Routing and Switching Management > Cisco Evolved Programmable Network (EPN) Manager and then select the required product version.

  2. When the results are displayed, use the filter and sort tools to find bugs according to their status, severity, how recently they were modified, if any support cases are associated with them, and so forth.

You can also search using bug IDs or keywords. For more information, click Help at the top right of the Bug Search page.

Accessibility Features in Cisco EPN Manager 6.1.1

For a list of accessibility features in Cisco EPN Manager 6.1.1, contact accessibility@cisco.com.

All product documents are accessible. If you want to receive the product documentation in audio format, braille, or large print, contact accessibility@cisco.com

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.

Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.