Cisco Cisco Email Security Appliance X1050 Troubleshooting Guide
What is centralized management for and how can a
centralized management cluster be created?
centralized management cluster be created?
Document ID: 118503
Contributed by Andrew Wurster and Enrico Werner, Cisco TAC
Engineers.
Oct 14, 2014
Engineers.
Oct 14, 2014
Contents
Introduction
What is centralized management for and how can a centralized management cluster be created?
Background
Requirements to Remember
Solution
Cautionary Steps to Remember
Related Information
What is centralized management for and how can a centralized management cluster be created?
Background
Requirements to Remember
Solution
Cautionary Steps to Remember
Related Information
Introduction
This document describes what centralized management on the Email Security Appliance (ESA) stands for and
how a centralized management cluster can be created.
how a centralized management cluster can be created.
What is centralized management for and how can a
centralized management cluster be created?
centralized management cluster be created?
Background
The centralized management feature allows you to manage and configure multiple appliances at the same
time, to provide increased reliability, flexibility, and scalability within your network, allowing you to manage
globally while complying with local policies. A cluster consists of a set of machines with common
configuration information. Within each cluster, the appliances can be further divided into machine groups,
where a single machine can be a member of only one group at a time. Clusters are implemented in a
peer−to−peer architecture − with no master/slave relationship. You may log into any machine to control and
administer the entire cluster or group. This allows the administrator to configure different elements of the
system on a cluster−wide, group−wide, or per−machine basis, with based on their own logical groupings.
time, to provide increased reliability, flexibility, and scalability within your network, allowing you to manage
globally while complying with local policies. A cluster consists of a set of machines with common
configuration information. Within each cluster, the appliances can be further divided into machine groups,
where a single machine can be a member of only one group at a time. Clusters are implemented in a
peer−to−peer architecture − with no master/slave relationship. You may log into any machine to control and
administer the entire cluster or group. This allows the administrator to configure different elements of the
system on a cluster−wide, group−wide, or per−machine basis, with based on their own logical groupings.
Requirements to Remember
All machines must have IP connectivity.
•
If using hostnames, make sure everything resolves correctly − with matching forward "A" and reverse
"PTR" DNS records.
"PTR" DNS records.
•
There must be connectivity on either TCP port 22 SSH or 2222 Cluster Communication Service
(CCS) or the customized port of your choice.
(CCS) or the customized port of your choice.
•
All appliances must have the exact same AsyncOS version and be of the same product family (NOTE:
C and X series appliances are interoperable).
C and X series appliances are interoperable).
•
All appliances must also have the "Centralized Management" feature key below version 8.x.
•
You will need command−line access as the cluster management tool "clusterconfig" is not available in
the GUI.
the GUI.
•