Cisco Cisco Fabric Manager Release 5.0 White Paper

Page of 34
C H A P T E R
S e n d   d o c u m e n t a t i o n   c o m m e n t s   t o   f m - d o c f e e d b a c k @ c i s c o . c o m
2-1
Cisco Fabric Manager Server Federation Deployment Guide
OL-21765-01, Cisco MDS NX-OS Release 5.x
2
Deploying Cisco Fabric Manager Server 
Federation
Fabric Manager Server clustering provides high availability, scalability and easy manageability of data 
and programs running within the cluster. The core of server cluster includes several functional units such 
as Fabric Manager Server, embedded web servers, database, and Fabric Manager Client accesses the 
servers. Three stages in the deployment cycle include planning for deployment, installing the federated 
servers and managing the federated servers. 
This chapter contains the following sections:
Planning for Deployment
To design a solution, including determining the structure, capabilities, and architecture for a site, you 
might want information that helps you to structure the server topology, plan authentication methods, 
determine which capabilities of Server Federation you want to take advantage of, and that helps you to 
plan for those capabilities and to tailor the solution to your organization's requirements. 
When planning for a clustered environment, consider the following factors:
Geographic locations of the data centers that are participating in the federation. 
Total number of ports or end devices for all the existing and potential fabrics in each data center (to 
determine the workload).
The Fabric Manager should be placed close to the fabrics it manages in order to reduce the latency 
in SNMP request and response.
One Fabric Manager will be able to manage 150,000 ports.
Dedicate one separate physical server for the database.
Dedicate one separate physical server for each Fabric Manager Server in the federation.