Creating a Collection

Each testable device in a network is called a "target".  A network is represented by a collection of targets that is stored in a single file in XML format.  You can create a collection manually or initiate the collection using the built-in "Wizard".  

Once a collection is created, you can tell PingView that you want it to be loaded and started automatically when the program starts.

Running the Collection

Once a network has been created or loaded from disk, it must be "run" to start testing its targets.  To start and stop the testing of a collection choose the appropriate items from the Actions Menu.

When a collection is started, testing begins with the left-most (highest level) targets.  If a high-level target responds correctly, its lower-level targets are tested in the order of nesting.  PingView uses multithreading is used to speed performance.  When a target doesn't respond within the specified time-out value (a settable collection property), its entry on the main display is shown in red.  When the target has failed to respond for several cycles, the network is considered "down" (non-perational) if the failed target is marked as "vital".

The state of the network can be read from the bottom of the main window, called the "status bar".  At the left is the state of the program.  "Ready" means the collection is ready to be run; "Running" means targets are being tested; "Sleeping" means the collection is paused for its configured "wait" period.  "<no collection>" means no collection is loaded.

The right-hand side of the status bar indicates the state of the network collection.  If it's blank, there is no information yet.  While the collection is running, this area is updated whenever the network status changes significantly.

While a network is running, you can force immediate testing of an individual target by using its context menu (right-click on the target name in the collection pane on the left).  Also, you can force a new test cycle any time the collection is "sleeping" or waiting.  See the Actions Menu for details.

Primary Window Areas

The left-hand side of the main window is the network collection "tree".  The color of each name indicates its status: green is operational, red is failed an grey is untested.  Subordinate elements can be collapsed to hide them.  If you have a lot of targets, use "group" targets to group them and hide them until needed.

The right-hand side of the main window is divided into three parts.  The upper area or "pane" shows the overall status of every target.   The center pane shows the status of the target currently or last selected the left-hand tree.  The bottom pane is the message area showing the recent activity, with the most recent activity listed first (at the top).

Accessing Menus

In addition to the top-level menu items, many PingView operations are controlled with "context" menus.  These menus appear when you right-click the mouse on specific text or in the open area of a window.

Some menu items are disabled while PingView is actively running a collection.  To enable the menus, stop the collection.

Adding and Updating Targets

To add a new target, right-click on the left-hand "tree" or collection pane and choose "Add Target...".  To edit an existing target, right-click on the target's name in the tree pane and choose "Properties...".  (See Target Menu for details.)

Each target is tested using either a standard "ping" (ICMP) message or by attempting to establish a TCP connection.  Most routers, wireless access points, modems and servers support ping operations.  Specialized devices and servers may require testing specific port numbers, which is done by attempting to connect to a specific TCP port (such as port 80 for web (HTTP) servers).

Each target is either at the top level of the collection tree or is subordinate to another target.  Top level targets are always tested; subordinate targets are tested only if their precursor or "parent" targets respond successfully.  You can use drag-and-drop or the "Promote" menu item from the target's context (right-click) menu to move a target to a different parent. 

Each target has a set of properties associated with it. 

 

The "description", "location" fields and "repair action" fields are documention you enter to help problem recogniztion and resolution.

The MAC (Media Access Control) address is only available for devices on the "local loop": that is, network elements sharing the same hub or router as the originating computer.  It is obtained automatically when it available.

As an alternative to using the IP address for local devices, you may enter the Window "machine" or computer name.  The IP and MAC addresses are retrieved and entered automatically.  The "Verify Machine Name" button allows you to test a Windows machine (computer) name and retrieve its IP and MAC addresses.

The "ping" target type can be one of these choices.

Many modern networking components (routers, hubs, modems) are configured and monitored using a built-in web site in the device itself.  PingView allows you to "browse" or navigate directly to the device's management web site.  This "Management URL" is usually based on the IP or doman name field.  In cases where other prototols (such as HTTPS) or special port numbers must be used, you can override the default URL string here.

The "Distance" field is optional and is provided just for documentation and special testing.

Collection Properties

To edit the properties of a collection, choose "Collection Properties" from the Options Menu.  Each tabbed section of this window has a different purpose.  All of this information is stored in the collection file itself (in XML format), not as part of the application configuration.

The collection is stored as a single text (XML) file.  Some of its properties are:

The "Connections" tab is used to set the primary networking options, including timeouts, local subnet IP address ranges and behaviors.

 

The timeout options control ICMP Echo Request ("ping") and TCP session timeouts.

The "Cycles to wait.." checkbox sets how many cycles of "up" or "down" status must pass before the changed situation is reported.  This prevents erratic behavior when networks are in transition.

"Number of worker threads" controls the level of mutiprocessing PingView does.  If you have more than 30 or so targets, you may try increasing this number.

"Cycle time" determines how long PingView sleeps between collection cycles.

The "IP Scan Range" options are used when rescanning the network for new targets.

The "Messages" tab is used to set up the messages that display when the status of the network changes.

These strings are the ones PingView will use when reporting the status of the network.

The "Failure Script" is a batch file or executable that can be executed when the network fails.  Its command line will indicate which vital targets have failed.

The "Sounds" tab is used to set up sounds that play when the status of the network changes.

The "History" tab is used to set up how much history is maintained in the collection while running.

The "Incoming Remote Access" tab is used to configure your PingView collection for remote access as a "PingView Server".

This information allows your PingView instance to operate as a server, delivering copies of updated target collection information to clients anywhere.  (Public use on the internet requires knowledge of router configuration and other factors.)  When your PingView instance needs to either receive requests for its collection or accept collections from remote clients, the PingView Server must be running.  This page configures the password and TCP port number that the server will use.

Each Ping "collection" (target set) is assigned a unique number called the collection GUID.  If you enable incoming remote access your PingView stores a copy of its updated collection at the end of each update cycle.  It can also store copies of collections from other PingViews elsewhere (see below).   These copies are available on request to clients who know the correct password and GUID.

The "Enable remote requests" checkbox indicates that your PingView's server will provide remote PingViews with a copy of the its collection or other stored collections upon request.  These requests originate from "PingView Server" targets on other machines.

The "Enable remote storage" checkbox indicates that your PingView's server will accept remote collection messages and store them.  These are used by "Pushed Client" targets in the local collection.

The "Retention time..." is the number of seconds that a "pushed" collection is held and used before it is considered "stale" or out-of-date.

The "Collection GUID" (Globally Unique InDentifer) is a generated, unique value used to identify each PingView collection.  This value allows PingView to detect endless loops or redundant collections.  It is also used to specify the identity of a remote "Pushed Client".

The "Outgoing Remote Access" tab is used to configure how your collection reports its status to remote PingView Servers.

This tab is used to configure a destination PingView where copies of the collection are sent.  In other words, this information must match the "Incoming Remote Access" configuration of a PingView on another machine.

When the "Enable outgoing..." checkbox is set, a copy of the current collection is sent to the given remote server at the end of each processing cycle.

Problem Notification and Troubleshooting

When a single target fails, PingView checks to see if it's marked "vital".   If so, it begins to count the number of cycles during which the target continues to fail to respond.  Once the preset limit has been exceeded, the notification sounds (and/or scripts) are executed.

One interesting capability of PingView is that it can launch your Internet browser and navigate to the web page associated with a target.  This is useful not only for testing Internet web sites, but many, if not most, of today's end-user network components have a built-in web site that is used to configure and diagnose the device.  Choose "Browse..." from the target menu (right-click on a target name in the left-hand window).

Tracing and Logging

The lower right-hand pane of the main window shows the recent history of the network; usually only significant events are recorded.  To see all PingView activity, set the "Verbose" property of the collection.

In addition to the activity tracing pane, you can set PingView to log all of its activity to a text file. This file is appended with new information whenever PingView runs.  The data can be viewed using the "View Log File" menu item.