Cluster Manager

Add Peer

The following buttons enable you to add a new peer to your cluster.

• Add Peer

• Clear Failed

• View Cluster Logs

These buttons work in conjunction with the Integration tab found at the appliance level on the Cluster Manager. When you want to add a new appliance to your cluster as a new peer, you start the integration process on the new appliance and finish the integration process on an appliance that is already in the cluster.

See the Integration section later in this chapter for instructions on how to add a new peer to your cluster.

Peer Statistics

The Peers tab displays the list of peers in the cluster with information that includes the peer capacity.

• Name - Displays the name of the peer. Click the name link to display the peer level Peer Overview tab to display additional peer specific statistics. See the Peer Overview section below.

• IP Address - Displays the IP address of the peer.

• Model - Displays the SevOne appliance model: PAS = Performance Appliance Solution, DNC = Dedicated NetFlow Collector, vPAS = Virtual Performance Appliance Solution.

• Elements - Displays the number of elements/objects the peer polls. The Object Types page, Object Rules page, and Object Manager enable you to manage the elements/objects the peer polls.

• Interfaces - Displays the number of interfaces you allow the peer to process incoming and outgoing flow data. The Flow Rules page and the Flow Interface Manager enable you manage interfaces and flow load.

• Flow Load - Displays the flow load the peer monitors. Each interface is 300 elements for license purposes and the flow load that displays here is equal to the number of interfaces you allow the peer to process multiplied by 300.

• Telephony - Displays the element count the peer uses to poll telephony data. The Telephony Browser enables you to view telephony elements.

• Capacity - Displays the sum usage of elements, flow, and telephony the peer uses. This displays the number of elements the peer is licensed to use and the percentage of the license capacity the peer uses.

• Status – Displays Ready to Use for all peers that are completely integrated into the cluster. Displays other status messages for peers you add to the cluster as they are integrated into the cluster.

Alerts

The Alerts subtab enables you to define alert settings that affect Alerts page and related pages workflows.

1. In the Alert Duration field, enter the number of days' worth of alert information to store.

2. Select the Acknowledge Alerts for Disabled Objects check box to clear alerts for objects that you disable.

3. Select the One Trap per Alert check box to send only one trap per alert. Leave clear to send a trap every time a threshold triggers, even if an alert already exists.

4. Select the Show Alerts in Title check box to display the number of alerting devices and the highest alert severity level in the web browser tab.

5. Click the Alerts Refresh Time drop-down and select the frequency at which to refresh the Alerts page. For large clusters that trigger many alerts, you should consider setting this higher than the 30 second default setting. The Alert engine runs every three minutes to trigger alerts and you cannot configure the alert engine via the UI.

6. Click the SevOne NMS Trap Revision drop-down and select 1 for revision one traps or select 3 for revision three traps. This defines what trap data SevOne NMS sends to your fault management system. If you change this you will need to update how your fault management system receives traps from SevOne NMS. See the Trap Revisions chapter for details.

7. Click Save to save the Alerts settings.

Baseline

The Baseline subtab enables you to define how to create baselines. Baselines are used in report workflows and policy/threshold workflows.

Exponential Smoothing: SevOne NMS uses a rolling average formula known as Exponential Smoothing for baseline calculation. This uses the scalar value of the previous average and the newly collected value to compute the new average. There is no reliance on the actual data points collected during the previous <n> weeks.

The value of (old weight / (old weight + new weight)) is the smoothing factor. The smoothing factor affects the resistance to change that new data has on a baseline. This value ranges between 0 and 1 and a higher smoothing factor causes a greater resistance to change.

As the smoothing factor approaches 1, the impact of each new value on the existing baseline approaches zero. This approach calculates the average and the standard deviation. No trending (slopes) is considered in the calculation as each baseline data point is computed individually.

1. In the Granularity field, enter the granularity of a baseline in seconds. The default is 900 seconds (15 minutes) which takes all data during a 15 minute time span, averages the 15 minutes' worth of data, and stores that average data point for every 15 minutes of the week for a total of 672 data points in order to create baselines.

2. In the Baseline Weight field, enter the weight to apply to existing baselines. A larger number here reduces the impact of new data on the baseline (maximum 52).

3. In the New Data Weight field, enter the weight to apply to new data. A larger weight here causes new data to change the baseline faster (maximum 52).

4. Click Save to save the Baseline settings.

Devices

The Devices subtab enables you to define device definition settings for the Device Manager and related workflows.

1. Select the Prevent Duplicate IP Addresses check box to prevent the addition of a device with an IP address that is already in SevOne NMS.

2. Select the Discover Trap Destinations check box to discover trap destinations on devices.

3. In the Device Names section:

   1. Select the Resolve Device Names check box to update the device IP address to the resolved address. If you do not enter the correct IP address when you add a device (or an IP address changes) and DNS can resolve the device's name, the device IP address in SevOne NMS updates upon discovery.

   2. Select the Lookup Hostnames check box to rename devices whose names are IP addresses to their hostname. If you enter an IP address as a device name and a reverse DNS lookup can resolve the IP address, the device name in SevOne NMS changes from the IP address to the device's hostname upon discovery.

   3. Select the Lookup SysNames check box to rename devices whose names are IP addresses to their sysName. If you enter an IP address as a device name and DNS cannot resolve the device name or you do not select the Lookup Hostnames check box, the device name in SevOne NMS changes to the SNMP sysName upon discovery, if possible. The device name updates during discovery only if the current name is an IP Address. This check box does not cause the device name to change in SevOne NMS if you change the sysName on the device, in which case you must manually change the device name in SevOne NMS.

   4. Select the Force Hostnames check box to use DNS to change all device names to their host names if DNS can resolve the device name.

4. In the Device Name Masks section, view the device name masks you define to mask (hide) device names.

   1. Click Add to display a pop-up.

   2. In the text field, enter a valid Perl regular expressions.

   3. Click OK.

   4. Repeat to define the list of expressions.

   5. Click the arrows to move the expression up or down in the list to arrange the sequence of expressions. The mask process stops when a match is found.

5. In the Time Information section:

   1. Click the Default Date Format drop-down and select the date format to use by default. Each user can override this setting on the Preferences page.

   2. Click the Default Time Zone drop-down and select the time zone to appear by default in the device definition Time Zone fields from the Device Manager. Reports use the time zone that each user associates with their user profile from the Preferences page.

   3. In the Time Zone Filter field, select the check box next to each country for which you want time zones to appear available for selection from the Time Zone drop-down lists. You must select at least one country time zone.

6. Click Save to save the Device settings.

Discovery

The Discovery subtab enables you to define the way device discovery works to find the objects to poll.

1. Click the Device Note Severity Level drop-down and select the severity level at which to create device notes during discovery.

2. Select the Allow Object Entries for Disabled Objects check box to create entries for objects that are disabled by object rules. If you clear this check box after discovery has discovered objects, those objects will be deleted via the Missing Objects - Days Until Delete setting described below.

   When you select this check box, you can negatively affect the system performance to the point of failure if the number of disabled objects exceeds 300% of the total system capacity.
   For most implementations this should not be an issue. For very large networks or for networks that contain devices with very large numbers of objects, contact SevOne Support.

3. In the Thread Pool section:

   1. In the Low Priority Size field, enter the number of low priority devices to simultaneously discover. Automatic discovery is low priority. The default setting is usually ideal for most implementations and there is a maximum thread pool of 100 devices that can be simultaneously discovered. More threads use more CPU and RAM so you should reduce this number and/or the High Priority Size number if you notice system slow down.

   2. In the High Priority Size field, enter the number of high priority devices to simultaneously discover. User initiated discovery is high priority.

4. In the Missing Objects section:

   1. In the Days Until Disable field, enter the number of days to wait before an object that is not found during discovery is marked disabled. Enter 0 (zero) to disable missing objects as soon as SevOne NMS determines an object is missing.

   2. In the Days Until Delete field, enter the number of days to wait before an object that is not found during discovery is deleted. Enter 0 (zero) to delete missing objects (and all associated data) as soon as the object is determined to be missing. The value you enter in the Time Until Delete field must be greater than the value you enter in the Time Until Disable field.

5. In the Administrative Status section:

   1. In the Enable Up Objects field, enter the number of days to wait before an object that is administratively up is enabled. Enter 0 (zero) to not use this feature.

   2. In the Disable Down Objects field, enter the number of days to wait before an object that is administratively down is disabled. Enter 0 (zero) to not use this feature.

6. In the Operational Status section:

   1. In the Enable Up Objects field, enter the number of days to wait before an object that is operationally up is enabled. Enter 0 (zero) to not use this feature.

   2. In the Disable Down Objects field, enter the number of days to wait before an object that is operationally down is disabled. Enter 0 (zero) to not use this feature.

   3. Select the Preserve Max Values check box to enable SevOne NMS to update the maximum value for indicators on objects that are operationally down.

7. In the VMware section, select the Resource Pool Device Group check box to automatically create a device group on the Device Groups page for each resource pool discovery finds on the vCenter.

8. Click Save to save the Discovery settings.

Duration

The Duration subtab enables you to define how long to store device history data, TopN report data, and trap data. If you are unfamiliar with the consequences of these settings, contact SevOne Support.

1. In the Device History Duration field, enter the number of days to store Debug severity level device history. Info severity level history is stored for twice as long, Notice severity level history twice that, and so forth.

   Example: Enter 7 to store Debug level device history 7 days, Info = 14 days, Notice = 28 days, Warning = 56 days, Error = 112 days, etc.

2. In the Short Term Hourly Duration field, enter the number of days to store TopN report data in the hourly data buckets (between 2 and 7).

3. In the Short Term Six Hour Duration field, enter the number of weeks to store TopN report data in the six hour data buckets (between 2 and 7).

4. In the Short Term Daily Duration field, enter the number of months to store TopN report data in the daily data buckets (between 2 and 7).

5. In the Logged Trap Duration enter the number of days to store logged traps for display on the Logged Traps page.

6. In the Unknown Trap Duration field, enter the number of days to store unknown traps for display on the Unknown Traps page.

7. Click Save to save the Duration settings.

Email

The Email subtab enables you to define the email server that SevOne NMS uses to email reports and alerts.

1. In the Email Server field, enter the host name or IP address of the SMTP email server for SevOne NMS to use to send emails.

2. In the Username field, enter the user name SevOne NMS needs to authenticate onto the email server.

3. In the Password field, enter the password SevOne NMS needs to authenticate onto the email server.

4. In the Email Sender field, enter the email address to appear as the sender of the emails. This must have a valid email address format.

5. In the Email Sender Name field, enter the name to appear as the sender of the emails.

6. In the Alerts Email Subject field, enter the text to appear in the Subject line of alert emails. When you leave the Multiple Alerts Per Email check box clear, this field supports the following variables: $severity - Alert severity text form, $severityNum - Alert severity numeric form, $deviceName - Name of alerting device, $singleAlertMsg - Combination of severity and device name with format $severity: $deviceName.

7. In the Reports Email Subject field, enter the text to appear in the Subject line of report emails. Supports the following variables: $name - Report name, $id - Report ID

8. Select the Multiple Alerts Per Email check box to place multiple alerts in the same email. Leave clear to receive each alert in a separate email. If you select this check box, the Alerts Email Subject does not include variables.

9. Select the Email Cleared Alerts check box to send an email when an alert clears.

10. Click the Connection Security drop-down and select a connection security protocol.

11. In the Port field, enter the port number on the email server for SevOne NMS to use.

12. Select the Compress Emailed Reports check box to compress the size of email attachments. Perform the following steps if you select this check box.

    1. In the Compress Reports Larger Than field, enter the minimum report size to compress. All smaller reports are not compressed. Enter 0 (zero) to compress all emailed reports.

    2. In the Image Quality field, enter how much to compress images. 10 = no compression and the best quality and 1 = more compression and less quality.

13. Click Send Test Email to send a test email to the email address you associate to your user profile from the email sender through the email server.

14. Click Save to save the Email settings.

FlowFalcon

The FlowFalcon subtab enables you to define how to collect and process raw flow data and aggregated flow data used in FlowFalcon Reports. An example at the end of this section sums up many of the following settings.

1. * Select the Store Raw Flow check box to collect and store raw flow data. Most FlowFalcon views use raw data which provides more specificity in the result set at the trade off of longer report execution times and less historical data availability.

2. * Select the Store Aggregated Flow check box to collect and store the most relevant flow data in an aggregated format that aggregated FlowFalcon views use for faster report execution times.

3. * In the Raw Flow Duration field, enter the number of days' worth of raw flow data to keep. Gigabytes of raw flow data can accumulate quickly.

4. * In the Raw Flow Data Size field, enter the maximum amount of disk space to allocate for raw flow data.

5. * In the Write Interval field, enter the number of seconds to collect flow data before creating a flat file and writing the data to the disk (recommend 60). A longer write interval results in fewer (but larger) flat files for raw data and smaller tables for aggregated data. See example below.

6. Select the Drop Long Flows check box and enter the maximum number of seconds to consider flow data "long" in the Max Flow Duration field. This drops flows when the flow's duration exceeds the write interval. Long flows are usually due to improper router configuration. This setting triggers an administrative message that appears upon log on to inform you to review the router configuration. Suggested Max Flow Duration is ~2x the Write Interval from the previous step.

7. Select the Enable MPLS Attribute Mapping check box and enter the number of seconds for how frequently to read the map files and to refresh the mapping in the MPLS Attribute Mapping Refresh Interval field. This enables you to map v9 NetFlow template data from core "P" routers for reports that use the following fields in FlowFalcon views: 45050: Customer Client IP, 45051: Customer Client Subnet, 45052: Customer VRF Name, 45053: Customer Application IP, 45054: Customer Application Subnet, 45055: PE Ingress IP, and 45056: PE Egress IP.

   Map files are customer specific. The MPLS Flow Mapping page enables you uploaded the two required map files into SevOne NMS.

8. * In the Aggregation TopN field, enter the number of results (50-1000) to store for each aggregation per each write interval. This consumes disk space and is the maximum number of individual results that an aggregated FlowFalcon view can display.

9. In the Hide Inactive field, enter the number of days to display data for an inactive device or interface before the device or interface is considered inactive and its information is hidden. A device or interface is considered inactive if it does not send data to SevOne NMS.

10. In the Purge Inactive field, enter the number of days to store data for an inactive device or interface. Enter 0 (zero) to never purge data.

11. In the Incoming Port field, enter the port number on the SevOne appliance to listen for flow traffic.

12. Click the Raw Data Compressions drop-down and select the compression method for raw data files. More compression requires less storage, but more CPU is necessary to read the data. Select None, GZip, or BZip2.

13. Select the Advanced FlowFalcon Views check box to display a Metrics drop-down field on the FlowFalcon View Editor, the Object Mapping page, and the FlowFalcon Reports page. The Metrics drop-down enables you to create and select FlowFalcon views that monitor Medianet data in networks that use Cisco Medianet and to monitor response time metrics in networks that use Cisco NAM devices.

14. Select the Display Flow Sample Rates check box to display the sampled flow rate on FlowFalcon reports that contain split interfaces and to display an additional column on the Flow Interface Manager for sampled data. FlowFalcon reports with sampled data display a message. Interfaces that are not sampled use a sample rate of 1X.

15. Select the Create Egress Records When Not Available check box to automatically create egress records for ingress interfaces that do not receive egress records. Leave clear if your devices support bot both ingress and egress interface flow export.

16. Click Save to save the FlowFalcon settings.

FTP

The FTP subtab enables you to define the FTP destination settings for SevOne NMS to use when you send a report via FTP.

1. In the Server field, enter the IP address or host name of the FTP server where SevOne NMS is to send reports.

2. In the Port field, enter the port to which SevOne NMS is to send reports.

3. In the Username field, enter the user name SevOne NMS needs to authenticate onto the FTP server.

4. In the Password field, enter the password SevOne NMS needs to authenticate onto the FTP server.

5. In the Path field, enter the path to the location on the FTP server where you want the report to be sent.

6. Click Test FTP Settings to verify that your FTP settings work correctly.

7. Click Save to save the FTP settings.

General

The General subtab enables you to define general system settings.

1. Click the Log Entry Severity Level drop-down and select the severity level at which to write to the log file. Select a lower severity level to generate more log data. This setting is primarily for use by SevOne Support Engineers.

2. Select the Override Precision check box to specify the level of precision. Data typically rounds to two decimal places. Select this check box and enter the number of decimal places to which to round data.

3. Select the API Weekend Work Hours check box if you use the SevOne NMS API and your work hours include weekends.

4. Select the Measure System Uptime check box to populate the Deferred Data plugin for each device with a system object and a SysUpTime indicator that contains the normalized data. The deferred data sysuptime is the true representation of the devices uptime as SevOne NMS derives from polls every 15 minutes. Each poll collects data for the past 7 days. System uptime is the length of time a device has been up without any downtime (loss of connection to the device can appear as downtime).

5. Select the Reports Private By Default check box to make new reports private. You can override this setting for each report on the Report Properties.

6. Select the Use WebKit to PDF check box to use WebKit to render .pdf reports. WebKit integration is a beta feature.

7. Select the Enable Localization check box to enable the display of SevOne NMS in a language other than English. When you select this check box, click the Default Language drop-down and select the language to appear by default in drop-down fields and on the Login page. Localization is a beta feature and can be set for each user on the Preferences page.

8. Click Save to save the General settings.

Graphs

The Graphs subtab enables you to define the settings for the graphs that appear in reports.

1. Select the Abbreviate Graph Text check box to abbreviate long names on the graph with ellipses.

2. Select the Display Poll Frequency check box to display the poll frequency in the graph legend.

3. Select the Draw Horizontal Grid Lines check box to display horizontal lines on the graph then enter how close the horizontal lines should be to one another in the Horizontal Grid Density field.

4. Select the Draw Vertical Grid Lines check box to display vertical lines on the graph enter how close the vertical lines should be to one another in the Vertical Grid Density field.

5. Select the Display Last Poll Value check box to display the value of the last successful poll in the graph legend.

6. Click Save to save the Graphs settings.

ICMP

The ICMP subtab enables you to define ICMP settings for devices on which you enable the ICMP plugin.

1. Select the Always 100% Availability check box to report 100% availability in ICMP even if a single packet makes it through. Leave clear to set availability to the percentage of the packets that make it through.

2. Click Save to save the ICMP settings.

IP SLA

The IP SLA subtab enables you to set the Default Responder Action to have all new devices ignore the default IP SLA responder action, to have SevOne NMS execute SET commands on the target device, or to have SevOne NMS not perform the default IP SLA responder action. You can override this cluster wide setting for each individual device from the Edit Device page.

1. Click the Default Responder Action drop-down.

   • Select Ignore to have SevOne NMS not change the IP SLA responder setting on devices.

   • Select Yes to turn on the IP SLA responder on devices upon discovery, when possible.

   • Select No to turn off the IP SLA responder on devices upon discovery, when possible.

2. Click Save to save the IP SLA settings.

Login

The Login subtab enables you to add a custom message to the Login page and to display the Alert Summary, Instant Status, and Alerts on the Welcome Dashboard.

1. In the Login Page Message field, enter the message to appear on the Login page. Limit is 1500 characters and you cannot use HTML formatting.

2. Select the Use a Fixed Width Font check box to use a font whose letters and characters each occupy the same amount of horizontal space. The font you define for your browser is the default font for the message. To change your font in Internet Explorer; click the Tools menu and select Internet Options then Fonts. To change your font in Firefox: click the Tools menu, select Options, and then select Content.

3. In the Welcome Dashboard section:

   1. Select the Display Alert Summary check box to display an Alert Summary report on the Welcome Dashboard.

   2. Select the Display Instant Status check box to display an Instant Status report on the Welcome Dashboard.

   3. Select the Display Alerts check box to display an Alerts section on the Welcome Dashboard.

4. Click Save to save the Login settings.

Poller

The Poller subtab enables you to define poller settings.

1. In the Poller Threads field, enter the number of poller threads to use concurrently (maximum - 1000).

2. In the Update Interval field, enter the number of seconds to collect poll data before writing data to the disk.

3. Select the Display Poller Downtime check box and enter the number of seconds for polling to be down before the data in a graph will display a break in the Poller Downtime Threshold field. This displays a break in data graphs when poller downtime exceeds the Poller Downtime Threshold you define. Leave clear to display a continuous line in graphs between actual poll points.

4. In the Oracle Plugin Timeout field, enter the number of minutes to keep each Oracle poller thread polling before time out and start over. This prevents threads from being consumed by infinite Oracle poll times.

5. Click Save to save the Poller settings.

Ports

The Ports subtab enables you to define the port settings for communication between peers in the cluster.

1. The Primary/Secondary Port field displays the TCP port for communication between the Primary appliance and the Secondary appliance in a Hot Standby Appliance peer pair. Do not change. This port is for internal use.

2. The Alert Server Port field displays the port for alerts. Do not change. This port is for internal use.

3. The Peer Communication Port field displays the port for communication among peers. Do not change. This port is for internal use.

4. In the Trap Receiver Port field, enter the UDP port number on the SevOne appliance to listen for incoming SNMP traps.

5. Click Save to save the Ports settings.

Security

The Security subtab enables you to define security settings.

1. In the Inactivity Timeout field, enter the number of minutes a user can remain inactive before the user is logged off (between 5 minutes and 86400/60 days). You can override this setting for each individual user from the User Manager.

2. In the Minimum Password Length field, enter the number of characters users must have in their password. Enter 0 (zero) to disable this feature.

3. In the Enforce Password History field, enter the number of password changes a user must make before they can repeat a password.

4. In the Minimum Password Age field enter the number of days a user must wait between password changes.

5. In the Password Change Notification field, enter the number of days to wait after a password change, before a user is sent a password change notification.

6. In the Maximum Password Age field, enter the number of days a user account can remain enabled before the user must change their password.

7. Select the Mask Read Community Strings check box to mask Read Community Strings on user interfaces. Write Community Strings are masked by default.

8. Select the Require Strong Passwords check box to enforce the complexity of user passwords. If you select this check box, passwords must contain at least one special character and at least two of the following three types of characters: Lower case letters, UPPERCASE LETTERS, and numbers. In addition, passwords cannot contain more than two of a given type of character in succession (upper and lower case letters count as the same type). Example: 8s0h43o@7!o(p3

9. Select the Allow Forcelogin check box to enable SevOne NMS integration with other software applications via the Forcelogin script.

10. Select the Force Same Origin Policy check box to prevent SevOne NMS from being loaded outside of the current domain. This includes portals and the use of the force login script to load SevOne NMS into an iframe from where a malicious user could log a user's activity. Note: If you clear this check box, the application security is lowered in a way that can prevent SevOne NMS from passing specific security scans.

11. Select the Require HTTPS check box to require a secure connection for all dynamic content. You must log on via HTTPS to enable this check box.

12. In the Account Lockout section:

    1. In the Disable Inactive Users field, enter the number of days a user can go without logging on before their account is disabled. Enter 0 (zero) to disable this feature.

       This setting does not affect the Guest users you define on the Authentication Settings page for LDAP, TACACS, and RADIUS nor does it affect the "admin" user.

    2. In the Threshold field, enter the number of incorrect log on attempts a user can make (within the Duration time span) before the account is locked. Enter 0 (zero) to disable this feature. Note: When you set this to anything other than 0 (zero), log on becomes dependent upon validation from the cluster master peer. If the cluster master peer is not accessible from a peer on which a user attempts to log on, access to the application will not be available.

    3. If you enter a number in the Threshold field, in the Counter Reset field, enter the number of minutes during which the user enters an incorrect user name and password combination before the account is locked. Set this to 0 (zero) to disable this feature. Example: Enter 3 as the Threshold and 2 as the Counter Reset. If the user incorrectly enters their user name and password combination three times in a two minute time span, the account is locked for the number of minutes you enter in the Duration field.

    4. If you enter a number in the Threshold field, in the Duration field, enter the number of minutes for the account to be locked after the Threshold/Counter Reset combination is exceeded.

13. Click Save to save the Security settings.

SNMP

The SNMP subtab enables you to define the SNMP settings for devices on which you enable the SNMP Plugin. You can override these settings for individual devices from the Edit Device page.

1. Select the Strictly Support RFC 2233 check box to have interfaces under 20Mbps not support 64 bit counters when 32 bit counters are available and to have interfaces over 20Mbps not support 32 bit counters when 64 bit counters are available. Certain combinations of Strictly Support RFC 2233 and Prefer 64 bit can result in data loss.

2. Select the SNMP Version Lock check box to use the version of SNMP you select. This prevents SevOne NMS from trying to determine the proper version if the version you select fails.

3. Select the Discover Max PDUs for Devices to attempt to discover the maximum data packet size that devices allow. SNMP PDU (Protocol Data Unit) data types are complex data types that are specific to SNMP. The PDU field contains the body of an SNMP message. There are two PDU data types, GetRequest and SetRequest, which hold all the necessary data to get and set parameters.

4. Click the Counter Preference drop-down. This setting controls how SNMP discovery determines what counter type (32 bit or 64 bit) to choose. If you select the Strictly Support RFC 2233 check box, this setting does not apply to in and out utilization for interfaces. Certain combinations of Strictly Support RFC 2233 and Prefer 64 bit can result in data loss.

   • Select Allow Both to use both 64 bit and 32 bit counters for an object.

   • Select Prefer 64 bit to have interfaces under 20Mbps not support 64 bit counters when 32 bit counters are available and to have interfaces over 20Mbps not support 32 bit counters when 64 bit counters are available.

   • Select Prefer 32 bit to use 32 bit counters.

5. In the Synchronize Objects section:

   1. Select the Administrative State check box to hide and not poll objects that are administratively down. Leave clear to poll administratively down objects normally. The Object Manager enables you to override this setting on a per object basis.

   2. Select the Operational State check box to hide and not poll objects that are operationally down. Leave clear to poll operationally down objects normally. The Object Manager enables you to override this setting on a per object basis.

6. Click + next to Default Community Strings to display the SNMP community strings. The field on the left displays the list of read community strings SevOne NMS uses to authenticate onto devices. The field on the right displays the write community strings SevOne NMS uses to authenticate onto devices. When SevOne NMS discovers a device and attempts to poll SNMP data, the first string in the list is tested. If that string fails, the subsequent strings are tested, in sequence, until a string is successful. The successful read community string appears on the Edit Device page for the device.

   1. In the Read Community Strings field and the Write Community Strings field, click Add to display a pop-up that enables you to enter a string.

   2. Repeat the previous step to add additional strings.

   3. Click the arrows to move the string up or down in the list. The discovery process goes through the list sequentially.

7. Click Save to save the SNMP settings.

Storage

The Storage subtab enables you to define the size of items in the system.

1. In the Hot Standby Appliance Binary Log Size field, enter the number of gigabytes of space to allot for storage of data that accumulates during an interruption of the communication between the primary appliance and the secondary appliance in a Hot Standby Appliance peer pair implementation. When your cluster has a single Hot Standby Appliance peer pair, enter a number between 2 and 6. When your cluster has multiple Hot Standby Appliance peer pairs enter a number between 10 and 40.

2. In the Data Retention field, enter the number of days' worth of data to store. Enter 999 here to use the Maximum Disk Utilization percentage you enter in the next step as the Data Retention limit.

3. In the Maximum Disk Utilization field, enter the percentage of disk space to allocate for the storage of poll data. Leave some disk space for logs and flow data. The FlowFalcon subtab (described above) enables you to define FlowFalcon data retention.

4. Click Save to save the Storage settings.

Trap Collector

The Trap Collector subtab enables you to define the trap collector settings for devices. Please consult with your SevOne Support Engineer before you modify Trap Collector settings.

1. In the Threads field, enter the number of trap-handling threads to use. Each thread handles one trap at a time.

2. In the Update Interval field, enter the number of seconds for how often the trap collector updates the event information and caches data.

3. Click Save to save the Trap Collector settings.

WMI Proxies

The WMI Proxies subtab enables you to define the WMI proxy servers for the WMI plugin use to poll WMI data and provides links to the WMI Proxy service and the .NET 3.5 Framework software you need to install on the proxy server. See the Enable WMI chapter for details.

1. In the WMI Proxies section, click Add WMI Proxy or click to display the Add/Edit Proxy pop-up.

2. In the Name field, enter the name of the proxy server.

3. In the IP Address field, enter the proxy server IP address.

4. In the Port field, enter the port for the proxy server to use to communicate with SevOne NMS (default – 3000).

5. On the pop-up, click Save.

6. Repeat the previous steps to define additional WMI proxy servers.

7. Click Save to save the WMI Proxy settings.

Downloads

The Downloads section includes the SevOne NMS WMI Proxy service file and the .NET 3.5 Framework installation file. On the WMI proxy server, run the .NET 3.5 Framework setup.exe if needed, then run the SevOne WMI Proxy Setup.msi to install the SevOne NMS WMI Proxy service.

• The SevOne NMS WMI Proxy file installs a Windows service on the Windows device you designate to act as the proxy to perform WMI queries. Click the WMI Proxy Download Installation Package link and save the file to the proxy device.

• If the proxy device is not running the Microsoft .NET 3.5 framework, click the .NET 3.5 Framework Download Installation Package link to download the .NET installation package setup.exe file.

Plan an Update

After you have the update files, the following tools enable you to plan the update on your SevOne NMS cluster.

• Click the View Release Notes drop-down and select the version specific release notes to view. Click View to view the release notes.

• Click the Update to Version drop-down and select the SevOne NMS software version to which to update your cluster.

Perform an Update

When you perform an update, you will need to acknowledge the Release Notes. If you update through several software versions the down time is cumulative, the system will be down for the length of each update added together. SevOne NMS performs a system check and queues the update. After the system check, all user sessions are terminated and all current users are logged out of SevOne NMS. You can log back on to access the Updates tab on the Cluster Manager to view the progress of the update. No other functionality is available during the update.

1. Click the Update to Version drop-down and select the SevOne NMS software version to which to update your cluster.

2. Click Update to display the Update Wizard.

3. Click Next to display the Release Notes for the first update to run.

4. Click Next through all Release Notes for each update that is required to get you to the SevOne NMS software version you select in step one.

5. Click Yes to queue the update to begin.

• The update is queued (could take five minutes or more to start).

• SevOne NMS performs a system check.

• All user sessions are terminated and all current users are logged out.

• You (administrative users) can log back on to access the Updates tab on the Cluster Manager to view the progress of the update on the Update Status subtab.

• No other functionality is available during the update.

• All peers in your cluster update simultaneously.

Update Status

The Update Status subtab displays the following update information.

• A Cluster Progress status bar appears along the top of the subtab to display the update progress.

• The Peer/Hot Standby section displays a list of all appliances in your cluster and an update progress message for each appliance.

• The Status Messages section displays the peer name, appliance type, the time each message appeared and update status messages.

FlowFalcon

The FlowFalcon subtab enables you to define the retention of aggregated flow data on the peer for use in FlowFalcon reports.

1. In the Write Interval field, enter the number of days' worth of <write interval> aggregated flow data to store for calculations. You define the write interval on the Cluster Settings tab FlowFalcon subtab. See above for details.

2. In the Fifteen Minutes field, enter the number of days' worth of fifteen minute aggregation data to store for calculations.

3. In the One Hour field, enter the number of days' worth of one hour aggregation data to store for calculations.

4. In the One Day field, enter the number of days' worth of one day aggregation data to store for calculations.

5. Click Save to save the FlowFalcon peer settings.

General

The General subtab enables you to add a tunneling proxy server for the peer you select in the hierarchy to use for HTTP poll requests and proxy information for VMware requests. This subtab also enables you to schedule when the peer you select in the hierarchy is to perform the automatic discovery function to discover the devices that this peer polls.

1. In the HTTP Proxy section, in the Default HTTP Proxy Server field, enter the full URL of the HTTP server you want this peer to poll for data from devices on which you enable the HTTP plugin. This field is applicable when your implementation includes an HTTP proxy server and the URL must have a valid format with a port number.
   

   Example: http://www.yourproxyserver.com:portnumber/

2. In the VMware Proxy section, the following fields enable you to define how peers communicate with each other to collect VMware data from the VMware plugin.

   1. In the Port field, enter the port on the proxy for this peer to use to collect the VMware data from other peers in your cluster.

   2. In the Username field, enter the user name the peer needs to authenticate onto the proxy.

   3. In the Password field, enter the password the peer needs to authenticate onto the proxy.

3. In the Automatic Discovery section: the following fields enable you to schedule when this peer is to run the Automatic Discovery process to discover the devices that this peer polls.

   1. In the Days field, click the day tab for each day that this peer is to run the automatic discovery. Automatic discovery runs on the days that appear dark blue. You must schedule automatic discovery to occur at least once every week. You should run automatic discovery daily at a time when the application is least utilized.

   2. Click the Time drop-downs to enter the automatic discovery start time.

   3. Click the Time Zone drop-down and select a time zone you want this peer to use for the automatic discovery process to discover the devices that this peer polls.

   4. Click Discover Now to run automatic discovery now to have this peer run automatic discovery to discover the devices this peer polls.

4. Click Save to save the General peer settings.

Primary/Secondary

The Primary/Secondary subtab enables you to view the IP addresses for the two appliances that act as one SevOne NMS peer in a Hot Standby Appliance (HSA) peer pair implementation. In a primary/secondary relationship, the active appliance does the normal network polling and the passive appliance pulls the config database data from the active appliance and pulls the data database data from the active appliance to provide redundancy. The passive appliance takes the active role if the active appliance fails. The primary appliance is initially set up to be the active appliance. If the primary appliance fails, it is still the primary appliance but its role changes to the passive appliance. The secondary appliance is initially set up to be the passive appliance. If the primary appliance fails, the secondary appliance is still the secondary appliance but it becomes the active appliance. You define the appliance IP address upon initial installation and implementation. See the SevOne NMS Installation and Implementation Guide for details.

1. In the Primary Appliance IP Address field, view the IP address of the primary appliance.

2. In the Secondary Appliance IP Address field, view the IP address of the secondary appliance.

3. The Virtual IP Address field appears empty unless you implement the primary appliance and the secondary appliance to share a virtual IP address. A virtual IP address is useful when you configure the devices SevOne NMS polls to communicate with a specific appliance IP address because if that appliance fails, the virtual IP address becomes the IP address of what was the passive appliance and the communication from the poller is not blocked because of a different poller IP address.

4. In the Failover Time field, enter the number of seconds for the passive appliance to wait for the active appliance to respond before the passive appliance takes over. SevOne NMS pings every 2 seconds and the timeout for a ping is 5 seconds.

   If you change this setting, you must restart the SevOneMaster/Slave Monitor process for both the active peer and the passive peer on the Cluster Manager at the appliance level on the Process Overview tab.

5. Click Save to save the Primary/Secondary peer settings.