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.
This chapter describes the WAE Design GUI tools available to discover and retrieve information from router configuration tools and from the Alcatel-Lucent 5620 Server Aware Manager (SAM) server. These tools are useful for capturing and importing network information into the WAE Design GUI.
This chapter gives high-level information on accessing the tools from the WAE Design GUI. These same tools, plus several other offline tools, are available from the CLI and are described in more detail in the references listed in the Related Topics section.
The Parse Configs tool reads a set of Cisco, Juniper Networks, and/or Huawei router configuration files, creates a plan file of the network, and imports it into the WAE Design GUI.
Step 1 Select the File->Get Plan from->Configs menu.
Step 2 Select whether to create a new plan file or add information to an existing plan.
– Update only if the nodes exist in either config files or a plan file.
– Update only if the nodes exist in both config files and a plan file.
– Update only if the nodes exist in config files and do not exist in a plan file.
Step 3 Enter or browse to the name of the directory containing the router configurations to be parsed.
Step 4 Select one or more configuration objects to parse.
Step 5 Select whether IGP is OSPF or IS-IS.
If multiple process IDs exist, WAE Design uses the first one in the config unless you specify otherwise.
If multiple instance IDs exist, WAE Design uses the first one in the config unless you specify otherwise.
Step 6 To set advanced options, click Advanced.
– Loopback interface for Cisco routers is 0.
– Create interfaces and circuits to build a network topology after parsing the configs.
– Create pseudonodes and interfaces for matching circuits for shared media, such as Ethernet LANs.
– Create port circuits to connect LAG ports to remote ports. The match between the two is created in ascending order using a combination of port names and port numbers.
Step 7 To save the imported SAM information as a plan file, select File->Save As.
The Parse IGP tool converts IGP information from router show
commands and imports the IGP database into a new or existing plan file.
Step 1 Select the File->Get Plan From->IGP Database menu.
Step 2 Either enter or browse to one of the following.
Step 3 Select whether to import OSPF or IS-IS database.
By default, WAE Design collects OSPF area 0 LSDB. To import topologies from non-zero area LSDBs, select the All option.
Choose Level 1, Level 2, or both metrics. If you select the Both option, WAE Design combines both levels into a single network, and Level 2 metrics take precedence.
Step 4 Select whether to use DNS to resolve IP addresses (node names) in the resulting plan file. (In the GUI, routers are called nodes.)
Step 6 To save the imported information as a plan file, select File->Save As.
The SAM Get Plan retrieves network topology, as well as current or historical interface traffic measurements, from 5620 SAM servers, and imports it into the WAE Design GUI. The tool queries each router in the discovered network to obtain additional information, such as router name, vendor, and model. It also creates a plan file.
Step 1 Select the File->Get Plan from->SAM menu.
Step 2 In the Access section, specify the following.
Step 3 In the Configuration section, specify the IGP topology discovered by SAM that you want to import.
Step 4 In the Operational Data section, identify whether to include actual LSP paths and traffic statistics in the plan file. The default is to not include them.
– Measurement Window Length (min)—Amount of time over which the traffic is averaged. For example, if this is set to 30, the amount of traffic over a 30-minute time period is averaged. The recommended value is greater than twice the Collection Interval of the accounting policy on the SAM server.
– Number of Measurement Windows—Number of samples being collected. For example, if you enter a 2 here and a 30 in the Length field, you would generate two 30-minute samples.
Step 5 To import the SAM information, click OK.
Step 6 To save the imported SAM information as a plan file, select File->Save As.