CA eHealth SystemEDGEehealth-spectrum.ca.com/support/secure/pdfs/60pdfs/relnotes... · Release...

Release Notes, Release 4.2 c©2007 CA, Inc.

CA eHealth SystemEDGERelease Notes for Release 4.2

Document Version 1.2.2.2825 April 2007

Introduction

This software package contains Release 4.2 of the CA, Inc. CAeHealth SystemEDGE. CAeHealth SystemEDGEimplements MIB-II (RFC 1213), Concord’s Systems Management MIB, and the Host Resources (RFC 1514) MIB.The Systems Management MIB defines groups for kernel and system parameters, boot configuration, network, streams,and I/O buffer statistics, kernel performance statistics, an object monitoring table, system-log file monitoring, CPUmonitoring, disk I/O statistics as well as object history collection. The Host Resources MIB includes information onstorage areas (filesystems, disk partitions), running and installed software, and the system’s devices such as keyboard,disks, and network cards – information that is especially useful for asset management.This document includes information about features, requirements, and restrictions of CAeHealth SystemEDGE.Please read these release notes before using the SystemEDGE agent.For detailed information on how to usethe agent, refer to the CAeHealth SystemEDGE User Guide. For the latest support information, FAQs, and so on,refer to the following Web page:

http://www.concord.com/support/

1 What’s New in 4.2 Patch Level 5

Enhancements

• SystemEDGE is now licensed on the basis of trust.

• Monitoring windows AIM for activation/deactivation of monitoring on a daily basis. SystemEDGE can performa number of monitoring functions, as determined by user instructions, or by automated setup by some of theSystemEDGE AIMs or Aview templates. These include self-monitoring, process and process group monitoring,history collection, log file monitoring, and (for Windows) event monitoring. The SystemEDGE User Guidehas several chapters describing these monitoring functions. The sysedge.cf file contains numerous examples,also. The Monitoring Windows AIM allows the selection of any particular monitor by name and index andprovides the facility to activate and deactivate the monitor within a daily time window. This reflects user inputindicating that some monitors need not be active (producing traps and/or actions) at certain times of day due tomaintenance or other activity. The AIM can be found in the ../sysedge/plugins/monwin subdirectory. It uses asimple configuration file (monwin.cf) kept in that subdirectory, with instructions imbedded in comments in thatfile.

Bug fixes

• There are no bug fixes in this release.

Support for following Operating Systems have been dropped from this release

• Solaris SPARC 6

• Solaris SPARC 7

• HP-UX PA-RISC 11.0

1


• HP TRU64 4.0

• AIX 4.3.3

• AIX 5.1

2 What’s New in 4.2 Patch Level 4 02132007

The 02132007 release of SystemEDGE 4.2pl4 is only a Solaris 10 release.

Enhancements

• Support for Solaris 10 zones on SPARC, x86, and x8664.

Bug fixes

• SystemEDGE did not correctly enumerate software patches. (Solaris) (22420)

• SystemEDGE unable to load plugins (SA and topprocs) on x8664. (Solaris 10) (Issues: STAR 15575295,CallT0000181712, CallT0000180472)


Enhancements

• Support for SUSE Linux Enterprise Server 10 on x86, AMD64, EM64T, and Itanium.

• Support for Solaris 10 on AMD64.

• Support for HP-UX PA-RISC 11i v2 (11.23).

Bug fixes

• SystemEDGE did not correctly identify number of open files (HP-UX IA64)


The 04142006 release of SystemEDGE 4.2pl3 is a Solaris-only release.

This release applies to all processor architectures supported for Solaris (SPARC and x86).

Bug fixes

• New versions of Solaris 10 contain a updated kernel structure that causes SystemEDGE to assert an error.(Solaris 10) (17279)

• Some Host MIB oid values return strings found in the sysedge.cf file. (Solaris) (14313)

2



The 01182006 release of SystemEDGE 4.2pl3 is a Windows-only release. It contains a fix for a problem with NTservices monitoring. SeeBug fixesbelow.

NOTE: If you have already installed the original release of the Windows 4.2pl3 agent using Installshield you mustremove it prior to installing this release.

This release applies to all processor architectures supported for Windows (x86, x64 and IA64). It does not apply toany UNIX platforms. For UNIX platforms use the original 4.2pl3 release.

Bug fixes

• NT service monitoring fails to send traps when a service stops/starts (Windows) (17552)


Enhancements

• Support for SUSE Linux 9 on x86, AMD64, EM64T, and Itanium.

• Support for Red Hat Enterprise Linux WS/AS/ES 4, on x86, AMD64, EM64T and Itanium.

• Support for Windows Server 2003 on AMD64, EM64T and Itanium.

• Support for the diskStatsQueueLength, diskStatsServiceTime and diskStatsUtilization Empire MIB variableshas been added for Linux 2.6-based kernels.

• The ability to include system buffers, disk cache, or both, in the Linux free memory value reported by the agenthas been added. These values may be included in the calculation by using the linuxfreememinclude keywordin sysedge.cf. See the eHealth SystemEDGE User’s Guide for more information.

Bug fixes

• CPU statistics incorrect on system where CPUs are not numbered consecutively from 1. (HP-UX 11.x) (8627)

• Individual CPU statistics may be lower than expected on multiple CPU systems. NICE component not beingaccumulated for individual CPU metrics of the cpuStatsEntry table. (Linux) (17128)

• SystemEDGE numBreadHits counter decrementing. (Windows) (8695)

• SystemEDGE is incorrectly reporting memory and swap utilization. (HP-UX 11.x) (11116)

• processStop trap is sent when SystemEDGE agent is started if entry does not test for procAlive != 1. (All)(12648)

• SystemEDGE can report incorrect Windows service status if the service has a large amount of configurationdata. (Windows) (13024,15521)

• Regular expression passed improperly to email.exe when used as a logfile monitoring action. (Windows) (13231)

• SystemEDGE reports disks on a Compaq RAID controller incorrectly. (Linux) (13265)

• email.exe not displaying usage error when sending to multiple recipients without specifying the mail server.(All) (13419)

3


• email.exe can fail on certain DNS MX record lookups. (HP-UX IA64) (13514)

• Can’t create an ntevent monitoring entry with edgewatch against a Windows 2003 system. (All) (13911)

• First Windows idle thread is not returned by the agent. (Windows) (14326)

• SystemEDGE setup.exe does not display SystemEDGE patch level. (Windows) (14421)

• Windows disk partition sizes ¿= 4GB reported incorrectly. (Windows) (14765)

• ifLastChange value is incorrect. (Windows) (14793)

• SystemEDGE leaks handles if disk API call fails (Windows). (14894)

• SystemEDGE logfile monitoring of 2+ GB logfile always in ”Not Ready” state. (Linux) (14907)

• SystemEDGE returning empty string for group names ¿= 31 characters. (Windows) (14931)

• ifOperStatus reported incorrectly when interface link is disconnected. (Solaris) (15349)

• Incorrect number of disks reported on a Compaq RAID controller. (Linux) (15438)

• SystemEDGE fails to monitor a process with long argument list. (Solaris) (14965)

• SystemEDGE generating ”failed to open /proc/sys/kernel/inode-max” messages on Linux. (Linux) (15920)

• Slow SystemEDGE Windows startup with AIMs. (Windows) (15929)

• sysedge.mon did not get updates for ”notReady” for log monitor. (All) (16238)

• Windows agent doesn’t log authenFailure messages. (Windows) (16240)

• sendtrap core dumps with long string varbind. (Solaris) (16283)

• edgewatch doesn’t show help for ”no action script arguments (0x0020)” and ”do not send notReady traps(0x0040)” flags. (All) (16295)

• Linux Remove script does not clean up rc3.d and rc5.d. (Linux) (16364)

• Linux x86 installer allows installation on IA64. (Linux x86) (16429)

• Linux IA64 Install script allows installation on non-IA64 platforms. (Linux IA64) (16413)

• SystemEDGE leaks memory if no disks are discovered. (Windows) (16442)

• Disk Service Time is incorrect under heavy disk activity. (Windows) (16449)

• Disk Queue Length is incorrect. (Windows NT4) (16456)

• licenseme needs to report DNS failures. (All) (16710)

• File Cache Attempts and Hits always ’0’. (Solaris) (16716)

• Licensing step sometimes fails during installation due to agent startup time. (HP-UX IA64) (16718)

• Cannot discover licensed agent on system with DVD+-RW drive. (HP-UX IA64) (16809)

• diagsysedge.exe fails to determine agent’s platform. (HP-UX IA64) (16811)

• walktree core dumps while walking the MIB-2 address translation table. (HP-UX IA64) (16812)

• HP-UX disk service time always shows as 0. (HP-UX 11.x) (16899)

4


Additional Notes

• As a result of bug fix 14326 this release of SystemEDGE now returns NT thread table indices that are 1-based.Earlier versions of the agent returned 0-based indices. This change requires a corresponding fix in eHealthAdvantEDGEView (AView) so that the NT Threads query will work properly. This fix was added in eHealthversions 5.6.5 P7 and 5.7 P3. An NT Threads query issued to the new agent from an AView bundled witheHealth 5.6.5 P6/eHealth 5.7 P2 or earlier will go into an infinite loop. Should this happen, first click Stop onthe browser. Then use ”ps” (UNIX) or Task Manager (Windows) to find and kill perl.exe, which will still beexecuting.


Enhancements

• Support for AIX 5.3, 32 and 64-bit.

• Support for Solaris 10, Sparc and 32-bit x86. SystemEDGE is only supported in the global zone.

• email.exe can now insert user-defined header information, specifying ISO character set, for instance.

• checkfile.exe will now handle files of ¿ 2 gigabytes. Filesize may be displayed in bytes, kilobytes, megabytes,or gigabytes. See ”checkfile.exe -h” for details.

Bug fixes

• SystemEDGE can crash with Exchange 2.0 AIM. (Windows) (10280)

• diskQueueLength is incorrect. (Windows) (10349)

• Wrong example in sysedge.cf file. (Windows) (10884)

• Incorrect calculation of disk capacity. (Windows) (10983)

• trap source entry for SystemEDGE configuration file, not previously available on Windows. (Windows) (11013)

• Unable to license SystemEDGE on certain AIX systems. (AIX) (11279)

• Incorrect value for wordsize on Itanium. (Linux) (11299)

• SystemEDGE describing mirrored disks as unknown (Solaris) (11359)

• SystemEDGE can crash with bad values for interface number. (Windows) (12214)

• diskStatsKBytesTransferred calculated incorrectly. (AIX) (13149)

• TCP statistics incorrect on 64-bit systems. (AIX) (13853)


Enhancements

• Independence from Microsoft SNMP master agent on Windows platforms. SystemEDGE 4.2pl1 does not re-quire the Microsoft SNMP master agent. SystemEDGE 4.2pl1 can not be configured as a sub-agent under theMicrosoft SNMP master agent.

• Support for Solaris 9 x86.

5


• Support for Red Hat Enterprise Linux WS/ES/AS 3, on both x86 and Itanium.

• Concord support for Windows 2000 Datacenter.

• Concord support for Windows 2003 Datacenter.

• Support for Tru64 5.1B.

• Support for Windows 2003 clusters.

• Support for HP-UX 11i v2 Itanium (11.23).

• Control panel applet for SystemEDGE on Windows.

• sendtrap can send traps using SystemEDGE Enterprise OID. (All)

• setup.exe provides ability to change/display SystemEDGE SNMP port. (Windows)

Bug fixes

• Return behavior of the parent process monitoring flag to that of 4.1pl2. (All) (30697, 39003)

• SystemEDGE loops at ipRouteDest OID (1.3.6.1.2.1.4.21.1.1) when walked - dynamic routes. (HP-UX) (33047)

• sysUptime reporting inaccurate after 30 days. (Windows) (33719)

• SystemEDGE and vmstat show different values for page in/out. (HP-UX) (33801)

• Correction to incrementing of indices for history, log, process, and process group monitoring. (All) (33882)

• Problem with configuring SystemEDGE process monitoring and action execution. (Windows 2000) (34301)

• Lexicographic error detected in RoutingTable of SystemEDGE 4.1 pl3. (Solx86) (34390)

• SystemEDGE cores during invalid SNMP SET. (Solaris 2.7) (34422)

• Sendtrap and xtrapmon occasionally core. (Solaris 2.7) (34708)

• SNMP service could terminate unexpectedly under certain send trap conditions. (Win2000+) (35687)

• Disk partition is not being discovered. (Solaris 2.8) (35865)

• SystemEDGE stops unexpectedly, caused by topprocs. (All) (35915)

• Unable to query values from hrProcessorTable. (Solaris) (35923)

• numOpenFiles being incorrectly reported. (HP-UX) (36009)

• SystemEDGE crashing on passive node in failover cluster. (Windows 2000) (36107)

• RAW FRACTION performance registry counter type value wrong with display type of DISPLAY PERCENT.(Windows) (36767)

• SNMP service stops when SystemEDGE is loaded. (Windows 2000/2003 cluster) (37221)

• MIB returns ”incorrect” data from perf registry. (Windows) (37258)

• System user partition storage capacity values are incorrect. (HP-UX) (37714)

• Packaging for Solaris x86 contains erroneous file owner. (Solx86) (37996)

6


• Wrong varbinds sent in ntEventMonNotReady trap. (Windows) (38188)

• Under certain conditions, sendtrap variable bindings could be incorrect. (All) (38297)

• SystemEDGE crashes on some NT4 systems when xchgmod is loaded. (Windows) (38542)

• Walktree command line timeout option fixed. (All) (40416)

• SNMP failing on scheduled restart of systems. (Windows) (38804)

• walktree string oid output limited to 89 characters. (All) (39287)

• SystemEGDE loops in ipRouteTable if two interfaces have same route destination. (Linux) (39763)

• Lexicographic ordering problem in ipRouteTable. (Linux) (40171)

• SNMP MIB compilation error in topprocs.asn1. (All) (40220)

• SNMP MIB compilation error in hostmib.asn1. (All) (35575)

• Specifying timeout in walktree does not work. (All) (40416)

• Active memory reported incorrectly on 2.4 or later kernels (Linux) (40749)

• hrProcessorLoad incorrectly handled for more than 4 cpus. (HPUX) (40962)

• No hrProcessor table on some systems. (HPUX) (40967)

• SystemEDGE crashing with more than 32 physical disks (Windows) (41298,41384)

• Disk statistics reported incorrectly in some multiple physical disk environments. (Windows) (41381)

• SystemEDGE now reports on missing key data objects. (Windows) (40911)

• SystemEDGE loops in ipAddrTable (Windows Datacenter 2003) (40905)

• restartproc.exe arguments documented. (Windows) (41128)

• Enhanced MIB compiler compatibility for empire.asn1. (All) (42294)

• Fixed uninitialize string array to guard against problems originating with corrupt event log. (Windows) (42373)

• Memory allocation improvements for performance objects. (Windows) (42789)

• Debug messages for missing Windows performance objects. (Windows) (42860, 42853)


Enhancements

• Support for Microsoft Windows 2003.

• Support for AIX 5.1 64-bit.


• Support for Red Hat Enterprise Linux AS 2.1.

• Support for Red Hat Linux 9.0.

7


• Support for 64-bit disk stats on AIX 5.1 (64 bit).

• Support for 64-bit disk stats on AIX 5.2 (64 bit).

• Enhanced server types. (Windows)

• Enhanced diagnostics support tool, diagsysedge.exe. (AIX, DU/Tru64, Solaris x86)

Bug Fixes

• Recognize and exit with message if /dev/lan is absent. (HPUX) (27018)

• Increased device support on SPARC platforms (Solaris 7, Solaris 8, Solaris 9) (31562, 30189)

• Fixed numInterrupts (Windows 2000+) (33225)

• Adjustments to disk statistics to address boundary conditions. (Windows 2000+)(32781)

• Proper Registry Mapping. (Windows)

• SystemEDGE port change from install will be reflected correctly in init.d (DU/Tru64) (34968)

• Adding system contact from install will be reflected in sysedge.cf (DU/Tru64) (34967)

• Unsupported registry data types will not be added. (Windows) (34726)

• Fixed invalid comment in empire.asn1 (All)

EOL Platforms

• Dropped Support for Solaris 2.5. No Longer Supported by Sun.

• Dropped Support for Solaris 2.5.1.

• Dropped Support for HPUX 10.10. No Longer Supported by HP.

• Dropped Support for HPUX 10.20. No Longer Supported by HP.

• Dropped Support for AIX 4.2. No Longer Supported by IBM.

• Dropped Support for AIX 4.3.0 - AIX 4.3.2. No Longer Supported by IBM.

• Dropped Support for Digital Unix 4.0D - Digital Unix 4.0E. No Longer Supported by HP.

• Dropped Support for Irix.


Enhancements

• Support for Red Hat Linux 8.0.

• Support for NT4/2000 clusters. NT4 now requires SP6a+ (NT) (12429)


• Support for Tru64 5.1.

• Enhanced InstallShield SystemEDGE support for upgrades. (NT) (24194)

8


• Support for restartproc.sh in $SYSEDGE/bin. (UNIX) (25650)

• Longer NT action line length. (NT)

• Support for RPM installed software, patches on Linux. (Linux)

• InstallShield graphics enhancements. (NT)

• Enhanced support for installed software inventory on NT. (NT)

• New MIB variables for HI disk counters. (Solaris 64 bit, Linux, HPUX 64 bit, NT)

• Process group monitoring table support for users and groups. (UNIX)

• Support for chkconfig in Linux install. (Linux)

• Plugin architecture change for registering dependency data. (All)

• Support for Virtual interfaces. (Solaris 8+)

• New MIB variable for list of plugins loaded, enabled. (All)

• New MIB variable for list of templates. (All)

• Updated contrib: OracleSA Script, aviewehcustomvar, dumpsvcrsp, ntdist, svcrsp.content, licensetools (All)

• Support in licenseme.exe and autolicense.pl for UB licenses. (All) (26689)

• Diagnostics support tool, diagsysedge.exe. (Solaris, HPUX, Linux, NT)

Bug Fixes

• Support for multi-processor CPU statistics. (Tru64/DU) (10230)

• Disk I/O queue length could be incorrect. (Tru64/DU) (25070)

• Incorrect filesystem types. (Linux) (Tru64/DU) (24765)

• Incorrect flags for process monitoring in config example. (All) (24268)

• Incorrect disk stats utilization. (HPUX) (22874)

• Extra disks could show on system. (HPUX) (22867)

• Fixed processStart/processStop traps if NT service disabled. (NT) (23769)

• Eliminated delay for most CDROM and DVD devices. (HPUX)

• Updated bindaddress description in config file and manual. (UNIX) (29749)

• Fixed post Install of community string,trap destination. (IRIX) (30078)

• HPUX 11.x plugin load failures with multiple plugins. (HPUX) (24651)

• AIX 4.3.0 MIB-2 udpTable looping. (AIX) (24112)

• Fixed nostatsnfs filesystems on remote mounted SMB filesystems. (Linux) (24321)

• Removed netsvc,sybmod from licenseme. (All) (28439)

• Fixed time stamp sent by email.exe/email.pl. (All) (25342)

9


• Fixed email.exe -a parameter. email.exe as action. (NT) (27793)

• Fixed SystemEDGE config file permission problem after install. (HPUX) (30074)

• Fixed bindaddress in SystemEDGE. (AIX, Tru64/DU) (30434)

• Fixed ifSpeed 1 on Solaris 2.8. (Solaris) (26701)


Patch level 2 is primarily a bug fix release.

• Support for Solaris 9 (32-bit, 64-bit) has been added

• Support for AIX 5.1 has been added

• Support for RedHat 7.3

• Small memory leak within MIB-2 interface table (HPUX 11) (ID 695/22894)

• Large process IDs can core-dump SystemEDGE when reloading process cache. (AIX) (ID 694/22143 )

• devCapacity and devInodeCapacity MIB object percentages are now rounded rather than chopped. (All) (ID688/64643)

• Top processes plugin can sometimes miss processes causing inaccurate CPU percenates (All) (ID 686)

• Linux 2.4 kernels change how memory and swap values are obtained; SystemEDGE now properly handles this.(Linux) (ID 685/59940,21333)

• SystemEDGE ACLs now support hostnames in addition to IP addresses (UNIX) (ID 683)

• On Solaris, some patches could be omitted from software/patch inventory because they were contained in secrethidden.patchDBfile. SystemEDGE now parses this file. Solaris (ID 681)

• On AIX, installation could fail to properly set file permissions and could miss some platform variations. (AIX)(ID 680/61676)

• On AIX, ODM library confusion could cause SystemEDGE to leak memory (AIX) (ID 676)

• On HPUX, applications setting RUSEADDR could cause MIB-2 UDP table to loop. (HPUX) (ID 669/21354)

• On systems with DHCP configured network interfaces, SystemEDGE could fail to determine the system identi-fier. (Linux) (ID 667)

• skgedevice support added (Solaris) (ID 666)

• walktreedoes not allow timeout configuration (All) (648)

• SystemEDGE now distinguishes between logfile monitor matches and logfile monitor matches (All) (ID 640)

• MIB-2 ARP table memory leak (AIX) (ID 638)

• NT SNMP could core dump, mainly on laptops, after an address change (NTx86) (ID 635)

• Solaris postinstall package utility could omit some input needed by licenseme utility (Solaris) (ID 632/19166/21435)

• ntCommittedKBytes and ntCommitLimit incorrect for some NT platform combinations (NTx86) (ID 629)

10


• SystemEDGE on UNIX was not closing all its file descriptors when daemon’izing. (UNIX) (ID 624)

• On AIX, add support for SCSI ID/LUN display in disk description (AIX) (ID 623)

• ntCommitLimit fixes on NT (ID 622)

• HPUX diskStatsKBytesTransfered could be incorrect (HPUX) (ID 621)

• process group monitoring table omitted CPU seconds tallying for group (All) (ID 620)

• SystemEDGE/InstallShield package displays incorrect version number (NTx86/InstallShield) (ID 619/18857)

• At-most-x flags for process monitoring and threshold monitoring still syslog even after this condition reached(All) (ID 615)

• Logfile row creation, via SNMP, could fail if logfile does not yet exist. (All) (ID 614)

• Improvements to portability in how SystemEDGE handles memory stats across various versions of AIX (AIX)(ID 21565)

• Updates to email.exe for better out-of-box handling of default traps and actions. (All)

• SystemEDGE now distinguishes between NT-event match events and traps (NTx86)

• SystemEDGE now distinguishes between process threshold events and traps (All)

• SystemEDGE now distinguishes between threshold events and traps (All)

• Support for AdvantEDGE View 3.1 configuration profiles has been added (All)

• Install script did not properly link startup scripts (Linux) (ID 632/19166/21435)

• Install script did not properly link startup scripts (DU4) (ID 632/19166/21435)

• NT4 4-gigabyte memory systems may report incorrect memory values (NT4) (ID 19082)

• Solaris SCSI probing updated to avoid warnings from older Solaris drivers (Solaris) (ID 663)

• Process monitoring can be fooled if parent-flag is enabled but parent does not exist (All) (ID 19185)

• SystemEDGE install on NT now properly sets InstallPath registry parameter (NT)

• MIB object for fully-qualified domain name added (All)

• Two-for-one actions with NT-event monitoring (NT) (ID 18440)

• Linux distribution is now reported in kernel version MIB variable (Linux)

• Added MIB object for NT system/server type (e.g. server, advanced server, terminal server, etc.)

11


12 What’s New in Release 4.1

Release 4.1 includes new functionality, new packaging, and bug fixes. Following is an overview of the new features:

• Process group monitoring table

• Packaging for UNIX, including more comprehensive post-install scripts

• InstallShield packaging for Windows NT

• More bundled actions and extensions (including email.exe, bounce.exe, checkfile.exe, and others)

• Enhanced and bundled contributed material

• DHCP client address-change traps

• Support for trap community name configuration

• Ability to configure agent address field in traps (UNIX)

• Ability to bind to specific interfaces (UNIX)

• Row-creation optimizations for enhanced scalability and automation

• Documentation of plug-in architecture

• Licenseme utility support for authenticated proxies

• Support for Windows XP operating system

• Support for HP-UX 11i operating system

• Process state MIB variables, consistent across all platforms

• Support for monitoring new Windows 2000 event logs (Directory Service, DNS Server, and File ReplicationService)

• Shorter startup time on Windows NT

In addition to these new features, Release 4.1 includes several bug fixes:

• SystemEDGE did not allow a logfile monitoring entry to be created via SNMP if that logfile did not exist at thetime of the operation. (All) (ID 614)

• SystemEDGE did not always correctly identify number of open files (Linux) (ID 609)

• SystemEDGE sends processStart Traps for NT services even if flag disables them (NT) (ID 607)

• SystemEDGE can now detect Windows NT hotfixes. (Windows NT)

• New flag for performing logical not operation on Windows NT-event monitoring regular expressions. (WindowsNT) (ID 16404)

• New flags for performing logical not operation on regular expressions for log file monitoring. (All)

• New time zone MIB variable.

• When monitoring theprocAliveprocess attribute, SystemEDGE should sendprocStoptraps instead ofnotReadytraps if thecontNotReadyflag is set. (All) (ID 16403)

12


• DLL resource properties are now set forsysedge.dll. (NT)

• New MIB object for number of zombie processes. (All)

• Memory stats on very large Windows 2000 systems could be incorrect. (Windows NT) (ID 13519)

• Maximum size of log file monitoringlastMatchfield to 256-characters. (All) (ID 12444)

• Interface speed was incorrect for Sun gigabit-ethernet cards. (Solaris) (ID 15785)

• SystemEDGE failed to send continuous notReady traps when flag was set for Windows NT service monitoring.(Windows NT) (ID 450)

• Edgewatch dropped action field for log file monitoring entries. (All) (ID 498)

• ntCommitLimit MIB object wraps. (Windows NT) (ID 500, 11016)

• Perfmon extension counters must exist at agent start time; now, SystemEDGE can acquire them if they areinitializedafter SystemEDGE. (Windows NT) (ID 501)

• SystemEDGE could fail to get some Windows NT event log descriptions. (Windows NT) (ID 503)

• Windows NT SNMP would return NULL instead of noSuch error when querying selected SystemEDGE MIBobjects. (Windows NT) (ID 504)

• SystemEDGE now matches MIB objects in case-insensitive manner. (All) (ID 511)

• Edgewatch not catching new Windows NT system types. (All) (ID 513)

• SystemEDGE had problems accessing selected registry/perfmon counters. (Windows NT) (ID 514, 13503)

• Incorrect memory stats on AIX 4.3.3. (AIX) (ID 515, 14841)

• Windows NT instructions should point to Wordpad instead of Notepad. (Windows NT) (ID 524)

• New support for NFS/RPC (v2 and v3) stats for Linux version of SystemEDGE. (Linux) (ID 539)

• Windows NT service monitoring not reinitializing upon restart. (Windows NT) (ID 541)

• History of cpuStatsIdlePercent could fail due to race conditions. (Linux) (ID 545)

• Windows NT setup now puts installation directory in registry. (Windows NT) (ID 549)

• Windows NT setup now puts Concord Communications in registry. (Windows NT) (ID 551)

• Process state mapping may be incorrect, which could affect process monitoring. (Linux) (ID 553, 14994)

• SystemEDGE could die when queried in unlicensed mode. (HP-UX 64-bit) (ID 558)

• NT setup could produce registry warnings when removing SystemEDGE (Windows NT) (ID 559, 12693)

• Who table contains bogus date/time. (Windows NT) (ID 560, 13190)

• Auto-history capability could wedge SystemEDGE. (All) (ID 566)

• Patch list may be incomplete. (HP-UX) (ID 567)

• New no-notReady flag in 4.1. (All) (ID 569)

• Remove script error with UID variable. (Linux) (ID 571)

13


• HP-UX post-install not recognizing anything but HP-UX 11.0. (HP-UX) (ID 575, 15619)

• SystemEDGE does not detect time going backwards due to NTP. (All) (ID 578)

• SystemEDGE causes various device-related syslog messages. (Linux) (ID 579)

• SystemEDGE inefficient on HP-UX systems with large numbers of disks. (HP-UX) (ID 580)

• SystemEDGE can incorrectly identify Windows NT service pack. (Windows NT) (ID 581)

• hrSystemUptime on HP-UX can be negative. (HP-UX) (ID 582)

• Excessive Linux CPU footprint due to not caching some values. (Linux) (ID 584)

• NFS/RPC stats broken on 64-bit Solaris. (Solaris) (ID 585)

• Linux CPU stats can be munged. (Linux) (ID 587)

• Action args can be lost if double-quotes exist inside single-quotes. (All) (ID 588, 13876)

• Linux syslog messages contain garbage. (Linux) (ID 591)

• Linux disk stats broken on 2.4 kenels. (Linux) (ID 593)

• Enhance Windows NT service-enumeration capabilities (Windows NT) (ID 595)

• AIX Readme fixes (AIX) (ID 596)

• Excessive length of plug-in description can corrupt SystemEDGE. (All) (ID 599)

• PERFRAW FRACTION counters not supported in perfmon extensions. (Windows NT) (ID 600)

• Top Processes plugin on AIX 4.3.3 gives bogus values. (AIX) (ID 601)

• MIB-2 stats not rolling over. (Linux) (ID 606)

Please note that we have dropped support for HP-UX 10.01, Windows NT 3.51, and RedHat Linux 5.x. Thosereleases have reached end-of-life support from their respective vendors.New minimum requirement for SystemEDGE on Windows NT 4.0: SystemEDGE now requires NT 4.0 servicepack 4 or later.


Patch Level 3 is primarily a bug fix release. Bugs fixed and feature improvements in this release include the following:

• A new process monitoring table flag can disable all start processing so noprocessStartTraps are sent, no processstart logging occurs, and no process start actions are invoked. (All) (ID 497)

• On AIX systems, process names obtained via SystemEDGE may not match the output from thepscommand.(AIX) (ID 496)

• CPU statistics on AIX 4.3 were sometimes wrong due to kernel structure changes from 4.2 to 4.3. (AIX) (ID489)

• Process monitor action argument for current value was incorrect. (UNIX) (ID 487)

• Linux multi-processor CPU statistics were incorrectly reported. (Linux) (ID 486)

• A new global monitoring table flag can disable SystemEDGE args passed to actions. (All) (ID 485)

14


• If user had disabled process table support viano processtableconfiguration file directive, process monitoringwas also disabled. This change requests permits process monitoring to occur even if the process table has beendisabled. (All) (ID 481)

• A new version of the Top Processes plug-in (version 1.0 patchlevel 2) is bundled with this release and includesthe addition of a new column indicating process arguments. The previous version (1.0 patchlevel 1) is incom-patible with SystemEDGE 4.0 patchlevel 3 and should not be used. (All) (ID 480)

• Solaris MIB-2 ARP table could loop. (Solaris) (ID 479)

• On Linux systems, process names obtained via SystemEDGE may not match the output fromps command.(Linux) (ID 476)

• A final fix for MIB-2 ipAddressTable looping. Previously reported as BugID 207. (Solaris) (ID 474)


Patch Level 2 is primarily a bug fix release.

• Support for Solaris 8 has been added (Sparc,x86)

• Support for 64-bit HP-UX 11.x has been added. Software bundleXSWGR1100revisionB.11.00.49.3or later isrequired or patchPHNE 19984. This bundle or patch provide a missing system library.

• Process-monitor table logged notReady messages despite theno logflag big being set. (All) (ID 465)

• SNMP tooBigerror messages were not sent in all cases (UNIX) (ID 464)

• Windows NT setup.exe has been enhanced for remote and large-scale deployments with SMS (Windows NT)(ID 463)

• xtrapmoncan now be run on alternative ports (All) (ID 444)

• HP-UX 11.x startup script did not set correct SystemEDGE binary (HP-UX) (ID 441)

• SystemEDGE license Traps on Windows NT could contain wrong product code (Windows NT) (ID 440)

• edgewatchutility could not properly set flags (All) (ID 438)

• Row creations with createAndGo could create on top of active rows (All) (ID 436)

• CreateAndGo with some tables did not set the row to active state (All) (ID 435)

• Licenseme now supports web proxies and hides password (All) (ID 433)

• HP-UX 10 and 11 DT logout would sometimes kill SystemEDGE. Coded workaround for HP-UX bug. (HP-UX)(ID 431)

• Setting process monitor row state from notInService to active fails to re-acquire process ID (All) (ID 428)

• Parent process ID (PID) now supported on Windows 2000 (Windows NT) (ID 427)

• Process monitor regular expression length limit does not match MIB specification (All) (ID 423)

• Solaris ATAPICD shows up as disk rather than CDROM (Solaris) (ID 416)

• Table entries of status=destroy were sometimes visible. (All) (ID 413)

15


What’s New in 4.0

Release 4.0 includes significant new functionality. Please see theSystemEDGE Agent User Guidefor more informa-tion on these features. Briefly, the new features are as follows:

• Support for SystemEDGE plug-ins has been added. SystemEDGE’s plug-in architecture supports addition ofoptional AdvantEDGE Point Modules including Top Processes, Application and Service Response Measurementand Monitoring, Exchange, IIS, and Oracle and others. These plugin-modules can be loaded into SystemEDGEat initialization and provide an extensible and flexible approach to supporting application-specific semanticknowledge.

• Support for remote licensing has been added. Command-line utilities and License traps allow SystemEDGEto be licensed remotely without the need to hand-type system identifiers and system configuration information.AdvantEDGE View, a Web-based element manager for SystemEDGE, also supports licensing of SystemEDGEand plugins.

• Support for direct Windows NT service monitoring has been added to the process-monitor table. With thisfeature, you can monitor a Windows NT service’s status w/o having to map that service to its underlying processname.

• Support for Windows 2000 has been added.

In addition to these new features, there are several bug fixes. Those bug fixes include:

• The numberOpenFilesMIB object was only valid on Windows NT servers. New algorithm better reports thevalue of this MIB object by counting open file handles. (Windows NT) (ID 415)

• Swap calculations were slightly different than those reported by Windows NT system administration tools.Calculation formulas now adjusted to better report what Windows NT administration tools report. (WindowsNT) (ID 414)

• Monitor Trap contained incorrect flags field. (All platforms) (ID 412)

• Process-monitor table (all platforms) and Windows NT event monitoring table (Windows NT only) now support32-bit unsigned integer indices. (ID 411)

• Certain capacity-objects (e.g. swap, memory) had intermediate-calculation overflows on systems with very largeamounts of memory or swap. (IRIX) (ID 409)

• Solaris disk name mapping algorithm improved based on newly released Sun documentation. This improvementwill reduce extraneous log file warnings from certain Sun RAID devices. (Solaris) (ID 408)

• Edgewatch utility did not properly format NT Event Monitor table indices in output. (All platforms) (ID 407)

• Process and threshold-monitor table entry re-initialization interval did not match the entry interval. (All plat-forms) (ID 405)

• Process-table cache corruption can occur. (AIX) (ID 403)

• MIB-2 ifSpeed incorrect on some Solaris/Intel systems due to inconsistencies in the kernel. (Solaris/x86) (ID402)

• Possible MIB-2 Interface table corruption. (Linux) (ID 401)

• Windows NT event identifiers were not formatted properly. (Windows NT) (ID 400)

• ARP table fixes for Linux systems. (Linux) (ID 399)

16


• AIX ifAdminStatus for lo0 incorrectly reported. (AIX) (ID 398)

• Support forudpNoPortsandtcpInErrshas been added. (Solaris) (ID 397)

• procThreshold Traps, instead of procStop, can be sent when a process becomes zombie. (All platforms) (ID396)

In addition, support for several platforms has been dropped because they are no longer fielded nor supported by theirrespective vendors. Platform/OSs dropped in 4.0 include the following:

• HP-UX 9.x

• AIX 4.1

• SunOS 4.1.x

• Solaris 2.3 and 2.4

Please note that HP-UX 10.x, Solaris 2.5 and later, and AIX 4.2 and later are still supported.

What’s New in 3.1 Patch Level 3

Patch Level 3 is primarily a bug-fix release.

• SystemEDGE on SunOS could crash while parsing printcap file (SunOS only) (ID 394)

• Support for Windows NT Event monitoring via event identifier has been added. (Windows NT only) (ID 393)

• Support for HP-UX 11.0 (32-bit) has been added. (ID 392)

• Support for Linux/Intel RedHat 5.2 and 6.0 distributions has been added. (ID 391)

• Sending Traps on Linux could fail due to socket errors. (Linux only) (ID 389)

• Windows NT security updates could prevent SystemEDGE from monitoring Windows NT security event log.(Windows NT only) (ID 388)

• SystemEDGE on Windows NT may crash if incorrect registry extension syntax used in config file. (WindowsNT only) (ID 387)

• Registry extensions sometimes failed due to naming conflicts. (Windows NT only) (ID 386)

• Kernel idle process now reported as[kernel idle] to better matchpscommand. (Digital UNIX only) (ID 385)

• Fixed bug in startup script. (Digital UNIX only) (ID 383)

• Interface speeds sometimes incorrect due to conflicting Solaris API documentation. (Solaris 2.x only) (ID 382)

• Interface speed is sometimes 0 on some AIX machines. (AIX only) (ID 381)

• SystemEDGE can now background itself via-b command-line option. (All UNIX) (ID 380)

• Support for Clarion storage arrays added. (Solaris 2.x only) (ID 377)

• Support for self-monitoring of SNMP variables of type TimeTicks has been added. (All platforms) (ID 376)

• Removed limitations on number of supported extension variables. (All platforms) (ID 373)

• Windows NT Service table indices reported incorrectly. (Windows NT only) (ID 371)

17


• Fixed Windows NT extension memory leak. Some system Paged Pool memory was lost during extension invo-cation. (Windows NT only) (ID 370)

• Enhanced default Windows NT event descriptions for events where no description is found. (Windows NT only)(ID 369)

• Removed overflow in UNIX DNLC hit rate calculation. (All UNIX) (ID 367)



• walktreepreviously returned a random exit code. (all platforms) (ID 345)

• 3.1 PL 1 incorrectly converted old monitor table entries with clear Traps (All platforms) (ID 346)

• xtrapmoncan core dump (Windows NT only) (ID 348)

• Solaris TCP connection table can loop (Solaris 2.x only) (ID 349)

• Unsupported Windows NT kernel performance variables returned incorrect values (Windows NT only) (ID 350)

• Agent updates tosysedge.monwere not synchronous (All platforms) (ID 351)

• Extraneous print statements removed for IRIX Agent (IRIX only) (ID 353)

• Enablingno stat nfs filesystemson Solaris 2.x may effect filesystem monitoring of local disks (Solaris 2.x only)(ID 355)

• SNMP Sets to Logfile monitoring entries could fail if the regular expression field is longer than the description.(all platforms) (ID 357)

• The ability to configure the syslog facility that SystemEDGE uses has been added via thesyslogfacility config-uration file keyword. (UNIX only) (ID 358)

• An interoperability problem with the UCD SNMP library has been fixed. (UNIX only) (ID 360)

• Excessively long comments in the license file could have caused SystemEDGE to fail to find a valid license. (allplatforms) (ID 361)

• SystemEDGE on Windows NT may crash if configured to access a non-existent performance registry variable(Windows NT only) (ID 362)

• CPU table counters on Windows NT have been changed from nano-seconds to centi-seconds. (Windows NTonly) (ID 363)

• Support for Solaris 7 32-bit and 64-bit support has been added. (ID 364)

• Support for Linux 2.0.X kernels on Intel systems has been added. (ID 365)

• Invoking extensions on SunOS 4.x and HP-UX 9 resulted in defunct processes. Only in 3.1 PL 1 (ID 366)

18


What’s New in 3.1

Release 3.1 includes significant new functionality. Please refer to theSystemEDGE Agent User Guidefor moreinformation on these features. Briefly, the new features are:

• There is a new Process Monitoring Table that provides enhanced process monitoring capability including theability to automatically track processes after they have been re-started. Accompanying this new process moni-toring table are two new Traps —processStopandprocessStartwhich indicate when a process has stopped andstarted respectively.

• Flag options have been introduced to each of the following tables: Monitor Table, Log Monitor Table, NT EventMonitor Table, Process Monitor Table. These flags enhance the configurability of the monitoring behavior. Forinstance, you can disable the sending of Traps or system logging on a per-entry basis.

• There are new configuration file keywords for easily configuring the Monitor, Log Monitor, NT Event Monitorand new Process Monitor tables. These keywords support the new flags options and provide the ability tospecify Object Identifiers by MIB name (e.g devCapacity) in addition to the dotted-decimal form. The newkeywords are:monitorandwatch. The analogous new command-line programs are:edgemonandedgewatch.The command-line utility programslogmon, monitor, monprocess, andnteventmonhave been deprecated infavor of the newedgemonandedgewatchcommands.

• The Windows/NT version now provides an additional MIB Extension group that allows users to configure Sys-temEDGE to report additional registry parameters and performance data without the need for external programs.

• The Agent now writes all monitoring tables (Process, Monitor, Log Monitor, and NT Event Monitor) to themonitor table backing store file (sysedge.mon).

• The following new MIB objects are now supported:

– kernelperf.pageScans- The number of page scans on the system. This is a good indicator of paging healthon the system. (UNIX only, except IRIX)

– ntServiceEntry.ntServiceObjectName- The object name for the service. This indicates the user name theservice is currently running as. (Windows NT Only)

– ntEvents.ntEventApplicationMaxSize- Maximum size for the Windows NT Application Event log. Similarentries for System and Security logs. (Windows NT Only)

– ntEvents.ntEventApplicationRetention- Retention flags for the Windows NT Application Event log. Sim-ilar entries for System and Security logs. (Windows NT Only)

• A memory leak in Windows NT process table manipulation has been fixed (Windows NT Only) (ID 340)

• NT Event monitor Traps contained an incorrect object-identifier for the event description match string. (Win-dows NT Only) (ID 339)

• The Agent was not properly closing open file descriptors before calling extensions. This could cause problemswith the SNMP port being held by extensions that did not exit correctly. (All UNIX platforms) (ID 326)

• The monitor table did not correctly update the maximum and minimum value columns for delta values. (Allplatforms) (ID 322)

• On Solaris systems the ifTable counters were sometimes incorrect for hosts with multiple interfaces. (Solaris2.x only) (ID 321)

• The implementation of filesystem information (hrStorage and empire.devTable) was changed to improve effi-ciency and reduce blocking problems with remote filesystems. (All Unix platforms) (ID 319)

19


• All platforms were converted to use our own regular expression library. This is mostly for consistency, nofunctional change should occur. (All Unix platforms) (ID 318)

• The monitor table did not calculate deltas as absolute deltas. Only positive deltas were previously handled. (Allplatforms) (ID 317)



• AIX agent reportedmib2.ip.ipForwardingincorrectly. (AIX only) (ID 315)

• Large sub-identifiers in object identifiers not properly ASN.1 encoded by agent utilities (e.g.monitor, etc.) (Allplatforms) (ID 314)

• AIX agent did not properly handle PIDs> 32, 000 (AIX only) (ID 313)

• Solaris agent did not include NFSv3 stats in NFS statistics MIB group (Solaris 2.x only) (ID 312)

• Support AIX 4.3 added. (AIX only)

• Solaris agent stat’d NFSv3 filesystems even ifno stat nfs filesystemswas enabled. (Solaris 2.x only) (ID 310)

• ntServiceTablevalue lengths were incorrectly reported. (Windows NT Only) (ID 309)

• Support for Digital UNIX 4.0D+

• runQLenreported incorrectly on IRIX. (IRIX Only) (ID 306)

• monitorandlogmonutilities would exit with exit code 0 even if invocation errors. (All platforms) (ID 305)

• IRIX agent can report incorrect number if network interfaces. (IRIX Only) (ID 304)

• Interaction between the agent’s self-monitoring functionality and extension objects has been made more robust.(AIX Only) (ID 302)

• AIX agent could loop within MIB-2 ipRouteTable. (AIX Only) (ID 301)

• Log file monitoring on AIX could miss expression matches. (AIX Only) (ID 300)

• Statistics on SunOS filesystems greater than 2 gigabytes were not reported correctly. (SunOS 4.1.x) (ID 299)

• Disk statistics on Windows NT were sometimes inaccurate (Windows NT Only) (ID 298)

• ntThreadElapsedTimeandntPageReadincorrectly reported. (Windows NT Only) (ID 297,293)



• AIX version reported nfs3 and mvfs filesystem types as local. This meant that the hostname was not included inthe devDevice field of the Empire devTable. (AIX Only) (ID 281)

• On HP-UX systems, cpum715e was not recognized correctly. (HP-UX Only) (ID 282)

• On Windows NT systems, agent could enter a loop when the event monitor fails to load a message from a DLL.(Windows NT Only) (ID 283)

20


• In 3.0 patch level 2 there is a race condition with the new cpuTotalPercents that could result in an agent coredump at startup when monitoring these variables. (All Platforms) (ID 284)

• Windows NT PageFileUsage was reported with incorrect scale. Should be between 0-100. (Windows NT Only)(ID 285)

• The logMonitorLogFileLastUpdate value was reported incorrectly. (All Platforms) (ID 286)

• Solaris agent was under reporting value for totalSwapSpace. Agent should report same value as ”swap -s”.(Solaris Only) (ID 287)

• AIX kernelper.runQLen and kernelperf.swapActive variables were not calculated correctly. (AIX Only) (ID288)

• On 64-bit IRIX systems, the ARP and ipNetToMedia tables were corrupted due to incorrect calculation of 64-bitstructure sizes. (IRIX Only) (ID 291)

• Solaris agent would occasionally report an empty devTable (mounted filesystem). Problem was a race conditioninvolving access to the mounted filesystem table. Fixed by locking access to the mount table. (Solaris Only) (ID292)

• The ntPageReads value was incorrectly reporting the same data as ntPageFaults. (Windows NT Only) (ID 293)



• Thesendtrapprogram exited with a random value rather than returning 0. It now returns zero on success. (AllPlatforms) (ID 268)

• AIX version did not reuse memory correctly when calculating filesystem capacity table. This memory loss hasbeen fixed. (AIX Only) (ID 269)

• Windows NT version did not correctly implement the processMEM and processRSS fields of the Empire Processtable. (Windows NT Only) (ID 270)

• An SNMP set of the Monitor table Action was incorrectly truncated at 64 characters. The full 256 characters isnow supported. (All Platforms) (ID 272)

• The description fields of the Monitor, Log Monitor and NT Event Monitor tables were previously limited to be64 characters long. This limitation has been increased to 128 characters. (All Platforms) (ID 273)

• Themonfilesysandmonprocessconfiguration file keywords now force the sysedge.mon file to be updated. (AllPlatforms) (ID 274)

• Themonprocesscommand now supports matching both on the process name and process parameters. See themonprocess.1man page for details. (All Platforms) (ID 275)

• The hrSWRunParameters column of the host resources running software table is now fully supported in AIX.(AIX Only) (ID 276)

• The hrSWRunParameters column of the host resources running software table previously returned arg0 whenthere are no parameters. This is changed to return a NULL string if no parameters are found. (All UNIXPlatforms) (ID 277)

• Support for Sun Sparc Ultra 5/10 systems has been added. (Solaris/Sparc Only) (ID 278)

• The mounted device table no longer includes /dev/fd. (Solaris Only) (ID 279)

• The MIB-2 interface table had incorrect entries for some SGI platforms. (IRIX only) (ID 260)

21



Patch Level 1 is primarily a bug-fix release. New features includeMonitor Clear Trapsand several new configurationfile keywords for simplifying agent configuration.

• The Monitor Table now supports sending amonitorClear Trapwhen a monitored condition changes from Trueto False. This is specified by using a different operator in the monitor table entry. See the manual for moredetails. (All Platforms)

• The History Table can now be configured at agent startup using theemphistorykeyword in the configuration filesysedge.cf. See the manual for details. (All Platforms)

• You can now specify a alternative user and group permissions for all subprograms invoked by the agent. Thesesubprograms include extensions, actions and remote shell commands. Use the configuration file statementssubprogramusernameandsubprogramgroup nameto configure this feature. (UNIX Only)

• A new configuration file statementno stat floppycan be used to turn off status queries of the floppy device onUNIX systems. This is useful to prevent long delays in accessing thehrDevicetable on some systems. (UNIXOnly) (ID 236)

• Errors in system swap calculation for Solaris 2.6 are fixed. (Solaris 2.6 Only) (ID 254)

• All extraneous file descriptors are now closed before calling action programs. (UNIX Only) (ID 256)

• Windows NT agent now uses the functionGetComputerName()for the Empirenodenamevariable. The previousagent used the DNS name which sometimes differed from the actual system name. (Windows NT Only) (ID259)

• A problem was fixed in theipAddrTablethat resulted in query loop when an uninitialized (zero) address waspresent. (SGI IRIX Only) (ID 260)

• Statistics in thediskStatsTableare now reported correctly for 64-bit SGI systems running IRIX 6.2. (SGI IRIXOnly) (ID 261)

• Statistics in thecpuStatsTableare now reported consistently on Windows NT systems. Previous versions of theagent would sometimes report zero for all CPU statistics. (Windows NT Only) (ID 263)

• Thecpu15Minvalue is now calculated correctly on SGI IRIX. Previous versions of the agent would report zerofor this value. (SGI IRIX Only) (ID 264)

• The use ofcpuStatsTableentries in the monitor table is now supported. Previous versions of the agent did notallow monitoring of these values across agent restarts. (All Platforms) (ID 266)

What’s New in 3.0

Release 3.0 includes significant new functionality. Please refer to theSystemEDGE Agent User Guidefor moreinformation on these features. Briefly, the new features are as follows:

• The new name for the Empire SNMP agent product is the SystemEDGE Agent. The names of software ex-ecutables and configuration files have been changed. (e.g. /etc/snmpd.empire.conf -¿ /etc/sysedge.cf) Whenupgrading you should rename your configuration, monitor, and license files. However, the agent will use oldconfiguration files if the new ones are not found.

• The product documentation and release notes are now provided in Adobe PDF format.

22


• MIB extension support allows users to add scalar MIB variables via the agent configuration file. Exampleextension scripts are also included. Please refer to manual for detailed information on MIB extensions.

• Support for Windows NT event log monitoring, filtering, and forwarding as SNMP Trap messages on WindowsNT systems.

• Self-management Actions enable the agent to invoke scripts/programs when monitor entries evaluate to true,when log-file matches are found, or when Windows NT event log matches are found

• A new disk I/O statistics table provides per-disk statistics such as queue length, utilization, number of reads andnumber of writes.

• A new CPU statistics table provides per-CPU statistics such as user time, system time, wait time and idle time.

• Support for Sun Solaris 2.6 on both SPARC and Intel x86 systems.

• Support for SGI IRIX 6.2+ on SGI systems.

• Support for IBM AIX 4.1.x on RS/6000 systems.

• MIB table index preservation for select Host Resources and Empire MIB tables.

• New command-line utilities for receiving Traps and initializing Windows NT event monitor table entries.

• New configuration file keywordsmonfilesys, monprocessare provided for simplifying the task of filesystem andprocess monitoring.

• Configuration files for use in conjunction with the Solstice Enterprise Agent (SEA).

• CDROM distribution

What’s New in 2.0• System log file monitoring

• Object history collection

• Management applications for log-file monitoring and object history collection

• UNIX man-pages

• Support for HP-UX 9 and 10 on 9000/700 systems

• Support for Solaris x86

• Support for Windows NT

System RequirementsThe SystemEDGE agent operates on a variety of systems and hardware platforms.

- 8MB of RAM- 4 MB disk space- hardware platform (one of the following:)

Sparc Workstations and ServersSolaris SPARC 2.6Solaris SPARC 2.7 (32/64 bit)Solaris SPARC 2.8 (32/64 bit)Solaris SPARC 2.9 (32/64 bit)Solaris SPARC 2.10 (64 bit, global zone only)

Solaris x86 2.6-2.10 (32 bit)

23


Solaris 2.10 (AMD64)HP 9000 series (PA-RISC)

HP-UX 11.0, HP-UX 11i (32/64 bit), HP-UX 11i v2 (11.23 64 bit)HP Integrity (Itanium)

HP-UX 11i v2 (11.23 64 bit)IBM RS/6000 series

AIX 4.3.3(32 bit)/AIX 5.1-5.3(32/64 bit)Windows Workstations and Servers (x86)

Windows NT 4.0 SP6a+Windows 2000Windows XPWindows 2003 (32 bit)

Windows Servers (x64 - AMD64 and EM64T)Windows 2003 (all versions except Datacenter)

Windows Servers (IA64 - Itanium)Windows 2003 (all versions except Datacenter)

Red Hat Linux (x86) 6.0-9.0Red Hat Enterprise Linux AS 2.1 (x86)Red Hat Enterprise Linux WS/ES/AS 3 (x86/Itanium)Red Hat Enterprise Linux WS/ES/AS 4 (x86/AMD64/EM64T/Itanium)SUSE Linux Enterprise Server 9 (x86/AMD64/EM64T/Itanium)SUSE Linux Enterprise Server 10 (x86/AMD64/EM64T/Itanium)Digital UNIX 4.0F/Digital UNIX 4.0GTru64 5.1ATru64 5.1B

Required and Recommended System Patches

In general, we recommend that all systems be kept up to date and that all recommend patches be installed. However,the following patches are required for use in conjunction with the relevant platform and the SystemEDGE agent. If asupported system is not listed below, no patches are required in order for the SystemEDGE agent to operate.

Required Patches

• HP-UX 11.0/64-bit

– XSWGR1100 revision B.11.00.49.3 or later is required or patch PHNE19984. This bundle provides amissing system library.

Recommended Patches

• Solaris 2.5

– 103244,102979 update the le and hme drivers (respectively) to better support MIB-2 interface table coun-ters

• Solaris 2.5.1


• Solaris 2.6

24



• Solaris 2.8

– 117000 (Sparc),117001 (x86) fixes an issue with incorrect cpu statistics.

• HP-UX 11.11

– PHNE 27063 s700800 11.11 cumulative ARPA Transport patch or later is recommended. This fixesmemory issues with HP-UX libraries.

Limitations

General Information

• Virtualization/partitioning

Different vendors support various methods of partitioning hardware to allow multiple operating systems to run concurrentlyon the same physical box.

The rule here is that for any specific partitioning/virtualization mechanism, if support is not called out explicitly, it is notsupported. In many cases the agent will run and respond, but one or more key pieces of data supplied may be incorrect.

• Interface Speed

The MIB-II Interface Table contains an object namedifSpeedrepresenting an interface’s current bandwidth in bits persecond. Since the SunOS and Solaris kernels do not track this object for network interfaces, the value of this object for anygiven interface can only be estimated. For example, interfaces conforming to the ethernet or IEEE 802.3, the interface speedis well-known (10 Mbps); on the other hand, the bandwidths of serial interfaces are inherently variable and therefore noaccurate estimate of the current bandwidth can be obtained. For these types of interfaces, the value of “1” is returned fortheir ifSpeedobject.

The Empire and Host Resources MIBs contain many objects representing different aspects of the performance of the com-puter and associated devices. In general, performance statistics are generally gathered and maintained by the kernel. In somecases, the performance statistics are estimates.

• Installed Software

The installed software group is not supported on SunOS 4.1.X platforms because no accurate, consistent method exists fortracking installed software. Indeed, all binaries and shell scripts installed by the system administratorand userscould beconsidered to be installed software packages. Because the disk capacity for Sun workstations could potentially be quitelarge, to list each and every executable file in the entire filesystem would be a time-consuming operation that would producea list that is so long as to become useless by its sheer magnitude.

Operating systems, such as Solaris 2.X, HP-UX 11.x, AIX, and Windows NT, that have a consistent Software PackageInstallation facility, do provide the information necessary for the agent to support this group. Any software package installedusing the Software Package Installation facility will be reported by the agent. In addition, operating system patches, installedusing Solarisinstallpatchor HP-UXupdateor swinstallfacilities, are also reported by the agent. On Windows NT systems,only those software packages registering themselves in the appropriate Registry directory will be reported.

• Remote Shell Invocation

Managers can invoke shell commands remotely by setting objects in the agent’s MIB (the Concord Systems ManagementMIB remoteShellgroup). If this functionality is considered a security weakness by local policies, it can be disabled via theno remoteshellgroupswitch in the agent’s configuration file. Several limitations apply to the remote shell invocation func-tionality. First, all output must be directed to a file in the/tmp, \temp, or\tmpdirectories. This re-direction occurs by settingtheshellOutputvariable. Second, the exit status of the sub-command is available if the command is run “synchronously” –that is, not in the background. The agent scans the shell-command (set via theshellCmdvariable) for the ’&’ character. On

25


HP-UX 9 systems, commands in the background prevent the agent from determining the exit status. On UNIX systems, theshell command is invoked via thesystemfunction call with usesfork andexecto spawn the shell command. On WindowsNT systems, however, thesystemcall is still used butfork andexecnot exist nor can the agent spawn additional threads dueto rules dictated by the Microsoft master agent. Therefore, Windows NT does not support the notion of invoking a commandin the background. Because of these Windows NT limitations, when a manager invokes a shell command on a Windows NTsystem, the entire agent (Master agent and Concord sub-agent) are blocked until that command exits. If the shell commandblocks indefinitely, so will the master agent and its sub-agents.

• Windows Systems

The SystemEDGE agent (4.1 pl 4 and lower) operates as a sub-agent operating under or within the Microsoft SNMP Masteragent. This does not apply to SystemEDGE 4.2 pl 1 and higher. In order for the Concord sub-agent to operate properly,the Microsoft agent must be installed and properly configured. Consequently, on Windows NT systems, all community andMIB-2 system-group configuration (normally done in the Concord agent’s config file) is accomplished via the MicrosoftSNMP service configuration dialogs. Community and system-group config statements in the Concord config file will beignored. In order to support legacy DOS/PC based filesystems, the Concord sub-agent’s configuration files (on Windows NTsystems only) have been renamed:snmpd.empire.confbecomesEMPuma.cf; snmpd.empire.licensebecomesEMPuma.lic;snmpd.empire.monitorbecomesEMPuma.mon. Also on Windows NT systems, the config files must reside in thesystem32sub-directory under the system root (e.g. c:\winnt35\system32 or c:\winnt\system32).

Windows Itanium-based servers:

– Windows 2003 Service pack 1 should be applied. If it is not, an incorrect start time will be returned for both the Idleand System processes.

– The ntThreadElapsed time for thread 0 of the System process is reported as a negative number. This is due to anincorrect start time returned by Windows.

– The romVersion variable returns a null value.

– The ntSysBiosVersion variable returns a null value.

• Extension Objects

The SystemEDGE agent provides the ability to add additional MIB objects to the agent’s MIB. This functionality enablesusers to utilize local programs and scripts to obtain information, cause actions, monitor application services, and have theirwell-formatted output returned by the Agent and, consequently, included in the SNMP framework. For example, mail, news,POP3, and Web server load can all be measured and returned by the Agent. However, care must be taken when writingextension scripts – they should not block indefinitely nor take excessive amounts of time. The Agent executes executesextension scripts/program synchronously and blocks until they return. A malformed or erroneous script can block the agentand prevent it from performing its other duties.

Device Information

SystemEDGE maintains an internal list of devices it knows about. Since the universe of third-party devices is unlimited, the ConcordSystemEDGE Agent may report a device as unknown. If a device is reported as unknown, please send email [email protected] the device name, description, device file name, man page, etc.

• Host Resources – Host’s Devices

Devices are automatically discovered using a variety of methods including examining the running kernel directly, checkingkernel configuration files, and querying kernel device files. For some devices, like terminals, modems, and printers, the kerneland user programs can only communicate with those devices if they are properly added to the appropriate configuration files.Therefore, some devices may not be discovered (and reported by the agent) if they have not been properly added to theirappropriate configuration files. HP-UX 9 provides a more limited ability for automatic device discovery; nevertheless, theagent does support the discovery of a subset of all HP devices. HP-UX 10 provides better, but not yet complete, support forautomatic device discovery.

In reporting a device’s status, configuration information, or usage statistics, the agent often depends on the device’s kerneldriver for such information. If the kernel driver does not keep statistics or configuration information, the SystemEDGE agent

26


may not be able to report such information either. For example, the keyboard device driver may report that a Sun keyboardis Type 4 even though the keyboard may actually be Type 5.

• Host Resources – Physical Devices

Removable media devices like tapes, floppy disk drivers, and compact-disc devices can often only be examined if there is amedia unit in them. For example, many times, a tape device not containing a tape, cannot have its status fully ascertained.

Further, some devices only allow a single process or program to access them at any one time. For example, if an audio CDis being played by a CDROM (on a Sun workstation), the agent will be unable to open the device and ascertain its devicedescription and vendor. Likewise, the floppy disk driver does not properly report its status unless a floppy disk has beeninserted. In addition, the floppy disk’s capacity will vary depending on what type of format has been placed on the floppydiskette.

• Solaris Volume Management

A volume management facility, starting with Solaris 2.2, provides support for the automatic mounting and unmounting ofremovable media like CDROM drives and floppy disks. The Volume Management daemon,vold, reads the configuration file/etc/vold.confto determine which devices it should monitor. However, in order to do so,vold exclusively opens the devicesit is monitoring. Consequently, the agent is often unable to ascertain the status of devices under volume management. Forthese devices, the agent returns a status of unknown.

Linux Support

SystemEDGE has been tested on a variety of Linux systems running kernel versions ranging from 2.0.35 to 2.6 fromthe RedHat distribution, as well as 2.6-based SUSE kernels. In general, Linux support is currently limited to kernelversions 2.0, 2.4 and 2.6 regardless of the particular distribution (e.g. Debian, Slackware, SUSE, etc.). However, dueto the considerable variation between Linux distributions, both commercial and non-commercial, Linux support isprovided on anas-isbasis only. In particular, variations in shared libraries (e.g. libc.so and ld-linux.so) can adverselyeffect the operation of SystemEDGE on those systems. Usually, Agent invocation errors can be obviated by updatingthose two libraries.The system libraries needed by SystemEDGE and associated utilities are:

• libc.so (compiled against libc-2.0.7.so)

• ld-linux.so (compiled against ld-2.0.7.so)

SystemEDGE, on Linux, makes extensive use of the/proc facilities provided by the underlying kernel. Failure toaccess those files can limit SystemEDGE’s support for certain MIB groups.Certain OIDs are meaningless for the Reiser file system. These are devTable.devTfiles (maximum number of files),devTable.devFfiles (number of free files), and devTable.devInodeCapacity (percentage of inodes in use).

Known Issues

• SystemEDGE may not report loopback interface on HPUX. (35025)

27


Unsupported MIB Objects on Solaris 2.X

MIB-IIObject Comment

ifTable.ifEntry.ifSpeed If appropriate patches have been installedifTable.ifEntry.ifInOctets If appropriate patches have been installedifTable.ifEntry.ifLastChange Not supported by Solaris 2.XifTable.ifEntry.ifInNUCastPkts Not supported by Solaris 2.XifTable.ifEntry.ifDiscards Not supported by Solaris 2.XifTable.ifEntry.ifInUnknownProtos Not supported by Solaris 2.XifTable.ifEntry.ifOutOctets If appropriate patches have been installedifTable.ifEntry.ifOutNUCastPkts Not supported by Solaris 2.XifTable.ifEntry.ifOutQLen Not supported by Solaris 2.XifTable.ifEntry.ifSpecific Not supported by Solaris 2.Xegp Not implemented in current release

Host Resources MIBObject Comment

hrSystemInitialLoadParametersNot implemented in current releasehrStorageAllocationFailures Not supported by Solaris 2.XhrDeviceID Hardware manufacturers haven’t assigned IDshrDeviceErrors If supported by the device itselfhrProcessorFrwID Manufacturers haven’t assigned IDshrPrinterTable Not implemented in current releasehrFSLastFullBackupDate Not implemented in current releasehrFSLastPartialBackupDate Not implemented in current releasehrFSBootable Not implemented in current releasehrSWRunID Not supported by Solaris 2.XhrSWRunPath Process may change these valueshrSWRunParameters or they may not be suppliedhrSWInstalledID Not supported by Solaris 2.X

28


Empire Systems Management MIB

Object Comment

streams.numMuxLinks Not supported by Solaris 2.Xstreams.dblockUse Not supported by Solaris 2.Xstreams.dblockMax Not supported by Solaris 2.Xstreams.dblockFail Not supported by Solaris 2.Xperformance.cpuSxbrk Not supported by Solaris 2.Xkernelperf.diskWaitNum Not supported by Solaris 2.Xkernelperf.pageWaitNum Not implemented in current releasekernelperf.swapActive Not implemented in current releasekernelperf.sleepActive Not implemented in current releasembufAllocTable Not supported by Solaris 2.XstrbufAllocTable Not supported by Solaris 2.XioBufferCache.numAgeAlloc Not supported by Solaris 2.XioBufferCache.numLRUAlloc Not supported by Solaris 2.XioBufferCache.minNumBufHdrs Not supported by Solaris 2.XioBufferCache.numAllocBuf Not supported by Solaris 2.Xnt Not supported by Solaris 2.Xnfs.clientNFSclsleep Not supported by Solaris 2.X

Unsupported MIB Objects on Solaris 2.10

Note: This is in addition to the above unsupported objects for Solaris 2.X.


Object Comment

queID Not supported by Solaris 2.10queKey Not supported by Solaris 2.10queMode Not supported by Solaris 2.10queOwner Not supported by Solaris 2.10queGroup Not supported by Solaris 2.10queNBytes Not supported by Solaris 2.10queNMesg Not supported by Solaris 2.10queDel Not supported by Solaris 2.10shmemID Not supported by Solaris 2.10shmemKey Not supported by Solaris 2.10shmemMod Not supported by Solaris 2.10shmemOwner Not supported by Solaris 2.10shmemGroup Not supported by Solaris 2.10shmemSegSz Not supported by Solaris 2.10shmemNLcks Not supported by Solaris 2.10shmemDel Not supported by Solaris 2.10semID Not supported by Solaris 2.10semKey Not supported by Solaris 2.10semMode Not supported by Solaris 2.10semOwner Not supported by Solaris 2.10semGroup Not supported by Solaris 2.10semNsems Not supported by Solaris 2.10semDel Not supported by Solaris 2.10

29


Unsupported MIB Objects on HP-UX 11.0/11.11/11.23 (PA-RISC, ia64)


ifTable.ifEntry.ifSpecific Not supported by HP-UX 11.XXip.ipRouteEntry.ipRouteMetric5 Not supported by HP-UX 11.XXip.ipRouteEntry.ipRouteInfo Not implemented in current releaseegp Not implemented in current release


hrSystemInitialLoadParametersNot implemented in current releasehrStorageAllocationFailures Not supported by HP-UX 11.XXhrDeviceID Hardware manufacturers haven’t assigned IDshrDeviceErrors If supported by the device itselfhrProcessorFrwID Manufacturers haven’t assigned IDshrPrinterTable Not implemented in current releasehrPartitionTable Not supported by HP-UX 11.XXhrFSLastFullBackupDate Not implemented in current releasehrFSLastPartialBackupDate Not implemented in current releasehrFSBootable Not implemented in current releasehrSWRunID Not supported by HP-UX 11.XXhrSWRunPath Process may change these valueshrSWRunParameters or they may not be suppliedhrSWInstalledID Not supported by HP-UX 11.XX


Object Comment

kernelconfig.romVersion Not supported by HP-UX 11.XXkernelconfig.maxInode Not supported by HP-UX 11.XXkernelconfig.maxFiles Not supported by HP-UX 11.XXkernelconfig.maxClist Not supported by HP-UX 11.XXkernelconfig.maxMemPerProc Not supported by HP-UX 11.XXstreams Not supported by HP-UX 11.XXperformance.cpuSxbrk Not supported by HP-UX 11.XXmbuf (group, table) Not supported by HP-UX 11.XXbootconf (group) Not supported by HP-UX 11.XXstrbufAllocTable Not supported by HP-UX 11.XXioBufferCache Not supported by HP-UX 11.XXnt Not supported by HP-UX 11.XXrpc.clientRPC Not supported by HP-UX 11.XXnfs.clientNFSclseeps Not supported by HP-UX 11.XXdiskStatsTable.diskStatsReadsNot supported by HP-UX 11.XXdiskStatsTable.diskStatsWritesNot supported by HP-UX 11.XXnumBreadHits Not supported by HP-UX 11.XXnumBreadRequests Not supported by HP-UX 11.XX

30


Unsupported MIB Objects on AIX 4.3.3/5.1/5.2


ifTable.ifEntry.ifSpeed Estimated value due to AIX 4.3.3/5.1/5.2 limitationsifTable.ifEntry.ifSpecific Not supported by AIX 4.3.3/5.1/5.2ip.ipInUnknownProtos Not supported by AIX 4.3.3/5.1/5.2ip.ipInDiscards Not supported by AIX 4.3.3/5.1/5.2ip.ipFragOKs Not supported by AIX 4.3.3/5.1/5.2ip.ipFragFails Not supported by AIX 4.3.3/5.1/5.2ip.ipFragCreates Not supported by AIX 4.3.3/5.1/5.2tcp.tcpOutRsts Not supported by AIX 4.3.3/5.1/5.2udp.udpInDatagrams Not supported by AIX 4.3.3/5.1/5.2udp.udpNoPorts Not supported by AIX 4.3.3/5.1/5.2udp.udpOutDatagrams Not supported by AIX 4.3.3/5.1/5.2egp Not implemented in current release


hrSystemInitialLoadParametersNot implemented in current releasehrStorageAllocationFailures Not supported by AIX 4.3.3/5.1/5.2hrDeviceID Hardware manufacturers haven’t assigned IDshrDeviceErrors If supported by the device itselfhrProcessorFrwID Manufacturers haven’t assigned IDshrPrinterTable Not implemented in current releasehrPartitionTable Not supported by AIX 4.3.3/5.1/5.2hrFSLastFullBackupDate Not implemented in current releasehrFSLastPartialBackupDate Not implemented in current releasehrFSBootable Not implemented in current releasehrSWRunID Not supported by AIX 4.3.3/5.1/5.2hrSWRunPath Not implemented in current releasehrSWRunParameters Not implemented in current release

31



Object Comment

devTable.devFstr Not supported by AIX 4.3.3/5.1/5.2kernelConfig.maxFiles Not supported by AIX 4.3.3/5.1/5.2kernelConfig.maxMemPerProc Not supported by AIX 4.3.3/5.1/5.2bootconf Not implemented in current releasestreams Not implemented in current releaseprocessTable.processSysCalls Not supported by AIX 4.3.3/5.1/5.2whoTable.whoEntry.whoPid Not supported by AIX 4.3.3/5.1/5.2performance.diskWaitNum Not supported by AIX 4.3.3/5.1/5.2performance.pageWaitNum Not supported by AIX 4.3.3/5.1/5.2performance.sleepActive Not supported by AIX 4.3.3/5.1/5.2performance.numSwapIns Not supported by AIX 4.3.3/5.1/5.2performance.numSwapOuts Not supported by AIX 4.3.3/5.1/5.2msgqueTable Not supported by AIX 4.3.3/5.1/5.2shmemTable Not supported by AIX 4.3.3/5.1/5.2semTable Not supported by AIX 4.3.3/5.1/5.2strbufs Not supported by AIX 4.3.3/5.1/5.2ioBufferCache Not supported by AIX 4.3.3/5.1/5.2nt Not supported by AIX 4.3.3/5.1/5.2distribsys Not supported by AIX 4.3.3/5.1/5.2diskStatsTable.diskStatsQueueLengthNot supported by AIX 4.3.3/5.1/5.2numBreadHits Not supported by AIX 4.3.3/5.1/5.2numBreadRequests Not supported by AIX 4.3.3/5.1/5.2

32


Unsupported MIB Objects on Windows NT 4/2000/XP/2003

MIB-II

The SystemEDGE agent does not support MIB-II on Windows NT/2000/XP/2003 systems because the MicrosoftMaster agent already provides this support.


hrSystemInitialLoadParameters Not supported by Windows NT/2000/XP/2003hrStorageAllocationFailures Not supported by Windows NT/2000/XP/2003hrDeviceID Hardware manufacturers haven’t assigned IDshrDeviceErrors If supported by the device itselfhrProcessorFrwID Manufacturers haven’t assigned IDshrPrinterTable Not implemented in current releasehrFSRemoteMountPoint Not supported by Windows NT/2000/XP/2003hrFSLastFullBackupDate Not supported by Windows NT/2000/XP/2003hrFSLastPartialBackupDate Not supported by Windows NT/2000/XP/2003hrFSAccess Not supported by Windows NT/2000/XP/2003hrFSBootable Not implemented in current releasehrSWRunEntry.SWRunPath Not supported by Windows NT/2000/XP/2003hrSWRunEntry.SWRunParametersNot supported by Windows NT/2000/XP/2003hrSWInstalledID Not supported by Windows NT/2000/XP/2003

33



Object Comment

system.hostid Not supported by Windows NT/2000/XP/2003devTable.devTfiles Not supported by Windows NT/2000/XP/2003devTable.devFfiles Not supported by Windows NT/2000/XP/2003devTable.devMaxNameLen Not supported by Windows NT/2000/XP/2003devTable.devFstr Not supported by Windows NT/2000/XP/2003devTable.devInodeCapacity Not supported by Windows NT/2000/XP/2003kernelConfig.serialNumber Not supported by Windows NT/2000/XP/2003kernelConfig.romVersion Not supported by Windows 2003 (x64, ia64)kernelConfig.maxInode Not supported by Windows NT/2000/XP/2003kernelConfig.maxFiles Not supported by Windows NT/2000/XP/2003kernelConfig.maxClist Not supported by Windows NT/2000/XP/2003kernelConfig.maxMemPerProc Not supported by Windows NT/2000/XP/2003kernelConfig.openMaxPerProc Not supported by Windows NT/2000/XP/2003kernelConfig.posixJobCtrl Not supported by Windows NT/2000/XP/2003kernelConfig.posixVersion Not supported by Windows NT/2000/XP/2003bootconf Not supported by Windows NT/2000/XP/2003streams Not supported by Windows NT/2000/XP/2003userTable.userUID,GID Not supported by Windows NT/2000/XP/2003userTable.userShell Not supported by Windows NT/2000/XP/2003processTable.processFlags Not supported by Windows NT/2000/XP/2003processTable.processUID,GID Not supported by Windows NT/2000/XP/2003processTable.processParentPID Not supported by Windows NT/2000/XP/2003processTable.processInBlks,outBlks Not supported by Windows NT/2000/XP/2003processTable.processMsgsSent,RecvNot supported by Windows NT/2000/XP/2003processTable.processSysCalls Not supported by Windows NT/2000/XP/2003processTable.processMinorPgFaultsNot supported by Windows NT/2000/XP/2003processTable.processNumSwaps Not supported by Windows NT/2000/XP/2003processTable.processVolCtx,InvolCtxNot supported by Windows NT/2000/XP/2003performance (except kernelperf) Not implemented in current releasekernelperf.diskWaitNum Not supported by Windows NT/2000/XP/2003kernelperf.pageWaitNum Not supported by Windows NT/2000/XP/2003kernelperf.swapActive Not supported by Windows NT/2000/XP/2003kernelperf.sleepActive Not supported by Windows NT/2000/XP/2003kernelperf.numTraps Not supported by Windows NT/2000/XP/2003kernelperf.numPageSwapIns Not supported by Windows NT/2000/XP/2003kernelperf.numPageSwapOuts Not supported by Windows NT/2000/XP/2003kernelperf.numSwapIns Not supported by Windows NT/2000/XP/2003kernelperf.numSwapOuts Not supported by Windows NT/2000/XP/2003kernelperf.numPageReclaims Not supported by Windows NT/2000/XP/2003kernelperf.pageScans Not supported by Windows NT/2000/XP/2003ipc Not supported by Windows NT/2000/XP/2003buffers.mbuf Not supported by Windows NT/2000/XP/2003buffers.strbuf Not supported by Windows NT/2000/XP/2003ioBufferCache.numBufSleeps Not supported by Windows NT/2000/XP/2003ioBufferCache.numAgeAllocs Not supported by Windows NT/2000/XP/2003ioBufferCache.numLRUAllocs Not supported by Windows NT/2000/XP/2003ioBufferCache.numBufHdrs Not supported by Windows NT/2000/XP/2003ioBufferCache.numAllocBuff Not supported by Windows NT/2000/XP/2003dnlc Not supported by Windows NT/2000/XP/2003

34


Empire Systems Management MIB (Cont.)

Object Comment

ntSystem.ntIoPageLockLimit Not supported by Windows 2003 (x64, ia64)ntSystem.ntCmdlineOptions Not supported by Windows 2003 (x64, ia64)ntSystem.ntDosMemSize Not supported by Windows 2003 (x64, ia64)ntSystem.ntWowCmdline Not supported by Windows 2003 (x64, ia64)ntSystem.ntWowSize Not supported by Windows 2003 (x64, ia64)ntSystem.ntSysBiosDate Not supported by Windows 2003 (x64)ntSystem.ntSysBiosVersion Not supported by Windows 2003 (x64, ia64)ntRegistry.ntRegistryCurrentSize Not supported by Windows NT/2000/XP/2003rpc Not supported by Windows NT/2000/XP/2003nfs Not supported by Windows NT/2000/XP/2003cpuStatsTable.cpuStatsWait Not supported by Windows NT/2000/XP/2003cpuStatsTable.cpuStatsWaitPercentNot supported by Windows NT/2000/XP/2003

35


Unsupported MIB Objects on Digital UNIX 4.0F,G/Tru64 5.1A,B


ifTable.ifEntry.ifOutQLen Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bip.ipRouteEntry.ipRouteAge Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bip.ipRouteEntry.ipRouteInfo Not implemented in current releaseegp Not implemented in current release


hrSystemInitialLoadDevice Not implemented in current releasehrSystemInitialLoadParametersNot supported by Digital UNIX 4.0F,G/Tru64 5.1A,BhrStorageAllocationFailures Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BhrDeviceID Hardware manufacturers haven’t assigned IDshrDeviceErrors If supported by the device itselfhrProcessorFrwID Manufacturers haven’t assigned IDshrPrinterTable Not implemented in current releasehrFSBootable Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BhrFSLastFullBackupDate Not implemented in current releasehrFSLastPartialBackupDate Not implemented in current releasehrSWRunID Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BhrSWInstalledID Manufacturers haven’t assigned IDs

36



Object Comment

kernelConfig.serialNumber Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BkernelConfig.romVersion Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BkernelConfig.maxInode Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bbootconf Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bstreams Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BprocessTable.processNumThreadsNot supported by Digital UNIX 4.0F,G/Tru64 5.1A,BprocessTable.processSysCalls Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bkernelperf.diskWaitNum Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bkernelperf.pageWaitNum Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bkernelperf.swapActive Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bkernelperf.sleepActive Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bkernelperf.numTraps Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bkernelperf.numPageSwapIns Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bkernelperf.numPageSwapOuts Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bmbufs.freeClusters Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bmbufs.numWaits Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BstrbufAllocTable Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BioBufferCache.numBufSleeps Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BioBufferCache.numAgeAllocs Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BioBufferCache.numLRUAllocs Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BioBufferCache.minNumBufHdrs Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BioBufferCache.numAllocBuf Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bdnlc Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,Bnt Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BdiskStatsEntry.diskStatsUtilizationNot supported by Digital UNIX 4.0F,G/Tru64 5.1A,BdiskStatsEntry.diskStatsReads Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,BdiskStatsEntry.diskStatsWrites Not supported by Digital UNIX 4.0F,G/Tru64 5.1A,B

37


Unsupported MIB Objects on Linux 2.X (x86, x64, ia64)


ifTable.ifEntry.ifType Estimated due to Linux limitationsifTable.ifEntry.ifSpeed Estimated due to Linux limitationsifTable.ifEntry.ifInOctets Not supported by Linux 2.X (x86, x64, ia64)ifTable.ifEntry.ifInNUcastPkts Not supported by Linux 2.X (x86, x64, ia64)ifTable.ifEntry.ifOutOctets Not supported by Linux 2.X (x86, x64, ia64)ifTable.ifEntry.ifOutNUcastPkts Not supported by Linux 2.X (x86, x64, ia64)ifTable.ifEntry.ifOutQLen Not supported by Linux 2.X (x86, x64, ia64)ifTable.ifEntry.ifSpecific Not supported by Linux 2.X (x86, x64, ia64)ip.ipRouteEntry.ipRouteAge Not supported by Linux 2.X (x86, x64, ia64)ip.ipRouteEntry.ipRouteInfo Not supported by Linux 2.X (x86, x64, ia64)ip.ipRoutingDiscards Not supported by Linux 2.X (x86, x64, ia64)tcp.inErrs Not supported by Linux 2.X (x86, x64, ia64)tcp.OutRsts Not supported by Linux 2.X (x86, x64, ia64)


hrSystemInitialLoadDevice Not implemented in current releasehrSystemInitialLoadParametersNot supported by Linux 2.X (x86, x64, ia64)hrStorageAllocationFailures Not supported by Linux 2.X (x86, x64, ia64)hrDeviceID Hardware manufacturers haven’t assigned IDshrDeviceErrors If supported by the device itselfhrProcessorFrwID Manufacturers haven’t assigned IDshrPrinterTable Not implemented in current releasehrPartitionTable Not supported by Linux 2.X (x86, x64, ia64)hrFSBootable Not supported by Linux 2.X (x86, x64, ia64)hrFSLastFullBackupDate Not implemented in current releasehrFSLastPartialBackupDate Not implemented in current releasehrSWRunID Not supported by Linux 2.X (x86, x64, ia64)hrSWInstalledTable Not supported by Linux 2.X (x86, x64, ia64)

38



Object Comment

kernelConfig.clockHZ Not implemented in current releasekernelConfig.maxClist Not supported by Linux 2.X (x86, x64, ia64)kernelConfig.maxMemPerProc Not supported by Linux 2.X (x86, x64, ia64)bootconf Not supported by Linux 2.X (x86, x64, ia64)streams Not supported by Linux 2.X (x86, x64, ia64)processTable.processNumThreads Not supported by Linux 2.X (x86, x64, ia64)processTable.processInBlks Not supported by Linux 2.X (x86, x64, ia64)processTable.processOutBlks Not supported by Linux 2.X (x86, x64, ia64)processTable.processMsgsSent Not supported by Linux 2.X (x86, x64, ia64)processTable.processMsgsRecv Not supported by Linux 2.X (x86, x64, ia64)processTable.processSysCalls Not supported by Linux 2.X (x86, x64, ia64)processTable.processMinorPgFlts Not supported by Linux 2.X (x86, x64, ia64)processTable.processNumSwaps Not supported by Linux 2.X (x86, x64, ia64)processTable.processVolCtx Not supported by Linux 2.X (x86, x64, ia64)processTable.processInvolCtx Not supported by Linux 2.X (x86, x64, ia64)kernelperf.diskWaitNum Not supported by Linux 2.X (x86, x64, ia64)kernelperf.pageWaitNum Not supported by Linux 2.X (x86, x64, ia64)kernelperf.swapActive Not supported by Linux 2.X (x86, x64, ia64)kernelperf.sleepActive Not supported by Linux 2.X (x86, x64, ia64)kernelperf.numTraps Not supported by Linux 2.X (x86, x64, ia64)kernelperf.numSyscalls Not supported by Linux 2.X (x86, x64, ia64)kernelperf.numSwapIns Not supported by Linux 2.X (x86, x64, ia64)kernelperf.numSwapOuts Not supported by Linux 2.X (x86, x64, ia64)kernelperf.numPageReclaims Not supported by Linux 2.X (x86, x64, ia64)kernelperf.numPageFaults Not supported by Linux 2.X (x86, x64, ia64)kernelperf.pageScans Not supported by Linux 2.X (x86, x64, ia64)ipc Not supported by Linux 2.X (x86, x64, ia64)buffers Not supported by Linux 2.X (x86, x64, ia64)dnlc Not supported by Linux 2.X (x86, x64, ia64)diskStatsEntry.diskStatsQueueLengthNot supported by Linux 2.X (x86, x64, ia64)diskStatsEntry.diskStatsServiceTimeNot supported by Linux 2.X (x86, x64, ia64)diskStatsEntry.diskStatsUtilization Not supported by Linux 2.X (x86, x64, ia64)cpuStatsTable.cpuStatsWait Not supported by Linux 2.X (x86, x64, ia64)cpuStatsTable.cpuStatsWaitPercent Not supported by Linux 2.X (x86, x64, ia64)cpuStats.cpuTotalWait Not supported by Linux 2.X (x86, x64, ia64)cpuStats.cpuTotalWaitPercent Not supported by Linux 2.X (x86, x64, ia64)nt Not supported by Linux 2.X (x86, x64, ia64)devTable.devTfiles If underlying kernel/module supports themdevTable.devFfiles If underlying kernel/module supports themdevTable.devInodeCapacity If underlying kernel/module supports themnumBreadHits Not supported by Linux 2.X (x86, x64, ia64)numBreadRequests Not supported by Linux 2.X (x86, x64, ia64)

39

CA eHealth SystemEDGEehealth-spectrum.ca.com/support/secure/pdfs/60pdfs/relnotes... · Release...

Documents

Transcript of CA eHealth SystemEDGEehealth-spectrum.ca.com/support/secure/pdfs/60pdfs/relnotes... · Release...