Gaining Visibility Into Enterprise Network Availability
ITM Agent for Ping Probe from
Blue Medoraprovides the ability to perform ITM-based availability checking (pings) against thousands of network hosts, including switches, routers, servers, and other TCP/IP enabled devices.
Business Benefits
Monitors availability of critical network hardware reducing length of downtime. Maximizes network uptime by identifying suspect hardware that is failing intermittently.
Features
- Global ping configuration options for Ping timeout, Ping retry attempts, and "Slow" threshold
- Easily scaled to ping many thousands of hosts via multiple Agent instances, polling intervals, and a option to specify the concurrent number of pings to be performed
- "Per host" Configurable timeout values that allow administrators to tailor the ping scans for their particular environment
- Ability to distinguish Hosts that are Up, Down, Responding Slowly, or not Resolvable in DNS along with specific TEP-based workspaces that drill down into each of those categories
- Summarized statistics and TEP-based workspaces indicating both the total number of Hosts that are Up, Down, Responding Slowly, or not Resolvable as well as the Percentage of each
- Highly configurable allowing many thousands of hosts to be added to the "host file" or via standard ITM agent configuration panels
Common uses of the Ping Probe Agent
- How many of hosts are currently DOWN?
- What portions of a network are experiencing slowness?
- What percentage of hosts are reachable and responding with an acceptable response time?
- What percentage of monitored hosts were available 100% of the time last month?
- Which hosts are experiencing intermittent network connectivity issues?
- How do ping response times compare from various customer geographies?
ITM Agent for Ping Probe Workspace as viewed from the TEP
Blue Medora's ITM Agent for Ping Probe
- Takes advantage of ITM's Tivoli Enterprise Portal (TEP) visualization capabilities to include best practices, expert advice, customized workspaces, and historical data gathering
- Integrates with Tivoli Data Warehouse (TDW) to provide ITDS-focused historical data collection and analysis
- Provides the ability to send application-specific events to the Tivoli Enterprise Console (TEC) and Netcool OMNIbus for advanced correlation and automation
Versions of IBM Tivoli Monitoring Supported
- IBM Tivoli Monitoring V6.2
- IBM Tivoli Monitoring V6.2.1
- IBM Tivoli Monitoring V.6.2.2
Operating System Support
- AIX 5.3 (64 bit)
- AIX 6.1 (64 bit)
- Solaris V9 (SPARC) (32/64 bit)
- Solaris V10 (SPARC) (64 bit)
- Solaris V10 (x86-64) on AMD Opteron
- HP-UX 11.23 and 11.31 on Itanium2
- Windows 2003 Server SE (32 bit) with Service Pack1 or higher
- Windows 2003 Server EE (32 bit) with Service Pack 1 or higher
- Windows 2003 Server (64 bit) with Service Pack 1 or higher
- Windows 2003 Server EE (64 bit)
- Windows Server 2003 Datacenter Edition
- Windows Server 2008 SE (32 bit)
- Windows Server 2008 EE (32 bit)
- Windows Server 2008 SE (64 bit)
- Windows Server 2008 EE (64 bit)
- Windows Server 2008 Data Center
- Windows Server 2008 Data Center (64 bit)
- Red Hat Enterprise and Desktop Linux 4 for Intel
- Red Hat Enterprise Linux 4 for AMD64/EM64T
- Red Hat Enterprise Linux 4 for pSeries
- Red Hat Enterprise Linux 4.0 for z/Series 31-bit
- Red Hat Enterprise Linux 4.0 for z/Series 64-bit
- Red Hat Enterprise Linux 5 for AMD64/EM64T
- Red Hat Enterprise Linux 5 for pSeries
- Red Hat Enterprise Linux 5.0 for z/Series 31-bit
- Red Hat Enterprise Linux 5.0 for z/Series 64-bit
- SUSE Linux Enterprise Server 10 for Intel
- SUSE Linux Enterprise Server 10 for zSeries 31-bit
- SUSE Linux Enterprise Server 10 for zSeries 64-bit
- SUSE Linux Enterprise Server 10 for pSeries
- SUSE Linux Enterprise Server 11 for Intel
- SUSE Linux Enterprise Server 11 for zSeries 31-bit
- SUSE Linux Enterprise Server 11 for zSeries 64-bit
- SUSE Linux Enterprise Server 11 for pSeries
Requirement for pre-existing IBM Tivoli Monitoring agent
To install any Blue Medora ITM Agent you must have at least one pre-existing IBM published agent installed. Blue Medora Agents do not include key IBM specific Java", IBM GSkit, or the IBM Tivoli Monitoring runtime libraries. Installing an IBM-provided agent (normally the OS agent) installs these elements.