Cisco Evolved Programmable Network Manager 8.0.1 Release Notes

Cisco Evolved Programmable Network Manager, Release 8.0.1. 3

New software features. 3

New hardware features. 3

Resolved issues. 3

Known issues. 3

Compatibility. 4

Related resources. 6

Legal information. 7

 

 

Cisco Evolved Programmable Network Manager, Release 8.0.1

Cisco Evolved Programmable Network Manager (EPNM) Release 8.0.1 is a maintenance update aimed at improving overall stability and performance. It included several important bug fixes that address issues reported in earlier versions, including improvements to Y.1731 statistics, software activation, HA failback, and template deployment.

New software features

This release does not include any new software features or enhancements.

New hardware features

This release does not include any new hardware features or enhancements.

Resolved issues

This table lists the resolved issues in this specific software release.

Table 1.        Resolved issues for Cisco Evolved Programmable Network Manager, Release 8.0.1

Known issues

Upgrade issues

●    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 intermediate system to intermediate system links.

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

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

Compatibility

Software modification guidelines

Cisco EPN Manager is distributed with all required components, including Red Hat Linux and Oracle Database, fully optimized and tested for secure operation. Cisco will not support environments where any of the following changes are made:

●      Modifications to software or operating system configurations.

●      Installation of third-party software directly on the embedded OS.

●      Application of patches or updates not provided by Cisco.

●      Internal setting changes undocumented in official Cisco guides.

Limitations on carrier ethernet circuit provisioning

●    Promotion of services using the old probe name format is now supported. These probes are listed in the user interface with the 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.

●    The validation limit for the 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.

Securing user inputs to prevent XSS vulnerabilities

Cross-site Scripting (XSS) is a security vulnerability that allows attackers to inject malicious scripts into applications. These scripts can be used to steal information or perform other malicious actions. To safeguard the Cisco EPN Manager, it is crucial to avoid certain patterns in user input fields and POST/PUT payloads.

The following patterns have been identified as vulnerable and are blocked by the Cisco EPN Manager's XSS prevention feature. The Cisco EPN Manager will not execute the command or proceed to the next step if it finds these patterns; therefore, ensure they are not used in user inputs or API calls.

●    src=’…’(multiline, case insensitive pattern): Avoid using src=followed by any text or newline within single quotes. For example,<img src='malicious_code'>.

●    src=”…”(multiline, case insensitive pattern): Avoid using src=followed by any text or newline within double quotes. For example,<img src="malicious_code">.

●    </script>(case insensitive pattern): Avoid using the closing script tag in any form.

●    <script…>(multiline, case insensitive pattern): Avoid using the opening script tag with any content inside.

●    eval(…)(multiline, case insensitive pattern): Avoid using the eval function in any context. For example, eval('malicious_code').

●    expression(…)(multiline, case insensitive pattern).

●    javascript(case insensitive pattern): Avoid using javascript: protocol in any field.

●    vbscript:(case insensitive pattern): Avoid using vbscript: protocol.

●    onload…=(multiline, case insensitive pattern): Avoid using event handlers like onload in any of the fields.

●    <…>(multiline, case insensitive pattern).

●    <script…/script>(multiline, case insensitive pattern): Avoid any complete script tags with content.

CLI templates for configuring PTP commands

On ASR920 devices with software version 16.9.1, IEEE 1588-2008 BC/MC license is required to execute the 1588 PTP commands.

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.

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. Contact your Cisco representative for support in this regard, if necessary.

Unsupported hardware

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

●    Cisco NCS 4200 devices with IOS-XE 16.8.1: The following features are not supported 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.

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

Unsupported software

●    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 by these configurations.

●    Deprecation of support for ONS 10.00.10, 10.01.00, 10.03.00: 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, Cisco NCS 2006, and Cisco NCS 2015 devices.

●    Cisco EPN Manager provides essential support for a few selected UCS computer systems, Nexus series devices, and the CSR 1000v devices.

●    LINK_DOWN alarms will not be generated when a link is down on sub interfaces in a Gig Port.

Related resources

Information portal

An Information Portal/Collection page is now available for Cisco Evolved Programmable Network Manager. 8.0 Information is categorized by functional area, making it easy to find and easy to access.

You can also access documentation for all Cisco Evolved Programmable Network Manager at https://www.cisco.com/c/en/us/support/cloud-systems-management/evolved-programmable-network-epn-manager/series.html#~tab-documents

Product documentation

Table 2.             Cisco Evolved Programmable Network Manager 8.0 documentation

Table 3.             Cisco Evolved Programmable Network Manager 8.0 supported documentation

 

Cisco bug search tool

You can use the Cisco Bug Search Tool to search for bugs.

1.     Go to the Cisco Bug Search Tool.

2.     Enter your registered Cisco.com username and password and click Log In. The Bug Search page opens.

Note: If you do not have a Cisco.com username and password, you can register on the registration page.

3.     To search for all Cisco Evolved Programmable Network Manager bugs, from the Product list select Cloud and Systems Management > Routing and Switching Management > Cisco Evolved Programmable Network Manager and enter additional criteria (such as bug ID, problem description, a feature, or a product name) in the Search For field. Examples: "Optimization Engine" or "CSCwc62479". When the search results are displayed, use the filter tools to narrow the results. You can filter the bugs by status, severity, and so on.

Note: To export the results to a spreadsheet, click Export Results to Excel.

Legal information

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2025 Cisco Systems, Inc. All rights reserved.