Best Practices For Discovering A Fabric; Setting Up Discovery For A Fabric - HP Cisco MDS 9216 - Fabric Switch Configuration Manual

Chapter 4 Authentication in Fabric Manager
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 m d s f e e d b a c k - d o c @ c i s c o . c o m

Best Practices for Discovering a Fabric

Fabric Manager Server monitors multiple physical fabrics under the same user interface. This facilitates
managing redundant fabrics. A licensed Fabric Manager Server maintains up-to-date discovery
information on all configured fabrics so device status and interconnections are immediately available
when you launch Fabric Manager Client.
If the Fabric Manager Server's CPU usage exceeds 50 percent, it is recommended that you switch to a
Caution
higher CPU-class system. For more information on recommended hardware, see the
section on page
We recommend you use these best practices for discovering your network and setting up Performance
Manager. This ensures that Fabric Manager Server has a complete view of the fabric. Subsequent Fabric
Manager Client sessions can filter this complete view based on the privileges of the client logging in.
For example, if you have multiple VSANs in your fabric and you create users that are limited to a subset
of these VSANs, you want to initiate a fabric discovery through Fabric Manager Server using a network
administrator or network operator role so that Fabric Manager Server has a view of all the VSANs in the
fabric. When a VSAN-limited user launches Fabric Manager Client, that user sees only the VSANs they
are allowed to manage.
Note Fabric Manager Server should always monitor fabrics using a local switch account, do not use a AAA
(RADIUS or TACACS+) server. You can use a AAA user account to log into the clients to provision
fabric services. For more information on Fabric Manager Server fabric monitoring, see the
a Fabric Manager Server Fabric" section on page

Setting Up Discovery for a Fabric

To ensure that Fabric Manager Server discovers your complete fabric, follow these steps:
Step 1 Create a special Fabric Manager administrative user name in each switch on your fabric with network
administrator or network operator roles. Or, create a special Fabric Manager administrative user name
in your AAA server and set every switch in your fabric to use this AAA server for authentication.
Verify that the roles used by this Fabric Manager administrative user name are the same on all switches
Step 2
in the fabric and that this role has access to all VSANs.
Launch Fabric Manager Client using the Fabric Manager administrative user. This ensures that your
Step 3
fabric discovery includes all VSANs.
Set Fabric Manager Server to continuously monitor the fabric.
Step 4
See the
Repeat
Step 5
.
OL-8007-10, Cisco MDS SAN-OS Release 3.x
2-18.
"Managing a Fabric Manager Server Fabric" section on page
Step 4 for each fabric that you want to manage through Fabric Manager Server.
Best Practices for Discovering a Fabric
3-3.
Cisco MDS 9000 Family Fabric Manager Configuration Guide
"Before You Install"
"Managing
3-3.
4-3