Tivoli Application Dependency Discovery Manager Version 7.3. Sensor Reference IBM

Transcription

1 Tivoli Application Dependency Discovery Manager Version 7.3 Sensor Reference IBM

2

3 Tivoli Application Dependency Discovery Manager Version 7.3 Sensor Reference IBM

4 Note Before using this information and the product it supports, read the information in Notices on page 475. Edition notice This edition applies to version 7, release 3 of IBM Tivoli Application Dependency Discovery Manager (product number 5724-N55) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2008, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ix Tables xi About this information xiii Conventions used in this information center... xiii Terms and definitions xiii Chapter 1. Sensor reference Overview Sensors that are enabled by default Sensors that support a non-admin discovery on Windows operating system Sensors that support script-based and asynchronous discovery Sensors that support discovery using IBM Tivoli Monitoring (old method) Sensors that support discovery using OSLC Automation Sensor setup problems Application sensors Active Directory sensor Apache sensor Model objects with associated attributes Troubleshooting the sensor Citrix 7 server sensor Chapter 2. Docker Host sensor Chapter 3. Docker Swarm Cluster sensor Chapter 4. DNS sensor Troubleshooting the sensor Chapter 5. HIS sensor Model objects with associated attributes Configuring the access list Troubleshooting the sensor Chapter 6. IBM Cluster Systems Management sensor Configuring the sensor Configuring the discovery profile Configuring the access list Chapter 7. IBM High-Availability Cluster Multi-Processing sensor Model objects with associated attributes Configuring the sensor Configuring the access list Configuring the collation.properties file entries 55 Troubleshooting the sensor Chapter 8. IBM Lotus Domino server sensor Asynchronous and script-based discovery support 58 Configuring the access list Troubleshooting the sensor Chapter 9. IBM Tivoli Monitoring Scope sensor Model objects with associated attributes Configuring the sensor Copying necessary files from the Tivoli Enterprise Portal Server to the TADDM server.. 63 Distributing the discovery target support bundle 63 Installing custom queries on the Tivoli Enterprise Portal Server Configuring the discovery profile Discovering endpoints behind firewalls Configuring the access list Uninstalling the sensor Deleting access list entries Deleting discovery profiles Uninstalling custom queries on the Tivoli Enterprise Portal Server Removing the discovery target support bundle 69 Deleting the Tivoli Enterprise Portal Server files from the TADDM server Troubleshooting the sensor Chapter 10. IBM WebSphere sensor.. 77 Asynchronous and script-based discovery support 79 Configuring the sensor Enabling JDBC driver discovery Configuring the discovery profile Configuring the access list Configuring the collation.properties file entries 87 Using the WebSphere seed sensor for z/os Preparing to run the WebSphere seed sensor.. 88 Running the WebSphere seed sensor Troubleshooting the sensor Chapter 11. IBM WebSphere extreme Scale cache sensor Model objects with associated attributes Configuring the sensor Chapter 12. IBM WebSphere Message Broker sensor Configuring the sensor Configuring the discovery profile Configuring the access list Configuring the collation.properties file entries 102 Troubleshooting the sensor Copyright IBM Corp. 2008, 2016 iii

6 Chapter 13. IBM WebSphere MQ Server sensor Asynchronous and script-based discovery support 105 Configuring the sensor Configuring the access list Configuring the collation.properties file entries 106 Troubleshooting the sensor Chapter 14. iplanet server sensor Chapter 15. JBoss server sensor Configuring the sensor Configuring the access list Configuring the collation.properties file entries 112 Troubleshooting the sensor Chapter 16. JBoss Application Server 7 sensor Configuring the sensor Configuring the collation.properties file entries Configuring for asynchronous discovery Troubleshooting the sensor Chapter 17. Kernel-based virtual machine sensor Configuring the sensor Configuring the collation.properties file Configuring the discovery profile Chapter 18. Microsoft Cluster sensor 121 Model objects with associated attributes Configuring the sensor Configuring the access list Configuring the collation.properties file entries 123 Troubleshooting the sensor Chapter 19. Microsoft Exchange sensor Model objects with associated attributes Configuring the sensor Configuring the access list Configuring the collation.properties file entries 134 Troubleshooting the sensor Chapter 20. Microsoft Exchange 2003 sensor Configuring the sensor Configuring the access list Configuring the collation.properties file entries 138 Troubleshooting the sensor Chapter 21. Microsoft HyperV sensor 143 Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Chapter 22. Microsoft IIS Web server sensor Configuring the sensor Configuring the access list Configuring the discovery profile Configuring for a non-admin IIS discovery Differences between IISServerSensor and IIsWebServiceSensor Troubleshooting the sensor Chapter 23. NFS sensor Chapter 24. Oracle Application Server sensor Configuring the sensor Configuring the access list Configuring the collation.properties file entries 157 Troubleshooting the sensor Chapter 25. Oracle VM sensor Configuring the Oracle VM sensor Configuring the access list Configuring the discovery profile Model objects with associated attributes Chapter 26. SAP CCMS server sensor 165 Configuring the sensor Installing the SAP Java Connector (JCo) libraries 165 Configuring the access list Configuring the collation.properties file entries 167 Troubleshooting the sensor Chapter 27. SAP SLD server sensor 171 Model objects with associated attributes Configuring the sensor Configuring the access list Configuring the collation.properties file entries 174 Troubleshooting the sensor Chapter 28. SMB server sensor Troubleshooting the sensor Chapter 29. SMS server sensor Configuring the collation.properties file entries Chapter 30. SysImager sensor Configuring the sensor Configuring the discovery profile Configuring the access list Chapter 31. Veritas cluster sensor Configuring the sensor Configuring the discovery profile Configuring the access list Configuring the collation.properties file entries 184 Troubleshooting the sensor iv Application Dependency Discovery Manager: Sensors

7 Chapter 32. VMware Virtual Center server sensor Model objects with associated attributes Configuring the sensor Configuring non-administrator users to run the sensor Configuring the discovery profile Configuring the access list Troubleshooting the sensor Chapter 33. WebLogic sensor Configuring the sensor Copying JAR files to the TADDM server Creating a wlfullclient.jar for the WebLogic sensor Editing the WeblogicVersionSensor.xml file Editing the WeblogicSensor2.xml file Copying JAR files to discover older versions of WebLogic application servers Configuring the access list Configuring the collation.properties file entries 203 Troubleshooting the sensor Chapter 34. WebLogic SSH sensor 209 Resources that the sensor discovers Asynchronous and script-based discovery support 213 Configuring the sensor Configuring the collation.properties file entries 215 Troubleshooting the sensor Chapter 35. Database sensors IBM DB2 sensor Asynchronous and script-based discovery support Configuring the sensor Troubleshooting the sensor IBM Informix sensor Model objects with associated attributes Configuring the access list Troubleshooting the sensor Microsoft SQL Server sensor Configuring the sensor Troubleshooting the sensor Oracle sensor Asynchronous and script-based discovery support Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Sybase sensor Model objects with associated attributes Configuring the access list Configuring the discovery profile Sybase IQ sensor Configuring the access list Chapter 36. Generic sensors Anchor sensor Configuring the sensor Asynchronous discovery sensor Troubleshooting the sensor Asynchronous discovery ping sensor Custom application server sensor Custom MIB2 computer system sensor Custom template sensor Configuring the sensor Troubleshooting the sensor Generic computer system sensor Generic server sensor Asynchronous and script-based discovery support Configuring the collation.properties file entries 259 Troubleshooting the sensor IBM Tivoli Utilization sensor Asynchronous and script-based discovery support Model objects with associated attributes Configuring the sensor Troubleshooting the sensor IP device sensor Configuring the collation.properties file entries 268 IP interface sensor Ping sensor Configuring the sensor Troubleshooting the sensor Port sensor Troubleshooting the sensor Session sensor Troubleshooting Configuring the collation.properties file entries 275 Solaris zones generic sensor Troubleshooting the sensor Stack Scan sensor Configuring the sensor Troubleshooting the sensor WPAR generic sensor zenterprise sensor Sharing a common ECC instance among multiple applications Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Chapter 37. Network sensors Overview of SNMP sensors Calling sequence for SNMP sensors SNMP MIB walking and debugging SNMP sensors Maintaining SNMP computer system templates and configuration files SNMP sensors properties Alteon port sensor Configuring the access list Alteon SNMP sensor Configuring the access list Alteon VLAN sensor Configuring the access list BIG-IP port sensor Configuring the access list BIG-IP SNMP sensor Configuring the access list Contents v

8 BIG-IP VLAN sensor Configuring the access list Bridge SNMP sensor Configuring the access list Configuring the collation.properties file entries Bridge SNMP 2 sensor Configuring the access list Configuring the collation.properties file entries Check Point sensor Configuring the collation.properties file entries 312 Troubleshooting the sensor Check Point SNMP sensor Configuring the access list Cisco Adaptive Security Appliance sensor Configuring the sensor Cisco Discovery Protocol sensor Configuring the access list Troubleshooting the sensor Cisco IOS sensor Configuring the sensor Cisco port sensor Configuring the access list Cisco UCS SNMP sensor Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Cisco VLAN sensor Configuring the access list CiscoWorks sensor Model objects with associated attributes Configuring the access list Troubleshooting the sensor Entity MIB sensor Configuring the access list Extreme VLAN sensor Configuring the access list IBM BladeCenter SNMP sensor Configuring the sensor Troubleshooting the sensor LAN Manager SNMP sensor Configuring the access list LDAP sensor Configuring the sensor Troubleshooting the sensor Link Layer Discovery Protocol sensor NetScreen SNMP sensor Configuring the access list Nokia SNMP sensor Configuring the access list PIX sensor Configuring the access list Configuring the collation.properties file entries 338 SNMP Light sensor Configuring the access list SNMP MIB2 sensor Configuring the sensor Troubleshooting the sensor Chapter 38. Operating system sensors 345 Citrix XenServer sensor Troubleshooting the sensor DataPower sensor Configuring the sensor Troubleshooting the sensor FreeBSD computer system sensor Asynchronous and script-based discovery support Model objects with associated attributes Configuring the sensor Troubleshooting the sensor HP BladeSystem SNMP sensor Configuring the sensor Troubleshooting the sensor HP NonStop computer system sensor Asynchronous discovery support Troubleshooting the sensor HP-UX computer system sensor Model objects with associated attributes Configuring the sensor Troubleshooting the sensor IBM AIX computer system sensor Asynchronous and script-based discovery support Model objects with associated attributes Configuring the sensor Troubleshooting the sensor IBM Hardware Management Console sensor Model objects with associated attributes Configuring the sensor IBM Integrated Virtualization Manager sensor Configuring the sensor IBM i computer system sensor Configuring the access list IPSO computer system sensor Configuring the access list Linux computer system sensor Asynchronous and script-based discovery support Model objects with associated attributes Configuring the sensor Troubleshooting the sensor OpenVMS computer system sensor Configuring the access list Troubleshooting the sensor Solaris computer system sensor Asynchronous and script-based discovery support Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Sun Sparc Virtualization sensor Model objects with associated attributes Sun Fire SysControl sensor Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Tru64 computer system sensor Configuring the sensor Troubleshooting the sensor vi Application Dependency Discovery Manager: Sensors

9 VMware ESX computer system sensor Configuring the sensor Troubleshooting the sensor VMware ESXi computer system sensor Configuring the sensor Troubleshooting the sensor Windows computer system sensor Asynchronous and script-based discovery support Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Chapter 39. Storage sensors EMC Storage Scope sensor Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Fibre Channel switch sensor Model objects with associated attributes Configuring the sensor Troubleshooting the sensor Host resources sensor Configuring the access list Host storage sensor Model objects with associated attributes Configuring the sensor Troubleshooting the sensor IBM Tivoli Storage Productivity Center sensor Model objects with associated attributes Configuring the sensor Troubleshooting the sensor NetApp sensor Configuring the access list Snap Drive sensor Configuring the access list Storage sensor Configuring the sensor Troubleshooting the sensor SVC Storage sensor Model objects with associated attributes Configuring the access list Veritas Storage Foundation sensor Configuring the collation.properties file entries 470 Troubleshooting the sensor XIV Storage sensor Configuring the sensor Model objects with associated attributes Troubleshooting the sensor Notices Trademarks Contents vii

10 viii Application Dependency Discovery Manager: Sensors

11 Figures 1. Calling sequence for SNMP Light sensor and SNMP MIB2 sensor Calling sequence for SNMP sensors, starting after the SNMP Light sensor or the SNMP MIB2 sensor is called Copyright IBM Corp. 2008, 2016 ix

12 x Application Dependency Discovery Manager: Sensors

13 Tables 1. Sensors that are enabled by default for a Level 1 discovery Sensors that are enabled by default for a Level 2 discovery Sensors that are enabled by default for a Level 3 discovery Sensors that are enabled by default for a utilization discovery Application sensors that support a non-admin discovery on Windows operating system Database sensors that support a non-admin discovery on Windows operating system Generic sensors that support a non-admin discovery on Windows operating system Operating system sensors that support a non-admin discovery on Windows operating system List of script-based sensors Sensors that support discovery using IBM Tivoli Monitoring Sensors that support discovery using OSLC Automation Package names of the SAP JCo 2.x library files Required WebLogic JAR files Configuration parameters Foundry OID mapping example Level 2 bridge topology data SNMP V3 credential mapping SNMP V3 credential mapping Copyright IBM Corp. 2008, 2016 xi

14 xii Application Dependency Discovery Manager: Sensors

15 About this information The purpose of this PDF document version is to provide the related topics from the information center in a printable format. Conventions used in this information center Terms and definitions In the IBM Tivoli Application Dependency Discovery Manager (TADDM) documentation certain conventions are used. They are used to refer to the operating system-dependent variables and paths, the COLLATION_HOME directory, and the location of the collation.properties file, which is referenced throughout the TADDM documentation, including in the messages. Operating system-dependent variables and paths In this information center, the UNIX conventions are used for specifying environment variables and for directory notation. When using the Windows command line, replace $variable with %variable% for environment variables, and replace each forward slash (/) with a backslash (\) in directory paths. If you are using the bash shell on a Windows system, you can use the UNIX conventions. COLLATION_HOME directory TADDM root directory is also referred to as the COLLATION_HOME directory. On operating systems such as AIX or Linux, the default location for installing TADDM is the /opt/ibm/taddm directory. Therefore, in this case, the $COLLATION_HOME directory is /opt/ibm/taddm/dist. On Windows operating systems, the default location for installing TADDM is the c:\ibm\taddm directory. Therefore, in this case, the %COLLATION_HOME% directory is c:\ibm\taddm\dist. Location of collation.properties file The collation.properties file contains TADDM server properties and includes comments about each of the properties. It is located in the $COLLATION_HOME/etc directory. Refer to the following list of terms and definitions to learn about important concepts in the IBM Tivoli Application Dependency Discovery Manager (TADDM). access collection A collection that is used to control the access to configuration items and permissions to modify configuration items. You can create access collections only when data-level security is enabled. Copyright IBM Corp. 2008, 2016 xiii

16 asynchronous discovery In TADDM, the running of a discovery script on a target system to discover systems that cannot be accessed directly by the TADDM server. Because this discovery is performed manually, and separately from a typical credentialed discovery, it is called asynchronous. business application A collection of components that provides a business functionality that you can use internally, externally, or with other business applications. CI See configuration item. collection In TADDM, a group of configuration items. configuration item (CI) A component of IT infrastructure that is under the control of configuration management and is therefore subject to formal change control. Each CI in the TADDM database has a persistent object and change history associated with it. Examples of a CI are an operating system, an L2 interface, and a database buffer pool size. credentialed discovery TADDM sensor scanning that discovers detailed information about the following items: v Each operating system in the runtime environment. This scanning is also known as Level 2 discovery, and it requires operating system credentials. v The application infrastructure, deployed software components, physical servers, network devices, virtual systems, and host data that are used in the runtime environment. This scanning is also known as Level 3 discovery, and it requires both operating system credentials and application credentials. credential-less discovery TADDM sensor scanning that discovers basic information about the active computer systems in the runtime environment. This scanning is also known as Level 1 discovery, and it requires no credentials. Data Management Portal The TADDM web-based user interface for viewing and manipulating the data in a TADDM database. This user interface is applicable to a domain server deployment, to a synchronization server deployment, and to each storage server in a streaming server deployment. The user interface is very similar in all deployments, although in a synchronization server deployment, it has a few additional functions for adding and synchronizing domains. discover worker thread In TADDM, a thread that runs sensors. Discovery Management Console The TADDM client user interface for managing discoveries. This console is also known as the Product Console. It is applicable to a domain server deployment and to discovery servers in a streaming server deployment. The function of the console is the same in both of these deployments. discovery server A TADDM server that runs sensors in a streaming server deployment but does not have its own database. xiv Application Dependency Discovery Manager: Sensors

17 domain In TADDM, a logical subset of the infrastructure of a company or other organization. Domains can delineate organizational, functional, or geographical boundaries. domain server A TADDM server that runs sensors in a domain server deployment and has its own database. domain server deployment A TADDM deployment with one domain server. A domain server deployment can be part of a synchronization server deployment. In a domain server deployment, the following TADDM server property must be set to the following value: com.collation.cmdbmode=domain launch in context The concept of moving seamlessly from one Tivoli product UI to another Tivoli product UI (either in a different console or in the same console or portal interface) with single sign-on and with the target UI in position at the proper point for users to continue with their task. Level 1 discovery TADDM sensor scanning that discovers basic information about the active computer systems in the runtime environment. This scanning is also known as credential-less discovery because it requires no credentials. It uses the Stack Scan sensor and the IBM Tivoli Monitoring Scope sensor. Level 1 discovery is very shallow. It collects only the host name, operating system name, IP address, fully qualified domain name, and Media Access Control (MAC) address of each discovered interface. Also, the MAC address discovery is limited to Linux on System z and Windows systems. Level 1 discovery does not discover subnets. For any discovered IP interfaces that do not belong to an existing subnet that is discovered during Level 2 or Level 3 discovery, new subnets are created based on the value of the com.collation.ipnetworkassignmentagent.defaultnetmask property in the collation.properties file. Level 2 discovery TADDM sensor scanning that discovers detailed information about each operating system in the runtime environment. This scanning is also known as credentialed discovery, and it requires operating system credentials. Level 2 discovery collects application names and the operating system names and port numbers that are associated with each running application. If an application has established a TCP/IP connection to another application, this information is collected as a dependency. Level 3 discovery TADDM sensor scanning that discovers detailed information about the application infrastructure, deployed software components, physical servers, network devices, virtual systems, and host data that are used in the runtime environment. This scanning is also known as credentialed discovery, and it requires both operating system credentials and application credentials. multitenancy In TADDM, the use by a service provider or IT vendor of one TADDM installation to discover multiple customer environments. Also, the service provider or IT vendor can see the data from all customer environments, but within each customer environment, only the data that is specific to the About this information xv

18 respective customer can be displayed in the user interface or viewed in reports within that customer environment. Product Console See Discovery Management Console. script-based discovery In TADDM, the use, in a credentialed discovery, of the same sensor scripts that sensors provide in support of asynchronous discovery. SE See server equivalent. server equivalent (SE) A representative unit of IT infrastructure, defined as a computer system (with standard configurations, operating systems, network interfaces, and storage interfaces) with installed server software (such as a database, a web server, or an application server). The concept of a server equivalent also includes the network, storage, and other subsystems that provide services to the optimal functioning of the server. A server equivalent depends on the operating system: Operating system Windows 500 AIX 1000 Linux 1000 HP-UX 500 Network devices 1000 Approximate number of CIs storage server A TADDM server that processes discovery data that is received from the discovery servers and stores it in the TADDM database. The primary storage server both coordinates the discovery servers and all other storage servers and serves as a storage server. All storage servers that are not the primary are called secondary storage servers. streaming server deployment A TADDM deployment with a primary storage server and at least one discovery server. This type of deployment can also include one or more optional secondary storage servers. The primary storage server and secondary storage servers share a database. The discovery servers have no database. In this type of deployment, discovery data flows in parallel from multiple discovery servers to the TADDM database. In a streaming server deployment, the following TADDM server property must be set to one of the following values: v com.collation.taddm.mode=discoveryserver v com.collation.taddm.mode=storageserver For all servers except for the primary storage server, the following properties (for the host name and port number of the primary storage server) must also be set: v com.collation.primarystorageserver.host v com.collation.primarystorageserver.port xvi Application Dependency Discovery Manager: Sensors

19 If the com.collation.taddm.mode property is set, the com.collation.cmdbmode property must not be set or must be commented out. synchronization server A TADDM server that synchronizes discovery data from all domain servers in the enterprise and has its own database. This server does not discover data directly. synchronization server deployment A TADDM deployment with a synchronization server and two or more domain server deployments, each of which has its own local database. In this type of deployment, the synchronization server copies discovery data from multiple domain servers one domain at a time in a batched synchronization process. In a synchronization server deployment, the following TADDM server property must be set to the following value: com.collation.cmdbmode=enterprise This type of deployment is obsolete. Therefore, in a new TADDM deployment where more than one server is needed, use the streaming server deployment. A synchronization server can be converted to become a primary storage server for a streaming server deployment. TADDM database In TADDM, the database where configuration data, dependencies, and change history are stored. Each TADDM server, except for discovery servers and secondary storage servers, has its own database. Discovery servers have no database. Storage servers share the database of the primary storage server. TADDM server A generic term that can represent any of the following terms: v domain server in a domain server deployment v synchronization server in a synchronization server deployment v discovery server in a streaming server deployment v storage server (including the primary storage server) in a streaming server deployment target system In the TADDM discovery process, the system to be discovered. utilization discovery TADDM sensor scanning that discovers utilization information for the host system. A utilization discovery requires operating system credentials. About this information xvii

20 xviii Application Dependency Discovery Manager: Sensors

21 Chapter 1. Sensor reference Overview For each sensor, this reference includes overview information, and if applicable for the respective sensor, also includes configuration and troubleshooting information. For some sensors, information about the attributes that are associated with the model objects is also included. Where attributes are included, the attributes are available in the IBM Tivoli Common Data Model (CDM) but are not necessarily shown in the IBM Tivoli Application Dependency Discovery Manager (TADDM) UI. Sensors and supported target systems For the list of the TADDM sensors and the supported versions of target systems that they can discover, see Sensors and supported target systems in the TADDM Wiki. Discovery process overview The TADDM Administrator's Guide contains an overview of the discovery process, including information about how a sensor discovers configuration items (CIs) and how an application sensor is started. Late-breaking updates For late-breaking updates about TADDM sensor support issues, see Release notes in the TADDM documentation. Sensor extensions If you want to discover additional software that is not discovered by TADDM by default, you can create custom server templates. You can create your own templates or use predefined templates. For details, see the Creating and managing custom server templates topic in the TADDM User's Guide. Sensors that are enabled by default These listings indicate which sensors are enabled by default in each of the following four discovery profiles: Level 1, Level 2, Level 3, and utilization. For more information about levels of discovery, see the Levels of discovery topic in the TADDM Administrator's Guide. Level 1 discovery profile These sensors are enabled by default in a Level 1 discovery profile. Table 1 on page 2 lists the sensors that are enabled by default for a Level 1 discovery. Sensors are listed in the order in which they are shown in the Discovery Profiles window in the TADDM UI. Copyright IBM Corp. 2008,

22 Table 1. Sensors that are enabled by default for a Level 1 discovery Sensor Anchor sensor on page 249 SNMP Light sensor on page 338 Stack Scan sensor on page 277 Sensor name that is used in the UI and logs AnchorSensor SnmpLightSensor StackScanSensor Level 2 discovery profile These sensors are enabled by default in a Level 2 discovery profile. Table 2 lists the sensors that are enabled by default for a Level 2 discovery. Sensors are listed in the order in which they are shown in the Discovery Profiles window in the TADDM UI. Table 2. Sensors that are enabled by default for a Level 2 discovery Sensor Alteon port sensor on page 300 Alteon SNMP sensor on page 301 Alteon VLAN sensor on page 302 Anchor sensor on page 249 Asynchronous discovery sensor on page 250 BIG-IP port sensor on page 303 BIG-IP SNMP sensor on page 304 BIG-IP VLAN sensor on page 306 Bridge SNMP sensor on page 307 Bridge SNMP 2 sensor on page 310 Check Point SNMP sensor on page 313 Cisco Discovery Protocol sensor on page 315 Cisco IOS sensor on page 316 Cisco port sensor on page 317 Cisco VLAN sensor on page 322 Custom application server sensor on page 252 Custom MIB2 computer system sensor on page 253 Entity MIB sensor on page 324 Extreme VLAN sensor on page 326 FreeBSD computer system sensor on page 349 Generic computer system sensor on page 257 Generic server sensor on page 257 Sensor name that is used in the UI and logs AlteonPortSensor AlteonSnmpSensor AlteonVlanSensor AnchorSensor ASDSensor BigIPPortSensor BigIPSnmpSensor BigIPVlanSensor BridgeSnmpSensor BridgeSnmpSensor2 CheckpointSnmpSensor CdpSensor CiscoIOSSensor CiscoPortSensor CiscoVlanSensor CustomAppServerSensor CustomMib2ComputerSystemSensor EntityMIBSensor ExtremeVlanSensor FreeBSDComputerSystemSensor GenericComputerSystemSensor GenericServerSensor 2 Application Dependency Discovery Manager: Sensors

23 Table 2. Sensors that are enabled by default for a Level 2 discovery (continued) Sensor IBM AIX computer system sensor on page 362 IBM BladeCenter SNMP sensor on page 327 IBM Hardware Management Console sensor on page 368 IBM i computer system sensor on page 377 IBM Integrated Virtualization Manager sensor on page 375 Host resources sensor on page 441 HP BladeSystem SNMP sensor on page 353 HP NonStop computer system sensor on page 355 HP-UX computer system sensor on page 356 IP device sensor on page 268 IPSO computer system sensor on page 378 LAN Manager SNMP sensor on page 330 Linux computer system sensor on page 379 NetApp sensor on page 463 NetScreen SNMP sensor on page 334 Nokia SNMP sensor on page 336 OpenVMS computer system sensor on page 387 Ping sensor on page 269 Port sensor on page 272 Session sensor on page 272 Snap Drive sensor on page 464 SNMP MIB2 sensor on page 340 Solaris computer system sensor on page 389 Solaris zones generic sensor on page 276 Sun Fire SysControl sensor on page 397 Fix Pack 2 Fix Pack 1 Sun Sparc Virtualization sensor SVC Storage sensor Tru64 computer system sensor on page 400 VMware ESX computer system sensor on page 402 Sensor name that is used in the UI and logs AixComputerSystemSensor BladeCenterSnmpSensor HmcSensor I5OSComputerSystemSensor IvmSensor HostResourcesSensor HPBladeSystemSnmpSensor HPNonStopComputerSystemSensor HpUxComputerSystemSensor IpDeviceSensor IPSOComputerSystemSensor LanManagerSnmpSensor LinuxComputerSystemSensor NetAppSensor NetscreenSnmpSensor NokiaSnmpSensor OpenVmsComputerSystemSensor PingSensor PortSensor SessionSensor SnapDriveSensor SnmpMib2Sensor SunSparcComputerSystemSensor ZonesGenericSensor SysControlSensor SunSparcVirtualizationSensor SVCStorageSensor Tru64ComputerSystemSensor VmwareComputerSystemSensor Chapter 1. Sensor reference 3

24 Table 2. Sensors that are enabled by default for a Level 2 discovery (continued) Sensor VMware ESXi computer system sensor on page 408 Windows computer system sensor on page 411 WPAR generic sensor on page 285 Sensor name that is used in the UI and logs VmwareEsxiComputerSystemSensor WindowsComputerSystemSensor WparGenericSensor Fix Pack 1 XIV Storage sensor XIVStorageSensor zenterprise sensor on page 286 ZEnterpriseSensor Level 3 discovery profile These sensors are enabled by default in a Level 3 discovery profile. Table 3 lists the sensors that are enabled by default for a Level 3 discovery. Sensors are listed in the order in which they are shown in the Discovery Profiles window in the TADDM UI. Table 3. Sensors that are enabled by default for a Level 3 discovery Sensor Active Directory sensor on page 16 Alteon port sensor on page 300 Alteon SNMP sensor on page 301 Alteon VLAN sensor on page 302 Anchor sensor on page 249 Apache sensor on page 18 Asynchronous discovery sensor on page 250 BIG-IP port sensor on page 303 BIG-IP SNMP sensor on page 304 BIG-IP VLAN sensor on page 306 Bridge SNMP sensor on page 307 Bridge SNMP 2 sensor on page 310 Check Point sensor on page 312 Check Point SNMP sensor on page 313 Cisco Adaptive Security Appliance sensor on page 314 Cisco Discovery Protocol sensor on page 315 Cisco IOS sensor on page 316 Cisco port sensor on page 317 Sensor name that is used in the UI and logs ActiveDirectorySensor AlteonPortSensor AlteonSnmpSensor AlteonVlanSensor AnchorSensor ApacheServerSensor ASDSensor BigIPPortSensor BigIPSnmpSensor BigIPVlanSensor BridgeSnmpSensor BridgeSnmpSensor2 CheckpointSensor CheckpointSnmpSensor v ASASensor v CiscoApplianceVersionSensor CdpSensor CiscoIOSSensor CiscoPortSensor Fix Pack 2 page 318 Cisco UCS SNMP sensor on CiscoUCSSensor Cisco VLAN sensor on page 322 CiscoVlanSensor 4 Application Dependency Discovery Manager: Sensors

25 Table 3. Sensors that are enabled by default for a Level 3 discovery (continued) Sensor CiscoWorks sensor on page 323 Sensor name that is used in the UI and logs v CiscoWorks405FileUDS v CiscoWorks405UDS v CiscoWorksFileUDS v CiscoWorksSensor v CiscoWorksUDS on page 20 CitrixServerSensor Citrix XenServer sensor on page 345 Custom application server sensor on page 252 Custom MIB2 computer system sensor on page 253 Chapter 4, DNS sensor, on page 41 EMC Storage Scope sensor on page 433 Entity MIB sensor on page 324 Extreme VLAN sensor on page 326 FreeBSD computer system sensor on page 349 Generic computer system sensor on page 257 Generic server sensor on page 257 Chapter 5, HIS sensor, on page 43 Host resources sensor on page 441 HP BladeSystem SNMP sensor on page 353 HP NonStop computer system sensor on page 355 HP-UX computer system sensor on page 356 IBM AIX computer system sensor on page 362 IBM BladeCenter SNMP sensor on page 327 IBM DB2 sensor on page 219 IBM Hardware Management Console sensor on page 368 Chapter 7, IBM High-Availability Cluster Multi-Processing sensor, on page 53 IBM i computer system sensor on page 377 XenServerSensor CustomAppServerSensor CustomMib2ComputerSystemSensor DnsSensor v EMCStorageScopeSensor v EMCStorageScopeDetailSensor EntityMIBSensor ExtremeVlanSensor FreeBSDComputerSystemSensor GenericComputerSystemSensor GenericServerSensor HISServerSensor HostResourcesSensor HPBladeSystemSnmpSensor HPNonStopComputerSystemSensor HpUxComputerSystemSensor AixComputerSystemSensor BladeCenterSnmpSensor v Db2Sensor v Db2WindowsSensor HmcSensor HACMPSensor IBM Informix sensor on page 224 Informix I5OSComputerSystemSensor Chapter 1. Sensor reference 5

26 Table 3. Sensors that are enabled by default for a Level 3 discovery (continued) Sensor IBM Integrated Virtualization Manager sensor on page 375 Chapter 8, IBM Lotus Domino server sensor, on page 57 IBM Tivoli Storage Productivity Center sensor on page 450 Chapter 11, IBM WebSphere extreme Scale cache sensor, on page 99 Chapter 12, IBM WebSphere Message Broker sensor, on page 101 Chapter 13, IBM WebSphere MQ Server sensor, on page 105 Chapter 10, IBM WebSphere sensor, on page 77 IP device sensor on page 268 Chapter 14, iplanet server sensor, on page 109 IPSO computer system sensor on page 378 Chapter 16, JBoss Application Server 7 sensor, on page 115 Chapter 15, JBoss server sensor, on page 111 Chapter 17, Kernel-based virtual machine sensor, on page 119 LAN Manager SNMP sensor on page 330 LDAP sensor on page 331 Linux computer system sensor on page 379 Chapter 18, Microsoft Cluster sensor, on page 121 Chapter 20, Microsoft Exchange 2003 sensor, on page 137 Chapter 19, Microsoft Exchange sensor, on page 125 Chapter 21, Microsoft HyperV sensor, on page 143 Chapter 22, Microsoft IIS Web server sensor, on page 145 Microsoft SQL Server sensor on page 227 NetApp sensor on page 463 NetScreen SNMP sensor on page 334 Sensor name that is used in the UI and logs IvmSensor v DominoDomainSensor v DominoServerDetailSensor v DominoInitialSensor TPCStorageSensor WebSphereXSCacheSensor MBServerSensor MQServerSensor v WebSphereCellSensor v WebSphereNodeSensor v WebSphereVersionSensor IpDeviceSensor IPlanetServerSensor IPSOComputerSystemSensor JBoss7Sensor v JBossSensor v JBossVersionSensor KvmSensor LanManagerSnmpSensor LdapSensor LinuxComputerSystemSensor MSClusterSensor Exchange2003Sensor ExchangeSensor Microsoft HyperV Sensor v IISWebServiceSensor v IISServerSensor SqlServerSensor NetAppSensor NetscreenSnmpSensor 6 Application Dependency Discovery Manager: Sensors

27 Table 3. Sensors that are enabled by default for a Level 3 discovery (continued) Sensor Chapter 23, NFS sensor, on page 153 Nokia SNMP sensor on page 336 OpenVMS computer system sensor on page 387 Chapter 24, Oracle Application Server sensor, on page 155 Oracle sensor on page 232 Ping sensor on page 269 PIX sensor on page 337 Port sensor on page 272 Chapter 26, SAP CCMS server sensor, on page 165 Chapter 27, SAP SLD server sensor, on page 171 Session sensor on page 272 Chapter 28, SMB server sensor, on page 177 Chapter 29, SMS server sensor, on page 179 Snap Drive sensor on page 464 SNMP MIB2 sensor on page 340 Solaris computer system sensor on page 389 Solaris zones generic sensor on page 276 Storage sensor on page 465 Sybase IQ sensor on page 246 Sybase sensor on page 239 Sun Fire SysControl sensor on page 397 Fix Pack 2 Fix Pack 1 Sun Sparc Virtualization sensor SVC Storage sensor Tru64 computer system sensor on page 400 Chapter 31, Veritas cluster sensor, on page 183 Veritas Storage Foundation sensor on page 469 VMware ESX computer system sensor on page 402 VMware ESXi computer system sensor on page 408 Chapter 32, VMware Virtual Center server sensor, on page 187 Sensor name that is used in the UI and logs NFSServerSensor NokiaSnmpSensor OpenVmsComputerSystemSensor v OracleAppOpmnSensor v OracleAppSensor OracleSensor PingSensor PixSensor PortSensor CCMSServerSensor SLDServerSensor SessionSensor SMBServerSensor SMSServerSensor SnapDriveSensor SnmpMib2Sensor SunSparcComputerSystemSensor ZonesGenericSensor StorageSensor SybaseIQSensor SybaseSensor SysControlSensor SunSparcVirtualizationSensor SVCStorageSensor Tru64ComputerSystemSensor VeritasClusterSensor VeritasStorageSensor VmwareComputerSystemSensor VmwareEsxiComputerSystemSensor VirtualCenterSensor Chapter 1. Sensor reference 7

28 Table 3. Sensors that are enabled by default for a Level 3 discovery (continued) Sensor Chapter 34, WebLogic SSH sensor, on page 209 Windows computer system sensor on page 411 WPAR generic sensor on page 285 Fix Pack 1 XIV Storage sensor zenterprise sensor on page 286 Sensor name that is used in the UI and logs v WeblogicLauncherSensor v WeblogicApplicationSensor v WeblogicDomainSensor v WeblogicServerSensor WindowsComputerSystemSensor WparGenericSensor XIVStorageSensor ZEnterpriseSensor Utilization discovery profile These sensors are enabled by default in a Utilization discovery profile. Table 4 lists the sensors that are enabled by default for a utilization discovery. Sensors are listed in the order in which they are shown in the Discovery Profiles window in the TADDM UI. Table 4. Sensors that are enabled by default for a utilization discovery Sensor Anchor sensor on page 249 IBM Tivoli Utilization sensor on page 261 Ping sensor on page 269 Port sensor on page 272 Session sensor on page 272 Sensor name that is used in the UI and logs AnchorSensor OperatingSystemUtilizationSensor PingSensor PortSensor SessionSensor Sensors that support a non-admin discovery on Windows operating system These sensors support discovery on the Windows operating system without providing user credentials with the administrator role. The following sensors now support discovery on Windows without providing user credentials with the administrator role: Application sensors Table 5. Application sensors that support a non-admin discovery on Windows operating system. Sensor Chapter 4, DNS sensor, on page 41 Chapter 23, NFS sensor, on page 153 Chapter 28, SMB server sensor, on page 177 Sensor name that is used in the UI and logs DnsSensor NFSServerSensor SMBServerSensor 8 Application Dependency Discovery Manager: Sensors

29 Database sensors Table 6. Database sensors that support a non-admin discovery on Windows operating system. Sensor Microsoft SQL Server sensor on page 227 Sensor name that is used in the UI and logs SqlServerSensor Generic sensors Table 7. Generic sensors that support a non-admin discovery on Windows operating system. Sensor Custom application server sensor on page 252 (with restrictions) Generic computer system sensor on page 257 Generic server sensor on page 257 (with restrictions) Ping sensor on page 269 Port sensor on page 272 Session sensor on page 272 (with restrictions) Sensor name that is used in the UI and logs CustomAppServerSensor GenericComputerSystemSensor GenericServerSensor PingSensor PortSensor SessionSensor Operating system sensors Table 8. Operating system sensors that support a non-admin discovery on Windows operating system. Sensor Windows computer system sensor on page 411 Sensor name that is used in the UI and logs WindowsComputerSystemSensor Restrictions: v Session sensor does not support automatic deployment of TADDM WMI provider files. See Copying the TaddmWmi files on page 422. v Generic server sensor does not discover runtime process command-line arguments. Therefore, the Custom application server sensor does not start for the templates that are based on the Argument type conditions. Also, any application sensors that use such templates might not start. A user with valid credentials and access rights still must be provided. The rest of the application sensors still require the user to have an administrator role for successful discovery. Note: Windows User Access Control (UAC) settings do not affect non-admin discovery because they cannot be disabled for standard users. Chapter 1. Sensor reference 9

30 Configuring the sensors to run a non-admin discovery To configure the sensors to run a non-admin discovery on the Windows operating system, see the Configuring for a non-admin Windows discovery on page 420 topic. Sensors that support script-based and asynchronous discovery Some sensors can be run as script-based sensors. These sensors are more apparent, which means that all commands that the sensor uses are in one script, which you can view. Script-based sensors also support asynchronous discovery. The following table lists all script-based sensors, and the operating systems, on which they are supported. The Asynchronous discovery sensor on page 250 is required for asynchronous discovery. See also the Configuring for asynchronous discovery topic in the TADDM Administrator's Guide. Notes: v Some of the following sensors are script-based by default, but some of them must be configured for script-based discovery. See the Configuring for script-based discovery topic in the TADDM Administrator's Guide. v If the target computer system is running the Solaris operating system, script-based discovery might not work if SunSSH 1.0 is used. Table 9. List of script-based sensors.. Sensor Apache sensor on page 18 Asynchronous discovery sensor on page 250 Citrix XenServer sensor on page 345 FreeBSD computer system sensor on page 349 Generic server sensor on page 257 Sensor name that is used in the UI and logs ApacheServerSensor ASDSensor The operating systems, on which the sensor is supported v AIX v Linux v Solaris v AIX v FreeBSD v Linux v HP NonStop v Solaris v Windows Scriptbased by default No Yes XenServerSensor v Linux Yes FreeBSDComputer SystemSensor GenericServerSensor v FreeBSD v AIX v Linux v Solaris v Windows No No 10 Application Dependency Discovery Manager: Sensors