• No results found

Running custom scripts which allow you to remotely and securely run a script you wrote on Windows, Mac, Linux, and Unix devices.

N/A
N/A
Protected

Academic year: 2021

Share "Running custom scripts which allow you to remotely and securely run a script you wrote on Windows, Mac, Linux, and Unix devices."

Copied!
183
0
0

Loading.... (view fulltext now)

Full text

(1)
(2)

About Foglight NMS

Foglight NMS is a comprehensive device, application, and traffic monitoring and trou-bleshooting solution. It is capable of securely monitoring single and multi-site networks of all sizes, from small corporate LANs to large enterprises or highly distributed environments. You can install and configure Foglight NMS in minutes, which will then automatically start dis-covering system resources and their metrics, including hardware, operating systems, vir-tualization, databases, middleware, applications and services.

Key features of the product include:

l Monitoring applications where you can view the performance of an application and iden-tify issues which may help you prevent an application from failing.

l Dashboards that you can manage and customize to display information about your sites' networks, such CPU load, memory, disk space utilization, network interface traffic, net-work latency, and packet loss.

l Analyzing network traffic to identify patterns and usage, which will allow you to deter-mine how traffic impacts the overall health of a network through real-time packet cap-ture.

l Running custom scripts which allow you to remotely and securely run a script you wrote on Windows, Mac, Linux, and Unix devices.

l Creating alerts and notifications that automatically notify you when there is a network performance issue, allowing you to resolve it before it impacts your sites' networks.

(3)

These features are new to Foglight NMS in this release.

Global Policies

A policy defines how you work with the information collected from your devices. Global Policies work very similar to local policies with a few exceptions. With global policies you can: view all policies across a site and change any setting on an individual device without applying that change to all the devices in the policy.

For more information on the new Global Policies feature, seeOverview of Global Policies.

Creating Custom Reports

Any data that PacketTrap collects from the devices in the network can be shown in a report. Using the custom reports feature, you can determine what type of data to show and how to organize it in the report. After you create a custom report, you can generate it, schedule it, send a PDF or HTML version of the report by email, and export it from Foglight NMS to any loca-tion.

(4)

Finding Information

Topics in this section

(5)

There are a variety of documents available online to help you get the most out of your Foglight products, as well as an online version of this help.

You can view the following Foglight NMS documents online:

l Foglight NMS Integration User's Guide.

Go tohttps://support.quest.com/to view this guide.

l API User's Guide

(6)

Contacting Support

Support for Foglight NMS is available to sites who have a trial version of Foglight NMS or who have purchased Foglight NMS.

Visit the Foglight NMS support site athttp://support.quest.com. From the Support page, click the Case Management link. You must create an account or sign in to your account to enter a support case.

From the Support page, you can retrieve solutions from the online Knowledgebase or contact a technical support representative for more information.

You can also contact support in the following ways:

l In the Foglight NMS Studio: Click Technical Support in the Help drop-down menu. l Email:foglightnmssupport@quest.com

l Phone: (949) 754-8000, press option 1 or (800) 306-9329

When you send an email to the Support team, it is recommended that you include "Foglight Net-work Management System" in the subject line along with a brief description of the issue or ques-tion. You should include as many details as possible about the issue, including your contact information, and any other relevant details in the body of the email. Quest Support will create a support ticket and you will receive an email about your case.

(7)

Topics in this section

l How to Set Up Foglight NMS l System Requirements l Adding sites

l Adding Groups

(8)

How to Set Up Foglight NMS

There are a couple of factors that you must keep in mind when setting up your product:

l It is recommended that you assign a public DNS to your product platform server instead of using an IP address.

l Make sure you open the correct outbound and inbound firewall ports. For more infor-mation, click here.

(9)

System Requirements

(10)

System Requirements

This section contains information on the minimum system requirements for Foglight NMS. Before you can begin to download Foglight NMS, you must make sure that your computer meets the minimum system requirements.

Topics in this section

l Things to Consider Before You Install Foglight NMS

l Host Server Hardware and Software System Requirements l Device and Collection Agent System Requirements

l Foglight NMS Studio System Requirements l SQL Server System Requirements

(11)

When you apply Smart Policy assignments to install Foglight NMS with the default monitor set-tings, this basic type of installation will perform well on a Dual-Core system with 4 GB of RAM.

If you adjust the policies to monitor larger networks or use the Network Traffic Flow module, you need to consider which hardware and system configuration you plan to use. As shown in the tables in the following sections, the minimum system requirements are dependent upon the number of devices that you are monitoring.

You must consider the following scalability issues before installing Foglight NMS:

l Number of monitored devices: If you monitor 500 or more devices, you may need to do some performance tuning on your system.

l Amount of data collected for each device: If you increase the number of monitors on a device, a spike in the amount of data collected will occur.

l Changing the default time intervals: If you set a time interval to collect data every five minutes, using a high performance server is recommended to complete the data col-lection in an efficient and timely manner.

l Number of Studio connections: A large number of Studio connections simultaneously accessing the system will impact performance.

To optimize performance when collecting traffic analysis data, it is recommended that you use a dedicated high performance server when the following conditions exist:

l You configure the application to collect Traffic Flow data from multiple routers or switches.

l There exists a large amount of traffic conversations.

(12)

Host Server Hardware and Software System Requirements

See the following table for the minimum hardware and software system requirements for your host server.

When you download a trial version of Foglight NMS, the application comes with an optimized version of SQL CE installed. This optimized version of SQL CE works when you are trying out Fog-light NMS or loading device count installations. However; in your production environment, you must install SQL server Standard or Enterprise Edition.

NOTE: The following minimum requirements apply when you install the default configuration. Significantly increasing the device monitoring intervals and network traffic collection may cause an additional load on the server, which may require you to increase your RAM and upgrade your CPU power.

Host Server System Requirements

Operating System For 32-bit or 64-bit:

l Microsoft Windows 2003 SP2 or later l Microsoft Windows 2008 Server

CPU Dual Core, 3.0 GHz or higher (Recommended)

Memory 4 GB RAM

NOTE: You will need to increase the amount of memory based on the high-volume data that you are collecting, such as netflow, syslog, and windows event logs.

Hard Drive Space 50 GB

NOTE: You will need a minimum of 3 GB of free space to install the SNMP MIB Library.

NOTE: You will need to increase your hard drive space based on the retention settings.

.Net Framework 2.0 or higher

Version 3.5. .NET Framework 3.5 SP1 (Recommended) Firewall Exceptions

-Allowed Programs

(13)

l ptserverservice l ptserverconfig l ptagentservice l ptagentconfig l ptstudio

Ports The following are the firewall rules for inbound connections:

l 5053 (TCP) = (128 AES Encrypted Host Server port) l 5054 (TCP) = Agent deployment CAB file downloads l 5055 (TCP) = (Encrypted Remote Control Tunnel port) l 61 (UDP) – SNMP Trap collector

l 69 (UDP) - TFTP Server l 514 (UDP) - Syslog collector l 2055 (UDP) – NetFlow collector l 6343 (UDP) – sFlow collector

(14)

Device and Collection Agent System Requirements

See the following table for the minimum hardware and software system requirements for your host server in order to deploy device and collection agents on it.

NOTE: When you install a collection agent on Microsoft Windows XP or Microsoft Vista, the lim-ited TCP connections available with these operating systems may impact the monitoring per-formance. It is recommended that you use Windows Server 2003 or Windows Server 2008 when possible.

System Requirements for Device and Collection Agents Operating System For 32-bit or 64-bit:

l Windows Server 2003 SP2 or later l Windows Server 2008

l Windows XP SP2 or later

l Windows Vista SP1 (all versions) l Microsoft Windows 7

l Ubuntu Server 8 l Fedora release 10 l Debian 4.0

l OpenSuse 11.0 l Apple Mac OS® X

NOTE: Windows Server 2003 or Windows Server 2008 is required if you are collecting Syslog, NetFlow, ad SNMP Traps data.

.Net Framework 2.0 or higher

Version 3.5. .NET Framework 3.5 SP1 (Recommended)

Ports The following are the firewall rules for Outbound connections:

(15)
(16)

Foglight NMS Studio System Requirements

You can use the following operating systems and browsers to run the web version of the Fog-light NMS Studio.

l Microsoft Windows (all versions) l Microsoft Internet Explorer 6 or later l Mozilla Firefox 3.6

(17)

See the following table for the minimum SQL Server system requirements.

When you download a trial version of Foglight NMS, the application comes with an optimized version of SQL CE installed. This optimized version of SQL CE works when you are trying out Fog-light NMS or loading device count installations. However; in your production environment, you must install SQL server Standard or Enterprise Edition.

System Requirements for SQL Server

Database For 32-bit or 64-bit:

l Microsoft SQL Server 2005 Standard or Enterprise Editions

l Windows Server 2008 Standard or Enterprise

CPU Dual Core, 3.0 GHz or higher (Recommended)

Memory 4 GB RAM

NOTE: You will need to increase the amount of memory based on the high-volume data that you are collecting, such as Net-Flow, syslog, and windows event logs.

Hard Drive Space

Additional Hardware Requirements for SQL Server

If you choose to run SQL Server on a separate machine from your Foglight NMS server, the fol-lowing requirements apply:

l You must install SQL server on a physical machine. l You must have a minimum of 32 GB of RAM.

(18)

If your machine is collecting traffic and log data, the following minimum system requirements apply:

Additional Requirements

Operating System 2 GB

Perspective Agent Service 1 GB

Perspective Service 1 GB

Additional RAM per Netflow Device(s) NoOfFlowDevices * 300MB

(19)

Because of intense I/O requirements and a high threshold of additional hardware

spec-ifications, installing Foglight NMS on a virtual machine in a production environment is not rec-ommend. You should install Foglight NMS in a testing environment to ensure that you and your colleagues and sites have the best user experience possible.

The following items are the minimum hardware and software system requirements when installing Foglight NMS on a virtual machine (VM).

l Operating System: For 64-bit, both Windows Server 2008 or Windows Server 2008 R2 are recommended; however, you can use Windows 7.

l CPU: Two physical cores dedicated to perspective VM (no hyper-threading core). l Memory: 4 GB RAM.

NOTE: If you install SQL server, you must include an additional 4 GB RAM. l You must provide a minimum of 100Mbs of bandwidth dedicated.

(20)

Adding Sites

When you have new sites, you can create profiles for them in PacketTrap and then run network discovery to discover the devices in their networks.

To create a new site

1. In the Foglight NMS Studio, click New -> site.

2. In the Editor dialog box, type a name and description for the site. This information will appear in the Devices View.

3. Type the host name of the remote site. It is recommended that you use the DNS name of your host; however, you can use the IP address.

4. Click Save.

5. Click Copy URL to download the agent software or click Email URL to send the link to the machine where you want to install the PacketTrap agent on the remote site.

NOTE: Every remote site needs an agent deployed to it. You will be prompted to select a polling agent or to manually install one. A polling agent is the agent the connects back to your platform server. For more information, seeInstalling Agents Manually.

To add devices to your new site

1. In the Devices View, select the new site in the site drop-down list. 2. Click Add New Devices.

3. Go through the screens of the Network Discovery wizard to discover the devices on your site's network. For more information, seeRunning Network Discovery.

See Also

Adding Devices by SNMP

(21)

You can create multiple groups to organize the various types of devices in a network. For exam-ple, you can group similar devices together, such as adding all the desktops in a network to a group called "Desktop".

To add a new group

1. In the Foglight NMS Studio, New -> Group.

2. In the Add a New Group dialog box, type a name for the group.

3. In the Edit Group dialog box, click Add Device Member to start adding devices to the group.

4. In the Select New Device Members, select one or more devices and then click Add. 5. Click Add to finalize your selection and add the devices to the group.

6. Click Save to save your changes.

(22)

1. In the tree view, right-click a group and click Edit. 2. (Optional) Type a new name in the Name field. 3. Click Add to add more devices to the group

OR

Select one or more devices and click Remove to remove the devices from the group. 4. Click Save to save your changes.

To remove a group

(23)

Before Foglight NMS can begin monitoring and collecting data from the devices in a network, you must enable SNMP or WMI. You will need to enable the correct protocol depending on the type of data you are collecting.

Simple Network Management Protocol (SNMP)

Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. SNMP allows you to collect data from all types of devices, such as desk-tops, servers, routers, and switches, across any operating system. When you enable SNMP on a device and provide the correct credentials, Foglight NMS can monitor that device and collect data from it.

For more information on how you can enable SNMP, seeEnabling SNMP on a Device.

Windows Management Instrumentation (WMI)

Windows Management Instrumentation (WMI) is a programming interface (API) in the Win-dows operating system that enables devices and systems in a network, typically enterprise net-works, to be configured and managed. WMI is based on Web-Based Enterprise Management (WBEM), which stores all definitions in a Common Information Model (CIM) database. WMI allows network administrators to query and set information on workstations, applications and networks, and can also be used to access the Active Directory.

Enabling WMI allows Foglight NMS to collect the following specific data from Windows-based devices:

l Microsoft Exchange l SQL

l Active Directory l Windows event logs l Windows services l Hardware Inventory

(24)

See Also

Enabling SNMP on a Device

(25)

When you enable SNMP on a device and provide the correct credentials, Foglight NMS begin to monitor that device and collect data from it. Use the SNMP Enablement tool to enable SNMP on the devices in a network.

1. In the PacketTrap Studio, select one or more devices in the Devices View. You can add more devices to your list by clicking Select Targets.

2. Right-click and then click Tools -> Enable SNMP.

3. In the Enable SNMP Wizard, click Next. Foglight NMS begins to determine if the devices are available for SNMP Enablement and will display the results.

4. Click Next.

5. Select the SNMP credential that you want to assign to the devices. Click the Manage Cre-dential link to add new creCre-dentials to the Encrypted CreCre-dential Store.

6. Click Next.

NOTE: If necessary, you can modify the preferred credential assigned to each device by selecting it and then clicking Set Preferred.

7. Click Next. SNMP is now enabled on the devices. 8. Click Finish to complete the process.

See Also

(26)

Enabling WMI on Windows Devices

For Windows-based machines running Windows XP or Vista, by default Microsoft installs and configures WMI. Before you can start monitoring your devices by WMI, you must make sure that the following services are running:

l Windows Management Instrumentation

l Windows Management Instrumentation Driver Extensions

To enable WMI

1. Go to the Control Panel and double click Administrative Tools.

2. In the Administrative Tools dialog, double-click Computer Management.

3. Expand Services and Applications, right-click WMI Control and follow the Windows menus.

For more information on troubleshooting WMI related-issues on Windows XP, clickhere.

For more information on connecting to WMI remotely on Windows Vista, clickhere.

See Also

(27)

Network Discovery scans the entire network, and then populates your database with the devices that you want to monitor and manage with Foglight NMS. Using various discovery techniques, such as ping and MAC resolution, network discovery provides a complete set of attributes for all devices. Using the data profile created for devices during discovery, Foglight NMS

 automatically assigns them to different policies, known as Smart Policies, that are comprised of monitors that best fit what kind of data you want to collect from the devices.

The Network Discovery Wizard appears shortly after you install Foglight NMS and open it for the first time. However, if you need to add more devices to your database, you can run network discovery again.

To run network discovery from the Studio

1. In the Foglight NMS Studio, click Add Devices.

2. In the Add Devices Wizard, select the method by which you want to add devices:. . l SeeAdding Devices By SNMPfor more information

l SeeAdding Devices by Deploying Agentsfor more information

3. Go through the remaining screens of the wizard to complete the process and click Finish.

Things to Consider Before You Run Network Discovery

Although network discovery detects a device in the network, the data profile that it creates for the device may not be complete because of several factors. It is recommended that you con-sider the following before you run network discovery:

l Enable SNMP or WMI on your devices in order to monitor and collect data from it. You do not need to enable SNMP on devices where an agent is deployed; however, if the agent is monitoring and collecting data from other devices, such as routers and switches, you will need to enable SNMP on those devices.

(28)

l Make sure you have the correct credentials. When you run network discovery, you can only enter one credential at a time for each level of security. So you may have to run net-work discovery more than once to properly discover all devices in the netnet-work. You can also set the credentials for a device at a later time using the Set Credential link in the Devices View. If you do not have the correct credentials assigned to a device in Foglight NMS, Foglight NMS will not be able to monitor and collect data from that device.

See Also

Adding Devices by SNMP

Adding Devices by Deploying Agents Managing Credentials

Enabling SNMP on a Device

(29)

Foglight NMS can use SNMP to discover devices in a network and then provide a complete set of attributes for each discovered device. This type of network discovery will gather technical data including hardware, software, and processes for each device, and then identify devices by responding status, protocols, type, and operating system. When you add a device by SNMP, it requires that you provide the SNMP credentials for the devices and you must make sure that you have the correct port open so that the target machine can accept SNMP packets from that device.

1. In the Foglight NMS Studio, click Add New Devices.

2. In the Add Devices Wizard, select Add Devices Via SNMP Network Discovery. 3. Click Next.

4. In the Enter Targets field, type any one of the following: CIDR, DNS, IP/Subnet Mask or range of IP Addresses.

5. In the Select Network Discovery Techniques section, deselect any of the check-boxes that do not apply to your discovery.

For more information on these techniques and configuring the advanced ping settings, seeNetwork Discovery Techniques.

6. In the Choose Device Credentials section, select a credential for each level of security that you want to use to discover each device.

For more information on credentials, seeSetting Device Credentials for Network Dis-covery.

7. Click Next to start the discovery process.

8. On page 2 of the Network Discovery Wizard, select the devices on which you want to do a complete discovery. You can use the options in the drop-down list to filter the devices shown on this screen.

9. Click Next.

10. On page 3 of the Network Discovery Wizard, select how you want to assign your devices to a policy.

For more information about the Policy Assignment Options, seeApplying Smart Policies to Devices.

(30)

See Also

Running Network Discovery Network Discovery Techniques

(31)

Foglight NMS provides 3 different techniques to help you discover the devices in a network. They are:

Exclude Existing Devices in Database Use this technique if you have previously run network dis-covery. It does not include devices that are currently in the database in you new search, which allows Foglight NMS to scan a network faster.

Ping Use this technique to send an ICMP command to a device. If the ping monitor is working as expected, a device will respond to the request. There are advanced ping settings that you can configure from the Network Discovery Wizard, which is explained further in the following section.

MAC Resolution

Foglight NMS uses the MAC Address to uniquely identify and profile a device in the network.

Configuring Advanced Ping Settings

Foglight NMS provides a way to configure the ping settings so that you can turn a resolution on to display or turn it off from displaying.

(32)

Ping Timeout (ms)

Maximum amount of time in milliseconds that a ping waits for a response from the target IP address. If the target does not respond within the number of milliseconds set, ping assumes it is not working as expected.

Ping Packet TTL (Time-To-Live)

Number of hops along the way to the specified address. If you assign a value of 32 to this set-ting, your ping scan may pass through up to 32 different routers on the way to the remote address before the network throws it away.

Pings Per Node

You can control the number of ping attempts to send to each address during a scan. When a net-work containing a Cisco router is scanned, you should set this number to a number greater than 2. If the target IP address is not in the ARP cache of a Cisco router, the router discards the ICMP query while it requests the MAC address of the target IP. The first ping will never arrive at the subnet of the target IP address; however, the Cisco router will respond to the second ping.

Delay Between Pings

Time in milliseconds between each successive ping to the target address. If you assign a low value to this setting a constant stream of pings is sent to the target IP address.

See Also

(33)

When you run network discovery, selecting the correct credentials is essential in order for Fog-light NMS to access the devices in a network. When a device is discovered during a scan of the network, Foglight NMS will add it to the database. However, if you incorrectly set the cre-dentials for that device (in the product), Foglight NMS cannot monitor and collect data from it.

In the Network Discovery Wizard, choose the correct credential for the devices in the network. Foglight NMS allows you to select a credential for the following protocols:

l SNMP Version 1 Credential l SNMP Version 2 Credential l SNMP Version 3 Credential l WMI Credential

From the Network Discovery Wizard, you can add new credentials to the Encrypted Credential Store by clicking the Managing Credentials link. For more information about credentials, see

Managing Your Credentials.

See Also

(34)

Adding Devices by Deploying Agents

The Deploy Agent Wizard allows you to select one or more devices where you can deploy a local or remote agent. Agents can only be deployed to Windows-based machines running Win-dows XP, WinWin-dows Vista, or WinWin-dows Server 2003. AS you work through the different screens of the wizard, you will select the device where you want to install the agent, determine if SNMP in enabled on the device, learn the status of that device (if it will support an agent deployed on it), set and manage the device's credentials, set the telnet/SSH credentials in order to connect to the device.

For more information about the minimum system requirements the agent device needs to meet, such as which ports you need to open, seeDevice and Collection Agent System Require-ments.

1. In the Foglight NMS Studio, click Add Devices.

2. In the Add Devices Wizard, select Add Devices By Deploying Agents and click Next. 3. In the Deploy Agent Wizard, type a CIDR, DNS, IP/SubnetMask or range of IP addresses in

the Enter Targets field.

4. Click Next.NOTE: This process may take a few moments to complete.

5. In the Connectivity Results screen, select a device in the list.NOTE: Check the Status col-umn for information about the devices that were discovered. If the returned results have a "Fail" status, you may not be able to select that device.

6. Click Next.

7. Select a preferred credential and type a username and password. You can create a new credential by selecting (new credential) in the drop-down list.

8. Click Next.

9. In the Set Telnet/SSH Credential screen, select the device on which you are installing an agent and click Set Preferred.

10. Click Next.

(35)

cific Windows-based data. For more information, seeMonitoring Your Devices by WMI. 13. NOTE: Use the Manage Credential link on this screen to edit your existing credentials or

to create a new credential. For more information, see Managing Your Credentials. 14. Click Next. The agent will now be deployed to the device. You can view the log in the

agent deployment status. 15. Click Finish.

See Also

(36)

Benefits of Deploying an Agent

You will experience the following benefits when you deploy an agent on a machine:

l An agent captures and monitors all data from a machine eliminating the need to enable SNMP or WMI on a device.

l You can use the Patch Management feature.

l You can remotely gain access to a machine using Expert Assist.

l Increase a machine's performance by decreasing the amount of traffic between devices. l Increase the quality of monitored data by missing fewer monitoring intervals than a

SNMP connection.

l Gives you remote access to various mobile assets, such as laptops. l Increase the amount of devices that you can monitor.

See Also

(37)

You can manually deploy an agent on any windows-based machine. When you install an agent manually, you are downloading the agent software from a known location on your Foglight NMS server. Also, you can use the Email URL feature to deploy an agent to all the desktops in a network. By emailing the location of the agent software to each desktop owner, they can down-load the agent software onto their desktops.

1. In the Foglight NMS Studio, click Add Devices.

2. In the Add Devices Wizard, select Add Devices By Deploying Agents. 3. Click Next.

4. In the Deploy Agent Wizard, click Install Manually.

5. In the Manually Deploy Agent dialog, select an operating system and do one of the fol-lowing:

l Click Copy URL to download the agent software from a known location on your Fog-light NMS server.

l Click Email URL to send the location of the agent software to all the desktops in a network.

6. Click Close.

See Also

(38)

Applying Smart Policies to Devices

When you run a network discovery, Foglight NMS creates an intelligent profile of a device and assigns it to a pre-configured policy called a Smart Policy. A Smart Policy is a product default policy made up of recommended monitors and data gathering time intervals appropriate to a specific type of device, such as a wireless device or desktop device. For example, Foglight NMS  assigns a desktop computer to the Desktop Policy, which monitors data specific to desktops such as CPU, memory, and disk volume. Applying Smart Policies during Network Discovery will save you time by automatically assigning all the devices discovered in your site's network to a qualifying Smart Policy.

You can edit Local and Global Smart Policies in the Edit Policy window; however, you cannot delete a Global Smart Policy.

Smart Policies in your product include:

l Default Policy

NOTE: A device is applied to the Default Policy when Foglight NMS cannot identify what type of device it is. For example, during network discovery, if Foglight NMS cannot iden-tify a device's description, OID, or which services are running on it, that device is

assigned to the Default Policy. In the Default Policy, all monitors are selected to cover a wide range of devices to make sure that data is monitored and collected from these devices. It is recommended that you migrate these devices from the Default Policy to the appropriate Smart Policy.

l Networking Policy l Server Policy l Desktop Policy l Wap Policy

l VMware Host Policy

Applying the Default Policy to Devices

(39)

created.

See Also

Overview of Network Discovery

(40)

Updating Your Product

There are two ways this software will update. One approach is manual update and the other approach is auto update.

Manually Updating Your Product

1. From the Foglight NMS Studio main menu, click Administration. 2. In the Administration window, click Check For Updates.

3. Click Update Now to manually apply the software updates. The program will close and then reopen automatically.

Automatically Updating Your Product

(41)

Topics in this section

l Monitoring Your Devices by SNMP l Monitoring Your Devices by WMI

(42)

Monitoring Your Devices By SNMP

Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. SNMP allows you to collect data from all types of devices, such as desk-tops, servers, routers, and switches, across any operating system. When you enable SNMP on a device and provide the correct credentials, Foglight NMS can monitor that device and collect data from it. Foglight NMS uses SNMP to gather much of the device performance information from a network.

If you choose to monitor your devices by SNMP you must first do the following:

l Enable SNMP on all the devices that you want to monitor. l Assign a credential to the device in Foglight NMS.

(43)
(44)

Monitoring Your Devices by WMI

Windows Management Instrumentation (WMI) is a programming interface (API) in the Win-dows operating system that enables devices and systems in a network, typically enterprise net-works, to be configured and managed. WMI is based on Web-Based Enterprise Management (WBEM), which stores all definitions in a Common Information Model (CIM) database. WMI allows network administrators to query and set information on workstations, applications, and networks and can also be used to access the Active Directory.

Similar to SNMP, monitoring your devices by WMI allows Foglight NMS to collect the following data from Windows-based devices:

l Microsoft Exchange l SQL

l Active Directory l Windows event logs l Windows services l Hardware Inventory

(45)
(46)

Monitoring Your Devices by Deploying Agents

You can choose to deploy one or more agents to your site's site for monitoring and collecting data. Agents can be deployed to all Windows, Mac, and Linux devices. Foglight NMS can only monitor devices such as routers, switches, and printers need to monitor by SNMP.

A collection agent is the device responsible for monitoring and collecting data from devices that cannot host an agent, such as a router. You can only deploy a collection agents to a win-dows-based machine. If you deploy an agent to a Mac or Linux device it can only monitor itself and cannot monitor other devices.

NOTE: You do not need to enable SNMP or WMI on an agent machine.

(47)
(48)

Collecting Syslog, NetFlow, and SNMP Traps Data

You must log on to the device to configure it to collect syslog, NetFlow, or SNMP Traps data. When you configure the device, you must tell it to export or send the data to the IP address of the collection agent that is monitoring the device.

Additionally, when you collect Syslog and SNMP Traps data from devices, you must make sure that the Syslog Listener and SNMP Traps monitors are configured for the policy or policies to which the devices are assigned.

Enabling NetFlow

You must enable NetFlow on your devices and configure it to export its data to the collection agent that is monitoring NetFlow.

Opening Ports for NetFlow, Syslog, and SNMP Traps

In order to collect, syslog, NetFlow, and SNMP Traps data, you must make sure that you open the following ports on the devices from where you are collecting this data.

l 514 (UDP) - Syslog collector l 61 (UDP) - SNMP Trap collector l 2055 (UDP) - NetFlow collector l 6343 (UDP) – sFlow collector

l 9555 (UDP) - NetFlow Alternative port #2 collector l 995 (UDP) – NetFlow Alternative port #3 collector

NOTE: You only need to open one port for NetFlow. If port 2055 is in use by another device, you can select an alternate port to open.

(49)
(50)

Using Dashboards to Quickly Diagnose Issues

Topics in this section

l Overview of Dashboards

l Touring the Dashboard View User Interface l Customizing Your Dashboard

l Adding Dashboard Tabs l About Gadgets

l Adding Gadgets to Your Dashboard l Creating Custom Gadgets

(51)

The Dashboard view is a network management dashboard that displays a high-level overview of network performance, fault management, and device availability across all of your sites' net-works. It provides you with critical device information, such as CPU load, network interface traf-fic, latency, and other key performance indicators (KPIs), which can expose devices that are not working as expected and reveal problem areas in a network. You can continuously monitor key assets of a network to make sure that it is always running at peak performance.

In the Dashboard view, you can do the following:

l Monitor device availability, CPU load, memory, disk space utilization, network interface traffic, network latency, and packet loss.

l Perform advanced monitoring of running services, process availability, and performance counters for MS Exchange, SQL, Active Directory.

l Make an inventory of gadgets include charts, gauges, lists, text, and web links. l Compare networks between sites and organizations.

l Create a custom view by dragging and dropping gadgets. l Restore the default dashboard settings.

NOTE: When you select to restore the default settings, all the gadgets and tabs that you created will be deleted from the Dashboard view. The restored default setting includes only the Top-Ten and Alerts and Logs dashboards.

Topics in this section

l Touring the Dashboard View User Interface l Customizing Your Dashboard

l Adding Dashboard Tabs l About Gadgets

l Adding Gadgets to Your Dashboard l Creating Custom Gadgets

(52)
(53)
(54)

The Main Elements of the Dashboard View

1

The Dashboard Menu Tab: Use the main menu tabs to navigate through the product. You can click the Dashboard tab to navigate to your dashboard from any place in the product.

2

Dashboard Menu Buttons: Use the menu buttons for the following: l Adding new dashboard tabs.

l Adding new gadgets to a dashboard.

l Restoring the product defaults to your dashboard. NOTE: This action will remove all gadg-ets and tabs that you added from the dashboard.

l Refresh the data in your gadgets.

3

Dashboard Navigation Tabs: Each tab represents a unique dashboard. Click a dashboard name to navigate to that dashboard.

4

Right-Click Menu Options: Use the right-click menu options to customize the Dashboard view.

5

Divider Bar: The Divider Bar allows you to adjust the size of each column. To activate the divider bar, place your cursor in the space between the columns. Click and hold the divider bar to move the columns left or right.

6

Gadget: The information displayed in a gadget will vary from gadget to gadget. You can do the following in a gadget:

l View the performance and activity of one or more devices in a network. l Filter the data by clicking a column header.

l Edit the way in which data is displayed in a gadget.

(55)

You can customize your dashboard by doing the following:

l Create new dashboard tabs to organize your gadgets. For example, you can create a new dashboard that will display only gadgets that are related to call path data.

l Add new standard gadgets or add custom gadgets that you created. l Edit or remove any of the existing tabs or gadgets.

l Move gadgets around in the Dashboard view using drag and drop functionality. You can also click on the gadget title bar to move it up on a dashboard.

l Resize the widths of columns and gadgets by moving the divider bar left or right.

Every Foglight NMS user can customize his or her own dashboard to fit their needs. The dash-board that you customize will be available to view only by you. Other Foglight NMS users can-not see your customized dashboard.

Dashboard Tab Right-Click Menu Options

You can use the right-click menu options to manage the tabs and gadgets on each dashboard.

l Configure Columns

Defines the number of columns on a dashboard. Existing gadgets on the dashboard are automatically resized based on the number of columns you select.

l Clear Gadgets

Removes all gadgets from the selected dashboard. l Rename Tab

Changes the name of the selected dashboard tab. l Close Tab

Permanently removes the selected dashboard and all the gadgets contained within it.

See Also

(56)
(57)

The Dashboard view offers a wide range of gadgets to present any data being collected about your network. Every gadget takes you through a similar and intuitive configuration wizard that allows you to easily and quickly set one up.

The following table lists all the available gadgets to add and view on a dashboard. Click a gadget name for more information.

Gadget Name Description Location of Gadget

Active Directory Monitors the performance counters for the active direc-tory server.

Application Per-formance

Alerts In Process Displays a detailed list of triggered alerts. Alerts and Logs

Average Latency Chart Displays the average latency of one or more nodes by charting the ping results.

Device Availability

Average Latency Gauge Displays the average latency of a node based on response time and average packet loss.

Device Availability

Average Latency List Displays the average latency of a list of one or more nodes by showing the response time and a color indi-cator bar.

Device Availability

Average Latency Text Displays the average latency of a node by changing the color of the text to green or red.

Device Availability

Configuration Backup Displays the current device configuration file and allows you to compare it to a previous configuration file.

Alerts and Logs

Call Path Jitter Chart Monitors call path jitter via IP SLA on Cisco routers. VoIP

Call Path Latency Chart Monitors call path latency via IP SLA on Cisco routers. VoIP

Call Path MOS Chart Monitors call path MOS via IP SLA on Cisco routers. VoIP

Call Path Packet Loss Chart Monitors call path packet loss via IP SLA on Cisco routers.

VoIP

Call Path Statistics Monitors call path statistics via IP SLA on Cisco routers. VoIP

CPU Chart Monitors the CPU usage percentage of a device. Device Performance

CPU Gauge Monitors the CPU usage percentage and average usage percentage of a device.

(58)

Gadget Name Description Location of Gadget

CPU List Monitors the CPU usage percentage of one or more devices within a network.

Device Performance

CPU/Memory Chart Monitors the CPU and memory usage percentage of a device.

Device Performance

CPU/Memory Gauge Monitors the CPU and memory usage percentage of a device.

Device Performance

CPU/Memory List Monitors the CPU and memory usage percentage of one or more devices.

Device Performance

CPU/Memory Status Monitors processor and memory usage. Device Performance

Device Alerts - Active Displays the alerts triggered for any given device. Alerts and Logs

Device Alerts - All Displays the alerts triggered for any given device. Quest System Info

Device Notes Displays notes about any given device. Quest System Info

Dial Manager ConfigurationDisplays dial manager configuration via IP SLA on Cisco routers.

VoIP

Dial Manager Phone Chart Displays dial manager phones via IP SLA on Cisco routers.

VoIP

Dial Manager Registration Status

Displays dial manager registration status via IP SLA on Cisco routers.

VoIP

Discovered Devices TBD Network Interface

Disk Volume Chart Monitors the disk utilization on a hard drive of a spe-cific device

Device Performance

Disk Volumes Monitors the disk utilization of each drive as a percent of capacity for a device

Device Performance

Installed Applications Displays installed applications via SNMP (some devices will require Telnet or SSH)

Device Performance

IP Configuration Displays the IP Configuration information for a device. Device Performance

IP SLA Overview Displays dial manager registration status via IP SLA on Cisco routers.

VoIP

(59)

Memory Gauge Monitors the memory usage percentage and average usage percentage of a device.

Device Performance

Memory List Monitors the memory usage percentage of one or more devices in a network.

Device Performance

MS Exchange Monitors the performance counters for the MS Exchange server. Application Per-formance Network Ethernet CRC Errors TBD Device Performance

Network Token Ring CRC Errors

TBD Device Performance

Network Interface Chart Monitors the network interface performance for a device.

Device Performance

Network Interface List Monitors the network interface performance for a device.

Device Performance

Network Statistics Sum-mary

Displays network statistics through SNMP. Device Performance

Network Traffic Flow Displays the NetFlow, sFlow, JFlow, and ptFlow traffic for a switch or a router.

Network Performance

Open Source Web Viewer Allows you to choose a browser-based open source net-work management tool or web site to display.

Application Per-formance

Quest Log Information Displays all the log files generated in a single view. Quest System Info

Policy Scheduled Actions Displays all the scheduled actions in a single view. Quest System Info

Running Processes Shows all the processes that are currently running on a device.

OS Details

SNMP Traps TBD Alerts and Logs

Software Inventory Provides a list of all the applications installed on a device.

OS Details

SQL Server Monitors the performance counters for SQL Server. Application Per-formance

Syslog Displays all the collected syslog messages for a specific device.

(60)

Gadget Name Description Location of Gadget

System Information Displays detailed system information for a device. OS Details

Top 10 - Average CPU Usage

Monitors the CPU performance of a list of one or more nodes.

Top 10

Top 10 - Average Memory Usage

Monitors the memory performance of a list of one or more nodes.

Top 10

Top 10 - Average Packet Loss

Displays the average packet loss of a list of one or more nodes.

Top 10

Top 10 - Disk Volume UsageDisplays the highest average disk volume usage as a percentage of drive capacity for a list of devices.

Top 10

Top 10 - Highest Average Latency

Displays the highest average latency of a list of one or more nodes.

Top 10

Top 10 - Network Interface Usage

Displays the highest network interface usage for a list of nodes.

Top 10

Top Network Traffic: Applications

(for one or multiple tar-gets)

Shows network traffic data, organized by application and dependent on the scope that you select when you create the gadget.

Top 10

Top Network Traffic: Convs

(for one target)

Shows network traffic data, organized by conversation and dependent on the scope that you select when you create the gadget.

Top 10

Top Network Traffic: Domains

(for one or multiple tar-gets)

Shows network traffic data, organized by domain and dependent on the scope that you select when you create the gadget.

Top 10

Top Network Traffic: End-points

(for one or multiple tar-gets)

Shows network traffic data, organized by endpoints and dependent on the scope that you select when you create the gadget.

Top 10

Virtual Machines Displays VMware ESX Server virtual machines. VMware

VMware Host Summary Displays a summary of VMware ESX Server host infor-mation.

(61)

VoIP Active Calls Displays active calls through IP SLA on Cisco call man-ager.

VoIP

VoIP Call History Displays call history through IP SLA on Cisco call man-ager.

VoIP

VoIP Phone Status Displays VoIP phone status through IP SLA on Cisco call manager.

VoIP

Windows Event Logs Displays all event logs collected for a device, including application, security, and system event logs.

Alerts and Logs

Windows Services Displays critical windows services information, such as status and start type.

OS Details

Wireless Access Point Displays information about key variables of a wireless access point, such as signal strength and quality.

Wireless Performance

Wireless Access Point List Displays information about all wireless access points on a network.

Wireless Performance

Wireless Clients Chart Shows how many wireless clients are connected to a wireless access point within a given time frame.

Wireless Performance

Wireless Clients List Displays key variables for each client connected to a wireless access point.

Wireless Performance

Wireless Traffic Chart Shows the amount of received and transmitted net-work traffic generated by a wireless device within a spec-ified interval of time.

Wireless Performance

See Also

(62)

Adding Dashboard Tabs

Adding a dashboard tab allows you to create multiple dashboards that you can customize with any of the available gadgets. For example, you can create a dashboard which contains only gadgets that display information specific to routers.

Foglight NMS includes the following pre-defined dashboards tabs:

l Top Ten

l Alerts and Logs

To add a tab

1. From the Dashboard menu, click Add Tab:

2. In the Add Dashboard Tab dialog, type a unique name.

3. Click OK. The new dashboard tab appears at the end of the list.

See Also

(63)

In the Dashboard view, gadgets provide a quick and convenient way to see the performance and activity of one or more devices in a network. When you double-click a device in a gadget, you can view more details about that device.

You can choose to view device information for a single site's network or you can configure a gadget to display information for a device across all your sites' networks.

To add a gadget to a dashboard

1. On the main menu, click the Dashboard tab:

2. In the Dashboard view, select the tab where you want to add your new gadget:

3. Click the Add Gadget button:

(64)

NOTE: You can also double-click a gadget name to open the Gadget Configuration wiz-ard.

5. Follow the steps in the wizard to configure your gadget:

NOTE: Depending on the gadget you select, in the Gadget Configuration wizard you may see different options to configure than the options shown in the previous image.

6. Click Finish.

See Also

(65)

1. On the title bar of the gadget that you want to edit, click the Edit link:

2. In the Gadget Configuration wizard, make your changes. 3. Click Finish to save your changes.

See Also

(66)

Creating Custom Gadgets

You can show certain types of data in a custom gadget. Using the custom gadgets feature, you can determine what type of data to show and how to organize it in a gadget. After you create a custom gadget, you can add it to the Dashboard View.

NOTE: You must be a System Administrator to create a custom gadget. To start creating a custom gadget

1. In the Dashboard View, click Gadget Manager.

2. In the Custom Gadget Template Manager, click Add. Follow the steps below to complete the process of creating a new custom gadget.

Page 1 of the Custom Gadget Template Wizard: What kind of custom gadget is it? 3. In the Custom Gadget Template Wizard, type a name and a description for the custom

gadget.

NOTE: The description appears only in the wizard and not in the gadget itself.

4. In the Display Data By (Group By) drop-down list, select a data type to set the scope of data displayed in the custom gadget. The selection you make here will determine what options appear in the Available Fields section on page 2 of the wizard.

5. Under What Would You Like To Create This Gadget For?, do the following:

l If you want the custom gadget to limit the devices displayed in it to one, select Sin-gle Device

l If you want the custom gadget to display data for all the devices in a policy or all the devices across your sites, select Multiple Devices

l If you want the custom gadget to include all the devices in a site's network, select Devices For Single site

6. For Choose Gadget Type, select how you want to display your results in the custom gadget.

(67)

Page 2 of the Custom Gadget Template Wizard: What and how does the data appear in the custom gadget?

8. In the Available Fields section, select a one or more fields and then click the right arrow button. To add all the fields in a category to the Display These Fields In This Order, select the category check-box.

NOTE: The selection you made in the Display Data By (Group By) on page 1 of the wizard determines what options appear in this section.

9. (Optional) To remove a default field, select the check-box and click the left arrow button. 10. The order of fields in the Display These Fields In This Order section determines the order

of the columns in the gadget. To change the order of a field, select its check-box and click the up arrow button to move its column to the left or click the down arrow button to move its column to the right.

11. Click Next.

Page 3 of the Custom Gadget Template Wizard: How is the data sorted in the custom gadget?

12. To make a data field the primary field by which the rows of data in the gadget are sorted, click Primary. By default, if a field is already set as the primary field, then it will become the secondary field.

NOTE: Sorting the fields on this page does not change the order of the columns. 13. To make a data field the secondary field by which the rows of data in the gadget are

sorted, click Secondary.

14. To make a data field sort from the beginning of the alphabet, the lowest number, or the earliest date, click Ascending.

15. To make a data field sort from the end of the alphabet, the highest number, or the latest date, click Descending.

16. (Optional) Click Defaults to reset the sort order. 17. Click Next.

(68)

See Also

(69)

Topics in this section

(70)

Overview of Credentials

The Encrypted Credential Store is a convenient, protected store of SNMP, WMI, SSH and FTP cre-dentials shared by all tools and gadgets which require them. It uses standard AES 256-bit encryp-tion.

1. Click Credentials from tree options in Devices.

2. In the opened Credential Store dialogue box, click on New.

3. From the drop-down list next to Type select the type of credential protocol you wish to configure and save. The configuration of each of the three choices displayed is described in the following three sections.

4. Click the Assign button to assign the credential to one or many devices. In addition there is an Un-assign button to remove credentials from devices.

(71)

Topics in this section

l Overview of Local Polices l Overview of Global Policies l Adding New Policies

l Editing Local and Global Policies l Applying Smart Policies to Devices

(72)

Overview of Local Policies

A policy defines how you work with the information collected from your devices. It encom-passes devices, monitors, alerts, scheduled actions, and blackout schedules so that any con-figuration changes you make occur from one central location. In a policy you can:

l Create and save permanent policies that are assigned to designated target a single IP or a range of IPs and device groups.

l Define what and how often data is monitored and collected from your devices. l Create custom SNMP monitors.

l Set alerts to automatically notify you when an issue arises or the network's performance declines.

l Schedule an action to fix issues and restore the network to peak performance.

l Disable alerts, notifications, and scheduled actions from occurring during specific times and situations.

See Also

Overview of Global Policies Adding New Policies

Editing Local and Global Policies Removing Policies

(73)

A policy defines how you work with the information collected from your devices. Global Policies work very similar to the Local Policies. It encompasses devices, monitors, alerts, scheduled actions, and blackout schedules so that any configuration changes you make occur from one central location. However, in a Global Policy you can:

l Create cross-site policies. You can assign devices from different sites' networks to a sin-gle policy.

l You can change a setting for an individual device without applying that change to all the devices in the policy.

See Also

Overview of Local Policies Adding New Policies

Editing Local and Global Policies Removing Policies

(74)

Adding New Policies

In addition to the built-in Smart Policies, you can create your own policies to manage data col-lected from your sites' networks.

1. In the Foglight NMS Studio, click New -> Policy.

2. Click OK. When the Policy Editor window appears, by default the Device tab is the tab that is active.

3. (Optional) Type a description in the provided field.

4. Click Add to add a device. To learn how to add devices to your policy seeAdding Devices to New Policies.

NOTE: You can add devices from different sites' networks to one policy. The Source col-umn in this dialog tells you which device belongs to which site.

5. Click the Monitors tab. To learn how to add monitors to your new policy, seeAdding Mon-itors to New Policies.

6. Click the Custom Monitors Tab. To learn how to add custom monitors to your policy, see

Adding Custom Monitors to Policies.

7. Click the Alerts tab. To learn how to add alerts to your policy, seeAdding Alerts.

8. Click the Scheduled Actions tab. To learn how to schedule an action for your policy, see

Creating Actions for Policies.

9. Click the Blackout Schedule tab. To learn how to disable alerts and notifications during specific hours, seeCreating New Blackout Schedules.

10. Click Save to save your changes and close the window.

See Also

(75)

After you create a new policy you can start to add devices to it. Global Policies work across sites so you can add devices from different sites' networks to them.

1. Open the Policy Editor window for your new policy. 2. In the Device Members tab, click Add.

3. In the Select New Device Members dialog, navigate to the devices that you want to add and select them.

NOTE: You can add devices from different sites' networks to one policy. The Source col-umn in this dialog tells you which device belongs to which site.

NOTE: You can select a single IP address or a range of IP addresses (using the Shift key). 4. Click Add. The IP addresses that you selected appear in the window below.

5. Click Select and then click Yes.

6. Click Save to save your changes and close the Edit Policy window.

See Also

(76)

Adding Monitors to New Policies

Monitors define what and how often data is monitored and collected from your sites' devices. When you add a monitor to your new policy, choose one that fits best with the devices in your policy. For example, if your new policy contains only VoIP devices, you will want to select the VoIP-related monitors, such as VoIP Call History, VoIP Active Calls, VoIP Manager Status, and VoIP Manager Settings.

Some monitors also have additional settings that you can modify to customize the information that your product monitors and collects from a device.

To add a monitor to a policy

1. In the Edit Policy window, click the Monitors tab. 2. Click Add Monitor.

3. In the Select Data Type dialog, select the monitor that you want to add to your new pol-icy.

4. Click OK.

5. Click the button to select how often you want data collected from the devices assigned to that policy.

6. (Optional) If applicable, click Settings to customize the data collected from a device. 7. Click Save to save your changes and close the Edit Policy window.

See Also

(77)

There are several changes to a policy that you can make in the Edit Policy window. For local pol-icies, any change that you make will affect all the devices in that policy. For global polpol-icies, you can change any setting for an individual device without applying that change to all the devices in the policy.

To edit a policy

1. In the tree view, in the Policies section, right-click a policy. 2. Click Edit. The Edit Policy window appears.

NOTE: You must have System Administrator privileges to edit and remove global policies. To edit the Devices section

You can add or remove the designated target devices that are assigned to a policy.

Add one or more devices by doing the following: 1. In the Device Members tab, click Add.

2. In the Select New Device Members dialog, navigate to the devices that you want to add and select them.

NOTE: You can select a single IP address or a range of IP addresses. 3. Click Add. The IP addresses that you selected appear in the window below. 4. Click Select and then click Yes when the message box appears.

5. Click Save to save your changes and close the Edit Policy window.

Remove one or more devices by doing the following:

1. In the Device Members tab, select one or more devices. 2. Click Remove.

(78)

To edit the Monitors section

If you applied the Smart Policy feature when you ran your network discovery, specific policies are automatically assigned recommended monitors and default time settings. When you edit the Monitors section of a policy, you can select additional monitors, remove existing monitors, and change the monitoring time interval.

Add additional monitors to a policy by doing the following: 1. In the Edit Policy window, click the Monitors tab. 2. Click Add Monitor.

3. In the Select Data Type dialog, select the monitor that you want to add to your policy. 4. Click OK.

5. Click the button to select how often you want data collected from the devices assigned to that policy.

6. (Optional) If applicable, click Settings to customize the data collected from a device. 7. Click Save to save your changes and close the Edit Policy window.

Remove existing monitors in a policy by doing the following:

1. In the Monitors Tab, select the monitor that you want to remove by clicking in the shaded gray area located on the left-hand side.

2. Click Remove Monitor.

3. When the message box appears, click Yes.

4. Click Save to save your changes and close the Edit Policy window.

Change how often you monitor a device by doing the following:

(79)

icy.

3. Click Save to save your changes and close the Edit Policy window.

To change a setting for an individual device

For Global Policies only, you can change how often you monitor a individual device and any set-tings for that device without applying your changes to all other devices in the policy.

1. In the tree view, in the Global Policies section, select a policy. 2. Select a device in the Devices view.

3. On the toolstrip, click Monitors And Alerts -> Configure For Device.

4. In the Device Policy Editor window, for the device that you want to edit, do one or both of the following:

l Update how often you monitor the device by clicking the button to select a new time interval.

l Update the settings for that device by clicking Settings and then redefining filters or selecting or deselecting check boxes.

NOTE: Device settings will vary for each device.

5. Click Save to save your changes and close the Device Policy Editor window.

See Also

(80)

About Monitors in Policies

Foglight NMS provides the following built-in monitors, which you can view when you click the Monitors tab in the Edit Policy window.

Some monitors also have additional settings that you can modify to customize the information that your product collects from a device. If applicable, you will find the name of these settings and a brief description in the provided tables.

Basic Group

l System Information

Collects the device IP address, device types and roles, operating system, domain, and other detailed system information for a device.

l Network Interface Configuration

Collects the interface name , MAC address, and other network interface information for a device.

l Ping

Sends an ICMP (ping) command to a device. If the device does not respond to the request, the Ping monitor may not be working as expected.

Setting Description

Ping Timeout (ms) Maximum amount of time in milliseconds that Ping will wait for a response from the target.

Ping Packet TTL (Time-To-Live) Number of hops along the way to a specific address. With a setting of 100, your Ping Scan may pass through 100 dif-ferent relay points on the way to the remote address before the network discards it.

Pings Per Node Establishes the number of Ping attempts sent to each address during a scan.

(81)

subnet of the target IP address. In this situation, the Cisco router responds to the second Ping.

Delay Between Pings (ms) Time in milliseconds between each successive Ping to a tar-get address. If you set this value to a very low number, it will send a constant stream of Pings to a target IP address

l CPU

Monitors the number of processors, current usage, and average usage over time from a device.

l Memory

Monitors the memory currently in use, available free memory, and total memory capac-ity of a system.

l Disk Volumes

Provides disk usage and total capacity per volume for a device. Results are available in raw numbers and as percentages.

l Programs Installed

Provides a detailed list of all the software programs installed on a device.

l Running Processes

Provides name, path, CPU, and memory consumption for all the processes running on a device.

l System Information

Provides device IP Address, device type and roles, operating system, domain, and other detailed system information for a device.

Application Group l Web Server

Sends a HTTP or HTTPs request to a device. If the device does not respond or returns an incorrect string, the web server monitor may not be working as expected.

Setting Description

(82)

Setting Description

Port Web server port

HTTP or HTTPS Type of traffic for the monitor

l Active Directory

Monitors the status and performance of application specific counters for Active Directory server.

l Exchange Server

Monitors the status and performance of application specific counters for MS Exchange server.

Setting Description

Services Captures Imap4, POP3, and Transport data Specific Processes Captures system processor and store data Counters Captures transport queues and logical disk data

l SQL Server

Monitors the performance counters for SQL Server.

Setting Description

Services Captures SQL Browser and writer data

Specific Processes Captures system processor and privileged time data Counters Captures database transactions, buffer manager, latches

and locks data

l Windows Services

Monitors critical windows services for up, down, disabled status and detailed information.

l DNS, NETBIOS

DNS monitor sends a DNS lookup request and ensures a value is returned.

Setting Description

References

Related documents

Professor Uma Coomaraswamy is Emeritus Professor and a former Vice-Chancellor of the Open University of Sri Lanka, served Sri Lanka University System for over forty years, as an

Pengujian data training ( recall ) untuk verifikasi dilakukan dengan membandingkan setiap 6 skor milik suara ke-n dengan 6 skor yang telah melewati normal distribusi dari 19

Such a collegiate cul- ture, like honors cultures everywhere, is best achieved by open and trusting relationships of the students with each other and the instructor, discussions

[r]

In this chapter, we faced the question of whether it is possible to estimate at the same time the task being performed (reach a target position) and the signal model (binary

When a compatible medication is added to the Glucose Intravenous Infusion, the solution must be administered immediately.. Those additives known to be incompatible should not

The bit type will affect the size and quality of cuttings collected, and various hole conditions will dictate the types of sample we see at the surface..

Parker Hannifin Corporation’s Veriflo Division presents the IR6000 Series internally threadless pressure regulator for pressure reducing industrial/analytical applications