Nieuws

Er is een nieuwe Wandy 4100 controller 19" machine en een Wandy 2011c SoHo router. Deze nieuwe Wandy's zijn ontwikkeld om, net als de 922 en 933 direct op glasvezel aan te kunnen sluiten! Kijk onder het menu producten hierboven naar deze mooie vernieuwing in onze portfolio.

De nieuwe 9xx serie is er! Kijk onder het menu Producten naar deze nieuwe Wandy's.

Onze vestiging in Utrecht is verhuisd naar Strijkviertel 25 in Utrecht / De Meern

Wandy komt met een nieuw type indoor AP voor plafond montage: de Wandy Dome. Zie hier de product sheet van onze nieuwe telg: Wandy M251d

Wandy kan u helpen met uw (glasvezel) internet aansluiting. Uw provider levert u een ultra snelle glasvezel verbinding, maar met het aansluiten in uw (bedrijfs) netwerk helpen zij niet. Wandy kan u daarbij helpen! Wij adviseren graag in de keuze van provider en technische oplossing, zodat u maximaal renement kunt halen uit uw snelle Internet verbinding. Bel ons voor een passende SLA, zodat u niet in de kou staat.

Wandy bouwt ook netwerken voor Voice over IP (VoIP) toepassingen! Veel bedrijven schakelen over op VoIP en lopen daarmee tegen complexe problemen aan. Wandy kan u daarbij helpen. Wij hebben veel ervaring met virtuele netwerken en QoS/bandbreedte management. Bel ons voor veder advies of hulp.

Reggefiber past een nieuw Wandy networking concept toe, om wifi internet access te kunnen bieden in winkelstraten van verschillende steden. Bericht Telecompaper.

Ziggo kiest voor Wandy voor de 5 mei viering in Zwolle. Ziggo sponsort wifi voor de bezoekers van de Zwolse binnenstad.

RCN vakantieparken heeft gekozen voor Wandy om alle RCN-parken in Nederland en Frankrijk van draadloos internet te voorzien.

Defensie en Veiligheidsregio Gelderland ontwikkelen samen met Wandy een nieuwe draadloze oplossing voor op voertuigen. Wij noemen dit nieuwe device de Bridget.

Het Nederlands Scheepvaartmuseum kiest voor Wandy om haar bezoekers een multimedia ervaring te kunnen laten beleven.

Ook voor industri�le oplossingen is Wandy de beste keuze. Kaasfabriek Rouveen heeft al haar heftrucks uitgevoerd met een Wandy client die nooit zijn verbinding verliest! (Interesse? Bel ons.)

In samenwerking met Unica bouwt Wandy het netwerk voor de Floriade in Venlo.

Freshpark Venlo wordt beveiligd door Unica en Wandy.

Voor Ahoy Rotterdam verzorgt Wandy het nieuwe toegangsnetwerk voor publiek en exposanten.  

Heeft u vragen? Bel ons!
Klik hier voor onze contactgegevens

 

 

Dude NMS

 

This manual describes the operation of Dude version 1.0.

Contents

What is the DudeThe Dude is a visual and easy to use network monitoring and management system designed to represent network structure in one or more crosslinked graphical diagrams, allowing you to draw (includes automatic network discovery tool) and monitor your network however complicated it might be. The Dude is capable of monitoring particular services run on the network hosts, and alerting you about any changes in their status. It can read statistics from the device monitored and show you graphs of the monitored values, allows you to test and connect to the devices easily, and provides some very basic RouterOS configuration tools.

It is written in two parts:


System Requirements


Getting Started
When you first start the Dude client, it launches the local server and automatically connects to it. Then you can disconnect and choose another server to connect to. You should remember that the client only works when connected to an either local or remote server.

If you do not have any Dude server running yet, you should start it. There is a button on the top of the application window called “Server”, which has indicator of whether the local server is running (it is green if the local server is running). If you press it, a new window will appear that allows you to start/stop the local Dude server, as well as completely reset its configuration.

When a server is started, you can connect to it pressing the Connect button. There are three connection modes:

Remote connection by default is using TCP 2210 port in regular mode or TCP 2211 port in secure mode, so make sure these ports are not limited by a firewall. The ports may be changed in the server's Global Settings menu. The default username for connecting to a server is “admin” with no password. You can change this later.

Note for Linux users: you should start the Dude from the root user (or delegate some permissions to your regular user), or else the Dude will not be able to ping hosts.

Graphical Interface


The interface has two panes. The first (left) pane is used to select a configuration section, and the second (right) – to display the configuration window. At the top of the selection pane, there are five buttons:

There is a network mini-map at the bottom of the left pane, displaying a scaled-down view on the active map, which can ease navigation on large network maps.

There may be many windows on the window pane. Each of them may be split in two either horizontally (empty left half - ; empty right half - ), or vertically (empty top half - ; empty bottom half - ) using buttons on the top of each internal window. By double-clicking on an entry in the selection pane, the chosen configuration window will be open on the top half of the window pane, zooming the existing windows of the pane to the bottom half. Any configuration pane entry may be dragged-and-dropped onto an existing window or selected with the drop-down list at the top of each window, and the chosen tool will replace the existing contents of the window. The size of any window may be easily resized by moving its borders, in which case all other windows will be zoomed accordingly.


Network Maps
The Dude is created to manage networks graphically, so the main interface to the program is the graphical network representation, i.e. network map. You can instruct the program to detect all your network devices automatically by specifying the IP address range it should scan. The Dude is capable of reading network configuration of the devices that support SNMP protocol, and, thus, is able to make recursively scan the networks connected to the already discovered network devices (up to the specified recursion level). It can even detect “smart” switches and bridges that provide link information over SNMP. You may divide the network into separate interlinked network maps.

There are two mouse cursor modes:

Left click on an object brings up a menu, where you can modify the object properties, as well as run device tools. Mouse wheel is used to zoom in/out the map.

The maps are built with the following objects:

On the map, you can select whether you want to see link diagram (all the network connections), or dependency diagram.
When navigating through a map, if you leave the mouse cursor over a network object for about two seconds, a tooltip will appear, showing some information on that object. Network devices will also have reachability time graphs for each service (like ping time). Submaps will have the list of elements and a map preview shown.
The map may be automatically aligned by pressing the “Layout button”. You can also align some selected objects in line with the the automatic alignment tools:


Device Representation
Each device is displayed as an icon related to a certain device type (fully customizable), which defines the list of services a device should have to be classified to a particular type. The discovery procedure, when adding a device, once detects all the services running on it, consults the device type table.

Each device has the table of all network services once found for the device. You can add and remove new services from any device. The services are constantly monitored, and the ones failed to respond are marked in this list. It is possible to configure a set of "parents" (dependency tree) for a device, so that the device is only monitored if at least one of the parents is reachable. You can set polling preferences (polling frequency and timeout for service probes) and select a notifier (procedure to undertake when the status of any probe is changing, like open a popup window, beep, send an email or execute a program) for each device, as well as for each particular service.

There is history, graphs and some SNMP information available as well.

Configuration

Global Settings


Tools

You may customize the list of tools, which may be executed for a device. These usually include telnet and HTTP access, ping, ftp and so on. You can add new tools, specifying that command to execute. Just like for map object labels, internal variables may be selected and used here.

Some built-in tools can not be deleted. Note: these tools are not used to probe whether a device is alive, but for administrator's convenience to connect or test the devices manually.

Files
List of the files uploaded to the server, like images for network map backgrounds and sounds for notifications. You can also remove files from the server.

Logs
List of all available log threads (and the subentries of this menu let you choose a particular log thread to view). For any particular log thread you can configure, how many lines should be shown (buffered entries), how often to start a new file for the thread and how many files to keep. You can filter only some entries out of a thread by writing a regular expression and pressing [Enter] key or “Apply” button. The regular expressions are saved in the drop-down menu, so you would not have to rewrite complex expressions each time you want to use them.

There are three log threads:

Note: this is different from the “Log files” menu, which shows actual files on disk, whereas this menu shows logging targets.


Probes
List of all available probe types used to check if a particular service is running on a device. The following probe types are available:


Devices
List of all the devices drawn on any of the network maps (type of the devices displayed and map they belong to may be chosen). You can not add devices here (to create a new device, you should place it on a map), just see all of them in a single list, remove them and change their settings (by double-clicking on a device):

Right-click on a device brings up a list of additional options, most notably the device tool list that is easily customizable in the respective control window (select “Tools” from the configuration plane).

All
This list contains all the discovered devices.


RouterOS
This list only contains the RouterOS devices. It displays additional version information for these devices, as well as provice an easy way to upgrade some or all of them.

Group
You can as well group some RouterOS devices into device groups, which make it easies to upgrade a set of routers all at once.

Device types
Device classification types used by the discovery procedure or assigned to some devices manually. Each entry defines how the devices of that type will look like: icon and scaling. “Identification” and “Services” tabs are used only by the discovery procedure to determine whether a device found is of that type, and which services to probe afterwards:

URL, which can be used later as an internal variable, may be specified for each device type.


Networks
List of all network segments places on the map. One network object may have more than one IP network associated to it. You can remove networks and change their settings here, but you can not add anything here. To create a new network, you should place it on a map.

Services
List of all the services present on each device. You can add and remove service probe from any device, as well as change TCP port, probe interval and timeout, and notification type here for each service independently. Service status (up, down or unknown) is displayed for each service listed here. Outages tab contains the log of all events when a service went down.


Outages
Outages table contains the combined log of all probe failures on any of the devices went down and lists whether a service is still down (and for how long time), or the problem has been resolved.


Admin groups
This menu lets you configure access permissions for administrator groups. Permissions are one or more from: read (read-only access to everything), write (change configuration), local (access the server locally), remote (access the server remotely), web (access the server using web interface).


Admins
List of all administrators that have access to the server. Each user must be allocated with permissions given by a admin-group. You can also restrict user access to a particular network.


Active Admins
List of the current user sessions.


Notifications
Notification types executed if a service changes its state (you can select one notifier for a service). Arbitrary applications may be launched on an event with some parameters either on server, or on all the connected clients. Other notification types include sending email, sending a syslog event (to a dedicated syslogd server), showing a popup window, flash the screen, and play a sound (WAW file, which can be uploaded on the server). The hours during which the notification will be active may be set for each weekday, so you may disable it during non-working hours and weekends.


Links
List of all the links drawn between map objects. You can only remove and configure links here, use network diagram to draw them. For each link you may choose the primary device it is connected to (network does not count as a device, so most links will have only one device to choose, but if you connect two devices manually, you will be given that choice), and the type:

Address Lists
You can define address groups that can be used to exclude some addresses from discovery procedure.

Network Maps
Working with the program mostly happen on the network maps, which represent your network graphically. You can add objects manually (the configuration options of each of the possible map object has been described earlier) or run automatic discovery with the following options:

General configuration for a map (accessible with the “Settings” button):


 
Dude as a windows service

This is a general how to, for running dudes as a windows service...
First question: why would you run dudes as a windows service???
Verry simple: dudes is a ideal program for network monitoring, but if you want good network monitoring, you need a server for this. The problem with dudes at the moment is that it requires a user to be logged on, if you log off it terminates dudes. running dudes as a service enables you to have dudes running on one server, and use a client to connect to it. Never again look at your dudes server, it will be running, and doesn't need logging in.

this is how you do it...

Find a copy of srvany (you can get it for free on the MS site) Copy SRVANY.EXE and INSTSRV.exe to your system folder (c:\windows, c:\winnt)
Issue the following command in a dos prompt...

INSTSRV dudes c:\winnt\srvany.exe

This will create a windows service called dudes, but it still doesn't do anything. set it to automatic startup in the service console, in the administrative tools section. also do not enable "Allow Service to Interact with Desktop" this is gives you some enoying windows. Choose your service restart policy, i do a restart service if dudes terminates for some reason.

Now open regedit and go to this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dudes

create a 'Parameters' key under this reg key.

now in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dudes\Parameters create an 'Application' value of type REG_SZ and specify there the full path of your app executable (including the extension). for example C:\Program Files\Dude\dudes.exe

now go to the services console and start you dudes service. use dudesw to open a client console on your server and manage your dudes service... don't forget to enable secure connection to your dudes server so you can use your dudes client to access it from remote... log off your server, and dudes will still be running, monitoring everything.


Appendix A.
Internal variables

Device variables
Set in device properties; available in “Tools”, “Device Types” and “Notifications” menus, as well as in tooltips and labels:


Device type variables
Set in device type properties; available in “Tools” and “Notifications” menus:

 

Service variables


Probe variables
Set in probe properties; available in “Notifications” menu:

Network variables
Set in appearance configuration; available in tooltips and labels:

Submap variables
Set in appearance configuration; available in tooltips and labels:


Link variables

 

 Back to Top