Software Vital Product Data

This topic provides an overview of the software VPD collected by the one-button data collection utility.

This section describes the software vital product data that is collected by the one-button data collection utility.

Engine

You can collect information about the software running on an engine in the cluster, such as the following:

Table 1. Engine software VPD
Software area Component VPD collected
Operating system Machine Name and version.
Operating system Version, build information, and installation date.
Processes Owner, ID, binary file, status, runtime parameters, and environment variables. Additional details as well.
System log files Collect in their entirety.
Core files Operating system core files and corresponding binary file, if present and requested.
Network Active connections Protocol (TCP/UDP), local and remote addresses, state, and receive and send queues.
Active sockets Type, state, flags, reference count, and full pathname.
ARP IP address, hardware address, and device.
Metadata server Configuration files Version, Tank.Bootstrap, and Tank.Config files.
Log files log.std, log.audit, log.trace, log.cim, log.failover, and log.*.old.
Core files Server core file, if present.
Server configuration Dump information about:
  • Version of installed server code
  • Current server state
  • Current server role
  • Protocol (TCP or UDP)
  • IP address and network mask
Server state Dump information about:
  • Active threads, their state, and activity
  • Mutexes and current state of each one
  • Latches and current state of each one
  • Condition variables and information about each one
  • Write-ahead log writer thread information.
Cluster configuration Dump information about:
  • Number of servers in cluster
  • Listing of all servers in cluster
  • Fileset (container) information
  • Global disk table and type of each disk (master, system, user)
  • List of registered clients and information about each one
  • Heartbeat interval between servers
  • Current state of High-Availability Manager
Administrative server Configuration files tank.properties, cimom.properties, and tank_device_map files.
Log files cimom.log, console.log, security.log, and WebSphere® Application Server-based trace.log files.
Core files Server core file, if present.

Client

You can collect information about the software running on a client, such as the following:

Table 2. Client software VPD
Software area Component VPD collected
Operating system Machine Name and version.
Operating system Version, build information, and installation date.
Processes Owner, ID, binary file, status, runtime parameters, and environment variables. Additional details as well.
System log files Collect in their entirety.
Core files Operating system core files and corresponding binary file, if present and requested.
SAN File System client Log files and trace files All client log and trace files
Network Active connections Protocol (TCP/UDP), local and remote addresses, state, and receive and send queues.
Active sockets Type, state, flags, reference count, and full pathname.
ARP IP address, hardware address, and device.

Parent topic: One-button data collection utility

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.