The run methods implemented by all Optimization and Prediction Module (OPM) packages with action callbacks, now accept one additional argument: sess_info.

The APIs which require Maapi or transaction handle, are called with one additional parameter, namely sess_info (variable of type SessionInfo).

Following are some of the sample changes:

Update OPMs you have developed, if any, to work with the new APIs.

Note	The maapi and the transaction handle will not be properties of the OpmActionBase object itself, but of the SessionInfo object. There are no changes to network model traversal/modification APIs.

Schedule the build-optical-topology resync action of optical nimo to get updates related to L1-L3 mapping:

Netwoks networks <optical_nimo_name> nimo optical_nimo build-optical-topology resync true

When pause action is invoked on the XTC agent (either on topo or LSP), the XTC agent completes processing the message it is currently processing and as soon as the message is processed, next message and subsequent messages are put into a queue. This allows the NIMOs to be run for collection.

A new pause-xtc-agent option is introduced for topo-bgpls-xtc-nimo and lsp-pcep-xtc-nimo which can be set during NIMO collection.

To set this option, when you configure Topology Collection using XTC or LSP Collection using XTC, navigate to advanced → xtc tab and enable pause-xtc-agent. For information on how to configure Topology Collection using XTC or LSP Collection using XTC, see Cisco WAE User Guide.

In Cisco WAE 6.6.2 XR release, the SR LSPs do not autoroute by default.

Configure bandwidth optimization application to set profile-id which enables autoroute. To configure bandwidth optimization, navigate to /wae:wae/components/bw-opt and click the config tab and set profile-id. The default value for profile-id is 0, which indicates the Bandwidth Optimization application to not use the profile-id. When a profile-id is set, all the LSPs deployed are created with that profile-id in the router. These SR LSPs are then enabled to autoroute.

For more information on how to configure bandwidth optimization, see Cisco WAE User Guide.

Layout NIMO is enhanced with a simpler workflow. The template information is now stored in native format which also enables a faster execution time.

Following is the new workflow introduced in this patch:

• From the Expert Mode, navigate to /wae:networks.

• Click the plus (+) sign and enter a network model name. We recommend a unique name that contains the source network and NIMO names. This procedure uses networkABC_layout as an example.

• Click Add.

• Click the nimo tab.

• From the Choice - nimo-type drop-down list, choose layout-nimo.

• Click layout-nimo and enter the following:

  • source-network－Enter the source network for the network to use.

  • storage-format－Select between yang and native formats.

  • template-plan-file-path－Enter the absolute path of the template file to be used by layout nimo.

• Launch WAE Design and choose File > Open From > WAE Automation Server.

• Enter the appropriate details, choose the plan file for the network model you just created (networkABC_layout), and click OK.

• Edit the layout.

• Click Save to > WAE Automation Server. Enter the plan file details and click OK.

• From the Expert Mode, click run-layout > Invoke run-layout.

• Navigate back to the layout-nimo network model (networkABC_layout).

• Click layouts tab.

• Click layout to confirm that the table has been populated with layout data.

WAE Design now allows you to directly update the Layout NIMO template file.

Once you edit the network layout, save the plan file using the option Save to > WAE Automation Server. Enter the plan file details and click OK.

A new aggregator configuration option cache-aggr-net is introduced in the Advanced tab (Navigation: From the Expert Mode, navigate to /wae:wae/components/aggregators/advanced).

When this value is set to True, a copy of the aggregator plan is maintained on disk which is used to fetch data during the get-plan requests on aggregator network, unless the file is an old version. (Database has got updated after the last time the plan file was generated). Default value is False.

The following table lists the supported XR versions for Cisco WAE 7.1.3 Patch 2 along with earlier supported XR versions on WAE 7.1.3:

CSCvp63150: DesignApi process memory footprints increased.

This issue can be resolved using the following workaround:

1. From the Expert Mode, navigate to /wae:wae/components/wmd:wmd and click config.

   - From the network-name drop-down list, select the final network model.

   - Click rpc-connection and set respawn-on-reload to true.

2. Navigate to /wae:wae/components/aggregators/aggregator <network_name> and schedule the resync-aggregator-net action.

3. After making the changes, run the following command on WAE CLI:

   admin@wae# packages reload

CSCvo36676: WAE server crashes leaving java processes running.

This issue can be resolved by upgrading Network Service Orchestrator to version 4.7.4 as part of WAE 7.1.3 patch 1.

CSCvo88515: WAE application crashes with errors "unexpected end of file" and "exception internal" after invoking or executing the custom-network-info task.

This issue can be resolved by upgrading Network Service Orchestrator to version 4.7.4 as part of WAE 7.1.3 patch 1.

WAE services have to be managed using Supervisor. Install and run Supervisor before starting WAE.

For more information, see Cisco WAE 7.1.3 Installation Guide.

A new Cisco Evolved Programmable Network Manager (Cisco EPN Manager) agent is added to support the collection of optical topology for Cisco Network Convergence System (NCS) 2000 series, Release 10.9. This agent also receives notifications from Cisco EPN Manager version 2.2.2.1 when the status of links and circuits change and updates the network model accordingly. When using the Expert Mode, changes to the nodes, circuits, and so on can be seen in the agent-model tab from the following path: wae:wae/agents/optical-agent:optical-agents/optical-agent/<epnm_agent_name>.

Note	If optical provisioning is not done through Cisco EPN Manager, notifications are not received.

For more information, see "Network Model Configuration—Cisco WAE UI" chapter in the Cisco WAE 7.1.3 User Guide.

LSP collection (lsp-config-nimo) configuration is updated to integrate with NSO using the NETCONF API.

For more information, see "Network Interface Modules (NIMOs)" chapter ("Segment Routing Traffic Matrix Collection" topic) in the Cisco WAE 7.1.3 User Guide

Segment Routing (SR) Traffic Collection (sr-traffic-matrix-nimo) discovers SR traffic. This NIMO enables the generation of demands between external interfaces of a network from collected telemetry data.

For more information, see:

• "Network Interface Modules (NIMOs)" chapter ("Segment Routing Traffic Matrix Collection" topic) in the Cisco WAE 7.1.3 User Guide

• "Telemetry Configuration" chapter in the Cisco WAE 7.1.3 User Guide

The DARE aging processor is enhanced to maintain an in memory map for aged elements instead of doing the CDB scan every time the aging scheduler runs.

For more information, see "Administration" chapter ("Configure Aging" topic) in the Cisco WAE 7.1.3 User Guide.

XATP functionality is moved into the two NIMOs that process data from XTC - topo-bgpls-xtc-nimo and lsp-pcep-xtc-nimo, removing the dependency on WMD.

The following NIMOs are enhanced to support native storage format:

• Traffic Demand NIMO

• Layout NIMO

• Inventory NIMO

• Netflow NIMO

• SRTM NIMO

For more information, see "Network Interface Modules (NIMOs)" chapter in the Cisco WAE 7.1.3 User Guide.

Multicast NIMO collects multicast flow data from a given network. It is a collection of the following NIMOs:

• snmp-find-multicast-nimo—Collects multicast data for multicast flows using SNMP.

• snmp-poll-multicast-nimo—Collects traffic data rate for multicast flows using SNMP.

• login-find-multicast-nimo—Logs in to router to fetch or parse multicast flow data.

• login-poll-multicast-nimo—Logs in to router to get multicast traffic rate

For more information, see "Network Interface Modules (NIMOs)" chapter in the Cisco WAE 7.1.3 User Guide.

port-cfg-parse-nimo is now renamed to topo-cfg-parse-nimo and the support to read topology from parse configs is added.

For more information, see "Network Interface Modules (NIMOs)" chapter ("Port, LSP, SRLG, and VPN Collection Using Configuration Parsing" topic) in the Cisco WAE 7.1.3 User Guide.

A new aggregator, SAgE (Simple Aggregation Engine), is introduced to receive patches from DARE and NIMOs depending on DARE and aggregate these changes.

For more information, see "Overview" chapter ("Cisco WAE Architecture" topic) in the Cisco WAE 7.1.3 User Guide.

inter-as-nimo is introduced to enable merging of plan files from different AS and resolve conflicts.

For more information, see "Network Interface Modules (NIMOs)" chapter ("Merge AS Plan Files" topic) in the Cisco WAE 7.1.3 User Guide.

Cisco WAE 7.1.3 is enahanced with various UI changes.

For more information, see "Network Model Configuration—CiscoWAE UI" chapter in the Cisco WAE 7.1.3 User Guide

The status dashboard in WAE helps to identify the processes that cause system leaks or processes that completely use the resources. System health, WAE health, status of NIMO actions and agent actions are captured in the dashboard.

For more information, see "Administration" chapter ("Status Dashboard" section) in the Cisco WAE 7.1.3 User Guide.

WAE 7.1.3 now supports building network model from multiple XTC.

Traffic Poller tuning is enhanced for better computing.

For more information, see "Network Interface Modules (NIMOs)" chapter ("Traffic Collection" topic) in the Cisco WAE 7.1.3 User Guide

Users can now cleanup Map cache based on configurable attribute in config.xml. By default, the cache for Map display is cleaned up every 3 days. To clean up the cache more frequently, you can configure as follows:

1. Stop the Cisco WAE web server.

2. Log in to your local server and open config.xml file for editing. The default location is /opt/cariden/etc/config/config.xml. Your location might differ if you chose a different installation directory.

3. In the config.xml file, locate the section - <application name="Map">

4. Under <application name="Map">, do one of the following, depending on whether you are upgrading or performing a fresh installation:

   • If you are upgrading from an earlier release, add the following line:

     <property name="Map.UiCacheTTL" type="String"><value> <unit></property>

   • If you are performing a fresh installation, edit the existing line:

     <property name="Map.UiCacheTTL " type="String"><value> <unit></property>

     where

     <value> is a float (a floating-point number, or a number that has a decimal place).

     <unit> is either hour, or day. The unit can be singular or plural and is not case-sensitive. For example, hour can be expressed in all of the following ways: hour, Hour, Hours, HOURS.

     For example, to purge time-series data that is older than 1 hour, enter:

     <property name="Map.UiCacheTTL" type="String">1 hour</property>

5. Save your changes and close the config.xml file.

6. Restart the Cisco WAE web server.

The Capacity Planning Optimization tool controls how L1 Circuits and their corresponding paths are created. However, it automatically mimics the L1 Circuit characteristics of existing parallel L1 Circuits when upgrading capacity.

To enhance the Capacity Planning Optimization tool to handle different scenarios, the following CLI options are introduced:

• -match-existing-l1-circuits: This is a new option that is added. If set to T, when existing L3 adjacencies are upgraded (by adding parallel Port Circuits or L3 Circuits), corresponding L1 Circuits are created based on associated L1 Circuits of parallel Port Circuits or L3 Circuits. This includes replicating primary and secondary paths with respect to their Standby property as well as their associated Actual L1 Circuit Path Hops and L1 Circuit Path Hops. Default is F.

• -create-l1-circuits: This is a modified option. If F (default), do not create L1 circuits for new port circuits. If T, create L1 circuits for new port circuits. If match-existing-l1-circuits is set to T, this option is only considered for new adjacencies.

• -primary-l1-circuit-paths: This is a modified option. If F (default), primary L1 circuit paths are dynamically routed. If T, assign L1 circuit path hops to new primary L1 circuit paths to match the explicitly specified routes of existing parallel L1 circuits. Ignored if -create-l1-circuits is F or if match-existing-l1-circuits is set to T.

• -secondary-l1-circuit-paths: If F (default), do not create secondary non-standby L1 circuit paths. If T, create secondary non-standby L1 circuit paths. Ignored if -create-l1-circuits is F. If match-existing-l1-circuits is set to T, this option is only considered for new adjacencies.

Cisco WAE Design GUI is modified as follows:

Tools > Capacity Planning Optimization > Layer 1 tab has new options - Do not create L1 circuits, Basic L1 Circuit Creation, and Advanced L1 Circuit Creation.

The load-plan CLI command (wae/components/load-plan) to load plan files can handle only plan files which have the Network table as defined in schema and the Title row. However, value for the title (network name) is optional.