Availability Monitoring

Basically everything connected to the network we can consider as a service. If there is some device on the network it always suits its purpose which is exactly providing a service. There are only different methods of checking those services availability.

Event Management

NetCrunch processes events coming from a variety of sources. Some of them may be external like SNMP Traps or Windows Event Log entries and others generated by NetCrunch like Monitoring Events (node state changed) or Atlas Events (like new node discovered).

Network Views

All the network components we want to deal with are contained in the Network Atlas. Some views can represent group of nodes and can be draw as maps, some other represent real time values of performance counters and they are drawn as charts or gauges.

Views can be dynamic - created by filtering rule (sql like query), or can be created manually by picking up nodes.

Program comes with many predefined views like: IP networks, Routing Map, Physical Segments, Servers, Maps with Issues and others, but of course is not limited to them.

**NetCrunch 5** System Requirements
	Minimum	Recommended
Processor	Intel Pentium 4 2.8 GHz or equivalent	Intel Core 2 Duo 2.0 GHz or equivalent
RAM Memory	1 GB	2 GB
Free Disk Space	800 MB	4 GB
Display	1280x1024 True Color	Wide Screen 1600x1050 True Color
Web Browser	Internet Explorer 6, Firefox 2	Internet Explorer 7, Firefox 2
Operating System	Windows XP SP2, Windows Vista SP1 (except Home editions)	Windows Server 2003 x32 or x64

System requirements depend on the amount of nodes monitored - in the case of monitoring more than 500 nodes, a machine that meets recommended system requirements should be used for NetCrunch network monitoring solution.