C H A P T E R 4 Authentication In Fabric Manager - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

Fabric Manager Authentication Overview
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
Figure 4-1
Fabric Manager
Administrators launch Fabric Manager Client and select the seed switch that is used to discover the
fabric. The user name and password used are passed to Fabric Manager Server and used to authenticate
to the seed switch. If this user name and password are not a recognized SNMP user name and password,
either Fabric Manager Client or Fabric Manager Server opens a CLI session to the switch (SSH or Telnet)
and retries the user name/password pair. If the user name and password are recognized by the switch in
either the local switch authentication database or through a remote AAA server, then the switch creates
a temporary SNMP user name that is used by Fabric Manager Client and server.
You may encounter a delay in authentication if you use a remote AAA server to authenticate Fabric
Note
Manager or Device Manager.
You must allow CLI sessions to pass through any firewall that exists between Fabric Manager Client and
Note
Fabric Manager Server. See the
We recommend that you use the same password for the SNMPv3 user name authentication and privacy
Note
passwords as well as the matching CLI user name and password.
Cisco MDS 9000 Family Fabric Manager Configuration Guide
4-2
Fabric Manager Authentication Example
Fabric Manager Server
and Performance
Manager
Client
Local database
AAA server
"Running Fabric Manager Behind a Firewall" section on page
Chapter 4 Authentication in Fabric Manager
Fabric
OL-17256-03, Cisco MDS NX-OS Release 4.x
2-40.