The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Multi-layer (L1 and L3) network collection is an advanced collection configuration. This section describes how to configure inventory, topology, and traffic collection from a multi-layer network. After installing the multi-layer package, you are able to collect and model the following information:
After collection, the network model (plan file) is placed in the Design Archive. You can open the plan file and view L1 and L3 topology in WAE Design. For more information, see “Layer 1 Simulation” in the Cisco WAE Design User Guide .
mate_auth_init
CLI tool. After the authentication file (auth.enc) is created, add the following lines to the file (using tabs, not spaces):
For more information on using the
mate_auth_init
tool, see Network Authentication.
The following steps describe the high-level workflow of multi-layer collection configuration.
Step 1 Download and Install the Multi-Layer (ML) Package
This step only needs to be done once.
Step 2 Start Multi-Layer Services
Step 3 Configure Layer 1 Collection
Step 4 Configure L3 Collection and Merge L1 Information in Snapshot
Step 5 (Optional) Collect from Multiple Networks
This step can be repeated depending on the number of L1 networks that need collection.
Confirm you have met all the requirements documented in the Prerequisites section.
The package installs necessary components used for multi-layer collection. See Table 6-1 for a list of services and associated command options that are installed. See Table 6-2 to see where all the components are installed.
Step 1 Log into the Planning Server with the username and password used during the WAE Planning Software installation. The default user is wae and the password is ciscowae .
Step 2 Go to the software download center where you obtained the WAE Planning Software. From there, download the WAE Optical Plug-in package <wae-ml-collector-xxxxxx-x86_64.bin>.
Step 3 Run the following commands:
The
|
Step 1 Edit and save the
$WAE_HOME/optical-plugin/config/ctc-connectors-domain.properties
file with the following information:
network.id
—Optical network name. For example, cisco:network
network.nodes.vendor
—Node vendor.
network.discovery.start.node
—The IP address of the discovery seed node.
network.discovery.start.node
—The ID to log into the seed node.
network.discovery.start.node.password
—The password to access the seed node.
network.discovery.inactivity.period
—Time in milliseconds which the discovery will time out if there is no access to the network.Step 3 Confirm that the services are running:
You can start and configure L1 collection using the CLI console.
Step 2 Enter into configuration mode:
Step 3 Configure the auth.enc and cariden-home paths using the Network Service Module setting options:
Step 4 Configure the L1Server IP address and optical plug-in port for the network:
Note The default port is 9000 for the first optical plug-in instance. Default for the next additional optical plug-in instances are 9001, 9002, 9003, and so on. To configure the optical plug-in to connect to a different port, edit the line restconf.http.port=<port_number>
in the $WAE_HOME/optical-plugin[-<instance_number>]/config/ctc-connectors-restconf.properties
file.
Step 5 Schedule L1 collection:
Step 6 Commit the collection and exit the console:
Step 1 Edit the $CARIDEN_HOME/etc/snapshot.txt file:
Note To collect L1-L3 port mapping in non-UNI networks, contact your Cisco representative.
Step 2 Run the snapshot collection:
Step 3 Open the plan files using WAE Design. Alternatively, you can collect multi-layer information from additional networks. For more information, see Collect from Multiple Networks.
The following procedure describes how to include additional L1 networks to the multi-layer collection. This procedure assumes that you have already performed a previous collection (as described earlier in this section) and the additional L1 networks are connected to a single L3 network.
Step 1 Create a new instance of an optical-plugin:
Step 2 Configure L1 collection.
Follow the same steps described in Configure Layer 1 Collection, but the network name, L1Server IP address, and port in the new network should refer to the network name IP Address and port of the new optical plug-in instance.
Step 3 Start the new instance of an optical plug-in:
Step 4 Run the
access_netconf
tool with the new network name and old output plan as the input.
# ./access_netconf –network NetworkB –authGroup ncs –action merge_l1_data –input-plan-file post-NetworkA.txt –output-plan-file post-NetworksAB.txt
You can repeat this procedure to merge collections from additional networks.
By default, L1 collection includes amplifier link and node information. You may want to remove optical amplifier information to declutter the topology shown when opening a plan file in WAE Design. Figure 6-1 and Figure 6-2 show the differences in topology when amplifiers are included and when they are not.
To exclude optical amplifiers from collection, do the following:
Step 2 Enter into configuration mode:
Step 3 From the Network Service Module setting options, set the
retain-amplifiers
option to false:
admin@ncs(config)# services NsmSettings network <network_name> options retain-amplifiers false
Step 4 Commit the collection and exit the console:
The next time L1 collection is scheduled, optical amplifier information is not included in the plan file.
Figure 6-1 Topology With Amplifiers
Figure 6-2 Topology Without Amplifiers
The quality of an L1 circuit deteriorates as it passes through L1 links. Using feasibility properties, WAE Design enables you to simulate the weakening of L1 circuits to determine if they have degraded to the point of being unroutable. To set the feasibilty limit margin, do the following:
Step 2 Enter into configuration mode:
Step 3 From the Network Service Module setting options, set the decimal value for the
feasibility-limit-margin
. The default value is 2.5.
admin@ncs(config)# services NsmSettings network <network_name> options feasibility-limit-margin <margin_decimal_value>
The next time L1 collection is scheduled, the set margin is implemented in the plan file.
To collect failed L1 nodes or L1 links, do the following:
Step 2 Enter into configuration mode:
Step 3 From the Network Service Module setting options, set the
compute-inactive-links
option to true:
The next time L1 collection is scheduled, failed L1 links and L1 nodes are included in the plan file.