Jp1 · 2019. 11. 29. · Title: Jp1 Author: sato naomi Created Date: 6/28/2005 3:32:05 PM
JP1 Version 11 - hitachi.com · JP1 Version 11: Example ... (OSs), the number of monitored ......
Transcript of JP1 Version 11 - hitachi.com · JP1 Version 11: Example ... (OSs), the number of monitored ......
© Hitachi, Ltd. 2016, 2017. All rights reserved.
JP1 Version 11: Example Configurations Performance management
© Hitachi, Ltd. 2016, 2017. All rights reserved. 1
List of example configurations for performance management (1/3)
Service Level Management
Configuration for monitoring web system service performance and availability by linking with operation and performance management products SLM - 02
JP1/Performance Management - Manager JP1/Performance Management - Agent Option for Service Response
Configuration for real-time monitoring of web system service performance SLM - 01
JP1/Base JP1/Service Level Management - Manager JP1/Service Level Management - User Response
Configuration for monitoring web system service performance across multiple segments SLM - 03
JP1/Base JP1/Service Level Management - Manager JP1/Service Level Management - User Response
Configuration for monitoring web system service performance in a virtual environment SLM - 04
JP1/Base JP1/Service Level Management - Manager JP1/Service Level Management - User Response
© Hitachi, Ltd. 2016, 2017. All rights reserved.
List of example configurations for performance management (2/3)
Operation and performance management (agentless (remote) monitoring)
Configuration for agentless monitoring of virtual environment operation status PFMR - 02
JP1/Performance Management - Remote Monitor for Virtual Machine
Configuration for agentless monitoring of database operation status (Microsoft(R) SQL Server) PFMR - 03
JP1/Performance Management - Remote Monitor for Microsoft(R) SQL Server Configuration for agentless monitoring of Internet service operation status PFMR - 04
JP1/Performance Management - Agent Option for Service Response
Configuration for agentless monitoring of server system operation status PFMR- 01
JP1/Performance Management - Manager JP1/Performance Management - Remote Monitor for Platform
2
© Hitachi, Ltd. 2016, 2017. All rights reserved.
Operation and performance management (agent monitoring)
Configuration for detailed monitoring of SAP ERP system operation status PFMA - 02
JP1/Performance Management - Agent Option for Enterprise Applications
Configuration for detailed monitoring of database operation status (Oracle) PFMA - 03
JP1/Performance Management - Agent Option for Oracle
Configuration for detailed monitoring of server system operation status PFMA- 01
JP1/Performance Management - Manager JP1/Performance Management - Agent Option for Platform
Agentless monitoring and agent monitoring
Agentless monitoring You can remotely monitor server operation status without installing an agent on the monitored servers. Because you do not have to install an agent product, you can immediately start monitoring systems (even those in operation). You can also introduce the operation monitoring system at a lower cost. Agentless monitoring is also suitable when you do not want monitoring to overload the monitored servers. Agent monitoring If you want to monitor server operation status in more detail, agent monitoring (in which you install a monitoring agent on a monitored server) is more suitable. You can obtain more in-depth operational information (monitoring items), and monitoring can be continued even if the server disconnects from the network. You can combine the methods of agent monitoring (powerful monitoring with in-depth monitoring items) and agentless monitoring (simple monitoring) according to the importance of servers, allowing flexibility in handling a variety of system requirements.
3
List of example configurations for performance management (3/3)
© Hitachi, Ltd. 2016, 2017. All rights reserved.
Configuration for real-time monitoring of web system service performance SLM - 01
This configuration is used for real-time monitoring of web system service performance from a user perspective, and for periodic evaluation of service level objectives (SLOs) that cannot be judged simply by monitoring items of resources and processes. You can also detect hidden problems and monitor failure warning signs.
Service level management manager Number of managers: 1 OS: Windows
User response monitoring server Number of servers: 1 OS: Windows
Monitored servers (web servers) Number of servers: 2 OS: Windows
Notes: - The service level management viewer requires a web browser
environment. - If multiple web servers exist on the same server machine, they
are counted as individually monitored servers.
Service level management
viewer Windows
Internet Explorer
Service level management
manager Windows
JP1/SLM - Manager JP1/Base
Switch
User response monitoring server
Windows JP1/SLM - UR
User User
Internet
Two monitored servers
(Web servers) Windows
Web server
Web server
4
Example configuration Conditions assumed in this example configuration
© Hitachi, Ltd. 2016, 2017. All rights reserved.
SLM - 02
MTTR: Mean Time To Recovery MTBF: Mean Time Between Failures
Service level management manager Number of managers: 1 OS: Windows
User response monitoring server Number of servers: 1 OS: Windows
Operating performance monitoring manager Number of managers: 1 OS: Windows
Remote monitoring server Number of servers: 1 OS: Windows
Monitored servers (web servers) Number of servers: 2 OS: Windows
Notes: - The service level management viewer requires a web browser
environment. - If multiple web servers exist on the same server machine, they
are counted as individually monitored servers.
Service level management viewer
and Operating performance
monitoring viewer Windows
Internet Explorer
Service level management
manager Windows
JP1/SLM - Manager JP1/Base
Switch
User response monitoring server
Windows JP1/SLM - UR
Operating performance monitoring manager Windows
JP1/PFM - Manager [Web Console] JP1/PFM - Manager [Manager] JP1/Base
Remote monitoring server
Windows JP1/PFM - Agent for SR [Service Response] JP1/PFM - Agent for SR [Base]
User User
Internet
This configuration is used to monitor web system service performance in combination with service availability (service operation ratio, MTTR, and MTBF) determined by periodic measurement of web system response time. This configuration is also used for periodic evaluation of service level objectives (SLOs).
Two monitored servers
(Web servers) Windows
Web server
Web server
Configuration for monitoring web system service performance and availability by linking with operation and performance management products
5
Example configuration Conditions assumed in this example configuration
© Hitachi, Ltd. 2016, 2017. All rights reserved.
SLM - 03
This configuration is used for real-time monitoring of web system service performance across multiple segments, from a user perspective. This configuration is also used for periodic evaluation of service level objectives (SLOs) that cannot be judged simply by monitoring items of resources and processes. You can also detect hidden problems and monitor failure warning signs.
Service level management manager Number of managers: 1 OS: Windows
User response monitoring server Number of servers: 2 OS: Windows
Monitored servers (web servers) Number of servers: 7 OS: Windows
Note: The service level management viewer requires a web browser environment.
Service level management
viewer Windows
Internet Explorer
Service level management
manager Windows
JP1/SLM - Manager JP1/Base
Switch
User response monitoring server
Windows JP1/SLM - UR
User User
User response monitoring server
Windows JP1/SLM - UR
Switch
Internet
Three monitored servers (Web servers)
Windows
Four monitored servers (Web servers)
Windows
6
Configuration for monitoring web system service performance across multiple segments
Example configuration Conditions assumed in this example configuration
© Hitachi, Ltd. 2016, 2017. All rights reserved.
SLM - 03
This configuration is used for real-time monitoring of web system service performance, in a virtual environment, from a user perspective. This configuration is also used for periodic evaluation of service level objectives (SLOs) that cannot be judged by monitoring items of resources and processes. You can also detect hidden problems, and monitor failure warning signs.
7
SLM - 04 Configuration for monitoring web system service performance in a virtual environment
Service level management
viewer Windows
Internet Explorer
Internet
User response monitoring server
Windows JP1/SLM - UR
Virtual environment
Virtual switch
Service level management manager Number of managers: 1 OS: Windows
User response monitoring server Number of servers: 1 OS: Windows
Monitored server (web server) Number of servers: 1 OS: Windows
Note: The service level management viewer requires a web browser environment.
User User
One monitored server
(Web server) Windows
Service level management
manager Windows
JP1/SLM - Manager JP1/Base
Example configuration Conditions assumed in this example configuration
© Hitachi, Ltd. 2016, 2017. All rights reserved.
PFMR - 01
This configuration is used for agentless monitoring of the OS operation status. There is no need to install an agent on servers to be monitored.
8
Configuration for agentless monitoring of server system operation status
Operating performance monitoring manager Number of managers: 1 OS: Windows
Remote monitoring server Number of servers: 1 OS: Windows
Number of monitored servers: 6 [Breakdown] Windows servers: 4 (including virtual machines: 2) Linux servers: 2
Notes: - The operating performance monitoring viewer requires a
web browser environment. - For JP1/PFM - RM for Platform, which monitors the
operation status of servers and virtual machines (OSs), the number of monitored devices includes the number of monitored servers and monitored virtual machines (OSs).
Operating performance monitoring viewer
Windows Internet Explorer
Remote monitoring server Windows
JP1/PFM - RM for Platform [Platform] JP1/PFM - RM for Platform [Base]
Two monitored servers
Windows
Operating performance monitoring manager
Windows JP1/PFM - Manager [Manager] JP1/PFM - Manager [Web Console]
Two monitored servers Linux
Two monitored devices
(Virtual machines)
Virtual machine Windows
Virtual machine Windows
Virtual environment
Example configuration Conditions assumed in this example configuration
© Hitachi, Ltd. 2016, 2017. All rights reserved.
PFMR - 02
This configuration is used for agentless monitoring of the OS operation status of virtual environments (hypervisors). There is no need to install an agent on servers to be monitored.
9
Configuration for agentless monitoring of virtual environment operation status
Operating performance monitoring manager
Windows JP1/PFM - Manager [Manager] JP1/PFM - Manager [Web Console]
Operating performance
monitoring viewer Windows
Internet Explorer
Remote monitoring server Windows
JP1/PFM - RM for Platform [Platform] JP1/PFM - RM for Platform [Base] JP1/PFM - RM for VM [Virtual Machine]
Example configuration Conditions assumed in this example configuration
Two monitored devices
(Virtual machines)
Virtual machine Windows
VMware ESX
Virtual environment
Monitored device (Hypervisor)
Virtual machine Windows
Operating performance monitoring manager Number of managers: 1 OS: Windows
Remote monitoring server Number of servers: 1 OS: Windows
Monitored devices (virtual environments) Virtual machines (OS: Windows): 2 Hypervisor: 1
Notes: - The operating performance monitoring viewer requires a web
browser environment. - For JP1/PFM - RM for Platform, which monitors the operation
status of servers and virtual machines (OSs), the number of monitored devices is equal to the number of virtual machines (OSs).
- For JP1/PFM - RM for VM, which monitors the operation status of hypervisors, the number of hypervisors is counted as the number of devices to be monitored. The number of virtual machines is not counted.
© Hitachi, Ltd. 2016, 2017. All rights reserved.
Configuration for agentless monitoring of database operation status (Microsoft(R) SQL Server) PFMR - 03
Operating performance monitoring manager Number of managers: 1 OS: Windows
Remote monitoring server Number of servers: 1 OS: Windows
Monitored server (database server) Number of servers: 1 OS: Windows
Note: The operating performance monitoring viewer requires a web browser environment.
Operating performance monitoring manager
Windows JP1/PFM - Manager [Manager] JP1/PFM - Manager [Web Console]
Operating performance
monitoring viewer Windows
Internet Explorer
One remote monitoring server Windows
JP1/PFM - RM for Platform [Platform] JP1/PFM - RM for Platform [Base] JP1/PFM - RM for SQL [Microsoft(R) SQL Server]
Database
10
Example configuration Conditions assumed in this example configuration
Monitored server (Database server)
Windows Microsoft SQL Server (One instance)
This configuration is used for agentless monitoring of the operation status of Microsoft SQL Server. There is no need to install an agent on servers to be monitored.
© Hitachi, Ltd. 2016, 2017. All rights reserved.
PFMR - 04
This configuration allows you to monitor Internet services and measure response time. You can also create a scenario that anticipates sequences of customer operations, and record web page transitions based on that scenario to measure response time. You can measure and quantitatively evaluate the response of web services from a customer perspective.
11
Configuration for agentless monitoring of Internet service operation status
Operating performance monitoring manager Number of managers: 1 OS: Windows
Remote monitoring server Number of servers: 1 OS: Windows
Monitored servers (web servers) Number of servers: 1 OS: Windows
Note: The operating performance monitoring viewer requires a web browser environment.
Operating performance monitoring manager
Windows JP1/PFM - Manager [Manager] JP1/PFM - Manager [Web Console]
Operating performance
monitoring viewer Windows
Internet Explorer
Inte
rnet
or i
ntra
net
Remote monitoring server
Windows JP1/PFM - Agent for SR [Service Response] JP1/PFM - Agent for SR [Base]
Monitored server (Web server)
Windows
Example configuration Conditions assumed in this example configuration
© Hitachi, Ltd. 2016, 2017. All rights reserved.
This configuration is used to monitor the OS operation status. Detailed monitoring is possible by installing agents on the servers to be monitored.
12
PFMA - 01 Configuration for detailed monitoring of server system operation status
Operating performance monitoring manager Number of managers: 1 OS: Windows
Monitored servers Number of servers: 5 [Breakdown] Windows servers: 3 Linux servers: 2
Note: The operating performance monitoring viewer requires a web browser environment.
Operating performance
monitoring viewer Windows
Internet Explorer
Operating performance monitoring manager
Windows JP1/PFM - Manager [Manager] JP1/PFM - Manager [Web Console]
Three monitored servers Windows
JP1/PFM - Agent for Platform [Platform] JP1/PFM - Agent for Platform [Base]
Two monitored servers Linux
JP1/PFM - Agent for Platform [Platform] JP1/PFM - Agent for Platform [Base]
Example configuration Conditions assumed in this example configuration
© Hitachi, Ltd. 2016, 2017. All rights reserved.
PFMA - 02
This configuration is used to monitor the OS operation status of the SAP ERP system and servers. Detailed monitoring is possible by installing agents on the servers to be monitored.
13
Configuration for detailed monitoring of SAP ERP system operation status
Operating performance monitoring viewer
Windows Internet Explorer
Monitored server (ERP server)
Windows JP1/PFM - Agent for Platform [Platform] JP1/PFM - Agent for Platform [Base] JP1/PFM - Agent for EAP [Enterprise Applications] SAP ERP system
Operating performance monitoring manager Number of servers: 1 OS: Windows
Monitored servers Number of servers: 6 [Breakdown] Windows servers: 4 (including one EAP server) Linux servers: 2
Note: The operating performance monitoring viewer requires a web browser environment.
Operating performance monitoring manager
Windows JP1/PFM - Manager [Manager] JP1/PFM - Manager [Web Console]
Three monitored servers
Windows JP1/PFM - Agent for Platform [Platform] JP1/PFM - Agent for Platform [Base]
Two monitored servers
Linux JP1/PFM - Agent for Platform [Platform] JP1/PFM - Agent for Platform [Base]
Example configuration Conditions assumed in this example configuration
© Hitachi, Ltd. 2016, 2017. All rights reserved.
PFMA - 03
14
Operating performance monitoring viewer
Windows Internet Explorer
Operating performance monitoring manager
Windows JP1/PFM - Manager [Manager] JP1/PFM - Manager [Web Console]
Three monitored servers
Windows JP1/PFM - Agent for Platform [Platform] JP1/PFM - Agent for Platform [Base]
Two monitored servers
Linux JP1/PFM - Agent for Platform [Platform] JP1/PFM - Agent for Platform [Base]
Database
Operating performance monitoring manager Number of servers: 1 OS: Windows
Monitored servers Number of servers: 6 [Breakdown] Windows servers: 4 (including one database server) Linux servers: 2
Note: The operating performance monitoring viewer requires a web browser environment.
Configuration for detailed monitoring of database operation status (Oracle)
Example configuration Conditions assumed in this example configuration
This configuration is used to monitor the operation status of Oracle databases. Detailed monitoring is possible by installing agents on the servers to be monitored.
Monitored server (Database server)
Windows JP1/PFM - Agent for Platform [Platform] JP1/PFM - Agent for Platform [Base] JP1/PFM - Agent for Oracle [Oracle] Oracle database
© Hitachi, Ltd. 2016, 2017. All rights reserved.
JP1/SLM - Manager : JP1/Service Level Management - Manager JP1/SLM - UR : JP1/Service Level Management - User Response JP1/PFM - Manager : JP1/Performance Management - Manager JP1/PFM - Agent for SR : JP1/Performance Management - Agent Option for Service Response JP1/PFM - Agent for Platform : JP1/Performance Management - Agent Option for Platform JP1/PFM - Agent for Oracle : JP1/Performance Management - Agent Option for Oracle JP1/PFM - RM for VM : JP1/Performance Management - Remote Monitor for Virtual Machine JP1/PFM - RM for SQL : JP1/Performance Management - Remote Monitor for Microsoft(R) SQL Server JP1/PFM - Agent for EAP : JP1/Performance Management - Agent Option for Enterprise Applications JP1/PFM - Agent for xxx : JP1/Performance Management - Agent Option for xxx JP1/PFM - RM for xxx : JP1/Performance Management - Remote Monitor for xxx
Abbreviations
15
© Hitachi, Ltd. 2016, 2017. All rights reserved.
Information about Hitachi product names and trademarks • HITACHI, JP1 are either trademarks or registered trademarks of Hitachi, Ltd. in Japan and other countries.
Information about third-party product names and trademarks • Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. • Microsoft, Internet Explorer, SQL Server and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. • Oracle and Java are registered trademarks of Oracle and/or its affiliates. • SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. • Other company and product names mentioned in this document may be the trademarks of their respective owners.
Product names and trademarks
16
© Hitachi, Ltd. 2016, 2017. All rights reserved.
JP1 Version 11: Example Configurations
17
Performance management
jp1v11_configuration_06_performance_e [03] 2017.1