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

About Foglight NMS Foglight NMS is a comprehensive device, application, and traffic monitoring and troubleshooting 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 discovering system resources and their metrics, including hardware, operating systems, virtualization, databases, middleware, applications and services. Key features of the product include: Monitoring applications where you can view the performance of an application and identify issues which may help you prevent an application from failing. Dashboards that you can manage and customize to display information about your sites' networks, such CPU load, memory, disk space utilization, network interface traffic, network latency, and packet loss. Analyzing network traffic to identify patterns and usage, which will allow you to determine how traffic impacts the overall health of a network through real-time packet capture. Running custom scripts which allow you to remotely and securely run a script you wrote on Windows, Mac, Linux, and Unix devices. 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. Creating custom SNMP monitors to provide complete SNMP (Simple Network Management Protocol) coverage on any network by defining a SNMP OID to monitor a SNMP device regardless of the manufacturer or type of device.

What's New in Foglight NMS Version 6.0 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, see Overview 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 location. For more information on the new Custom Reports feature, see Creating Custom Reports.

Finding Information Topics in this section Viewing Online Documentation Contacting Support

Viewing Online Documentation 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: Foglight NMS Integration User's Guide. Go to https://support.quest.com/ to view this guide. API User's Guide Go to https://support.quest.com/ to view this guide.

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 at http://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: In the Foglight NMS Studio: Click Technical Support in the Help drop-down menu. Email: foglightnmssupport@quest.com 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 Network Management System" in the subject line along with a brief description of the issue or question. 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. If you are updating a support case or ticket, you should include the following string in the subject line of your email: "CaseID:8xxxx" where "8xxxx" is your case number that you wish to update. Keep in mind the string is case sensitive (capital C, I, and D) and there are no spaces. If you follow the syntax protocol, the case will be updated and the support representative will receive an email with your update.

Setting Up Your Product Topics in this section How to Set Up Foglight NMS System Requirements Adding sites Adding Groups Enabling Devices for Monitoring Running Network Discovery

How to Set Up Foglight NMS There are a couple of factors that you must keep in mind when setting up your product: It is recommended that you assign a public DNS to your product platform server instead of using an IP address. Make sure you open the correct outbound and inbound firewall ports. For more information, click here. The following diagram shows how your product monitors and collects data from your devices and sends it to your product platform server.

See Also System Requirements Enabling Devices for Monitoring

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 Things to Consider Before You Install Foglight NMS Host Server Hardware and Software System Requirements Device and Collection Agent System Requirements Foglight NMS Studio System Requirements SQL Server System Requirements Installing Foglight NMS on a Virtual Machine

Things to Consider Before You Install Foglight NMS When you apply Smart Policy assignments to install Foglight NMS with the default monitor settings, 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: Number of monitored devices: If you monitor 500 or more devices, you may need to do some performance tuning on your system. 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. 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 collection in an efficient and timely manner. 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: You configure the application to collect Traffic Flow data from multiple routers or switches. There exists a large amount of traffic conversations. You set up the application to monitor more than 500 devices.

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 Foglight 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: Microsoft Windows 2003 SP2 or later Microsoft Windows 2008 Server CPU Memory Hard Drive Space.Net Framework Firewall Exceptions - Allowed Programs Dual Core, 3.0 GHz or higher (Recommended) 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. 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. 2.0 or higher Version 3.5..NET Framework 3.5 SP1 (Recommended) The following are automatically configured during installation:

Host Server System Requirements ptserverservice ptserverconfig ptagentservice ptagentconfig ptstudio Ports The following are the firewall rules for inbound connections: 5053 (TCP) = (128 AES Encrypted Host Server port) 5054 (TCP) = Agent deployment CAB file downloads 5055 (TCP) = (Encrypted Remote Control Tunnel port) 61 (UDP) SNMP Trap collector 69 (UDP) - TFTP Server 514 (UDP) - Syslog collector 2055 (UDP) NetFlow collector 6343 (UDP) sflow collector 9555 (UDP) - NetFlow Alternative port #2 collector 9995 (UDP) NetFlow Alternative port #3 collector

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 limited TCP connections available with these operating systems may impact the monitoring performance. 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: Windows Server 2003 SP2 or later Windows Server 2008 Windows XP SP2 or later Windows Vista SP1 (all versions) Microsoft Windows 7 Ubuntu Server 8 Fedora release 10 Debian 4.0 OpenSuse 11.0 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 Ports 2.0 or higher Version 3.5..NET Framework 3.5 SP1 (Recommended) The following are the firewall rules for Outbound connections: 5053 (TCP) = (128 AES Encrypted Host Server port) 5054 (TCP) = Agent deployment CAB file downloads

System Requirements for Device and Collection Agents 5055 (TCP) = (Encrypted Remote Control Tunnel port)

Foglight NMS Studio System Requirements You can use the following operating systems and browsers to run the web version of the Foglight NMS Studio. Microsoft Windows (all versions) Microsoft Internet Explorer 6 or later Mozilla Firefox 3.6 Google Chrome

SQL Server System Requirements 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 Foglight 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: Microsoft SQL Server 2005 Standard or Enterprise Editions Windows Server 2008 Standard or Enterprise CPU Memory Dual Core, 3.0 GHz or higher (Recommended) 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 following requirements apply: You must install SQL server on a physical machine. You must have a minimum of 32 GB of RAM. You must use SQL authentication instead of windows authentication.

If your machine is collecting traffic and log data, the following minimum system requirements apply: Additional Requirements Operating System Perspective Agent Service Perspective Service Additional RAM per Netflow Device(s) Additional RAM per Netflow Device(s) 2 GB 1 GB 1 GB NoOfFlowDevices * 300MB 1 GB

Installing Foglight NMS on a Virtual Machine Because of intense I/O requirements and a high threshold of additional hardware specifications, installing Foglight NMS on a virtual machine in a production environment is not recommend. 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). Operating System: For 64-bit, both Windows Server 2008 or Windows Server 2008 R2 are recommended; however, you can use Windows 7. CPU: Two physical cores dedicated to perspective VM (no hyper-threading core). Memory: 4 GB RAM. NOTE: If you install SQL server, you must include an additional 4 GB RAM. You must provide a minimum of 100Mbs of bandwidth dedicated. You must make sure that your VM is using a physical partition rather than a virtual harddisk.

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, see Installing 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, see Running Network Discovery. See Also Adding Devices by SNMP Adding Devices by Deploying Agent

Adding Groups You can create multiple groups to organize the various types of devices in a network. For example, 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. To edit a group

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 1. In the tree view, right-click a group and click Remove. 2. When the message appears, click Yes.

Enabling Devices for Monitoring 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 desktops, 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, see Enabling SNMP on a Device. Windows Management Instrumentation (WMI) Windows Management Instrumentation (WMI) is a programming interface (API) in the Windows operating system that enables devices and systems in a network, typically enterprise networks, 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: Microsoft Exchange SQL Active Directory Windows event logs Windows services Hardware Inventory For more information on how you can enable WMI, see Enabling WMI on Windows Devices.

See Also Enabling SNMP on a Device Enabling WMI on Windows Devices Monitoring Your Devices by SNMP Monitoring Your Devices by WMI

Enabling SNMP on a Device 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 Credential link to add new credentials to the Encrypted Credential 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 Monitoring Your Devices by SNMP Enabling Devices for Monitoring

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: Windows Management Instrumentation 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, click here. For more information on connecting to WMI remotely on Windows Vista, click here. See Also Monitoring Your Devices by WMI Enabling Your Devices for Monitoring

Running Network Discovery 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:.. See Adding Devices By SNMP for more information See Adding Devices by Deploying Agents for 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 consider the following before you run network discovery: 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. NOTE: Enabling WMI allows you to monitor and collect data for Microsoft Exchange, SQL, Active Directory, Windows Event Logs, Windows Services, and Hardware Inventory data types only.

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 network discovery more than once to properly discover all devices in the network. 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 Enabling WMI on Windows Devices

Adding Devices by SNMP 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, see Network 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, see Setting Device Credentials for Network Discovery. 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, see Applying Smart Policies to Devices. 11. Click Finish to complete the Network Discovery process.

See Also Running Network Discovery Network Discovery Techniques Setting Device Credentials for Network Discovery Applying Smart Policies to Devices

Network Discovery Techniques 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 discovery. 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. Click the Advanced Settings link in the Select Network Discovery Techniques section to modify the following settings:

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 setting, 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 network 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 Running Network Discovery Adding Devices by SNMP

Setting Device Credentials for Network Discovery When you run network discovery, selecting the correct credentials is essential in order for Foglight 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 credentials 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: SNMP Version 1 Credential SNMP Version 2 Credential SNMP Version 3 Credential 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 Adding Devices by SNMP

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 Windows XP, Windows Vista, or Windows 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, see Device and Collection Agent System Requirements. 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 column 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. 11. In the Results screen the Results screen will notify you if the Telnet/SSH credential for the device is valid.

12. Select a device with the correct WMI credential so that you can monitor and collect specific Windows-based data. For more information, see Monitoring 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 Monitoring Your Devices by Deploying Agents Benefits of Deploying an Agent

Benefits of Deploying an Agent You will experience the following benefits when you deploy an agent on a machine: An agent captures and monitors all data from a machine eliminating the need to enable SNMP or WMI on a device. You can use the Patch Management feature. You can remotely gain access to a machine using Expert Assist. Increase a machine's performance by decreasing the amount of traffic between devices. Increase the quality of monitored data by missing fewer monitoring intervals than a SNMP connection. Gives you remote access to various mobile assets, such as laptops. Increase the amount of devices that you can monitor. See Also Monitoring Your Devices by Deploying an Agent

Installing Agents Manually 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 download 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 following: Click Copy URL to download the agent software from a known location on your Foglight NMS server. Click Email URL to send the location of the agent software to all the desktops in a network. 6. Click Close. See Also Adding Devices by Deploying an Agent

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: 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 identify 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. Networking Policy Server Policy Desktop Policy Wap Policy VMware Host Policy Applying the Default Policy to Devices By selecting the Default Policy option in the Network Discovery Wizard, you are assigning the discovered devices to the Default Policy (only the devices that you selected on page 2 of the Network Discovery Wizard are applied to it). After the network discovery process is complete, you

can reassign devices in the default policy to a different smart policy or to a policy that you created. See Also Overview of Network Discovery Migrating Devices from the Default Policy

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 Upon launching Foglight NMS, the software will check for any updates available at the patch server. The software automatically pulls the updates and stores them in cache. The updates are applied the next time the software is launched.

Monitoring Your Devices Topics in this section Monitoring Your Devices by SNMP Monitoring Your Devices by WMI Monitoring Your Devices by Deploying an Agent Collecting Syslog, NetFlow, and SNMP Traps Data

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 desktops, 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: Enable SNMP on all the devices that you want to monitor. Assign a credential to the device in Foglight NMS. The following diagram shows how Foglight NMS uses SNMP to monitor your devices.

See Also Enabling SNMP on a Device

Monitoring Your Devices by WMI Windows Management Instrumentation (WMI) is a programming interface (API) in the Windows operating system that enables devices and systems in a network, typically enterprise networks, 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: Microsoft Exchange SQL Active Directory Windows event logs Windows services Hardware Inventory The following diagram shows how Foglight NMS monitors your devices by WMI.

See Also Enabling WMI on Windows Devices

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 windows-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. The following diagram shows how Foglight NMS monitors your devices by deploying an agent. Note that each desktop and server in this image has an agent deployed on it.

See Also Benefits of Deploying an Agent Adding Devices by Deploying Agents

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. 514 (UDP) - Syslog collector 61 (UDP) - SNMP Trap collector 2055 (UDP) - NetFlow collector 6343 (UDP) sflow collector 9555 (UDP) - NetFlow Alternative port #2 collector 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. The following diagram shows how Foglight NMS collects syslog, NetFlow and SNMP Traps data.

See Also Enabling NetFlow

Using Dashboards to Quickly Diagnose Issues Topics in this section Overview of Dashboards Touring the Dashboard View User Interface Customizing Your Dashboard Adding Dashboard Tabs About Gadgets Adding Gadgets to Your Dashboard Creating Custom Gadgets Editing Gadgets

Overview of Dashboards 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' networks. It provides you with critical device information, such as CPU load, network interface traffic, 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: Monitor device availability, CPU load, memory, disk space utilization, network interface traffic, network latency, and packet loss. Perform advanced monitoring of running services, process availability, and performance counters for MS Exchange, SQL, Active Directory. Make an inventory of gadgets include charts, gauges, lists, text, and web links. Compare networks between sites and organizations. Create a custom view by dragging and dropping gadgets. 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 Touring the Dashboard View User Interface Customizing Your Dashboard Adding Dashboard Tabs About Gadgets Adding Gadgets to Your Dashboard Creating Custom Gadgets Editing Gadgets

Touring the Dashboard View User Interface

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: Adding new dashboard tabs. Adding new gadgets to a dashboard. Restoring the product defaults to your dashboard. NOTE: This action will remove all gadgets and tabs that you added from the dashboard. 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: View the performance and activity of one or more devices in a network. Filter the data by clicking a column header. Edit the way in which data is displayed in a gadget. Move the gadget up in the Dashboard view when you click the gadget title bar. Remove the gadget from your dashboard by clicking the Close link.

Customizing Your Dashboard You can customize your dashboard by doing the following: 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. Add new standard gadgets or add custom gadgets that you created. Edit or remove any of the existing tabs or gadgets. 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. 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 dashboard that you customize will be available to view only by you. Other Foglight NMS users cannot 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. 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. Clear Gadgets Removes all gadgets from the selected dashboard. Rename Tab Changes the name of the selected dashboard tab. Close Tab Permanently removes the selected dashboard and all the gadgets contained within it. See Also Adding Gadgets to Your Dashboard Adding Dashboard Tabs

Creating Custom Gadgets Editing Gadgets

About Gadgets 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 directory server. Application Performance Alerts In Process Displays a detailed list of triggered alerts. Alerts and Logs Average Latency Chart Average Latency Gauge Average Latency List Average Latency Text Displays the average latency of one or more nodes by charting the ping results. Displays the average latency of a node based on response time and average packet loss. Displays the average latency of a list of one or more nodes by showing the response time and a color indicator bar. Displays the average latency of a node by changing the color of the text to green or red. Device Availability Device Availability Device Availability 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. Device Performance

Gadget Name Description Location of Gadget CPU List CPU/Memory Chart CPU/Memory Gauge CPU/Memory List Monitors the CPU usage percentage of one or more devices within a network. Monitors the CPU and memory usage percentage of a device. Monitors the CPU and memory usage percentage of a device. Monitors the CPU and memory usage percentage of one or more devices. Device Performance Device Performance Device Performance 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 Configuration Displays dial manager configuration via IP SLA on Cisco routers. VoIP Dial Manager Phone Chart Dial Manager Registration Status Displays dial manager phones via IP SLA on Cisco routers. Displays dial manager registration status via IP SLA on Cisco routers. VoIP VoIP Discovered Devices TBD Network Interface Disk Volume Chart Disk Volumes Installed Applications Monitors the disk utilization on a hard drive of a specific device Monitors the disk utilization of each drive as a percent of capacity for a device Displays installed applications via SNMP (some devices will require Telnet or SSH) Device Performance Device Performance 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 Memory Chart Monitors the memory usage percentage of a device. Device Performance

Gadget Name Description Location of Gadget Memory Gauge Memory List MS Exchange Network Ethernet CRC Errors Network Token Ring CRC Errors Network Interface Chart Network Interface List Network Statistics Summary Network Traffic Flow Monitors the memory usage percentage and average usage percentage of a device. Monitors the memory usage percentage of one or more devices in a network. Monitors the performance counters for the MS Exchange server. TBD TBD Monitors the network interface performance for a device. Monitors the network interface performance for a device. Displays network statistics through SNMP. Displays the NetFlow, sflow, JFlow, and ptflow traffic for a switch or a router. Device Performance Device Performance Application Performance Device Performance Device Performance Device Performance Device Performance Device Performance Network Performance Open Source Web Viewer Allows you to choose a browser-based open source network management tool or web site to display. Application Performance 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 Performance Syslog Displays all the collected syslog messages for a specific device. Alerts and Logs

Gadget Name Description Location of Gadget System Information Displays detailed system information for a device. OS Details Top 10 - Average CPU Usage Top 10 - Average Memory Usage Top 10 - Average Packet Loss Monitors the CPU performance of a list of one or more nodes. Monitors the memory performance of a list of one or more nodes. Displays the average packet loss of a list of one or more nodes. Top 10 Top 10 Top 10 Top 10 - Disk Volume Usage Displays 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 targets) Top Network Traffic: Convs (for one target) Top Network Traffic: Domains (for one or multiple targets) Shows network traffic data, organized by application and dependent on the scope that you select when you create the gadget. Shows network traffic data, organized by conversation and dependent on the scope that you select when you create the gadget. Shows network traffic data, organized by domain and dependent on the scope that you select when you create the gadget. Top 10 Top 10 Top 10 Top Network Traffic: Endpoints (for one or multiple targets) 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 information. VMware

Gadget Name Description Location of Gadget VoIP Active Calls VoIP Call History VoIP Phone Status Windows Event Logs Windows Services Wireless Access Point Displays active calls through IP SLA on Cisco call manager. Displays call history through IP SLA on Cisco call manager. Displays VoIP phone status through IP SLA on Cisco call manager. Displays all event logs collected for a device, including application, security, and system event logs. Displays critical windows services information, such as status and start type. Displays information about key variables of a wireless access point, such as signal strength and quality. VoIP VoIP VoIP Alerts and Logs OS Details Wireless Performance Wireless Access Point List Displays information about all wireless access points on a network. Wireless Performance Wireless Clients Chart Wireless Clients List Shows how many wireless clients are connected to a wireless access point within a given time frame. Displays key variables for each client connected to a wireless access point. Wireless Performance Wireless Performance Wireless Traffic Chart Shows the amount of received and transmitted network traffic generated by a wireless device within a spec- Wireless Performance ified interval of time. See Also Adding Gadgets to Your Dashboard

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: Top Ten 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 Customizing Your Dashboard

Adding Gadgets to Your Dashboard 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: 4. Select the gadget that you want to add and click Next.

NOTE: You can also double-click a gadget name to open the Gadget Configuration wizard. 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 About Gadgets Editing Gadgets

Editing a Gadget 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 About Gadgets

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: If you want the custom gadget to limit the devices displayed in it to one, select Single Device 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 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. NOTE: Depending on how you group your data, not all of the gadget type options will appear.

7. Click Next. 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. 18. Click Finish. Your new custom gadget appears in the list of gadgets under the Custom Gadgets category.

See Also Adding Gadgets to Your Dashboard

Managing Devices Topics in this section Managing Credentials

Overview of Credentials The Encrypted Credential Store is a convenient, protected store of SNMP, WMI, SSH and FTP credentials shared by all tools and gadgets which require them. It uses standard AES 256-bit encryption. 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. 5. Click Close to Finish.

Creating Local and Global Policies Topics in this section Overview of Local Polices Overview of Global Policies Adding New Policies Editing Local and Global Policies Applying Smart Policies to Devices Migrating Devices from the Default Policy

Overview of Local Policies A policy defines how you work with the information collected from your devices. It encompasses devices, monitors, alerts, scheduled actions, and blackout schedules so that any configuration changes you make occur from one central location. In a policy you can: Create and save permanent policies that are assigned to designated target a single IP or a range of IPs and device groups. Define what and how often data is monitored and collected from your devices. Create custom SNMP monitors. Set alerts to automatically notify you when an issue arises or the network's performance declines. Schedule an action to fix issues and restore the network to peak performance. 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 Migrating Devices from the Default Policy

Overview of Global Policies 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: Create cross-site policies. You can assign devices from different sites' networks to a single policy. 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 Migrating Devices from the Default Policy

Adding New Policies In addition to the built-in Smart Policies, you can create your own policies to manage data collected 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 see Adding Devices to New Policies. NOTE: You can add devices from different sites' networks to one policy. The Source column 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, see Adding Monitors 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, see Adding 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, see Creating New Blackout Schedules. 10. Click Save to save your changes and close the window. See Also About Monitors

Adding Devices to New Policies 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 column 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 Adding New Policies

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 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. See Also Adding New Policies About Monitors in Policies

Editing Local and Global Policies There are several changes to a policy that you can make in the Edit Policy window. For local policies, any change that you make will affect all the devices in that policy. For global policies, 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. 3. When the message box appears, click Yes.

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: 1. In the Monitors Tab, navigate to the monitor that you want to edit.

2. Click the button to select how often you want data collected from the devices in the policy. 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 settings 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: Update how often you monitor the device by clicking the button to select a new time interval. 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 About Monitors in Policies Adding New Policies

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 System Information Collects the device IP address, device types and roles, operating system, domain, and other detailed system information for a device. Network Interface Configuration Collects the interface name, MAC address, and other network interface information for a device. 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 different 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. When your product scans networks containing Cisco routers, you should set this number to a number above two (2). If the target IP address is not in the ARP cache of a Cisco router, the router discards the ICMP query (Ping) while it requests the MAC address of the target IP. The first Ping will never arrive at the

Setting Description 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 target address. If you set this value to a very low number, it will send a constant stream of Pings to a target IP address CPU Monitors the number of processors, current usage, and average usage over time from a device. Memory Monitors the memory currently in use, available free memory, and total memory capacity of a system. Disk Volumes Provides disk usage and total capacity per volume for a device. Results are available in raw numbers and as percentages. Programs Installed Provides a detailed list of all the software programs installed on a device. Running Processes Provides name, path, CPU, and memory consumption for all the processes running on a device. System Information Provides device IP Address, device type and roles, operating system, domain, and other detailed system information for a device. Application Group 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 Timeout (ms) Maximum amount of time in milliseconds that Ping will wait for a response from the target

Setting Port HTTP or HTTPS Description Web server port Type of traffic for the monitor Active Directory Monitors the status and performance of application specific counters for Active Directory server. Exchange Server Monitors the status and performance of application specific counters for MS Exchange server. Setting Description Services Specific Processes Counters Captures Imap4, POP3, and Transport data Captures system processor and store data Captures transport queues and logical disk data SQL Server Monitors the performance counters for SQL Server. Setting Description Services Specific Processes Counters Captures SQL Browser and writer data Captures system processor and privileged time data Captures database transactions, buffer manager, latches and locks data Windows Services Monitors critical windows services for up, down, disabled status and detailed information. DNS, NETBIOS DNS monitor sends a DNS lookup request and ensures a value is returned. Setting Description Resolve NetBIOS Name Resolve LMHost Resolve Host Resolves the NetBIOS name during the monitoring process Resolves the LMHost during the monitoring process Resolves the Host during the monitoring process

Setting Resolve Forward DNS Description Resolves the Forward DNS during the monitoring process POP3 Connects to a POP3 enabled server using the POP3 server and port information provided. Once connected, an attempt is made to retrieve the number of messages on the server and also to read the 1st message in the list. If the attempt fails, the POP3 server may not be working as expected. SMTP Connects to a SMTP server using the SMTP and port information provided. Once connected, an attempt is made to send a test message to the recipient selected using the SMTP server. If the attempt fails, the SMTP server may not be working as expected. Setting Description Mail Recipient Enter the email address for the test message VMware Collects data from the VMware Server. Monitors key variables on VMware performance, active VMs, and VM attributes. Networking Group Network Interface Traffic Monitors network interface performance for a device by showing the percent of capacity or throughput. Tracks the inbound and outbound traffic for each network interface in the device. Network Statistics Provides network statistics (netstat) information of active connections and their state for a device. IP Configuration Provides IP configuration details, such as IP Address, Subnet Mask, and Default gateway, for a device. Port Map Provides a map of ports for a device.

Network Statistics Summary Provides Network Statistics for the following: Last Boot Time, SNMP In Packets, SNMP Out Packets, ICMP In Messages, In Errors, In Destinations Unreached, In Time Exceeds, In Parm Probes, In Source Quenches, In Redirects, In Echoes, TCP Max Connections, Current Established, Active Opens, Passive Opens, Failed Attempts, Established Resets, In Errors Out Resets, UDP In Datagrams, Out Datagrams, No Ports, and In Errors. Ports Group TCP Ports Creates a TCP port client and attempts to connect to the defined port to determine if the port is opened or closed. Setting Description Timeout (ms) Selected Ports Maximum amount of time in milliseconds that the connection will wait for a response from the target Enter the ports to be monitored (separate ports by a comma) Port List Log Group Syslog Listener Receives, logs and displays syslog messages from routers, switches, and any other syslog enabled device. Filter by facility, severity, date, host name, and key word. Setting Description Facility Severity TBD TBD NetFlow/sFlow/JFlow/ptFlow Collector Provides in-depth visibility into traffic network patterns and usage to determine how traffic impacts the overall health of the network. Drill down into applications, conversations, devices will identify the exact sources of spikes and burst to take proper actions. Learn how to enable NetFlow, sflow, JFlow, and ptflow. Setting Description TCP, UDP or ICMP Deselect these check-boxes if you do not wish to view that type of traffic

Setting Description Discard IP Traffic Allows the user to disregard all traffic from the entered IPs Configuration Backup - Cisco, HP, and Juniper Automatically backup configurations files for your Cisco, HP and Juniper routers and switches. NOTE: HP and Juniper require Telnet read/write credentials. Config files can be viewed and compared all in the same interface. Setting Description Timeout (ms) Backup Maximum amount of time in milliseconds that the connection will wait for a response from the target Select running config and startup config Application Event Logs Receives and displays complete information for application event logs from Windows devices for you to detect occurrences or problems. Ability to set filters by event type. Setting Description Event Type Collect errors, warnings and/or information logs. Use the Ctrl key to select more than one log file type. Security Event Logs Receives and displays complete information for security event logs from Windows devices for you to detect occurrences or problems. Ability to set filters by event type. System Event Logs Receives and displays complete information for system event logs from Windows devices for you to detect occurrences or problems. Ability to set filters by event type. Setting Description Event Type Collect errors, warnings and/or information logs. Use the Ctrl key to select more than one log file type.

Wireless Group Cisco Wireless Monitors wireless networks and sees into wireless access points, clients and sessions. Monitors key variables on access points, including signal strength and quality. Voip Group VoIP Manager Settings Displays the Dial Manager Configuration information for a device. VoIP Manager Status Lists the VoIP phone status information for a device. VoIP Active Calls Lists the active VoIP calls information for a device. VoIP Call History Displays VoIP call history information for a device. IP SLA Displays IP SLA Overview, Call Path Statistics, Call Path Jitter Chart, Call Path MOS Chart, Call Path Latency Chart, and Call Path Packet Loss Chart information for a device. Call Manager Registration Status Monitors the active, registered and unregistered phone of a VoIP system. See Also Editing Local and Global Policies

Removing Policies You must have System Administrator privileges to remove a policy from your product. Additionally, you cannot delete a Global Smart Policy. 1. In the tree view, under Policies, select the policy that you want to delete and then rightclick. 2. In the context menu, click Remove. 3. When the message appears, click Yes. The policy no longer appears in the list. See Also Adding New Policies Editing Local and Global Policies

Migrating Devices from the Default Policy 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 identify 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. To migrate a device from the Default Policy 1. In the tree view, select the Local or Global Default Policy. A list of devices appears in the Devices view 2. Select the device that you want to migrate and then right-click. 3. In the context menu, click Monitors and Assets -> Reassign to New Policy. 4. In the Select Policy Reassignment dialog, select a policy. 5. Click Select to save your changes and close the dialog. If you look in the tree view, you will see that the device has been reassigned to its new policy, which is indicated by the increase in device numbers. See Also Applying Smart Policies to Devices

Creating Custom SNMP Monitors Topics in this section Overview of Custom Monitors Installing the SNMP MIB Library Creating Custom SNMP Monitors Assigning Custom Monitors to Policies Removing Custom Monitors from Policies Editing Custom Monitors Deleting Custom Monitors

Overview of Custom SNMP Monitors Foglight NMS provides pre-defined monitors that collect key data for most of the common devices in a network. When you create a custom SNMP monitor, you can define any Object Identifier (OID) to a MIB node in order to monitor any SNMP device (regardless of the manufacturer or type of device). For example, you can monitor temperature on a switch, fan speed on a router, and battery status on a UPS. Custom SNMP monitors enable Foglight NMS to provide complete SNMP coverage on any network. Foglight NMS has an extensive MIB database that determines the friendly name for each OID. Additionally, you can convert MIB values into the units of measurement that are most useful to you. Custom monitors work just like the pre-defined monitors included with Foglight NMS. You can scheduled alerts that will notify you of the status of any SNMP monitor and automatically create tickets in a third-party PSA application, as well as create reports and graphs for any monitor. Creating Custom Monitors in Your Product There are several places in Foglight NMS where you can create a custom monitor, edit an existing one, or double-click a custom monitor to assign it to a policy. From the Edit Policy window: When you create a custom monitor for a policy, the custom monitor applies to all the devices in that policy. 1. Right-click a policy and then click Edit. 2. In the Edit Policy window, click the Custom Monitors tab.

From a device: You can create a custom monitor that is specific to a device and applies only to that device. 1. In the Devices View, select a device and right-click it. 2. In the context menu, click Monitors And Alerts -> Configure For Device. 3. In the Device Edit window, click the Custom Monitors tab. From the Configuration -> Administration:

The Custom Monitor Database is a central library for all custom SNMP monitors. You can create, edit, and delete custom monitors from this library. When you modify a custom monitor assigned to a global policy, that policy is updated. 1. On the Foglight NMS main menu, click Configuration -> Administration. 2. Under the Configuration section, click the Custom Monitors icon. See Also Installing the SNMP MIB Library Creating Custom Monitors Assigning Custom Monitors to Policies Editing Custom Monitors

Installing the SNMP MIB Library The SNMP MIB Library is a repository of over 15,000 devices that you can use for SNMP walks, SNMP traps, and custom SNMP monitors. Updates to the library are published every quarter; however, you only need to download the library one time. You must install the library before you can start creating a custom SNMP monitor. To install the MIB library 1. On the Main menu, click Configuration -> Administration. 2. Double-click the SNMP MIB Library icon. 3. In the Update SNMP MIB Library dialog, click Start Download. NOTE: Initially, the status of the MIB Library appears as Library is not installed. The status will change to "Library Is Current" after you download the library. 4. Click Finish.

Creating Custom SNMP Monitors Click a link to learn more about the different ways you can create a custom monitor: To create a custom monitor by browsing the MIB library for an SNMP OID To create a custom monitor by using the SNMP Walk Utility Tool To create a custom monitor by manually adding an OID

Adding Custom SNMP Monitors from the MIB Browser You can browse the MIB library to locate an OID. In the MIB library, drill-down into the folders by double-clicking them. When you drill-down to a OID, select it to view its details and create your custom monitor. NOTE: This option is available only after you install the MIB library. You must install the library before you can start creating a custom monitor from the MIB browser. 1. From the Custom Monitor tab, click Add Custom Monitor. 2. On the Custom Monitor Database pop-up window, click Add From MIB Browser. 3. In the SNMP OID Browser pop-up window, drill-down in the tree view and select a MIB Library OID. Click the Name or OID radial buttons to change how you sort the OIDs in the tree view. 4. Click Create Custom Monitor From Selected. 5. In the Custom Monitor pop-up window, you can edit the friendly name, description, and select the value type. NOTE: If you select Value as the Value Type, then select the Value scale and Display scale. 6. Click Save to create your custom monitor.

Finding Vendors in the MIB Library There is a complete list of vendors in the MIB Library. You can view the list when you open the SNMP OID Browser window. In the tree view, click Private -> Enterprises and a list of supported vendors appears. If you do not find your vendor in the list, use the Give Feedback feature to send the MIBs to the Foglight team. When the library The library will be updated to include new MIBs and vendors. See Also Assigning Custom Monitors to Policies Editing Custom Monitors

SNMP Walking the Device Foglight NMS provides the SNMP Walk Utility tool, which is built into the custom monitor framework. This tool will walk any device with a valid SNMP credential. When the walk is complete and a variable identified, you can create a custom monitor. 1. From the Custom Monitor tab, click Add Custom Monitor. 2. In the Custom Monitor Database pop-up window, click Add From SNMP Walk to add the SNMP OIDs from the SNMP walk remote tool. 3. In the Select Device To Run SNMP Walk Against window, select a device and click Select. NOTE: If you want to select a different device later, in the SNMP Walk Tool dialog, click Change Device. 4. In the SNMP Walk Tool pop-up window, select a valid credential in the drop-down list, such as a public SNMP type.

5. Select an OID in the drop-down list. 6. Click Get to retrieve the OIDs for the selected device. NOTE: You must select the credential and OID for the device to prevent an error from occurring. If the OIDs are not selected for the specified IP Address, check that the device supports the OID and the credential used has access to that OID. If not, the OIDs are not listed. NOTE: If you want to stop the process of getting the OIDs by click Stop Walk. 7. Select an OID in the list. NOTE: If you want to clear to clear the results of your previous walk and start a new walk, click Clear. 8. Click Create Custom Monitor From Selected. When the message appears, click Yes. 9. In the Custom Monitor pop-up window, select the appropriate values and click Save to add the new custom monitor to the list. 10. Click Save to save your changes.

See Also Assigning Custom Monitors to Policies Editing Custom Monitors

Manually Adding Custom SNMP Monitors If you know the OID of a SNMP-enabled device you can manually enter it to add your custom monitor. 1. From the Custom Monitor tab, click Add Custom Monitor. 2. In the Custom Monitor Database pop-up window, click Add OID Manually. 3. In the Manually Add OID dialog, type an OID. 4. In the Select Device To Run SNMP Walk Against window, select a device and click Select. 5. In the SNMP Walk Tool pop-up window, select a valid credential in the drop-down list, such as a public SNMP type. 6. Select an OID in the OID drop-down list. 7. Click Get to retrieve the OIDs for the selected device. 8. Select an OID in the list. 9. Click Create Custom Monitor From Selected. When the message appears, click Yes. 10. In the Custom Monitor pop-up window, select the appropriate values and click Save to add the new custom monitor to the list. 11. Click Save to save your changes. For more information on the SNMP Walk Tool, see SNMP Walking the Device. See Also Assigning Custom Monitors to Policies

Editing Custom Monitors

Adding Custom SNMP Monitors to Policies From the Edit Policy window, you can add a custom monitor to the database, and then assign it to the policy. Additionally, set how often your custom monitor monitors and collects data from a device or disable it. 1. In the Foglight NMS Studio, select a policy and right-click. 2. In the context menu, click Edit. 3. In the Edit Policy window, click the Custom Monitors tab. 4. Click Add Custom Monitor. 5. In the Custom Monitor Database, select an existing custom monitor or create a new one. For more information about creating a new custom monitor, see Creating Custom SNMP Monitors. 6. Double-click your selected custom monitor. 7. In the Assign Custom SNMP Monitor to Policy, under Monitor Settings, select how often you want data monitored and collected from the devices in the policy. 8. Under Test Monitor, click Run Test (Required). You must run a test against a device before you can add the custom monitor to the policy. 9. In the Select Device To Test Against, select a device and click Add.

10. If the test was successful, select an OID. 11. Click OK. 12. Click Save to save your changes. See Also Creating Custom SNMP Monitors Removing Custom Monitors from Policies

Removing Custom SNMP Monitors from Policies Remove a custom monitor from a policy by doing the following: 1. In the Custom Monitors tab, select a custom monitor. 2. Click Remove Custom Monitor. 3. When the message appears, click Yes. After you confirm your action the selected custom monitor is removed from the policy; however, it is not deleted from the custom monitor database. You can choose to reassign the removed custom monitor to the same policy or to a different one. See Also Assigning Custom Monitors to Policies Deleting Custom Monitors

Editing Custom SNMP Monitors There are several places in Foglight NMS where you can edit or delete a custom SNMP monitor. From the Edit Policy window: From this window, you can only edit custom SNMP monitors assigned to the policy. You can change how often your custom SNMP monitor collects data from a device or disable it to stop it from collecting data. You cannot edit the friendly name or description of a custom monitor assigned to a policy. 1. In the Edit Policy window, click the Custom Monitors tab. 2. Select the custom monitor that you want to edit. 3. Click Edit Custom Monitor. 4. In the Assign Custom Monitor to Policy, select how often you want data monitored and collected from the devices in the policy in the Monitoring Interval drop-down list. 5. If you want to disable your custom monitor, de-select the Enabled check-box. 6. Click OK to save your changes. From a device: You can edit a device-specific custom monitor. Edit the friendly name, description, how often you monitor and collect data from a device, and enable or disable a custom monitor. Your changes will apply only to that device. 1. In the Devices View, select a device and right-click it. 2. In the context menu, click Monitors And Alerts -> Configure For Device. 3. In the Device Edit window, click the Custom Monitors tab.

4. Select a custom monitor. 5. Click Edit Custom Monitor. 6. Make the necessary changes to your custom monitor, such as modifying how often data is collected or enabling or disabling it. 7. Click OK to save your changes. From the Monitors and Alerts link on the Devices View: 1. Select a device in the Devices View. 2. In the Device details, on the toolstrip, click the Monitors and Alerts link. 3. Click Configure For Device. 4. In the Device Edit Monitor and Alerts window, click the Custom Monitors tab. 5. Select a custom monitor. 6. Click Edit Custom Monitor. 7. Make the necessary changes to your custom monitor, such as modifying how often data is collected or enabling or disabling it. 8. Click OK to save your changes. See Also Removing Custom Monitors from Policies Deleting Custom Monitors

Deleting Custom SNMP Monitors The following steps will show you how to permanently delete a custom monitor from the database. If you delete a custom monitor assigned to a policy, it will be deleted from that policy as well. 1. On the main menu, click Configuration -> Administration. 2. Under Configuration, click the Custom Monitors icon. 3. In the Custom Monitor Database window, select the custom monitor that you want to delete. 4. Click Delete Monitor. 5. When the message appears, click Yes. See Also Removing Custom Monitors From Policies

Viewing Custom SNMP Monitor Details The following information is available to view from the Device Details. To see the details of a device, select a device and double-click it. Viewing Trend Charts When you create a custom monitor, if you select the Trend Chart check-box the data collected by the custom monitor displays in a chart to show you how your device performed over a period of time. NOTE: The Trend Data check-box is not available for all data types. 1. In the Device Details, click the Custom Monitoring tab. 2. In the Custom Monitoring - Trendable gadget, click the Trend Chart link.

NOTE: If you have multiple custom monitors associated with a device, a unique trend chart is generated for each one. Viewing the Device Status The Device Details also provides you with a way to see the status of all the monitors added to a device. 1. Click Settings -> Verify Monitoring Status on the Device Details page.

2. Device Monitor Status pop-up window appears.

Setting Up Alerts Topics in this section Overview of Alerts Adding New Alerts Escalating Alerts Setting Up Alerts for Custom SNMP Monitors

Overview of Alerts and Notifications When you set up alerts in PacketTrap, you will automatically receive an email which notifies you if any issues arise in the network. These alerts allow you to fix the issues before they impact a user. You can configure alerts for multiple conditions that meet the needs of your network. An alert can monitor network events, traffic, and conditions to create a performance baseline, which makes sure that you are not inundated with false-positive alerts from normal network activity. Additionally, you can set up critical alerts to be escalated to one or more users until the problem is resolved or you can suppress alerts from triggering during scheduled network maintenance. You can also set up an alert for interrelated events or conditions. See Also Adding Alerts Escalating Alerts Setting Up Alerts for Custom SNMP Monitor

Adding Alerts Adding an alert to your policy allows you to stay informed of any issues that may arise. You can configure an alert to when you add an alert, you need to configure the conditions for which that alert will be triggered and what actions should be taken to resolve the issue. You can also escalate the alert if it is not resolved. 1. In the Edit Policy window, click the Alerts tab. 2. Click Add Alert. 3. Type a name for the alert. 4. In the drop-down lists, select a Severity and Priority. 5. In the Notifications section, select one or more of the following check-boxes: Notify On Conditions Met. This option notifies you by email after the your configured conditions have been met. Notify On Actions Complete. This option notifies you by email after an action has been taken to resolve the issue. Notify On Alert Reset. This option notifies you by email after an alert has been reset. 6. (Optional) In the Notification Target Override To and CC fields, type an email address. If you have a user already set up to receive alert notifications, this option overrides that person and sends an email to the email address that you enter in the To or CC fields. 7. In the Alert Reset Options, select whether you want the alert to be automatically or manually reset. 8. In the Conditions, Actions, and Escalations section, configure a new condition, action, escalation, or reset option. New Condition You can set the performance thresholds for monitors which determines when an alert is triggered. Set a condition for all monitors. NOTE: A condition will only work if the associated monitor is enabled for a device. For example, the CPU monitor must be enabled for an alert to work on CPU over 90%. New Action

Foglight NMS can take action on a device if the conditions are met. The inventory of actions includes: For Windows: Start Service, Stop Service, Pause Service, List Services, Create Process, Kill Process, List Process, List Process Top CPU Usage, List Process Top Memory Usage, List Process Top Read from Disk, List Process Write to Disk, List Network Statistics, Shutdown Restart, IP Config Info for Host, Route Table Info for Host. For Linux: Start Linux Process, Kill, Linux process, List Active Connections, List Daemon Processes, List Directory Details, List File System Details, List Installed Packages, List IP Config Details, List Memory Status, List Network Statistics, List Routing Table, List Running Processes, List Top CPU Details, Shutdown Linux. For Networking: Send a Syslog message. New Escalation You can set up a notification to be sent when an alert has not been reset or addressed for a specific period of time. For example, if an alert is not reset after 30 minutes, Foglight NMS will send another notification to the entire IT Department. New Reset Condition You can set the performance thresholds that need to be met in order for an alert to be reset. This option ensures that the device returns to optimal performance. 9. Click Ok to complete the process. 10. Click Save to save your changes. See Also Escalating Alerts

Escalating Alerts When an alert is not reset by a user, Foglight NMS escalates the alert to one or more users. In order to send the escalated alert to a specific user, you must assign an escalation rank to that user in the User Management section of the Administration View. The escalation rank is the priority by which users are notified. Once you establish the escalation ranking order, you can return to the policy, open an alert, and add a new escalation to it, as well as define the parameters for it. Setting the Escalation Rank For a User 1. In the Foglight NMS Studio, click Configuration -> Administration. 2. Click User Management. 3. In the list of users, select a user to which you want to assign a rank. 4. Click Notifications. 5. Click Add Rule. 6. Select a site in the site drop-down list. 7. In the Escalation Rank field, select a number. For example, if you assign "1" as the rank, then this user is the first person notified when an alert is escalated. 8. Click OK. Adding a New Escalation to an Alert 1. Select a policy to edit and then click the Alerts tab. 2. Select an alert and click Edit Alert. 3. Click the New Escalation link. 4. In the Escalation dialog, do the following to define the escalation parameters: 5. Click OK. In the After field, select the amount of time that passes between each email that is sent to the user. In the Trigger field, select the number of times a user will be notified before the alert is escalated to a different user or is placed back in to "Alert in Process" status.

See Also Managing Alert Notification Rules

Managing Alert Notification Rules For each user you add to Foglight NMS, you can specify who will receive alert notifications by creating a rule in the User Management tool. You can also set which users will be notified when an alert has been escalated. 1. From the Studio, click Configuration -> Administration. 2. Click User Management. 3. Click Notifications. 4. Select a user in the list. You can click Add Rule to add a new rule to the selected user or click Edit Rule to edit an existing rule. 5. Click OK to save your changes. NOTE: You can also access the Alert Notification Rules dialog from the Edit Policy Window. Click the Alerts tab, and then click the Manage Alert Notification Rules link. See Also Escalating Alerts

Setting Up Alerts for Custom SNMP Monitors When you have finished adding your custom monitors, you can set up alerts and conditions for each one by editing the policy for a device. An alert for a custom SNMP monitor is created the same way you create an alert for system monitor. Within a policy, the Alerts section includes a condition for custom SNMP monitors. You can create a new condition for your alert that sets up the notifications and actions for the custom SNMP monitor to make sure you stay informed of any issues before they impact users. To set up an alert for a custom monitor 1. In the Devices View, right-click a device and then click Alerts and Monitors -> Configure For Device. 2. In the Device Edit Monitor and Alerts window, click the Alerts tab. 3. Click Add Alert. 4. In the Alert dialog, click the new condition link and select Custom Monitor. 5. Select a monitor in the list and click Select. You can now assign the appropriate condition criteria and set the time span for the alert. 6. In the Value drop-down list, specify the value. 7. Type a valid integer value in the text box below the Value drop-down list. 8. Select the span and define the trigger criteria. 9. Click OK. The alert condition appears in the Conditions, Actions, and Escalations text box located in the Alert pop-up window. NOTE: You can only set one condition for each custom monitor. If you select a custom monitor that already has a condition, an error message displays. 10. Click OK to save the alert. 11. Click Save to save your changes to the policy. The alert is added to all the devices in that policy. When the monitor interval has elapsed and the condition is met, the alert triggers and displays in the Alert Triggered list. See Also

Creating Custom SNMP Monitors Adding Custom SNMP Monitors to Policies

Creating and Running Scripts Topics in this section Overview of Creating Custom Scripts

Overview of Creating Custom Scripts The scripting feature allows users to add, edit, and schedule custom scripts using any generic script language, including bash, VBscript, Jscript, Perl, and PowerShell. You can register custom interpreters so that any scripting language can be used. In addition, you can package scripts into functional IF-THEN-ELSE logic groups to complete more advanced maintenance and remediation tasks. Scripting is controlled by five functional sections which you can view by clicking the scripting dashboard in the tree view. The five functional sections are as follows: 1. Script Status This section shows the status of scripts that are currently running only. Double-clicking on a status line item will show the target machines that the scripts are running on, the current status for each target, and the current status for each script running on that target. 2. Script Library This section lists all the custom scripts that are currently in the database. These scripts include read-only scripts provided with the software, sample scripts, and custom scripts created by the users. The application supports any scripting language, and individual scripts can be customized to use custom parameter syntax. 3. Script Packages This section lists all the script packages in the database. A script packages organizes multiple scripts into functional blocks, either simple ordered lists of scripts, or IF-THEN-ELSE logical blocks that can check conditions and run different scripts based on the success or failure of the IF conditions. 4. Script Schedules This section lists all the script schedules in the database. A script schedule is a list of script packages than are to be run on a system, along with a schedule for the scripts and a list of target devices on which the lists can be run. Both Windows and Linux script packages can be added to the same schedule, and the packages will only run on the devices for which the packages were designed. 5. Logs This section includes the log output from all scripts that run on the system. Double-clicking on the log output will bring up more details and the full output from the script. Here you can see the results of the script, as well as IP address of the machine, Date, Severity, Schedule Name and Hostname.

Managing Windows Patches Topics in this section Overview of Patch Management Adding Patch Management Groups

Overview of Patch Management You can automatically manage and control critical Windows updates using the Patch Management feature. This feature gives you the ability to make sure that your site's devices are protected with the latest security patches and updates. Patch Management provides you with the following capabilities: Complete automation for patch discovery and deployment Ability to create multiple patch groups to meet your site's needs Real-time alerts for successes and failures Comprehensive history and reporting at the device level Individually manage each update at a granular level You can only create a patch management group on a Windows-based machine with an agent deployed on it. See Also Adding Patch Management Groups

Adding New Patch Management Groups When you create a new patch management group you can You can create a new patch management group do the following: In a new patch management group you can do the following: Add or remove devices Configure a type of update scan Schedule the group to check for updates and install them on a given date and at a specific time Configure the group to automatically download updates Control each individual update at a granular level To add a new patch management group 1. In the Foglight NMS Studio, click Configuration -> Patch Management. 2. Click Add New Patch Management Group. 3. Type a name and a description. 4. Click Add Device Member. 5. Select a device and click Add. 6. Click the Settings tab and do the following: To configure the Windows Automatic Configuration settings, select the Configure Windows Automatic Update Setting and select the appropriate Automatic Update Mode in the drop-down list. Schedule a date and time when the scan will take place. If you have selected to control Windows updates with Patch Management, you can set the date and time when the update is installed. 7. Select an update in the list to edit the patch. You can choose to approve the patch, set it for pending approval, or reject it. 8. (Optional) Select Monitor Windows Updates for a read only list of patch updates. 9. Click Save to save your changes.

See Also Overview of Patch Management

Connecting Remotely to Your site's Network Topics in this section Overview of Connecting Remotely to Your site's Network Using ExpertAssist

Overview of Connecting Remotely to Your site's Network You can connect remotely to any device in your site's network using the following programs: ExpertAssist Remote Desktop Connection (RDP) VNC SSH Telnet Web Browser See Also Using ExpertAssist

Using ExpertAssist ExpertAssist is an advanced, behind the screens remote troubleshooting tool for Windows-based desktops and servers. ExpertAssist can remotely manage devices without interrupting users while they work. It provides more than 45 distinct capabilities to control, manage and gather information from remote computers. These capabilities include file transfer, stopping and starting services, command prompt, registry editing, and local disk manipulation, as well as access to real-time performance information. ExpertAssist provides the following features: Instantly chat online with a site while you have control of their machine - in real-time Resolve issues on your sites' computers behind the scenes without interrupting them as they work and to increase their productivity Transfer files from your site's computer to your computer to quickly resolve issues Real-time remote control of end user computers and servers Reduce site downtime by covering all support scenarios Create and run custom scripts Transfer files by point-to-point Manage registry configuration Over 40 different features to support registry, file system, and performance indicators For more information about integrating ExpertAssist with your product, see the ExpertAssist User Integration Guide. To deploy ExpertAssist in Foglight NMS 1. In Foglight NMS Studio, select a device with an agent deployed on it and then right-click. NOTE: ExpertAssist only works on a device that is an agent. 2. In the Context menu, click Connect -> ExpertAssist.

NOTE: It may take a few seconds for the ExpertAssist login page to appear as the application attempts to initialize and connect. 3. Log in to ExpertAssist. See Also ExpertAssist User Integration Guide

Generating Reports Topics in this section Overview of Reports Running Reports Creating Custom Reports Scheduling Reports Emailing Reports Exporting Reports

Overview of Reports You can generate an instant report or schedule a report for all the data that Foglight NMS collects from the devices in a network. Reports can be instantly printed, emailed, and saved. You can drill-down into specific time periods and events or change the chart type. The report scheduler allows you to email reports on a daily, weekly, or monthly basis to colleagues and executive management. Use the Reports feature to do the following: Deliver critical information about devices that is easy to read Quickly configure time periods and data types for any device Schedule reports for executive management Plan future resource requirements using historical trend data See Also Running Reports Creating Custom Reports Scheduling Reports Emailing Reports Exporting Reports

Running Reports You can run an instant report for any device in the network, which displays in the Reports View. Once you designate a device, any report that you click on in the list automatically generates a report for that device. NOTE: You can brand any report with your own company information using the Branding Configuration tool in the Administration section of Foglight NMS. Running an Individual Report An individual report is a report whose scope is limited to one device in a network. 1. In the Foglight NMS Studio, click Reports on the main menu. 2. From the list of reports, double-click an individual report that you want to run. 3. Select the device that you want to display in the report and click OK. The report displays

as a graph or a list in the Reports View. Running a Group Report A group report is a report whose scope includes data from multiple devices. Group reports include Network Performance Reports, Network Traffic Flow Reports, VoIP Reports, and Custom Reports that have been designated as group reports. 1. In the Reports View, from the list of reports, double-click a group report that you want to run. 2. In the Select Target dialog box, select the devices that you want to display in the report and click OK. See Also Changing the Device in a Report Changing the Report Type Changing the Report Period

Changing Devices in a Report For individual reports, once you select a device to run a report against, all other reports that you generate will use the previously selected device. To generate an individual report using the data collected from a different device, you must change the device. You can select a device from any of your sites' networks. 1. In the Foglight NMS Studio, click Select Device. 2. Select a new device to run the report against. 3. Click OK. The report displays as a graph or a list in the Reports View. For group reports, you can also change which devices to display in the report. 1. In the Foglight NMS Studio, click Select Device. 2. In the Select Target dialog box, select a different site in the drop-down list and/or select a different policy. 3. Click OK. See Also Running Reports

Changing the Report Period You can change the report time interval by using the Report Period drop-down list in the Reports View. This option allows you to view data for the device over different periods of time. See Also Running Reports

Changing the Report Type You can choose to view any of the reports in the list at any time. Each new report you run uses the same device that you previously selected. There are 2 ways you can change a report type in the Reports View. In the Reports drop-down list, select the new report that you want to view. Double-click a device in the Reports list. See Also Running Reports Changing the Device in a Report Changing the Report Period

Creating Custom Reports You can show certain types of data in a custom 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 location. NOTE: You must be a System Administrator to create a custom report. To start creating a custom report 1. In the Reports View, click Report Manager. 2. In the Custom Report Template Manager, click Add. Follow the steps below to complete the process of creating a new custom report. Page 1 of the Custom Report Template Wizard: What kind of custom report is it? 3. In the Custom Report Template Wizard, type a name and a description for the custom report. NOTE: The description appears only in the wizard and not in the report 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 report. 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 Report For?, do the following: If you want the custom report to be an individual report, which limits the devices displayed in it to one, select Single Device If you want the custom report to be a group report, which allows you to select all the devices in a policy or all the devices across your sites, select Multiple Devices If you want the custom report to include all the devices in a site's network, select Devices For Single site 6. For Choose Report Type, select how you want to display your results in the custom report. NOTE: Depending on how you group your data, not all of the report type options will appear.

7. Click Next. Page 2 of the Custom Report Template Wizard: What and how does the data appear in the custom report? 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 report. 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 Report Template Wizard: How is the data sorted in the custom report? 12. To make a data field the primary field by which the rows of data in the report 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 report 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. 18. Click Finish. Your new custom report appears in the list of reports under the Custom Reports category.

See Also Running Reports

Scheduling Reports You can schedule reports to run and then you can distribute them by email to your colleagues and executive management. The report scheduler allows you to email reports on a daily, weekly, or monthly basis. 1. In the Reports View, click Scheduled Reports. 2. In the Scheduled Reports dialog, click Add. 3. Locate the report that you want to schedule and select it. A report dialog box appears. 4. In the Description field, type a name for the report 5. (Optional) Disable the report by deselecting the check-box 6. In the Report Period drop-down list, select the time interval you want to show in the report. 7. Click Notifications and type the email address of the recipient of this report. Click OK. 8. Click Recurrence and select how often during a given time period you want the report generated and select the dates when you want to start and stop generating the report. 9. Click Select Target to select a device to run against in the report. 10. Select a format for the report. You can send the report as either a PDF or HTML file. 11. Click OK to schedule the report and complete the process.

Edit a Scheduled Report 1. In the Scheduled Reports dialog, select a report to edit. 2. Click Edit. 3. Make your changes in the report dialog. 4. Click OK to save your changes. Remove a Scheduled Report 1. In the Scheduled Reports dialog, select the report that you want to delete. 2. Click Remove. NOTE: You can also click Remove All to delete the all the scheduled reports at one time. 3. When the message appears, click Yes.

Emailing Reports You can send an HTML or PDF version of a report by email. 1. In the Reports View, click Email and then select a format for the report that you want to send. 2. In the Report Email Information dialog, type an email address for the main recipient of the report. 3. (Optional) In the CC field, type a secondary email address. 4. Click OK to send the report. See Also Running Reports

Exporting Reports You can export a report to any location in your network. 1. In the Reports View, click Export. 2. In the Save As dialog, do the following: 3. Click Save. Select where you want to save your report In the File Name field, type a name for the report In the Save As Type field, select the file type. You can export the report as a HTML or PDF file. See Also Running Reports Emailing Reports

Mapping Networks Topics in this section Overview of Network Maps Touring the Network Map User Interface Creating New Network Maps Adding Groups Editing Network Maps Viewing Device Details

Overview of Network Maps Foglight NMS provides the Network Mapping feature, which allows you to create a functional and interactive topology of your sites' networks. You can use your network maps to quickly view the status of a network, find out if there are any broken connections between devices, determine where devices are located in an office, and view the details of any device in the map. For existing network maps, Foglight NMS can detect if the map is out of date and automatically begin to retrieve the latest monitored data. Foglight NMS will also update your map by removing devices that are no longer part of the network. NOTE: To create and view network maps, you need to install Adobe Flash Player. See Also Touring the Network Map User Interface Creating Network Maps Adding Groups Editing Network Maps Viewing Device Details

Touring the Network Map Editor User Interface

The Main Elements of the Network Map Editor Window 1 Main Editor Toolbar: Use these buttons to add or remove background images, update your map to retrieve the latest monitored data, and add devices or groups to your network map. 2 Zoom In / Zoom Out Buttons: You can choose how much you want to see of your network map. You can zoom in to get a close-up view of your network map or zoom out to see more of it at a reduced size. To return to the default view, click the arrow button. 3 Pan Window: You can pan to reposition the view in your network map. Panning does not change the location or magnification of nodes in your network map; it changes only the view. You can also double-click anywhere in the pan window to quickly reposition your network map. 4 Device or Node: A network map is made up of nodes, where each node represents a device in a network. You can select multiple nodes at a one time to edit them simultaneously. To select multiple nodes, click and hold your pointing device and drag your cursor over the nodes that you want to select. NOTE: In the Network Map View, you can double-click a device to view its details. 5 Connections Between Nodes: Each connection, represented by a line, links one node to one or more other nodes. The direction of a line indicates the source of the data. NOTE: In the Network Map View, if a device is running as expected, the line is green. If a device is down, the line is red. If there is an issue with a device, the line is green; however, a yellow dot appears next to the device. Black lines are drawn to unmanaged devices, which are devices that do not provide any Port Map data. 6Device Layout Drop-Down List: When you select a new device layout in the drop-down list, Foglight NMS automatically rearranges the nodes and their connections in your network map. 7 Group Icon: You can select a group to add devices to it, delete it from your map, change the size of the icon, or rename it.

8 Node and Group Edit Buttons: Use these buttons to remove a device or group from your network map or change the size of it. The Rename Selected Group button appears only when you select a group.

Creating a Network Map Each network map that you create is unique to a site and cannot include devices from other sites' networks. 1. In the Studio tree view, right-click Network Maps, and then click Add New. 2. In the Add Network Map dialog, type the name of your new map. 3. Click OK. 4. In the Network Map-Select Device(s) to Add, select one ore more devices to add to your map and then click Add.

NOTE: If you want to remove a device from the list, select it and then click Remove. You can continue to add your other devices to your network map by clicking the second Add button at the bottom of the dialog box. 5. Click Save to save your changes. See Also Editing Network Maps Adding Groups

Adding Groups Creating a group in your network map allows you to group your devices together according to type of device, site, or site. For example, if you have a site that has multiple offices in different cities across the country, you can download an image of the country and create a group for each site. You can then appropriately position those groups on the background image. To move a group around, select a group node and drag it to the appropriate location on the background image. To add a group 1. Open the Network Map Editor. 2. In the toolbar, click Add Groups. 3. In the Add Network Map Child, type a name to describe the group and then click OK. 4. Click Save to save your changes. To add devices to a group 1. Select a group and double-click. 2. Click Add Devices.

3. In the Network Map - Select Devices To Add, select one or more devices. 4. Click Add. See Also Editing Network Maps

Copying Network Maps You can make a copy of an existing map by doing the following: 1. In the tree view, right-click the network map that you want to copy. 2. Click Copy. 3. In the Copy Network Map, click Yes. See Also Editing Network Maps

Editing Your Network Maps Initially, the network map that you create shows only the devices that you selected. When you edit a network map, you can make the following changes: Add a background image, such as an office layout or blueprint. Organize your devices into a group by type Move the nodes around the map by dragging and dropping them Add new devices Resize the nodes Select a different layout for the devices Update your map to show changes to the network, if any Rename the map or group To edit your network map You can select multiple nodes at a one time to edit them simultaneously. To select multiple nodes, hold your left mouse button and drag your cursor over the nodes that you want to select. 1. In the tree view, right-click the network map that you want to edit.

2. Click Edit. The Network Map Editor window appears. NOTE: The following steps are optional. Click the corresponding link for more information. 3. Click Reset Background to clear a background image from the network map. 4. Click Set Background to add a background image to your network map. 5. Click Rebuild Relationships to update your map (if there were any changes to the network) and redraw the lines between devices. 6. Click Add Devices to add more devices to the network map.

7. Click Add Group to add a child group to the network map. You can also edit the group node by changing its name and size. 8. To remove a device from the network map, select the device and then click Delete. 9. To change the size of a node, select the node and click Set Size. 10. To move the devices around your map, select one or more devices and then drag and drop it to the desired location. 11. In the drop-down list, select a different layout. You must click Save to save your changes. See Also Touring the Network Map User Interface Setting the Background Resetting the Background Rebuilding Relationships Adding Groups Copying Network Maps

Setting the Background Adding a background image, such as an office layout image, to your network map allows you to visualize exactly where devices are located in your site's office. If you have a site that has multiple offices in different cities across the country, you can download an image of that country and create a group for each site. You can then position those groups appropriately on the background image. For more information about groups, see Adding Groups. To move devices and groups around on your background image, select and drag a node to the appropriate location on the background image and then drop it. You can add a background image to your map by clicking the Set Background button in the Network Map Editor and then selecting an image file.

See Also Editing Network Maps Resetting the Background

Resetting the Background If you added a background image to your map you can delete it by clicking the Reset Background button in the Network Map Editor. See Also Editing Network Maps Setting the Background

Rebuilding Relationships When you rebuild device relationships in a network map, if anything has changed in the network, Foglight NMS redraws the lines between each device. If your site removes a device or changes the way one device is connected to another the lines between the devices are automatically updated. If there are any changes to a network, you can refresh your network map by clicking the Rebuild Relationships button. See Also Editing Network Maps

Deleting Network Maps You can delete a network map by doing the following: 1. In the tree view, right-click the map that you want to delete. 2. In the context view, click Remove. 3. In the Remove Network Map dialog, click Yes. See Also Editing Network Maps

Viewing Device Details Network maps provide a quick way to access the device details page, which shows a device's performance and key metrics. You can view the device details for any device in your network map. 1. In the tree view, select a map. 2. In the network map, double-click a device. 3. Use the back button to return to your network map.

Integrating Foglight NMS Topics in this section Overview of Foglight Integration

Overview of Foglight Integration You can integrate Foglight NMS with Foglight and vfoglight. Any device and any alert associated with a device can sync up with the Foglight Management Server. Foglight will display alarms, and show which networking devices are impacting application performance across physical or virtual environments. You can drill into network device details directly by clicking from within the Foglight console. To view the Foglight NMS Integration Guide, go to https://support.quest.com/. You must create an account or sign in to your account to view or download Quest Foglight documentation.

Open API Topics in this section Overview of the Web Service Entry Point API

Overview of the Web Service Entry Point API Use Foglight NMS monitoring data in other applications or build your own reporting functionality using our Open API. The Open API provides standard web service methods for extracting monitoring data from Foglight NMS and returning it in HTML, XML, or JSON formats. A sample.net application is provided with source code that has examples for using all of the web service methods. You can retrieve the Open API files and related documentation from the Program Files folder and then open the OpenApiSdk.zip file in the server folder.

Administration Guide This guide provides information about the configuration options available in Foglight NMS. You can access the Administration View by clicking Configuration -> Administration in the Studio's main menu. The Administration View is made up of 2 sections: the configuration options and a platform summary. The platform summary shows the information about your Foglight NMS Platform Server, including: IP Address Current version of Foglight NMS installed on it, Number of interfaces currently being monitored Number of devices in your database Number of users Refer to the topics in this section for more information on configuring your administration settings. Topics in this section Agent Migration Auto Patch Settings Baseline Configuration Branding Configuration Check for Updates Credential Store Flow Configuration License Update Log Alert Configuration Port Management

Retention Configuration SMTP Settings Studio Deployment User Management

Agent Migration 1. From the Foglight NMS Studio, click Configuration -> Administration. 2. In the System section of the Administration View, click Agent Migration. 3. Select the site to migrate agents from and to. 4. Choose one or more devices in the list and click Migrate. Agent migration is complete. The agent appears in the new site in the devices section.

Auto Patch Settings Select the Automatically Patch check-box to automatically receive patch updates. If you disable auto patch settings, you need to use the Check For Updates option to manually update your software. See Also Updating Your Product

Baseline Configuration The performance baseline automatically analyzes collected data to identify changes in network behavior and establishes a baseline to represent the regular and expected activity of the devices in a network. The established baseline accurately reflects your organization s use of its IT infrastructure by taking into account patterns and variations in usage. For example, one such pattern may be an increase in processor utilization on Monday mornings at 9:00 am. The performance baseline continuously logs subsequent activity of a device and compares it to the baseline. When Foglight NMS detects irregular behavior, it sends out a qualified alert. This alert contains details that you can use for troubleshooting and remediation. Helps generate reports about the device monitors that vary during a business cycle that are more accurate Identifies abnormal increases and decreases in network utilization, performance, and quality, which cuts down the repair time Eliminates false positive alerts caused by normal behavior on the network Reduces manual configuration for administering setting and thresholds To set a baseline 1. In the Foglight NMS Studio, click Configuration -> Administration. 2. Click Baseline Configuration. 3. In the General section, determine the number of weeks from which you want to a calculate baseline. This setting can range from 1 to 4 weeks. You will start to receive alerts based on performance baseline after one week of data collection and analysis, even if your performance baseline is set for 4 weeks. 4. In the Weekday Grouping section, determine the week day groupings. You can group the days of the week to make a baseline more accurate and reflect how the network is utilized in your company. To group any set of days, simply give those days the same number. For example, if your network load is the same Monday to Friday but lower on the weekends, then set Monday to Friday to the same number (for example, 1) and set Saturday and Sunday to a different number (for example, 2). If you want each day to have its own baseline, set each day to a different number. NOTE: All settings take effect immediately, and can be changed at any time.

Branding Configuration You can brand this software by uploading your company icon and background images. These images rebrand the software for all users that log in to the Studio or Web Studio. Use the Branding Configuration dialog to implement the look and feel of Foglight NMS for your particular brand. Your changes will take effect the next time the user logs into the Studio or Web Studio. 1. Enable branding: Check the box to enable this feature. 2. Company name: This name will appear in all dialogues in the Studio. 3. Contact email: Set the email address that will appear. 4. Copyright text: The entered text will appear to the right of the copyright logo. 5. Logo Image: Click the Set button to browse for a logo image. 6. Background Image: Click the Set button to browse for a background image. 7. Logo/Background preview: Displays a preview of the changes.

Check for Updates Foglight NMS comes with a robust software updating system that makes sure the product is always running the latest release. To manually update 1. In the Studio, click Configuration -> Administration. 2. Check For Updates to see if an update is available. 3. Click Update Now to apply the software updates. The Program will close and open automatically. To automatically update Upon launching Foglight NMS, the software will check for any updates available at the patch server. The software automatically pulls the updates and stores them in cache. The updates are applied the next time the software is launched.

Flow Configuration Foglight NMS can filter network flow data (NetFlow, sflow, and Jflow) based on size of conversation. Set the noise threshold for individual conversations (source IP, destination IP, source port, destination port and protocol) for each interval. Foglight NMS discards conversations that fall below the threshold for each time period. Filter thresholds: 1-minute-data noise threshold, 5-minute-data noise threshold, 30-minute-data noise threshold, 2-hour-data noise threshold, 1-day-data noise threshold.

License Update The License Update Wizard provides you with information about your current license and allows you to attach a product to the license, if necessary. It will also download updates for the following components: Network Flow Analyzer Module, Remote Agent Module, VoIP Monitoring Module, and Wireless Monitoring Module. NOTE: To configure the proxy settings, click Configure Proxy Server. 1. In the Foglight NMS Studio, click Configuration -> Administration. 2. Click License Update. 3. To attach a product to the license, type the product key into the Product Key Field and click Apply. 4. Click Finish.

Port Management Port Management configuration allows the administrator to change the display of certain tcp ports. For example, tcp port 5054 can be configured to display login in the Tcp Monitor configuration screen. The Port Management settings also appear in Netflow / Ptflow Application results as well. Configuration Step1: Select Port Management icon from the list of utilities in the administrrations section. Step 2: Scroll down the list to re-name a specific port. Or, scroll to the bottom of the list to add a new port and description. Step 3: Click OK to complete the process.

Retention Configuration You can adjust the data retention settings to monitor certain data types. These types include DNS, MAC, ports, network adapter configuration, hardware inventory, software inventory, process, Windows services, Exchange, SQL Server, active directory, base device information, system event log, application event log, sevent log, Syslog, Cisco config, HTTP, SMTP, POP3, network services, and network addresses. Any administrator can adjust the number of days retained. 1. In the Foglight NMS Studio, click Configuration -> Administration. 2. Click Retention Configuration. 3. In the pop-up window, modify any of the settings. 4. Click OK.

SMTP Settings Foglight NMS sends alerts notifications and scheduled reports by email. These alerts and reports are critical components for any IT department to stay informed of any issues. It is recommended that you configure your SMTP settings as soon as possible. 1. Assign a Configuration Name. 2. Assign the From Email Address. If email will only be sent to internal email addresses, then the From email address can be fake. (for example, x@yourcompany.com) If email will also be sent to external email addresss like Gmail, then the From email must be a valid email address. 3. Configure the SMTP Server and Port. The default is Port 25. 4. Enter your Logon User Name and Password. 5. If your email server requires secure socket layer (SSL) encryption, then enable by selecting the checkbox. 6. Save your SMTP Settings. 7. Select Test Account Settings. Enter an email address to verify that you have configured it properly. A test email will be delivered to the email account.

Studio Deployment Use this option to install the thin client studio on a site's machine. 1. Studio Deployment Steps 2. In the Foglight NMS Studio, click Configuration -> Administration. 3. Click Studio Deployment. 4. Select a site. 5. Click Copy URL or Email URL to select the location. You can paste the URL into a Web browser to launch the Studio.

User Management You can create, edit, manage, and delete additional users. The User Management option has three types of users: System Administrator, Site/site administrator, and Read-only. To create a user configuration Create a new user. Assign the user to desired site/site. System administrator can view and make changes to all sites/sites. Also, the system administrator can create/manage users of all levels. The organization/site administrator can view/manage particular site(s) as determined by a system administrator. The organization/site administrator cannot create/manage additional users. You must provide information for the following fields for each new user: Username: login name Email: The associated email address Authority: Set the user s privileges. The three levels are Read-only, site/organization administrator, System administrator Password / Verify password: Set the user s password Invite user to connect via Hostname/IP: sends an email invitation for the user to connect with the selected Hostname/IP sites/organizations: Select the site(s)/organization(s) that the user will have access to Preferences: Set the Auto-run go live settings when device details is selected

Legal Notices This section contains information about Quest Software's copyright and trademarks.

Copyright 2011 All rights reserved. Under the copyright laws, this manual or the software described within, can not be copied, in whole or part, without the written consent of the manufacturer, except in the normal use of the software to make a backup copy. The same proprietary and copyright notices must be affixed to any permitted copies as were affixed to the original. This exception does not allow copies to be made for others, whether or not sold, but all of the material purchased (with all backup copies) can be sold, given, or loaned to another person. Under the law, copying includes translating into another language or format. Specifications and descriptions subject to change without notice.

Trademarks The name ScriptLogic Corporation, the software, the product name ScriptLogic sl360 Tool Suite, and the ScriptLogic logo are registered trademarks of ScriptLogic Corporation. ScriptLogic Corporation (the Software) is copyright 2011 by ScriptLogic Corporation. All rights are reserved. The name PacketTrap Networks, the software, the product name PacketTrap pt360 Tool Suite, PacketTrap IT, Foglight NMS, Perspective MSP, and the PacketTrap logo are registered trademarks of PacketTrap Networks, Inc. PacketTrap Networks (the Software) is copyright 2011 by PacketTrap Networks, a division of Quest Software. All rights are reserved. Microsoft Windows 98, Windows NT, Windows 2000, Windows XP, Windows Server 2003, Vista, Windows 7, Internet Explorer, and Active Directory are trademarks or registered trademarks of Microsoft Corporation. Adobe, Acrobat, and Acrobat Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the U.S. and/or other countries. Firefox is a trademark of the Mozilla Foundation. Other product and company names mentioned herein may be trademarks and/or registered trademarks of their respective companies and are the sole property of their respective manufacturers.