wktools Version 4 Documentation   (c) 2003 - 2013 by Mathias Spoerr

Table of contents:

  1. General

  2. wktools GUI

  3. Global Functions

  4. ConfigMaker

  5. Configure Devices

  6. IP List

  7. Device Information Parser

  8. Mapper

  9. Scheduler

  10. Wizard

1. General

wktools is a collection of tools which simplify the work with network devices, especially Cisco devices. At this time there are the following tools included:

Configmaker, IP list, Configure Devices and Device Information Parser.

How to work with these tools is explaned in the following document.

1.1. License

The application is FREEWARE. Use at your own risk.

1.2. Questions and Feature Requests

Please send questions and Feature Requests to wktools@spoerr.org

1.3. Bug Reports

Please send Bug Reports to wktools@spoerr.org

1.4. Using wktools

• Just execute the application - no installation is needed.
• Under Windows, .net is needed. If you get an error when starting the application, please install/update your .net Framework or the Microsoft Visual C++ 2008 Redistributable Package

1.5. Automatic version check

This feature was added in wktools Version 3.3.0.0.

wktools now checkes if there is a newer version available for download. It establishes a http session to www.spoerr.org and downloads a file with the version information. No other information is exchanged and all traffic is unencrypted.

Due to personal firewalls the version checker sometimes gets no connection and needs to timeout before the tool is startet. For the user it seems that the tool is not working. If this is the case for you, please disable the version check function in the Settings.

1.6. wktools.xml

All settings and tool profiles are saved in wktools.xml, which must be located in the same folder like wktools.exe.

2. wktools GUI

2.1. GUI layout

2.2. Toolbar

	Load File - Only available for Scheduler to load a Scheduler File
	Save Log output to file; For Scheduler it's used to save the Scheduler table
	Copy selected Log window output to clipboard
	Paste clipboard to Log window
	Cut selected Log window output
	Delete Log Output
BOX	Profile Selector DropDown Box Select or fill in the Profile name to load/save/remove.
	Load selected Profile Choose the profile to load in the drop down box
	Save Profile Write the profile name into the drop down box or select an existing profile to overwrite it.
	Remove Profile Delete the selected profile.
	DeviceGroup Refresh - Only available for Configure Devices; Load Device Group Table; Prerequisite to start Configure Devices
	DeviceGroup Save - Only available for Configure Devices; Save the displayed DeviceGroup Table into the specified file.
	Start/Stop Tool Select to start; unselect to stop
	Kill Tool - Use with caution.
	Settings
	XML Switch: Switch between the local and global wktools Config Files. The global Config can be specified under Settings.
	Host Search - Search for a host and to which switch it is connected to.
	MAC DB Update - Update MAC OUI Database; This will take a some minutes; The data is then used for the endpoint reports and for the Host Search Result.
	Detailed Log/Error Log - Select for Error log only; unselect for Detailed Log

2.3. Tool Selector

	wktools - General information
	Wizard: Quick Start for the most used operations.
	ConfigMaker: To simply generate many similar files/configurations. There are two data sources needed to achieve this: A pattern file and a data file.
	Configure Devices: To push/collect information to/from a network device. Supported protocols are Telnet, SSHv1+2, HTTP+S and Serial Console.
	IP List: To find and store IP addresses in config files.
	Device Information Parser: To parse Text files with "show" output from Cisco devices for Serial numbers, Module Information... - Very useful for making an inventory of your Installed base.
	Mapper: Generate network maps in Visio vdx format. Data sources are STP infos, CAM Table, ARP table, Interface infos and if available cdp neighbor infos.
	Scheduler: To schedule Tasks/Tools at a specified time or start one or more tools at one time.
	About - General information.
	License - End User Agreement

2.4. Tool Settings

To specify the Tool specific settings. Each setting is described in detail below.

2.5. Log Window

All output of wktools is written into this window. Please use to toggle between "Full Log" and "Error Messages only" views. A documentation of all error messages is available here.

2.6. Tool specific output

This section is differenty used from each tool. ConfigMaker uses it to display the Data File, Configure Devices shows the DeviceGroup File and DeviceInformation Parser diplays the result. The Scheduler lists all configured items.

2.7. How to use the GUI

This section is differenty used from each tool. ConfigMaker uses it to display the Data File, Configure Devices shows the DeviceGroup File and DeviceInformation Parser diplays the result. The Scheduler lists all configured items.

3. Global Functions

3.1. CLI Options

It's possible to start wktools with some parameters to automatically load a profile or start a tool or disable the GUI...

SYNTAX: wktools [-s] [-S] [-h] [-t tool -p profile]

3.2. Settings

4. ConfigMaker

With this tool you can generate configuration files in a fast and easy way. To achieve this, two files are needed: A Template and a Data file. The variable parts are represented by a placeholder like $var in the Template. The data file includes the placeholder names and appendant values.

The output can be stored in two ways:

• A separate file per Data file line
• One file for everything

4.1. Data File Format

• All placeholders must be in the first line. With the "Non standard format" option everything till the first character of the "Filename Variable" string is ignored (This character is used to mark the bgeinning of the file).
• The very first character of the file is the placeholder identifier, for example a "$" sign.
• Placeholders must not include the following chars: ENTER SPACE /,.;:_-\|()[]{}<>
• The data is separated by a user editable char (default: ";") and ENTER at the end of the line
• No Spaces are allowed between placeholders
• All records for one file have to be in the same line
• All lines have to be separated with ENTER
• All of the above statements are true, even if the "Use Separator as Placeholder End" option is used

If the file is generated with MS Excel and line breaks within a cell are used, please check the "non-standard format" Checkbox. In this case, all "sub-linebreaks" are replaced by " // " and the existing Data file is overwritten with the new data to get compliant with the tool.

If you use Linux, line breaks within cells are not supported, since LF is used for all line breaks. In Windows, line breaks within Cells are marked with LF, while "global" line breaks are marked with CRLF.

4.1.1. Data File enhancements

4.1.1.1. non-standard format

Sometimes it is needed that Line breaks within cells are used in Excel sheets. In this case the line breaks are converted into csv with a LF character. A line break at the end of a line is specified with CR/LF. The LF onlys are now replaced with the string specified at the "Replace LF" option.

4.1.1.2. Flexible Data File

In this case the LFs described under 4.1.1.1. are used to separate data entries. Each entry is only used once. For an example see the Tutorials at www.spoerr.org/wktools.

4.1.1.3. Use Tags

Tags are specified with two beginning placeholder identifiers - i.e. $$n. With tags you can add Linebreaks or copy entries several times. To get an idea when to use this option (in conjunction with 4.1.1.2.) is, when generating Firewall object-groups where the number of entries could vary for each device.

Possible tags ($ is used in this example as placeholder indentifier):

• $$n: Linebreak
• $$t: Tabulator
• $$s: Space
• $$b: Begin
• $$e: End
• $$i: Number of copies of the string between $$b and $$e

4.1.2. Simple Example

Data and placeholders in tabular format:

Needed format:

    $hostname;$lip;$dlci;$sip
    host1;10.1.1.1;100;10.1.2.1
    host2;10.2.1.1;101;10.2.2.1
    host3;10.3.1.1;102;10.3.2.1 
	

NOTE: This example also applies to the scenario when "Use Separator as Placeholder End" option is used.

4.2. Format of the Template File

Placeholders must be separated by the text with one of the following chars: CR SPACE /,.;:_-\|()[]{}<>

This statement is false when using the "Use Separator as Placeholder End" option.

4.2.1. Example

    hostname $hostname
    !
    interface Loopback0
     ip address $lip 255.255.255.0
     no shutdown
    !
    interface Serial0.$dlci point-to-point
     ip address $sip 255.255.255.252
     frame-relay interface-dlci $dlci IETF
    !
    ...
	

4.2.2. Example when using "Use Separator as Placeholder End" option

Additional Separator: ";"

    hostname $hostname;
    !
    interface Loopback0
     ip address $lip; 255.255.255.0
     no shutdown
    !
    interface Serial0.$dlci; point-to-point
     ip address $sip; 255.255.255.252
     frame-relay interface-dlci $dlci; IETF
    !
    ...
	

4.3. ConfigMaker Settings

5. Configure Devices

With this tool you can automatically configure Cisco IOS, CatOS and PIXOS devices. Aside these boxes also Linux with the following prompt ending is supported: "$ ".

The supported protocols are Telnet, SSHv1+2, HTTP+S, CLI and Serial Console. This protocols can be combined with one of the following connection types:

• SingleHop: A separate connection to each Host. All connections are handled one after another.
• MultiHop: One or more hosts are used as entry device. From the last "entry" the true devices are configured. The initial connection is used until all devices are configured.

Note: MultiHop: Don't forget "exit" at the end of the configuration file, because it is not sent per default!

When using the serial console, only MultiHop is supported, since one of the COM Ports is used as first Hop from which all others are configured.

When using the SSH, SSHv2 is always used first. When SSHv2 fails, SSHv1 is tried. Note:Since only one SSH is available anymore, there is a mismatch in the protocol index compared to older versions. If you have saved profiles with http or https, the profile needs to be edited.

When using HTTP or HTTPS, all output is saved in a file. The config file must contain the urls to request. When using an empty config file, "ip-address/" is downloaded and saved. Since wktools Version 4.6.0.0 it is possible to enter more than one URL.

CLI gives the ability to execute shell commands and save the output to a file. This may be helpful with commands like "curl" or "wget".

If there are "show" commands in the configuration, the output is stored in a file. The filename is either the Hostname or the IP address of the device. It's also possible to save the whole output in one file.

Note: "show" must be written out in full! Otherwise the output will not be saved.

The devices can have different configuration files and/or Username/Passwords. For different Usernames/Passwords there are two possible methods:

Software upgrade for IOS devices is supported. The configuration file must include the following lines:

     copy tftp flash:
     1.1.1.1
     test.bin
     test.bin

5.1. DeviceGroup File

With Version 3.1 a new feature was added: Device Groups. This feature allows you to define the whole dynamic information within one csv file. If the DeviceGroup file is not specified, the Tool generates its own file. The information used to configure the devices is displayed in the Tool specific outout window. The data format is a List. In front of each entry is a checkbox to select the Hosts for the next run - only checked lines are used.

Each entry in the list can be edited and new lines can be added. The information provided in the list is the data basis for configuring the devices. The list is temporarily stored in "tempDevGroup.txt".

The Configuration File can be viewed by right clicking the config file name in the Device Group and using the "Show Config File" option in the popup menu.

If the Device Group data is generated by the tool, the settings in the "Settings Tab" change to "Use Device Groups" and the temporary DeviceGroup File is added to the Settings Panel.

Note: The first element in the table must be checked when using MultiHop. The used protocol in all lines must be the same for Multihop. The used protocol for connections from the first device is specified under "Multihop Command" setting.

5.1.1. DeviceGroup File Format

• Comma Separated file with semicolon (;) as Separator
• "ENTER" at the end of each line
• If one subitem is not needed, use two semicolons right after another
• Eleven columns:

5.1.2. Example

    x;1.1.1.1;user1;lopw1;enpw1;conf1.txt;Telnet;;;telnet $ip;host1; 
    x;1.1.1.2;user2;lopw2;enpw2;conf2.txt;COM1;;;telnet $ip;host2;
    x;1.1.1.3;user3;lopw3;;conf3.txt;SSHv1;;;telnet $ip;host3; 
    x;1.1.1.4;user4;lopw4;enpw4;conf3.txt;SSHv2;;;telnet $ip;host4; 
    x;1.1.1.5;user5;lopw5;enpw5;conf5.txt;Telnet;;;telnet $ip;host5; 

5.2. IP Address File Format

• The addresses can be either IP addresses or DNS names
• The addresses must be separated with one of the following chars: ,;ENTER
• It is possible to enter remarks at the end of the line (See 6.2.1 for an example). These remarks will be taken over to to the Remark column of the DeviceGroup File.

5.2.1. Example

    1.1.1.1; host1
    2.2.2.2;
    3.3.3.3; host3

5.3. Configuration File

• The configuration file has no special format
• Exception: Dynamic Username/Password are included
• In case of dynamic configuration files and/or dynamic Username/Passwords the filename has to be the IP address or DNS name of the device.
• It is also possible to specify a default configuration file which will be taken when no special file is found.
• Two Config Templates are available. These templates are helpful for the "Device Information Parser". One template is for the Inventroy Parser and the second one for the Interface Parser. Use the "Config Option" drop-down Menu to select the template to be used. The commands used in the templates can be found in section 7.1.2 of this document.

5.3.1. Example of a config file with dynamic Username/Password

     !user = username           -> Username
     !lopw = login password     -> Login Password
     !enpw = enable password    -> enable Password
     !
     conf term
     logging buff 8000
     exit
     wr
     show run                  -> running configuration will be stored in file
     show version              -> show version output will be stored in file
     exit

5.3.2. Use of regular expressions as part of commands to complete them during runtime.

wktools4 supports regular expressions in commands. This feature allows you to complete specific commands during runtime. The regex is applied to the retur traffic of the previous command. The first match replaces the regex in the command.
Use [rgx] and [/rgx] tags to mark the regex. More than one regex may be used in a single command.
Here are some examples for the usage:

     conf t
     int lo 999
     do show ip interface brief
     ip address 10.10.[rgx](?<=FastEthernet1/0            192\.168\.)[0-9]+[/rgx].1 255.255.255.0
     do show run | i hostname
     description *** [rgx](?<=hostname )\b\w*[/rgx] ***
     no shut
     end
     exit

First expression: The 3rd octet in the IP address is looked up via the regex in "show ip interface brief" and the 3rd octet value from the IP address from Fa1/0 is used. The command, which is actually used, would be for instance: "ip address 10.10.56.1 255.255.255.0".
Second expression: The hostname, which is looked up from "show run | i hostname", is used for the interface description.

Sample 2: AAA server IP changed from 10.1.1.1 to 10.1.1.2 and the key is different on each device and the old key should be re-used...

     sh run | i tacacs-server host 10.1.1.1
     !IFRETURN (?<=10.1.1.1 key )[0-9]*.[a-zA-Z0-9]+
     #[rgx](?<=10.1.1.1 key )[0-9]*.[a-zA-Z0-9]+[/rgx]
     !ELSERETURN
     !EXIT
     conf t
     aaa accounting commands 1 default start-stop group tacacs+
     aaa accounting commands 0 default start-stop group tacacs+
     tacacs-server host 10.1.1.2 key [rgxMem]0[/rgxMem]
     no tacacs-server host 10.1.1.1
     exit
     wr mem
     exit

First expression: Reads the existing key from 10.1.1.1; If a key is returned, it is saved. Otherwise exit is sent to the device and nothing is changed.
RGX Memory: Each time a regex is used (with [rgx][/rgx], it is saved. The first time it is saved on position 0, the second time on position 1... The saved value can be recalled at any time with the [rgxMem]nnn[/rgxMem] option. The saved values are available until exiting the device.

5.3.3. Variables available in config files for CLI.

The following variables are availible for use in config files, but only for CLI mode:

• $$ip$$: IP Address/DNS Name
• $$port$$: Port
• $$user$$: Username
• $$lopw$$: Login Password
• $$enpw$$: Enable Password

5.4. Configure Devices Settings

5.4.1. DeviceGroup Settings

5.4.2. Host & ConfigFile Settings

5.4.3. User/Password Settings

For more information on how to use more than one Username/Password, please refer to 5.

5.4.4. Connection Settings

5.4.5. Output Settings

5.4.6. Advanced Settings

5.4.7. Debug Options

5.5. Special Config Tags

	conf t
	do show int statu | i ( 60 )
	!RGXBLOCK ^[a-zA-Z]+[0-9]+\/[0-9]+\/[0-9]+
	int [regex]
	switchport access vlan 61
	exit
	!RGXBLOCK
	end
	wr mem
	exit
		

!cmd-prefix CMD: 
show running-config

6. IP List

Use this tool to search configuration files in a directory, including sub directories, for IP addresses of a specified Interface. The result will be stored in a file.

The files to search can be restricted using search patterns for the file name.

A second option would be to scan IP address ranges for open ports (22, 23, 80, 443) and store the result in a file. Only the first open port is documented. This file could be used as input for "Configure Devices". The Port information will also be used.

The tool first tries to ping the remote host and then scans for open ports. The icmp echo operation only works, when the tool is started with Admin/root privileges.

6.1. IP List Settings

7. Device Information Parser - OBSOLET AND REMOVED

NOTE: No more maintenance is done for this tool. Use Mapper instead. The tool will be removed in one of the next releases.

This tool parses text files with show output from Cisco devices. Currently there are two parser implemented:

• Inventory Parse
• Interface Information Parser

7.1. Inventory Parser

• Hostname
• SNMP Location
• Device type
• Chassis S/N
• Memory
• Bootfile
• Softwareversion
• Installed Modules
• S/N of the Modules
• Hardware Revision (Chassis and modules)
• Memory (Chassis and modules, if applicable)
• PIX/ASA License Information
• Flash size

7.1.1. Supported Devices

7.1.1.1. Cisco Router

• 7600 with Sup720
• GSR (12008)
• 7200VXR
• 7304 NSE
• ASR 100x Router
• ISR x8xx Router
• 3600
• 7500
• 25xx
• 26xx

7.1.1.2. Cisco Switches

• Catalyst 3500XL
• Catalyst 3550
• Catalyst 3560
• Catalyst 3750
• Catalyst 3750 Stack
• Catalyst 4500 IOS
• Catalyst 2900XL
• Catalyst 6500 IOS
• Catalyst 2950
• CatOS based Switches

7.1.1.3. Cisco Other

• LS1010
• AS5300
• 6260 DSLAM
• IOS Access Points
• PIX, ASA, FWSM
• Cisco IP phones - information is collected with http or https

It may work for other IOS or CatOS hardware but there is no guarantee for it. If you have problems with any kind of IOS/CatOS hardware please send an email to wktools@spoerr.org.

7.1.1. Format of the file to parse

7.1.2.1. Template for all devices except 6200 DSLAMs

     show ver           ! Version Information
     show snmp          ! Location Information
     show module        ! Module Information for CatOS Devices
     show c7200         ! NPE Information for 7200 routers
     show diag          ! Module Information for IOS devices
     show invent        ! Module and Chassis Information for IOS devices
     show hardware      ! Module Information for LS1010 devices
     show system        ! Powersupply Information for CatOS devices
     show file system   ! File system Information for getting flash sizes
     exit

7.1.2.2. Template for 6200 DSLAMs

     show ver
     show harware chassis
     show hardware
     show hardware slot x   ! where x is the Slotnumber (Information for all Slots should be collected)
     exit

7.1.2.3. Cisco IP Phones

7.2. Interface Information Parser

With this Parser you can collect interface status information like sent/received Packets or Bytes or Interface errors. At this time only IOS devices (routers and switches) are supported.

The output will be comma separated file (.csv) with ";" as separators.

The information the parser uses to collect the statistics is from "show version" and "show interfaces" output. The output of each device has to be stored in a separate file and the output of both commands must be collected. Otherwise the Parser will fail.

7.3. GUI explanation

8. Mapper

The Mapper tool automatically draws a network map in Visio vdx format. Data sources are STP infos, CAM Table, ARP table, Interface infos and if available cdp neighbor infos.

The needed information can be collected by wktools or any other tool.

Supported devices: Cisco IOS Devices (router, switches, WLAN...); Cisco Nexus Switches; Cisco PIX and ASA Firewalls; Cisco IP Phones

There is a Lua Interface available to import custom parsers for unsupported devices. Please see this ducument for more information and API documentation: wktools4 Mapper Lua API

8.1. Mapper - HowTo

Two steps are needed to get the Visio drawing: Collect the needed data and then parse analyze it. The second part is done by Mapper. For the first step you can use wktools - Configure devices or a third party tool. The output of the following commands is needed. Please watch the order of the commands in case you use a 3rd party tool:

show version
show interface
show arp
show mac-address-table
show spanning-tree detail
show cdp neigh det
show ip arp
show mac address-table
show vpc
show ip route | excl B |Null0|connected
show ip bgp sum
show ip ospf neigh det
show ip eigrp neigh det
show crypto ipsec sa
show ospf neigh det
show eigrp neigh det
show route | excl connected|Null
show switch virtual link port
show snmp
show spanning-tree
show interfaces switchport
show module
show c7200
show diag
show inventory
show hardware
show system
show file system
show power inline
show ip route vrf all
show vrf interface
show ip vrf detail
show ip arp vrf all
show failover
show fex
show ip ospf
show ip ospf interface
show ip bgp neighbors
show ip route vrf xxxx
show ip arp vrf xxxx

For Cisco IP phones the following pages are needed:

DeviceInformation
NetworkConfiguration
PortInformation?1
DeviceInfo
NetworkCfg
NetworkInformation
DeviceInformation
WLANStatistics
localmenus.cgi?func=604
localmenus.cgi?func=219
localmenus.cgi?func=601

8.1.1. Collect the needed data with wktools

Step 1: Create new profile in Configure Devices with the following settings:

• Hostfile: File with the IP addresses of the devices, which you wish to have in the graph; See 5.2 for more information about the file format.
• ConfigFile Option: Mapper
• User/Password settings: Define the User to use to connect to the devices
• Modus: Select the needed protocol to connect to the devices
• Type: SingleHop or MultiHop -> See 5.4.4 for more information
• Show Output: Select either IP address or Hostname; See 5. for more information
• Log File: Logfile
• Output Directory: Directory, where the collected data is saved

Step 2: Press "DeviceGroup Window Refresh" Button

Step 3: Select all devices for which you want to collect the data

Step 4: Press "Start" Button

Step 5: Wait till Configure Devices ends and view the report if everything was ok

8.1.2. Mapper - HowTo

Define Search Directory, Output File and the needed options. Then press Start. After Mapper finished, open the .vdx file and do the needed fine-tuning.

Click here for a Mapper HowTo (only in German)

8.1.3. Mapper - Import devices

If you want to see Non-Cisco and Non-cdp devices in the network map and/or Report, use the import function. It is applicable for end-systems, but not for network devices.

File format:

• One line per device
• Contents: hostname;ip-address;mac-address;interface-name;location;type;model;s/n;
• hostname: Hostname of the device (mandatory)
• ip-address: IP Address of the device
• mac-address: MAC Address of the device; Either IP or MAC address must be available.
• interface-name: Interface name
• location: Additional information for the device location (only for your information); Displayed in the shape data
• type: device type. The following types are available; Default is 12
• 1 -> Router
• 2 -> Switch
• 3 -> Firewall
• 4 -> Accesspoint
• 6 -> VoiceGateway
• 11 -> Phone
• 12 -> End-system
• 13 -> ATA
• 14 -> Camera
• model: Additional information on the device type (only for your information); Displayed in the shape data
• s/n: Additional information on the device Serial-number (only for your information); Displayed in the shape data

Example:

Test-1;10.1.1.1;;;Test-Location-Rack1;12;testdevice_1;1234567890;
Test-2;;1234.5678.90AB;;Test-Location-Rack2;12;testdevice_2;9922334455;
Test-3;10.1.1.3;1111.2222.3333;Intf23;Test-Location-Rack3;12;testdevice_2;5676432456;

8.2. Symbols used in the Visio output

8.2.1. Systems and Networks

8.2.2. Interfaces

8.3. GUI explanation - Mapper Settings

8.4. Important Notes

8.4.1. General

• Visio Bug: There is a bug in Visio that sometimes the links between the shapes are hidden.
  Workaround: Select all shapes (Ctrl+A) and move them some pixels.
• Only Interfaces which are up/up are displayed.
• Detailled information is stored in the „Shape Data“: Right Click on a Shape -> Data -> Shape Data

8.4.2. Spanning Tree

• STP status per VLAN and interface is only recognized when BPDUs are received on this interface. This means that an interface may be forwarding for a VLAN, but is not shown in the shape data.
  -> If there are no STP speaking neighbors for a specific VLAN on an interface, the VLAN is never shown in any shape data.
• "root forwarding" and "designated forwarding" are not differentiated - it's all "forwarding"

8.5. Host Search and MAC DB Update

8.5.1. MAC DB Update -

Press the MAC DB Update Toolbar Button to download the latest version of the IEEE OUI listing (http://standards.ieee.org/develop/regauth/oui/oui.txt) and import it to wkm.db. The data is then used for additional information for "Host Search" and seeveral Reports.

8.5.1. Host Search -

To look up end-systems in your network. You can either search for the MAC address, IP address, or Switchport to see where a device is connected to. The data source is wkm.db, which is filled during Mapper Parsing. The result is written to the Result Text-Box and the global Log-Window.

9. Scheduler

9.1. GUI explanation - Task List

9.2. GUI explanation - Scheduler Settings

9.3. Task Types

9.3.1. On-Demand Tasks

9.3.2. Scheduled Tasks

Scheduled tasks are activated and stored as Windows task by clicking the "Start" Button. All saved Windows Tasks are listed in the "Scheduled Tasks" window:

Click Start, click All Programs, point to Accessories, point to System Tools, and then click Scheduled Tasks.

Please specify Username/Password in the Settings section. This account information is used to create and run the task.

10. Wizard

Quick Start for the most used operations: Draw Network Map; Collect Inventory; Config Backup

No need to configure each tool separately if standard options are sufficient. The settigs are saved in each tool, so they can be re-used later.

10.1. GUI explanation

wktools Version 4 Documentation   (c) 2003 - 2013 by Mathias Spoerr