13.6 OVO AUTOMATIC STARTUP AT BOOT TIME
You should become familiar with the automatic startup and shutdown process for the management server and the managed nodes. During server startup, it is necessary for several services, such as the Internet services or DNS, to start prior to the OpenView processes. If for some reason the prerequisite services are not enabled, you will experience problems with OVO. Information about the specific startup and shutdown files for Oracle, NNM, and OVO is provided here for reference. In general, the order of startup for the OpenView platform is operating system communication programs, Oracle database, NNM services, OVO server, and OVO agent.- /sbin/init.d/ov500
This script controls the startup of the OpenView server processes, including OpenView NNM and OpenView Operations. OVO processes start after NNM because the file opc.lrf is registered with the NNM ovsuf startup environment. Refer to the NNM documentation for details about the registration files. You can also check that the opc program was initialized with the command ovstatus c . During startup the script is called with the following option: /sbin/init.d/ov500 start. This causes the operating system startup program (called rc) to check the file /etc/rc.config.d/ov500 for the variable OV500=1. If the variable is set to the number one, the rc program will initialize the OpenView environment. If the variable is set to zero, OpenView will not start. The paths may be different on other platforms (such as /etc instead of /sbin on Solaris). - /sbin/init.d/OVCtrl
This script controls the startup of the OpenView agent processes. - /sbin/init.d/ovoracle
This script controls the startup of the Oracle processes. The rc program is responsible for checking for the startup variable OVORACLE=1 and OVORALISTENER=1 in the configuration file /etc/rc.config.d/ovoracle.
Refer to the operating system documentation for HP-UXHP-UX or Solaris for details on startup and shutdown procedures. |
لطفا منتظر باشید ...
