Step 1

From the Expert Mode, in Configuration editor, navigate to /wae:wae/nimos and click the l3-l1-mappings tab.

Step 2

Click l3-l1-mappings.

Step 3

Click the plus (+) sign, enter an arbitrary name for the L3-L1 mapping group, and click confirm.

Step 4

To provide an L3 - L1 circuit:

1. Click the l3-l1-circuit-mapping tab and click the plus (+) sign.

2. Enter each L3 and L1 circuit names, l3-node, l3-interface, l1-node, and l1-port.

3. Click confirm.

Step 5

To manually enter the mapping of L3 - L1 interfaces and ports:

1. Click the l3-l1-mapping tab and click the plus (+) sign to enter each mapping.

2. Click Add.

3. Repeat these steps to enter all L3-L1 mappings.

Step 1

Configure and run an L3 IGP topology collection network model with the following interface options set to true:

• lag
• get-physical-ports

Step 2

In Configuration editor, navigate to /wae:wae/agents/optical-agents and click the optical-agent tab.

Step 3

Click Add (+) and enter an agent name.

Step 4

Click the cisco-wae-optical-epnm-agent link.

Step 5

Select the epnm-server-conf tab and enter the verified domain of the Cisco EPN Manager server and access group (authgroup that was configured in the NCS devices).

admin@wae(config)# wae agents optical-agents optical-agent 
<agent-name> cisco-wae-optical-epnm-agent epnm-server-conf epnm-server-fqdn <fqdn> 
epnm-server-access <authgroup>
cisco-wae-optical-epnm-agent advanced net-recorder <net-recorder-option>
cisco-wae-optical-epnm-agent advanced net-record-dir <net-recorder-storage-directory>
cisco-wae-optical-epnm-agent advanced pool-size-per-query <number-of-queries>
cisco-wae-optical-epnm-agent advanced notification subscribe-to-notifications <true or false>

Step 6

Click the Commit button.

Step 7

If you plan to utilize Lambda ID mapping (where you can set whether channel ID, central frequency, or wavelength will be mapped to the lambda ID), then you must load the Lambda ID configuration file. Enter the following command:

# ncs_load -lmj /wae/agents/optical-agents/optical-agent <agent-name>/lambda-mappings

Step 8

To run the L1 collection, navigate back to the cisco-wae-optical-epnm-agent tab and click run-collection > Invoke run-collection.

Step 9

Create an L1 optical collection network model:

1. Navigate to /wae:networks.

2. Click the plus (+) sign and enter an optical network model name. We recommend a unique name that contains the source network and NIMO names; for example, networkABC_optical.

3. Click Add.

4. Click the nimo tab.

5. From the Choice - nimo-type drop-down list, choose optical-nimo.

6. Click optical-nimo and enter the following information:

• source-network—Choose the applicable network model that contains L3 topology information collected using one of the topology NIMOs.
• network-access—Choose a network access group that was previously configured.

Step 10

Click the advanced tab to configure the following:

• cfg-parse-agent—Choose the configuration parse agent name if it was used for L1-L3 mapping.
• lag—Choose true if using the configuration parse agent.
• feasibility-limit-margin-list—(Optional) Choose the feasibility margin list name.
• central-frequency-excludelists—(Optional) Choose the frequency excludelist.

Step 11

Click the optical-agents tab and add any agents that were created.

1. Click the advanced tab to configure advanced features, including the following:

• retain-amplifiers—Choose true if you want to include amplifiers as part of the collection.
• map-lambdas—If set to true, a user table is created that displays the lambda mapping values (LambdaID, ITU channel number, G.694.1, central frequency, and wavelength) selected in the map-lambda-id-to field. Cisco recommends to set this value to true when collecting information from a network with L1 links supporting 96 channels.
• use-configured-l3-l1-mapping—Choose true if you manually configured the l3-l1 mapping (see Configure L3-L1 Mapping Information).
• l3-l1-mapping—Choose the l3-l1 mapping group that you configured earlier.
• collect-user-properties—Set to false if you do not want to collect user properties from the agent. The default value is true.

Step 12

Configure the aggregator to consolidate the L1 and L3 network models you just created. See example for aggregator rules to pick the data from proper source network. To view a CLI configuration example of the rest of this procedure, see Aggregator and Multilayer Collection Configuration Example.

1. Create an empty network. This will be the final consolidated network model. From the Expert Mode, navigate to /wae:networks, click the plus (+) sign, and enter a final network model name. For example, networkABC_L3L1.

2. Navigate to /wae:wae/components/dare:aggregators/aggregator tab.

3. Click the plus (+) sign and select the multilayer network (networkABC_L3L1) you just created from the destination drop-down list.

4. From the sources tab, click source, and add the L1 and L3 network models you want to combine the collections from.

5. Click Commit.

Step 13

Run the L3 collection.

1. Navigate to /wae:networks/network/<network-name> nimo/topo-igp-nimo.

2. From the topo-igp-nimo tab, click run-collection.

Step 14

Run the L1 collection.

1. Navigate to /wae:networks/network/<network-name> nimo/optical-nimo.

2. From the optical-nimo tab, select the L1 source network and click build-optical-topology.

Step 15

To verify that the merge was successful, you can open the network from WAE Design (File > Open from > WAE Automation Server and select the final network model).