Cisco Evolved Programmable Network Manager 2.1.1 Release Notes
Available Languages
Table of Contents
Cisco Evolved Programmable Network Manager 2.1.1 Release Notes
Functionality Added in Cisco EPN Manager 2.1.1
Device/OS Support Added in Cisco EPN Manager2.1.1
TLS 1.2 Required for Secured Channel Communication for HTTPS and TLS
Reconciliation Report Limitations
Limitations on ME 1200 Devices
Data Center Device Lifecycle Support Only
Get Information About Cisco EPN Manager Bugs
Accessibility Features in Cisco EPN Manager 2.1.1
Obtaining Documentation and Submitting a Service Request
Contents
This document contains the following information about Cisco Evolved Programmable Network Manager 2.1.1:
Functionality Added in Cisco EPN Manager 2.1.1
Note If a feature is marked as “Beta” it means that the feature is available but has not been fully tested.
Provisioning of Serial Services
– Comprehensive inventory management of Cisco cBR-8 devices
– Visualization of Cisco cBR-8 in the network topology
– Next generation chassis view support for Cisco cBR-8 DPIC cards
– Support for inventory audit between Cisco EPN Manager and Cisco c-BR8 devices
– Managing software images on cBR-8 devices
– Viewing Cisco cBR-8 device 360 and interface 360 information
– Viewing Cisco cBR-8 device details in the chassis view
– Device specific filtering capability over NBI
Note This feature is not supported if your network includes optical devices (NCS 1000, NCS 2000, NCS 4000).
– Interfaces tab—Displays type and status information for the interfaces configured on the selected device, module, or port
– Performance tab—Displays performance information for the selected interface on a module or port
- Virtual rack support added for ASR 9000 devices with Satellite setting.
- Refresh and zoom support is now available after adding a line card.
- Enhancements to the chassis view:
– Port view now displays contextual information related to the selected port
– Patchcords that are not supported are disabled
– Additional supported devices:
- NCS 5001 and NCS 5002 devices
- VCoP pluggable on NCS42XX devices
- NCS 2000 and ONS 15454 patchcord enhancements
– Ability to do a side-by-side comparison of the high-level information and status for multiple devices in the Device 360 view
– Accessibility enhancements for 360 views
– Auto-refresh function for Device 360 view
– SRRG tab added to Device 360 and Link 360—Displays SRRG information for selected devices/links
- Configuration of devices with 5G or 10G card modes (NCS 4000 devices and ASR 9000 devices)
- Automatic In-Service (AINS) state is supported on NCS 42XX device interfaces running IOS-XE 16.5.1 and higher.
- Configuration of Cisco NCS42XX device interface pluggable types with Virtual Container over Packet (VCoP)
- Device image identification by content instead of image file name for Cisco NCS 1000 devices
- Distribution of images to any file system including folders in the root directory. For file systems with standby flash, the image is distributed to both the active and the standby flash and can be activated directly from either active or standby. New Image Details Verification tab enables you to choose the target file system. This feature is supported on NCS 42xx and ASR 907 devices.
- Ability to use Field Programmable Devices (FPD) image packages for the upgrade of FPDs during the image distribution and activation process. This feature is supported on NCS 1000 devices.
- Ability to switch a circuit to its working path or protected path so that you can perform network maintenance activities without interrupting the service.
- Ability to provision an Optical Channel Data Unit User-to-Network Interface (ODU UNI) Hairpin circuit.
- (Beta) TE tunnels can now start or terminate on NCS 4000 devices running IOS-XR 6.1.32 and higher.
- Ability to lock out an MPLS interface in order to do maintenance work on the TE tunnel link to which it belongs (Interface 360 view).
- CEM local connect service can now be created between two CEM groups on same controller port
- CEM service bandwidth usage calculation has been enhanced to include packet overhead.
- CEM service can be created on Ethernet ports using the following pluggables:
– ONS-SI-OC-VCOP = OC3/OC12 over Ethernet Smart Pluggable
– ONS-SI-PDH-VCOP = DS3 over Ethernet Smart Pluggable
- For OTU links, you can now see exactly which channels are being used and which circuits are using the channels.
- While configuring QoS services on Cisco NCS 4000 devices, the Classification profile Traffic Class action can now be used to create and deploy QoS Classification profiles. This enables packets to be permitted based on the selected traffic class parameters.
- Discard Class action can be configured as part of the Classification profile for provisioning CE services using Cisco ME1200 devices.
- Committed Information Rate (CIR) parameter configured using QoS Action profiles can now be configured with appropriate CIR units such as kbps, mbps, and gbps.
- Ability to view QoS information for a selected service on a Cisco ME 1200 device in the Performance dashboard's ME 1200 EVC QoS tab
- Visualization of NCS 2000 devices that function as optical line amplifiers.
- The map now refreshes automatically. Manual refresh is not required.
- Visualization of CBR-8 devices in the map (and the geo map).
- Ability to manage SRRG assignments to NCS 2000 devices and links and visualize them in the geo map.
- Ability to search for a specific location in the map (address, town, country, etc.).
- The geo map now shows device groups that have a defined location, for example, devices in a building at a specific address.
- Ability to launch cable functionality from the geo map.
- Y.1564 Carrier Ethernet EVC performance test enhancements
- Support for ME 1200 device as source or destination in Y.1564 performance test.
- (Beta) Ability to generate a report that indicates the number of link flaps that have occurred between selected devices within a specified time period.
- (Beta) Ability to generate a report that indicates the power level (Rx and Tx) for optical Small Form-Factor Pluggable (SFP) transceiver modules which are monitored and polled on every link discovered in Cisco EPN Manager.
– Acknowledge, un-acknowledge, clear, and delete alarms
– Retrieve all alarms for a given service
– Retrieve all services for a given alarm
- Support for creating, assigning, and unassigning SRRGs
- Virtual connection filtering based on UNI and node
- Support for running LSP ping and traceroute tests
- MLT route retrieval improvements:
– Retrieval of all topological layers
– Retrieval of containing and contained endpoints
– Retrieval of MLT routes for all virtual connections
- Fiber type and length retrieval as part of termination point retrieval
- (Beta) Support for L2VPN services on ME 1200 devices:
– Support for NID to remote building via MPLS
– Support for E-Line NID to service edge
- Support for L2VPN services on NCS 4000 devices
- Protection switch action on protected path optical services
- Notification filtering:
– Filtering by node attributes for any element: productType, productFamily, productSeries
– Filtering by element types: RC_Node, Equipment, PhysicalConnector
Device/OS Support Added in Cisco EPN Manager 2.1.1
This section lists the new support provided in Cisco EPN Manager 2.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.
Note “Beta support” means that the device/operating system has not yet been released but Cisco EPN Manager has been tested on the Beta version.
Cisco NCS 4200 Network Convergence Systems—New Device and Operating System Support
Metro Core—New Operating System Support
Note Only the WSON package is supported (device package name ending with W-SPA).
Cisco Network Convergence System 2000 Series—New Operating System Support
Note Only the Flex and Legacy packages are supported (device package name ending with F-SPA and L-SPA respectively).
Installation/Upgrade Paths
The following table lists the installation/upgrade paths for Cisco EPN Manager 2.1.1.
- PP = Point Patch
- Cisco EPN Manager 2.x.x = Cisco EPN Manager 2.x Maintenance Pack x. For example, Cisco EPN Manager 2.1.1 = Cisco EPN Manager 2.1 Maintenance Pack 1
- Cisco EPN Manager 2.1.0.x = Cisco EPN Manager 2.1 installed with point patch x . For example, Cisco EPN Manager 2.1.0.1 = Cisco EPN Manager 2.1 with PP1.
1. Install Cisco EPN Manager 2.1—See Cisco EPN Manager 2.1 Installation Guide
2. Install Cisco EPN Manager 2.1.1—See Cisco EPN Manager 2.1.1 Installation Guide
1. Upgrade to Cisco EPN Manager 2.1—See Cisco EPN Manager 2.1 Installation Guide
2. Install Cisco EPN Manager —See Cisco EPN Manager 2.1.1 Installation Guide
1. Install Cisco EPN Manager —See Cisco EPN Manager 2.1.1 Installation Guide
Important Notes
- TLS 1.2 Required for Secured Channel Communication for HTTPS and TLS
- Reconciliation Report Limitations
- Limitations on ME 1200 Devices
- Data Center Device Lifecycle Support Only
- Data Migration Issues
TLS 1.2 Required for Secured Channel Communication for HTTPS and TLS
As of Cisco EPN Manager 2.1, 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, they must be upgraded. Where 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
When provisioning a service, if you have not provided a value for any of the attributes, the provisioned value for those attributes will be displayed as “Missing” in the reconciliation report. The device may have default values for these attributes but Cisco EPN Manager does not have any values configured.
Limitations on ME 1200 Devices
- Manual sync required—Configuration changes to ME 1200 devices are not automatically discovered by Cisco EPN Manager. After making a change, you must manually sync the device. To do this, select the required device(s) in the Network Devices table and click Sync.
- QoS profiles are not supported for service provisioning on ME1200 devices.
Data Center Device Lifecycle Support Only
Cisco EPN Manager 2.1.1 provides foundation lifecycle support for UCS compute systems, CSR 1000v, and Nexus series devices but does not provide data center topology.
Force Failover Not Supported
In a high availability environment, if you want to switch to the secondary server, do not use the Force Failover function as it might cause HA configuration corruption and instability of the servers.
Use this procedure to switch to the secondary server:
1. Log in to the primary and secondary servers as the Cisco EPN Manager CLI admin user.
2. Verify that the primary server’s status is Primary Active and the secondary server’s status is Secondary Synching by running the ncs ha status command.
3. Stop the primary server by running the ncs stop command.
4. If your HA system is configured to use manual failover, log into the secondary server’s Health Monitor web page and click the Failover button in the Action column.
If your HA system is configured to use automatic failover, the secondary server will become active automatically a few of minutes after stopping the primary server.
Cisco EPN Manager Bugs
Open Bugs
Table 1 lists the open bugs in Cisco EPN Manager Release 2.1.1 according to the following criteria:
Click the identifier 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.
Resolved Bugs
Table 2 lists bugs that have been resolved since the last release. Specifically, it lists bugs that were listed as open bugs in the Cisco EPN Manager 2.1 release notes that have been resolved in Cisco EPN Manager 2.1.1.
For more information about the resolved bugs, go to the Bug Search Tool .
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 those cases, the Cisco EPN Manager bug will be resolved when the hardware/operating system bug is resolved.
Step 1 Log into the Bug Search Tool.
a. Go to https://tools.cisco.com/bugsearch/ .
b. 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.
a. Choose Cloud and Systems Management > Routing and Switching Management > Cisco Evolved Programmable Network (EPN) Manager and then select the required product version.
b. 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.
Related Documentation
For a list of all documentation available for Cisco EPN Manager 2.1.1, see the Cisco Evolved Programmable Network Manager 2.1.1 Documentation Overview . The documentation overview also lists several Cisco Prime Infrastructure documents because the content of those documents is relevant to Cisco EPN Manager 2.1.1.
Accessibility Features in Cisco EPN Manager 2.1.1
For a list of accessibility features in Cisco EPN Manager 2.1.1, please contact accessibility@cisco.com .
All product documents are accessible except for images, graphics and some charts. If you would like 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 at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html .
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.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
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.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)