Cisco Cisco Prime Network Registrar 8.3 문제 해결 가이드

Cisco Prime Network Registrar IPAM 8.3 Disaster Recovery Guide - Using MySQL Database Replication

1 Introduction

1.1 Overview

NOTE: This document describes functionality that is available only in Cisco Prime Network

Registrar IPAM 8.0 and higher. In addition, this support exists for environments that are

running IPAM 8.3 Agents.
NOTE: This document describes Disaster Recovery support for the IPAM Executive running

on supported Unix-based platform, Red Hat Linux. Disaster Recovery for the IPAM

Executive is not supported on Microsoft Windows platforms.
Environmental disasters, equipment failure, and power outages are scenarios that

can completely halt a company’s IT infrastructure. As part of the IPAM

comprehensive Business Continuity and Disaster Recovery (DR) solution,
IPAM offers a complete set of script utilities that enables customers to easily

transition to backup systems during an emergency - thus preventing negative

impact to normal business operations.
NOTE: IPAM 8.3 and later versions will not support Solaris. Refer to earlier versions of

IPAM documents if you want to use IPAM with Solaris support.

1.2 Major Functions

As part of the standard installation, IPAM already provides facilities for DHCP

Failover and Secondary DNS server configuration. These facilities ensure

continuous operation of these critical network services. During a DR event in

which the IPAM Executive is affected, the DHCP/DNS services continue to run

autonomously, so end clients will continue to operate. However, if the Executive

is unavailable, then configuration changes for DHCP/DNS cannot be made. To

address this need, the IPAM Executive can be configured for redundancy using

the DR guidelines and scripts described herein.

The following core functionality is provided with IPAM Disaster Recovery (DR)

support:

• Ability to mirror a Production Executive database
• Switch remote agents between Production and DR executives