Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Text Mode

  1. Open a console window or a telnet window to the NorthStar Planner server. If you are not already the NorthStar Planner user, switch to the NorthStar Planner user. For example, if user ID is wandl, type in “su - wandl” and enter the password.
  2. Type /u/wandl/bin/getipconf to see the command options:
  3. Run the program /u/wandl/bin/getipconf with the appropriate command-line variables. For example, if your configuration files all have the “.cfg” suffix, then type in the directory containing your configuration files:$ /u/wandl/bin/getipconf *.cfg

    Refer to the tables above for other corresponding command-line options available. Running getipconf in the command line offers more options. These are listed in the table below.



    -ospf ospfdatabase (Cisco and Juniper)

    This uses the OSPF database for topology information. The CLI command used to retrieve the OSPF database is: show ip ospf database (for Cisco) and show ospf database router extensive (for Juniper).

    This option is also available from File > Import Data wizard, Import Type, “OSPF Database”.


    This option is used for performance issues. This option will cause interfaces that are “ip unnumbered” to be ignored.

    -baseIntf baseIntf, -deltaIntf deltaIntf

    These options are used for performance issues when importing a large set of config files, and are normally not modified. baseIntf (default=8192) controls the base hash table size. deltaIntf (default=2048) indicates the delta size by which the hash table should be increased after the hash table capacity has been reached.


    This uses IPv6 addresses for link stitching. The default is not to use IPv6 for link stitching.

  4. Log onto the NorthStar Planner client and go to the directory containing the getipconf output files.
  5. Open the newly created specification file and perform Layout>Recalculate Layout from the right-click menu of the map.