Advanced MDS SAN Management: BRKSAN-2891

Advanced MDS SAN
Management
BRKSAN-2891
BRKSAN-2891
14573_05_2008_c1 © 2008 Cisco Systems, Inc. All rights reserved. Cisco Public 2
© 2006, Cisco Systems, Inc. All rights reserved. 1

Presentation_ID.scr
Session Objectives
Cisco Fabric Manager Overview

Fabric Manager Deployment Best Practices
Review Install Options
SAN Monitoring Details
Overview of Performance Monitoring and
Reporting Features
BRKSAN-2891
Fabric Manager
Overview
BRKSAN-2891

Presentation_ID.scr
Fabric Manager Evolution
Releases Representing Major FM Architecture Changes
JBOSS, FM
Client and Performance Standalone,
Server in a FM Split Collection Oracle HSQLDB
Single into Client and Web 10g Replaced with Performance
Application and Server Client Option PostgreSQL DB Enhancements
FM 1.0 FM 1.3 FM 2.0 FM 3.1 FM 3.2 FM 3.3

December 2002 December 2003 October 2004 January 2007 October 2007 March 2008
BRKSAN-2891
Cisco Fabric Manager Components

Fabric Manager server
Centralized services
Fabric Manager client
Fabric topology view
Fabric management
Cisco Fabric
Device Manager client Manager Server
Device specific view

Device management
Web client
Cisco Fabric
Historical performance reports Manager Client
(FM/DM/Web Client)
Operational views
Cisco Fabric Manager Standalone
BRKSAN-2891

Presentation_ID.scr
Fabric Manager Server
Centralized management services

Continuous health monitoring
Multiple fabric management
Performance monitoring
Prediction analysis
Roaming user profiles
Published database schema
BRKSAN-2891
Fabric Manager Client

Real-time fabric
topology views
Fabricwide
configuration
wizards
Fibre Channel
troubleshooting
tools
Health and
configuration
analysis tools
BRKSAN-2891

Presentation_ID.scr
Device Manager
Standalone
application
communicates
directly with the
device over SNMP
Graphical
representation of
the switch chassis
Configure device-
specific functionality
Real-time statistics
BRKSAN-2891
Fabric Manager Server License Package

FM Server License Provides Additional Functionality
with No Further Software Installation Required
Multiple fabric management
Historical performance monitoring
Thresholds based on performance monitoring
Performance prediction
Summary and drill-down reports
Continuous health and event monitoring
Roaming user profiles
Cisco Fabric Analyzer integration
BRKSAN-2891

Presentation_ID.scr
Web Client
Requires FMS license to
be fully operational
Operations view
Historic performance
report views
Thresholds based on
collected performance
data
Prediction capabilities
based on collected
performance data
Inventory
Syslog collector
Custom reports
Schedule report
generation
BRKSAN-2891
Fabric Manager Standalone:

3.2 and Later
Fabric Manager server and client
run in a single process
Switch events collected only while
the application is running
FMS license is not required, but if
present, multiple fabrics can be
opened in the FM client
No historic performance statistics
collection
No Web client
Cisco Fabric Manager
Optimizes host resources FM/DM Clients
BRKSAN-2891

Presentation_ID.scr
FMS Architecture 3.2 and Above
Red Hat JBoss—provides clustering, load balancing, distributed
deployment features, and future release of FMS plans on taking
advantage of these capabilities
Service Oriented Architecture (SOA)
Application built as services (J2EE)
Loosely coupled software components
PostgreSQL/Oracle 10g (RDBMS)
Web Server
Role-Based Access Control and Licensing
Componentization of FM Server J2EE Services
Discovery Inventory Interfaces
Event Performance RDBMS

Users and Roles
Management Collection
SME ACL Security

...
Transport : Telnet, SSH, SNMP
BRKSAN-2891
FM Deployment
Best Practices
BRKSAN-2891

Presentation_ID.scr
Fabric Manager Server (FMS)
Deployment
Dedicated server
Windows 2000, Windows 2003,
Windows XP, Solaris 8/10, Red Hat Data Center/
Private Network
Enterprise Linux AS Release 4 (2.6
Kernel), VMware Server 1.0 (Windows)
2 GHz or above processor
with 2 GB RAM
Cisco Fabric
10 GB storage Manager Server
Dual NIC—private/public network AAA Server
Corporate/
Management network Public Network
connectivity—dedicated
VLAN preferred Cisco Fabric
Manager Client
SNMP proxy (FM/DM/Web Client)
FMS server to be deployed in

proximity to the MDS switches
BRKSAN-2891
FMS Sizing Parameters

Monitoring
Discovery
Configuration
Events
Performance collection
Flows
Errors and discards
Number of Ports Managed by an FM Sever Instance

FM3.2 FM3.3
FM1.0–FM3.1 PostgreSQL/ PostgreSQL/
Oracle 10g Oracle 10g
Monitoring Only Under 1000 10,000 10,000
Monitoring +
Under 1000 5000 10,000
Performance Collection
BRKSAN-2891

Presentation_ID.scr
FMS Deployment Scenarios
FMS Servers Recommended Based on
Number of Ports Managed
Ports per Fabric Fabric A Fabric B
Up to 5000 Ports Single FMS Server
5001–10,000 Ports FMS Server A FMS Server B
A fabric to be managed by a single dedicated server

For fabrics spanning multiple data centers, a single instance of
FMS server at one of the locations, and good network connectivity
to minimize SNMP packet loss
Currently FM does not support performance collection and
monitoring to be split across servers
BRKSAN-2891
AAA
Staring with SAN-OS 3.1(1) Fabric
Manager has a user database
independent of the MDS users Data Center/
Private Network
FM users can be “network-admin”
or “network-operator”
FM User ID is required to log into
FM Client and Web Client starting Cisco Fabric
with 3.1(1) Manager Server
Device Manager login uses switch AAA Server

credentials Corporate/
Public Network
FM users can be authenticated
by a AAA server, similar to how
Cisco Fabric
MDS switch users are Manager Client
authenticated by AAA (FM/DM/Web Client)
MDS can be used as a proxy
BRKSAN-2891

Presentation_ID.scr
Fabric Manager—Communications
DM communicates directly
with MDS using SNMP
Device FM Client <-> MDS : SNMP
FM/DM perform all Manager
configuration changes FM Client <-> MDS : SNMP

in real time talking to FM Client
the switch directly FM
Clie
n t<
using SNMP ->
SNMP
FM
Se
rve
r:
J av
FM Client talks to FM aR
MI
Server using Java RMI Web Client <-> FM Server : HTTP

Web
Client
Web Client is primarily a
read only tool and talks to Cisco Fabric
Manager Server
the FM server over HTTP
BRKSAN-2891
SNMP Proxy
In firewall situations, enable
“SNMP Proxy” so that all Firewall
SNMP calls to the MDS from
Device Manager and Fabric
Manager are tunneled via the
FM Server
DM
SNMP
SN
When SNMP Proxy is enabled, Device Manager MP
C alls
to M
software upgrade option on DS
FM Clients working from

FM Client SNMP Calls to MDS
behind the firewall will not
FM Client <-> FM Server : Java RMI
work, as that functionality
depends on FM client FM Client
Server Also Acts as
establishing a direct SNMP Proxy
connection with the switch,
and CLI output parsing
BRKSAN-2891

Presentation_ID.scr
SNMP Proxy
Firewalls require
SNMP proxy
Configure “SNMP proxy” so
that SNMP calls to the MDS
from Device Manager and DM
SNMP
Fabric Manager are tunneled Device Manager
SN
MP
C alls
via the FM Server to M
DS
Configure the MDS

management port to receive FM Client SNMP Calls to MDS
“SNMP” traffic only from the FM Client <-> FM Server : Java RMI
designated FM server—
Cisco Fabric
prevents unauthorized FM Client
Manager Server
instances of Fabric Manger with SNMP Proxy
servers
BRKSAN-2891
MDS/Fabric Manager—Protocols
Communication Type Port(s) Used
FM Server SSH 22 (TCP)

Telnet 23 (TCP)
HTTP 80 (TCP)
TFTP 69 (UDP)
Syslog 514 (UDP)
FM Server SNMP Trap 2162 (UDP)
SNMP UDP (Random)/9198 TCP—SNMP Proxy
JAVA RMI 9099, 9100 (TCP)
FM Client SNMP UDP (Random)/9001 TCP—SNMP Proxy
JAVA RMI Available Port 19199–19399 (TCP)
DM Client SNMP Trap Available Port 1163–1170 (UDP)
SNMP UDP (Random)/9198 TCP—SNMP Proxy
BRKSAN-2891

Presentation_ID.scr
FMS Behind a Firewall—3.1 and Earlier
Protocols and ports used for FM client and FM server to
communicate
Firewall
FM Client 1 FM Server MDS

Open RMI
9099 Telnet 23
Use 9100 SSH
Close 9099
22
Open 9100
TFTP 69
9100 Syslog
Open 9101for Events
514
9101 HTTP 80
Open SNMP Proxy
9198 SNMP
9198 161
2162 SNMP TRAPS

FM Client 2
Open RMI
9099
Use 9102
Close 9099
Open 9102
9102
Open 9103for Events
9103
Open SNMP Proxy
9198 9198
BRKSAN-2891
FMS Behind a Firewall—3.2 and Above

FM Client initiates communication
with FM Server on port 9099 for
Java Naming Directory and Firewall FM Server
Interface (JNDI) lookup MDS
FM Server Bind Port
9099 Telnet
FM Server directs client to 1098, Java RMI Port SSH
23
1098 22
JBoss directs the request to the TFTP
appropriate service 69
RMI Object Port 4444 Syslog 514
Ports 4444, 4445, 8009, 8092, Server Bind Port 4445 HTTP 80
and 8093 are used by JBoss to AJP Connector 8009 SNMP 161
Server Bind Port SNMP TRAPS
monitor connectivity and for 8092 2162
Server Bind Port
JMS to send messages to the 8093
FM Client
SNMP Proxy 9198
SNMP proxy uses port 9198 Web Service Port 8083
HTTP Connector
Web Service Port 8083 used for 80
Web Services API, XML over
HTTP
HTTP port 80
BRKSAN-2891

Presentation_ID.scr
Aliases
Device Alias FC Alias/Zone Alias
Unique name across the Limited to a VSAN

entire physical fabric
Part of the zoning
User-friendly name for a configuration and limited
port WWN that can be to zone configuration
used in all configuration
commands like FCNS,
Zone, FC Ping, FC Trace
Route, and IVR
Device Aliases Are Distributed to All Switches in a

Fabric Using the Coordinated Distribution Mechanism
Using the Cisco Fabric Services (CFS)
Recommend Using Device Aliases
BRKSAN-2891
Enclosure
Enclosure
Names Auto
Generated
by FMS
Enclosures is a Fabric Manager functionality and is not supported by SAN-OS

Devices with multiple HBAs may be represented as individual devices by
Fabric Manager
By default, enclosures names are generated by the FM Server based on the
alias or WWN OUI
Enclosure name provides the ability to group end devices in a single
enclosure to have them represented by a single icon on the Fabric Manager
topology view
An enclosure name can be manually created based on the alias name,
by selecting one or more rows and using the “Alias Æ Enclosure” option
BRKSAN-2891

Presentation_ID.scr
Enclosure Example—Step 1
Assign Device Aliases
BRKSAN-2891
Select Alias Æ Enclosure button on top of the End Devices table—
an enclosure is generated based on the Alias name using Java
Regular Expressions
For more details about Java Regular Expressions, please refer to:
http://java.sun.com/docs/books/tutorial/essential/regex/
BRKSAN-2891

Presentation_ID.scr
Enclosure name generated based on Alias
All Disks for

Storage
Represented
as Single
Entity in
Topology Map
BRKSAN-2891
FM Server Trap Registration

MDS can forward events up
to 10 destinations
At the time of fabric
discovery, FM Server
Device Manager
registers with each MDS in
the fabric as a recipient of
SNMP events
Device Manager can also be
a recipient of SNMP events FM Client Cisco Fabric
Manager Server
SNMP events can be
forwarded to a NOC, and
destinations can be
configured via GUI or CLI
BRKSAN-2891

Presentation_ID.scr
FM Client—No Traps
Status Message
“No Traps” Would
Appear Under Two
Conditions:
FM Server failed to
register with the switch
as the list of 10
destinations is full
FM Server failed to
query its IP address,
this can be addressed
by providing an IP
address in the Web
client under
Admin/Configure/
Preferences/
trap.registeraddress,
this a rare occurrence
BRKSAN-2891
Clean Up Trap List
Identify Valid Destinations and

Delete Unwanted Entries from
GUI/CLI
# show snmp host

(config)# no snmp host 20.1.1.2 traps version v1
BRKSAN-2891

Presentation_ID.scr
Manage Continuously
FM Server loads a fabric information the first time a client opens a fabric
When the last client closes, FM Server closes the fabric, and any events
received from the switches will be ignored
For FM Server to not close the fabric information when the last client
disconnects from the server, mark “Manage Continuously” next to the
fabric in the Server Admin dialog
Prior to release 3.2 this was called “Monitor Continuously”
3.2 and above release provides three options
Unmanage: Stop managing the fabric
Manage: Keep fabric open as long as client is connected
Manage Continuously: Always keep the fabric information open
BRKSAN-2891
FM Backup—3.1 and Before
Regular backup of FM data highly recommended

List of files to backup
C:\Program Files\Cisco Systems\MDS 9000\*.properties
C:\Program Files\Cisco Systems\MDS 9000\*.log
C:\Program Files\Cisco Systems\MDS 9000\bin\*
C:\Program Files\Cisco Systems\MDS 9000\conf\*
C:\Program Files\Cisco Systems\MDS 9000\db\*
C:\Program Files\Cisco Systems\MDS 9000\log\*
C:\Program Files\Cisco Systems\MDS 9000\pm\*
C:\Program Files\Cisco Systems\MDS 9000\reports\*
BRKSAN-2891

Presentation_ID.scr
PostgreSQL DB—FMS Backup
By default, FM 3.2 and above uses PostgreSQL DB
FM relies on vendor tools to backup and restore FMS database
Contents of pgbackup.bat file, under C:\Program Files\Cisco Systems\MDS 9000\bin
set PGDIR=C:\Program Files\PostgreSQL\8.2. PostgreSQL DB Location
set DBNAME=dcmdb Do Not Change This
set DBUSERNAME=admin By Default, Set to Admin Update if Needed
"%PGDIR%\bin\pg_dump.exe" -c %DBNAME% -U %DBUSERNAME% > %1%

Usage Example
pgbackup.bat ciscoFMSData-apr-10-2008 Provide Backup File Name to the Script
In addition to completely restore FMS, the following files need to be

backed up
C:\Program Files\Cisco Systems\MDS 9000\*.log
C:\Program Files\Cisco Systems\MDS 9000\bin\*
C:\Program Files\Cisco Systems\MDS 9000\conf\*
C:\Program Files\Cisco Systems\MDS 9000\db\*
C:\Program Files\Cisco Systems\MDS 9000\logs\*
C:\Program Files\Cisco Systems\MDS 9000\pm\db\*
BRKSAN-2891
PostgreSQL DB—Restore
Prior to restoring FMS database, please stop the FM server
Contents of pgrestore.bat file under C:\Program Files\Cisco
Systems\MDS 9000\bin
set PGDIR=C:\Program Files\PostgreSQL\8.2
set DBNAME=dcmdb
set DBUSERNAME=admin
echo "You will delete all existing data and restore db with file %1%"
echo "Please stop FMServer before db restore"
set /p ans=Are you sure you want to continue? [Y/N]
IF /i %ans% EQU Y ("%PGDIR%\bin\psql.exe" -U
%DBUSERNAME% %DBNAME% < %1%)
Usage Example
pgrestore.bat ciscoFMSData-apr-10-2008
BRKSAN-2891

Presentation_ID.scr
Run CLI Commands from FM
Execute Cisco SAN-OS CLI commands on multiple switches
Screen output is captured from each switch and copied over to the
FM Client desktop
“Run CLI Commands” dialog can be accessed from the Fabric
Manager Tools menu
Set Location to
Save Switch Output
BRKSAN-2891
Installation
BRKSAN-2891

Presentation_ID.scr
FM Server Install (1 of 3)
FMS (Licensed)
License is not required to
have a standalone FM
Server instance
Server License enables
additional functionality
Fabric Manager
Standalone
Customers with Cisco
FMS License can open
multiple fabrics
BRKSAN-2891
Device Alias—unique name across all VSANS in a fabric
FC Alias—Unique name across a VSAN
1
1
2
1 Earlier releases called for “Use Device Aliases in place of FC Aliases”, with default check
mark, new install rewords the same option to “Use FC Aliases as Fabric default”, and the
option is unchecked by default.
Recommendation: Go with default option (Devices Aliases recommended)
2 FM 3.1 install, default admin password was set to password. With new install, no default
admin password is defined, administrator configures password as part of install.
BRKSAN-2891

Presentation_ID.scr
Oracle 10g option offered
starting with FM 3.1
Oracle 10g is not packaged
with FM, and has to be installed
prior to installing the FM Server
Starting with 3.2(1) release,
HSQLDB has been replaced
with PostgreSQL as default
option
No significant performance
difference between Oracle 10g
and PostgreSQL
BRKSAN-2891
FM Client Install
FM Client can be installed from the
Web client or using the URL
Click on Download
to Install FM Client
http://server-ip-address/download.do
By default, only FMS users with

“network-admin” credentials are
allowed to download the FM Client
To allow FMS users with “network-
operator” role to download the
client, enable the property
web.allowDownload4All=true
in server.properties file located in

directory C:\Program Files\Cisco
Systems\MDS 9000\conf
BRKSAN-2891

Presentation_ID.scr
User Login and Fabric Discovery
Starting with FM 3.1
Step 1: FM User login authentication is a separate step from fabric discovery
Step 2 If FM server has open fabrics, the open fabric window is presented for
user to select a fabric; if no open fabrics, then new fabric discovery window is
presented
1 2
BRKSAN-2891
FMS—Multifabric Management
Ability to manage multiple fabrics simultaneously

Fabrics need to be discovered by the same FM Server instance
Each Fabric topology displayed in its own tab, as shown below
BRKSAN-2891

Presentation_ID.scr
SAN Monitoring
BRKSAN-2891
SAN Monitoring
SNMP events
Syslog messages
Thresholds
Callhome
Web client health analysis reports
Multipath
Host to storage connectivity
Storage to host connectivity
Zone discrepancy
Configuration analysis
Switch health
BRKSAN-2891

Presentation_ID.scr
SNMP Events
MDS has over 125+ MIBs that generate a large number
of events
SNMP vents are grouped by functionality that can be enabled or
disabled
Trap Group Default Recommended
Entity FRU No Yes
FCC No No
FC Domain No Yes
Name Server No Yes
Fabric Configuration Services (FCS) No No
FDMI No No
FSPF No Yes
License Yes Yes
RSCN No No
SNMP Authentication No No
VRRP Yes Yes
Zone No Yes
BRKSAN-2891
Forwarding Events to NOC

MDS has over 125+ MIBs that could potentially generate a large
number of events
NOC operates are trained to flag hardware failures and critical
failures
Working with customers Cisco has identified a subset of events that are of
interest to a NOC
Cisco recommends customers to implement the identified subset as a phase one
approach
The document Cisco MDS Event Monitoring v1.pdf details the identified events
Scripts have been developed by Cisco for the most common used NOC
applications—HP OpenView and IBM NetView
Syslog messages
Every release of MDS SAN-OS publishes the Syslog messages supported by that
release, every effort is made to keep the Syslog messages backward compatible
Syslog messages can be forwarded from MDS to any application that can parse
the messages and populate a monitoring application
BRKSAN-2891

Presentation_ID.scr
Syslog Messages
2200+ Syslog messages
Syslog messages are published with each release of SAN-OS
Syslog messages are classified into eight security levels
(1—emergency, 8—debug); syslog messages from MDS can be
forwarded to FM Server
Syslog messages can be viewed via Web Client
Non MDS Syslog messages can be forwarded to FM Server, by
setting “syslog.promiscuous = true” property via the Web Client
Default max rows in FM server database is set to 10K; when limit
is reached, logs are copied to a log file on the server
BRKSAN-2891
DM—Syslog (1 of 2)
Syslog messages can be forwarded to a maximum of three
syslog servers
Security level (1–8) can configured per functionality/module
BRKSAN-2891

Presentation_ID.scr
DM—Syslog (2 of 2)
Syslog messages can be sent to console by selecting
“ConsoleEnable”
Message severity level to be forwarded can be configured too
BRKSAN-2891
RMON—Threshold Monitoring
Device CPU, memory
FC services threshold per VSAN
Interfaces thresholds
Default is 100, need to configured to 512
32-bit alarms—512 per box
64-bit alarms—512 per box
BRKSAN-2891

Presentation_ID.scr
DM—Configured Threshold Monitors
Recommend using 64-bit counters over 32-bit counters

for monitoring link counters
BRKSAN-2891
MDS Callhome
MDS Callhome is independent of
OSM Callhome
Fixed set of predefined alerts and
trigger events on the switch
Multiple message format
options—short text, plain text,
XML
Up to 50 e-mail destination
addresses for each destination
profile
Multiple message categories
including system, environment,
switching module hardware,
supervisor module, hardware,
inventory, syslog, RMON, and test
BRKSAN-2891

Presentation_ID.scr
Health Analysis—Multipath
Find devices with no redundancy or inactive paths
BRKSAN-2891
Health Analysis—Connectivity
Storage to host
Host to storage
BRKSAN-2891

Presentation_ID.scr
Health Analysis—Zone Discrepancy
Not in VSAN Full zone distribution off
Not in fabric Default permit on
Single member zone Only initiators in zone
BRKSAN-2891
Health Analysis—Switch Health
In-depth switch health analysis verifies the status of all

critical switches, modules, ports, and Fibre Channel
services; over 40 conditions are checked
BRKSAN-2891

Presentation_ID.scr
Health Analysis—Configuration Analysis
Compares the configurations of the switch to a

policy file
Define what functions to check and what type of checks
to perform
Looks for mismatched values, and missing or extra
values; over 200 checks performed
BRKSAN-2891
Performance Collection
BRKSAN-2891

Presentation_ID.scr
DM—Summary Tab
Real-time
performance metrics
Charting option
Quick switch health
Filter by VSAN
BRKSAN-2891
DM—Logging Real-Time
Performance Data
Real-time stats
greatly help with
debugging
Log file saved under
“logs” directory as:
“switch_name_
summarylog.txt”
Logging happens
only while the
summary tab
window is open
BRKSAN-2891

Presentation_ID.scr
FM—Real Time ISL Stats
BRKSAN-2891
Historic Performance—Flows (1 of 4)
Flows provide important information about SAN traffic

patterns (top talkers)
FM Performance Collection collects flow statistics
based on source destination combination
Source and destination can be on different switches
First generation line cards support about 1000 flows per
module, second generation line cards support 2000
flows per module
As flow collection is based on source and destination
FCIDs, recommend persistent FCIDs enabled
BRKSAN-2891

Presentation_ID.scr
Flow configuration is based on active zone database

Flows are configured in hardware
Flow statistics Æ frame count and bytes are
incremented in real time
Flows cannot be reset—need to delete and add again
CLI Output of Flows Configured on an MDS
Source Destination VSAN

FCID FCID
BRKSAN-2891
Flow Performance Collection is a two-step
process, and need to be configured from the
FM Client; flow configuration setup has to be
repeated for each VSAN
The option “Type” refers to the collection
process; recommend that flows are collected
both ways; FMS server is smart to
consolidate the data at the time of reporting
Checking the “Clear old flows on modified
switches” option purges all old data related to
the FCID; please select this option with
careful consideration; once selected, no way
to restore lost the data
The option “Create flows on all cards,” gives
flexibility for physical port to be moved to
another module on the same switch; this
option available on SAN-OS 3.1 and later
BRKSAN-2891

Presentation_ID.scr
Second step of the
Flow wizard lists all
flows for the VSAN
Manually remove
flows of not interest
Finish configures the
selected flows on the
corresponding MDS
switches and FM
Server
FM Server need to
be restarted for it to
pick the new flow
configurations
BRKSAN-2891
Performance Data Collection

FM Server collects flow information
once every 5 minutes; this interval
cannot be changed
Performance data collected every
5 minutes is saved in flat files with
an “rrd” extension under the…
pm\db directory
Every hour a background process consolidates the data to the database
To limit the size of database, performance data collected is retained for a
finite period time; the length of data retention can be configured to
customers needs; longer retention periods of data will require larger disk
space; default configurations are:
5 minute interval samples for 48 hours
30 minutes samples for 14 days
120 minute samples for 2 months
1-day samples for 300 days
Using default retention periods, each flow takes 115 KB of disk space
By default ISL interfaces statistics are also collected once every 5 minutes;
the time interval can be modified to as low as once every 30 seconds
BRKSAN-2891

Presentation_ID.scr
Database Sizing
To limit the size of database,
performance data collected is
retained for a finite period time
FM Server collects flow
information once every 5 minutes;
this interval cannot be changed
ISL statistics can be configured to
collect in 30 second intervals; default, once every 5 minutes
Configure data retention periods based on need; longer retention periods
of data will require larger disk space; default configurations are:
5 minute interval samples for 48 hours
30 minutes samples for 14 days
120 minute samples for 2 months
1-day samples for 300 days
Performance data collected every 5 minutes is saved in flat files with an
“rrd” extension under the…pm\db directory
Every hour a background process consolidates the data to the database
Using default retention periods, each flow takes 115 KB of disk space
BRKSAN-2891
FMS Performance Monitoring—Summary

SAN summary
Link utilization
summary
Drill down
BRKSAN-2891

Presentation_ID.scr
Performance Monitoring—Flows
Top talkers
Clicking on the flow generates chart
BRKSAN-2891
Performance Prediction
Based on past data, and acceptable threshold

utilization percentage, predict future traffic growths
BRKSAN-2891

Presentation_ID.scr
FMS—Threshold
Configure threshold monitoring based on absolute

values or based on past performance (week/month/year)
BRKSAN-2891
Custom Reporting
Customized report configuration

On demand/scheduled report generation
BRKSAN-2891

Presentation_ID.scr
FMS Server—Fabric Monitoring
Events, syslog messages being forwarded to

FM server?
Performance collection problems?
BRKSAN-2891
FMS—MIB OID Monitoring

FM server provides an ability to poll on any MIB OID once every
5 minutes
In Web Client, under Admin/Configure/Others, select Add, and
provide the OID to be polled for
Can be configured for all switches in a fabric, or select switches
BRKSAN-2891

Presentation_ID.scr
FM Server Properties
File located “MDS 9000”;
default windows location
C:\Program Files\Cisco
Systems\MDS
9000\server.properties
Changes require Fabric

Manger Server restart
Make backup copy prior
to making any changes
Changes can be made
from Web Client
BRKSAN-2891
Key Takeaways
Cisco Fabric Manager deployment

Switch and fabric health analysis tools
SAN monitoring
Performance collection
FMS reporting
BRKSAN-2891

Presentation_ID.scr
Q and A
BRKSAN-2891
Recommended Reading
Continue your Cisco Live

learning experience with further
reading from Cisco Press
Check the Recommended
Reading flyer for suggested
books
Available Onsite at the Cisco Company Store

BRKSAN-2891

Presentation_ID.scr
Complete Your Online
Session Evaluation
Give us your feedback and you could win Don’t forget to activate
fabulous prizes. Winners announced daily. your Cisco Live virtual
account for access to
Receive 20 Passport points for each session all session material
evaluation you complete. on-demand and return
for our live virtual event
Complete your session evaluation online now in October 2008.
(open a browser through our wireless network Go to the Collaboration
to access our portal) or visit one of the Internet Zone in World of
stations throughout the Convention Center. Solutions or visit
www.cisco-live.com.
BRKSAN-2891
BRKSAN-2891

Presentation_ID.scr

Advanced MDS SAN Management: BRKSAN-2891

Cargado por

Información del documento

Descripción original:

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Advanced MDS SAN Management: BRKSAN-2891

Cargado por

Copyright:

Formatos disponibles

Advanced MDS SAN

© 2006, Cisco Systems, Inc. All rights reserved. 1

 Cisco Fabric Manager Overview

© 2006, Cisco Systems, Inc. All rights reserved. 2

FM 1.0 FM 1.3 FM 2.0 FM 3.1 FM 3.2 FM 3.3

Cisco Fabric Manager Components

Device specific view

© 2006, Cisco Systems, Inc. All rights reserved. 3

 Centralized management services

Fabric Manager Client

© 2006, Cisco Systems, Inc. All rights reserved. 4

Fabric Manager Server License Package

© 2006, Cisco Systems, Inc. All rights reserved. 5

Fabric Manager Standalone:

© 2006, Cisco Systems, Inc. All rights reserved. 6

Role-Based Access Control and Licensing

Componentization of FM Server J2EE Services

Discovery Inventory Interfaces

Event Performance RDBMS

SME ACL Security

© 2006, Cisco Systems, Inc. All rights reserved. 7

 Dual NIC—private/public network AAA Server

 FMS server to be deployed in

FMS Sizing Parameters

Number of Ports Managed by an FM Sever Instance

Monitoring Only Under 1000 10,000 10,000

© 2006, Cisco Systems, Inc. All rights reserved. 8

Ports per Fabric Fabric A Fabric B

Up to 5000 Ports Single FMS Server

5001–10,000 Ports FMS Server A FMS Server B

 A fabric to be managed by a single dedicated server

 Device Manager login uses switch AAA Server

 MDS can be used as a proxy

© 2006, Cisco Systems, Inc. All rights reserved. 9

configuration changes FM Client <-> MDS : SNMP

Server using Java RMI Web Client <-> FM Server : HTTP

FM Clients working from

© 2006, Cisco Systems, Inc. All rights reserved. 10

Configure the MDS

FM Server SSH 22 (TCP)

© 2006, Cisco Systems, Inc. All rights reserved. 11

FM Client 1 FM Server MDS

2162 SNMP TRAPS

FMS Behind a Firewall—3.2 and Above

© 2006, Cisco Systems, Inc. All rights reserved. 12

 Unique name across the  Limited to a VSAN

Device Aliases Are Distributed to All Switches in a

 Enclosures is a Fabric Manager functionality and is not supported by SAN-OS

© 2006, Cisco Systems, Inc. All rights reserved. 13

© 2006, Cisco Systems, Inc. All rights reserved. 14

All Disks for

FM Server Trap Registration

© 2006, Cisco Systems, Inc. All rights reserved. 15

Clean Up Trap List

Identify Valid Destinations and

# show snmp host

© 2006, Cisco Systems, Inc. All rights reserved. 16

FM Backup—3.1 and Before

 Regular backup of FM data highly recommended

© 2006, Cisco Systems, Inc. All rights reserved. 17

set DBNAME=dcmdb Do Not Change This

set DBUSERNAME=admin By Default, Set to Admin Update if Needed

Cisco Fabric Manager Overview

Centralized management services

Dual NIC—private/public network AAA Server

FMS server to be deployed in

A fabric to be managed by a single dedicated server

Device Manager login uses switch AAA Server

MDS can be used as a proxy

Unique name across the Limited to a VSAN

Enclosures is a Fabric Manager functionality and is not supported by SAN-OS

Regular backup of FM data highly recommended

In addition to completely restore FMS, the following files need to be

By default, only FMS users with

Ability to manage multiple fabrics simultaneously

Recommend using 64-bit counters over 32-bit counters

Find devices with no redundancy or inactive paths

In-depth switch health analysis verifies the status of all

Compares the configurations of the switch to a

Flows provide important information about SAN traffic

Flow configuration is based on active zone database

Based on past data, and acceptable threshold

Configure threshold monitoring based on absolute

Customized report configuration

Events, syslog messages being forwarded to

Changes require Fabric

Cisco Fabric Manager deployment

Continue your Cisco Live