Cisco Cisco Unified Operations Manager 8.5 White Paper

Deployment Guide

Page 45 of 65

Step 1. Enter the BIOS Configuration and Setup screen by powering up the server and pressing F1 during system

startup.

Step 2. Go to Advance Setup > Advance Processor Option > Hyperthread.

Step 3. Select Disabled.

Step 4. Press Esc to return to the main menu.

Step 5. Select Save Settings, and press Enter.

Step 6. Select Exit Setup, and press Enter to continue the reboot process with hyperthreading disabled.

Cold Standby/Redundant Deployments

You can use two servers and achieve a cold standby configuration. One Operations Manager server is used as the

active server and the other server is left on cold standby and periodically synchronized with the active server using

the servers’ DCRs. When the active server is taken offline, the cold server will have an up-to-date inventory and can

quickly be made active.

Preparing for Redundancy

This section describes some prerequisites for redundant Operations Manager configurations.

The first step is to have two identical servers available for configuration. One server acts as the active server and the

second as the standby server. Refer to the Operations Manager installation guide for the hardware specification of

these servers. It is recommended that these servers connect to the network through redundant paths. This helps

ensure that a failure in one part of the network that affects the active server does not also affect the connectivity of

the standby server.

Setting Up Redundancy

Redundant deployment can be considered in four parts:

1. Setting up the active Operations Manager server.

2. Setting up the standby Operations Manager server by creating a baseline.

3. Replicating the active Operations Manager server configuration on the standby Operations Manager server on

an ongoing basis.

4. Tasks to be performed in case of failure of the active server.

Setting Up the Active Operations Manager Server

This is the same as setting up a standalone Operations Manager server. Typical tasks include:

●

Setting up users and associating roles

●

Providing a device list by manually adding devices or syncing up with LMS Device Credential Repository or

discovering the network using a seed device

●

Setting up the polling intervals based on your monitoring requirements (the default is 4 minutes)

●

Creating phone status tests

●

Creating synthetic tests

●

Creating node-to-node tests

●

Setting up SRST polling by creating SRST tests

●

Enabling performance polling

●

Setting up notification profiles for northbound notifications

●

Configuring Service Monitor to forward traps to Operations Manager