GUI - General

• EPNM Dashboard OTN/DWDM Performance Time Frame shell set zoom for all dashlets

• HundredGigE interface breakout support

• EPNM tables and listings shall have CSV export function

• Performance improvements for chassis view in abridge window

• Base UI/DLCM Portfolio for 5.1.0

Device Configuration

• EPNM to not show Uncertified Software version

• Option to enable Role-Based Access Control(RBAC) for template deployment

• Support of Location, User-defined Group Name, Device Groups during export and import

• Option to connect to device with stronger SSH algorthim

• Compliance Audit: Import and Export support for compliance profile

• EPNM: Specification of bandwidth (for a MPLS TE Tunnel) in Kbps is cumbersome and needs to be improved

• Deploy archived config with RESTAPI

Circuit Emulation

• BERT line test on a controller when no CEM service is configured (UI and API)

Device Support

• EPNM chassis view NCS-5500 Support for PID NC57-18DD-SE

• EPNM support of IOS-XR  7.3.1 on ASR9K

• EPNM support of IOS-XR  7.3.1 on NCS5500 (Especially NCS5504, NCS5508 NCS5516)

• EPNM support of IOS-XR 7.3.1 on NCS5700

• EPNM support of IOS-XR 7.3.1 on NCS1001

• EPNM support of IOS-XR 7.3.1 on NCS1002

• EPNM support of IOS-XR 7.3.1 on NCS1004

• EPNM support of IOS-XR 7.3.1 on NCS540

• EPNM support of IOS-XR  7.3.1 on NCS560

• EPNM support of IOS-XR  7.3.1 on NCS 540 (N540X-6Z18G-SYS-A, N540X-6Z18G-SYS-D AC/DC)

• EPNM Advantage RTM Support for 8201-SYS 24x 400G + 12x 100G device with QSFP-DD/ZR and XR 7.3.1 (Beta)

• EPNM support of IOS-XR  7.0.2 on ASR9K

• EPNM support of IOS-XR 7.1.2 on NCS560

• EPNM support of IOS-XR 7.2.2 on NCS540

• EPNM support of IOS-XR 7.2.2 on NCS5500

• EPNM validation for XRv 9000 XR 7.2.2

• EPNM Validation of IOS XE 17.4.1 (November 2020) on ASR900/NCS4200

• EPNM support of IOS-XR 7.2.1 on NCS540 (NCS540L)

• EPNM support of IOS-XR 7.2.1 on NCS540

• EPNM support of  NCS-57B1-5DSE-SYS

• EPNM support of NCS 2k 12.2 on NCS 2000

Performance

• OTDR add possibility to set scan zone and mode Fast/Hybrid

• OTDR enhancements based on customer Demo

• Improvements to support Y.1731 five minute collection buckets

Inventory Management

• EPNM(/NCS2k) Activate image device selection shall display standby image

Topology

• Option to set the Auto-Refresh Interval for Alarms and Tables in Topology View

• Segment Routing TE provisioning, Discovery and Overlay: FlexAlgo support

• Disables the 3D visualisation option

Scale

• Define EPNM professional profile content for current professional EPNM server dimensions

Security

• LDAP - Prevent injection attacks

• X.509 client certificate based auth instead of user name and password

• CT1952: SEC-509-VALIDATE-5: Validate X.509 certificates

• CT1942: SEC-ASU-SCAN-3: Evaluate the attack surface of an operational offering using automated scanning tools

• SEC-PWD-CONTROL: Control password usage and behavior to ensure security and awareness

• SEC-PWD-STRENGTH: Enforce password strength requirements for all user, local, administrative, and system account passwords

• CT1942: SEC-ASU-SCAN-3: Implement Static Analysis infrastructure

Circuit Provisioning

• Support EVPN Multi-Homed VPWS in EPNM (Beta level)

Licensing

• Update License/Admin tab as part of the metering standardisation

Optical

• Improve the NCS2k database retry mechanism

• QSFP-DD ZR+ pluggable support XR 7.3.1 applicable only on NCS-57B1-5DSE-SYS and 8201-SYS in EPNM 5.1 as par of IPoEoF support (Beta)

• Real Time PM in Interface 360 for Routers DWDM Interfaces

• Create OCH-Trail Between Routers coloured ports with no DWDM extended to ZR/ZRP (Beta)

• NCS1001 NCS1K-MD-64-C (64 channel AAWGs built for 400G-ZR)

• NCS2k SVO 12.2 support

• Support for NCS1004 Rel 7.3.1 OS Version

• Support for NCS1001 Rel 7.3.1 OS Version

• Support for NCS1002 Rel 7.3.1 OS Version

• EPNM to be able to map Router Port to ODU ""UNI"" SNCP

• EPNM to be able to map ODU ""UNI"" to MCH Trail

• Enhancement in REST API to get OSNR status

• NCS2k TL1 support for 11.1.2 Alien Wavelengths (ZR/ZR+)

• NCS2k SVO 10G clients leftovers - non peering modes

• NCS2k SVO 10G clients leftovers - peering modes

• NCS2k SVO 12.2 legacy cards support

• NCS2K SVO support for C+L band combiner NCS2K-MF-CL-SC

• NCS2k SVO support for MP OCH-Trail circuits with NCS1004

• NCS55xx, 560, 1004 wavelength retuning after SVO restoration

• NCS2k SVO based cross-connection provisioning with OCH circuit name

• EPNM shall auto delete NCS2k Optical WSON/SSON circuits

• EPNM Create Circuit Optical Endpoint selection column resize shall keep selected data

• EPNM/ NCS2k shall ask for service affecting interface Admin State change

• EPNM tables shall scale to pane size

• EPNM/NCS2k: CPS-1610 servicability details shall provide device name

• Support for NCS1004 OTN-XP  with 400G CFP2-DCO Rel.7.3.1

• 400G CFP2-DCO pluggable support

• NCS2k SVO support for 1.2T-MXP linecard

Fault Management

• Add alarm correlation column with Name for Circuits and Links

• EPNM – Include APC alarm on OMS/OTS Link 360 View

• EPNM – Include LOS-RAMAN alarm in OTS/OMS Link 360 View

• EPNM/Optical/NCS2k: Alarm shall indicate rack of alarmed object

• Support for Syslog 'INFRA-SHELF_MGR-4-CARD_RELOAD' for ASR 9k (9910) devices.

• EPNM NE ping/trace from Device A to Device B with source and destination

• Alarm Trap forwarding  has to provide more granular filtering capabilities - Websocket NBI

Service Discovery

• Large L3 VPN promotion should be blocked

System Logs

• Manage device lock mechanism for SWIM and CA

RESTCONF NBI

• NBI support for SVO-based circuits (MP OCH-Trail and OCH-CC) including GET of all provisioning parameters

  Following parameters are supported for circuit colour validation while creation of OCH-Trail with legacy cards:

  Mandatory port parameters : AmpliGainRange, ChPwr, Gain, Tilt, WkgMode - OpticalAmplificationSettings table VoaAttenuation, Attenuator - OpticalTransportSettings table.

  Reactive inventory will not get triggered if above port parameters changed on the device. User has to trigger sync operation to get updated parameters in EPNM. Mandatory link parameter : FiberType - (FiberAttributes) - ProtocolEndPoint table Optional link parameters : MeasuredLoss - (FiberAttributes) - ProtocolEndPoint table PmdCoefficient - (FiberAttributes) - ProtocolEndPoint table.

  No need for manual sync in case of any link parameter changes.

• OTDR NBI API retrieval of data without .sor formatting

• The ability to show/tie NE Name to the Termination Point/Interface in API response

• EPNM NBI: Single-entry array format for JSON return

• Device Ping and Trace with RESTAPI from EPNM

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

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

Cisco Network Convergence Systems 4200 Series Routers—New Operating System Support

Cisco NCS 5700 Network Convergence Systems—New Operating System Support

Cisco NCS 560 Network Convergence Systems—New Operating System Support

Cisco NCS 1000 Series Network Convergence Systems—New Operating System Support

Cisco NCS 2000 Series Network Convergence Systems —New Operating System Support

Cisco NCS 5500 Network Convergence Systems—New Operating System Support

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

Note	IOS-XR 7.1.3 is not supported on Cisco ASR 9903 router.

Upgrade Issues

• FTP and TPTP will be disabled by default.

• Active threshold crossing alarms (TCA) for temperature will remain active and will not be cleared. Please clear these alarms manually.

• Devices must be resynced in order to view ISIS links.

• LDP-enabled devices must be resynced in order to view LDP feature-related information.

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

• Job scheduler limitation with reports jobs(Recurrence mode: Hourly & Daily) in 3.1:

  In 3.x - the behavior of the Jobs Scheduler is, the NEXT RUN TIME of the job is set based on the PREVIOUS COMPLETION TIME of the job. Jobs occurrence is performed based on the trigger objects which are created and persisted in DB during 3.x. So the same behavior will be carried over for these old reports job after upgrading the setup with 5.1.

  However in 5.x - the behavior of the Jobs Scheduler for new reports job is, the NEXT RUN TIME of the job is set based on the Scheduler Time and not based on the PREVIOUS COMPLETION TIME. So it has fixed start time based on the scheduled time for the newly created/rescheduled Jobs.

  After upgrading from 3.x to 5.1:

  We are recommending that user needs to reschedule the reports which are created in 3.x through reports UI with own preferred date/time. This is required if user expects more accuracy in schedule and data collection for reports. After rescheduling the reports, job's old run history will be cleared and new run will be stored and it will start and run as per scheduled time.

  Also we are providing reports diagnostic utility page which will help the user to reschedule those reports in one step in 5.1. User has to be aware of the reschedule time that is selected by the utility.

  This utility page will list down only Hourly/Daily occurrence reports job which are created during 3.x.

  Retrieved actual scheduled date & time of the report and deriving new proposed schedule date and time.

  The proposed date is depends current date and time will remain as originally scheduled HH:MM:SS.[i.e. original scheduled time: Wed Mar 17 17:00:00 IST 2021 & Proposed date: Wed Mar 31 17:00:00 IST 2021]

  User can review the job details on this page and reschedule all the jobs by clicking the "Re-Schedule All" button.

  Once it is rescheduled successfully, these jobs will not display on this utility page next time.

  Link to access this page - https://[EPNM_IP]/webacs/pages/reports/RescheduleReportsJob.jsp

Limitations on Carrier Ethernet Circuit Provisioning

• Promotion of service using old probe name format will be supported and probes will get listed in user interface with appropriate standard OAM Profile name after promotion.

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

• Till custom profiles names is supported, empty modification of brownfield services with different naming format will cause deleting of existing custom profile and adding of new profiles with provisioning supported name format.

• Inventory models only loose and delay profiles which is associated to service. But, there can be profiles in device which is not associated to any service. Validation if limit of 100 profiles is reached in device is not handled before config is deployed.

• Error will be thrown from device and deploy will get failed when user tries to create new SLA operation profile when EPNM tries to create 101th profile.

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

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. 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

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

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 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 policied and create new one.

Limitations on NCS 4200 Devices Running IOS-XE 16.8.1

The following functionality does not work on 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 NCS540 and NCS5500 devices

• NCS540 device series does not support Fault-OAM, Wrap-Protection and BFD.

• NCS5500 device series does not support Fault-OAM, Wrap-Protection and BFD.

Use 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.

Configuration and Inventory Not Supported for PTP Templates

The behavior of modeling the configurations pushed through PTP templates may not work as expected because the model may not be in place for all the configurations 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

No 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 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 link is down on sub interfaces in Gig Port.

Limitations on Carrier Ethernet Circuit Provisioning