CPU, Memory and Disk Monitor - CA Technologies · Web viewDocumentation Changes Converged...

Eyeglass Connect Vblock Probe R1.0 SP3

Doc Version: 1.4

Technical Support Playbook

Eyeglass Connect Vblock R1.0 SP3 5Eyeglass Connect Vblock Overview.............................................................................................................................5Documentation Changes............................................................................................................................................6

Contact Information 7Company Address.......................................................................................................................................................7Support Portal............................................................................................................................................................7

Eyeglass Connect Vblock Architecture 9

Eyeglass Connect Vblock_Monitor General Information 12Log Files....................................................................................................................................................................12Configuration Items..................................................................................................................................................15Debug Facilities.........................................................................................................................................................15

Eyeglass Connect Vblock_Render General Information 17Log Files....................................................................................................................................................................17Configuration Items..................................................................................................................................................17Debug Facilities.........................................................................................................................................................17

Troubleshooting and FAQs 18Vblock Inventory Not Collected................................................................................................................................18Unable to Load Licenses...........................................................................................................................................22Authentication Error when accessing the SupernaNET Converge Dashboard..........................................................23No Vblocks Displayed................................................................................................................................................23No Vblock Alarms in Dashboard or Nimsoft Alarms windows...................................................................................25Converged Dashboard Display Area Too Small.........................................................................................................26

Eyeglass Connect Vblock Probe R1.0 SP3 3

Eyeglass Connect Vblock Probe R1.0 SP3

This description applies to Eyeglass_Connect_Vblock probe version 1.0 SP3.

The probe has following 2 components:

Eyeglass_Connect_Vblock_Probe_for_UIM_Monitor_1.0.0.0424.zip

Eyeglass_Connect_Vblock_Probe_for_UIM_Render_1.0.0.0424.zip


Preconfiguration Requirements

Eyeglass_Connect_Vblock_Probe_for_UIM_RenderThe Eyeglass_Connect_Vblock_Probe_for_UIM_Render probe has the following preconfiguration requirements:

1. The Eyeglass_Connect_Vblock_Probe_for_UIM_Render probe deploys a WAR file to an existing Nimsoft wasp probe and requires that the Nimsoft wasp and webservices_rest probes are already installed on the Nimsoft Monitor server. The Nimsoft wasp probe is typically deployed as part of the Nimsoft UMP installation. The Nimsoft webservices_rest probe must be deployed manually to the wasp probe. If Nimsoft webservices_rest has been deployed, it will appear on the wasp probe Webapps list.


Software Requirements

Figure 1 webservices_rest on wasp probe

Eyeglass_Connect_Vblock_Probe_for_UIM_Monitor

The Eyeglass_Connect_Vblock_Probe_for_UIM_Monitor probe has the following preconfiguration requirements:


Eyeglass Connect Vblock Overview

1. Eyeglass_Connect_Vblock_Probe_for_UIM_Monitor monitors the following components:

Component Version

VCE Vblock running Vision IO Vision IO R2.6

vCenter vCenter R5.1 and higher

2. On the server where the Eyeglass_Connect_Vblock_Probe_for_UIM_Monitor probe will be deployed, the /etc/hosts file must be configured with the FQDN information of Vision for the Vblocks that will be monitored or DNS must be configured to resolve FQDN.

Additional Requirements

Eyeglass_Connect_Vblock_Probe has the following additional requirements:

1. In order to install and manage Eyeglass Connect Vblock probes, a Nimsoft Infrastructure Manager licence is required. You can download Nimsoft products at www.nimsoft.com.

2. The user who is logged in to Nimsoft must have the “Web Service” option selected on his Access Control List to use the Eyeglass Connect Vblock_Dashboard.

Supported PlatformsThe Eyeglass Connect Vblock_Monitor probe installation supported platforms are:

Microsoft Windows Server 2008 R2 64

The Eyeglass Connect Vblock_Render probe can be deployed against any platform where the Nimsoft wasp probe is running.

8 CPU, Memory and Disk Monitor

http://www.nimsoft.com/


System RequirementsThe Eyeglass Connect Vblock_Monitor probe system requirements are:

Hardware or Virtual Machine with 4 G RAM and Dual Core CPU, 80G disk space for Operating System and application

The Eyeglass Connect Vblock_Monitor probe requires that the following ports on server be available:

Table 1 Eyeglass Connect Vblock_Monitor Probe Port Requirements

Port Direction Protocol

8443 Outbound https

5672 Outbound AMQP

443 Outbound https

There are no system requirements for the Eyeglass Connect Vblock_Render probe as it is deployed to the wasp probe.


Eyeglass Connect Vblock_Monitor was developed using Nimsoft SDK for Java R2.8.5.

Eyeglass Connect Vblock_Render requires that the following probes are installed:

wasp

webservices_rest

Eyeglass Connect Vblock was validated using:

Table 2 Nimsoft Validation List

Nimsoft Component Version

Nimsoft Unified Management Portal R7.5 & R8.1



webservices_rest Version 2.15

Eyeglass Connect Vblock OverviewEyeglass Connect Vblock Probes for CA Nimsoft leverage VCE Vision and VMware vCenterTM software to provide a single integration point for VCE Vblock management using the CA Nimsoft Monitor Server and the Nimsoft Unified Management Portal. CA Nimsoft with Eyeglass Connect Vblock offers visualization of all Vblock ™ components and virtual machines with real-time health status, alarm aggregation and component alarm tagging:

Eyeglass Connect Vblock_Monitor: This probe provides inventory, state and alarm collection from Vblock and vCenter.

Eyeglass Connect Vblock_Render: This webapp provides the SupernaNET Converged Dashboard Web Page for Vblock and Virtual Machine visualization.

This subject of this document is the Eyeglass Connect Vblock_Monitor probe and the Eyeglass Connect Vblock_Render webapp.

The primary capabilities of the Eyeglass Connect Vblock_Monitor probe are to:

● discover topology for a VCE Vblock as provided by VCE Vision IO● discover Virtual Machines running on the Vblock as provided by vCenter ● associate the Virtual Machines to the physical blade where they are running on

the Vblock● discover properties of the VCE Vblock components as provided by VCE Vision IO● discover basic properties of the Virtual Machines as provided by vCenter● bring into Nimsoft the alarms and component status for the Vblock

components as provided by VCE Vision IO ● bring into Nimsoft the alarms and status for the Virtual Machines running on

the Vblock as provided by vCenter



● discover Vblock Compliance to RCM

The SupernaNET.Monitor probe monitors the following components:

Component Version

VCE Vblock running Vision IO Vision IO R2.6

vCenter vCenter R5.1 and higher

The primary capabilities of the Eyeglass Connect Vblock_Render webapp are to provide following capabilities on the SupernaNET Converged Dashboard:

● Converged View of virtual and physical topology for Vblock components and their associated Virtual Machines

● Root Cause of problems by Domain or Component● Health Check by Domain utilizing VCE Vision computed status● Intelligent Alarms include subsystem id and Vblock serial number tagging using

Nimsoft component ID tags● Component Zoom for component properties including location, serial number

and version information● Vblock RCM Compliance score

Documentation ChangesThis table describes the version history for this document.

Version Date What's New?

1.0 June 26, 2014 Initial Document Release

1.1 July 3, 2014 Updated Converged Dashboard Display troubleshooting



1.2

1.3

July 17, 2014

March 5, 2015

Updated for logging level debug and troubleshooting for license loading

Updated for 1.0 SP3


Contact Information This section contains contact information for Eyeglass Connect Vblock. This section contains the following topics:

Company and Telephone Contact List (see page 18)

Company AddressSuperna

104 Schneider Road

Kanata

Ontario

K2K 1Y2

Canada

http://superna.net

Support PortalPlease use the support portal for support issues. Select the Eyeglass Connect Nimsoft Probes product, quoting the probe name and case number in the title:

support.superna.net

Contact Information 13

Eyeglass Connect Vblock Architecture

This section contains an overview of the probe architecture for Eyeglass Connect Vblock which is comprised of 2 components: Eyeglass Connect Vblock_Monitor and Eyeglass Connect Vblock_Render.

Eyeglass Connect Vblock_Monitor is a connector between Vblock and vCenter and Nimsoft. It collects the inventory and state information from these devices and passes it to the SupernaNET Converge Dashboard. It also collects alarm information from these devices and passes it to Nimsoft.

Eyeglass Connect Vblock_Render is a webapp that runs on the Nimsoft wasp web server. As part of the deployment of the Eyeglass Connect Vblock probes, the SupernaNET Converge Dashboard web page must be configured on the Nimsoft interface and associated to the Eyeglass Connect Vblock_Render webapp. The Eyeglass Connect Vblock_Render webapp has a dependency on the webservices-rest webapp having been installed and running on the same wasp probe where the Eyeglass Connect Vblock_Render webapp is running.

The data flow between Eyeglass Connect Vblock_Render, Nimsoft and Eyeglass Connect Vblock_Monitor and the related protocols are illustrated in the figure below.


Description of Main Monitor Probe Tasks:

Task Description

Vblock Inventory and Calculated (Calc) Status

● Protocol: REST● Scheduled retrieval of information every 30

minutes on the hour/half-hour as per SupernaNET Monitor probe server time

Vblock Compliance ● Protocol: REST● Scheduled retrieval of information every 30


Vblock Alarms ● Protocol: AMQP


Converged Dashboard Display Area Too Small

● Permanent AMQP connection established between SupernaNET.Converge Monitor probe and the AMQP on initial discovery of the Vblock

● Alarms processed as they are generated

vCenter Inventory ● Protocol: SOAP● Scheduled retrieval of information every 30


vCenter Alarms ● Protocol: SOAP● Polling for alarms at 1 minute interval

Troubleshooting and FAQs 17


Eyeglass Connect Vblock_Monitor General Information

This section contains general information about the Eyeglass Connect Vblock_Monitor probe. This section contains the following topics:

Log Files and Configuration Items (see page 18)

Log FilesThe log files can be found in the <Nimsoft>\probes\Marketplace\supernanet.converge.monitor directory. The following files should be checked

■ Eyeglass Connect Vblock_Monitor.log

Example log entries for common Eyeglass Connect Vblock_Monitor functions are provided in the table below.

Example Log Entry for starting Eyeglass Connect Vblock_Monitor Probe

014-07-02 11:31:51,661 NDEDaemon:start [286] ***** Starting Probe [ 8932@Nimsoft75server ] *****

2014-07-02 11:31:51,681 NDEDaemon:<init> [48] Initializing Components...

2014-07-02 11:31:51,681 NDEDaemon:<init> [50] Server

2014-07-02 11:31:51,689 NDEDaemon:<init> [53] License Management

2014-07-02 11:31:51,699 NDELicenseManager:initialise [296] Running in Daemon Mode - starting scheduler.

2014-07-02 11:31:52,137 NDELicenseManager:populateLicenses [244] Added Base Application license to instance.

2014-07-02 11:31:52,163 NDELicenseManager:populateLicenses [244] Added Base Application license to instance.

2014-07-02 11:31:52,164



NDELicenseManager$LicenseCheckScheduler:scheduleLicenseTask [1490] Scheduling Base Application license expiry check - serial C06E40B2 (0 0 4 7 5)

2014-07-02 11:31:52,189 NDELicenseManager:populateLicenses [244] Added NE Discovery license to instance.

2014-07-02 11:31:52,218 NDELicenseManager:populateLicenses [244] Added NE Discovery license to instance.

2014-07-02 11:31:52,219 NDELicenseManager$LicenseCheckScheduler:scheduleLicenseTask [1490] Scheduling NE Discovery license expiry check - serial B7DF326B (0 0 4 7 5)

2014-07-02 11:31:52,246 NDELicenseManager$LicenseCheckScheduler:scheduleLicenseTask [1490] Scheduling Replication Path license expiry check - serial 58D45407 (0 0 4 7 5)

2014-07-02 11:31:52,246 NDEDaemon:<init> [57] Key Management

2014-07-02 11:31:52,255 NDEDaemon:<init> [60] Alarm Handler

2014-07-02 11:31:52,360 NDEDaemon:<init> [64] Scheduler

2014-07-02 11:31:52,390 NDEDaemon:<init> [67] Plugin Server

2014-07-02 11:31:52,394 PluginDataIO:getPluginList [19] reading plugindata IO from file

2014-07-02 11:31:52,499 PluginDataIO:getPluginList [28] Successfully unmarshalled plugin file

2014-07-02 11:31:52,503 NDEDaemon:readConfigData [73] Sites

2014-07-02 11:31:52,504 NDEDaemon:readConfigData [77] Syslog

2014-07-02 11:31:52,505 RefreshSyslogData:execute [15] Refreshing Syslog Data...

2014-07-02 11:31:52,506 RefreshSyslogData:execute [33] Syslog Data Refreshed

2014-07-02 11:31:52,507 RefreshSyslogData:execute [36] Syslog Settings Updated

2014-07-02 11:31:52,507 NDEDaemon:startDaemon [203] Starting Components...

2014-07-02 11:31:52,507 NDEDaemon:startDaemon [206] Probe

2014-07-02 11:31:52,508 NDEDaemon:startDaemon [206] Tomcat

2014-07-02 11:31:52,508 NDEDaemon:startDaemon [206] Server



2014-07-02 11:31:52,509 NDEDaemon:startDaemon [206] Plugin Server

2014-07-02 11:31:52,509 NDEDaemon:startDaemon [206] EmbeddedDatabase

2014-07-02 11:31:52,635 PluginServer:run [56] Waiting for a new plugin data request

2014-07-02 11:31:52,636 NDEServer:run [127] Waiting for a new connection

2014-07-02 11:31:52,686 VblockProbe:<init> [114] Starting probe

Example Log Entry for adding Vblock/vCenter

2013-09-26 16:24:00,009 NDELicenseManager:networkChanged [1065] NODE ADDED: Licensed NE 'vblock_10.10.10.10' for 'NE Discovery'

2013-09-26 16:24:00,009 NDELicenseManager:networkChanged [1065] NODE ADDED: Licensed NE 'vcenter_10.10.10.20' for 'NE Discovery'

Example Log Entry for deleting Vblock/vCenter

2013-09-26 20:16:00,219 RefreshNEData:disconnectNode [355] vblock_10.10.10.10 was not connected

2013-09-26 20:16:00,228 NDELicenseManager:networkChanged [1080] NODE REMOVED: Unlicensed NE 'vblock_10.10.10.10' for 'NE Discovery'

2013-09-26 20:16:00,237 RefreshNEData:disconnectNode [359] vblock_10.10.10.10 Disconnected

2013-09-26 20:16:00,245 RefreshNEData:disconnectNode [355] vcenter_10.10.10.25 was not connected

2013-09-26 20:16:00,254 NDELicenseManager:networkChanged [1080] NODE REMOVED: Unlicensed NE 'vcenter_10.10.10.25' for 'NE Discovery'

2013-09-26 20:16:00,262 RefreshNEData:disconnectNode [359] vcenter_10.10.10.25 Disconnected



Example Log Entry for alarm processing

2014-07-01 14:36:54,989 ProbeAlarmHandler:AlarmData2NimAlarm [155] ....sending an alarm from FM .. vblock_ip = 10.10.10.10

2014-07-01 14:36:55,009 ProbeAlarmHandler:AlarmData2NimAlarm [182] Trying to create a CI obj with: vblock_ip=10.10.10.10

2014-07-01 14:36:55,022 ProbeAlarmHandler:AlarmData2NimAlarm [184] CREATED a CI obj with: vblock_ip=10.10.10.10

2014-07-01 14:36:55,038 ProbeAlarmHandler:handleAlarms [55] Sending alarm to Nimsoft from 10.10.10.10

2014-07-01 14:36:55,050 ProbeAlarmHandler:handleAlarms [56] Alarm Parameters: 172.16.70.41 N1A 1 Source Ip Address is: 10.10.10.22

2014-07-01 14:36:55,063 ProbeAlarmHandler:handleAlarms [59] Sent alarm with id: AC22819156-16836

Example Log Entry for inventory start

2014-07-01 15:00:00,056 NDEUpdateTask:run [354] Starting NDEUpdateTask



Configuration ItemsThe Vblock and vCenter being monitored by the probe are provisioned on the Eyeglass Connect Vblock_Render web page.

A read-only view of the provisioned Vblock/vCenter pairs is also provided in the Nimsoft Infrastructure Manager Configure interface:

1. Right-click on the Eyeglass Connect Vblock_Monitor probe.

2. Select the Confgure… option.

3. Expand the system_view folder. Each Vblock and vCenter provisioned will be listed. Select a folder to see the details for the Vblock or vCenter.

Debug FacilitiesFrom the Infrastructure Manager Raw Configure interface you may change the logging level for the Eyeglass Connect Vblock_Monitor log file to obtain additional debug information. Edit the “loglevel” key and enter a value between 0 and 5.



Eyeglass Connect Vblock_Render General Information

This section contains general information about the Eyeglass Connect Vblock_Render probe. This section contains the following topics:

Log Files and Configuration Items (see page 18)

Log FilesThere are no log files for the Eyeglass Connect Vblock_Render probe. Should there be an issue, it may be useful to check the logs of the wasp probe where Eyeglass Connect Vblock_Render is deployed.

Configuration ItemsThe Vblock and vCenter being monitored by the probe are provisioned on the Eyeglass Connect Vblock_Render web page.

Debug FacilitiesBrowser Developer Tools may be useful in debugging issues with the Eyeglass Connect Vblock_Render web page. For example, you are able to see each request URL and the response provided. Any errors will also be displayed in the console view.



Troubleshooting and FAQsThis section contains troubleshooting information for the Eyeglass Connect Vblock probes.

This section contains the following topics:

Vblock Inventory not Collected

Unable to Load Licenses

No Vblocks Displayed

No Vblock Alarms in Dashboard or Nimsoft Alarms windows


Vblock Inventory Not CollectedAssumptions:

● SupernaNET.Converge.Monitor probe deployed to Nimsoft robot with Vblock/Vision connectivity

● SupernaNET.Converge.Render probe deployed to Nimsoft wasp probe● SupernaNET.Converge licenses deployed● Vblock/Vision and Vcenter provisioned on SupernaNET.Converge

Problem:

In the SupernaNET Converge Dashboard, a Vblock that was added is permanently displayed with a spinner and the associated inventory tree is not populated.



Troubleshooting:

1. Refresh the SupernaNET Converge Dashboard page. Dashboard may not have been updated after successful completion of inventory.

2. Determine elapsed time since Vblock was added. Vblock inventory may take 30 - 90 minutes depending on the state of the system when the Vblock was added:

● Was inventory collection task in progress when Vblock was added? The in-progress inventory task has to complete before inventory for a new vblock is added.

● How many Vblock inventories are being completed simultaneously.

3. Look in Eyeglass Connect Vblock_Monitor log file and determine whether there was an inventory failure. You will see this almost immediately after NDEUpdate task starts with an entry in main.log that looks something like this:

2013-11-04 15:39:14,898 NDEUpdateTask:collectData [211] Failed to get Inventory Data. 2013-11-04 15:39:14,898 RefreshNEData:doDataRefresh [183] Could not sync inventory for new nodes - Failed to get Shelf Data - Inventory failed

Search the Eyeglass Connect Vblock_Monitor log for an entry like

Server supports System Library false

which indicates that there is a problem with connectivity to Vision. This log most often indicates a DNS problem where it is not possible to resolve the Vision IP address to its FQDN.

Troubleshooting Steps for Vision Connectivity Issue:

1. Confirm that there is an entry in the C:\Windows\System32\drivers\etc\hosts file for the Vision IP and FQDN ON THE SERVER WHERE SUPERNANET.CONVERGE.MONITOR is running. For example, an entry such as:

10.10.10.10 fm-nimsoft.internal.company.net



If it is not in the host file - add it. Next inventory should pick it up.

2. On the server where SupernaNET.Converge.Monitor is running execute following command

nslookup <Vision FQDN>

This should return the IP address of the Vision provisioned in SupernaNET.Converge if the host name and DNS are properly configured.

3. On the server where SupernaNET.Converge.Monitor is running open a browser and enter the URL:

https://10.10.10.10:8443/fm

where 10.10.10.10 is replaced with IP address provisioned in SupernaNET.Converge for Vision

You should be redirected from IP address to the Vision FQDN and then after entering credentials (default is admin/dangerous) see browser return like this:

<slib>

<link href="https://fm-nimsoft.internal.company.net:8443/fm/vblocks" rel="children" type="application/xml"/>

<link href="https://fm-nimsoft.internal.company.net:8443/fm/about" rel="children" type="application/xml"/>

</slib>

Go to each of the links provided. You should pages like this:



https://fm-nimsoft.internal.company.net:8443/fm/vblocks

<vblocks><vblock><alias>VB-700</alias><dbId>843</dbId><description>VB-700 (Vblock 700LX)</description><moId>VB700-975-318-642</moId><name/><url>https://vb701-viofm.vce.company.net:8443/fm/vblocks/843</url><assetId/><calculatedStatus>critical</calculatedStatus><firmwareRev/><fru>false</fru><hardwareRev/><lastOperStatus>unknown</lastOperStatus><lastStatusChange>1970-01-01T00:00:00Z</lastStatusChange><localInstanceId/><localName/><mfgDate>1970-01-01T00:00:00Z</mfgDate><modelName>Vblock 700LX</modelName><operStatus>critical</operStatus><phyClass/><serialNum>VB700-975-318-642</serialNum><softwareRev/><vendor>The VCE Company, Inc.</vendor><vendorType>1.3.6.1.4.1.38819.1.5.10.2.700.2</vendorType><link href="https://vb701-viofm.vce.superna.net:8443/fm/vblocks/843/vlans" rel="children" type="application/xml"/><lastUpdateTime>2013-11-06T18:38:33.847Z</lastUpdateTime><location><building>350 Campus</building><floor>1rd</floor><geo>Marlborough, MA</geo><room>Eisenhower</

https://fm-nimsoft.internal.company.net:8443/fm/about

<appinfo> <buildVersion>2.0.3</buildVersion> <dbId>1</dbId> <productName> VCE Vision(TM) Intelligent Operations System Library </productName></appinfo>



If these URLs don't work you either still have a DNS problem or a Vision problem. Contact the Network Administration for the Nimsoft and Vision installations for further troubleshooting.

Unable to Load Licenses Assumptions:

● SupernaNET.Converge.Monitor successfully installed and running● SupernaENT.Converge.Render successfully installed● license.zip file has been created for the install

Problem:

Try to upload the license zip file from the SupernaNET.Converge Dashboard Application Management “Licensing” tab and nothing happens.



Troubleshooting:

1. BrowserLicense upload only works with Chrome browser.

Authentication Error when accessing the SupernaNET Converge Dashboard

Problem:

When you open the SupernaNET Converge Dashboard, a popup window appears which indicates that there is an authentication error and is requesting credentials. You enter the credentials that you used to login to Nimsoft and the same authentication error window appears again each time that credentials are entered. You may also see error popups related to retrieving alarms or hub information.

Troubleshooting:

1. User permissionsThe user who is logged in to Nimsoft must have the “Web Service” option selected on his Access Control List.

To check this setting:

1. Log in to Nimsoft Infrastructure Manager.2. Select Security/Manage Access Control List.3. Select your user from the Access Control List.4. Ensure that in the Permissions list, the “Web Service” option is selected.



No Vblocks DisplayedProblem:

When you open the SupernaNET Converge Dashboard, the Vblock Inventory view is empty.

Troubleshooting:

1. Log in to Nimsoft Infrastructure Manager and open the Raw Configuration interface for the Eyeglass Connect Vblock_Monitor probe. Check that the expected Vision/vCenter pairs are provisioned on the system.

2. If Vision/vCenter information was found in Step 1, make sure that the webservices rest webapp is running.



To check the webservices webapp:

1. Log in to Nimsoft Infrastructure Manager.2. Locate the wasp probe.3. Right click on the wasp probe and select the Configure… option.4. Find the webapp called “webservices-rest”. It should have a green

icon indicating that it is running. If it is not running it should be started. If it is not present it needs to be deployed.

3. If Vision/vCenter information is not found in Step 1, contact Superna for further assistance.



No Vblock Alarms in Dashboard or Nimsoft Alarms windows

Problem: No Vblock or vcenter alarms in the Superna Dashboard or Nimsoft Alarms window.

Troubleshooting:

1. Check in Eyeglass Connect Vblock_Monitor log for AMQP entries on probe startup. For example:

2014-06-05 07:10:00,097 [Reachability-vblock_172.16.70.41] VBlockXXX:startListener [81] Begin AMQPConsumer, now=

2014-06-05 07:10:01,225 [Thread-121] AMQPConsumer:setupAMQPConsumer [117] ST-4323-d3q9xQ15HSYzK4dZU96b-cas01.vce.com

2. Check in log for alarm processing entries. Example of log entry when monitor probe receives and alarm:

3. If AMQP is running but there are no alarm processing entries check the following:

a) Check that trap destination setup properly for Vblock components to send traps to Vision.

b) Check your Nimsoft configuration. Settings related to handling of repeat alarms or alarm suppression may be affecting what is displayed in the Dashboard.



Converged Dashboard Display Area Too SmallProblem: The Converged Dashboard page only displays in a small portion of the available space in the browser.

Workaround:

1. Edit the SupernaNET Converge page and change the page “Type” to “URL”. Save your changes. This should display SupernaNET Converge page in full window but will be outside the Nimsoft UMP context.


CPU, Memory and Disk Monitor - CA Technologies · Web viewDocumentation Changes Converged...

Documents

Transcript of CPU, Memory and Disk Monitor - CA Technologies · Web viewDocumentation Changes Converged...