cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1448
Views
0
Helpful
1
Replies

Cisco Ironport Cluster feature

michelegarribba
Level 1
Level 1

Hi all,

 

i have 2x ESA and thinking about clutering them. Version is 8.5.6 so no need of feature key to cluster the configuration.

My doubt is that my ESA are alredy configured as per mail flow policies, sender groups, routing smtp routes and so on.

What is the impact of activating the cluster feature with the clusterconfig commmand and create a cluster? Do i loose all the configuration alredy done?

More my 2xESA are already centralized to an SMA for reporting, pov and spam quaratines. Any impact?

 

thanks

smaikol

1 Accepted Solution

Accepted Solutions

Robert Sherwin
Cisco Employee
Cisco Employee

Correct - as of 8.5, the cluster configuration is available without need for the additional license/feature key.  You should simply be able to log in on the CLI and run clusterconfig.

When you create the cluster --- you'll create on ESA_A.  Once you join ESA_B to ESA_A in cluster, it will overwrite the configuration on ESA_B --- and will have matching configuration of ESA_A.  On ESA_B, if you had special routing, mail flow policies, or other configuration differences, you would need to go back through and re-configure those at machine level.

As for ESA > SMA, it would not have any impact.  ESA_A and ESA_B will still report individually to the SMA.

-Robert

View solution in original post

1 Reply 1

Robert Sherwin
Cisco Employee
Cisco Employee

Correct - as of 8.5, the cluster configuration is available without need for the additional license/feature key.  You should simply be able to log in on the CLI and run clusterconfig.

When you create the cluster --- you'll create on ESA_A.  Once you join ESA_B to ESA_A in cluster, it will overwrite the configuration on ESA_B --- and will have matching configuration of ESA_A.  On ESA_B, if you had special routing, mail flow policies, or other configuration differences, you would need to go back through and re-configure those at machine level.

As for ESA > SMA, it would not have any impact.  ESA_A and ESA_B will still report individually to the SMA.

-Robert