Importing Offline Collections

This chapter describes the WAE Design GUI tools available to discover and retrieve information from router configuration tools in WAE 6.x. These tools are useful for capturing and importing network information into the WAE Design GUI.

This chapter provides high-level information on accessing the tools from the WAE Design GUI. These same tools are available from the CLI.

Import Router Configuration Files

The Parse Configs tool reads a set of Cisco, Juniper Networks, or Huawei router configuration files, creates a plan file of the network, and imports it into the WAE Design GUI.

 

381429.tif

Step 1blank.gif Choose File > Get Plan from > Configs.

Step 2blank.gif Choose whether to create a new plan file or add information to an existing plan.

    • For new plans, enter the complete path and plan filename you are creating.
    • If updating an existing plan file, choose how to update nodes.

blank.gif Update only if the nodes exist in either config files or a plan file.

blank.gif Update only if the nodes exist in both config files and a plan file.

blank.gif Update only if the nodes exist in config files and do not exist in a plan file.

 

381431.tif

Step 3blank.gif Enter or browse to the name of the directory containing the router configurations to be parsed.

Step 4blank.gif Choose one or more configuration objects to parse.

Step 5blank.gif Choose whether IGP is OSPF or IS-IS.

    • If parsing OSPF, either use all OSPF areas or choose one and enter its area ID as an integer or IP address. The default is area 0.

If multiple process IDs exist, WAE Design uses the first one in the config unless you specify otherwise.

    • If parsing multi-level IS-IS, choose whether to use Level 1, Level 2, or both.

If multiple instance IDs exist, WAE Design uses the first one in the config unless you specify otherwise.

 

381430.tif

Step 6blank.gif To set advanced options, click Advanced.

    • Enter values for these options, as needed, if you prefer not to use the WAE Design defaults.

blank.gif Ignore BGP ASNs.

blank.gif Loopback interface for Cisco routers is 0.

    • Choose these options, as needed.

blank.gif Create interfaces and circuits to build a network topology after parsing the configs.

blank.gif Create pseudonodes and interfaces for matching circuits for shared media, such as Ethernet LANs.

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

 

381428.tif

Step 7blank.gif Click OK.

Step 8blank.gif To save the imported information as a plan file, choose File > Save as.


 

Import IGP Database

The Parse IGP tool converts IGP information from router show commands and imports the IGP database into a new or existing plan file.


Step 1blank.gif Choose File > Get Plan from > IGP Database.

Step 2blank.gif Enter or browse to one of the following:

    • Directory name containing multiple IGP database files.
    • Filename containing the IGP database. This file is the equivalent of the show command output for Cisco and Juniper routers.

Step 3blank.gif Choose whether to import an OSPF or IS-IS database.

    • For OSPF, choose whether to import OSPFv2 or OSPFv3. Note that OSPFv3 is the protocol that runs in IPv6 networks.

By default, WAE Design collects OSPF area 0 LSDB. To import topologies from non-zero area LSDBs, choose All.

    • For IS-IS, choose whether to import IS-IS for IPv4 or IPv6. IS-IS topologies must be congruent.

Choose Level 1, Level 2, or both metrics. If you choose the Both option, WAE Design combines both levels into a single network, and Level 2 metrics take precedence.

Step 4blank.gif Choose whether to use DNS to resolve IP addresses (node names) in the resulting plan file. (In the GUI, routers are called nodes.)

Step 5blank.gif Click OK.

Step 6blank.gif To save the imported information as a plan file, choose File > Save as.