OMNM 6.5.
Notes and Cautions A NOTE indicates important information that helps you make better use of your computer. A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ © 2018 Dell Inc. Trademarks used in this text: Dell EMC™, the DELL EMC logo, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, KACE™, FlexAddress™ and Vostro™ are trademarks of Dell Inc.
Contents 9 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 In This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Overview . . . . . . . .
Upgrading on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Preparing to Upgrade on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79 83 7 Troubleshooting Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 A Installation User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Single-Server Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Distributed and HA Servers Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Remaining Application and Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Installing Remaining Mediation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 HTTPS Support with Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Verifying Clustered Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MySQL Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 MySQL Server Configuration File Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 6GB example (default): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 8GB example: . . . . . . . . . . . . . . . . . .
OMNM 6.5.
1 Introduction This section provides a high-level understanding of the tasks required to install or upgrade OpenManage Network Manager and the order in which to complete the tasks. In This Guide – 10 Intended Audience – 10 Installation Overview – 11 Related Documents – 11 OMNM 6.5.
In This Guide | Introduction In This Guide This guide covers the following topics related to the OpenManage Network Manager (OMNM) product installation: • • • • • • • • • • • • Introduction provides the guide content, intended audience, installation overview, and any related documents required. Preparing for Installation provides the tasks needed before you start the installation to ensure that you have all the system requirements in place to ensure a smooth installation.
Installation Overview | Introduction Installation Overview The installation process installs the OpenManage Network Manager (OMNM) application, including its foundation class software. See Preparing for Installation on page 13 for system requirements and other prerequisites. The OMNM application is not compatible with other software using the standard SNMP ports (such as 162), or other raw sockets.
Related Documents | Introduction 12 OMNM 6.5.
2 Preparing for Installation This section provides what you need to prepare for OpenManage Network Manager installation or upgrade and how to start the applications used to do the preparation tasks.
Preparing for Installation | Preparing for Installation Preparing for Installation Before installing the OpenManage Network Manager (OMNM) application, there are a few things you need to do to ensure a quick and successful installation. Table 2-1. Preparing for Installation or Upgrade Checklist Item Task Done 1 Obtain the installer (media/download). 2 Recommendation: Review device and OMNM release notes.
Verifying System Requirements | Preparing for Installation Verifying System Requirements System requirements depend on how you use the application and the operational environment. Your specific network and devices may require something different from the recommendations for typical installations. Base the minimum configuration of any system on its expected peak load. Optimally, your installation should spend 95% (or more) of its time idle and 5% of its time trying to keep pace with the resource demands.
Verifying System Requirements | Preparing for Installation Table 2-3. OMNM Software Requirements (Sheet 2 of 2) Software Requirements Virtualization OMNM may be installed on virtual servers. Supported hypervisors include: VMware, HyperV, and KVM. Note: System requirements for virtual machines are the same as physical machines, except the hardware must have the capacity for its own requirements and the virtual machine.
Recommended Linux Install Preparation | Preparing for Installation Recommended Linux Install Preparation If you are installing on Linux, you must log in as a non-root user. The Linux installation prompts you to run some additional scripts as root during the installation process. CAUTION: Do not log in as root and su to a non-root user. Make sure your login automation does not do this either. This causes problems, particularly with upgrades.
Recommended Linux Install Preparation | Preparing for Installation 2 Login as root, create a new user with a home directory, set the password, and add the user to the proper group. For example, here are the commands to configure the test user: useradd -m test passwd abcxyz usermod -aG wheel test The wheel user group allows password-less sudo. 3 Copy the installation files to the local system on which you plan to install the OMNM application.
Recommended Windows Install Preparation | Preparing for Installation Recommended Windows Install Preparation Although it is not always necessary, during installation or uninstallation a suggested option is to disable any virus protection software, and any other running applications. Some applications have additional services (like Norton Unerase) that prevent correct installation on some systems. Stop these in Services in Control Panel’s Administrative Tools.
Understanding Installation Types | Preparing for Installation Distributed Model The Distributed model is suitable for most larger network environments in service providers and Enterprises. The Web server, Application server, and Mediation server are installed on separate servers without clustering. This model helps achieve better performance and helps when the minimum hardware is not available for a single-server (standalone) installation.
Understanding Installation Types | Preparing for Installation Clustered servers process using a round-robin method so that systems are protected from server failure. With distributed Mediation servers (also called mediation agents), the system handles a larger number and volume of traps and events. This is usually used with even larger systems, or when the server will be processing a lot of traps.
Understanding Installation Types | Preparing for Installation the primary and secondary Application server, so that the failover is transparent to the clients and Mediation servers. Servers also use configurable heartbeats to monitor each others status. If the primary fails, the secondary takes over and generates an event/alarm. Clients and Mediation servers identify Applications server by partition name.
Understanding Installation Types | Preparing for Installation Paired load-balancers/proxy servers direct Web users to an available Web server, and distribute Web server traffic to an available Application server, and Mediation servers communicate with managed devices. Web Portal Installation By selecting one of the custom installation options during the installation process, you can install OpenManage Network Manager’s Web server on a separate machine.
Understanding Installation Types | Preparing for Installation Application Server Installation To install only the Application server, select that option in the Choose Install Set screen that appears in the installer. As in most installations, and as is essential for distributed installations, you must select a partition name, whether the server starts automatically on host startup, the heap size, database type and location (host and port).
Understanding Installation Types | Preparing for Installation —If no agent yet determined Is the local Application server configured to do mediation? yes - use the local server (not “sticky”) no - execution of mediation request will fail Compatibility with Previous Versions The impact of the above behavior on previous mediation versions occurs only where no preferred Mediation server is available.
Understanding Best Practices | Preparing for Installation Understanding Best Practices Here is a list of best practices related to OpenManage Network Manager (OMNM) installation. Table 2-4.
Linux Disk Partition Information | Preparing for Installation Linux Disk Partition Information Suggested partitioning includes separation into several partitions including /, swap, /usr, /opt, and / export/home. Partition Description / (root) The root partition contains everything that is not specifically placed on a slice/partition. The rule of thumb here is: Do not put data on this partition that is likely to grow significantly (logs, applications, data, and so on).
Linux Disk Partition Information | Preparing for Installation 28 OMNM 6.5.
3 Installing Single-Server Deployment Before installing the OpenManage Network Manager product, make sure that you have performed all the pre-installation tasks discussed in Preparing for Installation on page 13. For a description of the installation wizard and the different fields and options, see Single-Server Installer on page 84.
Single-Server Hardware Requirements | Installing Single-Server Deployment Single-Server Hardware Requirements The single server hardware guidelines provide suggested sizing for your OpenManage Network Manager system (Table 3-1). CAUTION: These hardware requirements assume you have a host dedicated to only the OpenManage Network Manager application. Other applications may compete for ports or other resources and can impair the system’s performance.
Single-Server Hardware Requirements | Installing Single-Server Deployment Table 3-1. Single Server Hardware Requirement Guidelines (Sheet 2 of 3) Max. Managed Devices 64-bit Operating System: Disks/RAM/ Hardware/Core (CPU) Max. Performance Max. Traffic Concurrent Monitor Flow Users Max. Targets Exporters 1000 18GB RAM, multidisk, server level PC /6-8 Core 50 100000 100 8-12GB Application server heap, 3GB database buffer, 5GB Synergy Web server 2000 32GB RAM, multi100 disk, server level PC.
Installing on Windows | Installing Single-Server Deployment Table 3-1. Single Server Hardware Requirement Guidelines (Sheet 3 of 3) Max. Managed Devices Unlimited/ HA 64-bit Operating System: Disks/RAM/ Hardware/Core (CPU) Max. Performance Max. Traffic Concurrent Monitor Flow Users Max. Targets Exporters Suggested Heap Memory Settings OMNM can support an unlimited RTM (device count) license where there is no limit on the number of managed devices in inventory.
Installing on Windows | Installing Single-Server Deployment • Anti-Virus application (25) 10 Continue with step 12. 11 Provide the following information if prompted: • Installation Folder • Network Interfaces If multiple network interfaces were detected on your local machine, select the network address to be used by this software. If your Windows version does not support the installer finding the host’s IP address, you are prompted for an IP address and Partition Name for your installation.
Installing on Linux | Installing Single-Server Deployment Installing on Linux CAUTION: If your Linux package already installed a version of the MySQL database, uninstall that database before proceeding. Also: Do not configure and/or install a database larger than the available disk space. Install the OpenManage Network Manager (OMNM) application on a single Linux information system as follows. 1 Log in as a non-root user from an ssh terminal window or GNOME desktop.
Installing on Linux | Installing Single-Server Deployment 8 Provide the following information if prompted: • Installation Folder • Network Interfaces If multiple network interfaces were detected on your local machine, select the network address to be used by this software. If your Windows version does not support the installer finding the host’s IP address, you are prompted for an IP address and Partition Name for your installation.
Installing OMNM Silently | Installing Single-Server Deployment c. Set a password reminder. d. Click Save. The OpenManage Network Manager Home page is displayed and you are ready to start Completing Post-Installation Tasks on page 65. Otherwise, resolve issues before continuing. Installing OMNM Silently Linux systems support OpenManage Network Manager (OMNM) silent installation where the installer runs without any user interaction. A near-silent mode is also possible on a Windows system.
Installing from the Command Line | Installing Single-Server Deployment c. Set a password reminder. d. Click Save. The OpenManage Network Manager Home page is displayed and you are ready to start Completing Post-Installation Tasks on page 65. Otherwise, resolve issues before continuing. Installing from the Command Line Installing from the Command Line You can execute the OpenManage Network Manager (OMNM) installation from the command line.
Installing from the Command Line | Installing Single-Server Deployment If you installed a MySQL database to a separate host in console mode, you must run loaddb, loaddb -s, and then run ocpinstall -s, all from the Application server installation console. By default, the servers automatically start after the installation successfully completes. 6 Verify your installation as follows. a.
Upgrading an Existing Installation | Installing Single-Server Deployment Upgrading an Existing Installation For a description of the installation user interface and the different fields and options, see Installation User Interface on page 83.
Upgrading an Existing Installation | Installing Single-Server Deployment • • • • • • • • • • • • • • Adaptive CLI with Perl scripts must contain valid Perl under the “strict” pragma (use strict;). If you import or migrate from a previous version a Perl script that does not pass this “strict” criterion, you must rewrite it for “strict” compliance before you can successfully edit or copy it. Any configured color changes to the portal may not persist and must be re-made manually.
Upgrading an Existing Installation | Installing Single-Server Deployment Defaults for the database are oware (login) and dorado (password). These are typically different from the login/password for the application. NOTE: To get a rough estimate of a database’s size, looking at the size of the directory [installation root]\oware3rd\mysql\data. Here are the backup commands for all the databases: mysqldump -a -u root --password=dorado owbusdb > owbusdb.
Upgrading an Existing Installation | Installing Single-Server Deployment If you are running a domain profile that implements the firewall setting with a Group Policy, the rules added by the OMNM installer may be overridden. Prepare to upgrade your OMNM version on a Windows system as follows. 1 Back up the database to another machine and any other resources that need manual installation. The backup is stored in the installPath/backup.sql directory.
Upgrading an Existing Installation | Installing Single-Server Deployment Preparing to Upgrade on Linux This section summarizes the steps to take to prepare for an OpenManage Network Manager (OMNM) application upgrade on a Linux system. Prepare to upgrade your OMNM version on a Linux system as follows. 1 Back up the database to another machine and any other resources that need manual installation. The backup is stored in the installPath/backup.sql directory.
Upgrading an Existing Installation | Installing Single-Server Deployment 6 Answer each prompt appropriately. If you did not backup your database before starting the update, you are given one more chance to do so. The database backup is stored in the installPath/backup.sql file by default. If you elect not to rebuild the database, the update still re-seeds the system settings. If you encounter port conflicts, resolve them before continuing. The servers automatically start when the update finishes.
Uninstalling the Application | Installing Single-Server Deployment Uninstalling the Application Use Control Panel to uninstall in Windows. Uninstall by running the following on Linux: $OWARE_USER_ROOT/uninstall No graphic wizard appears, and you must respond to the command-line prompts as they appear. You can uninstall the software by using Windows’ control panel’s Add/Remove programs feature (or from a Windows command prompt with %OWARE_USER_ROOT%\uninstall.
Uninstalling the Application | Installing Single-Server Deployment 46 OMNM 6.5.
4 Installing Virtual Appliance The OpenManage Network Manager (OMNM) Virtual Appliance, or virtual machine (VM) is a single .ova file, compatible with VMware® products including VMWare ESX®, VMware Workstation and VMware Player. NOTE: This section assumes that the user has in depth Linux and VMware administration knowledge. The section assumes that the VM is a standalone server and client access comes from a client browser from another host.
Quick Start the Virtual Appliance | Installing Virtual Appliance Quick Start the Virtual Appliance Get started quickly by importing and starting the Virtual Appliance as follows. 1 Import the .OVA file and power on. We recommend you review Understanding Prerequisites on page 49. 2 Start the VM and login with: user= synergy password=synergyP@$$ 3 Run the ./setup command. 4 Select Option #1 for initial VM configuration. This configures the VM's static IP address and installs the 30 day trial license.
Detail Steps to Start OMNM Virtual Appliance | Installing Virtual Appliance Detail Steps to Start OMNM Virtual Appliance This section provides detailed steps for importing/configuring and starting the Virtual Appliance. The Quick Start section shows you how to get the appliance up and running quickly with no issues. This section is intended for users that are experiencing issues during the quick start or if more information is needed regarding the process.
Detail Steps to Start OMNM Virtual Appliance | Installing Virtual Appliance • • • Neither Firewalls nor other restrictions block communication for ICMP, SNMP, FTP, TFTP, SCP, SSH, Telnet, HTTP SMTP and internet access are required for notification from OMNM by e-mail as well as for license/subscription renewal The following system requirements: Requirement Description Virtual Machine VM is configured with 1 processor and 4 cores.
Detail Steps to Start OMNM Virtual Appliance | Installing Virtual Appliance Requirement Description Adobe VM does not come with graphics capabilities to view PDF or run Flash. Remote access is required using a Web browser and there you need: • Flash Player (32-bit or 64-bit) • Reader Java • 1.6 or later Screen • Screen resolution must equal or exceed 1280 x 1024 pixels. Your screen must be at least 1250 pixels wide.
Detail Steps to Start OMNM Virtual Appliance | Installing Virtual Appliance Starting the Virtual Machine After you have completed the above steps, you can start the OpenManage Network Manager (OMNM) application in the VM console. NOTE: Before you start the VM console, make sure that you make any needed VM setting modifications by rightclicking the Image to get the menu of options. 1 Start the VM by clicking on its name and then selecting Power > Power On. 2 Open the VM Console.
Upgrading the VM | Installing Virtual Appliance Starting the Application Follow these steps to start the application. 1 Restart the VM if you have not already done so as follows: a. Shut down the Web and Application servers using one of the following: • Use option 6 from the ./setup menu. • Use the following commands: oware stop synergy stop b. Shutdown the database as follows: sudo service owaredb stop c.
Troubleshooting VM Installation | Installing Virtual Appliance 4 Start the installer: ./linux_install.bin 5 Accept the license agreement to start the upgrade process. A message is displayed indicating that an existing installation was detected and this will be an upgrade. Also noted are the installed features. Click Enter to continue. Otherwise, enter quit to cancel the upgrade. 6 Answer each prompt appropriately.
5 Installing Distributed and HA Deployments Before installing the OpenManage Network Manager product, make sure that you have performed all the necessary tasks discussed in Preparing for Installation on page 13. For a description of the installation wizard and the different fields and options, see Distributed and HA Servers Installer on page 87. This section covers the following installation tasks.
General Information | Installing Distributed and HA Deployments General Information This section includes some general information about: • • • • Distributed Installation Databases on Separate Servers Adding Mediation Servers High Availability and Clustering Distributed Installation A distributed installation requires the HA installer for your operating system.
General Information | Installing Distributed and HA Deployments To enable Mediation server portal, modify and rename the following properties file: oware/synergy/conf/server-overrides.properties.sample Uncomment the medserver.support=true property, and rename this file to omit the .sample extension. High Availability and Clustering When you are installing a high availability system, the installation includes a setup for the Config Server (the primary server in a cluster).
Distributed/HA Hardware Requirements | Installing Distributed and HA Deployments Distributed/HA Hardware Requirements The distributed server hardware guidelines are based on average OpenManage Network Manager application use on your managed network (Table 5-1). These guidelines include number of users, number of devices managed, Traffic Flow Analysis (TFA), Performance Management (PM), and Event Management (EM) as the most demanding elements.
Installing Distributed/HA Deployments | Installing Distributed and HA Deployments Installing Distributed/HA Deployments The following describes an installation to a cluster. In a production environment, such installations must take account of the network security settings and firewalls. Here are a few things to check before your installation: • • • • • Synchronize clocks on all hosts where you install OMNM. Ensure any time (NTP) server processes are running.
Installing Distributed/HA Deployments | Installing Distributed and HA Deployments (SERVER = DEDICATED) (SERVICE_NAME = MYDB) ) ) b. Run the following commands on the primary Application server: loaddb -u [dba user] -w [dba password] -s -g dbpostinstall NOTE: If you have a MySQL database on a separate host, you must also run dbpostinstall on the primary Application server. c.
Installing Distributed/HA Deployments | Installing Distributed and HA Deployments com.dorado.jdbc.user=redcell com.dorado.jdbc.password=mypwd com.dorado.jdbc.database_name.oracle=@my_server:1521:MYDB ... NOTE: If you plan to change the database name, you must change the relevant portion of your Application servers’ installed.properties files. Similarly, if you use a database tool to change the default user’s password, you must change that password in the com.dorado.jdbc.password property.
Verifying Your Installation | Installing Distributed and HA Deployments 5 Disable the Mediation server on the appserver host by not configuring it during installation. Otherwise, add the following property to the \owareapps\installprops\lib\installed.properties file: oware.appserver.mediation.setup=false 6 Configure autostarting in the owareapps/installprops/installed.properties file if you installed autostarting. See Startup Properties on page 74 for a list of potentially configurable properties.
Verifying Your Installation | Installing Distributed and HA Deployments Task Remember Alarms/Monitoring Minimize network traffic by configuring “chatty” devices to quiet down. Use Suppress Alarms to keep performance at acceptable levels, and configure database archiving so the database does not fill up. Caution: Some OMNM features, such as Maps, do not work without internet access. The maps that the OMNM application uses needs internet access to retrieve maps and plot locations.
Verifying Your Installation | Installing Distributed and HA Deployments 64 OMNM 6.5.
6 Completing Post-Installation Tasks This section provides what you need to prepare for OMNM installation or upgrade and how to start the applications used to do the preparation tasks.
Post-Install Checklist | Completing Post-Installation Tasks Post-Install Checklist The post-install checklist provides information to collect and recommended steps to complete post-install tasks. Table 6-1. Post-Install Checklist Item Task Done 1 Obtain inventory of devices (IP addresses) and ports to monitor. 2 Obtain an IP address for the OMNM server and then configure the IP address as a management station and receiver of SNMP traps on each device.
Securing MySQL Passwords | Completing Post-Installation Tasks Securing MySQL Passwords Secure MySQL passwords for all OMNM versions using the following steps to change the MySQL root and application passwords. These procedures also prevent the MySQL root password from being stored in configuration files and obviates MySQL root access by the application. 1 Stop web and application servers. 2 Change the MySQL root password. This password is not stored in any application configuration files.
Stopping Servers | Completing Post-Installation Tasks Installing Acrobat Reader After you complete the installation, you may want to install Adobe Acrobat Reader. You can download a free copy from www.adobe.com. This application requires Acrobat to successfully print reports. Installing Perl The OpenManage Network Manager (OMNM) Linux installation does not include the Perl package. The Windows installation includes Perl as part of the installed Cygwin component.
Starting Servers | Completing Post-Installation Tasks If you have not automated server startup, then you can use the stopappserver and stopmedserver scripts to stop these servers, even remotely. Single server platforms are set to Auto start by default. These commands do not apply. Here is the syntax: stopappserver :1099 -u -p stopmedserver :1099 -u -p Both -u and -p are optional parameters.
Auto Starting Servers | Completing Post-Installation Tasks By default, these scripts assume the OWAdmin user and a blank password, so if you have changed the default password for OWAdmin, you must pass it to stopappserver. Starting Linux Installations Servers on standalone installation will have auto start enabled and reboot or restart of the OS will auto start the servers.
Auto Starting Servers | Completing Post-Installation Tasks Both -u and -p are optional parameters. If you omit username, the application assumes OWAdmin is the user. If you omit a password, the application assumes a blank password. While you can always run the startappserver command-line script, a second Application server on the same port fails.
Installing Server Manager | Completing Post-Installation Tasks Installing Server Manager This section only applies to Distribute, HA or custom installations where Server control was not initially installed during installation. You can install the service post installation. The installprocman script is in $OWARE_USER_ROOT/oware/bin. The script takes several parameters.
Installing Server Manager | Completing Post-Installation Tasks c:/work/oware/lib/pmstartup.dat -i -- Number of times to repeat command, -1 is infinite (requires Ctl-C). -r -- Refresh rate of iterative command in seconds. Default is 5. Requires -i option. -? -- Show this help. Windows Server Monitor When you install your application as a service on Windows, you also install a server monitor.
Installing Server Manager | Completing Post-Installation Tasks The logs item let you view logged items for Server Manager, Application server or Mediation server. You can Start or Stop the service(s) running on your host. NOTE: System changes can make the server monitor system tray icon disappear while the process is still running. If you cannot make your icon reappear, try running pmtray -r from a command line. Web Server Parameters When you install OMNM, installation also includes an Apache Web server.
Installing Server Manager | Completing Post-Installation Tasks Network Manager User Guide for more on overriding properties). These are active for each execution of the server (even a Mediation server) on the machine where the override exists. Command line arguments override these properties. The following are properties you can set in owareapps\installprops\lib\ installed.properties to configure servers: • Default server partition name also used by client and mediation to locate a server oware.client.
Installing Server Manager | Completing Post-Installation Tasks • To change the default HTTP/HTTPS port numbers for web services, add the following properties to owareapps/installprops/lib/installed.properties: oware.appserver.web.http.port=[default port number:8080] oware.appserver.web.https.port=8443 You may then change the port values for these property entries and restart the Application server.
Installing Server Manager | Completing Post-Installation Tasks Add to /dorado/oware/jboss-5.1/owareconf/tomcat-server.xml on fresh or update installation: OMNM 6.5.
Installing Server Manager | Completing Post-Installation Tasks 78 OMNM 6.5.
7 Troubleshooting Installation Issues This section provides a list of actions that created issues during OpenManage Network Manager (OMNM) installation and the steps to resolve the issue. OMNM 6.5.
| Troubleshooting Installation Issues Action/Symptom Error Login Credentials are needed to access Modify the portalext.properties file in the /oware/synergy/ this application. tomcat-xxx/webapps/ROOT/WEB-INF/class directory to include: oware.appserver.ip=[appServerIPaddress] Resolution Run SOAP the first time SOAP Service Manager: Unable This is just an informational warning, not an error. The file to read ‘DeployedServices.ds: referenced does not exist but is created for you.
| Troubleshooting Installation Issues Action/Symptom Error Resolution Mediation server fails to start with an ENetworkFailure Manually delete all files in the oware\temp directory to successfully start the Mediation server. Application server or Mediation server fails to start after service interruption, such as a power failure. Delete the following director’s content and then start the servers: Application server startup on Windows oware\jobss*\server\oware\data FAILED TO LISTEN ON TRAP PORT 162.
| Troubleshooting Installation Issues 82 OMNM 6.5.
A Installation User Interface While running the OpenManage Network Manager (OMNM) installation wizard (installer) or the command line installer, the options that are displayed vary depending on the choices you make and the options you purchased. This section describes the windows and command line prompts where you input or change setting for the following installers: Single-Server Installer – 84 Distributed and HA Servers Installer – 87 OMNM 6.5.
Single-Server Installer | Installation User Interface Single-Server Installer This section shows the single-server installer options: Window/Prompt Field/Option Software Requirements Description Displays some minimum system requirements and provides: • A link to access the OpenManage Network Manager User Guide from the user interface • The OpenManage Network Manager User Guide location from the command line License Agreement Installation Types Allows you to install the product when selected.
Single-Server Installer | Installation User Interface Window/Prompt Field/Option Network Interfaces/ Address Network Address Description Lists the network interfaces detected on the local machine. Select or enter which address to use for the OMNM application. If you selected Express installation, your system is scanned for port conflicts. If conflicts are found, the Warning! Possible port conflicts window is displayed. Otherwise, the installation starts.
Single-Server Installer | Installation User Interface Window/Prompt Field/Option Description Monitor Server Startup Now? Yes/No Specifies whether to run the Server Status Console now (Yes) or not (No). The default is Yes. The console monitors the startup progress of you servers and allows you to start the application. If you selected Yes, the console is displayed after the installation completes and you click Done. Note: This option is not available when you run the installer from the command line.
Distributed and HA Servers Installer | Installation User Interface Distributed and HA Servers Installer This section shows the distributed and HA installer options.
Distributed and HA Servers Installer | Installation User Interface Window/Prompt Field/Option Description Choose Install Set instType Select one of the installation types: • Complete installs all features and recommended for most users. This is the default. The next option is to Choose Shortcut Folder. • Application Server installs only the core server required to support Mediation servers and Web portal servers. The next option is to Choose Shortcut Folder.
Distributed and HA Servers Installer | Installation User Interface Window/Prompt Field/Option Description Heap Settings Max Allows you to customize the number of devices monitored by the OMNM application and the number of concurrent OMNM users by setting the maximum values for: • Application Server Heap Settings (Gigabytes) • Synergy Web Services Heap Settings (Gigabytes) The default values are 3 for the application server and 2 for the Web service.
Distributed and HA Servers Installer | Installation User Interface Window/Prompt Field/Option Windows Firewall Allow/Do not Detected - Allow allow firewall Access? access Description Specifies whether to allow firewall access when a firewall is detected. If you allow firewall access, rules are automatically added to the Windows Firewall Inbound Rules list. If you do not allow the firewall, the OMNM application does not perform as intended.
Distributed and HA Servers Installer | Installation User Interface Window/Prompt Field/Option Description Database Migration Yes/No Specifies whether to apply any required schema changes and automate possible data migration tasks (No) or rebuild database content (Yes). The default is No (2). OMNM 6.5.
Distributed and HA Servers Installer | Installation User Interface 92 OMNM 6.5.
B Upgrading/Patching from Previous Versions Upgrade Overview – 94 Patches – 95 Upgrading from OMNM 6.2 SP3 to 6.5 – 98 Upgrading from OMNM 4.4 to 6.x – 98 Upgrading OMNM 5.x – 100 OMNM 6.5.
Upgrade Overview | Upgrading/Patching from Previous Versions Upgrade Overview Upgrading is a process for migrating data, converting database content to be compatible with updated software. Please review any release notes for your new version before assuming migration is necessary or possible. Not all upgrades require migration tasks, and migration is not possible from/ to all versions. New software is not always capable of using data from older versions.
Patches | Upgrading/Patching from Previous Versions Patches Patches are, in effect, upgrades to an existing package to either fix a bug or install a requested enhancement. To install a patched driver, the following are the recommended steps: Check Status When upgrading, check the status of any running processes with the following command(s): service oware status ..
Patches | Upgrading/Patching from Previous Versions Compatible Operating Systems/Databases/Browsers Sometimes upgrading OpenManage Network Manager (OMNM) requires an operating system upgrade on the host(s) where you install it. Such an upgrade typically follows these steps: 1 Back up the OMNM database. 2 Upgrade the operating system. 3 Install the OMNM version from which you were upgrading (again) on the newly updated (supported) operating system.
Patches | Upgrading/Patching from Previous Versions Release Number: 5.2SP1 5.3 MySQL 5.0.5164 5.0.51-64 Oracle 9.2.0.5 - 9.2.0.5 - 9.2.0.5 - 9.2.0.5 11 11 11 11 Database Browser Version 5.0 5.1 5.2 6.0 6.1 6.2SP3 6.5.x 5.0.51- 5.0.51- 5.0.51- 5.7.1664 64 64 64 9.2.0.5 - 9.2.0.5- 9.2.0.5- 9,10,11, 9,10,11. 11 11 11 12c 12c IE 9 9 9 9 9 9 11 11 11 Firefox 3.6 3.6 3.6 12 12 12 54 54 54 Chrome 6 6 6 22 22 22 59 59 63 Safari 5 5 5 5 5 5 5 5 5 1.
Upgrading from OMNM 6.2 SP3 to 6.5 | Upgrading/Patching from Previous Versions Upgrading an Oracle Installation Upgrading an installation with an Oracle database follows the steps outlined in the following sections. Read them, and the rest of this section first. Make sure the version of OpenManage Network Manager supports your Oracle version. See Software Requirements on page 15 for specifics about what’s supported. If your Oracle is not compatible, upgrade it first.
Upgrading from OMNM 4.4 to 6.x | Upgrading/Patching from Previous Versions c. Note or take screen shots of the following that must be manually recreated after upgrading: –Existing User Records and Associated User Group Membership –Existing Permissions for each User Group –Any configured, enabled Scheduled Items –Any Group Operations –Groups of Adaptive CLIs (for batch execution) –File Backup Actions –OpenManage Network Manager Change Management Actions 3 Do a full backup of your database.
Upgrading OMNM 5.x | Upgrading/Patching from Previous Versions e. Recreate Scheduled Items, taking into account any new actions configured for items above. f. Review previously Scheduled Items that appear in the upgraded installation. Recreate any missing Scheduled items to ensure proper visibility and execution of the associated scheduled activity. 9 Review / augment and retest Adaptive CLIs that had negate commands previously tied to them (both positive and negative/error use cases).
Upgrading OMNM 5.x | Upgrading/Patching from Previous Versions How To: Perform Patch Upgrades The patch process for patching the web portal is as follows: 1 Copy the *.ddp and *.ocp files to the installation root directory. 2 Copy the patched NetViewFactory.war and synergy-tomcat-xxxxx.zip to the installation root. These must replace any old files in the installation package that are not on the installed instance. 3 Re-run the installation.
Upgrading OMNM 5.x | Upgrading/Patching from Previous Versions Manual Migration The following requires manual migration (typically, export, then import) from 6.x versions: Discovery Profiles—Version 5+ no longer supports multiple networks in the profile, so migrating from previous versions whose profiles support multiple networks means those profiles are not well formatted. SMTP Settings—re-make these in the Quick Navigation portlet.
C Clustering Introducing Clustering – 104 OMNM Deployment Architecture – 104 Data Flow – 105 Cluster Constraints – 108 Synergy Web Server Clustering – 114 Preparation for Clustering – 117 Planning Clustering – 119 Step-By-Step Application Server Clustering – 120 Installing Mediation Servers – 123 HTTPS Support with Load Balancer – 126 Verifying Clustered Installations – 126 Starting Clusters Durably – 132 Clustered Server Installation Checklist – 133 Clustering with Virtual Machines – 141 OMNM 6.5.
Introducing Clustering | Clustering Introducing Clustering Clustering transparently balances the computing load for this application’s EJB components—rule engine, scheduler, logger, Business Object Manager (BOM), workspaces and mediation. This is especially beneficial for the applications’ communication with the database storing its business data. By default, this application supports the distribution of its processes. It distributes the load per client (not per request).
Data Flow | Clustering Mediation Server—Mediation Server manages the communication between the OpenManage Network Manager and the network elements. Like the application and database servers, you can deploy mediation servers in a fault tolerant master/ slave configuration to maintain constant communication with the network elements. You can make mediation servers highly available. See Mediation Clustering on page 129.
Data Flow | Clustering Distributed Non-HA This deployment distributes servers to separate machines. You can use distribution to achieve better performance by allocating dedicated servers. You may have to install to distributed servers when the minimum hardware is not available for a single server (standalone) installation. NOTE: For distributed installations best practice is to make all links connecting hosts 10GB or faster. Non-Distributed HA This is the simplest high availability (HA) installation.
Data Flow | Clustering redundancy. Paired load-balancers / proxy servers direct web users to an available web server, and distribute web server traffic to an available application server, and mediation servers communicate with managed devices. HA Distributed Cluster Deploy in this arrangement for best performance and high availability.
Cluster Constraints | Clustering • Paired, redundant mediation servers to handle traffic between OpenManage Network Manager and managed devices. Cluster Constraints This section describes the constraints within which a cluster configuration must work. • All servers in a cluster must be on the same local area network (LAN), be reachable for IP v4 multicast, and must have unique names.
Cluster Constraints | Clustering copied to the disaster recovery standby system on Real-time or on regularly scheduled intervals(Database Dump). Application servers can be replicated by software like VEEAM, Avamar etc. database Server to be replicated by oracle data guard(Real-time) or MySQL Replication(Real-time) • All cluster members must run the same version of the application and listen on the same port.
Cluster Constraints | Clustering Database Connections By default each deployed application server has 60 database pool connections available. In distributed systems, size connections by multiplying the number of application servers deployed in the system by 60 to get a starting point for the total number of required database connections.
Cluster Constraints | Clustering MySQL’s online support suggests that you can create as many as 10,000 connections depending on the amount of RAM available: “Linux should be able to support at 500 to 1000 simultaneous connections routinely and as many as 10,000 connections if you have many gigabytes of RAM available and the workload from each is low or the response time target undemanding.
Cluster Constraints | Clustering 5 And Uncomment CAUTION: Make sure you modify stack "tcp" section, not "tcp-sync" section Example: Alternative 2: non multicast-based replacement for MPING. Requires a static configuration of *all* possible cluster members.--> PAGE 115Synergy Web Server Clustering | Clustering Web Server Clustering Setup The following describes tasks needed to move existing files to the common share and basic properties which you must enable to turn on clustering. You must shut down OpenManage Network Manager during this process. Common Documents and Media Share Setup 1 Set up a network share location dedicated to store the documents and media.
Synergy Web Server Clustering | Clustering Set the Share Path 1 Document Library Share: Uncomment or add the dl.store.file.system.root.dir property. The value should point to the /path/to/share/document_library or, for Windows, if your share was drive G: then this entry would be G:/document_library 2 Legacy Images Share: Uncomment or add the image.hook.file.system.root.dir property. The value should point to the /path/to/share/images, or, for Windows, if your share was drive G: then G:/images.
Preparation for Clustering | Clustering For high availability (HA) installations, systems typically use pairs of load balancers. OpenManage Network Manager needs at least one load balancer pair to distribute loads among webservers. The load balancer IP is what clients connect to. If webserver and appserver are on same machines, all web servers can point to 127.0.0.1 to use their own local appserver.
Preparation for Clustering | Clustering • The partition names for servers in a cluster must be the same, and they must use the same multicast address for inter-cluster communication. You can set these for application servers with an the cluster installation screen that appears whenever you do a Custom installation in the installation wizard.
Planning Clustering | Clustering Config Server Functionality Clusters’ JMS implementations require ConfigServers. Configuration servers act as the coordinator for other servers joining the cluster. It must run for other servers to join the cluster. This is true for either an application server cluster or a mediation server cluster.
Step-By-Step Application Server Clustering | Clustering Step-By-Step Application Server Clustering The following is an example cluster. It includes application and web server on the same machine, and mediation server on a different machine.
Step-By-Step Application Server Clustering | Clustering 8 Specify the database access information (User, Password, Host, Port, SID). 9 Click the Install button. 10 For Linux, when prompted, run the command /opt/dorado/install/root/setup.sh as root, and then click on Next. NOTE: You may see benign errors during the root portion of the Linux installation. Installation always attempts to find the CWD (current working directory). If another process deleted it, an error appears before the script runs.
Step-By-Step Application Server Clustering | Clustering This installation program does not automatically create the database structure required by the application. This is a manual task that may require some initial MySQL database administration. 15 Create OpenManage Network Manager and Portal Tablespaces: loaddb -u system -w d0rad0 -s 16 Modify Portal-ext.properties Go to /opt/dorado/oware/synergy/tomcat-7.0.30/webapps/ROOT/WEB-INF/ classes, and edit the file portal-ext.properties. oware.appserver.
Installing Mediation Servers | Clustering Installing Mediation Servers For clustered mediation servers, first follow these steps to install the Mediation config server, then see Installing Remaining Mediation Servers on page 125. 1 Install by starting the installation wizard, and select Mediation Server in the Custom installation screen. 2 Enter the Application Server Partition Name. 3 Enter Mediation Partition Name and Subnet mask, and select Auto Start.
Installing Mediation Servers | Clustering Add mediation domain and routing entry In the OpenManage Network Manager Control panel, go to Mediation > Partitions > Add Partition name and Routing Entries. NOTE: When specifying a mediation server in Control Panel, add -medPartition at the end of mediation Partition name. For example if you specified your mediation partition as MYmeds during installation, when adding partition name to control panel it needs to be MYmeds-medPartition.
Installing Mediation Servers | Clustering You can configure the selected application server heap memory size not just during installation, but any time, with the following properties in \owareapps\installprops\lib\installed.properties. For example: oware.server.min.heap.size=4096m oware.server.max.heap.size=4096m To manually change OpenManage Network Manager web portal heap settings, change the setenv.sh or setenv.
HTTPS Support with Load Balancer | Clustering 5 Specify config server IP. Use the lowest IP among mediation servers. 6 Start mediation server when done installing. CAUTION: You must add file server's IP address to the Mediation Partition's routing entries in distributed environments that have application server's local mediation turned off. HTTPS Support with Load Balancer The industry norm is to configure the load balancer to handle SSL Offloading (SSL Termination).
Verifying Clustered Installations | Clustering Verifying Application Server In the Application Server Statistics portlet, you can see to which application server node the logged in user connects. When different users, for example, resync a device or deploy a service, the expectation is that they would use different web server + appserver hosts. That is, user A connects to server1 and user B connects to server 2 and user C connects to server 3, and so on.
Verifying Clustered Installations | Clustering Verify Application Server Redundancy Fail Over On one of server, go to directory /opt/dorado/oware/jboss-5.1 /server/oware/log, open a shell, type /etc/.dsienv (on Windows type oware), and then tail -f server.log. Observe changes to the log when one other cluster member goes down/up by unplugging/replugging the network cable or (disable/re-enable network connection). Validate Mediation Server On one of server, go to directory /opt/dorado/oware/jboss-5.
Verifying Clustered Installations | Clustering You can also observe medserver status within the Mediation panel in Control Panel. When a mediation server goes down you should see its severity turns to Critical. Mediation Clustering You can configure mediation servers which can fail over SNMP/CLI requests by configuring mediation servers as redundant peers during installation, or with the com.dorado.mediation.listener.use.high.availability=true/false property in installed.properties.
Verifying Clustered Installations | Clustering Follow these steps to configure Mediation server clusters: 1 (For MySQL installations only) If the installation has not already done so, override the database host name originally specified in oware/lib/owdatabase.properties. 2 Set oware.config.server in owareapps/installprops/medserver/lib/ installed.properties, setting it to the primary mediation host’s name (for example: aaron).
Verifying Clustered Installations | Clustering Mediation Behavior and Polling When you set up a mediation cluster to do polling, one server in the cluster does the all the polling. If the active server goes down, another resumes polling. A High Availability mediation setup duplicates the backlog of collected data that has not been posted to database in this standby server. In this case, installation requires redundant messages from devices to all servers in the cluster.
Starting Clusters Durably | Clustering Starting Clusters Durably Clusters provide failover protection for the processes they maintain, or “high availability.” To automate restarting this and other applications’ processes, install the application with process monitor. To configure process monitor to start and stop clusters if you have not installed electing autostart, you must modify the owareapps/lib/installprops/lib/ installed.properties file with a text editor.
Clustered Server Installation Checklist | Clustering Clustered Server Installation Checklist The following is a checklist for installing OpenManage Network Manager in a clustered configuration. See Upgrading Clusters on page 136 for checklists / instructions about upgrading a clustered installation.
Clustered Server Installation Checklist | Clustering 3 Obtain and Validate Database SID, User ID and Password Obtain and validate credentials and Database Instance ID to be able to perform backup and restore of the database instance. Database Server Name/IP Address: Database SID: Database Credentials: User ID Password 4 Copy OpenManage Network Manager Package File to Each of the Servers For each server, using the assigned OpenManage Network Manager User ID and Password from Above: a.
Clustered Server Installation Checklist | Clustering 6 OPTIONAL: Backup any Service Templates using OpenManage Network Manager's Services portlet Select the Export action and export all service templates to a single file with a file extension of *.xml. CAUTION: Make sure to save the export file to a directory outside of the OpenManage Network Manager's install directory tree. Export ACLI Scripts to a file system outside of the OpenManage Network Manager install directory path.
Clustered Server Installation Checklist | Clustering ORACLE Database Backup Steps Completed ORACLE backup steps q q q q MySQL Database Backup Steps Completed MySQL backup steps login as the OMNM User ID on the Database Server q Navigate to a directory outside of the OMNM installation path with writable access. q Example: cd $HOME/dbbackups q mysqldump -a -uoware -pdorado owbusdb>./ owbusdb.backup.mysql q mysqldump -a -uoware -pdorado owmetadb>./ owmetadb.backup.
Clustered Server Installation Checklist | Clustering Application Servers: Completed Application Server Name q q q q Mediation Servers: Completed Mediation Server Name q q q q The follow on steps to upgrade the OMNM nodes are as follows: Step 2: Upgrade 1st/Primary Application Server Step 3: Upgrade 1st Mediation Server Step 4: Verification: Validate System is Operational with the above three nodes after upgrade.
Clustered Server Installation Checklist | Clustering 2. Import new package's license (primary appserver only): licenseimporter license.xml f. Start OpenManage Network Manager processes: startpm& You can routinely check the startup status with the command: pmgetstatus g. Verify installed versions using showversions output and capture/save the output to a file for later reference. For example: showeversions > showversions....
Clustered Server Installation Checklist | Clustering Verification Do the following to validate the installation you just did: q Open OMNM Client in a browser and Test User Login q Test Network Discovery q Test Device Resync q Upgrade Remaining Application Servers Install to Remaining Systems Remaining Application Server Installations Application Servers 2 3 4 Steps 5 6 a) Get environment variables set up: q q q q q . /etc/.dsienv q q q q q Note the current installed.
Clustered Server Installation Checklist | Clustering Remaining Mediation Server Installations Application Servers 2 3 4 Steps 5 6 a) Get environment variables set up: q q q q q . /etc/.dsienv q q q q q Note the current installed.properties (database password needs to be given to the appserver installs) Install software: q q q q q 1. chmod +x sol_install.sh 2. ./sol_install.sh -console 3. Follow OMNM Installer steps. Get updated environment variables: q q q q q . /etc/.
Clustering with Virtual Machines | Clustering Test Cluster Failover Once All Application and Mediation Servers are up and running, perform the following tests: q Locate the application server designated as 'primary' in the server.log file's heartbeat status. q Verify that another Application Server becomes primary. q Connect the primary Application Server's network plug again. q On the matching Physical machine and pull its network plug.
Clustering with Virtual Machines | Clustering short, this overview is not a fully operational virtualization configuration, it is an example. Refer to the deployment scenarios described in this chapter for more information. The following examples focus on a VMware implementation. Each site requires access to an appropriate database.
Clustering with Virtual Machines | Clustering The following chart shows the processor assignment-workload association. This distribution is similar to the suggested expansion workload distribution.
Clustering with Virtual Machines | Clustering Primary Site - Virtualized - Failover Scenario Among the advantages of virtualization is the redundancy that can be built in to the system. The following diagram reflects a possible failover scenario that remains at full operational capacity while evacuating all workloads from one server from an unplanned outage or planned maintenance windows. The following chart shows the processor assignment-workload association.
Clustering with Virtual Machines | Clustering Primary Site - Virtualized: Expandability Virtualizing the infrastructure also allows for future workload increases. The following chart demonstrates increasing both application server processor core assignments from eight to twelve and increasing the web server processor core assignments from four to eight.
Clustering with Virtual Machines | Clustering Servers The consolidated workloads require higher capacity servers. • • • • • Dell PowerEdge R910 Processor4 x Intel E7 (10 core) => 40 threads Memory256 GB (1.
D Database Management Introducing Databases – 148 Database Timeout – 149 Embedded Database Sizing – 150 Modifying the MySQL FAT File Systems – 152 Database Backup/Restoration – 153 Distributed Database Upgrades – 155 OMNM 6.5.
Introducing Databases | Database Management Introducing Databases This chapter discusses database management procedures. This discussion includes installation with the embedded MySQL database. You must distribute Oracle installations and you can distribute MySQL. In addition to correctly sizing your database, best practice is to develop a plan to regularly back up the database, including steps to verify this backup with recovery.
Database Timeout | Database Management For Oracle: owbusdb ( specified during installation) lportal : netview/dorado synergy: synadmin/dorado For loaddb, use the system user’s password. For the portal databases (lportal, synergy) access, set the password in oware\synergy\tomcat-X.X\webapps \ROOT\WEBINF\classes\portal-ext.properties. The property com.dorado.jdbc.password.encrypted specifies whether the database password is encrypted between OpenManage Network Manager and the database.
Embedded Database Sizing | Database Management Database Emergency E-mail To send an e-mail notification to emergency support contacts, if the OpenManage Network Manager database becomes unavailable do the following: 1 In the file owareapps/installprops/lib/installed.properties add the following property: oware.monitor.
Embedded Database Sizing | Database Management Follow these steps to resize your database For Windows, 1 Shut down all applications and application server. And, if applicable, disconnect any other processes from MySQL. 2 Stop the MySQL service on Windows with the command line: net stop mysql. 3 Edit the text file innodb_data_file_path in my.ini.
Embedded Database Sizing | Database Management For Linux 1 Shut down all applications and application server. And also disconnect any other process connected to MySQL.
Database Backup/Restoration | Database Management innodb_data_file_path = d:/work/oware3rd/mysql/ibdata/ ibdata1:600M:autoextend:max:2000M To recreate database after modifying config file, use the following command from the application server: loaddb -q -d -m Syntax details: innodb_data_file_path = pathtodatafile:sizespecification;pathtodatafile:sizespecification;... innodb_data_file_path = ...
Database Backup/Restoration | Database Management MySQL Backup/Restore Follow these instructions to back up and restore the embedded MySQL database using native MySQL utilities on a command line. Backup Open a command shell (Start > Run cmd, in Windows), and then type the following at the prompt. By default, the primary database is owbusdb, and owmetadb includes metainformation. For the web server, back up lportal and synergy too (the latter contains multitenancy information).
Distributed Database Upgrades | Database Management mysql -u root --password=dorado owmetadb < owmetadb.mysql mysql -u root --password=dorado owbusdb < owbusdb.mysql mysql -u root --password=dorado lportal < lportal.mysql mysql -u root --password=dorado synergy < synergy.mysql You can configure the embedded MySQL database with multiple instances that fail over.
MySQL Replication | Database Management still on master mysql server, grand privileges for created user: mysql>GRANT ALL PRIVILEGES ON *.* TO 'repluser'@'10.35.35.170'; mysql>GRANT ALL PRIVILEGES ON *.* TO 'repluser'@'10.35.35.174'; on master mysql server (10.35.35.170) grant user permissions for replication: mysql> GRANT REPLICATION SLAVE ON *.* TO 'repluser'@'10.35.35.
MySQL Replication | Database Management log into slave mysql server (10.35.35.174) and create users: "mysql -u root --password=dorado mysql> CREATE USER 'repluser'@'10.35.35.170' IDENTIFIED BY 'slavepass'; mysql> CREATE USER 'repluser'@'10.35.35.174' IDENTIFIED BY 'slavepass'; still on slave mysql server, grand privileges for created user: mysql>GRANT ALL PRIVILEGES ON *.* TO 'repluser'@'10.35.35.170'; mysql>GRANT ALL PRIVILEGES ON *.* TO 'repluser'@'10.35.35.
MySQL Server Configuration File Examples | Database Management MySQL Server Configuration File Examples The my.cnf files optimize MySQL installations for the database size you configure at installation time. Refer to the OpenManage Network Manager User Guide for more suggestions about re/sizing your MySQL database, as well as starting, stopping and performance tuning it. Several my.cnf files and example *.ini files (my-small.ini, my-large.
MySQL Server Configuration File Examples | Database Management set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=256M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=512M set-variable = innodb_additional_mem_pool_size=20M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=30 8GB example: # The MySQL server [mysqld] port=
MySQL Server Configuration File Examples | Database Management #set high enough for 1 second worth of operations; maybe 1% of total (8M for 8G, 16 for 16, etc) set-variable = innodb_log_buffer_size=8M #default of 1 is slow. 2 uses the OS cache so only lose data on OS crash (power outage, etc). MUCH FASTER.
MySQL Server Configuration File Examples | Database Management # Uncomment the following if you want to log updates #log-bin innodb_locks_unsafe_for_binlog=1 set-variable = innodb_buffer_pool_size=2048M #larger sizes help with write intensive workloads and large data sets, but usually not needed above 512M set-variable = innodb_log_file_size=256M #set high enough for 1 second worth of operations; maybe 1% of total (8M for 8G, 16 for 16, etc) set-variable = innodb_log_buffer_size=12M #default of 1 is slow.
MySQL Server Configuration File Examples | Database Management set-variable = table_cache=1024 set-variable = sort_buffer=2M set-variable = record_buffer=2M set-variable = thread_cache=8 # Try number of CPU's*2 for thread_concurrency set-variable = thread_concurrency=8 set-variable = myisam_sort_buffer_size=64M server-id = 1 transaction-isolation = READ-COMMITTED # Uncomment the following if you want to log updates #log-bin innodb_locks_unsafe_for_binlog=1 set-variable = innodb_buffer_pool_si
MySQL Server Configuration File Examples | Database Management query_cache_type=1 #caches often used queries.
MySQL Server Configuration File Examples | Database Management set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=30 NOTE: Best practice is to archive the modified database sizing file somewhere safe. Upgrading or patching your installation may overwrite your settings, and you can simply copy the archived file to the correct location to recover any configuration you have made if that occurs. 164 OMNM 6.5.
E Oracle Database Management Installing Oracle – 166 Oracle Database Sizing – 171 Oracle Backup/Restore – 172 Database Recovery Procedures – 174 Oracle Failover – 174 OMNM 6.5.
Installing Oracle | Oracle Database Management Installing Oracle Before running this application’s Oracle setup, you must first install Oracle and create the database instance. The following is a set of basic guidelines for installing Oracle. This may not describe the optimum configuration for every environment, but it provides a simple example of how to install Oracle in a basic configuration.
Installing Oracle | Oracle Database Management In the portal-ext.properties file located in ../oware/synergy/tomcat-7.0.40/webapps/ROOT/ WEB-INF/classes, search for jdbc.default.url and set the property in this format jdbc:oracle:thin:@address:port/pdbname. In the installed.properties file located in ../owareapps/installprops/lib, search for com.dorado.jdbc.database_name.oracle and set the property in this format @address:port/ pdbname.
Installing Oracle | Oracle Database Management 2 Increase Oracle's default processes limit: SQL> alter system set processes=300 scope=spfile; System altered. If you do not set this limit to 300, you may get the following error while running the dbpostinstall command. ORA-12519, TNS:no appropriate service handler found 3 Set Oracle to use case insensitive passwords: SQL> alter system set SEC_CASE_SENSITIVE_LOGON = FALSE; System altered. 4 Change Oracle's default HTTP port: SQL> call dbms_xdb.
Installing Oracle | Oracle Database Management 2 To successfully install against an Oracle server running on a Windows Server Operating System you must create a user with DBA privileges on the Oracle server: sqlplus system/ create user foo identified by foo; grant dba to foo; exit You can then run loaddb from application server as described below.
Installing Oracle | Oracle Database Management Running dbpostinstall 4 After running loaddb, you must seed the database with all required information. This is based on what software is installed with your package. Running the dbpostinstall command on the (primary) application server examines your package and seeds all appropriate information.
Oracle Database Sizing | Oracle Database Management Other Best Practices • • Set CURSOR_SHARING=FORCE reduces CPU use. Increased log size from 3 groups of 52M, to 4 groups of 500M apiece. This definitely decreased the log_file_sync wait event, improving throughput. Oracle Database Sizing Sizing an Oracle database is part of its installation. Even before installing Oracle you should consult your DBA to estimate how big your data is going to be and size the database accordingly.
Oracle Backup/Restore | Oracle Database Management 4 Calculate number of bytes for each class. 5 Sum calculated byte count to determine total datafile size (convert to mega- or gigabytes, if needed) NOTICE Best practice is to size your database at least 20% larger than calculated above. Oracle Backup/Restore For Oracle fault tolerance, back up your Oracle database. To do this, we recommend using Oracle’s Recovery Manager (RMAN) backup utility.
Oracle Backup/Restore | Oracle Database Management You may encounter an ORACLE 2291 error when using command line imp. For example: . importing table "RCC_TASK_USAGE_ENTITY" IMP-00019: row rejected due to ORACLE error 2291 IMP-00003: ORACLE error 2291 encountered ORA-02291: integrity constraint (REDCELL.FKE609020E14863754) violated parent key not found The workaround for this is to find the foreign key reference table and import the parent table first then re-import the problematic table.
Database Recovery Procedures | Oracle Database Management Database Recovery Procedures You can recover Oware’s backed up databases if your system fails. The quality of recovery naturally depends on the frequency and integrity of the database backups. The more frequent the backups, the less data loss occurs. Since Oware supports multiple database types, the method used to recover the databases differs according to type. If RMAN is in place, use it for recovery.
Oracle Failover | Oracle Database Management Oracle RAC installation.properties File The following differs slightly for each Oracle versions. For example, 10G RAC uses VIP; 11G RAC uses Scan (and can also use VIP). Therefore, the installation.properties file needs to be like one of the following options: Option 1 com.dorado.oracle.rac.connect.url=@(DESCRIPTION=(ADDRESS_LIST=\ (ADDRESS=(PROTOCOL=TCP)(HOST=vip1)(PORT=1521))\ (ADDRESS=(PROTOCOL=TCP)(HOST=vip2)(PORT=1521))\ )\ (FAILOVER=on)(LOAD_BALANCE=on)(C
Oracle Failover | Oracle Database Management Example Tune-up Example setup: 10.17.7.10 cbj-ip-do-orac01-priv 10.17.7.11 cbj-ip-do-orac02-priv g2: flags=1000843 mtu 1500 index 4 inet 10.17.7.10 netmask ffff0000 broadcast 10.17.255.255 Tasks before making the change to jumbo frames for example servers g1 and g2: Verify: 1 Check all devices between databases support jumbo frames. 2 Identify if failover/bonding/teaming is active for your g2 (g1, for example).
F Using SSL Certificate Enabling HTTPS Using a Self-Signed SSL Certificate – 178 Enabling HTTPS Using a CA-Issued SSL Certificate – 179 Place SSL Certificates in the following location: %OWARE_USER_ROOT%\ oware\synergy\tomcat-7.0.70\bin\certs They will be backed up during future upgrades from this location. OMNM 6.5.
Enabling HTTPS Using a Self-Signed SSL Certificate | Using SSL Certificate Enabling HTTPS Using a Self-Signed SSL Certificate 1 Edit script: ‘makecert.sh’ (in directory: \oware\synergy\tomcat-7.0.70\bin\certs) a. Edit the group of lines starting with ‘KT_’ and set appropriate values for: ‘KT_HOSTNAME’ and ‘KT_IPADDRESS’ b. Changing values of other ‘KT_’ variables is optional 2 Edit script: ‘setenv.bat’ (Windows) or ‘sentenv.sh’ (Linux) (in directory: \oware\synergy\tomcat-7.0.
Enabling HTTPS Using a CA-Issued SSL Certificate | Using SSL Certificate d. Click “Browse...” button to place certificate in store: “Trusted Root Certification Authorities” e. Click “Finish” to install the certificate [Linux ONLY]. f. Consult Linux specific instructions to install the certificate file located in directory: $OWARE_USER_ROOT/oware/synergy/tomcat-7.0.70/bin/certs/selfsigned.cer 7 Close ALL open browser windows BEFORE opening application.
Enabling HTTPS Using a CA-Issued SSL Certificate | Using SSL Certificate 180 OMNM 6.5.
Index A Acrobat Reader, 68 Administration Basics, 148 appserver, 60 Automatically Starting Servers, 70 Avoiding long timeouts, 56 C Change the IP address, 75 Changing the system time, 76 Cluster Constraints, 108 Cluster Multicast, 131 clustered Application, 21 Clustered Server Installation Checklist, 133 Clustering, 103 Configuration, 119 Constraints, 108 Implementing, 104 Installation, 119 Mediation, 104 command line installation, 37 Command Line, Startup parameters, 69 Config Server, 118 Functionality, 1
M P Mediation Clustering, 104 disabling, 62 High availability, 22 No Multicast, 111 Pairs, 129 Polling, 131 Properties, 61 Server installation, 56 Startup parameters, 130 migrating versions, 39 Migration, Operating Systems, 94 Minimum Hardware, 15 missing, users, 80 Modified Files, 37 MPING, 113 Multiple NICs, 32-35 my.cnf, 152 my.
