The following is a list of issues addressed and enhancements implemented in this release:
This release of Foglight Web Monitor 5.9.7 includes the following fixes and enhancements.
|
Defect ID |
Resolved Issue |
|
IC-4298 |
Fixed an issue that WebMonitor Agent may fail to connect to web site if it requires an HTTP Accept header. |
This release of Foglight Net Monitor 5.9.8 does not include any fixes or enhancements.
This release of Foglight for PowerVM 5.9.8 does not include any fixes or enhancements.
The following is a list of issues known to exist at the time of this release:
The following is a list of Foglight Web Monitor issues known to exist at the time of this Foglight Infrastructure Utilities release.
|
Defect ID |
Known Issue |
|
IC-3361 |
"Deployed Locations" changed frequently if user sets several different "Agent Location Alias Name" for the same location. |
|
IC-3043 |
Registry Value of Synthetic_Transaction_Sample_Period, Aggregation rule and collection interval should match. |
|
AGENT-3050 |
Further performance improvement with 6000+ URL - Transactions Domain. |
|
AGENT-3036 |
Issue with Overall Response Time bar. |
The following is a list of Foglight Net Monitor issues known to exist at the time of this Foglight Infrastructure Utilities release.
|
Defect ID |
Known Issue |
|
IC-3768 |
The value of DeviceNameOverride cannot be displayed in the Alarms table, if user sets a value for the DeviceNameOverride field. |
|
IC-3013 |
Duplicate "Monitor Location" values displaying on Single Device Summary on HA primary FMS. |
|
AGENT-3345 |
Redesign the Net Monitor reports. |
|
AGENT-3258 |
It is not suitable to limit the packet size to larger than 40 bytes in UI, should find another better way. |
|
AGENT-3122 |
Add the ability to select existing hosts, monitored by other agents. |
|
AGENT-2852 |
The Single Location Summary page times out when a high number of devices is monitored by a single location. Workaround: You can monitor a maximum of 3,000 devices from a single location. Each device should be monitored from one location only. |
|
AGENT-2747 |
On SUSE® Linux® 10 or lower version [os command icmp] TraceRoute failed with java.lang.Exception: Stack Trace. |
|
AGENT-2700 |
Devices belonging to different LANs, with the same IP address but having different network IDs, are merged into the same Device Wrapper object. Workaround: Provide different override names for the merged network devices. |
|
AGENT-2658 |
The Net Monitor Agent does not support monitoring devices through a Round Robin DNS or DDNS name. Workaround: Do not use a Round Robin DNS or DDNS name as a device name. |
|
AGENT-2531 |
The response time, availability, and packet loss data are not consistent during the first time range period when the agents begin data collection. After the first time range period (four hours by default), the collected data becomes accurate. Workaround: Upgrade the Management Server to a version later than 5.6.11 (when available). |
|
AGENT-2449 |
Specifying an IP address as the target device name in the Net Monitor Agent Properties requires the agent to resolve the DNS name using the provided IP address. In some environments this result in a failure when the reverse DNS entry for a device is not configured properly. Workaround: Ensure that both forward and reverse DNS entries for the specified host are configured. If this does not work, use the device DNS name as the Device name override agent property value. |
|
AGENT-2446 |
Two network device entries in the Net Monitor Agent properties pointing to the same device do not trigger the Duplicated monitor on same IP Device rule. This is because one entry points to the device using the host name, while the other uses the IP address. Workaround: There is no workaround for this issue. |
|
AGENT-2108 |
NetMonitor agent doesn't support IPv6 IP address. |
The following is a list of Foglight for PowerVM issues known to exist at the time of this Foglight Infrastructure Utilities release.
|
Defect ID |
Known Issue |
|
AGENT-3716 |
PowerVMVirtualManager is not submitted when the PowerVM agent is running in an upgraded environment. For more details, see Troubleshooting Foglight for PowerVM. |
|
AGENT-3679 |
IBM® HMC Console events log takes too long to open, while the PowerVM agent is executing too many commands. |
|
AGENT-3232 |
The metrics in pop-up view of the dependency node should use the specific dependency time range, not the system time range. |
|
AGENT-3218 |
The "PowerVM VIOS State Inspect" alarm does not display in the alarm table as expected when using a Firefox® 18.0 browser. The "PowerVM Server Connect State" alarm has been cleared, but the warning icon of the specific server still exists when using a Firefox 18.0 browser. |
There are no known third-party issues specific to this release of Foglight Infrastructure Utilities.
The latest versions of the Foglight Infrastructure Utilities are:
For upgrade and compatibility information for these utilities, see the following sections:
The following is a list of product versions and platforms compatible with this Foglight Web Monitor release.
|
Product Name |
Product Version |
Platform |
|
Foglight Management Server |
5.9.2 or later |
All platforms supported by this version of the Foglight Management Server. |
|
Foglight Agent Manager |
5.9.7 or later |
All platforms supported by this version of the Foglight Agent Manager. |
Note: Foglight Agent Manager 5.9.7 or later must be installed on all the hosts that you want to use for local or remote monitoring.
The following is a list of product versions and platforms compatible with this Foglight Net Monitor release.
|
Product Name |
Product Version |
Platform |
|
Foglight Management Server |
5.6.5 or later |
All platforms supported by this version of the Foglight Management Server. |
|
Foglight Agent Manager |
5.7.0 or later |
All platforms supported by this version of the Foglight Agent Manager. |
Note: Foglight Agent Manager 5.7.0 or later must be installed on all the hosts that you want to use for local or remote monitoring.
The following is a list of product versions and platforms compatible with this Foglight for PowerVM release.
|
Product Name |
Product Version |
Platform |
|
Foglight Management Server |
5.7.5 or later |
All platforms supported by this version of the Foglight Management Server. |
|
Foglight Agent Manager Note: The monitoring agents available in this version of Foglight for PowerVM support the Agent Manager HA failover mode. For more information about this mode, see the Agent Manager Guide. |
5.8.0 or later |
All platforms supported by this version of the Foglight Agent Manager. |
Note: Foglight Agent Manager 5.8.0 or later must be installed on all the hosts that you want to use for local or remote monitoring.
Foglight Web Monitor 5.9.7 can co-exist with legacy Cartridge for Operating System 5.5.4. If you have the Cartridge for Operating System 5.5.4 installed:
To upgrade Foglight Web Monitor to version 5.9.7:
Do not uninstall or delete the previous version.
For complete instructions, see "Installing Foglight cartridges" in the Administration and Configuration Help.
For complete instructions, see "Deploying agent packages to monitored hosts" in the Administration and Configuration help.
Note: If you are monitoring URLs which need a proxy and proxy authentication, you will need to set the property 'enableProxyAuth' to 'true' to ensure there are no errors. If you do not set the property 'enableProxyAuth' to true, the monitored URLs will report a 407 error. For more details, see NTLM Proxy Authentication with Java Runtime Environment version 7.
To upgrade Foglight Net Monitor to version 5.9.8:
Do not uninstall or delete the previous version.
For complete instructions, see "Installing Foglight cartridges" in the Administration and Configuration Help.
For complete instructions, see "Deploying agent packages to monitored hosts" in the Administration and Configuration help.
To upgrade Foglight for PowerVM to version 5.9.8:
def stringType = type.getProperty("longName").type;
def shell = topSrv.beginUpdate(type);
shell.addProperty("hmcName", null, stringType, false, false, false, "default", null);
topSrv.endUpdate(shell);
def objects = #!PowerVMVirtualManager#.topologyObjects;
if(objects){
def shells = []
objects.each{object ->
def objShell = topSrv.getObjectShell(object);
objShell.set("hmcName", object.host.name);
topSrv.mergeData(objShell);
}
}
def tmp = topSrv.beginUpdate(type);
tmp.removeProperty("hmcName");
topSrv.endUpdate(tmp);
def topSrv = server.TopologyService;
def type = topSrv.getType("PowerVMVirtualManager");
tmp = topSrv.beginUpdate(type);
tmp.removeProperty("host");
tmp.removeProperty("virtualManagerHostName");
topSrv.endUpdate(tmp);
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center